Redefining Supportability

Supportability

That characteristic of a system and its support system design that

provides for sustained system performance at a required readiness

level when supported in accordance with specified concepts and procedures.

Supportability

That characteristic of a system and its support system design that

provides for sustained system performance at a required readiness

level when supported in accordance with specified concepts and procedures.

Supportability: Supportability as defined herein (a shift in the paradigm) is a metric that addresses every support event within the domain of the Integrated Logistics Support Elements, with respect to support event frequency, event duration, and event cost. This is reflected in a composite, quantitative and qualitative characteristic of the supported system (project) to meet specified operational requirements for its intended life cycle, and is optimized for Total Ownership (TOC).

Supportability: Supportability as defined herein (a shift in the paradigm) is a metric that addresses every support event within the domain of the Integrated Logistics Support Elements, with respect to support event frequency, event duration, and event cost. This is reflected in a composite, quantitative and qualitative characteristic of the supported system (project) to meet specified operational requirements for its intended life cycle, and is optimized for Total Ownership (TOC).

Supportability Approach must Emphasize Support EventCharacterization Beyond Traditional Operational Availability (AO)

TRADITIONAL APPROACH NEW APPROACH

Ma = SUPPORTABILITY (S)?

AO

OT + ST

OT + ST + TCM + TPM + A/LDT=

WHERE: TOTAL OPERATING TIME DURINGA SPECIFIC INTERVAL

TOTAL STANDBY DURING ASPECIFIED INTERVAL

TOTAL CORRECTIVE MAINTENANCETIME DURING THE SAME SPECIFIEDINTERVAL

TOTAL PREVENTIVE MAINTENANCETIME DURING THE SAME SPECIFIEDINTERVAL

TOTAL ADMINISTRATIVE ANDLOGISTICS DOWNTIME DURING THESPECIFIED INTERVAL

• HENCE, AO ADDRESSES R&M ONLY • HENCE, MATERIAL AVAILABIITY REQUIREMENTS ADDRESS ALL EVENTS

• GIVEN: Ma

OT

ST

TCM

TPM

A/LDT

=

=

=

=

=

OT + ST

(?) + OT + ST + TCM + TPM + MLDT=

MISSING EVENTS

- SERVICING- RECONFIGURING-GROUND/CARRIER HANDLING-SET UP AND TEAR DOWN

- COMBAT OPERATIONS- LAUNCH ACTIVITIES- MISSION VARIATIONS- OTHER NON R&M ACTIONS

• AND: S = {OPERATIONAL SUITABILITY, READINESS,SUSTAINABILITY, SURVIVABILITY, MOBILITY,

LIFE CYCLE COSTS, AO} Events

• BECAUSE: S IS NOT ADDITIVE BUT CONSISTS OF FINITE,SIMULTANEOUS SUPPORT EVENTS FROMALIGN TO WINTERIZE (500+ EVENTS DEFINED)

SUPPORT PLANNING BASELINE(PEACETIME OPERATIONS)

DESIGN FOR S BASELINE(WARTIME OPERATIONS)

• WHERE:

f = SUPPORT EVENT FREQUENCYd = SUPPORT EVENT DURATIONc = SUPPORT EVENT COST

S = F (f, d, c) IS A CHARACTERISTIC OF DESIGN

VSTHE PROBABILITY THAT, WHEN USED UNDER STATED CONDITIONS, A SYSTEM WILL OPERATESATISFACTORILY AT ANY TIME. AO CAN BEEXPRESSED BY THE FOLLOWING FORMULA:

Supportability (S) – Addressing Integration

• The Supportability Metric addresses EVERY support event as a DESIGN DRIVEN attribute, with respect to support event frequency, event duration, and event cost.

• This approach reflects an integration of quantitative and qualitative characteristics that meet specified Operational Requirements, Total Ownership Cost (TOC) goals and Performance Based Logistics (PBL).

• What is Supportability (S)?• S = Supportability is the integrating function for all “ilities” with regards to design

