DRAFT--PWS_v.2.2_LSS 2025.docx

Litigation Support Services ITS CCO

DRAFT

Performance Work Statement for Litigation Support Services

Litigation Support Services

BPAS

Business Process Automation Systems ITS SPS

1.0 GENERAL

The Office of the Comptroller of the Currency (OCC) is an independent, non-appropriated bureau within the U.S. Department of the Treasury. The OCC charters, regulates, and supervises national banks, federal savings associations, and federal branches and agencies of foreign banks. Headquartered in Washington, DC, the OCC has district offices located in New York, Chicago, Dallas, and Denver and smaller offices across the country. Bank supervision is the core activity of the agency.

The OCC’s Chief Counsel’s Office (CCO) centrally manages four legal practice areas, including the Litigation and Enforcement groups. The Litigation and Enforcement groups, and occasionally attorneys practicing in other groups, use electronic discovery (eDiscovery) systems and services to support legal matters routinely handled by the OCC, including responses to subpoenas, Congressional requests, OCC investigations, OCC administrative enforcement proceedings, civil litigation before courts and administrative tribunals, and notices of public rulemaking. The OCC employs approximately 160 attorneys and 17 legal support staff,[footnoteRef:2] including approximately 50 attorneys in the Litigation and Enforcement groups who routinely use eDiscovery systems and services in their daily work. [2: In this document, references to "Legal Staff" include both OCC attorneys and legal support staff in CCO.]

The acquisition for Litigation Support Services (LSS) is intended to provide the Litigation and Enforcement groups with the eDiscovery services needed to effectively carry out the agency’s mission.

The OCC’s CCO is seeking an eDiscovery and LSS solution that leverages advance technologies for its CCO employees to collect and cull defensible data. This solicitation is issued pursuant to FAR Part 12 under the procedures of FAR Subpart 13.5 for establishing a single-award contract. The Government is restricting this procurement to Small Business concerns not specific to any socioeconomic category per FAR 19.5. The Contractor must be registered in the System for Award Management (SAM). The resulting contract must be for a period not to exceed 5 years (60 months).

2.0 APPLICABLE LINE ITEMS

The Contractor must furnish all materials, labor, equipment, and facilities except as specified herein to be furnished by the Government and must do all that which is necessary or incidental to the satisfactory and timely performance of the requirements.

The Contractor must furnish all the following items required under a resulting contract at a firm-fixed-price (FFP), time and materials (T&M), and labor hour (LH) basis. The T&M and LH quantities below have been estimated by the Government. The line items below are examples of what the Government has historically viewed for similar LSS services. However, the Contractor may restructure line items and propose new line items and hours with the exception of only using the FFP, T&M, and LH contract types.

2.1 Base Period (Month 1 through Month 12)

TOTAL COST FOR OP1 PERIOD

2.2 Option Period One (Month 13 through Month 24)

TOTAL COST FOR OP1 PERIOD

2.3 Option Period Two (Month 25 through Month 36)

TOTAL COST FOR OP2 PERIOD

2.4 Option Period Three (Month 37 through Month 48)

TOTAL COST FOR OP3 PERIOD

2.5 Option Period Four (Month 49 through Month 60)

TOTAL COST FOR OP4 PERIOD

TOTAL COST FOR ALL PERIOD (BASE + OPTIONS)

3.0 BACKGROUND

