CG-LIMS ORD

U.S. Deparlment of Homeland Security
Washington, rx:t 20528
I

HOlmeland
August 9,2011 Se¢urity

ACQUISITION DECISION MEMORANDUM

:MEMORANDUM FOR: Vice Admiral Sally Brice-O'Hara
Vice Commandant
United States ~=..,~

FROM: Rafael Borras
Under Secretary 0

SUBJECT: Approval ofthe United States Coast Guard's LQgistics Infonnation
Management System Operational Requirementsl Document dated
June 15,2011
!
The Department of Homeland Security (DHS) Acquisition Program Manage~ent Division (APMD)
has reviewed the United States Coast Guard's (USCG) Logistics Infonnation Management System
(CG LIMS) Operational Requirements Document (ORD) dated June 15,20111. The ORD allows
the end-user to accurately defme the capabilities required for the acquisition program manager to
enable the end-user to execute the assigned missions.
i
The CG LIMS program manager has adequately addressed the APMD review! comments. The
program is commended for gaining approval ofthe ORD prior to the Acquisition Review Board
(ARB) to review and approve the CG LIMS program and the planned acquisition strategy. The
CG LIMS program should schedule their ARB this year. .

The CG LIMS ORD is approved.

It is the responsibility of USCG to appropriately promulgate the decisions an~ directions of this
ADM and the attachment to the affected organizations. The APMD will pro~ide support and
assistance. Please send action items, status, and supporting documentation toI
APMD.CAD@hq.dhs.gov. Should you have any questions, please contact Gjbson Kerr at
(202) 343-4534. I

Attachment

cc:
Assistant Secretary for Policy
Under Secretary for Science and Technology Directorate (S&T)
Under Secretary for Management
Deputy Under Secretary for Management
Chief Administrative Officer
Deputy Chief Financial Officer
Chief Human Capital Officer
Chief Information Officer
Chief Procurement Officer
Chief Security Officer
Office ofthe General Counsel, Principal Deputy General Counsel
Chief of Staff to the Under Secretary for Management
Executive Director, Acquisition Program Management Division
Director, Contract Operating Division, OCPO
Director, Test Evaluation and Standards, S&T
Director, Operational Test and Evaluation, S&T
Chief of Staff, USCG
Assistant Commandant for Acquisition, USCG
Head of Contracting Activity, USCG
Program Executive Officer, USCG
Director, USCG Requirements and Analysis, USCG (CG-771)

2

Operational Requirements Document (ORO)

For

USCG Logistics Infonnation

Management System v1.0 (CG LIMS)

