nato managing the defence system life cycle cals

8/3/2019 Nato Managing the Defence System Life Cycle Cals

1/36

AUGUST 1998


2/36

MANAGING THE DEFENCE SYSTEM LIFE CYCLE

The NATO CALS

Through Life Business Model (TLBM)

The TLBM presents a vision of how NATO can improve its acquisition and logisticsupport processes by adopting a consistent approach to the management of Defence

System programs over their full life cycle:

.. The enablers .

A Concurrent Engineering approach. Multi Disciplinary Groups, or Integrated Project Teams, involving all stake-

holders.

Electronic interaction between participants, based on a Shared DataEnvironment, maintained for the life of the program.

. The techniques..

Improved management of requirements, sustained through life. Consistent Life Cycle Strategies for managing risk, quality, configuration,

acquisition (and re-supply), support and program information.

Project Optimisation over the life-cycle, including

Early through life cost modelling, and improved cost awareness Trade-off studies: capability, supportability, cost, risk and in-service dateare treated as independent variables. Continuous review and approval of predicted or measured performanceagainst the current requirement Optimisation of the supply chain, for acquisition and for support.

Optimisation of support management based on feedback of in-serviceperformance.

Life cycle management of roles and relationships giving a flexible boundarywith industry.

Information is managed as an asset.. The outcome

Faster and cheaper acquisition Improved system availability Cheaper in-service support Safer disposal or re-use

Interested? Want to know more? Read on.

For help in using the TLBM, or in managing information more effectively contact the

NATO CALS Office by Fax: 00 322 707 3598 e mail [email protected]

We can help you to do better.


3/36

TLBM v6.00

Definition:

A model to illustrate NATO's improved business processes for

the through life management of a Defence System, as enabled by a SharedData Environment.

Scope:

The model illustrates the core activities which are required to

respond successfully to the Validated Mission Need and BusinessDirectives for the specific defence system programme over its full lifecycle. Integration of the DS into any wider organisational or businesscontext (e.g. armed force or industrial company) is assumed to occur

outside the model and is reflected by ICOMs crossing the TLBM boundary,as shown in the context diagram.The TLBM model does not define the order in which these activities are

to be performed, nor the organisation which may undertake them.

In using the TLBM DS programs will need to tailor the model to reflecttheir specific relationships with Armed Forces and Industry. The TLBMcan be used to identify information exchanges between organisations byselecting the activities (boxes) each organisation will perform andnoting the arrows which cross the organisational boundary, as shownwithin the TLBM or at its boundary.

DS will vary in the degree to which their support is integrated with the

support of other Defence Systems operated by the relevant Armed Forces.The model includes all activities required to provide support for aspecific DS. Information required by others to support the integrationof support for the specific DS with the support of others DS are

reflected by ICOMs crossing the TLBM boundary.The model reflects several activities which could be performed undercontract. It does not attempt to define relationships or interfaces

into the industrial supply chain beyond the Prime Contractor.

Purpose:

1. The TLBM is one of three NATO CALS products that are requiredto support the Strategic Plan.

2. To illustrate for NATO, the improved business processes for through lifemanagement of a DS, enabled by an SDE

3. This purpose is clarified and extended by the following notes,developed as a result of working on the comments received, and the

outstanding Issues (AnnexH of 4.2.report).

Intended Use:

4. The TLBM will be used to support both Track 1 and Track 2 of the 1998

Strategic Plan as follows:

Track 1:

By DS program managers and their staff, supported by NCO, to develop a

DS Program Strategy for CALS, based on NCOPS. In this context the modelmust:


4/36

- provide a top level over view of the main activities through the DSlife cycle, as enabled by an SDE.- draw attention to certain key activities that need to be managed in a

consistent manner through all lifecycle phase (CM, QA, ILS, Info

Management).- illustrate, at a high level, the major information flow within the DSprogram lifecycle, so that the program management can see the totalityof information to be managed through life.- support discussions and decisions of the likely impact, on

responsibilities and on information flows across boundaries arising from:

- different organisational boundaries (within the project, between theproject and industry, between the project and the Armed Forces)- different SDE boundaries and capabilities

- show where the IM processes themselves fit into the TL activities- provide a basis for the development of a program specific TLBM. Orother activity models required to solve specific problems.

By other members of NCO, and others, in presenting CALS concepts and

ideas during awareness activities.

By other NATO or national agencies who are seeking to explore lifecycle issues (e.g. Co-operative Logistics).

Viewpoint:

the viewpoint taken in the TLBM is that of the life-time owner of the DS.

The life time owner is accountable for providing and sustaining thespecific DS,over its full life cycle, to meet the Validated Mission Need andBusinessDirectives agreed and maintained for that DS. Responsibility for

performing

this role may be held by different organisations over time.


5/36


6/36

USED AT: AUTHOR: John Dunford DATE:

REV:PROJECT: NATO CALS Office - TLBM

10/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: MANAGE A DEFENCE SYSTEM THROUGH LIFEA-0

MANAGE A DEFENCESYSTEM THROUGH LIFE

