top - download
⟦b2ffee86c⟧ Wang Wps File
Length: 95309 (0x1744d)
Types: Wang Wps File
Notes: CPS/PLN/006
Names: »0726A «
Derivation
└─⟦d10d3ed68⟧ Bits:30006014 8" Wang WCS floppy, CR 0055A
└─ ⟦this⟧ »0726A «
WangText
Q…00……00……00……00…D…0a……00……00…D…0b…D…0d…D C…0c…C
B…0d…B
…18……0c……18……02……18……07……17……0d……17……0e……17……02……17…
…17……07……16……0d……16……02……16……07……15……08……15……0d……15……0e……15……06……14……0d……14…
…13……09……13……0a……13……01……13……02……12……09……12……0e……12……0f……12…
…12… …11……0b……11……0f……11……02……11…
…11……07……10……0b……10……0c……10……02……10…
…10… …86…1 …02… …02… …02…
0726A/ktd…02…CPS/PLN/006
…02…PMS/830301…02……02…#
CAMPS MAINTENANCE PLAN
…02…Issue 2.2 …02…CAMPS
CAMPS MAINTENANCE PLAN
CPS/PLN/006
CDRL Logistics Support No.05
Line Item No. 8.4.1
…0f…Per S]ndergaard
Kurt Nybroe-Nielsen
SHAPE, (5), GJ, KNN, BHB, FE, OE, PMS, KM,
ORP, PLN, KJA, QA, Conf. Mgr., Library (5),
GQAR.
…0f… ILS Manager 830301
QA Manager 830301
2.3
830301
…0e… Conf. Mgmt. 830301
0726A/ktd …02… CPS/PLN/006
…02… PMS/830301…02… ii
CAMPS MAINTENANCE PLAN…02… Issue 2.2…02… CAMPS
810308 All Issue 1 of document
1 810826 All Issue 2 of document
2 820120 7
9
10
10a
11
12
27
28
31
34
47
50
54
58 Changed according to:
60
61 CPS/101/tlx/0391
63 CPS/101/tlx/0364
64
75
84
86
86
92
93
94
95
96
App. A First Issue
2 App. B First Issue
2.1 821130 CPS/MOM/21 App. A New update
2.1 821130 CPS/MOM/21 App. B New update
2.2 830301 CPS/MOM/22 76 New update
2.2 CPS/MOM/31 77 New update
2.2 CPS-LOG NO. 1129 78 New update
2.2 CPS/MOM/31 84 New update
2.2 CPS/MOM/31 85 New update
2.2 CPS/MOM/31 86 New update
2.2 CPS/MOM/31 App. A New Update
2.2 CPS/MOM/31 App. B New Update
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION ................................
8
1.1 SCOPE .....................................
8
1.2 MAINTENANCE CONCEPT .......................
8
1.3 LIST OF ABBREVIATIONS .....................
9
1.4 MAINTENANCE DOCUMENTATION, OVERVIEW ....... 11
1.4.1 Site Level Documentation............... 11
1.4.1.1 System Descriptiom Manual.......... 11
1.4.1.2 Technical Manual................... 12
1.4.1.3 Test Equipment Manuals............. 14
1.4.1.4 Peripheral Equipment Manuals....... 14
1.4.1.5 Installation Manual................ 14
1.4.2 Depot Level Documentation.............. 14
1.4.2.1 System Description Manual...........14
1.4.2.2 Technical Manual....................15
1.4.2.3 Test Equipment Manuals..............15
1.4.2.4 Peripheral Equipment Manuals........15
1.4.3 CAMPS Remote Terminal Documentation.....15
1.4.3.1 Equipment Handbook..................15
1.4.3.2 Peripheral Equipment Manuals........15
1.5 MAINTENANCE PLAN, ORGANIZATION ............ 16
2 MAINTENANCE ENGINEERING ..................... 18
2.1 INTRODUCTION .............................. 18
2.2 MAINTENANCE DOCUMENTATION.................. 18
2.2.1 Site Level ............................ 18
2.2.1.1 System Description Manual.. ....... 18
2.2.1.2 Technical Manual................... 20
2.2.1.2.1 Preventive Maintenance ........ 20
2.2.1.2.2 Corrective Maintenance......... 21
2.2.1.2.3 Failure Reporting System .......21
2.2.1.3 Installation Manual................ 22
2.2.1.4 Test Equipment Manuals............. 22
2.2.1.5 Peripheral Manuals................. 23
2.2.2 Depot Level ........................... 23
2.2.3 Remote Terminal Level.................. 23
2.3 FAILURE REPORTING SYSTEM .................. 25
2.3.1 General ............................... 25
2.3.2 Information Flow ...................... 25
2.3.3 Module Flow ........................... 27
2.3.4 Failure Reports ....................... 28
2.3.5 Logbook ............................... 30
2.3.6 Error Print-Outs ...................... 32
2.4 TOOLS AND TEST EQUIPMENT .................. 32
2.4.1 Sites ................................. 32
2.4.2 Depots ................................ 33
2.4.3 Tools ................................. 33
2.4.3.1 Standard Tools .................... 33
2.4.3.2 Special Tools ..................... 33
2.4.4 Test Equipment (TE) ................... 33
2.4.4.1 Standard Test Equipment ........... 33
2.4.4.2 Special Test Equipment ............ 34
2.4.4.3 Scenarios ......................... 34
2.4.4.3.1 Crate Lay-Out ..................36
2.4.4.3.2 Internal Bus Lines .............36
2.4.4.3.3 Standard V24 Lines .............39
2.4.4.3.4 Disk and Floppy Disk ...........39
2.4.4.3.5 OPTO Link Connection Lines .....39
2.4.4.3.6 V24 Terminal Lines .............42
2.4.4.3.7 External Channel Lines .........42
2.4.4.3.8 Remote Terminal Lines ..........46
2.4.4.4 Calibration ....................... 48
2.4.5 Accessories ........................... 48
2.4.6 Consumables ........................... 48
2.4.7 Programmes ............................ 48
2.5 CODIFICATION .............................. 49
2.6 PROVISIONING CONFERENCE ................... 49
3. ON-SITE MAINTENANCE ....................... 51
3.1 INTRODUCTION .............................. 51
3.2 WORK DEFINITIONS .......................... 51
3.2.1 Preventive Maintenance ................ 51
3.2.2 Corrective Maintenance ................ 52
3.2.3 Installation of Modifications ......... 52
3.2.4 Site Maintenance Management ........... 52
3.2.5 On-Job Training ....................... 53
3.3 MAINTENANCE ORGANIZATION .................. 53
3.4 PREVENTIVE MAINTENANCE .................... 55
3.4.1 Central Equipment ..................... 55
3.4.2 Peripherals ........................... 55
3.4.3 Test Equipment ........................ 56
3.4.4 Modules ............................... 56
3.5 CORRECTIVE MAINTENANCE .................... 58
3.5.1 Error Detection ....................... 58
3.5.2 Isolation of Errors to Assembly ....... 61
3.5.2.1 Watchdog Processor ................ 63
3.5.2.2 Processor Unit .................... 63
3.5.2.3 TDX ............................... 66
3.5.2.4 Distribution Equipment ............ 66
3.5.2.5 External Channels ................. 66
3.5.2.6 Power Supplies .................... 70
3.5.2.7 Stand-by PU ....................... 70
3.5.3 M&D Programs .......................... 70
3.5.3.1 WD Troubleshooting Tree ........... 71
3.5.3.2 System Troubleshooting Tree ....... 71
3.5.3.3 Off-Line Troubleshooting Tree ..... 72
3.5.4 Gain Access to and Replace Faulty
Module ................................ 72
3.5.5 Verification of Repair ................ 72
3.5.6 Return to Normal Operation ............ 73
3.5.7 Paper Work ............................ 73
3.6 FAILURE REPORTING SYSTEM .................. 73
3.6.1 Logbook ............................... 73
3.6.2 Error Print-out ....................... 74
3.7 PERSONNEL ................................. 74
4. DEPOT MAINTENANCE ......................... 75
4.1 INTRODUCTION .............................. 75
4.2 WORK DEFINITIONS .......................... 75
4.3 MAINTENANCE ORGANIZATION .................. 76
4.4 SITE SUPPORT .............................. 76
4.4.1 Supply Schedule ....................... 76
4.4.1.1 Standard Items (Group 1) .......... 76
4.4.1.2 Critical Items (Group 2) .......... 76
4.4.1.3 Emergency Items (Group 3) ......... 77
4.5 PREVENTIVE MAINTENANCE .................... 77
4.5.1 Test Equipment Calibration ............ 77
4.6 CORRECTIVE MAINTENANCE .................... 77
4.6.1 Module Repair during Warranty ......... 77
4.6.2 Module Repair after Warranty .......... 78
4.6.3 Test
Equipment
Repairs
................
78
4.7 FAILURE REPORTING SYSTEM .................. 78
4.8 SPECIFICATION OF TEST EQUIPMENT ........... 78
5. MAINTENANCE MANAGEMENT .................... 79
5.1 INTRODUCTION .............................. 79
5.2 MAINTENANCE ORGANIZATIONAL FLOW ........... 79
5.3 MANAGEMENT RESPONSIBILITIES ............... 80
5.3.1 Site Responsibilities ................. 80
5.3.2 Depot Responsibilities ................ 80
5.3.3 SHAPE Responsibilities ................ 80
5.3.4 CR Responsibilities ................... 81
5.4 PERSONNEL ................................. 81
5.4.1 Resident Site Technicians (RST) ....... 81
5.4.2 Technicians ........................... 81
6 MAINTENANCE SUPPORT ......................... 83
6.1 INTRODUCTION .............................. 83
6.2 FIELD ASSISTANCE .......................... 83
6.2.1 Warranty Support ...................... 83
6.2.2 Post-warranty Support ................. 83
6.3 SPARES .................................... 83
6.3.1 Approved Spare Parts List (ASPL) ...... 83
6.3.2 Follow-on Spares ...................... 84
6.3.3 Information & Materials Flow .......... 84
6.3.4 Warranty Repair Flow .................. 84
6.4 FIELD CHANGES ............................. 87
6.4.1 General ............................... 87
6.4.2 Registration of FCNs .................. 87
6.4.3 Description of FCNs ................... 87
6.4.3.1 Heading ........................... 87
6.4.3.2 Identification .................... 88
6.4.3.3 Parts Disposition ................. 88
6.4.3.4 Classification .................... 88
6.4.3.5 Type of Information ............... 88
6.4.3.6 Related Information ............... 91
6.4.3.7 Field Change Description .......... 91
6.4.3.8 Affected Documents ................ 91
6.4.3.9 Approval Authority ................ 91
6.4.3.10 Succeeding Pages ................ 91
6.5 SOFTWARE MAINTENANCE SUPPORT .............. 92
6.5.1 S/W Warranty Phase .................... 92
6.5.1.1 Programming Services at CR ........ 92
6.5.1.2 Software Modifications ............ 92
6.5.1.2.1 System Software ............... 92
6.5.1.2.2 Application Software .......... 93
6.5.1.2.3 Patches ....................... 93
6.5.2 S/W Post-Warranty Phase ............... 93
6.5.2.1 Maintenance Concept ............... 93
6.5.2.1.1 Integrated Systems Support
Centre (ISSC) ................. 94
6.5.2.1.2 Operational Support Centre (OSC)95
6.5.2.1.3 Operational Sites ............. 95
6.5.3 S/W Error Reporting ................... 95
Appendix A: Preliminary Tools and TE List ......
Appendix B: Level of Repair Analysis ...........
1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
1.1 S̲C̲O̲P̲E̲
This plan provides an overview of the task delegations
within the CAMPS maintenance program. It will describe
the elements in the program and their implementation.
The maintenance concept will be presented and discussed.
1.2 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲C̲O̲N̲C̲E̲P̲T̲
It is a main feature of the on-site maintenance philosophy
that corrective maintenance is carried out down to
module level for both processor equipment and peripherals.
Defective modules are returned to depot for repair
or other disposition.
In most instances, the level of isolation and replacement
will be plug-in cards and modules. This principle
is especially emphasized in the central equipment where
also the power supplies are plug-in modules and modules
in the Channel unit can be replaced with power ON so
that the operational integrity of the remaining system
is preserved while one module is being replaced.
The corrective maintenance to components level is restricted
to simple tasks as replacement of fans, fuses etc.
Another significant feature in the on-site maintenance
philosophy is that troubleshooting with open doors
in the EMI racks is kept to a minimum. Most of the
corrective maintenance can be performed from the operator
position terminal and often the doors need only be
open in order to replace the defective module.
1.3 L̲I̲S̲T̲ ̲O̲F̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
The following lists the abbreviations as used throughout
in the maintenance plan.
M̲n̲e̲m̲o̲n̲i̲c̲s̲ E̲x̲p̲l̲a̲n̲a̲t̲i̲o̲n̲
A/D Analog/Digital
ASPL Approved Spare Parts List
BPJF Black Panel Junction Field
BSM-X Bus Switching Module
CCA Crate Configuration Adaptor
CCB Change Control Board
CCIS Command & Control Information System
CIA Crate Interface Adaptor
CNFG Configuration
COCB Configuration Control Bus
CPU Central Processor Unit
CR Christian Rovsing A/S
CRC Cyclic Redundancy Check
CSSI CAMPS Software Support Installation
DAMOS Dual Advanced Multiprocessor Operating
System
DCA Disk Control Adaptor
DEMUX Demultiplexer
ECO Engineering Change Order
ECP Engineering Change Proposal
EDCN Engineering Design Change Notice
EMI Electro-Magnetic Interference
FCN Field Change Notice
FD Floppy Disk
H/W Hardware
IDF Intermediate Distribution Frame
ILS Integrated Logistics Support
I/O Input/Output
ISSC Integrated Systems Support Centre
LIA Line Interface Adaptor
LP Line Printer
LTU Line Termination Unit
LTUX-S Line Termination Unit for TDX
MBT Main Bus Termination
M&D Maintenance & Diagnostics
MDF Main Distribution Frame
MFG P/N Manufacturer's Parts Number
MGMT Management
MIA Map Interface Adaptor
MSP Medium Speed Printer
MTTR Mean Time To Repair
MUX Multiplexer
NAK Negative Acknowledge
NCB Network Configuration Board
OCR Optical Character Reader
OEM Original Equipment Manufacturer
OJT On Job Training
OMDT OPTO MUX/DEMUX Transceiver
OSC Operational Support Centre
PCT Percent
PL Parts List
PSU Power Supply Unit
PU Processor Unit
QA Quality Assurance
R&M Reliability & Maintainability
RAM Random Access Memory
RPJF Red Panel Junction Field
RSPL Recommended Spare Parts List
RST Resident Site Technician
SCARS Status Control and Reporting System
SE System Engineering
SPA Site Provisional Acceptance
SPDCN Spare Part Design Change Notice
SS&C System Status & Controller
STI Supra-bus & TDX Interface
S/W Software
TARE Telegraph and Relay Equipment
TBD To Be Defined
TDX Telecommunication Data Exchange
TE Test Equipment
TIA TDX Interface Adaptor
TRC Torn Tape Relay Center
TR/REC Transceiver/Receiver
VDU Visual Display Unit
WD Watchdog Crate Adaptor
WDP Watchdog Processor
WPU Watchdog Processor Unit
1.4 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲,̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
The CAMPS maintenance documentation consists of
a) Manuals related to site level maintenance
b) Manuals related to depot level maintenance
c) Manuals related to remote terminal maintenance
These manuals will contain all information necessary
in order to perform hardware maintenance including
both hardware and software error reporting and field
modifications, while software maintenance will be described
in the manuals for the CSSI site (Programming Development
Tools Manuals). Refer to fig. 1.4-1.
1.4.1 S̲i̲t̲e̲ ̲l̲e̲v̲e̲l̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
1.4.1.1 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲M̲a̲n̲u̲a̲l̲
This Manual will contain an introduction to the CAMPS
system with descriptions of how the software and firmware
interrelates to the hardware.
1.4.1.2 T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲M̲a̲n̲u̲a̲l̲
The technical manual at the site consists of 3 volumes
which are
a) Site Level Maintenance Manual. Main sections herein
are
- Introduction describing the H/W structure break-down.
- Preventive maintenance comprising all tasks
concerned with preventive maintenance of an
on-site CAMPS installation.
- Corrective maintenance comprising all tasks
concerned with corrective maintenance of an
on-site CAMPS installation.
- Failure reporting system including descriptions
of
Failure Reports
Logbook
S/W Error Reporting
Field Modifications
S/W Updates
b) Assembly Break-Down. This volume provides a detailed
hierachy of the CAMPS site down to the lowest replaceable
module/subassembly.
c) Inventory Manual. This volume lists all items delivered
to the particular CAMPS site.
1.4.1.3 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲M̲a̲n̲u̲a̲l̲s̲
The manuals used for the test equipment will be the
original OEM manuals. The quality of these manuals
will be sufficient as to satisfy the CAMPS requirements.
With respect to preventive and corrective maintenance
references will be made from the Technical Manual.
where appropriate , the test equipment manuals will
also contain calibration procedures.
1.4.1.4 P̲e̲r̲i̲p̲h̲e̲r̲a̲l̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲M̲a̲n̲u̲a̲l̲s̲
The manuals used for the peripherals will be the original
OEM manuals and there will be separate manuals for
each peripheral. With respect to preventive and corrective
maintenance, references will be made from the Technical
Manual.
The OEM manuals will be annotated to display the delivered
configuration in order to avoid confusion.
Manuals for Low Speed Teleprinters (TRC) and Optical
Character Readers (OCR) are supplied by customer and
will not be part of the CAMPS Documentation Package.
1.4.1.5 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲M̲a̲n̲u̲a̲l̲
This volume is a selv-contained document intended for
installation purposes. It is not directly related to
maintenance, but it may be consulted as it contains
as-built drawings of installation and cabling, check
lists, and a verification print-out. Any prospective
expansions will be reflected in this document.
1.4.2 D̲e̲p̲o̲t̲ ̲L̲e̲v̲e̲l̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
1.4.2.1 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲M̲a̲n̲u̲a̲l̲
This manual is the same for site level and depot level.
1.4.2.2 T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲M̲a̲n̲u̲a̲l̲
The technical manual at the depot consists of
a) Module descriptions. A functional description of
each individual module is provided together with
a components parts list.
Where necessary, similar functional descriptions
are provided at subassembly level.
b) Approved Spare Parts Lists (ASPL). This volume
identifies all necessary spares and consumables.
1.4.2.3 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲M̲a̲n̲u̲a̲l̲s̲
The manuals used for the test equipment will be the
original OEM manuals. The quality of these manuals
will be sufficient as to satisfy the CAMPS requirements.
1.4.2.4 P̲e̲r̲i̲p̲h̲e̲r̲a̲l̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲M̲a̲n̲u̲a̲l̲s̲
A similar set of manuals as found at the sites will
also be available at the depot(s).
1.4.3 C̲A̲M̲P̲S̲ ̲R̲e̲m̲o̲t̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲(̲C̲R̲T̲)̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
1.4.3.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲
This manual contains all necessary documentation for
the maintenance of the remote terminal. A copy of the
manual will be placed at the main site.
1.4.3.2 P̲e̲r̲i̲p̲h̲e̲r̲a̲l̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲M̲a̲n̲u̲a̲l̲s̲
The related original OEM manuals will be available
at the remote terminal site.…86…1 …02… …02… …02… …02…
1.5 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲P̲L̲A̲N̲,̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
In addition to this present section, the maintenance
plan is divided into 5 sections each covering a well
defined part of the CAMPS equipment maintenance as
shown in figure 1.5-1. The contents of the sections
is in short described below:
a) The Introduction (Sec. 1) presents the scope and
organization of the plan as well as the maintenance
concept.
b) The Maintenance Engineering (Sec. 2) describes
the engineering tasks prior to installation on
the sites. A major part of this section is a description
of the maintenance manual.
c) The On-Site Maintenance section (sec. 3) presents
the multiple tasks involved in maintaining a CAMPS
site.
d) Depot level maintenance (sec. 4) describes how
the sites are being supported from the depot.
e) The Maintenance Management section (sec. 5) describes
the tools for management, control, and communication
within the CAMPS maintenance program.
f) The Maintenance Support section (sec. 6) describes
how the CAMPS project will be supported from the
contractor (CR) during and after the warranty period.
Maintenance Plan, Organization
Fig. 1.5-1
2 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲E̲N̲G̲I̲N̲E̲E̲R̲I̲N̲G̲
2.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This section outlines the engineering efforts necessary
prior to commencement of the on-site maintenance.
It describes the tools necessary to keep up the versatile
duties connected with the on-site maintenance and explains
the tools which are prerequisites for effective handling
and control of the CAMPS equipment.
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̲
2.2.1 S̲i̲t̲e̲ ̲L̲e̲v̲e̲l̲
Fig. 2.2.1-1 illustrates the applicable documentation
for the total site maintenance tasks, and the following
description provides an introductional explanation
of the structure.
2.2.1.1 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲M̲a̲n̲u̲a̲l̲
The System description manual provides an overview
of a CAMPS site breaking it down into assemblies and
subassemblies and relating the firmware to both hardware
and software. Also the intercommunication between sites
are discussed through the system concept and the application
S/W configuration is presented.…86…1 …02… …02… …02… …02…
Site Level Documentation…01…Fig. 2.2.1-1…86…1 …02… …02… …02… …02…
2.2.1.2 T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲M̲a̲n̲u̲a̲l̲
The technical manual consists of 3 volumes which are
a) An Inventory Manual identifying the property inventory
for the site.
b) A H/W Assembly Break-Down Manual identifying each
replaceable module by means of its position in
the rack hierachy and parts number.
c) A Site Level Maintenance Manual which is the reference
manual for the complete maintenance of a CAMPS
site. It is divided into sections of which the
most important are described below.
2.2.1.2.1 P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
This section contains a full description of the preventive
maintenance tasks at a CAMPS site. A major asset is
the preventive maintenance schedules which specifies
whenever a unit needs maintenance. There are schedules
covering all different types of peripherals and instruments,
and corresponding sub-sections will briefly describe
the set-up, prerequisites, tasks, etc.
a) The maintenance of the central equipment is described
in detail. All necessary information about test
instruments, tools, consumables, and test figures
are described.
b) A separate sub-section contains the preventive
maintenance schedule of the peripherals involved.
References are made to the respective OEM manuals
which will serve as the appropriate documents for
the peripherals. There will be one schedule for
each type of peripheral.
c) The Test Equipment (TE) will generally require
little or no maintenance, but where preventive
maintenance is necessary, the same philosophy as
in "b" above applies. If a regular calibration
is necessary this will most probably need to be
done at a depot. In such case a TE Calibration
Schedule will be found and the procedures described.
2.2.1.2.2 C̲o̲r̲r̲e̲c̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
This section in the maintenance manual contains all
descriptions necessary for the isolation and repair
of an error down to module level. It is based on
troubleshooting trees which provide a structured troubleshooting
procedure throughout the system. The error print-out
at the maintenance position (or missing print-out)
will provide an entry point to a particular troubleshooting
tree and by following the descriptions outlined an
effective and time saving troubleshooting path is ensured.
Once the error is isolated to a particular module,
this is interchanged with a spare module and a verification
test is performed before the application programs are
reloaded and the system brought back to normal operation.
2.2.1.2.3 F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲ ̲S̲y̲s̲t̲e̲m̲
This section explains in detail the Failure Reporting
System which comprises all aspects of failure reporting
from a site. Main chapters herein are
a) F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲s̲
Whenever a corrective maintenance action has taken
place a failure report should be filled in. Sec
2.3 describes how to use and fill in failure reports.
b) L̲o̲g̲b̲o̲o̲k̲
A logbook is supplied to be effective from the
start of the Provisional Site Acceptance (PSA).
All irregularities, errors, and configuration
changes, f.inst. due to preventive maintenance
operations, must be written in the logbook. This
section in the manual describes how the logbook
is maintained. (The logbook is described in sec.
2.3.5).
c) S̲/̲W̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲
This chapter describes the procedures applicable
when a S/W error occur at a site. In this case
the system status must be read before a memory
dump, if necessary, is initiated. The results must
be written into a S/W report formular which will
be issued and under cover of a failure report sent
to the CSSI site where actual S/W maintenance will
be performed.
d) H̲/̲W̲ ̲M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
This chapter describes the procedures applicable
when field modifications are performed at the site
including configuration control procedures. Section
6.4 describes the Field Change Notices which will
be used to describe the modifications.
e) S̲/̲W̲ ̲U̲p̲d̲a̲t̲e̲s̲
S/W Modifications will be performed as patching
or load of modified software from a diskette and
the procedures will be described in this chapter.
Refer to sec 6.5 for more details.
2.2.1.3 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲M̲a̲n̲u̲a̲l̲
The installation Manual will contain as-built drawings
for a CAMPS site herein included interconnection cable
diagrams and pin designators. Also this manual will
provide disassembly instructions to rack, crate, and
module level.
2.2.1.4 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲M̲a̲n̲u̲a̲l̲s̲
The application of test equipment will be addressed
through the preventive and corrective maintenance chapters
in the Site Level Maintenance Manual.
Note, that parts lists for test equipment will be found
in their respective manuals.
2.2.1.5 P̲e̲r̲i̲p̲h̲e̲r̲a̲l̲ ̲M̲a̲n̲u̲a̲l̲s̲
The peripherals will be addressed through the preventive
maintenance schedules and the troubleshooting trees
in the Site Level Maintenance Manual and through the
ASPL in the Inventory Manual.
Note, that parts lists for OEM equipment will be found
in their respective manuals.
2.2.2 D̲e̲p̲o̲t̲ ̲L̲e̲v̲e̲l̲
Fig. 2.2.2-1 provides a tentative illustration of the
applicable documentation for a depot level. As details
within the depot level repair have yet to be finalized,
although the general depot level philosophy is clear,
the contents of the Technical Description will be evaluated
later. However, the main sections are foreseen to
be as shown in the figure.
2.2.3 R̲e̲m̲o̲t̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲L̲e̲v̲e̲l̲
Maintenance of the CRT will widely be initiated from
the CAMPS main site with assistance, if necessary,
from an operator at the CRT site. Therefore, a copy
of the documentation will be placed at the main site
while another will be placed at the CRT site.
As the equipment installed is relatively simple all
necessary maintenance documentation apart from the
original OEM manuals will be gathered in the Equipment
Handbook comprising
- System Description
- Assembly Break-Down
- Corrective Maintenance descriptions
- Parts Lists
- Diagrams
- Intallation Descriptions
- Inventory
2.3 F̲A̲I̲L̲U̲R̲E̲ ̲R̲E̲P̲O̲R̲T̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲
2.3.1 G̲e̲n̲e̲r̲a̲l̲
A Failure Reporting System will be established in order
to maintain the operation and overall performance of
the system. By an analysis of the errors reported,
it is possible to screen systematic failures and proper
action may be taken to avoid unnecessary down-time.
Where action is deemed necessary a resulting Field
Change Notice (FCN) will be generated enabling each
site or depot concerned to perform the retrofit.
Prerequisites for Failure Reports from the sites are
a properly maintained logbook and the documentational
error print-outs appearing on the maintenance position
Line Printer.
The official failure reporting system will start at
the Site Provisional Acceptance (SPA), but in-house
registration and analysis will commence at the start
of factory acceptance test.
2.3.2 I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲F̲l̲o̲w̲
Any failure occurring at a site or depot will initiate
an information flow, refer to fig. 2.3.2-1. A failure
report will be generated (refer to sec. 2.3.4-1) and
sent via SHAPE to CR-ILS which will analyse, file,
and distribute for further examination. If a resulting
change is recommended, an Engineering Change Proposal
(ECP) is sent to a Change Control Board (CCB) which
in turn may issue an Engineering Change Order (ECO).
ILS will then prepare a Field Change Notice (FCN)
under configuration mgmt, QA, and Project Office control.
The FCN will be sent through SHAPE to the affected
sites and/or depots.
Information Flow
Fig. 2.3.2-1
The FCN, which may prescribe a H/W design change, S/W
modification, or a spare part change, must be implemented
by the RST, and upon completion an acknowledgement
must be returned through SHAPE to CR-ILS' file to close
the item. An FCN is considered closed only when acknowledgement
is received from all sites/depots concerned.
One exception to this information flow exists when
the FCN is concerned with change of spare parts in
which case the change will be subject to approval by
SHAPE. In case the spare part change is a consequence
of a H/W design change, an FCN containing all relevant
information will be issued as a proposal to SHAPE within
4 weeks from the H/W change. After their consent,
the proposal will be promoted to become an FCN. In
case a spare part will no longer be produced the above
procedure applies, now, however, not later than 9 months
before the item will no longer be produced.
It is worth noting that the failure reports' file may
be employed in screening for systematic errors. If
necessary, copies of the logbook and error print-outs
covering the observed time span must be accessible
to CR.
2.3.3 M̲o̲d̲u̲l̲e̲ ̲F̲l̲o̲w̲
If an error occurs at a site, the problem can most
often be traced down to a defective module which will
be replaced, usually from stock. The module is returned
to a repair depot and simultaneously another spare
module is sent to the site. Refer to sec. 6.3.
The shipment from a site to the repair depot must be
covered by a failure report.
2.3.4 F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲s̲
When a failure report (refer to fig. 2.3.4-1) is filled
in at a site, one copy is filed for information, one
copy is sent to SHAPE, and one together with the failing
item to the repair depot. When the repair is completed,
the failure report is also completed and one copy is
filed, one copy is sent to SHAPE, and one copy is filed
at CR.
The failure reports, which are numbered in succession,
contain 3 sections. The first section is the identification
part which is filled in by the originator, the second
section applies only to the sites, while the third
section applies to depots only.
The failure report serves as a cover sheet in order
to register all failures. If there is not sufficient
space for an error description a reference is made
to an enclosure where details can be found.
This is especially applicable when dealing with a S/W
error in which case a S/W error report will be filled
out, attached to the failure report and forwarded to
the CSSI and ISSC sites.
Failure Report
Fig. 2.3.4-1
2.3.5 L̲o̲g̲b̲o̲o̲k̲
A logbook (see fig. 2.3.5-1) will be supplied and be
effective at each site from the SPA. The logbook must
at all times reflect the status of the equipment e.g.
unavailability due to:
- Failures
- Corrective Maintenance
- Preventive Maintenance
- On-Job-Training
- Equipment Expansion
- Load of new Software
- Verification of repairs
- Other access with the EMI doors open
The logbook must reflect the time span of any irregularity,
the cause of it, what has been done within the time
span (remedy), a signature, and a possible reconfiguration.
The logbook may be a reference document for a failure
report to which a copy may be enclosed. Furthermore,
the logbook must be accessible to CR to the extent
necessary for systematic troubleshooting.
Logbook
Fig. 2.3.5-1
2.3.6 E̲r̲r̲o̲r̲ ̲P̲r̲i̲n̲t̲-̲O̲u̲t̲s̲
All events detected by the on-line diagnostic are logged
on the maintenance position Line Printer with a time
indication and an error information. If an automatic
switchover is performed this will also be indicated.
As the error print-outs are the true information of
the equipment status it is mandatory that they are
filed at least during the warranty period and as the
failure reports very often are initiated by an event
causing a print-out, it is usually desired that a copy
of the print-out is an enclosure to the failure report.
Also the print-outs must be accessible to CR to the
extent necessary for a systematic troubleshooting.
2.4 T̲O̲O̲L̲S̲ ̲A̲N̲D̲ ̲T̲E̲S̲T̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲
2.4.1 S̲i̲t̲e̲s̲
A list of tools, test equipment, accessories, consumables,
programmes, etc. required for maintenance of a CAMPS
site is being prepared. In its final form, the list
will be priced and handed to SHAPE for approval. Test
equipment which is included in the basic contract will
be clearly identified. It may be deleted from the
basic contract as well as new equipment may be added
by an appropriate amendment.
Upon acceptance, the list will be incorporated in the
Technical Manual - Inventory.
Some tools - both standard and special - may be gathered
in a suitcase together with selected consumables to
form a service kit and offered as such to SHAPE in
order to improve the maintenance effectiveness.
The appendix contains a tentative list showing the
to-date recommended tools.
2.4.2 D̲e̲p̲o̲t̲s̲
TBD
The tools and test equipment list will be issued later
pending a decision on the test methods employed at
the depots.
2.4.3 T̲o̲o̲l̲s̲
2.4.3.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲T̲o̲o̲l̲s̲
A standard set of multi-purpose hand tools is specified.
They will be applicable throughout the various maintenance
tasks and need no further presentation. They will
be listed in the tools catalog section in the Inventory
document.
2.4.3.2 S̲p̲e̲c̲i̲a̲l̲ ̲T̲o̲o̲l̲s̲
Special tools will be specified as required. They
will typically have one application in the maintenance
program and will be specified and referenced in details
in the tools catalog section in the Inventory document,
where they also will be pictured.
2.4.4 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲(̲T̲E̲)̲
2.4.4.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Standard TE with multi-purpose applications will be
specified. It is typically oscilloscope, voltmeter,
etc.
2.4.4.2 S̲p̲e̲c̲i̲a̲l̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
Special TE will be specified in order to ease troubleshooting
and/or alignment. It may be instruments bought from
sub-contractors or special developments designed by
CR.
Incorporated in the special TE list are also monitoring
instruments such as temperature and humidity recorders,
etc.
2.4.4.3 S̲c̲e̲n̲a̲r̲i̲o̲s̲
The figures in this section shows the application of
test equipment and identify the necessary break-points
in the CAMPS equipment. A tentative list of the applied
TE is found in the appendix.
CAMPS-Crate Lay-Out
Fig. 2.4.4.3.1-1
2.4.4.3.1 C̲r̲a̲t̲e̲ ̲L̲a̲y̲-̲o̲u̲t̲
Fig. 2.4.4.3.1-1 identifies the applicable extension
boards. In the PU crates and the I/O Channel crate
access to the panel wiring may be gained by tilting
the rear crate with power ON.
The fans for PU, I/O Channel, and TDX crates are accessed
from the front by removal of screws. Dust filters
may be removed with power ON.
The fan in the WD is built into the crate. No dust
filter is necessary.
2.4.4.3.2 I̲n̲t̲e̲r̲n̲a̲l̲ ̲B̲u̲s̲ ̲L̲i̲n̲e̲s̲
Fig. 2.4.4.3.2-1 shows the interconnection buses between
modules and crates. Buses identified by 1 to 6
are being analyzed for the use of an easy test procedure.
A short description of the test tools is found below.
1 & 2. P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲B̲u̲s̲ ̲a̲n̲d̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲B̲u̲s̲
An off-line M&D program exercises the bus lines when
an error cannot be refered to a particular module.
The lines are verified individually.
Tools: Test Program
Extension Boards
Analyzer
3 & 4. C̲r̲a̲t̲e̲ ̲I̲n̲t̲e̲r̲c̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲B̲u̲s̲ ̲a̲n̲d̲ ̲I̲/̲O̲ ̲B̲u̲s̲
An off-line M&D program may be loaded to exercise the
bus lines when an error cannot be refered to a particular
module. The lines are verified individually.
Tools: Test Program
Extension Board (for I/O Bus only)
Analyzer
5. T̲D̲X̲ ̲B̲u̲s̲
An off line M&D program may be loaded to exercise the
bus lines via the TIA when an error cannot be refered
to a particular module. The lines are verified individually.
Tools: Test Program
Analyzer
X-net Outlet Adaptor
6. 1̲6̲-̲w̲i̲r̲e̲ ̲C̲C̲A̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲s̲
The wires will be individually measured by means of
an oscilloscope or an analyzer. The possibility of
a stimulus program is being investigated.
Tools: Oscilloscope
Test Program
7. W̲a̲t̲c̲h̲d̲o̲g̲ ̲I̲n̲t̲e̲r̲c̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲L̲i̲n̲e̲s̲
No measuring. If an error cannot be referred to a
particular module, the crate is exchanged.
Tools: Multimeter
Internal Bus and Standard V24 Lines
Fig. 2.4.4.3.2-1
2.4.4.3.3 S̲t̲a̲n̲d̲a̲r̲d̲ ̲V̲2̲4̲ ̲L̲i̲n̲e̲s̲
Fig. 2.4.4.3.2-1 shows the standard V24 lines to both
the watchdog and the terminals.
8. A data communication Test Equipment will be employed.
A test program which can send and receive: "THE
QUICK BROWN FOX" etc. will be loaded and executed.
Tools: Test Program
Data Communication Tester
2.4.4.3.4 D̲i̲s̲k̲ ̲a̲n̲d̲ ̲F̲l̲o̲p̲p̲y̲ ̲D̲i̲s̲k̲
Fig. 2.4.4.3.4-1 shows the interconnection of the Disks
and Floppy Disk.
9. A test program will be employed for exercising
the communication with the disk and a Disk Exerciser
will be employed if available.
Tools: Test Program
Disk Exerciser (as applicable)
2.4.4.3.5 O̲P̲T̲O̲ ̲L̲i̲n̲k̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲s̲
Fig 2.4.4.3.5-1 shows the possible break-points in
the OPTO Link.
10. A test pattern may be sent from the PU to verify
the link. A loop-back tool shall verify the LTUX-S.
With the wrap-around connection removed a V24
Monitor inserted in the Monitor Panel can monitor
data sent both from PU and VDU.
11. The OPTO link modules have the ability both to
perform an internal check and a communication check
with a status word. LEDs will indicate the actual
status of the modules. An Optical Multimeter can
be used to check the OPTO cables.
Disk and Floppy Disk Configuration
Fig. 2.4.4.3.4-1
OPTO Link Connections
Fig. 2.4.4.3.5-1
12. By means of an adaptor a V24 communication tester/monitor
may be connected in order to separate VDU errors
from data link errors.
Tools: Loop-back connector for LTUX-S
V24 Data Communication Tester
Optical Multimeter
V24 Communication Monitor
V24/VDU Adaptor
2.4.4.3.6 V̲2̲4̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲L̲i̲n̲e̲s̲
Fig. 2.4.4.3.6-1 shows the possible break-points in
the V24 Link. Note that break-points common to fig.
2.4.4.3.5-1 are not mentioned here.
13. A loop-back connection shall be used to verify
the V24 Adaptor Driver/Receiver module. This is
separated from the LTUX's board because of the
previous mentioned test. Also a V24 Communication
Tester equipment may be connected.
Tools: Loop-back Connector
V24 Communication Test Equipment
2.4.4.3.7 E̲x̲t̲e̲r̲n̲a̲l̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲L̲i̲n̲e̲s̲
Fig. 2.4.4.3.7-1 shows the remote TARE link. The other
external channels end at the exit of the I/O Channel.
14. A test pattern may be sent from the PU to verify
the link. A loop-back tool shall verify the LTU.
V24 Terminal Lines…01…Fig. 2.4.4.3.6-1
15. A V24 Monitor equipment connected to the V24 Monitor
Panel can monitor data sent in both directions
when the loop-back connector is removed from the
LTU.
16. A loop-back connection on the LIA-N may isolate
this module.
17. A V24 Communication Test equipment may be applied
in order to send/receive a test pattern through
the Modems.
18. The Modems contain both an internal test and an
intercommunication test feature and the results
are indicated. In case of a communication failure,
a loop-back connection together with item 17 above
may provide an unequivocal proof whether the error
is inside the racks.
Tools: Loop-back connector for LTU
Loop-back connector for LIA-N
Loop-back connector for BPJF
Loop-back connector for BPJF (4-wire)
V24 Communication Test Equipment
V24 Monitor Equipment
V24 Adaptor for BPJF
Test Program
External Channel Lines…01…Fig. 2.4.4.3.7-1
2.4.4.3.8 R̲e̲m̲o̲t̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲L̲i̲n̲e̲s̲
The remote terminal lines are not yet defined, but
for the specification of test equipment a tentative
outline will be sufficient.
Fig. 2.4.4.3.8-1 shows the breakpoints in such a tentative
outline of the remote terminal link. A test program
which may transmit distributed test sequence through
several LTUX-S channels or via one selected channel
may be employed in order to exercise the multiplexer.
19. A loop-back connection between two LTUX-S channels
will verify that the LTUX-S is operating. A V24
communication test equipment may transmit or monitor,
respectively, a test pattern.
20. The Statistical Multiplexers feature an internal
as well as an intercommunication test to verify
the interconnections. If the signals are missing
a V24 Communication Tester can be employed to check
the Multiplexer.
21. A V24 Monitor may be employed to monitor the line
at this point.
22. A V24 Monitor or Communication Tester may be inserted
to isolate the VDU from the Multiplexer and to
transmit a test pattern through the Multiplexer.
Tools: Loop-back connector for LTUX-S
V24 Communication Tester
V24 Communication Monitor
Adaptor for V24 on Stat. Mux.
Adaptor for patch panel
Test program.
Remote Terminals Configuration (Tentative outline)…01…Fig. 2.4.4.3.8-1
2.4.4.4 C̲a̲l̲i̲b̲r̲a̲t̲i̲o̲n̲
If the calibration of a special TE cannot easily be
performed in simple operations with standard measuring
instruments at the site, the equipment shall be returned
to depot for calibration. Based on the final version
of the tools and test equipment list, it will be apparant
whether this situation exists or not.
If such a situation exists, a maintenance calibration
schedule is prepared and incorporated in the preventive
maintenance section of the Technical Manual vol. 1
- Maintenance (Ref. sec. 2.2) similar to the peripherals.
A sufficient reference or a detailed description of
the procedures involved and the standards to be met
will be attached.
The specification of this type of equipment will be
kept to a minimum.
2.4.5 A̲c̲c̲e̲s̲s̲o̲r̲i̲e̲s̲
Test accessories will be specified and listed. They
are typically extension boards, cables, adaptors, jigs,
etc. In its final form they will be part of the tools
catalog sections in the Inventory document where they
will be pictured and referenced.
2.4.6 C̲o̲n̲s̲u̲m̲a̲b̲l̲e̲s̲
Consumables are typically filters, sticks, cleaners,
etc. which are consumed during preventive maintenance.
They will be listed and referenced in the Inventory
document.
2.4.7 P̲r̲o̲g̲r̲a̲m̲m̲e̲s̲
All programmes, both application and maintenance M&D,
will be referenced and listed in the Inventory document.
2.5 C̲O̲D̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
All items reflected in the Approved Spare Parts List
(ASPL) will be codified with a NATO stock number.
Similarly, subassemblies not being addressed by the
ASPL and spares superseeding already codified items
will also be codified.
As the assignment of NATO stock numbers is an effort
successive to the ASPL of the equipment (including
peripherals), the procedure will commence after the
Recommended Spare Parts List (RSPL) is promoted to
ASPL. It is consequently an on-going task which is
performed in parallel with the evaluation of the Technical
Manual. In its final form it will be incorporated
as a separate section in vol. 4 - Inventory.
The number of codified items may be increased by separate
agreements during progress meetings in which case they
will be handled as above.
2.6 P̲R̲O̲V̲I̲S̲I̲O̲N̲I̲N̲G̲ ̲C̲O̲N̲F̲E̲R̲E̲N̲C̲E̲
As part of the approval of the maintenance plan a time
schedule for provisioning conferences shall be jointly
agreed. These conferences will provide the basis for
selection of parts, tools, and test equipment.
Items for discussion at the provisioning conference
are listed below.
a. Test Equipment (TE)
- TE for processor equipment
- TE for peripherals
- TE for general purposes
b. Tools
- Standard hand tools
- Special hand tools
c. Spare Parts
- Spare sub-assys for processor equipment
- Spare sub-assys for peripherals
- Piece parts
3. O̲N̲-̲S̲I̲T̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
3.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This section outlines the efforts required to maintain
the on-site CAMPS equipment. It discusses the employment
of manuals, tools, and test equipment.
3.2 W̲O̲R̲K̲ ̲D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲S̲
3.2.1 P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Scheduled preventive maintenance will be carried out
as specified in the Maintenance Manual. Preventive
maintenance includes the following tasks:
1) Replacement of airfilters.
2) Cleaning of equipment such as line printers and
papertape reader/puncher.
3) Inspection of ventilators.
4) Verification of modules returned from repair at
depot.
5) Calibration and alignment as specified in the Maintenance
Manual.
6) Visual examination of equipment as specified in
the Maintenance Manual.
At the conclusion of each preventive maintenance task,
the paperwork must be completed as specified in the
procedures.
3.2.2 C̲o̲r̲r̲e̲c̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Corrective Maintenance is the act whereby an abnormal
situation is corrected and the equipment restored to
normal operation.
Corrective maintenance will be effected by replacing
faulty modules and returning them to the depot for
repair.
3.2.3 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
The responsibility of the maintenance personnel at
site also includes installation of field modifications
issued by CR. Furthermore, expansion and reconfiguration
of the CAMPS System is the responsibility of the maintenance
staff.
3.2.4 S̲i̲t̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The Resident Site Technician (RST) will supervise CAMPS
Site Maintenance. He will be responsible for implementing
the procedures specified in the CAMPS Maintenance Documentation.
Among the specific responsibilities of the RST are:
1) Assist the other technicians in any maintenance
aspect of the system, provide technical expertise
and assume a leading role where difficulty is experienced
by the station personnel. The expertise which
the RST provides shall be that furnished by his
knowledge, supplemented by his guaranteed access
to the information and expert advice available
within CR.
2) Act as a technical expert in all matters relating
to the maintenance and repair of the system.
3) Administer the procedure necessary for the repair
and/or replacement of unserviceable items.
4) Administer the production of detailed statistical
records for all faults associated with the system
and from the records, advise SHAPE and the Officer-in-Charge
of adjustments necessary to on-site spare equipment
stock holdings.
5) Take all reasonable steps to ensure that any actions
carried out by the station personnel under his
guidance will not result in damage or malfunction
of the equipment.
6) Perform repair and maintenance tasks including
modifications when authorized by CR.
Technical cooperation between the RST and CR will normally
be encouraged. However, CR will inform the CAMPS project
manager of all contacts initiated by RSTs which relate
to repair and maintenance.
3.2.5 O̲n̲-̲J̲o̲b̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
On-job training of technicians and operators is performed
on site. The extent and depth is described in the
CAMPS Integrated Training Plan - CPS/PLN/010. The
RST is responsible for the conduct of OJT.
3.3 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
The On-site maintenance organizational flow is shown
in fig. 3.3-1. The maintenance tasks listed reference
the appropriate sections in the document.
On-Site Maintenance Organizational Flow…01…Fig. 3.3-1
3.4 P̲R̲E̲V̲E̲N̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
The on-site personnel must perform the recommended
routine maintenance tasks in order to ensure continuous
and satisfactory performance of the equipment. These
maintenance tasks are thoroughly described in the equipment
manuals, but for quick reference a preventive maintenance
chart for each piece of equipment requiring preventive
maintenance will be generated. Refer to fig. 3.4-1.
Each chart will contain information of the periodicity
of the specified maintenance task, key-words which
describe the task, and a reference to the manuals where
the detailed description may be found.
A registration form binds the individual maintenance
charts together thus providing an overview of the preventive
maintenance duties throughout the year. This form
will act as a planning tool for the RST ensuring that
the preventive maintenance schedule is maintained.
The form is filled in when issued, but special considerations
to the physical lay-out of a site and technicians available
may require a reorganization of the scheduled duties.
The RST may easily perform the reorganization under
the condition that the periodicity of the maintenance
tasks is preserved.
It is the responsibility of the RST that the preventive
maintenance program is executed.
Upon completion of a maintenance task, a maintenance
log form must be signed. The form is issued for every
piece of maintainable equipment. Generally, this form
should be resident at the equipment.
Fig. 3.4-1 gives examples of applicable types of equipment.
3.4.1 C̲e̲n̲t̲r̲a̲l̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The central equipment covers equipment installed in
crates within the CAMPS racks. Generally, the preventive
maintenance tasks are limited to cleaning of dust filters,
etc.
3.4.2 P̲e̲r̲i̲p̲h̲e̲r̲a̲l̲s̲
The peripherals are identified as all OEM equipment
inclusive of disks and frequency stabilizers. The
preventive maintenance procedures will generally rely
on the descriptions found in the respective manuals.
3.4.3 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The test equipment is identified to include both test
instruments employed during troubleshooting as well
as environmental monitors. The preventive maintenance
and/or scheduled calibration will generally rely on
the descriptions found in the respective manuals.
3.4.4 M̲o̲d̲u̲l̲e̲s̲
Modules returned from depot must be tested and verified
before they are stocked. This will prevent a total
system failure in case the module has suffered from
transportation damages or otherwise is defective.
The verification will not be scheduled, but may be
carried out at convenience. The modules shall normally
be tested in the off-line configuration.
Preventive Maintenance Structure…01…Fig. 3.4-1
3.5 C̲O̲R̲R̲E̲C̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
The objective of the corrective maintenance on-site
is to detect whenever an error is occurring, perform
the repair necessary, and bring the system back to
normal operation within the time limits specified by
the predicted MTTR requirements. This is achieved
through the "pull-and-replace" principle on a module
basis and by applying structural software tools (M&D
programs) in error detection and troubleshooting procedures.
The sequence will be as follows:
- Detect an error
- Isolate the error to an assembly
- Apply appropriate off-line M&D programs
- Interchange defective module with spare module
- Verify correct system performance
- Return to normal operation
- Complete paper work
A flow chart displaying the general troubleshooting
procedure as described throughout in this section is
found in fig. 3.5-1.
3.5.1 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
An on-line error detection program package will, together
with DAMOS, ensure that if errors are detected, an
error print-out is transmitted to the maintenance position.
The on-line error detection programs operate alongside
with the application program in order to detect an
error before it may damage normal operations. The
following diagnostic features are contemplated:
Flow Chart of General Troubleshooting Procedures…01…Fig. 3.5-1
- Test of the Watchdog Processor to ensure that the
Watchdog (WD) is operative and communicates with
both the operator position and the PUs.
- Analysis program for the TDX system. This is a
program which is executed when an error is detected
in a communication via the TDX bus.
- Communication test with the LTUs in the channel
Unit to detect possible errors.
- Stand-by PU test to ensure that the stand-by PU
will be operational if a switchover is required.
During normal operation check-pointing information
is transmitted via the TDX bus system to update
the stand-by PU with the current status of the
system stored on the disks.
The application programs are governed by DAMOS and
include an error detection facility. In case an error
is detected, an error print-out is sent to the maintenance
position. Also a keep-alive message is frequently transmitted
to the WD informing the WD that the PU is still operational.
A response from the WD to the PU ensures that the WD
is operational. In case the WD fails, so that no print-out
is possible on the maintenance position, the print-outs
will be directed to the supervisor position.
Another important DAMOS feature is the ability to perform
retries. If a read instruction from a disk gives invalid
data the operation is repeated. In case the operation
succeeds, the program continues, but the error will
be incorporated in a statistics program which may be
called from the operator position. Thus, a potential
problem may be foreseen and avoided.
If a soft-ware error is suspected the status of the
system should be filled in according to a S/W report
formular and a memory dump may be performed if appropriate.
The formular is sent to the CSSI site covered by a
failure report.
3.5.2 I̲s̲o̲l̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲E̲r̲r̲o̲r̲s̲ ̲t̲o̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲
When an error is detected, a print-out will be provided
on the maintenance position line printer together with
a time-of-day print-out. These print-outs are summarized
messages providing entry points for an off-line M&D
troubleshooting tree in order to speed up the troubleshooting
procedures. To the extent necessary on-line analysis
programs as described above for the TDX bus system
will be employed. The major elements identified are:
- WDP
- Processor Unit
- TDX
- Distribution Equipment
- External Channels
- Power Supplies
- Stand-by Processor Unit
A typical repair time sequence is shown in fig. 3.5.2-1.
Here an average repair is shown to be performed within
one hour which is the estimated repair time for all
modules as indicated in the R&M plan. This is sufficient
to fulfill the availability requirements. In many
cases, the repair time may be lower because the on-line
diagnostic programs will eliminate the necessity of
employing all the off-line M&D tests. That is especially
the case for errors in the TDX, distribution equipment,
and remote channels elements, where the analysis will
provide an immediate start to the troubleshooting.
A power supply error print-out will be equally easy
to remedy.
The time consumed by the repair is defined to be the
effective repair time not covering halts caused by
absence of technicians, missing spares, etc. These
conditions will be reflected in the logbook thereby
displaying the total unavailability or degraded performance
of the system.
Sequence of Typical Repair…01…Fig. 3.5.2-1
3.5.2.1 W̲a̲t̲c̲h̲d̲o̲g̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲
The Watchdog Processor Unit (WPU) controls the communication
with the maintenance position simultaneously transmitting
return messages to the active PU. Also the WD receives
keep-alive messages and error messages as well as switch
messages from the PU. Thus, the WD is a stand-alone
unit controlled from the active PU.
The configuration is shown in fig. 3.5.2.1-1.
3.5.2.2 P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲U̲n̲i̲t̲
An error in the active PU is typically detected by
DAMOS. If possible, the print-out will contain information
about the type of error (e.g. parity, instruction type,
memory location, etc.) Errors that will corrupt the
print-out routines and where the keep-alive signal
to the WD is missing will be interpreted as a PU error
and a switchover is required.
Finally, retries from the disks will be logged as failures
in the processor assembly.
The configuration is shown in fig. 3.5.2.2-1
Watchdog Processor Element…01…Fig. 3.5.2.1-1
Processor Element…01…Fig. 3.5.2.2-1
3.5.2.3 T̲D̲X̲
Errors in the TDX will be recognized and analysed by
an on-line program which will identify the failing
channels and provide a log to the maintenance position.
Switching to the redundant TDX bus will if necessary
be controlled by the PU.
The TDX configuration is shown in fig. 3.5.2.3-1.
3.5.2.4 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The distribution equipment consists of the modules
beyond the LTUX-S to the terminals. While in the TDX
sub-system, a cyclic redundancy check (CRC) is employed
to recognize errors on the TDX bus, no real on-line
tests are assumed for the distribution equipment although
multiplexers, modems, and crypto equipment for the
remote terminals may incorporate error detection facilities.
It is assumed that if the transmission is severed,
a Negative Acknowledge (NAK) is reported to DAMOS while
a data error will require intervention from the operator
at the terminal.
The configuration is shown in fig. 3.5.2.4-1.
3.5.2.5 E̲x̲t̲e̲r̲n̲a̲l̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲
The LTUs in the external channels are frequently tested
by an on-line program which transmits and receives
status words for comparison. If an error is detected,
the status is reported to the operator position.
The configuration is shown in fig. 3.5.2.5-1.
TDX Element…01…Fig. 3.5.2.3-1
Distribution Equipment Element…01…Fig. 3.5.2.4-1
External Channel Element…01…Fig. 3.5.2.5-1
3.5.2.6 P̲o̲w̲e̲r̲ ̲S̲u̲p̲p̲l̲i̲e̲s̲ ̲
(Refer to fig. 3.5.2.1-1)
The power supply lines are currently monitored by the
WD. The CCA and BSM-X modules in each crate are scanning
the voltages and by means of an A/D converter the voltage
is sensed. In this way variations in the power supplies
may be detected before causing damages. If the system
is corrupted by a power failure, DAMOS will report
the error detected in the application program, but
the succeeding print-out will be followed by reporting
of a power drop out.
3.5.2.7 S̲t̲a̲n̲d̲-̲b̲y̲ ̲P̲U̲
Tests continously being performed in the stand-by PU
will detect errors eventually resulting in an error
print-out at the maintenance position.
3.5.3 M̲&̲D̲ ̲P̲r̲o̲g̲r̲a̲m̲s̲
Once an error message is received, the maintenance
technician must start the faultfinding following the
instructions laid down in the troubleshooting trees.
The error print-out will provide an entry point to
a particular troubleshooting tree which will guide
the technician to the defective module(s). The troubleshooting
trees describe the application procedures of a string
of off-line M&D programs and reference sections in
the Maintenance Manual. Here the application procedures
of tools and test equipment are described in relation
to the actual test performed.
Prior to any execution of an off-line M&D program which
may be destructive to the resident data information,
a memory dump may be requested from the maintenance
position. This will be required in case a design failure
is suspected in order to analyse the origin of the
error, but will not be applicable in normal troubleshooting
procedures.
The troubleshooting trees which are employed and will
be described below are:
- WD troubleshooting tree
- System troubleshooting tree
- Off-line troubleshooting tree
3.5.3.1 W̲D̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲T̲r̲e̲e̲
The WD troubleshooting tree is rather simple, the WD
being a stand-alone element consisting of principally
two modules, a power supply, and a crate with a ventilator,
all replaceable.
3.5.3.2 S̲y̲s̲t̲e̲m̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲T̲r̲e̲e̲
The system troubleshooting tree is the highest level
of troubleshooting. It is applicable where the error
print-out is corrupted, in case of a total system failure,
or if other unpredictable situations occur. It also
references load of new programs, saving of data after
system failures, errors during start up procedures,
initial start procedures, etc.
The methods employed will typically be memory dumps,
descriptions of cold start procedures, descriptions
of the functioning of the on-line M&D programs and
DAMOS, and data save procedures.
Some types of errors may be difficult to isolate, but
by structuring the descriptions it may be possible
to find a pattern which can direct the troubleshooting
down to the off-line troubleshooting tree.
Intermittent errors and software problems may fall
into this group. It is worth noting then, that software
errors and hardware errors are distinctively different
in that way that software errors will never cause parity
errors as will typically hardware errors.
If an error is intermittent and cannot be detected
during the tests, it may be necessary to return the
equipment back into operation. In this case special
attention must be given to the problem.
3.5.3.3 O̲f̲f̲-̲L̲i̲n̲e̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲T̲r̲e̲e̲
The off-line troubleshooting tree describes the procedures
to be followed when isolating a recognized error down
to a module level. It addresses the application of
tools necessary and describes the employment of the
off-line M&D program package. The off-line M&D program
package consists of a string of test programs selectable
from the maintenance position VDU, typically one per
module. Depending of the type of module it may perform
an actual test of a module, or it may be used to exercise
one or more modules which are tested with a test equipment.
A typical example is the remote terminal lines which
will widely be exercised with TE in which case the
troubleshooting tree will address the procedures involved.
3.5.4 G̲a̲i̲n̲ ̲A̲c̲c̲e̲s̲s̲ ̲T̲o̲ ̲a̲n̲d̲ ̲R̲e̲p̲l̲a̲c̲e̲ ̲F̲a̲u̲l̲t̲y̲ ̲M̲o̲d̲u̲l̲e̲
Access to the modules implies that the shielded doors
must be opened. This will be necessary during some
of the tests, but it is part of the maintenance concept
that the doors will generally not need to be kept open
until the error is traced down to one module which
must then be replaced. This implies also that the
doors will be open a minimum of time during the corrective
maintenance procedures and that most of the troubleshooting
is effectively performed from the maintenance position.
3.5.5 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲e̲p̲a̲i̲r̲
After the replacement of a module, a verification test
must be performed to ensure that the error has been
removed. The same test which located the error to
be on that type of module must be employed.
3.5.6 R̲e̲t̲u̲r̲n̲ ̲T̲o̲ ̲N̲o̲r̲m̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
Upon completion of the verification test any interference
in the hardware which may have taken place, must be
reconnected and the shielded doors closed whereafter
the equipment is restored back to normal operation.
The procedures will be described in the Maintenance
Manual.
When the equipment returns to normal operation a time-of-day
print-out appears at the maintenance position.
3.5.7 P̲a̲p̲e̲r̲ ̲W̲o̲r̲k̲
Now the repair is completed and the papers concerned,
such as a Failure report, logbook, request for another
spare module, etc. as described elsewhere in this plan,
must be completed.
An error message print-out on the maintenance position
printer and a logbook will be the documentation prerequisites
for filling in a Failure Report form when the error
is found and remedied. Thus the failure reports inform
about the status of the system simultaneously providing
the necessary information for the repair of the defective
module.
Consequently, when a failure report is filled in, one
copy should be filed for own purpose, one must be sent
to SHAPE for information, and one copy should follow
a defective module when sent back to depot for repair.
The accompanying failure reports may be used in the
current fault analysis. The analysis of the failure
reports may result in a Field Change Notice generated
by CR and transmitted to SHAPE.
3.6 F̲A̲I̲L̲U̲R̲E̲ ̲R̲E̲P̲O̲R̲T̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲
3.6.1 L̲o̲g̲b̲o̲o̲k̲
From the commencement of the on-site installation,
a logbook must be generated and maintained. The logbook
must be the document that contains all deviations from
normal operation.
The logbook is a book of (numbered) pages where the
date and hour of an interruptional event is written,
the type of interrupt, the reason if possible, explanatory
remarks, and the date and hour of returning the equipment
back to normal operation again.
A copy of the corresponding page in the logbook should
be attached when completing a failure report.
3.6.2 E̲r̲r̲o̲r̲ ̲P̲r̲i̲n̲t̲-̲o̲u̲t̲
As virtually all errors are printed on the maintenance
position line printer, it is mandatory to preserve
this information for later failure analysis. Consequently,
the history which appears on the maintenance line printer
supplemented with the rare print-outs on the supervisor
position line printer when the maintenance position
is incidentally out of order must be filed in case
an analysis is required during the warranty period.
Likewise, whenever a failure report accompanies a defective
module to depot for repair, a copy of the error print-out
should be attached.
3.7 P̲E̲R̲S̲O̲N̲N̲E̲L̲
Any technician duly trained by CR or similarly will
be capable of performing maintenance on the CAMPS equipment,
although two levels of educational skills are mentioned
in the System Requirements. Refer to CAMPS Integrated
Training Plan - CPS/PLN/010.
The level of skills required are outlined in section
5.4 and further information about skills and duties
may be found in the CAMPS Integrated Training Plan
- CPS/PLN/010.
4. D̲E̲P̲O̲T̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
4.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
Two fixed depots are envisaged for the CAMPS program
one in Central Europe and one in the South, each including
a repair and a supply section.
The depots will perform calibration and repair of modules
and subassemblies as well as overhaul or rebuild of
equipment after extensive periods of operation. Furthermore,
the depots will hold spares to support the respective
sites for 270 days of operation.
The fixed repair depots will be staffed and managed
by NATO.
4.2 W̲O̲R̲K̲ ̲D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲S̲
Depot level maintenance, as currently planned for the
CAMPS equipment will comprise all maintenance tasks
beyond the capabilities of the site level. The depth
of depot level maintenance is unrestricted and consists
of the following maintenance functions:
- Repair of modules and subassemblies received from
the sites.
- Overhaul of items which includes a thorough repair
and alignment as well as accomplishments of modifications.
- Calibration of test equipment to national standards
to the extent it is found necessary in the CAMPS
maintenance program.
- Spares management which incorporates stock holdings,
replenishments to sites, and the communication
to CR through a central supply coordination agency
(NAMSA).
4.3 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
The CAMPS Depots will be part of the NATO Supply and
Repair Depot Service. They will be staffed by computer
trained technical personnel. Spares supply on the
CAMPS program will be managed by this organization.
4.4 S̲I̲T̲E̲ ̲S̲U̲P̲P̲O̲R̲T̲
The depots will start supporting the sites when CR
deliver spares to the depots. The depots will also
support the CR installation team with the depot spares
and provide the transportation of these spares from
site to site.
4.4.1 S̲u̲p̲p̲l̲y̲ ̲S̲c̲h̲e̲d̲u̲l̲e̲
All parts will be categorized into 3 groups as described
below corresponding to their importance for the availability
of the site equipment operation.
4.4.1.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲I̲t̲e̲m̲s̲ ̲(̲G̲r̲o̲u̲p̲ ̲I̲)̲
a) Items already in stock on the site and covered
by a high confidence level as described in the
RSPL.
b) Items not important for the electrical functioning
of the equipment.
4.4.1.2 C̲r̲i̲t̲i̲c̲a̲l̲ ̲I̲t̲e̲m̲s̲ ̲(̲G̲r̲o̲u̲p̲ ̲I̲I̲)̲
a) Items in stock on the site, but covered by a low
confidence level.
b) Items not stocked on the site, but not essential
for the equipment (degraded availability).
c) Items which, when not functioning, increases the
probability of a system failure significantly.
4.4.1.3 E̲m̲e̲r̲g̲e̲n̲c̲y̲ ̲I̲t̲e̲m̲s̲ ̲(̲G̲r̲o̲u̲p̲ ̲I̲I̲I̲)̲
a) Applies when a system failure has occurred or is
imminent and spares are not available at site.
4.5 P̲R̲E̲V̲E̲N̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
4.5.1 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲C̲a̲l̲i̲b̲r̲a̲t̲i̲o̲n̲
To the extent an on-site equipment needs scheduled
calibration, it will be individually decided whether
the equipment must be returned to the depot or another
calibration center.
The decision of calibration is subject to selection
of test equipment. However, if the calibration is
scheduled to be performed at the depot detailed instructions
and handling procedures will be available as part of
the maintenance program.
4.6 C̲O̲R̲R̲E̲C̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
4.6.1 M̲o̲d̲u̲l̲e̲ ̲R̲e̲p̲a̲i̲r̲ ̲d̲u̲r̲i̲n̲g̲ ̲W̲a̲r̲r̲a̲n̲t̲y̲
To provide the repair depot with valuable "dry-run"
experience before expiry of warranty following work
task is allowed during warranty:
a) Repair Depot is allowed to verify the boards in
the mock-up when received from the site before
going for warranty repair at CR. Likewise to verify
the boards after return from CR.
b) Repair depot is allowed to test the respective
boards on the incircuit tester and work stations
and identify a defective component before shipment
to CR for repair. Depot shall not perform any repair
unless authorized by CR.
c) The above depot activities shall not be started
before consultation with CR.
d) SHAPE will only perform repairs during the warranty
period acting as CR agent and will not be held
liable for any damage due to that repair.
4.6.2 M̲o̲d̲u̲l̲e̲ ̲R̲e̲p̲a̲i̲r̲ ̲a̲f̲t̲e̲r̲ ̲W̲a̲r̲r̲a̲n̲t̲y̲.̲
After expiration of the warranty period, the depot
takes over responsibility for module repair. The depot
repair is performed by using Gen Rad tester, Zehntel
tester and Mock-Up's.
4.6.3 T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲R̲e̲p̲a̲i̲r̲s̲
When an on-site test equipment needs repair it is individually
decided whether it should be returned directly to manufacturer
or to depot.
4.7 F̲A̲I̲L̲U̲R̲E̲ ̲R̲E̲P̲O̲R̲T̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲
The procedures in sec. 3.6 applies except that error
print-outs do not exist. Instead, a repair record
for every module will be generated and maintained and
a copy may be enclosed the failure report.
4.8 S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲O̲F̲ ̲T̲E̲S̲T̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲
Test equipment is specified in Appendix A.
5 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲
5.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The effectiveness of the CAMPS maintenance program
is dependent not only on well trained site personnel,
but also on the management parameters set up by the
customer. This section outlines and discusses the
requirements to customer's management program which
complements the proposed maintenance plan.
5.2 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲A̲L̲ ̲F̲L̲O̲W̲
The management structure is shown in fig. 5.2-1 below.
Maintenance Management Structure…01…Fig. 5.2-1
5.3 M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲ ̲R̲E̲S̲P̲O̲N̲S̲I̲B̲I̲L̲I̲T̲I̲E̲S̲
5.3.1 S̲i̲t̲e̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
The RST is responsible for implementing the procedures
as specified in the maintenance plan as well as local
and SHAPE related procedures.
Simultaneously, the RST is the on-site contact person
through which all approaches in technical matters are
directed from CR. The RST is responsible for the fulfilment
of maintenance tasks which may arise during the warranty
period of the equipment. Applicable tasks are field
modifications, load of new software, etc.
5.3.2 D̲e̲p̲o̲t̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
The following management responsibilities are applicable:
- Implementation of repair procedures as specified
by CR in the depot maintenance organization.
- Implementation of local and SHAPE related procedures
for repair, calibration, and spares management
at depot.
5.3.3 S̲H̲A̲P̲E̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
During the life of this contract, SHAPE must act as
the interface between CR and the CAMPS sites. The
sites will direct requests for contractor support to
SHAPE who will forward them to CR. Likewise, SHAPE
will direct all CR generated service instructions,
field modification notices, etc. to the sites.
Furthermore, SHAPE will on request from CR obtain relevant
information from the sites to aid CR in fulfilling
his maintenance responsibilities under this contract.
The operating procedures between SHAPE and CR should
be discussed between the parties.
5.3.4 C̲R̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
CR will establish and maintain an organization at CR's
headquarter in Ballerup to fulfill the requirements
under this contract.
5.4 P̲E̲R̲S̲O̲N̲N̲E̲L̲
At the site, two personnel categories will perform
maintenance on the CAMPS System:
1) Resident Site Technician (RST)
2) Technician
The following summarizes the qualifications of the
two categories. The fulfilment of the requirements
is an obligation to SHAPE.
Non-withstanding the requirements stated below the
contractual requirements as stated in CE 80-9009-INF
apply.
5.4.1 R̲e̲s̲i̲d̲e̲n̲t̲ ̲S̲i̲t̲e̲ ̲T̲e̲c̲h̲n̲i̲c̲i̲a̲n̲s̲ ̲(̲R̲S̲T̲)̲
The incumbent must be a 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 or installation testing
of such equipment. Previous experience in the repair
of automatic data processing systems is desirable.
The RST shall have an English language proficiency
level fo SLP 4443 as described in STANAG 6001 of 20th
October 1976.
5.4.2 T̲e̲c̲h̲n̲i̲c̲i̲a̲n̲s̲
The incumbent must have experience in electronic maintenance
especially in the respect of computer controlled message
processing and communication systems.
The Technician shall have an English language proficiency
level of SLP 3333 as described in STANAG 6001 of 20th
October 1976.
6. M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲S̲U̲P̲P̲O̲R̲T̲
6.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This section describes the CR support routines which
will commence after the SPA.
6.2 F̲I̲E̲L̲D̲ ̲A̲S̲S̲I̲S̲T̲A̲N̲C̲E̲
6.2.1 W̲a̲r̲r̲a̲n̲t̲y̲ ̲S̲u̲p̲p̲o̲r̲t̲
During the warranty period field service engineers
will be prepared to assist in service problems which
may arise at the sites. The service aid may take form
of advisory guidance to the RSTs or it may include
an on-the-spot service.
Requests for on-the-spot service visits must always
be routed through SHAPE. It is assumed, however, that
a service visit will have been preceded by consultancy
guidance from CR.
6.2.2 P̲o̲s̲t̲-̲W̲a̲r̲r̲a̲n̲t̲y̲ ̲S̲u̲p̲p̲o̲r̲t̲
The same kind of field assistance as provided during
the warranty period will be available, but the form
must be negotiated and laid down in a separate contract.
6.3 S̲P̲A̲R̲E̲S̲
6.3.1 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̲)̲
All spares listed in the ASPL will be delivered prior
to the provisional site acceptance (PSA) of each site.
After the first year of operation spares will be replenished
according to the contract.
6.3.2 F̲o̲l̲l̲o̲w̲-̲O̲n̲ ̲S̲p̲a̲r̲e̲s̲
Follow-on spares will be available on order for ten
years after expiration of the warranty period. Any
change which may occur will be notified in advance
to SHAPE prior to their execution. Upon acceptance
a change will be effective when covered by an Field
Change Notice (FCN). Refer to sec. 6.4.
The use of an FCN as described in this section replaces
the requirement for using a Spare Parts Design Change
Notice (SPDCN) as stated in para 3.7.3.1.8 of CAMPS
System Requirement Specification (CPS/210/SYS/0001).
6.3.3 I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲&̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲s̲ ̲F̲l̲o̲w̲
Fig. 6.3.3-1 and -2 display the communication and spare
part flow in the warranty and post-warranty period
respectively. It should be noted, that during the
warranty period, it is assumed that CR acts as a repair
depot and the NATO depot acts as a supply depot only,
and clearing house for all repairable items to be returned
to CR. When the warranty is expired, the depot will
take over the repairs and CR will usually resupply
through the depot.
However, a possibility exists to require parts as an
emergency shipment from CR. In this case a parallel
information must be sent to SHAPE which in turn must
confirm the order.
6.3.4 W̲a̲r̲r̲a̲n̲t̲y̲ ̲R̲e̲p̲a̲i̲r̲ ̲F̲l̲o̲w̲
All warranty repair shipments shall go through North
depot (AFCENT); items sent for repair as well as items
returned.
The documentation used for the shipment will be:
F̲r̲o̲m̲ ̲D̲e̲p̲o̲t̲ ̲t̲o̲ ̲C̲R̲ (with copy to SHNMO)
1) DD form 1348 (shipping document)
2) DMR
3) Form 302 (not SHNMO)
F̲r̲o̲m̲ ̲C̲R̲ ̲t̲o̲ ̲D̲e̲p̲o̲t̲ (with copy to SHNMO)
1) T2 (not to SHNMO)
2) Proforma Invoice and/or Packing List
3) Repair Report
CR include the following information in the proforma
invoice:
1) NSN (if available)
2) True Manufacturer's Part No
3) Quantity
4) Item Ser. No
5) DD 1348 Ser. No
A contact person at CR and at Depot will be identified
for reporting of shipping discrepancies etc. Mailing
and shipment addresses, telex and telephone numbers
are the following:
a. within AFCENT CLD:
NCO In-Charge Receipt and Despatch Section
Telephone No: NL 045263102
Central Region Signal Group
HQ AFCENT
Post Box 990
NL 6430 AZ HOENSBROEK
b. Within Christian Rovsing A/S:
Christian Rovsing A/S
SD-ILS Repair Center
2 Lautrupvang
DK 2750 Ballerup
Denmark
Telex: 35111 cr dk
Telefax: 02-654373
Telephone 01-651144…86…1 …02… …02… …02… …02…
Warranty Period Spare Flow…01…Fig. 6.3.3-1
Fig. 6.3.3-2…01…Post Warranty Period Spare Flow
6.4 F̲I̲E̲L̲D̲ ̲C̲H̲A̲N̲G̲E̲S̲
6.4.1 G̲e̲n̲e̲r̲a̲l̲
Whenever a modification is necessary a Field Change
Notice (FCN) will be issued and 2 copies will be provided
to SHAPE and to each site affected.
The FCN will contain detailed information describing
the:
- Type of information
- Tools, Parts, and time required
- Equipment to be modified
- Instructions for implementing the modifications
Where the FCN indicates use of materials they will
be enclosed. If a modification necessitates amendment
of documentation, new pages will be provided sufficient
to amend all affected documentation.
Generation of FCNs by CR will commence after the Site
Provisional Acceptance and take place during the H/W
or S/W warranty periods whichever is applicable.
6.4.2 R̲e̲g̲i̲s̲t̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲C̲N̲s̲
A reference or Master List of all modifications will
be issued and concurrently updated. Herein the FCNs
are listed consecutively indicating the equipment modified
and the reason for modification.
6.4.3 D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲C̲N̲s̲
The field Change Notice Sheets shown overleaf are explained
by the following subparagraphs (1-10).
Refer to fig. 6.4.3-1 and -2.
6.4.3.1 H̲e̲a̲d̲i̲n̲g̲
The FCNs are issued consecutively commencing with number
1. The number of pages included in the FCN in question
is indicated.
6.4.3.2 I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The part addressed by the FCN is identified by Type,
Parts No., NATO Stock no. if available, and description
as well as the next higher level is indicated.
6.4.3.3 P̲a̲r̲t̲s̲ ̲D̲i̲s̲p̲o̲s̲i̲t̲i̲o̲n̲
A checkmark indicates the disposition of parts, "N.A."
means "Not Applicable".
6.4.3.4 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The checkmark indicates the urgency by which the modification
must be executed. "Desirable" means earliest convenient
opportunity while "Mandatory" means immediately. "Mandatory"
classification is typically employed when the equipment
may malfunction without the modification or if the
operation of the system is endangered.
6.4.3.5 T̲y̲p̲e̲ ̲o̲f̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
This section is checked as appropriate. The three
main groups existing are:
- Rework (H/W change)
- Spares Change
- Software Change
Field Change Notice, Front Page
Fig. 6.4.3-1
Field Change Notice, Subsequent Pages
Fig. 6.4.3- 2
6.4.3.6 R̲e̲l̲a̲t̲e̲d̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
This section cross references related documents to
the FCN. Engineering Change Order (ECO) is the reference
no. for a CR in-house document, while the Failure Report
No. indicates that the FCN is originated by an error
occurred on a site or depot.
6.4.3.7 F̲i̲e̲l̲d̲ ̲C̲h̲a̲n̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The description includes a reason for action that is,
a brief explanation of why that particular FCN is necessary.
It also describes the change in details or, if the
space is insufficient, provides a summary of the modification.
It is always described as "Is" and "Was".
6.4.3.8 A̲f̲f̲e̲c̲t̲e̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
If a modification implies that the documentation is
revised, the applicable documents are listed with the
new revision level. Also reference documents are mentioned,
if any.
6.4.3.9 A̲p̲p̲r̲o̲v̲a̲l̲ ̲A̲u̲t̲h̲o̲r̲i̲t̲y̲
The author of the FCN must sign together with the approval
authorities and the RST which implemented the modification.
Upon completion, a signed copy of the front page of
the FCN must be returned to CR to indicate the status
of the equipment. The equipment is considered modified
upon receipt of this copy.
6.4.3.10 S̲u̲c̲c̲e̲e̲d̲i̲n̲g̲ ̲P̲a̲g̲e̲s̲
The succeeding pages provide the detailed information
about the modification. First the tools, parts, and
time required for the modification is indicated, next
step by step instructions illustrated as "Is" and "Was".
6.5 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̲
6.5.1 S̲/̲W̲ ̲W̲a̲r̲r̲a̲n̲t̲y̲ ̲P̲h̲a̲s̲e̲
6.5.1.1 P̲r̲o̲g̲r̲a̲m̲m̲i̲n̲g̲ ̲S̲e̲r̲v̲i̲c̲e̲s̲ ̲a̲t̲ ̲C̲R̲
A programming service will be provided commencing with
the SPA of the first site, i.e. start of S/W warranty,
and continue until such time that customer has formed
his own capability for S/W maintenance. The purpose
of this function will be to diagnose and correct faults
in the S/W if such should occur after the installation.
This service will also be in charge of the maintenance
of S/W documentation.
During the S/W warranty period, the programming service
shall be carried out at contractors facility unless
otherwise agreed. CR personnel may use the CSSI site
to test new or modified S/W.
Upon request and at additional costs, the service will
provide assistance for implementation of modifications
to the S/W.
Modifications will be authorized, issued, and produced
centrally by CR.
6.5.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
S/W modifications will be sent to the CAMPS sites where
the RST will perform the integration and test. The
following types of S/W modifications are identified.
6.5.1.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
System S/W may be modified to an extent which will
not affect the operation of the application software.
Modified system software is transported on a floppy
disk to the sites as an entity.
6.5.1.2.2 A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
Application S/W will be modified by CR's facility.
Modified application software is transported on a
floppy disk to the sites as an entity.
6.5.1.2.3 P̲a̲t̲c̲h̲e̲s̲
Patches of a size up to 50 instructions may either
be:
- transported to the site on a floppy disk or
- telexed or phoned directly to the RST at the site
The patch is loaded into the off-line disk from where
the RST may bring it into operation following the guidelines
which are described to him.
6.5.2 S̲/̲W̲ ̲P̲o̲s̲t̲-̲W̲a̲r̲r̲a̲n̲t̲y̲ ̲P̲h̲a̲s̲e̲
6.5.2.1 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲C̲o̲n̲c̲e̲p̲t̲
After the S/W warranty has expired, SHAPE will establish
the following maintenance organization.
- A central maintenance facility, i.e. Integrated
Systems Support Centre (ISSC) responsible for both
H/W and S/W maintenance and configuration control.
- An Operational Support Centre (OSC) responsible
for the day-to-day operation of CAMPS. The OSC
will be located at the CSSI site and, preferably,
be collocated with the ISSC.
- At the operational sites, the Resident Site Technicians
(RST) will be capable of diagnosing S/W faults
and report them to the OSC and ISSC. The RST will
be responsible for the system restoration following
standard procedures prepared by the ISSC.
The overall maintenance and control functions are shown
in Fig. 6.5.2.1-1 while the functions of the centers
are described below.
6.5.2.1.1 I̲n̲t̲e̲g̲r̲a̲t̲e̲d̲ ̲S̲y̲s̲t̲e̲m̲s̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲C̲e̲n̲t̲r̲e̲ ̲(̲I̲S̲S̲C̲)̲
Apart from a quick reaction cell for each system, the
ISSC reacts to error reports, locates faults, tests
fault repairs and issues updates; all of which are
under the control of the overall Network Configuration
Board (NCB). Within the ISSC there is a Systems Group
which supports the NCB in considering change requests
and in evaluating individual subsystem changes and
the effects on other subsystems. Under this Systems
group, each subsystem has its own subsystem group which
works with a model network in which enhancement/changes
may be tested prior to release. Supporting all of this
activity is a shared organization of administrative
staff and computer power which provides such services
as documentation, configuration management, and software
file configuration management.
Modifications to existing S/W and development of new
S/W at the ISSC will be carried out on CAMPS S/W development
system. This development system may be a subset of
an operational CAMPS equipment.
Post-Warranty Maintenance Function…01…Figure 6.5.2.1-1
6.5.2.1.2 O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲C̲e̲n̲t̲r̲e̲ ̲(̲O̲S̲C̲)̲
The Operational Support Centre (OSC) is in operation
for 24 hours a day/365 days a year and is the one contact
point for all emergencies raised at operational sites.
The OSC decides how faults can be best cleared. Any
requests for a quick fix will be made to the Integrated
Systems Support Centre (ISSC) facility which has to
be immediately responsive to the request. The OSC will
be collocated with an operational site.
The OSC acts as a focus for
- Operational tests
- Field trials and new releases from the ISSC
6.5.2.1.3 O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲S̲i̲t̲e̲s̲
At the sites S/W maintenance is limited to:
- generating trouble reports (FCNs)
- generating emergency trouble reports
- application of patches provided by phone and/or
message
- testing of patched S/W
- loading re-issues, enhancements, major revisions
- local site data base and configuration management
The media for transport of S/W updates to the sites
may be telephone, message, or floppy disc for patches,
while it will be floppy discs or removable disc packs
for re-issues and major revisions.
6.5.3 S̲/̲W̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲
The Failure Reports and Field Change Notices described
in sec. 2.3 and 6.4, respectively, will also be applicable
for S/W errors. In this case the forms will act as
cover sheets for more detailed information thus providing
means for central registration.
A̲ ̲P̲ ̲P̲ ̲E̲ ̲N̲ ̲D̲ ̲I̲ ̲X̲ ̲ ̲ ̲A̲
…01…PRELIMINARY TOOLS AND TEST EQUIPMENT…86…1 …02… …02… …02… …02…
1̲ ̲ ̲S̲C̲O̲P̲E̲
Appendix A contains a list of the tools and test equipment
necessary for maintenance . The list is divided into
site level and depot level.
2̲ ̲ ̲I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
2.1 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̲
With reference to the Tools and Test Equipment List
the following categories have been defined:
2.1.1 I̲D̲ ̲C̲o̲d̲e̲
The ID codes specify the application of the tools and
test equipment. The following applications have been
identified
ID Code Application
00 Standard tools and test equipment
01 Trouble Shooting
02 Installation
03 Disk
04 Field Modifications
05 PTP/R
06 OPTO Cables
2.1.2 G̲r̲o̲u̲p̲ ̲C̲o̲d̲e̲
The group code divides the types of tools and test
equipment into the following groups:
a) S̲t̲a̲n̲d̲a̲r̲d̲ ̲T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲(̲G̲r̲o̲u̲p̲ ̲A̲)̲
The Standard tools and test equipment are a standard
set of multipurpose handtools and test equipment.
b) S̲p̲e̲c̲i̲a̲l̲ ̲T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲(̲G̲r̲o̲u̲p̲ ̲B̲)̲
The special tools and test equipment are required
during installation, alignment, maintenance, and
testing.
2.1.3 Q̲u̲a̲n̲t̲i̲t̲i̲e̲s̲
The following general philosophy has been applied in
deciding the quantity baseline.
a) Two suitcases with 2 sets of standard tools allowing
work employment at a remote site and at the main
site simultaneously
b) One set of installation tools
c) One set of tools for field modifications
2.2 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̲
The depot tools and test equipment list will await
the detailed philosophy for the depot level.
2.3 P̲R̲I̲C̲E̲ ̲L̲E̲V̲E̲L̲
The prices indicated are June 1981.
