Proposed Contract with Modaxo Traffic Management USA Inc. to Contract No. CW124879

MURIEL BOWSER
MAYOR
October 1, 2025
The Honorable Phil Mendelson
Chairman
Council of the District of Columbia
John A. Wilson Building
1350 Pennsylvania Avenue, NW, Suite 504
Washington, DC 20004
Dear Chairman Mendelson:
Pursuant to section 451 of the District of Columbia Home Rule Act (D.C. Official Code § 1-204.51) and
section 202 of the Procurement Practices Reform Act of 2010 (D.C. Official Code § 2-352.02), enclosed
for consideration and approval by the Council of the District of Columbia is a proposed resolution, the
“Contract No. CW124879 with Modaxo Traffic Management USA, Inc. Emergency Approval Resolution
of 2025,” and the accompanying emergency declaration resolution.
Under the proposed contract, Modaxo Traffic Management USA, Inc., will provide ticket processing and
related services to support the provision of ticket processing and related services for parking and traffic
violations from October 16, 2025, through October 15, 2030.
My administration is available to discuss any questions you may have regarding the proposed contract. In
order to facilitate a response to any questions you may have, please have your staff contact Marc Scott,
Chief Operating Officer, Office of Contracting and Procurement, at (202) 724-8759.
I urge the Council to take prompt and favorable action on the enclosed legislation.
Sincerely,
Muriel Bowser
Enclosures

1

GOVERNMENT OF THE DISTRICT OF COLUMBIA
Office of Contracting and Procurement

Pursuant to section 202(c) of the Procurement Practices Reform Act of 2010, as amended, D.C.
Official Code § 2-352.02(c), the following contract summary is provided:

COUNCIL CONTRACT SUMMARY
(Multiyear)

(A) Contract Number: CW124879

Proposed Contractor: Modaxo Traffic Management USA, Inc.

Proposed Contractor’s Principals: William Robert Delaney, President

Contract Amount (Base Period): Not-to-Exceed $100,457,950.38

Unit and Method of Compensation: Payment based on firm fixed unit prices and a cost
reimbursement component.

Term of Contract: October 16, 2025, through October 15, 2030

Type of Contract: Requirements with a cost reimbursement component

Source Selection Method: Exempt from Competition

(B) For a contract containing option periods, the contract amount for the base period and for
each option period. If the contract amount for one or more of the option periods differs from
the amount for the base period, provide an explanation of the reason for the difference:

Base Period Amount: $100,457,950.38

Option Period 1 Amount: $21,569,205.22
Explanation of difference from base period (if applicable): The base year is for a five-year
period; option year one is for a one-year period.

Option Period 2 Amount: $22,491,762.46
Explanation of difference from base period (if applicable): The base year is for a five-year
period; option year two is for a one-year period.

Option Period 3 Amount: $23,456,282.61
Explanation of difference from base period (if applicable): The base year is for a five-year
period; option year three is for a one-year period.

2

(C) The goods or services to be provided, the methods of delivering goods or services, and any
significant program changes reflected in the proposed contract:

Under the proposed contract, Modaxo Traffic Management USA, Inc., will
continue processing tickets (handwritten, electronic, camera) issued by the various District law
enforcement entities on a routine basis. The Contractor will submit tickets processed to offenders of
the District’s traffic laws for appropriate fines or penalties. The Contractor shall continue providing
back-office administration services that include processing, storage, and logging tickets into the
electronic ticket processing system to be accessible by the Department of Motor Vehicle’s staff to
adjudicate driver claims and properly align fines and penalties with driver records.

(D) The selection process, including the number of offerors, the evaluation criteria, and the
evaluation results, including price, technical or quality, and past performance components:

The District of Columbia Office of Contracting and Procurement, on behalf of the District of
Columbia Department of Motor Vehicles (DMV), is awarding a multi-year exempt from
competition contract to Modaxo Traffic Management USA, Inc. This award is for ongoing ticket
processing and related services for the DC DMV.

In accordance with D.C. Official Code § 2-354.13, this procurement is exempt from competition.
Modaxo Traffic Management USA, Inc., is the incumbent provider, having previously provided
ticket processing and related services to the DMV under several emergency contracts. Additionally,
Modaxo Traffic Management USA, Inc., has developed the ticket processing and related service
system currently in use by the District, demonstrating their unique capability to support the existing
software and technology infrastructure.

In accordance with the 27 DCMR § 2401 contract types, the Contracting Officer recommends an
award of a requirements contract with a cost reimbursement type of contract to Modaxo Traffic
Management USA, Inc.

(E) A description of any bid protest related to the award of the contract, including whether the
protest was resolved through litigation, withdrawal of the protest by the protestor, or
voluntary corrective action by the District. Include the identity of the protestor, the grounds
alleged in the protest, and any deficiencies identified by the District as a result of the protest:

There were no protests associated with this procurement.

(F) A description of any other contracts the proposed contractor is currently seeking or holds
with the District:

The contractor currently provides ticket processing services under Emergency Contract No.
CW125486, this emergency contract is due to expire on October 16, 2025.

(G) The background and qualifications of the proposed contractor, including its organization,
financial stability, personnel, and performance on past or current government or private
sector contracts with requirements similar to those of the proposed contract:

3

Modaxo Traffic Management USA, Inc., has a comprehensive understanding of the District's
existing automated and manual ticket processing systems. Over the course of emergency contracts,
Modaxo Traffic Management USA Inc. has customized and modified several off-the-shelf
contracted program applications to meet specific District legislative and programmatic
requirements, as well as various personnel and client applications. As a vendor, Modaxo Traffic
Management USA, Inc. is the exclusive source capable of providing an integrated ticket processing
service to the District. These ticket processing services are essential functions that enhance the
enforcement of the District's traffic laws and regulations by issuing tickets for transportation and
parking violations.

(H) A summary of the subcontracting plan required under section 2346 of the Small, Local, and
Disadvantaged Business Enterprise Development and Assistance Act of 2005, as amended,
D.C. Official Code § 2-218.01 et seq. (“Act”), including a certification that the subcontracting
plan meets the minimum requirements of the Act and the dollar volume of the portion of the
contract to be subcontracted, expressed both in total dollars and as a percentage of the total
contract amount:

The contractor submitted their subcontracting plan required under section 2346 of the Small, Local,
and Disadvantaged Business Enterprise Development and Assistance Act of 2005, as amended,
D.C. Official Code § 2-218.01 et seq. (“Act”). The contractor's subcontracting plan meets the
minimum requirement of 35% and a copy of the Subcontracting plan has been submitted to DSLBD
for their records.

(I) Performance standards and the expected outcome of the proposed contract:

Modaxo Traffic Management USA, Inc., performance will be regularly and routinely monitored by
DMV. The expected outcome is to provide ticket processing and related services.

(J) The amount and date of any expenditure of funds by the District pursuant to the contract
prior to its submission to the Council for approval:

None.

(K) A certification that the proposed contract is within the appropriated budget authority for the
agency for the fiscal year and is consistent with the financial plan and budget adopted in
accordance with D.C. Official Code §§ 47-392.01 and 47-392.02:

The Office of the Chief Financial Officer certified that there is available funding in the amount of
$100,457,950.38 in accordance with D.C. Official Code §§ 47-392.01 and 47-392.02.

(L) A certification that the contract is legally sufficient, including whether the proposed
contractor has any pending legal claims against the District:

The Office of the Attorney General has determined that the proposed multi-year contract with
Modaxo Traffic Management USA, Inc., is legally sufficient and the contractor has no pending
legal claim against the District.

(M) A certification that the Citywide Clean Hands database indicates that the proposed contractor
is current with its District taxes. If the Citywide Clean Hands Database indicates that the
4

proposed contractor is not current with its District taxes, either: (1) a certification that the
contractor has worked out and is current with a payment schedule approved by the District;
or (2) a certification that the contractor will be current with its District taxes after the District
recovers any outstanding debt as provided under D.C. Official Code § 2-353.01(b):

The contractor is current with its District taxes according to the Clean Hands certification.

(N) A certification from the proposed contractor that it is current with its federal taxes, or has
worked out and is current with a payment schedule approved by the federal government:

The contractor has self-certified, via the Bidder Offeror certification form, that it is current with its
federal taxes.

(O) A certification that the proposed contractor has been determined not to violate section 334a of
the Board of Ethics and Government Accountability Establishment and Comprehensive
Ethics Reform Amendment Act of 2011, D.C. Official Code § 1-1163.34a; and (2) A
certification from the proposed contractor that it currently is not and will not be in violation
of section 334a of the Board of Ethics and Government Accountability Establishment and
Comprehensive Ethics Reform Amendment Act of 2011, D.C. Official Code § 1-1163.34a:

The contractor has self-certified, via the Bidder Offeror certification form, to not violate section
334a of the Board of Ethics and Government Accountability Establishment and Comprehensive
Ethics Reform Amendment Act of 2011, D.C. Official Code § 1-1163.34a; and they will not be in
violation of section 334a of the Board of Ethics and Government Accountability Establishment and
Comprehensive Ethics Reform Amendment Act of 2011, D.C. Official Code § 1-1163.34a.

(P) The status of the proposed contractor as a certified local, small, or disadvantaged business
enterprise as defined in the Small, Local, and Disadvantaged Business Enterprise
Development and Assistance Act of 2005, as amended; D.C. Official Code § 2-218.01 et seq.:

The contractor is not a District certified local, small, or disadvantaged business enterprise.

(Q) Other aspects of the proposed contract that the Chief Procurement Officer considers
significant:

None.

(R) A statement indicating whether the proposed contractor is currently debarred from providing
services or goods to the District or federal government, the dates of the debarment, and the
reasons for debarment:

The contractor is not currently debarred from providing services to any government entity. The
contractor does not appear as an excluded party on the District Excluded Parties List and the
Federal Excluded Parties List.

(S) Any determination and findings issues relating to the contract’s formation, including any
determination and findings made under D.C. Official Code § 2-352.05 (privatization
contracts):

5

Determination and Findings for Contractor Responsibility
Determination and Findings for Price Reasonableness
Determination and Findings for Multi-year contract
Determination and Findings for Contract Exceeding Five (5) Years

(T) Where the contract, and any amendments or modifications, if executed, will be made
available online:

http://ocp.dc.gov

(U) Where the original solicitation, and any amendments or modifications, will be made available
online:

Not applicable
1101 4th Street, SW
Washington, DC 20024
Date of Notice: September 30, 2025 L0014996343Notice Number:
FEIN: **-***2964
Case ID: 18720986

Government of the District of Columbia
Office of the Chief Financial Officer
Office of Tax and Revenue
MODAXO TRFFIC MNGEENT USA INC.
1110 CONTINENTAL PL NE
CEDAR RAPIDS IA 52402-2037

Branch Chief, Collection and Enforcement Administration
Authorized By Melinda Jenkins
To validate this certificate, please visit MyTax.DC.gov. On the MyTax DC homepage, click the
“Validate a Certificate of Clean Hands” hyperlink under the Clean Hands section.
CERTIFICATE OF CLEAN HANDS
As reported in the Clean Hands system, the above referenced individual/entity has no outstanding
liability with the District of Columbia Office of Tax and Revenue or the Department of Employment
Services. As of the date above, the individual/entity has complied with DC Code § 47-2862, therefore
this Certificate of Clean Hands is issued.
TITLE 47. TAXATION, LICENSING, PERMITS, ASSESSMENTS, AND FEES
CHAPTER 28 GENERAL LICENSE
SUBCHAPTER II. CLEAN HANDS BEFORE RECEIVING A LICENSE OR PERMIT
D.C. CODE § 47-2862 (2006)
§ 47-2862 PROHIBITION AGAINST ISSUANCE OF LICENSE OR PERMIT
1101 4th Street SW, Suite W270, Washington, DC 20024/Phone: (202) 724-5045/MyTax.DC.gov

COPY
GOVERNMENT OF THE DISTRICTOF COLUMBIA.
DEPARTMENT OF MOTOR VEHICLES
xk
aes
sea]
MEMORANDUM
To: NancyHepemanChiefProcurementOfficer
OficeofContractingandProcurement

From: ShaniquaRien 2 KecharconBudgetOfficer20" inaizzevarmoe
DepartmentofMotorVehicles‘OCFO~GovernmentServiceCluster
Date: September3,2025
‘Subject:FundingCertification-TicketProcessingContract(Mut-YearExemptfromCompetition)
Contractor| ModaxoTrafficManagementUSA,IncContractNo:_#CW124879

