Discussion on Configuration Management

Originally Configuration Management was restricted to the control of the functional and physical characteristics of a system described in its technical documentation.
However, some recent standardization documents seem to accept that the principle shall be extended to incorporate the CI associated documents, test documents, management documents, Reports, Records, etc., which were change controlled by procedures defined in the SEMP or Documentation Standard.
It appears (STANAG 4159 and DEF STAN 05-57) that some functions which have always been considered as Systems Engineering tasks have been transferred or duplicated as Configuration Management functions. Tasks such as "Formal Technical Reviews", "Baseline Management", "Decision and Control", Specification Tree", etc., should be "System Engineering Management" functions!
While this principle appears sound, in fact to much CM does cause more problems and expense. See MIL-STD-493
I would therefore suggest that distinctions be made in CM:

Changes to documents are detailed in the 'Documentation Standard' section 3.2. Additional procedural documentation shall be prepared by the individual suppliers to suit individual needs. 



LE FastCounter

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 © by Ken Rigby 1995 - 1998