APPENDIX J: VIKING THROUGH LIFE STRATEGY AND PLAN


PG Viking Through Life Information Management Strategy
Date of first issue:	Project No.:
14 August 1998
Approved by:	Organizational unit:
Truls Grasmo	The ILS Group
Client:	Client ref.:
	Kockums Ordernr: 213012 -10
Summary:
As the first of three reports making up the Information Management Study in the Viking program, this report constitutes the Through Life Information Management Strategy. In addition, the Information Management studies will deliver the reports "Information Management Plan" and "Preparation for next project phase." The Viking program is still in an early stage, and few decisions have been made, and it will probably be necessary to update the Through Life Information Management Strategy when more decisions regarding concept for the submarine and organization of the program have been made. The goals for Through Life Information Management are: · Improved through life quality and accuracy of system information · To establish accurate and consistent configuration management through life. · Reduce design, development, and production cost by 10%. In order to accomplish these goals the following recommendations are made: · To establish a shared data environment with a common logical data structure amongst all participating parties on both the government and the industry side. · The recommended solution for the shared data environment is: · Unclassified information: A shared data environment based on one logical information structure with integrated access. Data can be allowed to be stored in several geographical places, but in one logical structure. Information access shall be on-line. · Classified Information: Dedicated local systems with approved on-line connection. All classified information shall be managed in the same logical structure as for unclassified information. · The logical data structure for Viking should be able to hold and integrate all information necessary to design, build, operate, and support the Viking submarines. It should be based on open, international, or de facto industry standards, and necessary commercial software should be available.


PG Viking Through Life Information Management Strategy
Editors Ref.:		Subject Group:

fbp/98aaadzf				Indexing terms
Report title:
Through Life Information Management Strategy				Information Management, Digital Information Through Life, Viking
Work carried out by:
Viking Information Management group, see Appendix A Edited by: Nils Sandsmark, Frank Børre Pedersen				No distribution without permission from the responsible organizational unit
Work verified by:
Boye Tranum				Limited distribution within PG Viking
Date of this revision:	Rev. No.:		Number of pages:
5 September 1998	03		*	Unrestricted distribution

PG Viking Through Life Information Management Strategy

Table of Contents

1 Introduction *
2 Description of the Viking Business Environment *

2.1 Goals for Viking *
2.2 Constraints, political decisions and concept choices *
2.3 Roles and relationships *
2.4 Options to be maintained *
2.5 Miscellaneous *

3 the Viking lifecycle *

3.1 Introduction *
3.2 Purpose *
3.3 The TLBM Model for PG Viking *

4 External Information Environment *
5 Goals for Through life Information Management *

5.1 Technical goals *
5.2 Business improvements *
5.3 How improvements will be managed and measured *

6 Shared Data Environments for VIKING *

6.1 Shared data environment options for Viking *

6.1.1 Solution A *
6.1.2 Solution B *
6.1.3 Solution C *

6.2 Common logical data structure for Viking *

7 Assessment of Options *

7.1 Shared data environment options *

8 Recommendation *
9 References *
Participants in the study
Cost, benefit and risk definitions

PG Viking Through Life Information Management Strategy

1. Introduction
The Viking program is a joint Scandinavian defense program between Norway, Sweden and, Denmark with the overall intent to develop the next generation submarines. The program is currently in the study and concept phase, where the main goal is to:

"Prepare the necessary background documentation for a decision to be taken by March 31, 1999; thus allowing the authorities in the three countries to decide whether or not it is considered expedient to continue the co-operation and develop a common building specification for the new submarines."

See reference /1/ for further information.

As the first of three reports making up the Information Management studies in the Viking program, this report constitutes the Through Life Information Management Strategy. In addition, the Information Management studies will deliver the reports "Information Management Plan" and "Preparation for next project phase."

2. Description of the Viking Business Environment
2.1 Goals for Viking
The goals for the Viking program are:

· Common procurement: To plan for a possible common procurement and if politically acceptable, procure 10 submarines to Denmark, Sweden and Norway within the period from 1999 to 2012.
· Required capability: The submarines shall fulfill the operational goals for each nation, and procurement costs for each submarine must be far less than if each nation should procure individually. The program must also be beneficial for the life support cost for the participating nations, and shall give Scandinavian industry the opportunity to participate in the development and production of the submarines.
· Required availability: To be determined during study and concept phase, but not less than the Gotland-class. Staff requirements require that the benefit of availability must be considered in proportion to the procurement costs.
· Required sustainability: The submarine sustainability shall be calculated from the basis of operational profiles and submarine missions. High degree of sustainability must be given higher priority than redundancy.

2.2 Constraints, political decisions and concept choices
The Viking program is still in an early stage, and few decisions have been made, and it will probably be necessary to update the Through Life Information Management Strategy when more decisions regarding concept for the submarine and organization of the program have been made.

Program constraints:

· Decision to start a co-operative Project Definition Phase (PDP) medio/ultimo 1999 after the delivery of study phase reports in March 99.

· Nations will have the opportunity to decide a common procurement after PDP, probably at the end of 2001

· Cost limit for the procurement of Danish submarines is 900 mill SEK (1996)

· Limited competition due to the requirement to involve the nations submarine and submarine related industry.

Political decisions:

· Non of the nations have a political decision to acquire submarines

· Expected after PDP.

Concept choices already made:

· Study phase shows that harmonization of operational and technical requirements is possible, and that particular systems to fulfill the special Norwegian requirements can be fitted into separate sections or modules.

Requirements for training:

· To be decided during study phase.

2.3 Roles and relationships
Several actors, their roles, and relationships have been identified for the Through Life Information Management (TLIM) of Viking. As for section 2.2, several decisions will have to wait until the program as a whole has made the relevant governing decisions.

PMO and Prime Contractor:
The status of prime contractor to be decided during Study Concept Phase (SCP). Several options are possible, two of which are:

1. One prime contractor is preferred.
2. The prime contractor could be an industrial group/joint venture with participants from Norway, Denmark, and Sweden.

PMO and operational logistics and support concept:
To be decided during study phase.

Industry involvement through life:
Project Definition Phase: Common development of specifications between industry and PMO.

Design Phase (DP): To be decided during study phase.
Production Phase (PP): To be decided during study phase.
Support Phase (SP): To be decided during study phase.

· Management of mid-life-updates:

To be decided during study phase.

· Intellectual property rights:
To be decided during study phase.

· How to audit warrantees and incentive mechanisms:

To be decided during study phase.

· Roles and relationships regarding TLIM:

To be defined in TLIM Plan.

2.4 Options to be maintained
Not applicable in study phase.

2.5 Miscellaneous
Special issues requiring attention in the next version of the Through Life Information Management strategy are:

· Update of Through Life business Model (TLBM).

3. The Viking Lifecycle
3.1 Introduction
Based on the NATO CALS Through Life Business Model (TLBM), a TLBM has been developed for the Viking program. The TLBM is developed to help the program management to manage change, by making best use of information technology over the life-cycle of the program, as enabled by a shared data environment (SDE). It represents a common, agreed description of the major life-cycle activities and information flows, which a program will need to address.

The Viking TLBM has to some extent been tailored and adapted to a Scandinavian through life model for weapon systems, and to an appropriate level for the current project phase. The Viking TLBM covers all main activities in the project (not just the information management part), and is thus applicable to the program management of PG Viking. The TLBM may be further detailed, e.g., into the areas of risk management and logistic support analysis (LSA).

3.2 Purpose
This TLBM constitutes an agreed description of the Viking lifecycle, allowing PG Viking to:

· Maintain and update an agreed description of the Viking life-cycle, through a common understanding of the main activities and information flows.

· Gather, store and retrieve information for the Viking life-cycle

· Facilitate creation of project plans, work orders, etc.

3.3 The TLBM Model for PG Viking
This Viking TLBM is dynamic and is developed in a structured manner as a BPWin model /2/, based on the IDEF0 standard. The TLBM for the Viking program is enclosed in Appendix C in the form of a Word document. The original BPWin model should be consulted for a full reference of the Viking TLBM.

4. External Information Environment
At present, a large number of legacy systems are in use in Sweden, Denmark, and Norway. Some of these systems are old and will be replaced before year 2000. Some are new and a long life is expected.

Within the military services the situation is different in the three countries:

· Denmark has made a decision to replace all the old systems with one integrated system (DeMars) common to the entire Danish Defense. This system will be implemented in the period 1999-2004 and will therefore be in full operation well before the first Viking submarine will be delivered. This means that for the Danish navy, only the DeMars system needs to be addressed.

· Sweden is using a number of legacy systems, see reference /3/. The Swedish Defense has decided to put all software system development on hold until an ongoing study on the issue has been completed. This study is planned to be completed within a couple of years and until then it is difficult to make assumptions with respect to relevant IT trends, policies and plans.

· Norway is also using a number of legacy systems, see reference /4/. The Norwegian Navy is currently into a major acquisition project, where new escort vessels are to be procured. This project is of such a size that software standard, choices and policies will be of great relevance to other projects, also Viking.

For Defense industries in Sweden, Denmark, and Norway, very little information has been received. This will be addressed at a later stage.

5. Goals for Through life Information Management
5.1 Technical goals
With regard to Through Life Information Management, the following technical goals are set for the Viking program:

· To store system information according to a common logical data structure and be on-line available . This includes also all support and maintenance information.

· To establish and run accurate and consistent configuration management through life.

5.2 Business improvements
The use of Through Life Information Management will provide business improvements in the Viking program:

· Improved through life quality and accuracy of system information including support and maintenance information.

· Reduced cost, both in the acquisition phase, and in a life-cycle view. Reduce design, development and production cost by 10% by introducing a shared data environment and related working processes amongst all participating parties, both on the industry side and on the government side. The 10% reduction shall be gained purely because of better, faster and more accurate information flow, and shall be calculated based on estimates from previous Norwegian, Swedish and/or Danish submarine programs and LCC estimates to be calculated on the Viking submarine.

5.3 How improvements will be managed and measured

· System information: No duplication of information will be accepted. The program shall be manned with necessary skills to manage and handle information.

· Configuration Management: The configuration management scheme shall include a configuration audit function in order to assure the quality of the CM activity and CM information.

· Cost reduction: Cost reduction shall be measured by ongoing LCC tracking. Initial estimates shall form a baseline (expected in the PDP).

6. Shared Data Environments for VIKING
6.1 Shared data environment options for Viking
6.1.1 Solution A

· Unclassified information:

A shared data Environment based on common data structure with local stored information. Local data vaults partitioned based on functions and disciplines (e.g., CM, LSAR). Distribution of data between installations will be based on off line methods. The original data shall not be stored in more than one place. This requires a common data administration.

· Classified information:
Dedicated local systems with approved off line distributions.

6.1.2 Solution B

· Unclassified information:

A shared data environment based on one logical information structure with integrated access. Data can be allowed to be stored in several geographical places, but in one logical structure. Information access shall be on-line.

· Classified Information:
Dedicated local systems with approved on-line connection. All classified information shall be managed in the same logical structure as for unclassified information. A consistent system for referencing between classified and unclassified information must be established.

6.1.3 Solution C
One multi security concept where all information is managed in one logical structure. Information access shall be on-line.

6.2 Common logical data structure for Viking
The logical data structure for Viking should be able to hold and integrate all information necessary to design, build, operate, and support the Viking submarines. It should be based on open, international, or de facto industry standards, and necessary commercial software should be available.

7. Assessment of Options
This section contains an assessment of the three options for a shared data environment (SDE). The assessment takes into account:

· Benefits: Value added by SDE in meeting project goals (such as Operational Availability, minimized LCC, shorter development)
· Cost: Cost of SDE (people, software, maintenance, etc ) Information resources is all expenses incurred in the creation, processing and distribution of information
· Risks: Technical, cultural, process change, etc. How much change can we manage? How sophisticated can we be? (Evolution v revolution!)

Another important measure for the Viking program in order to support decisions regarding Information Management is the life-cycle cost (LCC) model. This would naturally be a part of the main LCC model in Viking. However, as the latter model is not established yet, this will have to be postponed.

The assessment is performed using the philosophy of Criticality Management Tools (CMT) as described in Refs. /5/-/6/. At the present stage, only a qualitative assessment is made. The various options are evaluated on a relative scale, using the definitions listed in Appendix B.

