Proposed Contract with DSI-ITI, Inc. d/b/a ViaPath Technologies to Contract No. CW130494

MURIEL BOWSER
MAYOR

May 11, 2026

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
proposed definitive Contract No. CW130494 with DSI-ITI, Inc. d/b/a ViaPath Technologies in the
amount of $2,129,325. The period of performance is from September 26, 2025 through September
25, 2026.

Under the proposed contract, DSI -ITI, Inc. d/b/a ViaPath Technologies will lead the transition
from the legacy PowerBuilder -based Jail and Community Corrections System to the latest
commercial off-the-shelf version of the District’s Offender Management System.

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 look forward to the Council’s favorable consideration of this contract.

Sincerely,

Muriel Bowser

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
(Letter Contract)

(A) Contract Number: CW130494

Proposed Contractor: DSI-ITI, Inc. d/b/a ViaPath Technologies

Proposed Contractor’s Principals: Carol A. File, Director, OMS & Strategy

Contract Amount: $2,129,325

Unit and Method of Compensation: Payment based on fixed prices

Term of Contract: September 26, 2025, through September 25, 2026

Type of Contract: Firm Fixed Price

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: $2,129,325

Option Period 1 Amount: $2,129,325
Explanation of difference from base period (if applicable): There is no difference.

Option Period 2 Amount: $366,788
Explanation of difference from base period (if applicable): Option year two price covers only
Operation and Maintenance.

Option Period 3 Amount: $376,977
Explanation of difference from base period (if applicable): Option year three price covers only
Operation and Maintenance.

Option Period 4 Amount: $387,676.00
Explanation of difference from base period (if applicable): Option year four price covers only
Operation and Maintenance.
2

(C) The date on which the letter contract or emergency contract was executed:

September 26, 2025.

(D) The number of times the letter contract has been extended:

One

(E) The value of the goods and services provided to date under the letter contract, including
under each extension of the letter contract:

$1,000,000.

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

None

(G) 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 definitized contract, ViaPath Technologies will lead the transition from the
legacy PowerBuilder-based Jail and Community Corrections System to the latest Commercial Off-
The-Shelf version of Offender Management System (OMSE).

ViaPath Technologies will deliver an on-premises OMSE solution that includes all required
services for successful deployment, configuration, data migration, reporting needs, training, and
support. The OMSE platform is designed to meet the operational needs of the District of Columbia
Department of Corrections (DOC) with minimal custom development, leveraging its out-of-the-box
capabilities to the greatest extent possible.

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

In accordance with ;D.C. Official Code § 2-354.13, this procurement is exempt from competition.

ViaPath Technologies is the incumbent provider and is the sole developer and owner of the OMSE
software solution. As such, there are no other providers of the requirement platform.

The Statement of Work (SOW) was sent exclusively to ViaPath Technologies on August 07, 2025,
which ultimately resulted in the award of the letter contract. The proposed definitized contract is
required to formalize the terms and continue the work initiated under the letter contract. The
proposed contract will be a firm fixed type contract, as per 27 DCMR § 2401 (Contract Types).

(I) 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:

3

There were no protests associated with this procurement.

(J) 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:

ViaPath Technologies has the necessary background, qualification, and technical skills; ViaPath
Technologies is a company with deep roots in providing technology and services for state and local
Government, ViaPath Technologies design and deploy integrated, secure platforms that safeguard
correctional staff, protect communities, and optimize facility operations. ViaPath Technologies
solutions connect advanced security, operational intelligence, and rehabilitation tools—powering
safer, smarter systems that ultimately help reduce recidivism and transform lives.

ViaPath Technologies has a satisfactory performance record based on the current letter contract and
has adequate financial resources to perform the contract or the ability to obtain those resources
based on the Dun & Bradstreet report, the Contractor is financially secured.

(K) 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:

A subcontracting plan is not required for this contract.

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

ViaPath Technologies’ performance will be regularly and routinely monitored by DOC. The
expected outcome is to provide upgrading of the Offender Management System (OMSE).

(M) 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:

$500,000

(N) 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 funding is consistent with the financial plan
and budget.

(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:
4

The contractor has self-certified, via Bidders/Offerors 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) 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 contract with ViaPath
Technologies is legally sufficient and the contractor has no pending legal claim against the District.

(Q) 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
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 Citywide Clean Hands Databased indicates that the contractor is current with its District taxes.

(R) 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 it Bidder Offeror certification form, that it is current with its
federal taxes.

(S) 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.

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

None.

(U) 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.

5

(V) 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):

Determination and Findings for Contractor Responsibility
Determination and Findings for Price Reasonableness

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

http://ocp.dc.gov

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

Not applicable
/0 /0 /1 /0 /i255 /3 /4 /5 /i255 /6 /4 /7 /8 /8 /4 /9 /i255 /6 /10
/10/11 /12 /5 /13 /14 /15 /4 /16 /14 /9 /i255 /17 /18 /i255 /19 /1 /1 /19 /3
/20 /21 /22 /23 /i255 /25 /26 /i255 /27 /25 /22 /28 /29 /23 /30 /31/21 /32 /29 /33 /i255 /34 /35 /i255 /36 /37 /36 /38 /39 /37 /37 /40 /38 /40 /37 /41 /40 /42 /43/27 /25 /22 /28 /29 /23 /i255 /27 /44 /45/46 /23 /32 /30
/47 /48 /49 /50 /51 /i255 /52 /52 /53 /52 /52 /52 /3 /3 /3 /1
/18 /11 /12 /8 /i255 /49 /17 /51 /i255 /0 /54 /54 /55 /55 /56 /57 /57
/i255
/59 /16 /60 /8 /7 /14 /61/8 /14 /4 /i255 /16 /62 /i255 /4 /5 /8 /i255 /17 /13 /12 /4 /7 /13 /63 /4 /i255 /16 /62 /i255 /18 /16 /64 /65 /61/66 /13 /11
/67 /62 /62 /13 /63 /8 /i255 /16 /62 /i255 /4 /5 /8 /i255 /18 /5 /13 /8 /62 /i255 /47 /13 /14 /11 /14 /63 /13 /11 /64 /i255 /67 /62 /62 /13 /63 /8 /7
/67 /62 /62 /13 /63 /8 /i255 /16 /62 /i255 /68 /11 /69 /i255 /11 /14 /70 /i255 /71 /8 /60 /8 /14 /65 /8 /i255
/17 /6 /49 /53 /49 /68 /49 /9 /i255 /49 /50 /18 /72
/73 /0 /19 /1 /i255 /47 /74 /49 /71 /75 /49 /48 /10 /i255 /76 /74 /71 /77 /i255 /17 /71 /i255 /6 /68 /48 /i255 /73 /1 /1
/47 /74 /78 /78 /6 /i255 /18 /79 /80 /71 /18 /79 /i255 /75 /74 /i255 /i255 /19 /19 /1 /3 /19 /53 /3 /81 /56 /1
/i255
/82 /32 /21 /83 /29 /33 /i255 /84 /33 /28 /23 /26 /35 /i255 /84 /25 /85 /85 /23 /29 /22 /28 /25 /83 /i255 /21 /83 /86 /i255 /87 /83 /26 /25 /32 /29 /23 /45/23 /83 /22 /i255 /88 /86 /45/28 /83 /28 /89 /22 /32 /21 /22 /28 /25 /83
/88 /44 /22 /33 /25 /32 /28 /90 /23 /86 /i255 /82 /91 /i255 /31/23 /85 /28 /83 /86 /21 /i255 /92 /23 /83 /93 /28 /83 /89
/68 /16 /i255 /60 /11 /64 /13 /70 /11 /4 /8 /i255 /4 /5 /13 /12 /i255 /63 /8 /7 /4 /13 /62 /13 /63 /11 /4 /8 /9 /i255 /94 /64 /8 /11 /12 /8 /i255 /60 /13 /12 /13 /4 /i255 /95/96 /68 /11 /69 /72 /17 /18 /72 /15 /16 /60 /72 /i255 /67 /14 /i255 /4 /5 /8 /i255 /95/96 /68 /11 /69 /i255 /17 /18 /i255 /5 /16 /61/8 /94 /11 /15 /8 /9 /i255 /63 /64 /13 /63 /97 /i255 /4 /5 /8
/98 /75 /11 /64 /13 /70 /11 /4 /8 /i255 /11 /i255 /18 /8 /7 /4 /13 /62 /13 /63 /11 /4 /8 /i255 /16 /62 /i255 /18 /64 /8 /11 /14 /i255 /79 /11 /14 /70 /12 /99 /i255 /5 /96 /94 /8 /7 /64 /13 /14 /97 /i255 /65 /14 /70 /8 /7 /i255 /4 /5 /8 /i255 /18 /64 /8 /11 /14 /i255 /79 /11 /14 /70 /12 /i255 /12 /8 /63 /4 /13 /16 /14 /72
/100 /101 /102 /103 /104 /105 /104 /100 /106 /103 /101 /i255 /108/105 /i255 /100 /109 /101 /106 /110 /i255 /111/106 /110 /112 /113
/74 /12 /i255 /7 /8 /94 /16 /7 /4 /8 /70 /i255 /13 /14 /i255 /4 /5 /8 /i255 /18 /64 /8 /11 /14 /i255 /79 /11 /14 /70 /12 /i255 /12 /96 /12 /4 /8 /61/9 /i255 /4 /5 /8 /i255 /11 /66 /16 /60 /8 /i255 /7 /8 /62 /8 /7 /8 /14 /63 /8 /70 /i255 /13 /14 /70 /13 /60 /13 /70 /65 /11 /64 /114 /8 /14 /4 /13 /4 /96 /i255 /5 /11 /12 /i255 /14 /16 /i255 /16 /65 /4 /12 /4 /11 /14 /70 /13 /14 /15
/64 /13 /11 /66 /13 /64 /13 /4 /96 /i255 /115 /13 /4 /5 /i255 /4 /5 /8 /i255 /17 /13 /12 /4 /7 /13 /63 /4 /i255 /16 /62 /i255 /18 /16 /64 /65 /61/66 /13 /11 /i255 /67 /62 /62 /13 /63 /8 /i255 /16 /62 /i255 /68 /11 /69 /i255 /11 /14 /70 /i255 /71 /8 /60 /8 /14 /65 /8 /i255 /16 /7 /i255 /4 /5 /8 /i255 /17 /8 /94 /11 /7 /4 /61/8 /14 /4 /i255 /16 /62 /i255 /48 /61 /94 /64 /16 /96 /61/8 /14 /4
/6 /8 /7 /60 /13 /63 /8 /12 /72 /i255 /74 /12 /i255 /16 /62 /i255 /4 /5 /8 /i255 /70 /11 /4 /8 /i255 /11 /66 /16 /60 /8 /9 /i255 /4 /5 /8 /i255 /13 /14 /70 /13 /60 /13 /70 /65 /11 /64 /114 /8 /14 /4 /13 /4 /96 /i255 /5 /11 /12 /i255 /63 /16 /61/94 /64 /13 /8 /70 /i255 /115 /13 /4 /5 /i255 /17 /18 /i255 /18 /16 /70 /8 /i255 /116 /i255 /3 /56 /53 /19 /54 /55 /19 /9 /i255 /i255 /4 /5 /8 /7 /8 /62 /16 /7 /8
/4 /5 /13 /12 /i255 /18 /8 /7 /4 /13 /62 /13 /63 /11 /4 /8 /i255 /16 /62 /i255 /18 /64 /8 /11 /14 /i255 /79 /11 /14 /70 /12 /i255 /13 /12 /i255 /13 /12 /12 /65 /8 /70 /72
/68 /49 /68 /78 /48 /i255 /3 /56 /72 /i255 /68 /74 /117 /74 /68 /49 /67 /50 /9 /i255 /78 /49 /18 /48 /50 /6 /49 /50 /59 /9 /i255 /76 /48 /71 /95/49 /68 /6 /9 /i255 /74 /6 /6 /48 /6 /6 /95/48 /50 /68 /6 /9 /i255 /74 /50 /17 /i255 /47 /48 /48 /6
/18 /79 /74 /76 /68 /48 /71 /i255 /19 /54 /i255 /59 /48 /50 /48 /71 /74 /78 /i255 /78 /49 /18 /48 /50 /6 /48
/6 /80 /118 /18 /79 /74 /76 /68 /48 /71 /i255 /49 /49 /72 /i255 /18 /78 /48 /74 /50 /i255 /79 /74 /50 /17 /6 /i255 /118 /48 /47 /67 /71 /48 /i255 /71 /48 /18 /48 /49 /75 /49 /50 /59 /i255 /74 /i255 /78 /49 /18 /48 /50 /6 /48 /i255 /67 /71 /i255 /76 /48 /71 /95/49 /68
/17 /72 /18 /72 /i255 /18 /67 /17 /48 /i255 /116 /i255 /3 /56 /53 /19 /54 /55 /19 /i255 /119 /19 /1 /1 /55 /120
/116 /i255 /3 /56 /53 /19 /54 /55 /19 /i255 /76 /71 /67 /79 /49 /118 /49 /68 /49 /67 /50 /i255 /74 /59 /74 /49 /50 /6 /68 /i255 /49 /6 /6 /80 /74 /50 /18 /48 /i255 /67 /47 /i255 /78 /49 /18 /48 /50 /6 /48 /i255 /67 /71 /i255 /76 /48 /71 /95/49 /68
/121 /121 /122 /121 /i255 /123 /124 /125 /i255 /113 /124 /126 /127 /127 /124 /i255 /113 /128/129 /i255 /113 /130 /131 /124 /127 /i255 /128/132 /133 /122 /129 /i255 /128/134 /135 /125 /131 /136 /137 /124 /138 /136 /129 /i255 /112 /100 /i255 /132 /122 /122 /132 /123 /139 /140 /125 /138 /136 /127 /141 /i255 /142 /132 /122 /132 /143 /i255 /133 /132 /123 /144 /145 /122 /123 /145 /139 /146/147 /103 /134 /148 /149 /112 /100 /149 /137 /138 /150
/i255

GOVERNMENT OF THE DISTRICT OF COLUMBIA
OFFICE OF THE ASSOCIATE CHIEF FINANCIAL OFFICER
PUBLIC SAFETY & JUSTICE CLUSTER

MEMORANDUM

TO: Nancy Hapeman, Chief Procurement Officer
Office of Contracts and Procurement

FROM: David Garner, Associate Chief Financial Officer
Office of the Chief Financial Officer

DATE: April 7, 2026

SUBJECT: Certification of Funding for Upgrading and Maintenance Offender
Management System (CW130494)

The Office of the Chief Financial Officer certifies available funding in the amount of $2,129,325.00 for
Department of Corrections approved FY26 – FY31 capital budget for the contract and amount listed in the
table below. Future orders above the available funding are contingent upon the identification of additional
funding.

If you have any questions, please feel free to contact Anthony Norman, Agency Fiscal Officer at (202) 834-
7744.

1100 Fourth Street SW Suite 730E Washington, DC 20024
Contract Title Period of
Performance
Contract
Period
Contractor Name OCFO Certified
Amount
CW130494 Upgrading and
Maintenance
Offender
Management
System
09/26/2025 -
09/25/2026

Base Year DSI-ITI, Inc. d/b/a
ViaPath
Technologies
$2,129,325.00

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: April 17, 2026

SUBJECT: Approval of Offender Management System Letter Contract
Contractor: DSI-ITI, Inc. d/b/a Viapath Technologies
Contract Number: CW130494
Contract Amount: $2,129,325.00

This is to Certify that this Office has reviewed the above-referenced Modification and that we
have found it to be legally sufficient. If you have any questions in this regard, please do not
hesitate to call me at (202) 724-4018.

______________________________
Robert Schildkraut

GOVERNMENT OF THE DISTRICT OF COLUMBIA Office of Contracting and Procurement September 26, 2025DSI-ITI, Inc. d/b/a ViaPath Technologies 3120 Fairview Park Drive, Suite 300, Falls Church, VA 22042 Subject: Letter Contract: offender management system.Attention: Mr. Jim BradleyPer 27 DCMR § 2425.1. The contracting officer may use a letter contract when the District’s interests require that the contractor be given a binding commitment so that work can start immediately and executing a definitive contract is not possible in sufficient time to meet the requirement. Each letter contract shall be as complete and definite as possible under the circumstances.This is a Letter Contract between the District of Columbia (the District) on behalf of theDepartment of Corrections (DOC) and DSI-ITI, Inc. dba ViaPath Technologies referred to as theContractor, wherein the Contractor agrees to provide Offender Management System (OMSe) Maintenance and Support to the District’s DOC.The District intends to definitize this Letter Contract within 120 calendar days from date of execution by the Contracting Officer, at which time this Letter Contract shall merge with the Definitized Contract. The contracting officer may extend the letter contract but shall nevertheless execute a definitive contract prior to completion of fifty percent (50%) of the work to be performed. The total not-to-exceed value of this Letter Contract is $500,000.00If the District does not definitize this Letter Contract within 120 calendar days from the date of execution or extends thereafter; this Letter Contract shall expire. In the event of expiration of this Letter Contract, the District shall pay Contractor for services performed not-to-exceed amount of $500,000.00The contractor shall perform under this Letter Contract pursuant to the terms of the following documents, which are hereby incorporated by reference and made a part of this Letter Contract:•This Letter Contract•Terms and Conditions of DSI-ITI, Inc. d/b/a ViaPath Technologies Technical Proposal

AMENDMENT OF SOLICITATION / MODIFICATION OF CONTRACT1.ContractNumberPageofPagesCW1297511 12. Amendment/Modification Number 3. Effective Date 4. Requisition/Purchase Request No. 5. Solicitation CaptionM0001 01/25/2026 offender management system6.Issuedby:Code7.Administeredby(Ifotherthanline6)Office of Contracting and Procurement 441 4th Street NW, Suite 700S Washington, DC 20001Department of Employment Services 4058 Minnesota Ave, NE Washington, D.C. 200198. Name and Address of Contractor (No. street, city, county, state andzip code)DSI-ITI, Inc. d/b/a ViaPath Technologies 3120 Fairview ParkDrive, Suite 300,Falls Church, VA 220429A. Amendment of Solicitation No.9B. Dated (See Item 11)X 10A. Modification of Contract/Order No.CW12975110B. Dated (See letter Contract)09/26/2611.THISITEMONLYAPPLIESTOAMENDMENTSOFSOLICITATIONSThe above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended. is not extended.Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:(a) By completing Items 8 and 15, and returning copies of the amendment: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c)BY separate letter or fax which includes a reference to the solicitation and amendment number. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACEDESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of thisamendment you desire to change an offer already submitted, such may be made by letter or fax, provided each letter or telegram makes reference to the solicitation and thisamendment, and is received prior to the opening hour and date specified.12. Accounting and Appropriation Data (If Required)13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS,IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14A. This change order is issued pursuant to (Specify Authority): 27 DCMR, Chapter 36, Contract ModificationsThe changes set forth in Item 14 are made in the contract/order no. in item 10A.B. The above numbered contract/order is modified to reflect the administrative changes (such as changes in paying office, appropriation dataetc.) set forth in item 14, pursuant to the authority of 27 DCMR, Chapter 36, Section 3601.2.X C. This supplemental agreement is entered into pursuant to authority of 27 DCMR 2425.8X D. Other (Specify type of modification and authority)27 DCMR Section 2008 Exercise of optionE. IMPORTANT:Contractor is not is required to sign this document.14. Description of Amendment/Modification (Organized by UCF Section headings, including solicitation/contract subjectmatter where feasible.)The Letter contract CW129751 for Offender Management Systems for DOC is hereby modified as follows:1. In accordance with Section 27 DCMR 2425.8, the Government of District of Columbia, Office of Contracting andProcurement on behalf of the D.C. Department of Corrections, hereby extend the letter contract period ofperformance for an additional period of 120 days from January 25, 2026, through May 24, 2026. As a result of thischange, the letter contract total not-to-exceed (NTE) has increased from $500,000 to $1,000,000.2. All other terms and condition remain the same.Exceptasprovidedherein,alltermsandconditionsofthecontractremainunchanged.15A. Name and Title of Signer (Type or print) 16A. Name of Contracting OfficerAtiqullah Babajee15B. Contractor Signature 16B.District of Columbia(Signature of person authorized to sign) (Signature of Contracting Officer)