Purpose: To illustrate NATO 's improved business

processes for through life management ofa defence system, enabled by an SDE(See Model Editor for further clarification).

Viewpoint: the viewpoint ta

The life time owner is acco

over its full life cycle, to me

Directives agreed and main

this role may be held by dif

Validated Mission Need

Goods & Services fm others

Feedback fm Ops

Business

Directives

Laws &

Gov

Policy

Def.

Pol.&

Stds

Usage&support

Policy

O

P

Project

PersExisting

Infrastructure

External Data

DS needing support


7/36


8/36



10/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READE

NODE: TITLE: MANAGE A DEFENCE SYSTEM THROUGH LIFEA0

A1

ESTABLISH AND

CONTROL DS

PROGRAMME TL

A2

OBTAIN DS

SUPPORT THE US

the DS

External

Data

Program

SDE

Feedback

fm Ops

Business

Directives

Def.

Pol.&

Stds

Usage&support Policy Op Pro

Inst to Ops

Feedback fm Maintenance

Current Req

Existing I

Prg Dir

Information

Services

Support Info

Proc Spec

Core Product Data

Tools & Facs.

Perf Rep

Goods &

Servicesfm

others

Trg Req

Contracts and Requests

Change Impact

Project

Pers

Predicted Perf

DSneeding

support

Reqd Feedback

Eval Def

Spares & Components

Evaluation Findings

TestFindings

Validated

Mission

Need

Required Items


9/36


10/36



10/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: ESTABLISH AND CONTROL DS PROGRAMME TLA1

A11

ESTABLISH AND

CONTROL THE

REQUIREMENT

A12

DEVELOP LC

STRATEGIES

& POLICY

A13

ESTABLISH and

RUN the DS

ORGANISATION

Business

Directives


Usage&support

Policy

LC Strat & Pol.

Required Items

Change Proposal

Proc Spec

Validated Mission Need

Predicted Perf

Feedback fm Ops

Support Info

Evaluation Findings

External Data

TestFindings

Change Impact

Predicted LCC


11/36


12/36



27/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: DEVELOP LC STRATEGIES & POLICYA12

A121

DEFINE LC

STRATEGY

AND POLICIES

A122

DEFINE

ACQUISITION

STRATEGY

A123

DEFINE RISK

STRATEGY

A124

DEVELOP ILS

STRATEGY

A125

DEVELOP CM

STRATEGY

AND PLAN

D

CALS Strategy

CM Strategy

QA Strategy

External Data

Acq Strat

Risk Man

Strategy

ILS Strategy


13/36


14/36



26/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: ESTABLISH and RUN the DS ORGANISATIONA13

A131

MANAGE

PROGRAMSCHEDULE

A132

ESTABLISH

ROLES and

RELATIONSHIPS

A133

PLACE &

MANAGE

CONTRACTS

A134

MANAGE DS LC

FUNDING

MANAGE

RESOU

Program WBS

Budget R

Change Proposal

Current Req

Requests for Assistance

Financial Implication

Contract Dir.

Program Schedule

Av

Org Structure

Activities to be contracted

External

Data

SDE Req.

Change

Impact

Required

Items

Perf RepContracts

Proc Spec


15/36

NODE: TITLE: ESTABLISH and RUN the DS OA13

A131

MANAGE

PROGRAM

SCHEDULE

A132

ESTABLISH

ROLES and

RELATIONSHIPS

A133

PLACE &

MANAGE

CONTRACTS

M

Program WBSChange Proposal

Current Req



Contra

Program Schedule

Org Structure


External

Data

Change

Impact

Required

Items

Perf RepContra

Proc Spec

A133T PLACE & MANAGECONTRACTS

This chart briefly illustrates the major activities in placing and managing

contracts. The requirement should be noted for historic data from other

programs in developing a contract strategy (External data) and for

significant feedback from maintenance and operations, to assess the

performance of reliability or in service availability clauses. This is

provided by the Performance Report. The proposals received in

response to the ITT are treated as part of External Data.


16/36



03/04/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: PLACE & MANAGE CONTRACTSA133

A1331

DEVELOP CONTRACT

STRATEGY

A1332

ISSUE SOLICITATION

A1333

ASSESS PROPOSALS

Contract

Strategy


Invitation to Tender

Available Funding

Selected

Contractor

Contract Information Req

External Data

Proc Spec

Program

Schedule

SDE Req.

Required Items

Perf Rep


17/36

NODE: TITLE: ESTABLISH and RUN the DS OA13

A131

MANAGE

PROGRAM

SCHEDULE

A132

ESTABLISH

ROLES and

RELATIONSHIPS

A133

PLACE &

MANAGE

CONTRACTS

M

Program WBSChange Proposal

Current Req



Contra

Program Schedule

Org Structure


External

Data

Change

Impact

Required

Items

Perf RepContra

Proc Spec

A136T MANAGE DS INFORMATION

The extensive activities involved in managing information through life, in

the context of a Shared Data Environment are fully described in the

NCOPS to which reference should be made.


18/36

