XXXXXXXX XXXXXXXX

CW52081 – E-Citation System

2

SECTION B: CONTRACT TYPE, SUPPLIES OR SERVICES AND PRICE/COST

B.1 The Office of Contracting and Procurement, on behalf of the Metropolitan Police

Department (MPD) (“the District”) is awarding Gtechna USA Corporation (“the Contractor”) to implement a ticket issuance system, and integrate the database with other government applications connected to the enforcement activities of the police department. The MPD solution will be hosted on the PEMA cloud infrastructures.

B.2 The District awards a firmed fixed contract type in accordance with 27 DCMR

Chapter 24. B.3 AGGREGATE GROUP OR INDIVIDUAL ITEM

Award, if made, will be to a single bidder in the aggregate for those groups of items indicated by “Aggregate Award Group” herein. Bidder must quote unit prices on each item within each group to receive consideration. Award, if made, on all other items will be on an individual item basis.

B.4 PRICE SCHEDULE – FIRM FIXED PRICE

B.4.1 BASE PERIOD

Item No. Description Total Cost 0001 Phase 1: Task 1 – Project Planning and Kickoff Meeting $238,000.00

0002 Phase 1: Task 2 – Business Requirement/Process Analysis

$0.00

0003 Phase 1: Task 3 – Customized Applications to Satisfy District-specific Requirements

$0.00

0004 Phase 1: Task 4 – Data Conversion Analysis $0.00

0005 Phase 1: Task 5 – Install and Setup Software, Hardware, Mobile Units and Printers

$246,973.00

0006 Phase 1: Task 6 – Reporting Module $0.00 0007 Phase 1: Task 7 – Interfaces to External Applications $14,985.00 0008 Phase 1: Task 8 – Quality Control and Testing $0.00 0009 Phase 1: Task 9 – Training $0.00

0010 Phase 1: Task 10 – Application and Support Documentation

$0.00

0011 Phase 1: Task 11 – Software and Hardware Warranties, and Product Support

$0.00

0012 Phase 1: Task 12 – Production System Deployment $0.00 0013 Phase 1: Task 13 – Full Operational Support $0.00

0014 Phase 1: Task 14 – Quality Assurance & Status Reporting

$0.00

0015 Phase 1: Task 15 – Application and Network Security $0.00 Grand Total for 4.1 (Base Period) $499,958.00

CW52081 – E-Citation System

3

B.4.2 OPTION YEAR ONE

Item No. Description Total Cost

1001 Phase 2: Task 16 – Install and Setup Software, Hardware, Mobile Units and Printers

$448,248.00

1002 Phase 2: Task 17 – Data Conversion $15,800.00 1003 Phase 2: Task 18 – System Enhancements $25,150.00 1004 Phase 2: Task 19 – Full Operational Support $0.00 1005 Maintenance and Support $85,300.00

Grand Total for 4.2 (Option Year One) $574,498.00

B.4.3 OPTION YEAR TWO

Item No. Description Total Cost 2001 Maintenance and Support $182,547.00

Grand Total for 4.3 (Option Year Two) $182,547.00

B.4.4 OPTION YEAR THREE

Item No. Description Total Cost 3001 Maintenance and Support $185,633.91

Grand Total for 4.4 (Option Year Three) $185,633.91

B.4.5 OPTION YEAR FOUR

Item No. Description Total Cost 4001 Maintenance and Support $188,813.43

Grand Total for 4.5 (Option Year Four) $188,813.43

B.4.6 PRICE SCHEDULE SUMMARY

Item No. Period of Performance Total Price

0001 Base Period Item No. 0001-0015 $499,958.00

0002 Option Year One Item No. 1001-1005 $574,498.00

0003 Option Year Two Item No. 2001 $182,547.00

0004 Option Year Three Item No. 3001 $185,633.91

0005 Option Year Four Item No. 4001 $188,813.43

Grand Total for B.4 $1,631,450.34

4

Doc308925 – E-Citation System

SECTION C: SPECIFICATIONS/WORK STATEMENT C.1 SCOPE

a. The District of Columbia Office of Contracting and Procurement, on behalf of the Metropolitan Police Department (MPD) (“the District”) is seeking a contractor to implement a web-based ticket management system that will enhance officers' ability to effectively and efficiently prepare and issue traffic Notices of Infraction through an application supported by smart phones issued to every officer who has a body-worn camera. The E-Citation System shall automate ticket preparation, both reducing processing time and improving accuracy.

b. The District’s goals involve the implementation of a new ticket issuance system with expanded field computing capabilities, efficient interfaces with internal and external systems; a robust back-office application with vigorous reporting capabilities and enhanced communications, and data flow between MPD, Department of Public Works (DPW), District Department of Transportation (DDOT), and Department of Motor Vehicles (DMV).

c. The E-Citation System shall be compatible with, and mirror the Officer Ticket Issuance System (OTI) currently utilized by both the District Government’s Department of Public Works (DPW) and Department of Transportation (DDOT). The implementation of the 1 City 1 Solution Initiatives will be implemented in two (2) phases.

C.2 APPLICABLE DOCUMENTS

Not Applicable

C.3 DEFINITIONS These terms when used in this contract have the following meanings:

C.3.1 General Enforcement/Mobile Ticket Issuance - Enforcement of the applicable regulations is based on a single observation resulting in an immediate ticket such as: parking in front of a hydrant, in a loading zone, or failing to stop for a stop sign. Whether walking or driving, all officers have the same level of ticket writing authority.

C.3.2 Command Center - Configure the Command Center server database and system parameters. The Main elements are System Data (core data), Import – Export (ImpEx) specifications, DPW Hosting, Customer Ticket Layout.

C.3.3 Mobile Units - Install and configure the Android Mobile Ticket application and options. The main elements are: The Ticket layout software, Ticket Layout Media and Customer e-ticket cycle test.

C.3.4 Deployment - Test the interfaces (Export Tickets to DMV, Import Wanted Plates from Homeland Security), deploy mobile test communication (SSL), connect printers, train officers and administrators and assist with GO LIVE.

5

Doc308925 – E-Citation System

C.3.5 Application Development Plan – a description of the customization and configuration that will

be necessary to meet the application requirements, programming tools and methods that will be used to perform the customization and configuration. The schedule to complete the application development should relate to the overall project plan as depicted in the Gantt chart.

C.3.6 Integration Test Plan – a description of the system integration tasks that will be necessary to meet the application requirements. Data and instructions to be exchanged, frequency of exchange, tools, and methods shall be specified.

C.3.7 Software Test Plan – a plan for verifying the proper installation and operation of the software. The Contractor shall test all functions. A testing environment shall be identified by MPD thirty days after the award date. A checklist of functions and their expected results shall be included in the test plan.

C.3.8 User Acceptance Test Plan – A period of at least 4 weeks’ time will be allotted for users to operate the system after initial installation for testing purposes. The Contractor shall provide a user acceptance test plan and the users will conduct stress tests of the applications functionality in order to discover bugs in the system for resolution. The users will document the testing results and submit them back to the Contractor after the testing period is over. The application will not be considered accepted until all bug fixes are completed or as agreed upon by DPW/PEMA management.

C.3.9 Database Conversion Plan – Through the Needs Assessment task data held in database structures that are being replaced will be evaluated to determine what must be converted and saved in the new system database after MPDs approval. A conversion plan will be developed that will include existing data table and field configurations, new data tables and field configurations, and how the existing data will be copied into the new configuration to allow continued access to historic ticket data through the new system interface. The Contractor shall provide a documented method for verifying that the data conversions are successful. The verification method should include MPD personnel as user acceptance testing (UAT) for data verification.

C.3.10 Business Continuity Plan – Essential business process requirements that were supported by the existing system will need to be supported by the new system. The Business Continuity Plan shall identify the essential processes and interfaces and how those processes shall continue to be supported by the new system.

C.3.11 Security Plan – The new system will have functions designed to keep data secure. Those functions and the procedures that will be required to properly apply them will be specified through the Security Plan. All data in transit is secured through HTTPS (HTTP over TLS) end points.

HTTPS is enforced using the following • RSA 2048 asymmetric encryption • TLS1.1+ TLS1.1+ Ciphers: • EECDH+AESGCM • EDH+AESGCM

6

Doc308925 – E-Citation System

• AES256+EECDH • AES256+EDH

In addition “Salt Password Hashing” is used to keep all passwords secure. A Random salt value which is the same size as the output HASH function is used. SHA2 is used for the hashing function.

C.3.12 Disaster Recovery Plan – To plan for situations where the database could be destroyed or

corrupted, or the network is unobtainable, a Disaster Recovery Plan will be submitted, detailing methods for providing redundancy, recommendations for storage of backed up data, including back- up methods, frequency, media, and the reinstallation of the database.

C.3.13 Transition Plan – A plan to transition the system over to MPD, OCTO and the new contract vendor prior to contract expiration. The plan shall include: a) minimize risk b) Testing and acceptance methodologies for system transition c) Establish proper controls for a smooth transition with incoming vendor d) Transition schedule with milestones and deliverables

C.3.14 Unit Testing - The Contractor shall stress the most discrete decision processes of the software

program to determine if the actual code structure is correct, the code function as designed, and the test demonstrates the system operate as attended during periods of extremely high demand.

C.3.15 Integration Testing - The Contractor shall conduct integration testing to verify the integration of

the various modules in the application and test external interfaces that will interact with the system and the stakeholder agencies systems.

C.3.16 UAT Testing - The Contractor shall administer user acceptance testing. User acceptance testing

shall be conducted by the end users and shall verify that the application will produce the desired results. This testing will cover from initial input to final output. These tests, via scripted scenarios, will demonstrate the suitability of the customized application to business processes from inception to conclusion, including but not limited to, both automated and manual procedures.

C.3.17 Independent Verification and Validation (IV & V) - The Contractor shall support IV&V

testing performed by an independent entity. Like UAT testing, these tests shall verify that the application will produce the expected outcomes. This testing shall be an end-to-end test covering all processed from initial input to final output. They shall consist of validation of data conversion and integrity, and system performance.

The IV &V tests shall certify that the application is ready for UAT and IV&V. Test Incident Reports (TIRs) will be used to document instances when the application does not perform as expected. The Contractor shall review the TIRs and implement the appropriate solution. Once a solution has been implemented, the application will be retested until all tests produce satisfactory results. A successful completion of UAT and IV&V shall be preconditions for the Project Management Team’s decision to proceed with system deployment. If the Contractor is unable to satisfy these testing preconditions, the District shall provide notice to the Contractor that system deployment will not occur.

7

Doc308925 – E-Citation System

C.3.18 UAT and Frontline Employee Training for non-technical personnel – The Contractor shall assign a senior level trainer(s) to provide training for the UAT and Frontline Employees. The training shall be delivered prior to the scheduled testing activities and shall include end-user training.

C.3.19 “Super-user” training, (train the trainer) training - The Contractor shall provide a senior level

trainer(s) to conduct the training sessions for the personnel identified as super users. Training materials shall be provided to system administration personnel and the District shall have legal rights to said training materials and shall have access to these materials for training future users on the application.

