1 / 19

CG-LIMS Brief to Leadership Council

CG-LIMS Brief to Leadership Council. Program Manager: CDR Dan Taylor, CG-9334 Sponsor’s Rep: Mr. Jim Sylvester, CG-442. Supporting: Predictable time on mission Predictable time on liberty. Agenda. Capability Overview CONOP Scenarios Specific Improvement Examples

nyx
Download Presentation

CG-LIMS Brief to Leadership Council

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. CG-LIMS Brief to Leadership Council Program Manager: CDR Dan Taylor, CG-9334 Sponsor’s Rep: Mr. Jim Sylvester, CG-442 Supporting: Predictable time on mission Predictable time on liberty

  2. Agenda • Capability Overview • CONOP Scenarios • Specific Improvement Examples • Multiple Inventory Types • Maintenance Capture 2

  3. Linked Capability We need linked IT capability for Mission Support which will enable: Predictable time on mission, and predictable time on liberty. Change OPS CM MAINT SCM Budget MPC --------- --------- --------- We know we need this kind of integrated capability. We do not have a system that does this for us today. 3

  4. Maintenance & Inventory Type 2 (AMMIS) • Maintenance time is captured on MPC. • Two types of inventory. • Type 2 shown here. • Type 3 on next page. 4

  5. Maintnenance & Inventory Type 3 (CMPlus) 5

  6. Maintenance Capture (EAL) 6

  7. EAL Maintenance Capture Upon inspection found rivets to be pulled out of door. Also found two cracks on map case one beginning on each side. Stop drilled cracks and installed doubler on map case. Installed two new rivets to secure map case to door. All maintenance accomplished IAW 1H-60-3. No MPC 3-hours Maintenance Labor Hours (MLH) 1 2 3 • Time on maintenance task captured in EAL not ACMS (no MPC). • Parts (including cost) consumed in this example, not connected to maintenance action nor configuration items. 7

  8. Multiple Inventory Tools and Locations CMPlus Storeroom Type 3 & 5 Material CMPlus CMPlus AMMIS • To predict maintenance readiness, two supply systems must be consulted. • Neither supply system is directly connected to the supply requirements on the MPC. • All supply demand data lags (we know what we used, not what we need). MPC --------- --------- --------- Type 3 Type 2 Complete AMMIS Storeroom Type 2 & 4 material (mostly) AMMIS 8

  9. Maintenance Capture (with MPC) CMPlus Storeroom Type 3 & 5 Material CMPlus ACMS EAL AMMIS CMPlus FTO • Maintenance captured in EAL (description), and in ACMS (MPC, labor hours, etc). • Parts not directly related to CI. • Actual parts consumed not directly relatable to the maintenance action performed unless parts are serialized. MPC --------- --------- --------- 2 Type 3 1 Type 2 Complete AMMIS Storeroom Type 2 & 4 material (mostly) AMMIS 9

  10. Maintenance Capture (no MPC) CMPlus Storeroom Type 3 & 5 Material EAL CMPlus !??!! • Maintenance captured in EAL, not in ACMS. • Labor hours captured in EAL not easily related to specific maintenance actions or configuration items (no MPC); • Parts consumption not related to the CI’s • Failure data not being captured in ways that robustly supports RCM feedback. AMMIS Storeroom Type 2 & 4 material (mostly) AMMIS 10

  11. The Future Supply Vendor Confirmed parts available, Schedule maintenance. EAL CG-LIMS updates EAL. • All maintenance captured consistently • Labor hours captured and related to CI’s. • Parts consumption related to the CI’s • Parts consumption driven by maintenance and OPS • Failure data captured in ways that robustly supports RCM feedback. MPC --------- --------- --------- Complete 2 Type 3 1 Type 2 Consolidated Warehouse and Supply system CG-LIMS 11

  12. Linked Capabilities OPS CM MAINT SCM Budget MPC --------- --------- --------- CG-LIIMS EAL 12

  13. Why It Matters • CG-LIMS screens will be this intuitive • EAL and CG-LIMS will share information • Accuracy of status will remain excellent. • The predictability of status will improve. • Improved ability to plan Maintenance and Missions • Improved ability to plan and defend budgets • Better Operational and Support decisions Predictable time on Mission. Predictable time on Liberty. 13

  14. Questions? More info available here …and postings to iCommandant web journal. 14

  15. Total Asset Visibility CM O-Level & D-Level OSC CG-LIMS AOPS MISLE C4ISR & Facilities Others Private Industry Operational Tempo and Availability requirements create demand signal for support which is captured in CG-LIMS; maintenance, parts, and asset status visible to enterprise. Operational assignments and cost will be optimized; relationship measurable; budgets defendable. Financial integration is critical. CG-LIMS (OV-1) 01-Sep-2009Coast Guard Logistics Information Management System Financial Management (CFO) Enterprise Decisions Availability OpTempo Data Cost MPC ----------------------------------------------------------------------------------------------------------------- Data Knowledge CG-LIMS Remote Ops support (satellite not included) + MM SCM TIM CM CG Modernization Product Line Mgt Logistics & Service Centers ForceCom OpCom CG-LIMS will support product lines in a Bi-Level maintenance model at the logistics/service centers, with Configuration Mgt (CM) fed by Tech Info Mgt (TIM), capturing Maintenance Mgt (MM) information, which will drive Supply Chain Mgt (SCM) delivering operational capability. DoD & OGA’s

  16. ORD High Level – Seg #1 v FOC 16

  17. Maintenance Capture • Maintenance tech identifies discrepancy • If discrepancy is work for which there is an MPC, the tech may: • Enter the discrepancy into EAL, or • Schedule the MPC for execution in ACMS directly • In both cases, a record of maintenance execution will be captured in ACMS • In some cases, there may not be an EAL entry detailing the work except by reference of MPC#. • The MPC work is recorded on paper and provided to a Field Terminal Operator (data entry person) • If discrepancy is work for which there is not an MPC: • The tech will enter the discrepancy into EAL • When the work is complete, the actions taken will be entered into EAL • There will be no record of work captured in ACMS • Time will be captured in EAL • There is limited ability to report on both planned (MPC) and unplanned (no MPC) together • Cost information on completed maintenance work completed for type 2 and 4 parts; • Task hours from an MPC in ACMS, or , from EAL entry. 17

  18. Methodology (cont) • Determined high level Requirements taxonomy • Configuration Management (CM): MIL-HDBK-61A • Maintenance Management (MM): MIL-P-24534, NAVAIR 00-25-403 & 406, MSG3, RCM Handbook, Policy, Process Guides • Supply Chain Management (SCM): SCOR Model • Technical Data/Information Management (TDM/TIM): S1000D • Requirements categories • Functional • Non-Functional (system requirements) • Interface • Reporting • Industry Standards • Functional areas indicated above • Documented using DoDAFv1.5, SA, and DOORS • DoDAF views included in ORD: • Operational Views: OV-1, 2, 3, 4, 5 • System Views: SV-1 (Segment #1 and FOC) 18

  19. CONOP Scenarios 3.1 Mission Support Scenarios 3.1.1 A Day in the Life of an Operational Unit 3.1.1.1 Maintenance Planning 3.1.1.2 Supply Chain – Part 1 (maintenance demand) 3.1.1.3 Maintenance Preparation 3.1.1.4 Maintenance Execution 3.1.1.5 Supply Chain – Part 2 (reparable/serialization) 3.1.2 Interaction between CG-LIMS and EAL 3.1.2.1 Asset Availability 3.1.2.2 Discrepancy Discovery 3.1.2.3 Post-Operations Reporting 3.1.3 Configuration Management 3.1.3.1 Configuration Changes 3.1.3.2 Configuration Audit 3.2 System Support Scenarios 3.2.1 Readying the Production Environment 3.2.1.1 System Installation, Configuration and Integration - Host Site Infrastructure 3.2.1.2 System Installation, Configuration and Integration – Distributed Environment 3.2.2 Failure Planning (system monitoring & failover) 3.2.3 When Disaster Happens (Disaster Recovery) 19

More Related