Redefining Supportability

1. 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: 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).

2. ? Ma = SUPPORTABILITY (S) S IS NOT ADDITIVE BUT CONSISTS OF FINITE, SIMULTANEOUS SUPPORT EVENTS FROM ALIGN TO WINTERIZE (500+ EVENTS DEFINED) • BECAUSE: • AND: S = {OPERATIONAL SUITABILITY, READINESS, SUSTAINABILITY, SURVIVABILITY, MOBILITY, LIFE CYCLE COSTS, AO} Events S = F (f, d, c) IS A CHARACTERISTIC OF DESIGN • WHERE: f = SUPPORT EVENT FREQUENCY d = SUPPORT EVENT DURATION c = SUPPORT EVENT COST Supportability Approach must Emphasize Support EventCharacterization Beyond Traditional Operational Availability (AO) NEW APPROACH TRADITIONAL APPROACH VS OT + ST THE PROBABILITY THAT, WHEN USED UNDER STATED CONDITIONS, A SYSTEM WILL OPERATE SATISFACTORILY AT ANY TIME. AO CAN BE EXPRESSED BY THE FOLLOWING FORMULA: • GIVEN: Ma = (?) + OT + ST + TCM + TPM + MLDT MISSING EVENTS OT + ST AO = • - SERVICING • - RECONFIGURING • GROUND/CARRIER HANDLING • SET UP AND TEAR DOWN - COMBAT OPERATIONS - LAUNCH ACTIVITIES - MISSION VARIATIONS - OTHER NON R&M ACTIONS OT + ST + TCM + TPM + A/LDT = = = = = TOTAL OPERATING TIME DURING A SPECIFIC INTERVAL TOTAL STANDBY DURING A SPECIFIED INTERVAL TOTAL CORRECTIVE MAINTENANCE TIME DURING THE SAME SPECIFIED INTERVAL TOTAL PREVENTIVE MAINTENANCE TIME DURING THE SAME SPECIFIED INTERVAL TOTAL ADMINISTRATIVE AND LOGISTICS DOWNTIME DURING THE SPECIFIED INTERVAL WHERE: OT ST TCM TPM A/LDT • HENCE, AO ADDRESSES R&M ONLY • HENCE, MATERIAL AVAILABIITYREQUIREMENTS ADDRESS ALL EVENTS SUPPORT PLANNING BASELINE (PEACETIME OPERATIONS) DESIGN FOR S BASELINE (WARTIME OPERATIONS)

3. 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: STOC (f x d x c)

4. The Supportability Engineering “Top Ten” Steps • 1. Establish the Project Baseline with Systems Engineering (SE) • Review statistical supportability drivers [S = F(f,d,c)] of Comparative Systems using Pareto Analysis • Review the predecessor or comparable system’s technical data • Interview maintenance techs with SPECIFIC questions • 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. • Optimize SDTRs • CUSTOMER criteria • Technological opportunities • Explore with Design Team members and Producibility Engineers to ascertain design characteristics. • 8. Finalize SDTRs - use “specification language” • 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.

