U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Breadcrumb

  1. Home
  2. Communities of Practice
  3. Engineering
CommentCommunity

Engineering

This Community serves as a collaborative space to provide resources for systems engineering (SE) practitioners. These resources support program planning and design activities as well as implementation of SE processes. In addition this Community offers a variety of ways for Engineering to network with other SE practitioners, to access current community contributions and discussions on SE tips and best practices, and to share expert knowledge related to SE.

Members

Views

Community Contacts

COMMUNITY / Engineering
Mitchell Woods - Community Leader
COMMUNITY / Engineering
Monique Ofori - Community Leader
COMMUNITY / Engineering
Patrick Dallosta - Community Leader
COMMUNITY / Engineering
John Snoderly - Community Leader

Feed / Engineering

Event / Engineering
Specialty Engineering and Design Considerations
View Event

Specialty Engineering 

{insert text}

Design Considerations
 

The PM, Systems Engineer, and Lead Software Engineer should address and document design considerations, including all statutory and regulatory requirements in order to:

  • Translate the end-user desired capabilities into a structured system of interrelated design specifications that support delivery of required operational capability.
  • Enable trade-offs among the design considerations in support of achieving desired mission effectiveness within cost and schedule constraints.
  • Incorporate design considerations into the set of system requirements, as some are mandated by laws, regulations, or treaties, while others are mandated by the domain or DoD Component or Agency; these mandates should be incorporated during the Requirements Analysis process to achieve balance across all system requirements.
     

The DoD has put additional emphasis on the four Specialty Engineering design considerations as well as Value Engineering identified in the tiles below resulting in development of additional policy (DoDI 5000.88) and additional guidance. Select the tiles below and please refer to Section 5 of the Systems Engineering Guidebook for more information.
 


 

Event / Engineering
SE Processes
View Event

Systems Engineering Processes

The SE processes are used by contractor and Government organizations to provide a framework and methodology to plan, manage and implement technical activities throughout the acquisition life cycle. SE planning and execution should focus on applying the processes and tools in a rigorous, integrated, and disciplined manner to achieve a system solution that balances performance, cost, schedule, and risk. 

The eight technical management processes, applicable to all acquisition pathways, provide a consistent framework for managing technical activities and identifying the technical information and events critical to the success of the program. Technical information includes controlled unclassified information (CUI) as well as classified and unclassified Critical Technical Information (CTI) about DoD sponsored research, technology, programs, and systems being acquired. The eight technical processes ensure the system design and the delivered capability reflect the requirements that the stakeholders have expressed. The 16 SE processes are applicable to all the AAF pathways to some degree. The PM and SE will determine which processes to use for their program. 

Whereas the technical management processes provide insight of, and control over, the technical development of a system throughout its life cycle, the technical processes are used to design, develop and analyze the system, system elements and enabling system elements required for integration, test, production, deployment, support, operation and disposal. The eight technical processes provide a framework for ensuring and maintaining traceability between stakeholder requirements, systems design and the eventual delivered capability.
 

For more information refer to Section 4 of the Systems Engineering Guidebook.
 

Technical Management Processes
 
Technical Processes
 
Technical Planning  Stakeholder Requirements Definition
Decision Analysis  ​Requirements Analysis 
Technical Assessment  ​Architecture Design 
Requirements Management Implementation 
Risk Management Integration 
Configuration Management  Verification 
Technical Data Management  Validation 
Interface Management  Transition 

 

 

 


Event / Engineering
Technical Planning Process
View Event

 

Technical Planning Process

The Technical Planning Process is the method to define the scope of the technical effort required to develop, field, and sustain the system, as well as provides critical quantitative inputs to program planning and life-cycle cost estimates. Technical planning provides the program office with a framework to accomplish the technical activities that collectively increase product maturity and knowledge and reduce technical risks.  This sub-topical area contains information on the Technical Planning Process found in the Systems Engineering Guidebook, Section 4.1.1.

https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
Event / Engineering
Decision Analysis Process
View Event

Decision Analysis Process  

The Decision Analysis Process is the method to transform a broadly stated decision opportunity into a traceable, defendable, and actionable plan.  Decision Analysis can be the central process for formulating, managing, and executing an effective and efficient program at any point in the life cycle.  This sub-topical area contains information on the Decision Analysis Process found in the Systems Engineering Guidebook, Section 4.1.2. 

https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf

Discussions / Engineering

DoD SEP Outline v4.1 Now Posted to SE&A Site
0 Replies
View Discussion
QUESTION SCENARIO
QUESTION

