top - download
⟦67eee1225⟧ Wang Wps File
Length: 10008 (0x2718)
Types: Wang Wps File
Notes: Conf.chang.cont.stand.
Names: »0076A «
Derivation
└─⟦83a4a04d1⟧ Bits:30005815 8" Wang WCS floppy, CR 0002A
└─ ⟦this⟧ »0076A «
WangText
…00……00……00……86…1 …02… …02… …02…
SD/STD/003
…02…801020…02……02…#
CONFIGURATION CHANGE CONTROL STANDARD
…02……02…CAMPS
1 T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
…02…1 SCOPE ....................................... 4 to
7
…02……02…1.1 CLASSIFICATION OF CHANGES................ 4
…02……02…1.2 HARDWARE ................................ 5
…02……02…1.3 SOFTWARE ................................ 6
…02……02…1.4 DOCUMENTS ............................... 6
…02……02…1.5 DRAWINGS ................................ 7
…02…2 AUTHORIZATION ............................... 7 to
8
…02……02…2.1 TECHNICAL AUTHORIZATION ................. 7…02……02……02…2.2
INSTALLATION AUTHORIZATION .............. 8
…02…3 CONFIGURATION CHANGE REQUISITES ............. 8 to
9
…02……02…3.1 CHANGE PROPOSALS ........................ 8
…02……02…3.2 CHANGE ORDERS ........................... 9
…02…4 CONFIGURATION CHANGE REGISTRATION ........... 9 to
11
…02……02…4.1 IDENTIFICATION .......................... 10
…02……02…4.2 DESCRIPTION ............................. 10
…02……02…4.3 DISTRIBUTION ............................ 11
1 S̲C̲O̲P̲E̲
This standard is a derivative of Configuration Management
Standard Manual SD/STM/006 and has the same scope and
applicability as that document.
1.1 C̲L̲A̲S̲S̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲O̲F̲ ̲C̲H̲A̲N̲G̲E̲S̲
Changes in the configuration of any CI after baseline
has been established will be classified as either Class
I or Class II. Class I changes are those proposed
changes that affect "form, fit, or function". Class
II changes have no effect on performance, interchangeability,
cost, maintainability, reliability, or delivery schedules.
CCB approval prior to implementation of a Class II
change normally is not required. However, such changes
are subject to post facto classification review by
the CCB. Examples of Class II engineering changes
are: a change in documentation only (e.g., correction
of errors, addition of clarifying notes or views),
and a change in hardware (e.g., substitution of an
alternative material if a specific material is not
required). Class I ECP's are used when one or more
of the following factors is affected:
a) Baselines
b) Technical requirements to include (but not limited
to) performance outside stated tolerances; reliability,
maintainability or survivability outside stated
tolerances; weight, balance, moment of inertia;
interface characteristics.
c) Non-technical contractual provisions such as fee;
cost to customer schedules; guarantees or deliveries.
d) Other factors: NATO furnished equipment (NFE);
Safety; Electromagnetic characteristics; Operational,
test or maintenance computer programs; configuration
to the extent that retrofit action would be taken;
operation and maintenance manuals for which adequate
change/revisions funding is not on existing contracts;
interchangeability, substitutability or replaceability,
as applied to CI's and to all sub-assemblies and
parts of repairable CI's, excluding the pieces
and parts of non-repairable sub-assemblies; skills,
manning, training, bio-medical factors or human
engineering design.
e) Class I engineering changes to privately developed
items occur when the change affects the contractually
specified form, fit, function, cost or delivery
schedule of the item.
1.2 H̲A̲R̲D̲W̲A̲R̲E̲
Configuration change control applies to hardware items
which are previously approved.
Class II changes to such items can be made in cases
where the change is of minor importance, i.e. no effect
is measureable to the function of the hardware or software
implied, and the part number is not changed.
In case of Class I change, i.e. where the function
of hardware, or software, is changed, or the part number
is changed, it is the responsibility of the Configuration
Management to check that applicable software, documents,
and drawings, are simultaneously changed.
1.3 S̲O̲F̲T̲W̲A̲R̲E̲
Configuration change control applies to all software
items which have been approved and implemented (catalogued).
All Class I software changes must result in an updating
of the version and/or patch number of the software
item in question.
A new version/patch of a software item cannot be released
by Configuration Management until
- it has been approved by QAD
- all implications to other software, hardware, and
documents have been analysed
- applicable simultaneous changes to other software,
hardware, and documents have been performed.
1.4 D̲O̲C̲U̲M̲E̲N̲T̲S̲
Configuration Change Control applies to all documents
previously approved and released.
Any Class I change to a such document implies the change
of the issue and/or change status number.
A changed document cannot be accepted under Configuration
Management until any applicable simultaneous changes
are made to other documents, software, hardware, or
drawings.
Obsolete issue of a document should be kept centrally
for verification purposes until a completely new issue
has been released.
1.5 D̲R̲A̲W̲I̲N̲G̲S̲
Configuration Change Control applies to all drawings
which have been approved by QAD and filed as such.
Any Class I change to a such drawing implies the change
of its issue status.
A changed drawing cannot be accepted under Configuration
Control until any applicable simultaneous changes have
been made to other drawings or documents.
Obsolete issues of drawings should be kept centrally
for verification purposes until otherwise decided by
QAD.
2 A̲U̲T̲H̲O̲R̲I̲Z̲A̲T̲I̲O̲N̲
The responsibility of authorization of configuration
changes are divided in two parts: The technical authorization
and the installation authorization.
2.1 T̲E̲C̲H̲N̲I̲C̲A̲L̲ ̲A̲U̲T̲H̲O̲R̲I̲Z̲A̲T̲I̲O̲N̲
The Technical Authorization of a Class I change is
outside the scope of CM. Decisions are made by the
Change Control Board (CCB). Class II changes are subject
to post facto review by CCB.
Rules are found in plans and standards for CCB.
2.2 I̲N̲S̲T̲A̲L̲L̲A̲T̲I̲O̲N̲ ̲A̲U̲T̲H̲O̲R̲I̲Z̲A̲T̲I̲O̲N̲
CM has the responsibility for Installation Authorization.
Before authorizing a change for installation CM must
check
- feasibility (change control board)
- quality (QAD)
- consistency (simultaneous installation of mutually
dependent changes)
3 C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲C̲H̲A̲N̲G̲E̲ ̲R̲E̲Q̲U̲I̲S̲I̲T̲E̲S̲
This chapter describes the requisites and tools for
change of configurations.
3.1 C̲H̲A̲N̲G̲E̲ ̲P̲R̲O̲P̲O̲S̲A̲L̲S̲
Any staff member may propose changes to configuration
items. Likewise proposals may originate from the user/customer.
To obtain immediate consideration any proposal for
a change of configuration items must be written on
or accompanied by the appropriate change request form,
the Engineering Change Proposal (ECP).
The change proposal should be sent to the book captain
or team leader responsible for the configuration item
in question.
The change proposal must be thoroughly scrutinized
by the responsible leader and QAD, and - in case of
Class 1 change - after approval by Change Control Board
(CCB) it may be accepted. If a change proposal to one
configuration item implies influence on other items,
an additional change proposal must be issued, and cross
reference must be established.
3.2 C̲H̲A̲N̲G̲E̲ ̲O̲R̲D̲E̲R̲S̲
As soon a change proposal has been approved a copy
is sent to CM, who registers it as a pending change.
The change proposal is converted into a change order
on/or accompanied by the appropriate form: Engineering
Change Order (ECO).
Upon completion of the change and the subsequent QAD
approval, CM is advised, whereupon appropriate steps
are taken to issue Installation Authorization as stated
in section 2.2 of this standard by means described
in TBD.
4 C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲C̲H̲A̲N̲G̲E̲ ̲R̲E̲G̲I̲S̲T̲R̲A̲T̲I̲O̲N̲
Any change to a configuration item must be registered
by CM following the rules set down in this chapter.
4.1 I̲D̲E̲N̲T̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
Changes are registered on forms as described in chapter
3.
Those forms are identified by numbers assigned by CM.
None of those forms may be issued until they have been
registered by CM and assigned the said number, and
the configuration item involved must also be registered
by CM.
CM will keep a cross referencing file making it possible
to recognize any pending change both by change form
number and by configuration item identification.
4.2 D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
A copy of any document describing a change to a configuration
item must be filed by the CM. However, for pending
changes a very brief decription may be satisfactory
provided reference is made to a full description and
to the person holding this description.
Full description of the change must be filed by CM
at completion of the change (and approval by QAD).
This description must include a statement of the necessity
of distribution of a new issue or version. This statement
must clearly indicate whether
- the change makes it necessary to immediately distribute
a new issue/version
- distribution of a new issue/version is dependent
on other (identified) change(s) i.e must wait for
completion of that/those.
- distribution may be done occasionally.
4.3 D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲
CM keeps a cross reference file with entry by change
document identification and by configuration item identification
clearly indicating changes completed but not yet distributed.
Likewise, CM keeps a cross reference file with the
same entry points for distributed changes. This file
clearly indicates
- which changes have been distributed by a certain
issue/version
- which issue/version includes a certain change.