AMENDMENT OF SOLICITATION / MODIFICATION OF
CONTRACT
1. Contract Number Page of Pages
CW130494 1 3
2. Amendment/Modification Number 3. Effective Date 4. Requisition/Purchase Request No. 5. Solicitation Caption
M0002 See 16B offender management system
6. Issued by: Code 7. Administered by (If other than line 6)
Office of Contracting and Procurement
441 4th Street NW, Suite 700S
Washington, DC 20001
Department of Employment Services
4058 Minnesota Ave, NE
Washington, D.C. 20019
8. Name and Address of Contractor (No. street, city, county, state and
zip code)
DSI-ITI, Inc. d/b/a
ViaPath Technologies
3120 Fairview Park
Drive, Suite 300,
Falls Church, VA 22042
9A. Amendment of Solicitation No.
9B. Dated (See Item 11)
X
10A. Modification of Contract/Order No.
CW130494
10B. Dated (See letter Contract)
09/26/26
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended. is not extended.
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:
(a) By completing Items 8 and 15, and returning copies of the amendment: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c)
BY separate letter or fax which includes a reference to the solicitation and amendment number. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE
DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this
amendment you desire to change an offer already submitted, such may be made by letter or fax, provided each letter or telegram makes reference to the solicitation and this
amendment, and is received prior to the opening hour and date specified.
12. Accounting and Appropriation Data (If Required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS,
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14
A. This change order is issued pursuant to (Specify Authority): 27 DCMR, Chapter 36, Contract Modifications
The changes set forth in Item 14 are made in the contract/order no. in item 10A.
x B. The above numbered contract/order is modified to reflect the administrative changes (such as changes in paying office, appropriation data
etc.) set forth in item 14, pursuant to the authority of 27 DCMR, Chapter 36, Section 3601.2.
C. This supplemental agreement is entered into pursuant to authority of 27 DCMR 2425.8
D. Other (Specify type of modification and authority)
27 DCMR Section 2008 Exercise of option
E. IMPORTANT: Contractor is not is required to sign this document.
14.Description of Amendment/Modification (Organized by UCF Section headings, including solicitation/contract
subject
matter where feasible.)
The
Definitized contract CW130494 for Offender Management Systems for DOC is hereby modified as follows:
1. All
clauses regarding the subcontracting plan have been deleted in their entirety.
2. Section
F.3.1, regarding the submission of the 51% New Hires Requirement compliance report, is hereby incorporated as
Attachment A.
3. Section G.3 has been revised and replaced by Attachment B.
Except as provided herein, all terms and conditions of the contract remain unchanged.
15A. Name and Title of Signer (Type or print) 16A. Name of Contracting Officer
Atiqullah Babajee
15B. Contractor Signature 16B.District of Columbia
(Sign
ature of person authorized to sign) (Signature of Contracting Officer)
Date:3/19/2026
4. Section I.14-17 have been added to the contract as Attachment C.
List of Attachments
Attachment A
F.3.1 For contracts subject to the 51% District Residents New Hires Requirements and First Source Employment
Agreement requirements, the Contractor shall submit to the Contract Administrator, as a deliverable, the
compliance report or a waiver of compliance with its final request for payment.
Attachment B
G.3 FIRST SOURCE AGREEMENT REQUEST FOR FINAL PAYMENT
G.3.1 For contracts subject to the 51% District Residents New Hires Requirements and First Source Employment
Agreement requirements, final request for payment must be accompanied by the compliance report or a waiver
of compliance.
G.3.2 The District may impose monetary fines for willful breach of the employment agreement or failure to submit
the compliance report.
Attachment C
I.14 COST AND PRICING DATA
Delete Article 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 SPECIAL PROVISION RELATED TO CITY ADMINISTRATOR’S ORDER 2022-3
RESERVED
I.16 CAMPAIGN FINANCE REFORM
I.16.1 Mandatory Certification
I.16.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.16.1.2 The Contractor shall re-certify prior to the exercise of any option period 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
.16.2 Reporting Contractor’s Principals
C
ontractors shall inform the contracting officer of any change to its principals during the term of the contract within
thirty (30) days of its occurrence.
I
.16.3 Prohibited Contributions
I
.16.3.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.3.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 1 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)
D
uring the performance of the contract, 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.
AWARD/CONTRACT
1. Caption
Upgrading Offender Management System (OMSe)
Maintenance and Support
Page of Pages
1 90
2. Contract Number 3. Effective Date
See Section 20C
4. Requisition/Purchase Request/Project No.
CW130494
5. Issued By: Code 6. Administered by (If other than line 5)
Office of the Contracting and Procurement
441 4th Street, NW, Suite 700 South
Washington, DC 20001
D.C. Department of Corrections
3924 Minnesota Avenue, 2nd Floor
Washington, D.C. 20019
7. Name and Address of Contractor (No. street, city, county, state and Zip Code)
DSI-ITI, Inc. d/b/a ViaPath Technologies (Contractor)
3120 Fairview Park Drive, Suite 300,
Falls Church, VA 22042
8. Delivery
FOB Origin Other
9. Discount for prompt payment:
10. Submit invoices to the Address shown in Section 6 (2
copies unless otherwise specified)
Attn: Accounts Payable Duns No. TIN
11. Ship to/Mark For Code 12. Payment will be made by Code
D.C. Department of Corrections
3924 Minnesota Avenue, 2nd Floor
Washington, D.C. 20019
D.C. Department of Corrections
3924 Minnesota Avenue, 2nd Floor
Washington, D.C. 20019
13. Remit Address:
Same as 7
14. Accounting and Appropriation Data
ENCUMBRANCE CODE:
15A. Item 15B. Supplies/Services 15C. Qty. 15D. Unit 15E. Unit Price 15F. Amount
Upgrading Offender Management System (OMSe) 1 Lot $2,129,325
Maintenance and Support
Total Amount of Contract Shall Not Exceed  $2,129,325
16. Table of Contents
(X) Section Description Page (X) Section Description Page
PART I – THE SCHEDULE PART II – CONTRACT CLAUSES
X A Award/Contract Form X I Contract Clauses
X B Price Schedule PART III – LIST OF DOCUMENTS, EXHIBITS AND
OTHER ATTACHMENTS
X C Services-Specifications/Work Statement X J List of Attachments
X D Packing and Marking
X E Inspection and Acceptance Representations, Certifications and Other
Statements of Offerors X F Contract Term
X G Contract Administration data Instructions, conditions & notices to Offerors
X H Special Contract Requirements Evaluation factors for award
Contracting Officer will complete Item 17 or 18 as applicable
17. CONTRACTOR’S NEGOTIATED AGREEMENT
(Contractor is required to sign this document and return (2) copies to issuing office.)
Contractor agrees to furnish and deliver all items, perform all the services set forth or
otherwise identified above and on any continuation sheets, for the consideration stated
herein. The rights and obligations of the parties to this Agreement shall be subject to and
governed by the following documents: (a) this award/contract, (b) the solicitation, as
amended, and (c) such provisions,
representations, certifications, and specifications, as are attached or incorporated by
reference herein. (Attachments are listed herein.)
18. AWARD (Contractor is not required to sign this document.)
Your offer on Solicitation Number including the additions or changes made
by which additions or changes are set forth in full above, is hereby
accepted as to the items listed in B.3 and on any continuation sheets. This
award consummates the contract which consists of the following
documents: (a) this award/contract, and (b) your offer. No further
contractual document is necessary.
19A. Name and Title of Signer (Type or print)
Matthew Caesar - President
20A. Name of Contracting Officer
Atiqullah Babajee
19B.
(Signature of person authorized to sign)
19C. Date Signed
04/14/2026
20B. District of Columbia
(Signature of Contracting Officer)
20C. Date Signed

SECTION B: CONTRACT TYPE, SUPPLIES OR SERVICES AND PRICE/COST
B.1 The District of Columbia Office of Contracting and Procurement (OCP), on behalf of the D.C. Department of
Corrections (District), is awarding an Exempt from Competition contract In accordance with the Code of the
District of Columbia Section 2 -354.13, (8) to provide Upgrading Offender Management System (OMSe)
Maintenance and Support.

B.2 LETTER CONTRACT

This is the definitized contract, as contemplated by the awarded Letter contract on September 26, 2025. The
Letter Contract is merged herewith and is superseded by this Contract. The Definitized contract shall be
for one year from date of award.
B.3 The District contemplates the award of a firm-fixed-price contract in accordance with 27 DCMR
Chapter 24.

B.4 PRICE SCHEDULE

B.4.1 Base Period: One year from date of award

Contract Line-
Item No. (CLIN)
Item Description Quantity Unit Price Total Price
0001 Project Initiation
• Internal handoff and onboarding of
ViaPath’s implementation team
• Initial planning and kickoff activities
• Assignment of project teams and
stakeholder alignment
• Development and approval of the project
charter
1 $851,730 $851,730
0002 Planning Phase
• Detailed project plan and schedule
• UAT and training plans
• Communications and change
management strategies
• Environment readiness assessments
• RACI matrix and risk management
framework
1 $1,277,595 $1,277,595
Base Year Total Price $2,129,325

B.4.2 Option Year One

CLIN Item Description Quantity Unit Price Total Price
1001 User Acceptance Testing Completed
• Execution of test cases by DC DOC
• Validation of system functionality,
integrations, and configurations
• Resolution of identified issues
• Final UAT sign-off
1 $1,064,662 $1,064,662

1002 System Go-Live
• Final data migration and cutover
• Transition of OMSe to live operations
• Real-time support and monitoring
• Initial post-Go-Live stabilization

1

$638,798

$638,798
1003 Project Closeout
• Completion of all deliverables and
documentation
• Knowledge transfer and training wrap-
up
• Final stakeholder review and lessons
learned
• Formal project sign-off

1

$425,865

$425,865
Option Year One Total Price $2,129,325

B.4.2 Option Year Two

CLIN Item Description Total Price
2001 Operations and Maintenance $366,788
Option Year Two Total Price $366,788

B.4.3 Option Year Three

CLIN Item Description Total Price
3001 Operations and Maintenance $376,977
Option Year Three Total Price $376,977

B.4.4 Option Year Four

CLIN Item Description Total Price
4001 Operations and Maintenance $387,676.00
Option Year Four Total Price $387,676.00
B.5 NONPROFIT FAIR COMPENSATION ACT OF 2020, D.C. Code § 2-222.01 et seq.
B.5.1 Nonprofit organizations, as defined in the Act, shall include in their rates the indirect costs
incurred in the provision of goods or performance of 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 2 years; however, a nonprofit
organization may request to renegotiate indirect costs 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.5.2 If this contract is funded by a federal agency, indirect costs shall be consistent with the
requirements for pass-through entities in 2 C.F.R. § 200.331 or any successor regulations.
B.5.3 The Contractor shall pay its subcontractors, which are nonprofit organizations, the same
indirect cost rates as the nonprofit organization subcontractors would have received as a
prime contractor.

SECTION C: SPECIFICATIONS/WORK STATEMENT
C.1 SCOPE:
ViaPath Technologies will lead the transition from the legacy PowerBuilder- based Jail and
Community Corrections System (JACCS) to the latest Commercial Off- The-Shelf (COTS)
version of OMSe.

ViaPath Technologies will deliver an on- premise OMSe solution that includes all required
services for successful deployment, configuration, data migration, reporting needs, training,
and support. The OMSe platform is designed to meet the operational needs of DC DOC with
minimal custom development, leveraging its out- of-the-box capabilities to the greatest
extent possible.

C.2 BACKGROUND
The primary objective of this engagement is to ensure a timely and seamless transition
from JACCS to OMSe. To achieve this, ViaPath will conduct a comprehensive analysis of
existing business functions supported by JACCS. Each function will be addressed in
OMSe through configuration, business process alignment, or, where necessary, limited
custom development.
This implementation strategy is intended to ensure that all critical business requirements
currently fulfilled by JACCS are preserved or enhanced in the new system, with no
functional gaps. Additionally, any desired enhancements or future-state capabilities
The scope of this project encompasses the full implementation of the OMSe software solution for the
District of Columbia Department of Corrections (DC DOC), following a structured, phased approach
designed to ensure successful deployment and alignment with operational requirements.
Key scope elements include:
OMSe will be implemented as a Commercial Off-The-Shelf (COTS) product, leveraging its native
functionality to minimize custom development.
Only those modifications necessary to meet DC DOC’s current business requirements—specifically
those supported by the legacy JACCS system and not available in OMSe—will be implemented.
Any desired enhancements or additional features identified during discovery and analysis will be
documented for consideration in future development phases.
Comprehensive testing will be conducted to validate system configuration,
identified during the discovery and analysis phases will be documented for potential
inclusion in a future upgrade or enhancement project.

C.3 REQUIREMENTS

The implementation of the OMSe software solution will follow a structured, phased
project management methodology designed to ensure successful delivery,
alignment with DC DOC’s operational needs, and effective stakeholder engagement.
The project will proceed through the following key phases:

1. Project Management Approach

A. Initiation
This phase establishes the foundation for the project. It includes defining the
project’s objectives, scope, high-level deliverables, constraints, and
assumptions. Key stakeholders are identified, and roles and responsibilities are
assigned. A formal kickoff meeting will be conducted to ensure alignment
across all parties.

Milestones:
• ViaPath and DC DOC project teams assigned
• Project Kickoff Meeting Completed
• Project Charter Finalized and Approved
• Stakeholder Roles and Responsibilities Defined
• SOW Review Completed
• Stakeholder Engagement Plan Approved

B. Planning
During this phase, a detailed project plan is developed, including the work
breakdown structure (WBS), schedule, resource allocation, risk management
strategy, and communication plan. As part of this phase, a comprehensive
User Acceptance Testing (UAT) Plan and Training Plan will also be developed
to guide testing and knowledge transfer activities. The planning process
ensures that all project activities are clearly defined, sequenced, and aligned
with success criteria.

Milestones:
• Detailed Project Plan Developed and Approved
• Communication and Change Management Plans Finalized
• User Acceptance Testing (UAT) Plan Completed
• Training Plan Completed
• Environment Readiness Assessment Completed
• Discovery Sessions Completed
• RACI Matrix Approved
workflows, reporting capabilities, and data migration accuracy across all
functional areas.
• User Acceptance and Training
The project will include User Acceptance Testing (UAT), a Train -the-Trainer
program to prepare internal trainers, and full support for Go-Live activities to
ensure a smooth transition to the new system.
• Training Delivery (Train-the-Trainer) Completed
• Environment Installation Verified
• Interface Connectivity
• Functional Area Acceptance Sign-Offs
• Performance Metrics Tracked Against Baseline
• Monthly Governance Review
• RAID Log Updated and Reviewed
o Risk and Issue Management Framework Activated
C. Execution
The execution phase involves the implementation of planned activities,
including system configuration, data migration, interface development,
training, and testing. Project tasks are assigned, progress is monitored, and
deliverables are produced in accordance with the project schedule.
• Milestones:
• System Configuration and Customization Completed
• Interface Development and Integration Completed
• Data Migration (Initial Load) Completed
• Functional Area Testing Completed

D. Monitoring and Control
Throughout the project lifecycle, performance will be continuously monitored
against the baseline plan. This includes tracking milestones, managing risks
and issues, and implementing change control procedures to address scope
adjustments or unforeseen challenges.

Milestones:
• Weekly Status Reports and Risk Logs Maintained
• Change Requests Reviewed and Approved as Needed

E. Closure
Upon completion of all deliverables, the project will enter the closure phase.
This includes final validation, stakeholder sign-off, knowledge transfer, and
documentation of lessons learned. A formal project closeout will ensure a
smooth transition to ongoing operations and support.
Milestones:
• User Acceptance Testing (UAT) Completed and Approved
• Go-Live Executed Successfully
• Post-Go-Live Support Period Completed
• Final Project Review and Lessons Learned Documented
• Formal Project Closure and Sign-Off
• Final Data Migration Validation
• Internal handoff documentation summarizing background,
commitments, and expectations
• Knowledge Transfer Completion
• Support Transition Plan Approved
2. Project Phase Details
2.1. Initiation
The Initiation Phase serves as the strategic foundation of the OMSe
implementation project. It begins within 30 days of the acceptance of the
Statement of Work (SOW) by both the District of Columbia’s Office of
Contracting and Procurement (OCP) and ViaPath Technologies. During this
period, ViaPath will conduct an internal handoff from the Sales Account
Manager and OMSe Director to the assigned Implementation Manager. This
transition ensures that all relevant background, commitments, and
expectations are clearly communicated to the delivery team.
Once the internal handoff is complete, the Implementation Manager will lead
a comprehensive review of the SOW and any supporting documentation
provided by DC DOC. This review is critical to ensure a shared understanding
of the project’s scope, objectives, constraints, and deliverables. It also sets the
stage for aligning execution strategy with operational realities.
In parallel, both ViaPath and DC DOC will formally assign their respective
project teams. This includes identifying key personnel such as the
Implementation Manager, Technical Leads, Business Analysts, and the DC
DOC Project Manager. Each team member’s role and responsibilities will be
clearly defined and documented to establish accountability and streamline
communication.
A formal project kickoff meeting will be scheduled and conducted with all key
stakeholders. This meeting will serve as the official launch of the project and
will include introductions, a review of the project charter, discussion of high-
level timelines, communication protocols, and escalation procedures. The
kickoff will also confirm mutual understanding of the project’s goals and
expectations, ensuring that all parties are aligned before moving into the
planning phase.
By the end of the Initiation Phase, the project charter will be finalized and
approved. This document will encapsulate the project’s purpose, scope,
objectives, assumptions, and constraints, and will serve as a guiding reference
throughout the project lifecycle. Additionally, a stakeholder matrix will be
developed to document all key participants and their roles, ensuring clarity in
decision-making and communication.
Initiation Phase Deliverables

