6.4.0 System Engineering Management Plan (SEMP): DOES ONE SIZE FIT ALL?

Abstract

AbstractOne of the managerial and professional tools of the systems engineers in a project is the Systems Engineering Management Plan (SEMP). According to the INCOSE Systems Engineering Handbook, the SEMP is the top‐level plan for managing the Systems Engineering effort. The SEMP defines how the project will be organized, structured, and conducted and how the total engineering process will be controlled to provide a system that meets stakeholder requirements. The Handbook guides projects to tailor the SEMP to fit project, customer, or company standards.There are several procedures and templates for the SEMP. But in many organizations, companies and projects we find SEMPs that are not tailored for the project needs and goals and are not presenting specific and effective SE efforts to cope with the real project risks. It appears that many organizations believe that one SEMP size fits all projects, and work effectively from that belief. This panel will discuss the application and tailoring of the SEMP to different domains; how to make it effective. In particular, the panel will consider the following questions and dilemmas: How is the SEMP different than the actual planning? What are the special characteristics of a SEMP for developing: Complex Systems? Systems with high Technology Uncertainty? Systems with high Novelty and Innovation? Systems at a fast pace, or for Agile development? How to integrate effectively the SEMP into the project and system development planning and execution? How to integrate effectively the SEMP into evolutionary processes? How to deal with the most important requirement‐time? Can an effective SEMP contribute to the success of the project?