USED AT: AUTHOR: NCFP Team DATE:


14/04/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: MANAGE DS INFORMATIONA136

A1361

DEVELOP

IM PLAN

A1362

ESTABLISH &

OPERATEProgram SDE

I

Program

WBS

ProgramSchedule SDE Req.

IM

PlanExternal Data


19/36


20/36

USED AT: AUTHOR: NCFP Team DATE:


20/05/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: OBTAIN DSA2

A21

DEVELOP DS

A22

PRODUCE DS

A23

CONDUCT TESTING

Current Req

Project Pers

Prg Dir

Items

for

Test

External Data

Test Def

Goods &

Services fm

others

Users

Items for Rfb

DS for Deployment

Tools & Facs.

As-built Config

Spares & Components

Mfr &Rfb

data


21/36


22/36



27/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READE

NODE: TITLE: DEVELOP DSA21

A211

DEVELOP

CONCEPTUALOPTIONS

A212

DEFINE DS

A213

ENGINEERING

DESIGN

A214

FAILURE

ANALYSIS

A215

DESIGN THE

SUPPORT

SYSTEM

Support Equipment Requirements

Existing

Business

Info

DS Concept

Functional Architecture

TestFindings

FMECA

Data

Current

Req

In Service Goals

External

Data

Users

Prg


23/36

NODE: TITLE: MANAGE A DEFENCE SYSTEMA0

A1

ESTABLISH AND

CONTROL DS

PROGRAMME TL

A2

OBTAIN DS

External

Data

Program

SDE

Feedback

fm Ops

Business

Directives

Def.

Pol.&

Stds

Usage&support Policy

Inst to Ops


Current Req

Prg Dir

Information

Services

Support I

Proc Spec

Core Product D

Tools & Facs.

Perf Rep

Goods &

Services

fm

others

Trg Req

Contracts and Requests

Change Impact

Project

Pers

Predicted Per

DS

needing

support

Reqd Feedbac

Eval Def

Spares & Com

Evaluation Findings

TestFindings

Validated

Mission

Need

Required Items

A3T SUPPORT THE USE of the DS

This activity provides the support needed to bring

individual systems into the condition required for

operations.

A31 defines the work to be done, based on the Operational

Program, the Program Directives and the support

procedures within the Support Data. A31 also establishes

the requirement for items to be purchased for use in

support activities.

A32 provides storage, transportation and issue as required

of spares and other items needed for maintenance, based

on the deliveries from A2.

A33 undertakes the maintenance needed to restore the DSto the condition required for the next intended operation.

This includes the activities of diagnosing, repairing, testing

and calibrating the item in accordance with the Core

Product and Support Data. The activity also includes the

work needed to incorporate approved changes to the

system configuration. Feedback from maintenance is

provided as specified by Required IS Data, by recording the

findings, action taken, spares used and issues arising. The

AS Maintained (current) Configuration is reported to A31

(and elsewhere as needed) to reflect work undertaken.

Items removed or no longer required are passed to A4 for

disposal, recycling or refurbishment.

A34 undertakes any (non maintenance) activities needed to

prepare the system for operations e.g fuelling, tow from

hanger, empty waste tanks etc.

A35 maintains the support facilities and tools in a fit for use

condition.

A36 provides operator and maintainer

training, in accordance with the requirement

from A215.

A37 evaluates the performance of the

support system, in relation to predictedperformance, in accordance with the

definition provided from A212.


24/36



10/03/98

30/07/98

NOTES: 1 2 3 4 5 6 7 8 9 10

WORKING

DRAFT

RECOMMENDED

PUBLICATION

READENCO

NODE: TITLE: SUPPORT THE USE of the DSA3

A31

PLAN

SUPPORT

A32

STORE

TRANSPORT &

ISSUE ITEMS

A33

MAINTAIN,

UPDATE &

PROVIDE

FEEDBACK

A34

O&S TASKS

A35

MANAGE

FACILITIES

T

Support Plan

Support Info

Spares &

Components

External Data

Op Prog

Existing Infrastructure

MaintainedDS

Prg Dir

DS needing support

Core Product Data

Current Req

Tools & Facs.

Items for

Use

Goods & Services fm others

In-Scope EvalFindings

Req Config

Reqd

Feedback

Predicted Perf

As-maint Config

Tools & Facs.


25/36

TLBM v 6.00

Act i v i t y Def ini t i ons

Activity Name Activity Definition

MANAGE A DEFENCESYSTEM THROUGH LIFE

A0

ESTABLISH AND CONTROL

DS PROGRAMME TL

A1 Activities needed to create, resource and manage the

organisation, or organisations needed to obtain, use and

dispose of the DS over its life cycle.

ESTABLISH AND CONTROL

THE REQUIREMENT

A11 This activity takes the VMN, the Business directives, the

Usage&Support Policy and any recommendations for

change arising from within the DS program activities

and develops, and sustains a Current Requirement

statement, to the level of detail needed to execute the DS

program. Requirement change proposals are assessed,

approved or rejected, seeking external agreement where