This phase concludes with the achievement of several key milestones: the
assignment of project teams by both ViaPath and DC DOC, the successful
completion of the project kickoff meeting, the finalization and approval of the
project charter, and the formal definition of stakeholder roles and
responsibilities.
The Planning Phase builds upon the foundation established during Initiation
and transitions the project into a structured, execution-ready state. This phase
is critical for aligning expectations, defining the delivery roadmap, and
preparing both ViaPath and DC DOC teams for implementation activities. It
also introduces enhanced governance and risk mitigation strategies to
address known project gaps and ensure successful execution.
ViaPath will lead a comprehensive discovery process to gather detailed
requirements, validate assumptions, and assess the readiness of the technical
environment. This includes identifying and sequencing functional areas for
configuration and testing, establishing remote access for project execution,
and confirming the availability of DC DOC staff and external stakeholders
required for system configuration, testing, and acceptance.
To ensure clarity in ownership and accountability, a Responsibility Assignment
Matrix (RACI) will be developed. This matrix will define roles for all major
deliverables, including UAT, data migration, interface testing, and report
validation. Additionally, a formal change control process will be documented
and reviewed with stakeholders, outlining procedures for evaluating and
approving any proposed changes to scope, schedule, or deliverables.
All change requests must be submitted in writing and will be reviewed jointly
by ViaPath and DC DOC project leadership. The process includes:
• Submission: A Change Request Form is completed with details of the
proposed change, rationale, and potential impact.
• Impact Assessment: ViaPath evaluates the effect on scope, schedule,
cost, and risk.
• Review and Approval: The request is reviewed by the project
governance team. Approval from both parties is required before
implementation.
• Documentation: Approved changes are logged in the Change Log and
reflected in the updated project plan and deliverables.

2.2. Planning

• Reviewed and annotated Statement of Work and supporting materials
• Assigned project teams with documented roles and responsibilities
• Conducted project kickoff meeting with stakeholder participation
• Finalized and approved project charter
• Stakeholder matrix identifying key participants and their roles
• Defined communication protocols and escalation procedures
This process ensures transparency, accountability, and alignment on all
project adjustments.
A risk and issue management framework will be implemented, including:
• Defined service level agreements (SLAs) for issue resolution (e.g., critical
issues resolved within 3 business days)
• Escalation paths and response timelines
• A living RAID log (Risks, Assumptions, Issues, Dependencies) updated
weekly
UAT activities will be scoped and scheduled as part of the Execution and
Monitoring phases. ViaPath will support UAT preparation by providing
documentation, test environment setup, and issue resolution support. DC
DOC will lead and execute UAT, including the development of test cases and
validation of system functionality.
Final UAT acceptance will be the responsibility of DC DOC and is a
prerequisite for the Go/No-Go decision for production deployment. UAT
results, including any unresolved issues, will be reviewed jointly by ViaPath
and DC DOC prior to Go-Live readiness confirmation.
For data migration, ViaPath and DC DOC will jointly define data validation
criteria and acceptance thresholds. A Data Exception Log will be maintained
to track unconvertible records and document mitigation strategies. A Data
Migration Readiness Review will be scheduled prior to UAT to confirm
preparedness.
To support reporting governance, the number of custom report
units included in scope will be defined, and a report review and acceptance
process will be established. Report requirements will be defined during
discovery and configuration, and acceptance of a functional area will be
considered acceptance of all reports delivered for that area. ViaPath will track
report unit usage and coordinate with DC DOC to manage any requests for
additional reports or modifications through the change control process.
A resource capacity analysis will be conducted to ensure that SME availability
aligns with the functional area schedule. If conflicts are identified, the project
plan will be adjusted accordingly to avoid overextension of key personnel.
The Mock Go-Live will be scheduled with a minimum two-week buffer before
the production Go-Live. Success criteria and fallback procedures will be
documented in the Go-Live Plan, and a formal readiness review will be
conducted.
Finally, documentation and knowledge transfer planning will include:
• Defined quality and completeness criteria for user guides and training
materials
• A feedback loop to incorporate training evaluations into continuous
improvement
The Execution Phase marks the transition from planning into active
implementation, where the OMSe solution is configured, tested, and prepared
for deployment. This phase is focused on delivering the core components of
the system in alignment with the approved project plan and ensuring that all
technical and functional requirements are met through collaborative
execution.

• A Knowledge Transfer Checklist to ensure all materials are delivered and
reviewed prior to project closure
Planning Phase Deliverables:
• Detailed project plan including:
• Work breakdown structure (WBS)
• Task dependencies and timelines
• Resource assignments
• Responsibility Assignment Matrix (RACI)
• User Acceptance Testing (UAT) Plan with acceptance criteria
• Training Plan with feedback integration
• Communications Plan with escalation paths
• Issue and risk tracking tools with SLAs
• Change Control Process documentation
• Data Migration Plan with validation criteria and exception tracking
• Reporting Governance Plan
• Mock Go-Live Plan with success criteria and buffer schedule
• Knowledge Transfer Checklist
• Execution environment readiness documentation:
• Hardware specifications and network diagrams
• Architecture review feedback
• VPN and access credential setup
• Logistical coordination documentation:
• Project team assignments
• SME scheduling plans
• On-site and remote session schedules
• Formal approval of all foundational planning documents
2.3. Execution

• Configured OMSe system modules, workflows, business rules, and user
roles
• Developed and tested system interfaces with external systems (e.g.,
LDAP, VINE, Keefe, VisManager)
• Data migration artifacts including:
ViaPath will begin by configuring the OMSe application based on the
requirements gathered during the discovery phase. This includes setting up
system modules, workflows, business rules, and user roles to reflect DC DOC’s
operational needs. Configuration will be performed in close coordination with
DC DOC subject matter experts, who will provide use cases, documentation,
and feedback to ensure the system aligns with current business processes.
Interface development will be initiated to support integration with external
systems such as Active Directory (LDAP), VINE, Keefe Commissary,
VisManager, and others. ViaPath will design, build, and test each interface in
collaboration with DC DOC and third-party vendors, ensuring secure and
reliable data exchange. DC DOC will provide technical contacts and facilitate
coordination with external agencies to support interface implementation.
Data migration activities will begin with mapping legacy JACCS data to the
OMSe schema. ViaPath’s data analysts will perform iterative test conversions
in a staging environment to validate accuracy and refine transformation logic.
DC DOC will provide remote access to the legacy database and participate in
validation efforts to confirm data integrity. Migration will occur in phases,
including functional area- specific conversions, full conversion for UAT, and
final conversion for Go-Live.
Functional area testing will be conducted to validate system operations,
including configuration, workflows, reports, and data migration. DC DOC will
execute use cases and participate in solution demonstrations to confirm that
the system meets business requirements. Any issues identified during testing
will be documented, tracked, and resolved collaboratively.
Training activities will also be launched during execution. ViaPath will deliver
Train-the-Trainer sessions to prepare DC DOC’s internal trainers for end-user
instruction. Training will be structured by functional area and tailored to
operational roles. DC DOC will schedule and provide subject matter experts
for participation, and ViaPath will supply training materials, including user
guides and quick reference cards.
Throughout this phase, ViaPath will provide services during normal business
hours (M–F, 8:00 AM – 5:00 PM EST) and coordinate remote sessions with
assistance from the DC DOC Project Manager. On-site resources will be
deployed for key milestones such as Train-the-Trainer, UAT, and Go-Live.
Execution Phase Deliverables

• Data mapping documentation
Execution concludes when all system components have been configured,
tested, and validated; training has been delivered; and the system is ready for
User Acceptance Testing. The successful completion of these activities will be
confirmed through milestone reviews and formal sign-offs, paving the way for
final acceptance and Go-Live preparation.

2.4. Monitoring and Control
The Monitoring and Control Phase runs concurrently with execution and
continues through the remainder of the project lifecycle. Its purpose is to
ensure that all project activities remain aligned with the approved plan, that
risks are proactively managed, and that performance is continuously
measured against established baselines.
ViaPath will implement a structured approach to track progress, manage
issues, and maintain transparency with DC DOC stakeholders. The project
schedule, developed during the planning phase, will serve as the baseline for
monitoring task completion, milestone achievement, and resource utilization.
Any deviations from the schedule will be identified early and addressed
through collaborative problem-solving and formal change control procedures.
Weekly status meetings will be held between ViaPath and DC DOC project
teams to review accomplishments, discuss upcoming activities, and address
any emerging risks or issues. These meetings will be supported by written
status reports that include updates on task progress, risk and issue logs, and
any changes to the project timeline or scope. The reports will also include
performance metrics such as milestone completion rates, open issue counts,
and resolution timelines.
Risk management is a key component of this phase. ViaPath will maintain a
living risk register that identifies potential threats to project success, assesses
their likelihood and impact, and outlines mitigation strategies. High-priority
risks will be reviewed weekly, and contingency plans will be activated as
needed to keep the project on track.
• Test conversion results
• Validated data sets for UAT and Go-Live
• Functional area testing results and issue resolution logs
• Train-the-Trainer sessions and supporting training materials:
• User guides
• Quick reference cards
• Coordination and scheduling documentation for remote and on-site
activities
• Milestone review documentation and formal sign-offs confirming
readiness for UAT
Weekly written status reports including:
•
•
•
•
•
• Likelihood and impact assessments
• Mitigation strategies and contingency plans
•
•
•
•
Severity categorization
Resolution tracking and escalation records
• Approved change requests with documentation of evaluation and
• Updated project documentation including:
•
•
•
•
Project plan
Meeting
Change control records
•
The Monitoring and Control Phase ensures that the project remains focused,
responsive, and aligned with its objectives. It provides the structure and

Issue management will follow a structured process to ensure timely
resolution. All issues will be logged, categorized by severity, and assigned to
appropriate team members for resolution. Critical issues that impact
schedule, scope, or quality will be escalated to project leadership for
immediate attention. A formal change control process will be used to evaluate
and approve any proposed changes to the project scope, schedule, or
deliverables.
Throughout this phase, ViaPath will ensure that all project documentation is
kept current and accessible. This includes updates to the project plan, risk and
issue logs, meeting minutes, and approved change requests. These artifacts
will be stored in a shared repository accessible to both ViaPath and DC DOC
teams, ensuring transparency and accountability.

Monitoring and Control Phase Deliverables
• Verified and finalized project deliverables:
•
•
•
•
Configuration records
Final data migration reports
• Formal system acceptance documentation

2.5. Closeout
The Closeout Phase represents the formal conclusion of the OMSe
implementation project and marks the transition from project execution to
ongoing operations and support. This phase ensures that all project objectives
have been met, deliverables have been accepted, and knowledge transfer has
been completed to enable DC DOC to sustain the system independently.
ViaPath will conduct a comprehensive review of all project deliverables,
including system documentation, training materials, configuration records,
and final data migration reports. Together with DC DOC, we will verify that
each deliverable meets the specifications and quality standards outlined in
the Statement of Work (SOW). Any outstanding items will be addressed
through final revisions or clarifications to ensure full alignment with project
expectations.
A formal system acceptance process will be conducted to confirm that the
OMSe solution is functioning as intended in the production environment. This
includes validation that all modules, interfaces, reports, and user roles are
operating correctly, and that any issues identified during User Acceptance
Testing (UAT) and Go-Live have been resolved. Upon acceptance, the system
will be considered fully transitioned to DC DOC ownership.
Knowledge transfer is a critical component of this phase. ViaPath will ensure
that DC DOC’s designated administrators and support personnel are
equipped with the necessary documentation, tools, and training to manage
the system post-implementation. This includes walkthroughs of system
configuration, user management, reporting tools, and maintenance
procedures. Final Train-the-Trainer sessions or refresher trainings will be
delivered as needed to reinforce system proficiency.
Additionally, all administrative records and project documentation will be
finalized and archived. A final project review will be conducted with key
stakeholders to reflect on the project’s outcomes, challenges, and lessons
learned, supporting continuous improvement in future initiatives.
Closeout Phase Deliverables

discipline necessary to manage complexity, adapt to change, and deliver a
successful outcome.
The Closeout Phase concludes with formal sign-off from DC DOC,
acknowledging that all deliverables have been received and accepted, and
that the project is complete.

3. Technical Environment Responsibilities
This section outlines the responsibilities of DC DOC and ViaPath related to the
technical environment required to support the OMSe application. These
responsibilities are essential to ensuring a stable, secure, and accessible
infrastructure for successful implementation and ongoing operation.
DC DOC is responsible for procuring, providing, and maintaining all hardware and
third-party software necessary to support the OMSe application and its associated
functions. As part of this responsibility, DC DOC will review the OMSe hardware
specifications and provide a detailed diagram of the future OMSe environment. This
diagram must include all hardware components, network infrastructure, and third-
party software that will be used to support the system.
ViaPath will review the proposed OMSe architecture and provide technical guidance
as needed to support informed decision-making regarding the environment. This
collaboration ensures that the infrastructure is aligned with OMSe requirements and
best practices.
DC DOC will ensure and maintain network connectivity for all workstations requiring
access to the OMSe environment. This includes configuring firewalls, network
security settings, and VPN access as necessary to support secure and reliable
connectivity.
Ongoing server maintenance is also the responsibility of DC DOC. This includes
applying operating system updates, security patches, and monitoring system
performance to ensure optimal operation. Additionally, DC DOC will manage
database backup and maintenance in accordance with its disaster recovery policies
to ensure data integrity and availability in the event of system failure or data loss.
To support uninterrupted project execution, ViaPath will require 24x7 access to the
OMSe environment. DC DOC is responsible for providing and maintaining the
•
•
• Archived project documentation:
•
Change logs
• Final project review and lessons learned summary
• OMSe environment diagram including:
• Hardware components
• Network infrastructure
• Third-party software
• Configured and maintained network connectivity for OMSe workstations
• VPN access and credentials for ViaPath project team
• Ongoing server maintenance procedures and documentation
• Database backup and maintenance plan aligned with DC DOC’s disaster
recovery policies
• Technical architecture review feedback and recommendations from ViaPath
These deliverables ensure that the technical foundation for the OMSe system is
robust, secure, and ready to support all phases of implementation and operation.

4. Project Coordination and Resource Commitments
Effective coordination between ViaPath and DC DOC is essential to the success of
the OMSe implementation. This section outlines the roles, responsibilities, and
resource commitments required from both parties to ensure smooth collaboration,
timely decision-making, and efficient execution of project activities.
DC DOC will assign a Project Manager/Liaison to serve as the primary point of
contact with ViaPath’s Project Manager. This individual will also act as the lead
liaison with all third-party vendors and agencies involved in the project, particularly
for interface development. DC DOC will ensure that these external parties cooperate
in a timely and reasonable manner to support interface implementation.
For interfaces with DC DOC-owned systems, DC DOC will provide technical contacts
capable of addressing interface protocols (e.g., web services, database
procedures/triggers), file formats (e.g., flat files, XML), and proof -of-concept
requirements for each interface, including associated data elements.
ViaPath will assign an application administrator responsible for maintaining the
OMSe application and its documentation throughout the project.
DC DOC will also provide and schedule subject matter experts (SMEs) who are
familiar with their functional business and technical requirements. These SMEs are
expected to be available for approximately 10 to 14 hours per week to participate in
discovery, configuration, and validation activities.
ViaPath will provide services during normal business hours (Monday through Friday,
8:00 AM – 5:00 PM EST). Remote sessions will be scheduled in coordination with the
necessary access credentials, VPN configurations, and network permissions to
facilitate this access.
Technical Environment Deliverables
• Assigned DC DOC Project Manager/Liaison with defined responsibilities
• Assigned ViaPath Project Manager and application administrator
• Designated technical contacts for DC DOC-owned system interfaces
• Interface documentation including:
• Protocol specifications
• File format definitions
• Proof-of-concept summaries and data element mappings
• Scheduled and documented SME participation (10–14 hours/week)
• Scheduled remote sessions coordinated with DC DOC
• On-site support for key milestones:
• Kickoff/Discovery
• Train-the-Trainer
• UAT
• Go-Live
These deliverables ensure that both organizations are aligned in their roles and
responsibilities, and that the necessary personnel and resources are in place to
support the successful execution of the OMSe implementation.
This section outlines the tools and protocols that will be used to manage project
tasks, track issues, and facilitate communication between ViaPath and DC DOC
throughout the OMSe implementation.
DC DOC will report all issues encountered during the project using ServiceNow.
Each issue will include relevant details such as the time of occurrence, the location
within the application, and a description of the failure or concern. ViaPath will track
these issues in ServiceNow ITBM, associating them with the project, managing their
resolution, and obtaining acceptance for closure from the DC DOC Project Manager.
In addition to issue tracking, ViaPath will use ServiceNow ITBM to manage project
tasks. This will provide visibility into task ownership, status, and dependencies. Tasks
assigned to DC DOC will be communicated by the ViaPath Project Manager to the
DC DOC Project Manager with sufficient lead time to allow for proper resource
planning and allocation.
To support project scheduling and milestone tracking, ViaPath will maintain a Gantt
chart project schedule. Periodic copies of the schedule will be shared with the DC
DOC Project Manager to ensure alignment and visibility into progress.

5. Project Tracking, Issue Management, and Communication Tools

DC DOC Project Manager and aligned with the project timeline. On-site resources
will be deployed for key milestones, including the Kickoff/Discovery session, Train-
the-Trainer, User Acceptance Testing (UAT), and Go-Live.
Project Coordination Deliverables
• Logged issues in ServiceNow with detailed descriptions from DC DOC
• Issue tracking and resolution records in ServiceNow ITBM, including closure
approvals
• Project task tracking in ServiceNow ITBM with visibility into ownership and
status
• Task assignments communicated to DC DOC with appropriate lead time
• Maintained Gantt chart project schedule with periodic updates shared with
DC DOC
• Microsoft Teams environment for remote meetings and collaboration
These deliverables ensure that project activities are well -managed, issues are
promptly addressed, and communication remains clear and consistent across all
stakeholders.

6. Project Documents

Project documentation is essential to the successful execution, monitoring, and
completion of the OMSe implementation. ViaPath will develop and maintain a
comprehensive set of planning and execution documents that define the project’s
structure, guide activities, and ensure alignment between ViaPath and DC DOC.

During the Planning Phase, ViaPath will create a suite of foundational documents
that will be reviewed and acknowledged by DC DOC prior to the start of execution.
These documents will include detailed plans for data migration, training, Go -Live,
user acceptance testing (UAT), and communications. Each plan will outline
objectives, roles, timelines, and criteria for success. ViaPath will also define the
change request process to manage modifications to scope, schedule, or deliverables.

In addition to these planning documents, ViaPath will maintain a customer -facing
Microsoft Project schedule and Work Breakdown Structure (WBS), along with a RAID
log (Risks, Assumptions, Issues, and Dependencies). These tools will be updated
regularly and shared with DC DOC to ensure visibility into project progress, risks, and
decision points.