characterization, and is reflected by design features resulting from Supportability Design-to Requirements (SDTRs)

• S = F(f, d, c) provides the integrating function

f = support event frequency (includes reliability driven events)d = support event duration (includes maintainability driven events)c = support event cost - support system cost per event (e.g. all ILS elements – facilities,

training, transportability, etc.)

• Supportability is at its Optimum when S approaches “minima”, or when the system is self sufficient at least cost (therefore best value).

• Supportability can be expressed in terms of Total Ownership Costs (TOC) as shown below.

• Supportability Component of TOC: S TOC (f x d x c)

The Supportability Engineering “Top Ten” Steps

1. Establish the Project Baseline with Systems Engineering (SE)2. Review statistical supportability drivers [S = F(f,d,c)] of Comparative

Systems using Pareto Analysis3. Review the predecessor or comparable system’s technical data4. Interview maintenance techs with SPECIFIC questions 5. Develop detailed lessons learned from steps 3 & 4 – PBL IPT.6. Integrate technical data, statistics, and interviews - develop initial

SDTRs linked to the S function.7. Optimize SDTRs

CUSTOMER criteria Technological opportunities Explore with Design Team members and Producibility Engineers to

ascertain design characteristics.8. Finalize SDTRs - use “specification language”9. Update or negotiate SDTRs with SE and Designers.10. Incorporate SDTRs into the “System Specification” or ECP

The support scenario must focus on an attempt to eliminate the logistics infrastructure and reduce total ownership cost (TOC), which includes Depot and contractor support. PBL is applied to what’s left.

Comprehensive Supportability Design-To Requirements (SDTRs)Reduce Event Frequency, Duration and Cost to Meet System

Spec

• SUPPORTABILITY (S) ELEMENTS- OPERATIONAL SUITABILITY

- READINESS

- INFLIGHT SUSTAINABILITY

- MOBILITY/TRANSPORTABILITY

- LOGISTICS LIFE CYCLE COST

- AVAILABILITY (A0)- RELIABILITY

- MAINTAINABILITY

- OPERATIONAL SUSTAINABILITY

• SUPPORT A

CTIONS

- GROUND H

ANDLING

- SERVIC

ING (F

UEL, OIL

...)

- ARM

AMENT &

WEAPONS

• LOADIN

G

• UNLOADIN

G

- RADIO

/RADAR F

REQ CHANGES

- HOT/C

OLD WEATHER K

ITS

- BALLAST L

OADING/U

NLOADING

- MIS

SION R

ECONFIGURATIO

N

- TAPE IN

STALLATION (P

ROMS)

- CHAFF L

OADING/U

NLOADING

- PRESERVATIO

N

- DEPRESERVATIO

N

- ENGIN

E RUNUP IN

TEST C

ELL

- INSPECTIO

NS (MAJO

R, MIN

OR)

• OP

ER

AT

ION

S

- A

LE

RT

TIM

E

- R

EA

CT

ION

TIM

E

- F

LE

XIB

ILIT

Y

- C

OM

BA

T M

ISS

ION

S

- T

RA

ININ

G M

ISS

ION

S

- F

ER

RY

MIS

SIO

NS

- S

PE

CIA

L O

PE

RA

TIO

NS

- A

US

TE

RE

FIE

LD

(3r

d W

OR

LD

)

- E

QU

IPM

EN

T E

MP

LA

CE

ME

NT

(S

ET

-UP

)

- E

QU

IPM

EN

T D

ISP

LA

CE

ME

NT

(T

EA

R-D

OW

N)

- N

AV

Y O

PE

RA

TIO

NS

(O

CE

AN

, S

UB

-SE

A)

Traditional R & M

RELIABILITY & MAINTAINABILITY - MAINTENANCE • PREVENTIVE • CORRECTIVE - SUPPLY DELAY - ADMIN DELAY(128 PARAMETERS FROMMIL-STD-721C)

