top - download
⟦c0087e7f2⟧ Wang Wps File
Length: 13544 (0x34e8)
Types: Wang Wps File
Notes: SD/STD/001
Names: »0073A «
Derivation
└─⟦83a4a04d1⟧ Bits:30005815 8" Wang WCS floppy, CR 0002A
└─ ⟦this⟧ »0073A «
WangText
…00……00……00……00……00……07……86…1 …02… …02… …02…
…02…SD/STD/001
…02…SVO/800923…02……02…#
CONFIGURATION ITEM IDENTIFICATION STANDARD
…02……02…GENERAL
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
…02…1 SCOPE ........................................ 1 to
1
…02……02…1.1 ITEM IDENTIFIERS ......................... 1
…02……02……02…1.1.1 Internal Origin ...................... 1
…02……02……02…1.1.2 External Origin ...................... 1
…02……02…1.2 SECTIONS ................................. 1
…02…2 HARDWARE IDENTIFICATION ...................... 2 to
3
…02……02…2.1 CONFIGURATION ITEMS ...................... 2
…02……02…2.2 ASSEMBLIES, PARTS AND STANDARD ITEMS ..... 2
…02……02…2.3 SPARES ................................... 3
…02……02…2.4 MARKING FOR SHIPMENT AND STORAGE ......... 3
…02…3 SOFTWARE IDENTIFICATION ...................... 3 to
4
…02……02…3.1 DEFINITIONS .............................. 4
4 FIRMWARE IDENTIFICATION ......................
6 to 6
…02…5 DOCUMENT IDENTIFICATION ...................... 6 to
9
…02……02…5.1 "AAA" .................................... 6
…02……02…5.2 "BBB" .................................... 6
…02……02……02…5.2.1 General .............................. 7
…02……02……02…5.2.2 Plans of Specific Applicability ...... 7
…02……02……02…5.2.3 Specifications ....................... 7
…02……02……02…5.2.4 Manuals .............................. 8
…02……02……02…5.2.5 Reports .............................. 8
…02……02……02…5.2.6 Request/Proposals .................... 8
…02……02……02…5.2.7 Miscellaneous ........................ 8
…02……02…5.3 "CCC" .................................... 8
…02……02…5.4 (D.E) .................................... 9
…02…6 NUMBERING SYSTEM FOR DRAWINGS AND FORMS ...... 9 to
10
…02……02…6.1 PROJECT OR EQUIPMENT ORIENTED DRAWING
NUMBERING SYSTEM .........................
10
…02……02…6.2 NOTE IN DRAWING NUMBERING ................ 10
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 I̲T̲E̲M̲ ̲I̲D̲E̲N̲T̲I̲F̲I̲E̲R̲S̲
All items placed under Configuration Control shall
be given a unique identifier according to the rules
in this standard.
1.1.1 I̲n̲t̲e̲r̲n̲a̲l̲ ̲O̲r̲i̲g̲i̲n̲
The rules are applicable to all items originating within
the division regardless of the physical nature of the
item.
1.1.2 E̲x̲t̲e̲r̲n̲a̲l̲ ̲O̲r̲i̲g̲i̲n̲
All items received from external sources, and which
are given a proper identifier by the originator, will
retain this identifier. This also applies to items
received from other divisions within the company.
1.2 S̲E̲C̲T̲I̲O̲N̲S̲
According to the nature of the items in question the
standard is divided into the following sections:
- Hardware items
- Software items
- Documents
- Drawings
2 H̲A̲R̲D̲W̲A̲R̲E̲ ̲I̲D̲E̲N̲T̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
Every piece of hardware of a certain complexity is
provided with a part-number followed by a serial number.
Standard items as bars and brackets are stamped with
a part-number and not serialized. The part-number on
these items may be omitted. A given CI, once assigned
a serial number, will retain the serial number regardless
of modifications, as long as it is assigned the same
part number.
The Part and Serial number is the only unique number
for a Hardware item.
Identical part numbers ensure same form, fit and function,
i.e. usable as a spare.
2.1 C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲I̲T̲E̲M̲S̲
Identification plates for configuration items shall
include:
a) CI Part Number
b) CI Serial Number
c) Manufacturer Initials
2.2 A̲S̲S̲E̲M̲B̲L̲I̲E̲S̲,̲ ̲P̲A̲R̲T̲S̲ ̲A̲N̲D̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲ ̲I̲T̲E̲M̲S̲
Smaller items not directly under Configuration Control
shall be stamped with the following Id. numbers:
a) Part Number or Standard Identification Number.
b) Serial Number (if used).
Parts/standards which are too small, or which may be
physically or functionally damaged by this identification,
and those which are encapsulated within another, otherwise
permanently assembled and not replaceable as a unit,
need not comply with these requirements.
2.3 S̲P̲A̲R̲E̲S̲
Spares shall be identified by nameplate or markings
as applicable to the spare. (Spares will always be
configuration items).
2.4 M̲A̲R̲K̲I̲N̲G̲ ̲F̲O̲R̲ ̲S̲H̲I̲P̲M̲E̲N̲T̲ ̲A̲N̲D̲ ̲S̲T̲O̲R̲A̲G̲E̲
Shipping and storage containers are marked according
to internal standards. Shipping papers will follow
the general requirements suitable to actual shipment.
Ref. PRO/PROC/0009: "Packing and Labeling".
3 S̲O̲F̲T̲W̲A̲R̲E̲ ̲I̲D̲E̲N̲T̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
The software identification conventions apply to:
a) Individual computer program components (CPCs).
This includes support program CPCs used to facilitate
tests or generate tapes, simulation program CPCs,
models, etc., as well as application programs,
and computer programs associated firmware.
b) Other modular computer program elements such as
superglobal data, etc.
The part number consists of:
a 3 letter project mnemonic
a 3 digit subsystem code
a 3 letter form and medium code
a 4 digit version and patch number
Identification number: XXX/XXX/X-X/XXXX
Project name
Subsystem Module number
code Submodule number
Form code
Medium code
Version number
Patch number (00 if not a patch)
A computer program submodule will be assigned an identification
number, whose version will be incremented by one each
time its source form is modified.
A computer program module shall be assigned a subsystem
code N00 where N is one of the numbers 1 through 9.
Submodules belonging to a module with subsystem code
N00 shall be assigned one of the subsystem codes N01
through N99.
When a submodule is modified, the version number of
that submodule shall be incremented by one.
3.1 D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲S̲
Project name is a mnemonic abbreviation of a project
name. Examples are:
TOS - TOSCA
MET - METEOSAT
CSS - CR80 SYSTEM SOFTWARE
NIC - NICS-TARE
CPS - CAMPS
FIX - FIKS
The Subsystem Code is a 3-digit code assigned to a
subdivision of the system documentation. Figures 001
to 099 are associated to the general project documentation
while 100 to 999 are oriented towards a functional
breakdown of the project. For each project a list of
subsystem codes exists which shall be established at
the start of the project.
It is the responsibility of the Project Manager to
establish this list.
F̲o̲r̲m̲ ̲C̲o̲d̲e̲ S̲o̲f̲t̲w̲a̲r̲e̲ ̲F̲o̲r̲m̲
S SOURCE (computer program module, subsystem
library, system library).
T TEST MATERIAL
O OBJECT (Computer program module, subsystem
library, system library)
B BOOT OR LOAD MODULE (System or CPM)
L LISTING (all types)
D DATA (general)
J JCL
F FLOWCHART
V BIT PATTERN (primarily used for firmware).
Software Medium Codes are:
M̲e̲d̲i̲a̲ ̲C̲o̲d̲e̲ S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲e̲d̲i̲u̲m̲ ̲
T Mag Tape
C Punched Cards
D Disc/Drum
P Paper/Mylar Punched Tape
H Hard Copy
F Microfiche/Microfilm
J ROM
S Cassette
O Other
The 2 digit version number will initially be 01 and
will be incremented by 1 each time the CPM is modified.
The 2 digit patch number is an identification of patches
which apply to a CPM version.
If the software item is not a patch, the patch number
is 00.
4̲ ̲ ̲F̲I̲R̲M̲W̲A̲R̲E̲ ̲I̲D̲E̲N̲T̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
Firmware involves the merging of a software and a hardware
item and the identification must reflect this merging:
a) S̲o̲f̲t̲w̲a̲r̲e̲
The software item is identified as described in
section 3 of this standard.
b) P̲R̲O̲M̲
Master PROMs are given an identifier of the form:
…01…CR/XXXX/YY
XXXX is a unique number drawn from the PROM Registration
List kept at the factory's PROM burning facility.
YY is an unique version number drawn from a PROM
Revision Number List also kept at the PROM burning
facility.
c) D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
A Version Description Document must exist containing
description of a specific master PROM and its contained
software. This document must be identified as described
in section 5 of this standard.
d) C̲r̲o̲s̲s̲ ̲r̲e̲f̲e̲r̲e̲n̲c̲e̲
The Configuration Manager will maintain a list
giving a cross reference between the various aspects
of Firmware Items.
5̲ ̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲ ̲I̲D̲E̲N̲T̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲
All documents originating within the division shall
be supplied with a document identifier consisting of
4 fields in the following format:
AAA/BBB/CCC (D.E)
5.1 "̲A̲A̲A̲"̲
Is a code designating the organization (project, department,
division) within which the document originate or to
which the document is applicable. The code is a 2
to 4 letter mnemonic associated with each organization.
Example: CR = Christian Rovsing A/S Company-wide
SD = Systems Division
QAD = Quality Assurance Department
CPS = CAMPS Project
5.2 "̲B̲B̲B̲"̲
Is a 3 letter mnemonic designating the document type.
Only mnemonics authorized by the configuration manager
may be used.
Department or Project Management may define a subset
of the available types as being applicable to that
organization.
Applicable Document Types:
5.2.1 G̲e̲n̲e̲r̲a̲l̲
LET Letter
TLX Telex
MIN Minutes of meetings
PLN Plans of general applicability
MMO Memorandum
STD Standard
REP Report of general applicability
TCN Technical Notes
AUX Auxiliary documents
PRP Proposal (BID)
5.2.2 P̲l̲a̲n̲s̲ ̲o̲f̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲ ̲A̲p̲p̲l̲i̲c̲a̲b̲i̲l̲i̲t̲y̲
PIP Project Implementation Plan
QAP Quality Assurance Plan
CMP Configuration Management Plan
TSP Test Plan
5.2.3 S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
SYS System Requirements Specification
SRS Subsystem Requirements Specification
SDS System/Subsystem Design Specification
MDS Module Design Specification
ICD Interface Control Document
VCD Verification Control Document
TSS Test Specification
VDD Version Description Document
DBD Database Document
TPR Test Procedure
5.2.4 M̲a̲n̲u̲a̲l̲s̲
OPM Operating Manual
REM Reference Manual
USM Users Manual
STM Standard Manual
5.2.5 R̲e̲p̲o̲r̲t̲s̲
QAR Quality Assurance Report
W/M/QPR Weekly/Monthly/Quarterly Progress Report
EPR Engineering Problem Report
EPA Engineering Problem Analysis
TRP Test Report
5.2.6 R̲e̲q̲u̲e̲s̲t̲/̲P̲r̲o̲p̲o̲s̲a̲l̲s̲
ECR Engineering Change Request
SCR Specification Change Request
RFD Request for Deviation
RFW Request for Waiver
ECP Engineering Change Proposal
5.2.7 M̲i̲s̲c̲e̲l̲l̲a̲n̲e̲o̲u̲s̲
COC Certificate of Conformance
ECO Engineering Change Order
5.3 "̲C̲C̲C̲"̲
Is a consecutive number for each type of document.
The document control center will assign numbers and
keep list of all used numbers within each document
type.
5.4 (̲D̲.̲E̲)̲ ̲
Is a number designating the issue and change status
of a document.
This field may be omitted for original issues of a
document.
The number "D" designates the issue, starting with
one and incremented with one for each issue.
The number "E" designates the number of changes made
to a document, starting with O and incremented by one
at each change.
At new issues the change status is zeroed. The change
status and the associated decimal point may be omitted
when the change status is zero.
Example: SD/STD/001(1.0)
6 N̲U̲M̲B̲E̲R̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲ ̲F̲O̲R̲ ̲D̲R̲A̲W̲I̲N̲G̲S̲ ̲A̲N̲D̲ ̲F̲O̲R̲M̲S̲
All drawings and forms received from the customer will
retain their original numbers.
Drawings and forms generated by CR are numbered in
accordance with the rules below, but may also be assigned
an additional number by the customer in certain cases.
a) General drawings and form numbering system.
All drawings and forms are given a file number
by the drawing office as follows:
Project drawings: AX-YYYY(Z)
Component location Dwgs.: KX-YYYY (Z)
Proposal drawings: AX0-YYYY (Z)
Forms: AX00-YYYY-Z
where:
AX = Format code, where X = 0, 1, 2, 3, 4, for A0
to A4
KX formats T1 and T2 and K0 to K4 for component
location drawings.
YYYY = consecutive drawing or form number for each
format
without
leading
zeroes,
exept
for
component
location
drawings
where
the
number
is
identical
to
the
PWB
artwork
number.
Z = issue status for drawings and modification
or version of a basic form. Not included for
basic forms.
6.1 P̲R̲O̲J̲E̲C̲T̲ ̲O̲R̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲ ̲O̲R̲I̲E̲N̲T̲E̲D̲ ̲D̲R̲A̲W̲I̲N̲G̲ ̲N̲U̲M̲B̲E̲R̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲
If a project manager considers it useful to employ
an additional project or hardware oriented drawing
numbering system, he is free to do so. This numbering
system must then be defined in a project document.
This additional number is then marked on the drawings,
and used instead of the file number when referring
to the drawing.
6.2 N̲O̲T̲E̲ ̲I̲N̲ ̲D̲R̲A̲W̲I̲N̲G̲ ̲N̲U̲M̲B̲E̲R̲I̲N̲G̲
If a project oriented drawing numbering systen is used
it may be necessary to establish a cross-reference
index between this system and the corresponding file
numbers. In this way, the project oriented number,
which is logically constructed, can be used in all
references, and the drawing office can use this index
to locate the file numbers for retrieval.
