OmegaPS Analyzer: New Features Review. Cheltenham Manchester Fareham Ottawa Melbourne Aberdeen

Transcription

1 OmegaPS Analyzer: New Features Review Cheltenham Manchester Fareham Ottawa Melbourne Aberdeen

2 Availability Modelling Design Availability Target Model DATM Used to allocate and assess availability targets Through Life Availability Simulation TLAS Simulates missions of defined systems to evaluate availability Extension Models to OmegaPS Analyzer Uses the core model and data of Analyzer DND Supportability Model Provides DND projects with baseline methods

3 DATM Functionality Allocate CSC Availability system targets to Prime Equipment and systems Determine realistic availability targets to be required from ship designs Assess the Availability achievable from proposed ship designs at key design milestones (e.g. PDR, CDR, FDR, Production) Estimate supportability costs from optimized support solutions

4 DATM - Allocate A required availability is specified for the system. The required operational system availability is allocated to each PE in the system taking into account the mission, PE design concepts (e.g. redundancy), and support concepts (e.g. PM, supply chain). The system target is allocated to the constituent PE, based on a weighting method using average LRU reliability and cost. Allocated targets are the design to targets for an optimized support solution. DATM uses the basic structures defined in Analyzer and presents a report indicating how the PE should apply the design target availability. These are the preferred design targets.

5 DATM - Assess Ability to Achieve Availability The second process in DATM is the assessment of design data and that design s ability to achieve the design targets. Design Reviews As data is provided at significant mile stones (e.g. PDR, CDR, etc.), and the support solution matures, then the DATM assessment can be made, providing insight to the design s ability to provide the system at a required level of availability. Compared with maturing baseline system Report displays comparison between Allocated values and current design values.

6 TLAS Functionality 1. Assess CSC Availability over a Defined Life 2. Generate RCN Missions to simulate the life of a fleet of CSC ships 3. Integrate sparing solution into Stock Management 4. Log life events simulated by model 5. Evaluate support solution effectiveness

7 Updates in Release R5 New technology build to catch up with underline development environment Visual Studio 2015 accdb format database C++ core dll model Incorporates new functionality Integrates development branches to one product

8 Future Functionality Improved calculations to extend data depth Improved reporting to output detailed results Integration with SAE GEIASTD0007 xml entities Task Libraries Mission Essentiality Improved sparing Walk through OmegaPS Analyzer

9 Aberdeen Fareham Manchester Cheltenham Ottawa Melbourne

10 Basic TLAS Model 6. If LRU not discarded send to LOM2 Stock Management 5. Is LRU Repaired at LOM1 4. Uses LRU Stock Item 3. LRU Replaced restores PE 2. Prime Equipment waits in queue for LRU R/R 1. Prime Equipment has LRU failure. PE goes down

11 Mission Generation Ship HMCS Alpha HMCS Bravo HMCS Charlie HMCS Delta HMCS Echo HMCS Foxtrot Generator Type (e.g. International; Domestic) Random or Scheduled mission generation Multiple Missions defined for each generator type Phases defined within missions (e.g. Prep, Execute, Recovery) RCN Readiness Levels used (e.g. HR, SR, ER, RR) Mission associated required or critical equipment Jan-15 Feb-15 Mar-15 Apr-15 May-15 Jun-15 Jul-15 Aug-15 Sep-15 Oct-15 Nov-15 Dec-15 Jan-16 Feb-16 Mar-16 Apr-16 May-16 Jun-16 Jul-16 Aug-16 Sep-16 Oct-16 Nov-16 Dec-16 Jan-17 Feb-17 Mar-17 Apr-17 May-17 Jun-17 Jul-17 Aug-17 Sep-17 Oct-17 Nov-17 Dec-17 Jan-18 Feb-18 Mar-18 Apr-18 May-18 Jun-18 Jul-18 Aug-18 Sep-18 Oct-18 Nov-18 Dec-18 Jan-19 Feb-19 Mar-19 Apr-19 May-19 Jun-19 Jul-19 Aug-19 Sep-19 Oct-19 Nov-19 Dec-19 H H H H H H H H H H H H H H H H H H H H S S S S S S S S S S S S S S S S S S S S E E E E E E E E E E E E E R R R R R R R H H H H H H H H H H H H H H H H H H H H S S S S S S S S S S S S S S S S S S S S E E E E E E E E E E E E E R R R R R R R E E E E E E E E E E E E E R R R R R R R H H H H H H H H H H H H H H H H H H H H S S S S S S S S S S S S S S S S S S S S E E E E E E E E E E E E E R R R R R R R H H H H H H H H H H H H H H H H H H H H S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S E E E E E E E E E E E E E R R R R R R R H H H H H H H H H H H H H H H H H H H H S S S S S S S S S S S S S S S S S S S S E E E E E E E E E E E E E R R R R R R R H H H H H H H H H H H H H H H H H H H H

