top - download
⟦0437ffa2e⟧ Wang Wps File
Length: 38781 (0x977d)
Types: Wang Wps File
Notes: PC/PIP/001
Names: »2345A «
Derivation
└─⟦1ebdd46fc⟧ Bits:30006237 8" Wang WCS floppy, CR 0625A
└─ ⟦this⟧ »2345A «
WangText
…18……0b……18……02……18……05……17……0b……17……0d……17……02……17…
…16……0b……16……0d……16……0e……16… …86…1
…02…
…02…
…02…
PC/PIP/001
…02… SN/820630…02……02…#
PROTOCOL
CONVERTER
PROJECT
IMPLEMENTATION
PLAN…02……02…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION ....................... 5
1.1 Scope .............................. 5
1.2 Applicable Documents ............... 5
2 PROJECT MANAGEMENT & ORGANISATION .. 6
2.1 Organisation ....................... 6
2.2 Staffing ........................... 6
2.3 Project Implementation Procedures .. 8
2.3.1 Top-Level Work Breakdown Structure . 8
2.3.2 Operating Procedures ............... 10
2.3.3 Contracts Management & Admin-
istration........................... 13
2.3.4 Problem Recognition & Resolution ... 13
2.3.4.1 Problem Recognition ................ 13
2.3.4.2 Meeting............................. 14
2.3.4.3 Reporting........................... 14
2.3.4.4 Problem Resolution.................. 15
2.3.4.5 Customer Coordination .............. 15
3 WORK BREAKDOWN STRUCTURE AND
SCHEDULE............................ 16
3.1 Work Breakdown Structure ........... 16
3.2 Program Schedule.................... 19
3.2.1 Reports and Documentation........... 19
3.2.2 Software/Firmware................... 20
3.2.3 Services............................ 20
3.2.4 Hardware............................ 20
3.3 Planning Network.................... 21
4 SYSTEM DEVELOPMENT PLAN ............ 23
4.1 Introduction ....................... 23
4.2 System Engineering.................. 23
4.2.1 System Requirements Specification .. 23
4.2.2 Test Plans and Test Procedures ..... 24
4.2.3 Reliability Program................. 24
4.3 Hardware Specification ............. 24
4.4 Software Development ............... 25
4.5 System Integration ................. 25
5 RELIABILITY AND MAINTAINABILITY PLAN 26
5.1 Introduction........................ 26
5.2 R & M Model......................... 26
5.3 Calculated Reliability.............. 26
5.4 Availability........................ 26
6 MAINTENANCE PLAN ................... 29
6.1 Maintenance Engineering............. 29
6.2 Field Support....................... 29
6.3 Spares Management................... 30
6.4 Tools and Test Equipment............ 30
6.5 Failure Reporting................... 30
6.6 Plans and Procedures................ 31
6.7 Maintenance Plan Outline............ 31
7 TRANSPORTATION AND INSTALLATION PLAN 32
7.1 Summary ............................ 32
7.2 Organisation ....................... 32
7.3 Implementation Plan ................ 33
7.4 Preparation of as-to-be-built
Drawings............................ 34
7.5 Transportation and Planning ........ 34
7.6 Installation and Planning .......... 35
8 ACCEPTANCE TESTING ................. 36
9 TRAINING ........................... 36
10 DOCUMENTATION....................... 36
11 QUALITY ASSURANCE .................. 37
11.1 Parts and Materials ................ 37
11.2 Reliability ........................ 37
11.3 Quality Control .................... 37
11.4 Quality Assurance Policy ........... 38
11.5 Quality Assurance System ........... 38
11.6 Configuration Management .......... 39
12 Customer Responsibility ............ 41
1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
1.1 S̲c̲o̲p̲e̲
This document specifies the Management Plan for the
CAMPS/SCARS/WWMCCS Protocol Converter Project, hereinafter
referred to as the PC.
1.2 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
1.ACE ADP Standards Manual 007-3, 14 Jan. 1980.
2.AQAP-1, 13
3.Quality Assurance Policy (CR/QAP/001), Christian
Rovsing A/S
4.Installation Sequence and Site Numbering (CPS/TCN/020),
Christian Rovsing A/S.
2 P̲R̲O̲J̲E̲C̲T̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲ ̲&̲ ̲O̲R̲G̲A̲N̲I̲S̲A̲T̲I̲O̲N̲
2.1 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
A dedicated Project Office will be established within
the Systems Division - see FIGURE. 2-1.
The Project Office will have total system responsibility,
cognizance, and control authority in order to coordinate
in-house activities and provide close liaison with
the customer throughout the duration of the project.
The Project Manager will also undertake the tasks of
Engineering Management, Operations Management and be
supported by the Logistics Manager.
Within the supporting functional departments PC activities
will be assigned as project entities.
The site installations, provisioning, documentation,
training and field support aspects of the PC will be
planned and coordinated by the Logistics Manager supported
by the Logistics Support staff of Christian Rovsing
A/S.
The Project Office will establish the baseline for
work breakdowns, specifications, schedules and budgets;
it will
monitor variances and initiate corrective action.
2.2 S̲t̲a̲f̲f̲i̲n̲g̲
The following is a list of staff for key positions
on the PC project:
Project Manager: Steen N]rgaard
Logistics Manager: Ole Eskedal
SYS.DIV.
Gert Jensen
P C C A M P S I L S O T
H E R
Steen N]rgaard Gert Jensen Ole Eskedal P R O J
E C T S
PC/CAMPS RELATIONSHIP WITHIN
THE SYSTEMS DIVISION
FIGURE 2-1
2.3 P̲r̲o̲j̲e̲c̲t̲ ̲I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
This Project Implementation Plan, PIP, establishes
a firm baseline for all activities against which status,
progress and performance can be evaluated and controlled.
PIP will be used as a management tool to provide visibility
and control of the project. It describes the schedule,
performance control system, the detailed Work Breakdown
Structure (WBS), the project administration, the interfaces
with Shape and other aspects of the project.
2.3.1 T̲o̲p̲-̲L̲e̲v̲e̲l̲ ̲W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
The WBS will be the framework for establishing work
packages, schedules and budgets for managing the project
and will provide the baseline for performance evaluation.
A project tasks overview is shown in FIGURE. 2-2
The WBS is under management control and changes to
the WBS require Project Office approval. Combined with
the master schedule milestones for engineering, operations
and logistics, the WBS will become the system-level
plan.
PROJECT TASKS OVERVIEW
FIGURE 2-2
2.3.2 O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The Project Office is responsible for:
P̲l̲a̲n̲n̲i̲n̲g̲: Evaluation of contract requirements
and allocation of work to the various
functional groups.
W̲o̲r̲k̲ ̲A̲s̲s̲i̲g̲n̲m̲e̲n̲t̲: Performance of work statements, meeting
specification, budget and schedule
requirements.
M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲: Periodic review of technical schedule
and cost performance applying programme
control through budget authorisation.
C̲o̲-̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲: Co-ordination of all project activities
between participating departments.
Internal management procedures have been implemented
as a practical cost/schedule control system which produce
valid, auditable and timely performance reports. Variances
from budget and schedule are quickly identified and
significant deviations are flagged for immediate project
management attention and corrective action.
Technical supervision and monitoring are effected through
periodic design reviews with hardware and software
engineering staff.
The primary management controls are based on a WBS,
Master Schedule and Budget,providing firm baselines
early in the project as the basis for management; see
FIGURE 2-3.
The WBS consists of a family tree of hardware, software,
services and tasks organized to define and geographically
display the work to be accomplished for a successful
implementation of the project. As a planning tool,
it defines the work packages for planning, scheduling
and cost control. Negotiated and approved project changes
are reflected in the baseline WBS.
The master schedule incorporates customer-agreed milestones
from the contract (ref.: Appendix E, Deliverable Items
and Milestone schedule), and indicates the timing relationships
of the WBS elements. Detailed plans derived from the
master schedule establish work package milestones.
The budget baseline allocates the resources between
operating departments following contract award. Work
authorisations are timephased based on schedule constraints
All detailed packages identified and assigned from
the WBS are defined by an internal statement of work,
schedule, and budget thus establishing a performance
measurement baseline.
WBS, MASTER SCHEDULE AND BUDGET
FIGURE 2-3
2.3.3 C̲o̲n̲t̲r̲a̲c̲t̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲&̲ ̲A̲d̲m̲i̲n̲i̲s̲t̲r̲a̲t̲i̲o̲n̲
Contracts Management and Administration is a staff
function within the company providing support to the
Project Manager.
The function is responsible for the following:
o Contract terms and conditions in relation to the
customer, i.e. formulation and agreement of the
Contract between SHAPE and CR.
o Contract terms and conditions for purchase orders
on sub-contractors and suppliers of standard equipment
and supplies
o Project budgets
o Invoicing
o Settlement of suppliers and sub-contractors
o Finance
o Cost control
The function is required to keep such cost and accounting
records as are required to perform audit consistent
with Danish Law and according to the terms and conditions
of the contract.
The function is responsible for the conversion of all
capacity and other budgets and plans into economic
terms permitting the safe establishment of rolling
budgets and long range financial forecasts.
2.3.4 P̲r̲o̲b̲l̲e̲m̲ ̲R̲e̲c̲o̲g̲n̲i̲t̲i̲o̲n̲ ̲&̲ ̲R̲e̲s̲o̲l̲u̲t̲i̲o̲n̲
2.3.4.1 P̲r̲o̲b̲l̲e̲m̲ ̲R̲e̲c̲o̲g̲n̲i̲t̲i̲o̲n̲
From project start to start of acceptance test the
exchange of information between the Project Manager
and Shape is performed via:
- regular meetings
- progress reports
- telex, letter and telephone
- demonstrations.
The information to be exchanged makes it possible for
Shape to monitor the project and product and thus enables
Shape to intervene if some deficiencies which might
not be covered by the specification are foreseen.
In case that such deficiencies should occur, these
are handled a s Change Requests, which are acted upon
by the Project Manager specifying the cost and schedule
impact that the change might create.
However, in case that the Project Manager recognizes
that a specific requirement cannot be fulfilled within
the frame of the project he immediately informs Shape
and includes suggestions for the solution.
2.3.4.2 M̲e̲e̲t̲i̲n̲g̲s̲
Progress meetings will be held in conjunction with
major milestone reviews:
System Design Review - 29 - 30 July 1982
Acceptance Test Procedures - 82-11-15,82-11-16 & 82-11-17
Site 1 Factory Acceptance Test - 28 Jan. 1983
These meetings will take place at CR in Ballerup.
Representatives of SHAPE shall have the right to visit
the CR plant(s) to ascertain the progress relative
to any of the contract items and/or contractual performance
of securities at any time during working hours with
advance notice to CR. Other meetings, at either SHAPE
or CR, may be held according to need, and the date
and place of these meetings will be mutually decided
by SHAPE and CR.
2.3.4.3 R̲e̲p̲o̲r̲t̲i̲n̲g̲
The reporting by the Project Manager consists of:
- progress reports
- minutes of progress meetings.
Progress Reports describing critical activities regarding
design, manufacturing and management are submitted
at bimonthly intervals.
The contents of Progress Reports are typically as follows:
o Technical Status
o Problems Outstanding
o Schedule Status & Report
o List of documents received and submitted within
the reporting period
o Action Item List
2.3.4.4 P̲r̲o̲b̲l̲e̲m̲ ̲R̲e̲s̲o̲l̲u̲t̲i̲o̲n̲
Whenever internal problems and deviations are ascertained
the Project Manager refers the matter to the responsible
party.
The Project Manager takes action if responsibility
for the problem discovered is difficult to place.
QA problems within production are referred to the Project
Manager.
2.3.4.5 C̲u̲s̲t̲o̲m̲e̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲
Possible problems which may arise and which require
Shape action are reported directly to SHAPE for necessary
follow-up and action, whatever the case may be.Reporting
will be by telephone followed up by telex.…86…1
…02… …02… …02… …02…
3 W̲O̲R̲K̲ ̲B̲R̲E̲A̲K̲D̲O̲W̲N̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲,̲ ̲S̲C̲H̲E̲D̲U̲L̲E̲,̲ ̲A̲N̲D̲ ̲P̲L̲A̲N̲N̲I̲N̲G̲ ̲N̲E̲T̲W̲O̲R̲K̲
3.1 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
The design, implementation, installation and commisioning
of the Protocol Converter require the Work Packages
listed below to be performed by Christian Rovsing A/S.
The Programme Schedule, showing delivery dates of the
Work Packages, is given in section 3.2. A planning
network diagram, showing work package interdependence,
is given in section 3.3.
1. P̲r̲o̲g̲r̲a̲m̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
1.1 Program Management
1.2 Monthly Progress Reviews
1.3 Project Implementation Plan
2 S̲y̲s̲t̲e̲m̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲
2.1 Systems Engineering Management/Technical
Coordination
2.2 System Requirements Specification (SRS)
2.3 System Requirements Review
2.4 Test Plan
2.5 Test Procedures
2.6 Reliability Program
3 H̲a̲r̲d̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
3.1 Equipment Handbook Preparation
3.2 Equipment Manufacturing
4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲
4.1 Software Management
4.2 Software Design Specification (Sub-system
level)
4.3 Software Design Specification (Program level)
4.4 Program Coding and Unit Testing
5 S̲y̲s̲t̲e̲m̲ ̲I̲n̲t̲e̲g̲r̲a̲t̲i̲o̲n̲
5.1 Site 1 In-factory Integration and Testing
5.2 Site 2 In-factory Integration and Testing
5.3 Site 3 In-factory Integration and Testing
5.4 Factory Acceptance Test (FAT) site 1
5.5 FAT site 2
5.6 FAT site 3
6 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
6.1 Management and Planning
6.2 Site Preparation
6.2.1 Site Survey
6.2.2 Site Verification
6.2.3 As-Built-Doc.
6.3 Transportation
6.3.1 Site 1
6.3.2 Site 2
6.3.3 Site 3
6.4 Installation
6.4.1 Site 1
6.4.2 Site 2
6.4.3 Site 3
7 A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲
7.1 Preliminary site Acceptance Test (site 1)
7.2 Provisional site Acceptance Test (site 1)
7.3 Provisional site Acceptance Test (site 2)
7.4 Provisional site Acceptance Test (site 3)
8 T̲r̲a̲i̲n̲i̲n̲g̲
8.1 Training Plan
8.2 Hardware Maintenance
8.3 On-the-Job Training
8.3.1 Site 1
8.3.2 Site 2
8.3.3 Site 3
9 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
9.1 Equipment Handbook
9.2 Hardware Maintenance Handbook
9.3 Engineering Drawings (As-Built)
9.4 Inventory list per Site
9.5 Software Documentation
10 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲a̲n̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲
10.1 Hw Warranty site 1
10.2 Hw Warranty site 2
10.3 Hw Warranty site 3
10.4 Spares
10.4.1 RSPL
10.4.2 ASPL
10.5 SW Warranty
3.2 P̲r̲o̲g̲r̲a̲m̲m̲e̲ ̲S̲c̲h̲e̲d̲u̲l̲e̲
The programme schedule, listing each deliverable item
and its date of delivery, is given below.
3.2.1 R̲e̲p̲o̲r̲t̲s̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
L̲i̲n̲e̲ ̲I̲t̲e̲m̲ #̲ ̲o̲f̲ ̲c̲o̲p̲i̲e̲s̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲d̲a̲t̲e̲(̲y̲y̲-̲m̲m̲-̲d̲d̲)̲
1.1 PIP 9 82-06-30
1.2 Requirements Specification 9 82-04-30
1.3 Acceptance Test Plan 9 82-07-30
1.4 Acceptance Test Prodecures 9 82-11-02
1.5 Maintenance Plan 9 82-08-30
1.6 Progress Reports telex bimonthly
1.7 Equipment (Hw) Handbook(draft) 12 82-11-15
1.8 System Specification 9 82-07-15
1.9 Package Design Specification 12 82-11-02
1.10 Site a-t-b-b documentation 9 82-08-30
1.11 Site as-built documentation 9 83-01-30
1.12 Factory Acceptance Test Report
Site 1 6 83-01-30
1.13 Factory Acceptance Test Report
Site 2 6 83-02-15
1.14 Factory Aceptance Test Report
Site 3 6 83-02-28
1.15 PSA Test Report, Site 1 6 83-04-15
1.16 PSA Test Report, Site 2 6 83-05-31
1.17 PSA Test Report, Site 3 6 83-06-30
1.18 System Software
Documentation (standard CR doc-
umentation) 9 82-09-15
1.19 Maintenance Handbook 9 83-01-15
1.20 RSPL 9 82-08-31
1.21 ASPL 9 82-10-31
1.22 Equipment Handbook (final) 9 83-02-28
1.23 SW Program Maintenance Manual 9 83-04-15
3.2.2 S̲o̲f̲t̲w̲a̲r̲e̲/̲F̲i̲r̲m̲w̲a̲r̲e̲
#̲ ̲o̲f̲ ̲c̲o̲p̲i̲e̲s̲ D̲e̲l̲i̲v̲e̲r̲y̲
EPROMMED 1 per PC with
systems
Application and AMOS System
SW Object Code
Hardcopy of Application SW 8 with
Source Code systems
CR80 Editor & Swell Compiler 1 with
for AMOS SW Development CAMPS
3.2.3 S̲e̲r̲v̲i̲c̲e̲
#̲ ̲o̲f̲ ̲s̲e̲r̲v̲i̲c̲e̲s̲ L̲o̲c̲a̲t̲i̲o̲n̲
Hardware Maintenance course 1 CR
OJT 3 at
sites
prior
to
PSA
3.2.4 H̲a̲r̲d̲w̲a̲r̲e̲
Site 1 Provisional Acceptance Test (PSA) 83-04-15
Site 2 Provisional Acceptance Test (PSA) 83-05-31
Site 3 Provisional Acceptance Test (PSA) 83-06-30
3.3 P̲l̲a̲n̲n̲i̲n̲g̲ ̲N̲e̲t̲w̲o̲r̲k
The planning network, showing task dependencies, is
given in FIGURE 3-1 overleaf.…86…1 …02… …02… …02… …02…
PLANNING NETWORK
FIGURE 3-1…86…1 …02… …02… …02… …02…
4 S̲Y̲S̲T̲E̲M̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲P̲L̲A̲N̲
4.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The Systems Development Plan comprises the following
tasks:
o System Engineering
o Hardware Specification
o Software Development
o System Integration
4.2 S̲Y̲S̲T̲E̲M̲ ̲E̲N̲G̲I̲N̲E̲E̲R̲I̲N̲G̲
System Engineering consists of the following tasks:
o System Requirements Specification/Design
o Test Plan - the requirement matrix required in
the test plan (007-3) as augmented by those required
in CAMPS shall be augmented by the identification
of the security related tests.
o Test Procedures
o Verification Control Document for internal use.
o Reliability Program.
4.2.1 S̲y̲s̲t̲e̲m̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Appendix G of the contract is the system requirements
baseline for the protocol converter.
4.2.2 T̲e̲s̲t̲ ̲P̲l̲a̲n̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
Subsequent to the system requirements specification
a Final Test Plan and Test Procedures will be specified.
The test will be:
o Factory Acceptance Tests including TEMPEST validation
for site 1
o Preliminary Site Acceptance Test (PC-WWMCCS)
o Provisional Site Acceptance Test (CAMPS/SCARS-PC-WWMCCS)
4.2.3 R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲P̲r̲o̲g̲r̲a̲m̲m̲e̲
The reliability programme is be conducted in accordance
with Section 4 of the SRS, Availability and Maintainability,
contained in Appendix G of the contract.
The available goal stated in Section 4.6.1.1 of the
SRS, MTBF Verification, is to be greater than or equal
to 3500 hours. As calculated in Section 7.8.1 of this
document, all modules of the PC have predicted MTBF
values exceeding 3500 hours. The MTBF verification
is performed in accordance with Section 4.6.1.1 of
the SRS. The MTTR of the PC (fault finding) is set
equal to 0.2 hours. MTTR verification is performed
in accordance with section 4.6.1.2 of the SRS.
4.3 H̲a̲r̲d̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Protocol Converter Hardware will be specified in
the Equipment Handbook in accordance with the requirements
of section 10.4 of the SRS.
4.4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲
Software development consists of the following tasks: o System
Specification
o Assembly of documentation for:
- System Software (AMOS)
- Maintenance and Diagnostic software.
- Development Software
o Package Design Specification
o Coding
o Unit testing .
Software Design specification for the application software
will be produced in accordance with ACE Directive 007.
Software development will be carried out as specified
in Special Clause 18 of the contract.
4.5 S̲y̲s̲t̲e̲m̲ ̲I̲n̲t̲e̲g̲r̲a̲t̲i̲o̲n̲
Each system will be integrated and tested in the factory.
The software will in the final system resite in EPROM.
To ease the test of the first system, all software
will be prepared on a floppy disc and loaded into RAM.
When the converter have been finally accepted the program
will be issued in an EPROM.
5 R̲E̲L̲I̲A̲B̲I̲L̲I̲T̲Y̲ ̲&̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲A̲B̲I̲L̲I̲T̲Y̲ ̲P̲L̲A̲N̲
5.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The Reliability and Maintainability Plan (R&M) shows
that the PC will meet an overall equipment availability
of 0.999, as stated in Section 4.4 of the SRS. A reliability
model is used to predict the availability of the system
and a system of reporting will provide evidence that
the individual modules do meet the reliability figures
used.
5.2 R̲ ̲&̲ ̲M̲ ̲M̲o̲d̲e̲l̲
The R & M Block Diagram Model of the PC is shown in
FIGURE 5-1.
5.3 C̲a̲l̲c̲u̲l̲a̲t̲e̲d̲ ̲R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲
The MTBF for each module in the R & M Module is given
in FIGURE 5-2. The overall system MTBF is equivalent
to 3390 hours, and the MTTR to switch to a spare converter
is taken as 0.2 hours.
5.4. A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲
Using the formula for availability given in Section
4.3 of the SRS, the PC has an availability of 0.999941,
which meets the system requirement stated in Section
4.4 of the SRS.
Minicrate
WITH P.C.
CPU
SCM
EPROM
LTU
CAMPS
LTU-
WWMCCS
LIA-CPS
LIA
WWMCCS
V24 Filter
Mains
Filter
Power
Filter
CTX
CRATE
R & M MODEL
FIGURE 5-1
M̲o̲d̲u̲l̲e̲ ̲N̲a̲m̲e̲ M̲T̲B̲F̲ ̲ ̲ ̲ Backed up by CAMPS spares
1.Minicrate with
power 26300 38 Watchdog crate
2.CPU-SCM 36500 28
3.128k RAM 17000 59 128k RAM
4.EPROM 32k 10873 92
5.LTU-CAMPS 27600 36
6.LTU-WWMCCS 27600 36
7.LIA-CPS 10000000 0.1 X
8.LIA-WWMCCS 10000000 0.1 X
9.V24 Filter 5000000 0.2 X
10.Mains Filter 625000 1.6 X
ll.Power Filter 625000 l.6 X
12.CTX crate with
power 31250 32 X
-----
TOTAL 324.10…0e…-6…0f…
------
Equivalent to MTBF = 3090 hours.
MTTR of a faulty converter = 1 hour
MTTR to switch to spare converter = 0.2 hours
RELIABILITY CALCULATIONS
FIGURE 5-2
6 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲A̲N̲D̲ ̲S̲U̲P̲P̲O̲R̲T̲
6.1 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲
a) The Maintenance Section of the Logistics Department
is responsible for giving appropriate input to
System Engineering to ensure that the Converter
will meet the requirements for maintainability.
b) The Maintenance Section will work closely with
Systems Engineering to ensure consistency in
determination of the MTBF and MTTR figures.
c) The development of the Maintenance Plan and Associated
Procedures will be carried out by the Maintenance
Function.
d) In the area of deliverable documentation the
maintenance section will generate the Maintenance
Manual and conduct maintenance related training.
6.2 F̲i̲e̲l̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲
a) Field Support will be managed by The Maintenance
Section. The two major activities are:
1) Co-ordinate the implementation of field changes
2) Co-ordinate warranty repairs.
b) All questions forwarded to the Project Office
by the customer relating to equipment already
installed and accepted will be co-ordinated by
the Field Support Function
6.3 S̲p̲a̲r̲e̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
a) The Maintenance Section is responsible for the
specification, acquisition, packaging and delivery
of spares, repair and repairable sub-asemblies.
A priced Recommended Spare Lists (RSPL) will
be submitted to the customer. Conferences will
be held at the Contractor's facilities - planned
and conducted by The Maintenance Function.
b) An Approved Spare Parts List (ASPL) will be negotiated
with the customer and incorporated in the contract
by amendment.
c) Spare Parts Design Change Notices (SPDCN) will
be issued and controlled by the Maintenance Function.
6.4 T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The Maintenance function will specify all tools and
test equipment to be supplied under the contract.
Furthermore, a price list of tools and test equipment
will be submitted to the customer for all items required
at each site and maintenance depots to support the
equipment supplied. The Provisioning Conferences will
be held at the contractor's facilities - planned and
conducted by the Maintenance Function.
6.5 F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲
The generation and implementation of a Failure Reporting
System will be the responsibility of The Maintenance
Engineer. All incoming reports will be recorded and
analysed by The Maintenance Engineer and corrective
action co-ordinated with The Contractor's Program Office
if appropriate.
Annotated copies of the reports will be received by
The Quality Assurance (QA) and Systems Engineer, who
may participate in the analysis.
6.6 P̲l̲a̲n̲s̲ ̲a̲n̲d̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The following documentation will be developed. Some
of the plans listed below may make reference to subplans
and procedures which already are in existence or will
be developed under this program.
1) Maintenance Plan
2) RSPL
3) ASPL
4) List of Tools and Test Equipment
5) Maintenance Hand books.
6.7 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲P̲l̲a̲n̲ ̲O̲u̲t̲l̲i̲n̲e̲
The system wil be delivered with Maintenance and Diagnostics
Software with the aim of performing fault isolation
to board level (module level).
As the 8 converters are installed at only 3 sites we
recommend that the system should be backed up by a
set of spares at each site for 90 days and one depot
level set of spares for 270 days.
A RSPL will be generated. After a provisioned conference
the confirmed ASPL will be incorporated in the Maintenance
Plan as an appendix.…86…1 …02… …02… …02… …02… …02…
7 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̲
7.1 S̲u̲m̲m̲a̲r̲y̲
The protocol converter equipment is to be installed
at CAMPS sites number 01, 06, 05 concurrently with
the installation of the CAMPS equipment (see "Installation
Sequence and Site Numbering" for site number definition).
The equipment allocated for each site will preferably
be shipped to the site together with the CAMPS equipment.
7.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
a) The transportation and installation will be performed
by the Integration Logistics Department (ILS)
of the systems division. The ILS department is
also responsible for the transportation and installation
of the CAMPS.
The project organization including the ILS department
is shown in section 2.
b) The installation section within ILS will be responsible
for the installation of the protocol converter
and the planning of transportation and installation,
which will include preparation of civil works
requirements AS-TO-BE-BUILT and AS-BUILT documentation.
c) The on site installation of the converter will
be performed by the CAMPS installation team.
The team will be trained in the installation
of the converter by participation in integration
and test at CR's plant up to factory acceptance
test of the converter.
7.3 I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲
The following major tasks and deliveries are defined
and listed in chronological order:
1. Delivery of site documentation according to SRS
section 8.1 by Shape to CR 60 days after contract
award.
2. Preparation by CR of AS-TO-BE-BUILT-drawings
to include civil works requirements.
The drawings are to be submitted to SHAPE for
approval 60 days after reception of the site
documentation.(see SRS section 10.6)
3. SITE preparation by SHAPE/TERRITORIAL HOST NATION
.
In accordance with the approved civil works requirements
(see appendix D of contract) the site preparation period
will be completed with a site verification performance
by CR in connection with CAMPS (see appendix D and
CAMPS major schedule).
4. Delivery of the converter equipment and transportation
to site by CR in accordance with contract and
SRS, Section 8.1:
o The converter equipment will be shipped according
to the CAMPS delivery schedule
5. On site installation by CR, which may be monitored
by ACE COMSEC, or local COMSEC staff, per SRS
section 8.1.2.1.The installation will be performed
in continuation of the installation of CAMPS.
6. Delivery of updated AS-TO-BE-BUILT drawings at
time of PSA by CR.(see SRS section 10.6.)
7.4 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲A̲s̲-̲T̲o̲-̲B̲e̲-̲B̲u̲i̲l̲t̲ ̲D̲r̲a̲w̲i̲n̲g̲s̲
a) After reception of the site documentation CR
will start preparation of AS-TO-BE-BUILT drawings.
The drawings will include equipment related requirements
to sites concerning civil works.
b) The documentation will cover the following in
writing text and drawings:
1. Cable plan showing major equipment and relations
cable connections
2. Room layout showing the converter equipment
as installed, with details concerning mechanical
installation and cable interface
3. Requirements to access, space, cable ducting,
power and grounding
4. Other civil works requirements (if any).
5. A specification of constructions and customers
responsibilities concerning site preparation
and installation.
c) The ATBB drawings will be submitted to SHAPE
for approval and the approved drawings will be
used by CR for equipment installation. Updated
drawings will be presented as AS-BUILT drawings
at time of PSA.
7.5 T̲r̲a̲n̲s̲p̲o̲r̲t̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
a) The converter equipment will be packed marked
and shipped to site according to section 8.1
of the SRS.The equipment will be shipped from
CR's plant in Copenhagen, Denmark to a mainsite
by truck together with the related CAMPS equipment.
The converter shipment will be documented and
notified to SHAPE as part of the CAMPS shipment
to the same site.
b) Shipment of OPTO-cables to be run by host nation
will also follow the CAMPS shipment schedule,
if possible.
7.6 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
a) The installation of the converter equipment will
be performed in continuation of the CAMPS equipment
installation at the applicable sites.
b) The equipment will be installed according to
the requirements in section 3 and 8.1 of the
SRS. SHAPE will furnish support in accordance
with appendix D of the contract.
c) The installation team will perform installation
of the converter in accordance with the installation
procedure, and the AS-TO-BE-BUILT drawings.
The drawings will be marked up during the installation
to reflect possible changes and as AS-BUILT drawings
at time of PSA.
d) An installation check out will complete the installation
and indicate that the equipment is ready for
PSA.…86…1 …02… …02… …02… …02…
8 A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲ ̲T̲E̲S̲T̲I̲N̲G̲
The test plan for Acceptance Testing and Handover is
described in a separate document entitled, "TEST PLAN"
The Plan describes:
Factory Acceptance Test
Preliminary Site Acceptance Test
Provisional On-Site Acceptance Test
9 T̲R̲A̲I̲N̲I̲N̲G̲
The Training Plan is given in Attachment 1 to the PC-PIP.
1̲0̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲
The following documentation items/tasks will be performed:
- Equipment Handbook
- Hardware Maintenance Handbook
- Engineering Drawings (As-Built)
- Inventory list per site
- Software Documentation
The specification of the documents is given in section
10 of the SRS.
11 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲
The Quality Assurance Manager (QAM) is responsible
for all QA tasks within the company. This includes
the establishment and control of general QA procedures
and special QA procedures for dedicated projects.
The Engineering Drawing Office and Secretariat operate
in accordance with the procedures established and controlled
by the QAM.
The Quality Assurance Manager is, in particular, responsible
for the following:
11.1 P̲a̲r̲t̲s̲ ̲a̲n̲d̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲ ̲(̲P̲&̲M̲)̲
P&M is responsible for procurement control, vendor
evaluation & qualification, and performs a support
function for receiving inspection and purchasing.
11.2 R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲
This is a supervision function available for all projects.
Reliability analysis, trade-offs, and tests are performed
by the project team under the supervision and control
of QA.
11.3 Q̲u̲a̲l̲i̲t̲y̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲Q̲C̲)̲
This includes the establishment and control of general
QC procedures within the company and special QC procedures
for dedicated projects, and the establishment and control
of QC requirements relating to subcontractors and suppliers.
The QC function is in particular responsible for:
- Evaluation of quality control plans
- Evaluation of inspection plans
- Incoming inspection of parts and materials and
subcontractual items
- In-process inspection
- Software
- End-item acceptance test
- Shop procedures
- Control of special procedures
- Methodology and calibration relating to test
instrument and tools
- Electrical and environmental tests
- Entrance control and cleanlines control of restricted
clean room areas
- Control of packing & shipping
- Trend reporting
- Quality audits
11.4 Q̲A̲-̲P̲o̲l̲i̲c̲y̲
The Quality Assurance Policy of the company is defined
in "Quality Assurance Policy" which is an internal
standard.
Based on this policy, the company has implemented a
standard QA-system which is compliant with "NATO Quality
Control System Requirements for Industry", AQAP-1.and
AQAP-13
11.5 Q̲A̲-̲S̲y̲s̲t̲e̲m̲
The standard QA system comprises a series of functions
among which are:
a) Q̲u̲a̲l̲i̲t̲y̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
At an early point in the contract performance,
the quality requirements are reviewed and a contract
related Quality Plan is established. This plan
is based on the standard QA system but may contain
amendments or exemptions, if necessary. The plan
contains detailed scheduling of QA participation
in such activities like design reviews, factory
test, acceptance test, etc.
b) D̲e̲s̲i̲g̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
The QA system provides strict control of all
new designs of both hardware and software. Design
…86…1 …02… …02… …02… …02… …02…
Reviews are scheduled and performed and no design
is released for production/programming without
proper approval.
c) C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲C̲h̲a̲n̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
A Configuration and Change Control system ensures
that all necessary documentation is established
and baselined. Also software is placed under
control after programming and development test.
SHAPE shall have right inspect all change requests
and their management.
d) W̲o̲r̲k̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲s̲
In all areas where necessary for quality, work
instructions and standards are established. Standards
define the required quality level and instructions
define processes needed to reach that level.
e) I̲n̲s̲p̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲
Detailed procedures are established for Inspection
and Tests to be performed during development,
production and upon completion of the contract
(acceptance test).
f) All inspection and test results - as well as
any other events significant for the documentation
of the product quality - are recorded and kept
in the QA files until completion of the contract.
They will be delivered to SHAPE (1) at factory
acceptance and (2) at completion of the contract.
11.6 C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The configuration management function will be performed
by the project staff and coordinated by the Product
Assurance Department. To carry out the task, a Configuration
Control Board (CCB) - consisting of relevant project
staff and a member of the Product Assurance Department
- meets to analyse, classify, and approve all changes.
The Product Assurance Department member acts as chairman
of The CCB, thus providing consistency and ensuring
that the benefits of experience are passed on from
project to project Changes are initiated by project
members.
All items released as part of the baseline configuration
as well as subsequent change documentation to these
items are identified for the purpose of Configuration
Control with one or more of the following numbers:
o Drawing or part number
o Revision number
o Serial number
o Specification description
o Change identification number
o Class code
o Justification code …86…1 …02… …02… …02… …02… …02…
12 C̲U̲S̲T̲O̲M̲E̲R̲ ̲R̲E̲S̲P̲O̲N̲S̲I̲B̲I̲L̲I̲T̲Y̲
Customer is responsible for the following tasks:
1. Provision of a CAMPS, SCARS II and WMMCCS at
the dates scheduled for test of PC.
2. Provision of adjustable test time in CAMPS,
SCARS II and WMMCCS during prime working hours.
Provision of WMMCCS during prime working hours
should be met 80% of the time.
3. Preparation of site in accordance with contractor
specified site requirements.
4. Provision of the signal cables from CAMPS, SCARS
II and WMMCCS to the converter.
5. Provision of test network and personnel as specified
in the test plan and the test procedures. It
is assumed the contractor personnel will operate
the converter during acceptance test, whereas
customer personnel will operate interconnecting
systems and test equipment that are under SHAPE
control.