necessary. The valid current requirement is released for

use. Configuration of the requirement statement, and

the requirement history are maintained as required.

DEVELOP LC STRATEGIES

& POLICY

A12 Develop and implement an integrated suite of policies

and strategies for managing the DS over its life-cycle.

These strategies will shape the development of the

program organisation and establish the framework

within which the Program Directives are developed.

DEFINE LC STRATEGY AND

POLICIES A121

This activity establishes a consistent and integrated set

of high-level policies and strategies to guide the

management of the DS program over its full life cycle .

DEFINE ACQUISITION

STRATEGY A122

The approach to be taken in acquiring a service or DS

component, initially and for re-supply. It should cover

the method of acquisition, the "rent, make or buy"

policy, the use of competition and or partnering

arrangements and the contract incentive mechanisms.Particular attention should be paid to ensuring continued

satisfactory operation of the DS after the contract

closure, as this determines what rights and what data

must be acquired as part of the contract, or separately.

DEFINE RISK STRATEGY

A123

Development of the program approach to identifying,

assessing and managing risk of failure to comply fully

with the VMN or Business Directives

DEVELOP ILS STRATEGY

A124

Develop a strategy and plan to show how ILS will be

implemented for the particular DS over its full life cycle.

DEVELOP CM STRATEGY

AND PLAN A125

Develop a strategy and plan to show how CM will be

implemented for the particular DS over its full life cycle.

.

DEVELOP QA STRATEGY

AND PLANS A126

Define the actions required to ensure systematic

approaches are taken to the integrated concurrent design,manufacture and support of the DS and the related

processes

DEVELOP CALS STRATEGY

& PLAN A127

An assessment of the business and CALS Environment

facing the DS program, development of the program

goals for CALS and an assessment of the costs, risks,

and benefits of the options of CALS-implementation.

ESTABLISH and RUN the DS

ORGANISATION

A13 Set up and run an organisation capable of delivering an

acceptable DS, that meets the Current Requirement.


26/36


MANAGE PROGRAM

SCHEDULE A131

Define the tasks to be performed and services to be

provided, in response to the Current Requirement and

Change Proposals (what to do), and monitor task

achievement. Develop a Program WBS or Task list.

Develop any Service Level Agreements needed to

specify the standard of ongoing services. The WBS or

Task List must reflect the work needed to assess theimpact of proposed change. Based on the implications

reported, decisions are made on which proposed changes

to implement or reject. The work required to implement

approved changes is reflected in the updated WBS or

Task list. Develop and publish top level Program

schedules showing when activities are to be undertaken.

(Detailed planning of tasks in other activity boxes is

assumed to occur "locally".)

ESTABLISH ROLES and

RELATIONSHIPS A132

This activity establishes how responsibility for the

various program tasks is to be allocated over the life

cycle, including the identification of tasks to be placed

on contract. As roles and relationships will change over

time, particular attention should be paid to the

mechanisms for incentivising and ending contracts andto the management of transitional arrangements (e.g. on

entry into service).

PLACE & MANAGE

CONTRACTS A133

Action needed to place, operate and close contractual

agreements required by the DS program. It includes

generation of the contract requirements and the

development and operation of payment and incentive

arrangements.

DEVELOP CONTRACT

STRATEGY A1331

The process of programming, controlling, documenting,

and implementing the specific requirements levied by

the negotiated contract or agreement. This process

includes ensuring that the Staff Target, program

objectives, and implementation plans are incorporated in

contractual definitions and design information. Also, it

includes programming available funding into the

contractual process through negotiations, incentives, and

modifications, and the initiation and execution of

appropriate agreements which may fall outside of the

specific contract such as those between government

units.

ISSUE SOLICITATION

A1332

The specific contractual solicitation or tender is prepared

and Issued, including the Statement of Work, the

Evaluation Criteria, and the Contract Deliverables.

ASSESS PROPOSALS

A1333

This activity encompasses all actions in assessing the

formal response to the solicitation or tender, prepared by

either a contractor or another government entity

responding to the solicitation, and in choosing the

successful bidder.RUN CONTRACT

A1334

Activities required to place and operate the contract over

its life time, and, when required, to close it. This will

include assessment of achievement against requirements,

approval of payments, and resolution of issues arising.


27/36


MANAGE DS LC FUNDING

A134

Acquire, allocate, and account for the funds needed to

provide the DS through life. This is assumed to include

the task of forecasting and tracking DS Life Cycle Cost.

External data will be needed for this including cost of

the operator/users and their training. The extensive

feedback needed to capture costs and expenditure details

over the life cycle are not shown in this model.MANAGE HUMAN

RESOURCES A135

Plan, organise, monitor and control, the provision of

human resources for DS program lifecycle.

MANAGE DS INFORMATION

A136

The act of constantly monitoring and updating both the

technical data requirements and the database support

structure that provides the through-life support the

Defence System.

DEVELOP IM PLAN

A1361

Define the program Information and IT-infrastructure

requirements based on an analysis of user needs over the

life cycle. Develop a plan for capturing, controlling and