C.3.20 System Administration /Developer Training – The Contractor shall provide system administration and developer training with designated technical staff.

C.4 BACKGROUND

a. MPD is located at 300 Indiana Avenue NW, Washington, DC 20001. MPD is a twenty-four (24) hour operation three hundred and sixty five (365) days a year and officers must have the ability to at issue citations all times. MPD employs officers that deliver various types of enforcement activities throughout various operations.

b. MPD currently issues tickets/ citations to the following: 1) motorists for violations of the laws

and regulations governing traffic movement in the District of Columbia; 2) vehicles parked in violation of laws and regulations governing the stopping, standing and parking of vehicles; 3) bicyclists for violations of the laws and regulations regarding the operation of bicycles; and 4) pedestrians that violate the laws and regulations regarding the movement of pedestrians in the District of Columbia.

c. Currently MPD uses the Mobile Enforcement System, PocketPEO system. The data captured

and stored in the PocketPEO system is transmitted to the DMV eTIMS database on a daily basis. PocketPEO resides on the vendor network located in Tarrytown, NJ, and at cradle, data is transmitted in near real-time to Tarrytown.

C.5 REQUIREMENTS C.5.1 Phase 1 implementation shall include the command center, mobile units, and deployment.

C.5.2 Phase 1 of the project shall consist of the following tasks:

Task 1 - Project Planning and Kickoff Meeting Task 2 - Business Requirement/Process Analysis Task 3 - Customize Applications to Satisfy District-specific Requirements Task 4 - Data Conversion Analysis Task 5 - Install and Setup Software, Hardware, Mobile Units and Printers Task 6 - Reporting Module Task 7 - Interfaces to External Applications Task 8 - Quality Control and Testing Task 9 - Training Task 10 - Application Support Documentation Task 11 - Software and Hardware Warranties, and Product Support

8

Doc308925 – E-Citation System

Task 12 - Production System Deployment Task 13 - Full Operational Support (Phase 1) Task 14 – Quality Assurance & Status Reporting Task 15 – Application and Network Security

C.5.3 Phase 2 implementation shall include mobile units and deployment on additional units provided by MPD.

C.5.4 Phase 2 of the project shall consist of the following tasks: Task 16 – Install and Setup Software, Hardware, Mobile Units and Printers Task 17 – Data Conversion Task 18 – System Enhancements Task 19 – Full Operational Support (Phase 2)

C.5.5 Phase 1 - Task 1: Project Planning and Kickoff Meeting C.5.5.1 The Contractor shall conduct a project kickoff meeting to include attendees from MPD,

DPW, OCTO, DMV and DDOT. C.5.5.2 Prior to the kickoff meeting, MPD will provide to the Contractor documentation necessary for

the Contractor to complete the Needs Assessment Study and Plan. Documentation will include but is not limited to business requirements and processes; flow charts of current processes.

C.5.5.3 During the kickoff meeting, the Contractor shall submit a Project Management Plan and

Schedule using the standard Microsoft Project for all tasks. C.5.5.3.1 The Contractor shall include in the Project Management Plan a list of tasks and their

descriptions, along with a schedule illustrated through a Gantt chart to show task sequences, duration, dependencies and critical path risk.

C.5.5.4 The Contractor shall prepare, and present an orientation briefing during the kick-off meeting

to include project initiative, goals, scope, tasks, deliverables, and estimated schedule. C.5.5.5 Based on the outcome of the kick-off meeting, the Contractor shall make adjustments to the

Project Management Plan and Schedule as necessary to reflect any resulting changes in the Statement of Work.

C.5.5.6 The Contractor shall provide a detailed Implementation Plan including the following:

a) Application Development Plan b) Command Center Development Plan c) Integration Test Plan d) Software Test Plan e) User Acceptance Test Plan f) Database Conversion Plan g) Business Continuity Plan h) Security Plan i) Disaster Recovery Plan

9

Doc308925 – E-Citation System

j) Transition Plan C.5.5.7 The Contractor shall provide weekly project reports detailing a task by task percent

complete evaluation, any problems encountered and resolution. C.5.6 Phase 1 - Task 2: Conduct Business Requirements/Process Analysis C.5.6.1 The Contractor shall identify and confirm those business requirements and processes that

must be incorporated into the functionality of the ticket issuance system. In addition, the Contractor shall identify those operational business processes that MPD must utilize for maximum performance of the ticket issuance system and the business processes and procedures required for MPD to maximize efficient data flow and exchange with other District agency systems.

C.5.6.2 The Contractor shall gather and review information through documentation, through

observation and staff interviews. The information will be used to inform the Contractor during the process of configuring and customizing the system that is to be implemented.

C.5.6.3 The Contractor shall deliver documentation of the information gathering tasks to MPD to

verify that the information is correct prior to developing the Needs Assessment Plan. C.5.6.4 The Contractor shall develop and submit a list of all final documentation used to inform the

Contractor of business processes, existing database structure, existing interfaces and existing application functions for review. This shall include all documents, interview notes, images, and any other sources of information the Contractor uses. The documentation will be maintained by MPD for reference.

C.5.6.5 The Contractor shall conduct a Needs Assessment Study focused on the needs related to

meeting the system requirements. The Contractor shall document the results of The Needs Assessment Study in a report – The Needs Assessment Plan - to include a summary of business processes identified above that involves the use of the new system, identification of new business processes that will need to be established, identification of system interfaces that will be required to be developed and the data transfer process that will be necessary.

C.5.6.6 The Needs Assessment Study shall address the business processes, the application functions

that will facilitate those business processes, the hardware, software and network components that will be needed to properly implement the system, and training and support needed for staff and equipment.

C.5.6.7 The Contractor shall develop before and after Business Process and Flow Models. The

existing business process impacts and identification of new business processes will be depicted through flow chart models as well as through the descriptions included in the Needs Assessment Plan.

C.5.6.8 The Contractor shall recommend industry best practices in police officer enforcement and

include the recommendations in the needs assessment document. C.5.7 Phase 1 - Task 3: Customize Application and Command Center to Satisfy MPD-specific

Requirements

10

Doc308925 – E-Citation System

C.5.7.1 The Contractor shall customize the Gtechna Officer Suite (GOS) including the Mobile Ticket Application and Command Center based on the unique District business requirements identified in Task 2.

C.5.7.2 The GOS Command Center and Officer Mobile ticket application provided by the Contractor shall have the following capabilities:

a) Process traffic citations capturing comparable information as the current system for the

purpose of issuing a traffic citation to a vehicle operator or owner; b) The ability to scan 2D barcodes from driver permits and vehicle registrations for DC,

Maryland and Virginia if available; c) Capture officer wet or electronic signature on tickets; d) Possibility to capture up to 4 digital images and embed to OTI data record; e) Synchronize OTI data records to the command center in Real Time or End-of-Shift (EO)/

Start-of-Shift (SoS) modes via cellular connectivity or via MPD WiFi network; All data connections between the mobile devices to the backend application must be encrypted using a 256-bit encryption system or stronger

f) Heatmaps, Officer Live Map and Officer Activity Tracker Safety Awareness module; g) Export OTI data records to a shared SFTP of the District. DMV (eTIMS) is responsible

for retrieving this file and importing into the ticket processing database for payment and adjudication processing;

h) Import the Plate-Under-Investigation files at least twice daily using a predetermined file naming convention

i) Ticket media stock for 100,000 tickets. Stock should be 3” x 7” poly thermal non-tear 2 color. Final ticket length shall be determined once ticket layout is approved by MPD.

C.5.7.3 The Contractor shall install the MPD Command Center on DPW’s Officer Command Center infrastructure utilizing the multi-org configuration or new installation of the Officer Command Center on the same infrastructure

C.5.7.4 The Contractor shall grant Technical support staff administrative rights, supervisory staff

some administrative rights for entering users and assigning roles, and general users, who are responsible for ticket and related form creation, will not be granted administrative rights.

C.5.8 Phase 1 - Task 4: Data Conversion Analysis C.5.8.1 The Contractor shall provide analysis of the programming required to convert the existing

enforcement database records from the existing applications currently in-use by MPD including data from eTIMS to the new application database.

C.5.9 Phase 1 - Task 5: Install and Set Up Software, Hardware, Mobile Units and Printers C.5.9.1 The Contractor shall install and set up the violations tables in the software by building off

information obtained in Task 2 and entering data based on enforcement and other related practices, user roles, security, and other organizational data required by the system.

C.5.9.2 The Contractor shall provide mobile applications that must be able to operate within the District Government’s Air Watch Mobile Device Management (MDM) solution.

11

Doc308925 – E-Citation System

C.5.9.3 The GOS software and hardware provided by the Contractor shall meet the following network, application and data standards:

Network: 1. Must be able to communicate on an IPv4 and IPv6 network 2. Ports and protocols must be explicitly identified for exception through

network segmentation firewalls Application: 1. Must be able to run on Windows 10 w/ McAfee Anti-virus and ePolicy

Orchestrator (ePO) agent 2. Must be able to pass an application vulnerability scan prior to going live (recommend

at least 30 days prior to scheduled go-live date to remediate any findings) Data: 1. If the data is government sensitive or privacy data (e.g., PII, PHI, CJIS, etc.), then

all data must be encrypted at rest (full disk encryption and/or database encryption) and in transit (HTTPS, SSH, IPSec, etc.).

C.5.9.4 The Contractor shall establish a separate development, test and production environment for

all work required and future system enhancements. MPD and OCTO will work with Contractor to establish the list environments on the District network.

C.5.9.5 The Contractor shall deploy and configure the Officer Mobile ticket application (Mobile Unit

in definition section) on 500 Android devices provided by MPD. C.5.9.6 The Contractor shall purchase, configure and pair the Officer Mobile Ticket Application to

200 3” printers that comply with the specifications provided by MPD. There shall be a 1 year warranty from the Go Live date on the printers. The Contractor shall be responsible for maintenance and repair of printers consistent with section C.5.17.

C.5.9.7 The Contractor shall confirm the citations printed on 3” printer meet current 4” print form

specifications. C.5.10 Phase 1 - Task 6: Develop Reporting Module C.5.10.1 The Contractor shall configure a reporting module. The reporting module shall allow MPD

users to generate reports using various parameters.

C.5.10.2 The report module shall have the capability to generate daily, weekly and monthly reports on the various enforcement operations and other statistical related reports. The Contractor shall transport the existing reports from the PocketPEO systems to the new reports module.

C.5.10.3 The Contractor shall be required to adhere to the industry software standards for providing a

web-based report writing tool. C.5.10.4 The GOS provided by the Contractor shall have a reports module with the capability to