‘ThismemorandumoetifiesthattheDepartmentofMotorVehicleshasrequestedbudgetauthorityforFY2026tofundyear1oftheTicketProcessingcontract(#C1/124879)andwillsubsequentlyrequestbudgetauthorityforfiscalyears2027-2030throughtheannvalbudgetformulationprocess.
Themulti-yearexemptfromcompetitioncontractcrossesfiscalyearsbeginningSeptember29,2025andendsSeptember28,2030foratotalamountof$100,457,950.38.Thecontractamountsperyearareasfollows:

PricingforServices: “Amount
Yeart $20,884,542.85)
Year2 $19,953,428.22Year3 $19,070,421.61
Year4 $19,873,353.43,Years $20,676,204.29,
Total '$100,457,950.38
‘Allbudgetsaresubjecttoappropriationforeachfiscalyear.
‘TheproposedcontractsconsistentwiththefinancialplanandbudgetadoptedinaccordancewithD.C.code
{§47-392.0and§47-392.02,
youhaveanyquestionsorrequireadditionalinformation,pleasecallShaniquaRichardsonviaMSTeams.oremailatshaniquarichardson@dc.gov.
95M Street,SW,Suite300,Washington,DC20024~202-727-2200

GabrielRobinson,AgencyDirector-DMVWandaButler,AdudicatonAdministrator-DMVKarenTate,QualityProgramOfficer-DMVLLaChelleBurr,AgenoyFiscalOfficer-DMVDerrickWhite,ChiefContractingOfcer-OCPHeatherReynolds,SupervisoryContractSpecialist-OCPCamileChristian,SupervisoryContractSpecialist~OCP
95M Street,SW,Suite300,Washington,DC20024-202-727-2200

400 6th Street NW, Suite 9100, Washington, DC 20001 (202) 727-3400

GOVERNMENT OF THE DISTRICT OF COLUMBIA
Office of the Attorney General

ATTORNEY GENERAL
BRIAN L. SCHWALB

Commercial Division

MEMORANDUM

TO: Tomás Talamante
Director
Office of Policy and Legislative Affairs

FROM: Robert Schildkraut
Section Chief
Government Contracts Section

DATE: September 25, 2025

SUBJECT: Approval of Multiyear Contract for Ticket Processing, Adjudication, and
Administration System
Contractor: Modaxo Traffic Management USA, Inc.
Contract Number: CW124879
Contract Amount: NTE $100,457,950.38

This is to Certify that this Office has reviewed the above- referenced Contract and that we have
found it to be legally sufficient , contingent upon the following being submitted and reviewed by
this Office: (1) Final Contract, as approved by this Office on September 25, 2025, executed by
Modaxo; (2) Revisions to the D&F for Price Reasonableness; (3) Insurance documents in
compliance with Section I.8 of the Contract; and (4) Execution of the Determination and Findings
for Contract Exceeding Five Years.

If you have any questions in this regard, please do not hesitate to call me at (202) 724-4018.

______________________________
Robert Schildkraut

SOLICITATION, OFFER, AND
AWARD
1. Caption Ticketing System Page of Pages
1 80
2. Contract Number
CW124879
3. Solicitation Number
Doc728691
4. Type of Solicitation
Sealed Bid (IFB) Sealed
Proposals (RFP)
Exempts from Competition
Emergency
5. Date Issued
7/12/2024
6. Type of Market
Open
Set Aside
Open Market with Set-Aside
CBE Designated Category
7. Issued By 8. Address Offer to:
Office of Contracting and Procurement
200 I St., SE, 5th Floor
Washington, DC 20003
Office of Contracting and Procurement
441 - 4th Street, N.W., Suite 700 South
Washington, D.C. 20001
NOTE: In sealed bid solicitations, “offer” or “offeror” means “bid or “bidder.”
SOLICITATION
9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be via electronic format via the online solicitation software l
2:00 p.m. local time October 11, 2024 _
(Hour) (Date)
CAUTION: Late submission, Modifications, and Withdrawals: See 27 DCMR chapters 15 & 16 as applicable. All offers are subject to all terms & conditions contained in the solicitation.
10. For Information
Contact
A. Name B. Telephone C. E-mail Address
Karen Campbell-Tate
(Area
Code)
202
(Number)
719-0694
(Ext)
Karen.Tate@dc.gov
11. Table of Contents
(X) Section Description Page
No.
(X) Section Description Page No.
PART I – THE SCHEDULE PART II – CONTRACT CLAUSES
X A Solicitation/Contract Form 1 X I Contract Clauses 62
X B Supplies or Services and Price/Cost 2 PART III – LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
X C Specifications/Work Statement 14 X J List of Attachments 80
X D Packaging and Marking 47 PART IV – REPRESENTATIONS AND INSTRUCTIONS
X E Inspection and Acceptance 48
X K
Representations, certification, and other
statements of offerors X F Deliveries or Performance 49
X G Contract Administration Data 50 X L nstructions, conditions & notices to
fferors
X H Special Contract Requirements 55 X M Evaluation factors for award
12. In conjunction with the above, the undersigned agrees, if this offer is accepted within 120 calendar days from the receipt
of the offers specified above, to furnish any or all items upon which prices are offered at a price set opposite each item, delivered at the designated point(s), within the
time specified herein.
13. Discount for Prompt Payment
10 Calendar days % 20 Calendar days
%
30 Calendar days % Calendar days %
14. Acknowledgement of Amendments (The
offeror acknowledges receipt of amendments to
the SOLICITATION):
Amendment
Number
Date Amendment
Number
Date
15A.
Name and Address
of Offeror
Modaxo Traffic Management USA Inc.(“Contractor”)
750 First Street NE Suite 1060
Washington DC 20002
16. Name and Title of Person Authorized to Sign Offer/Contract
15B. Telephone 15 C. Check if the remittance
address is different from the above
– Refer to section G
17. Signature 18. Date
(Area Code) (Number) (Ext)
AWARD (TO BE COMPLETED BY GOVERNMENT)
19. Accepted as to Items Numbered 20. Amount 21. Accounting and Appropriation
William Delaney Chief Executive Officer
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
9/26/2025
2
CW124879 – Ticketing System

2. Name of contracting Officer (Type or Print) 23. Signature of Contracting Officer (District of Columbia) 24. Award Date
Government of the District of Columbia Office of Contracting & Procurement
SECTION B: CONTRACT TYPE, SUPPLIES OR SERVICES AND
PRICE/COST

B.1

B.2
The Government of the District of Columbia, through the Office of Contracting and
Procurement, on behalf of the Department of Motor Vehicles (DMV) (the District) required the
continued services of Modaxo Traffic Management to provide ticket processing and related
services. The period of performance is from October 16, 2025, through October 15, 2030 This
is a Multi-Year Exempt from Competition contract; the base year will be for the total five
years and three additional option years.

The District contemplates the award of a requirement contract with a cost reimbursement,
requirement component, and hourly rate in accordance with 27 DCMR Chapter 24.

B.3 The District will purchase its requirements of the articles or services included herein from the
Contractor. The estimated quantities stated herein reflect the best estimates available. The estimate shall
not be construed as a representation that the estimated quantity will be required or ordered or that
conditions affecting requirements will be stable. The estimated quantities shall not be construed to limit
the quantities which may be ordered from the Contractor by the District or to relieve the Contractor of
its obligation to fill all such orders:

a) Delivery or performance shall be made only as authorized in accordance with the price
schedule. The District may issue orders requiring delivery to multiple destinations or performance
at multiple locations. If the District urgently requires delivery before the earliest date that delivery
may be specified under this contract, and if the Contractor does not accept an order for the
accelerated delivery, the District may acquire the urgently required goods or services from another
source.
b) There is no limit on the number of orders that may be issued. The District may issue orders
requiring delivery to multiple destinations or performance at multiple locations.
c) Any order issued during the effective period of this contract and not completed within that period
shall be completed by the Contractor within the time specified in the order. The contract shall
govern the Contractor's and District's rights and obligations with respect to that order to the same
extent as if the order were completed during the contract's effective period, provided that the
Contractor shall not be required to make any deliveries under this contract after expiration.
B.4 PRICE SCHEDULE – REQUIREMENTS

The fixed unit price shall be fully loaded and include all costs, wages, benefits, overhead, general and
administrative expenses, and profit.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
3

Pricing Overview
The details below take into consideration the District’s request regarding references to the CLINs, Totals
by Year and 5 Year Base Total as well as the staffing alignments.
Project Resources
As part of the staffing alignments, Contractor has agreed to remove the second technical support team
member from the project scope. Today, the DMV staffing level currently comprises of 78 team
members excluding ATE staff. In the event that the DMV staffing increases to 90 or greater Contractor
will add a second technical support position and the price per ticket will increase by $0.02 per ticket.
Also, as part of the contract, the requirement to have a team member onsite at L’Enfant Plaza during
normal business hours will be amended to denote that Contractor’s team members will support the
DMV Offices during normal business hours. As such, it is understood that the team member(s) may
support L’Enfant Plaza remotely while onsite at another DMV location.
Section V. Pricing Considerations
Costs Included within the Core Services
Software Licenses and Usage for the term of the contract for:
o eTIMS®
o CiteWeb®
o Data Warehouse
Network and communication services necessary to support L'Enfant Plaza
Direct Costs - District to reimburse Contractor at cost for:
Postage for all mailings
Fees charged by state motor vehicle agencies for names and addresses of out-of-state violators,
excluding fees to obtain names and addresses relative to any ticket assigned to the Contractor for
delinquent collections.
SMS Text Messaging
District will Reimburse Contractor at cost plus 12% for
Workstations, monitors, keyboards, mice, scanners, check verifiers, and printers
Network and communications support for additional sites
Network cabling for workstation connectivity at existing or additional sites
Pricing Assumptions
Flat monthly fee, per p rocessed ticket, per warning notice, and SMS Text Messaging pricing will
increase by 5% annually, beginning in the 13th month after contract execution
Software Development and Comprehensive Data Science and Insights pricing will increase by 2.5%
annually, beginning in the 13th month after the contract execution.
Pricing assumes a 5-year base term and three (3) one (1) year extension options, for a total of eight (8)
years
All ticket volumes are based on the District’s estimated volumes of 5,362,503 tickets issued per year and
20,000 ATE warning notices issued per year.
All Postage and DMV Fees are based on the District’s estimates.
All software development and comprehensive data science and insights change orders will be billed in
the month upon completion.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
13

Certain District Government Buildings and Offices, dated April 14, 2022, and all substantially similar
mask requirements including any modifications to the Order, unless and until they are rescinded.
B.8 NONPROFIT FAIR COMPENSATION ACT OF 2020, D.C. Code § 2-222.01 et seq.

B.8.1 Nonprofit organizations, as defined in the Act, shall include in their rates the indirect costs incurred in
providing goods or performing services under this contract pursuant to the nonprofit organization's
unexpired Negotiated Indirect Cost Rate Agreement (NICRA). If a nonprofit organization does not have
an unexpired NICRA, the nonprofit organization may elect to instead include in its rates its indirect
costs:
(1) As calculated using a de minimis rate of 10% of all direct costs under this contract;
(2) By negotiating a new percentage indirect cost rate with the awarding agency;
(3) As calculated with the same percentage indirect cost rate as the nonprofit organization
negotiated with any District agency within the past two years; however, a nonprofit organization
may request to renegotiate indirect cost rates in accordance with 4.5.2 or
(4) As calculated with a percentage rate and base amount, determined by a certified public
accountant, as defined in the Act, using the nonprofit organization's audited financial statements
from the immediately preceding fiscal year, pursuant to the OMB Uniform Guidance, and
certified in writing by the certified public accountant.
B.8.2 If a federal agency funds this contract, indirect costs shall be consistent with the requirements for pass-
through entities in 2 C.F.R. § 200.331 or any successor regulations.
B.8.3 The Contractor shall pay its subcontractors and nonprofit organizations the same indirect cost rates as the
nonprofit organization subcontractors would have received as a prime contractor.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
14

SECTION C: SPECIFICATIONS/WORK STATEMENT

C.2 APPLICABLE DOCUMENTS

The following documents are applicable to this procurement and are hereby incorporated by this
reference:

Item
No.
Document
Type
Title Reference Site for
Document
Date
1 Standard Office of the Chief
Technology
Officer (OCTO)
Security Standards
and Procedures
Manual
https://octo.dc.gov/itpoli
cies

2 Publication NIST Special
Publication 800-53
https://csrc.nist.gov/publ
ications/detail/sp/800-
53/rev-5/final

3 Policy OCTO IT
Standards
https://octo.dc.gov/servi
ce/it-standards

4 Configuration
Management
Policy | octo
OCTO
Configuration
Management Policy
https://octo.dc.gov/publi
cation/configuration-
management-policy

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

Term Definition
Adjudication Services A DMV service center that is used primarily for customers to settle tickets either by
having a hearing or paying the ticket
Appeal When a customer challenges the initial ruling on a ticket, certain criteria must be met
for a customer to be eligible for an appeal.
Badge Number Each issuing officer is assigned an identifier, which can contain letters and numbers.
The badge number is used for identification purposes but may be reissued within an
agency and replicated across agencies.
Bankruptcy A legal proceeding ordered by a court occurs when an individual or organization
becomes insolvent and cannot pay creditors.
Batch A group of tickets bundled for processing, typically not exceeding 200 tickets
Batch Notices Refers to a group of like notices bundled to be mailed simultaneously, typically
identified by a notice batch number.
Batch Processing The transmission of a group of data records via an electronic interface
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
15

Booting When DPW immobilizes a vehicle that has violated District laws and meets established
criteria
Business Day All non-holiday weekdays, Monday through Friday, that the District is open for
business

CAD Number
A unique number that identifies an officer from a ticket-issuing agency within the
District or federal government. For MPD, this is a four-digit code and for other issuing
agencies, it is a six-digit code that combines the two-digit issuing agency and the
officer’s badge number.
Clean Hands Law
A law that stipulates that the DMV will put a stop on the driver's license or vehicle
registration and not allow the customer to conduct transactions with the DMV if the
customer has overdue tickets or other unpaid obligations to the District
Computer-Aided
Dispatch (CAD) A computer system used by DPW for booting, towing, and impoundment services
Correspondence Letters received from citizens or companies related to their tickets or accounts
Courtesy Tow When a DPW enforcement vehicle moves a customer’s vehicle to a new location when
the vehicle is not in violation of a law
Customer An individual or organization that interacts with DMV, DDOT, DPW, MPD, or other
issuing or associated agencies
Defendant A customer who is contesting his or her liability for a ticket
Department of Motor
Vehicles (DMV)
The District agency that develops, administers, and enforces vehicular laws for the
public to ensure public safety through the safe operation of motor vehicles
Department of Public
Works (DPW) The District agency conducts activities related to issuance and enforcement.
Department of
Transportation
(DDOT)
The District agency conducts activities related to transportation, meters, and issuance.

DESTINY
The DMV enterprise system that supports driver requirements, including permit
issuance, permit control, driver records, and medical review; vehicle requirements,
including vehicle information tracking, title issuance, registration, inspection,
insurance, parking permit management, and dealer management; and other operational
requirements including service via telephone, internet, and mail; financial transaction
processing; stop processing; material inventory management; administrative functions;
and system interfaces. The ticket processing system will need to interface with
DESTINY.
Disposition A final decision that ends an adjudication proceeding by a judgment of acquittal or
dismissal or which sets the fine or penalty.
Driver’s License
Number (DLN) A unique number is included on each license issued to drivers by the DMV.
Enforcement Activity The booting, towing, or impoundment of eligible vehicles
Entity Something to which tickets, penalties, and fees are tied. An entity could be a customer
or a vehicle plate.
Escaped Boot An enforcement boot that a customer has illegally removed from their vehicle.
Fleet Program A program that allows organizations that own more than five vehicles, such as
businesses or government agencies, to adjudicate and pay tickets all at once.
Group Processing The payment or adjudication of multiple tickets under separate vehicle plates or
drivers’ records.
Hearing A legal proceeding in which an examiner hears a customer’s case to determine liability.
Hearing Examiner The presiding official during a hearing.
Hearing Record A document that contains a hearing examiner’s decision on the liability for a ticket that
was issued or associated fees.
Images Visual information, such as a photo from a traffic camera or a copy of a ticket.
Installment Payment
Installment Payment
Plan (IPP)
A plan that allows customers who meet established criteria to pay their tickets off in
increments rather than all at once.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
16

Lockbox Where customers send their payment for tickets, the lockbox will need to interface
with the ticket processing system.
Low Number Tag A District license plate that has a plate number between 1 and 1250. These plates are
issued to associates of the Mayor and City Council members.
License Plate
Recognition System
(LPRS)
A system that can capture photographic video or images from license plates and
transform the optical data into digital information in real-time
Malfunction
The material failure of the TASS system or application to perform in accordance with
its agreed-upon technical specifications, resulting in a loss of previously delivered
functionality.
Meter Check A service performed where DDOT checks the status of a meter after a customer has
filed a complaint for receiving a ticket at a parking meter.
Metropolitan Police
Department (MPD)
The primary police agency in the District of Columbia, responsible for issuing parking
and moving tickets and for automated traffic enforcement, including red-light
enforcement, speeding enforcement, gridlock enforcement, height restriction
enforcement, and speed on-green restriction enforcement
Moving Tickets Tickets that have been issued because of moving violations.
Mobile Data Terminals
(MDT)
A computerized device used on mobile devices, laptops or tablets that are designed to
be used in the field by authorized personnel to communicate with a centralized control
system.
New Ticket A ticket that has been issued and has not aged to the status of an overdue ticket.
National Crime
Information Center
(NCIC)
A system used for law enforcement purposes
Nixie A letter or parcel that is undeliverable by the post office because of a faulty or illegible
address.
National Law
Enforcement
Telecommunications
System (NLETS)
A system used to obtain name and address information for vehicle registrations and
driver’s licenses.
Notice of Infraction
(NOI)
A ticket written to a vehicle or motorist in violation of DCMR Title 18 or 31 parking or
moving regulations. Also referred to simply as “tickets” in this document.
Overdue Tickets Tickets that have not been paid within a set amount of time and have incurred
penalties.
Parking Tickets Tickets that have been issued to enforce parking regulations.
Penalty An amount of money equal to the fine that is added to a ticket after it has become
overdue.
Photo Tickets A violation that is issued to a plate by a traffic camera.
Plate Number The combination of numbers and letters appears on a vehicle’s license plate.
Photo warning ticket
A photo enforcement ticket with zero dollars due, typically issued during a 30-day
warning period established to notify citizens in advance of a scheduled live
enforcement deployment.
Production Date The date a production notice is created.
Production Notice Includes but is not limited to decision letters, hearing records, late notices,
correspondence, and compliance notices.
Queue number
A number that is generated for customers who are placed into a queue when they arrive
at DMV centers. This number is created outside the ticket processing system but may
be manually entered into the system for identification purposes.
Real-Time The instantaneous upload and update of files and information.
Registered Out-of-
State Automobile
(ROSA)
A program designed to identify and ticket vehicles that are not registered in the District
but are parked overnight on District streets.
Report Documents or files that are created in Business Objects and are designed to include
selected information from the ticket processing system.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
17