The Electronic Discovery Reference Model The OCC uses the Electronic Discovery Reference Model (EDRM) (https://edrm.net/edrm-model) as the framework for organizing and defining its eDiscovery processes. This document references the model below and uses many of its terms.

Figure 1 Electronic Discovery Reference Model Furthermore, this document uses the term left-side to refer collectively to the Identify, Preserve, and Collect stages in the EDRM, and the term right-side to refer to the Process, Review, Analyze, and Produce stages. The scope of work does not include the Information Governance or Present stages, and therefore, they are not included in the definition of left-side and right-side stages.

OCC’s eDiscovery System OCC has procured its own instance of RelativityOne Government, which includes the add-on RelativityOne Government Legal Hold. This scope includes tasks to support eDiscovery using RelativityOne Government.

The Chief Counsel Information Systems Group Information and Technology Services (ITS) is the OCC’s information technology (IT) provider and support organization. Within ITS, the Chief Counsel Information Systems Group (CCISG) provides CCO legal staff with support primarily for left-side stages and systems. CCISG is a five-member team consisting of three government employees and two Contractors. The CCISG team will be managing the collection, preservation, and legal hold components of RelativityOne Government. The Contractor is not responsible for providing these services but must coordinate with CCISG to properly provide its portion of the eDiscovery services.

EDRM Left-side Stages: Identify, Preserve, and Collect Legal staff use several tools to identify case-relevant sources of electronically stored information (ESI) and their custodians. These tools include Active Directory, organization charts, attorney interviews of potential ESI custodians, a variety of custom-developed systems for managing bank examinations and learned knowledge of common sources of ESI. The number of custodians for a case can range from single digits to the low hundreds.

Legal staff oversee the preserve stage with the assistance of CCISG and other ITS staff, custodians, and data stewards.

CCISG manages the collect stage, relying on assistance from other ITS personnel and Legal Staff for its completion. When collecting ESI from a particular system or application, CCISG works closely with the team that supports the application. CCISG relies on the application team to collect the ESI and provide it to CCISG for staging.

OCC’s collection tools include Pinpoint Labs Harvester Portable 6.0, Magnet AXIOM 5.9, and Exterro FTK 7.4, RelativityOne Government Legal Hold, and Microsoft 365 Compliance Center in the G5 Office 365 Government community. When ESI is collected, it is typically staged on network file shares before being transferred into Relativity. When collecting ESI from a particular system or application, CCISG works closely with the team that supports the application. CCISG relies on the application team to collect the ESI and provide it to CCISG for staging.

EDRM Right-side Stages: Process, Review, Analyze, and Produce RelativityOne Government will be the system that supports right-side stages, and support for right-side stages per this requirements document.

4.0 DESCRIPTION OF SERVICES AND SUPPLIES

4.1 Scope

The scope of work under the resulting contract includes:

1. Providing day-to-day operational support for right-side stages by working closely with the OCC’s legal staff and CCISG

2. Providing technical and operational support for RelativityOne Government and RelativityOne Government Legal Hold

3. Providing end-user case-kick off sessions for RelativityOne Government

4. Work with any OCC incumbent for these services to transition the services from the incumbent to the Contractor

5. The option for the OCC to require the Contractor to transition to a new Contractor or the OCC’s staff at contract termination

4.2 Tasks

This section defines the specific tasks required for litigation support services (operational, technical, and other support).

The Contractor must provide all contract deliverables as required by this requirements document.

1.1 1.2

1.2.1 Task 1 Transition (Phase-In) Support

The Contractor must meet with Government Staff and Contractor Support to gain an understanding of: 1) workspace configurations for end-users in Relativity Server and RelativityOne; and 2) guidance provided by Contractor Support to attorneys for workspace specific review strategies in Relativity Server and RelativityOne. This Phase-In must occur over a 30-day period. This transfer of knowledge is crucial for the Contractor to provide support to attorneys for migrated workspaces in which attorneys have already completed the data migration.

1.2.2 Task 2 Provide eDiscovery Operational Support (Right-Side) The Contractor must provide day-to-day operational support for right-side stages of the EDRM. The Contractor must be responsible for providing support for all workspaces. This support must include:

Loading documents collected from OCC sources into RelativityOne Government;

Loading documents collected from non-OCC sources (e.g., banks) into RelativityOne Government;

Remediating data anomalies and problems;

Processing documents in RelativityOne Government so that they are available for review and analysis by Legal Staff and other OCC employees;

Providing processing reports listing all files processed and all files that could not be processed (e.g., password protected, corrupt files);

Producing documents for presentation to court, opposing counsel, and other parties;

Culling data sets and removing duplicates from data sets;

Performing optical character recognition processes on documents;

Identifying and extracting embedded files;

Assisting users in the development of search criteria, filters, and tags;

Assisting users on the manual and the automated redaction of document and advising users on its utilization and best practices;

Implementing the Technology-Assisted Review (TAR) functions of RelativityOne Government in a workspace and advising users on its utilization and best practices;

Implementing RelativityOne Government’s Analytics tools (Structured, Conceptual, and Sentiment) and advising users on its utilization and best practices;

Assisting with the creation of privilege sets, coding decisions, coding rules, views, and saved searches;

Providing desk-side support to RelativityOne Government users;

Utilizing RelativityOne Government tool to export productions of documents for opposing counsel, the court, and other third parties;

Delivering productions electronically to OCC and external parties;

Loading productions onto external media and securely delivering the external media;

Tracking the delivery of productions;

