RFI_for_ICMS_Final_Post.docx

Investigative Case Management System

REQUEST FOR INFORMATION (RFI)

Purpose:

DOJ OIG is conducting market research to gain a greater understanding of the full range of available options for an Investigations Division Case Management System (IDMS). This is an RFI released pursuant to Federal Acquisition Regulation (FAR) Part 10 - Market Research. This RFI's purpose is to obtain market information on viable sources of supply, industry practices, answers to specific questions, and industry comments related to investigative case management.

Background:

Department of Justice Office of the Inspector General (DOJ OIG), a component of the Department of Justice (DOJ), currently uses an in-house developed application called Investigation Database Management System (IDMS) as a case management tool for investigation purposes. This system is a web-based application with a desktop interface consisting of three interacting components: database entry (LawManager), document management (iManage), and report generation (Crystal Reports). DOJ OIG is looking to replace IDMS with a new system that provides the same core investigative case management functions along with some new capabilities. DOJ OIG is interested in obtaining responses to this RFI from prospective offerors that could provide the services and software for a Commercial Off-The-Shelf (COTS) system or a Low Code solution. The Government encourages responders to this RFI and prospective offerors to propose the most innovative, cost-effective method in achieving the desired capabilities and results.

Proposed software solution may be required to attain an Authorization to Operate (ATO) if they do not currently have one for DOJ. The ATO process normally takes six months to complete. Once the ATO is approved, the Letter to Commence is issued. FOC is the milestone when the DOJ OIG investigative case management users are using the replacement system with at least the same functionality as the current IDMS. The Government ideally seeks responders and prospective offerors that can provide low risk system solutions that are operational and customizable. The solution must be flexible enough to be tailored to the DOJ/OIG needs. If a low code solution is proposed DOJ/OIG will own the source code and all configuration documentation. If a COTs product is proposed applicable FAR data rights will apply. Contractor must assist with configuration changes and any system provided shall satisfy the Government's key requirements.

Objective:

DOJ OIG is seeking industry feedback regarding a methodology to acquire an Investigations Division Case Management System (IDMS) that must be:

1. Capable of managing all phases of OIG/Investigations Division (INV) investigations from initial allegation/complaint (input) to final disposition.

2. A web accessible application available to DOJ OIG office groups throughout the country.

3. Compliance with Federal Information Security Management Act (FISMA).

4. Able to meet the processing requirements of DOJ OIG/INV and compliance with the secure system requirements of the DOJ OIG network.

5. Capable of being hosted, in a cloud-based platform (GCC High).

The system must be customizable by DOJ OIG administrators to allow field changes and the ability to add new fields to the database as required Opportunity:

DOJ OIG/OIG wishes to identify industry specific information to help better define the systems requirements for a COTS IDMS or Low Code solution. The IDMS is used to process investigations from initial allegation/complaint (input) to final disposition. The system must be able to route cases through the different investigative phases automatically and be usable simultaneously by multiple groups on a nation-wide scale. The IDMS will be a System of Record (SOR), and as such shall maintain data integrity while also being easily editable.

Responses Requested:

To assist DOJ OIG in developing IDMS and further refine our requirements, please provide responses to the following questions and requirements. OIG understands that some responses may be conceptual, while others are limited to the type(s) of technologies being considered. Responses should include the following information: See Appendix A and the Attached Excel Spreadsheet Appendix B Instructions and Response Guidelines:

RFI responses are due by May 06, 2021 and shall be limited to a total of 25 pages for appendix A not including: foldouts and full-size page charts or other supporting artifacts. Page size is limited to 8.5 x 11 inches, 12-point font, with 1-inch margins in Microsoft Word format.

For Appendix B provide yes or no answers. Include an assumption page. If there are any caveats to the yes or no include them next to the answer. Keep it short if you can’t keep it short address it in Appendix A.

***Please review ICMS Requirements Appendix B and provide a yes or no response in the column by each requirement.

Please provide the information you deem relevant in order to respond to the specific inquiries of the RFI. To support budget and planning purposes include base year (development, implementation, software) along with additional maintenance and cost-to-operate estimates based upon the requirements outlined in the RFI. This RFI does not constitute a Request for Proposal (RFP), Invitation for Bid, or Request for Quotation, and it is not to be construed as a commitment by the Government to enter into a contract, nor will the Government pay for the information submitted in response to this request. All information contained in this RFI is preliminary as well as subject to modification and is in no way binding on the Government. Responses shall be submitted electronically via email with the title E-Mail Title: ICMS OIG RFI, to OIG.Procurement@usdoj.gov; Erica.J.Marcotte@usdoj.gov Erica.J.Marcotte@usdoj.gov the subject line shall read: OIG IDMS. NO SOLICITATION EXISTS AT THIS TIME.

