RFI_70Z02325R93360001_USCG CGCM 05202025.docx

THIS IS A REQUEST FOR INFORMATION (RFI)

RFI #70Z02325R93360001

Procurement Type: Request for Information (RFI) Sources Sought

Title: USCG Case Management System (CGCM) Modernization RFI

NAICS Codes: 513210, 541511, 541512, 541513, 541519

Primary POC: Patricia Willett, Contracting Officer – patricia.s.willett@uscg.mil Secondary POC: William Johnson, Contract Specialist – william.o.johnson@uscg.mil

A. Background

The USCG uses case management processes, tools, and Information Technology (IT) systems to enable and support execution of its search and rescue (SAR), law enforcement, security, military, marine safety, navigation, and disaster response operations in inland, coastal, and offshore zones.

The USCG has numerous legacy operational systems and a multitude of internally developed tools which provide these case management capabilities. The USCG identified ten (10) legacy systems which are high priority for modernization. These systems are not integrated, have different levels of capability, and are approaching obsolescence. These systems include:

· Marine Information for Safety and Law Enforcement (MISLE)

· Environmental Compliance System / Vessel Incident Discharge Act (VIDA)

· Field Activity Case Tracking System (FACTS)

· Case Matter Management Tracking System / Law Manager (CMMT/LM)

· Boating Accident Report Database (BARD)

· Incident Management Software System (IMSS)

· Country Assessment Tracking and Evaluation Tool (CATE)

· U.S. Aids-to-Navigation Information Management System (USAIMS) / Coast Guard Bridge Registry and Information System (USAIMS/BRIX)

· DHS Integrated Security Management System (ISMS)

These systems utilize many terabytes of data (both structured and unstructured) (e.g., MISLE ~12 TB as of early 2025) and numerous interfaces (e.g., MISLE ~30 interfaces) to other systems.

The legacy systems have a number of issues and capability gaps (to varying degrees) that the USCG desires to resolve in a future modernized solution. These include:

· Gap 1 - Obsolescence and Supportability

· Systems unsustainable due to reliance on outdated technology

· Systems subject to removal from network due to security risks

· Gap 2 - Data Quality:

· Incomplete Data Collection

· Inaccurate Date Capture

· Inconsistent Representation of Data across Systems

· Lack of Historical Records

· Gap 3 - Data Security:

· Lack of Credentialing

· Lack of Data Change Audit Trail

· Gap 4 - Interoperability:

· Inability to share information internally between systems

· Inability to share information externally with partners

· Gap 5 - Data Accessibility:

· Non-standardized data formats

· Inconsistent documentation standards

· Non-discoverable data

· Inability to display case data in real time

· Gap 6 - Workflow Management:

· Workflow Management and Documentation

· Mobile connectivity

· Electronic signatures

· Action/Completion Prompt

B. Scope

The USCG is seeking to procure a modernized CGCM IT solution to replace/integrate the legacy systems and mitigate the current capability gaps in the areas of obsolescence and supportability, data quality, data security, interoperability, data accessibility and workflow management. The new solution should improve affordability, efficiency, and effectiveness of the case management processes and supporting infrastructure. Affordability during operations and sustainment is particularly important.

The USCG has identified four (4) broad categories of workflows the new system needs to support:

· Compliance

· Investigation

· Response

· Waterways Management

The complexity, cost, and risk associated with replacing/integrating all ten (10) systems requires an agile incremental implementation approach where future applications can integrate into the existing family of systems. MISLE is the most complex and largest system and is targeted as the first system for modernization and integration with the other existing systems and applications systems. The CGCM system will achieve Initial Operating Capability (IOC) when the functional capabilities from MISLE are fully implemented. Modernization of other systems should follow an incremental approach to achieve a Full Operating Capability (FOC).