7.1 Shared data environment options
A qualitative assessment of the three solutions for a shared data environment (SDE) is provided in Table 7.1 below. Refer to Appendix B for definitions of the terms used.

Table 7.1 Assessment of the Options for SDE
Solution
Cost
Benefit
Risk

Solution A
Medium:
Cost estimate comparable to other solutions
Low:
Off-line methods for diversified information. Requires a common data administration
Significant:
Uncertainty regarding ability to adapt to technological and process changes.

Solution B
Medium:
Cost estimate comparable to other solutions
Medium:
On-line methods for geographically distributed data. Improved accessibility due to one logic structure.
Significant:
Geographically distributed data represents a considerable technological risk.

Solution C
High:
Cost estimate higher than comparable solutions
High:
One multi security system, with on-line access to one logical structure.
Critical:
Security requirements not acceptable.

8. Recommendation
Based on the assessment of Section 7, the following points are made for the shared data environment options:

· Solution A is inadequate as far as functionality is concerned, i.e., it is based on old-fashioned working processes that inhibit the full utilization of a shared data environment.
· Solution B is acceptable with respect to cost. Furthermore, it has major benefits. The associated risk level can be accepted.
· Solution C is unacceptable with respect to handling of classified information. Technical challenges in relation to developing a solution meeting the security requirements may be unacceptably costly.

From these considerations, the following recommendation is given: Solution B.

9. References

/1/
PG Viking, Minutes of meeting no 2, March 19, 1998.

/2/
BPWin User's Guide, Logic Works Inc., 1997.

/3/
List of Swedish legacy systems, FMV, 1998.

/4/
List of Norwegian legacy systems, SFK, 1998.

/5/
Criticality Management Tools - Operation Manual, Det Norske Veritas, 1998.

/6/
Risikomanual - PG Viking, 1998.

PG Viking Through Life Information Management Strategy
Appendix A: Participants in the Study

The participants in the Information Management group in the Viking program are:

Commander T. Grasmo
PG Viking

Major B. Tranum
NATO CALS

Principal Technical Officer U. S. Carlsson
FMV
Sweden

Head of Division J. B. Leimand
FKO
Denmark

Captain K. Eikanger (Meeting 1 through 4)
Senior Eng. V. Småberg (Meeting 5 and onwards)
SFK
Norway

Cons. N. Sandsmark
DNV

PG Viking Through Life Information Management Strategy
Appendix B: Cost, Benefit and Risk Definitions

This appendix contains the definitions of the cost, benefit and risk categories used in the assessment of the three options regarding a shared data environment.

As opposed to cost and benefits, risk is a two dimensional quantity. It describes uncertainties, and contains both a probability and a consequence dimension. For this reason, risk is treated separately from cost and benefits below.

Table B.1 Consequence Categories for Cost and Benefits
Category
Consequence
Definition

High
The option inflicts a large cost to the program

Cost
Medium
The option inflicts a considerable cost to the program

Low
The option inflicts a minor cost to the program

High
The option provides large benefits to the program

Benefit
Medium
The option provides considerable benefits to the program

Low
The option provides minor benefits to the program

Risk represents an unwanted deviation from a target. It has a two-dimensional nature, as it depends both on the probability of such a deviation, as well as the consequence ("size") of the deviation. In the qualitative version of CMT, the risk is divided into three levels, as shown in Table B.2 below.

Table B.2: Risk Levels
Risk level
Definition

Critical

A critical risk is unacceptable and mitigative actions must be implemented.
A Critical risk has both large probability of occurring and large consequence.

Significant

A significant risk represents a considerable risk, but is still acceptable on the grounds that it is constantly monitored to ensure that the risk level is not increased to a Critical level.
A Significant risk has either large probability of occurring or large consequence

Negligible

A negligible is acceptable and can in most cases be discarded.
A Negligible risk has small probability of occurring and small consequence

Using the measures defined in Tables B.1 and B.2, the three options regarding a shared data environment are evaluated with respect to their cost, their benefit, and the risks associated with that option. This is done in sec 7 of this report.