OPERATIONSGENERALSUPPORTACTIONS

SELECTED SET OFSDTRs

SUPPORT EVENTS• 500+ PARAMETERS• DESIGN TO ALGORITHMS

DESIGNER

TAILORED SDTRs

SYSTEM SPEC

Supportability Design-to Framework

How Should We Convey Supportability Requirements?

Supportability Design-to Requirement (SDTR): “The directional control computer shall contain BITE circuitry that tracks within the full range of control surface positions, and shall be impervious to variations in system ground levels (±0.5v DC).”

The Objective: Let’s make it easy for the designer by making supportability transparent through simple and direct specifications oriented to PBL.

• FAILURE - RELEVANT - NON-RELEVANT - CHARGEABLE - NON CHARGEABLE

95% BIT

WHAT THE….???

OR THIS:

MTTR

Mc

Mp

MTTS

MTMBA

DMMH

FMECA

MTBF

R GROWTH

DIRECT TIME

UPTIME

DOWNTIME

RTOK

FALSE ALARM

Ai

A a

Ao

Supportability is the “Forcing Function” that Addresses the Elements and Sub-Elements Simultaneously with SDTRs

Algorithms can Define Supportability (S) Design Characteristics

[( TH j1 Kb

± ADJ ) 61* SE(WTb) 9

1 E(WTb)* ]f{[( TH j

1 Kb± ADJ ) 6

1* SE(WTb) 91 E(WTb)* ]d

[( TH j1 Kb

± ADJ ) 61* SE(WTb) 9

1 E(WTb)* ]c } BASELINE

Then, S(f, d, c)OPT=

[( TH j1 Pb

± ) 61* SE(WTp) 9

1 E(WTP)* ]f{ 1nTHL

[( TH j1 Pb

± ) 61* SE(WTp) 9

1 E(WTP)* ]d1

nTHL

[( TH j1 Pb

± ) 61* SE(WTp) 9

1 E(WTP )* ]c } PROJECT1nTHL

IF S = Supportability and S = F(f, d, c)f = support event frequencyd = support event durationc = support event cost

S is at its optimum when S approaches “0” with respect to f, d, and c,

Correction of baseline value or historical dataBaseline, existing or predecessor systemSupportability elements - major1) Operational suitability2) Readiness3) In-flight sustainability4) Survivability5) Operational sustainability6) Mobility/transportability7) Reliability and maintainability8) Life-cycle cost

9) Availability (AO)

Engineering change proposalSelection range of baseline parameter valuesParameter reflecting historical dataParameter baseline from comparative,historical WUCsUnique set of SDTRs , that address baseline system, LRU, SRUSelection range of SDTRs that operate (+ or -) on the jTH set of baseline values off, d, or c.Supportability at optimum state whensupport events approach “0”Supportability design-to requirements

Supportability elements - subordinate1) 01- 09 support general codes2) Preventive maintenance3) Corrective maintenance4) Resource consideration5) Personnel requirements6) Support equipment and facilitiesWeighted or relative importance of elements- baselineWeighted or relative importance of elements- projectWork unit code reflects system data definition for historical data collection or for new systems

ADJ =

B or b =

E =

ECP =jTH =

K =

Kb =

L =

nTH =

S (f, d, c) OPT =

SDTR =

SE =

WTb =

WTp =

WUC =

andWhere:

Comparison baseline

The new project

The WBS - Beyond Earned Value Reporting

•The Work Breakdown Structure (WBS) is important as an Information Node

•Take Advantage of the WBS to nestle your •Comparative Data•Statistical Information

•Use the WBS as the Basis for Design-to Requirements

•Expand the WBS Dictionary to include the way you actually plan Work

Lessons Learned Linked to Requirements [P, S = F (f,d,c)] AreEmbedded In the Work Breakdown Structure (WBS)

PRODUCIBILITY ELEMENTS

ASPECTS OF D

ESIGN

SPECIFIC

ATIONS A

ND STANDARDS