A select few of the most qualified responses may be selected by OIG for an additional in-person question. The Government reserves the right to determine how many and who qualifies for a follow-up meeting. The Government will not be associated with any travel related cost for the follow-up meeting.

Contact Information:

Contract Specialist: Erica Marcotte Email address: Erica.J.Marcotte@usdoj.gov ; OIG.Procurement@usdoj.gov;

The Government is not required to respond to any information provided in response to this RFI. It is the responsibility of the interested parties to monitor Contract Opportunities for additional information pertaining to this RFI.

Questions and Submission Information:

E-Mail: OIG.Procurement@usdoj.gov; Erica.J.Marcotte@usdoj.gov E-Mail Title: ICMS OIG RFI Questions Due: March 27, 12:00 p.m. Est Due May 07, 2021 4:00 p.m. Est Appendix A: Interested Vendor Overview Questions (25 pages) Interested Vendors are requested to submit brief answers to the following:

1. Company Name and DUNS Number

2. Business Size - Is your company a small or large business based on NAICS 541512- Computer Systems Design Services

3. Certifications - Is your company FEDRAMP Certified as a Cloud Service Provider (CSP)

4. Product/Solution Description

5. Contract Vehicles - Is your product/solution available through DOJ, GSA IT70 or on a GWAC? Please provide the identifiers of any such contract vehicles on which your product/solution is available on.

6. System Use - Provide a brief description of the number of organizational customers that have acquired the precise product/solution you propose to use/configure/modify to meet DOJ OIG requirements, the daily transaction volumes for each organizational customer and the number of users at each organization (if known), along with the specific "mission" or application for which your product/solution is used by each organizational customer and the date when your product/solution began production operations with each organizational customer.

7. Law Enforcement Applications or Government Agencies - Is your system implemented and in-use in a law enforcement or Government production environment for investigative case management?

a. If yes, identify each and all organizational customers/system name and references including contact information (i.e. LAPD, ICE, FBI) as well as when the system reached full operational status with each law enforcement user.

b. Provide a POC for up to 3 of the Law Enforcement or Government Agencies

8. Costs - Based on experience, provide estimated base and O&M costs.

9. Software licenses - Identify costs associated with the product and any 3rd party software, including annual maintenance

10. Releases/patches - Identify software costs associated with following the recommended upgrade path

11. Labor - Identify labor costs to support the system and cost to install/implement upgrades (based on recommended upgrade path)

12. Other costs - Identify any costs associated with developing, or supporting the system (licenses, implementation, maintenance, and training).

13. Hardware Environment - Describe the hardware environment required for production operations and to support your system/solution.

14. Cloud Environment Transition (note IDMS legacy system is currently in Azure GOV Cloud)- Describe the capability of the proposed hardware environment required for production operations and to support to be transition to a hosted cloud-based service.

15. Implementation Model - How is your solution implemented? For example, is your company the sole implementer or are other companies also able to implement your product? Provide a brief explanation. Examples may include ability to train/certify government developers to maintain; evidence of third-party companies being able to support; etc.

16. Customizations - Explain how software development of customizations (i.e., modifications) would be conducted and managed, if required. For those customization(s) listed earlier which required such customizations, please provide a general description of the scope of those changes and how long it took to develop those changes to the customer's satisfaction, prior to system testing.

17. Interfaces - Describe your system's approach to interfaces, specifically any existing interfaces to law enforcement/other significant entities currently in production and the ability to add new interfaces.

18. Pre-Implementation Upgrade Path - When development of any required customizations is complete, will the most current version of the product be installed? What is your approach for installing patches during development of these customizations?

19. Post-Implementation Upgrade Path - Describe your approach to "routine" product upgrades post-implementation that apply to all of your customers of the proposed product/solution, including how upgrades are handled when customer selects not to upgrade on a scheduled basis. Also, describe your approach of notifying customers of software patches.

20. What is the product support posture/cost if the government falls 1, 2, or even 3 major upgrades behind the commercially available solution?

21. Licensing Model - Describe your licensing model (i.e. annual, name seats, or perpetual).

22. Property Rights - What are the property rights of your product, including ownership of the source code, in the event of company bankruptcy, sale of company, relationship with customer ends, etc.?

23. Proprietary Solution - Is any part of your system or solution you would propose proprietary? If so, please describe.