Providing project and case management to coordinate left-side and right-side activities for cases, including producing strategies and plans for ESI collection and processing;

Conducting case kick-off meetings;

Identifying opportunities to train RelativityOne Government end-users;

Maintaining the security of physical media (external ESI productions delivered to contractor for processing);

Properly securing and protecting data, including maintaining the proper chain of custody; and Archiving and restoring RelativityOne Government workspaces OCC’s license for RelativityOne Government includes three types of workspaces. Repository workspaces are limited functionality workspaces for early case assessment activities. Once data has been collected, processed, and placed into a repository workspace, the Contractor must work with the OCC’s attorneys to determine which subset of data will require review. Once that subset of data has been identified, the Contractor must push the subset of data into a standard review workspace. Standard review workspaces are fully functional workspaces in which attorneys will review, code, redact, and create productions of data. If an attorney requires a standard review workspace or a repository workspace to be archived, the Contractor must place the data into a cold storage workspace. The Contractor is responsible for restoring cold storage workspaces to their original state, at the request of the Government.

The Contractor must start to ingest and process data no more than 24 hours from receipt, excluding weekends and federal holidays. Each 200 GB of data sent for processing must be accessible by the attorneys for review in RelativityOne Government within 72 hours of receipt of source material, excluding weekends and federal holidays. The Contractor must provide output reports for data ingestion, processing, and loading into RelativityOne Government. These reports must list all files processed and files that failed to be processed. The report must list the reason files were unable to be processed. The Contractor must export productions (including Native, TIFF, and PDF) at a minimum of 200 GB of data per 24-hour period. This 24-hour period excludes weekends and federal holidays. The Contractor must deliver data productions to the OCC or an OCC-designated external party via courier, secure file transfer mechanism (provided either by the Contractor or by the OCC), or external encrypted media. External encrypted media must be supplied by the Contractor and upon delivery must become property of the OCC.

The Contractor must conduct case kick-off meetings with legal staff and CCSIG when a review case is created. This case kick-off meeting must be at the discretion of the legal staff and topics must include, at a minimum, and at the discretion of the Legal Staff:

Assisting users with logging in;

An overview of right-side functions of the RelativityOne Government;

Training of RelativityOne Government right-side features;

Assistance with the culling of objects in the workspace using various features of the review tool (e.g., deduplication, email threading, analytics, redactions);

Assistance with the creation of saved searches;

Assistance with the creation of review batching;

Assistance with the creation of custom coding decisions and coding rules; and Assistance with the creation of customized views of the data Case kick-off meetings must be up to 90 minutes in length (though longer meetings may happen for more complex and/or problematic cases) and will be conducted during the hours of 9:00 AM to 5:00 PM eastern time (ET), Monday-Friday, excluding federal holidays and government closures. The Contractor is responsible for scheduling all case kick-off meetings. Case kick-off meetings must be scheduled within one business day from the date of request and may be conducted remotely.

In performance of this task, the Contractor must work closely with legal staff and CCSIG for planning and scheduling.

Deliverable 1: Case Processing Deliverables For all workspaces, the Contractor must deliver case processing deliverables, that include: 1) batch reports that include file listings, file extensions, and file sizes; 2) exception reports listing files that could not be processed; and 3) case processing plans and schedules. Case processing deliverables must be delivered to OCC 3 business days after the completion of case processing.

Deliverable 2: Case Production Deliverables As requested by the Government, the Contractor must deliver case production deliverables, that include: 1) production document sets and accompanying load files (e.g., DAT files); and 2) any privilege log or similar reports as requested by the end-user. Productions 200 GB or smaller must be delivered within 24 hours from request. If size of production exceeds 200 GB, contractor is allotted 24 hours per 200 GB. (E.G., If a production is 500 GB in size, Contractor must complete the production in no more than 72 hours from request.)

1.2.3 Task 3 Perform Maintenance and Provide Operational Support The Contractor must assist RelativityOne Government users in the resolution of issues. Operational support must include, at a minimum:

Providing feedback to COR regarding upcoming patches and updates to RelativityOne Government and any impact to workspaces and end user experience;

Troubleshooting and resolving operational problems, including performance problems;

Monitoring system performance;

Performing system administration tasks, including the administration of users, system configuration, and the administration of security;

Developing new interfaces;

Maintaining existing interfaces;

Notifying the OCC at least five days in advance of system outages for maintenance or other operational activities.

Supporting and providing data for security and compliance activities, including audits and activities related to continuous authorization;

