Systems Engineering Management Plan - Model Text

Title pages

The title page shall be laid out in accordance with the requirement in the documentation standard and contain the following information:

• SYSTEMS ENGINEERING MANAGEMENT PLAN FOR THE name of project.;
• Document identifier including issue;
• Date the document was formally approved;
• The organization responsible for 'preparing' the document;
• The organization requiring the document preparation;
• A distribution statement;
• Total number of pages comprising the document;
• Any classification necessary.

FOREWORD

• This plan is applicable to the name of the project (program) to identify and define the organization(s), activities, overall tasks, principles, and objectives of Systems Engineering Management required to manage and control the design, development, production, and maintenance of the project.
  
• Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be sent to; name of organization controlling this document by any approved communication method (letter, fax, etc.).
  
• This document is intended to be tailored to fit the specific project SOW and used by both the acquirer and design authority for the identified project.
  
• The primary objectives of this document are:
  • To provide modern, state-of-the-art, project management requirements for the design, development, evaluation, production, evaluation, and maintenance of technical systems;
  • To limit and reduce the proliferation of management documentation and to implement relevant aspects of international standards;
  • To provide a coherent view in pursuance of joint international requirements;
  • identify relevant directives and references;
  • To establish a relationship with international standardization specifications;
  • To provide evidence that control over the design, development, production, installation and support and that inspections which demonstrate acceptability of materiel and services will be performed;
  • To provide emphasis on a disciplined integrated systems development approach;
  • To acquaint newcomers with the concepts of systems engineering management and techniques.
• To provide visibility and communication of Engineering Management. It is crucial that in design and development that questions should be asked and answers given; only in this way is it possible to integrate complex systems, to feedback information on past mistakes and successes and feedforward problems for which timely solutions must be found.
• The scope and depth of the specific tasks chosen for application shall be consistent with the needs of the specific program (project). The need to correctly identify only the required tasks to suit the specific project cannot be overstated prior to contract negotiations. If any tasks are determined "not applicable" the paragraph shall be identified as "not applicable".
  

CONTENTS

• Foreword
  Contents
  1. SCOPE
  2. APPLICABLE DOCUMENTS
  3. TECHNICAL PROGRAM PLANNING AND CONTROL
  4. SYSTEMS ENGINEERING PROCESS
  5. ENGINEERING SPECIALTY INTEGRATION
  6. NOTES
  

1. SCOPE

The scope shall identify the specific program or project, state the purpose and provide an introduction and summary of the document.

For example Section 1 see SEMP section 1

2. APPLICABLE DOCUMENTS

This section shall identify all the applicable and referenced documents which are required for the specific program or project.
Also, the order of precedence and availability of the documents shall be stated.
Identify any contractual and non-contractual provisions.

For example Section 2 see SEMP section 2

3. TECHNICAL PROGRAM PLANNING AND CONTROL

Technical program planning and control identifies organizational responsibilities and authority for system engineering management, including control of subcontracted engineering:

• levels of control established for performance and design requirements and control of the method used;
• technical program assurance methods;
• plans and schedules for design and technical program reviews;
• control of documentation;
• design approval and certification;
• CALS transfer of information from paper to electronic media.

For an example Section 3 see SEMP section 3

4. SYSTEM ENGINEERING PROCESS

This section contains a detailed description of the process to be used, including the specific tailoring of the process to the requirements of the system and project:

1. the procedures to be used in implementing the process;
2. in-house documentation;
3. the trade study methodology;
4. the types of mathematical and/or simulation models to be used for system and cost effectiveness evaluations;
5. and the generation of specifications.

For an example Section 4 see SEMP section 4

5. ENGINEERING SPECIALTY INTEGRATION

The integration and coordination of the program efforts for engineering specialty areas, to achieve a best mix of the technical/performance values incorporated in the contract, shall be described with the detailed specialty program (project) plans being summarized and/or referenced, as appropriate.
The specialty efforts and parameters will be integrated into the system engineering process at each iteration. The process will be described and considerations taken defined.

For an example Section 5 see SEMP section 5

6. NOTES

The section 'NOTES' shall contain information of a general or explanatory nature that may be helpful, but is not mandatory.
Notes generally contain lists of abbreviations and acronyms, definitions of special terms used, intended use, etc.

For an example Section 6 see SEMP section 6 .

An example SEMP is provided in the "Technical Management - a pragmatic approach".

Documents are available in .pdf format: See PDFDOCUMENTS.

Back to Home page MANAGING STANDARDS Home page

Back to start of this page Click here

Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk