4.1.1. Systems Engineering Policy and Guidance

DEFENSE ACQUISITION GUIDEBOOK
Chapter 4 -- Systems Engineering

4.1.1. Systems Engineering Policy and Guidance

4.1.1. Systems Engineering Policy and Guidance

Policy and guidance related to systems engineering (SE) are intended to minimize the burden and cost on programs while maintaining technical integrity through the planning and execution of SE activities across the acquisition life cycle. Program Managers and Systems Engineers should know and understand the statutory and regulatory SE mandates. Table 4.1.1.T1 identifies top-level SE-related policy and guidance.

Table 4.1.1.T1. Systems Engineering-Related Policy and Guidance

SE-related policy, guidance, specifications, and standards are intended to successfully guide the technical planning and execution of a program across the acquisition life cycle. Understanding the use and value of SE specifications and standards is fundamental to establishing, executing, and maintaining disciplined SE processes. The ASSIST document database is the official source for current DoD specifications and standards.

Compliance with mandated DoD SE policy is required for program approval and completion of successful milestone decisions. DoD policy and guidance provide a framework for structuring the program and help define the areas available for tailoring to effectively and efficiently deliver capability to the warfighter.

Within this policy and guidance framework, tailoring the acquisition effort to meet program cost, schedule, and performance goals is not only desired but mandated in accordance with DoDD 5000.01. In July 2012, USD(AT&L) emphasized there is no one-size-fits-all optimal program structure. Every program has its own optimal structure, and that structure is dependent on many variables that contribute to program success or failure. Areas that should be considered for tailoring include:

• The documentation of program information
• The execution of the acquisition phases
• The timing and scope of decision review
• The decision levels chosen to fit the particular conditions of the program in accordance with applicable laws and regulations
• The time-sensitivity of the capability need

The requirements of DoD SE policy that are identified for tailoring by the Program Manager are submitted to the Milestone Decision Authority (MDA) for approval.

The structuring of every program should start with a deep understanding of the nature of the capability intended to be acquired and the effort needed to realize that capability. Critical thinking during early program formulation is important to clearly identify the internal and external stakeholders, system interdependencies, technological opportunities, contractual and budgetary constraints, and policy mandates. The optimal program structure includes the set of technical activities, events, and management mechanisms that best address the unique circumstances and risks of the program.

All program strategy and planning documents depend on SE activities to define and balance requirements against cost, schedule, and risks; identify potential solutions; assess the maturity and feasibility of available technologies; develop a realistic schedule; and allow for multiple other considerations affecting the final cost and delivery of capability to the warfighter. Therefore, the Program Manager should build a program office structure that ensures the Systems Engineer is an integrated part of the program planning and execution activities.

The Systems Engineer leads or is a key enabler in the planning and execution of the program's technical approach. To aid this planning, the Systems Engineer should proactively seek experience from similar past and current programs and map this learning as applicable into the SE planning of the program (see also DAG section 4.3.19.4. Lessons Learned, Best Practices, Case Studies).