create ad-hoc reporting that will allow MPD to produce on-demand reports for all operational activity. The reports module shall allow users to choose all data elements/parameters to run reports, such as but not limited to: start date and end date; officer- id (name, beat, badge #, login-id), ticket #, location.

12

Doc308925 – E-Citation System

C.5.10.5 The GOS provided by the Contractor shall allow users the capability to save a report in a variety of formats such as but not limited to: PDF, EXCEL, WORD, CSV and Graph Charts. The GOS shall allow users to select the saved file format from the Reports tool bar menu.

C.5.10.6 The Contractor shall configure the GOS to only grant access to authorized users via a login-

id; users shall have the ability to change their password. C.5.10.7 The GOS provided by the Contractor shall have the capability to perform an audit trail of all

activities and produce a report. The audit trail shall include such information as but not limited to: authentication activities; transaction date and times, user-id, transaction add, delete and modify; system errors, and notifications.

C.5.10.8 The GOS provided by the Contractor shall allow for the printing of an audit history based on selected fields.

C.5.10.9 The GOS provided by the Contractor shall allow users the capability to sort reports by selected columns both in ascending and descending order.

C.5.11 Phase 1 - Task 7: Build Interfaces to External Applications C.5.11.1 The Contractor shall identify and construct system interfaces to external software

applications as defined in Task 2. This involves analyzing the interface requirements, working with other agencies and District contractors.

C.5.11.2 The Contractor shall work with the MPD, DPW, DMV, DDOT and existing District

application vendor, Conduent, to construct the required interfaces; some of the interfaces are bi-directional and will require an Application Programming Interface (API) from both applications. The Contractor will enable an existing interface to the DMV, Conduent eTims application (ticket processor). The District is responsible for all potential costs that may incur with Conduent.

C.5.11.3 Where possible, the Contractor shall build interfaces using Extensible Markup Language

(XML) via asynchronous messaging in accordance with industry guidelines, in order to allow for easier adaptation and integration in the future. Interfaces shall be designed to comply with current software standards in place at DPW and DDOT.

C.5.12 Phase 1 - Task 8: Quality Control and Testing C.5.12.1 The Contractor shall demonstrate basic functionality of the GOS through system testing.

Immediately, upon approval of the requirements and the design document, the Contractor shall begin development of the Test Plan.

C.5.12.2 The Contractor shall consult with the MPD Project Management Team as to the test priorities and shall modify the Test Plan as needed to reflect the impact of any Change Orders as they occur.

C.5.12.3 The Contractor shall conduct all testing in accordance with the OCTO standard system testing policies and procedures and provide results. Testing shall include the following: a) Unit Testing b) Integration Testing

13

Doc308925 – E-Citation System

c) UAT Testing d) Independent Verification and Validation (IV & V)

C.5.12.4 The Contractor shall conduct all testing in accordance with the documented transition plan as defined in C.3.13. Results of testing shall be provided in writing.

C.5.13 Phase 1 - Task 9: Provide Training C.5.13.1 The Contractor shall provide a Training Plan within ninety (90) days from date of contract

award. The training plan shall define the approach for delivering in-person training for 75 functional and technical personnel during Phase 1 of the project.

C.5.13.2 The Contractor shall outline in the training plan the following types of training

a) UAT and Frontline Employee Training for Non-Technical Personnel b) Super-User Training (Train-the-Trainer) Training c) System Administration/Developer Training

C.5.13.3 The Contractor shall provide a senior level trainer(s) to develop custom training material, and

perform required classroom training. The training will be supported by training exercises and a training manual that will guide users step by step through the training exercises using screen shots and user-friendly descriptions to illustrate the steps. The training exercises will be supported through a training database that the Contractor shall use to perform the training.

C.5.13.4 The Contractor shall provide initial in-person training during phase 1 of the contract, as well

as supplemental training materials including but not limited to DVDs; on-line training; train the trainer manuals. The training manual shall be updated with any software modifications made to the system prior to implementation of the software modifications for training purposes.

C.5.13.5 The Contractor shall provide written documentation of each participant completing in-person training; the date the training was completed and type of training completed (Front Line Testing; Train-the-Training Testing; System Training).

C.5.13.6 The Contractor shall grant the District exclusive rights to training materials and modules

developed under this contract. The training materials and modules will become the sole property of the District Government to use at its own discretion. All delivered training materials shall be electronically delivered, and be web-enabled (in HTML format) and capable of being stored on MPD’s Intranet web site.

C.5.14 Phase 1 - Task 10: Provide Application Support Documentation C.5.14.1 The Contractor shall produce an Implementation Plan Document with associated plan

breakouts. C.5.14.2 The Contractor shall develop a Mobile Ticket Application and Command Center User

Manual. The Contractor shall document the application operations through a User Manual that uses screen shots and captions to explain the use of the application and command center functions to users. The manual shall be written to allow users without technical knowledge of the system to understand. The Contractor shall also provide a portable user quick reference

14

Doc308925 – E-Citation System

guide. C.5.14.3 The Contractor shall produce an Operation and Maintenance Guide. This guide shall include

more technical system documentation that explains database configuration, tuning, interface requirements, and dependencies on other systems shall be documented and procedures for common trouble shooting and problem diagnosis shall be included.

C.5.14.4 The Contractor shall provide a System Administration Documentation that provides the

appropriate system administration documentation for system interfaces, system security, hardware and software specifications, the database schema with definitions and defined table relationships.

C.5.14.5 The Contractor shall provide documentation for all patches, hot-fixes and updates that have

been applied to the system at the time of deployment. Each reiteration shall be indicated by a new version number representing the changes in the new release.

C.5.14.6 The Contractor shall produce all user manuals (Mobile Ticket Application and Command

Center User Manual; Operation and Maintenance Guide; System Administration Documentation; Other updates) and training materials in an acceptable format to be posted on the MPD intranet for widespread access to all users and MPD support staff. The Contractor shall provide a full, online User Manual with keyword search capability.

C.5.15 Phase 1 - Task 11: Document Software and Hardware Warranties, and Product

Support C.5.15.1 The Contractor shall provide a one-year warranty covering parts and labor for the hardware

and software from the Go Live Date.

C.5.15.2 The Contractor shall describe how software “bug fixes” are to be reported by customers, and how customers are kept informed regarding the status and expected resolution of the reported problem. This deliverable should also describe how “fixes”, maintenance and enhancements are to be distributed and probable frequencies.

C.5.15.3 Software “bugs” reported to the Contractor by MPD are to be fixed by the Contractor and

provided to MPD for testing within the guidelines of section C.5.17. C.5.15.4 The Contractor shall provide product support including but not limited to maintenance,

updates, upgrades and parts replacement shall be provided for the software and operating system installed on the handheld devices as detailed in section C.5.17

C.5.15.5 The Contractor shall provide a written description of how desired enhancements to the system

should be communicated and how the Contractor evaluates, prioritizes and decides how enhancements are released. Upgrades to the GOS shall be provided to the District as they are completed.

C.5.15.6 The Contractor shall provide, prior to testing upgrades, documentation describing the

change(s) to be tested, how to test, and instructions on how to deploy them once tested. C.5.16 Phase 1 - Task 12: Production System Deployment

15

Doc308925 – E-Citation System

C.5.16.1 After successful completion of UAT and Independent Verification & Validation testing, the project manager shall recommend to MPD a “Go Live” date. Once the Contractor receives notification that the District is prepared to “Go Live”, the Contractor shall establish a final deployment date in conjunction with the MPD.

C.5.16.2 The Contractor shall provide a deployment plan and a rollback plan in the event the system

deployment causes a point of failure. C.5.16.3 The Contractor shall facilitate deployment of the GOS. This will consist of the installation

and configuration of all application components on the database servers(s) in the District’s production environment. All data must be frozen and converted by the next business day after the deployment begins. The Contractor shall provide adequate onsite support during the “Go Live”.

C.5.16.4 After implementation, the Contractor shall provide guidance, support and technical assistance

on proper use of the application, as required. C.5.17 Phase 1 - Task 13: Provide Full Operational Support C.5.17.1 The Contractor shall provide the District help desk support as defined in the Gtechna Support

Service Agreement (SSA). The Contractor shall provide on-call and remote helpdesk services 24 hours a day, 7 days a week, to resolve all system software and hardware problems as defined in the SSA.

C.5.18 Phase 1 – Task 14: Quality Assurance and Status Reporting C.5.18.1 The Contractor shall provide a project manager to continuously monitor the status of the

Contractor’s work hereunder, provide quality control and update MPD on project status. This project manager shall also assure that the Contractor provides MPD management timely information regarding possible problems with project progress and proposed actions required to mitigate such problems. Project manager shall have the authority to make binding decisions on behalf of the Contractor.

C.5.18.2 The Contractor shall complete tasks, milestones and deliverables identified in the statement of

work, project plan and document progress in reports. C.5.18.3 The Contractor shall schedule bi-weekly status meetings (or on other schedules, as

appropriate) with MPD and other participating agency representatives. Project manager shall confer with MPD management when submitting bi-weekly reports or as otherwise requested.

C.5.18.4 The Contractor shall continuously communicate status of the work relative to the approved

schedule. The Contractor shall notify the Contract Administrator of any potential problems in meeting scheduled deliverable dates.

C.5.18.5 The Contractor shall prepare a bi-weekly status report. The report shall include a list of

accomplishments during the reporting period, including:

a) completed and work-in progress items, b) accomplishments planned for the next reporting period, c) issues requiring management attention, including notification of any potential

16

Doc308925 – E-Citation System

schedule slippage for deliverables and causes, as well as proposed corrective action. C.5.18.6 The Contractor shall prepare a monthly status report. The report shall include:

a) a summarization of the weekly status for the reporting period, b) an accounting of total costs to date.

C.5.18.7 All correspondence, conferences, meetings and questions concerning the project directed to

the Contractor shall be through the chief representative.

C.5.18.8 The Contractor’s chief representative shall be personally available at all times during working hours from the beginning of the work through its completion.

C.5.18.9 The Contractor shall provide project management, technical management, administrative management and administrative support necessary for the work hereunder.

C.5.18.10 The District may direct the Contractor to remove any Contractor staff that the District finds unacceptable; the Contractor shall immediately remove such personnel. The Contractor shall replace the removed staff position with new individual(s) satisfactory to the District. The Contractor shall handle any time lost based on a replacement to ensure the project is not adversely impacted.

C.5.19 Phase 1 – Task 15: Application and Network Security C.5.19.1 The Contractor shall demonstrate through written documentation and testing that the

command center and application have the follow security features: a) Alerts sent to the designated administrator if unauthorized users are trying to access the

system b) Secure (encrypted) communication between systems and through Internet to mobile

devices c) The ability of administrators to invoke password polices determined by MPD d) The ability of administrators to disable an account e) The ability of administrators to assign permissible access levels for users f) Block the ability of users that do not have the assigned rights to execute specific

transactions g) Security is customizable and flexible and user groups rights allow for real world

modeling of a user’s job function h) Provides a default or “template” security groups that can be copied or altered i) Allows users to be assigned to multiple group rights without having to reconfigure

groups j) Tracks the date, time, and sources of all entries and updates and schedules for

verification of entries and/ or automatic deletion of temporary information k) Supports active login to determine all uses on the system at all times

l) Provide a security configuration template for Supervisors to easily create, manage and maintain user accounts

m) Allows users to manage their own passwords changes via a forgotten password link by sending to an email address

C.5.19.2 The Contractor shall document in writing which devices (if any) are connected to the District

17

Doc308925 – E-Citation System

Government network and how they are adequately maintained and/ or secured to provide protection of information.

