cg-lims ord

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

0

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

I

HOlmeland Se¢urityAugust 9,2011

ACQUISITION DECISION MEMORANDUM

:MEMORANDUM FOR:

FROM: Rafael Borras Under Secretary

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 to

I

[email protected]. Should you have any questions, please contact Gjbson Kerr at (202) 343-4534. I

Attachment

mailto:[email protected]

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 ChiefHuman Capital Officer Chief Information Officer ChiefProcurement Officer Chief Security Officer Office ofthe General Counsel, Principal Deputy General Counsel Chiefof 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 Chiefof 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)

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

Approved by:

from: Tjkia.N.RI9ajns@ySCQ dbs goy on behalf of Riggins. Jjkia II

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

Prepared by:

Submitted by:

Endorsed by:

Endorsed by:

Endorsed by:

Endorsed by:

- Endorsed by:

Endorsed by:

Endorsed by:

Endorsed by:

-Endorsed by:

CG Endorsement:

DHS Approval:

Version 1.0

L ~-------------------Assistant Commandant for Resources (CG-8)

See attached Under Secretary for Management

I

zrr/lli1if YJO IDate

il/tflztJ'OI

-Date

I ("j.zt:i/ 1.010

Date

'1!ibO,<> Dlite i

1Ug/;}(lJO Date

!.1f I C J i '.J i 'l;J \ ,-"

DJte /

,}t1/ to

Dat, I

t::IJ/Z"be,. 0 Date

...

CZ8 to~-e 'to, 0 Date

APR 272011 Date

Date

ii

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

1

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

2

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.

3

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

4

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

5

Table 1-1

DY = Deployment Year FY= Fiscal Year

Asset Type Asset

Ext

ract

Dat

a Fr

om

Leg

acy

Dat

abas

es

(AC

MS,

AM

MIS

, C

MPl

us, F

LS,

SA

MS)

RC

M R

equi

red

(AC

&I F

unde

d)

Segm

ent 1

Dep

loym

ent

Segm

ent 2

Dep

loym

ent

Segm

ent 3

Dep

loym

ent

Segm

ent 4

Dep

loym

ent

Segm

ent 5

Dep

loym

ent

Num

ber

of U

nits

Aviation Notes: This includes all air stations and ALC (26). This will include all District and Areas offices that monitor aircraft availability.

HC-144A MRS-MPA (including Mission System Pallet) Yes No DY01 DY02 DY03 DY04 DY05 36*

HC-130J Long Range Surveillance Aircraft Yes No DY01 DY02 DY03 DY04 DY05 6* HC-130H Long Range Surveillance Aircraft (including Seaspray Radar & Casper C4IT Pallet) Yes No DY01 DY02 DY03 DY04 DY05 25

MH-65C Multi-Mission Cutter Helicopter & H-65 Yes No DY01 DY02 DY03 DY04 DY05 101 MH-60T Medium Range Recovery Helicopter & HH-60 Helicopter Yes No DY01 DY03 DY04 DY05 DY06 42

C-143 Command and Control Aircraft Yes No DY01 DY03 DY04 DY05 DY06 1 C-37A Long Range Command and Control Aircraft Yes No DY01 DY03 DY04 DY05 DY06 1 HU-25 "Guardian" Medium Range Surveillance Aircraft Yes No DY01 N/A N/A N/A N/A 18

Sector & DOG Small Boats Standard boats including: 55’AtoN (18) 49’ AtoN (26) 26’ AtoN (58) 25’ TPS (59) 52’ D (457) MLB-HW (4) 47’ MLB (117)

1st District DY01 DY03 DY04 DY05 DY06 Sector Northern New England Yes Limited Sector Boston Yes Limited Sector Southeastern New England Yes Limited Sector Long Island Yes Limited Sector New York Yes Limited 5th District DY01 DY03 DY04 DY05 DY06 Sector Delaware Bay Yes Limited Sector Baltimore Yes Limited Sector Hampton Roads Yes Limited Sector North Carolina Yes Limited 7th District DY02 DY03 DY04 DY05 DY06

6

Asset Type Asset

Ext

ract

Dat

a Fr

om

Leg

acy

Dat

abas

es

(AC

MS,

AM

MIS

, C

MPl

us, F

LS,

SA

MS)

RC

M R

equi

red

(AC

&I F

unde

d)

Segm

ent 1

Dep

loym

ent

Segm

ent 2

Dep

loym

ent

Segm

ent 3

Dep

loym

ent

Segm

ent 4

Dep

loym

ent

Segm

ent 5

Dep

loym

ent

Num

ber

of U

nits

41’ UTB (134) 33’ SPC (44) 24’ SPC (8) 45’ RBM (180) It is assumed that all standard boats will have the RCM analysis completed. Non-standard boats: Non-standard boats will be included in the AC&I funded deployment plans with the Sectors. It is anticipated that an RCM analysis will need to be completed.

Sector Charleston Yes Limited Sector Jacksonville Yes Limited Sector Miami Yes Limited Sector Key West Yes Limited Sector St. Petersburg Yes Limited Sector San Juan Yes Limited 8th District DY02 DY03 DY04 DY05 DY06 Sector Mobile Yes Limited Sector New Orleans Yes Limited Sector Corpus Christi Yes Limited Sector Houston-Galveston Yes Limited Sector Lower Mississippi Yes Limited Sector Ohio Valley Yes Limited Sector Upper Mississippi River Yes Limited 11th District DY02 DY03 DY04 DY05 DY06 Sector San Diego Yes Limited Sector Los Angeles-Long Beach Yes Limited Sector San Francisco Yes Limited 13th District Yes Limited DY02 DY03 DY04 DY05 DY06 Sector Portland Yes Limited Sector Seattle Yes Limited 9th District DY02 DY02 DY05 DY06 DY07 Sector Lake Michigan Yes Limited 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

7

Asset Type Asset

Ext

ract

Dat

a Fr

om

Leg

acy

Dat

abas

es

(AC

MS,

AM

MIS

, C

MPl

us, F

LS,

SA

MS)

RC

M R

equi

red

(AC

&I F

unde

d)

Segm

ent 1

Dep

loym

ent

Segm

ent 2

Dep

loym

ent

Segm

ent 3

Dep

loym

ent

Segm

ent 4

Dep

loym

ent

Segm

ent 5

Dep

loym

ent

Num

ber

of U

nits

Sector Juneau Yes Limited

C4ISR DGPS Yes No DY01 DY03 DY04 DY05 DY06 1 Rescue 21 Sites by Sector which includes remote towers and stations with counsels. No Yes

Same As Hosting District





35*

NAIS No Yes DY03 DY03 DY05 DY06 DY07 VTS No Yes DY03 DY03 DY05 DY06 DY07

Cutters Note: This will include all standard cutter small boats {25’ Cutter Boat (91), 35’ Cutter Boat – Over the Horizon (33)}

87’ CPB

Yes No Same As Hosting District





73

110’ WPB Yes No






378’ WHEC Yes Yes DY03 DY03 DY03 DY07 DY08 270’ WMEC Yes Yes DY03 DY03 DY03 DY07 DY08 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

Yes No Dependant on procure-ment status

Dependant on procure-ment status




25*

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

8

Asset Type Asset

Ext

ract

Dat

a Fr

om

Leg

acy

Dat

abas

es

(AC

MS,

AM

MIS

, C

MPl

us, F

LS,

SA

MS)

RC

M R

equi

red

(AC

&I F

unde

d)

Segm

ent 1

Dep

loym

ent

Segm

ent 2

Dep

loym

ent

Segm

ent 3

Dep

loym

ent

Segm

ent 4

Dep

loym

ent

Segm

ent 5

Dep

loym

ent

Num

ber

of U

nits

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

Hosting District




DY09 11

160’ Inland Construction Tender Yes Yes DY04 DY04 DY04 DY04 DY09 4 100’ Inland Construction Tender Yes Yes DY04 DY04 DY04 DY04 DY09 1 75’ Inland Construction Tender Yes Yes DY04 DY04 DY04 DY04 DY09 8 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 Facilities include ~25,000 real property assets, ~25,000 fixed AtoN and ~25,000 floating AtoN aids.

SILC Assets Note: CG-LIMS will be deployed to SILC assets according t the Sector deployment schedule, with the exception that Segment 1 will be deployed at the same time as Segment 2.

Yes No Same as Hosting District Segment 2

Same as Hosting District Segment 2




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

No No Same As Hosting District





79

NESU No No Same As Hosting

Same As Hosting

Same As Hosting

Same As Hosting

Same As Hosting

9

9

Asset Type Asset

Ext

ract

Dat

a Fr

om

Leg

acy

Dat

abas

es

(AC

MS,

AM

MIS

, C

MPl

us, F

LS,

SA

MS)

RC

M R

equi

red

(AC

&I F

unde

d)

Segm

ent 1

Dep

loym

ent

Segm

ent 2

Dep

loym

ent

Segm

ent 3

Dep

loym

ent

Segm

ent 4

Dep

loym

ent

Segm

ent 5

Dep

loym

ent

Num

ber

of U

nits

District District District District District National Motor Lifeboat School, Cape Disappointment, WA and Yorktown, VA No No DY01 DY03 DY04 DY05 DY06 1

Remaining Units No No DY05 DY05 DY05 DY05 FY22 Assets Specifically Excluded

179’ Cyclone Class Patrol Boat 3 Loran Stations

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

detailed in Appendix B. 3.1.2.5 CG-LIMS shall provide a Configuration Verification and Audit capability as

detailed in Appendix B.

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

detailed in Appendix B. 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

detailed in Appendix B. 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 Availability5 CG-LIMS shall provide an

operational availability of at least 98.6%.

CG-LIMS shall provide an operational availability of at least 99.2%.

5.2 Operational Reliability6 CG-LIMS shall provide an operational reliability of at least 93.1%.

5.3 System Response CG-LIMS shall accommodate a registry of 56,000 named users with up to 35,000 concurrent users with no more than 5 seconds for any page to be displayed and 10 seconds for acknowledgment of any transaction.

CG-LIMS shall accommodate a registry of 56,000 named users with up to 35,000 concurrent users with no more than 3 seconds for any page to be displayed and 5 seconds for acknowledgment of any transaction.

5.4 Interoperability: Financial Compliance

For every transaction meeting the 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 Transaction Visibility7

CG-LIMS shall provide financial managers access to 100% of transaction-level detail for each financial event within 24 hours of posting.

CG-LIMS shall provide financial managers access to 100% of transaction-level detail for each financial event within 1 hour of posting.

5.6 Asynchronous Endurance The system shall implement mechanisms to process CG-LIMS activities at units operating in asynchronous environments for at least 3 months with zero network connectivity.

The system shall implement mechanisms to process CG-LIMS activities at units operating in asynchronous environments for at least 6 months with zero network 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

6.1.5 Allow user customization, such as changing function key assignments, adjusting screen colors, altering page layout, and altering content presentation.

6.1.6 Allow clear marking of mandatory fields required from the user. 6.1.7 Provide event alerts to indicate user errors in data entry or program execution. 6.1.8 Provide alerts that inform the user and system administrator of detected

equipment or software malfunction. 6.1.9 Require user action to acknowledge alerts. 6.1.10 Provide a useful, interactive, screen specific help function for performance

support.

6.2 Ease of Administration

Overall costs associated with support of an IT system can vary widely, depending largely on the administrative burden associated with its upkeep. This is another aspect of usability, but unique in that it has a direct association to support costs of the system, rather than the potential enterprise business impact discussed in Section 6.1. The following desirable attributes have been identified to evaluate system ease of administration. This is not an all inclusive list. A system that is easy to administer will: 6.2.1 Provide system-level password management, simplifying administration of

system-level passwords via adequate documentation of the location, purpose, and impact of the password.

6.2.2 Manage system level accounts from one administrative interface. 6.2.3 Suppress non-mandatory fields without source code changes. 6.2.4 Allow label customization which is inherited throughout the system. 6.2.5 Provide a database which has been normalized to Third Normal Form (3NF) to

reduce redundant storage. 6.2.6 Provide the ability to edit look up tables via an administrative Graphic User

Interface (GUI). 6.2.7 Allow for tuning without jeopardizing vendor product support. 6.2.8 Allow for hierarchical role-based permissions (i.e. higher role inherits

permissions of lower role). 6.2.9 Allow users full use of all their permissions with a single sign on, eliminating a

need to sign in under a different role to access different permissions. 6.2.10 Provide integrated data management utilities to allow simplified data mapping,

conversion, and import capabilities from source systems to CG-LIMS. 6.2.11 Provide multiple logging levels to assist error detection, identification, and

correction. 6.2.12 Provide an online vendor technical support system. 6.2.13 Provide a tiered priority response for technical support based on the environment

and severity of the issue. 6.2.14 Provide system managers the capability to start online diagnostics or to run

background diagnostics when the system is not actively engaged in operational processing.

6.2.15 Provide utility programs to support system administrators in the maintenance of system files and databases.

28

6.2.16 Permit automated software installation and updates across a network.

6.3 Adaptability to a Change Centric Organization

With the roll out of Modernization, CG-LIMS will support many moving parts within the enterprise. Replacing current logistics management systems will require migration strategies and provide unique integration challenges along the way. The details of the ongoing financial transformation are critical for CG-LIMS success, yet those details are not yet solidified. An evaluation of risk regarding proposed solutions with respect to our organizational change should help differentiate options. The following attributes have been identified as aspects to evaluate when considering adaptability to a change centric organization: 6.3.1 Vendor examples of past projects completed where business model change was