5. Comprehensive Supportability Design-To Requirements (SDTRs)Reduce Event Frequency, Duration and Cost to Meet System Spec Supportability Design-to Framework Traditional R & M SELECTED SET OF SDTRs RELIABILITY & MAINTAINABILITY - MAINTENANCE • PREVENTIVE • CORRECTIVE - SUPPLY DELAY - ADMIN DELAY (128 PARAMETERS FROM MIL-STD-721C) • SUPPORTABILITY (S) ELEMENTS - OPERATIONAL SUITABILITY - READINESS - INFLIGHT SUSTAINABILITY - OPERATIONAL SUSTAINABILITY - MOBILITY/TRANSPORTABILITY - LOGISTICS LIFE CYCLE COST - AVAILABILITY (A0) • SUPPORT ACTIONS - RELIABILITY DESIGNER - GROUND HANDLING - MAINTAINABILITY - SERVICING (FUEL, OIL...) - ARMAMENT & WEAPONS SUPPORT EVENTS • 500+ PARAMETERS • DESIGN TO ALGORITHMS • LOADING - RADIO/RADAR FREQ CHANGES • UNLOADING - HOT/COLD WEATHER KITS - BALLAST LOADING/UNLOADING - MISSION RECONFIGURATION - TAPE INSTALLATION (PROMS) TAILORED SDTRs - EQUIPMENT DISPLACEMENT (TEAR-DOWN) - CHAFF LOADING/UNLOADING - NAVY OPERATIONS (OCEAN, SUB-SEA) - EQUIPMENT EMPLACEMENT (SET-UP) - AUSTERE FIELD (3rd WORLD) - PRESERVATION - SPECIAL OPERATIONS - ENGINE RUNUP IN TEST CELL - DEPRESERVATION - TRAINING MISSIONS - COMBAT MISSIONS - FLEXIBILITY - FERRY MISSIONS - REACTION TIME - INSPECTIONS (MAJOR, MINOR) SYSTEM SPEC - ALERT TIME • OPERATIONS GENERAL SUPPORT ACTIONS OPERATIONS

6. 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. Ai DOWNTIME FMECA Aa MTMBA 95% BIT MTBF Ao MTTS DMMH FALSE ALARM UPTIME MTTR RTOK Mp R GROWTH • FAILURE - RELEVANT - NON-RELEVANT - CHARGEABLE - NON CHARGEABLE Mc WHAT THE….??? DIRECT TIME OR THIS:

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

8. [ ) j TH 6 9 ] ( ±    Kb ADJ E(WTb) SE(WTb) * * f 1 1 1 [ ) j TH 6 9 ] ( ±    Kb ADJ E(WTb) SE(WTb) * * d 1 1 1 [ ) j TH 6 9 ] ( ±    Kb ADJ E(WTb) SE(WTb) * * c 1 1 1 { [ ) j TH 6 9 ] ( nTHL ±    Pb 1 E(WTP) SE(WTp) * * f 1 1 1 [ ) j TH nTHL 6 9 ] ( ±  1   Pb E(WTP) SE(WTp) * * d 1 1 1 nTHL 1 Algorithms can Define Supportability (S) Design Characteristics IF S = Supportability and S = F(f, d, c) f = support event frequency d = support event duration c = support event cost S is at its optimum when S approaches “0” with respect to f, d, and c, and Where: { Then, S(f, d, c)OPT = Comparison baseline } BASELINE (>>>) The new project [ ) j TH 6 9 ] ( } ±    Pb E(WTP ) PROJECT SE(WTp) * * c 1 1 1 ECP = jTH = K = Kb = Engineering change proposal Selection range of baseline parameter values Parameter reflecting historical data Parameter baseline from comparative, historical WUCs Unique set of SDTRs , that address baseline system, LRU, SRU Selection range of SDTRs that operate (+ or -) on the jTH set of baseline values of f, d, or c. Supportability at optimum state when support events approach “0” Supportability design-to requirements ADJ = Correction of baseline value or historical data Baseline, existing or predecessor system Supportability elements - major 1) Operational suitability 2) Readiness 3) In-flight sustainability 4) Survivability 5) Operational sustainability 6) Mobility/transportability 7) Reliability and maintainability 8) Life-cycle cost 9) Availability (AO) Supportability elements - subordinate 1) 01- 09 support general codes 2) Preventive maintenance 3) Corrective maintenance 4) Resource consideration 5) Personnel requirements 6) Support equipment and facilities Weighted or relative importance of elements - baseline Weighted or relative importance of elements - project Work unit code reflects system data definition for historical data collection or for new systems SE = B or b = E = L = nTH = WTb = WTp = S (f, d, c) OPT = WUC = SDTR =

9. 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