C.5.19.3 The Contractor shall provide written guidelines for the configuration, maintenance and use of

network to preserve the confidentiality and integrity of the network as well as the information transmitted over the network.

C.5.19.4 The Contractor shall provide a detailed topology or network diagram depicting how firewalls

are used to control basic network security control. C.5.19.5 The Contractor shall identify what encryption and integrity protection is in place for all

internal network traffic that potentially carries sensitive information (including passwords, emails, files, source code, management traffic, etc.)

C.5.20 Phase 2 – Task 16: Install and Set Up Software, Hardware, Mobile Units and Printers C.5.20.1 The Contractor shall provide mobile applications that must be able to operate within the

District Government’s Air Watch Mobile Device Management (MDM) solution. C.5.20.2 The GOS software and hardware provided by the Contractor shall meet the following

network, application and data standards: Network: 1. Must be able to communicate on an IPv4 and IPv6 network 2. Ports and protocols must be explicitly identified for exception through network

segmentation firewalls Application: 1. Must be able to run on Windows 10 w/ McAfee Anti-virus and ePolicy Orchestrator

(ePO) agent 2. Must be able to pass an application vulnerability scan prior to going live (recommend at

least 30 days prior to scheduled go-live date to remediate any findings) Data: 1. If the data is government sensitive or privacy data (e.g., PII, PHI, CJIS, etc.), then all data

must be encrypted at rest (full disk encryption and/or database encryption) and in transit (HTTPS, SSH, IPSec, etc.).

C.5.20.3 The Contractor shall deploy and configure the Officer Mobile ticket application (Mobile Unit

in definition section) on 500 Android devices provided by MPD. C.5.20.4 The Contractor shall purchase, configure and pair the Officer Mobile Ticket Application to

200 3” printers that comply with the specifications provided by MPD. There shall be a 1 year warranty on the printers. The Contractor shall be responsible for maintenance and repair of printers consistent with Equipment Repair section C.5.17.

C.5.20.5 The Contractor shall provide citations printed to 3” printer, meet current 4” print form

specifications.

18

Doc308925 – E-Citation System

C.5.21 Phase 2 - Task 17: Data Conversion C.5.21.1 Based upon the analysis required by section C.5.8.1, the Contractor shall provide the

programming to migrate data from the existing PocketPEO/ eTIMS to the OCC. C.5.22 Phase 2 - Task 18: System Enhancements C.5.22.1 The Contractor shall establish a separate development, test and production environment for

all work required and future system enhancements, as required. MPD and OCTO will work with the Contractor to establish the list environments on the District network.

C.5.22.2 The Contractor shall provide system enhancements to include testing, training and

maintenance services. C.5.22.3 The Contractor shall provide a cost breakdown of all cost reimbursement costs. C.5.23 Phase 2 - Task 19: Full Operational Support C.5.23.1 The Contractor shall provide the District help desk support as defined in section C.5.17. The

Contractor shall provide on-call and remote helpdesk services 24 hours a day, 7 days a week, to resolve all system software and hardware problems.

C.5.23.2 The Contractor shall provide support services in accordance with section C.5.17.

19

Doc308925 – E-Citation System

SECTION D: PACKAGING AND MARKING

D.1 The packaging and marking requirements for this contract shall be governed by clause number (2), Shipping Instructions-Consignment, of the Government of the District of Columbia's Standard Contract Provisions for use with Supplies and Services Contracts, dated July 2010. (Attachment J.1)

D.2 Ship To:

Attn: LaMont Hinton Metropolitan Police Department Automated Traffic Enforcement Unit 2850 New York Avenue, NE Washington, DC 20018 Telephone: 202-299-3918

20

Doc308925 – E-Citation System

SECTION E: INSPECTION AND ACCEPTANCE E.1 The inspection and acceptance requirements for this contract shall be governed by clause number

five (5) Inspection of Supplies AND clause number six (6), Inspection of Services of the Government of the District of Columbia's Standard Contract Provisions for use with Supplies and Services Contracts, dated July 2010. (Attachment J.1)

21

Doc308925 – E-Citation System

SECTION F: PERIOD OF PERFORMANCE AND DELIVERABLES

F.1 TERM OF CONTRACT

The term of the contract shall be from the date of award specified on the cover page of this contract through September 30, 2017.

F.2 OPTION TO EXTEND THE TERM OF THE CONTRACT

F.2.1 The District may extend the term of this contract for a period of four (4) one-year option

periods, or successive fractions thereof, by written notice to the Contractor before the expiration of the contract; provided that the District will give the Contractor preliminary written notice of its intent to extend at least thirty (30) days before the contract expires. The preliminary notice does not commit the District to an extension. The exercise of this option is subject to the availability of funds at the time of the exercise of this option. The Contractor may waive the thirty (30) day preliminary notice requirement by providing a written waiver to the Contracting Officer prior to expiration of the contract.

F.2.2 If the District exercises this option, the extended contract shall be considered to include this

option provision.

F.2.3 The price for the option period(s) shall be as specified in the Section B of the contract.

F.2.4 The total duration of this contract, including the exercise of any options under this clause, shall not exceed four (4) years and three (3) months.

F.3 DELIVERABLES

The Contractor shall perform the activities required to successfully complete the District’s requirements and submit each deliverable to the Contract Administrator identified in section G.9 in accordance with the following:

Item No. Deliverable Quantity

Format/ Method of Delivery Due Date

0001 Project Management Plan and Schedule (C.5.5.3) 1

Microsoft Project / email Kickoff Meeting

0002

Implementation Plan (C.5.5.6; C.5.14.1)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0003

Application Development Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0004

Command Center Development Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

22

Doc308925 – E-Citation System

Item No. Deliverable Quantity

Format/ Method of Delivery Due Date

0005

Integration Test Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0006

Software Test Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0007

User Acceptance Test Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0008

Database Conversion Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0009

Business Continuity Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0010

Security Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0011

Disaster Recovery Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0012

Transition Plan (C.5.5.6)

1

Excel Spreadsheet/ email

No later than 14 calendar days after Kickoff Meeting

0013 Weekly Project Reports (C.5.5.7) 1 Excel Spreadsheet/ email

On-going

0014

Documentation of Information Used to Develop Needs Assessment Plan (C.5.6.3)

1

Excel Spreadsheet/ email

No later than 30 calendar days after Kickoff Meeting

0015

List of Final Documents Used for Needs Assessment Study (C.5.6.4)

1

Excel Spreadsheet/ email

No later than 30 calendar days after Kickoff Meeting

0016

Needs Assessment Plan (C.5.6.5)

1

Excel Spreadsheet/ email

No later than 30 calendar days after Kickoff Meeting

0017

Before and After Business Process and Flow Models (C.5.6.7)

1

Flow Charts and Written Report

No Later than 30 calendar days after Kickoff Meeting

23

Doc308925 – E-Citation System

Item No. Deliverable Quantity

Format/ Method of Delivery Due Date

0018

3” Printers that comply with the specifications provided by MPD(C.5.9.6)

400 Total (200

per Phase

Mail

No later than 10 days before Go Live Date

0019

Training Plan (C.5.13.1; C.5.13.2)

1

Excel Spreadsheet/ email

No later than 90 calendar days from contract award

0020

Training Manual (C.5.13.3)

1

Power point including screen shots and user friendly

No later than 7 calendar days before the first in-person training

0021

Supplemental training materials (C.5.13.4)

1

DVD’s; Online; Train the trainer manual / email

No later than 30 calendar days after the completion of in- person training

0022 Written documentation of participants in person training (C.5.13.5)

1 Excel Spreadsheet/email

No later than 7 calendar days after the

0023

Mobile Ticket Application and Command Center User Manual; Quick Reference Guide (C.5.14.2; C.5.14.6)

1

Power point/ email/ PDF

No later than 7 calendar days before the first in-person training

0024

Operation and Maintenance Guide (C.5.14.3)

1

Power point / email/ PDF

No later than 7 calendar days from the Go Live Date

0025

System Administration Documentation (C.5.14.4)

1

Power point/ flow chart/ email

No later than 7 calendar days from the Go Live Date

0026 Documentation of patches, hot-fixes and updates (C.5.14.5)

1 Power point/ flow charts/

On-going

0027 Documentation of how to report software “bug fixes” (C.5.15.2)

1 Power point/ report/ email

On-going

0028 Document on how to requests upgrades to the system; Document upgrades

1 Power Point/ excel spreadsheet

On-going

0029 Testing Task Documentation (C.5.15.6) 1 Excel spreadsheet/

On-going

0030

Deployment and Rollback Plan (C.5.16.2)

1

Excel spreadsheet/ email

No later than 7 calendar days before Go Live date

0031 Bi-weekly status reports (C.5.18.6) 1 Excel spreadsheet/ email

On-going

0032 Monthly status reports (C.5.18.7)

1 Excel spreadsheet/ email

On-going

0033 Written documentation addressing security features (C.5.19.1)

1 Excel spreadsheet/ email

On-going

24

Doc308925 – E-Citation System

Item No. Deliverable Quantity

Format/ Method of Delivery Due Date

0034 List of devices which are connected to the District Government network

1 Excel spreadsheet/

On-going at least monthly

0035 Written Guidelines for configuring , maintenance and use of network

1 Excel spreadsheet/

On-going

0036

Detailed topology or network diagram depicting firewalls (C 5 19 4)

1

Topology or diagram

No later than 30 calendar days of the Kickoff Meeting

0037

Documentation of encryption and integrity protection (C.5.19.5)

1

Excel spreadsheet/ diagram/ email

No later than 30 calendar days of the Kickoff Meeting

0038

Documentation of testing results (C.5.12.4)

1

Excel spreadsheet/ email

No later than 7 calendar days before Go Live date

0039

Analysis of the programming required to convert existing enforcement Pocket PEO/ eTIMS database (C.5.8.1)

1

Word document/ Email

No later than 7 calendar days before Go Live date

F.3.1 The Contractor shall submit to the District, as a deliverable, the report described in section H.5.5 which is required by the 51% District Residents New Hires Requirements and First Source Employment Agreement. If the Contractor does not submit the report as part of the deliverables, the District shall not make final payment to the Contractor pursuant to section G.3.2.

25

Doc308925 – E-Citation System

SECTION G: CONTRACT ADMINISTRATION

G.1 INVOICE PAYMENT G.1.1 The District will make payments to the Contractor, upon the submission of proper invoices, at

the prices stipulated in this contract, for supplies delivered and accepted or services performed and accepted, less any discounts, allowances or adjustments provided for in this contract.

G.1.2 The District will pay the Contractor on or before the 30th day after receiving a proper invoice from the Contractor.

G.2 INVOICE SUBMITTAL

G.2.1 The Contractor shall submit proper invoices on a monthly basis or as otherwise specified in

Section G.4. Invoices shall be prepared in duplicate and submitted to the agency Chief Financial Officer with concurrent copies to the Contract Administrator (CA) specified in Section G.9 below. The address of the CFO is:

Metropolitan Police Department Office of the Controller/Agency CFO 300 Indiana Avenue, NW Rm 4106 Washington, DC 20001 Telephone: (202) 727-5298

G.2.2 To constitute a proper invoice, the Contractor shall submit the following information on the

invoice: G.2.2.1 Contractor’s name, federal tax ID and invoice date (date invoices as of the date of mailing or

transmittal); G.2.2.2 Contract number and invoice number;

G.2.2.3 Description, price, quantity and the date(s) that the supplies or services were delivered or

performed; G.2.2.4 Other supporting documentation or information, as required by the Contracting Officer;

G.2.2.5 Name, title, telephone number and complete mailing address of the responsible official to

whom payment is to be sent; G.2.2.6 Name, title, phone number of person preparing the invoice;

G.2.2.7 Name, title, phone number and mailing address of person (if different from the person

identified in G.2.2.6 above) to be notified in the event of a defective invoice; and G.2.2.8 Authorized signature.

26

Doc308925 – E-Citation System

G.3 FIRST SOURCE AGREEMENT REQUEST FOR FINAL PAYMENT G.3.1 For contracts subject to the 51% District Residents New Hires Requirements and First Source

Employment Agreement requirements, final request for payment must be accompanied by the report or a waiver of compliance discussed in section H.5.5.

G.3.2 The District shall not make final payment to the Contractor until the agency CFO has received

the CO’s final determination or approval of waiver of the Contractor’s compliance with 51% District Residents New Hires Requirements and First Source Employment Agreement requirements.

G.4 PAYMENT

G.4.1 PARTIAL PAYMENTS

Unless otherwise specified in this contract, payment will be made on partial deliveries of goods and services accepted by the District if:

a) The payment amount is due on the deliveries; or

