DODI 5000.75 Appendix 4B: Implementation Plan


a. The implementation plan provides sufficient detail on the work being performed to manage the delivery of the capability and support leadership decisions at the program level and higher.

b. The implementation plan is not a specific document. Instead, it is the content needed by the program office to manage delivery of the capability, as stored and used by the program office in whatever applicable format or repository is needed. The acquisition strategy content of the implementation plan may need to be maintained separately to compartmentalize acquisition sensitive information. Similarly, technical content concerning cybersecurity may also be maintained separately.

c. The program may rely on external content such as portfolio procedures to govern technical management. In which case, the program implementation plan content supplements the portfolio procedures only as needed to tailor the program.


The implementation plan will include:

a. Reference information to identify the capability requirements that the implementation plan supports.

b. A description of planned decision points with governance details that describe decision authorities, information requirements that will support the decision, and actions the decision will authorize.

c. A description of business process actions and leaders responsible. Common business process actions include:

(1) Implementation of law, regulation, policy or business process changes, including those that do not require business systems and those that must occur before the business system can be acquired.

(2) Development of training materials in support of business process changes.

(3) Conduct of user training and deployment in support of the business system.

d. A description of acquisition actions and leaders responsible. Common acquisition actions include:

(1) Requests for information, peer reviews, RFPs, and contract awards for systems integration.

(2) Definition and modeling of functional requirements, inputs and outputs, and design specifications.

(3) Software design, development and testing.

(4) Developmental and operational test and evaluation.

(5) Technical and management assessments on the progress of the program. The technical and management assessment structure will reflect the program’s tailored software development lifecycle and may include events such as design reviews and test readiness reviews or short iteration retrospectives and acceptance reviews.

(6) Development of training materials in support of the business system.

(7) Coordination and approval of memoranda of agreement, interface control agreements and service level agreements.

e. Capability integrated master schedule: the combined schedule actions needed to deliver and support the capability. It must include:

(1) The ability to track actual progress against the baselined plan and the ability to load resources to perform actions, at the level of detail appropriate based on lead time.

(2) Technical and management assessments (e.g., engineering, test, and program management) on the progress program to identify risks and issues and address them. At a minimum, the implementation plan will include engineering, test and program management assessments both before releasing an RFP that includes development and following the associated contract award.

f. Capability work breakdown structure: a component-based representation of the decomposition of the work to be executed to deliver and support the capability.

g. Acquisition objectives: a description of the organizational business goals for the development and delivery of the capability in terms of cost and benefits, return on investment, affordability, and overall business case analysis.

h. Tailored business system acquisition strategy.

(1) Acquisition content: a description of the program approach to leverage competition to acquire the required capability at reduced cost and risk. The approach must describe the business strategy, including major contracts planned, contract type(s) and incentives, market research, potential sources, sustainment strategy, subcontracting opportunities, special contracting considerations and special clauses, the business case for or against obtaining warranties, payment methods, contract management and administration, intellectual property strategy, and use of COTS or reasons not to use COTS.

(2) Technical management content: a description of the program approach to leverage systems engineering, test and evaluation (T&E), cybersecurity, and data management processes to reduce technical risk. Specific T&E management content requirements include:

(a) Test events to collect data must be defined, scheduled, and resourced in the implementation plan, including a Developmental Evaluation Framework matrix for developmental testing events.

(b) Cybersecurity developmental and operational T&E must include cooperative vulnerability identification and adversarial cybersecurity testing. Cybersecurity operational T&E must also include a Cyber Economic Vulnerability Analysis as outlined in September 14, 2010 and January 21, 2015 DOT&E Memoranda. The MDA will not tailor cybersecurity T&E solely to meet authority to operate requirements.

(c) T&E planning will include mission-oriented development T&E with actual operators performing end-to-end scenarios in a controlled environment.

(d) Interoperability developmental T&E will include testing with actual representations of interface systems in a controlled environment.

(e) Business systems on the DOT&E Oversight List will document T&E management content in a test and evaluation master plan.

(3) Other content if needed: international considerations, multiyear procurement and integration of intelligence assessments.


a. Portions of the implementation plan will contain the level of detail appropriate based on the progress of the program through the BCAC.

b. Table 6 describes the expected progress of implementation plan content as a program progresses through decision points.

Table 6: Progression of Implementation Plan Content for Decision Points

Implementation Plan Content Area Functional Requirements ATP Acquisition ATP Prior to Development Deployment ATP
Business process actions Known and scheduled Updated for selected business system solution Updated for development Known and scheduled
Acquisition actions High-level overview ROM estimate Known and scheduled Known and scheduled
Capability integrated master schedule Business process detail Full business spectrum detail Full business spectrum detail Full business spectrum detail
Capability work breakdown structure Business process detail Full business spectrum detail Full business spectrum detail Full business spectrum detail
Acquisition objectives High-level overview ROM estimate Baselined Baselined
Acquisition strategy High-level overview Detailed plan Detailed plan Detailed plan
Share This