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)
- Log in to post comments
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.
108 |
This NASA policy directive, while short, provides a detailed discussion defining acceptable levels of mission success risk and crew safety levels for flight and is applicable to NASA HQ, NASA Centers, and their employees while expressing the importance of protecting all entities including terrestrial, orbital, and planetary environments from harm, and create a culture that understands risk, and safety. The directive is for use by the Administrator and goes through the process of identifying, accessing, managing, and accepting crew safety and mission safety and encouraging reporting without being held for misconduct.
The NASA Standard reviews safety for the handling and processing of explosives, propellants, and pyrotechnics by an individual. This standard is applicable to anyone that handles, stores, transports or encounters explosives or anything containing explosive materials. To ensure the safety of the system, and those handling and processing explosives need to understand and implement safety standards, procedures and requirements outlined in the NASA Standard. The Standard presents these as General and Detailed requirements.
https://standards.nasa.gov/sites/default/files/standards/A/0/nasa-std-871912a.pdf
The Federal Aviation Administration outlines and defines what SS is, a few key definitions, objectives, description, hazard identification, risk analysis, risk assessment and decision-making process, validation and control, system modifications (as needed). It should be noted that this document can be used as an outline or guide for the SS process but does not go into depth on the topics listed above.
https://www.faasafety.gov/gslac/alc/libview_normal.aspx?id=6877
This instruction’s main purpose is to ensure the safety of Air Force personnel and their assets. The US Air Force Mishap Prevention Program’s vision is that there will be compliance with all guidelines, risk reduction and continuous improvement.
https://static.e-publishing.af.mil/production/1/af_se/publication/dafi91-202/dafi91-202.pdf
The Risk Management Process Guide is designed to be utilized by program personnel assigned to each category in addition to the program risk manager. It is also important to remember that risk management is a job for everyone involved in the program including engineers, action officers, Program managers and everyone in-between, not only the individuals working on a specific aspect of the program.
This acquisition guidebook is meant to provide in detail the entire acquisition process and framework for the Navy which only mentions system safety once on p.6 when outlining preparation of program documents to include “system safety program to identify Environment, Safety, and Occupational Heath (ESOH) hazards”.
This manual’s purpose was to outline how SSE should be integrated into each system throughout their lifecycle. The manual does so by incorporating numerous guidance documents, which should be used from the beginning of a system’s lifecycle through disposal, into one manual for NAVSEA and other appropriate offices/departments on the policies that involve SSE such as ESOH, and risk management.
https://community.apan.org/wg/usdre/se-a/specengr/sse/m/documents/471981
This instruction is used to outline how to develop a System Safety Program, review policy for NAVSEA, PEOs, CHENG, PM, Principal for Safety (PFS) and other program personnel to ensure fielded systems are safe and following current applicable guidance while implementing & integrating SSE into all phases of the system lifecycle.
https://www.navsea.navy.mil/Portals/103/Documents/NAVINST/05100.021B.pdf
This instruction describes the Navy-wide use of operational risk management (ORM). The ORM process includes identifying hazards, assessing hazards, making risk decisions, implementing controls, and supervising.
This policy supersedes NAVAIRINST 5000.21A and must be reviewed annually, making changes as needed. The beginning ensures that this policy is compliant with other risk management requirements and begins explaining the circumstances of various terms relating to risk management. The following section delineates actions taken by PEO and systems command (SYSCOM) Commanders, PMs, Risk Management Boards (RMB), IPTs, Technical Authorities. and their responsibilities in the risk management process.
The PEO Theater Surface Combatant (TSC)’s Risk Management Instruction focuses on defining risk, risk management, PEO TSC Risk Management Program, risk identification, risk characterization and assessment, risk analysis and mitigation, risk tracking and reporting, likelihood of occurrence, consequences of risk, product programs, and mission programs. The procedures concentrate on reporting risk tracking and board membership requirements, which require a government member at a minimum, a representative from ASN (RDA), Chief Engineer (CHENG), and a representative from Defense Systems Management College (DSMC).
This manual briefly discusses system safety and risk throughout the entire document but also has Chapter 38 completely dedicated to System Safety. Chapter 38 is broken up into four categories: Discussion and Background, Highlights of System Safety Program, System Safety Working Groups (SSWG)/ Facility System Safety Working Groups (FSSWG). The SS program can help prevent injury, death, illness of personnel while also protecting the systems from adversaries and destruction to ensure a safe and successful mission.
https://www.secnav.navy.mil/doni/SECNAV%20Manuals1/5100.23%20CH-2.pdf
The CDC uses this document to convey their approach for hazard identification and risk analysis. As previously mentioned in MIL-STD-882E (2012) risk is determined as a function of the probability that a mishap will occur and (should a mishap occur) the impact (in terms of severity level) the mishap would have on system sustainability, survivability, and performance. The guide has 16 lessons beginning with an introduction to SS through various methods of accessing risk utilizing fault, success and even tree analysis, block diagrams, risk assessment matrix, cause-consequence analysis, failure analysis, reliability block diagrams etc. Each section outlines the purpose, description, application, procedures, samples including advantages and limitations of each method that can be used to determine and assess risks and hazards for management to be able to determine if the risk needs to be mitigated or accepted.
This Army regulation recently underwent a major revision, including a title change from the previous title of “The Army Safety Program”. The document reviews the specific responsibilities of from the Secretary of the Army establishing and implementing requirements down to the material developers, acquisition managers, and equipment, process, and facility designers and their contract responsibilities.
https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN34981-AR_385-10-000-WEB-1.pdf
This guide consists of eight chapters that include discussions on system safety management, risk and hazards management, integration of system safety associated disciplines, SS for testers and evaluators, weapon SS reviews, facility SS, facility SS program management, and facility SS program contracting.
https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN30886-PAM_385-16-000-WEB-1.pdf
This Army Pamphlet, while acquisition focused, is being included in this BoK because it discusses SS throughout multiple sections. SS is first discussed in Section 5 entitled, “Manpower and Personnel Integration/Human Systems Integration”. Under “Manpower and personnel integration considerations” SS is called out to be addressed by MATDEV’s strategy for HSI. Further mentioning of SS provides emphasis on early integration in the acquisition lifecycle.
SS programs will be developed based upon the risk management requirements and document risks by identifying, tracking, managing and mitigating hazards in the Human Systems Integration Plan (HSIP).
https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN11426_DAPam70-3_FINAL.pdf
This instruction is brief, but applies to all weapon and laser systems, except for medical and industrial, legacy systems and joint legacy systems.
JSSSEH is a handbook that is meant to clarify activities such as, design, code, test, independent verification, and validation (IV&V), operation and maintenance, and change control functions within the software engineering development and deployment processes (p.1).
https://ac.cto.mil/wp-content/uploads/2019/06/Joint-SW-Systems-Safety-Engineering-Handbook.pdf
The Risk Management Guide, which is utilized primarily by the PM, goes further in depth into the common sources of risk, how to identify and analyze risk, implement mitigation strategies and tracking than MIL-STD-882E.
This military standard outlines and defines the general requirements for system safety (SS) processes, approaches, and risks.
https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=36027
The guide goes over the three safety precepts that are necessary for unmanned systems, programmatic safety precept (PSP), operational safety precept (OSP), and design safety precept (DSP).
https://www.cto.mil/wp-content/uploads/2023/06/UxS-Precepts-2021.pdf
Systems Engineering Planning
|
|
|
Systems Engineering Processes
|
|
Technical Management ProcessesTechnical management processes are applicable to all acquisition pathways, providing a consistent framework for managing technical activities, as well as 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. |
|
Technical ProcessesTechnical processes ensure the system design and the delivered capability reflect the requirements that the stakeholders have expressed. |
Value engineering (VE) plays an integral and enduring role in accomplishing DoD's mission to provide the military forces needed to deter war and protect the security of our nation. DoD Instruction 4245.14, "DoD Value Engineering (VE) Program," implements 41 USC 1711, "Value Engineering," and Office of Management and Budget Circular No. A-131, "Value Engineering," to ensure the "effective administration of the DoD VE Program."
FAR Part 48, "Value Engineering," "prescribes policies and procedures for using and administering value engineering techniques in contracts."
Value Engineering (VE) is an organized, systematic technique that analyzes the functions of systems, equipment, facilities, services, and supplies to ensure they achieve their essential functions at the lowest life-cycle cost consistent with required performance, reliability, quality, and safety.
The DoD VE program has two elements:
Components retain DoD resource benefits resulting from the use of VE. For those that want to reach out to the broader Value Engineering community and potential commercial certification, see: https://www.value-eng.org/
For additional information on value engineering tools see the Systems Engineering Guidebook, Section 2.2.7. Value Engineering. This sub-topical area contains information on the use of value engineering in DoD acquisitions.
UPCOMING EVENTS
DEVCOM AvMC Value Management Documentation Course scheduled for July 23-25, 2024
All,
The DEVCOM AvMC VE Office at Redstone Arsenal, AL, scheduled a Value Management Documentation Course for July 23rd – 25th (4 hours for 3 days) via TEAMS. This course provides a detailed description of the recommended Government-accepted forms of documentation that capture data from each phase of the Value Methodology Job Plan in a final package by working through project case studies. This course also provides a method to share verified estimated savings and proof of implementation.
To register for the course, reply to this email with your full name, the organization you work for, and the organization you support (if different). This course does not have a registration fee. Government civilian employees will receive 1 CLP for each hour completed, for a maximum of 12 CLPs. Participation by contractors is encouraged.
For organizations that have a training POC who distributes this type of information, please request to share through the organization’s training information distribution system. Also, please forward this email to any individual that may be interested in learning about documenting the Value Methodology.
Class dates/times by time zone:
July 23rd – 25th (4 hours for 3 days)
@ 0700-1100 PST
@ 0800-1200 MST
@ 0900-1300 CST
@ 1000-1400 EST
Course Instructors/Moderators:
Toni Hamilton-Datcher, CVS - DEVCOM AvMC VE Office
Sharon Aldijaili, VMA - SAIC Supporting DEVCOM AvMC VE Office
Leticia Williams - CECOM Value Engineering and LSS Project Lead
We look forward to your reply and please let us know if you have any questions.
V/r,
Sharon Aldijaili, VMA
SAIC, Supporting DEVCOM AvMC and AMC Value Engineering Offices
Redstone Arsenal, AL
+++++++++++++++++++++++++++++++++++++++++++++++++
UPDATE 7/17/24: https://www.dau.edu/sites/default/files/webform/documents/26531/VE%20Course%20Flyer_202407016.pdf
As part of the rollout of DoDI 4245.14, R&E is sponsoring a workshop to develop the OSD implementation strategy for the requirements of the updated DoDI and subsequent updated guidance in SD-24. The workshop will be hosted by USACE the week of 19 AUG 24 in Louisville, KY. Components are encouraged to send representation to participate in strategy development. POC for workshop attendance is Toni Hamilton [[email protected]].
Details:
Workshop will be held 19-23 August in Louisville, KY and hosted by the Army Corps of Engineers. Address for the facility is 4803 Olympia Park Plaza, Suite 1000, Louisville, KY 40241-3068. Seeking participants from the Components and Services to provide implementation considerations and develop a comprehensive strategy for DoDI and SD-24 rollout. Participation is needed for the full duration.
This workshop will also have a virtual participation option. Schedule will be 6 hours daily, roughly anticipated as 0900 to 1600 Eastern. Virtual platform to be provided by workshop facilitator.
**Please note that in person is advantageous to the student and their organization for the direct interaction it provides with inherent learning and retention benefits for many participants, however the remote option is available for this one-time opportunity for Value Engineering training.
+++++++++++++++++++++++++++++++++++++++++++++++
For more information: https://www.cto.mil/sea/ve/
Background:
As part of rolling out the updated DoD Instruction 4245.14: DoD Value Engineering (VE) Program, R&E is sponsoring a workshop to help OSD and Components develop their VE implementation strategy to incorporate the requirements of the refreshed DoDI 4245.14 and subsequent updated guidance in SD-24 VE: A Guidebook of Best Practices and Tools. The workshop will be hosted by USACE the week of August 19, 2024, 4803 Olympia Park Plaza, Suite 1000, Louisville, KY 40241-3068.
Components are encouraged to participate for the full duration of the workshop, which will also have a virtual participation option.* The workshop will run from 0900 to 1600 Eastern with a one-hour lunch break. The virtual platform will be provided by workshop facilitator.
*Please note that in-person attendance is recommended to fully benefit from the interactive workshop environment.
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:
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.
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)
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:
OUSD(R&E) HSI website:
What: Value Engineering Workshop--Implementation strategy for updated DoDI 4245.14 and SD-24 rollout
When: August 19–23, 2024
Where: Army of Corps of Engineers (USACE) facility, Louisville, KY
POC: Toni Hamilton, [email protected]
Who: DoD Component Participants
Value Engineering Workshop: Seeking DoD Component participants to provide implementation considerations and develop a comprehensive strategy for updated DoDI and SD-24 rollout.
Background:
As part of rolling out the updated DoD Instruction 4245.14: DoD Value Engineering (VE) Program, R&E is sponsoring a workshop to help OSD and Components develop their VE implementation strategy to incorporate the requirements of the refreshed DoDI 4245.14 and subsequent updated guidance in SD-24 VE: A Guidebook of Best Practices and Tools. The workshop will be hosted by USACE the week of August 19, 2024, 4803 Olympia Park Plaza, Suite 1000, Louisville, KY 40241-3068.
Components are encouraged to participate for the full duration of the workshop, which will also have a virtual participation option.* The workshop will run from 0900 to 1600 Eastern with a one-hour lunch break. The virtual platform will be provided by workshop facilitator.
*Please note that in-person attendance is recommended to fully benefit from the interactive workshop environment.
____________________________
VE Community of Practice webpage: https://www.dau.edu/cop/se/resources/value-engineering
Systems Engineering & Architecture VE webpage: https://www.cto.mil/sea/ve/
All,
The DEVCOM AvMC VE Office at Redstone Arsenal, AL, scheduled a Value Management Documentation Course for July 23rd – 25th (4 hours for 3 days) via TEAMS. This course provides a detailed description of the recommended Government-accepted forms of documentation that capture data from each phase of the Value Methodology Job Plan in a final package by working through project case studies. This course also provides a method to share verified estimated savings and proof of implementation.
To register for the course, reply to this email with your full name, the organization you work for, and the organization you support (if different). This course does not have a registration fee. Government civilian employees will receive 1 CLP for each hour completed, for a maximum of 12 CLPs. Participation by contractors is encouraged.
For organizations that have a training POC who distributes this type of information, please request to share through the organization’s training information distribution system. Also, please forward this email to any individual that may be interested in learning about documenting the Value Methodology.
Class dates/times by time zone:
July 23rd – 25th (4 hours for 3 days)
@ 0700-1100 PST
@ 0800-1200 MST
@ 0900-1300 CST
@ 1000-1400 EST
Course Instructors/Moderators:
Toni Hamilton-Datcher, CVS - DEVCOM AvMC VE Office
Sharon Aldijaili, VMA - SAIC Supporting DEVCOM AvMC VE Office
Leticia Williams - CECOM Value Engineering and LSS Project Lead
We look forward to your reply and please let us know if you have any questions.
V/r,
Sharon Aldijaili, VMA
SAIC, Supporting DEVCOM AvMC and AMC Value Engineering Offices
Redstone Arsenal, AL
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!!
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.
DoD Engineering Recruitment Tool (Brochure).pdf
This NASA policy directive, while short, provides a detailed discussion defining acceptable levels of mission success risk and crew safety levels for flight and is applicable to NASA HQ, NASA Centers, and their employees while expressing the importance of protecting all entities including terrestrial, orbital, and planetary environments from harm, and create a culture that understands risk, and safety. The directive is for use by the Administrator and goes through the process of identifying, accessing, managing, and accepting crew safety and mission safety and encouraging reporting without being held for misconduct.
The NASA Standard reviews safety for the handling and processing of explosives, propellants, and pyrotechnics by an individual. This standard is applicable to anyone that handles, stores, transports or encounters explosives or anything containing explosive materials. To ensure the safety of the system, and those handling and processing explosives need to understand and implement safety standards, procedures and requirements outlined in the NASA Standard. The Standard presents these as General and Detailed requirements.
https://standards.nasa.gov/sites/default/files/standards/A/0/nasa-std-871912a.pdf
The Federal Aviation Administration outlines and defines what SS is, a few key definitions, objectives, description, hazard identification, risk analysis, risk assessment and decision-making process, validation and control, system modifications (as needed). It should be noted that this document can be used as an outline or guide for the SS process but does not go into depth on the topics listed above.
https://www.faasafety.gov/gslac/alc/libview_normal.aspx?id=6877
This instruction’s main purpose is to ensure the safety of Air Force personnel and their assets. The US Air Force Mishap Prevention Program’s vision is that there will be compliance with all guidelines, risk reduction and continuous improvement.
https://static.e-publishing.af.mil/production/1/af_se/publication/dafi91-202/dafi91-202.pdf
The Risk Management Process Guide is designed to be utilized by program personnel assigned to each category in addition to the program risk manager. It is also important to remember that risk management is a job for everyone involved in the program including engineers, action officers, Program managers and everyone in-between, not only the individuals working on a specific aspect of the program.
This acquisition guidebook is meant to provide in detail the entire acquisition process and framework for the Navy which only mentions system safety once on p.6 when outlining preparation of program documents to include “system safety program to identify Environment, Safety, and Occupational Heath (ESOH) hazards”.
This manual’s purpose was to outline how SSE should be integrated into each system throughout their lifecycle. The manual does so by incorporating numerous guidance documents, which should be used from the beginning of a system’s lifecycle through disposal, into one manual for NAVSEA and other appropriate offices/departments on the policies that involve SSE such as ESOH, and risk management.
https://community.apan.org/wg/usdre/se-a/specengr/sse/m/documents/471981
This instruction is used to outline how to develop a System Safety Program, review policy for NAVSEA, PEOs, CHENG, PM, Principal for Safety (PFS) and other program personnel to ensure fielded systems are safe and following current applicable guidance while implementing & integrating SSE into all phases of the system lifecycle.
https://www.navsea.navy.mil/Portals/103/Documents/NAVINST/05100.021B.pdf
This instruction describes the Navy-wide use of operational risk management (ORM). The ORM process includes identifying hazards, assessing hazards, making risk decisions, implementing controls, and supervising.
This policy supersedes NAVAIRINST 5000.21A and must be reviewed annually, making changes as needed. The beginning ensures that this policy is compliant with other risk management requirements and begins explaining the circumstances of various terms relating to risk management. The following section delineates actions taken by PEO and systems command (SYSCOM) Commanders, PMs, Risk Management Boards (RMB), IPTs, Technical Authorities. and their responsibilities in the risk management process.
The PEO Theater Surface Combatant (TSC)’s Risk Management Instruction focuses on defining risk, risk management, PEO TSC Risk Management Program, risk identification, risk characterization and assessment, risk analysis and mitigation, risk tracking and reporting, likelihood of occurrence, consequences of risk, product programs, and mission programs. The procedures concentrate on reporting risk tracking and board membership requirements, which require a government member at a minimum, a representative from ASN (RDA), Chief Engineer (CHENG), and a representative from Defense Systems Management College (DSMC).
This manual briefly discusses system safety and risk throughout the entire document but also has Chapter 38 completely dedicated to System Safety. Chapter 38 is broken up into four categories: Discussion and Background, Highlights of System Safety Program, System Safety Working Groups (SSWG)/ Facility System Safety Working Groups (FSSWG). The SS program can help prevent injury, death, illness of personnel while also protecting the systems from adversaries and destruction to ensure a safe and successful mission.
https://www.secnav.navy.mil/doni/SECNAV%20Manuals1/5100.23%20CH-2.pdf
The CDC uses this document to convey their approach for hazard identification and risk analysis. As previously mentioned in MIL-STD-882E (2012) risk is determined as a function of the probability that a mishap will occur and (should a mishap occur) the impact (in terms of severity level) the mishap would have on system sustainability, survivability, and performance. The guide has 16 lessons beginning with an introduction to SS through various methods of accessing risk utilizing fault, success and even tree analysis, block diagrams, risk assessment matrix, cause-consequence analysis, failure analysis, reliability block diagrams etc. Each section outlines the purpose, description, application, procedures, samples including advantages and limitations of each method that can be used to determine and assess risks and hazards for management to be able to determine if the risk needs to be mitigated or accepted.
This Army regulation recently underwent a major revision, including a title change from the previous title of “The Army Safety Program”. The document reviews the specific responsibilities of from the Secretary of the Army establishing and implementing requirements down to the material developers, acquisition managers, and equipment, process, and facility designers and their contract responsibilities.
https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN34981-AR_385-10-000-WEB-1.pdf
This guide consists of eight chapters that include discussions on system safety management, risk and hazards management, integration of system safety associated disciplines, SS for testers and evaluators, weapon SS reviews, facility SS, facility SS program management, and facility SS program contracting.
https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN30886-PAM_385-16-000-WEB-1.pdf
This Army Pamphlet, while acquisition focused, is being included in this BoK because it discusses SS throughout multiple sections. SS is first discussed in Section 5 entitled, “Manpower and Personnel Integration/Human Systems Integration”. Under “Manpower and personnel integration considerations” SS is called out to be addressed by MATDEV’s strategy for HSI. Further mentioning of SS provides emphasis on early integration in the acquisition lifecycle.
SS programs will be developed based upon the risk management requirements and document risks by identifying, tracking, managing and mitigating hazards in the Human Systems Integration Plan (HSIP).
https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN11426_DAPam70-3_FINAL.pdf
This instruction is brief, but applies to all weapon and laser systems, except for medical and industrial, legacy systems and joint legacy systems.
JSSSEH is a handbook that is meant to clarify activities such as, design, code, test, independent verification, and validation (IV&V), operation and maintenance, and change control functions within the software engineering development and deployment processes (p.1).
https://ac.cto.mil/wp-content/uploads/2019/06/Joint-SW-Systems-Safety-Engineering-Handbook.pdf
The Risk Management Guide, which is utilized primarily by the PM, goes further in depth into the common sources of risk, how to identify and analyze risk, implement mitigation strategies and tracking than MIL-STD-882E.
This military standard outlines and defines the general requirements for system safety (SS) processes, approaches, and risks.
https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=36027
The guide goes over the three safety precepts that are necessary for unmanned systems, programmatic safety precept (PSP), operational safety precept (OSP), and design safety precept (DSP).
https://www.cto.mil/wp-content/uploads/2023/06/UxS-Precepts-2021.pdf
Systems Engineering Planning
|
|
|
Systems Engineering Processes
|
|
Technical Management ProcessesTechnical management processes are applicable to all acquisition pathways, providing a consistent framework for managing technical activities, as well as 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. |
|
Technical ProcessesTechnical processes ensure the system design and the delivered capability reflect the requirements that the stakeholders have expressed. |
Value engineering (VE) plays an integral and enduring role in accomplishing DoD's mission to provide the military forces needed to deter war and protect the security of our nation. DoD Instruction 4245.14, "DoD Value Engineering (VE) Program," implements 41 USC 1711, "Value Engineering," and Office of Management and Budget Circular No. A-131, "Value Engineering," to ensure the "effective administration of the DoD VE Program."
FAR Part 48, "Value Engineering," "prescribes policies and procedures for using and administering value engineering techniques in contracts."
Value Engineering (VE) is an organized, systematic technique that analyzes the functions of systems, equipment, facilities, services, and supplies to ensure they achieve their essential functions at the lowest life-cycle cost consistent with required performance, reliability, quality, and safety.
The DoD VE program has two elements:
Components retain DoD resource benefits resulting from the use of VE. For those that want to reach out to the broader Value Engineering community and potential commercial certification, see: https://www.value-eng.org/
For additional information on value engineering tools see the Systems Engineering Guidebook, Section 2.2.7. Value Engineering. This sub-topical area contains information on the use of value engineering in DoD acquisitions.
UPCOMING EVENTS
DEVCOM AvMC Value Management Documentation Course scheduled for July 23-25, 2024
All,
The DEVCOM AvMC VE Office at Redstone Arsenal, AL, scheduled a Value Management Documentation Course for July 23rd – 25th (4 hours for 3 days) via TEAMS. This course provides a detailed description of the recommended Government-accepted forms of documentation that capture data from each phase of the Value Methodology Job Plan in a final package by working through project case studies. This course also provides a method to share verified estimated savings and proof of implementation.
To register for the course, reply to this email with your full name, the organization you work for, and the organization you support (if different). This course does not have a registration fee. Government civilian employees will receive 1 CLP for each hour completed, for a maximum of 12 CLPs. Participation by contractors is encouraged.
For organizations that have a training POC who distributes this type of information, please request to share through the organization’s training information distribution system. Also, please forward this email to any individual that may be interested in learning about documenting the Value Methodology.
Class dates/times by time zone:
July 23rd – 25th (4 hours for 3 days)
@ 0700-1100 PST
@ 0800-1200 MST
@ 0900-1300 CST
@ 1000-1400 EST
Course Instructors/Moderators:
Toni Hamilton-Datcher, CVS - DEVCOM AvMC VE Office
Sharon Aldijaili, VMA - SAIC Supporting DEVCOM AvMC VE Office
Leticia Williams - CECOM Value Engineering and LSS Project Lead
We look forward to your reply and please let us know if you have any questions.
V/r,
Sharon Aldijaili, VMA
SAIC, Supporting DEVCOM AvMC and AMC Value Engineering Offices
Redstone Arsenal, AL
+++++++++++++++++++++++++++++++++++++++++++++++++
UPDATE 7/17/24: https://www.dau.edu/sites/default/files/webform/documents/26531/VE%20Course%20Flyer_202407016.pdf
As part of the rollout of DoDI 4245.14, R&E is sponsoring a workshop to develop the OSD implementation strategy for the requirements of the updated DoDI and subsequent updated guidance in SD-24. The workshop will be hosted by USACE the week of 19 AUG 24 in Louisville, KY. Components are encouraged to send representation to participate in strategy development. POC for workshop attendance is Toni Hamilton [[email protected]].
Details:
Workshop will be held 19-23 August in Louisville, KY and hosted by the Army Corps of Engineers. Address for the facility is 4803 Olympia Park Plaza, Suite 1000, Louisville, KY 40241-3068. Seeking participants from the Components and Services to provide implementation considerations and develop a comprehensive strategy for DoDI and SD-24 rollout. Participation is needed for the full duration.
This workshop will also have a virtual participation option. Schedule will be 6 hours daily, roughly anticipated as 0900 to 1600 Eastern. Virtual platform to be provided by workshop facilitator.
**Please note that in person is advantageous to the student and their organization for the direct interaction it provides with inherent learning and retention benefits for many participants, however the remote option is available for this one-time opportunity for Value Engineering training.
+++++++++++++++++++++++++++++++++++++++++++++++
For more information: https://www.cto.mil/sea/ve/
Policy, guidance, and workforce development initiatives for the DoD engineering and technical workforce.
The Engineering and Technical Management (ETM) workforce has a vital role in developing, fielding, and sustaining high-quality, innovative, affordable, supportable, and effective defense systems and ensuring that DoD products are delivered on time, perform as expected, and are cost-effective. Learn more about training and events at https://www.dau.edu/functional-areas/engineering-and-technical-management.
The T&E workforce is responsible for, or is an integral part of, the conceptualization, initiation, design, development, contracting, testing, and evaluation of defense systems across all commodity areas. Learn more about training and events at https://www.dau.edu/functional-areas/test-and-evaluation.
The OUSD(R&E) partners with the Military Services and defense agencies to ensure the ETM and T&E acquisition workforces are certified, current, qualified, and have the capability and capacity to meet current and future leadership priorities. Refer to the ETM and T&E information sheets at https://www.cto.mil/sea/info-sheets/ to see a summary of how those efforts help these workforces’ meet challenges in the era of competition.
Workforce – DoD Research & Engineering, OUSD(R&E) (cto.mil)
Policy and guidance and best practices to encourage the use of systems engineering, other engineering disciplines, and standards and specifications for the engineering of defense systems.
The OUSD(R&E) developed and disseminated various policy and guidance and best practices located at Policy and Guidance.
Additionally, check out the DoD Instruction 5000.97, Digital Engineering information sheet at https://www.cto.mil/sea/info-sheets/ for a summary on how the instruction establishes policy, assigns responsibilities, and provides procedures for implementing and using digital engineering in the development and sustainment of systems.
Policy and Workforce is responsible for developing Systems Engineering policy and guidance and disseminating best practices. The following websites provides links to DoD policy and guidance related to defense acquisition systems engineering.
The impact of specialty engineering activities on total system cost, schedule, and performance will determine the extent of their application during the system design process. Execution of activities in specialty engineering will, to the largest extent practicable, use information from, and contribute to, the digital authoritative source of truth. (DoDI 5000.88). Specialty Engineering emphasizes improving delivery of advanced capability to warfighters by modernizing reliability and maintainability, manufacturing and quality, system safety, human systems integration, and value engineering practices.
The PM, Systems Engineer, and Lead Software Engineer should address and document design considerations, including all statutory and regulatory requirements in order to:
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.
Identifies, develops, manages, and provides access to standardization processes and products for the defense community to promote interoperability, reduce cost, and sustain readiness.
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.
Background:
As part of rolling out the updated DoD Instruction 4245.14: DoD Value Engineering (VE) Program, R&E is sponsoring a workshop to help OSD and Components develop their VE implementation strategy to incorporate the requirements of the refreshed DoDI 4245.14 and subsequent updated guidance in SD-24 VE: A Guidebook of Best Practices and Tools. The workshop will be hosted by USACE the week of August 19, 2024, 4803 Olympia Park Plaza, Suite 1000, Louisville, KY 40241-3068.
Components are encouraged to participate for the full duration of the workshop, which will also have a virtual participation option.* The workshop will run from 0900 to 1600 Eastern with a one-hour lunch break. The virtual platform will be provided by workshop facilitator.
*Please note that in-person attendance is recommended to fully benefit from the interactive workshop environment.
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 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 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.
To establish policy and assign responsibilities for a standardized risk management process across all Naval Systems Commands (SYSCOMs) and affiliated Program Executive Officers (PEOs).
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
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." .