Provide a high-level system description and discussion of C4ISP contents
Identify the program, acquisition category, and status within the acquisition cycle
State the purpose and scope of the C4ISP
Reference all approved (or validated) and draft documents affecting the finance and accounting and information technology aspects of the system that is being acquired
2.0 System Description
Provide a high-level overview of the specific system being acquired
Provide a graphic (block diagram) that shows the major elements/subsystems that make up the system being acquired, and how they fit together
Describe the system's function, its mission criticality/essentiality, interfaces with other systems, and primary databases used or supported
3.0 Operational Employment
Describe how the system being acquired will be employed, and the environment within which it will operate
Address all information interfaces, exchange requirements, and information technology (IT) capabilities (including National Security System)
3.1 Operational Employment Concept
Define the system's operational concept from a functional perspective
Clearly relate missions performed to the joint mission areas specified in CJCS memorandum CM-1014-00, "Joint Mission Areas to Organize the Joint Operational Architecture" dated September 6, 2000
Identify system functions that are critical for specific missions
Describe at a high level, the operational environment(s) within which the system will operate
3.1.1 Operational Architecture Views
Provide a High Level Operational Concept Graphic (OV-1) for each mission area supported by the system
For each functional area supported by the system, provide an Operational Node Connectivity Description (OV-2)
For each OV-2, provide supporting text that describes the roles of each operational facility (OPFAC) node in the architecture
Provide multiple OV-1 and OV-2 graphics if necessary because of operational concept changes over time
3.1.2 Information Exchange Requirements (IERs)
Provide an OV-3 (Operational Information Exchange Matrix) operational architecture view that is cross-referenced to the OV-2 views, showing all individual IERs represented by the need lines
All IERs that are necessary for successful performance of the mission must be represented in the OV-2 and OV-3 views, whether or not they are identified as "critical" IERs
Describe the interoperability key performance parameter (KPP), and show the construction of threshold and objective values, with supporting explanation of IER criticality
3.2 Operational Employment Requirements
Identify the impact of the information exchanges and information needs on the supporting infrastructure, and on other system interfaces that are critical to mission success
Discuss the threat and tactical considerations, describe time-critical events required to meet operational objectives, and address workload considerations based on the operational employment concept
Include Operational Event/Trace Description (OV-6c) views when needed to clarify the time-critical nature of information for each mission
3.3 Systems Architecture View
Provide time-phased, mission-based graphical and narrative descriptions of current/future systems and connectivity providing, receiving, or supporting the functions of the system being acquired
For each mission or functional area described in Section 3.1, show the systems that are anticipated to fulfill the needs
For each mission area operational view (OV-2) described in section 3.1, there must be a corresponding System Interface Description (SV-1) view
Each notional OPFAC should be replaced by either an existing or a planned system or facility, and each need line should represent a particular communication system that will provide a path for the information exchange
The SV-1 architecture view(s) must correlate with the SV-1 view(s) from the associated ORD
Provide increasing detail as the acquisition progresses from milestone to milestone and from evolutionary block to block
Include existing or planned systems and networks
Describe the relevant information exchange capabilities, operation, and limitations of each system within the architecture
Identify key nodes for information exchanges including materiel equipment, physical connections, association of systems to nodes, circuits, networks, warfighting platforms, and relevant specific system and component performance parameters
3.4 Systems IER Matrix Information
Prepare IER matrix
Include systems and communications information for each need line in the System Interface Description (SV-1)
3.5 Technical Architecture
Identify applicable technical standard(s) for each IER, based upon the DoD Joint Technical Architecture (JTA)
Include a discussion of relevant interoperability considerations, addressing operations with joint and combined forces in particular
Discuss how the standards are or will be implemented, and identify applicable existing technical guidance and tailoring
Provide a Technical Architecture View (TV-1) that identifies the applicable standard(s) for each row of the OV-3 operational IER matrix (Section 3.1.2)
3.6 Defense-Wide Integrated Architectures.
Provide a qualitative assessment of time-phased operational systems, and technical architecture views in Sections 3.1 through 3.5
Ensure views are consistent with the evolving Global Information Grid (GIG) integrated architecture (including the joint operational and technical architectures)
Ensure views are consistant with relevant mission area integrated architectures, as of the point in time at which the C4ISP is prepared
Highlight and characterize significant differences
Describe the interoperability, supportability, or sufficiency impact of these differences
4.0 Derived C4I Support Requirements
Document the derived system capabilities required to satisfy the development, testing, training, and operational employment of the system
Identify derived requirements, interoperability or support needs during system development
Section 4 should be organized by the function performed and the system that provides information to, or receives information from, the system being acquired
Focus on the system support requirements necessary for the system to be successfully developed and to perform its intended function, both as a consumer and as a producer/distributor of information
The STT methodology is the preferred approach for identifying derived requirements through hierarchical decomposition of the operational tasks performed by the system being developed
4.1 C4ISR Support to Operations
Couple each employment concept (Section 3.1) with the corresponding employment rates (Section 3.2) and the system architectures (Section 3.3) to assess and characterize the requirements placed on infrastructure support systems and activities.
4.1.1 IT Infrastructure Support to Operations
Describe the support required from the C4 infrastructure and other IT, including NSS, (e.g., other weapon systems) by the system being acquired
Each sub-section should show the demands of the system being acquired on the particular supporting/interfacing C4 system for each mission
Provide information for each external system interface
Identify the primary IT capabilities of each system, including computer hardware/software, workstations, peripherals, central processors, and routing processors
Include relevant options such as scalability, operating system or software characteristics, etc.
Identify new or updated data that may be required by the system
Identify data rates under a range of operating conditions
Identify the information security classification level(s) required and capabilities employed
4.1.2 ISR Support to Operations
4.2 C4ISR Support to Other Functions
Describe any special IT infrastructure support that is required for acquisition or sustainment of the system
4.2.1 C4ISR Support to Development
Describe any special IT infrastructure support that is required for the successful development of the system being acquired
Supporting systems should be identified with the nature of the support they provide clearly shown
4.2.2 C4ISR Support to Testing
Describe the plan to provide IT infrastructure support for the system's developmental and operational test and evaluation, including testing of IERs and the interoperability KPP
Plans for conducting tests should be addressed in the Test and Evaluation Master Plan (TEMP)
Address required support for interoperability demonstrations and testing both within the DoD Component (internal testing), and by external activities such as the Joint Interoperability Test Command (JITC)
Identify all information and IT infrastructure capabilities necessary for realistic test and evaluation
4.2.3 C4ISR Support to Training
Identify the IT infrastructure required to support training activities both prior to and after IOC
Discuss anticipated infrastructure support to training required for each of the three mutually supporting pillars of training: unit, institution, and self-development
Identify anticipated operator, crew, and netted training that may be required to support joint or combined operations
Identify anticipated use of computer-based training modules, simulations, and major exercises
5.0 Potential C4I Support Shortfalls and Proposed Solutions
Address known or potential shortfalls in required IT infrastructure support capabilities
Identify all derived IT infrastructure support requirements (Section 4) that may not be satisfied by the date that they are needed
Identify infrastructure-related shortfalls of other interfacing systems as well as shortfalls in the IT infrastructure
Identify potential shortfalls that are reasonably anticipated to exist, even though analysis is incomplete
Summarize shortfalls in matrix format, organized by the supporting/interfacing system causing or affected by the shortfall
Provide supporting discussion for each row of the matrix
Specify the impact of failure to resolve the shortfalls in terms of program resources and schedule, inability to achieve threshold performance, and system or warfighter vulnerability
Address the system's reliance on technology not currently available or affordable, and the system's reliance on other systems under development, or its dependency on schedules of other programs
Identify the plan and schedule to remedy each shortfall, including key issues that must be resolved
Provide a recommendation identifying the organization with the responsibility and authority to address the shortfall if the solution to an identified shortfall lies outside the control of the program office
5.1 Operational Employment Shortfalls
Identify known or potential shortfalls that will affect the ability to employ the system as envisioned by the ORD and employment concept
Address both the inability of the IT infrastructure to meet quantitative or qualitative requirements, and the inability of IT interfaces to provide or receive information as intended
Identify interface dependencies that remain undefined or unsatisfied, especially those beyond program office control
Identify potential conflicting demands on infrastructure support from other systems and activities
5.2 Other Shortfalls
Identify known or potential shortfalls that impact other system acquisition and sustainment functions
5.2.1 Development Support Shortfalls
Identify known or potential shortfalls that impact definition and development of the system being acquired
Focus particularly on finance and accounting related support needed to define the system
Identify shortfalls that limit or preclude design tradeoff studies or other analyses during system development and demonstration
5.2.2 Testing Support Shortfalls
Identify known or potential shortfalls that impact development or operational testing of the system
Identify potential discontinuities between the testing plan and supporting system and activity availability
5.2.3 Training Support Shortfalls
Identify known or potential shortfalls that impact the proposed training schemes for both system development and test, and operational employment
Appendix A. References
Identify all related documents (with dates) used to prepare the C4ISP
Appendix B. Information Exchange Requirements (IERs)
Provide the set of IERs (and supporting discussion) for each operational and system interface, unless this information is incorporated in Section 3.1.2 of the C4ISP
Appendix B will consist of an OV-3 matrix with narrative discussion as necessary
Provide a copy of the OV-3 matrix as a separate, appended spreadsheet file
Appendix C. Technical Standards
Provide the TV-1 matrix (and supporting discussion), with each row cross-referenced to the applicable row of the OV-3 matrix, unless this information is incorporated in Section 3.5 of the C4ISP
Appendix D. Interface Control Agreements
Identify documentation (e.g., MOAs and MOUs) that indicates what agreements have been made (and those that are required to be made) between this system and other interfacing systems
Appendix E. Acronym List
Provide formal definitions for key terms
Other Appendices or Annexes
Provide supporting information not included in the body of the C4ISP
[Edit footer.html to set your custom footer here]
Current URL: http://compliancemanager.com/ModelStore/ModelPreview?ModelStoreId=2fb6cf50-cce5-4079-878e-750074f7b6b1 Base URL: http://compliancemanager.com/ Current URL Domain Name: compliancemanager.com
1.0 Introduction
Provide a high-level system description and discussion of C4ISP contents