Producing and reviewing audit logs;

Developing operational reports to assist users; and Updating the Maintenance and Operational Support Deliverables listed in Deliverable 3.

Metadata is electronically stored information that describes the history, tracking, or management of an electronic document. Metadata is created automatically when a user creates, modifies, accesses, or takes other actions with respect to an electronic document. The Contractor must ensure data preservation requirements related to review cases are met. The Contractor must also ensure that metadata associated with review cases are preserved.

The Contractor must provide immediate access to all government data, and government-related data impacting government data, for review, scan, or forensic evaluation, and physical access to any contractor facility with government data.

Deliverable 3: Maintenance and Operational Support Deliverables. The Contractor must deliver Maintenance and Operational Support Deliverables that include audit logs and reports. Maintenance and Support Deliverables must be delivered on the 1st business day of every month.

1.2.4 Task 4 Provide (RelativityOne Government) Technical Support Tier-1 Support for OCC Systems is provided via telephone and online support by the OCC’s GetHelp help desk. The Contractor must provide tier-2 technical support to users of RelativityOne Government and its add-on Legal Hold tool, including:

Resolving incidents[footnoteRef:3], outages, degradations, and other problems, which may involve working with Relativity, the OCC’s tier-1 helpdesk, OCC users, and teams that support systems integrated with RelativityOne Government and RelativityOne Government Legal Hold, and other groups within ITS; [3: An ‘incident’ is defined as an unplanned interruption to or reduction in the quality of an IT service. Failure of a configuration item that has not yet impacted service is also an incident. An ‘outage’ is a complete disruption or interruption of an IT service or application. A ‘degradation’ is a decline in normal IT service or application service level which does not entirely disrupt or interrupt the service or application.]

Properly documenting incidents, including resolutions, in ServiceNow;

Answering questions from users;

Providing desk-side support to users, either in-person or remotely;

Writing customer-facing and ITS-internal knowledge base articles (KBA);

Fulfilling service requests[footnoteRef:4] from the ServiceNow service catalog; [4: A service (or catalog) request is a user request for information or advice, for a standard change (a pre-approved change that is low risk, relatively common and follows a procedure), or for access to an IT service.]

Escalating problems to Relativity and managing them through to resolution; and Work with tier-1 support contractors as appropriate to help them understand the functionality of RelativityOne Government (in the areas specifically stated in this requirements document) The Contractor must provide technical support from 7:00 AM to 7:00 PM ET on weekdays, excluding federal holidays. The Contractor must use the OCC’s ServiceNow incident management system to track and manage technical support requests. The Contractor must monitor one or more ServiceNow support queues for incidents escalated from tier-1 support. Note that incidents are prioritized according to the Incident Priority Process, which is included in Attachment B Incident Priority Process.

The Contractor must develop KBAs on various topics, including solutions to user problems and questions. The OCC estimates that fifteen new KBAs per year will be needed. The OCC COR may direct the Contractor to develop KBAs on specific topics. The Contractor must receive approval from the COR before developing any contractor-initiated KBAs. KBAs may be customer-facing or ITS-internal. Customer-facing KBAs are intended for use by end-users. ITS-facing KBAs are intended for use by ITS, including tier-1 support and technical teams. The Contractor must review and update existing KBAs at least annually or as requested by the COR. The Contractor must use the OCC’s ServiceNow Knowledge Base template to develop KBAs. All new KBAs and updates to existing KBAs must be completed no more than 10 business days after request from the COR.

The Contractor must prepare the OCC’s tier-1 support contractor to support operation of RelativityOne Government and its add-on tool RelativityOne Government Legal Hold. This must include meeting with members of the tier-1 support team to review KBAs, providing an overview of RelativityOne Government and its add-on tool RelativityOne Government Legal Hold, and familiarizing the team with tier-2 support queues for RelativityOne Government Review and Legal Hold.

The following service levels apply to providing technical support:

Time to Acknowledge an Incident The time to acknowledge an incident is the time from when an incident enters the ServiceNow queue to the time when the Contractor assigns it to an individual to resolve. The Contractor must acknowledge service requests within two business hours.