All finalized documents will be stored in a shared repository accessible to both
ViaPath and DC DOC project teams. This centralized location will serve as the
authoritative source for project records and ensure that all stakeholders have access
to the most current information.
For remote collaboration, ViaPath will utilize Microsoft Teams to conduct meetings,
facilitate discussions, and support ongoing project coordination with DC DOC.
Project Tracking and Communication Deliverables
Project Document Deliverables

• Project Schedule (Microsoft Project format)
• Work Breakdown Structure (WBS)
• Data Migration Plan
• Training Plan
• Go-Live Plan
• User Acceptance Testing (UAT) Plan
• Communications Plan
• RAID Log (Risks, Assumptions, Issues, Dependencies)
• Change Request Process
• Meeting agendas and minutes
• Configuration and interface documentation
• Training materials (e.g., user guides, quick reference cards)
• Finalized and archived project documentation in a shared repository

7. System Implementation and Installation

System implementation and installation activities are carried out during the
Execution Phase and represent the core of the OMSe deployment effort. ViaPath will
work collaboratively with DC DOC to ensure a structured and successful
implementation, maintaining alignment with the project plan, schedule, and
defined expectations.

Regular coordination meetings will be held to track progress, address challenges,
and ensure quality standards are met. The OMSe solution will be deployed as a
Commercial Off-The-Shelf (COTS) product, leveraging its out-of-the-box
functionality. Product modifications will be limited to those necessary to fulfill
existing JACCS functionality that is not present in OMSe.

Functional area testing will be conducted to validate system operations, followed by
User Acceptance Testing (UAT) and Go-Live using the COTS product. Any
enhancement requests identified during execution will be documented for
consideration in a potential Phase 2 project.

ViaPath will install and configure the OMSe application and database files across
three distinct environments:
• Production Environment – The live system used for day-to-day operations
• Test Environment – A controlled system for testing updates, configurations,
and patches
• Training Environment – A dedicated instance for staff training and user
familiarization

To perform installation and configuration activities, ViaPath will require appropriate
access to the OMSe environment, including remote access sessions. DC DOC will be
responsible for maintaining the execution environment, including server
configuration, operating system updates, and security settings.

DC DOC will also provide a valid SSL certificate to support secure operation of the
OMSe application. If a self-signed certificate is used, DC DOC will be responsible for
deploying it to all end-user workstations to ensure proper connectivity and
compliance.

If DC DOC elects to use the Client Workstation Utility for Terminal Security, they will
be responsible for installing and configuring the software on all applicable
workstations.

System Implementation and Installation Deliverables

• Deployment of OMSe as a COTS product with limited modifications
• Functional area testing results and validation documentation
• Execution of User Acceptance Testing (UAT) and Go-Live
• Documented enhancement requests for future consideration
• Installed and configured OMSe environments:
• Production
• Test
• Training
• Remote access setup for ViaPath installation activities
• SSL certificate provided by DC DOC (or deployment of self-signed certificate)
• Installation and configuration of Client Workstation Utility (if applicable)
• Ongoing server and environment maintenance by DC DOC

This phase ensures that the OMSe system is properly installed, validated, and
transitioned into operational readiness, setting the stage for final acceptance and
long-term sustainability.
8. System Interface and Integrations
ViaPath Technologies will deliver system integrations through API web services or
data file exchanges, depending on the technical requirements of each external
system. The appropriate integration method will be determined during the
discovery phase in collaboration with DC DOC and documented prior to
implementation. All API endpoints and data file specifications will be provided to DC
DOC for review and validation.
ViaPath will install and configure the interfaces listed below and provide guidance
on configuration and testing. DC DOC will be responsible for managing any third-
party software, external system dependencies, or development efforts required to
support these integrations. Additionally, DC DOC will ensure that all necessary
network and firewall settings are configured to allow proper connectivity.
Each interface will be tested and accepted by DC DOC upon delivery. This includes
verifying data exchange, confirming compatibility with third-party systems, and
ensuring that the interface meets operational requirements.

Interfaces to Be Delivered
• Active Directory (LDAP)
o Integration using a DC DOC-provided service account for secure user
authentication
• Email (SMTP)
o OMSe and OMS Push will connect to DC DOC’s email server using
provided credentials to send notifications
• OMS Push
o Delivery of data files, reports, and email notifications based on
preconfigured queries
• VINE
o One-way integration via SMTP to send population demographics in
CSV or XML format
• Keefe Commissary
o API token-based access to booking, account balances, and transaction
posting
• ViaPath VisManager
o Demographics file sent via SMTP; VisManager will populate scheduled
visits in OMSe
• ViaPath ICMv
o Real-time web service integration for booking demographics and
Telephone ID (TID)
• ViaPath Payment Services
Functional area analysis is a critical component of the OMSe implementation,
ensuring that the system is configured to meet DC DOC’s operational needs. This
work is conducted collaboratively between ViaPath’s Business Analysts and DC
DOC’s Subject Matter Experts (SMEs), who provide the business context and
decision-making authority necessary to guide system design and validation.
Each functional area will have an assigned SME from DC DOC who is responsible for
providing direction, making business decisions, and ensuring timely feedback to
keep the project on schedule. DC DOC will also provide relevant use cases and
current process artifacts—such as forms, documents, and screenshots—to support
the definition of business requirements and system workflows.
ViaPath’s Business Analysts will review the provided materials and identify:
• Application solutions that align with DC DOC’s operational needs
• Required reports to support business functions
• Data mapping requirements for legacy JACCS-to-OMSe system conversion
DC DOC will participate in solution demonstrations, review system configurations,
and provide feedback to ensure alignment with business processes. During
functional area testing, DC DOC will execute use cases to validate the configured
system meets operational requirements.
o Web service integration to support payment kiosks and Western Union
services
• ViaPath Tablets
o SFTP-based integration to send booking data to the tablet system
• ViaPath Imaging (Mugshots)
o Licensing for three (3) capture stations; hardware specifications
provided to DC DOC for procurement and installation
Interface Integration Deliverables
• Documented API endpoints and data file specifications for each interface
• Installed and configured interfaces for all listed external systems
• Interface configuration and testing guidance provided by ViaPath
• Verified network and firewall connectivity for interface functionality (DC DOC
responsibility)
• Interface testing and acceptance by DC DOC
• Hardware specifications for imaging integration (DC DOC procurement
responsibility)
• Licensing for three (3) OMSe imaging capture stations
This section ensures that all required system integrations are implemented, tested,
and validated to support seamless data exchange between OMSe and external
systems.
9. Functional Areas (Business Units) and Business Analysis

• Assigned SMEs for each functional area with defined responsibilities
• Use cases and process artifacts provided by DC DOC
• Business requirements and workflow documentation
• Functional area solution demonstrations and feedback sessions
• Functional area testing results based on executed use cases
• Data mapping documentation for legacy system conversion
• User Guides co-developed by ViaPath and DC DOC
This collaborative approach ensures that the OMSe system is tailored to DC DOC’s
operational environment and that all functional areas are fully validated prior to Go-
Live.

10. Reporting and Analytics
Reporting is a key component of OMSe implementation, supporting operational
visibility, compliance, and decision-making. ViaPath and DC DOC will work
collaboratively to identify the reports required to support business functions across
all functional areas.
Report requirements will be defined during the discovery and configuration phases,
and each report will be validated through DC DOC review. Acceptance of a
functional area will be considered acceptance of all reports delivered for that area.
ViaPath will provide custom report units in accordance with the report complexity
framework outlined in Appendix D. These units will be tracked by the ViaPath
Project Manager to ensure transparency and alignment with contractual
expectations.
In addition to new report development, ViaPath will assist DC DOC in modifying
existing reports to accommodate changes in data schema or business processes.
This ensures continuity for reports that will remain part of DC DOC’s future
operational workflows.
Reporting Deliverables
• Defined report requirements for each functional area
• Delivered reports validated through functional area acceptance
• Custom report units tracked by ViaPath Project Manager
• Modified legacy reports to align with new schema and business processes
• Collaborative review and feedback sessions with DC DOC
Additionally, DC DOC and ViaPath will work together to develop User Guides that
accurately reflect business processes and workflows within the OMSe system.
Functional Area and Business Analysis Deliverables
This approach ensures that all reporting needs are addressed, validated, and aligned
with the operational goals of DC DOC.
11. Data Migration
Data migration from the legacy JACCS Oracle schema to the OMSe Oracle schema
will follow a structured and iterative approach, as detailed in the Data Migration
Plan. This process ensures that critical data is accurately transferred, validated, and
aligned with the new system’s architecture and business processes.
Migration activities will begin with functional area-specific data mapping. ViaPath
Business Analysts will collaborate with DC DOC to document front-end application
requirements, while ViaPath Data Analysts will define the corresponding back-end
schema mappings. A series of test conversions will be performed in an internal
staging environment to validate data accuracy, refine transformation scripts, and
resolve discrepancies.
Due to schema differences between JACCS and OMSe, 100% data conversion cannot
be guaranteed. Any unconvertible data will be documented. To ensure continuity of
access to historical data that is not migrated into the OMSe system, ViaPath and DC
DOC will implement a Legacy Data Access Strategy. This strategy is designed to
preserve operational visibility into legacy records while minimizing disruption to
reporting and business processes.
DC DOC will maintain access to the legacy JACCS database in a read-only capacity
following the transition to OMSe. This access will allow authorized personnel to
query historical data directly for reporting, auditing, and reference purposes.
Key elements of the strategy include:
• Read-Only Access: DC DOC will retain read-only access to the legacy JACCS
Oracle database post-Go-Live.
• Query Capability: Authorized users will be able to write and execute SQL
queries against the legacy database using tools such as SQL Developer or SQL
Plus.
• Security and Permissions: Access will be governed by DC DOC’s internal
security policies to ensure appropriate data protection and user
accountability.
• Support for Reporting: Legacy data access will support reporting needs that
cannot be fulfilled through OMSe due to schema differences or data
exclusions (e.g., accounting transactions).
• Archival Planning: If DC DOC elects to decommission the legacy system in the
future, an archival solution (e.g., data warehouse export or static reporting
repository) will be developed in coordination with ViaPath.
This approach ensures that DC DOC retains full visibility into historical records while
transitioning to the new OMSe platform.
User Acceptance Testing (UAT) is a critical step in validating that the OMSe system
meets DC DOC’s operational needs. As this is a Commercial Off-The-Shelf (COTS)
implementation, a COTS-specific testing approach will be used, focusing on
validating configurations, integrations, and business processes rather than core
product functionality.
DC DOC will provide remote access to the legacy JMS database using SQL Developer
and SQL Plus, enabling ViaPath to perform conversion activities. Final validation and
acceptance of converted data will be the responsibility of DC DOC.
Data conversion will occur at strategic points throughout the project:
• During functional area validation
• Prior to User Acceptance Testing (UAT)
• During Mock Go-Live
• As part of the final Go-Live migration
The Mock Go-Live will simulate the full migration process to identify potential issues,
validate end-to-end workflows, and determine the duration required for the final Go-
Live maintenance window. These findings will inform the final execution plan to
ensure a smooth transition with minimal disruption.
Data Migration Deliverables
• Data Migration Plan outlining approach, validation, and acceptance criteria
• Data Mapping Document detailing JACCS-to-OMSe field mappings
• Functional area-specific data mapping documentation
• Test conversion results and transformation script refinements
• Documentation of unconvertible data and historical access solutions
• Modified census snapshots to reflect schema and process changes
• Remote access setup to legacy JMS database (DC DOC responsibility)
• Validated and accepted converted data by DC DOC
• Mock Go-Live findings and final migration readiness assessment
• Legacy Database Access Plan outlining read-only access strategy and query
capabilities
This structured migration process ensures that critical data is accurately transitioned
to OMSe, supporting operational continuity and long-term system integrity.
12. User Acceptance Testing (UAT)

During the UAT phase, the ViaPath engineering team will operate within ViaPath’s
existing Scrum Agile framework, using two-week sprints to iteratively deliver and
refine the configured OMS solution. Defects identified during UAT, whether in the
base COTS product or in custom-developed components, will be triaged, prioritized,
and addressed as part of the ongoing sprint cycle.
Defect Triage and Prioritization
The ViaPath project team will be responsible for collecting, documenting, and
triaging all UAT defects reported by DC DOC.
Severity classification will be determined in collaboration with DC DOC based on
business impact:
• Critical (Showstopper): Blocks core functionality or go-live readiness.
• High: Major impact but with available workarounds.
• Medium: Moderate impact with limited disruption.
• Low: Minor issues or cosmetic defects.
Triaged defects will be submitted to the ViaPath OMSe application product owner,
who will prioritize them within ViaPath’s internal product and sprint backlogs.
The OMSe product owner will provide regular updates to the ViaPath project
manager, who will in turn communicate status and resolution progress to the DC
DOC project manager, ensuring transparency and alignment throughout the UAT
process.
Response and Resolution Cadence
Critical defects will be addressed immediately and prioritized for resolution within
the current sprint or via a hotfix outside the sprint cycle, with:
• Initial response within 1 business day
• Resolution or mitigation within 10 business days
High and Medium defects will be proposed for inclusion in the next available sprint,
based on impact and team capacity.
Low severity defects will be tracked and scheduled based on product owner
prioritization and sprint planning.
ViaPath Technologies will support UAT preparation by providing user-facing
documentation, including user guides, system configuration documentation, and a
sample test case to illustrate the expected format and structure. During UAT
execution, ViaPath will offer support, guidance, and issue resolution through a
combination of onsite and remote methods to ensure a smooth and effective testing
process.
Defects must be closed or mitigated to DC DOC’s satisfaction prior to go-live.
DC DOC is responsible for leading and executing the UAT process. This includes
developing or adapting test cases based on their business processes, applied
configurations, and system integrations. UAT will be conducted by end users in real-
world scenarios to validate that the system performs as expected within the DC DOC
environment.
Best practices for COTS testing will be followed, including:
• Gap Analysis – Comparing business needs with COTS capabilities
• Configuration Testing – Validating the specific setup for DC DOC
• Integration Testing – Ensuring compatibility with external systems
• User Acceptance Testing – Executed by end users to confirm readiness
• User documentation provided by ViaPath (user guides, system configuration
documentation, sample test case)
• UAT Plan outlining roles, responsibilities, and acceptance criteria
• UAT test cases developed and executed by DC DOC
• Execution of UAT by DC DOC end users
• UAT results and issue tracking
• Resolution to all reported issues or accepted mitigation strategies delivered
by ViaPath
• Final UAT acceptance by DC DOC, required before the Go/No-Go decision for
production deployment
This approach ensures that the OMSe system is thoroughly validated in the DC DOC
environment and is ready for Go-Live with confidence in its performance and
alignment with operational needs.
Escalation Procedures
If a Critical defect is not resolved within the defined timeframe:
• Day 11: Escalation to technical leads for immediate intervention.
• Day 14: Escalation to project leadership and executive stakeholders to determine
mitigation strategies or go-live adjustments.
An escalation log will be maintained to track issue status and resolution actions.
Verification and Retesting
All resolved defects will be verified by the QA team and retested by DC DOC during
the same or subsequent sprint.

User Acceptance Testing Deliverables

ViaPath Technologies will utilize a Train-the-Trainer approach to ensure effective
knowledge transfer and scalable end-user training. A subset of customer-identified
trainers will be selected to participate in structured training sessions, which will be
organized by functional area. This ensures that each trainer receives role-specific
instruction aligned with their operational responsibilities.
• Training Completion Document – A formal acknowledgment from DC DOC
confirming that OMSe application training has been completed and the
organization is prepared for Go-Live
13. Training

The training program will utilize a hybrid model comprising both onsite, instructor -
led sessions and virtual sessions delivered via Microsoft Teams. Onsite sessions will
be conducted in a computer lab provided by DC DOC, enabling hands-on,
interactive instruction. This blended approach is designed to maximize flexibility and
accessibility, accommodating participants’ varying schedules and operational
demands.
Initial training for designated trainers will be conducted onsite to ensure
comprehensive, experiential learning. However, in recognition of potential
scheduling conflicts due to vacation, illness, or unforeseen operational constraints,
virtual sessions will be made available as needed. These sessions will serve as
retraining or supplemental instruction prior to go-live, allowing for timely knowledge
transfer without the logistical complexities of rescheduling onsite sessions.
The total number of individuals to be trained will be determined during the planning
phase in collaboration with DC DOC. This number will be based on the business
units identified for training and the trainers designated to support ongoing
knowledge transfer. At a minimum, the training program will include 150 trainers.
Feedback collected through training evaluations will be reviewed by ViaPath and DC
DOC to identify areas where additional clarification or reinforcement is needed.
Based on this input, training materials such as user guides and quick reference cards
may be updated to improve clarity and usability. If feedback indicates gaps in
understanding or confidence, refresher sessions will be scheduled to ensure staff are
fully prepared for Go-Live and ongoing system use.
DC DOC is responsible for ensuring that all designated trainers attend training
sessions, actively participate, and understand the significance of the OMSe
implementation. This includes reinforcing the importance of training attendance,
encouraging engagement during sessions, and supporting a culture of
accountability to ensure operational readiness at Go -Live.
Training sessions will be scheduled in coordination with DC DOC and documented
to ensure that all necessary personnel receive adequate instruction on system
functionality. These trainers will then be responsible for delivering end-user training
to staff across the organization.
Training Deliverables

As part of this Statement of Work, and as soon as feasible following project initiation,
ViaPath Technologies will hire and train a dedicated Site Administrator to support
the project. This individual will be onboarded and integrated into project activities
throughout the duration of the project, gaining hands-on experience with the OMSe
software platform and DC DOC-specific operational processes. By the time of go-live,
the resource will be fully trained and prepared to serve as a Site Administrator,
supporting the solution post-deployment.
ViaPath will cover all costs associated with hiring, onboarding, and training this
resource during the project period. Post go-live, the Site Administrator will be
provided as part of the ongoing support and maintenance agreement. To sustain
this support model, DC DOC must commit to a minimum of three years of post-go-
live maintenance and support.
The specific responsibilities, scope of work, and operational protocols for the Site
Administrator will be defined in the Maintenance and Support Agreement. As part of
this Statement of Work, ViaPath agrees to onboard and train the resource in the
OMSe platform, while DC DOC agrees to provide training on the agency’s business
practices related to OMS usage.
A Mock Go-Live will be conducted as a critical rehearsal to simulate real -world
system usage and validate operational readiness prior to full deployment. This
structured exercise allows end-users and subject matter experts (SMEs) to execute
key workflows in a controlled environment, ensuring that the OMSe system
performs as expected under near-production conditions.
ViaPath will coordinate and facilitate the Mock Go -Live in close collaboration with
DC DOC, providing technical support and monitoring system behavior throughout
the process. This phase serves to identify any final adjustments needed before the
production Go-Live and helps establish realistic timeframes for essential activities
such as data conversion, system cutover, and validation steps.
All issues identified during the Mock Go-Live will be logged, prioritized, and resolved
prior to proceeding to the production environment. Formal sign-off from DC DOC
will confirm readiness to move forward.
Mock Go-Live Success Criteria
• Successful execution of all critical workflows without errors
• System performance meets expected benchmarks under simulated load