central to the IT implementation. 6.3.2 Coast Guard initiated survey of past customers who went through organizational

change to implement an enterprise IT solution.

29

APPENDIX A: LIST OF ACRONYMS

3NF Third Normal Form ACMS Asset Computerized Maintenance System ALMIS Asset Logistics Management Information System AMMIS Asset Maintenance Management Information System APO Asset Project Office BRM Business Reference Model C4IT Command, Control, Communications, Computers and Information

Technology CCB Configuration Control Board CFO Chief Financial Officers (CFO) Act of 1990 CGEA Coast Guard Enterprise Architecture CG-LIMS Coast Guard Logistics Information Management System CGOne Coast Guard One Network CGSD Coast Guard Support Date CM Configuration Management CMP Configuration Management Plan CONOPS Concept of Operations COTS Commercial Off the Shelf DCMS Deputy Commandant for Mission Support DHS Department of Homeland Security DODAF Department of Defense Architecture Framework DOG Deployable Operations Group DY Deployment Year EA Enterprise Architecture EAL Electronic Asset Logbook ECP Engineering Change Proposal ESB Enterprise Service Bus FEA Federal Enterprise Architecture FFMIA Federal Financial Management Improvement Act of 1996 FLS Feet Logistics System FOC Full Operational Capability FSIO Financial Systems Integration Office FY Fiscal Year GUI Graphic User Interface IETM Interactive Electronic Technical Manual IOC Initial Operational Capability ILSP Integrated Logistics Support Plan IPT Integrated Product Team IT Information Technology KPP Key Performance Parameters LORA Level of Repair Analysis LTPIO Logistics Transformation Program Integration Office MCMS Machinery Control and Monitoring Systems MM Maintenance Management MNS Mission Need Statement

30

ORD Operational Requirements Document OT&E Operational Testing and Evaluation OV Operational View (DODAF) PLM Product Line Manager PM Program Manager PS&T Performance Support and Training RCM Reliability Centered Maintenance RFID Radio Frequency Identification SA System Architect® SAMS Shore Asset Management System SV System View (DODAF) SCM Supply Chain Management SOA Service Oriented Architecture SOP Standard Operating Procedures TASC Transformation and Systems Consolidation TEAMS The Enterprise Architecture Management System TEMP Test and Evaluation Master Plan TIM Technical Information Management TRM Technical Reference Model

31

32

APPENDIX B: CG-LIMS REQUIREMENTS

These requirements are to be tested as written, in the applicable context of the supporting referenced standard. There is no intent for the entire standard referenced to be tested beyond the stated requirement.

/CG-LIMS/Level 2 - CG-LIMS Stakeholder Requirements

1. Configuration Management

Version: 0.0Printed by: eldeclerckPrinted on: Monday, August 09, 2010

Generated from DOORS 9.2.0.0

Contents

1 1Configuration Management Planning

2 2Configuration Management Identification

3 7Configuration Control

4 11Configuration Status Accounting

5 18Configuration Verification and Audit

Contents ii

of 18 Printed Monday, August 09, 2010

UID

CM-01

CM-01-01

CM-01-02

CM-01-03

CM-01-04

CM-01-05

CM-01-06

Requirement

1 Configuration Management Planning

The system shall provide a summary of completion of checklist Actions prior to Major System and CI Development Events (MIL HDBK 61A)

The system shall compute ECP Cycle Time. (MIL HDBK 61A)

The system shall compute ECP Approval Rate. (MIL HDBK 61A)

The system shall record the number of deviation requests and percentage recurring. (MIL HDBK 61A)

The system shall record the number of configuration Audits/Open Actions. (MIL HDBK 61A)

The system shall provide the checklists for configuration management actions listed in MIL HDBK 61A, Appendix D. (MIL HDBK 61A)

Segment

1

1

1

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Track CM Metrics" Module Name:CMObject Text:"CM Metrics"





Module Name:CMObject Text:"Track CM Metrics"


UID

CM-02

CM-02-02

CM-02-03

CM-02-05

Requirement

2 Configuration Management Identification

The system shall support multiple identification standards for naming and numbering conventions. (MIL-HDBK-61A)

The system shall provide a function to catalog and cross reference between multiple numbering standards. (MIL-HDBK-61A)

The system shall maintain product baselines. (MIL HDBK 61A, Sec 5.5.1)

Segment

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Product Structure" Module Name:CMObject Text:"Document & Item Identifiers" Module Name:CMObject Text:"S1000D Coding" Module Name:CMObject Text:"Develop Product Structure" Module Name:CMObject Text:"Conduct Post-Audit" Module Name:MMObject Text:"S1000D Coding"

Module Name:CMObject Text:"Product Structure" Module Name:CMObject Text:"Develop Product Structure"

Module Name:CMObject Text:"Establish Baselines and Baseline documentation" Module Name:CMObject Text:"Release Baseline Documentation"


UID

CM-02-07

CM-02-08

CM-02-09

CM-02-10

Requirement

The system shall provide a function to associate a Configuration Item (CI) to it's Unique Identifier (UI). (MIL-HDBK-61A, JFMIP SR-03-02)

The system shall provide a function to create and assign Unique Identifiers (UI). (MIL-HDBK-61A, JFMIP SR-03-02)

The system shall provide a function to link UIs to their associated Asset(s). (MIL-HDBK-61A, JFMIP SR-03-02)

The system shall provide a function to enter CI attribute information stated in Table 5-11, MIL-HDBK 61A. (MIL-HDBK-61A, Table 5-11)

Segment

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Perform Configuration Status Accounting"

Module Name:CMObject Text:"Document & Item Identifiers" Module Name:CMObject Text:"Assign Configuration Identifiers"

Module Name:CMObject Text:"Document & Item Identifiers" Module Name:CMObject Text:"Establish Baselines and Baseline documentation" Module Name:CMObject Text:"Assign Configuration Identifiers"

Module Name:CMObject Text:"Establish Baselines and Baseline documentation" Module Name:CMObject Text:"Assign Configuration Identifiers"

Module Name:CMObject Text:"Technical Data" Module Name:CM


UID

CM-02-11-01

CM-02-11-02

Requirement

The system shall provide the capability to link a CI to an allocated baseline. (MIL-HDBK-61A, Sec 5)

The system shall provide the capability to link a CI to a functional baseline. (MIL-HDBK-61A, Sec 5)

Segment

1

1

OV-5 Links

Object Text:"Determine Configuration Items" Module Name:CMObject Text:"CSA Information"

Module Name:CMObject Text:"Technical Data" Module Name:CMObject Text:"Requirements Documentation" Module Name:CMObject Text:"Determine Configuration Items" Module Name:CMObject Text:"Perform Configuration Status Accounting"

Module Name:CMObject Text:"Technical Data" Module Name:CMObject Text:"Requirements Documentation" Module Name:CMObject Text:"Determine Configuration Items" Module Name:CMObject Text:"Perform Configuration Status Accounting"


UID

CM-02-13

CM-02-14

Requirement

The system shall link Configuration Items to configuration documentation. (MIL-HDBK-61A)

The system shall provide the ability to hierarchically identify a CI down to it's lowest repairable unit. (Table 4-4, MIL-HDBK-61A, Section 5.5)

Segment

1

1

OV-5 Links

Module Name:CMObject Text:"Technical Data" Module Name:CMObject Text:"Hardware Partitioning" Module Name:CMObject Text:"Establish Baselines and Baseline documentation" Module Name:CMObject Text:"Perform Configuration Status Accounting" Module Name:MMObject Text:"OEM Documentation" Module Name:MMObject Text:"Hardware Partitioning"

Module Name:CMObject Text:"Configuration Items" Module Name:CMObject Text:"Product Structure" Module Name:CMObject Text:"Hardware Partitioning" Module Name:CMObject Text:"Determine Configuration Items" Module Name:CMObject Text:"Perform Configuration Status Accounting"


UID Requirement Segment OV-5 Links

Module Name:MMObject Text:"Configuration Items" Module Name:MMObject Text:"Hardware Partitioning" Module Name:MMObject Text:Parts


UID

CM-03

CM-03-03

CM-03-04

CM-03-06

Requirement

3 Configuration Control

The system shall provide a function to identify configuration baseline documentation impacted by an ECP. (MIL-HDBK-61A)

The system shall identify Configuration Items (CI) impacted by ECPs. (MIL-HDBK-61A)

The system shall have the capability to document and record ECP workflow from ECP generation to completion. (MIL-HDBK-61A)

Segment

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Identify Change Requirements" Module Name:CMObject Text:"Change Requirements"


Module Name:CMObject Text:"Implement CM Module Name:CMObject Text:"Change Requests" Module Name:CMObject Text:RFD Module Name:CMObject Text:"Revised Baseline Documentation" Module Name:CMObject Text:"Class I ECP" Module Name:CMObject Text:"Class II ECP" Module Name:CMObject Text:NOR



Module Name:CMObject Text:"Identify Change Requirements" Module Name:CMObject Text:"Classify Change" Module Name:CMObject Text:"Prepare Change Documentation" Module Name:CMObject Text:"Change Classifications" Module Name:CMObject Text:"Perform Initial Review" Module Name:CMObject Text:"Perform CCB Review" Module Name:CMObject Text:"Dispose of Change" Module Name:CMObject Text:"Prepare Implementation Package" Module Name:CMObject Text:"Revise Baseline Documentation" Module Name:MMObject Text:"Change Requests" Module Name:MMObject Text:"Revised Baseline


UID

CM-03-07

CM-03-09

CM-03-10

CM-03-11

Requirement

The system shall support multiple control authorities for ECP workflow. (Chap 6.1.1.3 MIL-HDBK-61A)

The system shall provide a function to associate ECPs to requirements. (MIL-HDBK-61A)

The system shall provide a function to associate ECPs to technical documentation. (MIL-HDBK-61A)

The system shall provide a function for viewing ECPs, sorted by their attributes. (MIL-HDBK-61A)

Segment

1

1

1

1

OV-5 Links

Documentation"

Module Name:CMObject Text:"Configuration Control Authority" Module Name:CMObject Text:"Current Document Change Authority" Module Name:CMObject Text:"CCB Authority" Module Name:CMObject Text:"Establish Baselines and Baseline documentation"



Module Name:CMObject Text:RFD Module Name:CMObject Text:"Class I ECP"



Module Name:CMObject Text:"Class II ECP" Module Name:CMObject Text:NOR


UID

CM-04

CM-04-03

CM-04-05

CM-04-06

Requirement

4 Configuration Status Accounting

The system shall provide a function for comparing product baselines. (MIL-HDBK-61A, Sec 7)

The system shall provide selection criteria to display product baseline data. (MIL-HDBK-61A)

The system shall identify the current approved configuration documentation and identification number associated with each CI. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

Segment

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Perform Configuration Status Accounting"

Module Name:CMObject Text:"Approved Baseline Documentation" Module Name:CMObject Text:"CSA Information" Module Name:CMObject Text:"Perform Configuration Status Accounting" Module Name:MMObject Text:"Approved Baseline Documentation"

Module Name:CMObject Text:"Functional baseline documentation" Module Name:CMObject Text:"Allocated Configuration Baseline" Module Name:CMObject Text:"Product configuration documentation" Module Name:CMObject Text:"Approved Baseline Documentation"


UID

CM-04-07

Requirement

The system shall record and report the status of proposed engineering changes from initiation to final approval/contractual implementation. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

Segment

1

OV-5 Links

Module Name:CMObject Text:"Revised Baseline Documentation" Module Name:CMObject Text:"CSA Information" Module Name:CMObject Text:"Perform Configuration Status Accounting" Module Name:MMObject Text:"Approved Baseline Documentation" Module Name:MMObject Text:"Revised Baseline Documentation"

Module Name:CMObject Text:"Approved Class I ECP" Module Name:CMObject Text:"Confirm Need" Module Name:CMObject Text:"Determine Change Thresholds" Module Name:CMObject Text:"Prepare Request for Engineering Change Proposal" Module Name:CMObject Text:"ECP Need



Module Name:CMObject Text:"Official ECP Request" Module Name:CMObject Text:"Change Requests" Module Name:CMObject Text:RFD Module Name:CMObject Text:"Revised Baseline Documentation" Module Name:CMObject Text:"Class I ECP" Module Name:CMObject Text:"Class II ECP" Module Name:CMObject Text:NOR Module Name:CMObject Text:"Concurrence for Non-Class I ECP" Module Name:CMObject Text:"Non-concurrence for Non-Class I ECP" Module Name:CMObject Text:"Class I ECP Module Name:CMObject Text:"CCB Directive" Module Name:CM



Object Text:"Change Implementation Package" Module Name:CMObject Text:"ECP Implementation Status" Module Name:CMObject Text:"Approved Major RFD" Module Name:CMObject Text:"Class I ECP Endorsement" Module Name:CMObject Text:"Prepare Implementation Package" Module Name:CMObject Text:"Revise Baseline Documentation" Module Name:CMObject Text:"Perform Configuration Status Accounting" Module Name:MMObject Text:"Change Requests" Module Name:MMObject Text:"Revised Baseline Documentation" Module Name:MMObject Text:"Change Implementation Package"


UID

CM-04-08

CM-04-09

Requirement

The system shall record and report the results of configuration audits to include the status and final disposition of identified discrepancies. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