b) The Contractor requests it and the amount due on the deliveries is in accordance with the

following:

"Payment will be made on completion and acceptance of each item for which the price is stated in the Schedule in Section B"; and

c) Presentation of a properly executed invoice.

G.5 ASSIGNMENT OF CONTRACT PAYMENTS

G.5.1 In accordance with 27 DCMR 3250, the Contractor may assign to a bank, trust company, or

other financing institution funds due or to become due as a result of the performance of this contract.

G.5.2 Any assignment shall cover all unpaid amounts payable under this contract, and shall not be

made to more than one party. G.5.3 Notwithstanding an assignment of contract payments, the Contractor, not the assignee, is

required to prepare invoices. Where such an assignment has been made, the original copy of the invoice must refer to the assignment and must show that payment of the invoice is to be made directly to the assignee as follows:

“Pursuant to the instrument of assignment dated , make payment of this invoice to (name and address of assignee).”

27

Doc308925 – E-Citation System

G.6 THE QUICK PAYMENT CLAUSE G.6.1 Interest Penalties to Contractors

G.6.1.1 The District will pay interest penalties on amounts due to the Contractor under the Quick

Payment Act, D.C. Official Code § 2-221.01 et seq., for the period beginning on the day after the required payment date and ending on the date on which payment of the amount is made. Interest shall be calculated at the rate of 1% per month. No interest penalty shall be paid if payment for the completed delivery of the item of property or service is made on or before:

a) the 3rd day after the required payment date for meat or a meat product; b) the 5th day after the required payment date for an agricultural commodity; or c) the 15th day after the required payment date for any other item.

G.6.1.2 Any amount of an interest penalty which remains unpaid at the end of any 30-day period shall be

added to the principal amount of the debt and thereafter interest penalties shall accrue on the added amount.

G.6.2 Payments to Subcontractors

G.6.2.1 The Contractor must take one of the following actions within seven (7) days of receipt of any

amount paid to the Contractor by the District for work performed by any subcontractor under this contract:

a) Pay the subcontractor for the proportionate share of the total payment received from the

District that is attributable to the subcontractor for work performed under the contract; or

b) Notify the District and the subcontractor, in writing, of the Contractor’s intention to withhold all or part of the subcontractor’s payment and state the reason for the nonpayment.

G.6.2.2 The Contractor must pay any subcontractor or supplier interest penalties on amounts due to

the subcontractor or supplier beginning on the day after the payment is due and ending on the date on which the payment is made. Interest shall be calculated at the rate of 1% per month. No interest penalty shall be paid on the following if payment for the completed delivery of the item of property or service is made on or before:

a) the 3rd day after the required payment date for meat or a meat product; b) the 5th day after the required payment date for an agricultural commodity; or c) the 15th day after the required payment date for any other item.

G.6.2.3 Any amount of an interest penalty which remains unpaid by the Contractor at the end of any 30-

day period shall be added to the principal amount of the debt to the subcontractor and thereafter interest penalties shall accrue on the added amount.

G.6.2.4 A dispute between the Contractor and subcontractor relating to the amounts or entitlement of a

subcontractor to a payment or a late payment interest penalty under the Quick Payment Act does

28

Doc308925 – E-Citation System

not constitute a dispute to which the District of Columbia is a party. The District of Columbia may not be interpleaded in any judicial or administrative proceeding involving such a dispute.

G.6.3 Subcontract requirements

G.6.3.1 The Contractor shall include in each subcontract under this contract a provision requiring the

subcontractor to include in its contract with any lower-tier subcontractor or supplier the payment and interest clauses required under paragraphs (1) and (2) of D.C. Official Code § 2-221.02(d).

G.7 CONTRACTING OFFICER (CO)

Contracts will be entered into and signed on behalf of the District only by contracting officers. The contact information for the Contracting Officer is:

Chris Yi, CPPB Supervisory Contract Specialist/Contracting Officer Office of Contracting & Procurement 200 I Street, SE, Room 5410-H Washington, DC 20003 Telephone: (202) 724-5069 Email: chris.yi@dc.gov

G.8 AUTHORIZED CHANGES BY THE CONTRACTING OFFICER G.8.1 The CO is the only person authorized to approve changes in any of the requirements of this

contract. G.8.2 The Contractor shall not comply with any order, directive or request that changes or modifies the

requirements of this contract, unless issued in writing and signed by the CO. G.8.3 In the event the Contractor effects any change at the instruction or request of any person other

than the CO, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any cost increase incurred as a result thereof.

G.9 CONTRACT ADMINSTRATOR (CA)

G.9.1 The CA is responsible for general administration of the contract and advising the CO as to the

Contractor’s compliance or noncompliance with the contract. The CA has the responsibility of ensuring the work conforms to the requirements of the contract and such other responsibilities and authorities as may be specified in the contract. These include:

G.9.1.1 Keeping the CO fully informed of any technical or contractual difficulties encountered during

the performance period and advising the CO of any potential problem areas under the contract;

G.9.1.2 Coordinating site entry for Contractor personnel, if applicable;

29

Doc308925 – E-Citation System

G.9.1.3 Reviewing invoices for completed work and recommending approval by the CO if the Contractor’s costs are consistent with the negotiated amounts and progress is satisfactory and commensurate with the rate of expenditure;

G.9.1.4 Reviewing and approving invoices for deliverables to ensure receipt of goods and services.

This includes the timely processing of invoices and vouchers in accordance with the District’s payment provisions; and

G.9.1.5 Maintaining a file that includes all contract correspondence, modifications, records of inspections (site, data, equipment) and invoice or vouchers.

G.9.2 The address and telephone number of the CA is: LaMont Hinton, Program Director District of Columbia Metropolitan Police Department Automated Traffic Enforcement Unit 2850 New York Avenue NE Washington, DC 20002 Telephone: (202) 541-5494 Email: Lamont.Hinton@dc.gov

G.9.3 The CA shall NOT have the authority to: 1. Award, agree to, or sign any contract, delivery order or task order. Only the CO shall

make contractual agreements, commitments or modifications; 2. Grant deviations from or waive any of the terms and conditions of the contract; 3. Increase the dollar limit of the contract or authorize work beyond the dollar limit of the

contract, 4. Authorize the expenditure of funds by the Contractor; 5. Change the period of performance; or 6. Authorize the use of District property, except as specified under the contract.

G.9.4 The Contractor will be fully responsible for any changes not authorized in advance, in writing, by the CO; may be denied compensation or other relief for any additional work performed that is not so authorized; and may also be required, at no additional cost to the District, to take all corrective action necessitated by reason of the unauthorized changes.

30

Doc308925 – E-Citation System

SECTION H: SPECIAL CONTRACT REQUIREMENTS H.1 HIRING OF DISTRICT RESIDENTS AS APPRENTICES AND TRAINEES H.1.1 For all new employment resulting from this contract or subcontracts hereto, as defined in

Mayor’s Order 83-265 and implementing instructions, the Contractor shall use its best efforts to comply with the following basic goal and objectives for utilization of bona fide residents of the District of Columbia in each project’s labor force:

H.1.1.1 At least fifty-one (51) percent of apprentices and trainees employed shall be residents of the

District of Columbia registered in programs approved by the District of Columbia Apprenticeship Council.

H.1.2 The Contractor shall negotiate an Employment Agreement with the Department of Employment Services (DOES) for jobs created as a result of this contract. The DOES shall be the Contractor’s first source of referral for qualified apprentices and trainees in the implementation of employment goals contained in this clause.

H.2 DEPARTMENT OF LABOR WAGE DETERMINATIONS

The Contractor shall be bound by the Wage Determination No. 2015-4281, Revision No. 6, Date of Revision 5/8/2017, issued by the U.S. Department of Labor in accordance with the Service Contract Act, 41 U.S.C. § 351 et seq., and incorporated herein as Section J.2. The Contractor shall be bound by the wage rates for the term of the contract subject to revision as stated herein and in accordance with clause 24 of the SCP. If an option is exercised, the Contractor shall be bound by the applicable wage rates at the time of the exercise of the option. If the option is exercised and the CO obtains a revised wage determination, the revised wage determination is applicable for the option periods and the Contractor may be entitled to an equitable adjustment.

H.3 PREGNANT WORKERS FAIRNESS

H.3.1 The Contractor shall comply with the Protecting Pregnant Workers Fairness Act of 2016, D.C. Official Code § 32-1231.01 et seq. (PPWF Act).

H.3.2 The Contractor shall not:

(a) Refuse to make reasonable accommodations to the known limitations related to pregnancy, childbirth, related medical conditions, or breastfeeding for an employee, unless the Contractor can demonstrate that the accommodation would impose an undue hardship;

(b) Take an adverse action against an employee who requests or uses a reasonable

accommodation in regard to the employee's conditions or privileges of employment, including failing to reinstate the employee when the need for reasonable accommodations ceases to the employee's original job or to an equivalent position with equivalent: (1) Pay;

(2) Accumulated seniority and retirement;

31

Doc308925 – E-Citation System

(3) Benefits; and (4) Other applicable service credits;

(c) Deny employment opportunities to an employee, or a job applicant, if the denial is based

on the need of the employer to make reasonable accommodations to the known limitations related to pregnancy, childbirth, related medical conditions, or breastfeeding;

(d) Require an employee affected by pregnancy, childbirth, related medical conditions, or

breastfeeding to accept an accommodation that the employee chooses not to accept if the employee does not have a known limitation related to pregnancy, childbirth, related medical conditions, or breastfeeding or the accommodation is not necessary for the employee to perform her duties;