Approved by:
~~UnQl -
~-JW-l(
Date

Approved by:

I
from: Tjkia.N.RI9ajns@ySCQ dbs goy on behalf of Riggins. Jjkia I
To: CAP. APMP I
cc: Pfallt:z Jobn; Bloomfield. patrick M: Lyons James E: Taylor Daniel CAPT: Thomson. u,: Boyd Peter; tlaIler...
~ Sayle. Reojnald I

Subject: CG·UMS ORP for PHS Approval I
Date: Wednesday, June 15, 2011 8:47:48 AM I
AtlaChments: CG·UMS.zlp
CG·' IMS ORO yl.Q Transmittal Memo lS1ynll pdf

Greetings,

Attached is the CG-UMS Operational Requirements Document (ORO) v1.0 for D~S approval. This
is an official submission, no hard copy to follow. Thank you. I

Tikia Riggins-Jones
Administrative Assistant,
Acquisition Support Office, CG·924
202.475.3156 (0)
202.475.3903 (f)
"Ufe isn't about how to survive the storm, but how to dance in the rain."

OPERATIONAL REQUIREMENTS DOCUMENT
for the I
COAST GUARD LOGISTICS INFORMATION MANAGEME/fT SYSTEM
Version 1.0 I

Prepared by:
zrr/lli1if YJO
IDate

Submitted by:
il/tflztJ'O
I
-Date

Endorsed by:
I ("j.zt:i/ 1.010

Date

Endorsed by:
'1!ibO,<>
Dlite i

Endorsed by:
1Ug/;}(lJO
Date
!.1f '.J iJ'l;J ,-"
CI
Endorsed by:
i
DJte /

- Endorsed by: ,}t1/ to
Dat, I
Endorsed by: t::IJ
Date
/Z" be,. 0

Endorsed by: ...
Endorsed by: L
~-------------------
Assistant Commandant for Resources (CG-8)

-Endorsed by: CZ8 to~-e 'to, 0
Date
CG Endorsement: APR 272011
Date
DHS Approval: See attached
Under Secretary for Management Date

TABLE OF CONTENTS
Title/paragraph Page Number

REVISION SUMMARY ................................................................................................................ 1
EXECUTIVE SUMMARY ............................................................................................................ 2
SECTION 1: INTRODUCTION .................................................................................................... 3
1.1 Purpose .................................................................................................................................. 3
1.2 Background ........................................................................................................................... 3
1.3 Timeframe ............................................................................................................................. 4
1.4 Constraints........................................................................................................................... 11
SECTION 2: MISSION REQUIREMENTS ................................................................................ 12
2.1 Operating Requirements...................................................................................................... 13
2.2 Concept of Operations ......................................................................................................... 14
SECTION 3: EFFECTIVENESS REQUIREMENTS .................................................................. 17
3.1 Basic Requirements ............................................................................................................. 17
3.2 Interoperability .................................................................................................................... 19
3.3 Communications/Information Technology ......................................................................... 20
3.4 Sensors ................................................................................................................................ 21
SECTION 4: SUITABILITY REQUIREMENTS ........................................................................ 22
4.1 Design.................................................................................................................................. 22
4.2 Supportability and Sustainment (Integrated Logistics Support) ......................................... 23
4.3 Reliability ............................................................................................................................ 23
4.4 Availability .......................................................................................................................... 23
4.5 Maintainability .................................................................................................................... 23
4.6 Survivability ........................................................................................................................ 23
4.7 Personnel, Safety, Human Factors, and Environmental Considerations ............................. 24
4.8 Training Requirements ........................................................................................................ 24
SECTION 5: KEY PERFORMANCE PARAMETERS .............................................................. 26
SECTION 6: TRADE-OFFS ........................................................................................................ 27
6.1 Ease of Use .......................................................................................................................... 27
6.2 Ease of Administration ........................................................................................................ 28
6.3 Adaptability to a Change Centric Organization .................................................................. 29
APPENDIX A: LIST OF ACRONYMS ...................................................................................... 30
APPENDIX B: CG-LIMS REQUIREMENTS ............................................................................. 32
APPENDIX C: DODAF CG-LIMS ARCHITECTURE .............................................................. 84

ii

REVISION SUMMARY

Version Change Effective Date
Version 1.0 Initial Draft 21-May-2010
Version 1.0 Incorporated CG-8 comments 25-Oct-2010
Version 1.0 Incorporated VCG comments 21-Apr-2011

1

EXECUTIVE SUMMARY

This Coast Guard Logistics Information Management System (CG-LIMS) Operational Requirements Document
(ORD) translates the Mission Need Statement (MNS) and Concept of Operations (CONOPS) into system level
performance capabilities. It establishes the high level functionality required for CG-LIMS to support the
enterprise business model and modernize logistics information systems, enabling common tools to be used
across the Coast Guard to support a common mission support process.

A Requirements Integrated Product Team (IPT) was chartered by the Assistant Commandant for Engineering
and Logistics (CG-4) to define CG-LIMS requirements for a system to fully support the modernization and
business process transformation initiatives.

This ORD is to be used by the CG-LIMS Project Manager (CG-9334) as the overarching guide that defines the
scope of the project by clearly defining the requirements of the Project Sponsor.

CG-LIMS will consolidate and replace legacy logistics systems with Commercial Off The Shelf (COTS) tools,
implemented in a manner that minimizes customization to preserve supportability and leverages the Coast
Guard’s emerging Service Oriented Architecture (SOA).

CG-LIMS will provide the Coast Guard with standardized enterprise management capability for asset
configuration, maintenance, supply chain, and technical information. It will integrate with the Coast Guard core
financial system and provide accurate transaction-level data for financial accountability and analysis. Optimal
capability will result through further integration with workforce management systems, eliminating dual entry of
personnel, training, and competencies and enabling real time job-cost valuations.

This ORD defines five segments of discrete functions to be delivered through the acquisition. Each segment
will provide capability to the field for immediate use.

Segment 1 will implement configuration management and maintenance management functionality. Because
CG-LIMS will replace the Asset Logistics Management Information System (ALMIS) as the preferred tool to
manage transformed assets in accordance with the modernized mission support business model, ALMIS assets
will be targeted first for migration to CG-LIMS. The functional requirements for Segment 1 eclipse the
functional capability provided by the Asset Computerized Maintenance System (ACMS) subsystem of ALMIS.
Consequently, once Segment 1 is implemented and all assets previously enrolled in ACMS are migrated to CG-
LIMS, ACMS can be retired. Remaining assets will be migrated to CG-LIMS according to the logistics
transformation schedule.

Segment 2 will implement supply chain management functionality, replacing the Asset Maintenance
Management Information System (AMMIS) subsystem of ALMIS once migration is complete.

Segment 3 will implement technical information management functionality, providing a single repository for
electronic technical documentation which is retrievable, viewable, and printable from the CG-LIMS application.
Changes to technical documentation will also be managed and promulgated from within the system.

Segments 4 and 5 will implement the external interfaces necessary to automate integration with enterprise
financial and workforce management systems and systems outside of the Coast Guard. The financial system
integration (Segment 4) will be critical to overcoming the enterprise challenge to comply with the Chief
Financial Officers (CFO) Act of 1990.

2

SECTION 1: INTRODUCTION

CG-LIMS shall be an automated, integrated, mission support information system that links the functions and
data associated with the following functional areas: configuration management, maintenance management,
supply chain management, and technical document management. The first segment of CG-LIMS will support
the configuration management and maintenance management functional requirements defined in this ORD, as
well as the necessary interface, reporting, and non-functional requirements to support those functions. The
second segment will add supply chain management capability, and the third segment delivers technical
information management. The fourth segment implements full integration with the Coast Guard core
accounting system. The fifth segment completes the required interfaces, including enterprise workforce
management systems and logistics systems external to the Coast Guard.

1.1 Purpose

The purpose of CG-LIMS is to support Coast Guard Modernization by providing a tool by which the Mission
Support organization can fully implement their portion of the future enterprise business model through logistics
transformation. The CG-LIMS project will modernize logistics information systems, enabling common tools to
be used across the enterprise to support common logistics process. The information managed by CG-LIMS will
provide support for the enterprise financial transformation and accountability of Coast Guard investments.

As stated in the MNS dated 16 June 2008, CG-LIMS is intended to be a centrally-managed, integrated,
enterprise wide logistics information management system that leverages government and industry standards and
best practices. By implementing a logistics system capable of supporting improved business process and
organizational structures, the Coast Guard will optimize operational support, reduce costs across the
organization, provide real time financial data, and align with Department of Homeland Security (DHS)
enterprise architecture.

Specifically, CG-LIMS shall provide the IT capability to support the enterprise asset management functionality
for configuration, maintenance, supply chain, and technical information across all product lines. It is intended
to be the single information management system needed to support logistics for all assets, including aircraft,
vessels, shore facilities and Command, Control, Communications, Computers and Information Technology
(C4IT) systems. Throughout this document, the term “asset” is understood to be anything that requires logistics
support.

The CONOPS gives context for anticipated CG-LIMS use and should be used as a guide to help the system
developer configure the solution to meet the requirements spelled out in this document.

1.2 Background

The Coast Guard currently invests in multiple logistics information systems representing many communities
and business processes. Neither the systems nor the processes are well integrated and do not provide the
necessary asset readiness status and maintenance parts visibility to effectively support Coast Guard missions.
Our inability to share real time information regarding asset status, configuration, inventory, and maintenance
history degrades preparedness and has a negative impact on operations. Additionally, many of these systems
have been organically developed and carry with them significant support costs.

The Coast Guard’s inability to comply with the CFO Act and the related Federal Financial Management
Improvement Act of 1996 (FFMIA) is closely tied to our inability to correctly capture and track financial
information in our Core Accounting System that is traceable back to the transaction level of detail in our
logistics systems. We must enable the Coast Guard’s Chief Financial Officer to disclose organizational

3

financial performance by providing transparent, traceable financial information from our logistics system to our
core accounting system.

Our legacy logistics systems are not consistently aligned with the Coast Guard or DHS enterprise architectures.
This investment is an opportunity to rectify this situation by endorsing those architectures, potentially serving as
a model logistics system for the DHS enterprise. We must be able to effectively share information with external
systems and data bases, including many managed by agencies throughout the Departments of Defense and
Homeland Security.

Our legacy logistics systems are currently tied to their asset-specific business processes. However, many of
those processes are changing as the Coast Guard aligns aircraft, vessel, C4IT, and facility logistics processes.
The existing logistics information systems cannot be economically changed to fully support the new process or
scaled to meet the enterprise requirements. 1 Process transformation to a common business model has prepared
the foundation for a common logistics Information Technology (IT) tool.

1.3 Timeframe

One of the principles of this acquisition is to rapidly supply capability to the field through an incremental
acquisition strategy as defined in the DHS Acquisition Directive 102-01. An incremental approach is preferred
because the requirements are well defined and stable, and the Coast Guard has considerable interest in
delivering a usable product as soon as possible. The first segment required for implementation includes the
configuration management and maintenance management functional requirements (see Sections 2.1.2 and 3 for
a full description of the requirements and rationale for how they are broken into segments). A fully capable
system is required from Segment 1, providing asset configuration, maintenance management and deployment
functionality in accordance with the Coast Guard modernized mission support business model. Follow-on
segments will move forward in staggered overlapping efforts, benefiting from the lessons learned and known
configuration of Segment 1.

Table 1-1 lists the assets targeted for enrollment under this acquisition. The level of effort required to enroll
these assets will be dependent on several factors, including but not limited to logistics transformation status,
availability of Reliability Centered Maintenance (RCM) analysis data, any outstanding requirements to perform
additional RCM analysis, loading of data from legacy databases, asset operational requirements, geographic
location, and training requirements. Due to the availability of existing data, anticipated logistics transformation
progress, and several other factors (including the expanded capabilities of CG-LIMS), all assets listed in Table
1-1 may not be fully transformed to the new business model and fully enrolled in CG-LIMS under this
acquisition. This will require additional efforts outside the scope of this acquisition.

Deployment plans shall be coordinated with the applicable Deputy Commandant for Mission Support (DCMS)
teams so that transformation efforts effectively incorporate CG-LIMS capability and support. It should be noted
that not all assets and units in the Coast Guard are listed in Table 1-1. DCMS will enroll individual units and
asset types not targeted by this acquisition into CG-LIMS once it is deployed, according to transformation
strategy and schedules outside the scope of the CG-LIMS acquisition.

1 LMTO Report CG406T2, Coast Guard Logistics System of the Future Risk Assessment, dated February 2005
4

Table 1-1

DY = Deployment Year
FY= Fiscal Year

Segment 1 Deployment




CMPlus, FLS, SAMS)
Extract Data From
Legacy Databases
(ACMS, AMMIS,

Number of Units
(AC&I Funded)
RCM Required
Asset Type Asset

Aviation
HC-144A MRS-MPA (including Mission System 36*
Yes No DY01 DY02 DY03 DY04 DY05
Notes: Pallet)
HC-130J Long Range Surveillance Aircraft Yes No DY01 DY02 DY03 DY04 DY05 6*
This includes all HC-130H Long Range Surveillance Aircraft (including 25
air stations and Yes No DY01 DY02 DY03 DY04 DY05
Seaspray Radar & Casper C4IT Pallet)
ALC (26). MH-65C Multi-Mission Cutter Helicopter & H-65 Yes No DY01 DY02 DY03 DY04 DY05 101
MH-60T Medium Range Recovery Helicopter & HH- 42
This will include Yes No DY01 DY03 DY04 DY05 DY06
60 Helicopter
all District and C-143 Command and Control Aircraft Yes No DY01 DY03 DY04 DY05 DY06 1
Areas offices that C-37A Long Range Command and Control Aircraft Yes No DY01 DY03 DY04 DY05 DY06 1
monitor aircraft HU-25 "Guardian" Medium Range Surveillance 18
availability. Yes No DY01 N/A N/A N/A N/A
Aircraft
Sector & DOG
Small Boats 1st District DY01 DY03 DY04 DY05 DY06
Sector Northern New England Yes Limited
Standard boats Sector Boston Yes Limited
including: Sector Southeastern New England Yes Limited
Sector Long Island Yes Limited
55’AtoN (18) Sector New York Yes Limited
49’ AtoN (26) 5th District DY01 DY03 DY04 DY05 DY06
26’ AtoN (58) Sector Delaware Bay Yes Limited
25’ TPS (59) Sector Baltimore Yes Limited
52’ D (457)
Sector Hampton Roads Yes Limited
MLB-HW (4)
Sector North Carolina Yes Limited
47’ MLB (117)
7th District DY02 DY03 DY04 DY05 DY06

5





CMPlus, FLS, SAMS)
Extract Data From
Legacy Databases
(ACMS, AMMIS,

Number of Units
(AC&I Funded)
RCM Required
Asset Type Asset

41’ UTB (134) Sector Charleston Yes Limited
33’ SPC (44) Sector Jacksonville Yes Limited
24’ SPC (8) Sector Miami Yes Limited
45’ RBM (180) Sector Key West Yes Limited
Sector St. Petersburg Yes Limited
It is assumed that Sector San Juan Yes Limited
all standard boats 8th District DY02 DY03 DY04 DY05 DY06
will have the Sector Mobile Yes Limited
RCM analysis Sector New Orleans Yes Limited
completed. Sector Corpus Christi Yes Limited
Sector Houston-Galveston Yes Limited
Non-standard
Sector Lower Mississippi Yes Limited
boats:
Sector Ohio Valley Yes Limited
Sector Upper Mississippi River Yes Limited
Non-standard
boats will be 11th District DY02 DY03 DY04 DY05 DY06
included in the Sector San Diego Yes Limited
AC&I funded Sector Los Angeles-Long Beach Yes Limited
deployment plans Sector San Francisco Yes Limited
with the Sectors. 13th District Yes Limited DY02 DY03 DY04 DY05 DY06
It is anticipated Sector Portland Yes Limited
that an RCM Sector Seattle Yes Limited
analysis will 9th District DY02 DY02 DY05 DY06 DY07
need to be Sector Lake Michigan Yes Limited
completed. Sector Sault Ste Marie Yes Limited
Sector Detroit Yes Limited
Sector Buffalo Yes Limited
14th District DY02 DY02 DY05 DY06 DY07
Sector Guam Yes Limited
Sector Honolulu Yes Limited
17th District Yes Limited DY02 DY02 DY05 DY06 DY07
Sector Anchorage Yes Limited

6





CMPlus, FLS, SAMS)
Extract Data From
Legacy Databases
(ACMS, AMMIS,

Number of Units
(AC&I Funded)
RCM Required
Asset Type Asset

Sector Juneau Yes Limited

C4ISR
DGPS Yes No DY01 DY03 DY04 DY05 DY06 1
Rescue 21 Sites by Sector which includes remote Same As Same As Same As Same As Same As 35*
towers and stations with counsels. No Yes Hosting Hosting Hosting Hosting Hosting
District District District District District
NAIS No Yes DY03 DY03 DY05 DY06 DY07
VTS No Yes DY03 DY03 DY05 DY06 DY07
Cutters
87’ CPB Same As Same As Same As Same As Same As 73
Note: Yes No Hosting Hosting Hosting Hosting Hosting
This will include District District District District District
all standard 110’ WPB Same As Same As Same As Same As Same As
cutter small boats Yes No Hosting Hosting Hosting Hosting Hosting
{25’ Cutter Boat District District District District District
(91), 35’ Cutter 378’ WHEC Yes Yes DY03 DY03 DY03 DY07 DY08
Boat – Over the 270’ WMEC Yes Yes DY03 DY03 DY03 DY07 DY08
Horizon (33)} 210’ WMEC Yes Yes DY03 DY03 DY03 DY07 DY08
418’ Legend Class Maritime Security Cutter - Large Yes No DY04 DY03 DY03 DY07 DY08 8*
154’ Sentinel Class Patrol Boat Yes No DY04 DY04 DY03 DY07 DY08 58*
Off Shore Patrol Cutter Dependant Dependant Dependant Dependant Dependant 25*
Yes No on procure- on procure- on procure- on procure- on procure-
ment status ment status ment status ment status ment status
240’ Great Lakes Icebreaker Yes Yes DY04 DY04 DY04 DY08 DY09 1
420’ Healy Class Icebreaker Yes Yes DY04 DY04 DY04 DY08 DY09 1
225’ Juniper Class Seagoing Buoy Tender Yes No DY04 DY04 DY04 DY08 DY09 16

7





CMPlus, FLS, SAMS)
Extract Data From
Legacy Databases
(ACMS, AMMIS,

Number of Units
(AC&I Funded)
RCM Required
Asset Type Asset

175’ Keeper Class Coastal Buoy Tender Yes No DY04 DY04 DY04 DY08 DY09 14
140’ Bay Class Icebreaking Tug Yes Yes DY04 DY04 DY04 DY04 DY09 9
65’ Small Harbor Tug No Yes Same As Same As Same As Same As DY09 11
Hosting Hosting Hosting Hosting
District District District District
160’ Inland Construction Tender Yes Yes DY04 DY04 DY04 DY04 DY09 4
100’ Inland Buoy Tender Yes Yes DY04 DY04 DY04 DY04 DY09 2
75’ River Buoy Tender Yes Yes DY04 DY04 DY04 DY04 DY09 12
65’ Inland Buoy Tender Yes Yes DY04 DY04 DY04 DY04 DY09 2
65’ River Buoy Tender Yes Yes DY04 DY04 DY04 DY04 DY09 6
295’ Barque Eagle Yes Yes DY04 DY04 DY04 DY04 DY09 1
399’ Polar Class Icebreakers Yes Yes DY04 DY04 DY04 DY04 DY09 2
Facilities
SILC Assets Yes No Same as Same as Same as Same as Same as
Facilities include Hosting Hosting Hosting Hosting Hosting
~25,000 real Note: CG-LIMS will be deployed to SILC assets District District District District District
property assets, according t the Sector deployment schedule, with the Segment 2 Segment 2 Segment 3 Segment 4 Segment 5
~25,000 fixed exception that Segment 1 will be deployed at the same
AtoN and time as Segment 2.
~25,000 floating
AtoN aids.
Additional User
Training Operational Centers (Districts, Areas, HQ, etc.) No No DY01 DY02 DY03 DY04 DY05 12
Training Centers No No DY03 DY03 DY05 DY06 DY07 9
Communications Stations No No DY03 DY03 DY05 DY06 DY07 7
Service and Logistics Centers No No DY01 DY02 DY03 DY04 DY05 5
ESU/ESD Same As Same As Same As Same As Same As 79
No No Hosting Hosting Hosting Hosting Hosting
NESU Same As Same As Same As Same As Same As 9
No No
Hosting Hosting Hosting Hosting Hosting
8





CMPlus, FLS, SAMS)
Extract Data From
Legacy Databases
(ACMS, AMMIS,

Number of Units
(AC&I Funded)
RCM Required
Asset Type Asset

National Motor Lifeboat School, Cape Disappointment, 1
No No DY01 DY03 DY04 DY05 DY06
WA and Yorktown, VA
Remaining Units No No DY05 DY05 DY05 DY05 FY22
Assets
Specifically 179’ Cyclone Class Patrol Boat 3
Excluded Loran Stations

9

1.3.1 Initial Operational Capability Date
The targeted Initial Operational Capability (IOC) date for Segment 1 is FY13.

IOC for Segment 1 can be declared when the functionality specified in this ORD for
Segment 1 is being provided and supported in a production environment for the HC-
144A MRS-MPA product line.

Segment 1 shall be delivered in such a way that once all assets in ACMS are fully
implemented in CG-LIMS, ACMS can be retired, and any new assets being enrolled into
the new business model can be enrolled directly into CG-LIMS. Other databases, such as
Fleet Logistics System (FLS) and the Shore Asset Management System (SAMS), can be
retired when all assets contained in those databases are fully migrated to CG-LIMS.

1.3.2 Coast Guard Support Date
The anticipated Coast Guard Support Date (CGSD) is FY17. However, elements of both
contractor and organic support will be required to finish deployment and continue with
the logistics transformation process at varying levels throughout the lifecycle of the
incremental acquisition, depending on the final support and implementation strategy.
Operations and maintenance funding should start as soon as IOC of Increment 1 is
achieved and scaled upward to Full Operational Capability (FOC). For organic
deployment support, the processes and infrastructure set up by the Logistics
Transformation Program Integration Office (LTPIO) should be considered to the greatest
extent practical when developing the deployment plan and schedule.

To ensure effective support, performance and training systems support shall be developed
to support each segment of capability.

1.3.3 Incremental Operational Capability Date(s)
The segments shall be implemented according to the following schedule:

1.3.3.1 Segment 1 – Configuration and Maintenance Management IOC FY13.
1.3.3.2 Segment 2 – Supply Chain Management IOC FY14.
1.3.3.3 Segment 3 – Technical Information Management IOC FY15.
1.3.3.4 Segment 4 – Financial Integration IOC FY16.
1.3.3.5 Segment 5 – Human Resource & External System Integration IOC FY17.

1.3.4 Full Operational Capability Date
The targeted FOC date for CG-LIMS is FY17.

FOC for CG-LIMS can be declared when all segments of the CG-LIMS acquisition have
been delivered and have the capability of being fully deployed in a production
environment, the support infrastructure is in place, the CG-LIMS Product Line Manager
(PLM) takes over full responsibility for support, and all segments have been deployed to
a production environment for the HC-144A MRS-MPA product line.

10

1.3.5 Other Key Dates
It is anticipated that all five segments will be completely deployed to all the assets listed
in Table 1-1 by FY22. At that time it is envisioned the CG-LIMS acquisition project will
be terminated.

1.4 Constraints

The functional requirements for CG-LIMS are derived from industry standards. The
non-functional requirements are derived from both industry standards and the current
Coast Guard enterprise architecture. Each requirement cites the standard(s) from which it
was derived, and the system configuration should never conflict with a cited standard.
The most critical industry standards that shall be maintained are those from the Financial
Systems Integration Office (FSIO); all segments of CG-LIMS shall support the desired
end state where logistics transactions accurately account for financial events and provide
that data for the core accounting system and general ledger. The requirements are
maintained by the Coast Guard in The Enterprise Architecture Management System
(TEAMS) and are printed in Appendix B.

The enterprise Department of Defense Architecture Framework (DODAF) architecture is
also maintained in TEAMS, and the CG-LIMS operational and system views of that
architecture are found in Appendix C. These views present the required functional
process flows and system integration at a very high level, and should not be violated
without approval from the DCMS CCB.

CG-LIMS shall be comprised of commercially available software (COTS) complying
with the Open System Interconnection (OSI) Reference Model for open systems, and it
shall operate on the Coast Guard One Network (CGOne) from a standard Coast Guard
Workstation employing a Coast Guard approved operating system.

The deployment plan will be constrained by the level of transformation already achieved
by individual asset types, as described in section 1.3. Assets that have already been
transformed will be able to be migrated into CG-LIMS without back-fit RCM analysis.
However, because the logistics transformation effort is on-going, the schedule set in
Section 1.3 is based on the best information available at the time of this ORD publication.
Assets that have not been transformed when the acquisition project is ready to enroll
them into CG-LIMS will require some level of back-fit RCM analysis to re-baseline the
assets and transform them prior to CG-LIMS enrollment.

CG-LIMS supports both Asset Management and Supply Chain Management, as defined
in the Coast Guard Enterprise Architecture (CGEA), and the Federal Enterprise
Architecture (FEA) Business Reference Model (BRM). Ultimately, CG-LIMS shall
interface with multiple information objects and align with the CGEA Information
Inventory, as well as DHS Information Architecture. The Coast Guard IT Products and
Standards Inventory, DHS EA Transition Strategy, DHS Technical Reference Model
(TRM) and FEA TRM shall be considered when identifying an appropriate technical
solution that meets the requirements in this document.

11

SECTION 2: MISSION REQUIREMENTS

The Coast Guard defines logistics as all support activities associated with developing,
acquiring, testing, and sustaining the mission effectiveness of operating systems
throughout their service lives. 2 The overall objective of logistics is Mission Support:
provide our people and customers the right material, in the right condition, at the right
place, at the right time, in the right quantity, at the right cost.

Until recently, the Coast Guard placed insufficient emphasis on integrating logistics
across asset types throughout their lifecycle. For the most part, logistics was
synonymous with supply. We did not have a vision outlining what an integrated logistics
system would look like. The various components of capability were managed within
“stovepipes” which led to decisions about one component without consideration of its
impact upon other components. As a result, we are saddled with narrow and inefficient
business processes and are unable to optimize the effectiveness of our assets. It is evident
that we need to integrate our logistics system, or risk a negative impact to units
performing the missions of the Coast Guard. 3

The Coast Guard’s role in supporting the DHS mission of securing America is grounded
in its ability to provide capable, prepared operating forces. The ongoing acquisition
programs highlight the Coast Guard’s need to support new, complex assets within an
improved Coast Guard business process that provides visibility of parts and equipment
throughout the organization. The Coast Guard’s current logistics support capability,
which is tied to stressed, organically-designed IT systems and disparate business
processes, is not prepared to adequately handle the new assets, much less provide the
needed visibility and integrate the business process supporting them.

Recent efforts to comply with the CFO Act and FFMIA illustrate the need for improved
logistics within the Coast Guard. To adequately measure financial performance, provide
transparency to our financial history and obligations, and execute effective budgeting and
financial planning, the Coast Guard needs centrally-managed logistics capable of tracking
transactions throughout their lifecycle and properly integrating with the Coast Guard’s
core accounting system.

The mission need can be summed up by stating the current disparate IT logistics systems
in the Coast Guard cannot adequately fill the gap between current practice and what is
needed to support the modernized, standard business model. An unconstrained IT
solution configured to industry standards in support of our modernized business model is
necessary to fill the gap.

2 COMDTINST M4000.2 (series), Coast Guard Logistics Handbook
3 COMDTINST 4000.5 (series), Coast Guard Logistics Doctrine

12

2.1 Operating Requirements

2.1.1 Operating Environment
CG-LIMS shall be accessible via Coast Guard Standard Workstations in normal staff and
field office settings, on the floor of repair facilities and warehouses, and on operational
assets (including underway assets with periods of limited and no connectivity). The
system shall be hosted at a DHS and Coast Guard approved data center.

2.1.2 Operational Functions
CG-LIMS will provide functionality to support asset configuration, maintenance, supply
chain, and technical information management, as well as the associated interface and
reporting requirements.

The requirements for CG-LIMS are being managed within the IBM DOORS® and
System Architect® (SA) software systems in TEAMS. These documents and data
represent the functional baseline and changes will be controlled in accordance with the
CG-LIMS Configuration Management Plan (CMP) and approved by the CG-LIMS
Configuration Control Board (CCB). Appendix B contains the requirements exported
from DOORS, which are organized into functional areas as depicted in Figure 1. The
requirements are linked to enterprise business process models as appropriate, which are
documented in DODAF architectural views in Appendix C.

Sections 3 and 4 will further discuss the requirements and architecture artifacts found in
Appendices B and C.

2.1.3 Geographic Area
CG-LIMS shall support the enterprise business process through a centrally managed
system that is accessible anywhere with CGOne connectivity. CG-LIMS shall also
provide adequate functionality to users that require system use during periods of limited
and no network connectivity and synchronize with the production database when
connected.

2.1.4 Environmental Performance Envelope
CG-LIMS is not expected to have any special environmental requirements. It is expected
to operate on any workstation intended to provide CGOne access to CG enterprise
applications.

13

Figure 1. CG-LIMS Functional Breakdown

2.2 Concept of Operations

The CG-LIMS CONOPS explains in more detail how the system will be used. CG-LIMS
will be the backbone of Coast Guard mission support. It will be the tool by which
mission support personnel retrieve information about the configuration and condition of
assets and record activities supporting those assets. It will be used to support a common
business process across all asset communities. The following summary describes the
anticipated operating schemes.

2.2.1 Configuration Management
Asset configuration will be maintained and managed in the system. The product baseline
will be linked to the allocated and functional baselines, so potential changes to the
configuration can trace back to the requirements they support, and potential changes to
requirements can trace to physical configuration items designed to support the original
requirements. Approved configurations will be viewable to users, and maintainers will
be notified if they try to install a part that is not approved. Configuration auditors will
compare the system data with physical configuration to determine if approved
configurations are being maintained. The system will manage the workflow associated
with proposing, approving, and executing changes to approved configurations.
Engineering changes to physical assets or technical documentation can be initiated by
various methods and users, depending on the source and rationale for the proposed
change. The system will facilitate the review and approval of change requests, allow
approved changes to automatically apply to similar asset types, and generate pending
maintenance work orders to execute the changes.

14

2.2.2 Maintenance Management
Field maintenance personnel and product line managers will use CG-LIMS to execute the
Coast Guard’s maintenance program. All maintenance will be categorized as either
organizational (O-Level) or depot (D-Level) level, according to the bi-level maintenance
strategy supported by DCMS. Individual units will be responsible for using CG-LIMS to
identify and schedule O-Level maintenance required by them. They will be able to
schedule the maintenance, requisition parts, view detailed procedures, access technical
manuals, publications and drawings, and record the details of maintenance execution.
Product Line Managers will identify D-Level maintenance and arrange its execution. If
D-Level maintenance is performed by Coast Guard personnel, they will be assigned
within CG-LIMS and use the system the same way units do for O-Level maintenance. If
the work is performed by entities outside of the Coast Guard, the PLM will ensure the
maintenance executed is recorded in CG-LIMS.

CG-LIMS will accept entry of new discrepancies, which will generate a new work order
to track the problem and corrective maintenance execution. The system will push new
work orders through a progression to determine whether they are O-Level or D-Level
maintenance actions, generate any required casualty reports, and record maintenance
actions through successful resolution.

Maintenance activities executed in CG-LIMS will initiate supply activities within
CG-LIMS. When parts are requisitioned to perform maintenance, supply activities will
be driven based on location, inventory availability, and safety stock levels. The system
will support the DCMS business model by pushing parts to local units prior to scheduled
maintenance, based on the maintenance requirements managed in CG-LIMS. Data
analyzed from CG-LIMS will help optimize parts inventories necessary to handle
unscheduled, corrective maintenance. Maintenance data will also be used to improve
reliability centered maintenance strategies for certain equipment and identify bad parts so
they are not reused on multiple assets.

CG-LIMS will be capable of publishing configuration, maintenance, and supply data to
the enterprise SOA via services to the Enterprise Service Bus (ESB). These services will
enable any other system to consume the information for purposes of planning, reporting,
or mission execution. This ORD is being written with the best current information
regarding the desired enterprise architecture for the operations systems within the
modernized Coast Guard. Consequently, as a specific requirement of this acquisition,
CG-LIMS will explicitly integrate with the Electronic Asset Logbook (EAL) application
to show operations personnel the availability of assets according to their maintenance
status. If an asset has limited capability due to outstanding or ongoing maintenance, EAL
will highlight the limitation and display information provided by CG-LIMS describing
the nature of the limitation, timeframe expected until resolution, and any required
operational tests to be performed prior to mission operation. While the EAL interface
should provide all the necessary information for operators, it will always include a link to
outstanding CG-LIMS activities affecting mission availability so that users have the
option to open maintenance activity details.

15

2.2.3 Supply Chain Management
CG-LIMS will provide the Supply Chain Management (SCM) functionality necessary to
effectively manage inventory, requisitioning, procurement requests, and distribution. It
will support the business model in such a way that planned and actual maintenance will
automatically drive supply activities.

Parts will be pushed to field units from inventory control points as they are needed for
both upcoming planned maintenance and unplanned corrective maintenance. CG-LIMS
will monitor stocking levels and automatically notify responsible parties when
procurements are necessary. Item managers will have full visibility into both local and
centralized inventories to make supply movement decisions. Maintenance technicians
will use the system to identify and requisition supply required to perform assigned tasks.
Unit level supply activities will be recorded in the system for enterprise visibility.
Serialized parts will be tracked and forever linked to the history of maintenance and
supply activity.

The system will generate procurement requests as needed and interface with an enterprise
procurement management system. All transactions associated with performing supply
chain actions will account for financial events by capturing the necessary
transaction-level data and providing it for the enterprise core accounting system.

2.2.4 Technical Information Management
CG-LIMS will be the enterprise repository for technical information associated with
assets, such as drawings, technical manuals and publications. It will adhere to the
S1000D industry standard and support standard use of Interactive Electronic Technical
Manuals (IETMs). If technical material is maintained, there will be usable hyperlinks
from within the configuration, maintenance, and supply chain user interfaces so that the
material is easily accessible, viewable, and printable. Units expected to use CG-LIMS in
a disconnected environment shall have technical material stored locally and accessible
through the same hyperlinks. CG-LIMS will manage changes to technical documentation
the same way it manages engineering changes described in the configuration
management requirements, including the management of workflow and tracking and
executing the changes.

16

SECTION 3: EFFECTIVENESS REQUIREMENTS

3.1 Basic Requirements

Appendix B lists the CG-LIMS requirements being managed in DOORS. They are
organized according to the functional breakdown shown in Figure 1. It is intended that
the stated requirement be tested in the applicable context of the supporting referenced
standard, not that the entire referenced standard be tested. To achieve faster fielded
capability with less risk, CG-LIMS shall be acquired in discrete segments according to an
incremental acquisition strategy.

The legacy logistics system currently being used as the Coast Guard’s best-in-breed
logistics system to support Modernization and enterprise Logistics Transformation is
ALMIS. DCMS is currently enrolling legacy assets into ALMIS after they have been
transformed to the new business model, but the mission need ultimately recognizes
ALMIS cannot scale to meet the IT need for Modernization. CG-LIMS shall initially
target ALMIS for replacement so that modernized IT can be available as soon as possible
to support Logistics Transformation. Once CG-LIMS delivers functional capability
adequate to migrate transformed assets from other legacy systems, those assets shall be
targeted for enrollment and the legacy system targeted for disposal. Assets not yet
transformed shall undergo back-fit RCM prior to enrollment into CG-LIMS.

Since maintenance drives supply in the Coast Guard business model, and asset
configuration is critical to managing maintenance, Segment 1 shall start with the
configuration management requirements.

ACMS is a module in ALMIS that integrates a level of configuration and maintenance
functionality in such a way that it would be extremely difficult and costly to replace one
functional part without the other while maintaining satisfactory support for assets.
Consequently, CG-LIMS Segment 1 is targeting the whole of ACMS for replacement and
includes the maintenance management requirements. Until the Coast Guard implements a
FSIO compliant core accounting system, CG-LIMS will interface with the existing
accounting system to post accounting transactions. CG-LIMS will integrate with the
FSIO compliant core accounting system if the system is available in this segment.

Current AMMIS architecture provides opportunity to target supply chain management
functionality in a discrete segment. Segment 2 shall incorporate the SCM requirements
and integrate with Segment 1 according to the Internal Interface requirements and the
OV-5 process models in Appendix C. Until the Coast Guard implements a FSIO
compliant core accounting system, CG-LIMS will interface with the existing accounting
system to post accounting transactions. CG-LIMS will integrate with the FSIO compliant
core accounting system if the system is available in this segment.

Segment 3 shall provide the required technical information management functionality.
Technical documentation for assets, materials, and maintenance and supply activities
shall be seamlessly managed in the system so that hyperlinks from configuration,
maintenance, or supply activities provide access to the latest approved versions. Any

17

asset that has been enrolled in CG-LIMS by the time Segment 3 is being implemented
shall have its technical information enrolled in CG-LIMS.

Segment 4 shall include the integration between CG-LIMS and the expected FSIO
compliant integrated accounting system. The integration of CG-LIMS and the expected
FSIO compliant integrated accounting system will be included in Segments 1 and/or
Segment 2, if the FSIO compliant integrated accounting system is available in Segment 1
and/or Segment 2. Segment 4 shall be deferred until the Coast Guard has completed
enough of the financial transformation effort to warrant integration to the FSIO compliant
integrated accounting system.

The remaining system interfaces with Coast Guard and external systems will be
configured in Segment 5.

The interface requirements for CG-LIMS, while not implemented in many cases until
Segments 4 and 5, are still valid for earlier segments. While an interface may not be
configured and implemented until Segment 4, the function within CG-LIMS that will be
making the interface requires the capability from the start. Likewise, the reporting
requirements are valid for every segment.

The following breakdown outlines the requirements detailed in Appendix B:

3.1.1 Configuration Management
The National Consensus Standard for Configuration Management (ANSI/EIA-649) is the
industry standard to which the configuration management requirements are based. The
reference cited in the requirements, MIL-HDBK-61A, is accepted guidance to comply
with the industry standard.

3.1.1.1 CG-LIMS shall provide a Configuration Management Planning capability as
detailed in Appendix B.
3.1.1.2 CG-LIMS shall provide a Configuration Management Identification capability
as detailed in Appendix B.
3.1.1.3 CG-LIMS shall provide a Configuration Control capability as detailed in
Appendix B.
3.1.1.4 CG-LIMS shall provide a Configuration Status Accounting capability as
3.1.2.5 CG-LIMS shall provide a Configuration Verification and Audit capability as

3.1.2 Maintenance Management
3.1.2.1 CG-LIMS shall provide a Maintenance Management capability as detailed in
Appendix B.

18

3.1.3 Supply Chain Management
3.1.3.1 CG-LIMS shall provide a Requisition Management capability as detailed in
Appendix B.
3.1.3.2 CG-LIMS shall provide an Inventory and Warehouse Management capability as
3.1.3.3 CG-LIMS shall provide a Transportation, Distribution, and Disposition
Management capability as detailed in Appendix B.

3.1.4 Technical Information Management
3.1.4.1 CG-LIMS shall provide an Information Management capability as detailed in
Appendix B.
3.1.4.2 CG-LIMS shall provide a Content Development Management capability as
3.1.4.3 CG-LIMS shall provide a Content Use capability as detailed in Appendix B.

3.1.5 Interface
3.1.5.1 CG-LIMS shall provide External Interface capability as detailed in Appendix B.
3.1.5.2 CG-LIMS shall provide Internal Interface capability as detailed in Appendix B.

3.1.6 Reporting
3.1.6.1 CG-LIMS shall provide Reporting capability as detailed in Appendix B.

3.2 Interoperability

Appendix C illustrates DODAF artifacts exported from SA that represent the Coast
Guard enterprise business model that CG-LIMS shall support. The Operational View
(OV) and System View (SV) diagrams in the DODAF architecture are actively
maintained under configuration control in TEAMS as part of the Coast Guard Enterprise
Architecture. The included views provide the following information to help frame the
context for the requirements:

3.2.1 OV-1: High-Level Operational Concept Graphic.
This view depicts the overall capability of CG-LIMS to support the Coast Guard’s
modernized business model and shows its relationship with stakeholders, including the
CFO.

3.2.2 OV-2: Operational Node Connectivity Description.
This view shows the relationship between operational nodes (or physical units using
CG-LIMS). Because this represents the new business model, a single abstract node is
used to represent many distinct units that will follow the same business process, such as
Organizational Units, Logistics and Service Centers, and Inventory Control Points. The
“need lines” connecting operational nodes show where two nodes share information. The
activities listed in a node indicate a mission support activity directly supported by CG-
LIMS.

19

3.2.3 OV-3: Operational Information Exchange Matrix.
This matrix shows the relationship between individual information exchanges (defined
between activities in the OV-5) and operational nodes. In effect, it drills into the need
lines depicted in the OV-2 and more clearly describes which information CG-LIMS will
pass between two organizational units during the course of mission support.

3.2.4 OV-4: Organizational Relationships Chart.
This illustrates the command structure and relationships between CG-LIMS user
communities, as opposed to the relationships associated with a business process flow.

3.2.5 OV-5: Operational Activity Model.
This view describes the standard operations that are conducted in the course of achieving
mission support under the modernized business model. Thus far, the OV-5 detail is
limited to the activities supporting CG-LIMS Segment 1 requirements. Throughout the
OV-5 diagrams in Appendix C, an activity colored green indicates that CG-LIMS has
requirements to support that activity. The first OV-5 diagram shows a hierarchy chart for
the activities under “Manage Logistics.” The remaining OV-5 diagrams use the IDEF0
(Integration Definition for Function Modeling) modeling methodology to flow through
the business model, where inputs, outputs, controls, and mechanisms connect activities.
It should be noted that the OV-5 depicts sequence between activities, but not time. The
connections between activities are defined as information exchanges, which can be seen
in the OV-3.

3.2.6 SV-1: Systems Interface Description.
This view includes two diagrams. The first illustrates the system interfaces expected of
CG-LIMS at FOC. The second shows the expected interfaces for initial deployment of
Segment 1. Since Modernization is currently using ALMIS to support the transformation
of assets to the new business model, it will be the first IT system targeted for replacement
by CG-LIMS. However, until ACMS and AMMIS are retired, a level of interface
between those applications and CG-LIMS will be required to ensure continuity of
services across the ALMIS suite. Once the system architecture is in place for Segment 1
and more information is known about the CG-LIMS solution, the system views for
Segments 2 through 5 can be defined.

3.3 Communications/Information Technology

One of the key mission needs CG-LIMS will help rectify is financial accountability and
CFO compliance. To accomplish this, integration with financial, procurement, human
resource, and non-consolidated logistics systems in accordance with section 3.1.5 will be
crucial.

The Coast Guard shall use Service Oriented Architecture (SOA) to share information
between IT systems, in accordance with requirement INT-01-09 in Appendix B.

20

3.4 Sensors

CG-LIMS shall be compatible with technologies not yet used extensively in the Coast
Guard mission support community.

3.4.1 Sensor Interface Requirements
3.4.1.1 CG-LIMS shall have the capability to interface with Radio Frequency
Identification (RFID) tag readers.
3.4.1.2 CG-LIMS shall have the capability to interface with Bar-code scanners.
3.4.1.3 CG-LIMS shall have the capability to interface with Machinery Control and
Monitoring Systems (MCMS).

21

SECTION 4: SUITABILITY REQUIREMENTS

Section 5 of Appendix B lists the non-functional requirements being managed in
TEAMS. They are separated into process requirements and service requirements:

4.0.1 Non-Functional
4.0.1.1 CG-LIMS shall provide system Process capability as detailed in Appendix B.
4.0.1.2 CG-LIMS shall provide system Service capability as detailed in Appendix B.

The remaining paragraphs in this section of the ORD shall help clarify those
requirements and serve as a starting point for an Integrated Logistics Support Plan
(ILSP).

4.1 Design

Because the Coast Guard is adopting a standardized logistics business model across the
enterprise, the preferred IT solution to support IT modernization and consolidation of
business functions is a COTS product. Since the core business process across the
enterprise is neither unique to the Coast Guard, military, or government, nor different
than industry standards and best practices, the Coast Guard will leverage proven
technology to support IT modernization. 4

Further rationalization for targeting COTS tools centers on the current state of market and
evolution of known products that support our core requirements. Market research
conducted after the release of the Preliminary ORD proved that market leading COTS
products could effectively support our requirements with minimal or no customization.
COTS products in this market segment offer additional advantages to consumers because
the incentives and market pressures compel economically rational decisions, resulting in
constant innovation, little waste, and a rising standard of development. COTS products
supporting enterprise asset management functions are more cost effective, adaptable, and
functional in both the long-term and short-term. Licensing fees are potentially much
lower than up-front development and lifetime maintenance costs associated with custom
development. The schedule for development and implementation of a COTS system is
typically much shorter, helping to reduce overall enterprise cost. Market demands force
proven COTS products to improve with technology and pass those advantages to current,
as well as prospective users. Proven leaders in the enterprise-wide marketplace must
remain competitive with function-specific applications that support the standard, proven
processes successful organizations employ; as such, the functionality found in quality
COTS products that support our requirements can be very robust.

4 LMTO Report CG406T2, Coast Guard Logistics System of the Future Risk Assessment, dated February
2005

22

If one product does not meet the needs of the CG-LIMS requirements, a combination of
products shall be considered before custom development is evaluated.

4.2 Supportability and Sustainment (Integrated Logistics Support)

In order that an ILSP and sustainment strategies can be developed (including a training
analysis), it is important that this acquisition have, as an early deliverable, clear and
adequate documentation for system maintenance and support. Due to modernization and
the unique scope of this acquisition, all stakeholders shall be engaged early to ensure the
Coast Guard has a plan supported at the highest levels. A CG-LIMS product line should
be grown as part of the acquisition so that the support community has ownership and
competence in the system prior to CGSD. The Asset Project Office (APO) and C4IT
Service Center should be used heavily to help steer logistics planning and ensure the
Coast Guard is prepared to receive and support CG-LIMS as it is delivered.

Trade-offs are discussed in Section 6. Ease of system administration is discussed,
because its relative value has a potentially significant impact on support and sustainment
over the lifecycle of the system.

4.3 Reliability

The method for defining the reliability requirements (Appendix B NF-02-05 and Key
Performance Parameter (KPP) 5.2) is detailed in Section 2.4.3.2 of the CONOPS. The
key metric for measuring reliability is the probability that the system will perform
without failure between maintenance periods.

4.4 Availability

The method for defining the availability requirements (Appendix B NF-02-03 and KPP
5.1) is detailed in Section 2.4.3.1 of the CONOPS. The key metric for measuring
availability is downtime of the system in hours over a calendar year.

4.5 Maintainability

Section 4.0.1 contains the detailed system maintainability requirements.

Periods of planned system maintenance shall be coordinated so that down time impact is
minimized. There are no specific maintenance interval requirements, as long as the
availability and reliability requirements are met.

4.6 Survivability

Section 4.0.1 contains the detailed system survivability requirements.

Logistics plans developed to support this system shall include provisions for effective
continuity of operations during catastrophic events, such as a Katrina-like hurricane or an
attack, failure or other accident where redundant power and connectivity are completely

23

lost. Section 2.4.5 of the CONOPS describes how the sustainment community plans to
deal with threats and hazards once the system is supported by the Coast Guard.

4.7 Personnel, Safety, Human Factors, and Environmental Considerations

Aside from the section 4.0.1 requirements, Section 6 of this document (Trade-Offs)
discusses important usability attributes. The CONOPS section 2.5 provides further
insight into expected staffing and support structure of the Coast Guard IT sustainment
community.

4.8 Training Requirements

The PM shall engage the Assistant Commandant for Human Resources (CG-1), Human
Systems Integration for Acquisitions Division to analytically and systematically
determine Performance Support and Training (PS&T) requirements so that all CG-LIMS
capability delivered during the acquisition is supported.

PS&T includes familiarization for initial crews upon delivery, qualification systems,
embedded performance support systems, stand alone performance support systems, job
aids of all types, and resident training. It integrates training strategies with elements of
logistics support to most effectively and efficiently achieve the personnel performance
levels required to operate, maintain, and support systems and assets. It includes the
“tools” used to provide learning experiences, such as computer-based interactive
courseware, simulators, actual equipment (including embedded training capabilities on
actual equipment), and IETMs, as well as the methods by which they are used. The
PS&T system shall consider both unit-level operators and support personnel.

A specific strategy for CG-LIMS performance support and training shall include DCMS
Modernization teams as a focal point for initial training so that CG-LIMS use can be
effectively incorporated into transformation efforts.

All recommendations for PS&T solutions shall be supported by systematic analyses that
are validated and approved by CG-1. A key component in these analyses is the Front
End Analysis (FEA) process, which is a formal procedure for determining the most
effective and efficient performance support systems. The FEA process is specifically
detailed in the CG Training System Standard Operating Procedures (SOP), which are
intended to ensure the process is auditable, verifiable, traceable, and repeatable.

The CG Training System SOP requires that all maintenance and operator tasks be
identified, sorted, and analyzed up front, to determine whether performance gaps are best
closed by resident training or non-training solutions. Obtaining system support
documentation early in the acquisition will facilitate this analysis. The size and scope of
various types of performance support requirements are generally identified at this step.
Additional analyses are then conducted on each performance support system to determine
the best means (location, source, type) of delivery. After appropriate support
requirements are identified, it is imperative that equal rigor be applied to the analysis of

24

potential solutions as to how this support shall be designed, developed, implemented and
its effectiveness continuously evaluated, in order to minimize life-cycle cost.

To optimize the efficiency of these performance support systems, it cannot be overstated
that not all performance requirements require the development of formal performance
support or training. Analysis and development of interventions shall be limited by a
reasonable understanding of which knowledge, skills, attributes and abilities learners
need, and shall take into account whether such competencies are better acquired in other
existing training programs (i.e. Basic Training or A-school).

CG-1 will consider any commercially-provided support tools and systems and training
that might be available with the COTS product in order to determine if it is effective and
efficient for Coast Guard application. In many cases, commercially-provided support is
used to roll out initial delivery while the Coast Guard considers the benefit of developing
organic, long-term performance support and training systems.

If formal training is required, CG-1 will partner with Force Readiness Command to
ensure that it is appropriately delivered, resourced, documented, and supported in the
Formal Training System.

25

SECTION 5: KEY PERFORMANCE PARAMETERS

KPP Threshold Objective
5.1 Operational Availability 5 CG-LIMS shall provide an CG-LIMS shall provide an
operational availability of at least operational availability of at least
98.6%. 99.2%.
5.2 Operational Reliability 6 CG-LIMS shall provide an
operational reliability of at least
93.1%.
5.3 System Response CG-LIMS shall accommodate a CG-LIMS shall accommodate a
registry of 56,000 named users registry of 56,000 named users with
with up to 35,000 concurrent users up to 35,000 concurrent users with
with no more than 5 seconds for no more than 3 seconds for any page
any page to be displayed and 10 to be displayed and 5 seconds for
seconds for acknowledgment of acknowledgment of any transaction.
any transaction.
5.4 Interoperability: Financial For every transaction meeting the
Compliance definition of a financial event in
accordance with FSIO OFFM-NO-
0106, CG-LIMS shall capture
100% of the data required for
FFMIA compliance.
5.5 Interoperability: Financial CG-LIMS shall provide financial CG-LIMS shall provide financial
Transaction Visibility 7 managers access to 100% of managers access to 100% of
transaction-level detail for each transaction-level detail for each
financial event within 24 hours of financial event within 1 hour of
posting. posting.
5.6 Asynchronous Endurance The system shall implement The system shall implement
mechanisms to process CG-LIMS mechanisms to process CG-LIMS
activities at units operating in activities at units operating in
asynchronous environments for at asynchronous environments for at
least 3 months with zero network least 6 months with zero network
connectivity. connectivity.
5.7 Security Provide for sensitive but
unclassified, and/or unclassified
information in accordance with
COMDTINST M5500.13 (series)
and COMDTINST 5500.21, and
maintain the standards set forth in
NIST 800-37 and other application
security documents to protect
against unauthorized disclosures
of privacy information.

5 CG-LIMS CONOPS Section 2.4.3.1.
6 CG-LIMS CONOPS Section 2.4.3.2.
7 For every segment of CG-LIMS implementation, financial managers of the Coast Guard shall have access
to the transaction-level detail of each financial event for purposes of reconciliation and producing financial
reports. To achieve FOC, CG-LIMS shall automate the integration of this data with the general ledger and
enterprise core accounting system.

26

SECTION 6: TRADE-OFFS

The requirements in this ORD were deliberately developed to remain at a high functional
level that adheres to industry standards. Consequently, there is no prioritization of the
requirements, as they are all fundamental to the success of the enterprise system. The
KPPs in Section 5 highlight the most critical requirements, and are the only instances
where objectives are different from thresholds. In all cases, system lifecycle costs are
more important in source selection than acquisition costs. CG-LIMS will be the
backbone of Coast Guard mission support for the foreseeable future, and choices that
push excessive costs beyond the acquisition should be avoided.

When evaluating COTS products that meet the requirements detailed in this ORD, three
factors apart from cost shall be weighed heavily as product differentiators: ease of use,
ease of administration, and adaptability to a change-centric organization. These
differentiators should be used to help make a distinction between proposed solutions
when direct costs appear to be different. If these factors are favorable for one product, a
higher cost is justified.

6.1 Ease of Use

Usability is a quality attribute relating to how easy something is to use. More
specifically, it refers to how quickly people can learn to use something, how efficient
they are while using it, how error-prone it is, and how much users like using it. For
CG-LIMS to be effective, operational users will need to be able to use it in a standard
way to manage standard information. If it is difficult to use, information captured may
not be as complete and useful to the organization as intended, damaging the benefit
gained by enterprise management of asset information. The expected user base
population for CG-LIMS is large enough that small differences in time associated with
completing a task can add up to significant enterprise impact.

Usability experts can help evaluate proposed solutions to help determine the level of
usability and identify areas of negative impact. Usability problems with CG-LIMS can
have a lasting negative effect on the entire mission support structure of the Coast Guard,
and those problems should be searched for prior to settling on specific solutions.
Heuristic evaluations, user testing, and existing customer interviews can help immensely
in finding problems that could carry very high indirect costs over the lifespan of the
system.

The following desirable attributes have been identified to evaluate system ease of use.
This list is not all inclusive. An easy-to-use system will:

6.1.1 Provide at-a-glance labeling, so that users know what section of the application
they are viewing.
6.1.2 Minimize the number of screens needed to complete a transaction.
6.1.3 Allow the user to recover from an error, such as incorrect data entry, and preserve
correctly entered data in the non-offending fields on the active screen.
6.1.4 Allow sufficient time for an average user to input data.

27

CG-LIMS ORD

Recommended

Recommended

More Related Content

Recently uploaded

Recently uploaded (20)

Featured

Featured (20)

CG-LIMS ORD