Systems Engineering Management Plan
Section 3.2 - Model Text

3.2 Purpose and activities.

The purpose of this SEMP is to identify and define tasks required to progress the operational need from concept to the deployment and operation of the System.

Systems Engineering Management is a discipline to ensure the proper control of design, development, test, and evaluation tasks required to progress from an operational need to the deployment and operation of the system by the user.

Systems Engineering Management defines what is required, designed and produced, evaluating changes including effects on technical and operational performance and logistic support activities.

Engineering Management is the management of the engineering and technical effort required to transform a technical requirement into an operational system.*

3.2.1 Responsibilities for design and development.

3.2.1.1 System design authority.

• The Design Authority (DA) or a coordinating Design Authority (CDA) for a system or equipment shall be responsible for the preparation and maintenance of the system and subsystem design data. The responsibility to the acquirer or his agency shall include:
  
  • design of the materiel, including all necessary development and testing, to the requirements of the contractual specification;
  • preparation, updating and custody of specifications, drawings, and other data associated with the design of the materiel;
  • submission of reports, as required, on the progress of the work;
  • preparing an appropriate certificate of design and its submission for acceptance;
  • ensuring that the design shall be suitable for production in proposed facilities;
  • design of packaging as required for the materiel;
  • preparation of, or supply of information for, the necessary technical documentation and publications;
  • collaboration with users and agencies in the preparation and provision of information for maintenance of the materiel;
  • post design services.
    
• The System Design Authority shall be responsible for his suppliers work. Nomination of a supplier as a DA does not relieve the developer of his responsibilities.
  Arrangements shall be made to ensure that the applicable policies and procedures contained within this plan are followed.
  In particular, the developer shall:
  

• provide and maintain adequate specifications for sub-contracted materiel, delegate authority as appropriate for the detailed design of the materiel, and agree the arrangements for preparation, updating and custody of drawings and other design records, and for design acceptance;
• satisfy himself that the design and testing of sub-contracted materiel are adequate for the proposed application;
• obtain from suppliers nominated as design authorities a certificate of design that the materiel complies with the specification, and confirm in writing to the suppliers his acceptance of the certification.

3.2.1.2 Design records.

• Design records shall be prepared to define the standard of design of materiel being acquired.
  Design records shall consist of all the technical information necessary to define the design, manufacture, packaging, testing, installation, and maintenance of the system.
  The following provides an example of some or all of the design records:
  1. specifications;
  2. drawings;
  3. change proposals/requests;
  4. amendment/modification sheets;
  5. an index (software and hardware);
  6. delivery information.
     

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