10. PRODUCIBILITY ( P ) SUPPORTABILITY ( S ) PRODUCIBILITY ELEMENTS SUPPORTABILITY ELEMENTS SURVIVABILITY (COMBAT SUPPORT) MOBILITY AND TRANSPORTABILITY SPECIFICATIONS AND STANDARDS ENVIRONMENTAL REQUIREMENTS RELIABILITY/MAINTAINABILITY OPERATIONAL SUSTAINABILITY INFORMATION NODES OPERATIONAL AVAILABILITY INFORMATION NODES CLEANING REQUIREMENTS OPERATIONAL SUITABILITY SAFETY CONSIDERATIONS INFLIGHT SUSTAINABILITY GENERAL INSPECTIONS MATERIALS SELECTION PROCESS DEFINITION ASPECTS OF DESIGN LIFE CYCLE COST READINESS TESTING PRODUCIBILITY SUBELEMENTS SUPPORTABILITY SUBELEMENTS • DOCUMENTATION CONTROL & ADMINISTRATION • GENERAL SUPPORT • PIECE PART/MINOR FABRICATION • PREVENTATIVE MAINTENANCE • ASSEMBLY AND TEST • CORRECTIVE MAINTENANCE • INTEGRATION AND PERFORMANCE CHECKS • RESOURCE CONSIDERATION • PERSONNEL CHARACTERISTICS • PERSONNEL CHARACTERISTICS • FACILITIES/EQUIPMENT/TRANSPORTATION • SUPPORT EQUIPMENT & FACILITIES Design-to Data Base Producibility and Supportability Cell Characteristics Index Requirements Information Nodes/Cells reside in the WBS • Producibility unique Þ AL Film, metalized • Basis for design-to requirements • Supportability unique Þ 38 Service center • Provide automated information management • Common/shared Þ 37 Mounting and positioning Access Retrieval System New System Use Engineering Designer Cell division/multiple applications • Producible Process Traceability • Supportable Data base management Artificial intelligence information clusters Trade Studies Information management, knowledge capture, and a dynamic systems engineering environment result in producible and supportable products. PVC/283Z/194a Lessons Learned Linked to Requirements [P, S = F (f,d,c)] Are Embedded In the Work Breakdown Structure (WBS) Information Nodes WBS WBS

11. 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……

12. What about Producibility? The Producibility Design-to Requirements (PDTR) Development Process • New Design Related Metrics • Integrating Producibility and Supportability

13. PRODUCIBILITY DEFINED Producibility elements - major 1) Aspects of design 2) Specifications and standards 3) Materials selection 4) Processes definition 5) Environmental requirements 6) General inspections 7) Testing 8) Safety considerations 9) Cleaning requirements

14. AND THIS • Producibility element - subordinate • 1) Documentation control and administration • 2) Piece part/minor fabrication • 3) Assembly and test • 4) Integration and performance checks • 5) Personnel characteristics • 6) Facilities/equipment/transportation • Again, just as in Supportability, we compute: • Weighted or relative importance of elements for system being replaced or modified - Comparison Baseline • Weighted or relative importance of elements that we want to see in the new system- The New Project

15. 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

16. 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