(e) Require an employee to take leave if a reasonable accommodation can be provided; or (f) Take adverse action against an employee who has been absent from work as a result

of a pregnancy-related condition, including a pre-birth complication. H.3.3 The Contractor shall post and maintain in a conspicuous place a notice of rights in both

English and Spanish and provide written notice of an employee's right to a needed reasonable accommodation related to pregnancy, childbirth, related medical conditions, or breastfeeding pursuant to the PPWF Act to:

(a) New employees at the commencement of employment; (b) Existing employees; and (c) An employee who notifies the employer of her pregnancy, or other condition covered by

the PPWF Act, within 10 days of the notification. H.3.4 The Contractor shall provide an accurate written translation of the notice of rights to any non-

English or non-Spanish speaking employee. H.3.5 Violations of the PPWF Act shall be subject to civil penalties as described in the Act. H.4 UNEMPLOYED ANTI-DISCRIMINATION H.4.1 The Contractor shall comply with the Unemployed Anti-Discrimination Act of 2012, D.C.

Official Code § 32-1361 et seq. H.4.2 The Contractor shall not:

(a) Fail or refuse to consider for employment, or fail or refuse to hire, an individual as

an employee because of the individual's status as unemployed; or

(b) Publish, in print, on the Internet, or in any other medium, an advertisement or announcement for any vacancy in a job for employment that includes:

(1) Any provision stating or indicating that an individual's status as unemployed

disqualifies the individual for the job; or (2) Any provision stating or indicating that an employment agency will not consider or

32

Doc308925 – E-Citation System

hire an individual for employment based on that individual's status as unemployed. H.4.3 Violations of the Unemployed Anti-Discrimination Act shall be subject to civil penalties as

described in the Act. H.5 51% DISTRICT RESIDENTS NEW HIRES REQUIREMENTS AND FIRST SOURCE

EMPLOYMENT AGREEMENT

Delete Article 35, 51% District Residents New Hires Requirements and First Source Employment Agreement, of the Standard Contract Provisions dated July 2010 for use with District of Columbia Government Supplies and Services Contracts and substitute the following Section H.5 51% DISTRICT RESIDENTS NEW HIRES REQUIREMENTS AND FIRST SOURCE EMPLOYMENT AGREEMENT in its place:

H.5 51% DISTRICT RESIDENTS NEW HIRES REQUIREMENTS AND FIRST SOURCE

EMPLOYMENT AGREEMENT

H.5.1 For contracts for services in the amount of $300,000 or more, the Contractor shall comply with the First Source Employment Agreement Act of 1984, as amended, D.C. Official Code § 2-219.01 et seq. (First Source Act).

H.5.2 The Contractor shall enter into and maintain during the term of the contract, a First Source Employment Agreement (Employment Agreement) with the District of Columbia Department of Employment Service’s (DOES), in which the Contractor shall agree that: (a) The first source for finding employees to fill all jobs created in order to perform the contract

shall be the First Source Register; and

(b) The first source for finding employees to fill any vacancy occurring in all jobs covered by the Employment Agreement shall be the First Source Register.

H.5.3 The Contractor shall not begin performance of the contract until its Employment Agreement has been accepted by DOES. Once approved, the Employment Agreement shall not be amended except with the approval of DOES.

H.5.4 The Contractor agrees that at least 51% of the new employees hired to perform the contract shall be District residents.

H.5.5 The Contractor’s hiring and reporting requirements under the First Source Act and any rules

promulgated thereunder shall continue for the term of the contract.

H.5.6 The CO may impose penalties, including monetary fines of 5% of the total amount of the direct and indirect labor costs of the contract, for a willful breach of the Employment Agreement, failure to submit the required hiring compliance reports, or deliberate submission of falsified data.

H.5.7 If the Contractor does not receive a good faith waiver, the CO may also impose an additional penalty equal to 1/8 of 1% of the total amount of the direct and indirect labor costs of the contract for each percentage by which the Contractor fails to meet its hiring requirements.

H.5.8 Any contractor which violates, more than once within a 10-year timeframe, the hiring or reporting requirements of the First Source Act shall be referred for debarment for not more than five (5) years.

33

Doc308925 – E-Citation System

H.5.9 The contractor may appeal any decision of the CO pursuant to this clause to the D.C. Contract Appeals Board as provided in clause 14 of the SCP, Disputes.

H.5.10 The provisions of the First Source Act do not apply to nonprofit organizations which employ 50 employees or less.

H.6 RESERVED

H.7 RESERVED

H.8 RESERVED H.9.1 Subcontracting Requirements H.9.1.1 The Director of the Department of Small and Local Business Development (DSLBD) has

approved a waiver of the mandatory subcontracting requirements for this contract. H.9.1.2 A prime contractor that is a CBE and has been granted a bid preference pursuant to D.C.

Official Code § 2-218.43, or is selected through a set-aside program, shall perform at least 35% of the contracting effort with its own organization and resources and, if it subcontracts, 35% of the subcontracting effort shall be with CBEs. A CBE prime contractor that performs less than 35% of the contracting effort shall be subject to enforcement actions under D.C. Official Code § 2-218.63.

H.9.1.3 A prime contractor that is a certified joint venture and has been granted a bid preference

pursuant to D.C. Official Code § 2-218.43, or is selected through a set-aside program, shall perform at least 50% of the contracting effort with its own organization and resources and, if it subcontracts, 35% of the subcontracting effort shall be with CBEs. A certified joint venture prime contractor that performs less than 50% of the contracting effort shall be subject to enforcement actions under D.C. Official Code § 2-218.63.

H.9.1.4 Each CBE utilized to meet these subcontracting requirements shall perform at least 35% of its

contracting effort with its own organization and resources. H.9.1.5 A prime contractor that is a CBE and has been granted a bid preference pursuant to D.C.

Official Code § 2-218.43, or is selected through a set-aside program, shall perform at least 50% of the on-site work with its own organization and resources if the contract is $1 million or less.

H.10 FAIR CRIMINAL RECORD SCREENING H.10.1 The Contractor shall comply with the provisions of the Fair Criminal Record Screening

Amendment Act of 2014, effective December 17, 2014 (D.C. Law 20-152) (“Act” as used in this section). This section applies to any employment, including employment on a temporary or contractual basis, where the physical location of the employment is in whole or substantial part within the District of Columbia.

H.10.2 Prior to making a conditional offer of employment, the Contractor shall not require an

applicant for employment, or a person who has requested consideration for employment by the Contractor, to reveal or disclose an arrest or criminal accusation that is not then pending or did not result in a criminal conviction.

34

Doc308925 – E-Citation System

H.10.3 After making a conditional offer of employment, the Contractor may require an applicant to disclose or reveal a criminal conviction.

H.10.4 The Contractor may only withdraw a conditional offer of employment, or take adverse action

against an applicant, for a legitimate business reason as described in the Act. H.10.5 This section and the provisions of the Act shall not apply:

(a) Where a federal or District law or regulation requires the consideration of an applicant’s criminal history for the purposes of employment;

(b) To a position designated by the employer as part of a federal or District government

program or obligation that is designed to encourage the employment of those with criminal histories;

(c) To any facility or employer that provides programs, services, or direct care to,

children, youth, or vulnerable adults; or (d) To employers that employ less than 11 employees.

H.10.6 A person claiming to be aggrieved by a violation of the Act may file an administrative

complaint with the District of Columbia Office of Human Rights, and the Commission on Human Rights may impose monetary penalties against the Contractor.

H.11 DISTRICT RESPONSIBILITIES H.11.1 MPD will provide Test Scenarios and Test Scripts for the development of user testing. H.11.2 MPD will provide violation tables. H.11.3 MPD will define the different levels of access - Technical support staff shall be granted

administrative rights, supervisory staff will be granted some administrative rights for entering users and assigning roles, and general users, who are responsible for ticket and related form creation, will not be granted administrative rights.

H.11.4 MPD will be responsible for testing delivered “bug fixes” and other application software

upgrades and enhancements within five (5) business days after the software is delivered. In the event, MPD cannot meet the (5) business days testing period, MPD shall be responsible to request an extension from the Contractor in writing.

H.11.5 MPD and OCTO will work with Contractor to establish the list environments on the District

network.

35

Doc308925 – E-Citation System

H.12 PURCHASES OF IT HARDWARE AND EQUIPMENT

The Contractor shall provide only the most current models, components and accessories in new, fully operational, factory sealed condition, with all applicable licenses. The Contractor warrants and represents that the equipment is eligible for the manufacturer's normal and extended warranty and support within the United States to Authorized Users. Previously owned, damaged, refurbished, remanufactured, counterfeit, "gray market" or substitute third party items will not be accepted. The bidder shall provide evidence of its authorized reseller agreement or certification with its bid.

36

Doc308925 – E-Citation System

SECTION I: CONTRACT CLAUSES I.1 APPLICABILITY OF STANDARD CONTRACT PROVISIONS

The Standard Contract Provisions for use with District of Columbia Government Supplies and Services Contracts dated July 2010 (SCP) are incorporated as part of the contract. To obtain a copy of the SCP go to http://ocp.dc.gov, under Quick Links click on “Required Solicitation Documents”.

I.2 CONTRACTS THAT CROSS FISCAL YEARS

Continuation of this contract beyond the current fiscal year is contingent upon future fiscal appropriations.

I.3 CONFIDENTIALITY OF INFORMATION

The Contractor shall keep all information relating to any employee or customer of the District in absolute confidence and shall not use the information in connection with any other matters; nor shall it disclose any such information to any other person, firm or corporation, in accordance with the District and federal laws governing the confidentiality of records.

I.4 TIME

Time, if stated in a number of days, will include Saturdays, Sundays, and holidays, unless otherwise stated herein.

I.5 RIGHTS IN DATA

Delete clause 42, Rights in Data, of the Standard Contract Provisions dated July 2010 for use with District of Columbia Government Supplies and Services Contracts and substitute the following clause 42, Rights in Data) in its place:

A. Definitions

1. “Products” - A deliverable under any contract that may include commodities, services and/or technology furnished by or through Contractor, including existing and custom Products, such as, but not limited to: a) recorded information, regardless of form or the media on which it may be recorded; b) document research; c) experimental, developmental, or engineering work; d) licensed software; e) components of the hardware environment; f) printed materials (including but not limited to training manuals, system and user documentation, reports, drawings); g) third party software; h) modifications, customizations, custom programs, program listings, programming tools, data, modules, components; and i) any intellectual property embodied therein, whether in tangible or intangible form, including but not limited to utilities, interfaces, templates, subroutines, algorithms, formulas, source code, and object code.

37

Doc308925 – E-Citation System

2. “Existing Products” - Tangible Products and intangible licensed Products that exist prior to the commencement of work under the contract. Existing Products must be identified on the Product prior to commencement of work or else will be presumed to be Custom Products.

3. “Custom Products” - Products, preliminary, final or otherwise, which are created or developed by Contractor, its subcontractors, partners, employees, resellers or agents for the District.

4. “District” – The District of Columbia and its agencies.

B. Title to Project Deliverables

