4.3.4.1. Technical Measurement and Metrics
4.3.4.1. Technical Measurement and Metrics
Technical Measurement is the method of collecting and providing information to Program Managers and Systems Engineers at predefined intervals for decision making. Metrics constitute the data that identify the need for improvement (i.e., the facts and trends of process performance) and provide a basis for assessing the improvements.
Measures and metrics assist the Program Manager and the Systems Engineer in efforts to obtain insight into issues that have real or projected impacts on cost, schedule, performance, and risk. These issues can be at any level: the entire system, any of the various system elements or enabling system elements, and any or all of the SE processes in use across the program. This insight enables the Program Manager and others in leadership positions to make informed decisions.
Analysis of technical measures and metrics, in terms of progress against established plans, can reveal trends and provide indicators of future results. The Program Manager and Systems Engineer can use these trends and indicators to assess risk and make appropriate changes to program planning to mitigate potentially unfavorable outcomes.
Activities and Products
Programs document their strategy for identifying, prioritizing, and selecting the set of metrics for monitoring and tracking SE activities and performance in the Systems Engineering Plan (SEP). The measures/metrics strategy should include:
- An overview of the measurement planning and metrics selection process appropriate for the life-cycle phase
- The approach to monitor execution to the established plan
- Identification of roles, responsibilities, and authorities
The SEP requires two types of defined metrics:
- Technical Performance Measures (TPM) derived from Key Performance Parameters (KPPs) and Key System Attributes (KSAs) aid in assessing product maturity (see DAG section 4.3.4.2. Technical Performance Measures)
- Technical progress (at both the system and system element levels) should address product knowledge and therefore vary by phase throughout the life cycle
In addition to TPMs and product measures, the Program Manager and the Systems Engineer should ensure that technical planning identifies measures, metrics, and leading indicators to assess the effectiveness of SE process execution within both the Government program office and the developer’s SE organization. TPMs should be managed by the cognizant Integrated Product Team (IPT).
Areas in which measures and metrics should be monitored include but are not limited to:
- Software metrics (e.g., size, complexity, reuse, defects, productivity)
- Hardware metrics (space, weight and power (SWaP), processing margin, axle loading, available RAM, etc.)
- Technical staffing
- Technology maturity
- Affordability
- Risk Mitigation
- Schedule
- Quality / manufacturing / production measures (e.g., defects, first pass yields, process escapes)
- Infrastructure measures (e.g., capacity, availability, utilization of facilities and equipment)
- Design/development process measures (e.g., drawing releases, software modules, subsystem integration tasks, defined/documented interfaces, deviations, waivers, etc.)
DAG Tutorial 
