top - download
⟦f0b7f36a3⟧ Wang Wps File
Length: 18435 (0x4803)
Types: Wang Wps File
Notes: PIP
Names: »0022A «
Derivation
└─⟦83a4a04d1⟧ Bits:30005815 8" Wang WCS floppy, CR 0002A
└─ ⟦this⟧ »0022A «
WangText
…02…CPS/100/PIP/0001
…02…GJ/801017…02……02…#
CAMPS PROGRAM IMPLEMENTATION PLAN
…02……02…CAMPS
5̲ ̲ ̲P̲R̲O̲G̲R̲E̲S̲S̲ ̲ ̲R̲E̲P̲O̲R̲T̲S̲ ̲A̲N̲D̲ ̲M̲E̲E̲T̲I̲N̲G̲S̲
CR shall participate in formal progress meetings as described below:
On the second Tuesday of each month a progress meeting shall be held between SHAPE and CR
throughout the contract period. If that day coincides with a SHAPE or CR holiday, the meeting
will be held on the second working day after the holiday.
These meetings shall provide the main forum where any outstanding items and difficulties
encountered are discussed, and information exchanged between the two parties. The meetings
shall be chaired by CR's Program Management and its members shall be technical and administrative
personnel both from CR and SHAPE as required.
An agenda shall be issued by SHAPE one week prior to the meeting to allow ample time to prepare
for the discussions. CR shall provide his list of items to SHAPE by telex at least one working
day prior to the day that SHAPE issues the agenda. Items outside of the prepublished agenda
may be brought up during the meeting, hovewer, these should be kept to a minimum, and the
reply to these items may not necessarily be given immediately.
A progress Report shall be handed over to SHAPE at the commencement of the meeting and this
report shall provide the basis for CR's presentation of the progress made to date. The progress
report shall contain a statement of all the activities that have been started and concluded
since last meeting with a reference to the Master schedule; a statement of problem areas
encountered and/or resolved; and a statement and plan for near future activities; and an
action item list reflecting CR's action towards SHAPE and vice versa.
An unanimously agreed draft Minutes of the Meeting shall be prepared at the end of each meeting.
Preparation of these minutes shall be considered as part of the meeting. Thus, long delays
for coordination after meetings will be avoided. The finally typed minutes shall be issued
within a week after the meeting. The issue of the final minutes is the responsibility of
CR. Sufficient copies to satisfy both CR's as well as SHAPE's requirements shall be provided.
Office of Primary Responsibility (OPR) shall be assigned to any paragraph requiring action.
The progress meetings shall be held at CR's premises in Ballerup unless otherwise agreed.
During the meetings problems which are likely to have a cost, technical or schedule effect
on the project shall be discussed. The problem analysis and solution shall be presented in
narrative form and shall include, as a minimum, the description of problems, options, proposed
solution, and effect on project cost, technical performance or schedule. Amendments to PIP,
as necessary, shall be made. Critical Path Analysis shall be performed and efforts will be
made to determine or forecast any problem areas well in advance so that corrective action
is taken immediately. Software as well as hardware aspects shall be considered.
CR shall modify, change or improve any equipment or plan as required in accordance with the
outcome of these meetings. Any changes in the equipment or plan shall be submitted under
the procedure as outlined in the Configuration Management Plan. The responsibility of the
performance and operation of the final equipments and system, and the overall running of
the project as specified in the requirement specification lies, however, with CR.
CR shall provide the appropriate technical personnel, organise and present briefings as required,
provide appropriate facilities, test and design data and supporting analysis to support the
meetings. CR shall provide technical reports and supporting documents in sufficient quantities
for inclusion to the minutes of the meeting.
In addition to the regular, monthly progress meetings described above, Ad Hoc Working Meetings
may be called subject to mutual agreement at the request of either SHAPE or CR to resolve
urgent problems, clarify programme requirements or review progress.
In addition to the formal progress meetings a number of design reviews shall be held
6̲ ̲ ̲I̲M̲P̲L̲E̲M̲E̲N̲T̲A̲T̲I̲O̲N̲ ̲D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲
The detailed implementation of the program will be defined in a series of Plans as required
by the Contract.
Each of these plans will describe in full detail how one area of the program will be managed.
In the following is given a brief description of the content of each of the plans.
6.1 S̲Y̲S̲T̲E̲M̲S̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲P̲L̲A̲N̲
A systems development plan which clearly identifies what is to be done by whom, when and
for how much will be written for Systems Engineering, H/W development and S/W development.
The essentials of the plan will be:
- A summary of the program which will state the essentials of the program.
- A list of all deliverable end products in such a way that when they are produced they
can be easily identified and compared with the plan.
- A list of milestones identified in such a way that there can be no ambiquity about whether
a milestone has been achieved.
- A Work Breakdown Structure (WBS) that is detailed enough to provide identification of
all tasks.
- From the milestone list and the WBS the activity schedules will be produced. See also
section 4.
- The review process will be elaborated.
- The major technical items to be planned for are mentioned in section 2.2.
6.1.1 D̲e̲s̲i̲g̲n̲ ̲S̲t̲a̲n̲d̲a̲r̲d̲s̲.̲
Based upon the Systems Requirements Specifications a set of standards to be used during preparation
of the design documents, source listings, test procedures, etc. will be written. These standards
will be written in accordance with the structure of the ACE directive 007-3 issue 2. See
the contract para 15 for additional information.
6.1.2 I̲n̲t̲e̲g̲r̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲
The Integration and Verification plan describes the subsystem software verification philosophy,
software interface test planning and the system level software integration and test activities.
The general requirements to be planned for are listed in section 2.2. The plan will also
identify the procedures to be produced and what these products shall contain.
6.1.3 R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲a̲n̲d̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲ ̲P̲l̲a̲n̲ ̲
The Reliability and Maintainability Plan contains a description of the philosophy used to
model, analyse, and control the reliability and maintainability of the H/W components.
6.2 L̲O̲G̲I̲S̲T̲I̲C̲S̲ ̲S̲U̲P̲P̲O̲R̲T̲ ̲P̲L̲A̲N̲ ̲
In the following section the Logistics Support Plans are described.
6.2.1. T̲r̲a̲i̲n̲i̲n̲g̲ ̲P̲l̲a̲n̲
6.2.1.1 G̲e̲n̲e̲r̲a̲l̲
The CAMPS Training Plan will describe the mandatory and optional training programs offered
by Contractor:
- Technical Hardware Training
- On The Job Training
- Software Training (optional)
- Training of Resident Site Technicians.
6.2.1.2 T̲e̲c̲h̲n̲i̲c̲a̲l̲ ̲H̲a̲r̲d̲w̲a̲r̲e̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
This course will provide training for 80 students, i.e. 8 courses with a class size of 10
students. The courses will be conducted in the period May 1982 to October 1983. Each course
will consist of a 2 weeks hardware module and a 3 weeks software module.
6.2.1.3 O̲n̲ ̲T̲h̲e̲ ̲J̲o̲b̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
Contractor will develop course and training material for on the job training of customer's
maintenance technicians. Courses will be conducted by customer.
6.2.1.4 O̲p̲e̲r̲a̲t̲o̲r̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
Contractor will develop courses for customers operator. The courses will be conducted on
site by customer using course material supplied by contractor.
6.2.1.5 So̲f̲t̲w̲a̲r̲e̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲ ̲(̲o̲p̲t̲i̲o̲n̲a̲l̲)̲
Contractor will develop and conduct courses on software. The training will commence when
Customer has built-up the necessary expertise.
6.2.1.6 T̲r̲a̲i̲n̲i̲n̲g̲ ̲o̲f̲ ̲R̲e̲s̲i̲d̲e̲n̲t̲ ̲S̲i̲t̲e̲ ̲T̲e̲c̲h̲n̲i̲c̲i̲a̲n̲s̲
Contractor will develop and conduct courses for the Resident Site Technician assigned to
a CAMPS installation. Customer will assign one technician to each CAMPS site and make him
available for training for a 6 month period.
6.2.1.7 T̲r̲a̲i̲n̲i̲n̲g̲ ̲o̲f̲ ̲N̲C̲S̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲o̲r̲s̲
The contractor will train 2 instructors from NCS Latina during the period January - June
1983.
6.2.2 R̲S̲P̲L̲,̲ ̲A̲S̲P̲L̲
6.2.2.1 R̲S̲P̲L̲
CR shall submit a Recommended Spare Parts List (RSPL) within 60 days contract signature.
The RSPL will include all spare parts required to support the equipment delivered. The recommended
spare parts will support towards the achievement of predicted availability at each site with
a given level of confidence.
The RSPL will be based on on-site held spares sufficient to cover 90 days of operation at
each site. Furthermore it will include both a single depot concept and a two supply depots
concept with the spares required to cover 270 days of operation. The confidence level to
be used when determining the RSPL shall be 80%.
The RSPL will give due consideration to maintenance float at the central depot(s) as well
as insurance type items, i.e. items which though not required for pure statistical reasons
must be included due to operational reasons or lead time considerations. Notification will
be made on each item of the RSPL as to whichever method has been applied.
The RSPL will be submitted in tabular form under the following headings:
- site or depot identification
- item number
- description and type
- NATO Stock Number (where applicable)
- True Manufacturer's Part Number
- Quantity installed at each site
- Recommended quantity of spares per site
- Unit Price
- Remarks
A separate list will be provided for each site and one for each of the two central depot
concepts.
6.2.2.2. A̲S̲P̲L̲
The Approved Spare Parts List (ASPL) shall be determined jointly by SHAPE and CR during provisioning
meetings to be held by CR A/S. The ASPL shall be derived by using the RSPL and equipment
documentation. The final ASPL shall be agreed to and incorporated in the contract not later
than 60 days after the submission of the RSPL.
6.2.3 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲
The Documentation Plan will describe how all documentation related to the CAMPS Project will
be managed. Documentation standards will be described as well as quality control procedure
applicable to documentation.
The plan will be divided in two main sections:
1. Organization and Documentation Management
2. Description of the various documentation items and their associated standards.
CAMPS documentation will be the responsibility of the Logistics Department. Generally, the
contributors of the data will provide reviewed drafts to the documentation department where
the final version will be produced.
The Technical handbooks will be divided into two types of manuals: Maintenance Procedures
Handbooks and Equipment Handbooks.
The Maintenance Procedures Handbook will describe how customers Maintenance technicians can
maintain the equipment to the required level i.e. module replacement.
Equipment handbooks will give technical details about the Operational and functional aspects
of the equipment.
User Manuals will be written for CAMPS user, supervisor, supervisor assistent and for the
CAMPS H/W operator.
As-built documentation is derived from Civil Works Requirements Specifications and AS-TO-BE-BUILT
drawings. The drawings will be generated by a subcontractor to CR in accordance to standards
governing the CAMPS project.
Test documentation will be generated to accommodate both internal and external verifications
conduction on the CAMPS program. Each document will be designed to record the test it is
associated with. In most cases, the test form itself is an integral part of the test procedure
to be followed during the test.
Inventory documentation will be developed to cover all sites including depots.
6.3 P̲R̲O̲D̲U̲C̲T̲I̲O̲N̲ ̲P̲L̲A̲N̲
The plan will describe how contractor intends to manufacture, assemble and test the CAMPS
systems.
The allocation of responsibilities between the two divisions will be described i.e. System
Division(SD) having over all responsibility and Electronics Division (ED) developing and
producing the CR-80 modules hardware.
A detailed production and integration plan will be described illustrating the interrelationship
with development and testing.
6.4 I̲N̲S̲T̲A̲L̲L̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲T̲R̲A̲N̲S̲P̲O̲R̲T̲A̲T̲I̲O̲N̲ ̲P̲L̲A̲N̲
6.4.1 S̲i̲t̲e̲ ̲S̲u̲r̲v̲e̲y̲s̲
All sites under contract will be surveyed to provide the establishment of a good baseline
for site preparation and installation.
These surveys will provide for the initial contact between host nation representatives,
the contractor and the SHAPE delegation.
At each site information necessary to prepare the site civil works requirements and AS-TO-BE-BUILT
drawings will be gathered. Host nation delivered documents/drawing will be verified. Items
like transportation, temporary storage, installation, and installation support will be assessed.
6.4.2. S̲i̲t̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
In the period following site surveys the information gathered during site surveys will be
reviewed concerning preparation of site civil works requirements and AS-TO-BE-BUILT drawings.
If necessary, supplementary data is to be requested from host nation through SHAPE.
Contractor's civil works requirements will be used by host nation to design and prepare the
site for installation of the CAMPS equipment.
Contractor will also prepare AS-TO-BE-BUILT drawings, which will contain all details concerning
equipment installation.
Upon completion of the site preparation works a verification at each site will take place.
The verification shall prove that the site is ready for installation of the CAMPS equipment.
The proving will consist of inspections and tests according to a site verification procedure.
The procedure will be prepared on the basis of contractor's civil works specifications, the
AS-TO-BE-BUILT drawings and host nation civil works drawings.
The procedure is to be signed off by the representatives from host nation, SHAPE and CR and
issued as a site verification report.
Discrepancies found during the verification will be recorded together with corrective actions
to be taken and completion date of actions.
After successfull completion of the verification the site is ready for installation.
6.4.3 T̲r̲a̲n̲s̲p̲o̲r̲t̲a̲t̲i̲o̲n̲
Delivery of equipment for CAMPS will follow the schedule of the Master Schedule Plan. Actual
dates of shipment are to be determined with consideration to each site's readiness and transportation
time needed for the selected way of transportation.
A transportation plan, which describes how the Contractor will coordinate each site delivery
will be forwarded to SHAPE.
The plan will deal with packing, marking, shipping documentation, transport of equipment,
and reception at each site.
6.4.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
An installation schedule will be set up which optimizes personnel utilization within the
overall program scope and ensures that each site installation is completed in a timely fashion
to allow adequate test and checkout of equipment for site acceptance.
Contractor will forward to SHAPE an installation plan, which describes how he will manage
and coordinate the installation task
The plan will deal with manpower loading, installation scheduling, on site installation support,
Contractor's installation organization and responsibilities of the installation team.
6.5 A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲ ̲T̲E̲S̲T̲ ̲P̲L̲A̲N̲
Based upon the acceptance criterias to be specified during the requirements specification
phase, an acceptance test plan will be written. The plan defines the acceptance philosophy
for the h/w and s/w. The acceptance test procedures are procedures written by CR A/S and
are basically a subset of the systems verification procedures.
It furthermore:
- provides the test schedule
- identifies the performance requirements
- identifies the acceptance criterias
- provides a test tool development plan if any
- describes the objective and purpose of each test
- specifies staffing and other resources required to accomplish the task.
6.6 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲ ̲P̲L̲A̲N̲
An independent Quality Assurance Department is responsible for all Quality Assurance activities
pertaining the CAMPS project.
As basis for this activity will be used the established Quality Assurance Programme outlined
in Quality Assurance Plan SD/040/PLN/001 of which the following is a summary
The product assurance planning is divided into five separate activity areas as follows:
- Hardware Quality Assurance
- Software Quality Assurance
- System Reliability
- Parts and Materials
- Configuration Management
The detailed requirements for these areas are defined in five separate subplans. Each subplan
defines the quality assurance surveillance and the establishment of standards and procedures
for the equivalent area.
The purchaser QA delegate has the necessary access to perform the required QA in accordance
with NATO Stanag 4107 and 4108. The QA plan should be drafted in line with AQAP-1.
6.6.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲Q̲u̲a̲l̲i̲t̲y̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲P̲l̲a̲n̲
This plan comprises:
- Hardware design
- Hardware production
- Hardware testing
- Production of specification and drawings
- Calibration of instruments
- Inspection of products delivered by purchaser or other suppliers
- Reviews and audits of hardware production
