SEMP, TEMP and SHMEMP - Its time to stop the Mishigas

Sep 12, 2026

Upload by Skyler

A systems engineering management perspective explains how SEMP, TEMP, and SHMEMP function within the system development lifecycle and why fragmented planning across disciplines creates recurring mismatches. The discussion frames the context as a problem of poor subsystem partitioning and inconsistent terminology across postgraduate courses. It outlines systems thinking perspectives, details what a SEMP should contain, and links it to program planning, control, process tailoring, specialty integration, and trade-off guidance to reduce the “Mishigas” effect.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages44

Reading Time15 min

AccessFree to download

Topics

The context

Systems engineering

The SEMP

The TEMP

The SHMEMP

The Mishigas

How we might stop the Mishigas

Recommendations

Further information

Systems engineering management plan (SEMP)

Contents of the SEMP

Contents of the SEMP-1

Contents of the SEMP-2

Appendices in Florida SEMP

0703 8/03/2021 SEMP, TEMP and SHMEMP! Its time to stop the Mishigas Dr Joseph Kasser 1 Joseph Kasser 􀀁 The real world 􀀁 Electronic engineer, London, UK 􀀁 ALSEP, Apollo’s 15,16 & 17, USA 􀀁 Systems engineer 􀀁 TT&C, Comsat 􀀁 LuZ SEGS-1, Israel 􀀁 NASA-GSFC ground support 􀀁 The Right Requirement Ltd 􀀁 Academia 􀀁 GWU, UMUC 􀀁 Ass/Prof, Deputy Director, UniSA 􀀁 Leverhulme Visiting Professor, Cranfield, UK 􀀁 NUS Visiting Associate Professor 2 0703 8/03/2021 Topics 􀀁 The context 􀀁 Systems engineering 􀀁 The SEMP 􀀁 The TEMP 􀀁 The SHMEMP 􀀁 The Mishigas 􀀁 How we might stop the Mishigas 􀀁 Recommendations 􀀁 Further information 3 Context – problem 􀀁 Creating postgraduate courses in 􀀁 Systems engineering 􀀁 Project management 􀀁 Integrated logistics support 􀀁 Innovation and technology management 􀀁 Knowledge content 􀀁 Same knowledge in different courses 􀀁 Poor subsystem partitioning 􀀁 Different terminology for same concepts in different courses 􀀁 Difficulty of ‘independence’ 􀀁 Things not taught that should be 4 Perspectives of a problem-1 5 Perspectives of a problem-1a 6 0703 8/03/2021 | Perspectives of a problem-2
External

| 7 | | --- | --- | Systems thinking perspectives * 1. Big picture 2. Operational 3. Functional 4. Structural 5. Generic 6. Continuum 7. Temporal 8. Quantitative 9. Scientific *Kasser and Mackley, INCOSE, 2008 8 0703 8/03/2021 Systems thinking perspectives * 1. Big picture 2. Operational 3. Functional 4. Structural 5. Generic 6. Continuum 7. Temporal 8. Quantitative 9. Scientific *Kasser and Mackley, INCOSE, 2008 9 Systems engineering: Big picture observations-1 􀀁 The recommended way to solve the complex problems facing us today 􀀁 Aspects of success and failure discussed last year 􀀁 The forthcoming Seldon crisis in systems engineering 􀀁 Multiple definitions of systems engineering 􀀁 DAU’s two faces of systems engineering* 􀀁 Technical domain-processes 􀀁 Systems Engineering Management 􀀁 Overlap with Project Management 10 Systems Engineering Fundamentals. Defense Acquisition University Press, 2001 0703 8/03/2021 Systems engineering: Big picture observations-2 􀀁 A holistic approach (theory) 􀀁 Performed in a fragmented environment (practice) 􀀁 Fragmented by discipline 􀀁 Different disciplines perform overlapping work 􀀁 Legislated to do so in USA 􀀁 e.g. engineering specialties 11 Topics 􀀁 The context 􀀁 Systems engineering 􀀁 The SEMP 􀀁 The TEMP 􀀁 The SHMEMP 􀀁 The Mishigas 􀀁 How we might stop the Mishigas 􀀁 Recommendations 􀀁 Further information 12 0703 8/03/2021 The systems engineering management plan (SEMP) 􀀁 One of the critical documents in the system development lifecycle 􀀁 Produced by systems engineers 􀀁 In general, 􀀁 we don’t teach planning in SE courses 􀀁 we teach planning in Project Management 􀀁 When do they produce it? 􀀁 When do they use it? 􀀁 Who uses it? 13 The context for the SEMP: Big picture perspective * * Kasser, J. E., "The Hitchins-Kasser-Massie (HKM) Framework for Systems Engineering ", Proceedings of the 17th International Symposium of the INCOSE, San Diego, CA., 2007. 14 0703 8/03/2021 Internal perspective: Contents of the SEMP * 􀀁 Technical Program Planning and Control 􀀁 Systems Engineering Process 􀀁 Engineering Specialty Integration *Kasser J.E., Schermerhorn R.,“Gaining the Competitive Edge through Effective Systems Engineering", Proceedings of the NCOSE 4th International Symposium, San Jose , CA., 1994. 15 Contents of the SEMP-1 􀀁 Technical Program Planning and Control 􀀁 identifies organizational responsibilities and authority for systems engineering management 􀀁 describes the method of controlling the program, subcontracted engineering, and schedules 􀀁 contains 􀀁 the contract work breakdown structure (WBS) 􀀁 th

FAQs

What role does the SEMP play in the system development lifecycle?

The SEMP is described as one of the critical documents in the system development lifecycle, produced by systems engineers to guide planning, control, and related activities.

Why is subsystem partitioning and terminology consistency important in systems engineering education?

The document highlights that poor subsystem partitioning and different terminology for the same concepts across courses create difficulties, weakening independence and reuse of knowledge.

What does the SEMP include regarding program planning and control?

It identifies organizational responsibilities and authority, describes how the program and subcontracted engineering are controlled, and covers items such as the contract WBS, specification tree, risk analysis, test planning, decision/control processes, and technical performance measurements.

Sep 12, 2026

Upload by Skyler