7.2.4. Integration into the Acquisition Life Cycle
7.2.4.1. Before Milestone A
7.2.4.2. Before Milestone B
7.2.4.3. Before Milestone C
7.2.4.4. After Milestone C and the Full-Rate Production Decision Review/Full-Deployment Decision Review
7.2.4. Integration into the Acquisition Life Cycle
The following sections outline steps that the DoD Components, Combat Developers, Sponsors, Domain Owners, DoD Agencies, Program Managers, and/or other assigned managers should take to facilitate DoD Information Enterprise Architecture (IEA) compliance and net-centric information sharing when acquiring Information Technology-enabled capabilities that will interoperate within the Global Information Grid.
At Milestones, A, B, and C, architects should assure that any new architectural models they develop conform to the current version of the DoD Architecture Framework (DoDAF). The latest version of the DoDAF is always available on the DoD Architecture Registry System (DARS) website, URL https://intelshare.intelink.gov/sites/dars/default.aspx. Existing architecture models that require an update for reasons other than a DoDAF version change should include the updates necessary to conform with the most current DoDAF. Stable architecture models that do not otherwise require an update do not need to be updated solely because the DoDAF has changed. Also, IAW DoD policy, all AV-1s must be registered in the DARS. Instructions on how to do this are on the DARS portal.
7.2.4.1. Before Milestone A
Ensure that appropriate steps are taken to prepare or update a concept of operations and an operational view (High-level Operational Concept Description, OV-1) of the integrated (solutions) architecture for key mission areas and business processes using the DoD Architecture Framework (DoDAF) and the guidance in CJCS Instruction 6212.01. The Initial Capabilities Document (ICD) should reflect this architecture work, as prescribed by CJCS Instruction 3170.01 and in the format provided in the JCIDS Manual. It also supports analysis of alternatives, business process reengineering efforts, development of the acquisition strategy and acquisition information assurance (IA) strategy, and provides key artifacts that support development of the Information Support Plan. Ensure that architectures adhere to the DoD net-centric strategies.
Ensure that the mandatory architecture views align with the DoD Information Enterprise Architecture (IEA) and show linkage to parent enterprise architectures, where available, and DoD Component and DoD-level Capability Portfolio Management architecture descriptions as they emerge.
Compliance with the DoD IEA is mandatory for any platform, program of record, system, subsystem, component, or application that conducts communications. Business systems should align with the Business Enterprise Architecture.
Develop an Initial Capabilities Document (Intelink account required) to describe capability gaps identified through analysis of joint concepts and solutions architectures. Use the criteria in CJCS Instruction 6212.01 to ensure the Initial Capabilities Document and supporting OV-1 address required interoperability standards.
7.2.4.2. Before Milestone B
Build or update the architecture and supporting views (All Views, Capability Views, Data and Information Views, Operational Views, Project Views, Services Views, Systems Views, and Standards Views).
Develop a Capability Development Document, as prescribed by CJCS Instruction 3170.01 in the format provided in the JCIDS Manual, and a Net-Ready Key Performance Parameter (NR-KPP) that address the interoperability and Information Assurance requirements described in CJCS Instruction 6212.01. Address issues associated with the updated architecture, the Capability Development Document, and the DoD IEA .
Use the required architecture products to support development of the Information Support Plan.
Begin development of the Information Support Plan for review. Use the criteria in CJCS Instruction 6212.01 to guide the acquisition of net-centric capabilities.
7.2.4.3. Before Milestone C
Update the architecture and supporting views (All Viewpoint, Capability Views, Data and Information Views, Operational Views, Project Views, Services Views, Systems Views, and Standards Views) and ensure changes are reflected in the Capability Production Document, as prescribed by CJCS Instruction 3170.01 in the format provided in the JCIDS Manual, and in the Net-Ready Key Performance Parameter (NR-KPP). If the program is entering the acquisition process at Milestone C, develop an NR-KPP using guidance in CJCS Instruction 6212.01.
Address any remaining issues associated with Service-Level Agreements. A Service-Level Agreement defines the technical support, business parameters, and/or critical interface specifications that a service provider will provide to its clients. The agreement typically spells out measures for performance parameters and protocols used in interfacing, and consequences for failure.
Ensure the program delivers capabilities responsive to the Capability Production Document and meets interoperability and information assurance requirements reflected in the updated NR-KPP.
Use the criteria in CJCS Instruction 6212.01 to ensure services and data products delivered by the acquisition align with the Department's objectives for net-centricity.
Prepare and submit the Information Support Plan for final review.
Address all information exchange requirements as part of the Information Support Plan and the Information Technology and National Security Systems Interoperability Certification processes.
7.2.4.4. After Milestone C and the Full-Rate Production Decision Review/Full-Deployment Decision Review
Continue life-cycle compliance with the Information Support Plan Interoperability Requirements Certification and the Information Technology and National Security System Interoperability Certification.
Continue life-cycle compliance with Information Assurance Certification and Accreditation.
DAG Tutorial 
