3 MFOM 2.0 Provides 3 Significant Tools How does MFOM help?MFOM 2.0 Provides 3 Significant ToolsMaterial Readiness Reporting Tool for Ship SystemsMFOM calculates and reports a percentage of readiness for shipboard equipment and systems based on the documented material conditionMFOM uses standard material reporting toolsScreening Value for Maintenance ActionsMFOM provides each maintenance action a numerical value based on the Equipment Operating Capability (EOC) and system impactThis allows for the prioritization of maintenance actions based on their contribution to material readinessMaterial Readiness – Resources ToolMFOM identifies the funding required to reach a certain level of material readiness based on the documented material condition
4 Basics of MFOM Near real time reporting of ship’s material MFOM 2.0 is a computer based tool built on a hierarchical structure that calculates against operational requirementsDesigned to consistently and objectively calculate a material condition readiness value for equipment, systems, tasks, missions or the ship.MFOM resides on the classified and unclassified networks both ashore and afloatMFOM is accessed through any internet connectionMFOM is modeled based on input from operational and technical Subject Matter ExpertsMFOM takes into account redundancy and system interdependencyNear real time reporting of ship’s materialcondition to support maintenance planningand operational readiness reporting(supports DRRS-N)
5 MFOM Data Inputs MFOM takes input from existing documentation Automated Work Requests (i.e., 2 Kilos)Inspections, Certifications, Assessments and Visits (ICAVs)AlterationsRepair workCASREPs, etcTag-outs (eSOMS)Machinery Monitoring Systems (e.g., ICAS)IPARSClass Maintenance PlansOther Technical Documentation (DFS, UROs, IMMPs, Master Spec Catalog, MRCs)MFOM starts with existing ship’s configuration dataAll records for each hull from CDMD-OA
6 Building the Model A Coordinated Group Effort 40 Government Activities18 ContractorsFleet Forces CommandNSWCCD-SSES PhiladelphiaNSWC CraneNSWC Port HuenemeNSWC CoronaNSWC Indian HeadNSWC DahlgrenNAWC LakehurstNSWC Panama CityCarrier Planning ActivityNSLC MechanicsburgCenter for Naval AnalysisCOMFISCSOffice of Secretary of Defense(AT&L)CNSF, CNAF, CSFNUWC NewportNSWC LouisvilleNAVAIRNSWC EarlePort EngineersPEO Ships, Sub, & CarriersNorfolk Naval Shipyard(LHA/LHD)Puget Sound Naval Shipyard(MCM)Boston Detachment(FFG, LSD, LPD)Navy ERPSUBMEPPSPAWAR San DiegoSPAWAR CharlestonSPAWAR ChesapeakeSUPSHIP BathSUPSHIP Newport NewsSUPSHIP PascagoulaNAVSEANETWARCOMAIS Center NorfolkNAVSUPOPNAV N81/N43Office of Naval ResearchINSURVMARMCCDIMANTECHCSCCACIEG&GNorthrop Grumman Newport NewsNorthrop Grumman Pascagoula (CG)Bath Iron Works (DDG)MI Technical SolutionsUNISYSLockheed MartinBooze Allen HamiltonAntech SystemsRomulusL3 CommTech AssistGeneral DynamicsSAIC
7 Status Shipboard Implementation Shore Implementation Next Developments Expanded on DRRS-N software rollout scheduleInstalled on BATAAN ESG, ENTERPRISE CSG and NIMITZ CSG, GEORGE WASHINGTON, JACKSONVILLE and others (24 ships)Plan to have 50 ships by Dec 31 and all ships within 15 monthsShore ImplementationClassifiedWest coast production servers up for surface ships and subs/carriers214 ships reporting to DRRS-N214 ships reporting material condition in MFOMAll surface ships are generation 2 models on production – reporting to DRRS-NAll SSN 688’s on production – reporting to DRRS-NAll carriers on production – reporting to DRRS-NNo U-NNPI is displayedUnclassifiedNSWC Crane has distance support sites upNext DevelopmentsATM (Phase I – October delivers this week)IUID (Pilot ship USS FORREST SHERMAN DDG-98 Completes October 2007)Fleet Assessment Tool (Completes October delivered)NNWC modeling of shore facilities (Completes November 2007)Validation, Screening & Brokering (Completes March 2008)
8 Ship’s Material Condition Readiness New Readiness Values indicated after repairs are madeSoftware indicates which items should be repaired to support the next mission
9 Feeding Readiness Metrics DRRS-N ScreenDRRS ScreenTotal Force Integrated Readiness Model (TFIRM)$Defense Readiness Reporting System-NavyPESTONTAsTrack air targetsMove unitsSlide starts with MRAS vesselsMRAS operating on NIAPS and FAS servers2K data goes ashore and is fed to the MFOM models for each ship.MFOM applies these 2K to the NTAs.MFOM produces a rating value for the E pillar of PESTO.PESTO pillars fed TFIRM where dollars are linked to the maintenance data.The data is fed to the DRRS-N program and validated by chain of commandDRRS-N feeds DRRSFFGLSDLPDLHADDGCGMRASSSNCVNMFOM
11 Readiness (Sys/Eq MFOM) Costs (Parts and labor) TMA/TMI Data AnalysisReadiness (Sys/Eq MFOM)Systems screened overall in first processSystems ranked in second processSystems investigated in third processParts Cost, CASREPs, Days Down Time, 2K Volume, & Man-hoursCosts (Parts and labor)
12 Predictive MFOM Future Status Screen The “main” screen for MFOM PredictiveFive SectionsShip/Version/Year selectionAvailability ScheduleBudget Requirements & ControlsMFOM TableWork List
13 MFOM Predictive Output Data Class Summary of Readiness Values, Man-days and Material CostsIndividual Hull Build-up of Readiness Values, Man-days and Material CostsFY09 DDGs
14 Decision ProcessStarting with FY-08, notionally cut or add man-days to availabilities to accomplish appropriate readiness valuesCenter FDNF and deployers readiness values around 0.8 readinessCenter non-deployers readiness values around 0.7 readinessEnd-result of fiscal year calculations will provide for a net positive or negative requirement of notional man-days for class availabilitiesRepeat the process for each fiscal year through FY-13Data available by class and availability typeEnd-result of process calculations provides for a net positive or net negative requirement of notional man-days for class availabilities across the FYDPProcess repeated for each surface ship classIf positive, will have man-days to return to an individual FY budgetIf negative, will build a back-log of required maintenance to keep ships at appropriate readiness level
15 Readiness / Maintenance Interfaces 2 way Interface1 way to MFOMAbandon/ReplaceNewLink Only – no data passingReadiness / Maintenance InterfacesReadinessHigh Ship/ShoreDRRS-NIRRIIMSMFOMMaintenanceHigh/Low Ship/ShoreMFOMAIM / AIM XPMRMSLDSNDENMDMRSRMC AssessmentICMPCDMD-OA3MTMAGSOSHIPMAIN MetricsMaint Req UniversityRMMCOData ExchangeOther InterfacesHigh/Low Ship/ShoreWeb SkedAnchor DeskVSBHigh/Low Ship/ShoreRMAISMAMSMSTM&SWPMFOMHigh/Low Ship/ShoreMFOM 2.0MRASVSBATMMaster FINRadiant MercuryMFOM TrainingMFOM Discussion ThreadMFOM Info (Docs, Updates, Equations, Work PackagesMFOM Issues / ResolutionDocument Upload / Down loadSub 2K PassageATMHigh/Low Ship/ShoreMRAS / MFOMeSOMS *eDFS *PMS Sked *R-SupplyR-AdminETC / AWN *EDL / ESL *CWP / FWPSmall Valve MaintenanceComponent Line upQA Tools *OMMS NG / SNAPTMLSATISIPARSMaterial HistoryIUID ** Shared Database
16 FIN (Location)(Function)(ID) Functional Index Number (FIN):A alpha/numeric value assigned to all items in the model.Uniquely identifies every shipboard item by functionIdentifies same item across ship classesSimplifies retrieving data across ship classesDocuments material historyLocation:Compartment Number, Compartment Name, or XYZ CoordinatesFunction:Defines the operational contribution, action, purpose or activity of an object.Identification/Serial Number:Applies an Item Unique Identifier to an object.Can be composed of an IUID or Material Identification Number.
17 IUID DDG 51 Pilot Project Overview MFOM 2.0 implemented a pilot project integrating IUID technologyUses MRAS shipboard databaseEffort focused on DDG-51 classPilot Ship USS FORREST SHERMAN (DDG-98)Targets items that will have maintenance performed on them during the course of a one year period through the tag out system.There were two major components involved in the pilot;Determining the plan for uniquely identifying shipboard equipment and assetsApplication of IUID technology to mark legacy equipment and assets and register IUID numbers in the DoD registryMarking takes place primarily at the organizational level during maintenance.MRAS and MFOM were modified to track equipment with an associated IUID.
18 Project Schedule By 31 January 2007: By 1 February 2007: Determine procurement requirements for IUID marking technologyBy 1 February 2007:Develop training curriculum and material for training Ship’s ForceBy 1 April 2007:Conduct Pre-Pilot testing at the NSWCCD-SSES to verify database communicationsBy 1 May 2007:Begin application of IUIDs on shipboard equipmentConduct training for ship’s force personnelBy 1 September 2007:Complete DDG 51 Class Pilot program IUID applicationBy 30 September 2007:Complete post DDG 51 Class Pilot program analysis and reporting
19 Project ScheduleIdentify Construct # 1: Enterprise Identifier / Serial Number RequirementsUSFF UIC ( DoDAAC) / Special Handling Indicator/Unique Random Serial NumberDevelop and implement IUID Data processes and policy for DDG 51 legacy items:Develop non-shipboard initial IUID SOPDetermine UID tag type and application/attachment processDetermine standard IUID reader requirementsDevelop initial IUID SOP shipboardInitial Pre-Pilot project plan for testing of DDG 51 Class IUID Project at NSWCCD-SSES PhiladelphiaIdentify approximate DDG 51 Class shipboard item inventory for Pilot IUID/MID labeling:Project ship identified as USS FORREST SHERMAN DDG 98ESOMS inventory identifiedCommence shipboard pilot. ESD 23 April 2007
20 Ships with IUID implementation IUID TagIUID Tag on Valve
26 Purpose of the ATM Strategic Goals Better data for MFOM/MRAS Improved 2K / Notification accuracy (correct equipment identified, symptom/EOC captured)Non-2K impacts to readiness captured (Tag outs and Not completed PMS)Reduce the burden on the sailor for managing and performing maintenanceProvides ship’s force with a single entry portal for maintenance managementImproves visibility to the maintenance plan (CSMP, EDL, the Chief’s wheel book)Who are the users of MRAS?CO, XO, Department Heads?Fleet Leadership? (MFOM)Are current paper-based systems being added to MRAS? Or are they going to be new applications? Are some in SKED?
27 ATM Drawers Mission Readiness Assessment System (MFOM Afloat) IUIDE-Forms (EDFS)ESOMSPMS SKEDAWN & ETCEDL/ESL Trouble Call Manager)VSB (for Shore Maintenance Team)Component Line UpCWP / FWPLMAISMaterial HistoryReportsSmall Valve MaintenanceMRAS TrainingIPARSHandheld UpdatesGlobal Distance Support Help DeskATISCDMD-OAR-SupplyR-AdminMFOM ShoreNavy Maintenance DataNavy Data EnvironmentRMMCOTMLSOMMS-NGQA ToolkitVibration AnalysisPhase I Oct 07Phase II Jul 08
36 Ship’s Material Condition Readiness Scenario based material condition readinessWork candidates impacting this mission
37 Same ship portrays different readiness for different missions Different ships can be displayed at the same timeReadiness requirements are set by TYCOMsReadiness change can be changed by selecting an availability instead of current
40 Model Structure Colors and indenture show model levels Column shows impact of individual equipment on this warfare areaColumn shows equipment degradation if any
41 Analytical Hierarchical Ship Material Condition Model Conventions LevelofIndentureNTAsSYSTEMSUB-SYSTEMCOMPONENTSUB-COMPONENTPartPieceLowerWARFARE AREANTA
42 MFOM Horizontal Structure Sub System AAA has a horizontal relationship to Sub System ABBWARFARE AREANTAsSYSTEMSUB-SYSTEMCOMPONENT’sHorizontal FamilyModel structure that consists of two or more Parents with one or more children, in two or more systems that can be aligned (cross connected) to functionally support another Parent. An example would be Trim and Drain Pumps on a Submarine or use of AN/SPS-49 Radar when AN/SPN-43 Radar is inoperative.This Model structure may also contain like Children to support variable operational demands with the number of Children linked to the system design criteria. Example: Multiple pumps in the Fire Main System or Auxiliary Machinery Cooling Water System.Component AAAB becomes a child of Sub System ABB to show horizontal relationshipThe systems were designed to provide redundancyCross connection
43 MFOM Operational Structure Sub System AAA has an operational relationship to System ADWARFARE AREANTAsSYSTEMSUB-SYSTEMSub System AAA becomes a child of System AD to highlight a procedural or process interdependencyThe systems were NOT designed to provide this interdependencyOperationally Linked FamilyModel structure consisting of two or more Parents in the same or different systems, where the Material Condition of families are associated. Example: Boiler and Boiler Inspection Device or TACAN and Flight Operations.
45 MFOM RoadmapMFOM provides the Navy Maintenance community with a single, authoritative, centrally managed application that provides the necessary data upgrades and improvements to support readiness and maintenance reporting.MFOM is designed for easy incorporation into ERP.MFOM is the ship readiness feed for DRRS-N (equipment pillar)MFOM will address readiness appropriate to the FRTPMFOM will be the primary waterfront maintenance tool for budgeting, organizing and planning (O, I & D level)MFOM will associate detailed funding with appropriate maintenance actionsMFOM will improve the interaction between established maintenance tools to leverage necessary capabilities and functionalities.MFOM will provide validation, screening and brokering (VSB) capability for building the maintenance work packages based on metrics.
48 INSURV MI TrendsMFOM Readiness ValueMFOM Functional Area
49 Maintenance Planning in Predictive MFOM Predictive MFOM Work ListBuilds future availabilities based on VSB protocolsUses degradation curves to predict future failuresInputs known Class Maintenance Plan actions and Modernization in out yearsUses projected Man-day ratesOutputsIndicates predicted MFOM readiness value based on work listLinks modernization to maintenance actionsEstimates funding to achieve desired FRP readiness and Life Cycle readinessProvides information to port loading model and OPNAV campaign model
50 Readiness drill down Drill Down Capability Clicking on Equipment Pillar bubble brings up top five degraded systems degrading this capability on a shipSystem Name, JSN, ETR, CSMP Summary are displayedStarting PointNot all units are alike, so straight average of each unit is not preferredAggregate similar units into Subgroups, then average unit OVL assessments to provide Subgroup OVL.Average subgroup OVL assessments to produce Group OVL for the Capability.System Name JSN ETR CSMP SummaryChill Water Sys EM /09/06 # 2 CWP Seal leaksAnchor Windlass EA /15/06 Debris in lube oil
51 Operational Performance Values and Definition Fully operable: System or equipment capable ofperforming all required functions with only cosmeticdiscrepanciesTotally Inoperative: The system or equipment notcapable of performing required functionality.Example - when the power switch is turned onNothing happens, no lights on thepanel, nothing.1.00.00.50.18.104.22.168.22.214.171.124Operable: System or equipmentcapable of performing all requiredfunctions with minor discrepanciesInoperative: 0.2 or 0.1 –System or equipment notcapable of performingintended functions usingposted operatingproceduresMinor problems: 0.8 or 0.7System or equipmentFunctions when requiredwithout modification ofoperating instructions andprocedures. Minordiscrepancies are likely toimpede function in the nearterm.During Model development and after the hierarchal structure has been created, Weighting Values are developed. This is accomplished by associating the expected Operational Performance relative to the “parent” as provided by the “child”.An example is a car. The car as viewed as a “parent” has four tires that are “children” If one is the car-parent and the left front tire-child goes flat, what is the Operational Performance of the car? This scenario is repeated for each of the children in that family group.Major problems: 0.4 or 0.3 –System or equipment cannotperform one or more intendedfunctions. Functions may berestricted by time, environmentalor operational conditionsLimited capability: 0.6 or 0.5 –System or equipment is capable ofperforming intended functions, but notat full operational requirements, or notcapable of performing required functionsin all operating modes