Milestone I includes development of the Exhibit 300, either a “Planning Application” or a “Full Acquisition”. The applications can be combined depending on whether preliminary funding or full funding is being requested.

If preliminary funding for project development is needed, a preliminary Exhibit 300, the “Planning Application” should be prepared. The “Planning Application” will be reviewed by the Office of Information and Technology (technical review), the EIB Panel (strategic and financial review), the EIB, and the SMC (if required) for approval and funding.

If full funding is needed for the upcoming budget year a complete Exhibit 300 “Full Acquisition” should be prepared. The Exhibit 300 will be reviewed by the Office of Information and Technology (technical review), the EIB Panel (strategic and financial review), the EIB, and the SMC (if required) for approval and funding.

Planning Application (Exhibit 300) for Preliminary Funding: The Planning Application further defines this concept. It also includes a high-level evaluation of alternatives for an IT solution. The document should address functional, security, performance, and reliability requirements, concept of operations, high-level use cases, business case, technical approach, acquisition, testing and fielding strategy, training and documentation requirements, schedule, staffing, and skills requirements. Comparisons of alternative concept solutions normally result in identification of the most promising system concept. The Exhibit 300 also needs to include Return-on-Investment and Cost Benefits analysis estimates.

If the project is approved, preliminary funding will be provided and the project will be included in the budget request. The, Full Acquisition Exhibit 300, will be required for the project by the following summer, before the budget year for which it is funded begins. This should document in more detail the scope, schedule, cost resource requirements, test strategy, risk profile and mitigation plan, project organization and staffing, operational support strategy, detailed life-cycle cost, and detailed business case. OMB Circular A-11, Part VII, Section 300 provides full instructions for this document.

Concept Development for Full Funding: If full funding is needed for the upcoming budget year a complete Exhibit 300 (“Full Acquisition”) should be prepared. At Milestone I, additional documentation (in addition to the information from Milestone 0) is required that supports Exhibit 300, such as:

▲    Completed Row 2 of the Zachman Framework, the organizational business processes from the perspective of  line and staff managers, --revalidating the information relative to the EA addressed in the Milestone 0 review, showing how the project fits into the allocated functional baseline and integration points established in row 2 of the framework. In addition, the Project Manager is expected to take the functional requirements and integration points contained within row 2 and the Technical Reference Model (TRM) and standards profile and begin development of the functional and technical requirements baseline for their project that is the subject of row 3 of the framework, the IT system from the perspective of the Project Manager.

▲    An initial change management and communications plan

▲    A project organization plan and staffing inventory

▲    An updated mapping of the project concept to  Performance Goals