370 likes | 1.11k Views
2. . . . . . . POM/BudgetProcess. Today's Maintenance Strategy. . Ship Maintenance
E N D
1. 1 Ship Material Condition Metrics Model Maintenance Figure Of Merit (MFOM) 2.0 Mr. Dale Hirschman
MFOM PM, FFC N434
2. 2
3. 3 How does MFOM Help
4. 4 Basics of MFOM
5. 5 MFOM Roadmap 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 FRTP
MFOM will be the primary waterfront maintenance tool for budgeting, organizing and planning (O, I & D level)
MFOM will associate detailed funding with appropriate maintenance actions
MFOM 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.
6. 6 MFOM Data Inputs MFOM takes input from existing documentation
Automated Work Requests (i.e., 2 Kilos)
Inspections, Certifications, Assessments and Visits (ICAVs)
Alterations
Repair work
CASREPs, etc
Tag-outs (eSOMS)
Machinery Monitoring Systems (e.g., ICAS)
IPARS
Class Maintenance Plans
Other Technical Documentation (DFS, UROs, IMMPs, Master Spec Catalog, MRCs)
MFOM starts with existing ships configuration data
All records for each hull from CDMD-OA
7. 7
8. 8 Ships Material Condition Readiness
9. 9 Feeding Readiness Metrics Slide starts with MRAS vessels
MRAS operating on NIAPS and FAS servers
2K 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 command
DRRS-N feeds DRRS
Slide starts with MRAS vessels
MRAS operating on NIAPS and FAS servers
2K 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 command
DRRS-N feeds DRRS
10. 10 Readiness Drill Down Drill Down Capability
Clicking on Equipment Pillar bubble brings up top five degraded systems degrading this capability on a ship
System Name, JSN, ETR, CSMP Summary are displayed
Starting Point
Not all units are alike, so straight average of each unit is not preferred
Aggregate similar units into Subgroups, then average unit OVL assessments to provide Subgroup OVL.
Average subgroup OVL assessments to produce Group OVL for the Capability.
Starting Point
Not all units are alike, so straight average of each unit is not preferred
Aggregate similar units into Subgroups, then average unit OVL assessments to provide Subgroup OVL.
Average subgroup OVL assessments to produce Group OVL for the Capability.
11. 11
12. 12 TMA/TMI Data Analysis Systems screened overall in first process
Systems ranked in second process
Systems investigated in third process
Parts Cost, CASREPs, Days Down Time, 2K Volume, & Man-hours
13. 13
14. 14 Predictive MFOM Future Status Screen
The main screen for MFOM Predictive
Five Sections
Ship/Version/Year selection
Availability Schedule
Budget Requirements & Controls
MFOM Table
Work List
15. 15 Maintenance Planning in Predictive MFOM Predictive MFOM Work List
Builds future availabilities based on VSB protocols
Uses degradation curves to predict future failures
Inputs known Class Maintenance Plan actions and Modernization in out years
Uses projected Man-day rates
Outputs
Indicates predicted MFOM readiness value based on work list
Links modernization to maintenance actions
Estimates funding to achieve desired FRP readiness and Life Cycle readiness
Provides information to port loading model and OPNAV campaign model
16. 16 Readiness / Maintenance Interfaces
17. 17 Building the ModelA Coordinated Group Effort
18. 18 FIN(Location)(Function)(ID)
19. 19 IUID DDG 51 Pilot Project Overview MFOM 2.0 will implement a pilot project integrating IUID technology
Will use the MRAS shipboard database
Effort focused on DDG-51 class
Pilot 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 are two major components involved in the proposal;
Determining the plan for uniquely identifying shipboard equipment and assets
Application of IUID technology to mark legacy equipment and assets and register IUID numbers in the DoD registry
Marking would take place primarily at the organizational level during maintenance.
MRAS and MFOM will be modified to track equipment with an associated IUID.
20. 20 Project Schedule By 31 January 2007:
Determine procurement requirements for IUID marking technology
By 1 February 2007:
Develop training curriculum and material for training Ships Force
By 1 April 2007:
Conduct Pre-Pilot testing at the NSWCCD-SSES to verify database communications
By 1 May 2007:
Begin application of IUIDs on shipboard equipment
Conduct training for ships force personnel
By 1 September 2007:
Complete DDG 51 Class Pilot program IUID application
By 30 September 2007:
Complete post DDG 51 Class Pilot program analysis and reporting
21. 21 Project Schedule
Identify Construct # 1: Enterprise Identifier / Serial Number Requirements
FFC UIC ( DoDAAC) / Special Handling Indicator/Unique Random Serial Number
Develop and implement IUID Data processes and policy for DDG 51 legacy items:
Develop non-shipboard initial IUID SOP
Determine UID tag type and application/attachment process
Determine standard IUID reader requirements
Develop initial IUID SOP shipboard
Initial Pre-Pilot project plan for testing of DDG 51 Class IUID Project at NSWCCD-SSES Philadelphia
Identify approximate DDG 51 Class shipboard item inventory for Pilot IUID/MID labeling:
Project ship identified as USS FORREST SHERMAN DDG 98
ESOMS inventory identified
Commence shipboard pilot. ESD 23 April 2007
22. 22
23. 23 Backup Software Screenshots
24. 24
25. 25
26. 26 Ships Material Condition Readiness
27. 27
28. 28
29. 29
30. 30
31. 31 Analytical Hierarchical Ship Material Condition Model Conventions
32. 32 MFOM Horizontal Structure Horizontal Family
Model 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.
Horizontal Family
Model 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.
33. 33 MFOM Operational Structure
34. 34