SOURCES SOUGHT
70 -- Coast Guard Logistics Information Management System - Attachment 1 - CG Enterprise Architecture
- Notice Date
- 5/28/2009
- Notice Type
- Sources Sought
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Department of Homeland Security, United States Coast Guard (USCG), Commandant (CG-912), U.S. Coast Guard Headquarters, U.S. Coast Guard Headquarters (CG-912), 1900 Half Street, SW, Washington, District of Columbia, 20593-0001
- ZIP Code
- 20593-0001
- Solicitation Number
- HSCG23-09-I-2DW265
- Archive Date
- 7/31/2009
- Point of Contact
- Laura Q. Spillane, Phone: 202-475-3404
- E-Mail Address
-
laura.spillane@uscg.mil
(laura.spillane@uscg.mil)
- Small Business Set-Aside
- N/A
- Description
- Coast Guard Service Oriented Architecture Overview (SOA) & Enterprise Architecture (EA) This Request for Information (RFI) is issued by the United States Coast Guard (USCG) Office of Contract Operations in support of the Coast Guard Logistic Information Management System Project Management Office to conduct market research regarding the state of the market for COTS products that will meet the Coast Guard’s need for a Logistic Information Management System. Description and Capability Requirements: The Coast Guard Logistics Information Management System (CG LIMS) Acquisition Project will require a centrally managed, integrated, enterprise-wide logistics information management system to support U.S. Coast Guard assets and systems. This system will provide logistical support for aircraft, cutters, boats, shore facilities and Command, Control, Communications, Computers and Information Technology (C4IT) systems. The Coast Guard objective is to acquire a logistics system that will leverage industry standards and best practices to increase efficiency, optimize effectiveness, and establish common processes for managing logistics across the enterprise. The ability to maintain full operational capabilities and minimize lifecycle costs are fundamental goals. The required CG LIMS system will be robust and interoperable with legacy Coast Guard and other government agencies’ logistics and financial systems. CG LIMS will interface with existing and future Coast Guard logistics and financial systems as information technology (IT) systems are transformed and modernized. As such, the system will need to be Service Oriented Architecture (SOA) compliant, and be scalable and flexible in meeting existing and future requirements. The CG LIMS software solution is expected to use state-of-the-market, commercial-off-the-shelf (COTS) tools, including an Enterprise Asset Management (EAM) tool configured to meet the business requirements of the Coast Guard. CG LIMS configuration, integration and deployment will occur in discrete segments that will provide new capabilities and functionality or consolidate and replace existing logistics IT tools. CG LIMS will be an important tool used to support the Coast Guard’s Logistics Business Model and the Four Cornerstones of that model: Configuration Management, Total Asset Visibility, Bi-Level Maintenance and single point of accountability through Product Line Managers. CG LIMS will be designed to function on the Coast Guard Data Network (CGDN+), with future migration to DHS OneNet. It will be hosted at Coast Guard Operations Systems Center (OSC) and be accessible through Coast Guard Standard Workstations (CGSW) or other Coast Guard standard hardware. An overview of the Coast Guard SOA and Enterprise Architecture (EA) is provided in Attachment #1- CGEA. A design goal of the CG LIMS program is to reduce the amount of software development by using proven, well supported COTS IT tools. Minimizing customization of COTS tools will allow the Coast Guard to obtain the benefits of commercial best practices implemented in the COTS tools. CG LIMS will use an Evolutionary Acquisition approach based on an Incremental Model. This approach is expected to speed delivery of capability, providing improved capability in a shorter period of time. The initial deployment will be followed by subsequent segments of capability. Each cycle will produce a working system. The defined segments are listed below: CG-LIMS Segments: (1) Configuration and Maintenance Management (focus of this RFI), (2) Supply Chain Management, (3) Technical Data Management, (4) Financial Integration and (5) Additional Integration. The CG LIMS project and strategy will follow the DHS System Engineering Life Cycle policies and processes. It is very likely that the complexity and breadth of the CG LIMS requirements and Coast Guard business processes will demand a solution that consists of more than one major IT tool. In addition to EAM capability, CG LIMS may use technical data management, content management or other IT tools to address all requirements successfully. Requested Information: For the purposes of this RFI, we ask respondents to consider all the aforementioned segments of the program while providing information specific to Segment 1, Configuration and Maintenance Management. At a minimum, responses to this RFI should address the following: 1. How would you organize your approach to deploying and integrating multiple COTS software products for the Coast Guard’s enterprise logistics system? 2. Briefly describe your software configuration management methodology. (Include software configuration management tools you typically utilize) 3. Indicate all Rough Order of Magnitude (ROM) costs and cost drivers for implementing your product. (Include software, maintenance, licenses, tech data, training, support, etc.) 4. Briefly describe the Deployability of your product. Please include: -Success stories and current industry and government customers -Flexibility of your product (scalability, customization, and integration) -Limitations/constraints of your product (user capacity, integration limits, ease of use) 5. What would be your technical approach to integrating your product incrementally and replacing one or more of the Coast Guard’s current logistics IT tools for: 1.) Asset Configuration and Maintenance management, 2.) Supply Chain management, 3.) Technical Information/Data management, and 4.) interfaces with other CG systems such as Financial management and Accounting systems? 6. What would you consider as the significant technical risks associated with implementation of your product and how would you mitigate those risks? Provide past examples, if possible. 7. Please indicate whether your software is available on GSA Federal Supply Schedules, other Government-wide Agency Contract (GWAC), or Open Market. Business Issues and Response Format: This RFI is for planning purposes only and shall not be construed as a Request for Proposal (RFP), Request for Unsolicited Proposal, or as an obligation or intent by the USCG to acquire any products and/or services. The USCG does not intend to award a contract as a result of this RFI or otherwise pay for the requested information. The purpose of this RFI is to collect available market information that will be used to assist the USCG in evaluating its options related to its need for a logistics information management system. Submission of a response to this RFI is entirely voluntary and shall not obligate the USCG to pay, or entitle the submitter of information to claim, any direct or indirect costs or charges or any other remuneration whatsoever. The USCG understands that any pricing information submitted under this RFI is an estimate only and is not binding nor does it constitute a proposal. Not responding to this RFI will not preclude participation in any future RFP, if issued. If a solicitation is released, it will be publicized in accordance with the requirements of the Federal Acquisition Regulation. It is the responsibility of the potential offeror to watch for additional information pertaining to this requirement. In responding to this request, data and information (drawings, documents, tables, graphs, etc.) may be submitted in different formats and media (paper or electronic files). Electronic submissions should be formatted in MS Word, MS Excel, MS PowerPoint or Adobe.pdf. The total length of each response should not exceed 25 pages. Proprietary information, if any, should kept to a minimum and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Data marked proprietary will be protected in accordance with all applicable statutes and regulations. The submissions will not be returned, unless the Contractor specifically requests it. Costs associated with returning information shall be incurred by the provider of such information. Industry is advised that Government’s support contractors (Java Productions, Inc., Serco, Inc., and Perot Systems Corporation) will be involved with the review of submitted information. If a Government support contractor other than those listed above will be involved with the review of submitted information, each vendor that has responded to this RFI will be notified before their information is provided to that contractor for review. All Government support contractors required to review the information will submit non-disclosure or confidentiality statements. The Government assumes that any party submitting a response to this RFI consents to the release of their information to the Government support contractors noted above for the sole purpose of assisting the Government in its review of the response. Any party NOT wishing to release its submission to these contractors must explicitly so state on the cover page of the response. The applicable NAICS Code is 541512. All industry respondents should indicate their business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business). Small business concerns are defined as a concern, qualified as a small business under the criteria and size standards in 13 CFR part 121. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. Questions regarding this announcement shall be submitted in writing. Verbal questions will NOT be accepted. Questions should be submitted to Laura Spillane at the electronic or physical address below. Responses to this RFI may be submitted to Laura Spillane via email (laura.spillane@uscg.mil) or hard copy mail by 19 June 2009. Responses received after that date may not be afforded a comprehensive review. Responses should include the name, e-mail address, and telephone number of a point of contact having authority and knowledge to discuss responses with Government representatives.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DHS/USCG/GACS/HSCG23-09-I-2DW265/listing.html)
- Record
- SN01830275-W 20090530/090529000251-7669e75bf5973d9025b00e38dd396909 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |