cg-lims brief to leadership council

Assistant Commandant forEngineering and Logistics (CG-4)

HomelandSecurity

United StatesCoast Guard

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 missionPredictable time on liberty

HomelandSecurity



19-Nov-2009

Agenda

• Capability Overview

• CONOP Scenarios

• Specific Improvement Examples– Multiple Inventory Types– Maintenance Capture

2

HomelandSecurity



19-Nov-2009

Linked Capability

3

OPS CM MAINT SCM Budget

MPC---------------------------

Change

We know we need this kind of integrated capability. We do not have a system that does this for us today.

We need linked IT capability for Mission Support which will enable:Predictable time on mission, and predictable time on liberty.

HomelandSecurity



19-Nov-2009

Maintenance & Inventory

4

Type 2(AMMIS)

• Maintenance time is captured on MPC.• Two types of inventory.

o Type 2 shown here.o Type 3 on next page.

HomelandSecurity



19-Nov-2009

Maintnenance & Inventory

5

Type 3(CMPlus)

HomelandSecurity



19-Nov-2009

Maintenance Capture (EAL)

6

HomelandSecurity



19-Nov-2009

EAL Maintenance Capture

7

• 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.

1. 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.

2. No MPC3. 3-hours Maintenance Labor Hours (MLH)

1

2

3

HomelandSecurity



19-Nov-2009

CMPlus

Multiple Inventory Tools and Locations

8

CMPlus Storeroom Type 3 & 5 Material

AMMIS Storeroom Type 2 & 4 material (mostly)

MPC---------------------------

Type 3

Type 2

Complete

CMPlusAMMIS

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).

HomelandSecurity



19-Nov-2009

AMMIS

Maintenance Capture (with MPC)

9

EALAMMIS

MPC---------------------------

2 Type 3

1 Type 2

Complete

CMPlus



FTO

CMPlusACMS

• 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.

HomelandSecurity



19-Nov-2009

CMPlus


Maintenance Capture (no MPC)

10

EAL


AMMIS

• 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.

!??!!

HomelandSecurity



19-Nov-2009

Consolidated Warehouse and Supply system

The Future

11

EAL

CG-LIMS

MPC---------------------------

2 Type 3

1 Type 2

Confirmed parts available,Schedule maintenance.

SupplyVendor

CG-LIMS updates EAL.

Complete

• 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.

HomelandSecurity



19-Nov-2009

Linked Capabilities

12

OPS CM MAINT SCM Budget

MPC---------------------------

EAL

CG-LIIMS

HomelandSecurity



19-Nov-2009

Why It Matters

13

• 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.

HomelandSecurity



19-Nov-2009

Questions?

14

…and postings to iCommandant web journal.

More info available here

http://cgportal.uscg.mil/lotus/myquickr/-cg-lims-desc-cg-logistics-infor-management-sys-

https://epmo.uscg.mil/

http://www.uscg.mil/acquisition/lims/

https://www.intelink.gov/wiki/Category:CG-LIMS

https://www.intelink.gov/blogs/_cg-lims/

http://www.uscg.mil/comdt/blog/

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.

Enterprise Decisions

Financial Management (CFO)

Product

Line

Mgt

CG Modernization

CG-LIMS (OV-1) 01-Sep-2009Coast Guard Logistics Information Management System

MPC------------------------------------------------------------------------------------------------

-----------------

Knowledge

O-Level

&

D-Level

CMTotal

Asset

Visibility

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.

Logistics &Service Centers

OpCom

ForceCom

DoD & OGA’s

Remote Ops support(satellite not included)

Data

CG-LIMS

AOPS

MISLE

Others

OSC

C4ISR & Facilities

CM SCMTIM MM+CG-LIMS

Data

PrivateIndustry

CostAvailabilit

y

OpTempo

http://cgvi.uscg.mil/media/main.php?g2_itemId=107485




http://cgvi.uscg.mil/media/main.php?g2_itemId=222216&g2_imageViewsIndex=1

HomelandSecurity



19-Nov-2009

ORD High Level – Seg #1 v FOC

16

HomelandSecurity



19-Nov-2009

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

HomelandSecurity



19-Nov-2009

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 DoDAF v1.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

HomelandSecurity



19-Nov-2009

CONOP Scenarios3.1 Mission Support Scenarios

3.1.1 A Day in the Life of an Operational Unit3.1.1.1 Maintenance Planning3.1.1.2 Supply Chain – Part 1 (maintenance demand)3.1.1.3 Maintenance Preparation3.1.1.4 Maintenance Execution3.1.1.5 Supply Chain – Part 2 (reparable/serialization)

3.1.2 Interaction between CG-LIMS and EAL3.1.2.1 Asset Availability3.1.2.2 Discrepancy Discovery3.1.2.3 Post-Operations Reporting

3.1.3 Configuration Management3.1.3.1 Configuration Changes3.1.3.2 Configuration Audit

3.2 System Support Scenarios3.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

cg-lims brief to leadership council

Documents