Updated 12/5/2019: The OCC offers the following additional information regarding OpenText and OCC Proprietary systems referenced. OpenText: Microsoft SQL Server is the back-end database that support’s the OCC’s OpenText solution. The OCC is interested in solutions that have the capability to query a read-only view from the OpenText system that contains document metadata to return document IDs of potentially responsive documents. OCC proprietary systems: The OCC has a number of custom-developed systems with Java or ASP.NET front-ends and Microsoft SQL Server back-ends. The OCC is interested in solutions that have the capability to query a read-only view of data from these systems to identify rows from the view that contain information relevant to a legal matter (based on queries of up to 100 keywords). The view may be directory associated with the system in question or may be associated with the OCC’s enterprise data warehouse. Original Posting 11/25/2019: Requirement Title eDiscovery Software and Systems for Identification, Preservation, and Collection of ESI Introduction This is a Request for Information (RFI) only - it does not constitute an Invitation for Bids (IFB), Request for Proposal (RFP), or Request for Quotes (RFQ). This RFI is issued solely for information and planning purposes and does not commit the Office of the Comptroller of the Currency (OCC) to issue a solicitation (RFQ/RFP) or award a contract for any supply or service whatsoever. The OCC will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the respondents’ expense. Those who respond to this RFI should not anticipate feedback concerning its submission other than acknowledgement of receipt, if the submitter requests an acknowledgement. Background The OCC is an independent bureau of the U.S. Department of the Treasury that charters, regulates, and supervises all national banks and federal savings associations, as well as federal branches and agencies of foreign banks. Based in Washington, DC, the OCC has a nationwide staff of bank examiners that conduct on-site reviews of national banks and federal savings associations and provide sustained supervision of these institutions’ operations. The OCC is publishing this notice to obtain additional information about businesses that can provide eDiscovery Reference Model (EDRM) litigation support services addressing Electronically Stored Information (ESI) stored on the OCC’s network. ESI stored on the OCC’s network includes data on OCC local and network drives, in the cloud, in OpenText, in Appian applications, across Microsoft Office 365 products (e.g., Outlook and SharePoint), as well as in OCC proprietary systems. The OCC is seeking a solution that can identify, search, preserve, collect, process, and transfer such ESI from the OCC’s network to the OCC’s review platform, Relativity. While the OCC’s preference is for a cloud-based FedRAMP Authorized solution, the OCC will consider on-premises options in the event the agency finds justification related to cost, technical limitations, or security concerns. Requirement Description The OCC has a requirement for software and systems that can address certain EDRM litigation support services. EDRM services sought include, but are not limited to, the identification and preservation of potentially responsive ESI, the implementation of litigation holds, early case assessment (pre-review processing and/or analytics), and collection and transfer of relevant ESI to the OCC’s litigation review platform, Relativity. The OCC is seeking the following information from vendors with experience providing EDRM litigation support software or systems and services: Describe your EDRM litigation software or systems and the associated services you provide, including how your proposed solution will identify, search, preserve, collect, process, and transfer ESI, as well as and how the proposed solution will assist the OCC in litigation hold management. You should also detail whether the proposed solution is a single product or suite of products, whether it is compatible with Relativity, and how it interfaces with Relativity. State whether your proposed solution is cloud-based or on-premise. If your proposed solution is not cloud-based, please indicate why you propose an on-premise solution, and discuss any associated cost, technical limitations, and security concerns. Describe how your proposed solution will identify, search, preserve, collect, and transfer ESI stored on OCC local and network drives; in the cloud; in OpenText; in Appian applications; across Microsoft Office 365 products (e.g., Outlook and SharePoint); and in OCC proprietary systems. Describe how the proposed solution will interface with, and extract ESI from, the OCC’s SQL Server back-end databases. Describe the average data processing and transfer speed information associated with searching, collecting, processing, and transferring ESI to Relativity. For example, please describe the average data processing and transfer speed information associated with executing a search for ESI using twenty unique search terms across Outlook, SharePoint, and local and network drives containing in total 3 terabytes of information. Describe whether you offer managed services for your proposed solution. You should also detail whether you offer installation, deployment, maintenance, technical, and any other on-going product support, as well as whether you offer any end user and administrator training. What percentage of services do you provide to the private sector versus the federal government? Please provide any examples of where you successfully implemented EDRM solutions at other federal government agencies. Please describe any recommended security measures for the proposed solution to protect OCC data from bad actors (both internal and external). In addition, for any cloud-based solution, please state whether the solution is FedRAMP Authorized. Please indicate if your company has a comprehensive solution to address the entire EDRM process, including processing, review, analysis, and production of gathered ESI. Please tell us how you price your solution for Federal Government clients. Based on the information provided, for market research purposes, please provide a rough order of magnitude (ROM) of what you might expect your proposed solution to cost for the OCC, including including any associated storage and managed service cost information. Submission Requirements Interested parties are requested to respond to this RFI with an electronic document that fulfills the requirements below. Company Background - Provide summary information including company name, DUNS number, CAGE code, GSA Federal Supply Schedule (FSS) contract(s) or Government-wide Acquisition Contracts (GWACs) contract number(s) (if applicable), and designated point of contact’s name, title, email address and phone number. North American Industry Classification System (NAICS) Code, Size Standard, Product Service Code (PSC), and Company’s Business Type Classification under NAICS Code - Provide recommended NAICS Code to include Size Standard and your Company's Business Type Classification under the recommended NAICS Code (e.g. large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone business, woman-owned small business, veteran-owned small business, service-disabled veteran-owned small business, etc.). Provide recommended PSC. Price Lists or Catalogs/Pricing – Provide price lists or catalogs and the name of any resellers if you work through resellers. If applicable, provide information on volume discounts, prompt payment discounts, contract financing, and payment methodology. Responses shall be in Microsoft Word or Adobe Acrobat formats and no longer than 7 pages. The email shall include the following subject heading, “Response to 2031JW20N00002, eDiscovery Software and Systems for Identification, Preservation, and Collection of ESI RFI” Please email your response to: Laura Baker, Contract Specialist Email:
[email protected] Proprietary information, if any, shall be minimized and must be clearly marked. Responders shall avoid the use of excessive marketing language, submission of fancy brochures, and other unnecessary sales literature.