System Engineering Management Plan
Section 5 - Model Text
Foreword .
This
example Section 5 of the SEMP shall describe the integration of the specialty
program plans to attain the best mix of technical and performance values into
the Project Management System.
All specialty programs plans identified by the Statement of
Work (SOW) shall depict the integration of specialty efforts and parameters
into the system engineering process and show their consideration of the
process.
When the specialty programs overlap, the SEMP shall define the responsibilities
and authorities of each.
The
following identifies some of the specialty program plans to be considered:
Additionally,
Contractual and Non-contractual provisions shall be stated in section 5.
5. ENGINEERING SPECIALTY INTEGRATION
5.1 Software development standards/plan.
A 'Software
Development Standards' (SDS) document shall be prepared to establish the CSCI
development process for the specific project. This will ensure that a common
method and documentation will be prepared and used for all the software to be
produced.
The
'Software Development Standards' shall incorporate the eclectic development
required by the contract.
Realization
of the SDS requirements shall result in the preparation of a 'Software
Development Plan (overall)' will have the management functions for product
evaluation, configuration management, documentation, and software tools and
methods in separate documents when necessary.
When
software development distributed (performed at various locations) each software
development team shall produce a separate CSCI specific SDP to identify and
describe their organizations and activities and to confirm adherence to the
overall standards, plans and procedures identified in the SDP (overall). For
model text see Software Development Standards/Plan(s)
5.2 UCI design program plan.
When
required a user-computer interface shall be developed alongside any system
software development. The user-computer interface shall incorporate all system
design features and provisions which enable or enhance the interactions between
the system user and software.
For model
text see UCI design program plan TBC
5.3 Reliability program plan.
A
'Reliability program plan' shall be prepared in accordance with the
requirements of MIL-STD-785. The objective with be to assure attainment of the
reliability requirements of the acquisition.
For model
text see Reliability plan model text.
5.4 Maintainability program plan.
A
'Maintainability program plan' shall be prepared in accordance with the
requirements of MIL-STD-470.
The primary purpose of the Maintainability program is to improve overall
readiness, reduce maintenance manpower needs, reduce life cycle cost and to
provide data essential for management.
The objective is to assure attainment of the maintainability requirements of
the acquisition.
For model
text see Maintainability plan model text.
5.5 Testability program plan.
The
'Testability program plan' shall identify the performing activity approach for
implementing a testability program.
The principle is to provide the acquirer with the basis for review and
evaluation of the Testability programme.
The preparation and plan shall be in accordance with MIL-STD-2165. For model
text see Testability Program Plan
The
'Engineering project (program) plan' shall specify critical events defining the
relationship to Systems Engineering Management and schedule control of the
development/engineering programme, for example, sequencing of Formal reviews
for the system/segments, CSCIs, and HWCIs, release of engineering, production,
test, logistic support events, formal audits, formal progress reviews, etc.,
shall be identified.
This data shall be described graphically in the form of PERT charts and shall
identify the major milestones and events required by the 'Statement of Work'.
Any planned program strategies and build planning shall be defined and
described in detail appropriate with the information available.
This plan shall be revised prior to a formal progress review.
For model
text see Engineering program plan
5.7 Hardware Development plan.
The
'Hardware Development Plan' shall define the activities, objectives, and
schedules for the HWCIs during their development life cycle.
For large and complex systems a 'Hardware Development Plan (overall)' will be
necessary to identify and establish the overall management, polices, etc. for
the project.
5.8 System safety program plan.
A 'System
safety Program Plan' shall be prepared when applicable in accordance with the
requirements of MIL-STD-882 or DEF STAN 00-55 / 00-56. The
primary purpose of the System Safety program plan is to establish the
organization and define activities to identify possible hazards and to analyze
and reduce the risk of their occurrence relevant to the project.
For model
text see System safety program plan
5.9 Human engineering program plan.
5.10 System test plan.
The 'System
Test Plan' shall be prepared to when necessary (defined in the System
Specification) to establish the philosophy and strategy for qualifying the
System. This should identify any specialist test program plan e.g., Software
Test Plan for CSCIs and HWCI when necessary, together with any proving tests
(Trials, Flight, etc.,) that are to be planned.
For model
text see System Test plan model text.
5.11 System security management plan.
A system
security engineering management plan shall be prepared to minimize and contain
defence system vulnerabilities to known or postulated security threats. The
purpose of the 'System Security Engineering Management Program is to establish
definitive guidance in the initial acquisition or modification of new and
existing systems, equipment, and facilities to analyze security design and
engineering vulnerabilities (see MIL-HDBK-1785 for more information).
For model
text see System security programme plan model text.
5.12 EMC clearance plan.
When
applicable the electromagnetic compatibility shall be demonstrated by trials to
the satisfaction of the acquirer that all systems operate, with adequate safety
margins, without malfunction or degradation of performance, in the
electromagnetic environment generated by all installed systems on the aircraft,
and in an agreed external environment corresponding to the operational use.
For model
text see Electromagnetic compatibility programme plan
model text.
When
required user-computer interface shall be developed alongside any system
software development. The user-computer interface shall incorporate all system
design features and provisions which enable or enhance the interactions between
the system user and software. These shall include: displays, displayed
information, formats, and elements; command modes; user-interface language;
input devices and techniques; dialogues, interactions, and transactions between
user and computer; user feedback; decision aiding; procedures and user
documentation; and provisions for training, prompting, cueing, helping, tutoring,
and resource requirements.
A plan shall be prepared to identify: design constraints, design activities,
schedules, and milestones, and resource requirements.
For model
text see UCI design programme plan model text.
Data
management controls the interface of information available to the acquirer from
the supplier and vice-versa. The plan shall outline the procedures and identify
forms used in the performance of the interface. For model text see Value engineering management plan model text.
5.14 Value engineering program plan.
Value
engineering is an organized effort to obtain optimum value by providing the
necessary function at the lowest life cycle cost. Value Engineering is normally
undertaken like Systems Analysis for a new design. The plan outlines the
organization and methods which are used for value engineering;
under construction.
For model
text see Value engineering management plan model text.
etc.
The
proposed items which will be included in the contract will be identified here.
The items which are basic to the satisfaction of program objectives and the
previously declared parts of MIL-STD-499A which have been identified.
5.3 Non-contractual provisions.
The
in-house procedures and any other standards will be identified in sufficient
detail to provide the acquirer with the visibility, validation and verification
of the contractual items.
The non-contractual items will identify the engineering organizations and key
personnel, and other coverage not appropriate for contract change control by
the acquirer.
Rest -
under construction
SEMP example document
now available in 
.pdf format:
See PDFDOCUMENTS.
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
Copyright
© Ken Rigby 1996, 1997, 1998, 1999 -- 2004