The USCG requires a case management solution that allows multiple users to initiate, plan, actively update, report on and archive cases. The solution should have a method to establish relational linkages between multiple active mission workflows to achieve an overall operational awareness of related cases conducted in the 11 statutory missions of the USCG (https://www.history.uscg.mil/Home/Missions/).

The new CGCM system will be entirely UNCLASSIFIED but will host sensitive data (various types). The new CGCM system must be able to handle large quantities of both structured data and unstructured evidentiary data (e.g., video/voice recordings, pictures) and maintain evidentiary chain of custody.

The new CGCM system will include users who have different access needs. USCG users will have direct access to workflows and sensitive data (IL4), while some users (e.g., state/local, possibly federal users accessing via personal devices) need only limited access to input or export data (IL2).

The new CGCM system will need to be highly available, reliable, maintainable, and scalable.

The new CGCM system will need to be cyber secure and resilient (i.e., FIPS-199 H/H/H; DISA Cloud Security Requirements Guide (SRG) Impact Level (IL) 4/5 backend), support multi-factor authentication for federal (i.e., CAC/PIV) and non-federal (i.e., two-factor) users, support highly granular role-based access control to both functions and data, have robust data loss prevention mechanisms, and implement zero trust principles.

The new CGCM system will have between 20k-30k+ total USCG users with typical load being between 2k-3k+ USCG users daily.

The new CGCM system needs to be adaptable, allowing the USCG to change workflows as statutory and regulatory needs change, and needs to provide data analytics and reporting capabilities.

The new CGCM system will need to be able to interface with mobile devices for data import/export in situations where there is limited or no connectivity (i.e., Denied, Degraded, Intermittent, and Limited (DDIL) environments).

The new CGCM system will need to be interoperable, including legacy system interfaces, ability to add new interfaces, and the ability to import/export data.

The new CGCM system needs to accommodate digital signatures.

The new CGCM system needs to ensure data quality/validation and prevent redundant data entry (i.e., auto-populate, prevent duplicate entry).

The new CGCM system needs to provide for training, without altering live data.

The USCG is researching various potential solutions – especially those that can be fielded quickly with low risk(s). The USCG objective is for a modular solution that integrates mature sustainable products and readily allows for additional capability integration (e.g., computer aided dispatch, voice transcription).

This Request for Information (RFI) is to determine the ability of small and large business vendors to provide the requested CGCM software solution, along with the requisite services needed for implementation, operations, and maintenance.

B.1 General Information (Please reference the question number with each response as follows)

1. Company Name, Company Address, Company Point of Contact, Telephone Number, Email Address, and Business Type.

2. Provide a general description of your relevant products and/or capabilities. Please provide URL links, if more detailed information is available online.

3. Is your product available on any current government strategic sourcing contracts? Please list the contract vehicle (contract number, GSA FSS number) if applicable.

4. Would you likely provide a quote if a Request for Proposal was issued? If not, please explain why.

5. Can your company offer a solution that meets the USCG capability needs described in this RFI? If you can only meet a subset of capability needs, can your product(s) readily be integrated into a larger solution?

6. How many times have you successfully implemented large, highly complex case management solutions? Please provide an example including summary level details regarding size/complexity and technical approach (i.e., architecture, software). For each example, provide a customer/agency (including a contract # if for Federal Agency) contact name, phone number, email address.

In order to make a determination for a small business set-aside, two or more qualified and capable small businesses must submit responses that demonstrate their qualifications. Responses must demonstrate the company's ability to perform in accordance with the Limitations on Subcontracting clause (FAR 52.219-14).

B.2 Specific Information (Please reference the question number with each response as follows)

General

1. Given the description of the USCG need in this RFI, provide a recommended summary level technical solution architecture and brief rationale of how/why it meets the USCG need.

2. Describe how your recommended solution is modular and allows for capability insertion and integration of future modules.

3. Describe the licensing model(s) you would recommend, including any key affordability advantages it provides.

4. Have you implemented highly secure systems before, particularly FIPS-199 H/H/H and/or IL4/5 cloud solutions? Describe how you would ensure security is "baked-in, not bolted-on."

5. Given the description of the USCG need in this RFI, what key risks do you perceive? How would you address them?

6. What would be an estimated schedule including milestones for development environment stand-up, Minimum Viable Product (MVP), and Initial Operating Capability (IOC)? Describe any key schedule risks and how you would address them.

7. Describe the recommended developmental approach, including agile methodology. How is Technical Debt managed? Identify any key needs levied on the Government to enable success of the agile approach.

8. Provide a brief summary of problems encountered implementing large complex case management solutions and how you avoided or fixed them (i.e., lessons learned).

9. What key information do you feel is lacking, that may limit your ability to respond to this RFI completely and accurately? What key questions do you have? [Note - No proprietary information should be included in any response to this question, as the USCG may use this information in future RFIs, industry days, etc. or publish questions & answers (identity redacted).]

Acquisition, Procurement and Pricing

10. Describe what product modifications (if any) would be needed to meet the USCG needs. Briefly discuss any associated risks and cost implications.

11. Please provide a Rough Order of Magnitude (ROM) cost estimate, breaking out the following cost elements: development/implementation costs; cloud license(s); software license(s); sustainment cost(s). Identify any key cost assumptions or cost risks.

12. Please provide any recommendations for structuring the contract (e.g., CLINS, contract type(s), handling change requests, growth)

Cybersecurity, Cyber Survivability, & System Security Engineering

13. Describe cyber security & resilience aspects of the recommended solution, including zero trust.

14. Discuss how readily your solution could be implemented in a DISA Impact Level 4/5 cloud environment? Do you already have a similar solution running in an IL 4+ environment? If not, what would be the potential impacts of needing to do so?

15. Describe your approach to Role Based Access Control (RBAC) to limit access to functions and data? Would it ensure adequate protection of sensitive data of different types (PII, PHI, LES, etc.)?

16. Describe your approach to cyber monitoring and threat mitigation? Would the approach be compatible with using a DoD approved Cyber Security Service Provider (CSSP)?

Compliance

17. Is your solution compliant with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. §794d)?

Interoperability

18. How does your solution enable interoperability? What open standards are used? Does it offer a standard Application Programming Interface (API)?

Data Management & Storage

19. Describe how the recommended solution would improve data management, quality, uniqueness, validation, eliminate redundant data entry, etc.

20. How would your company handle the migration and integration of a large amount of historical data from an existing system?

21. How does your solution handle data lifecycle management, including data retention, archiving, and deletion policies?

22. Describe your Data Storage architectural approach including scalability for growth. Is it compatible with the long-term USCG vision of a Data Lake?

23. Describe how your solution handles unstructured evidentiary data (e.g., images) and can maintain chain of custody?

System Capabilities

24. Please describe your solution’s ability to deliver some capabilities with devices in a Denied, Degraded, Intermittent, and Limited (DDIL) environment (e.g., smart phone, tablet).

25. Please describe how your solution will allow multiple authorized users to initiate and collaborate on records simultaneously, retain work in progress while they determine required data to create and update case records.

Data Analytics and Reporting

26. Describe the Data Analytics capability in your approach, including custom reports and dashboards.

27. Describe if/how the system provides the capability to automatically generate and distribute reports.

Support

28. Please provide a description of system support strategy: (e.g., training, what levels/tiers of support are available; what is included; the procedures for helpdesk escalation; hours of operation; response times; and location(s) of support services).

Miscellaneous

29. Please provide any additional information or details that may have been missed.

30. Are there additional questions you recommend we ask industry in a follow-up RFI? [Note - No proprietary information should be included in any response to this question, as the USCG may use this information in future RFIs, industry days, etc. or publish questions & answers (identity redacted).]

31. Would you be interested in attending a “Reverse Industry Day” with the government?

B.3 Future State (Please reference the question number with each response as follows)

32. What provisions or features does your solution provide that mitigates future obsolescence risks?

C. Contract Type

TBD

Place of Performance

TBD

E. Requirements

See Sections A & B.

F. Submission and POC Information

· Please respond to this RFI electronically using the MS-FORMS link provided below by NLT 5/28/2025 @ 1400ET

· https://forms.osi.apps.mil/r/nsRwDbnQzZ

· All proprietary information that is not to be disseminated in follow-on Government documents must be clearly identified in the response.

All costs associated with responding to this (RFI/Intent to Bid) will be solely at the responding party’s expense. Proprietary information and trade secrets, if any, must be clearly marked on all materials submitted. All information received that is marked Proprietary will be handled accordingly. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Responses will not be returned nor will the Government confirm receipt. All Government and Contractor personnel reviewing responses will have signed nondisclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described in 41 USC 2101-2107. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Please be advised that all submissions become Government property and will not be returned.