MATERIA

LS SELECTIO

N

PROCESS DEFIN

ITIO

N

ENVIRONM

ENTAL REQUIR

EMENTS

GENERAL INSPECTIO

NS

TESTING

SAFETY CONSID

ERATIONS

CLEANING R

EQUIREM

ENTS

INFORM

ATION N

ODES

PRODUCIBILITY SUBELEMENTS

• DOCUMENTATION CONTROL & ADMINISTRATION

• ASSEMBLY AND TEST

• PIECE PART/MINOR FABRICATION

• INTEGRATION AND PERFORMANCE CHECKS

• PERSONNEL CHARACTERISTICS

• FACILITIES/EQUIPMENT/TRANSPORTATION

Producibility and Supportability Information Nodes/Cells reside in the WBS • Basis for design-to requirements • Provide automated information management Access Retrieval Use Cell division/multiple applications Traceability Data base management Artificial intelligence information clusters

SUPPORTABILITY ELEMENTS

OPERATIONAL S

UITABIL

ITY

READINESS

INFLIG

HT SUSTAIN

ABILIT

Y

SURVIVABIL

ITY (

COMBAT S

UPPORT)

OPERATIONAL S

USTAINABIL

ITY

MOBIL

ITY A

ND TRANSPORTABIL

ITY

LIFE C

YCLE COST

OPERATIONAL A

VAILABIL

ITY

RELIABIL

ITY/M

AINTAIN

ABILIT

Y

INFORM

ATION N

ODES

SUPPORTABILITY SUBELEMENTS

• GENERAL SUPPORT

• CORRECTIVE MAINTENANCE

• PREVENTATIVE MAINTENANCE

• RESOURCE CONSIDERATION

• PERSONNEL CHARACTERISTICS

• SUPPORT EQUIPMENT & FACILITIES

Information management, knowledge capture, and a dynamic systems engineering environment result in producible and supportable products.

Cell Characteristics Index RequirementsDesign-to Data Base

• Producibility unique AL Film, metalized • Supportability unique 38 Service center • Common/shared 37 Mounting and positioning

System Engineering Process

DesignerNew System • Producible • Supportable

Trade Studies

PVC/283Z/194a

PRODUCIBILITY (P ) SUPPORTABILITY (S )

WBS

WBS

Information Nodes

The WBS - Beyond Earned Value Reporting

•The Work Breakdown Structure (WBS) then:

•is structured to view Work Unit Codes as SDTRs

•can be monitored in scheduling tools (Microsoft Project) to track status of design progress to SDTRs

•which allows critical path identification of SDTRs

•Makes design appraisals more accurate and efficient

•Is used for Information Management•Access to your data•Retrieval of important information•Multiple applications of your knowledge•Generate schedules based on the WBS content•Requirements Traceability (DOORS, SLATE, etc.)•Data Base Management•Knowledge Clusters•Etc……

What about Producibility?

The Producibility Design-to

Requirements (PDTR) Development Process

• New Design Related Metrics

• Integrating Producibility and Supportability

PRODUCIBILITY DEFINED

Producibility elements - major

1) Aspects of design2) Specifications and standards3) Materials selection4) Processes definition5) Environmental requirements6) General inspections7) Testing8) Safety considerations9) Cleaning requirements

AND THIS

Producibility element - subordinate

1) Documentation control and administration2) Piece part/minor fabrication3) Assembly and test4) Integration and performance checks5) Personnel characteristics6) Facilities/equipment/transportation

•Again, just as in Supportability, we compute:

Weighted or relative importance of elements for system being replaced or modified - Comparison BaselineWeighted or relative importance of elements that we want to see in the new system- The New Project

PRODUCIBILITY DEFINED(surprise - same as Supportability!)

• Producibility is defined as :

• The frequency of the manufacturing event where f = manufacturing event frequency;

i.e., how often will it occur?

• The duration of the manufacturing event where d = event duration; i.e., how long is the event?

