top - download
⟦05f86d042⟧ Wang Wps File
Length: 49490 (0xc152)
Types: Wang Wps File
Notes: Crossfox tilbud
Names: »1801A «
Derivation
└─⟦e1d52bc1b⟧ Bits:30006228 8" Wang WCS floppy, CR 0137A
└─ ⟦this⟧ »1801A «
WangText
'…09…'…0e…'
&…08…&…0d…& %…08…%…0d…%…02…%…07…$…0c…$…02…#…08…#…0c…#…0d…#…0e…# "…0a……86…1
…02…
…02…
…02…
…02…
APPENDIX
I OF VOL
IV
1982-03-05
MESSAGE
SUBSYSTEM
Page
#
TECHNICAL
PROPOSAL
5. L̲I̲N̲E̲ ̲C̲I̲R̲C̲U̲I̲T̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲S̲ ̲A̲N̲D̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
The rules and standards to be followed when implementing
the different line circuits and interfaces for the
MPF system will comply with the standards described
in IFB Part III annex 5D to 5H and 5K to 5N with reference
to circuit characteristics and annex 5A, 5B, 5C and
5I with reference to message formats and control.
The line circuit standards to be followed will be the
CCITT's recommendation V24 and V28. All communication
lines leaving the MPF area will be implemented with
secure wires using low level signalling.
The line transmission quality for dedicated lines and
local user lines will be within the CCITT's Recommendations
G.132 and G.133 - Orange Book, Vol. III, Geneva 76.
The MPF subsystem exchange ACP127 and ACP126 messages
with shore based commanders via the NICS TARE and TRC
systems and with ship-borne commanders via the Ship-to-Shore,
Broadcast and MRL subsystems. Service messages for
communications control will be composed and dispatched
automatically, as part of the message level protocols.
5.1 N̲I̲C̲S̲ ̲T̲A̲R̲E̲
CHRISTIAN ROVSING A/S will, for the MPF subsystem,
implement an interface to NICS TARE in accordance with
the Nato approved document "NICS TARE Interface", CPS/ICD/004
which is used for the CAMPS project.
This interface document complies fully with Annex 5N
of the IFB except for the following:
- CPS/ICD/004 defines both colocated and remote NICSTARE
connections, only the colocated connection shall
apply for Crossfox.
- CPS/ICD/004 defines ITA No. 5 as character code.
CR will implement either ITA No. 2 or ITA No.
5. The decision as to which code shall be used
will be made during the design phase.
- CPS/ICD/004 defines the EDC link protocol document
updated with DCN G2. CHRISTIAN ROVSING A/S will
implement the EDC link protocol in accordance with
the referenced document, updated with DCN G9, dated
1 May 1981.
5.2 T̲A̲P̲E̲ ̲R̲E̲L̲A̲Y̲ ̲C̲E̲N̲T̲R̲E̲ ̲(̲T̲R̲C̲)̲
The interface to TRC will be implemented in compliance
with the requirements laid down in Annex 5D of the
IFB.
CHRISTIAN ROVSING A/S has implemented a TRC interface
for the CAMPS system in accordance with the NATO approved
document, "TRC, POINT-TO-POINT CONNECTION Interface",
CPS/ICD/007, which complies with Annex 5D.
5.3 B̲R̲O̲A̲D̲C̲A̲S̲T̲ ̲C̲I̲R̲C̲U̲I̲T̲
The interface provided for the Broadcast circuits will
have the following characteristics:
a) Physical Interface:
- The connection will be via a crypto/low speed
link. The cryptos will be of type KW7, KW46T
or KW37T.
- The electrical interface will be in accordance
with the CCITT's recommandation V24/V28 low
level specification
- The MPF will control the synchronization of
the Crypto's using V24 signals and special
crypto control equipment.
- The transmission will be asynchronous simplex
with baud rate of 75 bps.
- A seven bit character code will be used with
one start bit, five data bits, and one stop
bit.
b) F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
- The alphabet will be ITA No. 2
- All messages transmitted will conform to
the applicable sections of ACP127 Supp.
1 and 3.
- Messages related to maintenance and control
of the communication lines are either treated
by the supervisor manually or generated/analyzed
by the MPF automatically.
5.4 S̲h̲i̲p̲-̲t̲o̲-̲S̲h̲o̲r̲e̲ ̲C̲i̲r̲c̲u̲i̲t̲s̲
The interface provided for the Ship-to-Shore circuits
will have the following characteristics:
a) Physical Interface:
- The connection will be via a low speed crypto
(KW7) link.
- The electrical interface will be in accordance
with the CCITT's recommendation V24/V28 low
level specification.
- The transmission will be asynchronous simplex
with baud rate of 75 bps.
- A seven bit character code will be used.
b) Functional Interface
- The alphabet will be ITA No. 2
- All messages received will be in either ACP127
format or ACP126 format.
- Messages related to maintenance and control
of the communication lines are laid down in
ACP127 supp. 1 and 3.
5.5 M̲a̲r̲i̲t̲i̲m̲e̲ ̲R̲e̲a̲r̲ ̲L̲i̲n̲k̲ ̲(̲M̲R̲L̲)̲
The interface provided for the MRL circuits will have
the following characteristics.
a) Physical Interface
- The circuits will interface to the crypto KW7
for each circuit.
- The electrical interface will be in accordance
with the CCITT's recommendation V24/V28 low
level specification.
- The transmission will be asynchronous full
duplex with baud rate of 75 bps.
- A seven bit character code will be used
- crypto control will be performed by a special
crypto control equipment
b) Functional Interface
- The alphabet will be ITA No. 2
- All messages received or transmitted will be
either ACP127 format or ACP126 format.
- Messages related to maintenance and control
of the communication lines are either treated
by the supervisor manually or generated/analyzed
by the MPF automatically.
5.6 C̲I̲R̲C̲U̲I̲T̲ ̲T̲O̲ ̲S̲T̲A̲N̲D̲B̲Y̲ ̲M̲C̲
The interface provided for the purpose of exchange
of message traffic between the two MC's will have the
following characteristics:
a) Physical Interface
- The circuit will interface to the BID 1000
equipment.
- The electrical interface will be in accordance
with the CCITT's recommendation V24/V28 low
level specification.
- The transmission will be full-duplex with a
baud rate of 2400 bps. allocated for the MPF.
b) Functional Interface
- EDC LITSYNC is proposed as the link level protocol
to minimize the number of protocols
- The alphabet will be ITA No. 5.
- Information to be transmitted to the standby
MC will be of type:
- stored messages
- status information
- accounting information
- control information
5.7 T̲e̲r̲m̲i̲n̲a̲l̲ ̲C̲i̲r̲c̲u̲i̲t̲
The terminals to be used when operating the MPF consist
of VDU's and Receive Only Printers . The circuits
to these terminals will have the following characteristics.
- The electrical interface will be in accordance
with the CCITT's recommendation V24
- The transmission to/from the VDU's will be asynchronous
full duplex with baud rates from 600 bps to 9600
bps.
- The transmission to the RO Printers will be asynchronous
with baud rates from 600 bps to 1200 bps.
- The interface to the VDU/printer workstation in
the MCSF room will be made via secure optofiber
cables.
5.8 E̲l̲e̲c̲t̲r̲i̲c̲a̲l̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲ ̲o̲f̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲o̲r̲t̲s̲
The communications ports provided by the MPF will belong
to the following types:
- Low speed - operating asynchronously at any of
the following rates: 50/75/100 baud
- Medium speed - operating asynchronously at any
of the following rates: 600/1200/2400/4800/9600
bps
- Medium speed - operating synchronously at any of
the following rates: 600/1200/2400/4800/9600 bps.
Change from one rate to another rate within the same
group is achieved hardware wise by a switch and software
wise by a command.
The electrical signal levels at the external interface
will conform to the requirements laid down in CCITT
Rec V28 low level interface (+6 V/0/-6V). All control
leads provided will belong to the set defined in CCITT
Rec V24 with in addition to any required for cryptographic
control and warning purposes.
5.9 C̲r̲y̲p̲t̲o̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
External traffic channels, wherever required, will
be equipped with purchaser supplied cryptographic equipment.
The MPF will be designed to operate with the following
types of cryptographic equipment without manual intervention
except that associated with key changing and maintenance
operations:
1. KW7/BID 660
2. BID 1000
3. KW37T
4. KW46T
For equipment (1) and (2), the MPF will detect the
"control and warning" signals generated by the cryptographic
equipment and will raise an alarm at the supervisory
work station and inhibit transmission of traffic on
the channels involved whenever a malfunction is detected
and/or the cryptographic equipment unit reverts to
the non-cypher mode of operation. No warning signal
will be detected in the case of equipment (3) and (4).
The contractor will be responsible for integrating
the cryptographic equipments into the CROSSFOX system.
6. L̲O̲G̲I̲S̲T̲I̲C̲S̲ ̲S̲U̲P̲P̲O̲R̲T̲
6.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̲
6.1.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲
a) Christian Rovsing A/S (CR) will make the following
major deliveries to customer:
- Transportation and Installation Plan
- Site Preparation Requirements
- Equipment Installation Drawings
- Delivery and Installation of Equipment
b) The "Transportation and Installation Plan" will
contain CR's procedures for transportation and
installation. Furthermore, the plan specifies division
of responsibilities between customer and CR regarding
transportation and installation. Packaging of central
equipment and peripherals will correspond to requirements
for air and truck transport to the two MC sites.
c) Site Preparation Requirements (SPR) will specify
the extent of site preparation customer must undertake
before equipment is installed. In order to generate
the SPR, CR will conduct a Site Survey at each
site.
d) The equipment installation drawings will show how
the equipment is to be installed and integrated
on site.
e) Delivery and installation of equipment will be
performed in accordance with the master schedule
after CR has verified that the sites have been
prepared in accordance with the Site Preparation
Requirements.
6.1.2 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
a) Planning of the installation will start immediately
after contract award. The time span from contract
award to completion of installation will be divided
in to major phases regarding installation planning:
1) Site Preparation
2) Site Installation
b) The main activities in phase 1 are:
1) Site surveys within two months after contract
award
2) A transportation, installation and integration
plan specifying the activities to be performed
during phases 1 and 2.
3) Preparation and delivery of site preparation
requirements 6 months prior to on-site installation.
4) Preparation and delivery of equipment installation
drawings 3 months prior to on-site installation
5) Site readiness verification prior to start
of equipment installation.
c) The main activities in phase 2 are:
1) Transportation to sites
2) On-site installation
d) A more detailed description of phase 1 and 2 activities
is presented in the following sections.
6.1.3 S̲i̲t̲e̲ ̲S̲u̲r̲v̲e̲y̲s̲
a) During the first 2 months after contract award
CR will perform site surveys with customer participation.
The purpose is to verify the site information given
in the invitation to tender and to collect supplementary
information. The results of the survey will be
used by CR to prepare site preparation requirements
and plans for on-site integration and installation.
b) An important task to be performed during the survey
meetings is to determine an equipment room layout.
c) CR will prepare a list of site documentation (equipment
room drawings and installations) to be given to
CR at the meeting and submit it to customer prior
to the site survey.
6.1.4 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̲ ̲P̲l̲a̲n̲
a) CR will prepare a transportation and installation
plan which will specify the activities to be performed
during phases 1 and 2. The plan will be submitted
to customer 2 months after completion of site surveys.
b) The plan will cover the following areas:
1) Delivery of site preparation requirements (SPR)
and equipment installation drawings.
2) Site readiness verification.
3) Packing, shipment, customs clearance and transportation
to site.
4) A specification of the division of responsibilities
between customer and CR concerning transportation
and installation.
5) On-site integration and installation.
6.1.5 S̲i̲t̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲
a) CR will prepare site preparation requirements (SPR)
concerning the preparation of each site for installation
of the proposed equipment. The SPR will be submitted
to customer for approval 6 months prior to start
of installation at each site.
b) The SPR will be based on the site data collected
during the site survey, the equipment room layout
and the physical characteristics of the proposed
equipment.
c) The SPR will contain requirements to access, space,
power, power distribution, quantity and location
of power outlets, heat dissipation, cable ducting,
etc.
d) Customer will prepare the site for equipment installation
in accordance with these requirements.
6.1.6 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲D̲r̲a̲w̲i̲n̲g̲s̲
a) CR will deliver equipment installation drawings
to customer for approval 3 months prior to start
of installation. The drawings will show how the
proposed equipment is to be installed and integrated.
b) The approved installation drawings will be used
for the installation of the proposed equipment
on each site.
c) The equipment installation drawings will be based
on the approved site preparation requirements,
the hardware configuration and the equipment characteristics.
6.1.7 S̲i̲t̲e̲ ̲R̲e̲a̲d̲i̲n̲e̲s̲s̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) Prior to start of on-site installation CR and customer
will jointly perform a site verification.
b) The purpose is to verify that the site is ready
for installation, i.e. that the site is prepared
in accordance with the site preparation requirements.
c) Final arrangements concerning transportation to
site and CR presence at site during installation
and test are also to be made at time of site verification.
6.1.8 T̲r̲a̲n̲s̲p̲o̲r̲t̲a̲t̲i̲o̲n̲
a) The delivery of equipment will follow the master
schedule. Actual shipping dates are selected to
be in accordance with the readiness of site and
time for transportation.
b) The equipment will be shipped by air or truck and
packed accordingly. CR will try to arrange the
transportation so that his installation team will
be present at site for reception.
c) The packing and marking are proposed in accordance
with CR's standard procedures for CR80 equipment.
The following is a description of the method:
d) The computer equipment is constructed in a modular
fashion, i.e. 19" racks containing crate assemblies
with plug-in modules. This is reflected in the
packaging as follows:
1) Modules are packed in styropor containers designed
to fit each module size. A number of modules
are put into a card board box or similar of
Europe pallet standard size (see figure 6.1-1)
2) Crates are packed with styropor corners so
that they fit into a card board box of Europe
pallet standard size (see figure 6.1-2).
3) Each rack or cabinet bay is separately packed
on a wooden pallet, protected with styropor
corners, and wrapped in plastic sheets. A skeleton
of timber protects the five free surfaces.
e) Packing lists are forwarded with every shipping
container. One copy of the packing list is enclosed
in the container; one copy will be attached to
the exterior of the container in an envelope clearly
marked "packing list".
As requested in the IFB, 2 copies of each packing
list will be provided to the customer. Each packing
list will contain the following information:
1) Shipping address
2) Package number
3) Contract number
4) Contract item number
5) Item description
6) Part number
7) NATO stock number (If available)
8) Serial number (If available)
9) Quantity shipped
f) Each container is to be clearly marked on the exterior
surface with at least:
- purchaser identification (PROJECT no., contract
no., contract item no.)
- manufacturer's name and address
- shipping address
In addition each container is clearly marked with
package no. and precautionary marking applicable
to handling.
g) Since the shipping documents to be exchanged between
the two parties are to be defined, the following
is proposed:
- packing lists
- proforma invoice
- customs document
- bill of lading.
Fig. 6.1-1
Packing of a Module
Fig. 6.1-2
Packing of a Crate
6.1.9 S̲i̲t̲e̲ ̲I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
a) CR will prepare internal site installation procedures
based on the site preparation requirements and
the site installation drawings. These procedures
will detail the installation sequence and the installation
check-out procedures.
b) CR will set up an installation team to perform
the installation at the two MC sites. The team
will be working in accordance with the detailed
installation procedures.
c) The team will install the equipment in accordance
with the customer approved installation drawings.
Any changes during installation will be marked
on the drawings. Corrected drawing will be submitted
to customer after completion of site installation.
d) Installation check-out encompassing hardware verification
will be performed in accordance with an installation
check-out procedure. This task will complete the
installation and indicate the start of acceptance
test (refer to section 7.4).
6.1.10 T̲y̲p̲i̲c̲a̲l̲ ̲L̲a̲y̲o̲u̲t̲
a) A typical equipment room layout of the Site 101
and Site 301 installation is shown in figure 6.1-3
and 6.1-4. One of the tasks to be performed at
site surveys, as mentioned earlier, is to work
out the optimal layout in conjunction with customer.
The equipment in the layout comprises:
- 3 computer racks
- 2 disc cabinets
- 4 operator positions consisting of:
4 visual display units (VDU)
2 medium speed printers (MSP)
- 1 work station consisting of
1 tempest VDU
1 tempest MSP
- 1 Engineering position consisting of
1 VDU
1 Printer
b) The racks are positioned such that sufficient clearance
is maintained for access to front and rear of the
equipment. Otherwise, only few constraints as
to the placement of the equipment exist. The final
layout will take into account human factors, segregation
of functional activities, access for maintenance
and other considerations or preferences of the
operating personnel.
c) The typical layout reflects the floor space required
by cabinets and the operator positions. Either
top or bottom cable entrance to the racks can be
accomodated, depending on whether or not the equipment
room is provided with a computer floor. The heaviest
rack is well within the standard limit of 1000
Kg/m…0e…2…0f… for computer floors.
d) All equipment is mounted in standard 19" racks
except for the disk units which are contained within
acoustic cabinets. The dimensions are shown in
table 6.1-1. The equipment is cooled by fans with
intake in the front and exhaust at the top.
e) Power to equipment is fed from individual fuse-protected
240 V/50 HZ or 220 V/50 HZ outlets (10A or 16A).
The required power consumption is shown in table
6.1-1. The standard CDC disc drives require a frequency
stabilization of 50Hz + 0.5/-1.0 Hz for proper
operation (according to CDC specification).
f) The supervisor engineering position and operator
positions will be inter-connected by the contractor
and so will the work station. The TEMPEST equipment
at the work station will be interconnected with
optical fibre cable. It is assumed that the customer
will perform all cabling out of the equipment room.
g) Besides the equipment shown on the equipment room
layout contractor will install 4 message compilation
units (MCU) in the crypto room.
Fig. 6.1-3 Site 101, equipment room layout
Fig. 6.1-4 Site 301 Equipment Room Layout.
POSITION DIMENSIONS WEIGHT POWER
No. DESCRIPTION UNIT UNIT CONSUMPTION/
HxWxD(M) (KG) UNIT
STEADY STATE
(W)
1-3 COMPUTER
RACK 1.8x0.6x0.8 250 1400
4,5 DISC
CABINET 0.92x0.59x0.92 252 1600
6-9 OPERATOR
POSITIONS 1.2x1.2x0.8 60 300
10,11,13,15 MEDIUM
SPEED
PRINTER 1.0x0.70x0.62 55 250
12 WORK STATION 1.2x1.2x0.8 60 300
14 ENGINEERING 1.2x1.2x0.8 60 300
TOTAL POS.1 - 15: 10,2 kW
Table 6.1-1
Preliminary Physical Characteristics
6.2 D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲
6.2.1 M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲a̲n̲d̲ ̲O̲r̲g̲a̲n̲i̲z̲a̲t̲i̲o̲n̲
The training section, which is part of the Integrated
Logistics Support department, see fig. 6.2-1 is responsible
for development and conduct of customer training and
the documentation delivered with the systems.
Figure 6.2-1 Organization of…01…Integrated Logistics Support
The training section is organized with a manager, technical
writers, and instructors.
The combination of user documentation and training
ensures that the training is supported by documentation,
which is not only easy to use, but also complements
the training documentation, enabling effective training
in all aspects.
6.2.2 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
The following documentation is proposed incorporated
in the CR's total documentation of the CROSSFOX system:
- Equipment Handbooks
- Maintenance Manual
- System Handbook
- Operator Handbook
6.2.2.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲
Each module is documented in a Technical Manual, including:
- Product Specification
- Functional Description
- Parts Lists
- Assembly Breakdown
- Diagrams
6.2.2.2 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲M̲a̲n̲u̲a̲l̲
A maintenance manual is supplied for incorporation
in the CR's overall maintenance manual.
The maintenance manual includes:
- Introduction
- Operating Procedures
- Preventive Maintenance
- Corrective Maintenance
- Software Updating Procedures
- Failure Reporting System
- Tools and Test Equipment
- Appendix
6.2.2.3 S̲y̲s̲t̲e̲m̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲
A System Handbook is developed and delivered for incorporation
in the CR's overall CROSSFOX System Handbook.
The System Handbook includes:
- Introduction
- System Overview
- Operational Capabilities
- Functional Capabilities
- Hardware Description
- Software Description
- System Maintenance Overview
- Appendix
6.2.2.4 O̲p̲e̲r̲a̲t̲o̲r̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲
An Operator Handbook is delivered for incorporation
in the CR's system handbooks.
The Operator Handbook includes:
- Introduction
- Operation of Peripherals
- Step-by-step procedures
- Error messages and handling
- Abbreviations
- Appendix
6.3 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲A̲N̲D̲ ̲S̲U̲P̲P̲O̲R̲T̲
6.3.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
Based on the information given in the IFB the following
major requirements to the MS subsystem can be stated.
1) Levels of maintanance:
a) site maintenance consists of
- replacement of subassemblies
- minor repairs
- preventive maintenance
b) depot maintenance includes repair of defect
subassemblies
c) vendor repair used as applicable
2) The equipment must include maintenance and diagnostic
software to aid in troubleshooting.
3) CR will maintain the MS equipment from time of
installation to Site Provisional Acceptance (SPA).
4) Lifetime support of the subsystem must be available
from CR.
5) Hardware warranty is 24 months from SNT iii
6) Software warranty is 36 months from FSA
6.3.2 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
6.3.2.1 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
The purpose of the Maintenance Planning Phase is to
establish a complete maintenance program which will
fulfil the contractual requirements for maintenance.
Simultaneously, it shall provide a solid base for the
development of the detailed maintenance documentation.
At the end of the planning phase a maintenance plan
will be delivered by Christian Rovsing A/S to Prime
Contractor.
The maintenance plan will cover the subjects illustrated
in Fig. 6.3-1.
The Maintenance Plan will provide a general description
of the MS maintenance concept. The information will
be used by Prime Contractor for incorporation in the
overall Maintenance Plan.
Fig. 6.3-1…01……01…Overview of Maintenance Plan
6.3.2.2 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Christian Rovsing A/S will develop maintenance procedures
for the MS covering preventive as well as corrective
maintenance. These procedures will be incorporated
into the overall maintenance manual for the MC.
The procedures will make reference to other site documentation
delivered with the MS such as Hardware Breakdown, Peripheral
Equipment Manuals, etc.
6.3.2.3 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲A̲c̲t̲i̲v̲i̲t̲i̲e̲s̲
a) P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Preventive maintenance will be carried out by customer's
personnel in accordance with the procedures established
in the maintenance manual.
b) C̲o̲r̲r̲e̲c̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲
Corrective Maintenance, i.e. fault identification
and module replacement, will be carried out by
customer's trained technicians. Repair of defective
subassys will be undertaken by Christian Rovsing
A/S at no cost during the warranty period.
Implementation of field changes will be done by
customer's technicians after instructions from
prime contractor.
Isolation of faulty subassys is accomplished by
the use of both on-line and off-line diagnostic
software programs. On-line error detection programs
will detect hardware faults when they occur. This
is accomplished both by background checks and error
detection during data transfer from one subsystem,
to another. Depending on the type of fault the
"Watchdog" subsystem will reconfigure the system
designating the stand-by processor as active.
The defective subsystem is now off-line for further
fault diagnosis. If the on-line diagnostic program
did not give specific error identifications pinpointing
a specific module, the off-line diagnostic will be
activated. This program provides for a much more thorough
check of the various elements of a subsystem. In addition,
this program will be used to verify repaired modules.
6.3.3 S̲u̲p̲p̲o̲r̲t̲
6.3.3.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲S̲u̲p̲p̲o̲r̲t̲
Christian Rovsing A/S will provide facility for repair
of hardware modules delivered as part of the MS. The
repair service will be available both during the warranty
period as well as after expiration of warranty.
Spares will be available for purchase during the life
of the program on terms and conditions stated in the
contract.
6.3.3.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲p̲p̲o̲r̲t̲
Christian Rovsing A/S will, on request, provide software
support after expiration of the software warranty period.
During the warranty period Christian Rovsing A/S will
have the full warranty obligation provided customer
has not implemented changes to the software.
6.3.3.3 O̲t̲h̲e̲r̲ ̲S̲u̲p̲p̲o̲r̲t̲
Christian Rovsing A/S is prepared to train customer's
personnel in software programming and depot repair
of hardware modules. Please refer to section 6.5 Training,
for a description of the courses proposed to be delivered
under this program
6.4 S̲P̲A̲R̲E̲S̲ ̲A̲N̲D̲ ̲C̲O̲D̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
6.4.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
1) A complete list of the Bill of Materials (BOM)
shall be provided for each equipment. The BOM shall
be to component level.
The BOM may be provided with any suitable format
giving the following information:
a) Indenture code (drawing/family tree relationship)
b) Actual Manufacturer's part number and manufacturer's
name of code
c) Sub-contractor (equipment suppliers) part number,
if assigned
d) Description
e) Quantity used per next higher assembly
f) Quantity used per end item (major unit/equipment)
g) Delivery lead time (months)
h) MTBF's (for units, modules, and sub-assemblies)
i) Unit price
The BOM, including supporting information, will
be used for spares provisioning information only.
2) Supply of spares must be guaranteed for a period
of 20 years
3) Codification will be required, -level is to be
defined
6.4.2 S̲p̲a̲r̲e̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
Christian Rovsing A/S will use their expertise and
computerprograms developed under the CAMPS program
to fulfil the requirements stated in 6.4.1 above.
The Maintenance and Support Section of the Integrated
Logistics Support Department is responsible for Spares
Management.
6.4.3 R̲S̲P̲L̲
Assumptions
- The RSPL recommends modules to be stored at each
site based on the assumption that the site should
be selfsupporting in 90 days with an 80% confidence
level.
- The MIA module (CR8071 M/010--/00) is added as
an insurance item. It is possible directly to
connect a VDU to the MIA in order to troubleshoot
a defective PU thus disregarding the WD.
- It is assumed that peripherals are generally repaired
or exchanged locally. Hence no spare modules have
been specified.
- A spare kit for the SMD disks has been recommended.
The kit is based on vendor's recommendation.
The PCBs included will largely cover both the 80MB
and the 150MB disk.
A list of deliverable spare parts is given in table
6.4-1. For prices see price quotation vol. V.
Figure 6.4-1
Deliverable Spare Parts
6.5 T̲R̲A̲I̲N̲I̲N̲G̲
6.5.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
Based on information in the IFB, and Christian Rovsing's
previous experience from similar projects, the following
training requirements are listed:
a) One hardware course will train the technicians
in the maintenance of the system.
b) One software course will train 2 high-level software
specialists in diagnosing and maintaining the software.
c) One On Job Training, OJT, course is conducted at
each of the two sites. The course will include
start-up, running, and close-down of the system.
6.5.2 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲s̲
A training plan is developed for each of the courses,
giving an overview of how the courses are developed
and conducted.
Facilities, equipment, and course content are defined
in the plans.
6.5.3 C̲o̲u̲r̲s̲e̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
Courses will cover the following system components:
- CR80 Computer System
- Software
- System Operation (OJT)
6.5.3.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲C̲o̲u̲r̲s̲e̲
This course is conducted at Christian Rovsing A/S'
facilities in Copenhagen on customer equipment.
Contents of Course:
- Operation of the CR80 System
- Maintenance of the CR80 System
- Troubleshooting of the CR80 System
- Repair of the CR80 System
- Reconfiguration of the CR80 System
Previous knowledge required:
- 3 years experience in operation and maintenance
of electronic radio equipment
- some knowledge of digital- and microprocessor techniques
- a minimum English language vocabulary of 1500 words
Number of participants: 15
Length of course: 6 weeks of 30 lessons
6.5.3.2 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̲
The course is conducted at Christian Rovsing A/S facilities
in Copenhagen.
This course is partly based on an instructor tutoring
two software specialists, and partly based on self-study
of manuals and guides.
Contents of Course:
- DAMOS Operating System
- Software environment
- Utilities
- SWELL Programming
Previous knowledge required:
- a detailed knowledge of software techniques, i.e.
queue techniques, access methods, post- and file
organization, etc.
- at least 2 years experience in designing and coding
programs in assembler and one high-level language
(preferably Pascal).
Number of participants: 2
Length of course: 3 weeks of 30 lessons
6.5.3.3 O̲J̲T̲ ̲C̲o̲u̲r̲s̲e̲s̲
Two courses are conducted at the customer sites (one
each). The courses are conducted by an experienced
installation engineer in cooperation with the contractor.
Contents of Course:
- Operation of the CR80 System
- Start-up and Close Down procedures
- Emergency procedures
- Reconfiguration of the CR80 System
Previous knowledge required:
As described for the hardware maintenance course.
Lenght of course: 1 week of 15 lessons.
6.5.4 T̲r̲a̲i̲n̲i̲n̲g̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲s̲
6.5.4.1 T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
The training plan for each course defines
- the training strategy
- the training methods
- contents of the course
- schedules and sequence of instruction
- equipment
- facilities
6.5.4.2 I̲n̲s̲t̲r̲u̲c̲t̲o̲r̲'̲s̲ ̲T̲e̲x̲t̲ ̲B̲o̲o̲k̲
The instructor's text book includes
- Instructors Guide Sheets and Lesson Plans, defining
goals and procedures through a lesson. Please refer
to Fig. 6.5-1 and 6.5-2.
- Extracts from existing documentation, applicable
for the lesson(s).
- Copies of visual aids, tests, group works, etc.
6.5.4.3 H̲a̲n̲d̲b̲o̲o̲k̲s̲
Manuals and guides are supplied for the training, where
applicable.
Figure 6.5-1
Instructor's Guide Sheets
Figure 6.5-2
Instructors Lesson Plan
6.5.4.4 T̲r̲a̲i̲n̲i̲n̲g̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲s̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Student Hand-Out is supplied, including
- Manuals, where applicable
- Extracts from existing documentation
- Tasks
- Groupwork exercises
- Quizzes and tests
- Copies of visual aids
6.5.4.5 V̲i̲s̲u̲a̲l̲ ̲A̲i̲d̲s̲
The following types of visual aids are supplied:
- Wall Charts
- Photographic slides and films
6.5.4.6 M̲o̲d̲e̲l̲s̲ ̲a̲n̲d̲ ̲D̲e̲m̲o̲n̲s̲t̲r̲a̲t̲i̲o̲n̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Where demonstration equipment is not available, models
are supplied.
6.5.5 T̲r̲a̲i̲n̲i̲n̲g̲ ̲T̲e̲c̲h̲n̲i̲q̲u̲e̲s̲
The main principle of Christian Rovsing A/S's courses
is that student-centered training methods are used
wherever possible.
To evaluate the outcome of the courses, oral questions,
quizzes, and tests are used during the courses, and
a final practical and theoretical test is performed
by the participants.
The following training methods are used during the
courses:
a) Group-work: Specific tasks are distributed
in writing to the groups to work
on. The tasks may be theoretical
or practical examination of the
various topics.
b) Reports: The groups report the results
of their tasks in a group session.
c) Discussion: The results of the groups are
discussed by the class under guidance
of the instructor.
d) Lecture: Lectures are used (limited) for
outlining the basic rules for
given topics.
e) Informal Talk: Informal talk is invoked to obtain
feed-back to the instructor on
the outcome of the instruction.
f) Hands-on: Practical work is used extensively,
as this is the best way to implement
the use of theoretical knowledge
on the various topics covered
by other training methods. In
the same way, the instructor gets
feed-back on the student's understanding
of the topics covered in the instruction.
g) Tests: Tests and questionnaires are used
frequently, as these are highly
motivating and underline important
points of the instruction.
6.6 T̲O̲O̲L̲S̲ ̲A̲N̲D̲ ̲T̲E̲S̲T̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲
6.6.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
A recommended list of tools and test equipment shall
be provided for the MS. The Tools and Test equipment
(T & TE) list shall identify common and special items.
Furthermore, the list shall cover both first and second
maintenance levels.
6.6.2 M̲S̲ ̲F̲a̲u̲l̲t̲f̲i̲n̲d̲i̲n̲g̲ ̲P̲h̲i̲l̲o̲s̲o̲p̲h̲y̲
At site level (first level) the maintenance and diagnostics
software (M&D) in conjunction with module swapping
is the method used in corrective maintenance. Consequently,
some spare modules are needed in the process of fault
isolation.
Preventive maintenance does not require any special
tools.
At depot level (second level) Christian Rovsing A/S
recommends use of the same type of test equipment planned
to be procured by NATO for the CAMPS program, for details
see section 6.6.4.
Factory and Vendor repair (third level) will be recommended
for a few items where it is cost effective.
6.6.3 O̲n̲-̲S̲i̲t̲e̲ ̲T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Annex D defines the recommended, on-site tools and
test equipment.
The list has been derived by analysis of the Christian
Rovsing A/S hardware and peripheral hardware with due
attention paid to the proposed maintenance philosophy.
6.6.4 D̲e̲p̲o̲t̲ ̲T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
6.6.4.1 P̲r̲o̲p̲o̲s̲e̲d̲ ̲T̲e̲s̲t̲ ̲P̲h̲i̲l̲o̲s̲o̲p̲h̲y̲.̲
It is assumed that all faulty subassemblies will be
returned for repair at the NATO common repair depot.
6.6.4.2 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Christian Rovsing A/S recommends the following test
equipment for the repair depot.
1) Functional testers, e.g. GEN RAD 1795 HD general
purpose tester.
This equipment is intended for subassemblies of
low complexity as well as analog ones.
2) "In-circuit Tester", ZEHNTEL Troubleshooter 800.
This tester is intended for subassemblies of medium
and high complexity.
3) MS "Test Bed"
This equipment is needed to troubleshoot certain
faults which are only present in a real-time environment.
Furthermore, the equipment is used for fault verification
on items when they arrive at the depot for repair
as well as verification of fault-free items after
repair.
The "Test Bed" is a "tripped-down" version of a
MS system.
4) Conventional Instruments
To support repair, oscilloscopes, logic analyzers
and other common instruments will be needed.
6.6.4.3 N̲A̲T̲O̲ ̲O̲w̲n̲e̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Christian Rovsing A/S as a potential supplier of the
two MS systems would like to point out that NATO is
planning to procure the test equipment listed in 6.6.4.2
for the CAMPS program. Consequently, if the MS subsystem
of the CROSSFOX is delivered by Christian Rovsing A/S
significant savings could be achieved because of the
commonality between CAMPS and the CROSSFOX MS.
7. A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲G̲R̲A̲M̲ ̲P̲L̲A̲N̲.
7.1 G̲e̲n̲e̲r̲a̲l̲
The test program for the MPF subsystem has the objective
to provide a systematic, incremental verification of
the subsystem's compliance with all baseline requirements.
The objective of the test program is accomplished by
means of the existing, general Christian Rovsing A/S
Product Assurance provisions supplemented with the
specific test activities outlined in this section.
The overall test program will be described in a Test
Plan in accordance with ACE MANUAL No. 96-1-1, Annex
I ADP Standard 007-3. The Test Plan will contain a
list of the tests to be performed, test objectives,
methods and criteria. The Test Plan will further contain
the schedule and time phasing of the tests.
7.1.1 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
Throughout the test program all verification will be
accomplished by using approved procedures describing
the actions, objectives and required test results for
each test segment. A method will be provided for recording
the actual test results and for comparing them with
the required test results. These procedures will be
prepared and approved prior to the test operation.
Verification at any level or category will be performed
by one of the following methods:
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 an item or of the documentation associated with
an item.
b. A̲n̲a̲l̲y̲s̲i̲s̲
This method is a non-functional verification, such
as reduction or translation of data, review of
analytical data or review of performance from a
detailed test.
c. T̲e̲s̲t̲/̲D̲e̲m̲o̲n̲s̲t̲r̲a̲t̲i̲o̲n̲
This method is a functional verification of hardware
and/or software such that measurements and observations
of correct operation can be made. A test is where
the element of verification is instrumented, measured
or displayed directly. A demonstration is where
the element of verification is logically obvious,
as being a necessary constraint to some other result,
but is not itself displayed.
7.1.2 P̲r̲o̲d̲u̲c̲t̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲s̲
All products manufactured by Christian Rovsing A/S
are subject to the provisions of the company's Quality
Assurance Program. This program is compliant with AQAP-1:
"Nato Quality Control System Requirements for Industry".
7.1.3 F̲i̲r̲s̲t̲ ̲A̲r̲t̲i̲c̲l̲e̲ ̲Q̲u̲a̲l̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲T̲e̲s̲t̲s̲ ̲(̲F̲A̲Q̲T̲)̲
All the hardware items included in this proposal either
have previously been approved or are now being approved
by NATO for use on the CAMPS program as part of a CAMPS
First Article Qualification Program.
As the hardware requirements for the CROSSFOX MPF equipment
are identical to those for the CAMPS equipment it is
assumed that no additional FAQT is necessary. The
FAQT documentation from the CAMPS program will be provided
on customer request.
7.2 F̲A̲C̲T̲O̲R̲Y̲ ̲Q̲U̲A̲L̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲P̲R̲O̲V̲I̲N̲G̲ ̲T̲E̲S̲T̲ ̲(̲F̲Q̲T̲)̲
The objective of this test is to verify that the MPF
subsystem hardware and software have been designed
and manufactured in accordance with the functional,
environmental, operational and reliability requirements
specified. The verification activity will be performed
in compliance with the IFB as follows.
7.2.1 H̲a̲r̲d̲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̲
When the first MPF subsystem hardware has been integrated
a functional verification will be performed. The verification
will consist of interface requirements and functional
hardware requirements.
7.2.2 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
After completion of the functional hardware verification
a verification of all environmental requirements will
be performed.
7.2.3 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̲
This activity will consist of a verification of the
Operating System functions including security features
contained herein. Further, all functions provided by
the application software will be verified.
7.2.4 M̲P̲F̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲
This verification will be performed under simulated,
operational conditions by means of a Standard Test
Environment simulator.
The test simulator will be used for simulation of external
interfaces of the MPF subsystem.
The test simulator will be able to generate pseudorandom
MPF input traffic, which is representative of the specified
operational message traffic. The generated message
traffic load will be at least 0.5 Erlang for low speed
channels and 0.3 Erlang for medium speed channels.
The simulation will include message traffic corruption
by transmission media failure and noise.
The objective of the MPF Subsystem verification is
to verify the operational requirements and to provide
a demonstration of the software reliability. The software
reliability will be assessed by monitoring the mean
time between Discovery of Software Defects (MDSD).
The acceptance criteria for the MPF Subsystem verification
is an accumulated test time of 240 hours, with no more
than one failure during the 240 hours.
7.2.5 R̲e̲l̲i̲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̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The objective of this verification is to demonstrate
compliance with the reliability and maintainability
characteristics specified in the IFB, para 4.5.
7.2.5.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The hardware reliability verification will be provided
by calculations of reliability figures in accordance
with the principles described in MIL HDBK 217: "Reliability
Prediction of Electronic Equipment".
Reliability figures have been calculated for all units
contained in the MPF subsystem. Due to the high predicted
reliability values no test verification of MTBF values
is planned. However, the hardware reliability will
be monitored throughout the development, test and warranty
period by means of the Failure Reporting System.
7.2.5.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The software reliability will be assessed by monitoring
of the MDSD during the 240 hours accumulated test time
during the MPF Subsystem Verification.
7.2.5.3 H̲a̲r̲d̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
A set of maintenance and diagnostics (M&D) programs
will be provided as tools for corrective maintenance
actions.
A demonstration of the M&D program capabilities will
provide verification of the predicted MTTR values.
Preventive maintenance procedures will be provided
in a maintenance manual.
7.2.5.4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
A set of utility programs, editor, compiler, linker
and debugger will be provided as tools for software
maintenance.
A demonstration of the utility program capabilities
will provide verification of the software maintainability.
7.3 F̲A̲C̲T̲O̲R̲Y̲ ̲P̲O̲S̲T̲ ̲P̲R̲O̲D̲U̲C̲T̲I̲O̲N̲ ̲T̲E̲S̲T̲ ̲(̲F̲P̲P̲T̲)̲
The objective of this test is to provide a final verification
of the actual site equipment configuration before shipment
from the factory.
Before shipment to site the complete MPF subsystem
is assembled at the factory and the functional verification
of hardware and software is performed with a customer
approved subset of the FQT test procedure.
7.4 O̲N̲ ̲S̲I̲T̲E̲ ̲T̲E̲S̲T̲S̲
7.4.1 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̲ ̲T̲e̲s̲t̲
The objective of this test is to verify that all equipment
contained in the MPF subsystem have been correctly
installed.
The verification will consist of execution of the functional
hardware and software test.
7.4.2 S̲u̲b̲n̲e̲t̲w̲o̲r̲k̲ ̲T̲e̲s̲t̲
The objective of these tests is to verify the functions
of the subnetwork consisting of the MPF subsystem interfaced
to the:
- SNT category iii
- NICS-TARE Network
- Ship-to-Shore Stations
- Broadcast Stations
- SNT category iv
- Alternate MPF
The test will consist of a complete verification of
all functions to be provided by the subnetwork.
7.4.3 O̲v̲e̲r̲a̲l̲l̲ ̲S̲y̲s̲t̲e̲m̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
After completion of all individual subnetwork tests
an overall system test shall be performed.
The objective of the overall system test is to demonstrate
that the delivered system will provide the required
functions, facilities and software reliability.
The test shall be performed by continuous operation
of the MPF system for a period of 90 days without "Software
failures".
The concept "Software failure" will be defined in the
Acceptance Test Plan.
We are prepared to divide the overall system test into
two subtests. The first subtest will consist of a
complete functional test. Test procedures will be
specified by the contractor and shall be agreed by
the purchaser.
Initially all functions shall be exercised one by one.
Subsequent functional testing shall be performed by
execution of functions in parallel.
Any deviation from the specified functional requirements
shall be corrected and all functions affected by the
corrections shall be retested.
After completion of the functional subtest the final
operational subtest can be initiated. The test scenarios
and procedures for the operational test shall be prepared
by the purchaser together with the contractor.
The operational test shall be successfully performed
by exercising the complete CROSS FOX network over 3
periods each lasting at least 10 days.
Any software modifications required to comply with
operational and security requirements will have to
be made and demonstrated by the contractor before the
final acceptance of the software.