14. OMS Site Administrator

15. Mock Go-Live

• Training Schedule – A documented timeline of training sessions by functional
area and role
• Attendance Logs – Records of participation for all training sessions
• Training Feedback Forms – Collected input from trainers and end users to
assess training effectiveness and identify areas for improvement.
Roles and Responsibilities

ViaPath Technologies
• Coordinate and facilitate the Mock Go-Live event
• Provide technical support and issue resolution during execution
• Monitor system performance and assist with validation activities
• Document outcomes and provide recommendations for final adjustments
• Identify and assign end-users and SMEs to participate in the Mock Go-Live
• Execute operational workflows and validate business processes
• Log and report any issues encountered during testing
• Review and confirm resolution of issues
• Provide formal sign-off indicating readiness for Go-Live
This phase ensures that all stakeholders are aligned, the system is validated under
realistic conditions, and the project is positioned for a successful and confident
transition to live operations.

DC DOC

16. Go-Live
The Go-Live process marks the transition of the OMSe system from implementation
to operational use and is a critical milestone in the Execution Phase. ViaPath will
work in close coordination with DC DOC to ensure a smooth and structured Go-Live,
aligned with the project schedule, readiness criteria, and stakeholder expectations.
Prior to Go-Live, all functional area testing and User Acceptance Testing (UAT) will be
completed to validate that the OMSe system meets defined requirements and is
ready for production use. A formal Go-Live readiness review will be conducted to
confirm that all technical, functional, and operational prerequisites have been
satisfied.
During the Go-Live event, ViaPath will provide support to monitor system
performance, address any immediate issues, and ensure a stable transition to the
production environment. Post-Go-Live support will be available to assist with user
questions, troubleshoot issues, and ensure continuity of operations.
• Data conversion completes within the defined timeframe and is validated
• Cutover steps are executed in sequence and documented (Go-Live Checklist)
• All identified issues are logged, prioritized, and resolved
• End-user feedback confirms usability and operational readiness
• Formal acknowledgment from DC DOC indicating readiness for Go-Live
17. Project Closeout
The Project Closeout phase represents the formal conclusion of the OMSe
implementation and ensures that all contractual, technical, and administrative
obligations have been fulfilled. ViaPath will work collaboratively with DC DOC to
verify that all project deliverables meet the agreed-upon standards and objectives,
and that the solution has been successfully transitioned into operational use.
During this phase, final reviews will be conducted to confirm completion of all scope
items, and formal approvals and sign-offs will be obtained from designated
stakeholders. Outstanding administrative tasks, including contract closure and
financial reconciliation, will be completed in accordance with project governance
requirements.
In addition, ViaPath will facilitate a lessons learned session to capture insights,
challenges, and best practices from the project. These findings will be documented
to support continuous improvement and inform future initiatives.
The Project Closeout phase reflects ViaPath’s commitment to delivering a high-
quality solution and ensuring a smooth and organized conclusion to the project
lifecycle.
Project Closeout Deliverables
• Final review and verification of all project deliverables
• Stakeholder approvals and formal project sign-off
• Closure of contracts, financial accounts, and administrative items
• Documentation of lessons learned and recommendations
• Transition of project documentation and knowledge to DC DOC
• Confirmation of ongoing support and maintenance arrangements (if
applicable)
This phase ensures that the project is concluded in a structured and comprehensive
manner, leaving DC DOC with a fully delivered solution and a foundation for
continued success.
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)

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/OR [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)
SECTION F: PERIOD OF PERFORMANCE AND DELIVERABLES
F.1 TERM OF CONTRACT

The term of the contract shall be for a period of one-year from date of award specified on
the cover page of this 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 four (4) one -year option
periods, or successive fractions thereof, by written notice to the Contractor before the
expiration of the contract; provided that the District will give the Contractor preliminary
written notice of its intent to extend at least thirty (30) days before the contract expires.
The preliminary notice does not commit the District to an extension. The exercise of this
option is subject to the availability of funds at the time of the exercise of this option. The
Contractor may waive the thirty (30) day preliminary notice requirement by providing a
written waiver to the Contracting Officer prior to expiration of the contract.

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

F.2.3 The price for the option period 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 five (5) 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 (CA)
identified in section G.9 in accordance with the following:
Task Name Duration Start Finish Resource Names
DC OMS Sample Schedule 445 days Mon
10/13/25 Fri 7/30/27
Phase I - Initiation 13 days Mon
10/13/25
Wed
10/29/25

Project Initiated 1 day Mon
10/13/25
Mon
10/13/25 Director OMS and Strategy
Create Project Repository 1 day Tue
10/14/25
Tue
10/14/25 VP Implementation Manager
Internal Project Kickoff 1 day Wed
10/15/25
Wed
10/15/25
VP Implementation Manager, VP Project
Manager, Director OMS and Strategy
Review Project Scope 5 days Thu
10/16/25
Wed
10/22/25

Identify Project Objectives 4 days Thu
10/16/25
Tue
10/21/25
VP Project Manager, VP Implementation
Manager, VP Business Development
Determine Project
Boundaries 4 days Thu
10/16/25
Tue
10/21/25 VP Project Manager
Project Kickoff Virtual
Meeting - MS Teams

1 day Wed
10/22/25
Wed
10/22/25
VP Project Manager, DC Project Manager,
DC Executive Stakeholders, VP Executive
Stakeholders
Establish Project
Governance 5 days Thu
10/23/25
Wed
10/29/25

Form Project Team 5 days Thu
10/23/25
Wed
10/29/25 DC Project Manager, VP Project Manager
Define Governance
Structure 5 days Thu
10/23/25
Wed
10/29/25 VP Project Manager
Create an Escalation
Process 5 days Thu
10/23/25
Wed
10/29/25 VP Project Manager, DC Project Manager
Identify Stakeholders 4 days Thu
10/23/25
Tue
10/28/25

Identify All Stakeholders 2 days Thu
10/23/25
Fri
10/24/25 DC Project Manager, VP Project Manager
Analyze Stakeholder
Influence and Interest 1 day Mon
10/27/25
Mon
10/27/25 DC Project Manager, VP Project Manager
Develop a Stakeholder
Engagement Plan 1 day Tue
10/28/25
Tue
10/28/25 VP Project Manager
Create Project Charter 4 days Thu
10/23/25
Tue
10/28/25

Identify All Stakeholders 2 days Thu
10/23/25
Fri
10/24/25 DC Project Manager, VP Project Manager
Analyze Stakeholder
Influence and Interest 1 day Mon
10/27/25
Mon
10/27/25 DC Project Manager, VP Project Manager
Develop a Stakeholder
Engagement Plan 1 day Tue
10/28/25
Tue
10/28/25 VP Project Manager
Phase II - Planning 55 days Wed
10/29/25
Mon
1/26/26

Project Discovery 7 days Wed
10/29/25
Thu
11/6/25

Organize Onsite Discovery
Meeting Create Agenda 1 day Wed
10/29/25
Wed
10/29/25 VP Project Manager
Prepare Discovery
Materials 3 days Thu
10/30/25
Mon
11/3/25 VP Business Analyst Team

Onsite Discovery Meeting

1 day Thu
11/6/25
Thu
11/6/25
VP Project Manager, VP Business Analyst
1,VP Business Analyst 2,DC Project
Manager, DC SME
Discovery Sessions 11 days Fri 11/7/25 Mon
11/24/25

Individual Functional Area
Discovery 6 days Fri 11/7/25 Mon
11/17/25
VP Business Analyst 1,VP Business Analyst
2,DC SME
Collate Discovery
Information 5 days Tue
11/18/25
Mon
11/24/25
VP Business Analyst 1,VP Business Analyst
2
Schedule Planning 10 days Wed
11/26/25
Thu
12/11/25

Create Detailed Task List 5 days Wed
11/26/25
Thu
12/4/25 VP Project Manager
Sequence the Activities 5 days Wed
11/26/25
Thu
12/4/25 VP Project Manager
Estimate Task Durations 5 days Wed
11/26/25
Thu
12/4/25 VP Project Manager
Participate in Project
Timeline Refinements 5 days Fri 12/5/25 Thu
12/11/25 DC Project Manager
Develop/Refine the
Project Timeline 5 days Fri 12/5/25 Thu
12/11/25 VP Project Manager
Project Schedule Timeline
Completed 0 days Thu
12/11/25
Thu
12/11/25 DC Project Manager, VP Project Manager
Communication and
Environment Planning 5 days Fri
12/12/25
Thu
12/18/25

Communication 5 days Fri
12/12/25
Thu
12/18/25

Identify Communication
Needs 1 day Fri
12/12/25
Fri
12/12/25 VP Project Manager, DC Project Manager
Plan Communication
Methods 2 days Mon
12/15/25
Tue
12/16/25 VP Project Manager
Establish a
Communication Schedule 2 days Wed
12/17/25
Thu
12/18/25 VP Project Manager
Environment 1 day Fri
12/12/25
Fri
12/12/25

Identify Environment
Requirements 1 day Fri
12/12/25
Fri
12/12/25 VP Project Manager, DC Project Manager
Additional Project
Documentation 21 days Fri
12/19/25
Mon
1/26/26

Responsibility Assignment
Matrix (RACI) 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
UAT Plan 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Training Plan 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Issue and risk tracking 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Change Control Process 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Data Migration Plan 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Mock Go-Live Plan 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Reporting Governance
Plan 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Knowledge Transfer
Checklist 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Execution environment
readiness documentation 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Logistical coordination
documentation 10 days Fri
12/19/25 Wed 1/7/26 VP Project Manager
Document Review 5 days Thu 1/8/26 Wed
1/14/26 DC Project Manager
Planning Document
Refinement 5 days Thu
1/15/26 Fri 1/23/26 VP Project Manager
Formal approval of all
foundational planning
documents

1 day Mon
1/26/26
Mon
1/26/26

DC Project Manager
Phase II Complete 0 days Mon
1/26/26
Mon
1/26/26 VP Project Manager
Phase III - Execution 356 days Tue
1/27/26
Wed
6/30/27

Business Process Analysis
and Documentation 120 days Tue
1/27/26 Fri 7/17/26
Functional Area 1 30 days Tue
1/27/26
Tue
3/10/26

Requirements Gathering
and Analysis 5 days Tue 1/27/26 Mon 2/2/26 VP Business Analyst 1
Provide Artifacts and
Use Cases 5 days Tue 1/27/26 Mon 2/2/26 DC SME
Future State 25 days Tue 2/3/26 Tue
3/10/26

Provide Use Case /
Requirements Clarification 15 days Tue 2/3/26 Tue 2/24/26 DC SME
Business Process
Requirements Documentation 15 days Tue 2/3/26 Tue 2/24/26 VP Business Analyst 1
Reports Requirements 15 days Tue 2/3/26 Tue 2/24/26 VP Business Analyst 1
Data Mapping 15 days Tue 2/3/26 Tue 2/24/26 VP Business Analyst 1
Gap Analysis User
Stories 15 days Tue 2/3/26 Tue 2/24/26
Customer Review of
Documentation 5 days Wed
2/25/26 Tue 3/3/26 DC SME
Document Revisions 2 days Wed 3/4/26 Thu 3/5/26 VP Business Analyst 1
Final Review of
Documentation 2 days Fri 3/6/26 Mon 3/9/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Tue 3/10/26

Tue 3/10/26

DC Project Manager, VP Project Manager
Functional Area 2 30 days Tue
1/27/26
Tue
3/10/26

Requirements Gathering
and Analysis 5 days Tue 1/27/26 Mon 2/2/26 VP Business Analyst 2
Provide Artifacts and
Use Cases 5 days Tue 1/27/26 Mon 2/2/26 DC SME
Future State 25 days Tue 2/3/26 Tue
3/10/26

Provide Use Case /
Requirements Clarification 15 days Tue 2/3/26 Tue 2/24/26 DC SME
Business Process
Requirements Documentation 15 days Tue 2/3/26 Tue 2/24/26 VP Business Analyst 2
Reports Requirements 15 days Tue 2/3/26 Tue 2/24/26 VP Business Analyst 2
Data Mapping 15 days Tue 2/3/26 Tue 2/24/26 VP Business Analyst 2
Gap Analysis User
Stories 15 days Tue 2/3/26 Tue 2/24/26
Customer Review of
Documentation 5 days Wed
2/25/26 Tue 3/3/26 DC SME
Document Revisions 2 days Wed 3/4/26 Thu 3/5/26 VP Business Analyst 2
Final Review of
Documentation 2 days Fri 3/6/26 Mon 3/9/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Tue 3/10/26

Tue 3/10/26

DC Project Manager, VP Project Manager
Functional Area 3 30 days Wed
3/11/26
Tue
4/21/26

Requirements Gathering
and Analysis 5 days Wed
3/11/26 Tue 3/17/26 VP Business Analyst 1
Provide Artifacts and
Use Cases 5 days Wed
3/11/26 Tue 3/17/26 DC SME
Future State 25 days Wed
3/18/26
Tue
4/21/26

Provide Use Case /
Requirements Clarification 15 days Wed
3/18/26 Tue 4/7/26 DC SME
Business Process
Requirements Documentation 15 days Wed
3/18/26 Tue 4/7/26 VP Business Analyst 1
Reports Requirements 15 days Wed
3/18/26 Tue 4/7/26 VP Business Analyst 1
Data Mapping 15 days Wed
3/18/26 Tue 4/7/26 VP Business Analyst 1
Gap Analysis User
Stories 15 days Wed
3/18/26 Tue 4/7/26
Customer Review of
Documentation 5 days Wed 4/8/26 Tue 4/14/26 DC SME
Document Revisions 2 days Wed
4/15/26
Thu
4/16/26 VP Business Analyst 1
Final Review of
Documentation 2 days Fri 4/17/26 Mon
4/20/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Tue 4/21/26

Tue 4/21/26

DC Project Manager, VP Project Manager
Functional Area 4 30 days Wed
3/11/26
Tue
4/21/26

Requirements Gathering
and Analysis 5 days Wed
3/11/26 Tue 3/17/26 VP Business Analyst 2
Provide Artifacts and
Use Cases 5 days Wed
3/11/26 Tue 3/17/26 DC SME
Future State 25 days Wed
3/18/26
Tue
4/21/26

Provide Use Case /
Reqirements Clarification 15 days Wed
3/18/26 Tue 4/7/26 DC SME
Business Process
Requirements Documentation 15 days Wed
3/18/26 Tue 4/7/26 VP Business Analyst 2
Reports Requirements 15 days Wed
3/18/26 Tue 4/7/26 VP Business Analyst 2
Data Mapping 15 days Wed
3/18/26 Tue 4/7/26 VP Business Analyst 2
Gap Analysis User
Stories 15 days Wed
3/18/26 Tue 4/7/26
Customer Review of
Documentation 5 days Wed 4/8/26 Tue 4/14/26 DC SME
Document Revisions 2 days Wed
4/15/26
Thu
4/16/26 VP Business Analyst 2
Final Review of
Documentation 2 days Fri 4/17/26 Mon
4/20/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Tue 4/21/26

Tue 4/21/26

DC Project Manager, VP Project Manager
Functional Area 5 30 days Wed
4/22/26
Wed
6/3/26

Requirements Gathering
and Analysis 5 days Wed
4/22/26 Tue 4/28/26 VP Business Analyst 1
Provide Artifacts and
Use Cases 5 days Wed
4/22/26 Tue 4/28/26 DC SME
Future State 25 days Wed
4/29/26
Wed
6/3/26

Provide Use Case /
Reqirements Clarification 15 days Wed
4/29/26 Tue 5/19/26 DC SME
Business Process
Requirements Documentation 15 days Wed
4/29/26 Tue 5/19/26 VP Business Analyst 1
Reports Requirements 15 days Wed
4/29/26 Tue 5/19/26 VP Business Analyst 1
Data Mapping 15 days Wed
4/29/26 Tue 5/19/26 VP Business Analyst 1
Gap Analysis User
Stories 15 days Wed
4/29/26 Tue 5/19/26
Customer Review of
Documentation 5 days Wed
5/20/26
Wed
5/27/26 DC SME
Document Revisions 2 days Thu
5/28/26 Fri 5/29/26 VP Business Analyst 1
Final Review of
Documentation 2 days Mon 6/1/26 Tue 6/2/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Wed 6/3/26

Wed 6/3/26

DC Project Manager, VP Project Manager
Functional Area 6 30 days Wed
4/22/26
Wed
6/3/26

Requirements Gathering
and Analysis 5 days Wed
4/22/26 Tue 4/28/26 VP Business Analyst 2
Provide Artifacts and
Use Cases 5 days Wed
4/22/26 Tue 4/28/26 DC SME
Future State 25 days Wed
4/29/26
Wed
6/3/26

Provide Use Case /
Reqirements Clarification 15 days Wed
4/29/26 Tue 5/19/26 DC SME
Business Process
Requirements Documentation 15 days Wed
4/29/26 Tue 5/19/26 VP Business Analyst 2
Reports Requirements 15 days Wed
4/29/26 Tue 5/19/26 VP Business Analyst 2
Data Mapping 15 days Wed
4/29/26 Tue 5/19/26 VP Business Analyst 2
Gap Analysis User
Stories 15 days Wed
4/29/26 Tue 5/19/26
Customer Review of
Documentation 5 days Wed
5/20/26
Wed
5/27/26 DC SME
Document Revisions 2 days Thu
5/28/26 Fri 5/29/26 VP Business Analyst 2
Final Review of
Documentation 2 days Mon 6/1/26 Tue 6/2/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Wed 6/3/26

Wed 6/3/26

DC Project Manager, VP Project Manager
Functional Area 7 30 days Thu 6/4/26 Fri 7/17/26
Requirements Gathering
and Analysis 5 days Thu 6/4/26 Wed
6/10/26 VP Business Analyst 1
Provide Artifacts and
Use Cases 5 days Thu 6/4/26 Wed
6/10/26 DC SME
Future State 25 days Thu
6/11/26 Fri 7/17/26
Provide Use Case /
Reqirements Clarification 15 days Thu
6/11/26 Thu 7/2/26 DC SME
Business Process
Requirements Documentation 15 days Thu
6/11/26 Thu 7/2/26 VP Business Analyst 1
Reports Requirements 15 days Thu
6/11/26 Thu 7/2/26 VP Business Analyst 1
Data Mapping 15 days Thu
6/11/26 Thu 7/2/26 VP Business Analyst 1
Gap Analysis User
Stories 15 days Thu
6/11/26 Thu 7/2/26
Customer Review of
Documentation 5 days Mon 7/6/26 Fri 7/10/26 DC SME
Document Revisions 2 days Mon
7/13/26 Tue 7/14/26 VP Business Analyst 1
Final Review of
Documentation 2 days Wed
7/15/26
Thu
7/16/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Fri 7/17/26

Fri 7/17/26

