1 / 62

Lesson 9 Design For Supportability

Lesson 9 Design For Supportability. What Are The Goals of Defense Acquisition?. Provide a Military Capability Meet User Needs Be Affordable Minimize Risk Be Accountable. What Are The Goals of Defense Acquisition?. Provide a Military Capability Meet User Needs Be Affordable

nimrod
Download Presentation

Lesson 9 Design For Supportability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lesson 9Design For Supportability

  2. What Are The Goals of Defense Acquisition? • Provide a Military Capability • Meet User Needs • Be Affordable • Minimize Risk • Be Accountable

  3. What Are The Goals of Defense Acquisition? • Provide a Military Capability • Meet User Needs • Be Affordable • Minimize Risk • Be Accountable

  4. Affordable System Operational Effectiveness (ASOE) Model JCIDS KPP/KSA Materiel Availability (AM) Operational Availability (AO) Reliability Operating & Support Cost (O&S) Mean Down Time (MDT) Affordability

  5. Mapping Trade-Offs JCIDS KPP/KSA Materiel Availability(AM) Operational Availability (AO) Reliability Operating & Support Cost (O&S) Mean Down Time (MDT) Affordability

  6. JCIDS KPP / KSA Definitions • Key Performance Parameter (KPP) • “Performance attributes of a system considered critical or essential to the development of an effective military capability.” • Key System Attributes (KSAs) • "System attributes considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). KSAs provide decision makers with an additional level of capability prioritization below the KPP but with senior sponsor leadership control (generally four star, defense agency commander, or principal staff assistant)."

  7. JCIDS Sustainment KPP / KSA Definitions

  8. Traceability of Metrics from KPP/KSA – MOE – MOP – MOS - TPM • Measures of Effectiveness (MOE) are derived from User Needs defined in terms of Key Performance Parameters (KPP) and Key System Attributes (KSA) in a Capability Development Document (CDD) or a Capability Production Document (CPD). • MOEs may defined in terms of Measures of Performance (MOP), such as Speed and Measures of Suitability (MOS), such as Reliability. • MOPs and MOS may be expressed in terms of Technical Performance Measures, for example, Reliability may be defined in terms of Mean Time Between Failure (MTBF).

  9. Align MOEs to Milestones to Ensure Traceability of Requirements

  10. The Practitioner’s Guide to SupportabilityProcess Steps • Define/Establish an Analytical Framework • Translate Requirements into a Design • Mature the Design Through Testing • Use Analytical Tools to Conduct Trades • Develop, Maintain, Use and Report Data • Continuously Evaluate Suitability L9 Design For Supportability October 1 2018

  11. 1. Define/Establish an Analytical FrameworkFrom Competencies to Outcomes L9 Design For Supportability October 1 2018

  12. 1. Define/Establish the Analytical FrameworkApply Enterprise Standards Click for Hyperlink Source: US Army LOGSA • US Army LOGSA Logistics Enterprise • Standards • define the terminology, requirements, processes, and relationships necessary to provide a comprehensive assessment of system architectures • and resources.. L9 Design For Supportability October 1 2018

  13. 2. Translate Requirements into DesignObjective #1: Failure Identification / Prediction Attributes Which May be Considered KPPs or KSAs Include: Supportability as a JCIDS Design Objective • Built-In-Test (BIT) Fault Detection - a measure of recorded BIT indications which lead to confirmed hardware failures. • BIT Fault Isolation - A measure of recorded BIT indications which correctly identify the faulty replacement unit, either directly or through prescribed maintenance procedures. • BIT False Alarms - A measure of recorded BIT indications showing a failure when none has occurred The ability of the system to identify and/or predict failures down to a certain subsystem within a given percentage of accuracy. Potential attributes include health management, prognostics and diagnostics capabilities, Condition-Based Maintenance Plus (CBM+) enablers, support equipment and parts commonality. L9 Design For Supportability October 1 2018

  14. 2. Translate Requirements into DesignObjective #2: Rapid Restoration of Service Attributes Which May be Considered KPPs or KSAs Include: Maintainability as a JCIDS Design Objective • Corrective Maintenance - All actions performed as a result of any failure, to restore a system, subsystem, or component to a required condition. • Mission Maintainability - The ability of the system to be retained in or restored to a specified mission condition. • Maintenance Burden - A measure of maintainability related to the system's demand for maintenance manpower The ability of the system to be brought back to a state of normal function or utility. Normally expressed as Mean Down Time (MDT), Mean Time To Repair (MTTR) or a calculation of ease of maintainability. Maintainability Design Attributes Accessibility – Physical placement of hardware to facilitate maintenance. Modularity – Grouping of similar functions within a physical area. Testability – Extent to which the operational status of modules can be tested L9 Design For Supportability October 1 2018 Practitioner's Guide to Supportability

  15. 2. Translate Requirements into DesignObjective #3: Affordable Cost / Effective Sustainment L9 Design For Supportability October 1 2018

  16. 3. Mature the Design Through TestingDesigning for R&M / Developmental Test • Design for Reliability (DFR) is a System Engineering process that identifies and eliminates failure modes, and ensures the reliability and supportability of designs: • Redundancy • Derating • Thermal Design • Integrity Analysis • Software RAM • Parts Selection Program • Critical Items Analysis • Storage Analysis • Sneak Circuit Analysis • Developmental Test & Evaluation (DT&E) • Laboratory • Limited Operational • Simulation • Environmental Testing • (MIL-STD-810C) • Altitude • Hi / Low Temp / Shock • Vibration • Heat/Cold • Solar Radiance • Rain (Wind and Ice) • Humidity / Fungus • Wind/Fog • Salt The Failure Reporting And Correction System (FRACAS) Is An Integral Part Of The Development Process L9 Design For Supportability October 1 2018

  17. 4. Use Analytical Tools to Conduct TradesMIL-HDBK-502A Design Interface-Support Trades L9 Design For Supportability October 1 2018

  18. 4. Use Analytical Tools to Conduct Trades FMECA Appendix A - Maintainability Information System UHF/VHF Radio Indenture Level A304 Diode BridgeMission Rx Tx Full Duplex Identifies Engineering and Product Support Information for Design, CBM / RCM, Tech Manuals L9 Design For Supportability October 1 2018

  19. 4. Use Analytical Tools to Conduct TradesDoDProduct Support Analytical Tools USA AMSAA Center for Reliability Growth USA LOGSA Logistics Engineering Analysis Center Products Disclaimer The product support analytical tools identified in this database are provided solely to assist defense acquisition workforce professionals to identify best value product support solutions which optimize system readiness and life cycle cost. Neither the Department of Defense or the Defense Acquisition University provide any warranty of these tools whatsoever, whether express, implied, or statutory, including, but not limited to, any warranty of merchantability or fitness for a particular purpose or any warranty that the contents of the item will be error-free. This analytical tools database should under no circumstances be considered as being all-encompassing, and is in no-wise meant to endorse the capabilities or products of any particular individual, company, or organization. L9 Design For Supportability October 1 2018 Practitioner's Guide to Supportability

  20. 5. Develop, Maintain, Use and Report DataLogistics Product Data (LPD) / Data Sources MIL-HDBK-502A, Product Support Analysis, and GEIA-STD-0007 Logistics Product Data define over 100 logistics product data (LPD) tables that document information for the 12 Integrated Product Support (IPS) elements. T A B L E S D A T A CDD Inputs Bill of Materials Purchase Orders Drawings Facilities Test Equipment Specifications Maintenance Task Analysis Engineering Analyses L9 Design For Supportability October 1 2018 Practitioner's Guide to Supportability

  21. 5. Develop, Maintain, Use and Report DataIndustry Standards Facilitate Data Exchange • Universal Data Item Description (DID) • Standard reports supporting IPS Elements • Data requirements/attributes • Exchange protocols for data communication • Table relationships • Shared, common terminology OEM GOVT SAE GEIA-STD-0007 Logistics Product Data Has Been Adopted by the DoD for the Acquisition and Exchange of Logistics Product Data (LPD) Enables Error Free Data Transfer Govt Software Commercial Software 10101010101010010 Contracts can require the OEM provide SAE GEIA-STD-0007 compliant data to the Government. L9 Design For Supportability October 1 2018

  22. 5. Develop, Maintain, Use and Report DataLSA Reports Detail IPS Element Resources Over 80 Reports L9 Design For Supportability October 1 2018

  23. 5. Develop, Maintain, Use and Report DataData-Driven Decision Making / Governance Sustainment Quad Chart L9 Design For Supportability October 1 2018

  24. 6. Continuously Evaluate SuitabilityIndependent Logistics Assessment (ILA) The 2009 DoD Weapon Systems Acquisition Reform Product Support Assessment (WSAR-PSA) included the recommendation to implement independent Logistics Assessments during Weapon System Development, Production and Post-initial Operational Capability (Post IOC) (2) ILA Rating Criteria (1) Assessment Criteria (3) Risk Rating Summary ILA Provides Critical Technical And Management Information To Support the Governance Process L9 Design For Supportability October 1 2018

  25. Validate Tasks, Tools, Manuals, Sparing, Manpower/Skills 6. Continuously Evaluate SuitabilityInitial Operational Test & Evaluation (IOT&E) Suitability is the degree to which a system can be satisfactorily placed in field use, with consideration given to reliability, availability, compatibility, transportability, interoperability, wartime usage rates, maintainability, safety, human factors, manpower supportability, logistics supportability, documentation, environmental effects, and training requirements. The Log Demo evaluates the Suitability of system support that ensures the right resources, with the appropriate skill level, under the appropriate environment conditions, to achieve the maintenance task in the time allotted. L9 Design For Supportability October 1 2018 $ Ao MTTR LogisticsFootprint Maintenance Concept

  26. 6. Continuously Evaluate SuitabilityPost Fielding Data & Supportability Analysis (PFSA) Navy Visibility and Management of Operating and Support Cost (VAMOSC) Air Force Total Ownership Cost Management Information System (AFTOC) Army Operating and Support Management Information System (OSMIS) US Army Logistics Support Activity (LOGSA) Post Fielding Support Analysis (PFSA) Tool Weapon System Report • A two-year window rolling weapon system performance assessment • Equipment Availability • Demand Drivers • Maintenance Drivers • Fleet Usage L9 Design For Supportability October 1 2018

  27. 6. Continuously Evaluate SuitabilitySustaining Engineering • Sustaining Engineering: • Technology Insertion • Service Life Extensions • Correction of Deficiencies • Incorporation of New Capabilities • Improved Product Support Click Pic for Hyperlink Click Pic for Hyperlink Technology Insertion Sustaining Engineering spans engineering and sustainment domains (and analyses) to ensure continued operation and maintenance of a system with managed (i.e., known) risk. Service Life Extension Are the Levels of Performance, Reliability and Product Support Sufficient to Meet System Sustainment Requirements? L9 Design For Supportability October 1 2018

  28. Supportability Analysis Links LOG 211 Supportability Analysis (Classroom) CLL 008 Designing for Supportability in DoD Systems CLL 012 Supportability Analysis MIL-HDBK-502A Product Support Analysis MIL-HDBK-502A Product Support Analysis ACQuipedia Article Logistics Assessment Guidebook CLL 020 Integrated Logistics Assessment Integrated Logistics Assessment (ILA) Guidebook ACQuipedia Article L9 Design For Supportability October 1 2018

  29. Lesson 3/ 4Designing for supportability Capability Development Document (CDD) Review

  30. “Strike Talon” UAV Capability Development Document (CDD) LOG 211 Supportability Analysis uses a case-based approach to learning DAU worked with NAVAIRSYSCOM to review the Broad Area Maritime Surveillance S(BAMS) Unmanned Aerial System for use as a reference in LOG 211. DAU condensed the unclassified Capability Development Document (CDD) for the “Strike Talon” to convey program management, requirements, schedule and logistics-related concepts and information

  31. “Strike Talon” Capability Development Document (CDD)

  32. “Strike Talon” Capability Development Document (CDD)

  33. “Strike Talon” Capability Development Document (CDD)

  34. “Strike Talon” Capability Development Document (CDD)

  35. “Strike Talon” Capability Development Document (CDD)

  36. “Strike Talon” CDD

  37. “Strike Talon” CDD

  38. “Strike Talon” CDD

  39. “Strike Talon” CDD

  40. “Strike Talon” CDD

  41. “Strike Talon” CDD

  42. “Strike Talon” CDD

  43. “Strike Talon” CDD

  44. “Strike Talon” CDD

  45. “Strike Talon” CDD

  46. “Strike Talon” CDD

  47. “Strike Talon” CDD

  48. “Strike Talon” CDD

  49. “Strike Talon” CDD

  50. “Strike Talon” CDD

More Related