Scofflaw A driver or vehicle that has accumulated multiple unsatisfied tickets.
Seizure Activities Booting, towing, or impounding of a vehicle
Skeleton Record An entry is created whenever the issuing officer has not submitted the real ticket, and
customers take action to settle the ticket.
Soldiers and Sailors
Act
States that members of the armed services have a valid excuse for missing adjudication
hearings at DMV.
Suspend Code A code that creates or stops action on a ticket.
Table
A file that can be changed and updated contains the necessary information for various
procedures and provides information that will be populated to appropriate fields as
tickets are processed.
Template
A standard document that is used to create an official notice that is given or sent to
customers. Most templates will have fields that are populated by information in the
ticket processing system.
Tickets Notices that are written to either customers or plates for photo, parking, or moving
violations. Also referred to as Notices of Infraction (NOIs) in this document.
Ticket Processing
System
A system for the capture, update, and storage of ticket data and associated images and
transactions.
Total Amount Due The total monetary amount a customer owes, including tickets, penalties, and fees.
Towing A tow truck moves a vehicle from one location to another. There are two types of
towing: courtesy tows and tows for seizure and enforcement activities.
Traffic Adjudication
Appeals Board
(TAAB)
A group of three individuals that hear and decide appeal cases.
User Acceptance
Testing (UAT) Testing was performed by the users after beta testing by the Contractor.
User Any authorized representative from the District government to use the System in the
designated manner.
Vehicle Identification
Number (VIN) A unique number that each automobile has is used for identification purposes.
Violation
Occurs whenever a customer acts outside District laws, such as when a driver runs a
red light. Violations fall into three main categories: parking, photo enforcement, and
minor moving. Ticket fines vary according to the violation.
Washington Area Law
Enforcement System
(WALES)
A system developed by the Metropolitan Police Department as a front-end to NCIC
and NLETS to maintain all the District’s arrest and criminal history information and
provide access to gun and property registrations.
Walk-in Hearing It is a type of adjudication hearing where customers walk into the DMV service center
to seek a hearing of their tickets.
Central Name and
Address Acquisition
System (CAAS)
Database for driver information and owner registration data from all 50 states, the
District of Columbia, Canadian and Mexican provinces, and the US State Department,
which shall be attained via electronic interface with a national law enforcement
database.

C.4 BACKGROUND
The current Ticket and Adjudication Services System (“TASS”)operates as a Hosted Web-Based
Solution, and some functionality may require components to be installed on individual computers
(Desktops or Laptops). Modifications have evolved to extend functionality to meet the district's
specific requirements.
The District is seeking to maintain its current Ticket and Adjudication Services System (“TASS”)
system for ticket processing and adjudication services while bolstering its foundational soundness and
modernizing certain aspects, including near real-time data via management dashboards. DPW, MPD,
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
18

DDOT, and more than 20 other District and federal agencies in the District of Columbia issue tickets,
including but not limited to parking, moving, and photo-enforced violations. Notices of Infractions
(NOIs, i.e., tickets) are issued to motorists and vehicle registered vehicle owners violating District
traffic laws and regulations. More than 4,000,000 tickets are issued annually.
The current ticket processing system comprises six high-level processes:
1. Issue Tickets – Describes the District’s ticket life cycle, including receiving ticket data from various
sources, 3rd Party handheld ticketing devices, 3rd Party photo enforcement tickets loaded and processed
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

within Cite Web, and manually keyed paper tickets, integration of meter information to be provided by
the District’s DDOT, integration with the District’s Central Name and Address Acquisition System,
registration of out of state vehicles, and related back-office/administrative support services.

2. Process Payments—Describes District processes for in-person payment, payment methods, adjustments
to payments, ticketholder bankruptcy-related processes, the District’s Fleet Program, handling of
payments where a single transaction applies to multiple tickets, integration of installment payment plans
summary data from a third-party collection agency, archiving of payment records, and related back-
office/administrative support services.

3. Adjudication Tickets – Describes District processes for scheduling adjudication hearings, hearing intake,
the adjudication of tickets and fees, handling reconsiderations or appeals after adjudication, the
adjudication use of image/document/audio/video evidence, and supporting reporting requirements.

4. Process Ticket-Related Liens – Describes the booting, vehicle seizure, and impoundment process for
eligible vehicles.

5. Manage Ticket-Related Correspondence – Describes District processes for handling incoming ticket-
related correspondence, outgoing notifications, customer internet account procedures, and related back-
office/administrative support services.

6. Process User-Driven System Updates—Describes District processes related to the ticketing and
adjudication system's ability to handle user-defined parameters that conditionally affect business rule
logic or system workflow.
DMV desires to implement the foundational review and system enhancements with an agile, phased approach
to address existing shortfalls, accelerate the delivery of Ticket and Adjudication Services System (“TASS”)
capabilities, and establish an affordable investment profile that benefits the project's overall implementation
schedule. The District suggests a minimum of three (3) phases for optimum benefit to the overall project
schedule and simplicity of project management functions.

C.5 REQUIREMENTS
The Ticket and Adjudication Services System (“TASS”) shall be able to handle various ticket life cycle
functions, including point-of-sale Transactions at a DMV Service Centers, online transactions by customers,
and a mobile app integration for customers/authorized users.
The Contractor shall provide and maintain the existing Ticket and Adjudication Services System (“TASS”),
processes, interfaces, and ancillary support programs that exist today, Attachment A1 Ticket and Adjudication
Services System (“TASS”)and Functional Requirements, to manage critical ticketing and related transactional
data, images, video, and other ancillary files in an environment that allows real-time inputs and outputs to
different District agencies that rely on the accuracy and timeliness of this information.
The Ticket and Adjudication Services System (“TASS”) shall integrate seamlessly with other systems from other
District agencies. The TASS shall provide real-time updates and periodic batch (FTP) updates from the
Metropolitan Police Department (MPD), Department of Public Works (DPW), District Department of
Transportation (DDOT), and other agencies.

The Ticket and Adjudication Services System (“TASS”) shall interface with DESTINY, the District’s driver and
vehicle information system, including Destiny point of 1s8ale, Destiny Mobile, and Destiny Online, in real-time/
batch. The TASS shall be available for
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
19

uninterrupted operation to internal and external customers as per the DMV-published service center and the
website times as posted at the time of this solicitation.
TASS shall support ticket processing requirements and Adjudication Services’ needs. The Contractor’s TASS
and capabilities shall enable the District and federal agency partners and customers to do the following:
a. Provide a ticket processing system that is efficient and user-friendly.
b. Offer customers multiple ways to pay and adjudicate tickets.
a. Payments:
i. In Person
ii. Online
iii. District’s Mobile App Integration
iv. Mail
v. Phone
b. Adjudication
i. In Person
ii. Virtual (Using the District’s Online Meeting Service (i.e., Webex)
iii. Online
iv. Mail
c. Provide up-to-date information on new violations, personnel, and equipment issues, such as an officer’s
availability for hearings. Maintain officer calendars, allow updates to calendars in real-time, and
calculate impact in near real-time.
d. Integrate with DDOT meter information once an API is available
e. Maintain up-to-date and accurate information on customers, vehicles, tickets, and fees.
f. Enable customers to perform many transactions online, mobile, by phone, or by mail.
g. Provide electronic access to evidence for hearing examiners, customers, and ticket-issuing officers.
h. Provide the capability to allow hearing examiners and others to hold hearings over the Internet/Intranet,
to conference pertinent parties for meetings, and to include sharing of documents and images.
i. Perform real-time data and batch transfers to and from other District and federal District agencies, such
as Ticket Data, Payment Information, and Collections Information.
j. Provide im ages, audio, and video of all documents, transactions, hearings, and any other documents
associated with a case or ticket.
k. Provide a central repository for all ticket-related data, images, video and audio files, and transactions so
that agencies, citizens, media, and other interested parties can easily input, receive, and access this
information in a secure data center environment.
l. Increase transparency of ticket-related information to take advantage of data mapping and analysis of
core and ancillary data.
m. Support integration with the District’s mobile phone application development using newly accessible
data.
n. Meet and support business rules and District regulations.

During the Discovery phase, the District will coordinate with the Contractor to perform a foundational review
of all aspects of the TASS. The Discovery phase shall include a software requirements analysis for the existing
applications, including a User Portal that will provide access to all TASS Services.
If new functional and technical requirements are identified during the Discovery phase, the Contractor shall
document them and determine if and how it can meet the additional requirements. The Contractor shall present
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
20

the solution(s) to the District, who shall review them for final approval and change order processing in advance
of the Implementation phase.
The District and Contractor have worked to identify new dashboards for the DMV Adjudication Director. We
propose to continue this development for the DMV and can expand this to ATE as desired.
Concurrent to the Discovery Phase shall be an Initial Implementation Phase, during which the new features and
enhancements included within the Contractor’s scope of work shall be deployed, as outlined in Section C.7.3
System Engineering, Design, and Development. The Initial Implementation Phase will consist of multiple agile
three-month project increments.
A Second Implementation Phase may occur after the completion of the Discovery and Initial Implementation
Phases, dependent upon the requirements that may have been identified during the Discovery Phase.
C.5.1.2 The Contractor shall provide innovative and unique additions to the existing system as follows:

a. Improve the User Interface/User Experience (UI/UX)
b. New User Interface – User Experience (UI/UX)
c. Fewer clicks
d. Intuitive, easier to navigate
e. Action menus at the top of the page
f. Summary screen with new “carrot” feature
g. New icons to quickly navigate for specific functions like “adjust,” “pay,” and “blackout.”
h. Saved searches – last 10
i. View additional information without toggling out of the main screen
j. Enhance the adjudication and workflow application used by hearing examiners to include,
but not limited to:
i. Web-based hearing record templates to eliminate the need to update PCs and laptops
manually
ii. Create the ability for examiners to easily retrieve custom language for easy insertion
into the hearing record
iii. Expand the maximum character count in the decision boxes in Workflow and
Adjudication from 4,000 to 5,000 for Statement of Fact and Finding of fact
iv. Ability to track the number of completed cases in the workflow (end-of-day totals) or
a specific queue
k. Enhance Hearing support and Table functions to include but not limited to
i. Expand TASS code tables' long name description field for violation code names,
location, suspend code, and correspondence
ii. Enhance Search features – for quick search by keywords across all tables
iii. Automate the virtual hearing calendar so that hearing time slots are set and not
manually keyed for parking and photo enforcement tickets
iv. E-TIMS no tifications populate when inside an overdue ticket, or the ticket may
appear in a different color.
v. The ability to rearrange the screen with all of the ticket information after clicking the
ticket. DMV suggest one page, or one click that could display all of this information
on the same page.
vi. Cross reference addresses, plate numbers, and DLNs if a customer appears to have
had more than one
b. Utilize the latest generation software for reviewing photo-enforced violations
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
21

a. Migrate from version 3 to 5 with many new enhancements
b. New real-time integrations for Stolen Vehicles and Amber Alert
c. Advanced Search Capabilities
i. Narrow search parameters to find specific data easier
ii. Complete bulk updates
iii. View an event and go directly into the processing queue for that event
iv. Export search results for additional documentation.
d. Vehicle Registration History
i. Displays the various plate / state combinations, the dates of export and import, and
the number of times the event has gone to DMV for name, address, and vehicle
information.
e. Overall History
i. It displays a full audit trail of every touch or edit made on every event. History can be
used for adjudication purposes and exported in .csv, .pdf, and .xls.
f. Easier Administrative Functions for ATE
i. Add/Change User IDs
ii. Add/Change Locations
iii. Add/Change Notice Templates
g. New Screen Layout
i. The data thumbnail ribbon is easier to read, allowing the user to confirm the violation
immediately and increasing processing efficiency.
h. Filter
i. Pull up specific data in a queue for processing and use to train new team members.
i. Skip / VR Lookup
i. User can skip events, and the event doesn’t pop back into their queue for 30 minutes,
which increases processing efficiency.
ii. the user can update and send a new plate/state combination for name, address, and
vehicle information acquisition in every queue, increasing processing efficiency.
j. Video Playback / Image Editing
i. The video plays at 1/8, 1/4, 1/2, and double speed to allow the user to see the exact
point of violation for evidentiary purposes and for processing accuracy.
ii. Image editing, as needed, can be used to get a better plate crop by zooming in closer
or further out for better image quality, thereby increasing possible issuance.
k. QC Review
i. Staging area for new locations to be released and to confirm the integrity of the
deployment prior to releasing for processing
c. Offer dashboard and alerting functionality
a. Enhanced dashboard providing management visibility into the daily operations.
b. Key Reporting Components
i. Adjudications
1. Counts of Adjudications by Adjudication Type and Ticket Type
2. Pick List to view disposition undecided / upheld/dismissed/continued /
reconsiderations
3. Highlight Thresholds – if any of the cases are Near or Exceeding KPI
Thresholds, Highlight the cell yellow or red accordingly
4. Option to Select a relative timeframe for the Counts
a. Timeframe Options:
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

i. This Week
ii. This Month
iii. This Year
iv. Default timeframe to the prior timeframe selected by the user
(initial instance This Month)
ii. Adjudication Trend
1. Timeframe is associated with the timeframe on the Adjudication Component
2. Trend will show the current timeframe and prior five related timeframes (i.e.,
This Month will display This Month – 5, This Month – 4, This Month – 3,
This Month -2, This Month -1, and This Month in the trend. In the event This
Week or This Year is selected, the prior five related timeframes will be
displayed in the trend line).
3. Trend Line Filter on Ticket Type
iii. Appeals
1. Appeal volumes based on Appeal Date to Closure
2. Filter on Ticket Type (Parking, Moving, Photo)
3. Color Coding to Highlight Warning and Danger Counts based on the Age of
the Open Appeal
4. Goals for appeal processing need to be defined.
iv. Appeal Trend
1. The frame can be specified on the timeline, with the default being This Month
as the Appeal
2. Trend will show the current timeframe and prior five related timeframes (i.e.,
This Month will display This Month – 5, This Month – 4, This Month – 3,
This Month -2, This Month -1, and This Month in the trend. In the event This
Week or This Year is selected, the prior five related timeframes will be
displayed in the trend line).
3. Trend Line Filter on Ticket Type as the Appeals Filter specifies.
v. Issuance
1. Count of Citations loaded to eTIMS® by Ticket Type
a. Option to Select a relative timeframe for the Counts
i. Timeframe Opt ions:
1. This Week
2. This Month
3. This Year
4. Default timeframe to the prior timeframe selected by
the user (initial instance This Month)
vi. Payments
1. Value of Payments processed in eTIMS® Payment Process Date by Payment
Source
a. Option to Select a relative timeframe for the Payments
i. Timeframe Options:
1. This Week
2. This Month
3. This Year
4. Default timeframe to the prior timeframe selected by
the user (initial instance This Month)
vii. Issuance Trend 22
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

1. Timeframe is associated to the timeframe on the Issuance Component
2. Trend will show the current timeframe and prior 5 related timeframes (ie: This
Month will display This Month – 5, This Month – 4, This Month – 3, This
Month -2, This Month -1 and This Month in the trend. In the event This
Week or This Year is selected, the prior 5 related timeframes will be displayed
in the trend line).
3. Trend Line Filter on Ticket Type
viii. Payment Trend
1. Timeframe is associated to the timeframe on the Payment Component
2. Trend will show the current timeframe and prior 5 related timeframes (ie: This
Month will display This Month – 5, This Month – 4, This Month – 3, This
Month -2, This Month -1 and This Month in the trend. In the event This
Week or This Year is selected, the prior 5 related timeframes will be displayed
in the trend line).
3. Trend Line Filter on Ticket Type
ix. WorkFlow – Parking & Moving and WorkFlow – Photo
1. View of WorkFlow buckets with Color Coding to Highlight Warning and
Danger Volumes
2. Parking 61-90 Yellow, Above 90 Red
3. Photo 121-150, Yellow, Above 150 Red
x. WorkFlow – Parking & Moving and WorkFlow – Photo Trends
1. Timeframe is specified on the Trend Line and will default to This Month
2. Trend will show the current timeframe and prior 5 related timeframes (ie: This
Month will display This Month – 5, This Month – 4, This Month – 3, This
Month -2, This Month -1 and This Month in the trend. In the event This
Week or This Year is selected, the prior 5 related timeframes will be displayed
in the trend line).
xi. KPIs
1. M
easurement of Key KPIs utilized to monitor overall performance
2. If a KPI is close to defined limits, Color Coding to Highlight Warning and
Danger Percentages
3. KPI #3 (85% customers serviced within 40 mins) will require retrieving data
from outside of eTIMS® in order to provide the statistic
4. KPIs #1 (70% Park/Move process w/in 90 days), #2 (75% of Photo process
w/in 150 days), #4 (Decide 65% of Appeals) and #5 (28% Reversal Rate) can
be calculated from the information captured in eTIMS®
xii. Hear Exam (Hearing Examiners)
1. View of HEs processing the most cases for the selected timeframe
2. Selecting Disposition shows the Top 5 hearing examiners using the particular
Disposition for the selected timeframe
3. Option to Select relative timeframe for the cases
a. Timeframe Options:
i. This Week
ii. This Month
iii. This Year
b. Default timeframe to the timeframe selected by the user (initial
instance This Month)
xiii. Dispositions 23
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
24