DC Project Manager, VP Project Manager
Functional Area 8 30 days Thu 6/4/26 Fri 7/17/26
Requirements Gathering
and Analysis 5 days Thu 6/4/26 Wed
6/10/26 VP Business Analyst 2
Provide Artifacts and
Use Cases 5 days Thu 6/4/26 Wed
6/10/26 DC SME
Future State 25 days Thu
6/11/26 Fri 7/17/26
Provide Use Case /
Reqirements Clarification 15 days Thu
6/11/26 Thu 7/2/26 DC SME
Business Process
Requirements Documentation 15 days Thu
6/11/26 Thu 7/2/26 VP Business Analyst 2
Reports Requirements 15 days Thu
6/11/26 Thu 7/2/26 VP Business Analyst 2
Data Mapping 15 days Thu
6/11/26 Thu 7/2/26 VP Business Analyst 2
Gap Analysis User
Stories 15 days Thu
6/11/26 Thu 7/2/26
Customer Review of
Documentation 5 days Mon 7/6/26 Fri 7/10/26 DC SME
Document Revisions 2 days Mon
7/13/26 Tue 7/14/26 VP Business Analyst 2
Final Review of
Documentation 2 days Wed
7/15/26
Thu
7/16/26 DC SME
Requirements
Documentation - Customer
Sign Off

1 day

Fri 7/17/26

Fri 7/17/26

DC Project Manager, VP Project Manager
Product Modifications 140 days Wed
3/11/26
Mon
9/28/26

Functional Area 1 Mods 50 days Wed
3/11/26 Tue 5/19/26 Product and Engineering
Functional Area 2 Mods 50 days Wed
3/11/26 Tue 5/19/26 Product and Engineering
Functional Area 3 Mods 50 days Wed
4/22/26 Thu 7/2/26 Product and Engineering
Functional Area 4 Mods 50 days Wed
4/22/26 Thu 7/2/26 Product and Engineering
Functional Area 5 Mods 50 days Thu 6/4/26 Fri 8/14/26 Product and Engineering
Functional Area 6 Mods 50 days Thu 6/4/26 Fri 8/14/26 Product and Engineering
Functional Area 7 Mods 50 days Mon
7/20/26
Mon
9/28/26 Product and Engineering
Functional Area 8 Mods 50 days Mon
7/20/26
Mon
9/28/26 Product and Engineering
App Config / Reporting /
Data 233 days Wed
3/11/26
Wed
2/17/27

Application Configuration 128 days Mon
7/20/26
Tue
1/26/27

Functional Area 1 5 days Mon
7/20/26 Fri 7/24/26
Provide Configuration
Input 5 days Mon
7/20/26 Fri 7/24/26 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Mon
7/20/26

Fri 7/24/26

VP Business Analyst 1
Code Table Imports 5 days Mon
7/20/26 Fri 7/24/26 VP Data Analyst
Screen Customizations 5 days Mon
7/20/26 Fri 7/24/26 VP Report Analyst
Provide Configuration
Input 5 days Mon
7/20/26 Fri 7/24/26 DC SME
Functional Area 2 5 days Mon
7/20/26 Fri 7/24/26
Provide Configuration
Input 5 days Mon
7/20/26 Fri 7/24/26 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Mon
7/20/26

Fri 7/24/26

VP Business Analyst 2
Code Table Imports 5 days Mon
7/20/26 Fri 7/24/26 VP Data Analyst
Screen Customizations 5 days Mon
7/20/26 Fri 7/24/26 VP Report Analyst
Provide Configuration
Input 5 days Mon
7/20/26 Fri 7/24/26 DC SME
Functional Area 3 5 days Wed
9/9/26
Tue
9/15/26

Provide Configuration
Input 5 days Wed 9/9/26 Tue 9/15/26 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Wed 9/9/26

Tue 9/15/26

VP Business Analyst 1
Code Table Imports 5 days Wed 9/9/26 Tue 9/15/26 VP Data Analyst
Screen Customizations 5 days Wed 9/9/26 Tue 9/15/26 VP Report Analyst
Provide Configuration
Input 5 days Wed 9/9/26 Tue 9/15/26 DC SME
Functional Area 4 5 days Wed
9/30/26
Tue
10/6/26

Provide Configuration
Input 5 days Wed
9/30/26 Tue 10/6/26 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Wed
9/30/26

Tue 10/6/26

VP Business Analyst 2
Code Table Imports 5 days Wed
9/30/26 Tue 10/6/26 VP Data Analyst
Screen Customizations 5 days Wed
9/30/26 Tue 10/6/26 VP Report Analyst
Provide Configuration
Input 5 days Wed
9/30/26 Tue 10/6/26 DC SME
Functional Area 5 26 days Wed
9/30/26
Thu
11/5/26

Provide Configuration
Input 5 days Wed
9/30/26 Tue 10/6/26 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Fri
10/30/26

Thu
11/5/26

VP Business Analyst 1
Code Table Imports 5 days Fri
10/30/26
Thu
11/5/26 VP Data Analyst
Screen Customizations 5 days Fri
10/30/26
Thu
11/5/26 VP Report Analyst
Provide Configuration
Input 5 days Fri
10/30/26
Thu
11/5/26 DC SME
Functional Area 6 5 days Mon
11/23/26
Tue
12/1/26

Provide Configuration
Input 5 days Mon
11/23/26 Tue 12/1/26 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Mon
11/23/26

Tue 12/1/26

VP Business Analyst 2
Code Table Imports 5 days Mon
11/23/26 Tue 12/1/26 VP Data Analyst
Screen Customizations 5 days Mon
11/23/26 Tue 12/1/26 VP Report Analyst
Provide Configuration
Input 5 days Mon
11/23/26 Tue 12/1/26 DC SME
Functional Area 7 5 days Mon
12/28/26
Mon
1/4/27

Provide Configuration
Input 5 days Mon
12/28/26 Mon 1/4/27 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Mon
12/28/26

Mon 1/4/27

VP Business Analyst 1
Code Table Imports 5 days Mon
12/28/26 Mon 1/4/27 VP Data Analyst
Screen Customizations 5 days Mon
12/28/26 Mon 1/4/27 VP Report Analyst
Provide Configuration
Input 5 days Mon
12/28/26 Mon 1/4/27 DC SME
Functional Area 8 5 days Wed
1/20/27
Tue
1/26/27

Provide Configuration
Input 5 days Wed
1/20/27 Tue 1/26/27 DC SME
Application
Configuration - Code
Tables/System
Parameters/Security Admin

5 days

Wed
1/20/27

Tue 1/26/27

VP Business Analyst 2
Code Table Imports 5 days Wed
1/20/27 Tue 1/26/27 VP Data Analyst
Screen Customizations 5 days Wed
1/20/27 Tue 1/26/27 VP Report Analyst
Provide Configuration
Input 5 days Wed
1/20/27 Tue 1/26/27 DC SME
Report Development 175 days Wed
3/11/26
Wed
11/18/26

Functional Area 1 105 days Wed
3/11/26 Fri 8/7/26
Initial Report
Development 10 days Wed
3/11/26 Tue 3/24/26 VP Report Analyst
Post Modification
Report Refinements 5 days Mon
7/27/26 Fri 7/31/26 VP Report Analyst
Provide Report
Clarification 5 days Mon
7/27/26 Fri 7/31/26 DC SME
Reports Verification 3 days Mon 8/3/26 Wed 8/5/26 DC SME
Report Refinements 2 days Thu 8/6/26 Fri 8/7/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Fri 8/7/26 Fri 8/7/26 DC Project Manager, VP Project Manager
Functional Area 2 105 days Wed
3/25/26 Fri 8/21/26
Initial Report
Development 10 days Wed
3/25/26 Tue 4/7/26 VP Report Analyst
Post Modification
Report Refinements 5 days Mon
8/10/26 Fri 8/14/26 VP Report Analyst
Provide Report
Clarification 5 days Mon
8/17/26 Fri 8/21/26 DC SME
Reports Verification 3 days Mon
8/17/26
Wed
8/19/26 DC SME
Report Refinements 2 days Thu
8/20/26 Fri 8/21/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Fri 8/21/26 Fri 8/21/26 DC Project Manager, VP Project Manager
Functional Area 3 95 days Wed
4/22/26 Fri 9/4/26
Initial Report
Development 10 days Wed
4/22/26 Tue 5/5/26 VP Report Analyst
Post Modification
Report Refinements 5 days Mon
8/24/26 Fri 8/28/26 VP Report Analyst
Provide Report
Clarification 5 days Mon
8/24/26 Fri 8/28/26 DC SME
Reports Verification 3 days Mon
8/31/26 Wed 9/2/26 DC SME
Report Refinements 2 days Thu 9/3/26 Fri 9/4/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Fri 9/4/26 Fri 9/4/26 DC Project Manager, VP Project Manager
Functional Area 4 95 days Wed
5/6/26
Mon
9/21/26

Initial Report
Development 10 days Wed 5/6/26 Tue 5/19/26 VP Report Analyst
Post Modification
Report Refinements 5 days Tue 9/8/26 Mon
9/14/26 VP Report Analyst
Provide Report
Clarification 5 days Tue 9/8/26 Mon
9/14/26 DC SME
Reports Verification 3 days Tue 9/15/26 Thu
9/17/26 DC SME
Report Refinements 2 days Fri 9/18/26 Mon
9/21/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Mon
9/21/26
Mon
9/21/26 DC Project Manager, VP Project Manager
Functional Area 5 85 days Thu 6/4/26 Mon
10/5/26

Initial Report
Development 10 days Thu 6/4/26 Wed
6/17/26 VP Report Analyst
Post Modification
Report Refinements 5 days Tue 9/22/26 Mon
9/28/26 VP Report Analyst
Provide Report
Clarification 5 days Tue 9/22/26 Mon
9/28/26 DC SME
Reports Verification 3 days Tue 9/29/26 Thu
10/1/26 DC SME
Report Refinements 2 days Fri 10/2/26 Mon
10/5/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Mon
10/5/26
Mon
10/5/26 DC Project Manager, VP Project Manager
Functional Area 6 95 days Thu 6/4/26 Tue
10/20/26

Initial Report
Development 10 days Thu 6/4/26 Wed
6/17/26 VP Report Analyst
Post Modification
Report Refinements 5 days Tue 10/6/26 Tue
10/13/26 VP Report Analyst
Provide Report
Clarification 5 days Tue 10/6/26 Tue
10/13/26 DC SME
Reports Verification 3 days Wed
10/14/26
Fri
10/16/26 DC SME
Report Refinements 2 days Mon
10/19/26
Tue
10/20/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Tue
10/20/26
Tue
10/20/26 DC Project Manager, VP Project Manager
Functional Area 7 75 days Mon
7/20/26
Tue
11/3/26

Initial Report
Development 10 days Mon
7/20/26 Fri 7/31/26 VP Report Analyst
Post Modification
Report Refinements 5 days Wed
10/21/26
Tue
10/27/26 VP Report Analyst
Provide Report
Clarification 5 days Wed
10/21/26
Tue
10/27/26 DC SME
Reports Verification 3 days Wed
10/28/26
Fri
10/30/26 DC SME
Report Refinements 2 days Mon
11/2/26 Tue 11/3/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Tue 11/3/26 Tue 11/3/26 DC Project Manager, VP Project Manager
Functional Area 8 75 days Mon
8/3/26
Wed
11/18/26

Initial Report
Development 10 days Mon 8/3/26 Fri 8/14/26 VP Report Analyst
Post Modification
Report Refinements 5 days Wed
11/4/26
Tue
11/10/26 VP Report Analyst
Provide Report
Clarification 5 days Wed
11/4/26
Tue
11/10/26 DC SME
Reports Verification 3 days Thu
11/12/26
Mon
11/16/26 DC SME
Report Refinements 2 days Tue
11/17/26
Wed
11/18/26 VP Report Analyst
Functional Area
Reports Accepted 0 days Wed
11/18/26
Wed
11/18/26 DC Project Manager, VP Project Manager
Data Conversion 233 days Wed
3/11/26
Wed
2/17/27

Functional Area 1 110 days Wed
3/11/26 Fri 8/14/26
Database Schema
Initial Mapping 10 days Wed
3/11/26 Tue 3/24/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Mon
7/27/26 Fri 7/31/26 VP Data Analyst
Provide Data Mapping
Input 5 days Mon
7/27/26 Fri 7/31/26 DC SME
Data Mapping
Comparisons 10 days Mon 8/3/26 Fri 8/14/26 VP Data Analyst
Data Verification 5 days Mon 8/3/26 Fri 8/7/26 DC SME
Data Refinement 5 days Mon
8/10/26 Fri 8/14/26 VP Data Analyst, DC SME
Functional Area Data
Mapping Completed 0 days Fri 8/14/26 Fri 8/14/26 DC Project Manager, VP Project Manager
Functional Area 2 115 days Wed
3/25/26 Fri 9/4/26
Database Schema
Initial Mapping 10 days Wed
3/25/26 Tue 4/7/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Mon
8/17/26 Fri 8/21/26 VP Data Analyst
Provide Data Mapping
Input 5 days Mon
8/17/26 Fri 8/21/26 DC SME
Data Mapping
Comparisons 10 days Mon
8/24/26 Fri 9/4/26 VP Data Analyst
Data Verification 5 days Mon
8/24/26 Fri 8/28/26 DC SME
Data Refinement 5 days Mon
8/31/26 Fri 9/4/26 VP Data Analyst, DC SME
Functional Area Data
Mapping Completed 0 days Fri 9/4/26 Fri 9/4/26 DC Project Manager, VP Project Manager
Functional Area 3 116 days Wed
4/22/26
Tue
10/6/26

Database Schema
Initial Mapping 10 days Wed
4/22/26 Tue 5/5/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Wed
9/16/26 Tue 9/22/26 VP Data Analyst
Provide Data Mapping
Input 5 days Wed
9/16/26 Tue 9/22/26 DC SME
Data Mapping
Comparisons 10 days Wed
9/23/26 Tue 10/6/26 VP Data Analyst
Data Verification 5 days Wed
9/23/26 Tue 9/29/26 DC SME
Data Refinement 5 days Wed
9/30/26 Tue 10/6/26 VP Data Analyst, DC SME
Functional Area Data
Mapping Completed 0 days Tue 10/6/26 Tue 10/6/26 DC Project Manager, VP Project Manager
Functional Area 4 121 days Wed
5/6/26
Wed
10/28/26

Database Schema
Initial Mapping 10 days Wed 5/6/26 Tue 5/19/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Wed
10/7/26
Wed
10/14/26 VP Data Analyst
Provide Data Mapping
Input 5 days Wed
10/7/26
Wed
10/14/26 DC SME
Data Mapping
Comparisons 10 days Thu
10/15/26
Wed
10/28/26 VP Data Analyst
Data Verification 5 days Thu
10/15/26
Wed
10/21/26 DC SME
Data Refinement 5 days Thu
10/22/26
Wed
10/28/26 VP Data Analyst, DC SME
Functional Area Data
Mapping Completed 0 days Wed
10/28/26
Wed
10/28/26 DC Project Manager, VP Project Manager
Functional Area 5 122 days Thu 6/4/26 Tue
12/1/26

Database Schema
Initial Mapping 10 days Thu 6/4/26 Wed
6/17/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Fri 11/6/26 Fri
11/13/26 VP Data Analyst
Provide Data Mapping
Input 5 days Fri 11/6/26 Fri
11/13/26 DC SME
Data Mapping
Comparisons 10 days Mon
11/16/26 Tue 12/1/26 VP Data Analyst
Data Verification 5 days Mon
11/16/26
Fri
11/20/26 DC SME
Data Refinement 5 days Mon
11/23/26 Tue 12/1/26 VP Data Analyst, DC SME
Functional Area Data
Mapping Completed 0 days Tue 12/1/26 Tue 12/1/26 DC Project Manager, VP Project Manager
Functional Area 6 127 days Thu
6/18/26
Tue
12/22/26

Database Schema
Initial Mapping 10 days Thu
6/18/26 Thu 7/2/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Wed
12/2/26 Tue 12/8/26 VP Data Analyst
Provide Data Mapping
Input 5 days Wed
12/2/26 Tue 12/8/26 DC SME
Data Mapping
Comparisons 10 days Wed
12/9/26
Tue
12/22/26 VP Data Analyst
Data Verification 5 days Wed
12/9/26
Tue
12/15/26 DC SME
Data Refinement 5 days Wed
12/16/26
Tue
12/22/26 VP Data Analyst, DC SME
Functional Area Data
Mapping Completed 0 days Tue
12/22/26
Tue
12/22/26 DC Project Manager, VP Project Manager
Functional Area 7 128 days Mon
7/20/26
Tue
1/26/27

Database Schema
Initial Mapping 10 days Mon
7/20/26 Fri 7/31/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Tue 1/5/27 Mon
1/11/27 VP Data Analyst
Provide Data Mapping
Input 5 days Tue 1/5/27 Mon
1/11/27 DC SME
Data Mapping
Comparisons 10 days Tue 1/12/27 Tue 1/26/27 VP Data Analyst
Data Verification 5 days Tue 1/12/27 Tue 1/19/27 DC SME
Data Refinement 5 days Wed
1/20/27 Tue 1/26/27 VP Data Analyst
Functional Area Data
Mapping Completed 0 days Tue 1/26/27 Tue 1/26/27 DC Project Manager, VP Project Manager
Functional Area 8 133 days Mon
8/3/26
Wed
2/17/27

Database Schema
Initial Mapping 10 days Mon 8/3/26 Fri 8/14/26 VP Data Analyst
Database Schema
Mapping Updates 5 days Wed
1/27/27 Tue 2/2/27 VP Data Analyst
Provide Data Mapping
Input 5 days Wed
1/27/27 Tue 2/2/27 DC SME
Data Mapping
Comparisons 10 days Wed 2/3/27 Wed
2/17/27 VP Data Analyst
Data Verification 5 days Wed 2/3/27 Tue 2/9/27 DC SME
Data Refinement 5 days Wed
2/10/27
Wed
2/17/27 VP Data Analyst
Functional Area Data
Mapping Completed 0 days Wed
2/17/27
Wed
2/17/27 DC Project Manager, VP Project Manager
Unit Testing 139 days Mon
8/17/26
Thu
3/11/27

Functional Area 1 16 days Mon
8/17/26 Tue 9/8/26
Application
Demonstration 1 day Mon
8/17/26
Mon
8/17/26 VP Business Analyst 1
Test Case Execution 10 days Tue 8/18/26 Mon
8/31/26 DC SME
Test Case Execution
Support 10 days Tue 8/18/26 Mon
8/31/26
VP Data Analysts, VP Business Analyst
1,VP Report Analyst
Functional Area
Acceptance 0 days Mon
8/31/26
Mon
8/31/26 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Tue 9/1/26 Tue 9/8/26 VP Business Analyst 1,VP Data Analysts,
VP Report Analyst
Functional Area 2 16 days Tue 9/8/26 Tue
9/29/26

