JCIDS Process

Information Support Plan (ISP)

An Information Support Plan (ISP) describes a system’s dependencies and interface requirements in sufficient detail to enable testing and verification of Information Technology (IT) and National Security Systems (NSS) interoperability and supportability requirements. The ISP is required for all Acquisition Category (ACAT) programs that connect in any way to the communications and information infrastructure including both IT and NSS programs. The ISP is summarized in the Acquisition Strategy and reviewed at Milestones B and C and is prepared concurrently and collaboratively with the Capability Development Document (CDD) or Capability Production Document (CPD). [1]

An ISP provides 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. An ISP provides the methodology for meeting a program’s information needs and managing the issues and risks associated with those needs. [1]

The ISP comes in two forms: [1]

  • Traditional ISP
  • Tailored ISP

The ISP development process requires an Information Support Plan (ISP) Analysis of a program’s integrated architecture and processes associated with meeting a capability. This ISP analysis identifies information need, net-centric, interoperability, and supportability issues and assesses compliance with Assistant Secretary of Defense for Networks and Information Integration/DoD Chief Information Officer information policy and goals. [1]

The ISP contains interface descriptions, infrastructure, and support requirements, standards profiles, measures of performance, and interoperability shortfalls. The ISP includes:

  • an operational employment concept
  • system interface descriptions
  • required information exchanges
  • IT and NSS information support requirements
  • potential issues
  • proposed solutions

An ISP answers the following seven questions for information needed to support the operational and functional capabilities of a system.

  • What information is needed?
  • How good must the information be?
  • How much information (needed or provided)?
  • How will the information be obtained (or provided)?
  • How quickly must it be received in order to be useful?
  • Is the information implementation net-centric?
  • Does it comply with DoD information policies?

Tailored Information Support Plan (TISP)

The TISP provides a dynamic and efficient vehicle for certain programs ACAT II and below to produce requirements necessary for Interoperability and Supportability (I&S) Certification. Select Program Managers (PMs) may request to tailor the content of their ISP. For programs not designated Office of the Secretary of Defense (OSD) special interest by the Assistant Secretary of Defense for Networks and Information Integration (ASD(NII)), the component will make the final decision on the details of the tailored plan subject to minimums specified in the TISP procedures from the CJCSI 6212.01 resource page and any special needs identified by the J-6 for the I&S certification process.

Development and Reviews

Program Managers must develop and submit for review the ISP online by entering system information through the Global Information Grid (GIG) Technical Guidance-F (GTF) (https://gtg.csd.disa.mil). [3]

REGULATORY:  Applicable to all Information Technology (IT), including National Security Systems (NSS). A draft is due for Development RFP Release, approved at Milestone B and updated at the Critical Design Review (CDR). The ISP of record is due prior to Milestone C; an updated ISP of record may be required during Operations & Support (O&S). [2]


AcqLinks and References:

Updated: 2/4/2021

Print Friendly, PDF & Email

Leave a Reply

Scroll to Top