1. View of Top Dispositions the selected timeframe
2. Selecting HE shows the Top 5 dispositions used by the particular HE for the
selected timeframe
3. Option to Select relative timeframe for the cases
4. Timeframe Options:
a. This Week
b. This Month
c. This Year
5. Default timeframe to the timeframe selected by the user (initial instance This
Month)
xiv. Reporting Drill Down – referencing details supporting the dashboard for further
review/analysis.
d. Improve workflow processing and adjudication subsystem
a. Updated look and feel to match the new eTIMS UI/UX
b. Search capability (queues, tickets, etc.)
c. Web-based templates
d. View and select tickets from the count button
e. View and unlock records if authorized
f. Bulk move and updates
g. Images readily available for processing
e. Enhance table maintenance
a. Updated look and feel to match the new eTIMS UI/UX
b. Search capability (type in)
c. Bulk updates/deletes
f. Enhance static reporting
a. Updated look and feel
b. Browser Agnostic
g. Offer an installment payment plan (IPP) integration with the Central Collections Unit (CCU)
h. Integrate stolen vehicle and amber alerts with the photo enforcement software
i. Single-Sign-On In tegration between the Contractor’s primary applications
a. Single Sign-On Integration and Role-Based Access Control
j. Enhance correspondence documents that are attached to a ticket record that detail the date, time, and
source
a. Improve display of relevant image information

C.5.1.3 The Contractor shall include up to 1,000 hours of new development per contract year at the direction of
the DMV for additional system changes, enhancements, or other Change Requests at no additional cost to the
District. Providing a built-in allowance of development hours will allow the DMV to respond to new technical,
legislative, or programmatic requirements over the life of the contract.

C.5.1.4 The Contractor shall include up to 200 hours of insights-as-a-service (i.e., data science). (Elaborate
Description)
C.5.1.5 The Contractor shall hold a kickoff meeting to start the project with the District’s teams 15 days after
the Contract award.
C.5.1.6 The Contractor shall provide a Project Management Plan (PM Plan) with a timeline for the Discovery
and Initial Implementation phases within 45 days of completion of the kickoff meeting. The discovery phase
shall include a review of the foundational soundness to achieve system optimization, efficiency, and reliability.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
25

The Implementation phase shall consist of the release of system enhancements. The project plan shall include a
detailed timeline, milestones, deliverables at each milestone, and the corresponding contractor’s resources that
will be assigned to perform the tasks. The PM plan shall provide the details of the specific techniques, tasks,
and procedures to be used for managing the performance of the contract, including but not limited to risk
management, quality control, performance management, schedule management, configuration audits, test and
evaluation, implementation management, security management, and training development.
A second implementation phase may be considered after the discovery phase has closed to address requirements
unearthed during the discovery phase.
C.5.1.7 Priority Back Office Functions

Provide PO Boxes and Manage
Mail
Provide and manage incoming
mail to PO Boxes 1030 (fleet),
1813 (photo), 37135
(correspondence), and 77411
(appeals), which arrive by
courier to be managed on
business days. We provide the
PO Box 2014 (payment) to Citi.
Mail is sorted and separated by
task.
Manage couriers to transport
incoming and outgoing mail.
Correspondence
classification/coding
Correspondence is received via
PO Box or DMV via Courier—
the process of reading and
assigning ticket-related
correspondence to an
appropriate ticket and queue.
The correspondence is then
scanned into PDF and indexed
in the ticket in eTIMS.
Ninety percent (90%) of the
correspondence for any day is
required to be scanned and
indexed to the correct ticket
and/or queue within 3 business
days to be compliant.
Manual ticket Processing Handwritten tickets are received
daily, and sorted into categories
(parking, moving, personal
services, warning, void);
Parking, moving, personal
services and void ticket
information is keyed and loaded
into eTIMS; ticket scanned and
indexed to the keyed data.
Warning ticket information
keyed and loaded directly into
the data warehouse;
Parking, moving and personal
services tickets to be keyed and
uploaded to eTIMS within 2
business days of receipt.
Imaging of parking, moving and
personal services tickets
uploaded within 3 business days.
Payment processing Payments received are sorted
from incoming mail and
forwarded to the District's
Payment Processor.
Payments to be processed within
1 business day
DMV Notifications (Compact
and Compliance Notification
processing)
Compact and Compliance
Notices are generated by Print
Vendor and are received at our
office for processing. The
notices are sorted and mailed to
the appropriate DMV.
Notices sent to DMV addresses
on a regular (weekly) basis
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
26

Non-Deliverable mail
processing (Nixie)
Non-deliverable (Nixie) mail is
returned to our office via
Courier. Each non-deliverable
address is noted in eTIMS as
"Nixie" status.
Nixie mail to be processed
regularly within 3 business days.
Fleet program administration
and fleet account management
The fleet program is
administered by our team
including new account setup,
helpdesk, plate addition and
maintenance, new fleet and
refresher training and payment
research.
Response to fleet requests for
new account within 1 business
day. Individual additional plates
to be added to account within 1
business day. User ID requests
to be completed in 1 business
day.
Table and Calendar maintenance
(HEs, violation code, Hearing
Schedule, etc)
Maintenance of customer
administrative table data such as
user ids and violation codes, as
maintaining calendaring for
hearings.
Goal of processing change
requests or response within 1
business day.
eTIMS Account Administration New user setup, permissions
management, and maintenance
and support.
Goal of processing change
requests or response within 1
business day.
Local support Provide onsite support of
equipment, systems, and
software at DMV L'Enfant
Location
One full time equivalent onsite
during office
Payment reconciliation Reconcile payments processed
for Harris, Citi, JPMorgan, and
Destiny.
Resolve (or respond to) issues
related to transaction of payment
files within 1 business day.
Integrated partner reconciliation Reconcile files sent by
Gtechna,Contractor (Citeweb),
and DMV (Destiny).
Resolve (or respond to) issues
related to upload of partner files
within 1 business day.
Freedom of Information Act
Requests
Provide report development and
data in support of FOIA requests
received by the DMV.
Provide report (or respond to)
request within 1 week.
Split Plate Maintenance Review of split plate reports and
consolidate according to
business rules.
Daily Task
DMV documentation storage
and archival
Maintain physical
documentation on behalf of the
DMV at Iron Mountain Storage.
Documentation is maintained
and retreived as requested in
compliance with the District's
Document Storage Policy.
Seed/Salt Notice verification Monitor and review daily
notices to confirm daily mail
processes.
Monitoring for a daily basis and
rolling up on a monthly review.
Q/A and Q/C Processes Q/A and Q/C of:
Handwritten Ticket Processing:
Level 1 - Quality check and
error correction of 10% (and at
least one ticket) of each batch.
Level 2—Quality Assurance
review of the Level 1 quality
process, including QC of 10% of
Level 1 inspection and
Daily Task
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
27

correction and identification of
quality trends.
Correspondence Processing:
Level 1 - Quality check and
error correction of 25% of the
daily correspondence.
Level 2 - Quality Assurance
review of quality Level 1 quality
process, including QC of 10% of
Level 1 inspection and
correction, and identification of
quality trends.

C.6 TASS Hosting Environments

C.6.1 The Contractor shall provide a hosted solution for the proposed TASS System/Platform. This solution
design shall account for underlying system infrastructure/platforms with security, reliability, and support for the
duration of this contract.
C.6.2 Development Environment(s)

The Development Environment shall be used for Contractor Component Development and Test activities,
which include software development and iterative test activities for unit testing.

C.6.3 Test Environment(s)
The Test Environment shall be used for System Integration and Test activities to ensure the individual functions
and all of their components that have been developed work together without degrading the system. These
activities include iterative testing such as Development Test (DT) Integration Tests and DT Regression Tests.
The Test Environment will also be used for Production Readiness Testing and the District's Operational Test. A
Pre-Production instance(s) within the Test Environment will test the TASS system using contractor-developed
materials and installation instructions before production deployment. The Pre-Production instance(s) uses the
same TASS interfaces and data for testing as the Production instance within the Production Environment. The
Pre-Production instance(s) will demonstrate the system's production readiness.
The unit testing-related documentation shall contain, for the system, the proposed test methodology and
acceptance criteria for each of the individual component test plans, test scenarios, negative testing, and test
sign-off documentation, among other key information, for successful management of the testing process.
The test planning documents shall include the system and integration test plans, which cover the dependencies,
testing methodologies, automated testing and manual testing processes, automated testing tools, test
management tools, test documentation, test plans, and test scenarios, resources, error handling, resolution
process, testing workflow, acceptance criteria, and all other key information for successful management of all
the testing life cycle.
C.6.4 Production Environment

The Production Environment is the environment upon which TASS will be deployed, operated, and maintained.
Test Data, application, and hosting instances used for testing are not permitted within the Production
Environment.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
28

C.6.5 Hosting Requirements
1. The Contractor shall provide a disaster recovery plan with details regarding the Contractor’s capabilities
and approach for business continuity, i.e., backing up and restoring data, reports, bank connections,
TASS interfaces, security protocols, and login procedures.
2. The Contractor’s TASS shall be SOC2 Type II compliant or ISO 27001 certified. The Contractor shall
provide their most recent SOC2 Type II or ISO 27001 report to the District upon contract award and
shall forward the annual SOC2 Type II report update or annual ISO 27001 certificate to the District each
year.
3. The Contractor shall attest that they contract with an independent vendor with relevant certification to
conduct quarterly penetration testing and have policies and procedures in place to ensure that all critical
test failures are remediated or mitigated by compensating controls. Once a year, the Contractor shall
provide the District with copies of the quarterly penetration testing results or an annual attestation of
successful penetration testing results, identifying any outstanding vulnerabilities and the corrective
action plan.
4. The Contractor shall provide documentation that both internal and external audits are conducted
annually.
5. The Contractor shall provide its response and contingency plan or policy to the following situations:
a. Downtime during standard business hours between 7 am and 6 pm for more than 2 hours.
b. An unrecoverable loss of data.
c. Inability to access the system or system errors preventing users from performing normal
system functions
d. Ability to recover and restore data within four business hours in the event of a system outage
lasting longer than two hours.
6. The Contractor shall describe its Recovery Point Objective (RPO) and Recovery Time Objective (RTO)
in its Service Level Agreement (SLA).
7. The Contractor shall provide its Service Level Agreement (SLA), which defines the performance and
other operating parameters within which the infrastructure will operate to meet the District’s
requirements.
8. The TASS uptime shall be 99% or greater. The Contractor shall provide documentation on their standard
uptime service and related Service Level Agreement (SLA) criteria.
9. The Contractor shall provide the infrastructure that supports its multiple data centers, each of which
suppor
ts redundancy, failover capability, and the ability to run large-scale applications independently in
case one data center is lost.
10. The Contractor shall provide the location of its primary and secondary data centers. If the distance
between the centers is less than 200 miles, the Contractor shall provide documentation of processes in
place to mitigate against the geographic closeness of the primary and secondary data centers to ensure
continuity of services to the District.
11. The Contractor shall provide the District with documentation annually confirming that system logs are
reviewed quarterly by Contractor management and an external auditor.
12. The Contractor shall provide affirmation that the data centers used for the TASS are within the
continental US and that all support services are performed within the continental US. If the Contractor
utilizes non-US facilities or support services, the Contractor shall provide documentation of the
conditions upon which non-US-based activities are employed.
13. The Contractor shall provide documentation indicating whether the District is hosted in a private cloud
or shared tenant environment and details on how the District’s data is safeguarded to prevent data co-
mingling.
C.7 CONTRACTOR PROJECT MANAGEMENT AND TECHNICAL REQUIREMENTS
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
29

The Contractor shall provide all the tasks per the price schedule and corresponding deliverables as agreed upon
with DMV in the Project Plan.
C.7.1 Project Management Organization
The Contractor shall assign a Project Manager who has the resources and authority to ensure efficient and
timely Project execution. The project manager shall be the primary point of contact for all work performed
under this contract. The Project Manager shall be prepared at all times to discuss with the District the status and
progress of delivering the requirements.

The Contractor shall designate key personnel who shall be responsible for the performance of the contract in
accordance with Section C.7.2, Project Staffing.
C.7.1.1 Control and Sta tus Reporting
The Contractor shall continuously monitor performance under this contract to provide the District with a timely
assessment of project progress, problems, or risks. The Contractor shall provide the District with a Monthly
Status Report that assesses the Project's progress, identifies problems encountered or foreseen, updates the
Project schedule and risks, and provides the status of any open action items assigned to the Contractor.

C.7.1.2 Post-Award Conference
The Contractor shall host and conduct a Post Award Conference (PAC) within fifteen (15) calendar days after
the contract award to ensure that both the Contractor and the District clearly understand the contract
requirements. Briefing materials shall be provided two (2) business days prior to the PAC.
C.7.1.3 Project Management Reviews
The Contractor shall conduct and administratively support Project Management Reviews (PMRs) to provide the
status of the technical, schedule, and cost of the TASS Project. PMRs shall be conducted monthly for the first
24 months after the contract award and bi-monthly after that. PMRs shall be conducted at a mutually agreed-
upon location. The Contractor shall provide briefing materials at least three (3) calendar days before conducting
the review. The Contractor format may be used for the PMR briefing materials. The PMR shall be conducted
after the monthly electronic submission of the CPR and IMS for the previous month.
Topics to be addressed at the PMRs include, but are not limited to, the following:
a. Major accomplishments since the last PMR
b. Expected major accomplishments prior to the next PMR
c. Review of actions from previous PMR
d. Status of software development, integration, and configuration
e. Status of test and evaluation activities
f. Contractor deliverables to be delivered within the following ninety (90) calendar days, the status of
deliverable reviews from the District, and the status of changes from the previous PMR
g. Schedule status, including identification of major drivers behind schedule variances and the action plans
to resolve these variances, if applicable.
h. Project financial status
i. Project risks and status of risk mitigation activities
C.7.1.4 Meetings, Reviews, and Conferences
The Contractor shall support weekly recurring meetings and reviews to discuss Project progress, identify
potential problems, and resolve identified issues. The Contractor shall ensure the participation of responsible
personnel at all meetings, reviews, and conferences. The Contractor shall prepare agendas, meeting minutes,
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
30

action item lists, and briefing materials for each meeting, review, and conference. The Contractor shall provide
an agenda two (2) business days prior to the start of each meeting unless a different notification is specified.
Meeting minutes and action item lists shall be provided at least three (3) business days after the completion of
each meeting unless a different notification is specified.

C.7.1.5 Quality Management
The Contractor shall establish and maintain a quality management system to ensure compliance with the
requirements of this contract. The Contractor shall require that sub-tier suppliers maintain a similar quality
system to achieve quality control of services and supplies provided. The Contractor shall use the seven quality
management principles identified in ISO 9000, International Organization for Standardization (ISO) Quality
Management Systems as a guide.

C.7.1.6 Risk, Issue, and Opportunity Management
The Contractor shall support the DMV management processes for risks, issues, and opportunities. The
Contractor shall participate in monthly joint DMV/Contractor risk meetings. The Contractor shall report on
medium and high-risk/issue items including the status of the associated mitigation plans during PMRs and
included in the Monthly Status Report. The Contractor shall describe how they will effectively approach risk
management in the PM Plan. The Contractor shall be able to quantify risks with respect to the impact on all
aspects of the management of this SOW.
C.7.1.7 Configuration Management
The Contractor shall establish and maintain a Configuration Management (CM) Project that details the
pro
cesses for identifying, controlling, and maintaining all elements of the TASS system. CM shall be conducted
in accordance with the Configuration Management Policy referenced in Section C.2, Applicable Documents.
C.7.1.8 Transition Pl an at Contract Expiration
Six months before the expiration date of the current contract, the Contractor shall begin a transition phase with
the District’s transition team, which will include representatives from the incoming vendor, the affected District
agencies, and the DMV. The Contractor shall provide support as needed to transition the database, images, etc.
to the new system, including the generation of export files in the Contractor’s standard format.
The Contractor shall develop and submit a transition plan to be used in the event of contract expiration or
termination of the contract. The Contractor shall submit the transition plan by the date on which production
operations commence according to the contract. The objectives of the transition plan design meetings are to:
• Minimize risk;
• Expedite implementation of the next vendor;
• Establish a structure to ensure proper control in the transition and implementation of new services;
• Develop testing and acceptance methodology for transition in conjunction with the District’s next
vendor;
• Define milestones and timetable; and
• Finalize reporting requirements and report delivery methods.
The conversion planning portion of the Transition Plan shall contain the methodology, sequence, impact on the
System development processes, and conversion development life cycle phases, along with all other pertinent
information for the successful management of conversion processes.
All software and perpetual licenses shall be provided to the District during this phase.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
31