The Contractor acknowledges that it is commissioned by the District to perform services detailed in the contract. The District shall have ownership and rights for the duration set forth in the contract to use, copy, modify, distribute, or adapt Products as follows:

1. Existing Products: Title to all Existing Licensed Product(s), whether or not embedded in, delivered or operating in conjunction with hardware or Custom Products, shall remain with Contractor or third party proprietary owner, who retains all rights, title and interest (including patent, trademark or copyrights). Effective upon payment, the District shall be granted an irrevocable, non-exclusive, worldwide, paid-up license to use, execute, reproduce, display, perform, adapt (unless Contractor advises the District as part of Contractor’s bid that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the District’s satisfaction), and distribute Existing Product to District users up to the license capacity stated in the contract with all license rights necessary to fully effect the general business purpose of the project or work plan or contract. Licenses shall be granted in the name of the District as per the conditions included in the Gtechna License agreement. The District agrees to reproduce the copyright notice and any other legend of ownership on any copies authorized under this paragraph. If the District requests changes to the Contractor software solution, the new modules or software changes shall be considered an integral part of the Existing Product delivered as part of this project. All changes made to the Existing Product shall be covered by the Gtechna license agreement.

2. Custom Products: It is understood that the product delivered in this project does not include any “Custom Products”. Should the District ask for a proposal for the Contractor to quote a special Custom Product and should the Contractor agree to develop such a product, after full payment of such product then a new Custom Product shall be delivered. Effective upon Product creation, Contractor shall convey, assign, and transfer to the District the sole and exclusive rights, title and interest in Custom Products, whether preliminary, final or otherwise, including all patent, trademark, and copyrights. Contractor hereby agrees to take all necessary and appropriate steps to ensure that the Custom Products are protected against unauthorized copying, reproduction and marketing by or through Contractor. For clarity, it is understood that if the District asks the Contractor to quote for the development of a Special Product or feature, this product will not be considered a part of this project product. If the District decides to fund the development of a new product to be “Custom Product”, the product development shall be considered as a consultant project and all such product development will be separated from the main project to avoid any license agreement misunderstanding.

38

Doc308925 – E-Citation System

C. Transfers or Assignments of Existing or Custom Products by the District

The District may transfer or assign Existing or Custom Products and the licenses thereunder to another District agency. Nothing herein shall preclude the Contractor from otherwise using the related or underlying general knowledge, skills, ideas, concepts, techniques and experience developed under a project or work plan in the course of Contractor’s business.

D. Subcontractor Rights

Whenever any data, including computer software, are to be obtained from a subcontractor under the contract, the Contractor shall use this clause, Rights in Data, in the subcontract, without alteration, and no other clause shall be used to enlarge or diminish the District’s or the Contractor’s rights in that subcontractor data or computer software which is required for the District.

E. Source Code Escrow

1. For all computer software furnished to the District with the rights specified in section B.2, the Contractor shall furnish to the District, a copy of the source code with such rights of the scope as specified in section B.2 of this clause. For all computer software furnished to the District with the restricted rights specified in section B.1 of this clause, the District, if the Contractor either directly or through a successor or affiliate shall cease to provide the maintenance or warranty services provided the District under the contract or any paid-up maintenance agreement, or if the Contractor should be declared insolvent by a court of competent jurisdiction, shall have the right to obtain, for its own and sole use only, a single copy of the current version of the source code supplied under the contract, and a single copy of the documentation associated therewith, upon payment to the person in control of the source code the reasonable cost of making each copy. 2. If the Contractor or Product manufacturer/developer of software furnished to the District with the rights specified in section B.1 of this clause offers the source code or source code escrow to any other commercial customers, the Contractor shall either: (1) provide the District with the source code for the Product; (2) place the source code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the District, and who shall be directed to release the deposited source code in accordance with a standard escrow arrangement acceptable to the District; or (3) will certify to the District that the Product manufacturer/ developer has named the District as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the District, and who shall be directed to release the deposited source code in accordance with the terms of escrow. 3. The Contractor shall update the source code, as well as any corrections or enhancements to the source code, for each new release of the Product in the same manner as provided above, and certify such updating of escrow to the District in writing.

F. Indemnification and Limitation of Liability

The Contractor shall indemnify and save and hold harmless the District, its officers, agents and employees acting within the scope of their official duties against any liability, including costs and expenses, (i) for violation of proprietary rights, copyrights, or rights of privacy, arising out of the publication, translation, reproduction, delivery, performance, use or disposition of any

39

Doc308925 – E-Citation System

data furnished under this contract, or (ii) based upon any data furnished under this contract, or based upon libelous or other unlawful matter contained in such data.

I.6 OTHER CONTRACTORS

The Contractor shall not commit or permit any act that will interfere with the performance of work by another District contractor or by any District employee.

I.7 SUBCONTRACTS

The Contractor hereunder shall not subcontract any of the Contractor’s work or services to any subcontractor without the prior written consent of the CO. Any work or service so subcontracted shall be performed pursuant to a subcontract agreement, which the District will have the right to review and approve prior to its execution by the Contractor. Any such subcontract shall specify that the Contractor and the subcontractor shall be subject to every provision of this contract. Notwithstanding any such subcontract approved by the District, the Contractor shall remain liable to the District for all Contractor's work and services required hereunder.

I.8 INSURANCE A. GENERAL REQUIREMENTS. The Contractor at its sole expense shall procure and maintain,

during the entire period of performance under this contract, the types of insurance specified below. The Contractor shall have its insurance broker or insurance company submit a Certificate of Insurance to the CO giving evidence of the required coverage prior to commencing performance under this contract. In no event shall any work be performed until the required Certificates of Insurance signed by an authorized representative of the insurer(s) have been provided to, and accepted by, the CO. All insurance shall be written with financially responsible companies authorized to do business in the District of Columbia or in the jurisdiction where the work is to be performed and have an A.M. Best Company rating of A- / VII or higher. The Contractor shall require all of its subcontractors to carry the same insurance required herein.

All required policies shall contain a waiver of subrogation provision in favor or the Government of the District of Columbia. This waiver will not apply of the vendor/contractor is not legally responsible for the loss. The Government of the District of Columbia shall be included in all policies required hereunder to be maintained by the Contractor and its subcontractors (except for workers’ compensation and professional liability insurance) as an additional insureds for claims against The Government of the District of Columbia relating to this contract, with the understanding that any affirmative obligation imposed upon the insured Contractor or its subcontractors (including without limitation the liability to pay premiums) shall be the sole obligation of the Contractor or its subcontractors, and not the additional insured. The additional insured status under the Contractor’s and its subcontractors’ Commercial General Liability insurance policies shall be effected using the ISO Additional Insured Endorsement form CG 20 10 11 85 (or CG 20 10 07 04 and CG 20 37 07 04) or such other endorsement or combination of endorsements providing coverage at least as broad and approved by the CO in writing. All of the Contractor’s and its subcontractors’ liability policies (except for workers’ compensation and professional liability insurance) shall be endorsed using ISO form CG 20 01 04 13 or its equivalent so as to indicate that such policies provide primary

40

Doc308925 – E-Citation System

coverage (without any right of contribution by any other insurance, reinsurance or self- insurance, including any deductible or retention, maintained by an Additional Insured) for all claims against the additional insured arising out of the performance of this Statement of Work by the Contractor or its subcontractors, or anyone for whom the Contractor or its subcontractors may be liable. These policies shall include a separation of insureds clause applicable to the additional insured.

If the Contractor and/or its subcontractors maintain broader coverage and/or higher limits than the minimums shown below, the District requires and shall be entitled to the broader coverage and/or the higher limits maintained by the Grantee and subcontractors.

1. Commercial General Liability Insurance (“CGL”). The Contractor shall provide

evidence satisfactory to the CO with respect to the services performed that it carries a CGL policy, written on an occurrence (not claims-made) basis, on Insurance Services Office, Inc. (“ISO”) form CG 00 01 04 13 (or another occurrence-based form with coverage at least as broad and approved by the CO in writing), covering liability for all ongoing and completed operations of the Contractor, including ongoing and completed operations under all subcontracts, and covering claims for bodily injury, including without limitation sickness, disease or death of any persons, injury to or destruction of property, including loss of use resulting therefrom, personal and advertising injury, and including coverage for liability arising out of an Insured Contract (including the tort liability of another assumed in a contract) and acts of terrorism (whether caused by a foreign or domestic source). Such coverage shall have limits of liability of not less than $1,000,000 each occurrence, a $2,000,000 general aggregate (including a per location or per project aggregate limit endorsement, if applicable) limit, a $1,000,000 personal and advertising injury limit, and a $2,000,000 products-completed operations aggregate limit.

2. Workers’ Compensation Insurance. The Contractor shall provide evidence satisfactory

to the CO of Workers’ Compensation insurance in accordance with the statutory mandates of the District of Columbia or the jurisdiction in which the contract is performed.

Employer’s Liability Insurance. The Contractor shall provide evidence satisfactory to the CO of employer’s liability insurance as follows: $500,000 per accident for injury; $500,000 per employee for disease; and $500,000 for policy disease limit. All insurance required by this paragraph 3 shall include a waiver of subrogation endorsement for the benefit of Government of the District of Columbia. This waiver will not apply if the vendor/contractor is not legally responsible for the loss.

3. Cyber Liability Insurance - The Contractor shall provide evidence satisfactory to the

Contracting Officer of Cyber Liability Insurance, with limits not less than $2,000,000 per occurrence or claim, $2,000,000 aggregate. Coverage shall be sufficiently broad to respond to the duties and obligations as is undertaken by Contractor in this agreement and shall include, but not limited to, claims involving infringement of intellectual property, including but not limited to infringement of copyright, trademark, trade dress, invasion of privacy violations, information theft, damage to or destruction of electronic information, release of private information, alteration of electronic information,

41

Doc308925 – E-Citation System

extortion and network security. The policy shall provide coverage for breach response costs as well as regulatory fines and penalties as well as credit monitoring expenses with limits sufficient to respond to these obligations. This insurance requirement will be considered met if the general liability insurance includes an affirmative cyber endorsement for the required amounts.

4. Professional Liability Insurance (Errors & Omissions) - The Contractor shall provide Professional Liability Insurance (Errors and Omissions) to cover liability resulting from any error or omission in the performance of professional services under this Contract. The policy shall provide limits of $1,000,000 per claim or per occurrence for each wrongful act and $2,000,000 annual aggregate. The Contractor warrants that any applicable retroactive date precedes the date the Contractor first performed any professional services for the Government of the District of Columbia and that continuous coverage will be maintained or an extended reporting period will be exercised for a period of at least five (5) years after the completion of the professional services.

5. Commercial Umbrella Liability. The Contractor shall provide evidence satisfactory to

the CO of commercial umbrella liability insurance with minimum limits equal to the greater of (i) the limits set forth in the Contractor’s umbrella liability policy or (ii) $5,000,000 per occurrence and $5,000,000 in the annual aggregate, following the form and in excess of the underlying employers’ liability, commercial general liability, and commercial automobile liability policies, with an effective date that is concurrent with such liability policies. The insurance required under this paragraph shall be written in a form that annually reinstates all required limits. Coverage shall be primary to any insurance, self- insurance or reinsurance maintained by the District and the “other insurance” provision must be amended in accordance with this requirement and principles of vertical exhaustion.

