Acquisition Management Policy - View selected sections

Acquisition Management Policy _{(Revised 4/2009)}

2.3.3 : Concept and Requirements Definition Readiness Decision _{(Revised 8/2008)}

2.3.3.1 : Entrance Criteria _{(Revised 7/2008)}

2.3.3.2 : Vice President (ATO) or Director (non-ATO) Actions _{(Revised 7/2008)}

2.3.3 : Concept and Requirements Definition Readiness Decision _{(Revised 8/2008)}

The concept and requirements definition readiness decision occurs when an enterprise architecture roadmap indicates action must be taken to address a critical mission shortfall or opportunity. At this decision, the Director, ATO Systems Engineering verifies that the service need proposed to enter concept and requirements definition is the highest priority investment opportunity within an enterprise architecture roadmap and that planning and resources for concept and requirements definition are in place. The Director, ATO Systems Engineering notifies the Joint Resources Council and cognizant subordinate investment review board of the decision to begin concept and requirements definition. This decision does not apply to small administrative or mission support needs managed by the Information Technology Executive Board unless so designated.

2.3.3.1 : Entrance Criteria _{(Revised 7/2008)}

The following is required for the concept and requirements definition readiness decision:

Service shortfall or opportunity is in an enterprise architecture roadmap and is the highest priority at the time; and the
Plan for concept and requirements definition is approved.

2.3.3.2 : Vice President (ATO) or Director (non-ATO) Actions _{(Revised 7/2008)}

The Vice President (ATO) or Director (non-ATO) of the service organization with the mission need:

Makes the decision to enter concept and requirements definition.