C.7.1.9 Deliverable Approval Signoffs
In conjunction with delivery milestones and associated deliverables, Sign-Off documents formally acknowledge
and document the completion of requirements for the corresponding milestone. The major milestones requiring
a Sign-Off Document are a subset of the overall milestones.
C.7.2 Project Staffing
Key Personnel are defined as those critical to ensuring the success of TASS operations, the meeting of
performance metrics, and the adhesion to customer service standards.

The Contractor shall describe how it will handle the absence of any Key Personnel and whether one or more
staff will back up Key Personnel. The OCP Contracting Officer and DMV Contract Administrator must approve
the replacement of any Key Personnel. The Contract Administrator must be notified when Key Personnel are
out of the office for an extended period (more than two days). In these instances, the name and contact
information of the backup must be provided to the Contract Administrator before the absence of the Key
Personnel. Key personnel may be assigned to multiple functional tasks, but contractors must specify the
percentage of their time spent in what roles.
The Contractor’s Key Personnel or designee shall be available during regular business hours to coordinate with
the Contract Administrator.
The Contractor shall provide resumes for key personnel consisting of:
1. Account Manager who shall be onsite as needed.
2. PMP Certified Project Manager
3. Technical Program Manager
4. PMP Certified Program Manager Adjudication Services
5. PMP Certified Program Manager Photo Operations
6. Business Analyst
7. Technical Lead Photo Operations
8. On-site Support Technician
9. Technical Implementation Project Manager (1st 2 Years During Implementation / Upgrades)
10. Quality Assurance
The Contractor shall provide a proposed Organization Chart and Staffing Plan as part of the proposal for the
contract.
The District reserves the right to interview the proposed key personnel and either confirm the recommendation
or request resumes of alternate key personnel, including any future proposed replacements for key personnel.
The staffing plan should provide or address at a minimum:
a. The title/position for all staff to provide or support the delivery of the required services, including
monitoring and quality control activities.
b. The percentage of time each position shall spend in the delivery of the required services.
c. Indicate wh ether the staff position is onsite of offsite
d. The title/position for all information technology and development staff to provide or support the delivery
of the required development, quality assurance, and testing services.
The Contractor shall update the organization chart whenever the adopted staffing model changes for approval
by the Contract Administrator.

The District reserves the right to request a replacement of any Contractor team member at any time at the
District’s discretion. Under such circumstances, the Contractor shall replace the individual as soon as possible,
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
32

Doc737382 -T
icketing
but no later than four weeks after the request, with a replacement acceptable to the District and consistent w ith
the key personnel requirements s pecified h erein.
The Contractor shall ensure the performance is not adversely impacted while searching for a replacement.
All resources working at a DMV office location shall be within commuting distance of DC. Staffing r esources
supporting t he contract from r emote l ocations a re permitted, but work shall b e performed within t he United
States.
The Technical Implementation Project Manager shall report weekly on the status of the implementation
schedule, notify all parties of potential problems and risks, and shall document all events pertinent to the
implementation of the system including but not limited to meeting notes, emails, and any other relevant
communications.
Once the system is implemented, an important r ole of the Contractor's s upporting s taff shall be vetting customer
requests for Project ch anges t o ensure n o ancillary d amage or non -intended c onsequences w ill occur if that
change is implemented. Changes to the implemented system typically r esult from le gislative or programmatic
(policy) changes and m ay occur at any time during the base or option years and shall be governed b y the change
clause S ection I .12.
Clarifications:
As per the requirement for the key personnel, the Program Manager, the Program Manager Adjudication
Services and the Program Manager Photo Operations are to be PMP Certified positions. Contractor's existing
Program Manager, Matthew Hutman, is a certified PMP, Certification Number 2781896, obtained in July 2020
with an expiration date of July 2026. Contractor is also proposing Domencia Tyler and Paola Gonzalez-P igg,
for the Adjudication Services and Photo Operation roles, both Domencia and Paola are actively working on
obtaining their PMP certifications with the anticipated completion within 30 days of contract start date.
Contractor understands the District's idea of a Quality Control Manager and is consistently looking at our roles
and functions to ensure optimal services are being provided to the District.
Additionally, the Implementation Manager will support the program through the implementation period and no
hours f or operations staff a re included i n our implementation costs.
C.7.3 System Engineering, Design, and Development
C.7.3.1 Requirements Analysis
Two an
alyses (Part 1 and Pa rt 2) are required d uring the initial p roject Discovery P hase as proposed by the
contractor:
TASS System Design
The Contractor shall provide the TASS and conduct all development, i ntegration, t est, and deployment activities
in accordance w ith this SOW.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
33

Per the Contractor’s project schedule detailing timelines involved in various phases including any dependencies,
the Contractor shall perform the following application design activities during each of the proposed
implementation phases.
The contractor shall complete software development for all the interfaces specified and required for the system
based on the requirements, program specifications, procedures, design, mapping, completion of documentation,
standardization of reports, and security.

C.7.3.2 Design Reviews
C.7.3.2.1 Collaborative Design Workshops (CDW)
The Contractor shall organize, facilitate, and host structured Collaborative Design Workshops (CDW) to elicit
and clarify usability requirements, user scenarios, business rules, user interface needs, design preferences, and
user acceptance factors.

The Contractor shall define workshop session objectives and workshop facilitation approach and provide a
CDW agenda three (3) days before the start of the CDW. During each CDW, the Contractor shall facilitate
discussions and record outcomes. The Contractor shall provide facilitation tools, for example, user interface
forms/mockups, COTS prototype demonstrations, high-level workflow, and data diagrams, role-playing
scenarios, storyboards, and other techniques to promote the Contractor's understanding of end-user needs and
experiences and the end users' understanding of design options and limits. Human factors design guidelines
shall be consistent with the following standards and other documents:
a. 29USC 794D, the Rehabilitation Act Amendments (Section 508)
b. The current version of OCTO Ready-Set-Go: Guidance for Solution and Service Development.
The Contractor shall document the outcome of the CDW and provide a post-workshop summary report,
including action items, within seven (7) calendar days of its completion. The contractor shall include the status
of CDW action items in the Monthly Status Report (MSR).

C.7.3.2.2 Software Design Review/Software Design Description
The Contractor shall develop a Software Design Description and conduct a System Design Review (SDR) to
provide software design, data migration approach, and interface descriptions for the development of the TASS
system. The Contractor shall describe its plans for acquiring and developing the required software to meet
contract requirements. The Contractor shall describe the products, processes, methodologies, milestones, and
measurements to be used in conducting software development activities to meet the requirements in Attachment
A1, TASS System, and Functional Requirements. Overall technical project risks shall be reviewed on a
technical, cost, and schedule basis.
The SDR provides the baseline documentation that shall be used for the design, development, and
implementation of the TASS system. The SDR shall provide sufficient documentation to confirm that the
engineering analysis, design concepts, and design approach achieve the following:
a. Establish the basic design and engineering approach for the overall system, including all external
interfaces.
b. Identify and describe the critical system design, development, test, and preproduction environment
considerations, issues, performance problems, and risks,
c. c. Demonstrate that the detailed design and engineering approach for the overall system is complete.
d. Provide the allocation of TASS functional requirements to individual Software Build Release Plans.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
34

To complete the SDR, the Contractor shall meet the following acceptance criteria:
a. District receipt of the Contractor’s presentation of the SDR materials
b. District acceptance of SDR-related deliverables in Draft or Final form per the specific deliverable
a. Software Test Plan (STP)
c. District acceptance of detailed design that shows how COTS, modified COTS, and/or new development
will work together to satisfy the requirements baseline
d. The resolution, or approved plan for resolution, of all action items

The SDR shall be conducted for each phase before the start of development and integration activities.

C.7.4 Information System Security

The Contractor shall implement security controls consistent with currently accepted Federal Regulations,
Federal Laws, NIST, and OCTO policies and guidelines as documented in the policies referenced in Section
C.2, Applicable Documents. The Contractor shall update the security documentation following architectural
changes, software modifications, additions, and updates. The Contractor shall also provide support to assist with
vulnerability assessments, risk and requirements analysis, and design reviews.

TASS personnel's security requirements for access controls shall adhere to Multi-Factor Authentication login
and integration with the District Single Sign-On Platform.

The Contractor shall ensure that the system is configured to allow only authorized individuals access to it and
that all delivered software is free of malicious code. Flaws discovered during security assessments, continuous
monitoring, incident response activities, or information system error handling shall also be addressed
expeditiously.

C.7.4.1 Personnel Security
The Contractor sh all comply with the personnel security requirements specified in the IT Security Operations
Policies referenced in Section C.2, Applicable Documents.

C.7.5 Test and Evaluation
The Contractor shall plan, document, and conduct a Test and Evaluation (T&E) program to verify that TASS
meets the functional, interface, compliance, and performance requirements in the intended environment and
with the intended users in accordance with this Statement of Work (SOW).
C.7.5.1 Test Management
The Contractor is responsible for planning, conduct, and documentation of the T&E program. The Contractor
shall provide integration, control, oversight, and coordination of all Contractor testing. The Contractor shall
describe a plan that introduces user involvement as early as possible in the test phases described below to
facilitate collaboration between users and developers. The Contractor shall collaborate with the DMV to
schedule all test activities. The Contractor shall notify the District of all changes to these test activities.

C.7.5.2 Contractor-Conducted Tests
C.7.5.2.1 Development Test (DT)

The Contractor shall conduct Development Testing (DT) for all new or modified system requirements. The
Contractor shall perform all testing required to verify the requirements in the DT VRTM located in the STP.
The DT test phase includes a Component Development Test and a System Integration Test, and each test type
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
35

contains test activities. DT shall ensure that the system has met requirements and verifies that it is fully
integrated and stable. DT shall continuously employ quality control processes and procedures.

C.7.5.2.2 System Integration Test

The Contractor shall conduct System Integration Test activities to reduce risk and demonstrate that the system
meets requirements. The District reserves the right to observe and request test logs and results for Contractor
System Integration testing. The Contractor shall establish test environments as needed to support required
testing.. The Contractor shall perform any required System Regression tests based on the results of testing.
Automated regression testing shall continuously evolve to improve the efficiency of continuous integration. The
Contractor shall execute System Integration Test activities to verify system performance, functional
requirements compliance, and ensure the system's overall readiness leading up to Production Readiness testing.

The exit criteria for the System Integration Test activities are as follows:
a. Test criteria as defined in the approved STP are satisfied
b. Completion of all tests in accordance with approved STP and Test Procedures
c. Post-test briefings are complete
d. Test results are documented as per the Contract and accepted by OCTO and DMV.
e. PTRs are fully documented, assessed, and status provided
f. High Priority PTRs have been resolved
g. The ability to “rollback” to a known stable release version of the software has been demonstrated
The Contractor shall perform Performance/Load Testing to verify system processing time and stress thresholds.
The Contractor shall compare results to previously established Performance/Load baselines. These tests also
serve to measure system scalability, reliability, and resource usage. The Contractor shall automate these tests
throughout System (end-to-end) Testing.
The Contractor shall perform Compliance Testing to validate the system developed meets the requirements. The
Contractor shall automate these tests throughout System (end-to-end) Testing.

The Contractor shall perform System (end-to-end) testing as defined in the approved STP. System (end-to-end)
testing shall address verification of integrated software components to address specification items under
conditions that emulate the projected production conditions. The Contractor shall conduct these tests in the Test
Environment with the baseline software.

The Contractor shall conduct System Regression testing when issues are identified during System Integration
Test activities that prevent the Contractor from meeting the exit criteria established by the District for the TASS
DT Project.

C.7.5.2.3 User Acceptance Test

The Contractor shall follow independent test and evaluation activities with a User Acceptance test that
demonstrates to the District that the production system satisfies all allocated requirements for the corresponding
development phase. The Contractor shall support the District’s User Acceptance test activities.

The Contractor shall provide full regression testing. Before initiation of any UAT activities, the Contractor shall
produce the results of a successful full regression test (see Section C.7.5 Test and Evaluation).

The Contractor shall complete User Acceptance Testing of the System, subsystems, and interfaces in all
respects based on the requirements, program specifications, and procedures, approved User Acceptance Test
Plan, based upon the usability, performance, acceptance criteria, and documentation.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
36

Successful completion of the District’s pre-production independent test and evaluation and User Acceptance
testing (as documented in the Software Test Plan) will result in an accepted production version of the system
software.

C.7.5.2.4 Post-Test Briefings

The Contractor shall conduct a post-test briefing at the conclusion of the System Integration Test and
Production Readiness Test and provide the District with a post-test briefing report. The Posttest briefing shall
address the following topics, at a minimum:
a. Overall test results, including a summary of all associated requirements
b. Status of test objectives and exit criteria as specified in the associated Test Plan and Test Procedures
c. c. Test profile including details such as start date and time, stop date and time, supporting staff names,
etc.
d. Any test configuration changes since the STP was delivered
e. All problems encountered, including where and how they are documented
f. Descriptions of all deviations and anomalies encountered
g. Test procedure changes
h. Details on any failed steps and requirements
i. Review of Data Reduction and Analysis (DR&A) results and walkthrough findings
j. Regression test recommendations
k. Documentation of the outstanding test issues with action plans for closure

C.7.5.3 Problem Trouble Reports (PTR)
The Contractor shall track, report, and maintain Problem Trouble Reports (PTRs) as part of the test and
evaluation program. The Contractor shall provide District access to all PTRs. The Contractor shall assign a
unique identification number to each PTR. The Contractor shall identify the proposed regression testing or
future modification(s) to the testing program required to validate the successful corrective action. If a
component fails during a test, the Contractor shall perform a failure analysis to identify the cause of failure and
document the failure in a PTR. The Contractor shall perform any necessary corrective actions to ensure
compliance with all specifications.

The Contractor shall recommend a Priority Classification for each PTR. The final Priority Classification is
assigned by the District. The Contractor shall provide PTR reports and participate in regular meetings, chaired
by the District, to disposition PTRs.

The Project Trouble Reports Classification descriptions are as follows:
Priority 1: A problem that prevents the accomplishment of system functionality, security, or other
requirements designated as Critical Performance Requirements (CPRs).
Priority 2: A problem that adversely affects the accomplishment of system functionality and an
acceptable work-around solution is not known.
Priority 3: A problem that adversely affects the accomplishment of system functionality, but a work-
around solution is known.
Priority 4: A problem that results in a user/operator inconvenience, annoyance, or system
documentation errors but does not affect required system functionality.

C.7.5.4 Test Support
The Contractor shall provide all required support throughout the entire T&E program. This shall include support
continuing through the TASS baseline, transition, and District acceptance.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
37

C.7.6 Technical Documentation
The Contractor shall provide all documentation required for the operation and support of the TASS system. As
directed by the District, the Contractor shall develop and deliver the following Technical Manuals to support the
TASS system:

• End-User Instruction Manual

The Contractor shall establish the process and schedule for developing and delivering original documents,
revisions, and updates. The Contractor shall develop and validate any required revisions to the technical
manuals caused by changes in software and/or procedures. This includes changes resulting from the
introduction of newly developed functional requirements/capabilities and technical refreshes.