delivering the required information to users.

ESTABLISH & OPERATE

Program SDE A1362

Design, acquisition, deployment and use of a Shared

Data Environment for the DS. (See NCOPS)

PROVIDE INFORMATION

SERVICES A1363COMPARE ACTUAL

SYSTEM STATE &

PERFORMANCE WITH

REQUIRED

A14 The comparison of actual system state and performance

with that required by the Current Requirement, Business

Directives and Operational Program to identify the need

for changes. This comparison addresses both technical

and business aspects (e.g. will/can the aircraft achieve

the specified range; are in-service maintenance costs in

line with approved budgets, is the actual configuration in

line with that needed to meet the Current Requirement

and Operational Program? ) This comparison will

identify the need for any changes to the Defence System

itself, or to the DS Program, required to address the

VMN. (Changes to the VMN are outside the TLBM)

The comparison may lead to the raising of a Changes

Proposal, affecting either the DS Design or the DS

Program. Proposals may also be generated to change

the Current Requirement, either directly or after

assessing and rejecting the viability of a Proposed

Change to the DS. This activity will also address the

acceptability or otherwise of requests for waivers or

concessions for components which fall short of the

design intent. The activity also generates a report on

the performance of the DS and the DS Program

(Perf.Rep) and issues advice to Operators over specific

design limitations applicable as a result of shortfalls

(e.g. a power restriction applies until a suspect

component is inspected).


28/36


OBTAIN DS A2 The activities necessary to define, design, procure,

manufacture and test a new or improved DS capability

to meet the Current Requirement. The activity includes

the assessment of conceptual options, procurement of

systems via integrated product development, the

conducting of total system testing prior to making the

operational system available for first operationaldeployment. It also includes the refurbishment systems

and re-testing of Systems or components returned for re-

cycling from the Operational environment and the

establishment of a Support Capability which can sustain

the operational system in use.

DEVELOP DS A21 Develop possible realisable solutions to the Current

Requirement, to the appropriate level of detail. This

activity will be repeated to an increasing level of detail

as the solution evolves from a proposed DS concept to a

full definition of the DS to be produced. The DS

solution must address the intended operational system

and the support management arrangements needed to

sustain the system in use, including any special-to-type

tools, facilities and support equipment needed for thispurpose.

DEVELOP CONCEPTUAL

OPTIONS A211

The action taken to review the operational threat and

Mission Need to identify and evaluate potential

alternative solutions. The activity applies to both the

system and its support, establishing in-service goals for

operational implementation of the proposed Defence

System solution. The evaluation will address cost,

schedule, performance, supportability, and technological

feasibility to select the conceptual solution, or options to

be offered in response to the defined operational need.

DEFINE DS

A212

The functional design of the Defence System includes

analysis of the design features needed by the subsequent

manufacturing, transportation, use, support, and disposal

processes. From this analysis the required functionality

of systems, sub systems and components is derived, for

both the operational system and the support system, and

responsibility is allocated to the various elements within

the functional architecture, for meeting all aspects of the

overall system of performance, as defined by the Current

Requirement. Acceptance criteria for test (A23) and

evaluation (A37) are also defined. This activity also

decides what items can be bought in from suppliers (as

Goods and Services from Others), an which still require

to be designed.

ENGINEERING DESIGN

A213

The detailed engineering design activities to arrive at a

product model for the DS and its support equipment and

simultaneously define the manufacturing, refurbishmentand disposal processes. The task includes the design of

the deployed system and of any special to type support

tools, equipment and facilities.


29/36


FAILURE ANALYSIS

A214

Analyse failure modes, effects and criticality to define

product anomaly, criticality, causes/effects and

compensating provisions. Provide diagnostic and

troubleshooting recommendations. Predict the

expected frequency of failure and calculate expected

reliability.

DESIGN THE SUPPORTSYSTEM A215

Create the procedures and data needed to provide anoptimised support capability for the DS, to deliver the

readiness, sustainability and availability required from

the operational system, at least life cycle cost. This

activity will create procedures for operating, servicing

and maintaining the Operational System, including

diagnostics and post repair tests. It will define

intentions for managing the initial and ongoing supply of

materials, components and spares required for

manufacture and in-service use. This includes definition

of the intended spares holding and the development of

procedures buying, holding, issuing and accounting for

stock. Decisions on the form of stock management (e.g.

unique to the DS, by an Armed Force, by National or

NATO stock systems) and undertaking any screeningand codification activities form part of this task. It will

develop policies and procedures for the return,

assessment, refurbishment and disposal of items no

longer required. It will develop policies and

procedures for supplying operators and maintainers with

the information they require to perform operating,

servicing and maintenance tasks, deciding whether to

achieve this by components built into the equipment, by

access to the SDE, by digital storage medium or on

paper. It will also generate or re-format any additional

data required for support, which is not already available

from the SDE. It will define what feedback is needed

from operators and maintenance staff to optimise the

performance of the support system, and develop

procedures for data collection and analysis. It will

establish training requirements for operators and

maintainers. The support system design activity will