​DoD SEP Outline v4.1, 26 Apr 23, is now posted to the SE&A Engineering References for Program Office site in both Word and PDF formats. Links:

Word format

PDF format

SCENARIO
Updates to DTRAM, IMP/IMS Guide, and SEP Outline published in Apr-May 2023
1 Replies
View Discussion
QUESTION SCENARIO
QUESTION

​OUSD(R&E) SE&A has published updates to the following guidance documents in the past month:

DoD SEP Outline v4.1 adds a new Section 3.7 on Corrosion Prevention and Control (CPC). The sections after that were renumbered accordingly. v4.1 was released 26 Apr 23 but not yet posted on the SE&A website.

Defense Technical Risk Assessment Methodology (DTRAM) v6.4 adds emphasis on CPC by adding criteria 7.2.C5 to the Manufacturing parent criteria area and criteria 8.2.C4 to the RAM & Sustainment parent criteria area.

The Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) Preparation and Use Guide update to the 2005 version was released in late May 2023. It, too, is not yet posted on the SE&A site but will be in the future.

SCENARIO
Goulet, Joseph… September 25, 2023 - 12:35pm

SE&A's updated IMP/IMS guide and SEP Outline have been posted to SE&A's "Policy and Guidance" site at [https://www.cto.mil/sea/pg/]. Also, SE&A just posted the updated RIO Guide (Sep 2023)

Human Systems Integration (HSI) is a key enabler to Systems Engineering processes
0 Replies
View Discussion
QUESTION SCENARIO
QUESTION

Integrating human performance considerations into the defense acquisition system can present substantial challenges for Human Systems Integration (HSI) practitioners and stakeholders. The DAU HSI Community of Practice (CoP) provides a unique resource in this pursuit, offering a convenient platform to share knowledge aimed at achieving effective and relevant HSI practice across government, industry, and academia. Learn more about HSI as a Specialty Engineering discipline described within DODI 5000.88 for incorporating human needs during system design at the following resources:

DAU HSI COP

OUSD(R&E) HSI website:


SCENARIO

Events / Engineering

No content available.

Announcements / Engineering

Community Announcement / Engineering
New HSI tool for Systems Engineers
View Announcement

Integrating human performance considerations into the defense acquisition system can present substantial challenges for Human Systems Integration (HSI) practitioners and Systems Engineers. The DAU HSI Community of Practice (CoP) provides a unique resource in this pursuit, offering a convenient platform to share knowledge aimed at achieving effective and relevant HSI practice across government, industry, and academia. The HSI COP aims to help stakeholders find knowledge that can be readily applied in practice, including references, standards, templates, lessons learned, and best practices. 

A key resource for Systems Engineers to be compliant with the requirements outlined in DoDI 5000.95 is use of the HSI Framework (HSIF) tool.  Check out this invaluable tool here. The HSIF tool details all the required HSI activities for a program to successfully comply with HSI planning, management, and execution. Register for access today!!

Community Announcement / Engineering
DoD Engineering Recruitment Tool (Brochure) - Now Available for Use
View Announcement

SE CoP Members - In coordination with the Engineering Career Field Functional Integrated Product Team (FIPT) and OSD Graphics Division, a new DoD engineering recruitment tool has been developed to help attract new engineering talent to DoD’s workforce, and increase DoD’s recognition as one of the best places to work as an engineer.  The Defense Services and Agencies can use this brochure to augment their current recruiting and marketing material/messaging.  Included are examples which showcase how you can make a difference as a DoD engineer; descriptions of the unique work being done throughout the Department, and what you can look forward to as a DoD engineer. Also included are figures displaying the wide geographic distribution and variety of engineers employed by DoD.

Image removed.DoD Engineering Recruitment Tool (Brochure).pdf


Resources / Engineering

Community Resource / Engineering
Specialty Engineering and Design Considerations

Specialty Engineering 

{insert text}

Design Considerations
 

The PM, Systems Engineer, and Lead Software Engineer should address and document design considerations, including all statutory and regulatory requirements in order to:

  • Translate the end-user desired capabilities into a structured system of interrelated design specifications that support delivery of required operational capability.
  • Enable trade-offs among the design considerations in support of achieving desired mission effectiveness within cost and schedule constraints.
  • Incorporate design considerations into the set of system requirements, as some are mandated by laws, regulations, or treaties, while others are mandated by the domain or DoD Component or Agency; these mandates should be incorporated during the Requirements Analysis process to achieve balance across all system requirements.
     

The DoD has put additional emphasis on the four Specialty Engineering design considerations as well as Value Engineering identified in the tiles below resulting in development of additional policy (DoDI 5000.88) and additional guidance. Select the tiles below and please refer to Section 5 of the Systems Engineering Guidebook for more information.
 


 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
View Resource
Community Resource / Engineering
SE Processes

Systems Engineering Processes

The SE processes are used by contractor and Government organizations to provide a framework and methodology to plan, manage and implement technical activities throughout the acquisition life cycle. SE planning and execution should focus on applying the processes and tools in a rigorous, integrated, and disciplined manner to achieve a system solution that balances performance, cost, schedule, and risk. 

The eight technical management processes, applicable to all acquisition pathways, provide a consistent framework for managing technical activities and identifying the technical information and events critical to the success of the program. Technical information includes controlled unclassified information (CUI) as well as classified and unclassified Critical Technical Information (CTI) about DoD sponsored research, technology, programs, and systems being acquired. The eight technical processes ensure the system design and the delivered capability reflect the requirements that the stakeholders have expressed. The 16 SE processes are applicable to all the AAF pathways to some degree. The PM and SE will determine which processes to use for their program. 

Whereas the technical management processes provide insight of, and control over, the technical development of a system throughout its life cycle, the technical processes are used to design, develop and analyze the system, system elements and enabling system elements required for integration, test, production, deployment, support, operation and disposal. The eight technical processes provide a framework for ensuring and maintaining traceability between stakeholder requirements, systems design and the eventual delivered capability.
 

For more information refer to Section 4 of the Systems Engineering Guidebook.
 

Technical Management Processes
 
Technical Processes
 
Technical Planning  Stakeholder Requirements Definition
Decision Analysis  ​Requirements Analysis 
Technical Assessment  ​Architecture Design 
Requirements Management Implementation 
Risk Management Integration 
Configuration Management  Verification 
Technical Data Management  Validation 
Interface Management  Transition 

 

 

 


CREATED:
BY:
Rhyne, Darren
LAST MODIFIED:
BY:
Rhyne, Darren
View Resource
Community Resource / Engineering
Technical Planning Process

 

Technical Planning Process

The Technical Planning Process is the method to define the scope of the technical effort required to develop, field, and sustain the system, as well as provides critical quantitative inputs to program planning and life-cycle cost estimates. Technical planning provides the program office with a framework to accomplish the technical activities that collectively increase product maturity and knowledge and reduce technical risks.  This sub-topical area contains information on the Technical Planning Process found in the Systems Engineering Guidebook, Section 4.1.1.

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource
Community Resource / Engineering
Decision Analysis Process

Decision Analysis Process  

The Decision Analysis Process is the method to transform a broadly stated decision opportunity into a traceable, defendable, and actionable plan.  Decision Analysis can be the central process for formulating, managing, and executing an effective and efficient program at any point in the life cycle.  This sub-topical area contains information on the Decision Analysis Process found in the Systems Engineering Guidebook, Section 4.1.2. 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource
Community Resource / Engineering
Technical Assessment Process

 

Technical Assessment Process

The Technical Assessment Process is the method to provide a fact-based understanding of the current level of product knowledge, technical maturity, program status, and technical risk by comparing assessment results against defined criteria. These assessment results enable a better understanding of the health and maturity of the program, giving the program office a sound technical basis upon which to make program decisions. This sub-topical area contains information on the Technical Assessment Process found in Section 4.1.3 of the Systems Engineering Guidebook.
 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource
Community Resource / Engineering
Requirements Management Process

 

Requirements Management  

The Requirements Management Process is the method to maintain a current and approved set of requirements over the entire acquisition life cycle. This method helps ensure delivery of capability that meets intended mission performance to the operational user. This sub-topical area contains information on the Requirements Management Process found in the Systems Engineering Guidebook, Section 4.1.4. 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource
Community Resource / Engineering
Risk Management Process

 

Risk Management  

The Risk Management Process is the method to manage risks, issues and opportunities.  While risks, issues and opportunities have different characteristics, managing each utilizes a similar process where they are identified, analyzed, mitigated or handled, and monitored. Effectively managing risks, issues, and opportunities helps the Program Manager and Systems Engineer develop and maintain a system’s technical performance, achieve cost goals, and meet schedule estimates. This sub-topical area contains information on the Risk Management Process found in the Systems Engineering Guidebook, Section 4.1.5. 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource
Community Resource / Engineering
Configuration Management Process

Configuration Management Process

The Configuration Management Process is the method to establish and maintain consistency of a system’s functional, performance, and physical attributes with its requirements, design, and operational information and allows technical insight into all levels of the system design throughout the system's life cycle. This sub-topical area contains information on the Configuration Management Process found in the Systems Engineering GuidebookSection 4.1.6. 
 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource

Documents / Engineering

Software Transition Plan STrP Data Item Description DID
Document Type:
Document
Modified: Changed by Content Author No Reply on
Summary

The Software Transition Plan (STrP) identified the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developer's plans for transitioning deliverable items to the support agency.  The STrP is developed if the software support concept calls for transition of responsibility from the developer to a separate support agency.  The STrP may also be used by the acquirer for updating the Computer Resources Life Cycle Management Plan.  This Data Item Description (DID) is used when the developer is tasked to develop and record plans for transitioning deliverable items to the support activity. The STrP DID (DI-IPSC-81429) can be found on the DoD DLA ASSIST website at http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205908>. BOV

Schematic Block Diagrams Data Item Description DID
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

Schematic Block Diagrams are used as the basis for displaying functional and technical requirements and interfaces.  As such, they support the design synthesis, integration, and interface compatibility functions. The Schematic Block Diagrams DID (DI-GDRQ-81223) can be found on the DoD DLA ASSIST website at http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205262. BOV

NAVAIR Specific SE Policy, Guidance, and Tools
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

NAVAIR 4.1 Systems Engineering develops and grows the Systems Engineering capability of NAVAIR-through engineering policy, and substantive technical engagement throughout the life cycle of acquisition programs. Delivering a robust Systems Engineering capability across NAVAIR requires attention to Policy, People, and Practice. The NAVAIR SE website provided systems engineering policy, guidance,  training, and resources for NAVAIR systems engineers to support their mission. In addition, the website provides an online SETR checklist tool specific to NAVAIR policy and best practices.  NAVAIR SE Website: https://nserc.nswc.navy.mil/navair/NAVAIRSE/SitePages/Home.aspx    DISCLAIMER: The NAVAIR SE Website is developed and maintained by NAVAIR 4.1 Systems Engineering and is not endorsed by DASD(SE) for DoD-wide use.

DASD SE Guidance
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

TBD TBD

Naval SYSCOM Risk Management Policy
Document Type:
Document
Modified: Changed by Content Author No Reply on
Summary

To establish policy and assign responsibilities for a standardized risk management process across all Naval Systems Commands (SYSCOMs) and affiliated Program Executive Officers (PEOs).

Software Center Operator Manual SCOM Data Item Description DID
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

The Software Center Operator Manual (SCOM) provides personnel in a computer center or other centralized or networked software installation information on how to install and operate a software system.  The SCOM is developed for software systems that will be installed in a computer center or other centralized or networked software installation, with users accessing the system via terminals or personal computers or submitting and receiving inputs and outputs in batch or interactive mode.  This Data Item Description (DID) is used when the developer is tasked to identify and record information needed by persons who will operate software in a computer center or other centralized or networked software installation, so that the software can be used by others. The SCOM DID (DI-IPSC-81444) can be found on the DoD DLA ASSIST website at http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205923. BOV

Establishing the Technical Foundation - MSA Phase
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

From the DASD(SE) web site: "In the Defense Acquisition Research Journal article Establishing the Technical Foundation: Materiel Solution Analysis Is More than Selecting an Alternative, DASD(SE) team members Aileen G. Sedmak, Zachary S. Taylor, and Lt Col William A. Riski, USAF (Ret.) discuss evidence that adequately resourced systems engineering and technical planning before Milestone A can help a program define realistic requirements, establish executable programs, and deliver systems on time and on budget. "Several government and independent studies indicate effective systems engineering and program planning in the early stages of acquisition are essential to controlling costs and improving program results. The article describes the challenge of conducting good systems engineering and technical planning during the Materiel Solution Analysis (MSA) phase after completion of the Analysis of Alternatives and before Milestone A. "The article also presents the work of the DoD Development Planning Working Group to mitigate this challenge by describing the technical activities in the MSA phase necessary to develop the level of knowledge and system concept maturity necessary to proceed into the next phase of acquisition. These technical activities are represented in a notional MSA Phase Activity Model." .

Public Law, document synopsis, e.g.,
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

TBD TBD

To participate in this community, you must be registered. Join Now