Mean Time to Resolution for Incidents The time to resolution for an incident is the time from when an incident enters the ServiceNow queue to the time the issue is resolved, and the ticket is closed. The Mean Time to Resolution (MTTR) is the average time to resolution (as measured each 30 resolved incidences). The MTTR must be less than or equal to 16 business hours. If an incident is system related and outside of the Contractor’s control, the Contractor will serve as a liaison between the user and Relativity support. Time expended after an incident is entered in the ServiceNow queue that is outside of the Contractor’s control will not be included in any MTTR calculation (e.g., time spent for COR to respond to Contractor; time spent for Relativity to resolve a system issue). The COR will monitor this service level every month by reviewing the Monthly Catalog Task Report from ServiceNow.

Time to Acknowledge a Service Request The time to acknowledge service request is the time from when a service request enters the ServiceNow queue to the time when the Contractor assigns it to an individual to fulfill. The Contractor must acknowledge at least 90 percent of service requests within four business hours (See Hours Below). The COR will monitor this service level every month by reviewing the Monthly Incident Report from ServiceNow.

Mean Time to Fulfillment for Service Requests The time to fulfillment for a service request is the time from when a service request enters the ServiceNow queue to the time the service request is complete, and the ticket is closed. The Mean Time to Fulfillment (MTTF) is the average time to fulfilment over a specified time period (e.g., day, month, year). The Contractor must act as a liaison between OCC staff and Relativity Support to resolve service requests. The Contractor must ensure the MTTF is less than or equal to 24 business hours (excepting cases of force majeure). The COR will monitor this service level every month by reviewing the Monthly Catalog Task Report from ServiceNow.

For the purpose of calculating service levels, business hours are from 7:00 AM to 7:00 PM ET on weekdays, excluding federal holidays.

Deliverable 4: Knowledge Base Articles The Contractor must deliver KBAs as described above. The Contractor must draft a new KBA no more than 10 business days after request from COR. The Contractor must update existing KBAs no more than 10 business days after request from COR. The Contractor must review all KBAs annually to determine if updates are required. The Contractor must provide notice to the OCC no later than 10 business days prior to the end of every 12-month period on whether updates are required. If Contractor determines KBA updates are required, the Contractor must complete all updates no later than 10 business days after completing their review.

1.2.5 Task 5 Implement Quality Control Processes

The Contractor must develop a Quality Control Plan (QCP) and implement quality control processes for work performed. The QCP must describe the quality control processes (including any audits) for every stage of the EDRM covered by the contract. For example, during the production step, the Contractor must provide a quality control process to allow the OCC to validate the data was produced in conformance with the OCC’s production request. See the section titled Methods of Quality Assurance Surveillance for additional information on quality assurance.

Deliverable 5: Quality Control Plan The Contractor must deliver a Quality Control Plan as described above. The Contractor must deliver the Quality Control Plan no later than 30 calendar days after Contract Start.

1.2.6 Task 6 Export and Destroy OCC Data Upon Case Closure

Closed case data residing in the RelativityOne Government’s cloud environment must be returned by the Contractor to the OCC in a format that is suitable for archiving on OCC archival systems. Data will be exported from RelativityOne Government environment in raw format (natives, text, metadata, images, and load files). Return of case data must be on encrypted media provided by the Government. The OCC COR will inform the Contractor, in writing, when a case is closed to require the case be archived by the Contractor. The Contractor must schedule the case to be completely removed from the RelativityOne Government’s system 30 calendar days after the archival is complete. Case removal must include the destruction of any copies, backups, and forensic images. Upon providing the archive-ready data to the OCC, the Contractor must provide a Certification of Data Return and Destruction, certifying that it has performed all steps required to remove and destroy data from RelativityOne Government pertaining to the given case – see Attachment C Certificate of Data Return and Destruction (Subject to supplemental changes). The Contractor must deliver certifications of data return and destruction no later than 5 business days after the Contractor has removed and destroyed case data.

Deliverable 6: Data Exports for Closed Cases Prior to the destruction of OCC data, the Contractor must return all data via data exports and provide necessary supporting documentation, as specified in this task.

Deliverable 7: Certifications of Data Return and Destruction The Contractor must deliver certifications of data return and destruction as specified in this task.

1.2.7 Task 7 Provide Project Management

The Contractor must provide project management to facilitate on-time, on-budget, and high-quality execution of all requirements. The Contractor must provide a Project Manager who must provide overall management of work under the contract and be the primary point of contact for all contract-related activities, tasks, deliverables, as well as technical and contractual matters.

The Contractor must use the SharePoint site in the OCC’s SharePoint Online production environment as a repository for contract deliverables and project-related documents.