also identify requirements for special-to-type tools,

facilities, test and training equipment, the design of

which is undertaken in A214.

PREDICT LIFE CYCLE

PERFORMANCE A216

Task of predicting the expected performance of the DS

in regards to all aspects of the Current Requirement and

Business Directives. This includes prediction of system

capability, life, availability, readiness and life cycle cost.

PRODUCE DS A22 The fabrication, assembly and production testing of the

Operational DS, of related spares and components; of

engineering test models, breadboards and prototypes andof associated special-to-type tools, facilities and test

equipment. The re-furbishment of items returned from

service use to the original production standard, or as

otherwise defined, is also included in this activity as it

requires similar facilities and data.


30/36


CONDUCT TESTING A23 Process of measuring the performance of all DS

components (including software, hardware, and human

interface) for compliance with Current Requirements in

accordance with the Test Definition and Test Plan. The

Testing function also applies to the supportability

features, processes and equipment (e.g. a test of the

Maintenance Procedures and Tools). Normal productiontesting, applied routinely to each new item, is included

within A22 (Produce).

DEPLOY DS A24 The activities needed to, receive, process, and transport

new Operational DS, support equipment or components,

from the manufacturing environment to the location from

which they will normally operate, or be stored. NOTE:

the operational activity of deploying a DS from its

peacetime base to another operational environment, as

part of a Task Force, is not included in the TLBM as this

requires integration with other systems and activities

beyond the scope of this model.

SUPPORT THE USE of the DS A3

PLAN SUPPORT A31 Decide what work to do, in what order, on the systems

awaiting support action. The plan will includespecification of the required configuration for each

individual system. The Plan Support activity also

generates a requirement for items to be purchased for

use in support activities.

STORE TRANSPORT &

ISSUE ITEMS

A32 The storage and issue as required of items needed for

maintenance or to support the DS on operational use

MAINTAIN, UPDATE &

PROVIDE FEEDBACK

A33 Perform the work needed to restore the DS to the

condition required for the next intended operation

(except for O&S tasks), by diagnosing, repairing, testing

and calibration the item in accordance with the Core

Product Data and Support Information. Implement

updates and configuration changes in accordance with

Required Support Actions. Provide maintenance

feedback on findings, action taken and issues arising.

Update current configuration to reflect work done.

O&S TASKS A34 (Non maintenance) activities needed to prepare the

system for operations e.g. fuelling, tow from hanger,

empty waste tanks etc.

MANAGE FACILITIES A35 Activities needed to sustain the "special to type"

facilities and tools in a fit for use condition.

TRAIN SUPPORT STAFF A36 [IEEE Std 1220-1994] The tasks, actions, and activities

to achieve and maintain the knowledge and skill levels

necessary to efficiently and effectively perform

operations, support and disposal.

CONDUCT EVALUATIONS A37 The evaluation of a DS operational and support

capabilities based on both predetermined criteria and

needs evolving from operational experience. Theseevaluations include analysis of existing data derived

from operations and the collection and analysis of data to

support a particular need. Conclusions and

recommendations are documented as evaluation

findings.


31/36


DISPOSE or RECYCLE A4 Activities related with the retired Defence Systems and

DS components for disposal or refurbishment. Items for

refurbishment or recycling are returned to A2. Items no

longer needed are disposed of. Asses the state of the

item, decide whether to refurbish for use within the

program, make it available for use by others (sell or re-

allocate to other program) or scrap as waste.


32/36

TLBM 6 .00

ICOM Repo rt

Arrow Name Arrow Definition

Acq Strat An acquisition strategy details the requirements, approaches, andobjectives of a Program Acquisiton Strategy

Activities to be contracted Definition of the tasks to be undertaken, and services to be provided bycontract.

Allocated Manpower Allocation of available manpower resources to organisational units andplans for providing trained people

As-built Config The full configuration definition of each DS post production or re-furbishment.

As-maint Config The configuration definition of the DS following maintenance. This

definition would also include the reporting of configuration problems and

anomalies.Available Funding Actual funds, available to the DS program, after approval and release by

the Financial Management function.Budget Req Defence System specific requests for funding, in the form of budget

requirement requests to the external authorities responsible for theprogram Business Directives.Business Directives Program specific business requirements and constraints placed on the

LC-owner by his tasking body, matched by appropriate resources.Resources are assumed to be defined in terms of an allocated Budget for a

DS, based on annual cash limits plus a target or acceptable range forwhole Life Cycle Costs. These provide the input from which the programgoals, priorities and budget are derived. This should include anydirectives for international co-operation.

CALS Strategy

Change Impact Assessment of the technical implications of a proposed change to the DS,

or of an "off design" condition, arising in production or in-service use.Change Proposal A proposed change to the DS or the DS program to correct a state or

performance shortfall. This may include a request from within the DSprogram to change the requirement itself.

CM Strategy Strategy, Policies and plans for achieving adequate control of DSconfiguration through life

Contract Dir. Instructions to staff on actions they need to take in regard to DScontracts. This may include supplying information, checking progress, orassisting the contractor to perform elements of the work.