12 System of Systems Prime Equipment (PE) are defined: e.g. PE1 - Nav Radar, PE2-2D Radar, PE3-3D Radar PE work together as a system: e.g. System X = PE1 (fwd) & PE1 (aft) Redundancy between PE provides improved system availability (PE2) Missions systems and PE are required or critical for each mission execution. PE are made up of LRUs R/R LRU to return PE to service

13 Maintenance Facilities (MF) A hierarchy of maintenance and support shops Multiple lines, e.g. ships, FMF, depot, contractor Uses Analyzer support organizations Predefined models are reusable in TLAS Each MF is defined for operating times When maintenance techs are available for work Queues jobs as they arrive Operating Sites are LOM1 MF Ships operate equipment and do first line work Failure Diagnostics determine repair location.

14 Stock Management Applies the principle that stock might not be available when repair commences: Not held at this location (optimal sparing design) order stock Stock-out at this location replenish Stock out at highest MF procure Initial inventory taken as PDS in Analyzer LRU becomes Shop Item after removal from PE. Repair process returns LRU to stock

15 CFCD Missions DWP Docking Work Period - no RCN use ER Extended Readiness This readiness state is assigned to assets that are removed RR2 Restricted 2 Harbour Defence, Safe Alongside RR1 Restricted 1 Ready Duty Ship, Sea Trials, Basic Unit Force Generation FP Alongside Ready Duty Ship NR2 Normal 2 NR1 Normal 1 HR3 High 3 HR2 High 2 HR1 High 1 Ready Duty Ship, Ready Duty Combatant, Domestic Response, Basic Ready Duty and Intermediate Force Generation, Force Development, Combatant Continental Force Employment, Support to OGD (FISHPAT, RCMP), International FE (Permissive Environment) As per NR2+ Enhanced RDC HELAIRDET FG Assignment to the Naval Task Group, Advanced Force Generation, Continental Force Employment, International Force Employment Assignment to the Naval Task Group, Advanced Force Generation, Continental Force Employment, International Force Employment SSID Forward Deployed/VANGUARD, Assignment to the NTG, Combat Missions, International Force Employment on named operations, SNMG 2, Contingency Operations Naval Task Group Naval Task Group Expeditionary FE Ship Jan-15 Feb-15 Mar-15 Apr-15 May-15 Jun-15 Jul-15 Aug-15 Sep-15 Oct-15 Nov-15 Dec-15 Jan-16 Feb-16 Mar-16 Apr-16 May-16 Jun-16 Jul-16 Aug-16 Sep-16 Oct-16 Nov-16 Dec-16 Jan-17 Feb-17 Mar-17 Apr-17 May-17 Jun-17 Jul-17 Aug-17 Sep-17 Oct-17 Nov-17 Dec-17 Jan-18 Feb-18 Mar-18 Apr-18 May-18 Jun-18 Jul-18 Aug-18 Sep-18 Oct-18 Nov-18 Dec-18 Jan-19 Feb-19 Mar-19 Apr-19 May-19 Jun-19 Jul-19 Aug-19 Sep-19 Oct-19 Nov-19 Dec-19 HMCS Halifax E E R R R R R R R N N N N N N H H H H H H H H H H H H H E E E E R R N N N N N N N N N N N H H H H H H H H H H H H H E E HMCS Montreal H H H H H H H H H H H H H E E E E R R N N N N N N N N N N N H H H H H H H H H H H H H E E E E E E E E E E R R R R R R R HMCS Charlottetown R R R R N N N N N N H H H H H H H H H H H H H E E E E R R N N N N N N N N N N N H H H H H H H H H H H H H E E E E E E E HMCS Toronto E E E E E E E E E E E E E E R R R R R R R N N N N N N H H H H H H H H H H H H H E E E E R R N N N N N N N N N N N H H H HMCS VDQ N N N N N N N N N H H H H H H H H H H H H H E E E E E E E E E E E E E E E R R R R R R R N N N N N N H H H H H H H H H H HMCS Fredericton H H H H H H H H H H H E E E E E E E E E E E E E E R R R R R R R N N N N N N H H H H H H H H H H H H H E E E E R R N N N

