Systems Engineering is a disciplined approach for the specification, design, development, realization, technical management, operation, and retirement of a weapon system. SE is an interdisciplinary and collaborative effort requiring close interaction with many disciplines to include operations, maintenance, logistics, test, production, quality, etc. The practice of SE is composed of 16 processes: 8 technical processes and 8 technical management processes. These 16 processes provide a structured approach to increasing the technical maturity of a system, increasing the likelihood that the capability being developed balances mission performance with cost, schedule, risks, and design considerations. The DoD Systems Engineering model is located below, and M&Q personnel need to support these activities and processes.
Source: DoD Systems Engineering Guidebook https://ac.cto.mil/wp-content/uploads/2022/02/Systems-Eng-Guidebook_Feb2022-Cleared-slp.pdf
Eight Technical Processes that may require M&Q participation:
- Stakeholder Requirements Definition, Systems Engineering Guide, 4.2.1
- Requirements Analysis, Systems Engineering Guide, 4.2.2
- Architecture Design, Systems Engineering Guide, 4.2.3
- Implementation, Systems Engineering Guide, 4.2.4
- Integration, Systems Engineering Guide, 4.2.5
- Verification, Systems Engineering Guide, 4.2.6
- Validation, Systems Engineering Guide, 4.2.7
- Transition, Systems Engineering Guide, 4.2.8
Eight Technical Management Processes that may require M&Q participation:
- Technical Planning, Systems Engineering Guidebook, 4.1.1
- Decision Analysis, Systems Engineering Guidebook,4.1.2
- Technical Assessment, Systems Engineering Guidebook, 4.1.3
- Requirements Management, Systems Engineering Guidebook, 4.1.4
- Risk Management, Systems Engineering Guidebook, 4.1.5
- Configuration Management, Systems Engineering Guidebook, 4.1.6
- Technical Data Management, Systems Engineering Guidebook, 4.1.7
- Interface Management, Systems Engineering Guidebook, 4.1.8
The industry standard for systems engineering is ISO/IEC/IEEE 15288, “Systems and Software Engineering–System Life Cycle Processes has a slightly different list of technical and technical management processes, which is described in the graphic below:
Technical Management Processes
|
Technical Processes
|
Source: DoD Best Practices for Using Systems Engineering Standards ((ISO/IEC/IEEE 15288, IEEE 15288.1, and IEEE 15288.2) on Contracts for Department of Defense Acquisition Programs
- Best Practices for Using Systems Engineering Standards (ISO/IEC/IEEE 15288, IEEE 15288.1, and IEEE 15288.2) on Contracts for Department of Defense Acquisition Programs https://acqnotes.com/wp-content/uploads/2014/09/OSD-Guide-to-Best-Practices-Using-Engineering-Standards-2017.pdf
This resource page will focus on the following Pinned Content:
- Systems Engineering Resources and Guidance
- Systems Engineering Tools and Checklist
- Technical Reviews and Audits
- Producibility Engineering
- Key Characteristics
- Producibility Best Practices
DoD Systems Engineering Guidebook https://ac.cto.mil/wp-content/uploads/2022/02/Systems-Eng-Guidebook_Feb2022-Cleared-slp.pdf
Note: Additional information, guidance, tools, and other resources, by acquisition phase, may be found in the M&Q Body of Knowledge at https://www.cto.mil/sea/mq/
DAU Continuous Learning Modules and other training:
- DAU Media has over 175 covering Engineering and Technical Management https://media.dau.edu/channel/Engineering%2Band%2BTechnical%2BManagement/245262672
- CLE 066 Systems Engineering for System of Systems https://icatalog.dau.edu/onlinecatalog/courses.aspx?crs_id=1790
- WSE 005 Systems Engineering Plan (SEP) https://icatalog.dau.edu/onlinecatalog/courses.aspx?crs_id=1590
- DAU Webcast: Adaptive Framework and Systems Engineering https://media.dau.edu/media/1_ll4d66i0
- Systems Engineering Plan (SEP)
-
The Systems Engineering Plan (SEP) is a planning and management tool that defines the methods used for implementing all system requirements having technical content, technical staffing, and technical management. The SEP is specific to a program and is an important tool for managing complex technology-based system developments. The SEP should be tailored to meet program needs and objectives.
The purpose of the Systems Engineering Plan (SEP) is to help Program Managers develop, communicate, and manage the overall systems engineering (SE) approach that guides all technical activities of the program. The SEP documents key technical risks, processes, resources, metrics, SE products, and completed and scheduled SE activities. The SEP is a living document that should be updated as needed to reflect the program’s evolving SE approach and/or plans and current status.
The SEP describes the integration of SE activities with other program management and control efforts, including the Acquisition Strategy, Integrated Master Plan (IMP), Work Breakdown Structure (WBS), Integrated Master Schedule (IMS), Risk Management Plan, Technical Performance Measures (TPMs) and other documentation fundamental to successful program execution. The SEP also describes the program’s technical requirements, engineering resources and management, and technical activities and products as well as the planning, timing, conduct, and success criteria of event-driven SE technical reviews throughout the acquisition life cycle.
The SEP is the program’s blueprint for the conduct, management, and control of all technical activities, the SEP captures decisions made during the technical planning process and communicates objectives and guidance to program personnel and other stakeholders. The SEP should define the “who, what, when, why, and how” of the SE approach and should include the following:
- The program organization with roles and responsibilities, authority, accountability, and staffing resources.
- Key activities, resources, tools, and events that support execution of the SE technical processes and technical management processes.
- The event-driven technical reviews to be conducted and the approach to technical reviews based on successful completion of key activities as opposed to calendar-based deadlines.
- The approach for how requirements and technical performance trade-offs are balanced within the larger program scope to deliver operationally effective, suitable, and affordable systems.
- The identification of key design considerations and criteria.
- The use of and employment of modular design.
- The identification of how manufacturing and quality planning will be incorporated into the SEP and systems engineering processes.
- The identification of and management of Key Performance Parameters (KPPs) and Key System Attributes (KSAs) and development of a prototyping strategy to ensure system requirements can be met within cost and schedule constraints.
- The program’s strategy for identifying, prioritizing, and selecting the set of TPMs and metrics (TPMM) should provide sufficient insight into the technical progress and program risks.
The Systems Engineering Plan Outline:
1 Introduction
2 Program Technical Definition
2.1 Requirements Development
2.2 Architectures and Interface Control
2.3 Specialty Engineering
2.4 Modeling Strategy
2.5 Design Considerations
2.6 Technical Certifications
3 Program Technical Management
3.1 Technical Planning
3.1.1 Technical Schedule
3.1.2 Maturity Assessment Planning
3.1.3 Technical Structure and Organization
3.2 Technical Tracking
3.2.1 Technical Risk, Issue, and Opportunity Management
3.2.2 Technical Performance Measures
3.2.3 Reliability and Maintainability Engineering
3.2.4 Manufacturing and Quality Engineering
3.2.5 Human Systems Engineering
3.2.6 System Safety
3.2.7 Corrosion Prevention and Control
3.2.8 Software Engineering
3.2.9 Technology Insertion and Refresh
3.2.10 Configuration and Change Management
3.2.11 Technical Data Management
3.2.12 System Security Engineering
3.2.13 Technical Reviews, Audits and Activities
Appendix A - Acronyms
Appendix B - Item Unique Identification Implementation Plan
Appendix C - Agile and Development Security and Operations Software Development Metrics
Appendix D - Concept of Operations Description
Appendix E - Digital Engineering Implementation Plan
ReferencesSEP Guidance and other Resources:
- DoD Systems Engineering Guidebook https://ac.cto.mil/wp-content/uploads/2022/02/Systems-Eng-Guidebook_Feb2022-Cleared-slp.pdf
- Engineering of Defense Systems Guidebook https://www.cto.mil/wp-content/uploads/2023/06/Eng-Def-Sys-2022.pdf
- DoD Systems Engineering Plan Outline https://ac.cto.mil/wp-content/uploads/2023/05/SEP-Outline-4.1.pdf
- DoD Systems Engineering Plan Data Item Description (DID) SESS-2024-043 Systems Engineering Management Plan (SEMP) https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=276889
DAU Systems Engineering Plan training videos:
- Several videos are available via a web search
- Systems Engineering Resources and Guidance
-
- Systems Engineering Body of Knowledge (SE BoK) https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK)
- Guide to the Systems Engineering Body of Knowledge (SE BoK) https://sebokwiki.org/w/images/sebokwiki-farm!w/8/8d/SEBoKv1.4_full.pdf
- DoD Systems Engineering Guidebook https://ac.cto.mil/wp-content/uploads/2022/02/Systems-Eng-Guidebook_Feb2022-Cleared-slp.pdf
- IEEE 15288 Best Practice for Using Systems Engineering Practices https://www.iso.org/obp/ui/#iso:std:iso-iec-ieee:15288:ed-2:v1:en
- IEEE 15288.1 Application of Systems Engineering on Defense Programs https://ieeexplore.ieee.org/document/7105318
- IEEE 15288-2 Technical Reviews and Audit on Defense Systems https://standards.ieee.org/ieee/15288.2/5705/
- SAE Recommended Failure Modes and Effects Analysis (FMEA) Practices for Non-Automobile Applications https://www.sae.org/standards/content/arp5580/
- SAE Potential Failure Mode and Effects Analysis (FMEA) Including Design FMEA, Supplemental FMEA-MSR, and Process FMEA https://www.sae.org/standards/content/j1739_202101/
- DoDI 5000.88, Engineering of Defense Systems https://www.esd.whs.mil/Directives/issuances/dodi/
- DoD Engineering of Defense Systems Guidebook https://ac.cto.mil/wp-content/uploads/2022/02/Eng-Defense-Systems_Feb2022-Cleared-slp.pdf
- Early Manufacturing and Quality Engineering Guide https://ac.cto.mil/maq/
- DoD Producibility and Manufacturability Engineering Guide https://www.cto.mil/wp-content/uploads/2024/06/DoD-Producibility-and-Manufacturability-2024.pdf
- DoDI 5000.83 Technology and Program Protection to Maintain Technological Advantage https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500083p.pdf
- DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs https://www.dau.edu/sites/default/files/2023-10/DoD%20RIO%20Management%20Guide%2009-2023.pdf
- DoD Best Practices for Using Systems Engineering Standards https://acqnotes.com/wp-content/uploads/2014/09/OSD-Guide-to-Best-Practices-Using-Engineering-Standards-2017.pdf
- DoD Systems Engineering Plan Preparation Guide https://www.acqnotes.com/Attachments/Systems%20Engineering%20Plan%20Preparation%20Guide.pdf
- DI-SESS-81785A Systems Engineering Plan Data Item Description https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=276889
- Defense Technical Risk Assessment Methodology (DTRAM) https://ac.cto.mil/wp-content/uploads/2021/01/DTRAM-0-1.pdf
- DoD Technology and Program Protection Guidebook https://rt.cto.mil/wp-content/uploads/TPP_Guidebook_Jul2022_cleared.pdf
- Air Force Systems Engineering Assessment Model (AF SEAM) Management Guide https://apps.dtic.mil/sti/citations/ADA538786
- AFMC Instruction 63-1201 Integrated Life Cycle Systems Engineering and Technical Management https://static.e-publishing.af.mil/production/1/afmc/publication/afmci63-1201/afmci63-1201.pdf
- AFLCMC Engineering Guide to Writing RFP Technical Content
- Navy Systems Engineering Guide https://apps.dtic.mil/sti/citations/ADA527494
- NAVAIR INST 4355 Systems Engineering Technical Review Process
- MIL-STD-881E Work Breakdown Structure https://www.dau.edu/cop/se/documents/mil-std-881-work-breakdown-structures-defense-materiel-items
- MIL-STD-882E Systems Safety https://acqnotes.com/wp-content/uploads/2014/09/MIL-STD-882E-change-1-1.pdf
- MIL-HDBK-61 Configuration Management https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=202239
- MIL-HDBK-539 Digital Engineering and Modeling Practices https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=285031
- MIL-STD-1472 DoD Design Criteria Standard Human Engineering https://quicksearch.dla.mil/qsdocdetails.aspx?ident_number=36903
- MIL-STD-31000B Technical Data Packages http://everyspec.com/MIL-STD/MIL-STD-10000-and-Up/MIL-STD-31000_20516/
- Systems Engineering Tools and Checklist
-
- DAU Systems Engineering Brainbook https://www.dau.edu/tools/dau-systems-engineering-brainbook
- MIL-HDBK-520, DoD Systems Requirements Guidance http://everyspec.com/MIL-HDBK/MIL-HDBK-0500-0599/MIL-HDBK-520A_39996/ Acquisition Requirements Roadmap Tool (ARRT) https://www.fai.gov/content/dau-acquisition-requirements-roadmap-tool-arrt
- Acquisition Requirements Roadmap Worksheet https://content1.dau.edu/DAUMIG_SAM_185/content/resources/Requirements_Roadmap.html
- Requirements Traceability Matrix (DAU) https://acqnotes.com/acqnote/tasks/proposal-compliance-matrix/attachment/requirements-traceability-matrix
- JCIDS Initial Capabilities Document (ICD) AcqNotes https://acqnotes.com/acqnote/acquisitions/initial-capabilities-document-icd
- TRADOC Initial Capabilities Document Writers Guide https://www.acqnotes.com/Attachments/Initial%20Capabilities%20Document%20(ICD)%20Writers%20Guide.pdf
- JCIDS CDD Checklist https://www.dau.edu/sites/default/files/Migrated/CopDocuments/CDD%20Checklist.pdf
- JCIDS CDD Template https://www.acqnotes.com/Attachments/Capability%20Development%20Document%20Template%2030%20Oct%2012.doc
- Guide for Integrating Systems Engineering into DoD Acquisition Contracts https://apps.dtic.mil/sti/pdfs/ADA575981.pdf
- Systems Engineering Modernization Policy, Practice, and Workforce Roadmaps https://sercproddata.s3.us-east-2.amazonaws.com/technical_reports/reports/1687382869.DOPSR-STAMPED-WRT-1058_A013_Final%20Technical%20Report_SERC-2023.pdf
- Systems Engineering Plan (SEP) Outline https://ac.cto.mil/wp-content/uploads/2023/05/SEP-Outline-4.1.pdf
- Systems Engineering Plan (SEP) DI-SESS-81785A https://quicksearch.dla.mil/Transient/CB1A64704C5141C0B998799B9A474F9A.pdf
- Systems Engineering Management Plan SEMP (DI-MGMT-81024 SEMP) http://everyspec.com/DATA-ITEM-DESC-DIDs/DI-MGMT/DI-MGMT-81024_2911/
- Interactive MRL Users Guide Checklist for the Design thread https://www.dodmrl.com/
- Systems Engineering Modernization Pain Points https://www.cto.mil/wp-content/uploads/2023/06/SERC-WRT-1058-Excerpt-PainPoints-2023.pdf
- A Comprehensive List of Tools to Aid the Engineering Community
-
This document identifies tools that could be used to help manage DoD acquisition technical, business, and management processes to include many manufacturing and quality activities. Most of these tools support systems engineering technical and technical management processes, but a few can be used to support business processes such as cost estimating, contract language, acquisition strategies, etc. Some tools could be used by a contractor, some by government personnel and some tools can bd used by many different people in many functional specialties. Most tools are available from multiple on-line sources, some tools may need to be purchased to use, many are free.
Note: You can find more information on the tools listed below with a search of the web.
Tools (listed in alphabetical order include):
- 3Ps - Production Preparation Process
- 5S’s (Sort, Straighten, Shine, Standardize, Sustain
- 5-Whys
- 7 - Basic Tools for Quality Improvement (includes the following which are also discussed separately):
- Cause and Effect Diagram
- Check Sheet
- Control Chart
- Histogram
- Pareto Chart
- Run Chart
- Scatter Diagram
- Stratification or Flowchart or
- 7 - Management and Planning Tools, or Advanced Tools for Quality Improvement (includes the following which are also discussed separately):
- Affinity Diagram
- Relations Diagram or Interrelationship Diagraph
- Tree Diagram
- Matrix Diagram
- Matrix Data Analysis
- Arrow Diagram
- Process Decision Program Chart (PDPC)
- 8D/PSP (Eight Disciplines/Problem Solving Process)
- A3 Problem Solving Chart
- Acceptable Quality Levels (AQL)
- Acceptance Sampling
- Active Risk Manager (ARM)
- Affinity Diagram
- Advanced Product Quality Planning (APQP) Core Tools
- Arrow Diagram (Chart)
- AS6500 Manufacturing Management System (MMS)
- AS9100 Advanced Quality Management Systems (QMS)
- AS9103 Variation Management of Key Characteristics
- AS9110 Maintenance
- AS9120 Distributors
- AS9102 FAI
- AS9115 Software QA
- AS9131 N/C Document
- AS9132 Marking
- AS9133 Supplier QA
- AS 9137 AQAP Align
- AS 9138 Statistical Process Control
- AS9162 Self Verification
- Axiomatic Design
- Balanced Scorecard
- Baldrige Performance Excellence Criteria
- Bekidou Rate
- Benchmarking
- Bill of Materials (BOM)
- Bone Diagram
- Bottleneck Analysis
- Box and Whisker Plot
- Bubble Chart
- Capacity Matrix
- Capacity Analysis
- Cause and Effect Diagram (Fishbone or IshIkawa)
- Cause and Effect Matrix
- CFMEA – Concept Failure, Mode and Effect Analysis
- Check Sheet
- Chokko Rate
- Computer-Aided Design (CAD)
- Computer-Aided Manufacturing (CAM)
- Computer Aided Process Planning (CAPP)
- Computer-Aided Three-Dimensional Interactive Application (CATIA)
- Computer Integrated Manufacturing (CIM)
- Consensogram
- Contingency Planning
- Control Chart - C-chart for Attribute Data (Go/No Go, Good/Bad, etc.)
- Control Chart - C-chart for Attribute Data (Go/No Go, Good/Bad, etc.)
- Control Chart -U-chart for Attribute Data
- Control Chart - NP-chart for Attribute Data
- Control Chart - P-chart for Attribute Data
- Control Chart - X-barR chart for Variable Data (measurable)
- Control Chart - X-bar-S chart for Variable Data
- Control Chart - X-MR/I-MR chart for Variable Data
- Correlation Chart (Scatter Diagram)
- Cost/Benefit Analysis
- Cost of Quality Analysis
- Cost of Quality (COQ)
- Cost Modeling (Estimating)
- Criteria Testing
- Critical Chain Project Management
- Critical Design Review Checklist (DoD)
- Critical Path/PERT
- Critical to the Customer (CTC)
- Critical to Quality (CTQ) Tree
- Customer Contingency Table
- DCOV – Define, Characterize, Optimize and Verify
- Deming Cycle or Wheel (PDCA)
- Departmental Purpose Analysis
- Design of Experiments (DoE)
- DFMEA - Design Failure Mode and Effects Analysis
- DFMA - Design for Manufacturing and Assembly
- Design to Cost (DTC)
- DFSS - Design for Six Sigma
- DMAIC - Define, Measure, Analyze, Improve and Control
- DMADV (see DCOV)
- Domainal Mapping
- Factory Modeling and Simulation
- Producibility Analysis & Ergonomics
- Process Planning
- Production Planning & Scheduling
- Line Balancing & Bottleneck Analysis
- Capacity Planning
- Predictive Analytics & Optimization
- Facility Planning, Layout and Design
- Virtual Factory Mock-up
- Failure Mode and Effects Analysis (FMEA)
- Fault Tree Analysis
- First Article Inspection
- First Article Testing
- Flow Chart or Process Flow Chart
- Force Field Analysis
- Gage R&R Studies
- Gantt Chart
- Histogram (Frequency or Bar Chart)
- Hoshin Kanri (Quality Policy Deployment)
- Interrelationship Diagraph (also see Relations Diagram, or Network Diagram)
- ISO 9001 Quality Management Systems (QMS)
- Kano Model
- KJ model - Kawalota Jiro (see affinity diagram)
- Lead Time Analysis
- Learning Curve
- Learning Curve Analysis
- Line of Balance (LOB)
- Taguchi Loss Function
- Lotus Diagram
- Manufacturing Cost Estimating
- Manufacturing Plan
- Manufacturing Readiness Assessment (MRA)
- Manufacturing Readiness Level (MRL) Criteria
- Matrix Diagram
- Matrix Data Analysis Diagram
- Measurement Systems Analysis (MSA)
- MIL-HDBK-896A Manufacturing and Quality Program
- Multi-Vari Charts
- Nominal Group Technique
- One Piece Flow
- Operations Process Chart
- Overall Equipment Effectiveness (OEE)
- Pareto Charts (Template)
- Part-Family Analysis
- Paynter Chart
- P-Diagram or Parameter Design
- PERT Chart (Program Evaluation Routine Technique)
- PFMEA – Process Failure, Mode and Effect Analysis
- Pie Chart
- Preliminary Design Review Checklist (DoD)
- Preliminary Hazards List (PHL)
- Process Capability Studies (Cp and Cpk)
- Process Performance Studies (Pp and Ppk)
- Process Decision Program Chart (PDPC)
- Producibility Analysis/Assessments
- Producibility Assessment Worksheet
- Producibility Engineering and Planning (PEP) Program
- Production Part Approval Process
- Production Readiness Review (PRR) Checklist
- Programmatic Evaluation of ESOH (PESHE)
- Pugh Matrix
- Quadrant Chart
- Quality Function Deployment (QFD)
- Queuing Theory/Waiting Line Analysis
- Radar Chart
- Rational DOORS
- Relation Diagram
- Reliability Growth Analysis
- Requirements Verification (Traceability) Matrix (RVM)
- Risk Management Assessment Tool
- Route Sheet
- Run Chart
- Scatter Diagram (Mind Mapping)
- SIPOC – System, Input, Process, Output and Customer
- Six Sigma
- SMART – Specific, Measurable, Attainable, Resources, Time
- Spaghetti Diagram
- Spider Diagram
- Stratification
- Statistical Process Control (SPC)
- Supply Chain Management Risk Assessment
- Swim Lane Chart (sometimes called a Deployment Flow Chart)
- SWOT Model (Strength, Weaknesses, Opportunities and Threats
- Systems Engineering Plan (SEP)
- Takt Time Analysis
- Technical Risk Identification and Mitigation System (TRIMS)
- Technology Readiness Level (TRL) Checklist
- Theory of Constraints Analysis
- Throughput Analysis Tool
- Throughput Accounting
- Tolerance Analysis
- Tolerance Design
- Total Productive Maintenance (TPM)
- Trade Studies/Analysis
- Transition to Production (Willoughby Templates)
- Tree Diagram
- TRIZ Matrix
- Value Stream Mapping (VSM)
- Variability Reduction Program
- Venn Diagram
- Work Center
- Work Measurement
- X-Matrix
- Yamazumi Chart
Note: You can find a lot of additional information by googling the tool, by visiting a number of different academic sites, or professional organizations, or by visiting various Communities of Practice (CoPs).
- Quality of Design / Quality by Design / Quality Engineering
-
Quality By Design – Based on Juran Institute Processes
Quality by Design (Quality of Design or Concurrent Engineering) is the process of creating a design using multidisciplinary teams (IPTs) to conduct conceptual thinking, product design, and production planning all at one time. Quality by Design was developed by Dr. J. M. Juran who believed that quality should be built into a product from the beginning, and that most quality issues are related to the product's original design.
Quality by Design differs from traditional sequential engineering practices and uses a five step process of Define, Discover, Design, Develop, and Deliver. Each process step has a focus and utilizes a variety of advanced quality and technical tools to meet customer requirements (satisfies the customer) often focusing on the eight dimensions of quality to create a design that is optimized for performance, cost and schedule. Quality by Design should require input from many different technical teams to include manufacturing and quality. It is the job of systems/design engineers to create the design, and it is the role of these technical personnel is to “influence the design” for producibility, manufacturability, reliability and maintainability, testability, and sustainability.
Define Describe in general terms what the product is and what set of customers it is intended to serve. Establish the team, identify the customers and stakeholders, set goals, and create plans:
- Operational Needs and Requirements
- Sustainment Requirements
- IOC Date
- Weapon System Performance
- Cost (Procurement and Sustainment)
Discover Discover the exact needs of the customer expressed in terms of the benefit to the customer. Collect and prioritize customer needs and translate those needs and create:
- Work Breakdown Structure (WBS)
- Functional Allocation
- Allocated Baseline
- Measures of Effectiveness (MoE)
- Key Performance Parameters (KPP)
- Measures of Performance (MoP)
- Technical Performance Measures (TPM)
- “Critical to Quality” measures.
Develop planning worksheets for:
- Customer requirements
- Allocate Functions and Features
- Allocate Measures and Goals (MoE, KPP, MoP, TPM and Critical to Quality
- Detailed design features and goals
- Manufacturing Process features and goals
- Manufacturing Control features and goals
Design Design a product that will meet those needs better than competitors’ and preceding products. Establish high-level product features and goals: (functional design), then develop detailed product features and goals (detailed design), optimize design features, set and approve final design.
- Product Baseline
- Functional
- Allocated Design
- Detail Design
- Design reviews and approvals
- Identify and manage key and critical characteristics
- Producibility Engineering
- Trade Studies and Trade-off Analysis
- Design Reviews
- Above activities may require the use of the following advanced engineering techniques:
- Design of Experiments
- Quality Function Deployment
- Design for Manufacturing and Assembly (DFMA)
- Design for X
- Parameter Desing
-
Tolerance Design
Develop Produce or manufacture the product by identifying, managing, controlling manufacturing processes and control.
- Create manufacturing process planning (route sheets, flow diagrams, etc.)
- Create assembly charts and operations process charts
- Understand and control manufacturing processes:
- Set goals for processes
- Develop control plans
- Establish audit procedures
- Capture feedback and continuously improve
- Manage capacity, identify bottlenecks:
- Theory of Constraints
- Optimize throughput
- Optimize processes:
- Lean
- Six Sigma
- Standard Stable Processes
- Identify and manage critical process parameters
- Demonstrate process capability
- Optimize process capability
- Manage Quality:
- Establish a Quality Management System
- Identify critical quality attributes
- Control variation
- Statistical Process Controls
- Manage Supply Chain
Deliver Plan for the transfer of the product to the customer, then measure and manage customer satisfaction.
- Conforms to requirements
- Performs as expected
- Reliable product
- On-time
- Defect free
- Technical Reviews and Audits
-
For DoD systems development, a properly tailored series of technical reviews and audits provide key points throughout the system development to evaluate significant achievements and assess technical maturity and risk. Technical reviews of program progress should be event driven and conducted when the system under development meets the review entrance criteria as documented in the SEP. An associated activity is to identify technical risks associated with achieving entrance criteria at each of these points. SE is an event-driven process based on successful completion of key events as opposed to arbitrary calendar dates. As such, the SEP should clarify the timing of events in relation to other SE and program events.
Technical reviews of program progress should be event driven and conducted when the system under development meets the review entrance criteria as documented in the program’s Systems Engineering Plan (SEP). An associated activity is to identify technical risks associated with achieving entrance criteria at each of these points (see the DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs). Systems Engineering (SE) is an event-driven process based on successful completion of key events as opposed to arbitrary calendar dates. As such, the SEP should clarify the timing of events in relation to other SE and program events. While the initial SEP and Integrated Master Schedule (IMS) have the expected occurrence in the time of various milestones (such as overall system Critical Design Review (CDR)), the plan should be updated to reflect changes to the actual timing of SE activities, reviews and decisions. Figure 3-1 of the SE Guidebook provides the end-to-end perspective and the integration of SE technical reviews and audits across all AAF pathways. Technical reviews should be tailored appropriately for other acquisition pathway.
The DoD Systems Engineering Guidebook provides guidance on support of the following technical reviews and audits https://ac.cto.mil/wp-content/uploads/2022/02/Systems-Eng-Guidebook_Feb2022-Cleared-slp.pdf
- Alternative Systems Review (ASR): Is a technical review that assesses the preliminary materiel solutions that have been developed during the MSA Phase. The review ensures that one or more proposed materiel solution(s) have the best potential to be cost-effective, affordable, operationally effective, and suitable, and can be developed to provide a timely solution at an acceptable level of risk to satisfy the capabilities listed in an ICD. The ASR helps the PM and Systems Engineer ensure that further engineering and technical analysis needed to draft the system performance specification is consistent with customer needs. https://acqnotes.com/acqnote/tasks/alternative-systems-review-2
- System Requirements Review (SRR): Is a formal review conducted to ensure that system requirements have been completely and properly identified and that a mutual understanding exists between the government and the contractor. It ensures that the system under review can proceed into initial systems development and that all system and performance requirements derived from the ICD or draft CDD are defined and testable, and are consistent with cost, schedule, risks, technology readiness, and other system constraints. https://acqnotes.com/acqnote/acquisitions/system-requirements-review-srr
- System Functional Review (SFR): Is a technical review to ensure that the system’s functional baseline is established and can satisfy the requirements of the ICD or draft CDD within the currently allocated budget and schedule. It also determines whether the system’s lower-level performance requirements are fully defined and consistent with the system concept and whether lower-level systems requirements trace to top-level system performance requirements. https://acqnotes.com/acqnote/acquisitions/system-functional-review
- Preliminary Design Review (PDR): Is a technical assessment that establishes the Allocated Baseline of a system to ensure a system is operationally effective. A PDR is conducted before the start of detailed design and is the first opportunity for the Government to observe the Contractor’s hardware and software designs. This review assesses the allocated design documented in subsystem product specifications for each configuration item in the system. It ensures that each function in the Functional Baseline has been allocated to one or more system configuration items. A PDR is required by statute for all Major Defense Acquisition Programs (MDAPs). https://acqnotes.com/acqnote/acquisitions/preliminary-design-review
- Critical Design Review (CDR): Is a multi-disciplined independent technical assessment to ensure that a system can proceed into fabrication, demonstration, and test and meet stated performance requirements within cost, schedule, and risk. A successful CDR is predicated upon a determination that the detailed design satisfies the CDD. Multiple CDRs may be held for key Configuration Items (CI) and/or at each subsystem level, culminating in a system-level CDR. https://acqnotes.com/acqnote/acquisitions/critical-design-review
- System Verification Review (SVR): Is a product and process assessment to ensure the system under review can proceed into LRIP and FRP within cost, schedule, risk, and other system constraints during the EMD Phase. It assesses the system functionality and determines if it meets the functional requirements in the CDD documented in the functional baseline. The SVR establishes and verifies final product performance and provides inputs to the CPD. https://acqnotes.com/acqnote/acquisitions/system-verification-review-svr#google_vignette
- Functional Configuration Audit (FCA): Examines the functional characteristics of the configured product. It verifies that the product has met the requirements specified in its Functional Baseline documentation approved at the PDR and CDR. The FCA reviews the configuration item’s test and analysis data to validate that the intended function meets the system performance specification. The audit is more systems engineering-focused than program management official auditing. https://acqnotes.com/acqnote/tasks/functional-configuration-audit-2
- Production Readiness Review (PRR): Assesses a program to determine if the design is ready for production. It evaluates if the prime contractor and major subcontractors have accomplished adequate production planning without incurring unacceptable risks that will breach thresholds of schedule, performance, cost, or other established criteria. https://acqnotes.com/acqnote/acquisitions/production-readiness-review
- Physical Configuration Audit (PCA): Is a formal technical review that determines if the configuration of a system or item has met its documented requirements to establish a product baseline. The Milestone Decision Authority (MDA) receives proof from a successful PCA that the product design is stable, the capability satisfies end-user needs, and the production risks are tolerably low. https://acqnotes.com/acqnote/tasks/physical-configuration-auditaudit
- Independent Technical Risk Assessment (ITRA): is a formal review that is independent of the program office and is conducted in advance of milestone and production decisions in order to provide senior leaders with an independent review of a programs technical risks, including the maturity of critical technologies and manufacturing processes,
DAU Continuous Training Modules and other training:
- CLE 003 Technical Reviews https://icatalog.dau.edu/onlinecatalog/courses.aspx?crs_id=274
- CME 203 Engineering Support to Technical Reviews (DCMA) https://icatalog.dau.edu/onlinecatalog/courses.aspx?crs_id=2080
- CLE 017 Technical Planning https://www.dau.edu/courses/cle-017
- Technical Reviews Across the Acquisition Lifecycle -DAU Media https://media.dau.edu/media/0_ntghkgsg
Guidance and other resources:
- The DoD Systems Engineering Guidebook covers all of these technical reviews and is available at the following url https://ac.cto.mil/wp-content/uploads/2022/02/Systems-Eng-Guidebook_Feb2022-Cleared-slp.pdf
- Digital Engineering
-
Digital Engineering (DE), Digital Twin, Digital Threads, and Digital Models:
Digital Engineering: Digital Engineering can be used to support all of the Systems Engineering functions. MIL-HDBK-539 Digital Engineering and Modeling Practices defines digital engineering as “an integrated, computation-based approach that uses authoritative sources of system data and models as a continuum across disciplines to support lifecycle activities.” DE is a cutting-edge approach that uses authoritative sources of system data and models throughout the development and life of a system. Digital engineering harnesses computational technology, modeling, analytics, and data sciences to update traditional systems engineering practices. In the face of increasing global challenges and dynamic threat environments, digital engineering is a necessary practice to support acquisition.
DoDI 5000.97-Digital Engineering calls for the use of digital engineering methodologies, technologies and practices across the life cycle of defense acquisition programs. Further, the document:
- Mandates the incorporation of digital engineering for all new programs (exceptions can be granted by decision authority)
- Directs Components to use digital engineering practices in requirements, cost, business and sustainment.
- Calls for the replacement of documents with the use of digital models as the primary means of communicating system information.
- During program planning and contracting, requires that appropriate data rights be obtained.
- Singles out DAU as providing workforce training on digital engineering.
The diagram below, from the instruction, captures the digital Engineering framework:
- MIL-HDBK-539 Digital Engineering and Modeling Practices https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=285031
Digital Twin: Every product produced, and every process executed is unique. There can be thousands, of key input variables used to describe products, assets, entire lines, and processes. A Digital Twin is a virtual replica of a physical object, manufacturing process, or plant that is designed to capture, map, and structure process variables into a continuously updated database. This database can be used by an organization to monitor, analyze, design, or optimize the process without having to go out into the field or do costly trials on the physical equipment. By making this data more readily available in a digital environment, teams can use data in other applications, models, or third-party programs to make meaningful discoveries.
Digital Thread: A digital thread is a framework that connects data about a product throughout its lifecycle, from design to disposal. It uses a variety of technologies, including computer-aided design (CAD), product lifecycle management (PLM), and Internet of Things (IoT) sensors, to collect and share data. A manufacturing digital thread is designed to expand upon a digital twin. Put simply, the digital thread captures digital twin data as they evolve. As manufacturers evolve their processes and their digital twins adapt to new settings or recipe changes, the digital thread encapsulates the link between these evolutions.
The digital thread should seamlessly advance the controlled interplay of technical data, software, information, and knowledge in the digital engineering ecosystem. Digital threads are used to connect authoritative data and orchestrate digital models and information across a system’s life cycle. The digital thread informs decision makers throughout a system’s life cycle by providing the capability to access, integrate, and transform data into actionable information. The digital thread should support feedback over the life cycle.
Example Data Elements or Digital Artifacts
Engineering Design Data
Technical Product Data
Manufacturing and Quality Data
Enterprise Data
- Producibility Analysis
- CAD Data
- Modeling and Simulation Data
- Special Tooling Data
- Special Inspection Equipment Data
- Digital Drawings
- Digital Models
- Specifications
- Standards
- Critical Manufacturing Processes
- Configuration Data
- Interface Management Data
- Analytical Data
- Bill of Material
- Manufacturing Floor Layout
- Production Line Data
- Pilot Line Data
- LRIP/FRP Data
- Industrial Engineering Data
- Production Data
- Machining Instructions
- Customer Demand Data
- Rates and Quantities Data
- Work Breakdown Structure Data
- Supplier Data
- FRACAS Data
- Test Plans
- Schedules
- Product Support Strategy
Digital Models Include:
- Requirements Model
- Structural Model
- Functional Model
- Architecture Model
- Business Process Model
- Enterprise Model
- Human Performance Model
- Product Life Cycle Model
DAU Continuous Learning Modules and other training:
- DoD Introduction to Digital Engineering video https://media.dau.edu/media/1_wwl11oa7
- DAU Webcast "Digital Engineering Readiness" https://media.dau.edu/media/1_ck8yzvqv
- DAU Let's Get Digital Webinar: About Resilience Engineering in and of Digital Engineering https://media.dau.edu/media/1_xfmk3vyh
- Overview of Digital Engineering, Modeling and Simulation for DAU SE Modernization https://media.dau.edu/media/1_58ebhvc2
Guidance and other Resources:
- Digital Engineering Fundamentals https://www.cto.mil/wp-content/uploads/2023/06/Dig-Eng-Fundamentals-2022.pdf
- DoDI 5000.97 Digital Engineering https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500097p.PDF?ver=bePIqKXaLUTK_Iu5iTNREw%3D%3D
- MIL-HDBK-539 Digital Engineering and Modeling Practices https://quicksearch.dla.mil/qsDocDetails.aspx?identnumber=285031
- DoDI 5000.82 Requirements for the Acquisition of Digital Capabilities https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500082p.pdf
- Digital Engineering Body of Knowledge (DEBoK)
-
The Digital Engineering Body of Knowledge (DEBoK) will serve as a reference for the DoD engineering community to use in implementing digital engineering practices starting with systems engineering and expanding to specific disciplines, engineering domains and specialty areas. The BoK will store collective data, information and knowledge on digital engineering. Members of the government, industry and academia working within this space will be able to contribute to the DEBoK and build their digital engineering solutions based on collective knowledge. Access the DoD DE BoK briefing at https://ndiastorage.blob.core.usgovcloudapi.net/ndia/2021/systems/Wed_23770_Zimmerman_Davidson_Salvatore.pdf
As a best practice, when conducting early M&Q engineering analysis, the technical team should consider DE principles, methods, and tools. DE best practices and tools are defined in the DE Body of Knowledge (DEBoK). https://de-bok.org/
The DEBoK is also available to DoD Common Access Card users at the Defense Technical information Center (DTIC) website:
https://www.dodtechipedia.mil/dodwiki/pages/viewpage.action?page Id=760447627
- Digital Engineering Strategy and other Resources
-
DoD’s Digital Engineering Strategy provides guiding principles and promotes consistency in engineering processes through the use and reuse of digital tools, models, and curated data throughout the program’s life cycle. As a best practice, the technical team should consider M&Q digital data requirements (e.g. factory floor modeling and simulation, digital technical data packages and work instructions, digital data in supply chains) during early establishment and development of the digital thread.
Digital Engineering: An integrated digital approach that uses authoritative sources of systems’ data and models as a continuum across disciplines to support lifecycle activities from concept through disposal. Access to Digital Engineering Fundamentals can be found at the following urls:
https://www.cto.mil/wp-content/uploads/2023/06/Dig-Eng-Fundamentals-2022.pdf
https://ac.cto.mil/wp-content/uploads/2019/06/DE-Fundamentals.pdf
Digital Engineering Ecosystem: The interconnected infrastructure, environment, and methodology (process, methods, and tools) used to store, access, analyze, and visualize evolving systems’ data and models to address the needs of the stakeholders. End-to-end digital enterprise.
Digital Artifact: An artifact produced within, or generated from, the digital engineering ecosystem. These artifacts provide data for alternative views to visualize, communicate, and deliver data, information, and knowledge to stakeholders.
Guidance and other Resources:
- Digital Engineering Strategy https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf
- Digital Engineering Fundamentals https://www.cto.mil/wp-content/uploads/2023/06/Dig-Eng-Fundamentals-2022.pdf
- DoDI 5000.97 Digital Engineering https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500097p.PDF?ver=bePIqKXaLUTK_Iu5iTNREw%3D%3D
- MIL-HDBK-539 Digital Engineering and Modeling Practices https://quicksearch.dla.mil/qsDocDetails.aspx?identnumber=285031
- DoDI 5000.82 Requirements for the Acquisition of Digital Capabilities https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500082p.pdf
- Modeling and Simulation (M&S)
-
A model is a physical, mathematical, or logical representation of a system, entity, phenomenon, or process. Manufacturing models include plant diagrams, flow charts, 5Ms chart,
A simulation is the implementation of a model over time, showing how the model works, and can be live, virtual, or constructive. Manufacturing simulations include
The use of models and simulations in engineering is well recognized. Simulation technology is an essential tool for engineers in all application domains. A digital model represents an actual or conceptual system that involves physics, mathematics, or logical expressions. A simulation is a method for implementing a model over time. Together models and simulations allow the Department to vet potential requirements prior to the Request for Proposal release, assess engineering change orders or program upgrades, etc. M&S can be used to assess and optimize resource usage, examine process changes, support supply-chain management routing and inventory quantities, business decisions, etc.
Models and simulations are SE tools used by multiple functional area disciplines. Models, simulations, data, and other artifacts should be developed and used in a well-defined and controlled engineering ecosystem to support an effort’s reuse of the information across the life cycle of activities. Models, simulations, data, and artifacts should be integrated, managed, and controlled to ensure that the products maintain consistency with the system and external dependencies and provide a comprehensive view of the effort and increase efficiency and confidence throughout the project’s life span.
Systems Engineering process related tools:
Note: Each of these technical and technical management processes have commercial software tools that can be used to support these processes. A web search starting with Model-Based Systems Engineering (MBSE) tools should provide many links.
Systems Engineering Technical Processes Tool Capabilities and Features Stakeholder Requirements Definition - Assists in capturing and identifying stakeholder requirements
- Assists in analyzing and maintaining stakeholder requirements
Requirements Analysis - Assists in requirements definition and decomposition
- Interfaces with architecting tools
- Supports requirements validation
Architecture Design - Assists in development of functional and physical architectures
- Provides traceability among system elements
- Supports multiple views
Implementation - Assists in development of the system design, prototypes and alternate solutions
- Assists in realization of the system, system elements and enabling system elements
Integration - Assists in integration-planning activities
- Assists in assembling lower-level system elements into successively higher-level system elements
- Provides analysis and simulation capability
Verification - Assists in determining the system and system elements performance as designed through demonstration, examination, analysis and test
Validation - Assists in determining, the effectiveness, suitability and survivability of the system in meeting end-user needs
Transition - Assists in planning and executing delivery and deploying of the system to the end user for use in the operational environment
Systems Engineering Technical Management Processes Decision Analysis - Assists in trade-off analysis Provides optimization and sensitivity analysis capability
- Assists in recording, tracking, evaluating, and reporting decision outcomes
Technical Planning - Assists in planning and scheduling activities
- Assists in resource planning, tracking, and allocation Facilitates cost estimation
Technical Assessment - Assists in tracking, measuring, and assessing metrics
- Assists in metric collection
Requirements Management Provides requirements bi-directional traceability capability Provides requirements flow-down capability Tracks requirements changes Risk Management - Assists in risk, issue, and opportunity planning, identification, analysis, mitigation/management and monitoring
Configuration Management - Assists in the identification of configuration items
- Assists in baseline/version control of all configuration items
- Assists in ensuring configuration baselines and changes are identified, recorded, evaluated, approved, incorporated and verified
Technical Data Management - Assists in identification of data requirements
- Assists in recording and managing data rights
- Assists in storage, maintenance, control, use and exchange of data including digital artifacts
- Assists in document preparation, update, and analysis
Interface Management - Assists in capturing system internal and external interfaces and their requirement specifications
- Assists in assessing compliance of interfaces among system elements of the system or systems of systems
- Produces a view of interface connectivity
MBSE Software Tools:
- Requirements Management software provides a single, centralized platform to store, organize, and manage requirements, which enables better collaboration and communication among team members and stakeholders. Traceability provides end-to-end traceability between requirements, system elements, and their associated models, which ensures consistency throughout the development process and simplifies change management. Examples include Visure Requirements Platform, Siemens Teamcenter, and Sparx Systems Enterprise Architect to name a few. Listing these tools here is not an endorsement of these tools.
- Product Data Management (PDM) software manages design and engineering files such as CAD models and manufacturing instructions allowing teams to collaborate across concurrent design environments. PDM is mostly used by manufacturing companies to control product data from design to production. This type of software is beneficial for designers creating the initial specifications of a new product and production managers following manufacturing instructions. There are approximately 57 PDM software tool available to engineers. Examples include Autodesk Vault, Teamcenter, and Solidworks to name a few. Listing these tools here is not an endorsement of these tools.
- Product Lifecycle Management (PLM) software manages all of the information and processes at every step of a product or service lifecycle across globalized supply chains. Today’s PLM software provides the foundation and intersection of critical, cradle-to-grave product lifecycle processes woven with real-time data from technologies, such as the Internet of Things (IoT), artificial intelligence (AI), and machine learning (ML). Global organizations are leveraging what emerged as a “digital thread” to change how they design, manufacture, and service products. There are dozens of PLM software tools available to engineers. Examples include SAP PLM, Oracle Agile, and Aras PLM to name a few. Listing these tools here is not an endorsement of these tools.
- Ergonomic Design and Simulation software allows production engineers to design workstations and plant features while focusing on the man-machine interface in order to ensure safety of the worker, while providing for comfort, ease of use, productivity and performance. Examples include Delmia Ergonomic Workstations, Semins Human-centered design and simulation, ERGOMIX, and others. Listing these tools here is not an endorsement of these tools.
- Producibility Analysis software allows design engineers, along with other technical personnel, to design product that promotes the ease of fabrication and assembly thus reducing production time, while increasing reliability. See DFMA for more information. Examples include Solidworks DFMXpress, DFMPro, DFMA software by Boothroyd Dewhurst, and others. Listing these tools here is not an endorsement of these tools.
- Validation and Verification Support software supports the validation and verification of requirements by linking them to test cases, test results, and other verification artifacts, ensuring that the system meets its intended purpose and satisfies stakeholder needs. Examples include Visure, ANSYS SCADE Suite, Simulink, and others. Listing these tools here is not an endorsement of these tools.
- Change Management software provides efficient change management features such as version control, change tracking, and impact analysis, helping teams manage changes to requirements and their corresponding models effectively. Examples include Visure, Siemens Teamcenter, Topcased, and others. Listing these tools here is not an endorsement of these tools.
-
Note: There are many software vendors that offer these tools that are mostly used by government contractors. You can find more information on these software tools through a web search.
-
DAU Continuous Learning Modules and other training:
- CLE 084 Models, Simulations, and Digital Engineering https://icatalog.dau.edu/onlinecatalog/courses.aspx?crs_id=12176
- Modeling and Simulation in Digital Engineering https://media.dau.edu/media/1_289n9o27
- Modeling and Simulation 101: https://www.youtube.com/watch?v=X-6zxImekOE
Guidance and other Resources:
- DAU Community of Practice for Logistics Modeling and Simulation (M&S) https://www.dau.edu/acquipedia-article/logistics-modeling-and-simulation-ms
- DoD Modeling and Simulation Standards and Best Practice Guide
- Air Force Modeling and Simulation Resource Repository (MSRR) https://www.dau.edu/tools/air-force-modeling-and-simulation-resource-repository-msrr
- DoDI 5000.59 Modeling and Simulation (M&S) Management https://www.acqnotes.com/Attachments/DoD%205000.59%20Modeling%20and%20Simulation.pdf
- Modeling and Simulation (M&S) Guidance for the Acquisition Workforce https://www.dau.edu/cop/mq/documents/modeling-and-simulation-ms-guidance-acquisition-workforce
- M&S and DE Guidance and other Resources
-
- DoDI 5000.59 DoD Modeling and Simulation Management https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/500059p.pdf
- M&S Guidance for the Acquisition Workforce https://acqnotes.com/Attachments/Modeling%20&%20Simulation%20Guidance%20for%20the%20Acquisition%20Workforce.pdf
- DoD Digital Engineering Strategy https://apps.dtic.mil/sti/pdfs/AD1068564.pdf
- Digital Engineering, Modeling and Simulation (DEMS) Community of Practice (CoP) https://www.cto.mil/sea/dems_cop/
- DoD Modeling and Simulation Related Standards and Best Practices Guide https://www.cto.mil/sea/dems/
- Producibility Engineering
-
Producibility can be defined as “the measure of the relative ease of manufacturing.” That is, you can manufacture a part out of inexpensive material, using unskilled workers, simple tools, and manufacture it in a very short time.
The terms "producibility" and "manufacturability" are often used interchangeably. The DoD Producibility and Manufacturability Engineering Guide distinguishes between producibility and manufacturability as distinct but complimentary and sometimes overlapping concepts.
Producibility is a "design" consideration to facilitate the ease of manufacture, that is, designing a product in a way so it is relatively easy to manufacture. That includes any technique that helps to improve the designs efficient and ability to be produced (see producibility tools below). Development teams should consider producibility during system development and design following detailed design guidelines and producibility principles.
Manufacturability is a "factory floor or manufacturing operations," consideration used to enhance the ease of manufacture by developing and implementing efficient manufacturing processes. This includes and best practices like the use of Lean/Six Sigma, Theory of Constraints, Process Failure Modes and Effects Analysis, continuous process improvement, and others.
Note: Producibility Analysis is a requirement of MIL-HDBK-896, para. 6.2.1, and is addressed in the DoD Systems Engineering Guidebook. See Producibility Best Practices for more information on Producibility Engineering.
Listed below are some things to consider during the design process:
Producibility Resources
- MIL-HDBK-727 (while dated, it has the most comprehensive coverage of Producibility) http://everyspec.com/MIL-HDBK/MIL-HDBK-0700-0799/MIL_HDBK_727_1853/
- DoD Producibility and Manufacturability Engineering Guide https://www.cto.mil/wp-content/uploads/2024/06/DoD-Producibility-and-Manufacturability-2024.pdf
- DI-MGMT-80797A Producibility Analysis Report https://www.dodmrl.com/DI-MGMT-81889%20Manufacturing%20Plan.pdf
Producibility Tools (most will require a search of the web as there are no DoD links for these and there are dozens of links for each of the tools listed).
- Design for Manufacturing (DFM)
- Design for Assembly (DFA)
- Design for Manufacturing and Assembly (DFMA)
- Process Failure Modes Effects Analysis (PFMEA)
- Design for Ergonomics (DFE):
- Design for Reliability (DFR):
- Design for Maintainability (DFM):
- Design for Sustainability (DFS):
- Design for Quality (DFQ):
- Design for Supply Chain:
- Design for Safety (DFS):
- Producibility Assessment Worksheet
The graphic below illustrated the improvements from producibility initiatives.
Note: You can find more information on these producibility tools through a web search.
DAU Continuous Learning Modules and training:
- Producibility an Important Design Consideration https://media.dau.edu/media/1_mi18z71t
Guidance and other Resources:
- DoD Producibility and Manufacturability Engineering Guide https://www.cto.mil/wp-content/uploads/2024/06/DoD-Producibility-and-Manufacturability-2024.pdf
- NAVSO P-3687 Producibility Systems Guidelines http://everyspec.com/USN/NAVY-General/NAVSO_P-3687_8510/
- NAVSO P-6071 Best Practices http://everyspec.com/USN/NAVY-General/NAVSO_P-6071_MAR1986_8506/
- Design for Manufacturability Handbook, Bralla (available on Amazon) https://www.amazon.com/Design-Manufacturability-Handbook-James-Bralla/dp/007007139X
- Note: There have been many other books written on Manufacturability or Producibility that you can find with a web search
- Note: There are many videos on Manufacturability or Producibility that you can find with a web search
- Key Characteristics
-
A key characteristic is a feature whose variation has the greatest impact on the fit, performance (function), or service life of the finished product from the perspective of the customer. In other words, it is a product or process characteristic that if you deviate from the target value, there is a high loss function the further from the target value you get, and it will cost you (see graphic below). Most characteristics have a low loss function and thus do not need the same management attention as does a Key or Critical characteristic. Thus, when you deviate for the target value on a characteristic that has a low loss function, there is not a significant impact to fit, function or service life. However, Key Characteristics are the vital few characteristics that must be identified and managed in order to avoid this high loss function.
Note: A KC can be either a product, process, or service KC.
The management of KCs includes:
- Identifying product characteristics of the design which most influence fit, performance or reliability
- This will require the use of one or more of the approaches listed below
- Supporting the mapping of product characteristics to production processes
- Enabling the balancing of product design requirements with manufacturing process capabilities
- Enabling the development of the required process controls for production.
Engineers have used a wide variety of tools or approaches for identifying KCs with the identification process beginning in the design stage. There are objective and subjective approaches that may be used to help identify and manage KCs to include:
- Quality Function Deployment (QFD)
- Taguchi experimentation
- Capability Analysis
- Design Failure Mode and Effects Analysis (DFMEA)
- Process Failure Mode and Effects Analysis (PFMEA)
- Statistical Process Control (SPC)
- Design Verification
- Control Plans
- Statistical analysis of yield
- Process Flow Charts
- Advanced Product Quality Planning (APQP)
- Production Part Approval Process (PPAP)
- Field Reporting and Corrective Action System (FRACAS)
- Reliability data from similar products.
Watch the Ford Batavia Transmission Quality study at the url listed below for an excellent example of a company that was facing a serious manufacturing problem with building transmissions that were reliable, and Ford used some of the tools listed above to identify and manage key characteristics and get control of their manufacturing problems that helped them to achieve cost, schedule and reliability goals. What Ford found was that out of thousands of measurement characteristics, only four were significant to achieving their manufacturing goals. This profound knowledge then allowed them to control their processes. Note that the film is quite old but one of the best examples available.
The Batavia Movie https://www.youtube.com/watch?v=uAfUOfSY-S0
NOTE: Technical personnel should also control the quality of parts designated as Critical Safety Items (CSIs) or Critical Application Items. In addition to managing KCs technical personnel need to manage special characteristics which AIAG divides into two categories critical characteristics and significant characteristics. You can find more information on these tools through a web search.
- Special Characteristics: Product characteristics or manufacturing process parameters that can affect safety or compliance with regulations, fit, function, or performance.
- Significant Characteristics: Characteristics that are important to the customer or final client, but do not have a direct impact on the safety, performance or functionality of the product, but can still affect customer satisfaction.
- Critical Characteristics: Special characteristics that are crucial for the safety, performance, or functionality of the product. These characteristics have a direct impact on quality, reliability, and safety. If critical characteristics are not identified and managed, they could result in serious consequences.
- Source: IATF 16949:2016 clause 8.3.3.3 Special Characteristics
- These characteristics can be identified and managed using the tools and approaches listed above.
Below is a notional chart depicting the activities that should be accomplished during each planning and execution phase of development and production.
Key Characteristics Guidance can be found in:
- AS6500 Manufacturing Management Program https://www.sae.org/standards/content/as6500/
- AS9100 - Model for Quality Assurance in Design, Development, Production, Installation and Servicing https://www.sae.org/standards/content/as9100/
- AS9103 Variation Management of Key Characteristics https://www.sae.org/standards/content/as9103/
- MIL-HDBK-896 Manufacturing Management Program Guide https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=276275
- Identifying product characteristics of the design which most influence fit, performance or reliability
- Producibility Best Practices
-
Producibility analysis. Producibility should be considered as a part of design trade studies. The role of design trade studies in the manufacturing development process is to achieve a product design that effectively balances the system design with cost, schedule and performance elements to minimize total program risk. Institutionalizing producibility as part of the design trade study process is essential to an overall goal of affordable weapon system acquisition. Another excellent source for information on producibility programs is the Navy’s NAVSO P-3687, “Producibility System Guidelines.” This guide recommends a 5-step process: 1. establish a producibility infrastructure, 2. determine process capabilities, 3. address producibility during conceptual design, 4. address producibility during detailed design, and 5. measure producibility.
Producibility Best Practice tools include: the following and may require a web search to gather more information:
- Quality Function Deployment (QFD): A structured process and set of tools that can be used to tools used to effectively define customer requirements and convert them into detailed engineering specifications and plans to produce the products that fulfill those requirements. QFD is used to translate customer requirements (or VOC) into measurable design targets and drive them from the assembly level down through the sub-assembly, component and production process levels.
- Concurrent Engineering (CE): I more of an approach to engineering than a specific tool. Concurrent engineering can be used to reduce product development time while reducing costs and improving quality and reliability by concurrently and systematically product design along with associated manufacturing, quality and other processes.
- Integrated Product and Process Development (IPPD): Is a DoD management technique that simultaneously integrates all essential acquisition activities through the use of Integrated Product Teams (IPTs) to optimize design, manufacturing, and supportability processes. IPPD facilitates meeting cost and performance objectives from product concept through production, including field support. It evolved in industry as an outgrowth of efforts such as Concurrent Engineering to improve customer satisfaction and competitiveness in a global economy.
- Integrated Product Teams (IPT): An Integrated Product Team (IPT): Is a team composed of representatives from appropriate functional disciplines working together to build successful programs, identify and resolve issues, and make sound and timely recommendations to facilitate decision-making. IPTs are used in complex development programs/projects for review and decision-making. The emphasis of the IPT is on the involvement of all Stakeholders (users, customers, management, developers, contractors) in a collaborative forum.
- Taguchi/Robust Design/Parameter Design: Is s a powerful statistical method to produce high quality product and optimize the process design problems in a cost-efficient way by reducing process variation through robust design of experiments. An experimental design is used to identify and exploit the interactions between control and noise factors. Once the significant factors have been identified and their control settings established the resultant product will be optimized by designing quality into the product and processes.
- Taguchi Loss Function: Is a graphical technique to show how an increase in variation from the target value, on key characteristics, can have an exponential impact on cost, reliability and customer dissatisfaction. Traditional quality looks at product quality as either good or bad, that is it either meets the spec or does not. While this may be true for many characteristics, it is not true for key characteristics.
-
Modeling and Simulation M&S): Manufacturing simulation is the use of computer modeling to virtually test manufacturing methods and procedures – including processes such as production, assembly, inventory, and transportation. Simulation software can be used to predict the performance of a planned manufacturing system and to compare solutions for any problems discovered in the system's design. This makes manufacturing simulation a significantly competitive capability - allowing manufacturers to test a range of scenarios before buying tooling, reserving capacity, or coordinating other expensive production resources. By using simulation software to determine exactly what is needed, the manufacturer can avoid problems during production while also reducing scrap and rework. Various types of Factory Modeling and Simulation tools currently available include, but are not limited to the following areas:
• Producibility Analysis and Ergonomics
• Process Planning
• Production Planning and Scheduling
• Line Balancing and Bottleneck Analysis
• Capacity Planning
• Predictive Analytics and Optimization
• Facility Planning, Layout and Design
• Virtual Factory Mock-up - Model Based Engineering (MBE): Uses annotated digital three-dimensional (3D) models of a product and relevant production equipment and processes as the authoritative information source for all activities in that product’s lifecycle including relevant production equipment and processes. MBE is an integral part of the technical baseline that evolves throughout the acquisition life cycle.
- Model Based Systems Engineering (MBSE): Is a systems engineering methodology that focuses on creating and exploiting domain models as the primary means of information exchange between engineers, rather than on document-based information exchange. MBSE is generally defined as a formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases. MBSE uses models as an integral part of the technical baseline, which includes the requirements, analysis, design, implementation, and verification of a capability, system, and/or product throughout the acquisition life cycle
- Computer Aided Design (CAD): Is the process of digitally creating design simulations of products in 2D or 3D, complete with scale, precision, and physics properties, to optimize and perfect the design – often in a collaborative manner – before manufacturing. The use of digital data allows various engineering functions to share, review, simulate, and edit technical data and allow organizations to introduce new product quickly.
- Computer Aided Manufacturing (CAM): Involves the use of digital data, software and computer-controlled factory machinery to create products with a high quality by automating and optimizing manufacturing processes. CAM is used to either create new or improve upon existing manufacturing setups to boost efficiency and reduce wastage. It does so by expediting the manufacturing process and tooling and reducing energy requirements. The final results have a high degree of consistency, quality, and accuracy.
- Note: You can find more information on these producibility tools through a web search.