top - download
⟦2246d9993⟧ Wang Wps File
Length: 169184 (0x294e0)
Types: Wang Wps File
Notes: PC CONTRACT
Names: »1849A «
Derivation
└─⟦674a3d0c4⟧ Bits:30006239 8" Wang WCS floppy, CR 0622A
└─ ⟦this⟧ »1849A «
WangText
H…05…G…0c…G…0f…G…06…F…0c…F E…0b…E…01…E…06…D…0c…D C…09…C…0c…C
B…0a…B…01…B
A…09…A…00…@…09…@…0f…@…05…?…0b…?…02…? >…0a…>…0f…>…05…=…0c…=…02…<…08…<…0e…<…05…;…0b…;…02…:…0a…:…01…9…0a…9…02…8…08…8…01…7…08…7…0f…7…06…6…0c……86…1
…02…
…02…
…02…
…02…
…02…820429…02……02…#
PROTOCOL
CONVERTER
SYSTEM
REQUIREMENT
SPECIFICATION…02……02…
PC
3.4.2…02…P̲h̲y̲s̲i̲c̲a̲l̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
3.4.2.1 S̲i̲z̲e̲,̲ ̲W̲e̲i̲g̲h̲t̲,̲ ̲P̲o̲w̲e̲r̲ ̲C̲o̲n̲s̲u̲m̲p̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲H̲e̲a̲t̲ ̲D̲i̲s̲s̲i̲p̲a̲t̲i̲o̲n̲
The site equipments consist of a number of terminals
and one or two multi-bay rack assemblies.
The racks of each site equipment will be equipped with
subassemblies and modules according to the actual connectivity.
Detailed technical information will be supplied in
the System Design Specification.
3.4.2.2 P̲o̲w̲e̲r̲ ̲I̲n̲p̲u̲t̲
The equipments shall be capable of satisfying the specified
performance requirements when operating with following
power input:
a) Phases: Single- or 3-phase, and ground. (For
supply of redundant elements within
the equipment, the power input shall
be established with 2 independent
sources as a minimum).
b) Voltage: Nominal value 380/220 V AC
Tolerances: +10%/-15%
Except UKAIR where nominal value
is 405/240 V AC.
c) Frequency: Nominal value: 50 Hz
Tolerances: +10/-10%
d) Harmonic
distortion: Max. 5%
e) Transients: Non-repetitive impulsive interference
with a magnitude not to exceed 500
volts, pulse rise and fall times
not faster than 10 microseconds and
a total duration of maximum 1 millisecond.
The available impulse energy at the
equipment power inlet shall not exceed
5J.
f) Exemptions: Each site equipment will contain
three disk drives. These will not
operate within the tolerances of
section b) and c) above, but:
1) Voltage: Nominal value: 380/220V AC
Tolerances: +6%/-10%
2) Frequency: Nominal value: 50 Hz
Tolerance: +0,5 Hz/-1.0 Hz
In order to meet these special tolerance requirements
voltage/frequency stabilizers shall be inserted
in the power lines for the disk drives.
Frequency Stabilizers shall be delivered for installation
at all non-optional sites of figure 3.4.1.7.1 except
BALTAP, WEST STAR, and NATO.
For UKAIR see para 3.7.1.2.4.
g) Exemptions: Each site will contain a number of
Medium Speed Printers. These will
not operate within the tolerances
of section b) and c) above, but:
1) Voltage: Nominal value: 240/220V
AC
Tolerances: +10%/-15%
2) Frequency: Nominal value: 50
Hz
Tolerance: +5 Hz/-3
Hz
3.4.2.3 T̲e̲m̲p̲e̲s̲t̲ ̲R̲a̲c̲k̲s̲
The EMI racks are constructed of heavy gauge steel,
having all non-opening seams welded. The racks will
be of slightly greater size than equivalent non-EMI
racks and will be significantly heavier. Cable entrance
for power and signals will be either through the top
or bottom of each rack. The racks are prepared for
both type of outlet.
a) R̲a̲c̲k̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
The racks will be used as a single, free-standing
cabinet or assembled into bays of 2, 3, 4, or more
racks in a row forming a cabinet.
The individual racks will be transported separately
and joined with coupling accessories at site. Thus,
four rack types are defined.
1) L̲E̲F̲T̲ ̲E̲N̲D̲ ̲R̲A̲C̲K̲S̲, which includes one welded panelled
side and one open side with joiner frame, hardware,
and accessories.
2) I̲N̲T̲E̲R̲M̲E̲D̲I̲A̲T̲E̲ ̲R̲A̲C̲K̲, which includes both sides
open, but with only one joiner frame, hardware,
and accessories.
3) R̲I̲G̲H̲T̲ ̲E̲N̲D̲ ̲R̲A̲C̲K̲, which includes one open side
without joiner frame and one welded panelled
side and accessories.
4) F̲R̲E̲E̲-̲S̲T̲A̲N̲D̲I̲N̲G̲ ̲R̲A̲C̲K̲, which includes both sides
welded panelled, and accessories.
The types of racks are non interchangeable, left cannot
be interchanged with right, a freestanding cannot be
changed to a right, etc.
b) R̲a̲c̲k̲ ̲D̲o̲o̲r̲s̲
Each rack shall have a full size door in front
and rear. Doors will be operated with recessed
handles. The doors shall contain EMI gaskets.
c) R̲a̲c̲k̲ ̲V̲e̲n̲t̲i̲l̲a̲t̲i̲o̲n̲
To allow ventilation and EMI shielding, perforated
metal is used. The perforated areas are located
in the front doors and at the top.
d) A̲C̲ ̲P̲o̲w̲e̲r̲ ̲F̲i̲l̲t̲e̲r̲s̲
RF power filters shall be used, and they shall
be mounted directly to either the top or bottom
of racks.
e) I̲n̲t̲e̲r̲m̲e̲d̲i̲a̲t̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲F̲r̲a̲m̲e̲ ̲(̲I̲D̲F̲)̲
The IDF shall be enclosed within one of the main
frame EMI racks. It provides access to all input
and output electrical signal connections to the
CAMPS mainframe. Filtered connectors will be installed
in the IDF as described below to meet AMSG requirements.
The IDF consists of a separately shielded box sealed
to the rack surface within an EMI rack into which
conduit or ducts from all external electrical signal
cables are passed. Upon removal of the IDF cover,
52 banks of 25 pin connectors are accessible for
user connection. Optical signal cables are fed
through a wavequide placed separately or contained
in the IDF.
Rack cable connections between the multi-bay rack
assemblies shall be passed in tubes sealed to the
racks.
f) V̲2̲8̲(̲L̲)̲-̲A̲d̲a̲p̲t̲e̲r̲s̲ ̲f̲o̲r̲ ̲D̲r̲i̲v̲i̲n̲g̲ ̲E̲l̲e̲c̲t̲r̲i̲c̲a̲l̲ ̲C̲a̲b̲l̲e̲s̲
The V28(L) shall provide 6-0-6 volts signal levels
and waveshaping.
2 types shall be provided.
The first type shall cover the range up to 1200
BPS. The second type shall cover the range up to
9600 Bps.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲4̲.̲3̲
…02……02……02…3.4.3 Environmental Conditions ............ 250
…02……02……02……02…3.4.3.1 Temperature and Humidity ........ 250
…02……02……02……02…3.4.3.2 Dust, Fumes ..................... 251
3.4.3…02…E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲
In designing the equipment to meet the specified requirements
no account need be taken of catastrophic events such
as fire, flood, explosion, etc., which are beyond the
control of an equipment manufacturer.
The equipment will normally operate within accomodation
suitable for the operation of similar equipment produced
for commercial use.
After initial adjustments have been made, the equipment
shall maintain normal operation under all specified
environmental and power supply conditions.
3.4.3.1 …02…T̲e̲m̲p̲e̲r̲a̲t̲u̲r̲e̲ ̲a̲n̲d̲ ̲H̲u̲m̲i̲d̲i̲t̲y̲
The equipment shall continue to function when the humidity
and temperature of its environment are within the ranges
and cycling specified below.
The equipment shall continue to operate in a fully
satisfactory manner even under the worst conditions
specified below.
…02…a) T̲e̲m̲p̲e̲r̲a̲t̲u̲r̲e̲
…02……02…Range : 10 to 40 deg.C
…02……02…Change : max 10 deg. C per hour
…02…b) H̲u̲m̲i̲d̲i̲t̲y̲ ̲(̲R̲e̲l̲a̲t̲i̲v̲e̲ ̲H̲u̲m̲i̲d̲i̲t̲y̲ ̲=̲ ̲R̲H̲)̲
…02……02…Range : 40 to 90% RH, non-condensing
…02……02…Change : max. 6% RH per hour, non-condensing
…02…c) A̲l̲t̲i̲t̲u̲d̲e̲
…02……02…Range : Sea level to 2000 meter
The equipment shall be so designed that the loss of
site air conditioning or heating will not cause a catastrophic
failure within 15 minutes after the loss.
An alarm indication shall be given, when the environmental
temperature reaches a value which will require intervention
of supervisory personnel.
3.4.3.2 D̲u̲s̲t̲,̲ ̲F̲u̲m̲e̲s̲
The equipment shall be able to operate continuously
and with normal scheduled preventive maintenance in
the following air environment:
a) Ai̲r̲ ̲c̲l̲e̲a̲n̲n̲e̲s̲s̲
Particle size Max. allowable number
(̲m̲i̲c̲r̲o̲n̲s̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲(̲p̲a̲r̲t̲i̲c̲l̲e̲s̲/̲c̲u̲b̲i̲c̲m̲e̲t̲e̲r̲)̲
greater than 5 4* (10 5)
greater than 1.5 4* (10 6)
greater than 1 4* (10 7)
b) F̲u̲m̲e̲s̲
sulphur dioxide max. 14 ppm.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲…01…S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲4̲.̲4̲
…02……02……02…3.4.4 Availability and Maintainability .... 253
…02……02……02……02…3.4.4.1 General ......................... 253
…02……02……02……02…3.4.4.2 Reliability Characteristics ..... 253
…02……02……02……02…3.4.4.3 Availability Calculation ........ 253
…02……02……02……02…3.4.4.4 Availability and Reliability
Performance Requirements ........
254
…02……02……02……02……02…3.4.4.4.1 User Connecting Point ....... 254
…02……02……02……02……02…3.4.4.4.2 Individual User Connecting
Points ......................
255
…02……02……02……02……02…3.4.4.4.3 Groups of User Connecting
Points ......................
255
…02……02……02……02……02…3.4.4.4.4 User Connecting Points to
Supervisory and Service
Terminals ...................
255
…02……02……02……02……02…3.4.4.4.5 External Channels and
Circuits ....................
256
…02……02……02……02……02…3.4.4.4.6 Individual Channels ......... 256
…02……02……02……02……02…3.4.4.4.7 Groups of Channels .......... 256
…02……02……02……02……02…3.4.4.4.8 All Circuits, Channels and
User Connecting Points ......
256
…02……02……02……02…3.4.4.5 Equipment Redundancy ............ 257
…02……02……02……02……02…3.4.4.5.1 Withdrawal of Redundant
Items .......................
257
…02……02……02……02……02…3.4.4.5.2 Loss of Redundancy .......... 258
…02……02……02……02…3.4.4.6 Specific Equipment Availability
Requirements ....................
258
…02……02……02……02…3.4.4.7 Terms ........................... 258
4. A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲a̲n̲d̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲
4.1 G̲e̲n̲e̲r̲a̲l̲
Availability and maintainability requirements apply
to the equipment excluding environmental control equipment,
primary power supply to the equipment, and other purchaser
supplied equipment.
The equipment will meet the specified requirements:
a) When operating in a support environment which lies
within the limits of the specified operating requirements
of the equipment.
b) When tools, repair parts, manuals, manpower, etc.
required for maintenance are available.
In designing the equipment to meet the specified requirements
no account need to be taken to catastrophic events
such as fire, flood, explosion, etc. which are beyond
the control of the equipment manufacturer.
The definitions of the terms used in this section are
given in section 4.2.
3.4.4.2 R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲c̲t̲i̲c̲s̲
The reliability of the equipment is specified in terms
of its availability. The equipment is partitioned into
modules and units, which are used for construction
of the R & M models and block diagrams. A separate
analysis shall be conducted for each module performance
requirement specified below.
3.4.4.3 A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲C̲a̲l̲c̲u̲l̲a̲t̲i̲o̲n̲
The inherent availability of a module or unit shall
be measured in terms of two parameters:
- Mean time between failure (MTBF)
- Mean time to repair (MTTR)
The availability of a module or unit shall be determined
from the formula
Ai = ̲ ̲ ̲ ̲ ̲M̲T̲B̲F̲i̲ ̲ ̲ ̲ ̲ ̲
MTBFi + MTTRi
The availability value associated with each reliability
performance requirements, specified in succeeding paragraphs
of this section, shall be determined from a R&M model
and block diagram by combining the availability co-efficients
for the modules and units affecting that availability
performance requirement. The availability co-efficient
for a series configuration shall be calculated by:
elements ̲ ̲
A (system)= ll Ai
i=1
where Ai is the availability co-efficient of the i…09…th
element.
In the case of modules and units provided for the purpose
of redundancy (e.g. duplicated units) the availability
co-efficient shall be calculated by:
a) For (N-1) out of N redundancy is the availability
for (N-1) out of N being operative:
…0f…MTTR…0e…
A(N-1 out of N operative) = 1 - N * (N-1) * (------)…0e…2…0f…
…0e…MTBF…0f…
where MTTR MTBF.
b) For other types of redundancy the availability
shall be calculated using the R&M model. Assumptions
made shall be justified.
3.4.4.4 A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲a̲n̲d̲ ̲R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲P̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
3.4.4.4.1 U̲s̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲n̲g̲ ̲P̲o̲i̲n̲t̲
The demarcation point between terminals and the equipment
is the user connecting point. The availability of
service shall be measured at the user connecting point
of the equipment, to which each terminal is attached.
3.4.4.4.2 I̲n̲d̲i̲v̲i̲d̲u̲a̲l̲ ̲U̲s̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲n̲g̲ ̲P̲o̲i̲n̲t̲s̲
a) The availability of the subset of the equipment
which provides service to each user connecting
point shall be at least .9995.
b) The MTBF of a failure which causes loss of service
to a single user connecting point shall be at least
3 months with an MTTR not to exceed 40 mins.
3.4.4.4.3 G̲r̲o̲u̲p̲s̲ ̲o̲f̲ ̲U̲s̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲n̲g̲ ̲P̲o̲i̲n̲t̲s̲
It shall be possible to select user connecting points
in groups in such a way that no single failure shall
cause loss of service to more than one such group.
Within the expansion capacity specified in this document,
the maximum number of user connecting points in such
a group is 8.
The equipment shall be designed such that no single
failure can cause loss of service to 25% or more user
connecting points.
a) The availability of the subset of the equipment
at the maximum expanded configuration which provides
service to 75% or more of the user connecting points
shall be at least 0.9999.
b) The MTBF of a failure which causes loss of service
to 25% or more user connecting points of the maximum
expanded configuration shall be at least 1 year
with an MTTR not to exceed 1 hour.
3.4.4.4.4 U̲s̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲n̲g̲ ̲P̲o̲i̲n̲t̲s̲ ̲t̲o̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲a̲n̲d̲ ̲S̲e̲r̲v̲i̲c̲e̲
̲T̲e̲r̲m̲i̲n̲a̲l̲s̲
It shall be possible to divide the connecting points
providing service to the terminals of the supervisory
and service positions into more than one group.
a) The availability of the subset of the equipment
which provides service to any such group shall
be at least 0.9999.
b) The MTBF of a failure which causes loss of service
to such a group shall be at least 1 year with an
MTTR not to exceed 1 hour.
3.4.4.4.5 E̲x̲t̲e̲r̲n̲a̲l̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲ ̲a̲n̲d̲ ̲C̲i̲r̲c̲u̲i̲t̲s̲
Availability of service to external channels circuits
shall be measured at the connection point of the equipment,
to which each circuit is attached.
3.4.4.4.6 I̲n̲d̲i̲v̲i̲d̲u̲a̲l̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲
1) The availability of the subset of the equipment
which provides service to each incoming or outgoing
channel shall be at least .9995.
2) The MTBF of a failure which causes loss of service
to a single incoming or outgoing channel shall
be at least 3 months with an MTTR not to exceed
40 mins.
3.4.4.4.7 G̲r̲o̲u̲p̲s̲ ̲o̲f̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲
It shall be possible to divide outgoing channels and
incoming channels each into at least two groups such
that no single failure shall cause loss of service
to more than one such group.
a) The availability of the subset of the equipment
which provides service to any such group of external
connections of the maximum configuration shall
be at least 0.9999. The requirement shall be met
separately for incoming and outgoing channels.
b) The MTBF of a failure which causes loss of service
to any such group of external connections shall
be at least 1 year with an MTTR not to exceed 1
hour.
3.4.4.4.8 A̲l̲l̲ ̲C̲i̲r̲c̲u̲i̲t̲s̲,̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲ ̲a̲n̲d̲ ̲U̲s̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲n̲g̲ ̲P̲o̲i̲n̲t̲s̲
No single failure shall cause a total system failure.
a) The availability of the subset of the equipment
which provides service to all user connecting
points and external circuits shall be at least
0.99995.
b) The MTBF of a failure which causes loss of service
to all external circuits and user connecting points
shall be at least 2 years with an MTTR not to exceed
1 hour.
3.4.4.5 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲R̲e̲d̲u̲n̲d̲a̲n̲c̲y̲
3.4.4.5.1 W̲i̲t̲h̲d̲r̲a̲w̲a̲l̲ ̲o̲f̲ ̲R̲e̲d̲u̲n̲d̲a̲n̲t̲ ̲I̲t̲e̲m̲s̲
It is acceptable that redundant modules and units can
be withdrawn from use by the operational configuration
in order to perform:
a) Preventive maintenance
b) Execution of test programmes
c) Loading and check-out of new software
d) On-job training
e) Training/exercise with alternative procedures.
provided that:
- a failure, while in the degraded availability state,
shall not result in the loss of operational messages
and transaction accountability.
- the capability is maintained to re-integrate such
redundant items into the operational configuration
and return them to service within 5 minutes.
3.4.4.5.2 L̲o̲s̲s̲ ̲o̲f̲ ̲R̲e̲d̲u̲n̲d̲a̲n̲c̲y̲
With respect to redundant modules or units provided
to meet the availability and reliability requirements,
no failure shall result in the equipment being without
the complete planned degree of redundancy for longer
than 6 hours more than once a year.
3.4.4.6 S̲p̲e̲c̲i̲f̲i̲c̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
a) The reliability requirements with respect to contractor
supplied terminal equipment connected to the processor
equipment shall be as follows:
1) M̲e̲d̲i̲u̲m̲ ̲S̲p̲e̲e̲d̲ ̲P̲r̲i̲n̲t̲e̲r̲
MTBF: 3000 hrs
Downtime: not to exceed 30 mins. per month
excluding preventive maintenance.
2) V̲D̲U̲
MTBF: 5000 hrs.
Downtime: not to exceed 30 mins. per month
including preventive maintenance.
3.4.4.7 T̲e̲r̲m̲s̲
In interpreting specification and verification sections
in this paper on reliability and availability the following
terms shall apply:
a) A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲. The probability of finding an item
(system, module, unit and part thereof) in a functioning
condition at a given time.
b) C̲o̲r̲r̲e̲c̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲. The maintenance undertaken
to restore an item to a specified condition after
a failure has occurred.
c) D̲o̲w̲n̲ ̲T̲i̲m̲e̲. The time during which any of the facilities
or functions to be provided by the item is not
available, for whatever reason.
d) F̲a̲i̲l̲u̲r̲e̲. The inability of any item to carry out
its specified function within the tolerance allowed
under its normal operating conditions.
Following failure situations shall be disregarded
in availability calculation:
1) The item is or has been exposed to conditions,
which are not within the tolerances allowed
under its normal operating conditions.
2) The item is or has been exposed to violence.
e) I̲t̲e̲m̲. An item is defined as system, module, unit
and part thereof.
f) M̲e̲a̲n̲ ̲T̲i̲m̲e̲ ̲B̲e̲t̲w̲e̲e̲n̲ ̲F̲a̲i̲l̲u̲r̲e̲ ̲(̲M̲T̲B̲F̲)̲. The statistical
mean of the functioning time between failures.
For a given interval, the total measured functioning
time of the item divided by the total number of
failures of that item during the interval. Agreed
scheduled preventive maintenance of modules of
the equipment shall not be counted when estimating
mean time between failure of such modules.
g) M̲e̲a̲n̲ ̲T̲i̲m̲e̲ ̲t̲o̲ ̲R̲e̲p̲a̲i̲r̲ ̲(̲M̲T̲T̲R̲)̲. The statistical mean
of the distribution of times-to-repair. The summation
of active repair times during a given period of
time divided by the total number of malfunctions
during the same time interval. This repair time
shall include all actions required to detect, locate
and repair the fault.
h) P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲. The maintenance undertaken
systematically with the intention of keeping an
item in a specified condition, reducing the occurrence
of failures, and prolonging the useful life of
the equipment.
i) R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲. The probability that an item will
perform a required function under stated conditions
for a stated period of time.
k) R̲e̲p̲a̲i̲r̲. A repair is the restoration of an item
to the state in which it can provide its specified
functions.
When the item is a replaceable module or includes
replaceable modules, the exchange operation is
considered as the repair operation.
l) M̲o̲d̲u̲l̲e̲. A collection of one or more units as defined
in this section which satisfy the following conditions:
1) It has a functional significance in the context
of R&M.
2) Individual failures can be localised to the
specific module.
3) The module is capable of removal and replacement.
4) The module operational condition has a simple
two state classification (operative or inoperative)
in the availability calculation.
m) U̲n̲i̲t̲. This has an exclusively functional significance
in this R&M context. The smallest hardware or
software element utilized in the Reliability and
Maintainability (R&M) models. The set of all units,
taken together make up the equipment. Each unit
shall satisfy the following conditions:
1) It does not contain any portion of any other
unit.
2) The failure of the unit is independent of the
failure of any other unit.
3) The unit operational condition has a simple
two-state classification (operative or in-operative)
in the availability calculation.
4) Corrective maintenance on failed redundant
parts of a unit is performed only when the
unit containing these parts has failed.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲ ̲…01…S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲4̲.̲5̲
…02……02……02…3.4.5 Security ............................ 262
…02……02……02……02…3.4.5.1 TEMPEST Acceptance ............... 262
…02……02……02……02…3.4.5.2 Control of Record Output ........ 267
…02……02……02……02……02…3.4.5.2.1 Print-Out ................... 267
…02……02……02……02……02…3.4.5.2.2 Punched Paper Tape .......... 267
…02……02……02……02……02…3.4.5.2.3 Removable Storage Media ..... 268
…02……02……02……02…3.4.5.3 Accountability of Transaction ... 268
…02……02……02……02…3.4.5.4 Supervisory Security Monitoring . 268
…02……02……02……02…3.4.5.5 Terminal Access Control ......... 268
…02……02……02……02…3.4.5.6 Security Classification and
Special Handling ................
269
…02……02……02……02…3.4.5.7 System Design Requirements ...... 269
3.4.5 S̲e̲c̲u̲r̲i̲t̲y̲
This section addresses or references all requirements
related to security.
In general: Transfer and transmission within the installation
means transfer and transmission between the components.
3.4.5.1 T̲E̲M̲P̲E̲S̲T̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲
The components of the CAMPS equipment in the CAMPS
Main Site locations are divided in the following 3
categories.
1) 2 multi-bay EMI-rack assemblies containing: Processor
Unit, Channel Unit, TDX-Unit, Watch Dog Processor
Unit, and Disk Drives.
2) A number of terminals for maintenance and supervisory
positions, i.e. VDUs, medium speed printers and
paper tape reader/puncher.
3) Frequency stabilizers and the auxiliary equipment.
During short periods of corrective and preventive maintenance
e.g. open back doors, the emanation requirements below
are degraded.
It must be within the operational procedures, that
the supervisor is currently informed on activities
concerning corrective and preventive maintenance and
thus is able to decide whether it is acceptable to
continue operation or not.
a) To meet the NATO Security requirements, the equipment,
including ancillaries and peripherals, must be
installed in accordance with criteria laid down
in AMSG 719B. The production equipments shall be
subject to inspection and testing by ACE COMSEC
Radiation Team at the factory premises prior to
despatch/distribution to locations. After installation,
a final COMSEC Radiation Survey will be carried
out at each location prior to operational approval
being given. Rectification of the equipment characteristics
shortcomings shall be the responsibility of the
contractor.
b) Regarding of the EMI-racks, ACE COMSEC shall be
provided with tangible evidence as to their effectiveness.
Detailed design and manufacturing specification
shall be forwarded to SHAPE for evaluation. Also,
laboratory data on the shielding effectiveness
of the rack shall be provided. Finally a Quality
Plan shall be laid down to assure that all racks
are manufactured to the same performance.
ACE COMSEC has measured the ambient noise at the
factory site at Ballerup and subject to provision
of customer supplied power filtering accepted its
suitability for TEMPEST test (ref. CAMPS log 091
and CAMPS log 111). The actual TEMPEST test will
be perfomed as a qualification test by ACE COMSEC
at the factory site.
1) All equipment contained in multi-bay EMI-racks
assembly shall be TEMPEST cleared as a result
of the TEMPEST qualification test (equipment
of category 1 above). This shall include opto-electrical
interfaces.
2) Equipment of category 2 (terminals) will be
delivered with a TEMPEST clearance certification
according to AMSG720A with the understanding
that the cerfification provided will apply
to the standard approved version of the equipment.
Where modifications are required, supplementary
test data will be provided, to confirm that
the EMI integrity has been maintained.
3) Equipment of category 3 need not be TEMPEST
cleared.
During the contract phase, technical information
will be supplied to ACE COMSEC for evaluation and,
where required, a production model shall be delivered
for testing purposes.
c) S̲p̲e̲c̲i̲a̲l̲ ̲e̲a̲r̲t̲h̲i̲n̲g̲ ̲a̲r̲r̲a̲n̲g̲e̲m̲e̲n̲t̲s̲ with respect to 1)
AC power neutral, 2) safety ground, 3) Signalling
and control ground are necessary within the complete
system in order to comply with criteria laid down
in AMSG 719B. In the terminal equipments signal
common returns s̲h̲a̲l̲l̲ ̲b̲e̲ ̲s̲e̲p̲a̲r̲a̲t̲e̲ ̲a̲n̲d̲ ̲i̲n̲s̲u̲l̲a̲t̲e̲d̲
̲f̲r̲o̲m̲ ̲a̲l̲l̲ ̲o̲t̲h̲e̲r̲ ̲e̲a̲r̲t̲h̲s̲ or metal chassis (this includes
protective earth which is usually derived from
the station's main supply).
d) All electrical interconnections for data between
the equipments will use low level keying systems,
i.e. 6-0-6 volts at currents less than one milli-ampere.
All the remaining control lines should conform
to CCITT Recommendation V28.
In special cases where a line current of more than
one milli-ampere is felt necessary then the contractor
must submit his specific proposal for approval
by ACE COMSEC.
e) All electrical wiring on the red side shall be
run in a screened cable, consisting of twisted
pairs and an overall continuous n̲o̲n̲-̲f̲e̲r̲r̲o̲u̲s̲ ̲s̲c̲r̲e̲e̲n̲.
When installed, the cable will carry classified
information in telegraph and data form in the clear
text and must have been approved for this purpose
by the NATO Communications Security Authority.
The cables must receive COMSEC approval before
installation. Cable specifications and sample lengths
of not less than three metres shall be supplied
to A̲C̲E̲ ̲C̲O̲M̲S̲E̲C̲ for approval prior to installation.
1)-7) below lists the specifications, which should
be used for selection of the cable.
1) C̲a̲b̲l̲e̲
The cable shall contain 12 stranded conductors
in PVC insulated cores with a single collective
copper braid screen and overall PVC insulation.
It shall conform to the following parameters:
1) Number of strands in each conductor 7
2) Diameter of wires in core 0.2
mm nominal
3) Thickness of core insulation 0.3
mm nominal
4) Overall diameter of cable minimum 6.6
mm
maximum 7.2
mm
5) Capacitance, wire to wire, and each
wire to sheath 50
pF/metre max.
2) C̲o̲n̲d̲u̲c̲t̲o̲r̲s̲
There shall be no kinks, broken wires or other
irregularities in the conductors.
The PVC insulation is to be extruded on to the
conductors.
3) S̲c̲r̲e̲e̲n̲
The screen shall be of braided construction
and shall be formed of uniformly tinned copper
wires.
The screen shall be close fitting but it shall
be possible to slide back the screen by hand.
There shall be not more than one break in the
wires from any individual bobbin in any 25
mm length of cable.
There will be no joints in the complete braid.
The filling factor shall be not less than 0.7.
4) C̲o̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
A polyester film not thicker than 0.025 mm
shall be applied over the laid up cores in
such a manner that each turn of the tape shall
overlap the preceding turn by at least 15%.
Successive layers of cores shall be laid up
in the same direction with the layer short
enough to ensure reasonable flexibility to
the cable.
PVC filling may be used to assist in obtaining
a circular formation to the cable.
Overall insulation shall be of black PVC and
be free from inclusion and extrusion defects.
The sheath shall be easily removable from the
other component parts of the cable.
Colour coding shall be used for identification
of conductors.
5) E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲
The cable shall meet the following environmental
conditions:
Installation and operation: 0 C to 40
C, RH 10% - 88%
Storage and transportation: -30 C to 55
C, RH 10% - 98%
6) I̲n̲s̲u̲l̲a̲t̲i̲o̲n̲
The completed cable, in the dry state, shall
withstand for 1 min 1000 V rms. at 50 Hz applied
between all of the conductors connected together
and the screen.
7) P̲a̲c̲k̲a̲g̲i̲n̲g̲ ̲a̲n̲d̲ ̲M̲a̲r̲k̲i̲n̲g̲
The cable shall be delivered on disposable
drums.
Each drum shall carry 500 meters (+/-5%) of
cable in one piece and both ends of the cable
shall be suitably sealed to prevent the ingress
of moisture.
Each drum shall carry a printed label containing,
as a minimum, the following data:
1) NATO Property
2) 12W cable. CAMPS project
3) 500 metres
4) Date of manufacture (month and year)
5) NATO stock number
f) Installation of optical fibers shall be in accordance
with AMSG 719B.
g) As-built drawings and all circuit diagrams of the
first operational system, and similar material
for any variations in subsequent system to be delivered,
showing all electrical interfaces and voltages,
shall be supplied to ACE COMSEC before factory
inspection.
h) To assist in the assessment of physical security
and guarding of classified information, a list
of all items of equipment which will store, display
or record classified information shall be supplied
to ACE COMSEC by the contractor, both local and
remote. From the list, an assessment will be made
for physical security in accordance with AMSG 293D.
i) Installation work will be witnessed by local COMSEC
staff to ensure that all installation conforms
to COMSEC requirements.
j) External traffic circuits connected to the central
processor will normally be equipped with on-line
synchronous cryptographic equipment to be supplied,
installed and maintained by the purchaser.
k) The central processor will be installed in an area
designated as a Red Area. Within the Red Area classified
information may be handled in plain language; the
transfer of information in an electrical form within
this area shall be subject to and comply with the
criteria laid down in AMSG 719B.
l) The crosstalk attenuation between any circuit carrying
classified information and any other circuit within
the installation shall be not less than 100 dB.
m) Send and receive data circuits and release pulse
circuits shall be capable of producing or interpreting
signals when the pulse shape is such that the rise
and fall times, defined as the time required for
the voltage to rise or fall to 80% of its peak-to-peak
value, shall be within 5% to 15% of the unit interval
at the applicable modulation rate. Transitions
in both directions shall be approximately equal
with these limits and be equally affected by shunt
capacitance. Pulse forms shall exhibit smooth exponential
curves and contain no points of inflexion during
reversals.
n) On send circuits the pulse form shall be measured
at the line tag blocks at the Patch Test and Monitor
Facility. Limits shall be met at this reference
plan with the circuits terminated with a 5000 and
7000 ohm resistive load for the tests and repeated
with an additional shunt capacitance of 2500 picofarads.
o) The power supply to all the equipment in the Red
Area will enter via a filter or a group of filters
which will be supplied by the purchaser. The function
of these filters is to ensure that no compromising
signals are able to reach a Black Area via the
power supply leads. The equipment shall function
satisfactorily with these filters present in the
power leads.
p) The design of any maintenance facility shall incorporate
suitable security features which as a minimum shall
prevent:
1) B̲y̲p̲a̲s̲s̲i̲n̲g̲ ̲t̲h̲e̲ ̲E̲n̲c̲r̲y̲p̲t̲i̲o̲n̲ ̲D̲e̲v̲i̲c̲e̲
Any test procedure incorporating the bypassing
of the Data Encryption Devices and Isolators
shall include a positive hardware feature which
prevents the simultaneous bypassing of the
Panel Switching Equipment and the connection
of the DCE to an external telephone line.
2) I̲n̲a̲d̲v̲e̲r̲t̲e̲n̲t̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲e̲d̲ ̲a̲n̲d̲ ̲B̲l̲a̲c̲k̲ ̲W̲i̲r̲i̲n̲g̲
The test and patching facilities shall be designed
so that there is no possibility of inadvertently
connecting red and black wiring.
3.4.5.2 C̲o̲n̲t̲r̲o̲l̲ ̲o̲f̲ ̲R̲e̲c̲o̲r̲d̲ ̲O̲u̲t̲p̲u̲t̲
To facilitate control, procedures shall be implemented
which provide means for identification of:
1) Print out
2) Punched paper tapes
3) Removable storage media
3.4.5.2.1 P̲r̲i̲n̲t̲-̲O̲u̲t̲
Print-out shall carry document control number as defined
in section 3.2.3.7.2.
3.4.5.2.2 P̲u̲n̲c̲h̲e̲d̲ ̲P̲a̲p̲e̲r̲ ̲T̲a̲p̲e̲
Messages punched out shall be preceeded by 20 cms blank
tape and succeeded by 30 cms blank tape. A document
control number shall be punched in front of the message
punched out. (The number consists of 4 digits).
3.4.5.2.3 R̲e̲m̲o̲v̲a̲b̲l̲e̲ ̲s̲t̲o̲r̲a̲g̲e̲ ̲m̲e̲d̲i̲a̲
a) Units of removable storage such as a removable
disk pack shall be controlled logically by the
supervisor.
b) Logically controlled means that the supervisor
shall have commands available to control the removable
media after it has been physically mounted. Logically
controlled is as opposed to physical control, which
in principle can be performed by anyone having
physical access to the diskdrive.
c) The following procedures are implemented (refer
to supervisory functions, (section 3.2.4. 1.1.11).
1) Unit identification
2) Removal of previous stored information
3) Action on loading a unit for retrieval purposes
4) Unit directory
5) Display/print-out of stored information
3.4.5.3 A̲c̲c̲o̲u̲n̲t̲a̲b̲i̲l̲i̲t̲y̲ ̲o̲f̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲
Requirement related log and statistical information
to be complied by the system are given in sections
3.2.5 and 3.2.6 respectively.
3.4.5.4 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲S̲e̲c̲u̲r̲i̲t̲y̲ ̲M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲
All requirements related to supervisory security monitoring
are specified in detail in section 3.2.4.1.1.5.
3.4.5.5 T̲e̲r̲m̲i̲n̲a̲l̲ ̲A̲c̲c̲e̲s̲s̲ ̲C̲o̲n̲t̲r̲o̲l̲
All requirements related to terminal access control
are specified in detail in section 3.2.3.2.
3.4.5.6 S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
The classification applicable to CAMPS are the NATO
classifications specified below:
- COSMIC TOP SECRET
- NATO SECRET
- NATO CONFIDENTIEL
- NATO RESTRICTED
- NATO UNCLASSIFIED
S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
The number of special handling designators shall be
as specified in section 3.4.1.1.1.
The following designators applies:
S̲P̲E̲C̲I̲A̲L̲ ̲C̲A̲T̲E̲G̲O̲R̲Y̲ ̲W̲A̲R̲N̲I̲N̲G̲S̲ D̲E̲S̲I̲G̲N̲A̲T̲O̲R̲
ATOMAL .............................. L
EXCLUSIVE ........................... P
CRYPTO SECURITY ..................... Y
DATA MESSAGE ........................ D
Other, e.g. for exercise traffic may be specified up
to the maximum.
3.4.5.7 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲i̲g̲n̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
In this section requirements with respect to hardware
and software aspects of equipment design are given.
a) H̲a̲r̲d̲w̲a̲r̲e̲
1) A clean architectural design where unassigned
codes must cause a trap.
2) Memory bound mechanisms shall exist. The MAP
module prevents programs from being able to
write in memory occupied by the operating system
or by other application programs.
Attempt to illegally access occupied data areas
shall give rise to a warning to the supervisor.
3) Two classes of instructions, one for the privileged
use of the operating system and a user mode
used by both operating system and application
programs shall exist.
A set of privileged instructions exclusively
reserved for the operating system. These instructions
must control all I/O, the setting of memory
bounds mechanism, the setting of the system
state - privileged or user problem.
Sensitive instructions which could divert,
disrupt or inadvertently change the state of
the application software provided with CAMPS
shall not be available for execution unless
the processor is in a "privileged" state.
4) Every instruction code shall result in a prescribed
action. The occurence and/or attempted execution
of any illegal code or bit-pattern shall be
signalled and shall result in an abort procedure.
5) Key switches shall be provided on all VDU's
and medium speed teleprinters.
6) A read/write memory erase function feature
shall be provided. HW/SW techniques must be
available to the accomplishment of this function.
7) All hardware shall be individually addressable
by the computer.
b) S̲o̲f̲t̲w̲a̲r̲e̲
The following software features shall be provided:
1) All programmes and data files loaded into the
system shall carry block parity check sums
to allow the detection of corrupted data.
2) Access to CAMPS data files shall be made through
system calls which pass through the authorisation
mechanism.
3) Recovery procedures after system failure shall
include checksumming of the operating system
software, reloading if this is necessary.
4) The supervisor shall have facilities to cause
a system integrity check (i.e. checksumming
of system software) to be performed at any
time he sees fit. This shall be done without
disrupting the functioning of the system.
5) To the extent possible, the operating system
shall run in the non-privileged user state.
3.5 D̲E̲S̲I̲G̲N̲ ̲A̲N̲D̲ ̲C̲O̲N̲S̲T̲R̲U̲C̲T̲I̲O̲N̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
3.5.1 G̲e̲n̲e̲r̲a̲l̲
The following section defines the general design and
construction requirements applicable to CAMPS.
3.5.1.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲P̲r̲o̲d̲u̲c̲e̲d̲ ̲b̲y̲ ̲C̲h̲r̲i̲s̲t̲i̲a̲n̲ ̲R̲o̲v̲s̲i̲n̲g̲ ̲A̲/̲S̲
a) The CR produced equipment is designed and produced
according to CR standard.
b) This standard is based on the following NATO standards:
1) NGTS 45 General Manufacturing Requirements.
2) NGTS 50 Design, Construction and Installation
Criteria for electrical and electronic
material.
3) NGTS 40 Environmental Test Methods.
c) CR standards are currently updated in order to
incorporate improvements in technology.
d) Maintenance of CR standards are performed under
configuration management and supervised by CRs
Quality Assurance department.
e) All standards and their maintenance may be inspected
by customers Quality Assurance Representative.
3.5.1.2 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲P̲r̲o̲d̲u̲c̲e̲d̲ ̲b̲y̲ ̲S̲u̲b̲c̲o̲n̲t̲r̲a̲c̲t̲o̲r̲s̲
a) The sub-contractor supplying equipment to CAMPS
may propose the use of other standards, on condition
that adequate documentary evidence is provided
to demonstrate that the alternative standards are
at least equivalent in scope and depth of coverage
to this requirement section.
b) These proposals, if made, will take the form of
formal contract change proposals. They will not
be undertaken prior to contracting officer approval.
If the contracting officer does not approve, such
proposals shall not be implemented.
3.5.1.3 P̲r̲o̲d̲u̲c̲t̲s̲ ̲F̲r̲o̲m̲ ̲O̲t̲h̲e̲r̲ ̲S̲u̲p̲p̲l̲i̲e̲r̲s̲
a) Equipment supplied by OEMs not quoted as sub-contractors
- i.e. standard equipment from stock - is chosen
in accordance with the requirements stated compared
to the specification given by the OEMs.
b) Quality Assurance shall check and ensure that the
quality of such equipment fulfill all requirements
in respect of:
1) performance (in accordance with specifications
given by manufacturer)
2) durability
3) stability under extreme working condition
4) maintainability
3.5.2 S̲p̲e̲c̲i̲a̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲t̲h̲e̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
a) In this section is mentioned a number of requirements
special for the CAMPS project.
b) In case of conflict with the standards mentioned
in 3.5.1 above, the following standards shall supersede.
3.5.2.1 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲ ̲T̲e̲s̲t̲i̲n̲g̲
The methods of NGTS 40 shall be used for environmental
testing where they are applicable to CAMPS requirements.
As testing limits shall be used the appropriate environmental
characteristic from section 3.4.3.
3.5.2.2 U̲t̲i̲l̲i̲t̲y̲ ̲O̲u̲t̲l̲e̲t̲ ̲S̲o̲c̲k̲e̲t̲s̲
Utility outlet sockets for the operation of test equipment
etc. shall be located in close proximity to all major
racks or cabinets. Installation of utility outlets
will be the responsibility of purchaser.
3.5.2.3 M̲a̲t̲e̲r̲i̲a̲l̲s̲
Materials used for encapsulation and embedment shall
be selected for their electrical, operational, environmental
and storage characteristics. Hard curing compounds
to hold replaceable parts are prohibited. (Parts soldered
to terminals, printed wiring boards etc. are not considered
replaceable in this context).
3.5.2.4 I̲n̲t̲e̲r̲c̲h̲a̲n̲g̲e̲a̲b̲i̲l̲i̲t̲y̲
a) Modular hardware construction should be used wherever
feasible.
b) The items shall be designed to use the minimum
number practicable of the different types of electrical
cable, connectors, component and accessories.
c) Electrically identical units, assemblies, subassemblies
and replaceable parts shall be physically interchangeable
without modification of such items or of the equipment.
d) Interchangeable items shall be as defined in specifications,
drawings, and/or documentation to permit their
installation as interchangeable units, assemblies,
subassemblies, and parts without regard to the
source of manufacture or supply.
e) Provision shall be made for design tolerances such
that items having the dimensions and characteristics
permitted by the item specification may be used
as replacement without selection or departure from
the specified equipment performance.
3.5.2.5 B̲e̲n̲c̲h̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Smaller assemblies and sub-assemblies normally subject
to bench repair shall be capable of withstanding being
dropped onto a hard surface on all faces from a 30…0e…o…0f…
angle, using any one edge of the unit as a pivot, without
any physical, electrical or electronic damage.
3.5.2.6 C̲o̲v̲e̲r̲ ̲P̲l̲a̲t̲e̲s̲
Cover plates shall have a minimum of fasteners consistent
with normal mechanical strength requirements. All such
fasteners should preferably be of the "captive" type.
3.5.2.7 C̲a̲b̲l̲i̲n̲g̲ ̲a̲n̲d̲ ̲F̲i̲t̲t̲i̲n̲g̲s̲
For wiring and cabling the following shall apply:
a) Where inter-connecting cabling between assemblies
is run in steel conduit or in shielded cables,
electrical continuity of the conduit or shielding,
as appropriate, shall be ensured to permit the
correct grounding.
b) Wiring shall be identified by colour coding, numbering,
or by other feasible means such as marking of terminals
at both ends of lead. All wires shall carry corresponding
identification numbers at each end. Colour coding
for chassis wiring shall be comforming to good
engineering practice.
c) Where bus bars are used for interconnection between
assemblies and subassemblies they may be colour
coded to permit quick identification.
d) Cables and wires or similar connectors shall carry
a CR parts number. These numbers shall be the same
numbers as given in the as-built drawings and in
the maintenance and operating manuals.
3.5.2.8 F̲l̲u̲x̲ ̲a̲n̲d̲ ̲S̲o̲l̲d̲e̲r̲i̲n̲g̲
3.5.2.8.1 F̲l̲u̲x̲
Rosin fluxes conforming to recommended engineering
practices shall be used for making electrical electronic
connections. For fluxing purposes, a soldered joint
the functions of which are both a mechanical and an
electrical connection (for example in grounding applications
through a chassis) shall be considered an electrical
connection.
3.5.2.8.2 S̲o̲l̲d̲e̲r̲i̲n̲g̲
All soldered connections shall be clean and smooth
in appearance. Sufficient solder shall be used to ensure
a continuous strong concave fillet feathered into the
base metals. Flux or other foreign residue must be
removed. The insulation of soldered wires shall not
show damage from the heat of the soldering operation.
Discolouration is permitted, but not charring, cracking,
decomposition and distortion.
3.5.2.9 V̲e̲n̲t̲i̲l̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲C̲o̲o̲l̲i̲n̲g̲
a) Intake cooling air, if considered necessary, shall
be filtered such that the pressure within the associated
cabinet is higher than the ambient pressure outside.
The cooling air should preferably be exhausted
to the atmosphere at the top of the cabinet.
b) Resonance effects and vibrations because of the
ventilation and cooling shall not cause any deterioration
of equipment performance.
c) The distributed cooling systems in the CR produced
equipment may be supplied with air filters of a
nominal thickness of 2.5 cm.
3.5.2.10 E̲l̲e̲c̲t̲r̲o̲m̲a̲g̲n̲e̲t̲i̲c̲ ̲C̲o̲m̲p̲a̲t̲i̲b̲i̲l̲i̲t̲y̲
a) When installed the electromagnetic radiation of
the equipment shall comply with the COMSEC requirements
as described in AMSG 720 A and in para. 3.4.5 of
this specification.
b) When installed the different units, assemblies,
and subassemblies shall be able to perform as intended
in the presence of electromagnetic radiation from
other parts of CAMPS. Furthermore, they shall be
able to function in a radiation environment from
other system within the limits specified in 3.5.2.10.a
above.
3.5.2.11 T̲e̲s̲t̲ ̲a̲n̲d̲ ̲R̲e̲p̲a̲i̲r̲
3.5.2.11.1 A̲c̲c̲e̲s̲s̲i̲b̲i̲l̲i̲t̲y̲
a) Connections to parts inside removable container
shall be allowed to run through the container by
threading provided the container has a very low
failure rate.
b) Only chassis and assemblies contained within cabinets
or consoles shall be mounted on withdrawal slides
if they require removal or replacement during normal
maintenance and repair actions.
c) Plug-in boards and modules shall be provided with
a suitable removal tool, if they are not equipped
with build-in ejectors/extractors.
3.5.2.11.2 T̲e̲s̲t̲p̲o̲i̲n̲t̲s̲
a) Testjacks can be of the banana plug type.
b) Test points/tracing points for monitoring voltage/currents
and measuring/injecting signals/wave forms shall
only be provided to the extent they form part of
the maintenance/repair concept.
3.5.2.12 C̲o̲n̲s̲u̲m̲a̲b̲l̲e̲ ̲P̲a̲r̲t̲s̲ ̲
All fluids, life limited parts, and any other comsumable
parts required for continuous operation of the equipment
shall be kept to a minimum both in number and quantities
required.
3.5.2.13 S̲a̲f̲e̲t̲y̲
All necessary safeguards shall be taken during the
design, development, production and installation of
the equipment to ensure safety of operating and maintenance
personnel from electrical and mechanical hazards.
3.5.2.13.1 R̲e̲g̲u̲l̲a̲t̲i̲o̲n̲s̲
a) The actual site installations in the different
host nations shall be made in accordance with the
appropriate National Safety Regulations of the
country concerned according to installation drawings
as approved by the purchases.
b) The equipment itself and its associated power cabling
shall comply with the National Safety Regulations
of the country of origin for the equipment.
3.5.2.13.2 P̲e̲r̲s̲o̲n̲n̲e̲l̲ ̲S̲a̲f̲e̲t̲y̲
a) Interlocks or key locks shall be incorporated where
appropriate to prevent any major assembly carrying
high tension voltages from being opened by unauthorised
personnel.
b) With the equipment assembled and set up for operation,
personnel shall be protected from contact with
potentials in excess of 30 volts to ground, chassis
or frame, including potentials or charged capacitors.
c) Relevant notice and markings on equipment or documents
are to be provided to draw the attention of operating
and maintenance personnel to points where dangerous
voltages may be encountered.
d) Where a voltage of 50 or more volts is exposed
during the maintenance activities a suitable warning
shall be provided. It should be made according
to the following principles:
1) "DANGER (xxx) VOLTS WHEN COVER REMOVED" (in
aluminium or white lettering l.5 cm high on
a red background) where (xxx) is the nominal
voltage.
2) "DANGER HIGH VOLTAGE (xxx) VOLTS" where (xxx)
is the nominal voltage.
3) "CAUTION (xxx) VOLTS. DISCONNECT POWER BEFORE
REMOVAL OF COVER" where (xxx) is the nominal
voltage.
3.5.2.13.3 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲S̲a̲f̲e̲t̲y̲
a) Circuit breakers or switches which operate to make
or break AC power lines shall make or break all
conductors at the same time. The neutral wire in
three-phase circuits shall not pass through any
fuse.
b) Fuses and circuit breakers shall be provided within
the equipment as required for protection of the
equipment from damage due to overload. Each major
assembly shall be individually protected so that
a fault in one major assembly cannot damage any
other major assembly.
c) All fuses and circuit breakers should be located
such that they are readily accessible. Fuses shall
incorporate a visual system of failure indication.
3.5.2.13.4 G̲r̲o̲u̲n̲d̲i̲n̲g̲
a) The grounding system shall provide effective protection
for personnel and material against insulation defects.
It shall be arranged so that there are three separate
and isolated ground circuits, namely:
1) AC power neutral
2) Equipment frame ground
3) Signalling and control ground
b) The AC power neutral shall provide a return for
the primary current so that the equipment frame
ground is used only to establish a safety ground
and is not used as a normal current grounding element.
No place in the equipment or power filters shall
the AC power neutral be connected directly to equipment
frame ground.
c) All panels, drawers and other sub-assemblies, whether
fixed or removable, shall be fastened, or connected
to the associated frame, in a manner that ensures
they are securely grounded.
d) The signalling and control ground is to be routed
via the interconnecting wires and cables as appropriate.
3.5.2.14 N̲a̲m̲e̲p̲l̲a̲t̲e̲s̲ ̲a̲n̲d̲ ̲P̲r̲o̲d̲u̲c̲t̲ ̲M̲a̲r̲k̲i̲n̲g̲
A nameplate giving the serial number, SHAPE contract
number, date of manufacture, manufacturers name and
address and principal characteristics, where appropriate,
shall be attached in a prominent position on each major
assembly.
3.5.2.15 C̲o̲n̲t̲r̲o̲l̲s̲
The type and layout of controls shall be such as to
avoid an interruption of service or change of operational
mode as a result of accidental bumping, touching or
catching of clothing.
3.5.2.16 A̲c̲o̲u̲s̲t̲i̲c̲ ̲N̲o̲i̲s̲e̲
The maximum sound level due to noise emitted from the
equipment shall be less than 70 dB (A) when measured
under free field conditions by a precision sound level
meter located at a point 2 meters distant from the
noise source, and at the height at which the maximum
reading of the meter is obtained. The measuring instrument
shall be in accordance with IEC publication 179 second
edition 1973.
The contents of 3.5.3 to 3.5.10 of issue 1 is contained
3.5.1 and 3.5.2 in sunsequent issues.
3.5.11 S̲o̲f̲t̲w̲a̲r̲e̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
3.5.11.1 S̲y̲s̲t̲e̲m̲s̲ ̲P̲r̲i̲n̲c̲i̲p̲l̲e̲s̲
Fundamental properties of the software which shall
be considered in depth during the design, development
and production are its quality, integrity and flexibility.
The software shall meet the operational requirements
together with the requirements for ease of maintenance
and modification. The software shall be structured
in a clearly identifiable hierarchical way to ensure
that the integrity and reliability requirements of
this specification are met. At the same time it shall
be readily expandable and must provide the facilities
specified below in such a way that the tasks of future
modification, error elimination and maintenance are
facilitated.
a) The software shall be provided as a complete, well
structured system consisting of three s̲u̲b̲-̲s̲y̲s̲t̲e̲m̲s̲:̲
1) The system software comprises all the software
(i.e. the program code, permanent data, pre-set
work space, etc.) which is required to be resident
in or accessible to the system during its operation.
The system software shall provide the services
to the applications software.
2) The support software comprises all off-line
software required to support the implementation,
modification, testing and maintenance of the
operational system.
3) The applications software is defined as the
software providing the functional capabilities
called for in this specification.
b) The software, in conjunction with the hardware,
shall be designed to detect and limit the effect
of hardware faults which occur in the system. Upon
detection of the fault, action should be taken
to:
1) Report the fault.
2) Optimize the remaining system operational capabilities
while the fault persists.
c) The system design shall seek to maintain maximum
isolation and independence between units of all
types during program design and implementation
and during on-line operation of the system. Facilities
shall be provided by the hardware/software structure
to enforce the isolation between modules during
system run-time such as detection of program access
to an incorrect area of memory, or attempts to
make use of a machine facility to which it should
not have access.
d) In the construction of program code, clarity of
meaning shall be a major consideration. When writing
the program code comments shall be inserted to
aid comprehension and improve the readability.
e) It is mandatory that no instruction and constants
of the system software are modified during execution.
If it is done the circumstances must be well documented
and the program listing must contain complete cross-referencing
comments. In the applications software the use
of this technique shall be unacceptable.
f) The data areas of a module shall be logically contiguous
and all exchange of data between different modules
shall take place either through well defined shared
data areas or by a parameter passing.
g) The minimum program language requirements for the
software is an assembly language providing relocatable
code, symbolic addressing, and a sub-routine or
procedure concept. A macro facility is desirable
but not mandatory. The use of a high level language
is highly desirable for application programs and
desirable for system software.
h) The software shall be carefully documented in parallel
to the design during the production phase. The
documentation shall form part of the deliverable
software package and conform to the software documentation
standards specified elsewhere in this document.
3.5.11.2 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
a) The system software facilities must allow the applications
software to be structured in terms of functional
modules.
b) The system software shall include the following
general facilities in some form:
1) Multi-programming and scheduling at run time,
i.e. the provision of a set of processes or
equivalent entities as the basic entities to
which processor time, store and other system
resources are allocated at run time.
2) Store management, i.e. facilites for permanently
or dynamically allocating areas of core store
and backing store to processes or their equivalents
in a secure manner; for initializing data areas
securely when required; and for obtaining permanent
or dynamic access to such areas when required;
for ensuring the secure duplication of data
when required.
3) Device control and interrupt response, i.e.
standardized interfaces between hardware devices
(including traffic channels) and applications
software, such that the system software is
wholly responsible for the immediate control
of hardware device interfaces.
4) Inter-process interfaces, i.e. facilities for
securely passing activations and data between
processes over standardized interfaces.
5) Fault handling, e.e. facilities for the detection,
location and containment of software and hardware
faults: for ensuring the secure duplication
of data when required by applications or system
software in case of fault conditions; for maintaining
system operation and data integrity during
fault incidents (in conjunction with applications
software); and for providing adequate reports
of fault incidents for subsequent diagnosis
and correction of the faults.
c) The system software shall be implemented as a well-structured
suite of code and data modules incorporating sufficient
hardware protection and software checking to ensure
that:
1) The system software itself can achieve and
maintain the status of high integrity, trusted
code with respect to the applications software.
2) The structures present in the applications
software are maintained and enforced at all
stages of development, integration and run
time operation.
Preferably, the system software shall reside
in "read-only" memory.
d) The support element of the system software must
allow the secure preparation, editing, compilation,
linkage, module testing, integration, realtime
testing, system testing and incorporation into
run time operation of new or modified source code
modules. Any disturbance caused to the operational
system by each of these procedures should be minimal
and well defined. The support software shall include
facilites for maintaining and accessing any required
off-line libraries of procedures, data declarations,
macros, etc.
e) The use of the word secure in section 3.5.11.2
refer to requirements stated in section 3.4.5.7
and 3.5.11.
3.5.11.3 A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The application software shall be provided as well-structured
modules. The application software is to provide, in
conjunction with the system software, all the functional
capabilities called for in this specification. The
application software for each installation shall be
identical or, as a minimum, generated from a common
library of program routines.
a) O̲v̲e̲r̲a̲l̲l̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲. The applications code and data
shall be structured in a hierarchical manner into
a well defined set of functional modules and units
at different functional levels and with distinct
data areas for each transaction processed by the
system.
The ways in which the various applications software
modules are multi-programmed at run-time (i.e.
recursive/re-entry or "fresh copy", etc.) shall
be clearly defined.
Communication between modules shall wherever practicable,
take place via standardised system facilities such
as interprocess calls and procedure calls. The
sharing of data areas between two or more units
or modules handling different transactions shall
be avoided and the situations in which such sharing
takes place shall be clearly defined. It shall
be a design aim to ensure that whenever data is
transmitted across an inter-module interface, the
data is in a compact, well defined form.
Sufficient validity checks must be applied at appropriate
points in the applications software and/or system
software at compile time, and/or runtime to ensure
that the integrity requirements will be met, attention
being paid to maintaining efficiency.
The process of integrating a module into the system
shall not require recompilation of the other elements
of the system.
b) M̲o̲d̲u̲l̲e̲s̲ ̲o̲f̲ ̲A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲. It shall be a
design aim that each functional module of applications
software should satisfy the following criteria:
1) Provide a well defined function or group of
functions at some hierarchical level in the
software system, i.e. can be implemented as
self-contained programming task given a functional
specification, interface specifications of
any external modules and data structures to
which it must refer.
2) Has well defined, compact input and output
interfaces.
3) Can be separately compiled/assembled.
4) Hides its decisions from other modules (e.g.
it allows access to internal data structures
only through one access mechanism provided
by the module).
3.5.11.3.1 I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
a) U̲s̲e̲ ̲o̲f̲ ̲L̲a̲n̲g̲u̲a̲g̲e̲s̲
If a high level language is used, the use of assembly
language in the applications software shall be
confined to small well defined units and where
practicable embodied either in macros or library
procedures. In any case the use of assembly/machine
code should be restricted to the following circumstances:
1) Interfacing to system software calls.
2) Providing realtime critical facilities where
code produced by the high level language compiler
is too inefficient.
3) Implementing essential facilities not provided
by the high level language or the rest of the
system.
b) P̲r̲o̲g̲r̲a̲m̲s̲
It is mandatory that programme instructions shall
not be modified during run time and that within
each applications software module the programme
code and constants should be segregated from the
modifiable data. It is highly desirable, that,
wherever practicable, each segment of applications
code or data should be accessed and protected by
appropriate hardware facilities at run time. The
direct use of or access to absolute store addresses
by applications programmes should be reduced to
a minimum. Synchronization processes shall take
place at clearly defined points in the programme.
To maintain security and accountability, reservation
and release of shared resources, such as data areas,
must only take place at clearly defined points
in the applications programme.
c) M̲o̲d̲u̲l̲e̲ ̲S̲i̲z̲e̲ ̲C̲o̲n̲s̲t̲r̲a̲i̲n̲t̲s̲
The function of each module should be readily understandable.
As a rule, no module shall contain more than 250
source statements unless approved by CR QA internally
and notification to SHAPE. It shall be a design
aim to limit the number of modules, exceeding the
250 line limit to 5% of the modules. Each module
must implement a CAMPS function or function(s)
as specified in this document. Any requirement
which would lead to implementation of a module
unable to satisfy this constraint must be sub-divided
into more manageable units. It is essential that
any constraints imposed on the module size by compilers,
loading methods, store management arrangements,
etc., must be clearly defined and adequate methods
for dealing with these constraints must be defined
and implemented.
d) M̲a̲n̲/̲M̲a̲c̲h̲i̲n̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
In addition to the levels of command and control
specified elsewhere in this specification for supervision/operation,
and control for engineers limited facilities shall
be provided at operational sites for control of
system software. Provisions shall be made for dead
start, warm start, and cutover to an updated version
of the control software, the latter without affecting
the operational user facilities. In addition, the
supervisor shall have facilites to record the
current state of the machine for diagnostic purposes
on a loadable medium in a secure manner, e.g.,
raw dumps on a hardcopy printer are not acceptable.
This facility shall be available without affecting
user operational facilities.
3.5.11.4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲a̲n̲d̲ ̲M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The systems software shall be structured in a way that
will permit the addition or deletion of applications
units throughout the operational life of the system.
The degree of flexibility should at least be sufficient,
to allow:
a) Changes in format, new formats, changes in format
tolerances, improvements in man/machine interfaces,
and the accommodation of more CAMPS hardware.
b) Processing information which may be subject to
change, for example, specific character strings
such as security examining groups, which are searched
for during analysis, should wherever possible,
be held in specific data tables rather than embodied
in the program source code in order to preclude
unnecessary compilation/assembly of program modules.
3.5.11.5 S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
a) The support software includes all off-line software
required to support the implementation, modification
testing and maintenance of the on-line system.
All support software shall be available at the
CAMPS software support installation (CSSI), while
only that related to installation of changes and
assisting in fault finding is necessary at the
operational sites.
b) Any disturbance caused to the operational system
by use of the support software shall be minimal
and well defined. New code and data shall be transferred
to an operational installation on a machine readable
medium generated at the CSSI.
3.5.11.5.1 C̲S̲S̲I̲ ̲R̲e̲s̲i̲d̲e̲n̲t̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
At the CSSI site the support software shall as a minimum
accommodate the following functions:
a) Compilation/assembly shall be accomplished on the
CSSI system. Appropriate diagnostics shall be provided
when compilation/assembly cannot be carried out
successfully. Compilers/assemblers must make adequate
provision for insertion of programmers' comments.
b) Library maintenance - routines for the creation
and maintenance of the programs and other libraries
as applicable.
c) Data conversion shall be made for the transcription
and re-formatting of data from disc to floppy disc
and vice versa.
d) A debugger shall be provided at the CSSI. This
debugger shall together with a facility for simulation
of modules under test aid the programmer in testing.
The debugger shall support insertion of breakpoints,
dumps of registers and memory. Further the following
shall be supported from the terminal conducting
the test.
1) Display of memory or register dumps on the
console, VDU, and/or medium speed printer.
2) Updating the contents of main memory areas
and registers.
3) Transcription of the main memory contents to
or from backing store.
4) Loading of programs to be tested.
5) Program initiation and termination.
6) Deletion of main memory contents.
7) Recording of software modules being accessed
during test.
e) Loaders, editors and other utility programs which
are necessary to facilitate the compilation assembly
and testing of program changes in an efficient
and timely manner.
f) A cross reference listing tool which allows the
determination of which modules might be affected
by a programme change.
g) At the CSSI site a test and integration facility
shall be provided which in conjunction with other
CR supplied equipment can run the software module
under test as if it was part of an operational
CAMPS.
3.5.11.5.2 F̲a̲c̲t̲o̲r̲y̲ ̲T̲e̲s̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
a) At the CR factory a factory-test simulator shall
be provided to run the software under test emulating
the operational CAMPS environment.
b) The standard test environment shall be provided
by simulation of pseudorandom operational environment
in the factory such that:
1) All input channels are loaded to at least 0.5
Erlangs for low speed channels and 0.3 Erlangs
for medium speed channels.
2) The traffic input on the channels shall be
representative of the message traffic which
will be encountered in an operational environment,
including traffic corrupted by transmission
media failure and noise.
3) The following traffic sources shall generate
simulated traffic in accordance with the throughput
requirements in section 3.4.1.2.1.
- Message preparation facilities.
- Traffic exchanged with ACE CCIS facilities.
- Traffic exchanged with SCARS II.
- Traffic associated with message service
and operator distribution control facilities.
c) The simulation shall be performed under the restraints
defined below:
1) All of the following stores are loaded to at
least 0.75 of the design capacity.
- In-transit store for messages being processed.
- Queue storage.
- Message on-line storage.
2) At least 0.9 of all available output channels
shall be open.
3) All operator positions shall be manned so that:
- action can be taken with respect to situations
which arise in the equipment. The action
taken shall be that appropriate to an operational
environment.
- all available commands are used to exercise
the equipment.
3.5.11.6 S̲o̲f̲t̲w̲a̲r̲e̲ ̲I̲n̲t̲e̲g̲r̲i̲t̲y̲
a) Re-loadable copies of all the software in binary
form shall be held on backing store (e.g. disc,
magnetic tape on-line to the system) to permit
replacement of the software if it is suspected
of being corrupt.
b) Each module should contain credibility check to
contain the effects of corrupt or inaccurate data
to the extent this does not introduce redundant
processing which will decrease the system throughput.
c) It shall be a design aim that wherever possible
the consequence of a single software fault incident
will not affect more than one transaction. The
detection of an inconsistency indicating a fault
shall initiate a report and the re-processing from
a validated check-point in an attempt to recover
with a minimum of discontinuity. Only after further
failures should major recovery or operator intervention
action be invoked.
3.6 D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
3.6.1 G̲e̲n̲e̲r̲a̲l̲
a) Hardware documentation developed by CR under this
contract will be produced in accordance with the
requirements as stated in this section of the System
Requirements Specification. Documentation for
OEM equipment will be delivered according to the
requirements as stated in the contract.
b) Software documentation developed by CR under this
contract will generally be produced in accordance
with the structure of ACE directive 007-3 issue
2.
c) System Requirements Specification developed under
this contract shall be produced and maintained
in accordance with MIL SPEC 490 unless otherwise
specified in the Configuration Management Plan.
3.6.2 F̲o̲r̲m̲a̲t̲ ̲a̲n̲d̲ ̲P̲u̲b̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲r̲i̲t̲e̲r̲i̲a̲
All documentation delivered by the contractor shall
be prepared in accordance with the following requirements.
3.6.2.1 P̲a̲p̲e̲r̲
The documents, exclusive of covers, shall be printed
on a good grade of white paper of sufficient weight
and substance to permit printing on both sides. The
paper size will be DIN A4. The paper used for fold-out
drawings shall be of a quality and thickness that permits
repeated opening and folding without cracking or tearing
at the folds.
3.6.2.2 B̲i̲n̲d̲i̲n̲g̲
a) The documents shall be bound between hardbacked
covers that incorporate a metal binding system
which will permit easy removal and insertion of
pages, photographs, illustrations and drawings
and which will permit the documents to lie flat
when opened at any page.
b) The information on pull-out sheets bound in the
hard-backed covers shall be positioned so that
it is clear of the text of its associated document
when opened up so that the reader can readily cross-refer
between text, drawings and illustrations.
c) If they are not accountable items for security
reasons, excessively large drawings may be placed
in pockets formed in the rear covers of binders,
or in the case of, as-built and installation instructions,
to contain large drawings in separate folders equipped
with a fastening arrangement to prevent accidental
loss and spillage of the contents.
d) The cover and title page of the document shall
show the classification of the document, manufacturer
of the equipment, number of the document and its
issue number, number of the contract and the date
of issue. In the case that a subject is covered
in more than one volume then an indication of the
contents of each manual shall be shown. The title
and number of the document shall also be shown
on the spine of the cover if applicable.
3.6.2.3 N̲u̲m̲b̲e̲r̲i̲n̲g̲
a) The pages of Sections and Chapters are to be separately,
and sequentially numbered beginning with the number
one in each case, with the associated Section or
Chapter number added as a prefix. The page numbers
are to be inserted at the centre of the lower margin
above the classification, or in the appropriate
box if preprinted formsheets are used.
b) Paragraphs, sub-paragraphs, and sub-sub-paragraphs,
are to be numbered sequentially commencing with
one, and sub-paragraphs are to have the associated
paragraph number added as a prefix (i.e. 1.1.,
1.2., 1.3., etc.) and sub-sub-paragraphs, the associated
sub-paragraph number added as a prefix (i.e. 1.1.1.,
1.1.2., 1.1.3. etc). The maximum depth will be
4 (i.e. 1.1.1.1) unless otherwise agreed.
c) For sub-divisioning identification, lower-case
alphabetical characters enclosed in half brackets
shall be used (i.e. a), b), c), etc.). For Sub-sub
divisioning, upper-case Arabic numerals enclosed
in half brackets shall be used (i.e. 1), 2), 3),
etc).
d) Tables shall be captioned and allocated a Table
Number having the Section or Chapter number as
appropriate added as a prefix (e.g. Table 1.1).
Tables may be included as a part of the text or
printed on a fold-out sheet. When printed on a
fold-out sheet, the table number must be positioned
on the fold-out portion so that it is visible on
opening the document to which it belongs.
3.6.2.4 P̲r̲e̲f̲a̲c̲e̲
a) Each separately bound document (manual) shall commence
with a set of introductory pages, and when a manual
or set of documentation consists of only one separately
bound document, the introductory pages shall consist
of the following:
1) Title pages with the security classification
of the handbook, manufacturer of the equipment,
number of the handbook and its relevant issue
number, number of the relevant contract and
date of issue.
2) When applicable, instructions covering treatment
for electric shock.
3) Amendment history sheet.
4) Record of modifications to the equipment.
5) Introduction giving the purpose of the handbook
and instructions for its use.
6) Table of contents listing the titles of all
sections, headings and sub-headings, together
with relevant paragraph and page numbers.
7) Detailed list of all tables together with relevant
table and page numbers.
8) Detailed list of all drawings, illustrations
and photographs together with a relevant reference
and page numbers.
9) Legend explaining all abbreviations and symbols
used in the text and on the drawings.
10) Photographs or drawings of the major items/bays
described in the handbook.
b) When a manual or set of documentation consists
of more than one volume, each separately bound
volume, section or part, shall contain a set of
introductory pages as described, plus an additional
page inserted after the front sheet containing
an abbreviated list of contents for the complete
manual or set of documentation, as applicable.
c) Wherever possible, photographs, drawings and illustrations
shall be bound in the same cover as the associated
text. In addition when a manual or set of documentation
consists of more than one separately bound document
the first document of the series shall be identified
as the master document and shall contain all information
of a general nature applicable to all documents
of the series.
3.6.2.5 P̲r̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲T̲y̲p̲e̲
A conventional typewriter font shall be employed for
the printing of all letters and figures in the text
of all documents.
All titles and headings shall be underlined.
Operation and maintenance manuals shall be printed
using either a multilith or offset process.
3.6.2.6 L̲a̲n̲g̲u̲a̲g̲e̲
All documents shall be written in the English language.
All descriptions shall be written in a clear and precise
manner, using unambiguous English and a minimum of
words. Wherever feasible descriptions and procedures
shall be supported either by diagrams and photographs
or other types of illustrations to facilitate understanding
of the text by personnel having only a working knowledge
of the English language.
3.6.2.7 S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Manuals and documents shall be classified in accordance
with the classification of the information included
therein. The relevant classification of a document
shall be printed at the centre top and bottom of all
pages, photographs, illustrations and drawings, and
at the centre top and bottom of the front cover of
all binders. The highest classification of any section
of a document shall be printed on the cover of that
binder.
Applicable document for security classification is
NATO Document CM(55)15 Final "Security within the North
Atlantic Treaty Organization".
3.6.2.8 P̲h̲o̲t̲o̲g̲r̲a̲p̲h̲s̲,̲ ̲I̲l̲l̲u̲s̲t̲r̲a̲t̲i̲o̲n̲s̲ ̲a̲n̲d̲ ̲D̲r̲a̲w̲i̲n̲g̲s̲
a) All titles and included text and annotations shall
be in the English language in addition to any other
language that may be employed. To facilitate correlation
the figure numbers are to be preceded by the associated
chapter or section number as appropriate (e.g.
Figure 1.1).
b) The lettering and layout of drawings shall be in
accordance with recognized industrial or national
standards. Hand lettering shall be avoided except
on advance information copies and for marking-up
ATBB documents during site implementation.
c) Symbols, when employed, shall be defined so that
there can be no confusion in their interpretation.
The definitions may, at the discretion of the contractor,
be given on the drawings or collectively in the
associated document in the form of a glossary.
d) The use of drawings and illustrations that exceed
1 x 1.5 metres shall be avoided. Where necessary
the scale shall be shown.
3.6.2.9 A̲m̲e̲n̲d̲m̲e̲n̲t̲s̲
The contractor shall be responsible for the issue,
control and distribution of amendments to all delivered
documents, resulting from changes and/or modifications
in the equipment or spare parts, until expiration of
the warranty period for the associated equipment. In
the case of the training documentation the contractor
shall be similarly responsible until the end of the
first training year.
3.6.2.10 L̲e̲v̲e̲l̲s̲ ̲o̲f̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Documentation shall be written to be in keeping with
all the levels of maintenance as outlined in contractor's
maintenance plan.
3.6.2.11 U̲s̲e̲ ̲o̲f̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
To avoid duplication of information references to other
parts of the documentation may be made.
3.6.3 A̲p̲p̲r̲o̲v̲a̲l̲ ̲a̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
Approval and delivery of documentation will be in accordance
with paragraph 15 Special Provisions under this contract
unless otherwise agreed or stated in this section.
a) Six months before the provisional site acceptance
(PSA) of the first site four copies of each draft
document shall be submitted to the purchaser for
review. The resulting recommended changes shall
be considered and incorporated by the contractor
who shall re-submit one copy of the revised document
for printing approval. Upon receipt, in writing
from the purchaser, that the contents of the revised
version contain all of the purchaser's recommended
correcti- ons, changes and comments to his satisfaction,
the contractor shall be responsible for the editing,
production and delivery of the required number
of the documents. The contractor shall provide
page changes or if necessary shall re-issue portions
of the documents whenever changes/modifications
in equipment or spare parts are made.
b) In the event that approved copies are not available
at the time of on-site acceptance of equipments,
preliminary version of each document (advance information
in sufficient detail to permit satisfactory operation
and maintenance of the equipment) shall be provided
to each site at the time of the provisional site
acceptance.
c) Q̲u̲a̲n̲t̲i̲t̲i̲e̲s̲
The contractor shall deliver the following quantities
of handbooks (i.e. Equipment, maintenance and Test
Equipment Handbooks).…06…1 …02… …02… …02… …02…
T̲O̲ D̲R̲A̲F̲T̲ ̲P̲R̲E̲L̲I̲M̲I̲N̲A̲R̲Y̲ ̲V̲E̲R̲S̲I̲O̲N̲ F̲I̲N̲A̲L̲ ̲V̲E̲R̲S̲I̲O̲N̲
Each Site 0 2 (each) (Delivery
2
weeks
before
PSA)
Purchaser 4 (each) Delivery 6 months 5 (each)
"
before PSA of first site
NCS 0 20 (each)
"
3.6.4 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲s̲
3.6.4.1 C̲R̲ ̲P̲r̲o̲d̲u̲c̲e̲d̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Equipment handbooks shall be prepared for all main
and miscellaneous equipment supplied. The equipment
handbook shall contain as a minimum:
a) Equipment Specifications.
b) Installation and Commissioning Instructions.
c) Operating Instructions.
d) Technical Description.
e) Parts Lists.
3.6.4.1.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
a) This section shall contain a listing of all the
important parameters of the described equipment.
It shall include but not be limited to the following:
b) The required external power supply voltage and
frequency characteristics with acceptable tolerances.
c) Power consumption, ventilation and environmental
control data.
d) Characteristics and acceptable tolerances of all
input and output signals.
e) The environmental conditions over which the equipment
performance will continue to meet the design performance
criteria.
f) The overall weight and the weight of each typical
unit or sub-unit.
g) The overall dimensions and the dimensions of each
major unit or sub-unit.
3.6.4.1.2 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲C̲o̲m̲m̲i̲s̲s̲i̲o̲n̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲s̲
a) This section shall include the electrical and mechanical
information necessary for mounting and demounting
the equipment especially:
b) Detailed mechanical installation instructions.
c) Detailed external and inter-unit cabling instructions,
including earthing connections.
d) Specification of the cables to be used.
e) A detailed list of checks to be carried out prior
to application of power for the first time.
f) A detailed list of checks to be carried out following
the application of power and prior to putting the
equipment into service. Where these checks are
identical to the maintenance procedures references
shall be made to the maintenance procedures. Duplication
of the text is not required.
g) List of tools and test equipment required for installation,
commissioning and check-out of the equipment.
3.6.4.1.3 O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲s̲
a) The operating instructions shall be detailed and
cover all applicable equipment both central computer
and peripherals.
b) Operating instructions shall include the basic
functions such as:
1) Power ON and OFF.
2) Emergency power OFF.
3) Interpretation of alarm and warning conditions
and associated immediate action instructions.
4) Description of controls and indicators.
c) A user's manual will be written for the following
user categories:
1) CAMPS operator.
2) CAMPS supervisor.
3) CAMPS supervisor assistant.
d) The user's manual will describe all the functions
of the CAMPS System and illustrate how to operate
it.
3.6.4.1.4 T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) The depth of description will be in accordance
with the level of maintenance as outlined in contractor's
maintenance plan.
b) First section will give a general introduction
to the equipment and explain its purpose. It shall
give a brief description covering the overall physical,
electrical and electronic characteristics as applicable,
using as back-up information block diagrams, photographs
or other suitable illustrations.
…86…1 …02… …02… …02… …02…
c) Subsequent sections will describe the major elements
and assemblies, and present the overall functional
description of the system.
d) The object of the Technical Description is to provide
sufficient technical information to operating and
maintenance personnel to enable them to understand
and use the Maintenance Handbooks and Operating
Instructions respectively.
3.6.4.1.5 P̲a̲r̲t̲s̲ ̲L̲i̲s̲t̲
This section shall consist of a tabulation following
a "family tree" type breakdown of all parts for the
described equipment, and shall provide the following
information.
a) Manufacturer's part number and an associated brief
descriptive phrase for each major assembly.
b) The component reference number as used on the
circuit diagrams for all electrical/electronic
components parts. Each reference number shall
be followed by a brief descriptive phrase,
nominal value, rating and tolerance of the
associated component, together with the manufacturer's
reference number and manufacturer's address
or NATO code (if readily available).
c) Manufacturer's part number and an associated
brief descriptive phrase for each mechanical
part, together with the manufacturer's address
for each item listed.
d) A list of the sizes and types of nuts, bolts,
washers and fasteners supplied as a repair
kit to each site and depot.
3.6.4.2 O̲E̲M̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Handbooks and other relevant documentation for peripherals
and test equipment supplied shall be delivered in accordance
with the terms of the contract.
Contents of the documentation must be relevant to the
supplied equipment, and will be identical in scope
wherever applicable to that described in 3.6.4.1. The
applicability can be met either by the contents itself
or by marking up the document in a clear and unambiguous
way. Such markings shall be consistent with good legibility,
readability and utility of the end product.
3.6.5 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲
The maintenance procedures handbook is the basic document
which outlines how the maintenance of the system will
be effected. It shall be, in effect, the final version
of the contractor's maintenance plan. It shall be the
one document which will give precise instructions to
a technician as to how he will fulfil his responsibilities.
Drawings, illustrations and photographs used in connection
with maintenance will permit identification of the
location of all replaceable units to permit a technician
to repair and to satisfactorily maintain the equipment.
Equipment layout drawings, inter-unit and sub-unit
cabling and wiring diagrams shall be provided for all
electrical and electronic assemblies. Annotated line
drawings, annotated cut-away illustrations, and annotated
photographs, as appropriate, shall be provided to permit
identification of all mechanical assemblies and mechanisms
and parts thereof. As a minimum the following drawings
shall be included:
a) Block diagram of the whole equipment.
b) Block diagram of assemblies divided into units.
c) Block diagram of major units.
d) Detailed interconnection diagrams and internal
cabinet cabling diagrams including the views of
plug-in connectors.
e) If applicable, flow diagrams of the signals through
the equipment will be shown as part of the fault
isolation procedure.
f) Circuit diagrams of all units and subassemblies
will be supplied as part of the depot maintenance
documentation.
3.6.5.1 P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
The preventive maintenance instructions shall contain:
a) All recommended routine maintenance tasks necessary
to ensure continuous and satisfactory performance
of the equipment, based on the periodicity of maintenance
(i.e. daily, weekly, monthly etc.).
b) Illustrations and test set up schematics shall
be included to ensure that the procedures can be
understood by the CAMPS technician.
c) All test points clearly identified. The nominal
values and the acceptable limits that should be
measured at each test point shall be indicated.
d) The document shall include system and sub-system
alignment procedures.
e) Where necessary, reference shall be made to other
documentation where more detailed information regarding
the maintenance task may be found.
f) List of all required tools and test equipment supplied
for maintenance purposes.
g) Dismantling and re-assembly instructions shall
be given where applicable.
h) Procedures for adjusting factory sealed controls
and mechanisms are also required and shall include
statements giving the levels of maintenance where
these adjustments would normally be performed (i.e.
depot, etc.).
3.6.5.2 C̲o̲r̲r̲e̲c̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
The corrective maintenance instructions supplied to
each site will reflect the level of maintenance applicable
to CAMPS, i.e. module replacement.
The corrective maintenance instructions shall contain:
a) Detailed descriptions of the symptoms of a fault
to include alarm conditions if applicable.
b) Description of the possible fault isolation methods
and tools used in connection with fault isolation.
c) Comprehensive procedures for fault tracing and
fault isolation.
3.6.5.3 A̲s̲s̲o̲c̲i̲a̲t̲e̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Appropriate documentation, either in the form of the
manufacturer's handbook or leaflet, shall be provided
where applicable for each delivered item of test equipment.
Similarly, documentation shall be provided for those
tools, other than simple hand tools, which require
operation and maintenance instructions, when full information
is not given in the Maintenance and Operating Manual.
3.6.6 E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲D̲r̲a̲w̲i̲n̲g̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
3.6.6.1 C̲i̲v̲i̲l̲ ̲W̲o̲r̲k̲s̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The civil works requirements are to be provided by
contractor 12 months prior to equipment installation
at each site. This document should, as a minimum,
be in the form of engineering sketches and written
text describing all civil works that need to be accomplished
to prepare the site for contractor equipment installation.
This documentation must be in sufficient technical
detail to instruct a civil works contractor in the
work to be performed.
3.6.6.2 A̲s̲-̲t̲o̲-̲b̲e̲-̲B̲u̲i̲l̲t̲ ̲a̲n̲d̲ ̲A̲s̲-̲B̲u̲i̲l̲t̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
a) This documentation shall provide full details of
how all the major assemblies of the supplied equipment
at each location have been physically installed
and electrically integrated. They will be supplied
by CR as two deliveries:
1) As-to-be-Built drawings (due nine months before
scheduled start of equipment installations).
2) As-Built Drawings (due at time of PSA).
b) These documents shall be self sufficient and not
depend on any other documents other than the supplied
maintenance manual and equipment handbooks. If
reference to another document is unavoidable, then
a copy of, or a pertinent extract from the reference
document shall be included. These documents shall
be prepared for each location and include all relevant
information covering the following:
1) Floor and wall plans showing all cable runs
within the CAMPS equipment room. Cable runs
must be CAMPS related or have COMSEC implications.
Signal cable runs from CAMPS equipment room
to user terminals shall be incorporated in
the as-to-be-built and as-built documentation.
(Information on the routing of the cable-runs
will be provided by customer).
2) Plan showing grounding system related to CAMPS
with description of conductors, electrodes
and joints. Drawings and specifications to
be provided by customer.
3) Cable racking and cable runs with cable numbers
and cable functions to include as appropriate
all terminating points, connections, connectors
and sockets. The functions of all conductors
shall be shown.
4) Physical layout (plan and elevation) of all
major equipments.
5) Ventilation and environmental control systems
that impact on COMSEC. Drawings and specifications
to be supplied by customer if installed or
modified after site survey.
6) Cross-connection frames and patch panel details.
7) Power distribution boards, cabling, wiring
and distribution schemes showing position of
filters if fitted. Drawings and specifications
to be supplied by customer.
8) Ancillary equipment that have COMSEC implications.
Drawings and specifications to be provided
by customer if installed or modified after
site surveys.
9) Layout and cable runs of all intercom equipment
having a COMSEC impact relative to CAMPS equipment.
Drawings and specifications to be supplied
by customer if installed after site surveys.
10) All other information necessary for the Purchaser
to operate, maintain, and expand or modify
the installation.
3.6.7 I̲n̲v̲e̲n̲t̲o̲r̲y̲
3.6.7.1 G̲e̲n̲e̲r̲a̲l̲
The contractor shall prepare a property inventory for
each CAMPS site.
3.6.7.2 P̲r̲o̲p̲e̲r̲t̲y̲ ̲I̲n̲v̲e̲n̲t̲o̲r̲y̲
a) The contractor shall prepare a property inventory
of each site and shall deliver them to the related
sites before provisional site acceptance (PSA).
b) The inventory shall be prepared in block form and
shall consist of the following sections, as applicable:
1) Main Equipment.
2) Ancillary Equipment.
3) Test Equipment.
4) Technical Furnishings (tools etc.).
5) Spare Parts (Site and Depot).
6) Installation Material (Cable and Hardware).
7) Documentation (Handbooks and Drawings, Installation
Drawings, and Plans, As Built Drawings, Cable
and Wiring Diagrams).
c) For each applicable item a family tree breakdown
of the equipment (from main equipment, major assembly,
sub-assembly items etc. down to module PC board
level) shall be given in the inventory.
d) The inventory information, shall include as a minimum
the following data elements:
- Site
- Item Number
- Description
- True Manufacturer's Part Number
- Manufacturer's Identification Code
- Quantity
- Price
- NATO Stock Number (as available)
- Item Serial Number (for test equipment and
for major assemblies)
- Working or Spare
- Remarks
e) The inventory shall be checked against the installed
equipment at time of PSA and changed as necessary.
The marked up copy shall then form the official
record of all equipment and other items that have
been delivered. The deliverable final inventory
will be submitted in the form of a hard copy list
subsequent to SPA.
3.6.7.3 F̲i̲n̲a̲l̲ ̲I̲n̲v̲e̲n̲t̲o̲r̲y̲ ̲(̲o̲p̲t̲i̲o̲n̲a̲l̲)̲
An Optional Final Inventory will be prepared by contractor
in a form compatible with the purchaser's computer
punch cards or magnetic tapes with a hard copy. This
inventory will be made based on the hard copy inventory.
Work on the Optional Final Inventory will be initiated
after basic contract has been appropriately amended.
3.6.8 F̲a̲c̲t̲o̲r̲y̲ ̲a̲n̲d̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
3.6.8.1 G̲e̲n̲e̲r̲a̲l̲
As stated in section 4 of System Requirements Specification
the delivered equipment will be tested to verify its
compliance with the contractual requirements.
The quality and quantity of documentation produced
and delivered by contractor for class II tests is determined
solely by the extent to which customer and contractor
has agreed to test the equipment (i.e. requirements
stated in System Requirements Specification).
The documentation requirements listed below are applicable
for the tests conducted according to the test plan.
Documentation for class I test (contractor's internal
verification) will be developed for in-house use only.
3.6.8.2 P̲r̲o̲t̲o̲t̲y̲p̲e̲ ̲T̲e̲s̲t̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
Documentation for the following class II tests will
be submitted by contractor:
- DSMT (Prototype) System Verification
- Availability Verification
- In-Plant Software Verification
- Software Functional Verification
- Software Operational Verification
Detailed test requirements will be described in the
System Integration and Test Plan.
3.6.8.3 F̲a̲c̲t̲o̲r̲y̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
Factory Acceptance Test Document shall contain the
procedures for the tests that have to be performed
on each equipment and its associated accessories following
manufacture to ensure that all items to be delivered
are in accordance with the requirements of the contract
prior to shipment from the factory.
3.6.8.4 S̲i̲t̲e̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲a̲l̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲ ̲(̲S̲P̲A̲)̲
This document shall contain all test procedures and
inspections that are necessary to verify that the equipment
has been correctly installed and aligned. It shall
also contain a check list of all items that should
be supplied under terms of the contract such as accessories,
spare parts, tools, test equipment and documentation.
(For a brief description of the SPA test see section
4.2.3.2 of System Requirements Specifications).
3.6.8.5 T̲e̲s̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
Each procedure shall, where applicable, include as
a minimum the following:
a) The title of the proposed procedure and a list
of all required test equipment, where applicable.
b) Required test limits, where applicable.
c) A detailed step-by-step procedure written so that
the procedure can be understood by technician.
d) A block diagram of the required test set-up if
more than two test connections are involved.
3.6.8.6 T̲e̲s̲t̲ ̲R̲e̲s̲u̲l̲t̲ ̲F̲o̲r̲m̲s̲
The Test Results Forms to be used in conjunction with
the test procedures may be part of the test procedure
itself. They shall contain as a minimum a space for
inclusion of:
a) Test location and date.
b) Equipment type and serial number(s).
c) Test procedure reference number and issue number.
d) Type of test equipment employed.
e) Test Results.
f) Comments.
g) Signatures of official representatives of the contractor
and the purchaser.
3.6.8.7 A̲p̲p̲r̲o̲v̲a̲l̲ ̲a̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
A copy of each class II test document complete with
samples of the associated test result forms, shall
be submitted to SHAPE for approval at least thirty
days before the scheduled date for commencement of
the associated tests. Submittal will take place only,
if SHAPE has not previously approved the document.
SHAPE and the contractor shall mutually agree on any
changes to the scope and content during the period
between submission of the test procedures and the scheduled
date for commencement of the associated tests.
3.6.9 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
3.6.9.1 G̲e̲n̲e̲r̲a̲l̲
CR will produce all future CAMPS related software documentation
in accordance with ACE directive 007-3 issue 2, dated
14th January 1980.
3.6.9.2 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The CAMPS software documentation shall be structured
in a hierarchical system of levels in accordance with
the hierarchical structure of the software.
The software shall be documented in 2 levels:
- System Design Specification.
System Engineering CDRL NO. 07.
- Detailed Design Specifications.
Software Development CDRL NO. 05.
The software documentation shall, furthermore, be complemented
with:
- Data Base Design Specification.
- Software Test Specification and Test Procedures.
3.6.9.3 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲i̲g̲n̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲S̲D̲S̲)̲
The System Design Specification shall provide an introduction
to the complete CAMPS system consisting of both hardware,
firmware, and software. It shall show how the system
is constructed of subsystems, how these subsystems
are interrelated, and how the requirements of this
System Requirements Specification and associated ICDs
are mapped onto the subsystems. ACE Directive 007-3
is generated for software specifications only, and
is consequently not adequate for a full System Design
Specification. CR shall, however, use ACE Directive
007-3 as a guideline when producing the SDS.
a) S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲
A Subsystem shall have a well defined function
represented by a well defined set of requirements.
It is further essential that the division into
subsystems is made so that inter-subsystem interfaces
are simple and well defined.
The CAMPS subsystem shall be specified as follows:
1) Hardware Subsystems shall be documented as
described in section 3.6.4 to 3.6.6 (incl.)
2) The system software subsystems shall be documented
in accordance with the following:
a) Existing system software and software that
is a modification of existing software
shall be documented in accordance with
CR standard for system software.
b) Purchased software products shall be documented
in accordance with the internal standards
of the Purchaser. The level of details
shall, however, be equivalent to ACE Directive
007-3.
c) New System Software developed by CR shall
be documented in accordance with ACE Directive
007-3 Annex C.
3) The application software subsystems shall be
specified in accordance with ACE Directive
007-3 Annex C Subsystem Specification.
b) D̲o̲c̲u̲m̲e̲n̲t̲ ̲C̲o̲n̲t̲e̲n̲t̲
The SDS shall include the following information:
1) A chart showing the hierarchical breakdown
into subsystems.
2) Input-process-output diagrams (HIPO) showing
the flow of data between the subsystems.
3) Flow charts showing the logical relationship
between the subsystems.
4) Hardware configuration.
5) A mapping of the software and firmware onto
the hardware.
6) A mapping of the requirements of the SRS onto
the individual subsystem.
7) Performance budgets for the individual subsystem.
8) A description of how all the security requirements
are being met.
3.6.9.4 D̲e̲t̲a̲i̲l̲e̲d̲ ̲D̲e̲s̲i̲g̲n̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The software shall be broken down into software package
with well defined functions and interfaces. The Application
software package and new System Software shall be specified
in accordance with ACE Directive 007-3 Annex D "Program
Specification". The package Specifications will appear
in two issues: As-to-be-built and As-built.
3.6.9.6 D̲a̲t̲a̲ ̲B̲a̲s̲e̲ ̲D̲e̲s̲i̲g̲n̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲
All commonly used data and files shall be specified
in accordance with ACE Directive 007-3 Annex E "Data
Base Specification" (Dated l4th January 1980).
3.6.10 F̲i̲e̲l̲d̲ ̲M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
3.6.10.1 G̲e̲n̲e̲r̲a̲l̲
Copies of all modification advices shall be supplied
giving full information as regards all modifications
carried out on the equipment up to expiration of the
warranty period for the equipment in question. The
modification advices shall include the reason for the
modification, tools required, time required, parts
required, equipment to be modified and full instructions
for the implementation of the modification.
A master list of all modifications carried out on the
equipment shall be provided. The modifications shall
be presented consecutively showing the reason for the
modification equipment modified and a short description
of how it was carried out.
Where a modification necessitates amendment of the
documentation changed pages shall be provided in sufficient
quantity to amend all affected documentation.
3.6.10.2 D̲e̲l̲i̲v̲e̲r̲y̲
The contractor shall provide 2 copies at each modification
advice to the purchaser and 2 copies to each site affected
by the particular modification.
3.7 L̲O̲G̲I̲S̲T̲I̲C̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
3.7.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
3.7.1.1 T̲r̲a̲n̲s̲p̲o̲r̲t̲a̲t̲i̲o̲n̲
3.7.1.1.1 S̲e̲c̲u̲r̲i̲t̲y̲
In the case of classified equipment and/or material,
special shipping shall be provided by the contractor
and confirmed/co-ordinated with the purchaser. NATO
Security manual C-M(55)15 Final, Volume 2 Enclosure
D, Section V defines special security requirements.
The contractor shall ensure that all classified material
and/or equipment to be provided under the terms of
this contract will not be transported over or through
any non-NATO country, nor will any of the material
and/or equipment be handled by any non-NATO aligned
freight forwarder or shipping agency.
3.7.1.1.2 P̲a̲c̲k̲i̲n̲g̲
All equipment delivered under this contract will be
packed and crated in accordance with the best commercial
practices for the type of supplies involved, given
due consideration to climatic and shipping conditions
in order to ensure safe arrival to destination.
…02…a) Items returned for repair will be transported in the
original container used for transport to site. Contractor
will identify all items delivered in reusable containers.
…02…b) All delivered spares will be packed individually for
long term storage without performance or physical deterioration
with expected shelf life. Full details of the contents
and the shelf life shall be clearly indicated on the
package.
3.7.1.1.3 M̲a̲r̲k̲i̲n̲g̲
Items of supply and the packages or containers in which
supplies are transported shall in addition to normal
mercantile marking be marked with the following data
on a separate nameplate (tranfers or stamping acceptable
if nameplate is not practical).
…02… Project title
…02… Purchaser Contract Number
…02… Contract Item Number
…02… Manufacturer's name and address
…02… Ship to address
3.7.1.1.4 P̲a̲c̲k̲i̲n̲g̲ ̲L̲i̲s̲t̲s̲
Packing lists shall accompany all shipments and two
copies each shall be provided to the purchaser. Each
packing list will contain the following information:
…02… Shipping Address
…02… Package Number
…02… Contract Number
…02… Contract Item Number
…02… Item Description
…02… Part Number
…02… NATO Stock Number (if available)
Serial Number
…02… Quantity shipped
…02… Date Shipped
3.7.1.1.5 N̲A̲T̲O̲ ̲S̲h̲i̲p̲p̲i̲n̲g̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
Whenever shipments under this contract requires NATO
Form 302 or other NATO shipping documents these shall
be made available to contractor without delay when
requested by contractor.
3.7.1.2 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
3.7.1.2.1…02…S̲e̲c̲u̲r̲i̲t̲y̲
…02…a) The CAMPS Central Processor together with the supervisor
and maintenance positions will at each site be installed
in a communications security (red) area. The installation
shall therefore conform with the relevant requirements
to automatic processing devices contained in the current
issue of AMSG 719B.
…02…b) Customers local COMSEC staff shall be entitled to monitor
the installation works. A final test and inspection
before each installation becomes operative will be
carried out by an ACE-COMSEC team.
…02…c) The power supply to all equipment in the red area will
enter via a filter or a group of filters, which will
be provided by the customer.Detailed requirements will
be part of the Civil Works Requirements data package
to be supplied by contractor.
3.7.1.2.2…02…S̲t̲a̲n̲d̲a̲r̲d̲s̲
a) The equipment shall operate from mains power installations
conforming to national regulations concerning power
and safety.
b) Contractor will ensure that As-To-Be-Built drawings
submitted to SHAPE will conform to national safety
regulation.
c) Customer will approve the As-To-Be-Built drawings
for conformance to national regulations as well
as obtain approval of the completed installation
from national authorities.
d) The CAMPS Central Processor, together with supervisor
and maintenance positions are processing NATO classified
information in a "clear" electrical form and will
therefore be installed in a communications security
(red) area in conformity with criteria laid down
in the current edition of AMSG-719-b.
3.7.1.2.3…02…G̲r̲o̲u̲n̲d̲i̲n̲g̲
a) An efficient and comprehensive grounding system
shall be provided on each site by customer. The
grounding system shall comprise:
Safety ground (frame ground)
b) The safety ground will be part of the main power
system and conform to national regulations.
3.7.1.2.4…02…M̲a̲i̲n̲s̲ ̲P̲o̲w̲e̲r̲ ̲S̲u̲p̲p̲l̲i̲e̲s̲
a) To be provided at each site by customer.
…02…1) Three phase and single phase 380/220 volts 50 HZ
power supplies will be available at all sites,
except UKAIR where the nominal voltage is 405/240,
with a frequency of 50 HZ.
…02…2) If consisting with national regulations the following
color coding shall apply:
…02… Line: Brown
…02… Neutral: Blue
…02… Ground: Yellow/green
b) In case of 3 phase installation, the lines can
be of any color, except blue and yellow/green.
c) In conformance with national regulations each end
of the neutral and ground wire shall be clearly
marked (coloured sleeves or coloured durable adhesive
tape).
…02…1) P̲r̲o̲t̲e̲c̲t̲i̲v̲e̲ ̲D̲e̲v̲i̲c̲e̲s̲
Protective devices for the mains power installation
shall be provided.
…02… Circuit breakers which operate to make or break
A.C. power lines shall make or break all conductors
at the same time. The neutral wire shall not pass
through any fuse.
…02… All fuses and circuit breakers shall be so located
such that they are readily accessible.
…02… 2) U̲t̲i̲l̲i̲t̲y̲ ̲O̲u̲t̲l̲e̲t̲s̲ ̲S̲o̲c̲k̲e̲t̲s̲
…02… Utility outlets sockets for operation of each terminal
shall be provided as close as possible to the required
installation site of a terminal.
…02… The outlet sockets shall be of a uniform 220 V
AC standard type with ground and break of line
only according to the national standard for each
installation. The socket shall be of a type that
only allows the plug to mate in the correct orientation.
…02… 3) Contractor shall deliver his requirements to the
power installation specifying the required number
of utilily as part of the Civil Works Requirements
Package.
3.7.1.2.5 E̲f̲f̲e̲c̲t̲ ̲o̲n̲ ̲M̲i̲l̲i̲t̲a̲r̲y̲ ̲A̲c̲t̲i̲v̲i̲t̲i̲e̲s̲
Installations in buildings shall be performed in a
manner that avoids disruption of on-going military
activities. Contractor may be required under special
circumstances to stop work for military reasons. Under
such circumstances, the contractor shall furnish a
report to SHAPE giving details of the time that the
stop work order was enforced, together with any other
pertinent information.
3.7.1.2.6 S̲p̲a̲c̲e̲ ̲a̲n̲d̲ ̲A̲c̲c̲e̲s̲s̲ ̲D̲i̲m̲e̲n̲s̲i̲o̲n̲s̲
a) At each site an area of 7 meters by 5 meters will
be made available for the installation of the CAMPS
Central equipment (duplicated processor) and supervisory
positions with a minimum floor to ceiling height
of 220 cm without a raised floor, or 2 meters minimum
if a raised floor is provided.
…02…b) A̲c̲c̲e̲s̲s̲ ̲D̲i̲m̲e̲n̲s̲i̲o̲n̲s̲
All sites have access dimensions equal to or better
than:
Height 1.70 meters
Width 0.65 meters
Length 3.70 meters
Above dimensions will be guaranteed as the minimum
envelope along the equipment access route of any
site.
3.7.1.2.7 S̲i̲t̲e̲ ̲S̲u̲r̲v̲e̲y̲s̲
…02…a) Immediately following contract award contractor shall
perform formal site surveys at each site.
b) Subject to coordination with contractor SHAPE will
arrange a visit to each site. The purpose of the
site surveys is to ensure that the contractor can
perform the following tasks.
…02… 1) Verification of the site documentation specified
in d) below.
…02… 2) Preparation of the site civil works drawings/specifications
and the as-to-be-built drawings.
c) SHAPE representatives will assist contractor to
collect the relevant information to be used to
prepare the site for installation of the CAMPS
equipment. At least one of SHAPE representatives
on each site survey team will be authorized to
make decisions and to sign a survey protocol on
behalf of SHAPE.
…02…d) S̲i̲t̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Customer will deliver a data package to contractor
prior to site survey to permit him to conduct the
survey. Data not delivered prior to site survey
will be supplied during the survey. Additional
data will be supplied by customer in accordance
with minutes of meeting agreed to during the conclusion
of the site survey.
e) Drawings and specifications supplied by customer,
must contain sufficient information to permit contractor
to generate Civil Works Requirements, As-to-be-built
drawings and As-built Drawings as described in
section 3.6.6.
f) Customer shall without being requested so by contractor
submit all of the above data and subsequent updates
to ensure that contractor at all times has the
most current documentation package for the site
in question.
g) Above data shall be submitted to contractor no
later than 3 months prior to contractors scheduled
delivery of Civil Engineering requirements.
3.7.2 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲a̲n̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲
3.7.2.1 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲P̲l̲a̲n̲
Contractor shall develop a maintenance plan identified
in the CDRL of the contract. After review by the Customer
the plan will be updated.
3.7.2.2 R̲e̲p̲o̲r̲t̲i̲n̲g̲ ̲S̲y̲s̲t̲e̲m̲
Contractor shall establish and manage a fault reporting
system to monitor system status and to analyze failures.
3.7.2.3 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲S̲u̲p̲p̲o̲r̲t̲
Contractor shall provide a system analysis and programming
service to the Customer. This service shall commence
with the Provisional Site Acceptance (PSA) of the first
site and will continue until such a time that the Customer
has formed his own capability for software maintenance.
The following functions shall be fulfilled:
a) To design and implement changes and modifications
to the system and application software at the request
of the Customer. All software modifications and
changes shall be authorized, produced and issued
centrally.
b) Provide assistance and expertise to the purchaser
when required.
c) Diagnose and correct all faults that occur in the
software at all installations.
d) To control and maintain the software documentation.
Note: Effort in connection with subparagraph a)
and b) above is considered out of scope of contract
but will be performed on request and at additional
cost.
3.7.2.4 T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
a) G̲e̲n̲e̲r̲a̲l̲.̲ As part of the CAMPS Maintenance Plan
the Contractor will submit a price list of all
tools, test equipment, test cables, test adapters,
test programmes and other items required at each
CAMPS site, and maintenance depots to support the
equipment supplied, and necessary to make all measurements
on any part of the system at any time during installation,
alignment, maintenance and repair and testing to
specification.
b) Special type tools, test equipment and test programs
shall be clearly identified as well as the purpose
for which each tool and piece of test equipment
is required.
c) The list shall include, where applicable, associated
ancillaries such as signal sources, cable adapters,
matching devices, power sources and extension jigs
and cables.
d) The test equipment and tools supplied under this
contract may be supplemented with other items which
will be listed in the maintenance plan.
3.7.2.4.1 P̲u̲r̲c̲h̲a̲s̲e̲
Test equipment and tools suggested by the Contractor
may be substituted or augmented by the purchaser. Such
items will be deleted from or added to the contract
by an appropriate amendment. Test equipment supplied
with the site hardware and included in the basic contract
will be clearly identified.
3.7.2.4.2 U̲s̲e̲ ̲P̲r̲i̲o̲r̲ ̲t̲o̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲
a) All test equipment and tools to be used by the
Contractor on site for the setting up, alignment
and measurement of performance shall be equipment
identical to that which is recommended by the Contractor.
b) Test equipment, facilities and tools for delivery
to the purchaser are not to be used by the Contractor
without prior approval from the purchaser. Approval
for the use of such items will be subject to:
1) All used items being in an "as new" state at
the time of on-site acceptance.
2) Re-calibration of test equipment where appropriate,
at the Contractor's expense.
3.7.2.4.3 A̲u̲t̲o̲m̲a̲t̲i̲c̲ ̲T̲e̲s̲t̲i̲n̲g̲
The Contractor shall quote for the supply of test adaptors
and programs for use with the purchaser's automatic
test equipment held at the central repair depot(s),
so that all repairable modules which are to be supplied
by the Contractor may be tested by this automatic test
equipment. The Contractor shall also quote for the
supply of Contractor's own in-house test equipment
to serve above purpose.
3.7.2.5 C̲a̲l̲i̲b̲r̲a̲t̲i̲o̲n̲
The Contractor shall prepare a plan and procedures
for the calibration of each item of suggested special
test equipment. Calibration plans and procedures shall
also be provided for items of test equipment built
into the main equipment. A list of parameters to be
covered and recommended standards necessary for the
calibration of each item shall also be provided by
the Contractor. The calibration plan will be part of
the CAMPS Maintenance Plan.
3.7.2.6 F̲i̲e̲l̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲
The Contractor shall be responsible for generation
of all modifications found necessary to make the supplied
equipment conform to the requirements as stated in
the contract; including the supply of all modification
kits, any special test equipment and tools required
to implement and test modifications, and the updating
of handbooks and drawings. During the warranty period
all necessary kits and instructions will be supplied
by the contractor free of charge fob destination.
All modifications subsequent to the SHAPE witnessed
factory tests shall be correctly documented. Modifications
shall by numbered sequentially commencing with 01,
and shall contain modification instructions.
3.7.3 S̲p̲a̲r̲e̲s̲ ̲a̲n̲d̲ ̲C̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) G̲e̲n̲e̲r̲a̲l̲.̲ Contractor shall deliver to the Customer
the optimum range and level of spare parts, common
and special tools and test equipment required to
support the system.
b) Provisions to be supplied shall include the recommended
list of spares to be held on each site to cover
90 days operation without support from another
site and those to be held in a depot to cover 270
days operation. The parts selected and the quantities
recommended shall be based on provision of adequate
support to meet the reliability and maintainability
requirements for CAMPS at the lowest possible cost.
To this end it is understood that some spares will
take the form of insurance items.
3.7.3.1 S̲u̲p̲p̲l̲y̲ ̲o̲f̲ ̲P̲a̲r̲t̲s̲
3.7.3.1.1 R̲e̲c̲o̲m̲m̲e̲n̲d̲e̲d̲ ̲S̲p̲a̲r̲e̲ ̲P̲a̲r̲t̲s̲ ̲L̲i̲s̲t̲ ̲(̲R̲S̲P̲L̲)̲
a) 60 days after contract signature, the Contractor
shall submit a Recommended Spare Parts List (RSPL).
The RSPL shall include all spare parts required
to support all equipment supplied by the Contractor.
The method of calculation and the justification
outlined in the development and preparation of
RSPL shall be provided.
b) The RSPL will include:
1) A 90 days stock for each site (80% confidence).
2) A 270 days stock for one supply depot (80%
confidence).
3) A 270 days stock for two supply depots (80%
confidence).
4) A maintenance float to be held at the supply
depot.
5) Insurance items to be held on each site and
at the supply depot.
3.7.3.1.2 A̲p̲p̲r̲o̲v̲e̲d̲ ̲S̲p̲a̲r̲e̲ ̲P̲a̲r̲t̲s̲ ̲L̲i̲s̲t̲ ̲(̲A̲S̲P̲L̲)̲
The Approved Spare Parts List (ASPL) will be derived
by using the RSPL, the equipment and documentation
and will be determined jointly by the Customer and
the Contractor during provisioning meetings to be held
by the Contractor. The ASPL shall be incorporated in
the contract by an appropriate amendment 60 days after
the receipt of the RSPL.
3.7.3.l.3 P̲r̲o̲v̲i̲s̲i̲o̲n̲ ̲o̲f̲ ̲S̲p̲a̲r̲e̲ ̲P̲a̲r̲t̲s̲ ̲D̲u̲r̲i̲n̲g̲ ̲F̲i̲r̲s̲t̲ ̲Y̲e̲a̲r̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
a) The Contractor shall provide all spare parts listed
in the ASPL prior to the provisional site acceptance
of each site.
b) The Contractor shall replenish the spare parts
at each site for a period of one year after PSA.
Follow-on procurement of spare parts as well as
spares needed for the replenishment described above
shall be covered by separate contracts.
c) Prior to Provisional Site Acceptance (PSA) at any
site the Contractor shall provide his own spare
parts to maintain the equipment to the required
performance level.
3.7.3.1.4 F̲o̲l̲l̲o̲w̲-̲o̲n̲ ̲S̲p̲a̲r̲e̲s̲
a) The Contractor agrees that follow-on spares in
support of items supplied under this contract shall
be available on order, for delivery within a reasonable
period, for a period of ten years following the
date of final payment of the last delivered items
procured under this contract. The contractor further
agrees that the unit prices charged for such spares
shall be fair and reasonable and that spares will
be sold to SHAPE at the current catalog price for
CR's most favoured customer.
b) During the ten year period of guaranteed availability
of the follow-on spares the Customer may purchase
a fixed delivery time for follow-on spares.
3.7.3.1.5 S̲p̲a̲r̲e̲ ̲P̲a̲r̲t̲s̲ ̲A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲
The Contractor shall promptly notify the Customer upon
receipt of notice of any non-availability of spare
parts and will provide all data with respect to the
replacement and interchangeability of new parts.
3.7.3.1.6 I̲n̲v̲e̲n̲t̲o̲r̲y̲
The Contractor shall prepare a property inventory for
each site. The inventory will form part of the site
documentation.
3.7.3.1.7 D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲s̲
a) I̲n̲s̲u̲r̲a̲n̲c̲e̲ ̲T̲y̲p̲e̲ ̲I̲t̲e̲m̲.̲ Item which is generally not
subject to periodic replacement or wear out but
is subject to infrequent replacement as the result
of accidents and other unexpected occurrences and
the stockage of which is considered to be necessary
for operational reasons and lead time considerations.
b) M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲F̲l̲o̲a̲t̲.̲ Pool of all, or of selected
end items comprised in a system which are kept
in storage and made available as rapid replacement
for like but unserviceable end items to allow for
maintenance processing. They can be used either
on an exchange or a rental basis.
c) M̲o̲d̲u̲l̲e̲/̲P̲r̲i̲n̲t̲e̲d̲ ̲C̲i̲r̲c̲u̲i̲t̲ ̲C̲a̲r̲d̲s̲.̲ Part of an assembly
replaceable as a whole but also having some components
that may be replaceable individually; consisting
of a combination of components having a common
mounting or mounted on each other.
3.7.3.1.8 S̲p̲a̲r̲e̲ ̲P̲a̲r̲t̲s̲ ̲D̲e̲s̲i̲g̲n̲ ̲C̲h̲a̲n̲g̲e̲ ̲N̲o̲t̲i̲c̲e̲s̲
a) The Contractor will issue to the Customer Spare
Parts Design Change Notices (SPDCN) for each item
(fuse, resistor, capacitor, lamp, transistor, inductance
module, etc.) affected within:
1) Four weeks of the Customer's approval of the
Equipment Design Change Notice affecting the
spare parts change.
2) Not later than nine months before an item will
no longer be produced.
b) The SPDCN will refer to the assembly and the part
involved, the improvement achieved, the technical
manuals and the parts thereof to be amended, the
impact on the provisioning actions already taken
and/or stocks of parts and components already delivered.
The SPDCN will also indicate the price of the new
part and provide recommendations as to the disposition
actions to be taken on the previously recommended
part, as appropriate.
c) The above services are to be furnished at no additional
cost to the Customer, as long as the service is
rendered within the warranty period of the equipment.
d) Cost of issuing SPDCNs subsequent to expiration
of warranty period will be negotiated separately
or be part of additional spares procurement.
3.7.3.1.9 P̲r̲o̲v̲i̲s̲i̲o̲n̲i̲n̲g̲ ̲C̲o̲n̲f̲e̲r̲e̲n̲c̲e̲s̲
The Contractor and purchaser will schedule and conduct
provisioning conferences within a mutually agreed and
suitable time frame to allow selection and timely delivery
of parts, tools and test equipment. Conference facilities,
documentation and equipment as required/ available
will be provided by the Contractor.
3.7.3.2 N̲A̲T̲O̲ ̲C̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Contractor shall codify before final acceptance
of all CAMPS sites at no additional cost to purchaser:
a) Items shown in the approved spare parts list (ASPL).
b) Major and minor sub-assemblies (if not included
in the ASPL).
c) Equipment/spare parts affected by the equipment
Design Changes Notices.
Codification required in addition to a), b), and c)
above shall be established by the purchaser at progress
meetings with the Contractor.
3.7.4 T̲r̲a̲i̲n̲i̲n̲g̲
3.7.4.1 G̲e̲n̲e̲r̲a̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
a) Contractor shall develop training programs and
supply associated course material for the following
courses:
…02…1) Technical Hardware Training Course
…02…2) Operator Training Course
…02…3) On-The-Job Training
…02…4) Software Maintenance Course (optional)
…02…5) Training of Customer Resident Field Technicians
6) Depot level Training Course (optional)
b) …02…Contractor shall conduct the following training:
…02…1) Initial series of Technical Hardware Training Courses
to be conducted at contractor's facility. (Training
at NCS is optional).
…02…2) Training of customers Resident Field Technicians
(RFT) to be conducted at contractor's facility.
…02…3) Software Maintenance Course to be conducted at
contractors facility when customer has the resources
available to form a maintenance capability (optional).
3.7.4.1.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲a̲t̲ ̲N̲C̲S̲
a) The contractor shall install the training equipment
at the NATO Communications School (NCS) Latina,
so that it is fully operational before the first
formal training courses to be conducted at the
NCS by customer's instructors.
b) In addition to spares delivered to NCS the contractor
shall supply some modules and sub-assemblies with
representative and realistic faults so that the
fault finding techniques shall be true to life.
The lay-out of the installed equipment shall be
representative of a CAMPS configuration. Test equipment
of the same type and quantity as for a normal CAMPS
installation shall be provided to carry out all
maintenance activities that will be required of
the technicians. All such equipment will become
the property of the purchaser.
c) L̲a̲n̲g̲u̲a̲g̲e̲. All courses shall be conducted in English
and all equipment handbooks and training material
shall be produced only in English.
d) C̲o̲u̲r̲s̲e̲ ̲L̲e̲n̲g̲t̲h̲. Formal Courses shall be designed
to be effective and efficient, but should be kept
as short as possible. The integrated training plan
is to be based upon a 6 hour day, 45 minute training
period and a 5 day week, and take account of NATO
holidays (approx. 1 day/month) and course administration
(1 day/course and 1 day/month).
e) C̲o̲u̲r̲s̲e̲ ̲S̲t̲r̲e̲n̲g̲t̲h̲. There shall be a maximum of 12
students per course. For practical work a course
shall be divided into 6 groups of 2 students if
possible, or individual "stands" if continuous
flow self-paced methods are selected for formal
courses. The courses shall be developed to provide
for hands-on equipment training for at least 60%
of the time.
3.7.4.1.2 T̲a̲r̲g̲e̲t̲ ̲P̲o̲p̲u̲l̲a̲t̲i̲o̲n̲
a) All students to be trained except RFT (see d. below)
will be military and civilian personnel from various
NATO countries, each having an English language
proficiency level of at least SLP 3232 (as described
in STANAG 6001 of 21. Oct. 76.).
b) All operators will be capable of operating computer
type terminal equipment such as VDUs and line printers
through the former use of teleprinters and typewriters
but may not necessarily be experienced in working
with a processor.
Furthermore operating personnel must be conversant
with message handling procedures as defined in
ACP 127-3.
…02…c) All technicians will have been trained in general
electronics but may not have extensive knowledge in
the electronic and digital techniques used in computer
equipment.
…02…d) Personnel requirements applicable to customers Resident
Field Technician (RFT) are as follows:
…02… 1) The RFT shall have an English language proficiency
level of SLP 4443 as described in STANAG 6001 of
21 Oct 1976. The RFT must be graduate of an accredited
advanced communication or electronics technical
school and have a minimum of 5 years' experience
in modern communication systems using digital switching
techniques. This experience must include the maintenance
of installation testing of such equipment. He shall
have a generel knowledge of software to permit
an initial diagnosis and analysis of software faults
in order to furnish relevant data to the system
analysis and programming service.
2) He shall have the necessary qualifications
to conduct extensive OJT courses attended by
operators and technicians.
3.7.4.1.3 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲ ̲A̲i̲d̲s̲
a) The training documentation to be provided in support
of the training programme for the contract shall
be written, compiled, published and delivered in
accordance with the contractual requirements for
documentation applicable for this contract.
b) The contractor shall prepare and provide all training
aids in the light of the maintenance requirements.
c) I̲n̲s̲t̲r̲u̲c̲t̲o̲r̲'̲s̲ ̲M̲a̲n̲u̲a̲l̲. For each course supplied under
this contract contractor shall provide an instructor's
manual which will comprise a collection of all
the training material in one loose leaf binder,
properly indexed.
d) V̲u̲f̲o̲i̲l̲s̲ ̲a̲n̲d̲ ̲S̲l̲i̲d̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲. Vufoils shall
be prepared on transparent plastic sheets no larger
than 25 cm x 25 cm and no smaller than 17.5 cm
x 23.5 cm and shall be mounted in permanent cardboard
or plastic holders.
They shall be numbered in a manner, which clearly
identifies each vufoil with its associated lesson
plan and student notebook.
e) Slides shall be standard 35 mm slides mounted in
card or plastic holders. They shall be numbered
in a manner which clearly identifies each slide
with its associated lesson plan and student notebook.
f) A̲p̲p̲r̲o̲v̲a̲l̲ ̲a̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲. The contractor shall submit
a sample copy (preliminary version) of the training
documentation with readable prints of each associated
vufoil and slide, and films, to the purchaser and
the NCS (see annex A). Recommended changes shall
then be incorporated by the contractor and finalized
copies of the training documentation together with
training aids shall be delivered to the NCS and
purchaser.
The contractor shall deliver all training documentation
in the quantities shown at Annex A.
g) S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲. The contractor shall mark
the appropriate security classifications on all
documentation and training material following the
current ACE security directives. The purchaser
shall approve the security grading before production
in quantity.
3.7.4.2 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲r̲o̲g̲r̲a̲m̲ ̲P̲l̲a̲n̲
a) Contractor shall submit to purchaser a Training
Program Plan for his approval no later than 6 month
before the scheduled commencement of the first
course.
b) The plan shall give a detailed description of the
Training program and the interrelationship between
the five types of training:
- hardware training
- operator training
- on-the-job training
- software training
- training of customers Resident Field Technicians
c) The training plan for each of the five types of
courses will include appropriate subsets of the
following training objectives:
l) A general description of the system.
2) Operation and maintenance philosophy and policies.
3) Electronic components utilized.
4) Transmission and operation techniques.
5) Detailed step-by-step signal and information
flow through all equipment.
6) Use of test equipment and measuring techniques.
7) Practical training for fault diagnosis, alignment,
testing maintenance and operating procedures.
8) Sufficient instruction regarding the software
so that a technician will be able to diagnose
and analyze a software fault and furnish the
relevant details to the software maintenance
team.
9) The intended method of instruction, that is:
- Continuous flow, self paced method using
self
learning materials OR.
- Traditional classroom/laboratory methods
OR.
- A combination of both.
10) The expected duration of the course.
11) The syllabus and integrated training plan.
d) Furthermore, the following information will be
provided:
1) Skills and Knowledge Specification (SAKS).
That is, the skills and knowledge required
of the trained person as determined by the
contractor.
2) Training and Enabling Objectives.
These are to be formulated from the SAKS.
They are precise objective statements in behavioural
terms of what a trained person must be able
to do, the conditions under which he must carry
out the performance, and the standards which
the trained person must achieve to enable him
to do the job safely and effectively. Training
and enabling objectives will be developed for
each course and included in the respective
training plan.
3) Entry Standards.
The contractor shall state in the Training
Program Plan the required entry standards and
technical background of prospective students.
3.7.4.3 T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
3.7.4.3.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
a) Contractor shall submit an integrated Training
Plan no later than 6 months before the scheduled
commencement of the first formal course to be conducted.
b) The training plan will be worked out in conjunction
with the purchaser, based on the installation schedule,
at the same time ensuring that the initial training
courses shall be programmed so as to permit sufficient
qualified personnel to be available at each site
upon provisional acceptance.
c) The training programme shall be planned to allow
for the training of the NCS instructors before
the changeover of the training venue from contractor's
facility to NCS, Latina.
d) The Training and Enabling objective of this course
is two fold:
1) to let the technician diagnose and correct
a fault according to the requirements in the
Maintenance plan i.e. repair by module replacement.
Consequently, training below module level
will not be performed.
2) to let the technician perform Software program
and data base changes as directed.
3.7.4.3.2 C̲o̲n̲d̲u̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲u̲r̲s̲e̲s̲
a) The initial courses, 6 courses held at contractor's
facility, will ensure training of personnel to
be available at sites before PSA. Furthermore,
the two NCS instructors will be trained in the
following way:
b) The NCS instructors shall attend one course as
students, the following course shall be taught
by the contractor assisted by the NCS instructors.
The third course shall be taught by the NCS instructors
supervised by the contractor's instructors.
c) These three courses shall be programmed to be the
last three courses of the initial series of 6 courses
being taught by the contractor.
d) During and between the course the contractor shall
give all necessary support to the NCS instructors
for their theoretical and practical training.
e) The contractor shall provide two instructors for
the purpose of the initial training.
f) The contractor's instructors shall be qualified
to teach telecommunications and computer technology
to degree standard and have an English language
proficiency of SLP 4443 as explained in STANAG
6001 of 21. Oct. 76. The instructors shall have
full knowledge of the operation and maintenance
of the equipment being supplied by the contractor.
g) Contractor will develop the Formal Technical Training
course as a 10 days hardware course and a 15 day
software course.
h) At the end of each of the initial 6 courses all
students will be required to complete a questionnaire
on the training course content, length of course,
method of instruction, and all other circumstances
affecting student progress and/or proficiency.
The questionnaires will be submitted by the contractor
who shall forward them to the purchaser for his
comments. The questionnaires will be compiled
and produced by the contractor.
3.7.4.3.3 T̲r̲a̲i̲n̲i̲n̲g̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲
The contractor shall provide the following for each
technical course. All instruction and material is
to be based on the approved training and enabling objectives.
For documentation quantity requirements see Annex
A.
3.7.4.3.3.1 T̲e̲s̲t̲ ̲I̲t̲e̲m̲s̲
Test items, if of the multiple choice type, derived
from the approved training objectives, stating how
these tests will be carried out, i.e. at the end of
various phases or on a continuous assessment for practical
work shall be adopted.
3.7.4.3.3.2 L̲e̲s̲s̲o̲n̲ ̲P̲l̲a̲n̲s̲
These shall include statements on:
a) The objectives of the lesson.
b) The structure of the lesson indicating key teaching
points/words and test items.
c) The audio-visual aids required.
d) The time allowed for the lesson.
e) Reference documents, handbooks, etc.
3.7.4.3.3.3 S̲t̲u̲d̲e̲n̲t̲ ̲L̲a̲b̲o̲r̲a̲t̲o̲r̲y̲ ̲N̲o̲t̲e̲b̲o̲o̲k̲s̲ ̲(̲g̲u̲i̲d̲e̲s̲)̲
These shall contain for each practical exercise:
a) The objective of the exercise.
b) Appropriate diagrams (if not included in a separate
book).
c) Space in which to write exercise reports, results
and conclusions.
d) Trouble shooting charts.
3.7.4.3.3.4 I̲n̲s̲t̲r̲u̲c̲t̲o̲r̲ ̲L̲a̲b̲o̲r̲a̲t̲o̲r̲y̲ ̲G̲u̲i̲d̲e̲s̲
These shall be in more detail than the corresponding
student guides and must show:
a) The equipment required for each exercise and how
it should be set up to enable the objective to
be achieved.
b) How student performance should be monitored and
assessed.
c) Trouble shooting techniques.
3.7.4.3.3.5 V̲i̲s̲u̲a̲l̲ ̲A̲i̲d̲s̲
These shall include one or more of the following: vufoils,
slides, films or video tapes to demonstrate techniques,
procedures, etc.
3.7.4.3.3.6 S̲t̲u̲d̲e̲n̲t̲ ̲T̲e̲x̲t̲b̲o̲o̲k̲s̲
Comprehensive student notes should be produced for
all parts of training. They must include copies of
all visual aids used in instruction. Student texts
shall be produced in a loose leaf form with binders
so that the student is only issued with those notes
which are pertinent to the current part of the course
he is studying.
3.7.4.3.3.7 S̲t̲u̲d̲e̲n̲t̲ ̲L̲o̲g̲ ̲B̲o̲o̲k̲
A Student Log Book for objectives achieved shall be
supplied by the contractor. This log book shall be
a copy of the syllabus of the course which may be updated
as the course progresses and referred to later on-the-job
as a record of training performance standard achieved.
3.7.4.4 O̲p̲e̲r̲a̲t̲o̲r̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
3.7.4.4.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
The contractor shall submit specific proposals for
the operators course to the purchaser for his approval
6 months before the equipment is scheduled to become
operational. These proposals shall include:
a) Methods to be used e.g. Programmed learning texts,
use of a software package, multiple choice question
papers.
b) Samples of training aids.
c) Details of any essential off-line training equipment
required.
d) A statement as to the length of time an operator
will be required to carry out OJT before he will
be able to competently operate the equipment to
Operational Performance Standards.
Upon approval of his proposals the contractor shall
provide all materials and equipment to enable students
to reach the required objectives.
3.7.4.4.2 C̲o̲n̲d̲u̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲u̲r̲s̲e̲s̲
Formal operator training shall be carried out on-site
as on-the-job training, at customers full responsibility.
As the equipment will be in position and available
for use the self-paced method of instruction shall
be adopted. For supervision, the contractor can depend
on the availability of a part-time instructor. In
the first instance this part time instructor will be
the Resident Field Technician and later it will be
the operational supervisor.
3.7.4.4.3 T̲r̲a̲i̲n̲i̲n̲g̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲
Upon customer's approval of the Training Plan, contractor
shall provide all training material in the quantity
stated in Annex A.
3.7.4.5 O̲n̲-̲T̲h̲e̲-̲J̲o̲b̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
3.7.4.5.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
a) The contractor shall prepare a detailed OJT programme
for both operators and maintenance personnel for
implementation at all sites.
b) The maintenance personnel to be given OJT will
have attended the appropriate formal training course
at NCS or the initial Technical Course held at
contractors facility.
c) The operator personnel to be given OJT will have
attended the appropriate formal training on-site
(see Operator Training).
d) The contractor shall indicate, in detail, the contents
of each instruction phase and the time to be spent
on each phase of the OJT. The contractor shall
identify and prepare all training documents and
materials and aids necessary for the OJT.
e) The OJT programmes shall be in addition to the
formal training and be designed to qualify station
personnel to operate installed equipment, to carry
out required preventive maintenance and to perform
corrective maintenance.
f) A written and practical test shall be developed
by contractor to be taken by the participants at
the end of each phase of OJT. The written tests,
shall be of the multiple choice question type.
Evaluation of the test results will be done by
the RST.
3.7.4.5.2 C̲o̲n̲d̲u̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲u̲r̲s̲e̲s̲
OJT training will be conducted by the purchaser. The
purchaser is responsible for restoring equipments to
full operational status after completion of training
sessions. This customer's responsibilty in no way affects
the contractor's responsibility under the warranty
or contract special provision number 24.
3.7.4.5.3 T̲r̲a̲i̲n̲i̲n̲g̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲
Upon customer's approval of the Training program, contractor
shall provide all training material in the quantity
stated in annex A.
3.7.4.6 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲C̲o̲u̲r̲s̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
3.7.4.6.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
a) The contractor shall develop a training plan for
the software maintenance of the systems. The purpose
of this course shall be to give sufficient knowledge
and expertise to the students for maintenance and
modification of the software independently of the
contractor. These students shall be the software
maintenance personnel of the purchaser.
b) This course will only be required when the purchaser
has the resources and the possibilities of maintaining
the software. For this reason, the contractor
shall provide a separate training plan for this
course. The software training plan shall be submitted
to the purchaser within 6 months after the site
acceptance of the first site. Generation of the
Software Training Plan is considered within scope
of the basic contract.
3.7.4.6.2 C̲o̲n̲d̲u̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲u̲r̲s̲e̲s̲
Conduction of courses is not within scope of this contract.
As part of the proposal for the training plan contractor
will submit detailed costing for the development and
conduction of the software Maintenance Courses. The
courses may take place at one or more of three places.
- contractor's plant
- CSSI
- NCS Latina
3.7.4.6.3 T̲r̲a̲i̲n̲i̲n̲g̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲
Upon customer's approval of the Software Training Plan
contractor shall deliver training material for the
software Maintenance Course.
3.7.4.7 T̲r̲a̲i̲n̲i̲n̲g̲ ̲o̲f̲ ̲C̲u̲s̲t̲o̲m̲e̲r̲'̲s̲ ̲R̲e̲s̲i̲d̲e̲n̲t̲ ̲S̲i̲t̲e̲ ̲T̲e̲c̲h̲n̲i̲c̲i̲a̲n̲s̲
It is Customer's intention to have 12 persons trained
by contractor at his plant. These persons are termed
Resident Site Technicians (RST) and will be assigned
to the individual CAMPS site 2 weeks prior to site
installation.
3.7.4.7.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
Contractor shall submit a separate training plan 6
months before the scheduled commencement of the courses.
The level of training shall be such that the RST will
have sufficient knowledge to diagnose hardware faults
down to unit level and perform pull and replace maintenance.
He shall be able to identify software errors and report
them to contractor's software maintenance and support
team. After software corrections are made by contractor,
the RST shall implement the program change at his CAMPS
site. Furthermore, he will receive training in implementation
of Field Modifications required by the maintenance
plan.
3.7.4.7.2 C̲o̲n̲d̲u̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲c̲o̲u̲r̲s̲e̲s̲
The two proposed courses will be carried out at contractor's
facility.
Formal classroom training of the RST will be conducted
in classes of max. 6 students. Hands-on training will
be carried out on contractor's DSMT system and on Hardware
produced for NCS, Latina. To the extent possible the
students will participate in the integration and test
of the production systems. If relevant, visits to
a site will be made during the training period, to
familiarize the student with site installations etc.
After training the RST must be qualified to conduct
OJT and supervise maintenance as well as undertake
all the tasks as described in contractor's maintenance
plan.
3.7.4.7.3 T̲r̲a̲i̲n̲i̲n̲g̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲
Upon customers approval of the training program contractor
shall provide each student with a complete set of training
material. Additional sets (two) shall be delivered
to customer for information.
3.7.4.8 D̲e̲p̲o̲t̲ ̲L̲e̲v̲e̲l̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
Training of customer's personnel in depot level repair
of the CAMPS hardware modules will be carried out by
contractor at customer's request. This option should
be exercised when the final Depot Level repair method
has been selected i.e. use of customer's universal
test equipment (ATE) or contractor supplied CAMPS Module
Test Equipment.
ANNEX A 1 of 3 pages
D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲Q̲u̲a̲n̲t̲i̲t̲y̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The contractor is to provide training documentation
in the following quantities:
P̲r̲e̲l̲i̲m̲i̲n̲a̲r̲y̲ ̲V̲e̲r̲s̲i̲o̲n̲…02…P̲u̲r̲c̲h̲a̲s̲e̲r…02…N̲C̲S̲…02…O̲p̲t̲i̲o̲n̲a̲l̲ ̲s̲i̲t̲e̲…02…T̲o̲t̲a̲l̲ ̲
1. Preliminary ver-
sion of all do-
cumentation list-
ed below 6 months
before commence-
ment of the first
course…02……02……02…2…02…2…02…0…02…4
F̲i̲n̲a̲l̲ ̲V̲e̲r̲s̲i̲o̲n̲s̲
2. Integrated train-
ing plan for for-
mal courses…02…2…02…6…02…0…02…8
3. Integrated train-
ing plans for
programmed learn-
ing courses…02…2…02…4…02…2…02…8
4. Integrated train-
ing plan for OJT…02…2…02…1…02…2…02…5
5. Skills and Know-
ledge Specifica-
tions (SAKS),
sets per course…02…1…02…1…02…1…02…3
6. Training and
Enabling Objec-
tives, sets,
for all cour-
ses…02……02……02…2…02…6…02…1…02…9
ANNEX A 2 of 3 pages
7. For formal courses:
a. Course log book
& test items…02…2…02…14…02…-…02…16
b. Student assess-
ment sheets/
cards…02……02……02…2…02…200…02…-…02…202
c. Lessons plans,
sets…02……02……02…2…02…6…02…-…02…8
d. Course syllabus…02…2…02…6…02…-…02…8
e. Student log
book…02……02……02…2…02…200…02…-…02…202
f. Student lab
guides…02……02……02…2…02…200…02…-…02…202
g. Instructor
lab guides…02……02…2…02…6…02…-…02…8
h. Equipment
handbooks…02……02…2…02…20…02…-…02…22
i. Student text
books, sets…02……02…2…02…200…02…-…02…202
j. Visual aids,
sets…02……02……02…2…02…6…02…-…02…8
ANNEX A 3 of 3 pages
P̲r̲e̲l̲i̲m̲i̲n̲a̲r̲y̲ ̲V̲e̲r̲s̲i̲o̲n̲s̲
k. Student
aptitude
questionnaires…02…2…02…200…02…-…02…202
8. Instructors'
manuals…02……02……02…2…02…6…02…-…02…8
9. For OJT - all
documentation…02…2…02…2…02…10…02…14
10.Student's
Questionnaire…02…2…02…200…02…-…02…202
…02…Note 1 All documentation shall have one copy produced as a
master suitable for offset printing - this master shall
be delivered to the purchaser.
4̲ ̲ ̲Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲ ̲P̲R̲O̲V̲I̲S̲I̲O̲N̲S̲
This section specifies the quality assurance provisions
applicable to verification of equipment and software.
4.1…02…T̲E̲S̲T̲ ̲A̲N̲D̲ ̲V̲E̲R̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲M̲E̲T̲H̲O̲D̲S̲
The unit test requirements will be met by one of the
following methods:
…02…a. E̲x̲a̲m̲i̲n̲a̲t̲i̲o̲n̲.̲ This method is a non-functional verification,
such as visual inspection of the physical characteristics
of the item or of the documentation associated with
the item.
…02…b. A̲n̲a̲l̲y̲s̲i̲s̲.̲ This method is a non-functional verification,
such as deduction or translation of data, review of
analytical data, or performance of a detailed analysis.
…02…c. T̲e̲s̲t̲ ̲D̲e̲m̲o̲n̲s̲t̲r̲a̲t̲i̲o̲n̲.̲ This method is a functional verification,
such as actual operation wherein the element of verification
is instrumented, measured, or displayed directly (test)
or where the element of verification is logically obvious,
as the result of some other verification, but not itself
displayed (demonstration).
4.2…02…V̲E̲R̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
a) The verification efforts are divided into hardware,
software and system verification.
b) The verification will be divided into two classes
which are
…02… I - Internal verification
…02… II - External verification
c) Only class II verifications shall be approved by
SHAPE.
d) Class I verifications shall be approved by CR's
internal QA only, but may be inspected by SHAPE's
QAR.
e) The verification efforts shall be divided into
the verification type defined below.
f) H̲A̲R̲D̲W̲A̲R̲E̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
…02… C̲l̲a̲s̲s̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲T̲y̲p̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
…02…I…02…Prototype Verification
…02……02…I Preproduction Verification
…02…I…02…Production Verification
…02…II…02…DSMT (Prototype) System Verification
…02…II…02…Factory Acceptance Verification
…02…II…02…COMSEC In-Plant Verification
…02…II…02…Availability Verification
g)…02…S̲O̲F̲T̲W̲A̲R̲E̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
…02…C̲l̲a̲s̲s̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲T̲y̲p̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
…02…I…02…Software Development Verification
…02…II…02…In Plant Software Verification
…02…II…02…Software Functional Verification
…02…II…02…Software Operational Verification
h) S̲Y̲S̲T̲E̲M̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
C̲L̲A̲S̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲t̲y̲p̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
II Comsec On-site Verification
II Site Provisional Acceptance (SPA)
4.2.1…02…H̲a̲r̲d̲w̲a̲r̲e̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.2.1.1…02…P̲r̲o̲t̲o̲t̲y̲p̲e̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Prototype Verification is an internal verification
(class I). The verification methods used are examination
and test. The purpose of the prototype verification
is
to verify that the prototype meets the basic requirements
of its product specification. This is only applicable
to new design of units, modules and subsystems or modifications
to existing design.
4.2.1.2…02…P̲r̲e̲p̲r̲o̲d̲u̲c̲t̲i̲o̲n̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The preproduction verification (First Article Qualification
Test) is an internal verification (class I). The verification
methods used are examination and test. This verification
shall verify that the preproduction item meets all
the requirements of its product specification. This
verification is only applicable to new design of units,
modules and subsystems or modifications to existing
design.
4.2.1.3…02…P̲r̲o̲d̲u̲c̲t̲i̲o̲n̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The production verification which is internal (class
I) is the verification to be performed on each unit,
module and subsystem following manufacture to ensure
that all items are in accordance with product specification
prior to system integration.
4.2.1.4…02…D̲S̲M̲T̲ ̲(̲P̲r̲o̲t̲o̲t̲y̲p̲e̲)̲ ̲S̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) When the hardware of DSMT System has been integrated
and the system software completed, a DSMT (Prototype)
Acceptance Verification of the integrated system
will be performed.
b) This is an external verification (class II). Upon
SHAPE approval of the results of the tests, the
manufactured systems are baselined.
4.2.1.5…02…F̲a̲c̲t̲o̲r̲y̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) When a CAMPS has been integrated at the factory,
a test will be carried out to verify that all hardware
fulfils the functional specifications. The test
is a subset of the DSMT (Prototype) System Verification.
The subset of test procedures will be identical
to the performance test procedures used for the
DSMT (Prototype) tests, except for the exclusion
of the environmental tests.
b) This test is according to contract document para.
17.4 This is an external verification (class II).
4.2.1.6…02…C̲O̲M̲S̲E̲C̲ ̲I̲n̲-̲P̲l̲a̲n̲t̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The CAMPS equipment will be tested by Purchaser at
the factory. The purchaser will liaise directly with
the national COMSEC authorities where appropriate.
Refer to section 3.4.5.1.
4.2.1.7 A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) The availability and reliability performance characteristics
specified in section 3.4.4 shall be demonstrated
by performing availability measurements/calculations,
in which the values of the module/unit MTBFs and
MTTRs are verified by:
1) Testing/analysis in accordance with sections
4.2.1.7.1, 4.2.1.7.2 and 4.2.1.7.3 or,
2) Provision of acceptable evidence of conformity
to requirements, i.e. evidence supported by
prior observation of system or module performance
over a length of time sufficient to have the
same degree of confidence as the test procedure
that the required availability can be archived.
3) Availability/reliability/maintainability observations
which the contractor wishes to submit in lieu
of testing shall be provided as part of the
R&M Plan for agreement by the purchaser.
b) The set of units and modules, taken together, shall
make up the CAMPS equipment of the R&M model(s)
used for verification of system availability. A
definition of the terms module and unit is given
in section 3.4.4.7 l and m.
c) The R&M Characteristics shall be considered acceptable
if it is verified that the reliability performance
requirements specified in section 3.4.4. are met.
Demonstration that the specified availability requirements
have been met shall be accomplished prior to acceptance
of the first site.
4.2.1.7.1 M̲T̲B̲F̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.2.1.7.1.1 M̲T̲B̲F̲s̲ ̲o̲f̲ ̲3̲5̲0̲0̲ ̲H̲o̲u̲r̲s̲ ̲o̲r̲ ̲L̲e̲s̲s̲
a) Tests shall be performed to measure the MTBF of
all units and modules having a predicted MTBF value
of 3500 hours or less. The contractor need not
test all the individual units of a module being
tested unless the unit has a MTBF value less than
3500 hours and is part of another module which
is not being tested.
b) R&M testing shall be conducted in accordance with
an approved unit or module test plan. The overall
system test programme shall be planned so that
reliability data is obtained from as many functional
tests as possible. In this manner the performance
of reliability testing, per se, will be reduced
to the minimum necessary for the demonstration
of system compliance with the R&M availability
requirements.
c) The R&M Test Programme shall make provisions for
the accumulation of sufficient testing time on
each type of module. The accumulated testing time
shall be equivalent to at least three multiples
of either:
1) the predicted MTBF value of the module with
an MTBF of 3500 hours or less, or
2) the largest predicted unit MTBF value for units
having a predicted MTBF value less than 3500
hours and forming part of a module with a MTBF
value greater than 3500 hours.
d) The R&M test programme shall provide for demonstrating
that unit and module MTBF values are equal to or
greater than the respective predicted values, to
a lower confidence limit value in accordance with
the following schedule:
1) 70% lower confidence limit value at the time
of Factory Acceptance Verification (site 1)
2) 80% lower confidence limit value at the time
of SPA (Site 1)
e) The lower confidence limit values of MTBF shall
be determined from the test data using the following
equation:
2T…0f…M…0e…
MTBF…0f…LCL…0e… …0f…=…0e… …0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f…
2
,f
where
T…0f…M…0e… = the total cumulative module
or
unit operating time obtained
from the test programme
2
,…0f…f…0e… = chi-square value with
probability and f degrees
freedom
= (̲1̲0̲0̲-̲L̲C̲L̲)̲
100
LCL = Specified Lower Confidence
Level, expressed as a percentage
f = 2x(N…0f…p…0e… + 1)
N…0f…p…0e… = the actual number of va-
lid module or
unit failures observed
during the period T…0f…M…0e….
4.2.1.7.1.2 M̲T̲B̲F̲s̲ ̲G̲r̲e̲a̲t̲e̲r̲ ̲T̲h̲a̲n̲ ̲3̲5̲0̲0̲ ̲H̲o̲u̲r̲s̲
a) The contractor shall justify the use of MTBF values
greater than 3500 hours for individual units and
for modules, without redundant units, by means
of analytical calculations. Such calculations shall
use values taken from actual test data on "like"
or similar equipment or from a component analysis,
utilizing values taken from recognized sources,
e.g. reliability and maintainability handbooks
maintained by National Government and by Industry.
b) The preliminary and final R&M Programme Plans shall
identify those units and modules which have predicted
MTBF values greater than 3500 hours, and which
will have the MTBF values justified rather than
tested. The list shall include the predicted value
of MTBF for such units and modules. The list may
be changed as the programme progresses provided
notification is given at least 60 days in advance
of starting or cancelling any planned tests. The
change process contemplated for this list is the
same as that provided in the contract for all items
(data) under Configuration Control except:
1) The contractor's proposals will not include
any consideration of the cost impact for contractor's
proposed change.
2) Such proposals, once mutually agreed for all
project impacts other than cost, will be contractually
implemented at no change in contract price.
3) These change proposals shall be treated as
"critical documents" within the meaning of
Contract Special Provision No. 11, Approval
and Submittal of Documentation.
The analytical calculations for all units, and
modules in this category shall be submitted to
the purchaser for approval at least 60 days prior
to the start of any acceptance testing.
4.2.1.7.2 M̲T̲T̲R̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.2.1.7.2.1 M̲T̲T̲R̲s̲ ̲o̲f̲ ̲4̲5̲ ̲M̲i̲n̲u̲t̲e̲s̲ ̲o̲r̲ ̲L̲e̲s̲s̲
a) Tests shall be performed to measure the MTTR of
all types of units and modules with a predicted
MTTR value of 45 minutes or less.
The contractor need not test individual units of
a module that is being tested unless the unit is
also a part of another module that is not being
tested.
b) The tests shall be carried out in accordance with
an approved R&M Unit or Module Test Plan. The overall
test programme shall be planned so that data related
to maintainability is obtained from as many functional
tests as possible. In this manner the performance
of maintainability testing, per se, will be reduced
to the minimum necessary for the demonstration
of system compliance with the R&M availability
requirements.
c) The MTTR measurements shall include corrective
and preventive maintenance actions, the time to
localise the failure to a particular module, time
to replace the failed module, verify the repair
action and restoring the system to operational
configuration exclusive of any software load requirements.
The MTTR does not include the repair time of the
failed module. The R&M test programme shall provide
for demonstrating that unit and module MTTR values
are less than or equal to the respective predicted
MTTR values to an upper confidence limit value
in accordance with the following schedule:
1) 70% upper confidence limit value at the time
of Factory Acceptance Verification (Site 1).
2) 80% upper confidence limit value at the time
of SPA (Site 1).
d) The upper confidence limit values of MTTR shall
be determined from the test data by the following
equation:
̲
MTTR…0f…UCL…0e… = X + (t …0f…,f…0e…) . ̲S̲ ̲
…0e…N…0f…
where
̲
X = the observed statistical mean of
the measured maintenance action
periods:
̲
X
X = ̲ ̲i̲
N
Where X…0f…i…0e… are the individual observations and N is the
number of test measurements.
t …0f…,f = Students t-value with probability and
f degrees of freedom,
= (̲1̲0̲0̲-̲U̲C̲L̲)̲
100
UCL = Specified Upper Confidence Limit expressed
as
a percentage.
f = (N-1),
S = Observed standard deviation of the measured
maintenance action periods:
̲
S…0e…2…0f… = (X…0f…i…0e… - X)…0e…2…0f…/(N - 1)
4.2.1.7.2.2 M̲T̲T̲R̲s̲ ̲G̲r̲e̲a̲t̲e̲r̲ ̲T̲h̲a̲n̲ ̲4̲5̲ ̲M̲i̲n̲u̲t̲e̲s̲
a) The preliminary and final R&M Programme Plans shall
identify those units and modules that have MTTR
values greater than 45 minutes, together with the
predicted MTTR values. Reasons for assigning a
MTTR value in excess of 45 minutes to a unit or
module shall be given and shall explain the maintenance
procedures involved in restoring such a unit or
module to service when a malfunction occurs.
Justifying analyses to prove that the overall availability
requirements can be met with units having MTTR
values in excess of 45 minutes shall be provided.
b) The list of units and modules having MTTR values
greater than 45 minutes may be changed as the programme
progresses provided notification is given at least
60 days in advance of starting any testing or cancelling
any planned tests. The change process contemplated
for this list is the same as that provided in the
contract for all items (data) under Configuration
Control except:
1) The contractor's proposals will not include
any consideration of the cost impact for contractor's
proposed change.
2) Such proposals, once mutually agreed for all
project impacts other than cost, will be contractually
implemented at no change in contract price.
3) These change proposals shall be treated as
"critical documents" within the meaning of
Contract Special Provision No. 11, Approval
and Submittal of Documentation.
4.2.1.7.3 R̲&̲M̲ ̲U̲n̲i̲t̲ ̲o̲r̲ ̲M̲o̲d̲u̲l̲e̲ ̲T̲e̲s̲t̲ ̲P̲l̲a̲n̲s̲
The MTBF and MTTR for each unit and module shall be
part of a R&M Unit and module test plan which in detail
will specify how the MTBF and/or MTTR is to be verified
either by test, analysis or presentation of evidence
of conformity.
4.2.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.2.2.1 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The software development verification is an internal
verification (class I) performed during the development
of the software.
All software and parts thereof shall be thoroughly
tested at each step of development and integration.
4.2.2.2 I̲n̲ ̲P̲l̲a̲n̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
In plant software verification (class II) shall be
performed as outlined in the software test plan.
The software test will be performed in the factory
with a simulated environment specified in section 3.5.11.5.2.
The status information on request refer section 3.2.3.6
shall not be used during acceptance test of busy hour
performance. The test criteria requires an accumulated
test time of 240 hours with the following allowable
errors:
a) C̲a̲t̲e̲g̲o̲r̲y̲ ̲1̲
a total of 1 error allowed of the following types:
- Loss of a message or other transaction.
- Corruption of a message or other transaction.
- A message or transaction being missent.
- Misapplication of security rules.
- Failure of accounting procedures.
b)\C̲a̲t̲e̲g̲o̲r̲y̲ ̲2̲
A total of 2 errors allowed of the following types:
1) loss of service to more than 25% of all
channels and user connecting points.
2) loss of service to more than 50% of all
operating positions or system reporting
facilities.
3) Loss of ability to recover the system.
c) C̲a̲t̲e̲g̲o̲r̲y̲ ̲3̲
a total of 3 errors allowed of the following types:
1) errors not included in 1 and 2 above.
d) The software Test Plan shall specify the tests
which will provide the reliability prediction to
calculate the probability that the MDSD of:
1) category 1 SW errors is 240 hours
2) category 2 SW errors is 120 hours
3) category 3 SW errors is 80 hours
4.2.2.3…02…S̲o̲f̲t̲w̲a̲r̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) At the first site (SHAPE) CR shall conduct a formal
functional test (class II) to verify basic system
functions and interfaces. The test will be supervised
by CR test engineers and SHAPE operational staff
will assist in operating the system.
b) NICS-TARE, ACE CCIS, and SCARS II are planned to
be available, however, in the event one or more
of the interfaces are not available, the contractor
shall proceed with all of those components of the
system that are independent of the missing interfaces.
c) In this event SHAPE will give Site Provisional
Acceptance, not withstanding the inability to test
all interfaces, providing all other aspects of
the test are satisfactorily completed.
4.2.2.4…02…S̲o̲f̲t̲w̲a̲r̲e̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) Immediately after successful completion of the
Software Functional Verification at the SHAPE site,
an Operational Test (class II) shall take place
in order to verify the reliability of the software
system. The status information on request shall
(refer section 3.2.3.6) not be used during busy
hour test performance.
b) The operational test will take place under CR control
but SHAPE personnel will operate the system in
a live operational mode in accordance with agreed
test plans and procedures.
c) The acceptance test criteria shall be that the
CAMPS system shall be able to execute the basic
software functions according to the approved System
Requirements Specification for a period of 60 calendar
days in a live operational mode without any software
failure.
d) Any software failure, which concept will be defined
in the acceptance test plan, shall require a complete
retest cycle. The duration of the test or retest
may be shortened at SHAPE's discretion.
4.2.3…02…S̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.2.3.1…02…C̲O̲M̲S̲E̲C̲ ̲O̲N̲-̲S̲i̲t̲e̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) When the CAMPS computer equipment and peripherals
have been installed on-site, a COMSEC verification
will be performed by the national COMSEC authorities.
b) Purchaser will supervise the verification and Christian
Rovsing A/S test engineers will assist in operating
the system. The COMSEC on-site verification is
a formal verification (class II). The verification
shall take place in conjunction with the SPA.
4.2.3.2…02…S̲i̲t̲e̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲a̲l̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲(̲S̲P̲A̲)̲
a) Site provisional acceptance is the act whereby
SHAPE will acknowledge by protocol that CR has
fully demonstrated that a site is complete and
ready for initial operation and will take place
when the following requirements have been met:
1) Completion of an agreed on-site acceptance
test.
2) Verification of the site inventory.
3) If applicable, availability of a mutually agreed
discrepancy list showing the agreed date for
clearance of each listed discrepancy.
