Table of Contents | Appendix C-12 | Appendix C-14



The following sections should be considered for inclusion in the SEMP. Additionally, if both a government and a contractor SEMP are needed, the contents should be coordinated and integrated such that the technical management plans for the project are unambiguous to all concerned.

1.0      Introduction.

This section identifies the project, the applicable organization (contractor, government, or both), the date approved, and the revision version. If applicable, the title page should show an internal document control number.

1.1      Executive Summary.

This section describes the technical plan summary and applicability. If applicable, it also lists major subordinate plans.

1.2      Table of Contents.

1.3      Project Summary.

Briefly describe the project, to include complexities and challenges that are addressed by the technical development effort.

1.4      Scope.

Describe the applicability of the SEMP and assign general responsibilities for the required activities shown in the SEMP.

1.5      Applicable Documents.

List by title, version number, and issue date applicable documents to the technical management efforts described in the SEMP.

2.0      System Engineering Process.

This section describes the system engineering process to be applied to the project and assigns specific organizational responsibilities for the technical effort, to include contracted or subcontracted technical tasks. This section also details or references technical processes and procedures to be applied to the effort. Where these processes or procedures are developed as part of the project, the need dates and development schedule should be shown.

2.1       Systems engineering process planning.

This section addresses planning for the key system outputs, to include products, processes, and trained people. The following may be included in this section:

-- Major products. Include major specification and product baseline development
    and control

-- System engineering process inputs. Include major requirements documents and
    resolution instructions for conflicting requirements

-- Technical objectives. Include cost, schedule, and key performance objectives

-- Technical work breakdown structure. Describe how and when the technical work
    breakdown structure will be developed, to include development and tracking tool
    sets usage

-- Subcontracted technical efforts. Describe the integration of contracted and
    subcontracted technical efforts

-- Processes. Describe the use of established technical processes and standards on
    the project

-- Process development. Describe processes to be developed as part of the project,
    together with the schedule for their development

-- Constraints. List any significant constraint to the technical effort

2.2      Requirements Analysis.

This section describes the methods, procedures, and tools used to analyze project requirements. This section should specify specific tools to be used to capture and trace project requirements.

2.3      Functional analysis/allocation.

This section addresses the methods and tools used analyze the project requirements and allocate them down into project component functional requirements.

2.4      Synthesis.

This section addresses the methods and tools used to analyze the functional requirements and allocate those requirements to a physical project component.

2.5      System Analysis.

This section describes the processes and procedures to be used for formal and informal trade studies, to include system and cost-benefit effectiveness analyses. Also included in this section are the risk management approaches to be used on the project.

2.6      System Control.

This section describes the control strategies needed for the following:

-- Configuration management

-- Data management

-- Technical performance measurement

-- Quality control

-- Interface management

-- Schedule tracking and control

-- Formal technical reviews

-- Informal technical reviews/interchanges

-- Subcontractor/supplier control

-- Requirements control

3.0      Technology Refreshment.

This section describes the plans to establish and maintain a viable technological baseline during project development. This section also describes the strategy to be used during development to ensure refreshment remains a viable option during future project operations.

4.0      Implementation Planning.

This section outlines the planned activities leading to project implementation. Included in this area may be plans for:

-- Test and evaluation

-- Transition of technical baselines to operations and maintenance

-- Supportability planning

-- Facilities planning

-- Operations and user training development

-- Project integration into an existing system-of-systems architecture

5.0      Specialty Engineering Planning.

This section outlines any special subject applicable to the project not covered in a previous section.


Cover Page
Table of Contents

            1.1        Executive Summary
            1.2        Project Summary
            1.3        Scope
            1.4        Applicable Documents

            2.1        Systems Engineering Process Planning
            2.2        Requirements Analysis
            2.3        Functional Analysis/Allocation
            2.4        Synthesis
            2.5        Systems Analysis
            2.6        Systems Control




Table of Contents | Appendix C-12 | Appendix C-14