• The cost of the manufacturing event where c = event cost;

I.e., how much will it cost?

P IS AT ITS OPTIMUM WHEN P IS MINIMIZED OR WHEN PRODUCTION IS MOST EFFICIENT, EASY TO ASSEMBLE, AND AT LEAST COST

Producibility Integration Process

•Evolving designs are optimized for producibility

• Producibility Design-To-Requirements (PDTRs) provide comparison basis against Predecessor• PDTRs serve as guidelines during the Technology Insertion Process to ensure technology

does not proliferate producibility risks

•Maximize producibility/supportability synergism

•Simulate factory flow optimization after PDTR implementation to determine PDTR effectiveness

•Incorporate PDTRs into the Technical Data Package so as not to lose them when you create a build package for re-procurement

A disciplined, systematic approach enhances Producibility Implementation

Algorithm Defined Producibility (P) Design-to RequirementsAssure Team Member Focus >>> Reduce Production Events

POWER SOURCESELECTRO-MECHANICAL& HARNESS

ASSEMBLYAND TEST

MACHINE SHOPAND PLATING

PRODUCIBILITYENGINEER

• PDTR OPTIMIZATION• TECHNOLOGIES INSERTION• TRADE STUDIES• INDEPENDENT RESEARCH & DEVELOPMENT (IRAD)

OTHER ORGANIZATIONS

INTEGRATIONAND TEST

FABRICATION &PRECISIONMECHANICALASSEMBLY

PRODUCTIONPLANNING ANDCONTROL

HYBRIDMANUFACTURING

PRODUCIBILITYMANAGER

SYSTEM ENGINEERING

DESIGN ENGINEERING

PRODUCIBILITY ELEMENTS

ASPECTS OF DESIGN

SPECIFICATIONSAND STANDARDS

MATERIALS SELECTION

PROCESS DEFINITION

ENVIRONMENTALCONSIDERATIONS

GENERAL INSPECTIONS

TESTING

SAFETY CONSIDERATIONS

CLEANING REQUIREMENTS

ALGORITHMSP = {((((±JthPS...)})

[( TH j1 Kb

± ADJ ) 61* SE(WTb) 9

1 E(WTb)* ]f{[( TH j

1 Kb± ADJ ) 6

1* SE(WTb) 91 E(WTb)* ]d

[( TH j1 Kb

± ADJ ) 61* SE(WTb) 9

1 E(WTb)* ]c } BASELINE

P(f, d, c)OPT =

[( TH j1 Mb

± ) 61* SE(WTm) 9

1 E(WTm)* ]f{ nTHL

[( TH j1 Mb

± ) 61* SE(WTm) 9

1 E(WTm)* ]dnTHL

[( TH j1 Mb

± ) 61* SE(WTm) 9

1 E(WTm )* ]c }PROJECT

nTHL

P = Producibility.

P = F(f, d, c)

Producibility is a metric with respect to production event frequency,duration, and cost that reflects composite characteristics of the manufactured system (project), to meet specified quantity, schedule and production standards.

Where:f = manufacturing event frequencyd = manufacturing event durationc = manufacturing event cost

P is at its optimum for the project when P approaches “0” with respect to f, d, and c, or POPT = PBASELINE >>> P PROJECT

B or b =Correction of baseline value or historical dataBaseline, existing or predecessor systemProducibility elements - major1) Aspects of design2) Specifications and standards3) Materials selection4) Processes definition5) Environmental requirements6) General inspections7) Testing8) Safety considerations9) Cleaning requirementsEngineering change proposal

Selection range of baseline parameter valuesParameter, reflecting historical dataParameter baseline from comparative,historical WBSsUnique set of PDTRs analyses thataddress baseline system andgenerate project requirementsProject, new system or major ECPSelection range of PDTRs that operate (+ or -) on the jTH set of baseline values off, d, or c.Producibility at optimum state whensupport events approach “0” (minima)Producibility design-to requirements