In addition to the deliverables specified in this task, the Contractor must provide other artifacts typically produced as part of project and contract management, including (but not limited to) a project schedule, a list of personnel working on the contract, work-breakdown-structure (WBS), responsibility assignment matrix (RAM), completion reports for training, and signed non-disclosure agreements (NDAs).

Deliverable 8: Project Schedule The Contractor must deliver a project schedule that covers the full scope of work outlined. The Contractor must deliver the project schedule within 45 calendar days of the start of the contract. The project schedule will be created in the OCC’s instance of Microsoft Project Online. After initial delivery, the Contractor must maintain the project schedule by updating it on the first business day of every month. The project schedule must be fully resourced, and include tasks, milestones, and dependencies.

Deliverable 9: Weekly Status Report The Contractor must deliver a weekly status report throughout the performance period of the contract. The Contractor must deliver the weekly status report on the first business day of every week by 12:00 PM EST. The weekly status report must include:

A summary of progress for the week, including notable activities performed during the week;

A summary of work planned for the upcoming week;

Documentation of outstanding issues, including progress towards resolutions; and A risk register documenting risks, including risk probability, impact, and proposed mitigations

1.2.8 Task 8 (Optional Task) - Transition (Phase-Out) Data Migration Upon contract completion or termination, the OCC may require the Contractor to transfer all workspace and legal hold data in RelativityOne Government to another/new contractor and/or authorized government personnel. The Contractor must meet with the OCC designated official(s) and other authorized government personnel, as well as the new contractor, to finalize a transition (phase-out) plan. The plan must be delivered 90 days prior to the end of the contract. At a minimum, the transition plan must address the following topics, as appropriate:

Transition resource(s) and tool(s) needs;

Transition schedule;

Transition communications;

Data migration activities;

Transition of Key Personnel;

Schedules and milestones;

Government actions and/or assistance needed;

Testing of the data migration;

Quality assurance of the migrated data;

Technical support for the data migration;

Contingency planning;

Transition reporting;

Transition management controls; and Transition governance and approvals The Contractor must perform all transition (phase-out) services necessary to provide a smooth and efficient transition. During the transition, the Contractor must maintain services in accordance with contract requirements until formal transition is complete. The transition process will be dictated in part by the incoming service provider (contractor and/or the Government) transition period and the transition guidance provided by the OCC. The Contractor must also establish and maintain effective communication with the government personnel (and if applicable, incoming Contractor support) for the period of this transition (phase-out). All data must be provided to the OCC in a fully delimited format that can be imported into the new contractor’s system. Transition services must be provided over a period not to exceed 90 calendar days. The transition must be performed without any interruption or degradation in any services. The Contractor is required to provide OCC a certificate of completion report confirming the transition is complete.

Deliverable 10: Transition-Out Plan The Contractor must deliver a transition-out plan as described in this task. The transition-out plan must be delivered no later than 90 calendar days prior to the end of the contract.

Deliverable 11: Data Migration and Transition Certification The Contractor must deliver a certificate of completion upon migrated and transitioned task completed. The Contractor must deliver the data migration and transition certification no more than 5 business days after all data has been migrated and all services have been transitioned to successful awardee.

5.0 Deliverables

The OCC has identified the following deliverables. The Contractor must deliver all deliverables to the COR unless otherwise stated in Table 1 “List of Deliverables.”

Table 1 List of Deliverables

For new KBAs, 10 business days after a request from the COR.

Remove and destroy case data 30 calendar days after the OCC has confirmed receipt of exported case data.

6.0 Key Personnel

Personnel in the following roles are considered key personnel: Project Manager, Senior Litigation Support Coordinator, and Litigation Support Coordinator.

(a) Definition. "Personnel", when not otherwise qualified (e.g., government personnel, ITS personnel) means employees of the contractor, or any subcontractor(s), affiliates, joint venture partners, or team members, and consultants engaged by any of those entities.

(b) The personnel specified below are considered to be essential to the work being performed under the resulting contract.. Key personnel provided by the Contractor have the responsibilities described below and must meet the minimum qualifications stated below:

Project Manager The Project Manager (PjM) position is responsible for enabling and ensuring the successful completion of the requirements set forth in the contract focusing on planning, scheduling, reporting, and resource management of all projects associated with RelativityOne Government and additional right-side eDiscovery support tasks. Additionally, the PjM is responsible for ensuring quality deliverables, coordinating efforts across all work streams, requesting contract actions, providing monthly progress reports, cost controls, and schedule management. The following qualifications are associated with this key personnel position:

