U.S. Deparlment of Homeland Security                                                                  Washington, rx:t 205...
cc:Assistant Secretary for PolicyUnder Secretary for Science and Technology Directorate (S&T)Under Secretary for Managemen...
Operational Requirements Document (ORO)                              For                   USCG Logistics Infonnation     ...
Ifrom:            Tjkia.N.RI9ajns@ySCQ dbs goy on behalf of Riggins. Jjkia                            ITo:               C...
OPERATIONAL REQUIREMENTS DOCUMENT                        for the            ICOAST GUARD LOGISTICS INFORMATION MANAGEME/fT...
TABLE OF CONTENTSTitle/paragraph                                                                                          ...
REVISION SUMMARY     Version       Change                       Effective Date     Version 1.0   Initial Draft            ...
EXECUTIVE SUMMARYThis Coast Guard Logistics Information Management System (CG-LIMS) Operational Requirements Document(ORD)...
SECTION 1: INTRODUCTIONCG-LIMS shall be an automated, integrated, mission support information system that links the functi...
financial performance by providing transparent, traceable financial information from our logistics system to ourcore accou...
Table 1-1                                                                       DY = Deployment Year                      ...
Segment 1 Deployment                                                                                                      ...
Segment 1 Deployment                                                                                                      ...
Segment 1 Deployment                                                                                                      ...
Segment 1 Deployment                                                                                                      ...
1.3.1 Initial Operational Capability DateThe targeted Initial Operational Capability (IOC) date for Segment 1 is FY13.IOC ...
1.3.5 Other Key DatesIt is anticipated that all five segments will be completely deployed to all the assets listedin Table...
SECTION 2: MISSION REQUIREMENTSThe Coast Guard defines logistics as all support activities associated with developing,acqu...
2.1 Operating Requirements2.1.1     Operating EnvironmentCG-LIMS shall be accessible via Coast Guard Standard Workstations...
Figure 1. CG-LIMS Functional Breakdown2.2 Concept of OperationsThe CG-LIMS CONOPS explains in more detail how the system w...
2.2.2     Maintenance ManagementField maintenance personnel and product line managers will use CG-LIMS to execute theCoast...
2.2.3     Supply Chain ManagementCG-LIMS will provide the Supply Chain Management (SCM) functionality necessary toeffectiv...
SECTION 3: EFFECTIVENESS REQUIREMENTS3.1 Basic RequirementsAppendix B lists the CG-LIMS requirements being managed in DOOR...
asset that has been enrolled in CG-LIMS by the time Segment 3 is being implementedshall have its technical information enr...
3.1.3   Supply Chain Management3.1.3.1 CG-LIMS shall provide a Requisition Management capability as detailed in        App...
3.2.3     OV-3: Operational Information Exchange Matrix.This matrix shows the relationship between individual information ...
3.4 SensorsCG-LIMS shall be compatible with technologies not yet used extensively in the CoastGuard mission support commun...
SECTION 4: SUITABILITY REQUIREMENTSSection 5 of Appendix B lists the non-functional requirements being managed inTEAMS. Th...
If one product does not meet the needs of the CG-LIMS requirements, a combination ofproducts shall be considered before cu...
lost. Section 2.4.5 of the CONOPS describes how the sustainment community plans todeal with threats and hazards once the s...
potential solutions as to how this support shall be designed, developed, implemented andits effectiveness continuously eva...
SECTION 5: KEY PERFORMANCE PARAMETERS                 KPP                  Threshold                            Objective ...
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
CG-LIMS ORD
Upcoming SlideShare
Loading in …5
×

CG-LIMS ORD

1,939 views

Published on

4/27/2011 signed version of Coast Guard Logistics Information Management System (CG-LIMS) Operational Requirements Document (ORD)

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,939
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
75
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

CG-LIMS ORD

  1. 1. U.S. Deparlment of Homeland Security Washington, rx:t 20528 I HOlmeland August 9,2011 Se¢urity ACQUISITION DECISION MEMORANDUM:MEMORANDUM FOR: Vice Admiral Sally Brice-OHara Vice Commandant United States ~=..,~FROM: Rafael Borras Under Secretary 0SUBJECT: Approval ofthe United States Coast Guards 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 Guards (USCG) Logistics Infonnation Management System(CG LIMS) Operational Requirements Document (ORD) dated June 15,20111. The ORD allowsthe end-user to accurately defme the capabilities required for the acquisition program manager toenable the end-user to execute the assigned missions. iThe CG LIMS program manager has adequately addressed the APMD review! comments. Theprogram 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. TheCG 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 thisADM and the attachment to the affected organizations. The APMD will pro~ide support andassistance. Please send action items, status, and supporting documentation toIAPMD.CAD@hq.dhs.gov. Should you have any questions, please contact Gjbson Kerr at(202) 343-4534. IAttachment
  2. 2. cc:Assistant Secretary for PolicyUnder Secretary for Science and Technology Directorate (S&T)Under Secretary for ManagementDeputy Under Secretary for ManagementChief Administrative OfficerDeputy Chief Financial OfficerChief Human Capital OfficerChief Information OfficerChief Procurement OfficerChief Security OfficerOffice ofthe General Counsel, Principal Deputy General CounselChief of Staff to the Under Secretary for ManagementExecutive Director, Acquisition Program Management DivisionDirector, Contract Operating Division, OCPODirector, Test Evaluation and Standards, S&TDirector, Operational Test and Evaluation, S&TChief of Staff, USCGAssistant Commandant for Acquisition, USCGHead of Contracting Activity, USCGProgram Executive Officer, USCGDirector, USCG Requirements and Analysis, USCG (CG-771) 2
  3. 3. Operational Requirements Document (ORO) For USCG Logistics Infonnation Management System v1.0 (CG LIMS)Approved by: ~~UnQl - ~-JW-l( DateApproved by:
  4. 4. Ifrom: Tjkia.N.RI9ajns@ySCQ dbs goy on behalf of Riggins. Jjkia ITo: CAP. APMP Icc: Pfallt:z Jobn; Bloomfield. patrick M: Lyons James E: Taylor Daniel CAPT: Thomson. u,: Boyd Peter; tlaIler... ~ Sayle. Reojnald ISubject: CG·UMS ORP for PHS Approval IDate: Wednesday, June 15, 2011 8:47:48 AM IAtlaChments: CG·UMS.zlp CG· IMS ORO yl.Q Transmittal Memo lS1ynll pdfGreetings, Attached is the CG-UMS Operational Requirements Document (ORO) v1.0 for D~S approval. Thisis an official submission, no hard copy to follow. Thank you. ITikia Riggins-JonesAdministrative Assistant,Acquisition Support Office, CG·924202.475.3156 (0)202.475.3903 (f)"Ufe isnt about how to survive the storm, but how to dance in the rain."
  5. 5. OPERATIONAL REQUIREMENTS DOCUMENT for the ICOAST GUARD LOGISTICS INFORMATION MANAGEME/fT SYSTEM Version 1.0 I Prepared by: zrr/lli1if YJO IDate Submitted by: il/tflztJO I -Date Endorsed by: I ("j.zt:i/ 1.010 Date Endorsed by: 1!ibO,<> Dlite i Endorsed by: 1Ug/;}(lJO Date !.1f .J iJl;J ,-" CI Endorsed by: i DJte /- Endorsed by: ,}t1/ to Dat, I Endorsed by: t::IJ Date /Z" be,. 0 Endorsed by: ... Endorsed by: L ~------------------- Assistant Commandant for Resources (CG-8)-Endorsed by: CZ8 to~-e to, 0 Date CG Endorsement: APR 272011 Date DHS Approval: See attached Under Secretary for Management Date
  6. 6. TABLE OF CONTENTSTitle/paragraph Page NumberREVISION SUMMARY ................................................................................................................ 1EXECUTIVE SUMMARY ............................................................................................................ 2SECTION 1: INTRODUCTION .................................................................................................... 3 1.1 Purpose .................................................................................................................................. 3 1.2 Background ........................................................................................................................... 3 1.3 Timeframe ............................................................................................................................. 4 1.4 Constraints........................................................................................................................... 11SECTION 2: MISSION REQUIREMENTS ................................................................................ 12 2.1 Operating Requirements...................................................................................................... 13 2.2 Concept of Operations ......................................................................................................... 14SECTION 3: EFFECTIVENESS REQUIREMENTS .................................................................. 17 3.1 Basic Requirements ............................................................................................................. 17 3.2 Interoperability .................................................................................................................... 19 3.3 Communications/Information Technology ......................................................................... 20 3.4 Sensors ................................................................................................................................ 21SECTION 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 ........................................................................................................ 24SECTION 5: KEY PERFORMANCE PARAMETERS .............................................................. 26SECTION 6: TRADE-OFFS ........................................................................................................ 27 6.1 Ease of Use .......................................................................................................................... 27 6.2 Ease of Administration ........................................................................................................ 28 6.3 Adaptability to a Change Centric Organization .................................................................. 29APPENDIX A: LIST OF ACRONYMS ...................................................................................... 30APPENDIX B: CG-LIMS REQUIREMENTS ............................................................................. 32APPENDIX C: DODAF CG-LIMS ARCHITECTURE .............................................................. 84 ii
  7. 7. REVISION SUMMARY Version Change Effective Date Version 1.0 Initial Draft 21-May-2010 Version 1.0 Incorporated CG-8 comments 25-Oct-2010 Version 1.0 Incorporated VCG comments 21-Apr-2011 1
  8. 8. EXECUTIVE SUMMARYThis 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 levelperformance capabilities. It establishes the high level functionality required for CG-LIMS to support theenterprise business model and modernize logistics information systems, enabling common tools to be usedacross the Coast Guard to support a common mission support process.A Requirements Integrated Product Team (IPT) was chartered by the Assistant Commandant for Engineeringand Logistics (CG-4) to define CG-LIMS requirements for a system to fully support the modernization andbusiness process transformation initiatives.This ORD is to be used by the CG-LIMS Project Manager (CG-9334) as the overarching guide that defines thescope 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 CoastGuard’s emerging Service Oriented Architecture (SOA).CG-LIMS will provide the Coast Guard with standardized enterprise management capability for assetconfiguration, maintenance, supply chain, and technical information. It will integrate with the Coast Guard corefinancial system and provide accurate transaction-level data for financial accountability and analysis. Optimalcapability will result through further integration with workforce management systems, eliminating dual entry ofpersonnel, 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 segmentwill provide capability to the field for immediate use.Segment 1 will implement configuration management and maintenance management functionality. BecauseCG-LIMS will replace the Asset Logistics Management Information System (ALMIS) as the preferred tool tomanage transformed assets in accordance with the modernized mission support business model, ALMIS assetswill be targeted first for migration to CG-LIMS. The functional requirements for Segment 1 eclipse thefunctional 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 logisticstransformation schedule.Segment 2 will implement supply chain management functionality, replacing the Asset MaintenanceManagement Information System (AMMIS) subsystem of ALMIS once migration is complete.Segment 3 will implement technical information management functionality, providing a single repository forelectronic 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 enterprisefinancial and workforce management systems and systems outside of the Coast Guard. The financial systemintegration (Segment 4) will be critical to overcoming the enterprise challenge to comply with the ChiefFinancial Officers (CFO) Act of 1990. 2
  9. 9. SECTION 1: INTRODUCTIONCG-LIMS shall be an automated, integrated, mission support information system that links the functions anddata associated with the following functional areas: configuration management, maintenance management,supply chain management, and technical document management. The first segment of CG-LIMS will supportthe configuration management and maintenance management functional requirements defined in this ORD, aswell as the necessary interface, reporting, and non-functional requirements to support those functions. Thesecond segment will add supply chain management capability, and the third segment delivers technicalinformation management. The fourth segment implements full integration with the Coast Guard coreaccounting system. The fifth segment completes the required interfaces, including enterprise workforcemanagement systems and logistics systems external to the Coast Guard.1.1 PurposeThe purpose of CG-LIMS is to support Coast Guard Modernization by providing a tool by which the MissionSupport organization can fully implement their portion of the future enterprise business model through logisticstransformation. The CG-LIMS project will modernize logistics information systems, enabling common tools tobe used across the enterprise to support common logistics process. The information managed by CG-LIMS willprovide 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 andbest practices. By implementing a logistics system capable of supporting improved business process andorganizational structures, the Coast Guard will optimize operational support, reduce costs across theorganization, 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 functionalityfor configuration, maintenance, supply chain, and technical information across all product lines. It is intendedto 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 logisticssupport.The CONOPS gives context for anticipated CG-LIMS use and should be used as a guide to help the systemdeveloper configure the solution to meet the requirements spelled out in this document.1.2 BackgroundThe Coast Guard currently invests in multiple logistics information systems representing many communitiesand business processes. Neither the systems nor the processes are well integrated and do not provide thenecessary 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 maintenancehistory degrades preparedness and has a negative impact on operations. Additionally, many of these systemshave 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 ManagementImprovement Act of 1996 (FFMIA) is closely tied to our inability to correctly capture and track financialinformation in our Core Accounting System that is traceable back to the transaction level of detail in ourlogistics systems. We must enable the Coast Guard’s Chief Financial Officer to disclose organizational 3
  10. 10. financial performance by providing transparent, traceable financial information from our logistics system to ourcore 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 asa model logistics system for the DHS enterprise. We must be able to effectively share information with externalsystems and data bases, including many managed by agencies throughout the Departments of Defense andHomeland Security.Our legacy logistics systems are currently tied to their asset-specific business processes. However, many ofthose 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 orscaled to meet the enterprise requirements. 1 Process transformation to a common business model has preparedthe foundation for a common logistics Information Technology (IT) tool.1.3 TimeframeOne of the principles of this acquisition is to rapidly supply capability to the field through an incrementalacquisition strategy as defined in the DHS Acquisition Directive 102-01. An incremental approach is preferredbecause the requirements are well defined and stable, and the Coast Guard has considerable interest indelivering a usable product as soon as possible. The first segment required for implementation includes theconfiguration management and maintenance management functional requirements (see Sections 2.1.2 and 3 fora full description of the requirements and rationale for how they are broken into segments). A fully capablesystem is required from Segment 1, providing asset configuration, maintenance management and deploymentfunctionality in accordance with the Coast Guard modernized mission support business model. Follow-onsegments will move forward in staggered overlapping efforts, benefiting from the lessons learned and knownconfiguration of Segment 1.Table 1-1 lists the assets targeted for enrollment under this acquisition. The level of effort required to enrollthese 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 performadditional RCM analysis, loading of data from legacy databases, asset operational requirements, geographiclocation, and training requirements. Due to the availability of existing data, anticipated logistics transformationprogress, and several other factors (including the expanded capabilities of CG-LIMS), all assets listed in Table1-1 may not be fully transformed to the new business model and fully enrolled in CG-LIMS under thisacquisition. 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 notedthat not all assets and units in the Coast Guard are listed in Table 1-1. DCMS will enroll individual units andasset types not targeted by this acquisition into CG-LIMS once it is deployed, according to transformationstrategy and schedules outside the scope of the CG-LIMS acquisition. 1 LMTO Report CG406T2, Coast Guard Logistics System of the Future Risk Assessment, dated February 2005 4
  11. 11. Table 1-1 DY = Deployment Year FY= Fiscal Year Segment 1 Deployment Segment 2 Deployment Segment 3 Deployment Segment 4 Deployment Segment 5 Deployment CMPlus, FLS, SAMS) Extract Data From Legacy Databases (ACMS, AMMIS, Number of Units (AC&I Funded) RCM Required Asset Type AssetAviation HC-144A MRS-MPA (including Mission System 36* Yes No DY01 DY02 DY03 DY04 DY05Notes: Pallet) HC-130J Long Range Surveillance Aircraft Yes No DY01 DY02 DY03 DY04 DY05 6*This includes all HC-130H Long Range Surveillance Aircraft (including 25air stations and Yes No DY01 DY02 DY03 DY04 DY05 Seaspray Radar & Casper C4IT Pallet)ALC (26). MH-65C Multi-Mission Cutter Helicopter & H-65 Yes No DY01 DY02 DY03 DY04 DY05 101 MH-60T Medium Range Recovery Helicopter & HH- 42This will include Yes No DY01 DY03 DY04 DY05 DY06 60 Helicopterall District and C-143 Command and Control Aircraft Yes No DY01 DY03 DY04 DY05 DY06 1Areas offices that C-37A Long Range Command and Control Aircraft Yes No DY01 DY03 DY04 DY05 DY06 1monitor aircraft HU-25 "Guardian" Medium Range Surveillance 18availability. Yes No DY01 N/A N/A N/A N/A AircraftSector & DOGSmall Boats 1st District DY01 DY03 DY04 DY05 DY06 Sector Northern New England Yes LimitedStandard boats Sector Boston Yes Limitedincluding: Sector Southeastern New England Yes Limited Sector Long Island Yes Limited55’AtoN (18) Sector New York Yes Limited49’ AtoN (26) 5th District DY01 DY03 DY04 DY05 DY0626’ AtoN (58) Sector Delaware Bay Yes Limited25’ TPS (59) Sector Baltimore Yes Limited52’ D (457) Sector Hampton Roads Yes LimitedMLB-HW (4) Sector North Carolina Yes Limited47’ MLB (117) 7th District DY02 DY03 DY04 DY05 DY06 5
  12. 12. Segment 1 Deployment Segment 2 Deployment Segment 3 Deployment Segment 4 Deployment Segment 5 Deployment CMPlus, FLS, SAMS) Extract Data From Legacy Databases (ACMS, AMMIS, Number of Units (AC&I Funded) RCM Required Asset Type Asset41’ UTB (134) Sector Charleston Yes Limited33’ SPC (44) Sector Jacksonville Yes Limited24’ SPC (8) Sector Miami Yes Limited45’ RBM (180) Sector Key West Yes Limited Sector St. Petersburg Yes LimitedIt is assumed that Sector San Juan Yes Limitedall standard boats 8th District DY02 DY03 DY04 DY05 DY06will have the Sector Mobile Yes LimitedRCM analysis Sector New Orleans Yes Limitedcompleted. Sector Corpus Christi Yes Limited Sector Houston-Galveston Yes LimitedNon-standard Sector Lower Mississippi Yes Limitedboats: Sector Ohio Valley Yes Limited Sector Upper Mississippi River Yes LimitedNon-standardboats will be 11th District DY02 DY03 DY04 DY05 DY06included in the Sector San Diego Yes LimitedAC&I funded Sector Los Angeles-Long Beach Yes Limiteddeployment plans Sector San Francisco Yes Limitedwith the Sectors. 13th District Yes Limited DY02 DY03 DY04 DY05 DY06It is anticipated Sector Portland Yes Limitedthat an RCM Sector Seattle Yes Limitedanalysis will 9th District DY02 DY02 DY05 DY06 DY07need to be Sector Lake Michigan Yes Limitedcompleted. Sector Sault Ste Marie Yes Limited Sector Detroit Yes Limited Sector Buffalo Yes Limited 14th District DY02 DY02 DY05 DY06 DY07 Sector Guam Yes Limited Sector Honolulu Yes Limited 17th District Yes Limited DY02 DY02 DY05 DY06 DY07 Sector Anchorage Yes Limited 6
  13. 13. Segment 1 Deployment Segment 2 Deployment Segment 3 Deployment Segment 4 Deployment Segment 5 Deployment CMPlus, FLS, SAMS) Extract Data From Legacy Databases (ACMS, AMMIS, Number of Units (AC&I Funded) RCM Required Asset Type Asset Sector Juneau Yes LimitedC4ISR DGPS Yes No DY01 DY03 DY04 DY05 DY06 1 Rescue 21 Sites by Sector which includes remote Same As Same As Same As Same As Same As 35* towers and stations with counsels. No Yes Hosting Hosting Hosting Hosting Hosting District District District District District NAIS No Yes DY03 DY03 DY05 DY06 DY07 VTS No Yes DY03 DY03 DY05 DY06 DY07Cutters 87’ CPB Same As Same As Same As Same As Same As 73Note: Yes No Hosting Hosting Hosting Hosting HostingThis will include District District District District Districtall standard 110’ WPB Same As Same As Same As Same As Same Ascutter small boats Yes No Hosting Hosting Hosting Hosting Hosting{25’ Cutter Boat District District District District District(91), 35’ Cutter 378’ WHEC Yes Yes DY03 DY03 DY03 DY07 DY08Boat – Over the 270’ WMEC Yes Yes DY03 DY03 DY03 DY07 DY08Horizon (33)} 210’ WMEC Yes Yes DY03 DY03 DY03 DY07 DY08 418’ Legend Class Maritime Security Cutter - Large Yes No DY04 DY03 DY03 DY07 DY08 8* 154’ Sentinel Class Patrol Boat Yes No DY04 DY04 DY03 DY07 DY08 58* Off Shore Patrol Cutter Dependant Dependant Dependant Dependant Dependant 25* Yes No on procure- on procure- on procure- on procure- on procure- ment status ment status ment status ment status ment status 240’ Great Lakes Icebreaker Yes Yes DY04 DY04 DY04 DY08 DY09 1 420’ Healy Class Icebreaker Yes Yes DY04 DY04 DY04 DY08 DY09 1 225’ Juniper Class Seagoing Buoy Tender Yes No DY04 DY04 DY04 DY08 DY09 16 7
  14. 14. Segment 1 Deployment Segment 2 Deployment Segment 3 Deployment Segment 4 Deployment Segment 5 Deployment CMPlus, FLS, SAMS) Extract Data From Legacy Databases (ACMS, AMMIS, Number of Units (AC&I Funded) RCM Required Asset Type Asset 175’ Keeper Class Coastal Buoy Tender Yes No DY04 DY04 DY04 DY08 DY09 14 140’ Bay Class Icebreaking Tug Yes Yes DY04 DY04 DY04 DY04 DY09 9 65’ Small Harbor Tug No Yes Same As Same As Same As Same As DY09 11 Hosting Hosting Hosting Hosting District District District District 160’ Inland Construction Tender Yes Yes DY04 DY04 DY04 DY04 DY09 4 100’ Inland 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 2Facilities SILC Assets Yes No Same as Same as Same as Same as Same asFacilities include Hosting Hosting Hosting Hosting Hosting~25,000 real Note: CG-LIMS will be deployed to SILC assets District District District District Districtproperty assets, according t the Sector deployment schedule, with the Segment 2 Segment 2 Segment 3 Segment 4 Segment 5~25,000 fixed exception that Segment 1 will be deployed at the sameAtoN and time as Segment 2.~25,000 floatingAtoN aids.Additional UserTraining Operational Centers (Districts, Areas, HQ, etc.) No No DY01 DY02 DY03 DY04 DY05 12 Training Centers No No DY03 DY03 DY05 DY06 DY07 9 Communications Stations No No DY03 DY03 DY05 DY06 DY07 7 Service and Logistics Centers No No DY01 DY02 DY03 DY04 DY05 5 ESU/ESD Same As Same As Same As Same As Same As 79 No No Hosting Hosting Hosting Hosting Hosting District District District District District NESU Same As Same As Same As Same As Same As 9 No No Hosting Hosting Hosting Hosting Hosting 8
  15. 15. Segment 1 Deployment Segment 2 Deployment Segment 3 Deployment Segment 4 Deployment Segment 5 Deployment CMPlus, FLS, SAMS) Extract Data From Legacy Databases (ACMS, AMMIS, Number of Units (AC&I Funded) RCM Required Asset Type Asset District District District District District National Motor Lifeboat School, Cape Disappointment, 1 No No DY01 DY03 DY04 DY05 DY06 WA and Yorktown, VA Remaining Units No No DY05 DY05 DY05 DY05 FY22AssetsSpecifically 179’ Cyclone Class Patrol Boat 3Excluded Loran Stations 9
  16. 16. 1.3.1 Initial Operational Capability DateThe 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 forSegment 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 fullyimplemented in CG-LIMS, ACMS can be retired, and any new assets being enrolled intothe new business model can be enrolled directly into CG-LIMS. Other databases, such asFleet Logistics System (FLS) and the Shore Asset Management System (SAMS), can beretired when all assets contained in those databases are fully migrated to CG-LIMS.1.3.2 Coast Guard Support DateThe anticipated Coast Guard Support Date (CGSD) is FY17. However, elements of bothcontractor and organic support will be required to finish deployment and continue withthe logistics transformation process at varying levels throughout the lifecycle of theincremental acquisition, depending on the final support and implementation strategy.Operations and maintenance funding should start as soon as IOC of Increment 1 isachieved and scaled upward to Full Operational Capability (FOC). For organicdeployment support, the processes and infrastructure set up by the LogisticsTransformation Program Integration Office (LTPIO) should be considered to the greatestextent practical when developing the deployment plan and schedule.To ensure effective support, performance and training systems support shall be developedto 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 DateThe targeted FOC date for CG-LIMS is FY17.FOC for CG-LIMS can be declared when all segments of the CG-LIMS acquisition havebeen delivered and have the capability of being fully deployed in a productionenvironment, 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 toa production environment for the HC-144A MRS-MPA product line. 10
  17. 17. 1.3.5 Other Key DatesIt is anticipated that all five segments will be completely deployed to all the assets listedin Table 1-1 by FY22. At that time it is envisioned the CG-LIMS acquisition project willbe terminated.1.4 ConstraintsThe functional requirements for CG-LIMS are derived from industry standards. Thenon-functional requirements are derived from both industry standards and the currentCoast Guard enterprise architecture. Each requirement cites the standard(s) from which itwas 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 FinancialSystems Integration Office (FSIO); all segments of CG-LIMS shall support the desiredend state where logistics transactions accurately account for financial events and providethat data for the core accounting system and general ledger. The requirements aremaintained 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 isalso maintained in TEAMS, and the CG-LIMS operational and system views of thatarchitecture are found in Appendix C. These views present the required functionalprocess flows and system integration at a very high level, and should not be violatedwithout approval from the DCMS CCB.CG-LIMS shall be comprised of commercially available software (COTS) complyingwith the Open System Interconnection (OSI) Reference Model for open systems, and itshall operate on the Coast Guard One Network (CGOne) from a standard Coast GuardWorkstation employing a Coast Guard approved operating system.The deployment plan will be constrained by the level of transformation already achievedby individual asset types, as described in section 1.3. Assets that have already beentransformed 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 inSection 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 enrollthem into CG-LIMS will require some level of back-fit RCM analysis to re-baseline theassets and transform them prior to CG-LIMS enrollment.CG-LIMS supports both Asset Management and Supply Chain Management, as definedin the Coast Guard Enterprise Architecture (CGEA), and the Federal EnterpriseArchitecture (FEA) Business Reference Model (BRM). Ultimately, CG-LIMS shallinterface with multiple information objects and align with the CGEA InformationInventory, as well as DHS Information Architecture. The Coast Guard IT Products andStandards Inventory, DHS EA Transition Strategy, DHS Technical Reference Model(TRM) and FEA TRM shall be considered when identifying an appropriate technicalsolution that meets the requirements in this document. 11
  18. 18. SECTION 2: MISSION REQUIREMENTSThe Coast Guard defines logistics as all support activities associated with developing,acquiring, testing, and sustaining the mission effectiveness of operating systemsthroughout 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 rightplace, at the right time, in the right quantity, at the right cost.Until recently, the Coast Guard placed insufficient emphasis on integrating logisticsacross asset types throughout their lifecycle. For the most part, logistics wassynonymous with supply. We did not have a vision outlining what an integrated logisticssystem would look like. The various components of capability were managed within“stovepipes” which led to decisions about one component without consideration of itsimpact upon other components. As a result, we are saddled with narrow and inefficientbusiness processes and are unable to optimize the effectiveness of our assets. It is evidentthat we need to integrate our logistics system, or risk a negative impact to unitsperforming the missions of the Coast Guard. 3The Coast Guard’s role in supporting the DHS mission of securing America is groundedin its ability to provide capable, prepared operating forces. The ongoing acquisitionprograms highlight the Coast Guard’s need to support new, complex assets within animproved Coast Guard business process that provides visibility of parts and equipmentthroughout the organization. The Coast Guard’s current logistics support capability,which is tied to stressed, organically-designed IT systems and disparate businessprocesses, is not prepared to adequately handle the new assets, much less provide theneeded visibility and integrate the business process supporting them.Recent efforts to comply with the CFO Act and FFMIA illustrate the need for improvedlogistics within the Coast Guard. To adequately measure financial performance, providetransparency to our financial history and obligations, and execute effective budgeting andfinancial planning, the Coast Guard needs centrally-managed logistics capable of trackingtransactions throughout their lifecycle and properly integrating with the Coast Guard’score accounting system.The mission need can be summed up by stating the current disparate IT logistics systemsin the Coast Guard cannot adequately fill the gap between current practice and what isneeded to support the modernized, standard business model. An unconstrained ITsolution configured to industry standards in support of our modernized business model isnecessary to fill the gap. 2 COMDTINST M4000.2 (series), Coast Guard Logistics Handbook3 COMDTINST 4000.5 (series), Coast Guard Logistics Doctrine 12
  19. 19. 2.1 Operating Requirements2.1.1 Operating EnvironmentCG-LIMS shall be accessible via Coast Guard Standard Workstations in normal staff andfield office settings, on the floor of repair facilities and warehouses, and on operationalassets (including underway assets with periods of limited and no connectivity). Thesystem shall be hosted at a DHS and Coast Guard approved data center.2.1.2 Operational FunctionsCG-LIMS will provide functionality to support asset configuration, maintenance, supplychain, and technical information management, as well as the associated interface andreporting requirements.The requirements for CG-LIMS are being managed within the IBM DOORS® andSystem Architect® (SA) software systems in TEAMS. These documents and datarepresent the functional baseline and changes will be controlled in accordance with theCG-LIMS Configuration Management Plan (CMP) and approved by the CG-LIMSConfiguration Control Board (CCB). Appendix B contains the requirements exportedfrom DOORS, which are organized into functional areas as depicted in Figure 1. Therequirements are linked to enterprise business process models as appropriate, which aredocumented in DODAF architectural views in Appendix C.Sections 3 and 4 will further discuss the requirements and architecture artifacts found inAppendices B and C.2.1.3 Geographic AreaCG-LIMS shall support the enterprise business process through a centrally managedsystem that is accessible anywhere with CGOne connectivity. CG-LIMS shall alsoprovide adequate functionality to users that require system use during periods of limitedand no network connectivity and synchronize with the production database whenconnected.2.1.4 Environmental Performance EnvelopeCG-LIMS is not expected to have any special environmental requirements. It is expectedto operate on any workstation intended to provide CGOne access to CG enterpriseapplications. 13
  20. 20. Figure 1. CG-LIMS Functional Breakdown2.2 Concept of OperationsThe CG-LIMS CONOPS explains in more detail how the system will be used. CG-LIMSwill be the backbone of Coast Guard mission support. It will be the tool by whichmission support personnel retrieve information about the configuration and condition ofassets and record activities supporting those assets. It will be used to support a commonbusiness process across all asset communities. The following summary describes theanticipated operating schemes.2.2.1 Configuration ManagementAsset configuration will be maintained and managed in the system. The product baselinewill be linked to the allocated and functional baselines, so potential changes to theconfiguration can trace back to the requirements they support, and potential changes torequirements can trace to physical configuration items designed to support the originalrequirements. Approved configurations will be viewable to users, and maintainers willbe notified if they try to install a part that is not approved. Configuration auditors willcompare the system data with physical configuration to determine if approvedconfigurations are being maintained. The system will manage the workflow associatedwith proposing, approving, and executing changes to approved configurations.Engineering changes to physical assets or technical documentation can be initiated byvarious methods and users, depending on the source and rationale for the proposedchange. The system will facilitate the review and approval of change requests, allowapproved changes to automatically apply to similar asset types, and generate pendingmaintenance work orders to execute the changes. 14
  21. 21. 2.2.2 Maintenance ManagementField maintenance personnel and product line managers will use CG-LIMS to execute theCoast Guard’s maintenance program. All maintenance will be categorized as eitherorganizational (O-Level) or depot (D-Level) level, according to the bi-level maintenancestrategy supported by DCMS. Individual units will be responsible for using CG-LIMS toidentify and schedule O-Level maintenance required by them. They will be able toschedule the maintenance, requisition parts, view detailed procedures, access technicalmanuals, publications and drawings, and record the details of maintenance execution.Product Line Managers will identify D-Level maintenance and arrange its execution. IfD-Level maintenance is performed by Coast Guard personnel, they will be assignedwithin CG-LIMS and use the system the same way units do for O-Level maintenance. Ifthe work is performed by entities outside of the Coast Guard, the PLM will ensure themaintenance executed is recorded in CG-LIMS.CG-LIMS will accept entry of new discrepancies, which will generate a new work orderto track the problem and corrective maintenance execution. The system will push newwork orders through a progression to determine whether they are O-Level or D-Levelmaintenance actions, generate any required casualty reports, and record maintenanceactions through successful resolution.Maintenance activities executed in CG-LIMS will initiate supply activities withinCG-LIMS. When parts are requisitioned to perform maintenance, supply activities willbe driven based on location, inventory availability, and safety stock levels. The systemwill support the DCMS business model by pushing parts to local units prior to scheduledmaintenance, based on the maintenance requirements managed in CG-LIMS. Dataanalyzed from CG-LIMS will help optimize parts inventories necessary to handleunscheduled, corrective maintenance. Maintenance data will also be used to improvereliability centered maintenance strategies for certain equipment and identify bad parts sothey are not reused on multiple assets.CG-LIMS will be capable of publishing configuration, maintenance, and supply data tothe enterprise SOA via services to the Enterprise Service Bus (ESB). These services willenable any other system to consume the information for purposes of planning, reporting,or mission execution. This ORD is being written with the best current informationregarding the desired enterprise architecture for the operations systems within themodernized Coast Guard. Consequently, as a specific requirement of this acquisition,CG-LIMS will explicitly integrate with the Electronic Asset Logbook (EAL) applicationto show operations personnel the availability of assets according to their maintenancestatus. If an asset has limited capability due to outstanding or ongoing maintenance, EALwill highlight the limitation and display information provided by CG-LIMS describingthe nature of the limitation, timeframe expected until resolution, and any requiredoperational tests to be performed prior to mission operation. While the EAL interfaceshould provide all the necessary information for operators, it will always include a link tooutstanding CG-LIMS activities affecting mission availability so that users have theoption to open maintenance activity details. 15
  22. 22. 2.2.3 Supply Chain ManagementCG-LIMS will provide the Supply Chain Management (SCM) functionality necessary toeffectively manage inventory, requisitioning, procurement requests, and distribution. Itwill support the business model in such a way that planned and actual maintenance willautomatically drive supply activities.Parts will be pushed to field units from inventory control points as they are needed forboth upcoming planned maintenance and unplanned corrective maintenance. CG-LIMSwill monitor stocking levels and automatically notify responsible parties whenprocurements are necessary. Item managers will have full visibility into both local andcentralized inventories to make supply movement decisions. Maintenance technicianswill 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 andsupply activity.The system will generate procurement requests as needed and interface with an enterpriseprocurement management system. All transactions associated with performing supplychain actions will account for financial events by capturing the necessarytransaction-level data and providing it for the enterprise core accounting system.2.2.4 Technical Information ManagementCG-LIMS will be the enterprise repository for technical information associated withassets, such as drawings, technical manuals and publications. It will adhere to theS1000D industry standard and support standard use of Interactive Electronic TechnicalManuals (IETMs). If technical material is maintained, there will be usable hyperlinksfrom within the configuration, maintenance, and supply chain user interfaces so that thematerial is easily accessible, viewable, and printable. Units expected to use CG-LIMS ina disconnected environment shall have technical material stored locally and accessiblethrough the same hyperlinks. CG-LIMS will manage changes to technical documentationthe same way it manages engineering changes described in the configurationmanagement requirements, including the management of workflow and tracking andexecuting the changes. 16
  23. 23. SECTION 3: EFFECTIVENESS REQUIREMENTS3.1 Basic RequirementsAppendix B lists the CG-LIMS requirements being managed in DOORS. They areorganized according to the functional breakdown shown in Figure 1. It is intended thatthe stated requirement be tested in the applicable context of the supporting referencedstandard, not that the entire referenced standard be tested. To achieve faster fieldedcapability with less risk, CG-LIMS shall be acquired in discrete segments according to anincremental acquisition strategy. The legacy logistics system currently being used as the Coast Guard’s best-in-breedlogistics system to support Modernization and enterprise Logistics Transformation isALMIS. DCMS is currently enrolling legacy assets into ALMIS after they have beentransformed to the new business model, but the mission need ultimately recognizesALMIS cannot scale to meet the IT need for Modernization. CG-LIMS shall initiallytarget ALMIS for replacement so that modernized IT can be available as soon as possibleto support Logistics Transformation. Once CG-LIMS delivers functional capabilityadequate to migrate transformed assets from other legacy systems, those assets shall betargeted for enrollment and the legacy system targeted for disposal. Assets not yettransformed shall undergo back-fit RCM prior to enrollment into CG-LIMS.Since maintenance drives supply in the Coast Guard business model, and assetconfiguration is critical to managing maintenance, Segment 1 shall start with theconfiguration management requirements.ACMS is a module in ALMIS that integrates a level of configuration and maintenancefunctionality in such a way that it would be extremely difficult and costly to replace onefunctional part without the other while maintaining satisfactory support for assets.Consequently, CG-LIMS Segment 1 is targeting the whole of ACMS for replacement andincludes the maintenance management requirements. Until the Coast Guard implements aFSIO compliant core accounting system, CG-LIMS will interface with the existingaccounting system to post accounting transactions. CG-LIMS will integrate with theFSIO compliant core accounting system if the system is available in this segment.Current AMMIS architecture provides opportunity to target supply chain managementfunctionality in a discrete segment. Segment 2 shall incorporate the SCM requirementsand integrate with Segment 1 according to the Internal Interface requirements and theOV-5 process models in Appendix C. Until the Coast Guard implements a FSIOcompliant core accounting system, CG-LIMS will interface with the existing accountingsystem to post accounting transactions. CG-LIMS will integrate with the FSIO compliantcore 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 activitiesshall be seamlessly managed in the system so that hyperlinks from configuration,maintenance, or supply activities provide access to the latest approved versions. Any 17
  24. 24. asset that has been enrolled in CG-LIMS by the time Segment 3 is being implementedshall have its technical information enrolled in CG-LIMS.Segment 4 shall include the integration between CG-LIMS and the expected FSIOcompliant integrated accounting system. The integration of CG-LIMS and the expectedFSIO compliant integrated accounting system will be included in Segments 1 and/orSegment 2, if the FSIO compliant integrated accounting system is available in Segment 1and/or Segment 2. Segment 4 shall be deferred until the Coast Guard has completedenough of the financial transformation effort to warrant integration to the FSIO compliantintegrated accounting system.The remaining system interfaces with Coast Guard and external systems will beconfigured in Segment 5.The interface requirements for CG-LIMS, while not implemented in many cases untilSegments 4 and 5, are still valid for earlier segments. While an interface may not beconfigured and implemented until Segment 4, the function within CG-LIMS that will bemaking the interface requires the capability from the start. Likewise, the reportingrequirements are valid for every segment.The following breakdown outlines the requirements detailed in Appendix B:3.1.1 Configuration ManagementThe National Consensus Standard for Configuration Management (ANSI/EIA-649) is theindustry standard to which the configuration management requirements are based. Thereference cited in the requirements, MIL-HDBK-61A, is accepted guidance to complywith 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 Management3.1.2.1 CG-LIMS shall provide a Maintenance Management capability as detailed in Appendix B. 18
  25. 25. 3.1.3 Supply Chain Management3.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 Management3.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 Interface3.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 Reporting3.1.6.1 CG-LIMS shall provide Reporting capability as detailed in Appendix B.3.2 InteroperabilityAppendix C illustrates DODAF artifacts exported from SA that represent the CoastGuard enterprise business model that CG-LIMS shall support. The Operational View(OV) and System View (SV) diagrams in the DODAF architecture are activelymaintained under configuration control in TEAMS as part of the Coast Guard EnterpriseArchitecture. The included views provide the following information to help frame thecontext 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’smodernized business model and shows its relationship with stakeholders, including theCFO.3.2.2 OV-2: Operational Node Connectivity Description.This view shows the relationship between operational nodes (or physical units usingCG-LIMS). Because this represents the new business model, a single abstract node isused to represent many distinct units that will follow the same business process, such asOrganizational Units, Logistics and Service Centers, and Inventory Control Points. The“need lines” connecting operational nodes show where two nodes share information. Theactivities listed in a node indicate a mission support activity directly supported by CG-LIMS. 19
  26. 26. 3.2.3 OV-3: Operational Information Exchange Matrix.This matrix shows the relationship between individual information exchanges (definedbetween activities in the OV-5) and operational nodes. In effect, it drills into the needlines depicted in the OV-2 and more clearly describes which information CG-LIMS willpass 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 usercommunities, 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 achievingmission support under the modernized business model. Thus far, the OV-5 detail islimited to the activities supporting CG-LIMS Segment 1 requirements. Throughout theOV-5 diagrams in Appendix C, an activity colored green indicates that CG-LIMS hasrequirements to support that activity. The first OV-5 diagram shows a hierarchy chart forthe activities under “Manage Logistics.” The remaining OV-5 diagrams use the IDEF0(Integration Definition for Function Modeling) modeling methodology to flow throughthe 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. Theconnections between activities are defined as information exchanges, which can be seenin the OV-3.3.2.6 SV-1: Systems Interface Description.This view includes two diagrams. The first illustrates the system interfaces expected ofCG-LIMS at FOC. The second shows the expected interfaces for initial deployment ofSegment 1. Since Modernization is currently using ALMIS to support the transformationof assets to the new business model, it will be the first IT system targeted for replacementby CG-LIMS. However, until ACMS and AMMIS are retired, a level of interfacebetween those applications and CG-LIMS will be required to ensure continuity ofservices across the ALMIS suite. Once the system architecture is in place for Segment 1and more information is known about the CG-LIMS solution, the system views forSegments 2 through 5 can be defined.3.3 Communications/Information TechnologyOne of the key mission needs CG-LIMS will help rectify is financial accountability andCFO compliance. To accomplish this, integration with financial, procurement, humanresource, and non-consolidated logistics systems in accordance with section 3.1.5 will becrucial.The Coast Guard shall use Service Oriented Architecture (SOA) to share informationbetween IT systems, in accordance with requirement INT-01-09 in Appendix B. 20
  27. 27. 3.4 SensorsCG-LIMS shall be compatible with technologies not yet used extensively in the CoastGuard mission support community.3.4.1 Sensor Interface Requirements3.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
  28. 28. SECTION 4: SUITABILITY REQUIREMENTSSection 5 of Appendix B lists the non-functional requirements being managed inTEAMS. They are separated into process requirements and service requirements:4.0.1 Non-Functional4.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 thoserequirements and serve as a starting point for an Integrated Logistics Support Plan(ILSP).4.1 DesignBecause the Coast Guard is adopting a standardized logistics business model across theenterprise, the preferred IT solution to support IT modernization and consolidation ofbusiness functions is a COTS product. Since the core business process across theenterprise is neither unique to the Coast Guard, military, or government, nor differentthan industry standards and best practices, the Coast Guard will leverage proventechnology to support IT modernization. 4Further rationalization for targeting COTS tools centers on the current state of market andevolution of known products that support our core requirements. Market researchconducted after the release of the Preliminary ORD proved that market leading COTSproducts could effectively support our requirements with minimal or no customization.COTS products in this market segment offer additional advantages to consumers becausethe incentives and market pressures compel economically rational decisions, resulting inconstant innovation, little waste, and a rising standard of development. COTS productssupporting enterprise asset management functions are more cost effective, adaptable, andfunctional in both the long-term and short-term. Licensing fees are potentially muchlower than up-front development and lifetime maintenance costs associated with customdevelopment. The schedule for development and implementation of a COTS system istypically much shorter, helping to reduce overall enterprise cost. Market demands forceproven COTS products to improve with technology and pass those advantages to current,as well as prospective users. Proven leaders in the enterprise-wide marketplace mustremain competitive with function-specific applications that support the standard, provenprocesses successful organizations employ; as such, the functionality found in qualityCOTS products that support our requirements can be very robust. 4 LMTO Report CG406T2, Coast Guard Logistics System of the Future Risk Assessment, dated February2005 22
  29. 29. If one product does not meet the needs of the CG-LIMS requirements, a combination ofproducts 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 traininganalysis), it is important that this acquisition have, as an early deliverable, clear andadequate documentation for system maintenance and support. Due to modernization andthe unique scope of this acquisition, all stakeholders shall be engaged early to ensure theCoast Guard has a plan supported at the highest levels. A CG-LIMS product line shouldbe grown as part of the acquisition so that the support community has ownership andcompetence in the system prior to CGSD. The Asset Project Office (APO) and C4ITService Center should be used heavily to help steer logistics planning and ensure theCoast 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 sustainmentover the lifecycle of the system.4.3 ReliabilityThe method for defining the reliability requirements (Appendix B NF-02-05 and KeyPerformance Parameter (KPP) 5.2) is detailed in Section 2.4.3.2 of the CONOPS. Thekey metric for measuring reliability is the probability that the system will performwithout failure between maintenance periods.4.4 AvailabilityThe method for defining the availability requirements (Appendix B NF-02-03 and KPP5.1) is detailed in Section 2.4.3.1 of the CONOPS. The key metric for measuringavailability is downtime of the system in hours over a calendar year.4.5 MaintainabilitySection 4.0.1 contains the detailed system maintainability requirements.Periods of planned system maintenance shall be coordinated so that down time impact isminimized. There are no specific maintenance interval requirements, as long as theavailability and reliability requirements are met.4.6 SurvivabilitySection 4.0.1 contains the detailed system survivability requirements.Logistics plans developed to support this system shall include provisions for effectivecontinuity of operations during catastrophic events, such as a Katrina-like hurricane or anattack, failure or other accident where redundant power and connectivity are completely 23
  30. 30. lost. Section 2.4.5 of the CONOPS describes how the sustainment community plans todeal with threats and hazards once the system is supported by the Coast Guard.4.7 Personnel, Safety, Human Factors, and Environmental ConsiderationsAside from the section 4.0.1 requirements, Section 6 of this document (Trade-Offs)discusses important usability attributes. The CONOPS section 2.5 provides furtherinsight into expected staffing and support structure of the Coast Guard IT sustainmentcommunity.4.8 Training RequirementsThe PM shall engage the Assistant Commandant for Human Resources (CG-1), HumanSystems Integration for Acquisitions Division to analytically and systematicallydetermine Performance Support and Training (PS&T) requirements so that all CG-LIMScapability 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, jobaids of all types, and resident training. It integrates training strategies with elements oflogistics support to most effectively and efficiently achieve the personnel performancelevels required to operate, maintain, and support systems and assets. It includes the“tools” used to provide learning experiences, such as computer-based interactivecourseware, simulators, actual equipment (including embedded training capabilities onactual equipment), and IETMs, as well as the methods by which they are used. ThePS&T system shall consider both unit-level operators and support personnel.A specific strategy for CG-LIMS performance support and training shall include DCMSModernization teams as a focal point for initial training so that CG-LIMS use can beeffectively incorporated into transformation efforts.All recommendations for PS&T solutions shall be supported by systematic analyses thatare validated and approved by CG-1. A key component in these analyses is the FrontEnd Analysis (FEA) process, which is a formal procedure for determining the mosteffective and efficient performance support systems. The FEA process is specificallydetailed in the CG Training System Standard Operating Procedures (SOP), which areintended to ensure the process is auditable, verifiable, traceable, and repeatable.The CG Training System SOP requires that all maintenance and operator tasks beidentified, sorted, and analyzed up front, to determine whether performance gaps are bestclosed by resident training or non-training solutions. Obtaining system supportdocumentation early in the acquisition will facilitate this analysis. The size and scope ofvarious types of performance support requirements are generally identified at this step.Additional analyses are then conducted on each performance support system to determinethe best means (location, source, type) of delivery. After appropriate supportrequirements are identified, it is imperative that equal rigor be applied to the analysis of 24
  31. 31. potential solutions as to how this support shall be designed, developed, implemented andits effectiveness continuously evaluated, in order to minimize life-cycle cost.To optimize the efficiency of these performance support systems, it cannot be overstatedthat not all performance requirements require the development of formal performancesupport or training. Analysis and development of interventions shall be limited by areasonable understanding of which knowledge, skills, attributes and abilities learnersneed, and shall take into account whether such competencies are better acquired in otherexisting training programs (i.e. Basic Training or A-school).CG-1 will consider any commercially-provided support tools and systems and trainingthat might be available with the COTS product in order to determine if it is effective andefficient for Coast Guard application. In many cases, commercially-provided support isused to roll out initial delivery while the Coast Guard considers the benefit of developingorganic, long-term performance support and training systems.If formal training is required, CG-1 will partner with Force Readiness Command toensure that it is appropriately delivered, resourced, documented, and supported in theFormal Training System. 25
  32. 32. SECTION 5: KEY PERFORMANCE PARAMETERS KPP Threshold Objective 5.1 Operational Availability 5 CG-LIMS shall provide an CG-LIMS shall provide an operational availability of at least operational availability of at least 98.6%. 99.2%. 5.2 Operational Reliability 6 CG-LIMS shall provide an operational reliability of at least 93.1%. 5.3 System Response CG-LIMS shall accommodate a CG-LIMS shall accommodate a registry of 56,000 named users registry of 56,000 named users with with up to 35,000 concurrent users up to 35,000 concurrent users with with no more than 5 seconds for no more than 3 seconds for any page any page to be displayed and 10 to be displayed and 5 seconds for seconds for acknowledgment of acknowledgment of any transaction. any transaction. 5.4 Interoperability: Financial For every transaction meeting the Compliance definition of a financial event in accordance with FSIO OFFM-NO- 0106, CG-LIMS shall capture 100% of the data required for FFMIA compliance. 5.5 Interoperability: Financial CG-LIMS shall provide financial CG-LIMS shall provide financial Transaction Visibility 7 managers access to 100% of managers access to 100% of transaction-level detail for each transaction-level detail for each financial event within 24 hours of financial event within 1 hour of posting. posting. 5.6 Asynchronous Endurance The system shall implement The system shall implement mechanisms to process CG-LIMS mechanisms to process CG-LIMS activities at units operating in activities at units operating in asynchronous environments for at asynchronous environments for at least 3 months with zero network least 6 months with zero network connectivity. connectivity. 5.7 Security Provide for sensitive but unclassified, and/or unclassified information in accordance with COMDTINST M5500.13 (series) and COMDTINST 5500.21, and maintain the standards set forth in NIST 800-37 and other application security documents to protect against unauthorized disclosures of privacy information. 5 CG-LIMS CONOPS Section 2.4.3.1.6 CG-LIMS CONOPS Section 2.4.3.2.7 For every segment of CG-LIMS implementation, financial managers of the Coast Guard shall have accessto the transaction-level detail of each financial event for purposes of reconciliation and producing financialreports. To achieve FOC, CG-LIMS shall automate the integration of this data with the general ledger andenterprise core accounting system. 26

×