|
Actions Required to Comply With Subtitle III/CCA (Reference (v))
|
Applicable Program Documentation1
|
| 1. Make a determination that the acquisition supports core, priority functions of the Department. 2 |
ICD Approval
|
| 2. Establish outcome-based performance measures linked to strategic goals. 2, 3 |
ICD, CDD, CPD and APB approval
|
| 3. Redesign the processes that the system supports to reduce costs, improve effectiveness and maximize the use of COTS technology. 2, 3 |
Approval of the ICD, Concept of Operations, AoA, CDD, and CPD
|
| 4. Determine that no Private Sector or Government source can better support the function. 4 |
Acquisition Strategy page XX, para XX
AoA page XX
|
| 5. Conduct an analysis of alternatives. 3, 4 |
AoA
|
| 6. Conduct an economic analysis that includes a calculation of the return on investment; or for non-AIS programs, conduct a Life-Cycle Cost Estimate (LCCE). 3, 4 |
Program LCCE
Program Economic Analysis for MAIS
|
| 7. Develop clearly established measures and accountability for program progress. |
Acquisition Strategy page XX
APB
|
| 8. Ensure that the acquisition is consistent with the Global Information Grid policies and architecture, to include relevant standards. |
APB (Net-Ready KPP)
ISP (Information Exchange Requirements)
|
| 9. Ensure that the program has an information assurance strategy that is consistent with DoD policies, standards and architectures, to include relevant standards. 3 |
Acquisition Information Assurance Strategy
|
| 10. Ensure, to the maximum extent practicable, (1) modular contracting has been used, and (2) the program is being implemented in phased, successive increments, each of which meets part of the mission need and delivers measurable benefit, independent of future increments. |
Acquisition Strategy page XX
|
| 11. Register Mission-Critical and Mission-Essential systems with the DoD CIO. 3, 5 |
DoD IT Portfolio Repository
|
|
1. The system documents/information cited are examples of the most likely but not the only references for the required information. If other references are more appropriate, they may be used in addition to or instead of those cited. Include page(s) and paragraph(s), where appropriate.
2. These requirements are presumed to be satisfied for Weapons Systems with embedded IT and for Command and
Control Systems that are not themselves IT systems.
3. These actions are also required to comply with section 811 of Reference (ag).
4. For NSS, these requirements apply to the extent practicable (section 11103 of Reference (v))
5. Definitions:
Mission-Critical Information System. A system that meets the definitions of "information system" and "national security system" in the CCA (Reference (v)), the loss of which would cause the stoppage of warfighter operations or
direct mission support of warfighter operations. (The designation of mission critical shall be made by a
Component Head, a Combatant Commander, or their designee. A financial management IT system shall be considered a mission-critical IT system as defined by the Under Secretary of Defense (Comptroller) (USD(C)).) A "Mission-Critical Information Technology System" has the same meaning as a "Mission-Critical Information System."
Mission-Essential Information System. A system that meets the definition of "information system" in Reference (v), that the acquiring Component Head or designee determines is basic and necessary for the accomplishment of the organizational mission. (The designation of mission-essential shall be made by a Component Head, a Combatant Commander, or their designee. A financial management IT system shall be considered a mission-essential IT system as defined by the USD(C).) A "Mission-Essential Information Technology System" has the same meaning as a "Mission-Essential Information System."
|
DAG Tutorial 
