1 / 23

OUGM 2012 Analyzer New Capabilities

OUGM 2012 Analyzer New Capabilities. What, When, Why, How? Graham Brum. 40 YEARS OF HISTORY!!. 1971 – 1990 DND LCC Tool ALORA II, III, IV OSAM, ROSAM 1990’s LOGAN 1996 Pennant Licence Agreement LOGAN developed as Windows 3 tool for production release. History and Progress II. 2000

quasim
Download Presentation

OUGM 2012 Analyzer New Capabilities

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. OUGM 2012Analyzer New Capabilities What, When, Why, How? Graham Brum

  2. 40 YEARS OF HISTORY!! • 1971 – 1990 • DND LCC Tool • ALORA II, III, IV • OSAM, ROSAM • 1990’s • LOGAN • 1996 • Pennant Licence Agreement • LOGAN developed as Windows 3 tool for production release Pennant OUGM 2012

  3. History and Progress II • 2000 • LOGAN 3.0.4 included in OmegaPS CASS Suite – Part of DND MASIS solution • 2001 • LOGAN 4.0 rebranded as OmegaPS Analyzer • 2008 • Analyzer R4 added multi scenario concepts • 2011 • OmegaPS Analyzer R4.3 released Pennant OUGM 2012

  4. What’s Changing • New Capabilities being developed: • OSAM – OmegaPS Supportability Analysis Model • LORA2 – Next generation LORA math • ASOAR – Achieving a System Operational Availability Requirement • OSAM released in R15.3, Revised in R17.7 • LORA2 prototype running • ASOAR in this years work Pennant OUGM 2012

  5. OSAM • OmegaPS Supportability Analysis Model • An add on module to OmegaPS LSAR to incorporate the Analyzer Math Models • Works directly off the Oracle DB and Forms • Not yet fully identical to Analyzer R4.3 • No Risk and Sensitivity • No Detailed LORA drill down reports • Extended Data is provided in XML files Pennant OUGM 2012

  6. LORA2 • The integer programming (IP) model version of LORA was developed by DMGOR AST. This was provided in the form of a code file (.mod) and a sample data file (.dat). Pennant was tasked with integrating the integer programming solution into Analyzer in an effort to speed up the LORA process, particularly in the area of Test Equipment distribution. The development consisted of: • Selection of IP programming platform (GPLK) • Integration of IP programmer into Analyzer • Creation of new tables within Analyzer to support FMEA • Design of new forms within Analyzer to support FMEA • Output of FMEA data to IP .dat file • Investigation into sparing requirements for IP • Integrating sparing into IP • Creating new Analyzer tables to support solution data • Reading of solution data (.sol file) • Integer programming reports Pennant OUGM 2012

  7. Example LORA2 Screen Pennant OUGM 2012

  8. ASOAR Achieving a System Operational Availability Requirement Based on DoD work done in 1991 The Achievable Platform Availability Utility (DND’s ASOAR) is a macro-level analysis tool requested by PMSO. Facilitates system level Reliability, Availability and Maintainability (RAM) analysis and early-on Logistics Support Analysis (LSA). A top down approach that integrates RAM and LSA in establishing a platform level achievable availability, supporting the intent of the ISSCF. Its output would quantify a platform level availability capability limit computed from readily accessible manufacturer’s end-item equipment specifications. Pennant OUGM 2012

  9. MODELS • APAU • Achievable Platform Availability Utility, A tool foroptimally allocating a System Ao to End Item Ao goals. • Analyzer • A DND supportability model that integrates End Item Sparing, LORA and LCC to determine the best distribution of resources to achieve System Availability goals at least cost

  10. SYSTEMS AND END ITEMS • Systems are a collection of End Items System = EI1 + EI2 .......... + EIn • End Items are usually different acquisition contracts • For Example: • Halifax Combat System includes 3D Radar, 2D Radar, FCS, Nav, IFF, etc

  11. Modeling to Operational Availability * Taken from B. Price PPT 1991 SYSTEM Ao/ READINESS RATE REQUIREMENT OPTIMAL ALLOCATION OF OPERATIONAL AVAILABILITY (Ao) ASOAR END ITEM Ao GOAL MAINTENANCE OPTIMIZATION SUPPLY OPTIMIZATION SESAME COMPASS LEAST COST MAINTENANCE CONCEPT FOR LRUs & SRUs LEAST COST SPARING MIX FOR LRUs & SRUs

  12. COMPARED WITH ANALYZER SYSTEM Ao/ READINESS RATE REQUIREMENT OPTIMAL ALLOCATION OF OPERATIONAL AVAILABILITY (Ao) ASOAR (APAU) END ITEM AoGOAL Analyzer Multi-PE Models SUPPLY OPTIMIZATION MAINTENANCE OPTIMIZATION SESAME Analyzer-SPARING COMPASS Analyzer-LORA LEAST COST MAINTENANCE CONCEPT FOR LRUs & SRUs LEAST COST SPARING MIX FOR LRUs & SRUs Taken from B. Price PPT 1991

  13. RAM DATA • End Items have RAM Data requirements for • Reliability (MTBF) • Maintainability (MTTR) • These combine to determine System level values: (1/MTBFsys) = (1/MTBF1) + (1/MTBF2) +....+ (1/MTBFn) MTTRsys = (MTBFsys/MTBF1)*MTTR1 + ..... + (MTBFsys/MTBFn)*MTTRn Note: equations taken from AD-A262 406ASOAR Model Methodology

  14. AVAILABILITY Availability is the measure of a system’s “Uptime” with respect to “Downtime” Ao = UPTIME UPTIME + DOWNTIME Or AoSys = MTBFsys MTBFsys + MTTRsys + MLDTsys

  15. MLDT Mean Logistics Delay Time – waiting for resources to be provided to restore the equipment The system MLDT is a weighted average of the End Item’s failure frequency multiplied by the EI MLDT

  16. TARGET SYSTEM MLDT Because Ao, MTBF and MTTR are specified the System MLDT target can be determined from: AoSys = MTBFsys MTBFsys + MTTRsys + MLDTsys Therefore, Target MLDT MLDTtarget= ((1-Ao) * MTBFsys) – (Ao * MTTRsys) AoSys

  17. COST – FAILURE RATE RATIO Sparing to Availability works with the largest Ao gain per unit cost. Also, Ao increased by optimal location of spares leads to largest reduction in MLDT for least spares cost. The Cost to Failure Rate ratio of an LRU is a key parameter which can aid in selecting spares

  18. SYSTEM TARGETS When the LRU structure is not known in the End Item the Cost/FR ratio can be estimated. Use average LRU Cost and average LRU failure rate. Adjust for high cost low FR items to prevent skew. MLDT is calculated as the cost effective End Item target value.

  19. Ao ESTIMATES With the target End Item MLDT calculated it can be used to estimate the End Item Ao The estimated System Ao is the product of all End Item Ao estimates Compare estimated System Ao with required value Iterate until estimate equals target

  20. ADJUSTMENTS • ASOAR makes computational adjustments for various cases in the system • Equipment Configurations (e.g. Common EI and redundancy) • Periodic Maintenance (Scheduled and PM) • Maintenance Plans

  21. OmegaPS ANALYZER Analyzer does all the LORA and Sparing models (similar to the COMPASS and SESAME) Analyzer can determine support results for multiple End Items (PE) mixed to create a system with individual Ao targets Analyzer does not take a required system Ao and allocate to End items (PE)

  22. I Wish....... • WIBNIs - What’s a WIBNI • Some current WIBNIs: • Redundancy • Enhanced mission sparing analysis • Task Based (FMEA) model • Simulation • Variable operating profiles • PE Spares Pools • Enhanced cost analysis Pennant OUGM 2012

  23. Current Development With limited DMGOR modelling support in current climate, DMGOR and Pennant have decided to focus on completing LORA2 to a basic level of functionality APAU model will be incorporated into the Analyzer GUI for data and report generation OSAM will be stabilized in OmegaPS LSAR User requested needs will be addressed Pennant OUGM 2012

More Related