16 Sample Files xml Input Data

17 Sample Files Simulation Log ( :0) platform=hmcs Fredericton, time to readiness transition = (335.0 days) ( :0) Platform=HMCS Fredericton, System=Navigation System, PE[1]=Nav Radar, LRU=LRU1, time_to_failure = ( :0) Platform=HMCS Fredericton, System=Navigation System, PE[2]=Nav Radar, LRU=LRU1, time_to_failure = ( :0) Platform=HMCS Fredericton, System=Radar System, PE[1]=3D Radar, LRU=LRU3, time_to_failure = ( :0) Platform=HMCS Fredericton, System=Radar System, PE[2]=2D Radar, LRU=LRU2, time_to_failure = ( :0) Platform=HMCS Fredericton, System=Radar System, PE[3]=2D Radar, LRU=LRU2, time_to_failure = ( :0) December 31, 2014 ( :0) January 01, 2015 ( :1) Mission Generator=HR-international, time_to_next_mission completed. Generating new mission. ( :2) Mission Generator=HR-international, time_to_next_mission completed. Generating new mission. ( :2) Primary Mission=Combat Mission, added to PM queue ( :2) Mission Generator=HR-international, time to next mission = ( :2) MF=MF2-East (CLSD), unable to assign mission Combat Mission. Platform readiness NA does not match mission requirement (HR). ( :2) MF=HMCS Halifax (CLSD), satisfies requirement for mission Combat Mission. removed from PM queue ( :2) MF=HMCS Halifax (CLSD), primary mission Combat Mission assigned after 0.0 hrs in QUEUE. mission phase updated to [preparation] with duration ( :23) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar, LRU=LRU1, has failed and is now IN QUEUE. time to replace is ( :23) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar, LRU=LRU1, upness transition UP to DOWN ( :23) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar (OFF), upness tranistion UP to DOWN ( :23) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar (OFF), operating code transition STOPPED to STOPPED ( :0) January 25, 2015 ( :0) January 26, 2015 ( :11) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar (ON), time to replace has ended ( :11) MF=HMCS Halifax (OPEN), Stock=LRU1, inventory(4) reduced by 1 ( :11) MF=HMCS Halifax (OPEN), shop item=lru1 (pid:6) now IN QUEUE ( :11) MF=HMCS Halifax (OPEN), shop item=lru1 failure is TYPEII. time to repair is hrs ( :11) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar, LRU=LRU1, maintenance progress = DONE, time to failure = ( :11) Platform=HMCS Halifax, System=Navigation System, PE[1]=Nav Radar, LRU=LRU1, upness transition UP to UP