Required Minimum Qualifications Bachelor’s Degree from a regionally accredited university in a related field (e.g., business administration) A minimum of 6 years of experience as a project lead, responsible for the planning, coordination, and monitoring of project activities A minimum of 4 years, within the past 7 years, experience with managing eDiscovery system implementations

Project Management Professional (PMP) Certification is not required but is highly desired.

Senior Litigation Support Coordinator or Similar The Senior Litigation Support Coordinator (SLSC) position is responsible for enabling successful completion of the requirements set forth in the document focusing on left and right-side work, and providing technical and analytical assistance in the identification, collection, preservation, processing, review, and production of ESI. The SLSC is responsible for the oversight of the processing of data into the review tool, the creation of workspaces, end user review tool assistance, workspace customizations, and ESI productions. The SLSC will also provide technical and analytical assistance to the CCISG team on the use of the collection and litigation hold tools. The following qualifications are associated with this key personnel position:

Required Minimum Qualifications Bachelor’s Degree from a regionally accredited university in a related field (e.g., communications, English, etc.)

A minimum of 6 years, within the past 9 years of hands-on experience using eDiscovery solutions in an operational environment and providing technical and consulting support as a team lead for eDiscovery solutions A minimum of 3 years of hands-on experience with RelativityOne (commercial or government) Highly Desired Qualities (not required) Previous experience collecting data from laptops, network file shares, commercial applications, and custom-developed applications Have experience implementing eDiscovery software within a government agency Litigation Support Coordinator or Similar The Litigation Support Coordinator (LSC) position is responsible for enabling successful completion of the requirements set forth in the document focusing on left and right-side work and providing technical and analytical assistance. The LSC is responsible for the processing of data into the review tool, the creation of workspaces, end user review tool assistance, workspace customizations, and ESI productions. The LSC will also provide technical and analytical assistance to the CCISG team on the use of the collection and litigation hold tools. The following qualifications are associated with this key personnel position:

Required Minimum Qualifications A minimum of 4 years, within the past 7 years of professional experience in eDiscovery related employment A minimum of 2 years of professional experience using RelativityOne (commercial or government).

A minimum of 2 years using one or more of the tools for legal holds, identification, collection, processing, or review tools in this requirements document A bachelor’s degree from a regional accredited institution is not required but highly desired.

7.0 Methods of Quality Assurance Surveillance

7.1 Quality Control Plan

The Contractor must use a quality control plan (QCP) covering all tasks and deliverables identified for the resulting contract. The Contractor must develop, implement, and maintain an effective QCP to ensure services are performed in accordance with the Government’s requirements. The Contractor must develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. Upon review and approval by the OCC COR, the Contractor must operate under the QCP. The QCP must promote excellence in all functional areas of the contract, noting the specifics of the QCP may be changed periodically to ensure successful performance of this contract. Upon any proposed changes must be approved by the OCC COR.

7.2 Quality Assurance

The OCC COR will review the Contractor’s performance under the contract award in accordance with the QASP. This plan is primarily focused on what the OCC will do to ensure that the Contractor has performed in accordance with the performance standards established and on the methods used for inspection and acceptance of Contractor’s performance. It defines how the performance standards will be applied, what methods will be used to perform assessment of Contractor’s performance, the frequency of surveillance, and the minimum acceptable defect measures. For the avoidance of doubt, though the QASP provides a general guideline for surveillance of critical performance, all contract requirements are binding and enforceable regardless of their inclusion in the QASP. Similarly, characterization of the performance of any requirement is reportable in government past performance reporting systems regardless of their inclusion in the QASP.

7.3 Quality Assurance Surveillance Plan

The OCC intends to use a QASP to monitor the quality of the Contractor’s performance. The QASP will aid in ensuring that service levels reach and maintain the required levels throughout the contract term. Further, the QASP provides the COR with a proactive way to avoid unacceptable or deficient performance and provides verifiable input for the required Past Performance Information Assessment(s). The QASP will be finalized after acceptance of the Contractor’s Quality Control Plan by the COR. The QASP is a living document; it will not be incorporated into the resulting contract award as it may be updated by the OCC as necessary. The Government must have the unilateral right to change the contents of the QASP given 30 days’ notice to the Contractor.

The OCC will use the QASP as internal guidance for determining how to monitor the Contractor’s compliance with the contract’s terms and conditions, and for identifying non-conforming services to determine appropriate action. This plan sets forth the method and manner by which the OCC intends to conduct surveillance of work under per the LSS requirements. All work required under the resulting contract is subject to surveillance, whether specifically included in the plan or not, in effort of meeting successful project completion.

