Acquisition Management Policy - View selected sections

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

2.3.3 : Concept and Requirements Definition Readiness Decision _{(Revised 11/2009)}

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 11/2009)}

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 a valid 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 cognizant investment decision authority of the decision to begin concept and requirements definition. This decision does not apply to small ACAT 5 needs managed by the Information Technology Executive Board.

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.