This example Section 3 of the SEMP identifies specific tasks which may be selected by the SOW to fit the program needs. The scope and depth of the specified tasks chosen for application shall be consistent with the needs of the project or program. The intention is to enable adjustments to specific program (project) needs and subsequent contact negotiations.
NOTE: If paragraphs are to be determined not applicable then state "not applicable" directly after the paragraph heading.
Systems Engineering Management is defined as part of the Engineering Management System and shall operate on conceptual levels from the managing agency, prime contractor to the suppliers.
The Systems engineering management process group shall be responsible for the preparation and maintenance of the overall project plans, standards, and procedures as defined within a SOW in accordance with the contracted design requirements specification.
A more detailed description will be provided by SEMP 3.1 Organisation.
The purpose of the SEMP is to establish, identify, and define tasks required to progress the operational need from concept to the deployment of the specific system.
Design authorities or coordinating design authorities for the system, subsystem, or equipment shall be responsible for the preparation and maintenance of the specific design data.
A more detailed description will be provided by SEMP 3.2 Purpose and activities.
The SEMP shall be applicable throughout all the stages and phases of the system life cycle starting with the Concept Exploration phase. The SEMP shall establish and document the process by which the system is managed from concept to deployment.
A more detailed description will be provided by SEMP 3.3 Objectives.
The technical elements of the CWBS/SOW shall be developed initially with a preliminary contract CWBS leading to refinements and eventually a final CWBS and specification tree.
A more detailed description will be provided by SEMP 3.4 CWBS and specification tree.
The program definition and re-definition effort shall include a continuing analysis of the risks associated with the related cost, schedule, and technical parameters.
A more detailed description will be provided by SEMP 3.5 Risk analysis.
The objectives, scope, and type of system testing shall be the products of the engineering effort wherein all engineering specialities are integrated to define an effective and economical total system test program.
Whenever practicable, tests for different objectives shall be combined.
A Testability Program Plan shall be established early in the program to identify and integrate all testability and test design management tasks, when applicable.
A more detailed description will be provided by SEMP 3.6 System Test Planning.
Technical, budgetary, and scheduling problems shall be diagnosed as early as possible to determine their impact.
A more detailed description will be provided by SEMP 3.7 Decision and control processes.
The specific technical performance management effort shall be tailored to meet the program (project) needs and shall be planned and executed.
The technical performance parameters selected for tracking shall be key indicators of program success, with each parameter identified shall be correlated within a specific CWBS/SOW element.
A more detailed description will be provided by SEMP 3.8 Technical performance management.
Formal technical reviews shall be conducted in accordance with MIL-STD-1521 general and detailed requirements to assess the degree of completion of technical efforts related to major milestones before proceeding with further technical effort.
A more detailed description will be provided by SEMP 3.9 Formal technical reviews.
Any subsystems, LRUs, HWCIs or CSCIs being produced or developed by suppliers/subcontractors shall be formally reviewed when applicable to the same requirements contained in 3.9.
A more detailed description will be provided by SEMP 3.10 Supplier reviews.
Organizational elements responsible for the technical program effort shall be identified and lines of communication defined for control of resources and accomplishment of specific elements of the CWBS/SOW.
Detailed work authorization (work orders/directives) shall be compatible with the cost/schedule control system and shall include technical measures of task accomplishment.
A more detailed description will be provided by SEMP 3.11 Work authorisation.
Documentation prepared during the system evolution and development shall be held and change controlled by the Technical Authority areas where they are prepared and shall be identified and controlled in a similar manner to Engineering Drawings and in accordance with ISO/AQAP control system requirements.
A more detailed description will be provided by SEMP 3.12 Documentation control.
Certification of design shall be required to identify the extent to which the requirements of the system/subsystem specification have been achieved in accordance with contractual requirements.
A more detailed description will be provided by SEMP 3.13 Approval procedure.
CALS initiative is to enable more effective generation, exchange, management and the integration of digital technical information for system acquisition, design, manufacture, and support.
A more detailed description will be provided by SEMP 3.14 CALS
Back to Home page MANAGING STANDARDS Home page
Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk