Chapters in the Defense Acquisition Guidebook that addresses this topic:
Chapter 7.3.6. Information Support Plan (ISP), Enhanced Information Support Plan (EISP), and Tailored Information Support Plan (TISP)
The ISP (formerly called the Command, Control, Communication, Computers, and Intelligence Support Plan (C4ISP)) is intended to explore the information-related needs of an acquisition program in...
The ISP is intended to explore the information-related needs of an acquisition program in support of the operational and functional capabilities the program either delivers or contributes to. ISPs provide a means to identify and resolve potential information support implementation issues and risks that, if not properly managed, will limit or restrict the ability of a program to be operationally employed in accordance with the defined capability. The ISP focuses on net-readiness, interoperability, information supportability, and information sufficiency concerns. The ISP process is one of discovery, requiring analysis of the program's architecture and processes associated with meeting a capability. This analysis identifies information need, net-centric, interoperability, and supportability issues and assesses compliance with the DoD Chief Information Officer’s (DoD CIO) stated information policy and goals.
Chapter 7.3.6.2 Information Support Plan (ISP) Integration into the Acquisition Life Cycle
An ISP provides the methodology for meeting a program's information needs and managing the issues and risks associated with those need. It ensures compliance with DoD CIO policy and is used by various other activities to monitor compliance and sufficiency. The Joint Staff utilizes the ISP in the Interoperability and Supportability Certification process; J2 utilizes the ISP for intelligence supportability (CJCS Instruction 3312.01); and the ISP is used as part of Title 40/CCA statutory oversight, oversight of Information Assurance (IA), spectrum supportability, and the National Signature Program...
Chapter 7.3.6.7. Information Support Plan (ISP) Content
Summarize the program's relationships to relevant Joint Operating Concepts (JOCs) and/or Joint Functional Concepts (JFCs) (e.g., focused logistics), as described in the program's JCIDS documents. Provide an OV-1 (High-Level Operational Concept Graphic) for the basic program and descriptive text. For programs not covered by JCIDS, analogous documentation may be used.
Chapter 7.3.6.9. Information Support Plan (ISP) Waiver Process
The requirement for an ISP may be waived when the requirement for JCIDS documentation has been waived, Joint Staff has determined that the Net-Ready Key Performance Parameter or Interoperability Key Performance Parameter are not needed, or the program does not meet any of the criteria identified in paragraphs 2.2.2, 2.2.3, and 2.2.4 of DoD Instruction 4630.8. Additionally, programs accepted under the Legacy System Interoperability Validation and Certificate Request Process are waived from producing an ISP.