8.0 Section 508 Requirements

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use information and communication technology (ICT), it must be accessible to people with disabilities. Federal employees and members of the public who have disabilities must have access to, and use of, information and data that is comparable to people without disabilities. As such, the following requirements apply to this solicitation:

1) Products, platforms and services delivered as part of this work statement that are ICT, or contain ICT, must conform to the Revised 508 Standards, which are located at 36 C.F.R. § 1194.1 & Apps. A, C & D, and available at https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines.

2) E102 / 702.10 – Web Content Accessibility Guidelines (WCAG) 2.0 guidelines success criteria level A & AA are incorporated as a requirement. The referenced WCAG criteria is available at http://www.w3.org/TR/WCAG20/.

3) A completed Accessibility Conformance Report (ACR) found at https://www.itic.org/policy/accessibility/vpat, using Voluntary Product Accessibility Template (VPAT) Revised Section 508 Edition, Version 2.5, is required to assist the Government in determining that the ICT products or services support Section 508 accessibility standards.

4) E202 – General Exceptions Authorized by OCC as applicable.

The following items are identified as containing ICT:

Applicable Functional Performance Criteria: All functional performance criteria apply when using an alternative design or technology that achieves substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4-6 of the Revised 508 Standards, or when Chapters 4-6 do not address one or more functions of ICT.

Applicable requirements for electronic documents and/or support services:

9.0 Security and Privacy Requirements

A. Compliance with Applicable Laws, Regulations, and Standards

Federal Laws. The contractor and all of its respective subcontractors must follow and remain compliant at all times with the Federal Acquisition Regulation (FAR), Privacy Act of 1974 (5 U.S.C. 552a - the Act), Federal Information Security Modernization Act of 2014 (Public Law 107-347) (FISMA).

FIPS. The contractor and all of its respective subcontractors must follow Federal Information Processing Standards (FIPS), National Institute of Standards and Technology (NIST) standards and guidelines, and other laws, mandates, or executive orders pertaining to the protection of sensitive information and information systems.

OCC Policies and Procedures. The OCC understands that there are limitations in applying agency-specific policies to systems and environments shared with other organizations or customers. The requirements in this OCC Policies and Procedures subsection applies to all activities specifically performed for the OCC by the contractor (e.g., professional services to develop or customize a component for the OCC). The intent of this section is to require contractor compliance with OCC policies and procedures for those activities, tasks, and deliverables specifically and uniquely performed and/or completed for the OCC by the contractor that is not a typical service or component of the existing contractor system/solution. This section also applies to contractors with access and use of OCC information resources (i.e., OCC network, systems, laptops, other IT equipment, and/or OCC information).

The contractor and all of its respective subcontractors must comply with all Office of the Comptroller of the Currency (OCC) security and privacy policies and standards in effect at the time of the award of the contract, as well as those requirements that may be added during the contract.

The contractor/service provider must conform to OCC administrative regulations, policies, and procedures, as listed in section 9 Security and Privacy Requirements, in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The contractor must work with OCC internal organizations, as needed, to ensure that policies, procedures, configuration control, and product life-cycle requirements are fulfilled to the satisfaction of OCC ITS.

B. General Requirements

Location. Information collected, used, stored, maintained, or otherwise processed by the contractor in the performance of this contract must be accessed, transferred, stored or processed only within the United States. In addition, the maintenance and support operations of the contractor's technology and information must take place, and originate from, within the United States.

Authorization to Use, Store, or Share Sensitive Information. The contractor must be responsible for properly protecting all information used, gathered, or developed as a result of work under this contract. The contractor must also protect all government data, equipment, etc. by treating the information as sensitive. All information gathered or created under this contract must be considered as Controlled but Unclassified (CUI) information. It is anticipated that this information will be gathered, created, and stored within the primary work location. If contractor personnel must remove any information from the primary work area, they must protect it to the same extent they would their proprietary data and/or company trade secrets.

Confidentiality. The contractor agrees to assume responsibility for protecting the confidentiality of government records and data associated with this contract, which are not public information.

Non-Disclosure Agreement. Each individual who has access to sensitive OCC data and/or the OCC network, systems, applications, laptops, or other OCC information resources that may process, store or transmit sensitive OCC data under this contract must execute a NDA (Attachment H) before being allowed such access.

Deliverables. The deliverables in this…