The system shall record and report the status of all critical and major requests for deviations and waivers which effect the configuration of a CI. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

Segment

1

1

OV-5 Links

Module Name:CMObject Text:"Post Audit Report" Module Name:CMObject Text:"Audit Report" Module Name:CMObject Text:"Perform Configuration Status Accounting"

Module Name:CMObject Text:RFD Module Name:CMObject Text:NOR Module Name:CMObject Text:"Approved Major RFD" Module Name:CMObject Text:"Major RFD" Module Name:CMObject Text:"Perform Configuration Status Accounting"


UID

CM-04-10

CM-04-11

CM-04-12

Requirement

The system shall record and report implementation status of authorized changes. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

The system shall provide the traceability of all changes from the original baselined configuration documentation of each CI. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

The system shall report the affectivity and installation status of configuration changes to all CIs at all locations. (MIL-HDBK-61A, Fig 7-2, Table 7-1 on 61A)

Segment

1

1

1

OV-5 Links

Module Name:CMObject Text:"Class I ECP" Module Name:CMObject Text:"Class II ECP" Module Name:CMObject Text:"ECP Implementation Status" Module Name:CMObject Text:"Perform Configuration Status Accounting"

Module Name:CMObject Text:"ECP Implementation Status" Module Name:CMObject Text:"Perform Configuration Status Accounting"

Module Name:CMObject Text:"Implement Change" Module Name:CMObject Text:"ECP Implementation Status" Module Name:CMObject Text:"CSA Information" Module Name:CMObject Text:"Perform Configuration Status Accounting"


UID

CM-04-13

Requirement

The system will capture and manage data, or service oriented interfaces, which supports property management functions such as, but not limited to ownership, utilization, custodial responsibility, etc. (JFMIP SR-00-4)

Segment

1

OV-5 Links

Module Name:CMObject Text:"Available Resources" Module Name:CMObject Text:"CSA Information"


UID

CM-05

CM-05-01

CM-05-02

CM-05-03

Requirement

5 Configuration Verification and Audit

The system shall provide a function to budget for configuration audits. (MIL-HDBK-61A, Chap 8)

The system shall provide a function to schedule configuration audits. (MIL-HDBK-61A, Chap 8)

The system shall produce a validation aid populated with configuration data that satisfies the Configuration Audit Certification checklist stated in Table E-1 of MIL-HDBK-61A. (MIL-HDBK-61A, Table E-1)

Segment

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Plan Audit"

Module Name:CMObject Text:"Plan Audit"

Module Name:CMObject Text:"Verify Configuration" Module Name:CMObject Text:"Conduct Pre-Audit" Module Name:CMObject Text:"Conduct Audit" Module Name:CMObject Text:"Conduct Post-Audit"


2. Maintenance Management



Contents

1 1Maintenance Management

Contents ii


UID

MM-01

MM-01-01

MM-01-02

MM-01-03

Requirement

1 Maintenance Management

The system shall provide the capability to record costs associated with completing maintenance (JFMIP FFMSR-8)

The system shall provide the capability to indicate the completion status of maintenance. (NAVAIR 00-25-403, Chap 5.4.2)

The system shall provide the capability to track cannibalization necessary to complete maintenance tasks while maintaining the integrity of configuration, supply and readiness data. (MIL-P 24534)

Segment

1

1

1

1

OV-5 Links

Module Name:MMObject Text:"Normalized Costs" Module Name:MMObject Text:"Monitor Maintenance"

Module Name:CMObject Text:"ECP Implementation Status" Module Name:MMObject Text:"Maintenance History"

Module Name:MMObject Text:"Configuration Items" Module Name:MMObject Text:"Maintenance History" Module Name:MMObject Text:"Serial Tracked Configuration Items" Module Name:MMObject Text:"Asset Status"


UID

MM-01-04

MM-01-06

MM-01-26

Requirement

The system shall provide the capability to record findings during the completion of a maintenance activity. (NAVAIR 00-25-403, Chap 5.2.7)

The system shall provide the capability to manage maintenance for a class of parts. (NAVAIR 00-25-403, Sec 3)

The system shall provide the capability to manage maintenance for similar parts with different maintenance requirements in different environments.(NAVAIR 00-25-403, Sec 3)

Segment

1

1

1

OV-5 Links

Module Name:MMObject Text:"Maintenance History" Module Name:MMObject Text:"Monitor Maintenance" Module Name:MMObject Text:"Condition Found" Module Name:MMObject Text:"Maintenance Schedule"

Module Name:MMObject Text:"Develop Maintenance Plan" Module Name:MMObject Text:"Perform RCM Analysis" Module Name:MMObject Text:"Schedule Maintenance" Module Name:MMObject Text:"Execute Maintenance" Module Name:MMObject Text:"Monitor Maintenance"

Module Name:MMObject Text:"Develop Maintenance Plan" Module Name:MMObject Text:"Perform RCM Analysis" Module Name:MMObject Text:"Schedule Maintenance"


UID

MM-01-07-01

MM-01-07-02

MM-01-08

MM-01-11

Requirement

The system shall provide the capability to manage maintenance for serialized parts. (MIL-HDBK 61A, Chap 5-31, Table 5-1, item 4D)

The system shall maintain maintenance and transit history for individual serialized parts. (SCM-04-05, MIL-HDBK 61A, JFMIP SR-03-02)

The system shall provide the capability to track tool usage with a check-in and check out process for each maintenance procedure. (COMDTINST 13020.1F)

The system shall provide the capability to access detailed maintenance procedures for all maintenance activities. (MIL-P 24534)

Segment

1

1

1

1

OV-5 Links

Module Name:MMObject Text:"Execute Maintenance" Module Name:MMObject Text:"Monitor Maintenance"

Module Name:MMObject Text:"Serial Tracked Configuration Items"

Module Name:MMObject Text:"Serial Tracked Configuration Items"

Module Name:MMObject Text:"Maintenance Emphasis Program Requirements" Module Name:MMObject Text:"Tool Control"

Module Name:CMObject Text:MPCs Module Name:MMObject Text:"Configuration Items" Module Name:MMObject Text:"Serial Tracked Configuration Items" Module Name:MMObject Text:"Maintenance Requirements" Module Name:MMObject Text:"Asset Status"


UID

MM-01-14

MM-01-16

MM-01-20

Requirement

The system shall provide the capability to defer maintenance (JFMIP SR-00-4)

The system shall provide the capability to record measurements of effectiveness (MOEs) related to the performance of maintenance. (NAVAIR 00-25-403)

The system shall provide the capability to capture structured maintenance and equipment failure data to support Reliability Centered Maintenance (RCM) analysis and maintenance management processes. (CGTO PG-85-00-30, Chap 3; NAVAIR 00-25-403)

Segment

1

1

1

OV-5 Links

Module Name:MMObject Text:"Deferred Maintenance"

Module Name:MMObject Text:"Maintenance Module Name:MMObject Text:"Perform RCM Analysis" Module Name:MMObject Text:"Maintenance History" Module Name:MMObject Text:MOEs

Module Name:MMObject Text:"Perform RCM Analysis" Module Name:MMObject Text:"Trend Analysis" Module Name:MMObject Text:"Maintenance History" Module Name:MMObject Text:"Monitor Maintenance" Module Name:MMObject Text:"Condition Found" Module Name:MMObject Text:"Equipment Monitoring and Status"


UID

MM-01-22

MM-01-23-01

MM-01-23-02

MM-01-24

MM-01-27

MM-01-28

Requirement

The system shall provide the capability to schedule personnel to perform maintenance. (CGTO PG-85-00-110, pg. 3-4 para. a.2.h.)

The system shall provide the capability to track maintenance using configurable time interval (operating/calendar) and condition parameters. (MSG-3, 2-3-8)

The system shall provide the capability to track maintenance using configurable condition parameters. (MSG-3, 2-3-8)

The system shall provide the capability to track items under warranty. (MIL-HDBK 61A, Table 7-1)

The system shall provide the capability to define and execute workflows related to conducting maintenance. (NAVAIR 00-25-403 5.2.7)

The system shall provide the capability to plan maintenance activities. (MIL-P24534, CGTO PG 85-00-110, CGTO PG-85-00-30)

Segment

1

1

1

1

1

1

OV-5 Links

Module Name:CMObject Text:"Implement Change" Module Name:MMObject Text:"Schedule Maintenance"

Module Name:MMObject Text:"Monitor Maintenance"

Module Name:MMObject Text:"Monitor Maintenance"

Module Name:MMObject Text:"Equipment Monitoring and Status"

Module Name:MMObject Text:"Develop Maintenance Plan" Module Name:MMObject Text:"Perform RCM Analysis" Module Name:MMObject Text:"Execute Maintenance"

Module Name:MMObject Text:"Develop Maintenance Plan"


UID

MM-01-29

MM-01-30

MM-01-31

Requirement

The system shall provide the capability to develop a maintenance due list (MDL) for the status of all maintenance due. (MIL-P 24534)

The system shall link maintenance requirements to configuration items. (MIL-P 24536)

The system shall have the capability to capture and display Condition Based Maintenance (CBM) data. The system shall must contain attributes for meter reading in an intuitive and graphically relevant format. (NAVAIR 00-25-403)

Segment

1

1

1

OV-5 Links

Module Name:MMObject Text:"Develop Maintenance Plan" Module Name:MMObject Text:"Maintenance Requirements"

Module Name:MMObject Text:"Develop Maintenance Plan" Module Name:MMObject Text:"Service Level Tasks" Module Name:MMObject Text:"Maintenance Requirements" Module Name:MMObject Text:"Maintenance Requirement Task Definition"

Module Name:MMObject Text:"Develop Emphasis Areas" Module Name:MMObject Text:"Trend Analysis" Module Name:MMObject Text:"Maintenance History" Module Name:MMObject Text:"Serial Tracked Configuration Items" Module Name:MM


UID

MM-01-32

MM-01-33

MM-01-34

Requirement

The system shall provide the capability to capture the direct and indirect costs of work orders. (JFMIP SR-03-02)

The system shall provide the capability to hierarchically assign work orders to parent maintenance activities (in order to support large depot project management). (NAVAIR 00-25-403 3.7.2)

The system shall provide the capability to associate work orders to service contracts. (INT-01-07)

Segment

1

1

1

OV-5 Links

Object Text:"Monitor Maintenance" Module Name:MMObject Text:"Condition Found" Module Name:MMObject Text:"Equipment Monitoring and Status"

Module Name:MMObject Text:"Computed Costs by Activity"

Module Name:MMObject Text:"Schedule Maintenance" Module Name:MMObject Text:"Change Implementation Package" Module Name:MMObject Text:"Maintenance Crew Assignments" Module Name:MMObject Text:"Contract Terms"

Module Name:MMObject Text:"Contract for Maintenance"


3. Supply Chain Management



Contents

2 1Requisition Management

3 2Inventory and Warehouse Management

4 5Transportation, Distribution, and Disposition

Contents ii


UID

SCM-02

SCM-02-01

SCM-02-02

SCM-02-03

SCM-02-04

SCM-02-06

SCM-02-07

SCM-02-08

Requirement

2 Requisition Management

The system shall provide the capability to process Inventory Control Point requisitions from Other Government Agencies following the FEDSTRIP/MILSTRIP process (MILSTRIP/MILSTRAP/MILSBILLS, 41 CFR 26).

The system shall provide the capability to process ICP requisitions using credit card purchases (JFMIP SR-02-02)

The system shall provide the capability to process unit level requisitions from OGA using the MILSTRIP process (MILSTRIP/MILSTRAP/MILSBILLS).

The system shall provide the capability to process unit level requisitions from OGA using credit card purchases. (MILSTRIP/MILSTRAP/MILSBILLS)

The system shall provide the capability to process unit level requisitions following the UMMIPS process (DOD 4000.25-1-M)

The system shall provide the capability to automatically generate a due-in for mandatory turn-in Items (DOD 4000.25M C23)

The system shall provide the capability to process requisitions based on Force Activity Designator Codes, and unique business rules based on priority. (DOD 4000.25-1-M)

Segment

2

2

2

2

2

2

2

2


UID

SCM-03

SCM-03-01

SCM-03-02

SCM-03-04

SCM-03-05

SCM-03-06

SCM-03-07

SCM-03-08

SCM-03-09

SCM-03-10

SCM-03-11

SCM-03-12

SCM-03-13

SCM-03-14

Requirement

3 Inventory and Warehouse Management

The system shall provide the capability to record management information for all inventory classifications (JFMIP SR-03-02).

The system shall provide the capability to update inventory records when material is received and record information necessary to maintain material control. (JFMIP SR-03-02)

The system shall provide the capability to process item inspections, (JFMIP SR-03-02)

The system shall provide the capability to process placement of items into inventory. (JFMIP SR-03-02)

The system shall provide the capability to process release of items out of inventory. (JFMIP SR-03-02, See Disposition)

The system shall provide the capability to process material valuation and financial categorization. (JFMIP SR-03-02)

The system shall provide the capability to process storing and physical verification. (JFMIP SR-03-02)

The system shall provide the capability to process items in storage in multiple storage locations within a storage facility. (JFMIP SR-03-02)

The system shall provide the capability to provide an inventory management function for multiple Inventory Control Points (JFMIP SR-03-02)

The system shall provide the capability to process material in-transit. (JFMIP SR-03-02, See Disposition)

The system shall provide the capability to process material undergoing repair (JFMIP SR-03-02, See Project Based Maintenance Planning).