The Contractor shall complete report-development software for all existing and new reports based on the
requirements for program specifications, procedures, design, mapping, documentation completion, report
standardization, security, and user acceptance testing.
C.7.6.1 End-User Instruction Manual
The Contractor shall develop and deliver an End User Instruction Manual (EUIM) to provide user instructions
sufficient to execute all TASS functions. Users include all user types who will be primary users of the TASS
system. The End User Instruction Manual shall include, but is not limited to, the following:
• Navigation
• Login
• Security
• Information & Messages
• User Configuration Options
• Error messages
• Any other significant functional capability developed for the TASS system

C.7.7 Training
The District’s agencies using the TASS system shall be provided the knowledge and training required to
operate, monitor, maintain, test, and support the TASS system. The Contractor shall design, develop, and
deliver the following interactive online training courses in accordance with this SOW:
a. TASS On-Line Help
b. TASS Administrator Training
C.7.7.1 TASS On-Line Help
The Contractor shall develop in-application, online help functions. The online help function is designed to
provide the user with the knowledge to perform the functions required for the user’s role. The Contractor shall
update and maintain the online help for each phase of TASS. TASS online help shall be consistent with the End
User Instruction Manual (EUIM).
C.7.7.2 TASS User Training
The Contractor shall complete End-User training for different user groups, management, back-office users, QA
groups, etc. of the TASS System in accordance with the approved User Training Plan, User Training Schedule,
Application User Manual, User Training Material, and usability, performance, acceptance criteria, and
documentation.

The User Training Plan shall contain the proposed overview on training schedules, frequency, training
resources, identify different audience groups, initial training, refresher training, release training, training scope,
and all pertinent information.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
38

The Contractor shall provide an online help capability designed to support users and augment the district's user
training.

C.7.7.3 District Training Support
The Contractor shall provide the DMV with end-user training material, including training lessons or labs. The
contractor shall provide training for material relating to the TASS system functionality.

C.7.7.4 District Refresher Training
The Contractor shall provide the District refresher training quarterly. The DMV will provide the Contractor
with the User Group and Topic for Training one (1) month before the quarterly training.
C.7.8 In-Service Management

C.7.8.1 Software Maintenance
As a hosted, full-service solution, Contractor agrees to software maintenance for the life of the contract and to
provide notification of new releases. Contractor will apply all security patches to our infrastructure for the life
of the Contract.
Contractor agrees to provide software licenses needed to maintain the software for the life of the contract.
Contractor will provide 30 days of post-production support. In fact, our implementation plan includes a 90-day
hyper-care period to ensure all new functionality works per specifications.

C.7.8.2 Help Desk Support
The Contractor shall provide Tier 1, Tier 2, and Tier 3 level support for the TASS system. All service/help calls
will be homed to the TASS Tier 1 Help Desk. As determined by the Tier 1 staff, calls may be escalated to
Contractor Tier 2 staff. For SLA purposes, SLA response time requirements begin from the time of receipt of a
Tier 1 call.

• Tier 1 – Initial maintenance support contact for all problems. Tier 1 help desk support shall be available
24/7. SLA response time requirements will vary depending on the severity of the event and whether the
SLA-related event occurs during regular business hours, Monday-Friday from 6:00 AM EST to 8:00 PM
EST (excluding District holidays), or at other hours. Tier 1 support shall effectively resolve routine
support issues for TASS system users.
• Tier 2 – Maintenance support for problems not resolved by TASS Tier 1 help desk functions. Tier 2 help
desk support shall be available 24/7. SLA response time requirements will vary depending on the
severity of the event and whether the SLA-related event occurs during regular business hours, Monday-
Friday from 6:00 AM EST to 8:00 PM EST (excluding District holidays), or at other hours.
• Tier 3—Support is required for correcting system software problems. Tier 3 support is used when Tier 2
support cannot resolve the issue, or the issue is a software fault requiring software maintenance or
development action.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
46

Severity 3: Definition: Any outage, malfunction, or deterioration in normal service level limited to one
user, including operability of hardware.
Response: Service/Request shall be restored/completed within 4 hours of receipt of a request
by the Tier 1 Service Desk.

Other Assumptions:

The District shall use the Contractor’s monthly system report data to assess the applicability of Service Level
Credits and may supplement this data with the District’s reports or analyses.
The District expects the deliverables to be proposed sequentially or in parallel and iterated multiple times,
consistent with the proposed development methodology. Agile development methodologies may permit initial
versions of milestone deliverables much earlier than the required delivery date for final delivery.
C.7.10 Deliverable Requirements
The Contractor shall submit the Deliverables per the requirements specified in Section F.3. Each Deliverable
document required by Section F.3 shall be delivered no later than the due date in F.3 subject to the District’s
review and approval. If any requirements in the work statement in section C require consultation with the
District to clarify requirements, the Contractor shall arrange with the CA for timely consultation so that the due
dates for milestones and deliverables are not adversely impacted.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
47

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)
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
48

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)
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
49

SECTION F: PERIOD OF PERFORMANCE AND DELIVERABLES
F.1 TERM OF CONTRACT

The term of the contract is five years from the date of award specified on the cover page of this
contract.

This multiyear contract will be canceled if funds are not appropriated or otherwise made available to
support the continuation of performance in any fiscal period succeeding the first. This clause does not
affect either the District’s or the contractor’s rights under any termination clause in the contract.

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 three (3) one-year option periods by
written notice to the Contractor before the expiration of the contract, provided that the District will give
the Contractor written notice of its intent to extend at least thirty (30) days before the contract expires.
The exercise of this option is subject to the consent of the Contractor and the availability of funds at the
time of the exercise of this option. The Contractor may waive the thirty (30) day notice requirement by
providing a written waiver to the Contracting Officer before the expiration of the contract. Upon
agreement of the parties to exercise an option period the parties agree to negotiate the limitation of liability that
will apply to the option year. If the parties cannot agree on the option year limitation of liability the contract will
expire at the end of the current contract term.
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 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 eight (8) years.
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:

CLIN Deliverable Deliverable Format/Method of
Delivery
Due Date
001 1 Interface Control
Document (ICD)
Electronic
002 2 Software Design
Description (SDD)
Electronic
003 3 Sign-Off/Client
Acceptance for
implementation
Electronic

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 Hire 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.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

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.1.3 Unless otherwise specified in this contract and with the presentation of a properly executed invoice:
a) Payment will be made on completion and acceptance of each item for which the price is stated in the Pricing
Schedule in Section B,
b) Payment will be made on completion and acceptance of each percentage or milestone of work in accordance
with the prices stated in the Pricing Schedule in Section B or
c) Payment may be made on partial deliveries of goods and services accepted by the District if the Contractor
requests it and the amount due on the deliveries warrants it as determined by the District.

G.2 INVOICE SUBMITTAL

G.2.1 The Contractor shall submit proper invoices monthly or as specified in the contract.

G.2.2 The Contractor shall submit payment requests in electronic format through the DC Vendor Portal
(www.vendorportal.dc.gov) by selecting the applicable purchase order number listed on the Contractor’s
profile.

G.2.3 To constitute a proper invoice, the Contractor shall attach to all payment requests the invoice and all
supporting documentation or information.
G.2.4 The Cost reimbursement ceiling for this contract is outlined in Section B.4.
G.2.5 The costs for performing this contract shall not exceed the cost reimbursement ceiling specified in
Section B.4.
G.2.6 The Contractor agrees to use its best efforts to perform the work specified in this contract and meet all
obligations within the cost reimbursement ceiling.

G.2.7 The Contractor shall notify the CO, in writing, whenever it has reason to believe that the total cost for
the performance of this contract will be either greater or substantially less than the cost reimbursement
ceiling.

G.2.8 As part of the notification, the Contractor shall provide the CO with a revised estimate of the total cost
of performing this contract.

G.2.9 The District is not obligated to reimburse the Contractor for costs incurred in excess of the cost
reimbursement ceiling specified in Section B.4. The Contractor is not obligated to continue performance
under this contract (including actions under the Termination clauses of this contract), or otherwise incur
costs in excess of the cost reimbursement ceiling specified in Section B.4, until the CO notifies the
Contractor, in writing, that the estimated cost has been increased and provides revised cost
reimbursement ceiling for performing this cont r5a0ct.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
51

G.2.10 No notice, communication, or representation from any person other than the CO shall change the cost
reimbursement ceiling. In the absence of the specified notice, the District is not obligated to reimburse
the Contractor for any costs in excess of the costs reimbursement ceiling, whether such costs were
incurred during the course of contract performance or as a result of termination.
G.2.11 If any cost reimbursement ceiling specified in Section B.4 is increased, any costs the Contractor incurs
before the increase that is in excess of the previous cost reimbursement ceiling shall be allowable to the
same extent as if incurred afterward unless the CO issues a termination or other notice directing that the
increase is solely to cover termination or other specified expenses.

G.2.12 A change order shall not be considered an authorization to exceed the applicable cost reimbursement
ceiling specified in Section B.4 unless the change order specifically increases the cost reimbursement
ceiling.
G.2.13 Only costs determined in writing to be reimbursable in accordance with the cost principles set forth in
rules issued pursuant to Title V of the D.C. Procurement Practices Reform Act of 2010 shall be
reimbursable.

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, the 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 Reserved
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
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
52

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).”

G.6 THE QUICK PAYMENT ACT

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., as amended, 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 at least 1.5% 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 the required
payment date. The required payment date shall be:
G.6.1.1.1 The date on which payment is due under the terms of the contract;
G.6.1.1.2 Not later than 7 calendar days, excluding legal holidays, after the date of delivery of meat or meat
food products;

G.6.1.1.3 Not later than 10 calendar days, excluding legal holidays, after the date of delivery of a perishable
agricultural commodity; or
G.6.1.1.4 30 calendar days, excluding legal holidays, after receipt of a proper invoice for the amount of the
payment due.
G.6.1.2 No interest penalty shall be due to the Contractor if payment for the completed delivery of goods or
services is made on or after:

G.6.1.2.1 3rd day after the required payment date for meat or a meat food product;
G.6.1.2.2 5th day after the required payment date for an agricultural commodity; or

G.6.1.2.3 15th day after any other required payment date.
G.6.1.3 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 the contract:
G.6.2.1.1 Pay the subcontractor(s) for the proportionate share of the total payment received from the District
that is attributable to the subcontractor(s) for work performed under the contract; or

G.6.2.1.2 Notify the CO and the subcontractor(s), in writing, of the Contractor’s intention to withhold all or
part of the subcontractor’s payment and state the reason for the nonpayment.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

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 at least 1.5% 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 the:

G.6.2.2.1 3rd day after the required payment date for meat or a meat product;

G.6.2.2.2 5th day after the required payment date for an agricultural commodity; or

G.6.2.2.3 15th day after any other required payment date.
G.6.2.3 Any amount of an interest penalty that 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 not constitute a dispute to
which the District is a party. The District may not be interpleaded in any judicial or administrative proceeding
involving such a dispute.
G.6.3 Subcontract requirements. 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:
Derrick D. White, NIGP-CPP, CFCM, CCCM
Chief Contracting Officer, Information Technology
Office of Contracting and Procurement
Office of the Chief Technology Officer
Government of the District of Columbia
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 ADMINISTRATOR (CA)
G.9.1 The CA is responsible for the 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 incl ude5: 3
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

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.

G.9.1.3 Review invoices for completed work and recommend 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 invoices or vouchers.
G.9.2 The address and telephone number of the CA is:

Karen Campbell-Tate
Quality Program Officer
DC DMV Adjudication Services
955 L'Enfant Plaza, SW P121
Washington, DC 20024
Office: 202.719.0694
Karen.Tate@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.

54
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

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.1.3 If a contractor has one or more contracts to provide information technology work to the District valued
at $500,000 or more during a 12-month period, the contractor is required to register an apprenticeship
program with the DC Apprenticeship Council through the DOES Office of Apprenticeship. The prime
contractor shall include this provision in its subcontracts under those contracts.

H.2 DEPARTMENT OF LABOR WAGE DETERMINATIONS
The Contractor shall be bound by the Wage Determination No. 2015-4281 Revision No.32 dated
December 23, 2024, 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 adverse action against an employee who requests or uses a reasonable accommodation
regarding 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 an
equivalent position with equivalent:

(1) Pay;

(2) Accumulated seniority and retirement; 55
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
56

