Difference between revisions of "Systems Engineering Plan (SEP) (glossary)"

From SEBoK
Jump to navigation Jump to search
(Created page with '''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow ...')
 
(23 intermediate revisions by 7 users not shown)
Line 1: Line 1:
''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow to manage program risks and meet program objectives. The Acquisition Strategy should define the relationship between the acquisition phases and work efforts, and key program events such as decision points, reviews, contract awards, test activities, production lot/delivery quantities, and operational deployment objectives. (DAU February 19, 2010)</blockquote>''
+
''<blockquote>A systems engineering plan (SEP) is a "living" document that captures a program's current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP purpose is to guide all technical aspects of the program. It should be established early in the Materiel Solution Analysis phase and updated continually.'' (DAU 2012)</blockquote>
  
====Source====
+
===Source===
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
+
DAU 2012. "Systems Engineering Plan (SEP)." (online). Virginia, USA: ACQuipedia. Your Online Acquisition Encyclopedia. Accessed on 20 October 2019. Available at: https://www.dau.edu/acquipedia/pages/articledetails.aspx#!206.
  
 
===Discussion===
 
===Discussion===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
In many contexts, the Systems Engineering Plan (SEP) and Systems Engineering Management Plan (SEMP) are used interchangeably, to refer to the highest level technical plan. However, in the context of the U.S. Department of Defense the context, intent, and content of these documents are quite different:
 +
* The SEP is a high-level plan that is made before the system acquisition and development begins. It is written by the government customer.
 +
*The SEMP is the specific development plan written by the developer (or contractor).
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
<center>'''SEBoK v. 2.4, released 19 May 2021'''</center>

Revision as of 02:47, 20 May 2021

A systems engineering plan (SEP) is a "living" document that captures a program's current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP purpose is to guide all technical aspects of the program. It should be established early in the Materiel Solution Analysis phase and updated continually. (DAU 2012)

Source

DAU 2012. "Systems Engineering Plan (SEP)." (online). Virginia, USA: ACQuipedia. Your Online Acquisition Encyclopedia. Accessed on 20 October 2019. Available at: https://www.dau.edu/acquipedia/pages/articledetails.aspx#!206.

Discussion

In many contexts, the Systems Engineering Plan (SEP) and Systems Engineering Management Plan (SEMP) are used interchangeably, to refer to the highest level technical plan. However, in the context of the U.S. Department of Defense the context, intent, and content of these documents are quite different:

  • The SEP is a high-level plan that is made before the system acquisition and development begins. It is written by the government customer.
  • The SEMP is the specific development plan written by the developer (or contractor).
SEBoK v. 2.4, released 19 May 2021