The system shall provide the capability to track logistics management information in accordance with MIL-PRF-49506. (MIL-PRF-49506)

The system shall provide the capability to use Automated Identification Technology (AIT) (JFMIP SR-03-02)

Segment

2

2

2

2

2

2

2

2

2

2

2

2

2

2


UID

SCM-03-15

SCM-03-16-01

SCM-03-16-02

SCM-03-16-03

SCM-03-17

SCM-03-18

SCM-03-19

SCM-03-20

SCM-03-21

SCM-03-22

SCM-03-23

SCM-03-24

SCM-01-09

SCM-01-11

Requirement

The system shall provide the capability to perform lateral support/parts pooling. (COMDTINST 13020.1F)

The system shall provide the capability to classify material in accordance with the Federal Catalog System (41 CFR 101-30)

The system shall provide the capability to classify material in accordance with the Federal Supply Classification System (41 CFR 101-30)

The system shall provide the capability to classify material in accordance with the Qualified Parts Lists (41 CFR 101-30)

The system shall provide the capability to use product descriptions in accordance with the Federal Standardization Manual (41 CFR 101-29.302)

The system shall provide the capability to record results of inventory audits for units and ICPs. (JFMIP SR-03-02)

The system shall provide the capability to limit use of inventory items to users based on authorization. (JFMIP SR-03-02, MIL-HDBK-61A)

The system shall provide the capability to provide visibility to all inventory items in all storage locations throughout the Coast Guard. (JFMIP SR-03-02)

The system shall provide the capability to add new items to inventory. (JFMIP SR-03-02)

The system shall provide the capability to track to storage space available at all storage facilities throughout the Coast Guard. (JFMIP SR-03-02)

The system shall provide the capability to provide a function for technical feedback from unit to ICP for allowance adjustments. (JFMIP SR-03-02)

The system shall provide the capability to automatically correct for pending stock shortages to provide a pro-active means of ensuring service levels are met. (DOD 4140.1R)

The system shall provide the capability to forecast demand for inventory, supplies and materials. (JFMIP SR-03-02).

The system shall provide the capability to manage shelf-life materials (41 CFR 101-27)

Segment

2

2

2

2

2

2

2

2

2

2

2

2

2

2


UID

SCM-01-12

SCM-01-13

SCM-01-14

Requirement

The system shall provide the capability to identify items of long supply and excess material (41 CFR 101-27).

The system shall provide the capability to process receipt of material procured from any source. (Acquiring Supply Items, JFMIP SR-03-02)

The system shall provide a functiton that will identify and minimize the risk of DMSMS. (DoD 4140.1-R)

Segment

2

2

2


UID

SCM-04

SCM-04-01-01

SCM-04-01-02

SCM-04-01-03

SCM-04-02

SCM-04-04

SCM-04-05-01

SCM-04-05-02

SCM-04-05-03

SCM-04-05-04

SCM-04-06-01

SCM-04-06-02

SCM-04-07

Requirement

4 Transportation, Distribution, and Disposition

The system shall provide the capability to issue items in inventory (JFMIP SR-03-02).

The system shall provide the capability to loan items in inventory (JFMIP SR-03-02).

The system shall provide the capability to dispose of items in inventory (JFMIP SR-03-02).

The system shall provide the capability to process items in transit (JFMIP SR-03-02)

The system shall provide the capability to, prior to the transportation of hazardous materials the CG, certify on the shipping document that the hazardous materials are properly classified, described, packaged, marked, and labeled and are in proper condition for transportation. (41 CFR Part 178)

The system shall provide the capability to track identity information of all issued material. (JFMIP SR-03-02)

The system shall provide the capability to track identity information of all loaned material. (JFMIP SR-03-02)

The system shall provide the capability to track identity information of all sold material. (JFMIP SR-03-02)

The system shall provide the capability to track identity information of all disposed material. (JFMIP SR-03-02)

The system shall provide the capability to process information required for inventory disposal (JFMIP SR-03-02, DHS MD 5100.1)

The system shall provide the capability to process information required to create disposal documentation for material approved for disposal. (JFMIP SR-03-02, DHS MD 5100.1)

The system shall provide the capability to produce a DD1348 for processing transportation of inventory items. (MILSTRIP)

Segment

2

2

2

2

2

2

2

2

2

2

2

2

2


UID

SCM-04-08

SCM-04-09

SCM-04-10

SCM-04-12

SCM-04-14

SCM-04-15

SCM-04-16

SCM-04-17-01

SCM-04-17-02

SCM-04-17-03

Requirement

The system shall provide the capability to produce a DD1149 for processing a transportation request for non-inventory items. (MILSTRIP)

The system shall provide the capability to route transportation requests to the appropriate transportation office based on location. (JFMIP SR-03-02)

The system shall provide the capability to manage the exchange of shipping information between units and transportation offices. (JFMIP SR-03-02)

The system shall provide the capability to process tracking information for all shipments. (JFMIP SR-03-02)

The system shall provide the capability to process receiving information for completed shipments. (JFMIP SR-03-02)

The system shall provide the capability to process transportation discrepancy reports (TDR). (JFMIP SR-03-02)

The system shall provide the capability to provide electronic notification for changes in shipping status to senders and receivers. (JFMIP SR-03-02)

The system shall provide the capability to provide a Customer Information Management function to enable the sale of goods and services to Intra-Coast Guard Customers. (OFFM-NO-0106)

The system shall provide the capability to provide a Customer Information Management function to enable the sale of goods and services to Inter-Governmental costumers. (OFFM-NO-0106)

The system shall provide the capability to provide a Customer Information Management function to enable the sale of goods and services to non-governmental customers. (OFFM-NO-0106)

Segment

2

2

2

2

2

2

2

2

2

2


4. Technical Information Management



Contents

1 1Information Management

2 3Content Development Management

3 4Content Use

Contents ii


UID

TIM-01

TIM-01-01

TIM-01-02

TIM-01-03

TIM-01-04

TIM-01-05

TIM-01-06

TIM-01-07-01

TIM-01-07-02

TIM-01-08

TIM-01-09

TIM-01-10

TIM-01-11

Requirement

1 Information Management

The system shall provide the capability to store Technical Data such as Publications, Engineering Drawings, Diagrams, Illustrations, Maintenance Procedure Cards, UR etc. (MIL-HDBK-61A, S1000D)

The system shall provide the capability to manage metadata associated with Tech data. (MIL-DTL-31000C, MIL-DTL-24784 (series), S1000D, MIL-HDBK-61A)

The system shall provide the capability to identify technical data with a unique identifier (UID). (MIL-HDBK-61A, S1000D)

The system shall have a sorting and indexing function using a standard naming and numbering convention. (MIL-DTL-31000C, MIL-DTL-24784 (series), S1000D)

The system shall provide the capability to support multiple naming and numbering conventions. (S1000D)

The system shall provide the capability to associate TechData to Configuration Items. (MIL-HDBK-61A)