Contract Information Req The information requirements to be included in DS program contracts.Contract StrategyContracts Contracts and/or Invitations to Tender for the provision of goods or

services to the DS ProgramContracts and Requests Contracts or Request for action from organisations or entities not

directly controlled by the DS Life Cycle Owner. This may include:contracts to industry, training requirements, request for changes to otherDS, facility change requests, proposed changes to imposed, constraints

including requests for additional funding. proposed new common tools.

Core Product Data Information to define and describe items, components, assemblies andsystems to the level needed by those who will operate and support thesystem in-service. It includes the identity, version, definition, properties,classifications and characteristics of all parts likely to be exchangedduring the in-service life and the assembly structure of the DefenceSystem (the Design Configuration) including permitted options and

variants.


33/36

Arrow Name Arrow DefinitionCurrent Req Current Requirement The latest approved statement of the functional and

interface requirements for the DS, including the definition of theintentions and requirements for operational use and support (Use Study).The Current Requirement is also assumed to reflect approved changes.

(Instructions to implement changes, either to the system design, or tospecific systems, are part of Programme Directives). The level of detail in

the Current Requirement will grow over time. It will range from theValidated Mission Need, at the program outset, to the full technicalspecification of the product to be produced or in service. The Current

Requirement is assumed to be managed as one or more CIs, in its ownright. The history of requirement changes will be maintained over time,and made available, where needed, through the SDE.

Def. Pol.& StdsDisposed Items All, or any part of a DS, or waste it has generated, which are no longer

required for operations and is to be removed from DS Program control.

DS Concept Selected Concept, or Concepts, to be further developed into a full design.DS Data to Others All data relating to the DS required by external authorities. This

includes: reports on achievement v targetDS for Deployment A new DS or component ready for initial deployment.

DS needing support The Operational Defence System requiring support, as returned fromoperations.

DS ready for Ops DS ready for OperationsEval Def Evaluation Definition: The criteria and specific manner in which

evaluations will take place.

Evaluation Findings The documented results of an evaluation of a DSExisting Business Info Existing Business Information: Data, needed by the LSA activity, from

external sources. This may include government-provided list of approvedLSA tools, standard supportability data such as labour costs at eachechelon, existing documented historical data, etc.

Existing Infrastructure Facilities Systems Tools

External Data Data from other Systems or Authorities, needed by the DS program.Other DS program Schedules, Policies, WBS, Budgets and Organisations(A131/2/3), Data on other Contracts and Contractors (A134), Personnelinformation (A135), extent of and experience with existing Info Systems

(A136) Data needed for Support Design (A215) including historical

data, predecessor data, independent study data, health, safety orenvironmental data and data on existing tools, facilities, components andparts. Current locations holdings of other equipment and spares (A24)

Feedback fm Maintenance Feedback fm Maintenance Feedback of information arising from

maintenance activities. This may include reporting of defects found,actions taken, resources used and proposals for design or support systemchanges. It must include the Current Product Structure (Configuration)post maintenance.

Feedback fm Ops Feedback from Operators Ops History Survey Results State, Failures,

Deficiencies Changes madeFinancial Implication Report of the financial implications of the program WBS, including

proposed changes.

FMECA Data Description of possible failure modes for the DS, with their likelyconsequences and frequency of occurence.

Functional Architecture An arrangement of functions and their sub-functions and interfaces(internal and external) that define the execution sequencing, conditionsfor control of system data flows, and the allocation of performancerequirements to each functional element within the operational andsupport systems, to satisfy the overall system requirement. Support

influence on design is achieved through the allocation of requirements in

the functional architectureGoods & Services fmothers

Goods and Services from others


34/36

Arrow Name Arrow DefinitionILS Strategy The formal planning document for the integration of the activities

concerned with logistics support. It is kept current throughout the projectlife. It sets forth the concept of operational support, provides a detailedILS programme to fit with the overall programme and results in the

necessary ILS information required by decision making bodies to makesound decisions in the system development and production.

IM Plan Plan to manage information over the LCIn Service Goals A statement of general utilisation intentions for a Defence Systemincluding reference to national or co-operative logistics and training

arrangements.Information Services Provision of Information services which cannot be provided directly

through the SDE itself e.g archiving, retrieval of historic records, specialreports, new applications, new hardware, help desk services etc.

In-Scope EvalFindings In-Scope Evaluation Findings: Evaluation findings that indicate a

requirement to change Operational Support Instructions or Operational

Support Requirements that do not effect existing system plans orstrategies.

Inst to OpsInvitation to Tender A formal request for a proposal from a contractor upon which a contract

for goods or services could be based. It includes, either directly or byreference, all of the technical, commercial and legal information needed

to establish and operate a successful contract.Items for Rfb Items for Refurbishment Items removed from operational service and

returned for reconditioning or repair

Items for TestItems for Use Spares and other consumables supplied for incorporation into the main

equipment, (this includes the "on board stock" where appropriate)Laws & Gov Policy Relevant Laws and regulations from beyond the Defence environmentLC Strat & Pol. The set of documents which provide the DS program team with policies