Producibility element - subordinate1) Documentation control and administration2) Piece part/minor fabrication3) Assembly and test4) Integration and performance checks5) Personnel characteristics6) Facilities/equipment/transportationWeighted or relative importance of elements- baselineWeighted or relative importance of elements- projectWork breakdown structure reflects system datadefinition for historical data collection orfor new systems

ADJ =

E =

jTH =K =

Kb =

L =

M or m =nTH =

P (f, d, c) OPT =

PDTR =

SE =

WTb =

WTm =

WBS =ECP =

Events range from Anodize to Zyglo

Integrated Supportability and Producibility

Relia

bility

Mai

ntain

abili

ty

Produci

bility

Logistic

s

Other

DESIGNINTEGRATION

DESIGNERDESIGNERS DESIGNERSSYSTEMS

ENGINEERS

ProducibilityP

SupportabilityS

POWER SOURCESELECTRO-MECHANICAL& HARNESS

ASSEMBLYAND TEST

MACHINE SHOPAND PLATING

PRODUCIBILITYENGINEER

• PDTR* OPTIMIZATION• TECHNOLOGIES INSERTION• TRADE STUDIES• INDEPENDENT RESEARCH & DEVELOPMENT (IRAD)

HYBRIDMANUFACTURING

INTEGRATIONAND TEST

FABRICATION &PRECISIONMECHANICALASSEMBLY

PRODUCTIONPLANNING ANDCONTROL

• HUMAN FACTORS• SAFETY

RELIABILITY

MAINTAINABILITY

LOGISTICS SUPPORTANALYSIS

DESIGN• SUPPORT EQUIPMENT• TRAINING DEVICES

SUPPORTABILITYENGINEER

• SDTR INTEGRATION**• SUPPORTABILITY TECHNOLOGIES• TRADE STUDIES• INDEPENDENT RESEARCH & DEVELOPMENT (IRAD)

FIELDSUPPORT

ILS DISCIPLINES/ELEMENTS• MAINTENANCE PLANNING• MANPOWER AND PERSONNEL• SUPPLY SUPPORT• TRAINING• TECHNICAL DATA• COMPUTER RESOURCES SUPT• PKG, HANDLING AND STORAGE• TRANSPORTATION• FACILITIES• STANDARDIZATION AND INTEROPERABILITY

* Producibility Design-To-Requirements (PDTRs)

**Supportability Design-To-Requirements (SDTRs)

FORMAL

INFORMAL

Summary

• Supportability (S) and Producibility (P) may be redefined as the integrating functions, represented by all ILS elements, that addresses all support events related to the design of the system such that Supportability “is a Function of”:

f = Support or Production event frequency

d = Support or Production event duration

c = Support or Production event cost per event

• This function can be used in Pareto analyses of an existing, baseline or comparative system to determine the drivers (f,d,c), which also include MTBF and MTTR.

• Those same drivers are then intentionally reduced by design-collaborated SDTRs for each event.

• Design responses to each SDTR are tracked and assessed for the entire system.

• When (S) and (P) approach minima, the system is said to be self-sufficient and in an ideal state. Support event frequency, duration and cost can be independently defined, and using a life cycle cost model such as CASA, the impact on cost can be immediately determined.

CONCLUSION

• Integrate Producibility and Supportability design-to results into a systems engineering requirement. We must:

• Extend Supportability beyond traditional metrics (MTBF, MTTR, etc.)

• Define NEW metrics: Producibility - Supportability

• Develop requirements written in design-to language

• Address Readiness, Sustainability, Mobility, Transportability and Operational Availability via SDTRs

• Use the Work Breakdown Structure (WBS) as an Information Node for requirements development and tracking

• Support by Design is the Key - through Supportability and Producibility Design-to Requirements (SDTRs and PDTRs), resulting in:

Low Maintenance Man Hours per Flight Hour (Mmh/FH) Reduced Cycle Time Reliability and Robustness Reduced Logistics Foot Print Supportable and Producible Products