17. HYBRID MANUFACTURING PRODUCTION PLANNING AND CONTROL POWER SOURCES ELECTRO- MECHANICAL & HARNESS [ ) j TH 6 9 ] ( ± S S S Kb ADJ E(WTb) SE(WTb) * * f 1 1 1 INTEGRATION AND TEST [ ) j TH 6 9 ] ( ± S S S Kb ADJ E(WTb) SE(WTb) * ASSEMBLY AND TEST * d 1 1 1 [ ) j TH 6 9 ] ( ± S S S Kb ADJ E(WTb) SE(WTb) * * c OTHER ORGANIZATIONS 1 1 1 MACHINE SHOP AND PLATING { [ ) j TH 6 9 ] ( nTHL ± S S S Mb S1 E(WTm) SE(WTm) * * f 1 1 1 FABRICATION & PRECISION MECHANICAL ASSEMBLY [ ) j TH nTHL 6 9 ] ( ± S S1 S S Mb E(WTm) SE(WTm) * * d 1 1 1 [ ) j TH 6 9 ] nTHL ( } ± S S S Mb S1 E(WTm ) SE(WTm) * * c 1 1 1 PROJECT Algorithm Defined Producibility (P) Design-to RequirementsAssure Team Member Focus >>> Reduce Production Events 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. PRODUCIBILITY MANAGER SYSTEM ENGINEERING DESIGN ENGINEERING Where: f = manufacturing event frequency d = manufacturing event duration c = manufacturing event cost Events range from Anodize to Zyglo PRODUCIBILITY ELEMENTS ASPECTS OF DESIGN SPECIFICATIONS AND STANDARDS MATERIALS SELECTION PROCESS DEFINITION ENVIRONMENTAL CONSIDERATIONS GENERAL INSPECTIONS TESTING SAFETY CONSIDERATIONS CLEANING REQUIREMENTS PRODUCIBILITY ENGINEER P is at its optimum for the project when P approaches “0” with respect to f, d, and c, or POPT = PBASELINE >>> PPROJECT • PDTR OPTIMIZATION • TECHNOLOGIES INSERTION • TRADE STUDIES • INDEPENDENT RESEARCH & DEVELOPMENT (IRAD) { P(f, d, c)OPT = ALGORITHMS P = {((((±JthPS...)}) } BASELINE jTH = K = Kb = Selection range of baseline parameter values Parameter, reflecting historical data Parameter baseline from comparative, historical WBSs Unique set of PDTRs analyses that address baseline system and generate project requirements Project, new system or major ECP Selection range of PDTRs that operate (+ or -) on the jTH set of baseline values of f, d, or c. Producibility at optimum state when support events approach “0” (minima) Producibility design-to requirements ADJ = Correction of baseline value or historical data Baseline, existing or predecessor system Producibility elements - major 1) Aspects of design 2) Specifications and standards 3) Materials selection 4) Processes definition 5) Environmental requirements 6) General inspections 7) Testing 8) Safety considerations 9) Cleaning requirements Engineering change proposal Producibility element - subordinate 1) Documentation control and administration 2) Piece part/minor fabrication 3) Assembly and test 4) Integration and performance checks 5) Personnel characteristics 6) Facilities/equipment/transportation Weighted or relative importance of elements - baseline Weighted or relative importance of elements - project Work breakdown structure reflects system data definition for historical data collection or for new systems SE = B or b = E = L = M or m = WTb = nTH = WTm = P (f, d, c) OPT = WBS = ECP = PDTR =

18. PRODUCTION PLANNING AND CONTROL POWER SOURCES ELECTRO- MECHANICAL & HARNESS RELIABILITY FABRICATION & PRECISION MECHANICAL ASSEMBLY ASSEMBLY AND TEST MAINTAINABILITY MACHINE SHOP AND PLATING INTEGRATION AND TEST HYBRID MANUFACTURING Integrated Supportability and Producibility DESIGN INTEGRATION DESIGNERS SYSTEMS ENGINEERS DESIGNERS DESIGNER Reliability Maintainability Producibility Logistics Other FORMAL INFORMAL Supportability S Producibility P FIELD SUPPORT PRODUCIBILITY ENGINEER SUPPORTABILITY ENGINEER • HUMAN FACTORS • SAFETY • PDTR* OPTIMIZATION • TECHNOLOGIES INSERTION • TRADE STUDIES • INDEPENDENT RESEARCH & DEVELOPMENT (IRAD) • SDTR INTEGRATION** • SUPPORTABILITY TECHNOLOGIES • TRADE STUDIES • INDEPENDENT RESEARCH & DEVELOPMENT (IRAD) 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 LOGISTICS SUPPORT ANALYSIS DESIGN • SUPPORT EQUIPMENT • TRAINING DEVICES **Supportability Design-To-Requirements (SDTRs) * Producibility Design-To-Requirements (PDTRs)

19. 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.

20. 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