7.3.6. Information Support Plan (ISP), Enhanced Information Support Plan (EISP), and Tailored Information Support Plan (TISP)
7.3.6.1. Review of Information Support Plan (ISP)-Specific Mandatory Policies
7.3.6. Information Support Plan (ISP), Enhanced Information Support Plan (EISP), and Tailored Information Support Plan (TISP)
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.
The ISP comes in several forms as a document (ISP or TISP) or as data in the form of an EISP tool (for both ISP and TISPs). The preferred format is using the data-centric EISP tool. The EISP is evolving to become the only acceptable form for ISP content. The ISP provides the PM a mechanism to identify information-related dependencies, to manage these dependencies and to influence the evolution of supporting systems to meet the demands of the system as it evolves to meet the warfighter's needs and capabilities. In the case where the supporting system will not be available, the ISP should provide the PM with awareness of this problem in sufficient time to adjust the program in the most cost effective and operationally efficient manner.
The end-product of the ISP/EISP/TISP is the identified issues and risks associated with information needs and dependencies of the program. Information issues and risks should be treated as any program issue or risk as defined in the AT&L's "Risk Management Guide for DoD Acquisition, Sixth Edition, Version 1, August, 2006." Information issues and risks should be managed as defined in this guide and presented in acquisition decision meetings (such as Overarching Integrated Product Team meetings) by the PM as any other area of issue and risk is presented (e.g., reliability risks).
7.3.6.1. Review of Information Support Plan (ISP)-Specific Mandatory Policies
- DoD Instruction 5000.02, Enclosure 4, Table 3, as amended by the 23 June 2011 PDUSD(AT&L) Memorandum “Improving Milestone Process Effectiveness”"Regulatory Requirements Applicable to All Acquisition Programs," requires that all acquisition programs, regardless of acquisition category level, submit an ISP at Pre-EMD Review (Initial ISP), CDR (Revised ISP), Milestone C (ISP of Record, unless waived), at major system or software updates (Updated ISP), and at Program Initiation for ships (Initial ISP).
- DoD Instruction 4630.8, Enclosure 4 provides a ISP content requirements and guidelines..
- CJCS Instruction 6212.01 also provides detailed implementing guidance regarding the ISP and specifically the TISP.
- Intelligence Community Policy Guidance 801.1 provides requirement for Intelligence Community programs to develop an ISP.
DAG Tutorial 
