4.3.2. Technical Planning Process
4.3.2. Technical Planning Process
The Technical Planning process includes defining the scope of the technical effort required to develop, field, and sustain the system, as well as providing critical quantitative inputs to program planning and life-cycle cost estimates. Technical planning provides the Program Manager and Systems Engineer with a framework to accomplish the technical activities that collectively increase product maturity and knowledge and reduce technical risks. Defining the scope of the technical effort provides:
- An accurate basis for program cost and schedule estimates, documented in the Independent Cost Estimate (ICE), Cost Analysis Requirements Description (CARD), and Acquisition Program Baseline (APB);
- A foundation for risk identification and management (see DAG section 4.3.6. Risk Management Process);
- Quantitative measures supporting the Technical Assessment process (see DAG section 4.3.4. Technical Assessment Process) identifying system maturity; and
- An accurately constructed and resourced IMS supporting the assignment of Earned Value.
The resulting program cost estimates and risk assessments are essential to support milestone decisions, establish the plan for accomplishing work against which contract performance is measured, and enable mandatory program certifications (e.g., section 2366a or section 2366b title 10 United States Code).
Technical planning includes the program’s plan for technical reviews and audits (see DAG sections 4.2.8. through 4.2.17.). It should also account for resources (skilled workforce, support equipment/tools, facilities, etc.) necessary to develop, test, produce, deploy, and sustain the system.
Technical planning should be performed in conjunction with, and address, key elements and products of all the other SE processes to ensure the program’s technical plan is comprehensive and coherent. For example, it should be used with the Technical Assessment process to evaluate the progress and achievements against requirements, plans, and overall program objectives. If significant variances are detected, this process includes re-planning as appropriate.
The Program Manager and Systems Engineer should ensure that technical planning remains current throughout the acquisition life cycle. They should initiate technical planning activities early in the life cycle prior to the Materiel Development Decision (see DAG section 4.2.2. Pre-Materiel Development Decision) and during the Materiel Solution Analysis (MSA) phase (see DAG section 4.2.3. Materiel Solution Analysis Phase). Beginning in MSA, programs begin to capture their technical planning in the Systems Engineering Plan (SEP) (see DAG section 4.1.2. Systems Engineering Plan), which is required at each milestone review from Milestone A to Milestone C. As the system matures and issues arise throughout the life cycle, the Program Manager and Systems Engineer should consistently look for root cause(s) and implement corrective actions in order to enable programmatic and technical success. Modifications to the SE processes and SEP may be required because of root cause and corrective action analysis and implementation.
Activities and Products
The Program Manager is ultimately responsible for all program plans. The Systems Engineer is responsible for:
- Developing, maintaining and executing the program’s SEP
- Tracking alignment of the developer’s Systems Engineering Management Plan (SEMP)
- Providing key technical inputs and ensuring SEP alignment to other program plans (Technology Development Strategy/Acquisition Strategy (TDS/AS), Test and Evaluation Strategy/Test and Evaluation Master Plan (TES/TEMP), Life-Cycle Sustainment Plan (LCSP) and Programmatic Environment, Safety, and Occupational Health Evaluation (PESHE)
Technical Planning should reflect the context of the organization and comply with all applicable policies. The Program Manager and Systems Engineer should consider all relevant constraints when identifying technical tasks, sequencing these tasks, and estimating resources and budgets. Inputs to the technical planning process vary over time as the program evolves and the system matures. Technical Planning includes the following activities:
- Defining the scope and objectives of the technical effort
- Identifying constraints and risks
- Establishing roles and responsibilities
- Dividing the program scope and objective into discrete elements
- Identifying technical reviews and audits as well as their timing
- Establishing schedules and costs
- Preparing or updating planning documentation
- Scaling SE processes based on the scope and complexity of the program/system
- Identifying areas for potential tailoring (including rationale) for MDA approval
Key factors that the Systems Engineer should consider when accomplishing technical planning include:
- Capability needs (requirements, gaps, threats, operational context, concept of operations (CONOPS))
- The system concept or materiel solution
- Key interfaces and interdependencies that exist or need to be developed
- The acquisition approach and strategy, from both a business and a contract perspective
- The chosen engineering approach and development strategy
- The test and evaluation approach and strategy, for both developmental and operational testing (See DAG Chapter 9 Test and Evaluation for additional information regarding interactions with the Chief Developmental Tester)
- Program management approach, including organization, processes, and products
- External dependencies and agreements with other systems or organizations that may be in place
- Need date
- Availability of resources, including funds, personnel, facilities, etc.
- Program risks
- Risk mitigation and shrinkage strategies
In addition to the SEP, the technical planning effort supports the development of the following documents:
- Work Breakdown Structure (see DAG section 4.3.2.1. Work Breakdown Structure) – a framework for specifying program objectives
- Integrated Master Plan (see DAG section 4.3.2.2. Integrated Master Plan/Integrated Master Schedule) – an event-based plan consisting of a hierarchy of program events that need to be accomplished
- Integrated Master Schedule (see DAG section 4.3.2.2. Integrated Master Plan/Integrated Master Schedule) – an integrated, networked schedule that contains all lower-level tasks required to support program events
Other useful resources available to assist the Program Manager and Systems Engineer in the Technical Planning process can be found in the “Guidance & Tools” section of the ODASD(SE) Policy and Guidance website.
DAG Tutorial 