The system shall have a database that is searchable by metadata. (S1000D, MIL-HDBK-

The system shall have a database that is searchable by metadata properties. (S1000D, MIL-HDBK-61A)

The system shall provide the capability to store and mange content at the component level. (S1000D)

The system shall provide the capability to reuse and repurpose content through relational tagging. (S1000D)

The system shall provide the capability to maintain documentation for all components, regardless of the status of disposition. (MIL-HDBK-61A, S1000D)

The system shall provide the capability to relate multiple numbering conventions to the S1000D standard. (S1000D)

Segment

3

3

3

3

3

3

3

3

3

3

3

3

3


UID

TIM-01-12

Requirement

The system shall provide the capability to search tech data by key content (MIL-HDBK-61A, S1000D)

Segment

3


UID

TIM-02

TIM-02-01

TIM-02-02

TIM-02-03

TIM-02-04

TIM-02-05

TIM-02-06

TIM-02-07

TIM-02-08

TIM-02-09

TIM-02-10

TIM-02-11

TIM-02-12

Requirement

2 Content Development Management

The system shall provide the capability to manage content development workflows. (MIL-HDBK-61A, S1000D)

The system shall provide the capability to version all content. (MIL-HDBK-61A)

The system shall provide the capability to track all change history. (MIL-HDBK-61A)

The system shall provide the capability to manage versions and their histories. (MIL-HDBK-61A)

The system shall provide the capability to process updates/change packages (ANSI / ISO 9001 Document and Data Control)

The system shall provide the capability to process role-based check-in/check-out functions for tech data. (MIL-HDBK-61A, S1000D)

The system shall have content lifecycle controls for tech data status management. (MIL-HDBK-61A)

The system shall provide the capability to reuse and repurpose content through relational tagging. (S1000D)

The system shall provide the capability to provide version control for content published to discs, include indexing, and disc labeling capability. (MIL-DTL-31000C, MIL-DTL-24784 (series) )

The system shall provide the capability to sort and index change recommendations based on priority. (MIL-HDBK-61A)

The system shall provide the capability to track and report the current status of pending tech data changes. (MIL-HDBK-61A)

The system shall provide the capability to enroll new tech data in bulk. (MIL-HDBK-61A, S1000D)

Segment

3

3

3

3

3

3

3

3

3

3

3

3

3


UID

TIM-03

TIM-03-02

TIM-03-03

Requirement

3 Content Use

The system shall be able to view multiple files types (such as .xls,.doc, .pdf, Interactive Electronic Technical Manual). (MIL-DTL-31000C, MIL-DTL-24784 (series) )

The system shall have a function for end user tech data library management (audit/ordering pull--not push). (MIL-HDBK-61A, S1000D)

Segment

3

3

3


5. Non-Functional



Contents

1 1Process1.1 1Documentation

1.2 1Implementation

1.3 1Performance

1.4 2Solution Constraint

1.5 2Standard

1.6 2Usability

2 3Service2.1 3Adaptability

2.2 3Interoperability

2.3 3Performance

2.4 4Portability

2.5 4Reliability

2.6 5Scalability

2.7 5Security

2.8 6Usability

Contents ii


UID

NF-01

NF-01-01

NF-01-01-01

NF-01-01-02

NF-01-01-03

NF-01-01-04

NF-01-01-05

NF-01-02

NF-01-02-01

NF-01-02-02

NF-01-03

NF-01-03-01

1 Process

1.1 Documentation

The system shall deliver documentation that identifies all software and hardware products needed by an agency to install, operate, access, and maintain the application. (OFFM NO-0106, TLK-01)

The system shall deliver application design documentation. (OFFM NO-0106, TLK-02)

The system shall deliver product installation and maintenance documentation. (OFFM NO-0106, TLK-03)

The system shall deliver system operations and user manuals.(OFFM NO-0106, TLK-04)

The system shall provide documentation updates concurrent with the distribution of new software releases. Release notes must clearly identify all changes made to the system’s functionality, operation or required computing hardware and software. (OFFM NO-0106, TLK-05)

1.2 Implementation

The system shall provide data archiving and record retention in accordance with the Operations section of the Office of Federal Financial Management document OFFM NO-0106 rules published by the National Archives and Records Administration (NARA), GAO, Information and Life Cycle Management Manual COMDTINST M 5212.12 (series) and National Institute of Standards, Technology (NIST). (OFFM NO-0106, TLI-06/TLI-07)

The system must support Transmission Control Protocol/Internet Protocol (TCP/IP) for application component connectivity. (OFFM NO-0106, TLG-01)

1.3 Performance

The system shall provide the capability to archive and retrieve archived data in accordance with the Operations section TLI of OFFM NO-0106. (OFFM NO-0106, TLI-08)

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

NF-01-03-02

NF-01-04

NF-01-04-01

NF-01-04-02

NF-01-04-03

NF-01-04-04

NF-01-04-05

NF-01-05

NF-01-05-01

NF-01-05-02

NF-01-06

NF-01-06-01

The system shall maintain and report application usage statistics. Productivity statistics shall include concurrent users, job submissions, transactions throughput, and system availability. (OFFM NO-0106, TLI-10)

1.4 Solution Constraint

The system shall provide an integrated workflow management capability in accordance with Section TLE, OFFM NO-0106.

The system shall provide the capability to suspend erroneous Application Programming Interface (API) transactions. (OFFM NO-0106, TLD-04)

The system shall provide API processing controls to ensure real time transactions or batch transactions files are received from authorized sources, complete and not duplicates. (OFFM NO-0106, TLD-05)

The system shall process API transactions using the same business rules, program logic, and edits used by the system in processing transactions submitted through the application client. (OFFM NO-0106, TLD-03)

The system shall generate API transaction edit error records using a data layout defined by the vendor (i.e., provide two-way interface support). (OFFM NO-0106, TLD-06)

1.5 Standard

All XML Schema and instances shall conform to National Information Exchange Model. ("NIEM Conformance" [Online] 23 February 2009.)

The system shall conform to the NIEM IEPD standard for all information exchange packet documentation (IEPD) . ("NIEM Conformance" [Online] 23 February 2009.)

1.6 Usability

The system shall provide the capability to customize system logging features. The intent is to allow the agency or user to specify which parameters (or tables) to log; and to allow the agency or user to turn logging features on or off as needed. (OFFM NO-0106, TLI-13)

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

NF-02

NF-02-01

NF-02-01-01

NF-02-01-02

NF-02-01-03

NF-02-01-04

NF-02-02

NF-02-02-01

NF-02-02-02

NF-02-02-03

NF-02-02-04

NF-02-03

NF-02-03-01

2 Service

2.1 Adaptability

The system shall be customizable to meet agency-defined business practices. Agency customizable features shall be table/parameter driven. (OFFM NO-0106, TLA-02)

The system shall be upgradeable to accommodate changes. Examples of changes include changes in laws, regulations, best practices or new technology. (OFFM NO-0106, TLA-03)

The system shall provide the capability to customize error message text.

The system shall be recoverable in the face of a disaster within 24 hours of the disabling event.

2.2 Interoperability

The system shall provide a capability to import and process standard transactions generated by other systems. (OFFM NO-0106, TLD-01)

The system shall provide data record layouts for all standard transactions that can be accepted by the application’s API facility. Transactions shall have sufficient data to enable complete validation and processing by the receiving system. (OFFM NO-0106, TLD-02)

The system shall provide an integrated Extensible Markup Language (XML) parsing capability. (OFFM NO-0106, TLD-09)

The system shall provide a capability to exchange data using the Extensible Business Reporting Language. (OFFM NO-0106, TLD-10)

2.3 Performance

The system shall provide a process scheduling capability. This capacity allows the agency to define, initiate, monitor and stop system processes (e.g., online availability, batch jobs, and system maintenance). (OFFM NO-0106, TLI-01)

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

NF-02-03-02

NF-02-03-03-01

NF-02-03-03-02

NF-02-03-04-01

NF-02-03-04-02

NF-02-03-05

NF-02-03-06

NF-02-03-07

NF-02-03-08

NF-02-04

NF-02-04-01

NF-02-04-02

NF-02-05

NF-02-05-01

The system shall maintain internal database consistency at all times, including in the event of a system failure. (OFFM NO-0106, TLI-02)

The system shall be capable of supporting 56,000 named users at full operating capability. (OFFM NO-0106, TLL-04)

The system shall be capable of supporting 35,000 concurrent users at full operating capability. (OFFM NO-0106, TLL-04)

The system shall provide a restart capability for all application’s online and batch processing components. (OFFM NO-0106, TLI-04)

Batch jobs shall be segmented to facilitate restart in the event of a system failure. (OFFM NO-0106, TLI-04)

The system shall maintain a minimum system availability of 98.6%.

The system shall utilize technologies that are authorized for use within the USCG Technical Reference Manual (TRM) to the greatest extent practicable

The system shall display any page in no more than 3 seconds (threshold is 5 seconds) at full operating capability.

The system shall acknowledge receipt of any transaction in no more than 5 seconds (threshold is 10 seconds) at full operating capability.

2.4 Portability

The system shall operate on USCG Standard Workstations.

The system shall have the capability to support PDA or other commercially available mobile device use.

2.5 Reliability

System shall provide fault-free performance in the processing of date and date-related data (including, calculating, comparing, and sequencing) by all hardware and software products included as part of the application both individually and in combination (i.e., be Y2K compliant). (OFFM NO-0106, TLA-05)

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

NF-02-05-02

NF-02-06

NF-02-06-01-01

NF-02-06-01-02

NF-02-06-01-03

NF-02-07

NF-02-07-01

NF-02-07-02

NF-02-07-03

NF-02-07-04

NF-02-07-05

NF-02-07-06

The system shall maintain a minimum system reliability of 93.1%.

2.6 Scalability

The system shall be modular. (OFFM NO-0106, TLA-01)

The system shall be highly scalable. (OFFM NO-0106, TLA-01)

The system shall incorporate an open-systems architecture. (OFFM NO-0106, TLA-01)

2.7 Security

The system shall deliver integrated security functionality compliant with the National Institute of Standards and Technology (NIST) Security Standards (OFFM NO-0106, TLH-01)

The system shall be compliant with DHS Sensitive Systems Policy Directive 4300A, Version 6.1.1, October 31, 2008. (DHS Sensitive Systems Policy Directive 4300A, Version 6.1.1)

The system shall ensure that the management, operations and technical baseline security controls are implemented in accordance with Federal Information Processing Standards (FIPS) 199 Standards for Security Categorization of Federal Information and Information Systems and other current NIST guidance on selecting the appropriate security controls. (OFFM NO-0106, TLH-02)

The system shall display a logon banner in accordance with DOD Memo re: Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement, May 9, 2008.

The system shall conform to all appropriate Security and Technical Implementation Guidelines (STIG) specified by Defense Information Systems Agency (DISA)

The system shall provide adequate functionality aboard assets that may not have 100% network connectivity.

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

NF-02-07-07

NF-02-07-08

NF-02-07-09

NF-02-08

NF-02-08-01

NF-02-08-02

NF-02-08-03

NF-02-08-04

NF-02-08-05

NF-02-08-06

The system shall be capable of requiring Common Access Card (CAC) authentication and single signon authentication. (HSPD-12)

The system shall meet the standards and criteria for classification and protection of information in accordance with Executive Order 12958, “Classified National Security Information" (EO 12958)

The system shall provide the capability to control function access (e.g., system modules, transactions, approval authorities) and data access (i.e., create, read, update, delete) by assigned:• User ID• Functional role (e.g., payable technician) or• Organization.Enable the agency to define access rules based on any combination of these attributes. (OFFM NO-0106, TLH-03)

2.8 Usability

The system shall provide an online graphical user interface Graphical User Interface (GUI). The GUI must provide consistent data entry, navigation and information presentation across all modules and sub-systems. (OFFM NO-0106, TLC-01)

The system shall comply with Section 508 of the Rehabilitation Act, as detailed in 36 CFR 1194, Subpart B. (OFFM NO-0106, TLC-02)

The system shall provide a context-sensitive, online help facility. This facility must be customizable by the agency. (OFFM NO-0106, TLC-03)

The system shall generate online status messages to the operator. This includes job or transaction type, name, when processing initiates, when it completes, and any processing errors encountered. (OFFM NO-0106, TLI-03)

The system shall provide common error-handling routines across functional modules. This is intended to generate meaningful and traceable error messages that allow the user or system operator to identify and respond to reported problems. (OFFM NO-0106, TLI-05)

The system shall incorporate user interface features designed to reduce the amount of direct keying required for transaction processing, such as:• Default values based on system maintained transaction and user profiles

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

• Value look-up tables• Highlighting or accentuating required fields• Grayed data fields that are unavailable for user entry• Auto tabs• Automatic data recall• Auto fill text• Cut, copy and paste functionality• Keyboard shortcuts (e.g., function keys to invoke help facility, clear screen, etc.)• Menu mode of screen navigation• Undo/redo• Disabling of non-supported function keys• Ability to select records from a list by scrolling or typing only part of an entry. (OFFM NO-0106, TLC-05)

Segment


6. Interface

Version: 0.0Printed by: eldeclerckPrinted on: Tuesday, August 10, 2010


Contents

1 1External Interfaces

2 4Internal Interfaces

Contents ii

of 4 Printed Tuesday, August 10, 2010

UID

INT-01

INT-01-02

INT-01-04

INT-01-06

INT-01-07-01

INT-01-07-02

INT-01-08

INT-01-09

INT-01-10

INT-01-11

INT-01-12

INT-01-13

INT-01-14

Requirements

1 External Interfaces

CG-LIMS shall be capable of interfacing with a FSIO compliant Core-Accounting System to provide detailed and summary sub-ledger data.

CG-LIMS shall interface with the current Coast Guard Supply Chain Management system, Asset Maintenance Management Information System (AMMIS), until it is fully replaced by CG-LIMS.

CG-LIMS shall be capable of interfacing with the USCG HR system for access to personnel assignments and qualifications.

CG-LIMS shall be capable of interfacing with the USCG Contract Management System to track costs associated with multiple contracting types. (OFFM-0106, SMB)

CG-LIMS shall be capable of interfacing with the USCG Contract Management System to track costs associated with multiple pricing mechanisms. (OFFM-0106, SMB)

CG-LIMS shall interface with the Coast Guard's business reporting tools, Decision Support System (DSS) and Coast Guard Business Intelligence (CGBI).

CG-LIMS shall use the USCG Service Oriented Architecture (SOA) by exposing transaction data to the USCG Enterprise Service Bus. (DHS SOA Technical Framework, Version 1.0, Feb 2007)

CG-LIMS shall provide the capability to interface with Prognostics and Health Management (PHM) systems. (NAVAIR 00-25-403, 3.7.1)

CG-LIMS shall interface with the USCG Electronic Asset Logbook (EAL) to provide asset availability status and access asset usage information.

CG-LIMS shall provide the capability to interface with the Training System to associate engineering changes to training data

CG-LIMS shall interface with a project management system and provide all data necessary for performing Earned Value Management in accordance with ANSI/EIA-748A.

CG-LIMS shall provide the capability to interface with designated DHS property management systems. (JFMIP SR-00-4).

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

INT-01-15

INT-01-16

INT-01-17

INT-01-18

INT-01-19

INT-01-20

INT-01-21

INT-01-22

INT-01-23

INT-01-24

INT-01-25

INT-01-26

INT-01-27

INT-01-28

Requirements

CG-LIMS shall provide the capability to interface with external analytics systems.

CG-LIMS shall provide the capability to interface with external vendors' supply chain management systems.

CG-LIMS shall provide the capability to interface with Defense Logistics Agency's (DLA) Asset Visibility (AV) system.

CG-LIMS shall provide the capability to interface with Navy inventory management systems.

CG-LIMS shall provide the capability to interface with the USCG Messaging System to generate CASREPs.

CG-LIMS shall provide the capability to interface with the USCG Procurement System to process Procurement Requests (PRs). (JFMIP SR 02-02)

CG-LIMS shall provide the capability to interface with the Global Freight System (GFS) to process shipping requests. (DOD 4000.25M)

CG-LIMS shall provide the capability to interface with approved commercial small package carriers. (JFMIP SR-03-02)

CG-LIMS shall provide the capability to interface with the Federal Logistics Information System Web Access (WebFLIS) to process procurements from the federal supply system. (DOD 40000.25-1-M)

CG-LIMS shall provide the capability to interface with Defense Automatic Addressing System Center (DAASC) system to complete logistics transactions (requisition processing).

CG-LIMS shall provide the capability to interface bi-directionally with the Navy's Technical Manual Application System (TMAPS).

CG-LIMS shall provide the capability to interface bi-directionally with the Technical Data Management Information System (TDMIS).

CG-LIMS shall provide the capability to interface bi-directionally with the Configuration Data Managers Database - Open Architecture (CDMD-OA).

CG-LIMS shall provide the capability to interface bi-directionally with the Joint Deficiency Reporting System (JDRS).

Segment

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5

1-5


UID

INT-01-29

INT-01-30

INT-01-31

Requirements

CG-LIMS shall provide the capability to interface bi-directionally with the Electronic Retrograde Management System (ERMS).

CG-LIMS shall provide the capability to interface bi-directionally with eRMs.

CG-LIMS shall provide the capability to interface with Integrated Product Data Environment (IPDE) to automate the migration of an asset's technical data from acquisition to sustainment. (MIL-HDBK-61A)

Segment

1-5

1-5

1-5


UID

INT-02

INT-02-01

INT-02-02

INT-02-03

INT-02-05

INT-02-08

INT-02-10

INT-02-11

INT-02-12

Requirements

2 Internal Interfaces

CG-LIMS shall include an interface between the Configuration Management and the Maintenance modules to initiate or track an engineering change. (MIL-HDBK-61A, Table 4-4)

CG-LIMS shall provide the capability to interface between a FSIO Compliant Commercial Off The Shelf (COTS) Supply System and the Configuration Management module to link parts to Configuration Items. (MIL-HDBK-61A, Table 4-4)

CG-LIMS shall include an interface between the Configuration Management and the Maintenance modules to track maintenance actions on configuration items. (MIL-HDBK-61A)

CG-LIMS shall provide the capability to interface between a FSIO Compliant Commercial Off The Shelf (COTS) Supply System and the Maintenance module to provide visibility to parts in inventory. (CGTO PG 85-00-110, CGTO PG 85-00-30)

CG-LIMS shall provide the capability to interface between the Configuration Management and a S1000D compliant Technical Information Management module to access technical data associated with configuration items and product baselines.(MIL-HDBK-61A, Table 4-1 - Table 4-4)

CG-LIMS shall include an interface between the Technical Information and Supply modules to order paper copies of Technical Information. (CGTO PG-85-00-50, ANSI / ISO 9001 Document and Data Control)

CG-LIMS shall provide the capability to interface between an S1000D compliant Technical Data Management and a FSIO compliant COTS Supply module to link parts information associated with technical data. (MIL-HDBK-61A)

CG-LIMS shall provide the capability to interface between an S1000D compliant Technical Data Management and the Maintenance Management module for access to technical data. (MIL-HDBK-61A, MIL-P 24534, S100D)

Segment

1-5

1

1

1

1

1

3

3

3


7. Reporting



Contents

1 1General

Contents ii


UID

REP-01

REP-01-01

REP-01-02

1 General

The system shall provide an integrated ad hoc query capability in accordance with section TLJ of OFFM NO-0106. (OFFM NO-0106, TLJ-01)

The system must generate output reports, query results and data files in accordance with section TLA of OFFM NO-0106. (OFFM NO-0106, TLA-04)

Segment

1-5

1-5

1-5

APPENDIX C: DODAF CG-LIMS ARCHITECTURE

Note: Throughout the OV-5 Mission Support Process diagrams, an activity colored green indicates that CG-LIMS has requirements to directly support that activity:

Activity supported by CG‐LIMS

Activity not supported by CG‐LIMS.

84

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-2009

Coast Guard Logistics Information Management System

CG-LIMS (OV-1) 01-Sep-2009


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

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

Cost

Availability

OpTempo

CG-LIMS ORD v1.0 page 85

Logistics and Service CentersActivities

"Classify Change""Conduct Audit"

"Conduct Post-Audit""Implement CM Process"

"Conduct Pre-Audit""Confirm Need"

"Contract for Maintenance""Determine Configuration Items"

"Develop Maintenance Plan""Develop Product Structure"

"Dispose of Change""Identify Change Requirements"

"Implement Change""Prepare Implementation Package""Prepare Change Documentation""Implement Process Improvement"

"Initiate Configuration Change""Monitor Maintenance""Perform CCB Review""Perform Initial Review"

"Perform LORA Analysis""Perform RCM Analysis"

"Plan Audit""Prepare Change Proposal"

"Prepare Request for Engineering Change Proposal""Perform CM lifecycle planning"

"Release Baseline Documentation""Review Change Proposal"

"Revise Baseline Documentation""Determine Change Thresholds"

"Perform Configuration Status Accounting""Schedule Maintenance"

"Track CM Metrics"

APOActivities

"Assign Configuration Identifiers""Determine Configuration Items"

"Establish Baselines and Baselinedocumentation"

"Monitor Maintenance""Develop Maintenance Plan""Develop Product Structure"

"Perform RCM Analysis""Prepare Change Documentation"

"Confirm Need""Perform Configuration Status

Accounting""Perform LORA Analysis"

PROActivities

"Develop Product Structure""Perform CM lifecycle planning"

"Develop Maintenance Plan""Implement CM Process""Monitor Maintenance"

"Track CM Metrics""Implement Process Improvement"

"Perform RCM Analysis""Release Baseline Documentation"

"Perform LORA Analysis"

DCMSActivities

"Develop Emphasis Areas""Develop Policy Statement"

"Implement ProcessImprovement"

"Perform Configuration StatusAccounting"

"Perform CM lifecycle planning""Implement CM Process""Monitor Maintenance"

"Track CM Metrics"

Limited/Zero NetworkAvailabilityActivities

"Schedule Maintenance""Execute Maintenance"

External Logistics Systems

Organizational UnitsActivities

"Execute Maintenance""Schedule Maintenance"

"Verify Configuration""Dispose of Change"

"Monitor Maintenance""Perform Configuration

Status Accounting"

OPCOM

FORCECOM

Organic Depot MaintenanceActivities

"Monitor Maintenance""Schedule Maintenance""Execute Maintenance""Perform Configuration

Status Accounting""Verify Configuration"

Outsourced MaintenenceActivities

"Execute Maintenance"

ICP (Internal)

External Source of Supply

Financial Data Center

Assistant Commandant forResources

Production Requirements

Production Status

Production Assessment

Mission Support Requirements

Program Management Requirements


Product Line Management

D-Level Maintenance Management


Maintenance Status

Maintenance Status

Total Asset Visibility


Production Status

Technical Support

Technical Authority Requirements

Logistics Integration Support


Asset Enrollment Info

Logistics Status

Supply Needs

Supply Needs

Supply Status

Supply Status

Sub-Ledger Transaction




Budget Needs / Total Asset Visibility

Budget

Information Sharing

Maintenance Status

Maintenance Status

Logistics Status



CG-LIMS OV-2

CG-LIMS OV-3

Need Line Information Exchange Source Node Source Activity Destination Node Destination ActivityProduction Requirements Maintenance Emphasis Program Requirements DCMS Develop Emphasis Areas PRO Develop Maintenance Plan

Performance Measurements Established DCMS Track CM Metrics PRO Implement Process ImprovementDocumented Lessons Learned DCMS Implement Process Improvement PRO Perform CM lifecycle planningCSA Information DCMS Perform Configuration Status Accounting PRO Track CM MetricsPolicy, Training & Process Guides DCMS Implement CM Process PRO Track CM MetricsConfiguration Management Plan DCMS Perform CM lifecycle planning PRO Implement CM Process

Maintenance Policy DCMS Develop Policy Statement PRODevelop Maintenance PlanPerform LORA Analysis

Production Status Service Level Tasks PRO Perform LORA Analysis APO Develop Maintenance PlanNormalized Costs PRO Perform LORA Analysis APO Develop Maintenance Plan

Approved Baseline Documentation PRO Release Baseline Documentation APO

Perform RCM AnalysisConfirm NeedPerform Configuration Status Accounting

Trend Analysis PRO Perform RCM Analysis APO Develop Maintenance PlanMaintenance Requirement Task Definition PRO Perform RCM Analysis APO Perform LORA AnalysisMaintenance Requirements PRO Develop Maintenance Plan APO Establish Baselines and Baseline documentationProduct Structure PRO Develop Product Structure APO Determine Configuration ItemsHardware Partitioning PRO Perform RCM Analysis APO Develop Product StructureMaintenance Emphasis Program Requirements PRO APO Develop Maintenance Plan

Maintenance Policy PRO APODevelop Maintenance PlanPerform LORA Analysis

Change Requests PROPerform RCM AnalysisMonitor Maintenance APO Confirm Need

Computed Costs by Activity PRO Monitor Maintenance APOPerform LORA AnalysisPerform RCM Analysis

Program Management Requirements Documented CM Process DCMS Perform CM lifecycle planning Logistics and Service Centers

Implement CM ProcessPrepare Implementation PackageRevise Baseline DocumentationConduct Pre-AuditConduct AuditPlan AuditConduct Post-AuditDetermine Change ThresholdsPrepare Request for Engineering Change ProposalConfirm NeedPerform CCB ReviewDispose of ChangePerform Initial ReviewReview Change ProposalImplement ChangePrepare Change ProposalInitiate Configuration ChangePerform Configuration Status AccountingDevelop Product StructureDetermine Configuration ItemsRelease Baseline DocumentationIdentify Change RequirementsPrepare Change Documentation

Documented Lessons Learned DCMS Implement Process Improvement Logistics and Service Centers Perform CM lifecycle planning

Maintenance Policy DCMS Develop Policy Statement Logistics and Service CentersDevelop Maintenance PlanPerform LORA Analysis

Policy, Training & Process Guides DCMS Implement CM Process Logistics and Service Centers Track CM MetricsPerformance Measurements Established DCMS Track CM Metrics Logistics and Service Centers Implement Process ImprovementMaintenance Emphasis Program Requirements DCMS Develop Emphasis Areas Logistics and Service Centers Develop Maintenance PlanConfiguration Management Plan DCMS Perform CM lifecycle planning Logistics and Service Centers Implement CM Process

Product Line Management Approved Class I ECP Logistics and Service CentersReview Change ProposalPerform CCB Review Organizational Units

Perform Configuration Status AccountingDispose of Change

Maintenance Requirements Logistics and Service Centers Develop Maintenance Plan Organizational UnitsExecute MaintenanceSchedule Maintenance

Approved Major RFD Logistics and Service CentersReview Change ProposalPerform CCB Review Organizational Units Dispose of Change

ECP Funding Logistics and Service CentersReview Change ProposalPerform CCB Review Organizational Units

Schedule MaintenanceDispose of Change

Approved Baseline Documentation Logistics and Service Centers Release Baseline Documentation Organizational Units

Verify ConfigurationPerform Configuration Status AccountingDispose of Change

D-Level Maintenance Management Change Implementation Package Logistics and Service CentersPrepare Implementation PackageImplement Change Organic Depot Maintenance Schedule Maintenance

Maintenance Requirements Logistics and Service Centers Develop Maintenance Plan Organic Depot MaintenanceExecute MaintenanceSchedule Maintenance

Approved Class I ECP Logistics and Service CentersReview Change ProposalPerform CCB Review Organic Depot Maintenance Perform Configuration Status Accounting


CG-LIMS OV-3

Need Line Information Exchange Source Node Source Activity Destination Node Destination Activity

Revised Baseline Documentation Logistics and Service CentersRevise Baseline DocumentationImplement Change Organic Depot Maintenance

Schedule MaintenancePerform Configuration Status Accounting

Maintenance Plan Logistics and Service Centers Develop Maintenance Plan Organic Depot MaintenanceMonitor MaintenanceSchedule Maintenance

Change Requests Logistics and Service CentersPerform RCM AnalysisMonitor Maintenance Organic Depot Maintenance

ECP Funding Logistics and Service CentersReview Change ProposalPerform CCB Review Organic Depot Maintenance Schedule Maintenance

D-Level Maintenance Management Maintenance Requirements Logistics and Service Centers Develop Maintenance Plan Outsourced Maintenence Execute MaintenanceApproved Baseline Documentation Logistics and Service Centers Release Baseline Documentation Outsourced Maintenence

Maintenance Status Asset Status Outsourced Maintenence Execute Maintenance Organizational Units Monitor MaintenanceMaintenance Crew Assignments Outsourced Maintenence Organizational Units Execute MaintenanceChange Requests Outsourced Maintenence Execute Maintenance Organizational UnitsMaintenance Schedule Outsourced Maintenence Organizational Units Execute MaintenanceCondition Found Outsourced Maintenence Execute Maintenance Organizational Units Schedule Maintenance

Maintenance Requirements Outsourced Maintenence Organizational UnitsExecute MaintenanceSchedule Maintenance

Maintenance History Outsourced Maintenence Execute Maintenance Organizational Units Monitor MaintenanceDeferred Maintenance Outsourced Maintenence Execute Maintenance Organizational Units

Maintenance Status Maintenance Requirements Organic Depot Maintenance Organizational UnitsExecute MaintenanceSchedule Maintenance

Deferred Maintenance Organic Depot Maintenance Execute Maintenance Organizational UnitsMaintenance History Organic Depot Maintenance Execute Maintenance Organizational Units Monitor MaintenanceCondition Found Organic Depot Maintenance Execute Maintenance Organizational Units Schedule MaintenanceMaintenance Crew Assignments Organic Depot Maintenance Schedule Maintenance Organizational Units Execute Maintenance

Change Requests Organic Depot MaintenanceMonitor MaintenanceExecute Maintenance Organizational Units

Maintenance Schedule Organic Depot Maintenance Schedule Maintenance Organizational Units Execute MaintenanceAsset Status Organic Depot Maintenance Execute Maintenance Organizational Units Monitor Maintenance

Production Status Performance Measurements Established PRO Track CM Metrics DCMS Implement Process ImprovementConfiguration Management Plan PRO Perform CM lifecycle planning DCMS Implement CM ProcessPolicy, Training & Process Guides PRO Implement CM Process DCMS Track CM MetricsDocumented Lessons Learned PRO Implement Process Improvement DCMS Perform CM lifecycle planning

Documented CM Process PRO Perform CM lifecycle planning DCMSImplement CM ProcessPerform Configuration Status Accounting

Technical Support Approved Baseline Documentation APO PRO Perform RCM AnalysisService Level Tasks APO Perform LORA Analysis PRO Develop Maintenance PlanMaintenance Requirements APO Develop Maintenance Plan PROHardware Partitioning APO Perform RCM Analysis PRO Develop Product StructureTrend Analysis APO Perform RCM Analysis PRO Develop Maintenance PlanMaintenance Emphasis Program Requirements APO PRO Develop Maintenance PlanMaintenance Requirement Task Definition APO Perform RCM Analysis PRO Perform LORA AnalysisNormalized Costs APO Perform LORA Analysis PRO Develop Maintenance Plan

Computed Costs by Activity APO Monitor Maintenance PROPerform LORA AnalysisPerform RCM Analysis

Change Requests APOPerform RCM AnalysisMonitor Maintenance PRO

Product Structure APO Develop Product Structure PRO

Technical Authority Requirements Documented CM Process DCMS Perform CM lifecycle planning APO

Confirm NeedPerform Configuration Status AccountingDevelop Product StructureDetermine Configuration ItemsEstablish Baselines and Baseline documentationAssign Configuration IdentifiersPrepare Change Documentation

Maintenance Policy DCMS Develop Policy Statement APODevelop Maintenance PlanPerform LORA Analysis

Maintenance Emphasis Program Requirements DCMS Develop Emphasis Areas APO Develop Maintenance PlanLogistics Integration Support Hardware Partitioning Logistics and Service Centers Perform RCM Analysis APO Develop Product Structure

Configuration Items Logistics and Service CentersRelease Baseline DocumentationDetermine Configuration Items APO

Develop Maintenance PlanPerform LORA AnalysisPerform RCM AnalysisEstablish Baselines and Baseline documentation

Serial Tracked Configuration Items Logistics and Service Centers Perform RCM Analysis APO Perform Configuration Status Accounting

Change Requests Logistics and Service CentersPerform RCM AnalysisMonitor Maintenance APO Confirm Need

Maintenance Requirements Logistics and Service Centers Develop Maintenance Plan APO Establish Baselines and Baseline documentation


CG-LIMS OV-3

Need Line Information Exchange Source Node Source Activity Destination Node Destination Activity

Documented CM Process Logistics and Service Centers Perform CM lifecycle planning APO

Confirm NeedPerform Configuration Status AccountingDevelop Product StructureDetermine Configuration ItemsEstablish Baselines and Baseline documentationAssign Configuration IdentifiersPrepare Change Documentation

Approved Class I ECP Logistics and Service CentersReview Change ProposalPerform CCB Review APO

Perform Configuration Status AccountingDetermine Configuration ItemsEstablish Baselines and Baseline documentationAssign Configuration Identifiers

Maintenance Emphasis Program Requirements Logistics and Service Centers APO Develop Maintenance PlanService Level Tasks Logistics and Service Centers Perform LORA Analysis APO Develop Maintenance Plan

Approved Baseline Documentation Logistics and Service Centers Release Baseline Documentation APO

Perform RCM AnalysisConfirm NeedPerform Configuration Status Accounting

Product Structure Logistics and Service Centers Develop Product Structure APO Determine Configuration ItemsTrend Analysis Logistics and Service Centers Perform RCM Analysis APO Develop Maintenance Plan

Maintenance Policy Logistics and Service Centers APODevelop Maintenance PlanPerform LORA Analysis

Computed Costs by Activity Logistics and Service Centers Monitor Maintenance APOPerform LORA AnalysisPerform RCM Analysis

Maintenance Requirement Task Definition Logistics and Service Centers Perform RCM Analysis APO Perform LORA AnalysisNormalized Costs Logistics and Service Centers Perform LORA Analysis APO Develop Maintenance Plan

Total Asset Visibility Asset Status Logistics and Service Centers DCMS Monitor MaintenanceEquipment Monitoring and Status Logistics and Service Centers DCMS Monitor MaintenanceMOEs Logistics and Service Centers Perform RCM Analysis DCMS Monitor Maintenance

Asset Enrollment Info Maintenance Emphasis Program Requirements APO Logistics and Service Centers Develop Maintenance Plan

Maintenance Policy APO Logistics and Service CentersDevelop Maintenance PlanPerform LORA Analysis

Configuration Items APO Determine Configuration Items Logistics and Service Centers

Develop Maintenance PlanSchedule MaintenancePerform LORA AnalysisPerform RCM Analysis

Product configuration documentation APO Establish Baselines and Baseline documentation Logistics and Service Centers Release Baseline DocumentationProduct Structure APO Develop Product Structure Logistics and Service Centers Determine Configuration Items

Documented CM Process APO Logistics and Service Centers


Maintenance Requirement Task Definition APO Perform RCM Analysis Logistics and Service Centers Perform LORA Analysis

Computed Costs by Activity APO Monitor Maintenance Logistics and Service CentersPerform LORA AnalysisPerform RCM Analysis

Serial Tracked Configuration Items APO Perform RCM Analysis Logistics and Service Centers Perform Configuration Status Accounting

Change Requests APOPerform RCM AnalysisMonitor Maintenance Logistics and Service Centers

Confirm NeedInitiate Configuration Change

Approved Class I ECP APO Logistics and Service Centers

Revise Baseline DocumentationPrepare Implementation PackagePerform Configuration Status AccountingImplement ChangeDispose of ChangeDetermine Configuration ItemsRelease Baseline Documentation


CG-LIMS OV-3

Need Line Information Exchange Source Node Source Activity Destination Node Destination ActivityService Level Tasks APO Perform LORA Analysis Logistics and Service Centers Develop Maintenance PlanAllocated Configuration Baseline APO Establish Baselines and Baseline documentation Logistics and Service Centers Release Baseline DocumentationHardware Partitioning APO Perform RCM Analysis Logistics and Service Centers Develop Product Structure

Maintenance Requirements APO Develop Maintenance Plan Logistics and Service CentersSchedule MaintenanceContract for Maintenance

Trend Analysis APO Perform RCM Analysis Logistics and Service Centers Develop Maintenance PlanFunctional baseline documentation APO Establish Baselines and Baseline documentation Logistics and Service Centers Release Baseline Documentation

Approved Baseline Documentation APO Logistics and Service Centers

Revise Baseline DocumentationIdentify Change RequirementsPerform RCM AnalysisConfirm NeedConduct AuditPlan AuditConduct Pre-AuditPrepare Request for Engineering Change ProposalPerform Configuration Status AccountingImplement ChangePrepare Change ProposalInitiate Configuration ChangePerform CCB ReviewPerform Initial ReviewDispose of ChangeReview Change Proposal

Normalized Costs APO Perform LORA Analysis Logistics and Service Centers Develop Maintenance PlanLogistics Status Verified Configuration Organizational Units Verify Configuration Logistics and Service Centers Conduct Audit

Documented CM Process Organizational Units Logistics and Service Centers


Maintenance History Organizational Units Execute Maintenance Logistics and Service CentersPerform RCM AnalysisMonitor Maintenance

Asset Status Organizational Units Execute Maintenance Logistics and Service Centers Monitor Maintenance

Equipment Monitoring and Status Organizational Units Logistics and Service CentersSchedule MaintenanceMonitor Maintenance

CSA Information Organizational Units Perform Configuration Status Accounting Logistics and Service Centers

Conduct AuditConduct Post-AuditConduct Pre-AuditPlan AuditTrack CM Metrics

MOEs Organizational Units Logistics and Service Centers Monitor Maintenance

D-Level Maintenance Management Maintenance Requirements Organizational Units Organic Depot MaintenanceExecute MaintenanceSchedule Maintenance

Condition Found Organizational Units Execute Maintenance Organic Depot Maintenance Schedule MaintenanceDeferred Maintenance Organizational Units Execute Maintenance Organic Depot MaintenanceMaintenance Crew Assignments Organizational Units Schedule Maintenance Organic Depot Maintenance Execute MaintenanceMaintenance History Organizational Units Execute Maintenance Organic Depot Maintenance Monitor MaintenanceAsset Status Organizational Units Execute Maintenance Organic Depot Maintenance Monitor Maintenance

Change Requests Organizational UnitsMonitor MaintenanceExecute Maintenance Organic Depot Maintenance

Maintenance Schedule Organizational Units Schedule Maintenance Organic Depot Maintenance Execute Maintenance

Maintenance Status Change Requests Organic Depot MaintenanceMonitor MaintenanceExecute Maintenance Logistics and Service Centers

Confirm NeedInitiate Configuration Change


CG-LIMS OV-3

Need Line Information Exchange Source Node Source Activity Destination Node Destination ActivityAsset Status Organic Depot Maintenance Execute Maintenance Logistics and Service Centers Monitor Maintenance

ECP Implementation Status Organic Depot Maintenance Monitor Maintenance Logistics and Service Centers

Revise Baseline DocumentationImplement ChangePerform Configuration Status Accounting

Maintenance History Organic Depot Maintenance Execute Maintenance Logistics and Service CentersPerform RCM AnalysisMonitor Maintenance

Verified Configuration Organic Depot Maintenance Verify Configuration Logistics and Service Centers Conduct AuditMOEs Organic Depot Maintenance Logistics and Service Centers Monitor Maintenance

CSA Information Organic Depot Maintenance Perform Configuration Status Accounting Logistics and Service Centers


Maintenance Status Asset Status Outsourced Maintenence Execute Maintenance Logistics and Service Centers Monitor Maintenance

Maintenance History Outsourced Maintenence Execute Maintenance Logistics and Service CentersPerform RCM AnalysisMonitor Maintenance

Approved Baseline Documentation Outsourced Maintenence Logistics and Service Centers

Revise Baseline DocumentationIdentify Change RequirementsPerform RCM AnalysisConfirm NeedConduct AuditPlan AuditConduct Pre-AuditPrepare Request for Engineering Change ProposalPerform Configuration Status AccountingImplement ChangePrepare Change ProposalInitiate Configuration ChangePerform CCB ReviewPerform Initial ReviewDispose of ChangeReview Change Proposal

Change Requirements Outsourced Maintenence Logistics and Service Centers Prepare Change Documentation

Documented CM Process Outsourced Maintenence Logistics and Service Centers


CSA Information Outsourced Maintenence Logistics and Service Centers


Logistics Status Maintenance History Limited/Zero Network Availability Execute Maintenance Organizational Units Monitor MaintenanceAsset Status Limited/Zero Network Availability Execute Maintenance Organizational Units Monitor Maintenance

Equipment Monitoring and Status Limited/Zero Network Availability Organizational UnitsSchedule MaintenanceMonitor Maintenance

Production AssessmentMission Support RequirementsMission Support RequirementsTotal Asset VisibilityTotal Asset VisibilitySupply Needs


CG-LIMS OV-3

Need Line Information Exchange Source Node Source Activity Destination Node Destination ActivitySupply NeedsSupply StatusSupply StatusSub-Ledger TransactionSub-Ledger TransactionSub-Ledger TransactionBudget Needs / Total Asset VisibilityBudgetInformation SharingMission Support Requirements


Used at: Context:Author:

Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date:

Rev:

READER:

DATE:

Node: Title:Deputy Commandant for Mission Support

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

PUBLICATION

OperationsSystemsCenter

CG-8 FORCECOM

FinanceCenter

C3CENTISCOM

PROAPO

DCMS-5

C4IT SCSFLCSILCALCPSC

CG-9CG-6CG-4CG-1

DHS DoD

DCMS

OPCOM


CG-LIMS OV-4


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node: Title:CG-LIMS

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

PUBLICATION

A.0 Perform TechnicalInformation Management

A.0 Perform Supply ChainManagement

A2.3.3 Monitor Maintenance

A2.3.1 Schedule Maintenance

A1.3.2.3 Prepare ChangeDocumentation

A2.2 Perform MaintenancePlanning

A2.3 Perform Maintenance A2.4 Contract for Maintenance A2.5 Manage Support Functions

A2.3.2 Execute Maintenance

A2.2.1 Perform RCM Analysis

A2.2.2 Perform LORA Analysis

A2.1 Develop MaintenancePolicy

A2.1.1 Develop Policy Statement

A2.1.2 Develop Emphasis Areas

A2.2.3 Develop MaintenancePlan

A.1 Perform ConfigurationManagement

A1.1 Perform ConfigurationManagement & Planning

A1.2 Perform ConfigurationIdentification

A1.3 Perform ConfigurationControl

A1.5 Perform ConfigurationVerification & Audit

A1.5.1 Plan Audit

A1.5.2 Verify Configuration

A1.5.3 Conduct Pre-Audit

A1.5.4 Conduct Audit

A1.5.5 Conduct Post-Audit

A1.3.1 Initiate ConfigurationChange

A1.3.2 Prepare Change Proposal A1.3.3 Review Change Proposal

A1.3.1.1 Confirm Need

A1.3.1.2 Determine ChangeThresholds

A1.3.1.3 Prepare Request forEngineering Change Proposal

A1.3.2.1 Identify ChangeRequirements

A1.3.2.2 Classify Change

A1.3.3.1 Perform Initial Review

A1.3.3.2 Perform CCB Review

A1.3.3.3 Dispose of Change

A1.2.1 Develop ProductStructure

A1.2.2 Determine ConfigurationItems

A1.2.3 Establish Baselines andBaseline documentation

A1.2.4 Assign ConfigurationIdentifiers

A1.2.5 Release BaselineDocumentation

A1.1.1 Perform CM lifecycleplanning

A1.1.2 Implement CM Process

A1.1.3 Track CM Metrics

A1.1.4 Implement ProcessImprovement

A1.4 Perform ConfigurationStatus Accounting

A1.3.4 Implement Change

A1.3.4.1 Revise BaselineDocumentation

A1.3.4.2 PrepareImplementation Package

A.0 Manage Logistics

A.2 Perform MaintenanceManagement


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node:A-0

Title:Manage Logistics Parent

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

NONEA-0PUBLICATION

A.0

Manage Logistics

FSIO Requirements

Equipment Monitoring and Status

Program ManagerMaintenance Officer

COTR

Asset Status

Available Resources

Material AvailabilityTool Control

ECP Funding

Documented CM Process

Policy, Training & Process Guides

System Engineering ProcessCurrent Document Change Authority

Configuration Control Authority

Installation Team

Contract Terms

Maintenance Release Authority

CCB Authority

Change to Mission Requirements


Budget and Resource Availablility

Computed Costs by Activity

Training Status and RequirementsMaintenance Plan

Contract Officer

Maintenance Crew

Product Line Manager

APO

EngineersLogisticians

Stakeholder RequirementsUnit and Depot Maintenance CapabilitiesMission Capabilities and Schedule

QA Feedback

S1000D Coding

Maintenance Strategy

Doctrine

Acquisition StrategyCM CONOP

CM Objectives

Program InitiationCM Metrics

CM ManagerProgram Reviews

Gov't/Contractor IPTCCB Members

Verification and Audit Team

Verified Configuration

Configuration Control AuthorityCurrent Document Change Authority


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/27/2009

Rev:

X READER:

DATE:

Node:A0

Title:Manage Logistics Child

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

TOPA0PUBLICATION

A.1

Perform Configuration Management

A.2

Perform Maintenance Management

Stakeholder Requirements

QA FeedbackMission Capabilities and Schedule

Unit and Depot Maintenance Capabilities


Doctrine

LogisticiansEngineers

APO

Maintenance Crew

Training Status and Requirements

Computed Costs by ActivityMaintenance Plan


CM Objectives

Program InitiationCM Metrics


Gov't/Contractor IPT

CCB MembersVerification and Audit Team


Approved Class I ECP


Provisioning Concept

Maintenance Release Authority

Contract Terms

System Engineering Process

Installation Team


CCB Authority

Asset Status


Current Document Change AuthorityConfiguration Control Authority


ECP Funding

Tool ControlMaterial Availability

Available Resources

COTR

Maintenance OfficerProgram Manager


A.3

Perform Supply ChainManagement

A.4

Perform TechnicalInformation Management

FSIO Requirements

Approved Baseline Documentation

Product Structure

Revised Baseline Documentation

Approved Major RFD

Requirements Documentation

Change Requests


S1000D CodingBudget and Resource Availablility

OEM Documentation

Technical Data

Supply Information

PartsTools

Supply FeedbackParts Orders

Parts Disposition


Change Requests

Hardware PartitioningSerial Tracked Configuration Items

ECP Implementation StatusMaintenance Requirements

Product Line ManagerContract Officer

CSA InformationConcurrence for Non-Class I ECP

Change Implementation PackageConfiguration Items


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node:A-0

Title:Perform Configuration Management Context

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

NONEA-0PUBLICATION

A.0

Perform Configuration Management


CM Objectives

Program InitiationCM MetricsRequirements DocumentationTechnical Data


Gov't/Contractor IPTCCB Members



CSA InformationRevised Baseline Documentation


Current Document Change Authority

Product Structure

Supply Information

S1000D Coding

Change Requests

Change to Mission RequirementsMaintenance RequirementsHardware PartitioningSerial Tracked Configuration ItemsECP Implementation Status

CCB Authority

Requirements DocumentationBudget and Resource Availablility

Concurrence for Non-Class I ECPPolicy, Training & Process Guides


Approved Major RFD

Configuration ItemsChange Implementation Package

Documented CM ProcessInstallation Team


System Engineering ProcessProduct Line Manager

Contract Officer




CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node:A-0

Title:Perform Configuration Management

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

NONEA-0PUBLICATION

A.3

Perform Configuration Control

A.4

Perform Configuration StatusAccounting

A.2

Perform Configuration Identification

A.5

Perform Configuration Verification& Audit

A.1

Perform Configuration Management &Planning

Maintenance Requirements


S1000D Coding


CSA Information


Approved Major RFD


Concurrence for Non-Class I ECP


Post Audit Report

Audit Report


ECP Implementation Status


Supply Information

Hardware Partitioning

Serial Tracked Configuration Items


Configuration Control AuthorityInstallation Team

Product Line ManagerContract Officer

CCB Authority




Change Requests

CM Metrics



Change Implementation Package

Configuration Items

Product Structure

Acquisition Strategy

Program Initiation

CM CONOP

Program Reviews

CM Objectives

CM Manager


CCB Members




Technical Data



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/1/2009

Rev:

X READER:

DATE:

Node:A1.1

Title:Perform Configuration Management & Planning

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A1.1PUBLICATION

A1.1.1

Perform CM lifecycleplanning

A1.1.2

Implement CM Process

A1.1.3

Track CM Metrics

A1.1.4

Implement ProcessImprovement

ConfigurationManagement Plan

CM Objectives

Program Reviews


Acquisition Strategy

CM CONOP

Performance Measurements Established

Program Initiation

Documented Lessons Learned

CM Metrics


CM Manager

CSA Information


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/5/2009

Rev:

X READER:

DATE:

Node:A1.2

Title:Perform Configuration Identification

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A1.2PUBLICATION

A1.2.5

Release Baseline Documentation

A1.2.3

Establish Baselines and Baseline documentation

A1.2.4

Assign Configuration Identifiers

A1.2.2

Determine Configuration Items

A1.2.1

Develop Product Structure




Configuration Items

Requirements DocumentationS1000D Coding

Supply Information


Technical Data



Product Structure


Document & Item Identifiers

Configuration Items



Functional baseline documentation

Allocated Configuration Baseline

Product configuration documentation



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node:A3

Title:Perform Configuration Control

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

A3PUBLICATION

A3.3

Review Change Proposal

A3.4

Implement Change

A3.2

Prepare Change Proposal

A3.1

Initiate ConfigurationChange



Change Thresholds

Class I ECP Disapproval

Non-concurrence for Non-Class I ECP





Change Requests

Technical Data


Current Document Change AuthorityConfiguration Control Authority


S1000D Coding

Official ECP Request

CCB Authority



Installation TeamProduct Line Manager

Gov't/Contractor IPTContract Officer

CCB Members

NOR

RFD

Class II ECP

Class I ECP

ECP Funding

Approved Major RFD

CCB Directive


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/1/2009

Rev:

X READER:

DATE:

Node:A1.3.1

Title:Initiate Configuration Change

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A1.3.1PUBLICATION

A1.3.1.3

Prepare Request forEngineering Change

Proposal

A1.3.1.2

Determine ChangeThresholds

A1.3.1.1

Confirm Need


Need forECP Confirmed

Configuration Control AuthorityDocumented CM Process


Change Thresholds




Change Requests



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/14/2009

Rev:

X READER:

DATE:

Node:A1.3.2

Title:Prepare Change Proposal

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

A1.3.2PUBLICATION

A1.3.2.2

Prepare ChangeDocumentation

A1.3.2.1

Identify ChangeRequirements

Technical Data

Gov't/Contractor IPTDocumented CM Process

RFD

NOR

Class II ECP

Class I ECP

S1000D Coding


Change Thresholds


Non-concurrence for Non-Class I ECPChange Requirements



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/1/2009

Rev:

X READER:

DATE:

Node:A1.3.3

Title:Review Change Proposal

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A1.3.3PUBLICATION

A1.3.3.1

Perform Initial Review

A1.3.3.3

Dispose of Change

A1.3.3.2

Perform CCB Review

Approved Major RFD



ECP Funding

NOR

Documented CM ProcessContract Officer

Major RFD



Class I ECP

CCB Members

CCB Directive

CCB Authority

Non-concurrence for Non-Class I ECP


RFD

Class II ECP

Class I ECP Endorsement


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/1/2009

Rev:

X READER:

DATE:

Node:A1.3.4

Title:Implement Change

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A1.3.4PUBLICATION

A1.3.4.1

Revise BaselineDocumentation

A1.3.4.2

Prepare ImplementationPackage





Gov't/Contractor IPTProduct Line Manager

Installation Team

ECP Funding

Change Implementation PackageConcurrence for Non-Class I ECP

CCB Directive



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/1/2009

Rev:

X READER:

DATE:

Node:A1.5

Title:Configuration Verification & Audit

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A1.5PUBLICATION

A1.5.1

Plan Audit

A1.5.5

Conduct Post-Audit

A1.5.3

Conduct Pre-Audit

A1.5.2

Verify Configuration

A1.5.4

Conduct Audit



Audit Report

Audit PlannedApproved Baseline Documentation

CSA Information


Audit Plan


Post Audit Report


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node:A-0

Title:Maintenance Management Context

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

NONEA-0PUBLICATION

A.0

Perform Maintenance Management

Program ManagerMaintenance Officer

COTR

Maintenance Crew

LogisticiansEngineers

APO

Contract Officer


OEM DocumentationToolsPartsEquipment Monitoring and StatusQA FeedbackStakeholder RequirementsUnit and Depot Maintenance CapabilitiesMission Capabilities and ScheduleRequirements DocumentationChange Implementation PackageConfiguration Items

Available ResourcesMaterial Availability

Tool ControlECP Funding

Contract TermsMaintenance Strategy

Maintenance Release AuthorityDoctrine

S1000D CodingRevised Baseline Documentation


Parts DispositionParts OrdersAsset Status

Change RequestsECP Implementation Status

Hardware PartitioningMaintenance Requirements


Maintenance Plan

Computed Costs by ActivityTraining Status and Requirements

Supply Feedback



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/26/2009

Rev:

X READER:

DATE:

Node:A-0

Title:Maintenance Management

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

NONEA-0PUBLICATION

A.3

Perform Maintenance

A.2

Perform Maintenance Planning

A.5

Manage SupportFunctions

A.4

Contract for Maintenance

A.1

Develop MaintenancePolicy

OEM Documentation

Parts Orders


Maintenance Plan




Asset Status


Mission Capabilities and ScheduleConfiguration Items


Parts DispositionToolsParts


Revised Baseline DocumentationECP Funding

Maintenance Officer

Maintenance Plan

COTR

Contractor Logistics Support

Logisticians

Change Requests

Program Manager

Maintenance Policy

Maintenance EmphasisProgram Requirements


S1000D Coding

Tool Control

Maintenance History





Contract TermsMaintenance Release Authority

Contract OfficerMaintenance Crew


Material Availability

MOEs

Supply Feedback


Available Resources


APO

Engineers

QA Feedback

Doctrine



CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/1/2009

Rev:

X READER:

DATE:

Node:A2.1

Title:Develop Maintenance Policy

Number:

WORKING

DRAFT

RECOMMENDED

jr007

LTPIO(CG_Mission_Support_Target_03272009)

Page:

A2.1PUBLICATION

A2.1.2

Develop Emphasis Areas

A2.1.1

Develop Policy Statement


Maintenance Emphasis Program Requirements

Engineers

Maintenance Policy

Doctrine


Logisticians

Program Manager

Maintenance Objectives


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/13/2009

Rev:

X READER:

DATE:

Node:A2.2

Title:Perform Maintenance Planning

Number:

WORKING

DRAFT

RECOMMENDED

Peter M

Page:

A2.2PUBLICATION

A2.2.1

Perform RCM Analysis

A2.2.2

Perform LORA Analysis

A2.2.3

Develop MaintenancePlan

OEM DocumentationNormalized Costs

MOEs

OEM Documentation

Program Manager

Maintenance Emphasis Program Requirements

Maintenance Plan

Change Requests

Configuration ItemsComputed Costs by Activity

Mission Capabilities and Schedule

APOProduct Line Manager

S1000D Coding

Maintenance Requirement Task Definition

Maintenance Policy

Trend Analysis

Requirements DocumentationMaintenance HistoryQA Feedback





Logisticians

Service Level Tasks



Engineers


CG-LIMS OV-5


Project:

Notes: 1 2 3 4 5 6 7 8 9 10

Date: 10/6/2009

Rev:

X READER:

DATE:

Node:A2.3

Title:Perform Maintenance

Number:

WORKING

DRAFT

RECOMMENDED

jr007

Page:

A2.3PUBLICATION

A2.3.1

Schedule Maintenance

A2.3.2

Execute Maintenance

A2.3.3

Monitor Maintenance

Asset StatusMaintenance History

Change Requests

Supply FeedbackECP Implementation Status


Parts Disposition

ToolsParts

Revised Baseline DocumentationECP Funding

Maintenance Officer

Maintenance Plan



Contractor Logistics Support

Configuration Items


Maintenance Crew


Mission Capabilities and Schedule


Material Availability

Part Orders

MOEs

Maintenance RequirementsTool Control

Condition Found

Deferred Maintenance

Maintenance Schedule

Available Resources

Maintenance Crew Assignments


CG-LIMS OV-5

Operations Systems Center

Other Government Agency

Defense Logistics Agency

Financial Center

Telecommunication and Information Systems Command

USCG Deployable Assets

USCG Personnel Services Center

Commercial Service Provider

Department of Homeland Security


Supports capabilities in the area of:

1. Configuration Management2. Maintenance Management3. Supply Chain Management

4. Technical Information Management System5. Property Management

Supply Vendors

Transportation Vendors

Aviation Logistics Center

Acquisition Directorate

Coast Guard Logistics Information Management System Deployed

Enterprise Project Management System

Sunflower

Coast Guard Business Intelligence

Defense Automatic Addressing System

Abstract of Operations / Training Mgmt Tool

Federal Logistics Information System

Supply Vendor System

Finance Procurement Desktop

Asset Visibility

Core Accounting System

Contract Information Management System

Departmental Accounting and Financial Information System

Electronic Retrograde Management System

Coast Guard Messaging System

World-wide Inventory System

NAVSEA ICP System

Commercial Carrier Systems

Configuration Data Managers Database-Open ArchitecturePrognostics and Health Management Systems

Enhanced Technical Information Management System

Integrated Product Data Environment(s)

Joint Deficiency Reporting System

Learning Management System

Technical Data Management Information System

USCG Direct Access

DirAcs may be hosted bya commercial system node

Technical Manual Application System

Electronic Asset Logbook

3rd Party Supply Chain Management System

3rd Party Analytics System

CG-LIMS Full Operating Capability (SV-01 SystemsInterface)

System ArchitectWed Oct 14, 2009 13:21

CommentVersion 1.3 - Revised to re-size objects and re-size font

for better visibility in preparation for ORD package.

CG-LIMS SV-1 Systems Interface Diagram

System-to-system interfaces should not be assumed to be point to point interfaces.Note: FOC data requirements may be supported by data resident in the USCG Enterprise Data Warehouse or via services through an Enterprise Service Bus.

SV-1


Operations Systems Center

Aviation Logistics Center

USCG Deployable Assets


Asset Computerized Maintenance SystemElectronic Asset Logbook

Asset Maintenance Management Information System Decision Support System

Coast Guard Logistics Information Management System Deployed

CG-LIMS Segment 1 Micro View (SV-01 SystemsInterface)

System ArchitectWed Oct 07, 2009 14:57

CommentVersion 1.3 - Revised based on continued

analysis of Segment One external interfacerequirements.

CG-LIMS

Note: Segment One data requirements may be supported by data resident in the USCG Enterprise Data Warehouse or via services through an Enterprise Service Bus. System-to-system interfaces should not be assumed to be point to point interfaces.

ALC Logistics Systems (Segment One Interfaces)

CG-LIMS (Segment One Interfaces)

SV-1