Application
Demonstration 1 day Tue 9/8/26 Tue 9/8/26 VP Business Analyst 2
Test Case Execution 10 days Wed 9/9/26 Tue 9/22/26 DC SME
Test Case Execution
Support 10 days Wed 9/9/26 Tue 9/22/26 VP Data Analysts, VP Report Analyst 2,VP
Business Analyst 2
Functional Area
Acceptance 0 days Tue 9/22/26 Tue 9/22/26 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Wed
9/23/26 Tue 9/29/26 VP Data Analysts, VP Report Analysts, VP
Business Analyst 2
Functional Area 3 16 days Wed
10/7/26
Thu
10/29/26

Application
Demonstration 1 day Wed
10/7/26
Wed
10/7/26 VP Business Analyst 1
Test Case Execution 10 days Thu
10/8/26
Thu
10/22/26 DC SME
Test Case Execution
Support 10 days Thu
10/8/26
Thu
10/22/26
VP Data Analysts, VP Business Analyst
1,VP Report Analyst
Functional Area
Acceptance 0 days Thu
10/22/26
Thu
10/22/26 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Fri
10/23/26
Thu
10/29/26
VP Business Analyst 1,VP Data Analysts,
VP Report Analyst
Functional Area 4 16 days Thu
10/29/26
Fri
11/20/26

Application
Demonstration 1 day Thu
10/29/26
Thu
10/29/26 VP Business Analyst 2
Test Case Execution 10 days Fri
10/30/26
Fri
11/13/26 DC SME
Test Case Execution
Support 10 days Fri
10/30/26
Fri
11/13/26
VP Data Analysts, VP Business Analyst
2,VP Report Analyst
Functional Area
Acceptance 0 days Fri
11/13/26
Fri
11/13/26 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Mon
11/16/26
Fri
11/20/26
VP Data Analysts, VP Report Analysts, VP
Business Analyst 2
Functional Area 5 16 days Wed
12/2/26
Wed
12/23/26

Application
Demonstration 1 day Wed
12/2/26
Wed
12/2/26 VP Business Analyst 1
Test Case Execution 10 days Thu
12/3/26
Wed
12/16/26 DC SME
Test Case Execution
Support 10 days Thu
12/3/26
Wed
12/16/26
VP Data Analysts, VP Business Analyst
1,VP Report Analyst
Functional Area
Acceptance 0 days Wed
12/16/26
Wed
12/16/26 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Thu
12/17/26
Wed
12/23/26
VP Business Analyst 1,VP Data Analysts,
VP Report Analyst
Functional Area 6 16 days Wed
12/23/26
Tue
1/19/27

Application
Demonstration 1 day Wed
12/23/26
Wed
12/23/26 VP Business Analyst 2
Test Case Execution 5 days Mon
12/28/26 Mon 1/4/27 DC SME
Test Case Execution
Support 5 days Tue 1/5/27 Mon
1/11/27
VP Data Analysts, VP Business Analyst
2,VP Report Analyst
Functional Area
Acceptance 0 days Mon
1/11/27
Mon
1/11/27 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Tue 1/12/27 Tue 1/19/27 VP Data Analysts, VP Report Analysts, VP
Business Analyst 2
Functional Area 7 16 days Wed
1/27/27
Thu
2/18/27

Application
Demonstration 1 day Wed
1/27/27
Wed
1/27/27 VP Business Analyst 1
Test Case Execution 5 days Thu
1/28/27 Wed 2/3/27 DC SME
Test Case Execution
Support 5 days Thu 2/4/27 Wed
2/10/27
VP Data Analysts, VP Business Analyst
1,VP Report Analyst
Functional Area
Acceptance 0 days Wed
2/10/27
Wed
2/10/27 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Thu
2/11/27
Thu
2/18/27
VP Business Analyst 1,VP Data Analysts,
VP Report Analyst
Functional Area 8 16 days Thu
2/18/27
Thu
3/11/27

Application
Demonstration 1 day Thu
2/18/27
Thu
2/18/27 VP Business Analyst 2
Test Case Execution 5 days Fri 2/19/27 Thu
2/25/27 DC SME
Test Case Execution
Support 5 days Fri 2/26/27 Thu 3/4/27 VP Data Analysts, VP Business Analyst
2,VP Report Analyst
Functional Area
Acceptance 0 days Thu 3/4/27 Thu 3/4/27 DC Project Manager
App Config / Reporting /
Data Refinements 5 days Fri 3/5/27 Thu
3/11/27
VP Data Analysts, VP Report Analysts, VP
Business Analyst 2
Environment Installation 302 days Tue
1/27/26
Tue
4/13/27

Test Environment 171 days Tue
1/27/26
Tue
9/29/26

Test Environment
Prepared 3 wks Tue 1/27/26 Tue 2/17/26 DC Information Technology, VP
Implementation Specialist
Test Instance Installed 2 days Wed
2/18/26
Thu
2/19/26 VP Implementation Specialist
Custom Dev Release 1 1 day Wed
5/20/26
Wed
5/20/26

Custom Dev Release 2 1 day Mon 7/6/26 Mon 7/6/26
Custom Dev Release 3 1 day Mon
8/17/26
Mon
8/17/26

Custom Dev Release 4 1 day Tue 9/29/26 Tue 9/29/26
Production Environment 8 days Fri 4/2/27 Tue
4/13/27

Environment Prepared 5 days Fri 4/2/27 Thu 4/8/27 DC Information Technology
Production Instance(s)
Installed 3 days Fri 4/9/27 Tue 4/13/27 VP Implementation Specialist
Training Environment 7 days Fri 4/2/27 Mon
4/12/27

Training Environment
Prepared 5 days Fri 4/2/27 Thu 4/8/27 DC Information Technology
Training Instance
Installed 2 days Fri 4/9/27 Mon
4/12/27 VP Implementation Specialist
Interfaces 75 days Fri 2/5/27 Fri 5/21/27
Interface 1 - Active
Directory (LDAP) 7 days Fri 2/5/27 Tue
2/16/27

Interface Requirements
Review 1 day Fri 2/5/27 Fri 2/5/27 VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Mon 2/8/27 Mon 2/8/27 VP Implementation Specialist
Application
Configuration 2 days Tue 2/9/27 Wed
2/10/27 VP Implementation Specialist
Interface Testing 1 day Thu
2/11/27
Thu
2/11/27
VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Fri 2/12/27 Tue 2/16/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Tue 2/16/27 Tue 2/16/27 DC Project Manager, VP Project Manager
Interface 2 - Tablet
Integration 7 days Thu
2/18/27 Fri 2/26/27
Interface Requirements
Review 1 day Thu
2/18/27
Thu
2/18/27
VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 2/19/27 Fri 2/19/27 VP Implementation Specialist
Interface Development 2 days Mon
2/22/27 Tue 2/23/27 VP Implementation Specialist
Interface Testing 1 day Wed
2/24/27
Wed
2/24/27
VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu
2/25/27 Fri 2/26/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 2/26/27 Fri 2/26/27 DC Project Manager, VP Project Manager
Interface 3 - Payment
Services Integration 7 days Thu 3/4/27 Fri 3/12/27
Interface Requirements
Review 1 day Thu 3/4/27 Thu 3/4/27 VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 3/5/27 Fri 3/5/27 VP Implementation Specialist
Interface Development 2 days Mon 3/8/27 Tue 3/9/27 VP Implementation Specialist
Interface Testing 1 day Wed
3/10/27
Wed
3/10/27
VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu
3/11/27 Fri 3/12/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 3/12/27 Fri 3/12/27 DC Project Manager, VP Project Manager
Interface 4 - Phone
Integration 7 days Thu
3/18/27 Fri 3/26/27
Interface Requirements
Review 1 day Thu
3/18/27
Thu
3/18/27
VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 3/19/27 Fri 3/19/27 VP Implementation Specialist
Interface Development 2 days Mon
3/22/27 Tue 3/23/27 VP Implementation Specialist
Interface Testing 1 day Wed
3/24/27
Wed
3/24/27
VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu
3/25/27 Fri 3/26/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 3/26/27 Fri 3/26/27 DC Project Manager, VP Project Manager
Interface 5 - Vine
Integration 7 days Thu 4/1/27 Fri 4/9/27
Interface Requirements
Review 1 day Thu 4/1/27 Thu 4/1/27 VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 4/2/27 Fri 4/2/27 VP Implementation Specialist
Interface Development 2 days Mon 4/5/27 Tue 4/6/27 VP Implementation Specialist
Interface Testing 1 day Wed 4/7/27 Wed 4/7/27 VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu 4/8/27 Fri 4/9/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 4/9/27 Fri 4/9/27 DC Project Manager, VP Project Manager
Interface 6 - VisManager
Integration 7 days Thu
4/15/27 Fri 4/23/27
Interface Requirements
Review 1 day Thu
4/15/27
Thu
4/15/27
VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 4/16/27 Fri 4/16/27 VP Implementation Specialist
Interface Development 2 days Mon
4/19/27 Tue 4/20/27 VP Implementation Specialist
Interface Testing 1 day Wed
4/21/27
Wed
4/21/27
VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu
4/22/27 Fri 4/23/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 4/23/27 Fri 4/23/27 DC Project Manager, VP Project Manager
Interface 7 - Keefe 7 days Thu
4/29/27 Fri 5/7/27
Interface Requirements
Review 1 day Thu
4/29/27
Thu
4/29/27
VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 4/30/27 Fri 4/30/27 VP Implementation Specialist
Interface Development 2 days Mon 5/3/27 Tue 5/4/27 VP Implementation Specialist
Interface Testing 1 day Wed 5/5/27 Wed 5/5/27 VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu 5/6/27 Fri 5/7/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 5/7/27 Fri 5/7/27 DC Project Manager, VP Project Manager
Interface 8 - Imaging 7 days Thu
5/13/27 Fri 5/21/27
Interface Requirements
Review 1 day Thu
5/13/27
Thu
5/13/27
VP Project Manager, VP Implementation
Manager, VP Implementation Specialist
Interface Design
Document 1 day Fri 5/14/27 Fri 5/14/27 VP Implementation Specialist
Interface Development 2 days Mon
5/17/27 Tue 5/18/27 VP Implementation Specialist
Interface Testing 1 day Wed
5/19/27
Wed
5/19/27
VP Implementation Specialist, DC
Information Technology
Interface Refinements
and Retesting 2 days Thu
5/20/27 Fri 5/21/27 DC Project Manager, VP Implementation
Specialist, VP Project Manager
Interface Acceptance 0 days Fri 5/21/27 Fri 5/21/27 DC Project Manager, VP Project Manager
User Acceptance Testing 15 days Fri 3/12/27 Thu 4/1/27
Review UAT Testing Plan 1 wk Fri 3/12/27 Thu
3/18/27 VP Project Manager, DC Project Manager
UAT Data Migration 2 days Fri 3/12/27 Mon
3/15/27

User Acceptance Testing 2 wks Fri 3/19/27 Thu 4/1/27 DC SME
User Acceptance Testing
Support 2 wks Fri 3/19/27 Thu 4/1/27 VP Business Analyst 1,VP Business Analyst
2
User Acceptance Testing
Acceptance 0 days Thu 4/1/27 Thu 4/1/27 VP Project Manager, DC Project Manager
Training 205 days Mon
7/27/26 Fri 5/21/27
Go Live Planning 26 days Fri 4/23/27 Fri 5/28/27
Go-Live Checklist Creation 1 day Fri 4/23/27 Fri 4/23/27 VP Project Manager
Checklist Review 1 day Mon
4/26/27
Mon
4/26/27 DC Project Manager
OMS Support Engagement 1 day Mon
5/17/27
Mon
5/17/27 VP Project Manager
All OMS Instances Online
and Refreshed 1 day Mon
4/26/27
Mon
4/26/27 VP Implementation Specialist
Mock Go-Live 1 day Fri 5/28/27 Fri 5/28/27 VP Project Manager
Mock Go Live Data
Migration 1 day Fri 5/28/27 Fri 5/28/27
Mock Go-Live Review 1 day Fri 5/28/27 Fri 5/28/27 VP Project Manager
Go Live - Cutover 10 days Wed
6/16/27
Wed
6/30/27

Application Go Live 1 day Wed
6/16/27
Wed
6/16/27

Execute Go Live Checklist 1 day Wed
6/16/27
Wed
6/16/27

Post Go Live Support -
Project Team 8 days Thu
6/17/27 Tue 6/29/27
Go-Live Assessment 1 day Wed
6/30/27
Wed
6/30/27

Phase III Complete 0 days Wed
6/30/27
Wed
6/30/27 VP Project Manager, DC Project Manager
Phase IV - Project Control /
Monitoring 0 days Wed
6/30/27
Wed
6/30/27

Monthly Project Plan
Update 0 days Wed
6/30/27
Wed
6/30/27 VP Project Manager
Weekly Project Status 0 days Wed
6/30/27
Wed
6/30/27 VP Project Manager
Milestone Payments 0 days Wed
6/30/27
Wed
6/30/27 VP Project Manager
Phase V - Project Closing 22 days Thu 7/1/27 Fri 7/30/27
Create System
Configuration Manual 20 days Thu 7/1/27 Wed
7/28/27 VP Site Admin
Closure Meeting 2 days Thu
7/29/27 Fri 7/30/27
Phase V Complete 0 days Fri 7/30/27 Fri 7/30/27
Unless otherwise specified herein, all deliverables identified below shall be submitted in
accordance with the project phases, milestones, and sequencing set forth in the Contractor’s
approved Project Schedule and Project Management Plan and shall be subject to District review
and acceptance pursuant to Sections E and G of this Contract.
Table F.3 – Contract Deliverables and Timing
Deliverable
Category
Reference
(Section C) Deliverable Description Delivery Timing / Milestone
Execution
Phase
Deliverables
C.3.2.3
All execution phase
deliverables, including
configuration artifacts, testing
support materials, and
implementation outputs
Delivered incrementally
throughout the Execution Phase
and finalized prior to
commencement of User
Acceptance Testing (UAT).
Monitoring and
Control Phase
Deliverables
C.3.2.4
Status reports, risk and issue
logs, change documentation,
and governance artifacts
Delivered on a recurring basis
throughout the Execution Phase
and maintained through Project
Closeout.
Closeout Phase
Deliverables C.3.2.5 / C.3.17
Final documentation,
knowledge transfer materials,
lessons learned, and formal
project closure artifacts
Delivered following successful
Go-Live and post-Go-Live
stabilization and finalized prior to
final project acceptance and
submission of the final invoice.
Technical
Environment
Deliverables
C.3.3
Environment diagrams, access
documentation, configuration
details, and related technical
artifacts
Delivered in advance of or
concurrent with the installation
and configuration of each
applicable environment (test,
training, production) and prior to
District use.
Project
Coordination
Deliverables
C.3.4
Governance documentation,
stakeholder coordination
artifacts, and project
organization materials
Delivered during the Initiation
and Planning Phases and updated
as necessary throughout the
Execution Phase.
Project
Tracking and
Communication
Deliverables
C.3.5
Project schedules, task
tracking artifacts,
communication materials, and
reporting tools
Delivered in accordance with the
approved communication cadence
and maintained throughout the
duration of the project.
Project
Document
Deliverables
C.3.6
Planning, execution, and
management documents
including plans, logs, and
supporting documentation
Delivered during the Planning and
Execution Phases and finalized no
later than the applicable
functional area sign-off or
milestone completion.
System
Implementation
and Installation
Deliverables
C.3.7
System installation artifacts,
configuration outputs, and
validation materials
Delivered in conjunction with
completion of system
implementation and prior to
District acceptance of the
applicable system components.
Interfaces to Be
Delivered C.3.8
Interfaces including, but not
limited to, LDAP, ICMv,
tablets, payment services, and
other identified integrations
Delivered in accordance with the
interface sequencing identified in
the approved Project Schedule
and completed, tested, and
submitted for District acceptance
prior to UAT for the associated
functional areas.
Interface
Integration
Deliverables
C.3.8
Interface specifications,
configuration artifacts, testing
documentation, and
acceptance materials
Delivered concurrently with
interface implementation activities
and completed prior to initiation
of UAT.
Functional
Area and
Business
Analysis
Deliverables
C.3.9
Business requirements
documentation, use cases,
workflows, and analysis
artifacts
Delivered on a
functional-area-by-functional-area
basis and approved prior to
initiation of configuration and
development activities for each
functional area.
Reporting
Deliverables C.3.10
Custom and configured
reports and supporting
documentation
Delivered in coordination with
configuration and data migration
activities and finalized prior to
functional area acceptance.
Data Migration
Deliverables C.3.11
Data mapping documents,
conversion results, validation
artifacts, and migration logs
Delivered iteratively throughout
the Execution Phase, with final
migration artifacts delivered prior
to UAT and final data validation
completed prior to Go-Live.
User
Acceptance
Testing
Deliverables
C.3.12
UAT plans, test support
materials, defect tracking, and
acceptance documentation
Delivered in accordance with the
approved UAT Plan and
submitted concurrently with or in
advance of commencement of
UAT activities.
Training
Deliverables C.3.13
Training materials, schedules,
attendance logs, and
completion documentation
Delivered in advance of and
during training activities and
finalized prior to Go-Live to
support operational readiness.
Project
Closeout
Deliverables
C.3.17
Final acceptance
documentation, transition
artifacts, and contract closeout
materials
Delivered upon completion of all
project activities and prior to final
acceptance and closeout of the
Contract.

Deliverables not explicitly assigned a discrete delivery date shall be deemed timely if delivered in
accordance with the sequencing, milestone dependencies, and phase completion criteria set forth in
the Contractor’s approved Project Schedule and associated plans.

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 presentation of a properly executed
invoice:
1. Payment will be made on completion and acceptance of each item for which the price is
stated in the Pricing Schedule in Section B and according to the Contractor’s agreed
upon Project Management Plan, milestones, and corresponding deliverables.

2. 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 create and submit payment requests in an electronic format through the DC
Vendor Portal, https://vendorportal.dc.gov.
G.2.2 The Contractor shall submit proper invoices monthly or as otherwise specified in Section G.4.

G.2.3 To constitute a proper invoice, the Contractor shall enter all required information into the Portal
after selecting the applicable purchase order number which is listed on the Contractor’s profile.

G.3 FIRST SOURCE AGREEMENT REQUEST FOR FINAL PAYMENT

G.3.1 For contracts subject to the 51% District Residents New Hires Requirements and First Source
Employment Agreement requirements, final request for payment must be accompanied by
the report or a waiver of compliance discussed in section H.5.5.

G.3.2 The District shall not make final payment to the Contractor until the agency CFO has received
the CO’s final determination or approval of waiver of the Contractor’s compliance with 51%
District Residents New Hires Requirements and First Source Employment Agreement
requirements.

G.4 ASSIGNMENT OF CONTRACT PAYMENTS

G.4.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.4.2 Any assignment shall cover all unpaid amounts payable under this contract, and shall not be
made to more than one party.

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

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

G.5 Reserved

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.

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 which remains unpaid by the Contractor at the end of any 30-day
period shall be added to the principal amount of the debt to the subcontractor and thereafter interest
penalties shall accrue on the added amount.

G.6.2.4 A dispute between the Contractor and subcontractor relating to the amounts or entitlement of a
subcontractor to a payment or a late payment interest penalty under the Quick Payment Act does 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:

Atiqullah Babajee
Office of Contracting and Procurement
Office of the Chief Technology Officer
The District of Columbia Government
200 I Street SE Suite 5608
Washington, DC 20003
Email: atiqullah.babajee@dc.gov
Cell: (202) 409-0199
G.8 AUTHORIZED CHANGES BY THE CONTRACTING OFFICER

G.8.1 The CO is the only person authorized to approve changes in any of the requirements of this
contract.

G.8.2 The Contractor shall not comply with any order, directive or request that changes or modifies
the requirements of this contract, unless issued in writing and signed by the CO.

G.8.3 In the event the Contractor effects any change at the instruction or request of any person other
than the CO, the change will be considered to have been made without authority and no
adjustment will be made in the contract price to cover any cost increase incurred as a result
thereof.

G.9 CONTRACT ADMINSTRATOR (CA)
G.9.1 The CA is responsible for general administration of the contract and advising the CO as to the
Contractor’s compliance or noncompliance with the contract. The CA has the responsibility of
ensuring the work conforms to the requirements of the contract and such other responsibilities
and authorities as may be specified in the contract. These include:
G.9.1.1 Keeping the CO fully informed of any technical or contractual difficulties encountered during
the performance period and advising the CO of any potential problem areas under the contract;
G.9.1.2 Coordinating site entry for Contractor personnel, if applicable;

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

G.9.1.4 Reviewing and approving invoices for deliverables to ensure receipt of goods and services.
This includes the timely processing of invoices and vouchers in accordance with the District’s
payment provisions; and
G.9.1.5 Maintaining a file that includes all contract correspondence, modifications, records of
inspections (site, data, equipment) and invoice or vouchers.
G.9.2 The address and telephone number of the CA is:
Baron Hsu
Chief of Information Technology
D.C Department of Corrections
Office of Information Technology
1901 D St, Southeast, 2003
(202) 523-7108
Baron.Hsu@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.
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 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.28 dated
December 26, 2023, issued by the U.S. Department of Labor in accordance with the Service
Contract Act, 41 U.S.C. § 351 et seq., and incorporated herein as Section J.2. The Contractor
shall be bound by the wage rates for the term of the contract subject to revision as stated herein
and in accordance with clause 24 of the SCP. If an option is exercised, the Contractor shall be
bound by the applicable wage rates at the time of the exercise of the option. If the option is
exercised and the CO obtains a revised wage determination, the revised wage determination is
applicable for the option periods and the Contractor may be entitled to an equitable adjustment.

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

H.3.2 The Contractor shall not:

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

(b) Take an adverse action against an employee who requests or uses a reasonable
accommodation in regard to the employee's conditions or privileges of employment, including
failing to reinstate the employee when the need for reasonable accommodations ceases to the
employee's original job or to an equivalent position with equivalent:

(1) Pay;
(2) Accumulated seniority and retirement;

(3) Benefits; and

(4) Other applicable service credits;

(c) Deny employment opportunities to an employee, or a job applicant, if the denial is based on
the need of the employer to make reasonable accommodations to the known limitations related
to pregnancy, childbirth, related medical conditions, or breastfeeding;

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

(e) Require an employee to take leave if a reasonable accommodation can be provided; or

(f) Take adverse action against an employee who has been absent from work as a result of a
pregnancy-related condition, including a pre-birth complication.

H.3.3 The Contractor shall post and maintain in a conspicuous place a notice of rights in both English
and Spanish and provide written notice of an employee's right to a needed reasonable
accommodation related to pregnancy, childbirth, related medical conditions, or breastfeeding
pursuant to the PPWF Act to:
(a) New employees at the commencement of employment;

(b) Existing employees; and

(c) An employee who notifies the employer of her pregnancy, or other condition covered by the
PPWF Act, within 10 days of the notification.
H.3.4 The Contractor shall provide an accurate written translation of the notice of rights to any non-
English or non-Spanish speaking employee.
H.3.5 Violations of the PPWF Act shall be subject to civil penalties as described in the Act.
H.4 UNEMPLOYED ANTI-DISCRIMINATION
H.4.1 The Contractor shall comply with the Unemployed Anti-Discrimination Act of 2012, D.C.
Official Code § 32-1361 et seq.

H.4.2 The Contractor shall not:

(a) Fail or refuse to consider for employment, or fail or refuse to hire, an individual as an
employee because of the individual's status as unemployed; or
(b) Publish, in print, on the Internet, or in any other medium, an advertisement or announcement
for any vacancy in a job for employment that includes:

(1) Any provision stating or indicating that an individual's status as unemployed disqualifies
the individual for the job; or

(2) Any provision stating or indicating that an employment agency will not consider or hire
an individual for employment based on that individual's status as unemployed.

H.4.3 Violations of the Unemployed Anti-Discrimination Act shall be subject to civil penalties as
described in the Act.

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

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

H.5 51% DISTRICT RESIDENTS NEW HIRES REQUIREMENTS AND FIRST SOURCE
EMPLOYMENT AGREEMENT
H.5.1 For contracts for services in the amount of $300,000 or more, the Contractor shall comply with
the First Source Employment Agreement Act of 1984, as amended, D.C. Official Code § 2-
219.01 et seq. (First Source Act).

H.5.2 The Contractor shall enter into and maintain during the term of the contract, a First Source
Employment Agreement (Employment Agreement) with the District of Columbia Department
of Employment Service’s (DOES), in which the Contractor shall agree that:

(a) The first source for finding employees to fill all jobs created in order to perform the
contract shall be the First Source Register; and
(b) The first source for finding employees to fill any vacancy occurring in all jobs covered by
the Employment Agreement shall be the First Source Register.
H.5.3 The Contractor shall not begin performance of the contract until its Employment Agreement
has been accepted by DOES. Once approved, the Employment Agreement shall not be
amended except with the approval of DOES.
H.5.4 The Contractor agrees that at least 51% of the new employees hired to perform the contract
shall be District residents.
H.5.5 The Contractor’s hiring and reporting requirements under the First Source Act and any rules
promulgated thereunder shall continue for the term of the contract.
H.5.6 The CO may impose penalties, including monetary fines of 5% of the total amount of the direct
and indirect labor costs of the contract, for a willful breach of the Employment Agreement,
failure to submit the required hiring compliance reports, or deliberate submission of falsified
data.
H.5.7 If the Contractor does not receive a good faith waiver, the CO may also impose an additional
penalty equal to 1/8 of 1% of the total amount of the direct and indirect labor costs of the
contract for each percentage by which the Contractor fails to meet its hiring requirements.

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

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

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

H.6 RESERVED

H.7 RESERVED

H.8 RESERVED

H.9 SUBCONTRACTING REQUIREMENTS
Delete Article 45, Subcontracting Requirements, 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.9 SUBCONTRACTING REQUIREMENTS in its place:
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 completely fulfill the requirement of paragraph H.9.1.1, 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 proposal 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 proposal preference pursuant to D.C.
Official Code § 2-218.43, or is selected through a set-aside program, shall perform at least
50% of the on-site work with its own organization and resources if the contract is $1 million
or less.

H.9.2 Subcontracting Plan
If the prime contractor is required by law to subcontract under this contract, it must subcontract
at least 35% of the dollar volume of this contract in accordance with the provisions of section
H.9.1 of this clause. The plan shall be submitted as part of the proposal and 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 If the Contractor has a subcontracting plan required by law for this contract, 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 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) (the “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.
SECTION I: CONTRACT CLAUSES
I.1 APPLICABILITY OF STANDARD CONTRACT PROVISIONS

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

I.2 CONTRACTS THAT CROSS FISCAL YEARS

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

I.3 CONFIDENTIALITY OF INFORMATION

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

I.4 TIME

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

I.5 RIGHTS IN DATA

42, Rights in Data, of the Standard Contract Provisions dated July 2010 for use with District
of Columbia Government Supplies and Services Contracts.
I.6 Title to Project Deliverables

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

1. Existing Products: Title to all Existing Licensed Product(s), whether or not embedded in,
delivered or operating in conjunction with hardware or Custom Products, shall remain with
Contractor or third party proprietary owner, who retains all rights, title and interest (including
patent, trademark or copyrights). Effective upon payment, the District shall be granted an
irrevocable, non-exclusive, worldwide, paid-up license to use, execute, reproduce, display,
perform, adapt (unless Contractor advises the District as part of Contractor’s bid that adaptation
will violate existing agreements or statutes and Contractor demonstrates such to the District’s
satisfaction), and distribute Existing Product to District users up to the license capacity stated in
the contract with all license rights necessary to fully effect the general business purpose of the
project or work plan or contract. Licenses shall be granted in the name of the District. The
District agrees to reproduce the copyright notice and any other legend of ownership on any
copies authorized under this paragraph.
2. Custom Products: Effective upon Product creation, Contractor hereby conveys, assigns, and
transfers to the District the sole and exclusive rights, title and interest in Custom Product(s),
whether preliminary, final or otherwise, including all patent, trademark and copyrights.
Contractor hereby agrees to take all necessary and appropriate steps to ensure that the Custom
Products are protected against unauthorized copying, reproduction and marketing by or through
Contractor.
I.7 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 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 to 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.
The Government of the District of Columbia shall be included in all policies required hereunder
to be maintained by the Contractor and its subcontractors (except for workers’ compensation and
professional liability insurance) as an additional insureds for claims against The Government of
the District of Columbia relating to this contract, with the understanding that any affirmative
obligation imposed upon the insured Contractor or its subcontractors (including without
limitation the liability to pay premiums) shall be the sole obligation of the Contractor or its
subcontractors, and not the additional insured. The additional insured status under the
Contractor’s and its subcontractors’ Commercial General Liability insurance policies shall be
effected using the ISO Additional Insured Endorsement form CG 20 10 11 85 (or CG 20 10 07
04 and CG 20 37 07 04) or such other endorsement or combination of endorsements providing
coverage at least as broad and approved by the CO in writing. All of the Contractor’s and its
subcontractors’ liability policies (except for workers’ compensation and professional liability
insurance) shall be endorsed using ISO form CG 20 01 04 13 or its equivalent so as to indicate
that such policies provide primary 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 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 set forth in the Contractor’s commercial automobile liability policy or (ii) $1,000,000
per occurrence combined single limit for bodily injury and property damage.
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 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 is undertaken by Contractor in this agreement and shall
include, but not limited to, claims involving infringement of intellectual property, including
but not limited to infringement of copyright, trademark, trade dress, invasion of privacy
violations, information theft, damage to or destruction of electronic information, release of
private information, alteration of electronic information, extortion and network security.
The policy shall provide coverage for breach response costs as well as regulatory fines and
penalties as well as credit monitoring expenses with limits sufficient to respond to these
obligations. This insurance requirement will be considered met if the general liability
insurance includes an affirmative cyber endorsement for the required amounts 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 $1,000,000 per claim or per occurrence for each wrongful act and
$2,000,000 annual aggregate. The Contractor warrants that any applicable retroactive date
precedes the date the Contractor first performed any professional services for the
Government of the District of Columbia and that continuous coverage will be maintained or
an extended reporting period will be exercised for a period of at least 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) $5,000,000 per occurrence and $5,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 of Columbia and shall carry listed coverages for ten years for
construction projects following final acceptance of the work performed under this contract and
two years for non-construction related contracts.

D. LIABILITY. These are the required minimum insurance requirements established by the
District of Columbia. However, the required minimum insurance requirements provided above
will not in any way limit the contractor’s liability under this contract.
E. CONTRACTOR’S PROPERTY. Contractor and subcontractors are solely responsible for any
loss or damage to their personal property, including but not limited to tools and equipment,
scaffolding and temporary structures, rented machinery, or owned and leased equipment. A
waiver of subrogation shall apply in favor of the District of Columbia.
F. MEASURE OF PAYMENT. The District shall not make any separate measure or payment for
the cost of insurance and bonds. The Contractor shall include all of the costs of insurance and
bonds in the contract price.
G. NOTIFICATION. The Contractor shall ensure that all policies provide that the CO shall be
given thirty (30) days prior written notice in the event of coverage and / or limit changes or if
the policy is canceled prior to the expiration date shown on the certificate. The Contractor shall
provide the CO with ten (10) days prior written notice in the event of non-payment of premium.
The Contractor will also provide the CO with an updated Certificate of Insurance should its
insurance coverages renew during the contract.
H. CERTIFICATES OF INSURANCE. The Contractor shall submit certificates of insurance
giving evidence of the required coverage as specified in this section prior to commencing work.
Certificates of insurance must reference the corresponding contract number. Evidence of
insurance shall be submitted to:
The Government of the District of Columbia and mailed to the attention of:

Atiqullah Babajee
Office of Contracting and Procurement
Office of the Chief Technology Officer
The District of Columbia Government
200 I Street SE Suite 5608
Washington, DC 20003
Email: atiqullah.babajee@dc.gov
Cell: (202) 409-0199

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

I. DISCLOSURE OF INFORMATION. The Contractor agrees that the District may disclose
the name and contact information of its insurers to any third party which presents a claim
against the District for any damages or claims resulting from or arising out of work performed
by the Contractor, its agents, employees, servants or subcontractors in the performance of this
contract.
J. CARRIER RATINGS. All Contractor’s and its subcontractors’ insurance required in
connection with this contract shall be written by insurance companies with an A.M. Best
Insurance Guide rating of at least A- VII (or the equivalent by any other rating agency) and
licensed in the District.

I.8 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 Report are incorporated herein as Section J.3. An award cannot be made to any
offeror who has not satisfied the equal employment requirements.

I.9 ORDER OF PRECEDENCE
A conflict in language shall be resolved by giving precedence to the document in the highest order
of priority that contains language addressing the issue in question. The following documents are
incorporated into the contract by reference and made a part of the contract in the following order of
precedence:
(1) An applicable Court Order, if any
(2) Contract document.
(3) Standard Contract Provisions.
(4) Contract attachments other than the Standard Contract Provisions.
(5) ViaPath’s Technical proposal Dated August 7, 2025
I.10 DISPUTES
Delete Article 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
Article 14, Disputes, in its place:
Disputes
All disputes arising under or relating to the contract shall be resolved as provided herein.
(a) Claims by the Contractor against the District: Claim, as used in paragraph (a) of
this clause, means a written assertion by the Contractor seeking, as a matter of right,
the payment of money in a sum certain, the adjustment or interpretation of contract
terms, or other relief arising under or relating to the contract. A claim arising under a
contract, unlike a claim relating to that contract, is a claim that can be resolved under
a contract clause that provides for the relief sought by the claimant

(1) All claims by a Contractor against the District arising under or relating to a contract shall
be in writing and shall be submitted to the CO for a decision. The Contractor’s claim
shall contain at least the following:

(i) A description of the claim and the amount in dispute;
(ii) Data or other information in support of the claim;
(iii) A brief description of the Contractor’s efforts to resolve the dispute prior to filing
the claim; and
(iii)The Contractor’s request for relief or other action by the CO.

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

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

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

(i) Provide a description of the claim or dispute;
(ii) Refer to the pertinent contract terms;
(iii) State the factual areas of agreement and disagreement;
(iv) State the reasons for the decision, including any specific findings of
fact, although specific findings of fact are not required and, if made,
shall not be binding in any subsequent proceeding;
(v) If all or any part of the claim is determined to be valid, determine the
amount of monetary settlement, the contract adjustment to be made,
or other relief to be granted;
(vi) Indicate that the written document is the CO’s final decision; and
(vii) Inform the Contractor of the right to seek further redress by appealing
the decision to the Contract Appeals Board.
(5) Failure by the CO to issue a decision on a contract claim within 120 days of receipt of
the claim will be deemed to be a denial of the claim, and will authorize the
commencement of an appeal to the Contract Appeals Board as provided by D.C. Official
Code § 2-360.04.

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

(7) Pending final decision of an appeal, action, or final settlement, the Contractor shall
proceed diligently with performance of the contract in accordance with the decision of
the CO.

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

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

(i) Provide a description of the claim or dispute;
(ii) Refer to the pertinent contract terms;
(iii) State the factual areas of agreement and disagreement;
(iv) State the reasons for the decision, including any specific findings of
fact, although specific findings of fact are not required and, if made,
shall not be binding in any subsequent proceeding;
(v) If all or any part of the claim is determined to be valid, determine the amount
of monetary settlement, the contract adjustment to be made, or other relief to
be granted;
(vi) Indicate that the written document is the CO’s final decision; and
(vii) Inform the Contractor of the right to seek further redress by appealing
the decision to the Contract Appeals Board.

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

(4) Before or after issuing the decision, the CO may meet with the Contractor to
attempt to resolve the claim by agreement.
(5) The authority contained in this paragraph (b) shall not apply to a claim or
dispute for penalties or forfeitures prescribed by statute or regulation which
another District agency is specifically authorized to administer, settle or
determine.

(6) This paragraph shall not authorize the CO to settle, compromise, pay, or
otherwise adjust any claim involving fraud.
(c) Decisions of the CO shall be final and not subject to review unless the Contractor timely
commences an administrative appeal for review of the decision, by filing a complaint
with the Contract Appeals Board, as authorized by D.C. Official Code § 2-360.04.
(d) Pending final decision of an appeal, action, or final settlement, the Contractor
shall proceed diligently with performance of the contract in accordance with the
decision of the CO.

I.11 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:
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:

(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) Provides 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 5 business days of its receipt of notice 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 for the additional work within 10 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 to agree on a price
for the additional work.

I.12 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 subcontracts 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 is prohibited by the Act.
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 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 non-discrimination 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 non-
discrimination requirements set forth 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.
SECTION J: ATTACHMENTS

The following list of attachments is incorporated into the Contract by reference;

Attachment
Number Document

J.1
Government of the District of Columbia Standard Contract Provisions for
Use with the Supplies and Services Contracts (July 2010)
available at http://ocp.dc.gov, under Quick Links click on “Required
Solicitation Documents”
J.2
U.S. Department of Labor Wage Determination No. 2015-4282 Revision
No.: 34 Date of Revision:07/08/2025 available at
https://sam.gov/wage-determination/2015-4281/34

J.3
Equal Employment Opportunity Employer Information Report and Mayor’s
Order 85-85
available at available at http://ocp.dc.gov, under Quick Links click on
“Required Solicitation Documents”
J.4
Department of Employment Services First Source Employment Agreement
available at http://ocp.dc.gov, under Quick Links click on “Required
Solicitation Documents”

J.5
Way to Work Amendment Act of 2006 - Living Wage Notice available at
http://ocp.dc.gov, under Quick Links click on “Required Solicitation
Documents”
J.6
Way to Work Amendment Act of 2006 - Living Wage Fact Sheet available at
http://ocp.dc.gov, under Quick Links click on “Required Solicitation
Documents”
J.7 Subcontracting Plan (if required by law) available at http://ocp.dc.gov, under
Quick Links click on “Required Solicitation Documents”
J.8 First Source Initial Employment Plan (if contract is $300,000 or more)
J.9 Waiver of SCPs: Section 9 Indemnification and Section 42 Rights in Data
[subsection (f), bullet (3)], dated January 29, 2026