(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
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
57

(2) Any provision stating or indicating that an employment agency will not consider or 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 (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 in all jobs covered by the Employment
Agreement shall be the First Source Register.
H.5.3 The Contractor shall not begin the performance of the contract until DOES has accepted its
Employment Agreement. 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 contract's
direct and indirect labor costs, 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 contract's direct and indirect labor costs for each
percentage by which the Contractor fails to meet its hiring requirements.

H.5.8 Any contractor that 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.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

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 that employ 50
employees or less.

H.6 RESERVED

H.7 RESERVED

H.8 RESERVED

H.9 SUBCONTRACTING REQUIREMENTS

H.9.1 Mandatory Subcontracting Requirements

H.9.1.1 For all contracts in excess of $250,000, at least 35% of the dollar volume of the contract shall be
subcontracted to qualified small business enterprises (SBEs).

H.9.1.2 If there are insufficient SBEs to fulfill the requirement of paragraph H.9.1.1 completely, then the
subcontracting may be satisfied by subcontracting 35% of the dollar volume to any qualified,
certified business enterprises (CBEs); provided, however, that all reasonable efforts shall be made to
ensure that SBEs are significant participants in the overall subcontracting work.

H.9.1.3 A prime contractor that is certified by DSLBD as a small, local, or disadvantaged business enterprise
and performs 100% of the work shall not be required to comply with the provisions of sections
H.9.1.1 and H.9.1.2. However, the Prime contractor that is certified by DSLBD still has to submit a
subcontracting plan to confirm 100% of the contracting effort will be performed with its own
organization and resources and will not subcontract any portion of the contract.

H.9.1.4 Except as provided in H.9.1.5 and H.9.1.7, 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.5 If the prime contractor 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, the CBE member of the
certified joint venture 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. If the CBE
member of the certified joint venture prime contractor performs less than 50% of the contracting
effort, the certified joint venture shall be subject to enforcement actions under D.C. Official Code § 2-
218.63.

H.9.1.6 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.7 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 resources58if the contract is $1 million or less.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
59

H.9.2 Subcontracting Plan

If the prime contractor is required to subcontract under this contract, it shall submit a subcontracting
plan as part of the bid and it may only be amended after award with the prior written approval of the CO
and Director of DSLBD. Any reduction in the dollar volume of the subcontracted portion resulting from
an amendment of the plan after award shall inure to the benefit of the District.

Each subcontracting plan shall include the following:

(1) The name and address of each subcontractor;
(2) A current certification number of the small or certified business enterprise;
(3) The scope of work to be performed by each subcontractor; and
(4) The price that the prime contractor will pay each subcontractor.

H.9.3 Copies of Subcontracts
Within twenty-one (21) days of the date of award, the Contractor shall provide fully executed copies of
all subcontracts identified in the subcontracting plan to the CO, CA, District of Columbia Auditor and
the Director of DSLBD.

H.9.4 Subcontracting Plan Compliance Reporting

H.9.4.1 The Contractor shall submit a quarterly report to the CO, CA, District of Columbia Auditor and the
Director of DSLBD. The quarterly report shall include the following information for each
subcontract identified in the subcontracting plan:

(A) The price that the prime contractor will pay each subcontractor under the subcontract;
(B) A description of the goods procured or the services subcontracted for;
(C) The amount paid by the prime contractor under the subcontract; and
(D) A copy of the fully executed subcontract, if it was not provided with an earlier quarterly report.

H.9.4.2 If the fully executed subcontract is not provided with the quarterly report, the prime contractor will
not receive credit toward its subcontracting requirements for that subcontract.
H.9.5 Annual Meetings

Upon at least 30-days written notice provided by DSLBD, the Contractor shall meet annually with the
CO, CA, District of Columbia Auditor and the Director of DSLBD to provide an update on its
subcontracting plan.
H.9.6 Notices

The Contractor shall provide written notice to the DSLBD and the District of Columbia Auditor upon
commencement of the contract and when the contract is completed.

H.9.7 Enforcement and Penalties for Breach of Subcontracting Plan
H.9.7.1 A contractor shall be deemed to have breached a subcontracting plan required by law, if the
contractor (i) fails to submit subcontracting plan monitoring or compliance reports or other required
subcontracting information in a reasonably timely manner; (ii) submits a monitoring or compliance
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
60

report or other required subcontracting information containing a materially false statement; or (iii)
fails to meet its subcontracting requirements.
H.9.7.2 A contractor that is found to have breached its subcontracting plan for utilization of CBEs in the
performance of a contract shall be subject to the imposition of penalties, including monetary fines in
accordance with D.C. Official Code § 2-218.63.
H.9.7.3 If the CO determines the Contractor’s failure to be a material breach of the contract, the CO shall
have cause to terminate the contract under the default provisions in clause 8 of the SCP, Default.

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.
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
Reserved

H.12 CONTRACTOR RESPONSIBILITIES
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
61

Reserved

H.13 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.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
62

SECTION I: CONTRACT CLAUSES
I.1 APPLICABILITY OF STANDARD CONTRACT PROVISIONS
The Standard Contract Provisions (SCP) for use with District of Columbia Government Supplies and
Services Contracts dated July 2010 are incorporated as part of the contract. To obtain a copy of the SCP,
go to http://ocp.dc.gov, and 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 the 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.
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
the commencement of work, or else they 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 solely for the District’s use under
the contract. Custom Products do not include Contractor Preexisting Intellectual Property as defined below.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
63

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

B. Title to Project Deliverables – Rights in Data

Contractor shall retain all right, title and interest in and to all of its Intellectual Property used,
provided or delivered by Contractor to DISTRICT in connection with the performance of this
Agreement. For purposes of this Agreement, “Contractor Preexisting Intellectual Property” means
all pre -existing and independently developed intellectual property, and any derivation thereof,
including but not limited to designs, models, inventions, processes, methodologies, software,
associated documentation, software upgrades, modifications and customizations, copyrightable
material and other tangible and intangible materials authored, and combinations thereof, prepared,
created, made, delivered, conceived or reduced to practice, in whole or in part, by Contractor prior
to this Agreement, or if developed after execution of this Agreement, then developed independently
of this Agreement in the normal course of Contractor ’s operations for general use by clients.

Contractor grants to DISTRICT, a non- exclusive, non-transferable, license to use the Contractor
Preexisting Intellectual Property based on the fees contained in this Agreement for the purpose of
implementing the ticket processing and related services for the duration of this Agreement. The
DISTRICT may make copies of any user manuals for backup and archival purposes which originals
and any copies thereof shall be returned to Contractor at expiration of the contract. The DISTRICT
will not reverse engineer, decompile, or otherwise attempt to derive the source code for the
Contractor Preexisting Intellectual Property.

In addition to the above granted rights the following restrictions apply to the License to Use:

1. DISTRICT may not sell, rent or lease the Contractor Preexisting Intellectual Property
software, nor disassemble, alter, modify, assign, translate, adapt or make derivative works of the
Contractor software;
2. DISTRICT agrees not to remove or destroy any proprietary markings or proprietary legends
placed upon or contained within the Contractor Preexisting Intellectual Property products or
software or any related materials or documentation;
3. DISTRICT agrees to not sell, lease, rent, or transfer Contractor Preexisting Intellectual
Property or equipment to a competitor of Contractor , nor allow any unauthorized access to
Contractor Preexisting Intellectual Property software;

C. District Rights in Data
All data generated in the performance of this Contract shall be the sole property of the District. The Contractor
hereby acknowledges that all data, including, without limitation, citation data produced by Contractor solely for
the District under this Contract, are works made for hire and are the sole property of the District; but, to the
extent any such data may not, by operation of law, be works made for hire, Contractor hereby transfers and
assigns to the District the ownership of copyright in such works, whether published or unpublished. The
Contractor agrees to give the District all assistance reasonably necessary to perfect such rights including, but
not limited to, the works and supporting documentation and the execution of any instrument required to register
copyrights. The Contractor agrees not to assert any rights in common law or in equity in such data. The
Contractor shall not publish or reproduce such data in whole or in part or in any manner or form, or authorize
others to do so, without written consent of the District until such time as the District may have released such
data to the public. Notwithstanding this section Contractor retains all rights and does not transfer any rights not
specified herein for Contractor’s Preexisting Intellectual Property defined above

D. Subcontractor Rights
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
64

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. Indemnification and Limitation of Liability

The Contractor shall indemnify the District, its officers, agents and employees acting within the scope of
their official duties against any actual and direct liability, including costs and expenses, for violation of
proprietary rights, copyrights, or rights of privacy, arising out of the District’s authorized use of any
Contractor Preexisting Intellectual Property furnished under this contract.
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. Should the Contractor decide to engage a subcontractor for segments of the
work under this contract, then, prior to the commencement of work by the subcontractor, the Contractor
shall submit in writing the name and brief description of work to be performed by the subcontractor on
the Subcontractors Insurance Requirement Template provided by the CA, to the Office of Risk
Management (ORM). ORM will determine the insurance requirements applicable to the subcontractor
and promptly deliver such requirements in writing to the Contractor and the CA. The Contractor must
provide proof of the subcontractor's required insurance prior to commencement of work by the
subcontractor. If the Contractor decides to engage a subcontractor without requesting from ORM
specific insurance requirements for the subcontractor, such subcontractor shall have the same insurance
requirements as the Contractor.
All required policies shall contain a waiver of subrogation provision in favor of the Government of the
District of Columbia.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
65

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 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 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 Contractor 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 for 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.

The vendor should be named as an additional insured on the applicable manufacturer’s/distributer’s
Commercial General Liability policy using Insurance Services Office, Inc. (“ISO”) form CG 20 15
04 13 (or another occurrence-based form with coverage at least as broad).
OCP should collect, review for accuracy and maintain all warranties for goods and services.

2. Automobile Liability Insurance - The Contractor shall provide evidence satisfactory to the CO of
commercial (business) automobile liability insurance written on ISO form CA 00 01 10 13 (or
another form with coverage at least as broad and approved by the CO in writing) including coverage
for all owned, hired, borrowed and non-owned vehicles and equipment used by the Contractor, with
minimum per accident limits equal to the greater of (i) the limits outlined in the Contractor’s
commercial automobile liability policy or (ii) $1,000,000 per occurrence combined single limit for
bodily injury and property damage.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
66

3. 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 the Government of the District of Columbia.
4. Cyber Liability Insurance - The Contractor shall provide evidence satisfactory to the Contracting
Officer of Cyber Liability Insurance, with limits not less than $5,000,000 per occurrence or claim,
$5,000,000 aggregate. Coverage shall be sufficiently broad to respond to the duties and obligations
as 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, the release of private information, alteration of electronic information,
extortion, and network security. The policy shall provide coverage for breach response costs,
regulatory fines and penalties, and 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 and coverages.
5. 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
$5,000,000 per claim or per occurrence for each wrongful act and $5,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 ten years after the completion of the professional services.
6. Commercial Umbrella or Excess Liability - The Contractor shall provide evidence satisfactory to the
CO of commercial umbrella or excess liability insurance with minimum limits equal to the greater of
(i) the limits set forth in the Contractor’s umbrella or excess liability policy or (ii) $10,000,000 per
occurrence and $10,000,000 in the annual aggregate, following the form and in excess of all liability
policies. All liability coverages must be scheduled under the umbrella and/or excess policy. 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.

C. DURATION. The Contractor shall carry all required insurance until all contract work is accepted by the
District, and shall carry the required General Liability; any required Professional Liability; and any
required Employment Practices Liability insurance for five (5) years following final acceptance of the
work performed under this contract.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
67

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. Contractors 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.

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 insurance and bond costs in the contract price.

G. NOTIFICATION. The Contractor shall immediately provide the CO with written notice in the event
that its insurance coverage has or will be substantially changed, canceled, or not renewed and provide an
updated certificate of insurance to the CO.

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. Evidence of
insurance shall be submitted to the following:

Derrick D. White, NIGP-CPP, CFCM, CCCM
Chief Contracting Officer, Information Technology
Office of Contracting and Procurement
Office of the Chief Technology Officer
Government of the District of Columbia

I. DISCLOSURE OF INFORMATION. The Contractor agrees that the District may disclose the name
and contact information of its insurers to any third party that 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 District.

I.9 EQUAL EMPLOYMENT OPPORTUNITY

In accordance with the District of Columbia Administrative Issuance System, Mayor’s Order 85-85
dated June 10, 1985, the forms for completion of the Equal Employment Opportunity Information
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
68

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 this solicittaion will 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, which 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) This Contract document
(3) Project Management Plan
(4) Standard Contract Provisions
(5) Contract attachments other than the Standard Contract Provisions
(6) Contractor Proposal as amended
(7) District Solicitation, as amended

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 to further resolve the claim by agreement.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
69

(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. It 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 the final decision of an appeal, action, or final settlement, the Contractor shall proceed
diligently with the 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.
(2) The CO shall send the contractor written notice of the claim. 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;
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
70

(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 in this paragraph (b) shall not apply to a claim or dispute for penalties or
forfeitures prescribed by statute or regulation that 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 the final decision of an appeal, action, or final settlement, the Contractor shall
proceed diligently with performance of the contract in accordance with the CO's decision.
I.12 CHANGES

Delete clause 15, Changes, of the Standard Contract Provisions dated July 2010 for use with District of
Columbia Government Supplies and Services Contracts and substitute the following clause 15, Changes,
in its place:
15. Changes:
(a) The CO may, at any time, by written order and without notice to the surety, if any, make changes in
the contract within the general scope hereof. If such change causes an increase or decrease in the
cost of performance of the contract or in the time required for performance, an equitable adjustment
shall be made. Any claim for adjustment for a change within the general scope must be asserted
within ten (10) days from the date the change is ordered; provided, however, that the CO, if he or
she determines that the facts justify such action, may receive, consider and adjust any such claim
asserted at any time prior to the date of final settlement of the contract. If the parties fail to agree
upon the adjustment to be made, the dispute shall be determined as provided in clause 14, Disputes.
(b) The District shall not require the Contractor, and the Contractor shall not require a subcontractor, to
undertake any work that is beyond the original scope of the contract or subcontract, including work
under a District-issued change order, when the additional work increases the contract price beyond
the not-to-exceed price or negotiated maximum price of this contract unless the CO:
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
71

(1) Agrees with Contractor, and if applicable, the subcontractor on a price for the additional
work;
(2) Obtains a certification of funding to pay for the additional work;
(3) Makes a written, binding commitment with the Contractor to pay for the additional work
within 30 days after the Contractor submits a proper invoice; and
(4) Provide the Contractor with written notice of the funding certification.

(c) The Contractor shall include in its subcontracts a clause that requires the Contractor to:
(1) Within five business days of its receipt of notice of the approved additional funding,
provide the subcontractor with notice of the amount to be paid to the subcontractor for
the additional work to be performed by the subcontractor.
(2) Pay the subcontractor any undisputed amount to which the subcontractor is entitled to the
additional work within ten days of receipt of payment from the District; and
(3) Notify the subcontractor and CO in writing of the reason the Contractor withholds any
payment from a subcontractor for the additional work.
(d) Neither the District, Contractor, nor any subcontractor may declare another party to be in default or
assess, claim, or pursue damages for delays until the parties agree on a price for the additional work.
I.13 NON-DISCRIMINATION CLAUSE
Delete clause 19, Non-Discrimination Clause, of the Standard Contract Provisions dated July 2010 for use with
District of Columbia Government Supplies and Services Contracts and substitute the following clause 19, Non-
Discrimination Clause, in its place:
19. Non-Discrimination Clause:

(a) The Contractor shall not discriminate in any manner against any employee or applicant for
employment that would constitute a violation of the District of Columbia Human Rights Act,
effective December 13, 1977, as amended (D.C. Law 2-38; D.C. Official Code § 2-1401.01 et seq.)
(“Act”, as used in this clause). The Contractor shall include a similar clause in all subcontracts
except for standard commercial supplies or raw materials. In addition, the Contractor agrees, and
any subcontractor shall agree, to post in conspicuous places, available to employees and applicants
for employment, a notice setting forth the provisions of this non-discrimination clause as provided
in section 251 of the Act.
(b) Pursuant to Mayor’s Order 85-85 (6/10/85), Mayor’s Order 2002-175 (10/23/02), Mayor’s Order
2011-155 (9/9/11), and the rules of the Office of Human Rights, Chapter 11 of Title 4 of the D.C.
Municipal Regulations, the following clauses apply to the contract:
(1) The Contractor shall not discriminate against any employee or applicant for
employment because of actual or perceived race, color, religion, national origin,
sex, age, marital status, personal appearance, sexual orientation, gender identity or
expression, family responsibilities, genetic information, disability, matriculation,
political affiliation, or credit information. Sexual harassment is a form of sex
discrimination which the Act prohibits. In addition, harassment based on any of the
above-protected categories is prohibited by the Act.
(2) The Contractor agrees to take affirmative action to ensure that applicants are
employed and that employees are treated during employment, without regard to
their actual or perceived race, color, religion, national origin, sex, age, marital
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
72

status, personal appearance, sexual orientation, gender identity or expression,
family responsibilities, genetic information, disability, matriculation, political
affiliation, or credit information. The affirmative action shall include, but not be
limited to, the following:
(a) employment, upgrading, or transfer.
(b) recruitment, or recruitment advertising.
(c) demotion, layoff, or termination.
(d) rates of pay or other forms of compensation; and
(e) selection for training and apprenticeship.
(3) The Contractor agrees to post in conspicuous places, available to employees and
applicants for employment, notices to be provided by the contracting agency,
setting forth the provisions in paragraphs 19(b)(1) and (b)(2) concerning
nondiscrimination and affirmative action.
(4) The Contractor shall, in all solicitations or advertisements for employees placed by
or on behalf of the Contractor, state that all qualified applicants will receive
consideration for employment pursuant to the nondiscrimination requirements
outlined in paragraph 19(b)(2).
(5) The Contractor agrees to send to each labor union or representative of workers with
which it has a collective bargaining agreement or other contract or understanding, a
notice to be provided by the contracting agency advising the said labor union or
workers’ representative of that contractor’s commitments under this
nondiscrimination clause and the Act and shall post copies of the notice in
conspicuous places available to employees and applicants for employment.
(6) The Contractor agrees to permit access to its books, records, and accounts
pertaining to its employment practices by the Chief Procurement Officer or
designee, or the Director of the Office of Human Rights or designee, for purposes
of investigation to ascertain compliance with the Act and to require under terms of
any subcontractor agreement each subcontractor to permit access of such
subcontractors’ books, records, and accounts for such purposes.
(7) The Contractor agrees to comply with the provisions of the Act and with all
guidelines for equal employment opportunity applicable in the District adopted by
the Director of the Office of Human Rights or any authorized official.
(8) The Contractor shall include in every subcontract the equal opportunity clauses,
i.e., paragraphs 19(b)(1) through (b)(9) of this clause, so that such provisions shall
be binding upon each subcontractor.
(9) The Contractor shall take such action with respect to any subcontract as the CO may
direct as a means of enforcing these provisions, including sanctions for noncompliance;
provided, however, that in the event the Contractor becomes involved in, or is threatened
with, litigation with a subcontractor or vendor as a result of such direction by the
contracting agency, the Contractor may request the District to enter into such litigation to
protect the interest of the District.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
73

I.14 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.

I.15 CAMPAIGN FINANCE REFORM
I.15.1 Mandatory Certification
I.15.1.1 The Contractor shall certify that it has read and is in compliance with the Campaign Finance Reform
Amendment Act of 2018, effective March 13, 2019 (D.C. Law 22-250; D.C. Official Code § 1-1001.03
et seq.). This certification is included in the Bidder/Offeror Certification Form.
I.15.1.2 The Contractor shall re-certify prior to the exercise of any option period that it has read and complies
with the Campaign Finance Reform Amendment Act of 2018, effective March 13, 2019 (D.C. Law 22-
250; D.C. Official Code § 1-1001.03 et seq.). This certification is included in the Bidder/Offeror
Certification Form.
I.15.2 Reporting Contractor’s Principals
Contractors shall inform the contracting officer of any change to their principals during the contract
term within thirty (30) days of the change occurring.
I.16 Prohibited Contributions
I.16.1 For contracts with a maximum aggregate value (the total sum of the contract ceiling for the base period
and any subsequent option periods) of between $250,000 and up to and including $1,000,000 and a
base period of performance of 1 year or less, neither the Contractor nor any of its principals may make
any contribution to the Mayor, any candidate for Mayor, any political committee affiliated with the
Mayor or a candidate for Mayor, or any constituent-service program affiliated with the Mayor for the
period from the date of contract award through one year after the contract ends or is terminated.
I.16.2 For contracts with a maximum aggregate value (the total sum of the contract ceiling for the base period
and any subsequent option periods) of over $1,000,000 or with a base period of longer than one year,
neither the Contractor nor any of its principals may make any contribution to the Mayor, any candidate
for Mayor, any political committee affiliated with the Mayor or a candidate for Mayor, any constituent-
service program affiliated with the Mayor, any Councilmember, any candidate for Councilmember, any
political committee affiliated with a Councilmember or a candidate for Councilmember, or any
constituent-service program affiliated with a Councilmember for the period from the date of contract
award through one year after the contract ends or is terminated.

I.17. AMERICANS WITH DISABILITIES ACT of 1990 (ADA)
During the contract's performance, the Contractor and all of its subcontractors shall comply with the
ADA. The ADA makes it unlawful to discriminate in employment against a qualified individual with a
disability. Contractors providing public transportation shall comply with Title II of the ADA.
Contractors providing public accommodations shall comply with Title III of the ADA. Contractors
providing telecommunication shall comply with Title IV of the ADA. See 42 U.S.C. § 12101 et seq.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
74

The following clauses are submitted to replace the corresponding terms in the
District of Columbia’s Standard Contract Provisions

I.18. INDEMNIFICATION
The Contractor agrees to defend and indemnify the District, its officers, agencies,
departments, agents, and employees (collectively the "District") from and against any third
party actual and direct claims, losses, liabilities, penalties, fines, forfeitures, demands, causes
of action, suits, costs and expenses (including reasonable cost of defense and attorneys' fees),
resulting from the willful misconduct, reckless or gross negligence performed by the
Contractor, Contractor's officers , employees acting for or by permission of the Contractor in
performance of this Contract.
Except for the fees and amount expressly due and payable to Contractor hereunder and
notwithstanding anything else in the Agreement, Contractor's cumulative liability for any and all
damages arising out of or relating to its performance of the Services and this Contract in the
aggregate will not exceed the lesser of: (i) District's actual proven direct damages for the event
giving rise to the cause of action or (ii) the amount invoiced by Contractor to the District for the
total charges payable to Contractor under Clin1 and Clin 2 for the base term of the agreement.
The Contractor reserves the right to negotiate a new limitation of liability applicable for each
option year exercised. UNDER NO CIRCUMSTANCES WILL EITHER PARTY TO THIS
AGREEMENT BE LIABLE FOR ANY INCIDENTAL, CONSEQUENTIAL, INDIRECT,
PUNITIVE OR SPECIAL DAMAGES ARISING OUT OF OR IN CONNECTION WITH THIS
AGREEMENT, HOWEVER CAUSED AND BASED ON ANY THEORY OF LIABILITY.

The indemnification obligation under this section shall not be limited by the existence of any
insurance policy and shall survive the termination of this Contract. The District agrees to give
Contractor written notice of any claim of indemnity under this section. Additionally,
Contractor shall have the right and sole authority to control the defense or settlement of such
claim, provided that no contribution or action by the District is required in connection with the
settlement.

I.19. RETENTION AND EXAMINATION OF RECORDS:
The Contractor shall establish and maintain books, records, and documents (including
electronic storage media) in accordance with generally accepted accounting principles and
practices which sufficiently and properly reflect all revenues and expenditures of funds
provided by the District under the contract.
The Contractor shall retain all records, financial records, supporting documents, statistical
records, and any other documents (including electronic storage media) pertinent to the contract
for a period of three (3) years after termination or expiration of the contract, or if an audit has
been initiated and audit findings have not been resolved at the end of three (3) years, the
records shall be retained until resolution of the audit findings or any litigation which may be
based on the terms of the contract.
The Contractor shall assure that these records shall be subject at all reasonable times to
inspection, review, or audit by federal, District, or other personnel duly authorized by the CO.

The CO, the Inspector General and the District of Columbia Auditor, or any of their duly-
authorized representatives shall, until three years after final payment, have the right to examine
any directly pertinent books, documents, papers and records of the Contractor involving
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

transactions related to the contract.
Notwithstanding the foregoing, the City’s access to Contractor’s records shall not be performed
by competitors of the Contractor and shall be limited to the extent necessary to establish
Contractor’s compliance with this Agreement or applicable law and shall not include Contractor’s
proprietary, confidential, and, trade secret information including but not limited to cost and
pricing data as well as source code.

I.20. (16) TERMINATION FOR CONVENIENCE:
(a) The Contractor or the District may terminate performance of work under this contract in
whole or, from time to time, in part if the Contractor determines that a termination is in the
Contractor’s interest or the CO determines that a termination is in the District's interest. Either
Party shall terminate by delivering to the other party a Notice of Termination specifying the
extent of termination and effective date.
(b) After receipt of a Notice of Termination, and except as directed by the CO, the
Contractor shall immediately proceed with the following obligations, regardless of any delay
in determining or adjusting any amounts due under this clause:
1. Stop work as specified in the notice.
2. Place no further subcontracts or orders (referred to as subcontracts in this clause) for
materials, services, or facilities, except as necessary to complete the continued portion of the
contract.
3. Terminate all contracts to the extent they relate to the work terminated.
4. Assign to the District, as directed by the CO, all rights, title and interest of the
Contractor under the subcontracts terminated, in which case the District will have the right
to settle or pay any termination settlement proposal arising out of those terminations.
5. With approval or ratification to the extent required by the CO, settle all outstanding
liabilities and termination settlement proposals arising from the termination of subcontracts.
The approval or ratification will be final for purposes of this clause.
6. As directed by the CO, transfer title and deliver to the District the completed or partially
completed plans, drawings, information, and other property that, if the contract has been
completed, would be required to be furnished to the District.
7. Complete performance of the work not terminated.
8. Take any action that may be necessary, or that the CO may direct, for the
protection and preservation of the property related to this contract that is in the possession
of the Contractor and in which the District has or may acquire an interest.
9. Use its best efforts to sell, as directed or authorized by the CO provided, however, that
the Contractor (i) is not required to extend credit to any purchaser and (ii) may acquire the
property under the conditions prescribed by, and at prices approved by, the CO. The proceeds
of any transfer or disposition will be applied to reduce any payments to be made by the
District under this contract, credited to the price or cost of the work, or paid in any other
manner directed by the CO.
(c) After the expiration of ninety (90) days (or such longer period as may be agreed to)
after receipt by the CO of acceptable inventory schedules, the Contractor may submit to the
CO a list. certified as to quantity and quality of termination inventory not previously
disposed of excluding items authorized for disposition by the CO. The Contractor may
request the District to remove those items or enter into an agreement for their storage. Within
fifteen (15) days, the District will accept title to those items and remove them or enter into a
storage agreement. The CO may verify the list upon removal of the items, or if stored, within
forty five (45) days from submission of the list, and s h a7l5l correct the list, as necessary, before
final
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

settlement.
(d) After termination, the Contractor shall submit a final termination settlement proposal
to the CO in the form and with the certification prescribed by the CO, which will include any
applicable unamortized costs and wind down expenses for early termination. The Contractor
shall submit the proposal promptly, but no later than one year from the effective date of
termination, unless extended in writing by the CO upon written request of the Contractor
within this one year period. However, if the CO determines that the facts justify it, a
termination settlement proposal may be received and acted on after one year or any extension.
If the Contractor fails to submit the proposal within the time allowed, the CO may determine,
on the basis of information available, the amount, if any, due to the Contractor because of the
termination and shall pay the amount determined.
(e) Subject to paragraph 16(d) above, the Contractor and the CO may agree upon the
whole or any part of the amount to be paid because of the termination. The amount may
include a reasonable allowance for profit on work done. However, the agreed amount,
whether under this paragraph (e) or paragraph 16 (f) below, exclusive of costs shown in
subparagraph 16(f)(3), may not exceed the total contract price as reduced by (1) the amount
of payment previously made and (2) the contract price of work not terminated. The contract
shall be amended, and the Contractor paid the agreed amount. Paragraph 16(f) shall not limit,
restrict, or affect the amount that may be agreed upon to be paid under this paragraph 16(e).
(f) If the Contractor and the CO fail to agree on the whole amount to be paid because
of the termination work, the CO shall pay the Contractor the amounts determined by the
CO as follows, but without duplication of any amounts agreed on under paragraph 16(e)
above:
1. The contract price for completed supplies or services accepted by the not previously
paid for, adjusted for any saving of freight and other charges.
2. The total of:
1. The costs incurred in the performance of the work terminated, including initial costs
and preparatory expense allocable thereto as well as unamortized costs and wind down
expenses, but excluding any costs attributable to supplies or services paid or to be paid under
paragraph I6(f)( l) above;
2. The cost of settling and paying termination settlement proposals under terminated
subcontracts that are properly chargeable to the terminated portion of the contract if not
included in paragraph l 6(f)(l) above; and
3. A sum, as profit on paragraph I 6(f)( l) above, determined by the CO to be fair and
reasonable; however, if it appears that the Contractor would have sustained a loss on the entire
contract had it been completed, the CO shall allow no profit under this subparagraph (iii) and
shall reduce the settlement to reflect the indicated rate of loss.
3. The reasonable cost of settlement of the work terminated, including-
1. Accounting, legal, clerical, and other expenses reasonably necessary for the preparation
of termination settlement proposals and supporting data;
2. The termination and settlement of subcontractors (excluding the amounts of such
settlements); and
3. Storage, transportation, and other costs incurred, reasonably necessary for the
preservation, protection, or disposition of the termination inventory.
(g) Except for normal spoilage, and except to the extent that the District expressly assumed
the risk of loss, the CO shall exclude from the amounts payable to the Contractor under
paragraph 16(f) above, the fair value as determined by the CO, of property that is destroyed,
lost, stolen, or damaged so as to become undeliverable to the District or to a buyer.
(h) The Contractor shall have the right of app 7e6al, under clause 14 Disputes, from any
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing

determination made by the CO under paragraphs 16(d), (f) or (j), except that if the Contractor
failed to submit the termination settlement proposal within the time provided in paragraph
16(d) or (j), and failed to request a time extension, there is no right of appeal. If the CO has
made a determination of the amount due under paragraph 16(d), (f) or (j), the District will pay
the Contractor (1) the amount determined by the CO if there is no right of appeal or if no
timely appeal has been taken, or (2) the amount finally determined on an appeal.
(i) In arriving at the amount due the Contractor under this clause, there shall be deducted:
1. All unliquidated advances or other payments to the Contractor under the termination
portion of the contract;
2. Any claim which the District has against the Contractor under this contract; and
3. The agreed price for, or the proceeds of sale of, materials, supplies, or other
things acquired by the Contractor or sold under the provisions of this clause and not recovered
by or credited to the District.
(j) If the termination is partial, the Contractor may file a proposal with the CO for an
equitable adjustment of the price(s) of the continued portion of the contract. The CO shall
make any equitable adjustment agreed upon. Any proposal by the Contractor for an
equitable adjustment under this clause shall be requested within ninety (90) days from the
effective date of termination unless extended in writing by the CO.
(k) (1) The District may, under the terms and conditions it prescribes, make partial
payments and payments against costs incurred by the Contractor for the terminated portion
of the contract, if the CO believes the total of these payments will not exceed the amount to
which the Contractor shall be entitled.
1. If the total payments exceed the amount finally determined to be due, the Contractor
shall repay the excess to the District upon demand together with interest computed at the rate
of 10 percent (10%) per year. Interest shall be computed for the period from the date the
excess payment is received by the Contractor to the date the excess payment is repaid.
Interest shall not be charged on any excess payment due to a reduction in the Contractor's
termination settlement proposal because of retention or other disposition of termination
inventory until 10 days after the date of the retention or disposition, or a later date determined
by the CO because of the circumstances.
2. Unless otherwise provided in this contract or by statute, the Contractor shall maintain all
records and documents relating to the terminated portion of this contract for three (3) years
after final settlement. This includes all books and other evidence bearing on the Contractor's
costs and expenses under this contract. The Contractor shall make these records and
documents available to the District, at the Contractor's office, at all reasonable times, without
any direct charge. If approved by the CO, photographs, micrographs, or other authentic
reproductions may be maintained instead of original records and documents.

I.21. Default:
(a) The District may, subject to the provisions of paragraph 8(c) below, by written notice of
default to the Contractor, terminate the whole or any part of this contract in any one of the
following circumstances:
1. If the Contractor fails to make delivery of the supplies or to perform the services
within the time specified herein or any extension thereof; or
2. If the Contractor fails to perform any of the other provisions of this contract, or so
fails to make progress as to endanger performance of this contract in accordance with its
terms, and in either of these two circumstances does not cure such failure within a period of
thirty ( 3 0) days (or such longer period as the Contracting Officer may authorize in writing)
after receipt of notice from the Contracting Officer sp7ec7ify in g such failure.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
78

1. In the event the District terminates this contract in whole or in part as provided in paragraph
(a) of this clause, the District may procure, upon such terms and in such manner as the
Contracting Officer may deem appropriate, supplies or service similar to those so terminated,
and the Contractor shall be liable to the District for any costs incurred for procuring similar
supplies or services; provided, that the Contractor shall continue the performance of this
contract to the extent not terminated under the provisions of this clause.
2. Except with respect to defaults of subcontractors, the Contractor shall not be liable for
any excess costs if the failure to perform the contract arises out of causes beyond the control
and without the fault or negligence of the Contractor. Such causes may include , but are not
restricted to, acts of God or of the public enemy, acts of the District or federal government in
either their sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions,
strikes, freight embargoes, and unusually severe weather; but in every case the failure to
perform must be beyond the control and without fault or negligence of the Contractor. If the
failure to perform is caused by the default of the subcontractor, and if such default arises out
of causes beyond the control of both the Contractor and the subcontractor, and without the
fault or negligence of either of them, the Contractor shall not be liable for any excess cost for
failure to perform, unless the supplies or services to be furnished by the subcontractor were
obtainable from other sources in sufficient time to permit the Contractor to meet the required
delivery schedule.
3.
4. If, after notice of termination of this contract under the provisions of this clause, it is
determined for any reason that the Contractor was not in default under the provisions of this
clause, or that the default was excusable under the provisions of this clause, the rights and
obligations of the parties shall, if the contract contains a clause providing for termination of
convenience of the District, be the same as if the notice of termination had been issued
pursuant to such clause . See clause 16 Termination for Convenience of the District.
5. The rights and remedies of the District provided in this clause shall not be exclusive and
are in addition to any other rights and remedies provided by law or under this contract.

I.22. NEW CLAUSE - FORCE MAJEURE EVENT
The parties acknowledge and agree that the parties’ respective obligations under this
CONTRACT and any Agreement entered into pursuant to this Contract (including any Liability for
failure to perform, or delay in performing, an obligation but excluding an obligation to pay money)
are suspended during any period of a Force Majeure Event, but only to the extent the following
conditions are satisfied:
(i) the failure or delay arose from a Force Majeure Event where the affected party is or was
unable to perform its obligations under this CONTRACT and an Agreement;
(ii) the affected party took all reasonable precautions against that cause and did its best to
mitigate its consequences (noting nothing in this clause subsection will require the party to settle a
labor dispute, if, in the party's reasonable opinion, that is not in its best interests); and
(iii) the affected party gave the other party notice of the cause of the Force Majeure Event as
soon as practicable after the happening of the event or circumstance relied upon as a Force Majeure
Event.
Either party may terminate this CONTRACT by giving notice to the other party if an event
referred to in part a continues to preclude a party from complying with its obligations to perform
under this CONTRACT for more than 60 consecutive calendar days. This termination will be
deemed a termination for convenience by the parties.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Doc737382 – Ticketing
79

For the avoidance of doubt, termination of this CONTRACT pursuant to clause (b) above will
not affect the accrued rights or remedies of either party.
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1
Docusign Envelope ID: A3CA7D61-B2F5-488C-8D14-6D65E9A1B8F1