top - download
⟦03a13876f⟧ Wang Wps File
Length: 105164 (0x19acc)
Types: Wang Wps File
Notes: ACCESS Technical Data
Names: »3050A «
Derivation
└─⟦ab79d1adb⟧ Bits:30006221 8" Wang WCS floppy, CR 0269A
└─ ⟦this⟧ »3050A «
WangText
…1f……07……1e……0b……1e……0f……1e…
…1d……08……1d……0e……1d……00……1d… …1d……06……1c……0a……1c……0d……1c……02……1c…
…1b……0b……1b……00……1b……02……1a……0a……1a……0b……1a……02……19……0a……19……00……19……07……18……09……18……0f……18……05……17……0b……17…
…17……07……16……08……16……01……15……08……15……0c……15…
DOC 3050A
ACCESS PART II TECHNICAL DATA SYS/1983-01-25
SUBPART H - MANAGEMENT AND SUPPORT PLAN Page #
…01…A C C E S S
AUTOMATED COMMAND AND CONTROL
EXECUTIVE SUPPORT SYSTEM
DOC NO ACC/8004/PRP/001 ISSUE 1
PART II
TECHNICAL PROPOSAL
SUBPART H
MANAGEMENT & SUPPORT PLAN
SUBMITTED TO: AIR FORCE COMPUTER AQUISITION CENTER (AFCC)
Directorate of Contracting/PK
Hanscom AFB
MA. 01731
USA
IN RESPONSE TO:Solicitation No F19630-82-R-0001
AFCAC Project 211-81
PREPARED BY: CHRISTIAN ROVSING A/S
SYSTEM DIVISION
LAUTRUPVANG 2
2750 BALLERUP
DENMARK
…0e…c…0f… Christian Rovsing A/S - 1982
This document contains information proprietary to Christian
Rovsing A/S. The information, whether in the form of text, schematics,
tables, drawings or illustrations, must not be duplicated or
used for purposes other than evaluation, or disclosed outside
the recipient company or organisation without the prior, written
permission of Christian Rovsing A/S.
This restriction does not limit the recipient's right to use
information contained in the document if such information is
received from another source without restriction provided such
source is not in breach of an obligation of confidentiality
towards Christian Rovsing A/S.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
8. SUBPART H - MANAGEMENT AND SUPPORT PLAN ...
8.1 ACCESS PROGRAM MANAGEMENT ORGANISATION ..
8.1.1 Project Organisation .................
8.1.2 Project Communication ................
8.1.3 Key Management Description ...........
8.1.4 Training and Experience ..............
8.1.4.1 ACCESS Key Personnel .............
8.2 ACCESS PLANNING AND CONTROL .............
8.2.1 Schedule and Task Planning ...........
8.2.2 Assessment and Reporting of Project
Status ...............................
8.2.3 Subcontractor Management .............
8.2.4 Quality Assurance (QA) ...............
8.2.4.1 QA Areas of Responsibility .......
8.2.4.2 QA System ........................
8.3 ACCESS CONFIGURATION MANAGEMENT ..........
8.3.1 Configuration Control Items ..........
8.3.2 Configuration Identification .........
8.3.3 Configuration Control ................
8.3.4 Configuration Status Accounting and
Audits ...............................
8.4 COMPANY RESOURCES: RELEVANT EXPERIENCE,
FACILITIES, AND FINANCIAL STATUS .........
8.4.1 Relevant Experience ..................
8.4.1.1 Description of Major Contracts ...
8.4.1.2 Logistics Support and
Capabilities .....................
8.4.2 Facilities: Corporate Information ....
8.4.2.1 History of Christian Rovsing A/S..
8.4.2.2 Employee Profile .................
8.4.2.3 Facilities .......................
8.4.2.4 Organisation .....................
8.4.3 Financial Status .....................
8.4.3.1 Annual Report 1981 ...............
8.4.3.2 ACCESS Project Financing .........
…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
8. S̲U̲B̲P̲A̲R̲T̲ ̲H̲ ̲-̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲ ̲A̲N̲D̲ ̲S̲U̲P̲P̲O̲R̲T̲ ̲P̲L̲A̲N̲ ̲
Founded in 1963, Christian Rovsing A/S has expanded
rapidly to become a recognized supplier to major military
and civilian customers for computer systems, with essential
experience covering:
o design and production of computers
o development of extensive software packages
o prime contractor integration of hardware/software
systems
o full logistics support including turn-key system
installation, training, documentation, and maintenance.
Some examples demonstrating that Christian Rovsing
A/S has developed the necessary resources to meet exacting
demands are:
F̲-̲1̲6̲ ̲F̲i̲r̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲m̲p̲u̲t̲e̲r̲, procuced, tested, and delivered
by Christian Rovsing A/S in accordance with US Military
Standards under a co-production agreement with Delco
Electronics.
S̲p̲a̲c̲e̲ ̲S̲h̲u̲t̲t̲l̲e̲ ̲-̲ ̲S̲p̲a̲c̲e̲ ̲L̲a̲b̲'̲s̲ ̲E̲l̲e̲c̲t̲r̲i̲c̲a̲l̲ ̲G̲r̲o̲u̲n̲d̲ ̲C̲h̲e̲c̲k̲o̲u̲t̲
̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲ delivered under a sub-contract to
ERNO/European Space Agency (ESA), requiring implementation
of effective software management procedures to ensure
success of this major software package.
N̲A̲T̲O̲'̲s̲ ̲C̲o̲m̲p̲u̲t̲e̲r̲ ̲A̲i̲d̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲S̲y̲s̲t̲e̲m̲ ̲(̲C̲A̲M̲P̲S̲)̲
with Christian Rovsing A/S as prime contractor providing
SHAPE with:
- TEMPEST approved computer equipment, built by Christian
Rovsing A/S
- Fault-tolerant computing with automatic switch-over,
built by Christian Rovsing A/S
- ADPS, implementing complex military message and
security procedures
- Sub-contractor management with more than twenty
suppliers under contract, the biggest contract
with a value of over 2 million dollars.
A̲i̲r̲ ̲C̲a̲n̲a̲d̲a̲'̲s̲ ̲D̲a̲t̲a̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲, a new nation-wide communications
system for which Christian Rovsing A/S has been chosen
as prime contractor, indicating that the hardware,
software, and systems expertise at Christian Rovsing
A/S are commercially competitive items.
C̲o̲m̲p̲u̲t̲e̲r̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲s̲ ̲S̲y̲s̲t̲e̲m̲,̲ ̲D̲J̲O̲T̲/̲D̲R̲E̲S̲ is being
developed for the EDWARDS AFB, California by the Christian
Rovsing Corporation, Thousand Oaks, California. DJOT/DRES
is planned to be operational in October, 1983.
The Management and Support Plan for ACCESS will be
detailed in the four sub-sections to follow, namely:
8.1 ACCESS Program Management Organisation, showing
how communication channels address government needs.
8.2 ACCESS Planning and Control, giving the procedures
necessary to monitor status and ensure meeting
project requirement and schedules.
8.3 Configuration Control, presenting methods for coordinating
documentation and changes in hardware and software
to effect on-time delivery within specification.
8.4 Company Resources, highlighting the experience
and performance record for projects comparable
to ACCESS with proof of adequacy of company facilities
and financial status to undertake ACCESS.
8.1 A̲C̲C̲E̲S̲S̲ ̲P̲R̲O̲G̲R̲A̲M̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲ ̲O̲R̲G̲A̲N̲I̲S̲A̲T̲I̲O̲N̲ ̲
The ACCESS Project Office will have total system responsibility,
cognizance, and control authority in order to coordinate
in-house activities and provide close liaison with
the AFCC Contract Office throughout the duration of
the program.
8.1.1 Project Organisation
Overall direction for the ACCESS program is to be provided
by an administratively distict Project Office. It will
operate under a Project Manager whose sole responsibility
will be the management of ACCESS. The Project Manager
will be the prime interface between Christian Rovsing
A/S and the AFCC Contract Office; internally, he will
have direct access to corporate management. He will
be supported by a Principal Engineering Manager, an
Operations Manager, a Logistics Manager, and a Contracts
Administrator, all reproting directly to him and dedicated
to the project - see FIGURE 8-1. Within supporting
functional departments, ACCESS activities will be assigned
as project entities.
Since the ACCESS program requires heavy technical emphasis,
the Principal Engineer will coordinate all technical
activities and provide close liaison with AFCC designated
technical staff on all technical aspects of the program;
he will direct the systems, hardware, and software
engineering efforts, hold design reviews, and report
on status.
Equipment production and quality control will be planned
and monitored by the Operations Manager. He will be
supported in-house by the Production Manager and his
functional staff.
Site installations, provisioning, doucmentation, training
and field support aspects of ACCEESS will be coordinated
by the Logistics Manager.
FIGURE 8-1
ACCESS PROJECT MANAGEMENT ORGANISATION
showing the direct access channel to corporate management.…86…1 …02… …02… …02… …02…
The Project Office will establish a baseline for work
breakdowns, specifications, schedules and budgets;
it will monitor variances and initiate corrective action.
The management control provided internally and closely
coordinated with AFCC will ensure successful implementation
of ACCESS.
8.1.2 Project Communication
Project communication procedures will be established
to ensure:
o intra-company communication
- to top management
- within the project
o AFCC - Christian Rovsing A/S communication
- management
- technical
o Christian Rovsing A/S - Subcontractor/Supplier
communication
Within the company, the ACCESS Project Manager will
have direct access to top management. As related experience
with other major programs has shown, this communication
channel must be planned and maintained throughout the
project to ensure that schedules are supported by availability
of necessary resources - the resource necessary to
deliver on-time and to specification.
Within the project, the necessary communication channels
will be ensured by the creation of a detailed work
description, starting with the ACCESS Program Management
Work Breakdown Structure - see FIGURE 8-2. The Work
Breakdown Structure is further expanded to identify
detailed work packaes which contain a statement of
work, input (results of other work packages) and output
(dependent work packages), schedule, and budget, thus
defining the multi-
dimensional communication channels, and contents to
be followed in order to achieve each individual milestone
of the Master Program Schedule.
AFCC-Christian Rovsing A/S communication will be implemented
to ensure the operation of both management and technical
channels. Although the program manager will be the
primary point of contact for the AFCC Contract Office,
it is our policy to make top management available to
the customer by identifying the person, a director
of the company, who is responsible for the program.
Likewise, the Engineering Manager will be the primary
point of contact for AFCC desinated technical staff,
and all key technical personnel will be identified
to allow efficient, direct contact.
FIGURE 8-2
ACCESS PROGRAM MANAGEMENT WORK
BREAKDOWN STRUCTURE
provides the basis for project communication
Christian Rovsing A/S - subcontractor communication
will be based on the already proven SUBCONTRACTOR CONTROL
PROCEDURE for managing subcontractors and major vendors.
Each subcontractor will be required to set-up an ACCESS
project organisation and to provide a description of
the organisation including relevant responsibilities
assigned to members of the organisation. This description,
to be included in the contract, will also describe
the interface points between the subcontractor and
the ACCESS organisation.
Details of the SUBCONTRACTOR CONTROL PROCEDURE for
maintaining purchasing and subcontracting schedules
are given in the section on Planning and Control, Section
8.2.
8.1.3 Key Management Description
S̲y̲s̲t̲e̲m̲s̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲r̲. Reporting directly to top
company management, the Manager of the Systems Division
is the ultimate divisional authority, with responsibility
for implementing corporate policy, approving decisions
to bid, and ensuring the resources necessary for successfull
completion of a project. Thus, the decision at Christian
Rovsing A/S to prepare a proposal for ACCESS is effectively
a corporate decision, and the Manager of the Systems
Division will effect the vital link between project
management and top management.
A̲C̲C̲E̲S̲S̲ ̲P̲r̲o̲g̲r̲a̲m̲ ̲M̲a̲n̲a̲g̲e̲r̲. As the executive responsible
for successful execution of the ACCESS project, the
Program Manager has authority over and is responsible
for budget allocation, cost, control, schedule and
timely performance, technical cognizance of design
and development, and control of production, test, integration
and support activities. The Program Manager will report
directly to the Manager of the Systems Division, giving
ready access to corporate officers for prompt resolution
of project issures. He is directly supported by the
Project Office staff and indirectly by the managers
of all operating departments within the Christian Rovsing
A/S organisation.
E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲M̲a̲n̲a̲g̲e̲r̲. This senior engineer, with a complete
understanding of the technical implications of ACCESS
system specifications, will be responsible for the
ultimate technical performance and compliance of
the ACCESS installation. The Engineering Manager, directing
the efforts of System, Hardware and Software Engineering,
provides the correct technical interpretation of all
RFP requirements. He plans, directs, monitors, audits
and controls the design, development, testing, installation
and cutover of ACCESS with regard to all technical
aspects and provides the technical liaison with the
customer, the in-house development and production groups
and with subcontractors and suppliers. This position
will be filled by a senior engineer experienced in
computer design, software, message switching and data
communications.
O̲p̲e̲r̲a̲t̲i̲o̲n̲s̲ ̲M̲a̲n̲a̲g̲e̲r̲. This manager provides the liaison
between the Program Office and the in-house production
activities. Scheduling, cost control, configuration
control, production status, and product assurance are
his major concerns. He is responsible for establishing
and maintaining an up-to-date baseline configuration
and to access the status and quality of ACCESS during
implementation.
L̲o̲g̲i̲s̲t̲i̲c̲s̲ ̲M̲a̲n̲a̲g̲e̲r̲. The installation and site support
tasks will be combined under one manager. The Logistics
Manager will be responsible for site surveys, delivery
and installation, training, maintenance, spares, documentation
and site support.
Product Assurance and Contracts Management are corporate
staff functions carried on for all projects. Intensive
support will be given ACCESS during critical phases
and will continue throughout the implementation phases
of the program.
8.1.4 Training and Experience
A list of personnel envisaged to be assigned key project
positions if Christian Rovsing A/S is awarded the ACCESS
Contract is given below. On the pages to follow, the
training and experience of each project member is detailed.
8.1.4.1 ACCESS KEY PERSONNEL
P̲O̲S̲I̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲A̲M̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Systems Division Manager Gert Jensen
Project Manager Kurt Nybroe-Nielsen
Engineering Manager Flemming Enevoldsen
Systems Engieering Uffe
Holst
Hardware Engineering S]ren
Rasmussen
Software Engineering Jens J]rgen Serup
Operations Manager Bjarne
Berthold
Logistics Manager Ole
Eskedal
Contract Manager Per Weng
It should be noted that in light of the length of contract period
and the changing demands of program phases some change of personnel
can be envisaged. Under all circumstances Christian Rovsing
A/S will strive to provide the optimum staff for successful
project completion.
G̲E̲R̲T̲ ̲J̲E̲N̲S̲E̲N̲ ̲M̲.̲S̲c̲.̲
Employed at Christian Rovsing A/S as Systems Division
Manager.
Education:
1967 Bachelors degree in Electronic Engineering.
1972 Master of Computer Science, University
of Philladelphia, U.S.A.
Experience:
1968-1970 The Brewery Company, Seattle, USA Electro
Dynamic Staff.
1970-1974 Sperry Univac, Blue Bell, PA, USA
Operating Systems Design and Implementation.
1974-1978 Sperry Univac, Copenhagen, Denmark
Manager of Systems Department.
1978-1979 Christian Rovsing A/S
Software Development Manager, Spacelab
Program in Bremen, Germany (25 people)
FIKS Software Development Manager
1980 - Systems Division Manager including direct
responsibility for CAMPS Program Management.
Systems Division size 130 people. Turnover
160 mio. D.Crowns.
Flemming Enevoldsen M.Sc.C.E., M.B.A.
Education:
1972 Master of Science in Civil Engineering
from the Technical University of Denmark.
Specialization in Opertion Research, Statistics
and Mathematical Programming.
1975 Master of Business Administration, MBA
from Copenhagen School of Economics and
Business
Experience:
1973 Military Service at the Danish Defence
Research Establishment
Responsible for War Gaming Systems Development
and Infra-red Missile Simulation.
1973-1981 Systems Engineer for a large Multinational
Shipping Company, EAC.
Responsible for the development of Real
Time Systems for Typical Shipping Applications
(Container Tracking, Agent Monitoring etc.).
1981- Christian Rovsing A/S , System Engineering
Manager with responsibilities within the
Development of Military and Commercial
Message Processing Systems.
Bjarne Berthold M.Sc. EE
Date of Birth: 31 January, 1944
Languages: Danish, English (spoken and
written) (German & French
spoken)
Education: Technical University of Denmark
Experience:
1971-1975 S]ren T. Lyngs] A/S, S]borg. Project Engineer.
Development of Module Systems for Automation
and Remote Control
1975-1977 S]ren T. Lyngs] A/S, S]borg. Project Leader
Designed and managed the Implementation
of Electronic Systems for Automation and
Remote Control.
1977-1980 S]ren T. Lyngs] A/S, S]borg
Department Manager. Head of Development,
Engineering and Installation of Computer-based
Systems for Remote Control and Process
Control
1980 - Formed Christian Rovsing A/S in 1980 and
is currently Engineering Manager in the
Systems Division. At present Hardware
Manager for the CAMPS Project.
Ole Eskedal M.Sc. EE
Education:
1972 University of Santa Clara, California M.Sc.
EE
1964-1965 Teleteknisk Forskningslab., Copenhagen,
Denmark.
Position: Project Engineer.
Developed test equipment for push button
telephones.
1965-1967 General Electric Semiconductor Syracuse,
New York.
Position: Project Engineer.
Developed special purpose test equipment
for Analogue Integrated Circuits.
1967-1969 Raytheon Semiconductor Moutain View, California.
Position: Project Engineer.
Developed production test equipment for
Integrated Circuits.
1969-1974 Hewlett-Packard Cuperino, California.
Position: Project Engineer.
Developed controllers for computer peripherals.
1974-1976 Christian Rovsing A/S, Ballerup, Denmark.
Position: Project Leader.
Designed and managed the development of
Micro Computer Based Data Collection and
Control Systems.
Author of several technical proposals for
commercial and military projects.
1979 - Christian Rovsing A/S, Ballerup, Denmark.
Manager ILS Department of Systems Division.
Kurt Nybroe-Nielsen M.Sc. EE., M.B.A.
Education:
1974 Technical University of Denmark,M.Sc.EE
1977 Copenhagen School of Economics and Business
Administration, M.B.A.
Experience:
Mr. Nybroe-Nielsen joined Christian Rovsing A/S
in 1977 and is currently Deputy Program Manager
for the CAMPS Program (NATO Computer Aided Message
Processing System.)
1982 - Deputy Program Manager for the CAMPS Program
1981-1982 Software Manager for the CAMPS Program
1980--1981 System Engineering Manager for the CAMPS
program.
1978-1979 System Engineer for the SPACELAB Project
at the Project Office at ERNO in Bremen,
West Germany.
1979-1978 Team Leader, responsible for the design,
implementation, and control of a software
project consisting of assembler, linkage
editor, drivers and bootstrap compilers,
written in PASCAL fora the L.M. Ericsson
in Sweden.
1977 Software Engineer with the Christian Rovsing
Electronic Division working with communication
software for the NICS-TARE project.
1976-1977 S]ren T. Lyngs] A/S. Responsible for the
development and implementation of software
for micro and minicomputers used in automatic
control systems for infuctrial processes.
1974-1975 Lieutenant, Military Service with the Danish
Defence Research Laboratories, developing
mini-computer systems for digital signal
processing, including systems engineering
and software development.
Date of Birth: October 30, 1948
Languages: Danish, English & German
Uffe R]nnenkamp Holst M.Sc. EE
Education:
1975 Technical University of Denmark, M.Sc. EE.
Experience:
Mr. R]nnenkamp Holst joined Christian Rovsing A/S
in 1980 and is currently Manager of System Engineering
on the CAMPS Program
1980- Systems Engineer on the CAMPS Program with
responsibility for System Test Planning.
1978-1980 Danish PTT, Radio Communication Service.
Position: Development Enginer.
Development of Microcomputer Systems for
monitoring and control of Microwave Communication
Systems.
1975-1978 Danish PTT, Telephone Communication Service.
Position: Systems Engineer
Implementation of Widebank transmission
systems.
Date of Birth: January, 13th 1943
Languages: Danish, English, German
(spoken and written)
S]ren Rasmussen
Education:
1973 Technical University of Denmark, BSc. EE
Experience:
1973 Soldier, The Danish Defence Research Establishment
1974-1980 S]ren T. Lyngs]
1980 Christian Rovsing A/S
Jens J]rgen Serup B.Sc.,
Education:
1974 Aarhus Katedralskole, 8000 Aarhus C
1974-1975 Mechanical training at Odense Technical
Training School, Odense
Experience:
1975 Practical trainee at Drastrup Radio & TV,
8900 Randers
1976 Practical trainee work at Electromatic
A/S 8370 Hadsten
1976-1980 Candidate at Aarhus Technical Engineering
College, 8000 Aarhus C, Graduated B.Sc.
for Electrical Engineering
1981 Employed by Christian Rovsing A/S on the
Computer Aided Message Processing System
Project, CAMPS.
February 1981 - August 1981
participated in preliminary design of CAMPS
application software.
September 1981- April, 1982
participated in design, coding and testing
of maintenance and diagnostic software
for CR80M disc and floppy disc computer
hardware and firmware.
May 1982 - November 1982
participated in coding and unit test of
CAMPS application software
Per Weng
Education:
1979 University of Copenhagen, Denmark
Experience
Mr. Per Weng joined Christian Rovsing A/S in August
1982 and is currently Contracts Manager with the responsibility
for Legal affairs.
1981-1982 Assitant Manager, Den Danske Banke af 1871,
International Department.
1980-1981 Trainee at the Legal Service for the EEC.
179-1980 Assistant Legal Adivser, A.P. M]ller, Danish
Underground Consortium
Date of Birth: January 14th, 1956
Languages: Danish, English, German,
French
8.2 A̲C̲C̲E̲S̲S̲ ̲ ̲P̲L̲A̲N̲N̲I̲N̲G̲ ̲A̲N̲D̲ ̲C̲O̲N̲T̲R̲O̲L̲
A Project Implementation Plan will be established to
provide a firm baseline for all ACCESS activities against
which STATUS, PROGRESS, and PERFORMANCE can be evaluated
and controlled.
8.2.1 Schedule and Task Planning
P̲r̲o̲j̲e̲c̲t̲ ̲I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲ ̲(̲P̲I̲P̲)̲. The PIP will be
used as a management tool to provide visibility and
control of the ACCESS Program. It describes the schedule,
the performance control system, the detailed Work Breakdown
Structure (WBS), the program administration, the subcontract
administration, the AFCC interfaces, and other key
aspects of the program.
The PIP will have a well-defined structure. Each section
will identify the activity, its organisation and operating
procedures. A work breakdown structure for the activity
will be related to the schedule network consistent
with the master schedule and correlated with the associated
WBS elements of other activities. Documentation produced
by the activity will be listed. Finally, a cross-reference
with contractual items will be made for accountability
of deliverable items and unique requirements.
The various aspects of the PIP are depicted in FIGURE
8-3.
FIGURE 8-3
PROJECT IMPLEMENTATION PLAN
baseline for status evaluation and control
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 basic framework
which will be used for integrating and reconciling
all contractual requirements of ACCESS with the program
implementation plan is the Work Breakdown Structure
(WBS). The WBS will be finalized during the post-award
planning phase and it will then be used to establish
planning baselines.
The major work tasks delineated by the top-level WBS
are:
1.1 Program Management
1.2 ACCESS System Engineering
1.3 Hardware
1.4 Software
1.5 Hardware Fabrication and test
1.6 Site Installation and Support
1.7 Cut-over and Acceptance Test
1.8 Training and Field Support
1.9 Maintenance and Spares
1.10 Documentation
For each of these major tasks a further breakdown will
be generated detailing hardware, software, and service
tasks. Ultimately, these WBS elements will become work
packages for reporting, scheduling and cost control.
Changes to the WBS will be under configuration management
and require Program Office approval. Combined with
the master schedule milestones for engineering, operations
and logisitics, the WBS will become the system-level
plan from which budgets can be allocated.
M̲a̲s̲t̲e̲r̲ ̲S̲c̲h̲e̲d̲u̲l̲e̲. A baseline schedule for ACCESS allows
ample time for planning, definition, and design to
ensure orderly fabrication, installation and cut-over.
The key events which pace ACCESS implementation will
be correlated with the WBS elements, and a preliminary
masterplan will be prepared. This schedule will identify
major milestones for ACCESS design, installation, and
support activities.
Owing to the importance of meeting delivery requirements
the pre-delivery testing schedules for software and
TEMPEST certification are shown below in FIGURE 8-3.
8.2.2 Assessment and Reporting of Project Status
Formal operating procedures and proven management methods
will be used by the Project Office to control the ACCESS
program.
Management procedures define the methods used within
Christian Rovsing A/S for planning, work assignments,
monitoring and coordination of activities within a
project such as ACCESS.
The Project Office and its staff will operate within
these well-established procedures and be responsible
for:
P̲l̲a̲n̲n̲i̲n̲g̲ Evaluation of contract requirements
and allocation of work to the various
functional departments.
W̲o̲r̲k̲ ̲A̲s̲s̲i̲g̲n̲m̲e̲n̲t̲s̲: Issuance of work statements,
specification, budgets and schedules
reflecting ACCESS requirements.
M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲: Periodic review of technical schedule
and cost performance applying program
control through budget authorization.
C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲: Coordination of all project activities
between
operating
departments.
. TEMPEST SCHEDULE
. S/W DEVELOPMENT SCHEDULE
FIGURE 8-4
ACCESS MASTER PROGRAM SCHEDULE
showing approved software testing
and TEMPEST Certification milestones
Internal management procedures have been developed
as a practical cost/schedule control system which produces
valid, auditable and timely performance reports. Variancies
from budget and schedule are quickly identified and
significant deviations are flagged for immediate program
management attention and correction action.
Technical supervision and monitoring is effected through
periodic design reviews with hardware and software
development engineering managers.
The primary management controls for ACCESS will be
based on a well-planned WBS, master schedule and budget.
Firm baselines established early in the program will
provide the basis for managing the program. The operating
prodedures for assessing and reproting ACCESS status
are highlighted in FIGURE 8-5.
The WBS consists of a family tree of hardware, software,
services and work tasks organized to define and relationally
display the work to be accomplished for a successful
implementation of ACCESS. As a planning tool, it defines
the work packages for planning, scheduling and cost
control. Negotiated and approved program changes will
be reflected in the baseline WBS.
The master schedule incorporates customer-directed
milestones and indicates the timing relationships of
the WBS elements. Detailed plans are derived from the
master schedule to establish work package milestones.
The budget baseline allocates the resources among operating
departments following contract award. Work authorizations
are time-phased based on schedule constraints. Internal
budget allocations allow for the retainment of funds
for contigencies and unforeseen efforts.
All detailed packages, identified and assigned from
the WBS, will be defined by a statement of work, schedule
and budget, thus establishing a performance measurement
baseline.
FIGURE 8-5
WBS/MASTER SCHEDULE/BUDGET BASELINE
provide the framework for status
assessment and reporting
8.2.3 Subcontractor Management
The ACCESS program will use the SUBCONTRACTOR CONTROL
PROCEDURE for managing subcontractors and major vendors;
this procedure has been proven to be an effective aid
to ensure maintaining schedules.
A subcontractor is defined as an organization outside
the corporation performing work in connection with
the project. The scope of the effort must be such that
a legal contract can be established between Christian
Rovsing A/S and the subcontractor prior to commencement
of work.
A̲C̲C̲E̲S̲S̲ ̲P̲R̲O̲J̲E̲C̲T̲ ̲O̲F̲F̲I̲C̲E̲ is ultimately responsible for
the performance of a subcontractor.
Before the contract is signed the subcontractor must
be given statements of work and schedules for the task
in question. During contract negotiations the project
office will assist the contracts department to ensure
that the technical aspects are understood by the subcontractor.
Furthermore, the project office must ensure that all
relevant elements of
o performance schedule
o technical requirements
o management control requirements
o payment principles
are included in the subcontract.
The following is a description of the major requirements
imposed on a subcontractor by the Project Office:
P̲l̲a̲n̲n̲i̲n̲g̲ ̲a̲n̲d̲ ̲S̲c̲h̲e̲d̲u̲l̲i̲n̲g̲. The subcontractor is required
to utilize a planning system which enables the prime
contractor to have full visibility of the subcontractor's
performance.
S̲u̲b̲c̲o̲n̲t̲r̲a̲c̲t̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲. The Subcontractor will, at
regular intervals, submit progress reports to the project
office. In addition, requests for payment must be submitted
according to principles stated in the contract.
R̲e̲v̲i̲e̲w̲s̲. Project reviews will take place on a scheduled
basis. The Project Office will hold reviews with the
subcontractor in order to access interpretation of
the requirements, progress against schedule and cost
and to achieve early identification of potential problem
areas. The subcontractor will present material in such
depth as to give full visibility of the review period
and current status.
S̲u̲b̲c̲o̲n̲t̲r̲a̲c̲t̲o̲r̲'̲s̲ ̲O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲.Subcontractor is requested
to set-up an ACCESS project organisation. The subcontractor
must provide, to be included in the contract, a description
of the organisation, including relevant responsibilities
assigned to memebers of the organisation. This description
will also describe interface points between the subcontractor
and the ACCESS organisation.
P̲u̲r̲c̲h̲a̲s̲i̲n̲g̲ ̲D̲e̲p̲a̲r̲t̲m̲e̲n̲t̲ is the official channel for release
of work packages and funds to the subcontractor. This
is usually done by an invoice referencing the contract.
C̲o̲n̲t̲r̲a̲c̲t̲s̲ ̲D̲e̲p̲a̲r̲t̲m̲e̲n̲t̲ has the responsibility for the
generation and negotiation of the subcontract.
P̲r̲o̲d̲u̲c̲t̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲D̲e̲p̲a̲r̲t̲m̲e̲n̲t̲ must ensure that applicable
quality control requirements are imposed on subcontractor
by incorporation in the contract. When work is being
performed the department is responsible for ensuring
that the requirements are being following.
8.2.4 Quality Assurance (QA)
The Quality Assurance Manager (QAM), a member of the
corporate staff, reports directly to corporate management
and is responsible for controlling product quality
to specification according to milestones established
in the project master schedule.
The document "Quality Assurance Policy" (CR/QAP/001)
defines the Quality Assurance Policy at Christian Rovsing
A/S . This document is included with the Technical
literature in SUBPART A - Ref. Q.1.
8.2.4.1 QA Areas of Responsibility
Particular QAM areas of responsibility are:
P̲a̲r̲t̲s̲ ̲a̲n̲d̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲ ̲(̲P̲&̲M̲)̲
P&M covers procurement control, vendor evaluation and
qualification, as well as receiving inspection and
purchasing.
R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲
This is a supervision function provided for all projects.
Reliability analysis, trade-off's, and tests are performed
by the project team under the supervision and control
of QA.
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 division and special QA procedures
for dedicated projects, and the establishment and control
of QA 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
- End-item acceptance test
- Shop procedures
- Control of special procedures
- Methology and calibration relating to test
instrument and tools
- Electrical and environmental tests
- Entrance control and cleanliness control of
restricted clean room areas
- Control of packing and shipping
- Trend reporting
- Quality audits.
8.2.4.2 QA System
A QA System has been developed to ensure on-schedule
delivery of products according to specified quality
requirements.
This standard QA system comprises a series of functions
of which the most important are:
o Q̲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 as design reviews, factory test,
acceptance test, etc.
o 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 Reviews
are scheduled and performed and no design is released
for production/programming without proper approval.
o 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. The Change
Control is managed by a board with participation
of a customer representative, if required/desired.
o 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.
o I̲n̲s̲p̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲
Detailed procedures are established for Inspection
and Test to be performed during development, production
and upon completion of the contract (acceptance
test).
o R̲e̲c̲o̲r̲d̲s̲
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.
8.3 A̲C̲C̲E̲S̲S̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲
Through experience gained on major programs such as
the F-16 Fire Control Computer, NICS-TARE, and CAMPS,
Christian Rovsing A/S has developed configuration management
procedures for handling documentation development,
hardware change, and software change, thus ensuring
on-time delivery to specification.
8.3.1 Configuration Control Items
A. Specifications and procedures.
The following documents dealing with hardware or
software belong to this category:
o Product Specifications
o Test Specifications
o Test Procedures
Maintenance of above documents will be accomplished
by Engineering Change Orders (ECO). A specification
once approved by the customer may only be changed
with the customer's approval.
B. Engineering Drawings
Engineering Drawings and other primary documentation
once released by the engineering department shall
be changed only by direction of an authorized ECO.
C. Change Documentations.
Change documentation under configuration control:
o Engineering Change Proposal (ECP)
o Engineering Change Order (ECO)
o Stop/Recind Orders
o Request for Deviation/Waiver
D. Hardware and Software Items
All hardware and software items controlled by the
documentation described in the previous paragraphs
will be under configuration control.
8.3.2 Configuration Identification
All items released as part of the baseline configuration
as well as subsequent change documentation to these
items shall be 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
8.3.3 Configuration Control
Configuration control can be divided into three major
tasks:
o Change analysis
o Change classification
o Change approval
Configuration Control of Project Office initiated changes
is ensured by a Configuration Control Board (CCB) which
includes project relevant experts and which is chaired
by the configuration management staff member responsible
to the project. The CCB is responsible for analysis,
classification and approval of changes to:
- specifications and procedures
- engineering drawings
- hardware and software
- documentation
C̲h̲a̲n̲g̲e̲ ̲a̲n̲a̲l̲y̲s̲i̲s̲
The objective of the change analysis is to ensure that
impact of the proposed change is thoroughly analysed
by all departments concerned. Alternative solutions
may also be proposed and will then undergo eveluation.
C̲h̲a̲n̲g̲e̲ ̲c̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
As a result of the analysis the change will be classified
in accordance with MIL-STD-480 as a Class I change
or a Class II change.
Class I changes which involve form, fit, and functions
must be approved by the customer if the change has
influence on the product specifications.
Class II changes will be incorporated in Baseline documentation
without customers approval.
N̲o̲n̲-̲c̲o̲n̲f̲o̲r̲m̲a̲n̲c̲e̲ ̲h̲a̲n̲d̲l̲i̲n̲g̲ ̲
Non-comforming material could result in waivers or
deviations. It is the responsibility of configuration
management to ensure that the applicable documentation
form is correctly filled in. The configuration control
function will be represented at the Material Review
Board Meetings where such non-conformance is being
discussed.
8.3.4 Configuration Status Accounting and Audits
The configuration status accounting function will record
and maintain the information and documentation required
by configuration control management. It includes listings
of approved engineering documentation status reports,
of proposed changes, and implementation status of approved
changes.
The Physical Configuration Audit (PCA) will be the
formal examination of the as-built version of a configuration
item against its technical documentation in order to
establish the Configuration Item's product baseline.
If stated so in the contract the PCA will be conducted
by the configuration management function with participation
of the customer's representative.
8.4 C̲O̲M̲P̲A̲N̲Y̲ ̲R̲E̲S̲O̲U̲R̲C̲E̲S̲:̲ ̲R̲E̲L̲E̲V̲A̲N̲T̲ ̲E̲X̲P̲E̲R̲I̲E̲N̲C̲E̲,̲ ̲F̲A̲C̲I̲L̲I̲T̲I̲E̲S̲,̲
̲A̲N̲D̲ ̲F̲I̲N̲A̲N̲C̲I̲A̲L̲ ̲S̲T̲A̲T̲U̲S̲ ̲
In this section focus will be on the experience and
the performance record of Christian Rovsing A/S gained
in successfully meeting the requirements of projects
comparable to ACCESS. Additionally the plant facilities
and equipment will be discribed, showing that they
are adequate to accomplish the tasks inherent in delivering
ACCESS. Finally the financial status of Christian Rovsing
A/S will be highlighted, demonstrating that the ability
to finance ACCESS is adequate.
8.4.1 Relevant Experience
Christian Rovsing has considerable experience in the
field of data communication, reliable and flexible
computer systems, and management of significant computer
system projects. These skills and know-how have been
developed over many years, and during the last 6 years
we have carried out extensive programs in the field
of data communication.
We believe that we have available exceptional professional
talent dedicated to advanced computerized information
techniques. Furthermore, the company excels in applying
current technology to modular equipment design. We
have no outdated product lines to support; our hardware
is second-generation LSI technology.
Systems are configured around the company's CR80 Computer
which has proven itself particularly well suited to
communication disciplines. The following is a list
of those communication disciplines in which the company
has gained significant expertise:
o Packet Switching
- Routing Algorithm
- X25
- X21, X21 bis Interfaces
- X75
o Message Switching
- Preparation and Distribution
- Format Conversion (ACP127/128)
- Protocols (LITSYNC, CCITT X.25)
- Storage and Retrieval
o Line Switching
- Signalling and Supervision
- Routing Algorithms
- Synchronization and Timing
- Multiplexing and Trunking
o Dualized Systems
- Configuration Control
- Switchover and Recovery
- Reliability Performance
- V24/V28 Interfaces
o Security
- Access Control
- SPECAT Handling
- Red/Black Interfaces
- Crypto Interface (DOLCE)
- Privileged User State
- Tempest
System contracts awarded to the company on a Prime
Contractor or Principal Sub-contractor basis are typically
worth several millions of US Dollars. Administratively
distinct Project Offices are formed within the company
to manage these large programs.
A summary of the company's overall experience in data
communication is presented in FIGURE 8-6.
DATA COMMUNICATION EXPERIENCE
FIGURE 5.3-1
Successful participation in these programmes as prime
or sub-contractor has broadened the company's resources.
The high degree of reliability, security, efficiency
and operational performance which these projects demand
is met by applying up-to-date technology, specialized
engineering expertise, and sophisticated data communications
techniques.
Christian Rovsing was principal sub-contractor to Litton
Data Systems Inc. for the NICS-TARE programme and is
Prime Contractor for the FIKS, CAMPS and LME-NET programmes.
The FIKS network will be installed at the customer's
8 sites in the course of 1982 under the direction of
the Integrated Logistics Support Department of the
System Division.
The CAMPS program with a contract value of $ 30 Million,
before options, is the largest, single computer systems
contract ever to be awarded to a Danish electronics
company. The system is based on the latest version
of the company's CR80 Computer product line. The CAMPS
project team has successfully completed the design
phases and is moving into the implementation phase.
The installation phase will involve 16 separate sites
located throughout Europe. The CAMPS program involves
the fulfillment of strict TEMPEST requirements.
The LME-NET program is to be delivered in several phases.
Phase 1 provides a network center with interfaces
to IBM and UNIVAC mainframe computers and 10 switching
nodes forming a network covering Europe. This phase
will be completed in June 1982. The network will follow
international standards for packet switching data networks,
as defined by CCITT in recommendation X.25. Later
phases will provide facilities like multiple network
control centers, satellite links to remote nodes, interfacing
to other makes of mainframe computers and support of
facsimile and voice transmission.
The ADA Compiler Development Project is part of a larger
project which addresses the construction of an entire
programming environment including an ADA computer.
The programming environment will conform to the Stoneman
specifications from the U.S. Department of
Defence. The total environment system is financed by
the Commission of the European Communities with a grant
of US $ 3.2 million , which corresponds to 50% of the
total development costs. The remaining development
costs are covered by the participating companies and
various public sources and funds.
In the HAWK project Christian Rovsing has developed
and now produces converters which makes it possible
to communicate between the HAWK BATTERIES by means
of an extended message structure, while providing unchanged
communication with the Battery Operation Control.
This provides a cost effective improvement to HAWK
communication
The CR-Videotex system is a commercial information
retrieval and display system which provides simple
and efficient instant access to a wealth of information
and services. Using low cost terminals based on TV
Technology, it can use either the public telephone
network or a private telephone system. Data can be
contained either in a control data base located on
a single computer or a network of geographically distributed
computers, each containing the local information of
interest.
To Air Canada Christian Rovsing A/S will deliver a
new nation-wide communications system. This contract,
just recently signed, has an initial value of approximately
15 million dollars.
Much of the extensive management and technical experience
which Christian Rovsing has acquired in message switching
and data communication projects are directly applicable
to the ACCESS project.
The company's overall exposure to major computer system
discipline reflects its ability to carry out a technically
demanding project.
8.4.1.1 D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲ ̲O̲F̲ ̲M̲A̲J̲O̲R̲ ̲C̲O̲N̲T̲R̲A̲C̲T̲S̲
Eight major contracts are described below:
a) NICS-TARE for Litton Data Systems
b) FIKS for the Danish Ministry of Defence
c) CAMPS for NATO-SHAPE
d) LME-NET for L.M. Ericsson in Sweden
e) HAWK for NATO-HAWK
f) ADA Compiler for EEC
g) Protocol Converter for NATO-SHAPE
h) VIDEOTEX
i) Air Canada Data Network (ACDN)
j) Communication at Hill AFB/Edwards AFB
Each of these projects uses the CR80 computer, designed
and manufactured by Christian Rovsing A/S
To provide further information about the capabilities
of Christian Rovsing A/S as seen by our customers,
contact with the respective company or organisation
is invited.
a) N̲I̲C̲S̲-̲T̲A̲R̲E̲
Description: Communications Front-end Processors
for Message Switching Network
Customer: NATO Integrated Communications System
Management Agency, Brussels,Belgium
Prime Con- Litton Data Systems Inc.
tractor: Van Nuys,California.
CRA Sub-
contract
value: Approx. $6 Million
Program
Duration 36 months (1976-1979)
A rigorous and competitive evaluation of various front-end
communication processors was conducted by Litton's
Data Systems Division to satisfy NICSMA's stringent
operational and realiability requirements for TARE.
A CR80-based configuration was chosen based on the
criteria of traffic handling, expandability, reliability,
and cost.
The dualized configuration consists of two "CR COMPROCESSORS",
two groups of line termination units, and dual data-channel
interfaces to the TARE Message Processors. The modularity
and distributed processing aspects are apparent in
the use of repetitive functional units around a multi-level
data transfer bus structure (see FIGURE 8-7).
Christian Rovsing has developed a customized configuration
to NICSMA specifications and produced 20 dual-processors
and associated line termination sub-systems each of
them capable of up to 163 line connections. Several
prototype systems have been delivered and successfully
tested.
In addition to supplying the complete front-end configuration,
Christian Rovsing also assumed responsibility for the
definition, system design, and implementation of the
NICS-TARE line coordination protocols, buffering and
other communication preprocessing functions.
Our U.S. subsidiary, Christian Rovsing Corp., assumed
a major coordination role in supporting Litton NICS-TARE
effort.
A brief description of the TARE COMPROCESSOR subsystem
and its major functional role now follows.
The TARE Communication Processor Subsystem is a fully-redundant
front-end serving as concentrator and pre-processor
for a maximum of 163 lines. It interfaces the network
to the Litton L3050 Message Processors. A line-splitter
assembly routes the lines to two CP's. Both synchronous
(2400 baud) and asynchronous (600 baud) channels are
accomodated. Synchronous lines are controlled through
an EDC protocol (LITSYNC).
Message pre-processing is performed by a Multiplexer
Processor and a Communications Processors; both are
duplicated in the redundant configuration. The Multiplexer
performs the line polling. The Comprocessor does the
message processing and manages the interface to the
Message Processor. Message processing functions include
character sequence recognition, alphabet translation,
channel, error recognition and EDC protocol management,
security checking, and message sector assembly and
distribution.
The CR80 Communication Processor is a distributed minicomputer
system specifically designed as a communications line
concentrator and pre-processor. Of recent design and
employing a modular architecture, it provides TARE
with a flexible front-end for individual line terminations,
multiplexing and character-orientated data processing.
Communication line characteristics such as speed, synchronisation,
distortion, timeout, bit sampling, character and block
assembly are completely divorced from the L3050 Message
Processors.
Extensive use of LSI contributes to the versatility
of the microprocessor controlled line termination units.
These form an integral part of the front-end system
and provide an interface to a variety of line types
for the interchange of data, control, and timing signals.
The impact of LSI on weight, size and power is clearly
demonstrated by the compact hardware packaging. (See
FIGURE 8-8).
Of particular significance is the cost reduction realisable
by LSI. By way of illustration, note that it was economically
feasible to duplicate entire line termination units
to route traffic to both the active and hot stand-by
processors, thus allowing on-line switchover without
loss of data.
NICS-TARE H/W CONFIGURATION
SHOWING MODULARITY AND DISTRIBUTED PROCESSING
FIGURE 8-7
NICS-TARE H/W PACKAGING
FIGURE 8-8
b) F̲I̲K̲S̲ ̲D̲e̲f̲e̲n̲c̲e̲ ̲I̲n̲t̲e̲g̲r̲a̲t̲e̲d̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲S̲y̲s̲t̲e̲m̲
Description: Defence Integrated Communications
System
Customer: Danish Ministry of Defence
Prime Con- Christian Rovsing
tractor:
Contract
Value: Approx. $ 7 Million
Program
Duration: 48 months (1976-1979)
FIKS is Denmark's tri-service defense communications
network. Its objective is to integrate, automate and
upgrade teletype command networks and data communications
systems previously operated by the army, navy, and
the air force.
Christian Rovsing and the Danish Air Material Command
jointly developed the top-level system specification,
and a contract was awarded early in 1978. The specification
covers design, development, installation and cut-over
of a common nodal network for message and data traffic.
When completed, FIKS will provide higher survivability,
improved security, greater efficiency, simpler operation
and easier expansion through computerization.
FIKS integrates and fully automates message switching
and data transfer functions. It consists of a multi-node
network geographically distributed throughout Denmark.
As initially structured, 8 nodes are arranged in a
grid configuration and interconnected via 15 full-duplex
trunks operating at 9.6 kilobaud per line.
Message and data traffic under control of computerized
nodal switching centers are interchanged between military
users . Message users at remote terminals are served
through COMCENTERs, some of which are co-located at
the nodes.
Message traffic rates range from low-speed (50 baud)
to medium-speed (2400 baud). FIKS is sized to handle
a throughput of 25,000 messages per busy hour including
messages entering the network, multiple distribution
of messages, retrievals, service messages and a 25%
allowance for growth.
Data users, continuously or not, exchange information
through the FIKS network. Typical data users are military
data systems which relate to air defense, air traffic
control, intelligence and command nets such as LINK-1,
LOW-LEVEL RADAR, TVT EXTRACTORS, ACBA-CCIS, TOSCA,
FLY-PEP, CHODDEN, and INTEL.
The FIKS network interfaces to NICS-TARE through compatible
circuits and protocols. Also, access to the Nordic
Public Data Network, NPDN, is provided using CCITT
X.21 for circuit-switched calls and conversion to X.25
for virtual calls; this interface is consistent with
expansion to higher level X.25 packet switching.
To accomodate the navy's unique requirements, ship-to-shore
secure communications channels are provided through
the appropriate ground-based comcenters.
The generic elements of the Nodal Switching Center,
one of several in the FIKS network, are depicted in
FIGURE 8-9. Though physically separate, the Nodal Switch
is shown co-located with the System Control Center
and the Message Entry and Distribution Equipment.
An abbreviated list of functions performed by the system
includes:
- Message Preparation and Distribution
- Simplified and ACP127 Format Handling
- Message Storage and Retrieval
- Network Supervision and Control
- Automatic Switchover and Recovery
- Alternate Routing
- Traffic and Operational Security.
A FIKS site under factory integration and test is shown
in FIGURE 8-10.
FIKS GENERIC ELEMENTS
FIGURE 8-9
FIKS SITE UNDER FACTORY TEST
FIGURE 8-10
c) C̲A̲M̲P̲S̲
Description: Computer-aided Message Processing
System
Customer NATO-SHAPE, Brussels, Belgium
Prime
Contractor Christian Rovsing
Contract
Value: Approx. $ 30 Million
Program
Duration: 46 months (1980-1983)
Christian Rovsing has contracted with NATO (SHAPE)
to deliver CAMPS, the Computer Aided Message Processing
System, on a turn-key basis to a number of NATO sites
.
CAMPS has two essential functions:
1. CAMPS assists the user in message handling, i.e.
preparation, dispatch and receival of messages.
2. CAMPS communicates with data networks, and other
systems such as SCARS II (Strategic Command and
Alert Reporting System) and ACE CCIS (Command Control
Information System).
There are, naturally, high demands for reliability
and security in a system like CAMPS, and these
demands are met by the hardware and software as
an entity.
The hardware system is based upon the company's
CR80 computer. In designing this computer, advanced,
proven technology has been employed. Reliability
is further secured by using MIL quality components
and by subjecting all electronic modules to a burn-in
cycle, (See FIGURE 8-11).
CAMPS SIMPLIFIED H/W-SYSTEM CONFIGURATION
FIGURE 8-11
The CAMPS software consists of system programs
and application programs. The software engineering
profits from the experience the company has obtained
through the participation in other complex message
processing and communication systems.
CAMPS will exchange data with other computer- associated
handling and communication systems. Interface systems,
which exist or are being developed, include NATO-TARE
and Tape Relay Centers plus SCARS II and ACE CCIS.
The interface design is structured to permit the
accomodation of new systems as they are introduced.
The primary format for messages will conform to
ACP-127 NATO SUPP-3 for all interfaces.
CCIS and SCARS II will utilise the X-25 data communication
protocol (CCITT) when interfacing with CAMPS.
To interconnect CAMPS with older CCIS equipment,
Christian Rovsing has offered to implement protocol
converters.
Extensive use of up-to-date technology is required
to meet the stringent requirements set forth by
SHAPE. The hardware configuration features distributed,
autonomous processing-subsystems made economically
feasible by LSI (RAM's, PROM's, CPU's, USART's,
FIFO's, ALU's, etc.). The dualised configuration
is partitioned into three Processors per Processing
Unit: Main Memories, Terminal Data Exchanges, and
pre-processor-controlled Line Termination Units.
CAMPS also uses up-to-date technology like optical
fiber-optic communication to connect terminals
to the computer.
CAMPS is characterised quantitively by:(a) a connectivity
of 256 full-duplex lines or an equivalent 153,
600 bytes/second (b) a 240-megabyte mass storage
with 40-msec access, providing immediate retrieval
of 24-hour traffic (c) a peak processing throughput
of 30,000 messages/hour (d) a cross-office processing
time of 400 msec (e) a system response time of
less than 3 seconds (f) a predicted systems availability
of 0.999996.
CAMPS functional requirements deal with message
handling, message preparation, coordination, and
release, message distribution, format translation,
storage and retrieval, supervision control, statistics
and reports, protocols, and recovery and back-up-techniques.
Three aspects of CAMPS are depicted by the simplified
software description shown in FIGURE 8-12.
Of particular significance are: (1) the cost, weight,
and size reduction achieved by CAMPS-the 6 rack,
12 KW Hardware represents a drastic reduction compared
to similar equipment (2) the unique security features
to prevent unauthorized access such as privileged
instructions, memory bounds, and separate SYSTEM
USER states.
A typical CAMPS installation consists of the following
elements(see FIGURE 8-13).
- Processors and Mass Storage (3-bay Rack)
- Line Interface Equipment (4-bay Rack)
- Supervisory Console
- Software Maintenance Equipment
- Spares/Tools Cabinet.
The above equipment complement, which does not
include the terminal option for remote locations,
will be installed in a secure area dedicated CAMPS.
The computer crates are installed in TEMPTEST proved
EMI-racks for COMSEC approval of the system.
CAMPS S/W SYSTEM CONFIGURATION - OVERVIEW
FIGURE 8-12
CAMPS TYPICAL SITE LAY-OUT
FIGURE 8-13
d) L̲M̲E̲-̲N̲E̲T̲
Customer: L.M. Ericsson, Stockholm, Sweden
Prime Con-
tractor: Christian Rovsing
Contract
Value: Approx. $ 4.5 Million
Program
Duration: 48 months (1979-1983)
The L.M.Ericsson Data Network is being developed as
a private data communication network to cover the need
within the organization with regard to data communication
between data centres and terminal users.
LME-NET is based on the CR80 computer and the first
phase consists of (see FIGURE 8-14)
o a network center
o a host interface processor system for connection
of IBM and UNIVAC computers
o 10 switching nodes where traffic is collected and
directed to the receiver
o a number of leased lines between the nodes, eight
of which are in Sweden, one in Copenhagen and one
in Madrid.
In the later phases, the network will be enlarged with:
o additional network control centers, which will
enable certain distributed control parts of the
network
o additional geographically distributed host interface
processors, perhaps with interfaces to the other
machine types, e.g. ICL
o connection via satellite to new nodes, e.g. in
Brazil.
o The LME-NET architecture is based on the following
concept:
1. A general standardized transport facility is provided.
The network will follow international standards
for packet switch data networks, as defined by
CCITT in the recommendation X.25. This will enable
a later connection to public networks and ensure
the adaptation of LMENET to future standards.
2. Existing makes of computers and terminals can be
connected to the general network by means of mechanisms
in the network which do not require modifications
of the existing system.
The above concept will enable a layered construction
of LMENET following recognized principles of system
construction in general, and network construction in
particular (ISO's seven-layer model for network: Open
Systems Interconnection Reference Model).
LMENET provides the following functions:
o complete monitoring and control of the network
independent of host computers connected
o emulation of a network, complying with IBM's Systems
Network Architecture (SNA), in order to establish
communication between the IBM user programs and
the SNA terminals as well as certain non-SNA terminals.
o emulation of network complying with UNIVAC's Distributed
Communication Architecture (DCA) which enables
communication between UNIVAC user programs and
terminals
o direct program to program communication
o various traffic types with different resource requirements
- dialog traffic
- batch traffic
- transparent traffic
The first phase of the LMENET will be in operation
from July, 1982, with six connected host computers
and approx. 2000 terminals.
LME-NET PHASE 1 CONFIGURATION
FIGURE 8-14
e) H̲A̲W̲K̲ ̲A̲T̲D̲L̲/̲M̲B̲D̲L̲ ̲C̲o̲n̲v̲e̲r̲t̲e̲r̲
Customer: NATO HAWK Production and Logistic
Office
Prime Con-
tractor: Christian Rovsing
1. D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲C̲o̲n̲t̲r̲a̲c̲t̲
Contract
Value: Approx. $ 1.2 Million
Program
Duration: April 1979 - Oct. 1981.
2. P̲r̲o̲d̲u̲c̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲a̲c̲t̲
Contract
Value: Approx. $ 6 Million
Program
Duration: Nov. 81 - Aug. 84.
I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The ATDL/MBDL Converter (AMC) constitutes the means
by which PIP modified IHAWK batteries, communicating
in ATDL-1, and Battery Operation Control (BOC), communicating
in MBDL, are able to exchange information.
The Missile Battery Data Link (MBDL) was the message
format used for communication between BOC and HAWK
batteries in the earlier design. The PIP modification
of the IHAWK batteries introduced a new message format
ATDL-1, which is much more powerfull than the MBDL.
The AMC is a CR80 computer that in most applications
will be located inside the BOC shelter. In such configurations
only the ATDL communication lines using the connectors
normally used for the MBDL communication are visible
from outside the BOC shelter
I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Up to 8 PIP modified IHAWK batteries can be connected
to the AMC via ATDL links. Similarly the AMC is connected
to the 8 MBDL battery links of the BOC.
In FIGURE 8-15 a schematic of the interconnection to
BOC and Batteries is shown.
The AMC will receive commands and reference track messages
from the BOC in MBDL format. The commands will be transmitted
to the relevant IHAWK battery in ATDL format.
The ATDL status messages received from the batteries
will be converted to MBDL and transmitted to the BOC
for presentation on the display.
As the ATDL message format enables an extensive exchange
of track-information, a track file is established in
the AMC to support the forwarding of this information
to all other batteries.
The software block diagram for the AMC is shown in
FIGURE 8-16.
E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
As the AMC is installed in a shelter which is transported
from site to site between operations, the CR80 modules
have been environmentally tested to demonstrate that
the equipment is capable of survive these conditions.
AMC INTERCONNECTION SCHEMATIC
FIGURE 8-15
AMC FUNCTIONAL BLOCK DIAGRAM
FIGURE 8-16
f) A̲D̲A̲ ̲C̲o̲m̲p̲i̲l̲e̲r
Customer: European Economic Community
Contract
value: Approx. $ 3.2 Million
Program
Duration: 36 month (1981-1984)
The aim of the ADA Compiler Development Project is
to develop an easily portable compiler for the full
Ada language as standardized by the U.S. Department
of Defense.
The compiler development will be accomplished using
state of the art formal derivation and verification
techniques to ensure maximum correctness and reliability
of the resulting compiler system.
The compiler system will be tailored for mini/micro
computer system applications. Particular attention
will be given to the problems caused by the limited
address and/or physical memory space in such systems.
The total system project encompasses the following
subprojects:
1) Specification and implementation of a standard
interface to the operating system and file system
of the host computer. The standard interface will
conform to the Stoneman KAPSE requirements and
will be specified as an ADA package. Particular
attention will be paid to the design of the KAPSE
database.
2) Minimum Toolset for ADA Program Development, conforming
to the Stoneman MAPSE requirements. The toolset
contains the following program development items:
- Text Editor
- ADA Compiler (see subproject (4))
- Linker
- Debugger
- Database Utility
- Command Interpreter
- Object Formatters (including Pretty Printer)
- Library File Utilities.
3) Distributed System Study addressing the impacts
on the total system (KAPSE/MAPSE) caused by a distributed
system architecture.
4) Ada Compiler, consisting of:
- Front End Compiler which converts ADA source
code into an intermediate language.
- Separate Compilation Handler
- Back End Compiler which generates A-code from
the intermediate language.
The front end compiler produced in this project
will be a test version primarily intended for generation
of test input to the back end compiler and test
of the compiler interfaces to KAPSE/MAPSE. The
project also includes adaption and integration
of an optimizing front end compiler produced by
a French/German consortium (Alsys/Cii Honeywell
Bull/Siemens).
An important aspect of the compiler development
project is the propagation of the formal and systematic
software engineering methods used to produce the
ADA compiler.
5) Run Time System including virtual machine:
- Design of portable run time system (A-code
machine, tasking kernel, i/o system).
- Implementation of run time system on the Christian
Rovsing CR80 and on the Olivetti S6000 computers.
Subprojects 1, 2 and 3 are being carried out by the
Italian partner with Systems Designers Limited (England)
as subcontractor, while subprojects 4 and 5 are being
carried out by the Danish partners.
The complete system will be implemented on the Olivetti
S6000 computer, which is a 16-bit minicomputer with
virtual memory, and on the Christian Rovsing A/S CR80
computer, which is a 16-bit minicomputer with multiprocessor
capabilities, a 32M byte memory space, a 128K byte
program addressing space and a 128K byte data space.
The total system is financed by the Commission of the
European Communities with a grant of 21 million Danish
Kroner (approximately 2.7 million European Units of
Account, or US $ 3.2. million ), which corresponds
to 50% of the total development costs. The remaining
development costs are covered by the participating
companies and various public sources and funds.
The total system project requires approximately 1000
man months and will be completed in 1983.
At present Christian Rovsing has implemented a subset
of the ADA Compiler on our CR80 computer, which translates
ADA code to the system programming language SWELL.
g) P̲R̲O̲T̲O̲C̲O̲L̲ ̲C̲O̲N̲V̲E̲R̲T̲E̲R̲
Description: CAMPS and SCARS II interface
adaptors to CCIS/Honeywell 6060
Customer: NATO-SHAPE, Belgium
Prime Contractor: Christian Rovsing A/S
Contract Value: Approx. US $ 1 million
Programme Duration: mid 1982 to mid 1984
SHAPE has approved a concept for the improvement
of command and control through the use of ADP.
This concept includes a requirement for the interlinking
of host computers supporting an ACE-wide data
base which is updated from information primarily
contained in original messages of the ACE reporting
system. The interlinkig of CAMPS, SCARS and ACE-CCIS
systems is a major step towards the realisation
of this concept (see FIGURE 8-17). Christian Rovsing
will provide interface adapters to achieve CAMPS
- SCARS II - CCIS System interoperability.
PROTOCOL CONVERTER/CAMPS Hardware Commonality
will enable SHAPE to intergrate CAMPS, SCARS II
and CCIS in a minimum of time, at a lower cost
and with a proven level of availability.
The CAMPS (Computer Aided Message Processing System)
will be istalled at SHAPE and in the Central Region
(CR) starting in January 1983. In Jan 1983, testing
will begin and continue until June 1983. Likewise,
SCARS II (Status Control Alerting and Reporting
System) will be installed at SHAPE starting in
June 1983. CAMPS and SCARS II are required to
interface with the Honeywell 6060 to permit an
automated message flow between the networks supporting
the systems. Final system acceptance is planned
for mid 1984.
FIGURE 8-17
PROTOCOL CONVERTER
showing CAMPS, SCARS, and CCIS Interoperability
h) V̲I̲D̲E̲O̲T̲E̲X̲
Description : Information retrieval and display
system
Customer: Danish Tele-administration
Prime Contractor: Christian Rovsing A/S
Contract Value:
Program Duration: end 1980 - end 1981 (VIDEOTEX
is available as a CR commercial
product)
I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
VIDEOTEX is the name given to a low cost, easy to use,
two way information service for homes, offices, libraries,
schools, railway terminals, etc. The main objective
of VIDEOTEX is to provide subscribers with information
- text and graphics - at an ordinary TV console.
Information provided to subscribers comes from a VIDEOTEX
Computer Center (VCC) data base maintained by participaing
suppliers of information. Information can be updated
in several ways:
o on-line immediate edit - supplier determines when
to update
o on-line bulk edit - supplier can transmit new data
to VCC at any time; VCC updates at scheduled times
o off-line magnetic tape transfer - VCC updates at
scheduled times
o direct connection through VCC between subscribers
and suppliers.
A subscriber establishes a two-way information session
via common carrier switched lines by dialing VCC. If
an input port is available, VCC accepts the call request
and gives access rights. If a call request cannot be
accepted, the subscribed receives a busy tone - as
with normal telephone usage.
A subscriber can access information and can also transmit
a message to other subscribers or suppliers of information.
Finally, interactive services between a subscriber
and the VCC can be provided.
A detailed technical discription is found in the Technical
Literature, Ref. V.1.
S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The principal functions offered by VIDEOTEX are:
o Information Retrieval
o Message Service
o On-line Applications
o Transaction Service
o Closed User Groups
o On-line Editing
V̲I̲D̲E̲O̲ ̲D̲a̲t̲a̲b̲a̲s̲e̲ ̲U̲n̲i̲t̲
The VIDEOTEX Data Base Unit (VDU) is a self-contained
computer system containing hardware/software to control
and maintain an internal database. The VBU is dualized
as it is a mandatory function of VIDEOTEX. Therefore,
the VIDEOTEX configuration contains 2 VBUs - one acting
as a back-up for the other. Thus it is possible to
reestablish the data base after a disc failure.
E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲D̲e̲s̲i̲g̲n̲
An overview of the hardware structure is given in FIGURE
8-18, and the principal components are:
o VIDEOTEX Retrieval Unit
o VIDEOTEX Database Unit
o VIDEOTEX Input Unit
o VIDEOTEX External Database Unit
Each unit is a self-contained, operational computer
system and is dedicated to specific sub-tasks. Interchange
of information between units is via the TDX-Bus, a
time division multiplex path with high band-width.
FIGURE 8-18
VIDEOTEX Computer System Configuration
showing modular design
S̲y̲s̲t̲e̲m̲ ̲G̲r̲o̲w̲t̲h̲ ̲
The VIDEOTEX System Architecture (VSA) developed by
Christian Rovsing A/S is based on a comprehensive and
flexible approach; the system contains a number of
operatinal capabilities performed by distributed processing
elements which together provide the desired VIDEOTEX
Service.
Each processing element communicates with other operational
elements through a transmission network (e.g. X.25
package switching network, local area network, TDX-bus,
etc.)
System growth and expansion is, by virtue of the distributed
architecture, very flexible, and in fact the growth
potential is only a question of network capacity.
i) A̲i̲r̲ ̲C̲a̲n̲a̲d̲a̲ ̲D̲a̲t̲a̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲(̲A̲C̲D̲N̲)̲ ̲
A contract to build an advanced data communication
network for Air Canada has recently been received by
Christian Rovsing A/S after an proposal effort in competition
with major international computer companies. The network
will be based on the CR80 computer, which has been
developed by Christian Rovsing A/S and which will be
built at the company's modern manufacturing plant in
Ballerup, Denmark.
The new data network will provide the backbone for
Air Canada's overall data communication, covering ticket
reservations, passenger aircraft and airfreight information,
as well as administrative and financial tasks, thus
necessitating a network that can meet strict requirements
for reliability and security.
The data network will consist of three nodes in respectively
Toronto, Montreal, and Winnipeg. Each node will contain
a powerfull CR80 computer to control network communication
including 15,000 Air Canada terminals throughout North
America.
As Air Canada is recognized as a communications leader
among the airlines, the order to Christian Rovsing
A/S is another mark of international recognition for
the company's data communication expertise.
j) D̲J̲O̲T̲/̲D̲R̲E̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲a̲t̲ ̲H̲i̲l̲l̲ ̲A̲F̲B̲,̲ ̲U̲t̲a̲h̲/̲E̲d̲w̲a̲r̲d̲s̲ ̲A̲F̲B̲
The DJOT/DRES is being developed for the Utah
Test and Training Range at Hill AFB, Utah by
the Christian Rovsing Corporation, Thousand Oaks,
California. DJOT/
DRES is planned to be operational in October,
1983.
The primary AF objective is to perform first
generation data processing at Hill AFB, and all
other processing at Edwards AFB. The DAPAC system
is the primary first generation processor at
Hill AFB. The Cyber computers provide processing
resources at Edwards AFB.
DJOT/DRES provides services to support this objective.
The following is a general description of DJOT/DRES
capabilities:
a) A communications capability linking the Data
Oprations Center (DOC) at Hill AFB and the
Flight Test Mission Control Center (FTMCC)
at Edwards AFB using existing microwave equipment
to provide:
1) High speed transfer of data between the
two facilities.
2) Remote job input/remote job output (RJE/RJO)
for the Cyber at FTMCC to support UTTR
customers.
3) Remote interactive service on the Cyber
system for users at the DOC for Cyber
software development, data file access,
and the management of data processing
performed at FTMCC.
4) Transfer of ASCII files between facilities.
b) Creation, editing and storage of ASCII files
at UTTR.
c) Online and offline storage sufficient to
receive, store, list, display, and transmit
flight test data generated at UTTR or FTMCC.
d) Online data review capability for:
1) Quality control of first generation data
processing.
2) "Quick-look" and graphics generation
for flight test data.
The detailed capabilities of DJOT/DRES are described
in the DJOT/DRES System Specification which is
available on requests.
The DJOT/DRES is comprised of two major functional
subsystems - DJOT and DRES (Data Review Subsystem).
DJOT is comprised of two physical subsystems,
DJOT/E and DJOT/H, located at Edwards AFB and
Hill AFB, respectively. Each of these three subsystems
is based on a CR80M (mapped) Computer System
running the Distributed Advanced Multiprocessor
Operating System (DAMOS).
Figure 4.1.1-1, DJOT/DRES System Block Diagram
8.4.1.2 Logistics Support and Capabilities
The System Division of Christian Rovsing A/S has a
support deparment named Integrated Logistics Support
(ILS). ILS undertakes the following work:
- Installation and Site Preparation
- Maintenance and Field Support
- Training and Documentation
In accordance with the current contracts, encompassing
FIKS (Danish Integrated Communications System) and
CAMPS (NATO wide Communication System), ILS will provide
Installation, Maintenance and Field Support to 8 danish
and 16 NATO Military headquarters. This service has
already started and will continue at least until mid
1985. It is planned that ILS will develop a European
wide service capability based on these initial contracts.
As part of the Air Canada Project, a major ILS activity
is being planned for North America; this activity can
be expended to cover ACCESS, assuming award of contract.
As the RFP stresses the importance of maintenance,
the maintenance sub-section below addresses these areas:
o effect of maintenance on maximizing continuity
of operation
o the degree to which the maintenance concept can
simplify and ecominize the diagnostics process
o the reliability, suitability and responsiveness
of
past maintenance experience
O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
The organisation of the Logistics Department is shown
in FIGURE 8-19 with indication of major responsibilities.
All personnel in ILS have a security allowance to at
least NATO SECRET. Maintenance and installation terms
have a higher allowance determined by the project in
question.
The following chapters describe the general responsibilities
of the 3 functional sections on a typical military
program.
LOGISTICS SUPPORT ORGANISATION
FIGURE 8-19
I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲ ̲S̲e̲c̲t̲i̲o̲n̲
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̲
At time of bidding the Installation section is undertaking
site preparation on the FIKS and CAMPS programs.
Assited by the divisional drafting department and subcontractors
the installation section will perform the following
tasks:
1) Conduct Site Survey
2) Generate Civil Works Requirements
3) Generate As-Built Drawings
4) Perform Site Verification
The Civil Works Requirements package contains the necessary
details for the customer (host nation) to draft work
specifications for local contractors.
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̲
Transportation of Equipment from the CR factory is
the responsibility of the Logistics Department. This
includes development of the Transportation Plan. CR
will utilize the service of a freight forwarder to
handle the details of the shipments.
During the installation phase, typically 1 or more
teams will install the equipment and perform a test
to verify that the hardware is functioning. The test
is made in preparation for the Site Provisional Acceptance
(SPA) being carried out by a test team from the project
organization.
In conjunction with equipment installation the installation
team will conduct a property inventory check (spare
parts, documentation etc.).
P̲a̲c̲k̲a̲g̲i̲n̲g̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The Installation Section is also responsible for the
development of Packaging Requirements for all types
of shipments to the sites. The requirements are formulated
in a procedure.
Special packaging instructions will be developed for
shipment of repairable items.
a) M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲a̲n̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲e̲c̲t̲i̲o̲n̲
M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲
The maintenance section of the Logistics Department
is responsible for giving appropriate input to System
Engineering to ensure that the systems developed will
meet the requirements for maintainability. Furthermore,
the maintenance section will give support to the group
writing the Maintenance and Diagnostic Software.
The maintenance section will work closely with Systems
Engineering to ensure consistency in determination
of the MTBF and MTTR figures.
The development of the Maintenance Plan and associated
procedures will be done by the maintenance function.
In the area of deliverable documentation the maintenance
section will generate the Maintenance Manual and conduct
maintenance related training.
b) F̲i̲e̲l̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲
Field Support will be managed by the maintenance section.
The three major activities are:
1) Coordinate the implementation of field changes
2) Assistance to customer's technical personel with
respect to hardware and software problems
3) Coordinate warranty repairs
c) S̲p̲a̲r̲e̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The maintenance section is responsible for the specification,
acquisition, packaging and delivery of spares, repair
parts and repairable subassemblies. Normally priced
Recommended Spare Parts List (RSPL) will be submitted
to CR's customer. Provisioning Conferences will be
held at contractors' facility, planned and conducted
by the maintenance function.
An approved Spare Parts List (ASPL) will be negotiated
with CR's customer and incorporated in the contract
by amendment.
Spare Parts Design Change Notices (SPDCN) will be issued
and controlled by the maintenance function.
d) C̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲u̲p̲p̲l̲y̲ ̲I̲t̲e̲m̲s̲
Codification (assignment of NATO stock numbers) will
be carried out by the maintenance and support section
if required by the contract.
e) T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲s̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The Maintenance function will specify all tools and
test equipments to be supplied under the contract.
Fur- thermore, a priced list of tools and test equipment
will be submitted to customer for all items required
at each site and maintenance depot to support the equip-
ment supplied.
f) 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 Maintenance Engineering.
All incoming reports will be recorded and analyzed
by maintenance engineering, and the corrective action
coordinated with the customer.
T̲r̲a̲i̲n̲i̲n̲g̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲S̲e̲c̲t̲i̲o̲n̲
a) O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
Logistics Department is responsible for all customer
training on programs undertaken by the Systems Division
of Christian Rovsing A/S. The training organization
also has the responsibility for the development of
manuals and handbooks.
The material used for training is essentially the same
documentation which the technician later will work
with on site.
The training section of Logistics Department is headed
by a section manager who has technical writers/instructors
reporting to him.
b) D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲a̲n̲d̲ ̲C̲o̲n̲d̲u̲c̲t̲ ̲o̲f̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲ ̲C̲o̲u̲r̲s̲e̲s̲
The development of the individual courses which make
up a typical Training Program will take place in the
Training Section.
The staff of the Training Section encompasses both
hardware and software instructors.
The Training Section is responsible for the coordination
of the use of all training facilities within the company.
In addition to training customers of the System Division
the section conducts inhouse courses in Software programming
as well as general courses on the CR-80 computer.
Coordination of in-house video courses is also managed
by the training section.
c) M̲a̲n̲u̲a̲l̲s̲ ̲a̲n̲d̲ ̲H̲a̲n̲d̲b̲o̲o̲k̲s̲
Technical writers will develop the necessary manuals
in accordance with the contractual requirements.
On programs where several types of peripheral devices
are used, the technical writers will specify the contents
of the manuals. Review sessions will be held with suppliers
and with in-house participation.
8.4.2 F̲a̲c̲i̲l̲i̲t̲i̲e̲s̲:̲ ̲C̲o̲r̲p̲o̲r̲a̲t̲e̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
8.4.2.1 H̲i̲s̲t̲o̲r̲y̲ ̲o̲f̲ ̲C̲h̲r̲i̲s̲t̲i̲a̲n̲ ̲R̲o̲v̲s̲i̲n̲g̲ ̲A̲/̲S̲
Christian Rovsing A/S was founded in 1963. At first
the company worked mainly in a consulting and advisory
capacity within the EDP field. Activities developed
rapidly, and the business gradually changed character
from consultant to supplier of systems.
Around 1971, a deliberate commitment was made by the
company to apply its resources to the European Space
Programme. It has since participated in most major
programmes, and successful participation has broadened
the company's capabilities. The high degree of performance
which these programmes demand has been met by applying
up-to-date technology, specialised hardware and software
engineering expertise, and modern management methods.
For the design and production of switching power supplies
to the European Space Programme, the company developed
an advanced technology and sophisticated design philosophy
which can be applied to the solution of complex power
supply problems. Several patents are held by the company
relating to power supply circuit design.
Based on experience gained from engagement in the European
Space Programme the company decided to enter the demanding
military market. An important contract with Delco Electronics
Inc. to co-produce their Fire Control Computer as part
of the 4-nation European F-16 Program was won. The
Fire Control Computer is the only "end-item" co-produced
in Denmark and is delivered directly to the F-16 assembly
lines in Europe or the U.S.A.
In the mid-seventies the company began to enter the
data communications market. It has since participated
in critical computer communications-oriented programmes
for both commercial and defence customers, with such
projects as CAMPS (NATO), FIKS (Danish MOD), and LME-Network
(commercial).
Christian Rovsing A/S believes that it has developed
exceptional, professional resources dedicated to advanced
data communication. Furthermore, the company excels
in applying current technology to modular equipment
design and has a product line that is in the front
end of the state-of-the-art.
In short, Christian Rovsing has acquired extensive
experience in the design, development, and manufacture
of computer and aerospace electronics.
8.4.2.2 E̲m̲p̲l̲o̲y̲e̲e̲ ̲P̲r̲o̲f̲i̲l̲e̲
The group employs approximately 800 persons.
Approximate staffing levels by functional groupings
are as follows:
o Engineering and/or Scientific Professionals
320
o Technicians
170
o Assembly/Production Workers
90
o Q.A. & Inspection
20
o Administrative and clerical
200
8.4.2.3 F̲A̲C̲I̲L̲I̲T̲I̲E̲S̲
The company has 2 major facilities:
o A 5500 sq. metre (59,000 sq.ft.) leased facility
in Herlev, near Copenhagen.
o A 12000 sq. metre (128,500 sq.ft.) leased facility
in Ballerup, near Copenhagen.
A separate, dedicated facility (1,000 sq. m./10,700
sq.ft.) has been established for the co-production
of the F-16 FCC (computer). This facility is located
in Valby, which is about 10 Km from Ballerup.
Approximate break-down of floor area by function in
the 2 major facilities is as follows:
C̲a̲t̲e̲g̲o̲r̲y̲ S̲q̲.̲ ̲M̲e̲t̲r̲e̲s̲ S̲q̲.̲
̲F̲t̲.̲
o General Manufacturing 2,500 26,900
o "Space Qualified"
clean room 200 2,200
o Test & Integration Areas 2,500 26,900
o Laboratories 3,000 32,000
o Engineering and
Administration 9,300 99,500
Repair facilities are shown in FIGURE 8-20
REPAIR FACILITIES
FIGURE 8-20
8.4.2.4 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
Management of the Company is in the hands of Messrs.
Christian F. Rovsing, Claus Jepsen and Lars Stig Nielsen.
Mr. Rovsing is the President and the founder of the
company. He is a member of many government and industrial
committees as well as professional societies related
to research and data processing.
Today, there are five major divisions within the company
- FIGURE 8-21
o Data Processing Division
o Electronics Division
o Systems Division
o Production Division
o Development Division
and three wholly owned subsidiaries:
o Christian Rovsing Corporation (Los Angeles, California)
supports the mother company in major contracts
with North American customers and has its own software
development center.
o Christian Rovsing International located in Copenhagen
delivers computer systems for communication networks
and process control and contracts staff to large
international customers.
o CR Card System located in Copenhagen delivers electronic
systems for the automation of gasoline (petrol)
stations.
The Data Processing Division is located in a 5,000
sq. meter leased facility in Herlev, near Copenhagen.
The Electronics and Systems Divisions are based in
a newly constructed 12,000 sq. metre facility in Ballerup,
also near Copenhagen.
The Administration and General Management are located
in the Ballerup facility.
The Ballerup location houses development laboratories,
the main production and test department, a model shop
and special "clean room" facilities for the production
of space-qualified hardware, as well as engineering
and administrative offices.
A separate, dedicated facility has also been established
for the co-production of the airborne FCC computer
for the European F-16 program. It is located about
10 Km from the main Ballerup facility.
Military data communication systems are the responsibility
of the Systems Division.
More details about the five divisions of Christian
Rovsing A/S and Christian Rovsing International are
given in the sections to follow.
For further financial information, the company annual
report is available.
COMPANY ORGANISATION
FIGURE 8-21
a) D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
The Development Division FIGURE 8-22 has 5 departments,
which are Product Design, Divisional Support, Electronic
Design, CR80 System Software, and Micro Systems Software.
The Product Design Group is responsible for the preliminary
definition of new projects and the decision to start
development as well as high level system policy and
continuous evaluation of divisional development efforts.
Department heads are responsible for carrying out division
plans for development, and together with the divisional
manager resources are allocated to ensure meeting divisional
goals. Department heads also participate in budget
preparation and are responsible for meeting them.
As development demands efforts from all departments,
projects are staffed accordingly. Each project, or
task, is led by a task manager with responsibility
for weekly progress reporting to ensure meeting schedules
- a uniform, computer based reporting system, started
in 1982, simplifies this task.
THE DEVELOPMENT DIVISION
FIGURE 8-22
b) E̲D̲P̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
The Data Processing Division FIGURE 8-23 employs about
150 people, of whom 80 work within the data service
bureau - Christian Rovsing Data Services, CRDS.
CRDS is one of Denmark's largest service bureaux utilising
two IBM-370's and two Burroughs-6700's at its central
computer installation. Access to the service bureau
is via several hundred direct and dial up lines forming
a large private network which stretches from Oslo and
Stockholm in the north via Copenhagen to Frankfurt
and Vienna in the south.
The division has a separate consultingdepartment which
gives assistance to clients outside CRDS.
This department advises on the application of data
processing to organisations, and work on systems development
and programming for both technical and administrative
business.
The Technical Computer Applications department employs,
almost exclusively, engineers and software specialists
and works with projects in data-communications, automation
and process control, and medical systems.
The Business Systems department delivers small computer
based business systems for inventory control, wage
and salary control, accounting systems, etc.
Many projects within the Data Processing Division are
carried out in co-operation with other suppliers, whereby
the customer can be offered complete turn-key systems.
EDP DIVISION
FIGURE 8-23
c) E̲l̲e̲c̲t̲r̲o̲n̲i̲c̲s̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
The Electronics Division FIGURE 8-24 consists of three
principal engineering departments, which are the Data
Management Department, the Communications Product Department,
and the Support and Maintenance Department.
The Data Management Department is dedicated to data
base applications. Two current projects are DANKORT
and TELEDATA. DANKORT is a national credit card system
covering bank and retail transactions as well as inter-bank
funds transfer. TELEDATA is a national VIDEOTEX service
provided by the Danish Teleadministration (Post & Telegraph
and the Telephone Administration - KTAS/FKT/JTAS).
The Communications Product Department is concerned
with all aspects of data communications. Four major
products are DORA - an on-line, real-time editing system
for news programs on Danish Television, BARONET - a
front end processor to ICL computers with planned expansion
to a full communications network, CRISP - a communications
network serving ICL computers, and Local Area Networks.
The department has its own Product Software Group.
The Support and Maintenance Department provides support
to all division projects, and includes the MICRO Systems
Group, the H/W Support Branch, the S/W Maintenance
Group, and the Training Section. The H/W Support Branch
includes design, test and integration, and field support
services.
On the divisional level, there is a marketing function
and a Product Group which co-ordinates all projects.
ELECTRONICS DIVISION
FIGURE 8-24
d) P̲r̲o̲d̲u̲c̲t̲i̲o̲n̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
The Production Division FIGURE 8-25 has three major
functions, which are Module Production, Integration
and Test, and Test Engineering. There are 100 employees
and 2000 sq.m. of production area with a present capacity
of 7000 modules per year. Production capacity growth
is planned to be from 40 to 60% per year in the coming
years.
There are two production lines:
o Medium volume, complex modules - CR80 modules
o Large volume products - power supplies and local
area networks.
Quality Assurance is ensured by a separate group, reporting
directly to top-level management. Production meets
NATO AQAP-1 standards.
At present, production is semi-automatic with laser
guided mounting of module components and automatic
test equipment. By 1985, production is expected to
be fully automated - an overview of the Electronic
Factory is shown in FIGURE 8-26
THE PRODUCTION DIVISION
FIGURE 8-25
THE ELECTRONIC FACTORY
FIGURE 8-26
e) S̲y̲s̲t̲e̲m̲s̲ ̲D̲i̲v̲i̲s̲i̲o̲n̲
The Systems Division FIGURE 8-27 was structured late
in 1979, and systems-related activities were consolidated
to improve the handling of large, integrated hardware/software
data communications programs. The division is organised
on a project basis including CAMPS and FIKS, two major
military communication projects. Each major project
is under the cognizance of a Project Office with total
system responsibility and control authority to co-ordinate
in-house activities, and to provide close liaison with
the customer throughout the duration of the Project.
Projects are supported by the Integrated Logistics
Department. Its services include site surveys, installation,
training, documentation, maintenance, spares and other
support.
Advanced system development projects are assigned to
the Computer Systems Engineering Group. Current projects
include satellite image-data handling systems and miscellaneous
consulting services.
The Systems Division is also responsible for contract
performance in conjunction with Danish Industrial Group
One on the production and delivery of some 400 military-qualified
computers for the F-16 project. A complete computer
is produced each workday.
Quality Assurance reports directly to top-level management.
Emphasis is placed on the quality of the hardware and
of the software, both of which affect system performance.
THE SYSTEMS DIVISION
FIGURE 8-27
8.4.3 Financial Status
8.4.3.1 Annual Report 1981 (Summary)
Statement of Net Assets 31st December 1981:
Fixed Assets 41.9 million Dkr
Current Assets 132.8 " "
Net Proceeds from
Share Issue (1) ̲4̲0̲.̲6̲ ̲ ̲ ̲"̲ ̲ ̲ ̲ ̲ ̲ ̲"̲
Total Assets 215.3 million Dkr
Current Liabilities 1̲2̲5̲.̲1̲ ̲ ̲ ̲"̲ ̲ ̲ ̲ ̲ ̲ ̲"̲
Net Assets less
Current Liabilities 90.2 " "
Long-term Liabilities ̲3̲1̲.̲5̲ ̲ ̲ ̲"̲ ̲ ̲ ̲ ̲ ̲ ̲"̲
Shareholder's Equity 58.7 million Dkr
=================
The 1981 Annual Report is contained in the technical
Literature, ref. A.1.
8.4.3.2 ACCESS Project Financing.