B. PRIMARY AND NONCONTRIBUTORY INSURANCE

The insurance required herein shall be primary to and will not seek contribution from any other insurance, reinsurance or self-insurance including any deductible or retention, maintained by the Government of the District of Columbia unless the contractor/vendor is not legally responsible for the loss.

C. DURATION. The Contractor shall carry all required insurance until all contract work is accepted by the District of Columbia, and shall carry listed coverage’s for ten years for construction projects following final acceptance of the work performed under this contract and two years for non-construction related contracts.

D. LIABILITY. These are the required minimum insurance requirements established by

the District of Columbia. HOWEVER, THE REQUIRED MINIMUM INSURANCE REQUIREMENTS PROVIDED ABOVE WILL NOT IN ANY WAY LIMIT THE CONTRACTOR’S LIABILITY UNDER THIS CONTRACT.

E. CONTRACTOR’S PROPERTY. Contractor and subcontractors are solely responsible

for any loss or damage to their personal property, including but not limited to tools and equipment, scaffolding and temporary structures, rented machinery, or owned and leased equipment. A waiver of subrogation shall apply in favor of the District of Columbia.

42

Doc308925 – E-Citation System

F. MEASURE OF PAYMENT. The District shall not make any separate measure or payment

for the cost of insurance and bonds. The Contractor shall include all of the costs of insurance and bonds in the contract price.

G. NOTIFICATION. The Contractor shall ensure that all policies provide that the CO shall be given thirty (30) days prior written notice in the event of coverage and / or limit changes or if the policy is canceled prior to the expiration date shown on the certificate. The Contractor shall provide the CO with ten (10) days prior written notice in the event of non-payment of premium. The Contractor will also provide the CO with an updated Certificate of Insurance should its insurance coverage’s renew during the contract.

H. CERTIFICATES OF INSURANCE. The Contractor shall submit certificates of insurance

giving evidence of the required coverage as specified in this section prior to commencing work. Certificates of insurance must reference the corresponding purchase order number. Evidence of insurance shall be submitted to:

The Government of the District of Columbia

And mailed to the attention of:

Metropolitan Police Department 300 Indiana Avenue, NW Washington, DC 20001 Telephone: (202) 727-5298

The CO may request and the Contractor shall promptly deliver updated certificates of insurance, endorsements indicating the required coverage’s, and/or certified copies of the insurance policies. If the insurance initially obtained by the Contractor expires prior to completion of the contract, renewal certificates of insurance and additional insured and other endorsements shall be furnished to the CO prior to the date of expiration of all such initial insurance. For all coverage required to be maintained after completion, an additional certificate of insurance evidencing such coverage shall be submitted to the CO on an annual basis as the coverage is renewed (or replaced).

I. DISCLOSURE OF INFORMATION. The Contractor agrees that the District may disclose

the name and contact information of its insurers to any third party which presents a claim against the District for any damages or claims resulting from or arising out of work performed by the Contractor, its agents, employees, servants or subcontractors in the performance of this contract.

J. CARRIER RATINGS. All Contractor’s and its subcontractors’ insurance required in

connection with this contract shall be written by insurance companies with an A.M. Best Insurance Guide rating of at least A- VII (or the equivalent by any other rating agency) and licensed in the in the District.

I.9 EQUAL EMPLOYMENT OPPORTUNITY

In accordance with the District of Columbia Administrative Issuance System, Mayor’s Order

43

Doc308925 – E-Citation System

85- 85 dated June 10, 1985, the forms for completion of the Equal Employment Opportunity Information Report are incorporated herein as Section J.3. An award cannot be made to any bidder who has not satisfied the equal employment requirements.

I.10 ORDER OF PRECEDENCE

The contract awarded as a result of Solicitation Doc308925 contain the following clause:

ORDER OF PRECEDENCE

A conflict in language shall be resolved by giving precedence to the document in the highest order of priority that contains language addressing the issue in question. The following documents are incorporated into the contract by reference and made a part of the contract in the following order of precedence:

(1) An applicable Court Order, if any (2) Contract document (3) Standard Contract Provisions (4) Contract attachments other than the Standard Contract Provisions (5) IFB, as amended (6) Bid/Proposal

a) Contractor’s Service Level Agreement b) Contractor’s License Agreement

I.11 DISPUTES

Delete clause 14, Disputes, of the Standard Contract Provisions dated July 2010 for use with District of Columbia Government Supplies and Services Contracts and substitute the following clause 14, Disputes) in its place:

14. Disputes

All disputes arising under or relating to the contract shall be resolved as provided herein.

(a) Claims by the Contractor against the District: Claim, as used in paragraph (a) of this clause, means a written assertion by the Contractor seeking, as a matter of right, the payment of money in a sum certain, the adjustment or interpretation of contract terms, or other relief arising under or relating to the contract. A claim arising under a contract, unlike a claim relating to that contract, is a claim that can be resolved under a contract clause that provides for the relief sought by the claimant

(1) All claims by a Contractor against the District arising under or relating to a contract

shall be in writing and shall be submitted to the CO for a decision. The Contractor’s claim shall contain at least the following:

(i) A description of the claim and the amount in dispute; (ii) Data or other information in support of the claim; (iii) A brief description of the Contractor’s efforts to resolve the dispute prior to

filing the claim; and (iii) The Contractor’s request for relief or other action by the CO.

(2) The CO may meet with the Contractor in a further attempt to resolve the claim

44

Doc308925 – E-Citation System

by agreement.

(3) The CO shall issue a decision on any claim within 120 calendar days after receipt of the claim. Whenever possible, the CO shall take into account factors such as the size and complexity of the claim and the adequacy of the information in support of the claim provided by the Contractor.

(4) The CO’s written decision shall do the following:

(i) Provide a description of the claim or dispute; (ii) Refer to the pertinent contract terms; (iii) State the factual areas of agreement and disagreement; (iv) State the reasons for the decision, including any specific findings of fact,

although specific findings of fact are not required and, if made, shall not be binding in any subsequent proceeding;

(v) If all or any part of the claim is determined to be valid, determine the amount of monetary settlement, the contract adjustment to be made, or other relief to be granted;

(vi) Indicate that the written document is the CO’s final decision; and (vii) Inform the Contractor of the right to seek further redress by appealing the

decision to the Contract Appeals Board.

(5) Failure by the CO to issue a decision on a contract claim within 120 days of receipt of the claim will be deemed to be a denial of the claim, and will authorize the commencement of an appeal to the Contract Appeals Board as provided by D.C. Official Code § 2-360.04.

(6) If a contractor is unable to support any part of its claim and it is determined that

the inability is attributable to a material misrepresentation of fact or fraud on the part of the Contractor, the Contractor shall be liable to the District for an amount equal to the unsupported part of the claim in addition to all costs to the District attributable to the cost of reviewing that part of the Contractor’s claim. Liability under this paragraph (a)(6) shall be determined within six (6) years of the commission of the misrepresentation of fact or fraud.

(7) Pending final decision of an appeal, action, or final settlement, the Contractor shall

proceed diligently with performance of the contract in accordance with the decision of the CO.

(b) Claims by the District against the Contractor: Claim as used in paragraph (b) of

this clause, means a written demand or written assertion by the District seeking, as a matter of right, the payment of money in a sum certain, the adjustment of contract terms, or other relief arising under or relating to the contract. A claim arising under a contract, unlike a claim relating to that contract, is a claim that can be resolved under a contract clause that provides for the relief sought by the claimant.

(1) The CO shall decide all claims by the District against a contractor arising under or relating to a contract.

45

Doc308925 – E-Citation System

(2) The CO shall send written notice of the claim to the contractor. The CO’s written decision shall do the following:

(i) Provide a description of the claim or dispute; (ii) Refer to the pertinent contract terms; (iii) State the factual areas of agreement and disagreement; (iv) State the reasons for the decision, including any specific findings of

fact, although specific findings of fact are not required and, if made, shall not be binding in any subsequent proceeding;

(v) If all or any part of the claim is determined to be valid, determine the amount of monetary settlement, the contract adjustment to be made, or other relief to be granted;

(vi) Indicate that the written document is the CO’s final decision; and (vii) Inform the Contractor of the right to seek further redress by appealing

the decision to the Contract Appeals Board.

(3) The CO shall support the decision by reasons and shall inform the Contractor of its rights as provided herein.

(4) Before or after issuing the decision, the CO may meet with the Contractor to

attempt to resolve the claim by agreement.

(5) The authority contained in this paragraph (b) shall not apply to a claim or dispute for penalties or forfeitures prescribed by statute or regulation which another District agency is specifically authorized to administer, settle or determine.

(6) This paragraph shall not authorize the CO to settle, compromise, pay, or

otherwise adjust any claim involving fraud.

(c) Decisions of the CO shall be final and not subject to review unless the Contractor timely commences an administrative appeal for review of the decision, by filing a complaint with the Contract Appeals Board, as authorized by D.C. Official Code § 2-360.04.

(d) Pending final decision of an appeal, action, or final settlement, the Contractor

shall proceed diligently with performance of the contract in accordance with the decision of the CO.

I.12 COST AND PRICING DATA

Delete clause 25, Cost and Pricing Data, of the Standard Contract Provisions dated July 2010 for use with District of Columbia Government Supplies and Services Contracts.

46

Doc308925 – E-Citation System

SECTION J: ATTACHMENTS The following list of attachments is incorporated into the contract by reference.

Attachment

Number Document

J.1

Government of the District of Columbia Standard Contract Provisions for Use with the Supplies and Services Contracts (July 2010)

available at http://ocp.dc.gov, under Quick Links click on “Required Solicitation Documents”

J.2 U.S. Department of Labor Wage Determination No. 2015-4281, Revision No.

6, Date of Revision,: 5/8/2017

J.3

Equal Employment Opportunity Employer Information Report and Mayor’s Order 85-85

available at available at http://ocp.dc.gov, under Quick Links click on “Required Solicitation Documents”

J.4

Department of Employment Services First Source Employment Agreement available at http://ocp.dc.gov, under Quick Links click on “Required

Solicitation Documents”

J.5 Way to Work Amendment Act of 2006 - Living Wage Notice available at

http://ocp.dc.gov, under Quick Links click on “Required Solicitation Documents”

J.6

Way to Work Amendment Act of 2006 - Living Wage Fact Sheet available at http://ocp.dc.gov, under Quick Links click on “Required Solicitation

Documents”

J.7 Tax Certification Affidavit available at http://ocp.dc.gov, under Quick

Links click on “Required Solicitation Documents”

J.8 Subcontracting Plan (if required by law) available at http://ocp.dc.gov,

under Quick Links click on “Required Solicitation Documents”

J.9

First Source Initial Employment Plan (if contract is $300,000 or more) available at http://ocp.dc.gov, under Quick Links click on “Required

Solicitation Documents”

J.10 Gtechna Support Services Agreement dated 2017

J.11 Gtechna License Agreement