Information Support Plan AnalysisAdd to favorites
Information Support Plan (ISP) Analysis is concerned with analyzing a program’s information needs and dependencies. This analysis must be considered in the context of the process that is critical to the capability being completed by the system. It examines the critical mission threads associated with a program and compare the operational architecture views to the system architecture views to make sure all information needs and dependencies that are critical to the capability being developed are met. The analysis should include: 
- Analysis of the qualitative and quantitative sufficiency of Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) support (e.g., hardware, software, processes, etc.) should be accomplished in terms of the operational/functional capabilities that are being enabled.
- An understanding of the operational/functional capabilities and the metrics that define whether they are being performed adequately.
- An understanding of what enabling functional capabilities must be performed in order to achieve a higher-level capability (C4ISR functions will almost always be enabling capabilities).
- An understanding of which players (nodes) will direct or perform the missions associated with delivering the capabilities.
- An understanding of DoD Information Policies.
- A definition of the Time Phase in which the analysis is to be accomplished. A user identifies the Time Phase, or Time Phases, their program operates within and defines the Time Phase Name (i.e., increment, block, spiral, et al.), Year, and a Description.
The following thirteen (13) steps are based on using the Integrated Architecture developed in accordance with the DoD Architectural Framework, during the JCIDS process. For more info on the steps visit Defense Acquisition Guidebook (DAG) – Chapter 126.96.36.199.2
- Identify the warfighting missions and/or business functions within the enterprise business domains that will be accomplished/enabled by the system being procured.
- Identify information needed to enable operational/functional capabilities for each warfighting mission identified in Step 1 by performing functional capability decomposition.
- Determine the operational users and notional suppliers of the information needed.
- Establish the quality of the data needed to enable the functions identified in OV-5 and performed by the operational nodes in OV-2 (Operational Node Connectivity).
- Determine if timeliness criteria exist for the information.
- Determine/Estimate the quantity of information of each type that is needed.
- Discuss the way information will be accessed or discovered.
- Assess the ability of supporting systems to supply the necessary information.
- Assess Radio Frequency (RF) Spectrum needs.
- Assess Net-Centricity.
- Discuss the program’s inconsistencies with the DoD Enterprise Architecture and the program’s strategy for getting into alignment.
- Discuss the program’s Information Assurance (IA) strategy. Also provide a reference to the Program Protection Plan (PPP), if applicable.
Identify information support needs to enable development, testing, and training.
- ISP preparation and format can be found in DoD Instruction 4360.08 Enclosure 4
- Traditional ISP content and analysis steps can be found in Chapter 188.8.131.52 of the DAG
AcqLinks and References:
-  Defense Acquisition Guidebook (DAG) – Chapter 7
- DoD Instruction 4360.08 “Procedures for Interoperability and Supportability of IT and NSS – Enclosure 4
- CJCSI 3170.01 “JCIDS”
- CJCSI 6212.01F “Net Ready Key Performance Parameter (NR KPP)” – 12 March 12
- Website: DoD Chief Information Officer
- Website: Defense Information Agency (DISA)
- Website: Defense Information Agency (DISA) “Information Assurance Support Environment”
- Website: DAU Information Technology Portal
- Website: DoD Information Enterprise Architecture