and strategies for managing the acquisition and support of a DS in a

consistent manner over its lifecycle. It includes: Acquisition Strategy(Acq Strat) Quality Management Plans (ImpPlan) ILSPlans

Maintained DS DS after completion of the maintenance tasks, awaiting preparation fordeployment on mission

Mfr & Rfb data Manufacturing and refurbishment data: information needed to

manufacture, refurbish or dispose of the DS and its associatedcomponents

Op ProgOrg Structure

Perf Rep The currently achieved (or predicted) performance of the DS in relationto Current Requirement and Business Directives, highlighting any actualor expected shortfalls in technical or financial performance.

Predicted LCC Prediction of the expected Life Cycle Cost of the DSPredicted Perf

Prg Dir Program Directives: Program management directives generated withinthe DS Program, issued to set up the DS Organisation and to control thework of staff who can be tasked directly by the DS Life Cycle Owner.

(other resources are obtained or tasked through Contracts and Requests)Programme Directives include the Organisational Structure and approved

budgets, WBS, program plans, "make or buy" plans, instructions to buy,change authorisations and all other forms of instruction used to makethings happen on the program. The Program Directives alsocommunicate the specific policies, procedures and plans established bythe DS program and approved by the Life Cycle Owner.

Proc Spec Technical or functional definition of Items to be purchased, to the level of

definition needed to enable contract action to proceed. Note: Instructionto place orders for specific Items of Supply are provided from twosources: the Program WBS, for initial acquistion or from Plan Support,for re-supply, as "Required Items".


35/36

Arrow Name Arrow DefinitionProgram Schedule Plans showing what activities have to be performed when, to meet DS

Program requirements.Program SDE The hardware, software and communications and information

infrastructure needed to enable participants in DS program to access the

information they require to conduct the business processes illustrated bythis TLBM.

Program WBS Definition of the activities to be performed to deliver (or dispose of) asuccessful DS. This may take any form. Typical outputs would include aformal work breakdown structure, a Task list or a series of Service Level

Agreements for ongoing tasks. Changes to the DS and to the workprogram are initiated by changes to the Program WBS.

Project Pers Project Personnel Staff from industry, government or the Armed Forceswho is supplied to work on the programme, potentially as part of a MultiDisciplinary Team or Integrated Project Team. Will include operational

user on temporary deployment to the DS program to provide their

experience or evaluation skills. People supplied as a resource are trainedand educated adequately except in regard to the DS itself.

QA StrategyReq Config The required configuration state of a specific DS to be achieved by the

maintenance activity. This would define the desired operationalconfiguration required for a particular mission (e.g. fit the long range

fuel tanks), and indicate what approved changes/modifications were to beincorporated during a specific maintenance session.

Reqd Feedback

Requests for Assistance Requests for assistance from or action by parties beyond the control ofthe DS Life Cycle Owner (e.g. the owners of other DS, the ArmedForces, External training authorities, The DoD etc)

Required Items The identity, quantity and required delivery details for purchased itemsneeded to support the use of the DS.

Returned Items

Risk Man StrategySDE Req. Requirement Statement for the Program SDESelected ContractorSpares & Components Spares and components obtained for use in support activities.

Support Equipment

Requirements

Requirements for special-to-type support equipment, tools, training

equipment and facilities required to support the DS.Support Info Support information provides the directives and data required to support

the DS in-service. It includes: maintenance policy and maitenanceprocedures including, task descriptions and resources needed (skills,

tools, parts etc); diagnostic, callibration and test procedures; supplysupport policy and procedures e.g. supply policy, stock holdings, initialstock buy, stock management and provisioning procedures, provisioningdata, codification data return, assesment, re-furbishment and disposalinstructions.

Support Plan Instructions (short term) and plans (longer terms) defining the work to beundertaken on specific DS or DS components requiring support.

Test Def Test Definition: Test objectives which are based on DS specifications and

program requirements that define the parameters on which thequalification and quality tests are based.

TestFindings The results of comparing actual results with identified performance,functional, and logistic specifications.

Tools & Facs. The special-to-type tools, test equipments and facilities created for theDS.

Trained People

Trg Req Training Requirements A specification of the training needed by the

operators and maintainers of the DS, plus a request to the trainingauthorities to provide the necessary training in a time scale required bythe program.


36/36

Arrow Name Arrow DefinitionUsage&support Policy Constraints, requirements or policy guidance relating to the operation or

support of the DS in service, placed on the program by the known orpotential users of the System

Users The designated user of the proposed system (maintainers, operators,

repairmen, commanders, etc.), provided to contribute to, or assess theevolving product and support design.

Validated Mission Need A statement based on a mission analysis, identifying in broad outline aquantitative or qualitative operational deficiency that cannot be solvedsatisfactorily with existing forces or equipment. The mission need is

constantly re-evaluated throughout the life of the Defence System andmay change over time. The VMN will also define any requirements forinteroperability with other DS.

nato managing the defence system life cycle cals

Documents