ESBD_547673_1786134525422_02. Statement of Work.pdf

TEXAS DEPARTMENT OF TRANSPORTATION

STATEMENT OF WORK

TxDOT 920-45-54021 DATED: May 2026

1-4

HVR Software for Oracle

1. REQUIREMENTS: This SOW is to provide HVR Licenses, ongoing maintenance, and support services to ensure the software remains functional, secure and up to date.

1.1. FUNCTIONAL SPECIFICATIONS: HVR Software is a real-time data integration and replication service. It provides continuous tracking of database modifications, automated data synchronization, and low-impact log reading capabilities. It improves the agency’s ability to capture and deliver incremental data updates instantly to ensure data warehouses remain current without impacting primary system performance.

1.2. INSTALLATION AND CONFIGURATION: Vendor must perform all installation, initial setup, and configuration tasks required to deliver a final product that has been piloted, tested and is fully functional for TxDOT users. Tasks may include, but are not limited to, developing reports, configuring and deploying standard workflows to meet TxDOT specific business needs and rules.

1.3. SYSTEM REQUIREMENTS: Vendor must specify the method that will be used to deliver the software, login requirements, special system requirements or other requirements to ensure software is fully functional within the TxDOT environment.

Reference the Delivery Methods Schedule.

1.4. WARRANTY: Vendor must specify the Publisher’s standard warranty, maintenance and support period and service levels including any limitations.

1.5. MAINTENANCE AND SUPPORT: Vendor must:

Provide standard product maintenance and support services included with the standard license such as annual updates, patches and fixes needed to improve functionality and keep the software in working order.

Propose additional or enhanced maintenance and support plan options if available. TxDOT will select the level of maintenance and support needed.

Reference Pricing Schedule.

Follow agreed upon Patching/Upgrade process and TxDOT CAB procedures.

Follow written approvals provided in the TxDOT Authorization To Operate

(ATO), as directed by the designated TxDOT representative for installing the software product and providing standard software maintenance and support.

Provide support documentation, to include but not limited to: Support Policies, FAQ’s, Support SLA’s, Online Guides.

1.6. DELIVERABLES:

Valid software licenses, license keys, etc. for the core CDC platform and any required source or target database connectors.

2-4

Subscription— this would be whatever is needed to ensure access to the subscription—License, License keys, Log In credentials, tenant access for cloud-based CDC deployments, etc.

Updated and patched software, including the latest versions of replication agents, hub components, and security patches.

Support logs and issue resolution documentation, specifically focusing on troubleshooting replication errors, connection drops, or data latency issues.

Performance and maintenance reports, including replication latency metrics, data throughput statistics, and routine system health checks.

Provide Product Documentation—Standard product documentation that comes along with a product. Documentation to include installation guides, administrator guides, user guides, network topology and architecture design guidelines, quick starts, training guides, and any other items that provide guidelines in configuring and maintaining data pipelines.

Initial Load and Synchronization Report: Detailed report documenting the initial data ingestion process, ongoing change replication setup, and data validation/compare results between the source and target systems.

Knowledge Transfer and Training Materials: Presentation slides, summarized Knowledge Transfer (KT) documentation, and hands-on training exercises for technical staff (DBAs, Data Engineers) to independently manage, monitor, and troubleshoot the CDC software.

1.7. ACCEPTANCE CRITERIA:

Licenses and Access: All required software licenses, license keys, and login credentials have been delivered, verified, and successfully grant full access to the core CDC platform and all necessary source/target database connectors.

Software Versioning: The delivered CDC software, including all replication agents and central hub components, is verified to be the latest stable release with all current security patches applied.

Product Documentation: All standard product documentation (installation guides, administrator guides, user guides, and architecture/network topology guidelines) has been provided in an accessible format and is deemed complete by the technical team.

Initial Load and Synchronization: The Initial Load and Synchronization Report has been submitted and reviewed, successfully demonstrating that the historical data was ingested accurately, continuous replication is active, and data validation (compare) confirms consistency between source and target databases.

Performance Metrics: Performance and maintenance reports have been delivered and demonstrate that the software meets the agency's required Service Level Agreements (SLAs) for data throughput, system impact, and acceptable replication latency.

Issue Resolution: Support logs and issue resolution documentation from the implementation phase have been provided, confirming that all critical replication errors, connection drops, or latency issues encountered during setup have been successfully resolved.

Training and Knowledge Transfer (KT): All specified training materials (presentation slides, exercises) and Knowledge Transfer documentation have been delivered, and the required training sessions for designated technical staff (e.g., DBAs, Data Engineers) have been completed to ensure independent operation and troubleshooting of the software.

3-4

1.8. TRAINING: Vendor must provide standard functional and system user training along with comprehensive documentation, including methods of delivery, at no additional cost. If specified in the pricing schedule, the vendor must:

Develop and present a detailed training plan outlining the training content, affected users or user groups, recommended training schedule, etc. to the designated TxDOT representative.

Create and provide curriculum for training sessions. The materials must be tailored specifically for TxDOT use and software configuration – no generic training curriculum unless approved by the designated TxDOT representative.

Conduct train-the-trainer or system user training sessions. The vendor must include a thorough outline of the level of training support that will be required, including methods of delivery and outcomes for training NOTE: Vendor must not invoice, and TxDOT will not pay for, any additional charges associated with training such as travel costs, per diem expenses or other out-of-pocket expenditures.

2. DEFINITIONS OF TERMS AND ACRONYMS

2.1. ATO- An Authorization to Operate (ATO) is a formal declaration by a Designated Approving Authority, TxDOT ITD InfoSec that authorizes operation of a solution and explicitly accepts the risk to agency operations.

2.2. CAB-Change Advisory Board-Any information system solution that will be installed on any TxDOT owned equipment or that will access TxDOT network or will be accessed by TxDOT personnel or use or transmit data created by TxDOT may be subject to review and approval by the ITD Change Advisory Board (“CAB”) prior to implementation or delivery.

2.3. Contract – Any Purchase Order (PO) or Blanket Purchase Order (BPO) resulting from this solicitation as listed in the Order of Precedence in the resulting PO or

BPO.

2.4. BPOR – Blanket Purchase Order Release – A written authorization to perform work under the contract listing the items of work to be performed and the cost based on the prices established in the BPO.

2.5. FLSA – Fair Labor Standards Act.

2.6. PM – Project manager.

2.7. POC – Point-of-contact.

2.8. TxDOT – Texas Department of Transportation.

3. APPLICABLE LAWS AND STANDARDS: The vendor shall provide the specified service requirements in accordance with all federal, state, and local applicable laws, standards, and regulations necessary to perform the services, including, but not limited to:

3.1. 1 TAC 206, aligns state web accessibility standards with the federal regulations set forth in Section 508 of the Rehabilitation Act of 1973.

3.2. 1 TAC 213 enacted state standards for procurement, development, or usage of EIR for people with disabilities and also aligns accessibility standards with the federal regulations set forth in Section 508.

4. PRICING: Must be based on the pricing schedule.

4-4

5. ADDITIONAL INVOICING INSTRUCTIONS:

5.1. Prior to submitting the invoice, the vendor must submit, via email, documentation validating the invoice charges to the designated TxDOT representative to include, but not be limited to:

5.1.1. Hosting/Maintenance/Support service dates; or

5.1.2. Project Deliverable Review Summary Form (PDRSF).

5.1.3. Once TxDOT approves the deliverable(s) and sends the signed PDRSF to the Vendor, the invoice may be submitted.

5.2. Vendor must attach the signed PDRSF for deliverable(s) invoiced.

NOTE: Invoices requiring correction must be resubmitted with the same invoice number and clearly marked “corrected”.

6. CONTRACT REMEDIES: In the event of a breach of contract or non-performance by the vendor, TxDOT may, at its sole discretion, require the vendor to pay damages not to exceed 10% of the total price for the line item referenced on the pricing schedule. Any line item that is more than 30 calendar days late will incur liquidated damages. Delays in deliverables caused by factors outside the vendor’s control are exempt from these liquidated damages.

This provision is for liquidated damages, not a penalty. If damages are assessed, the vendor may reimburse TxDOT by discounts, credits, refunds, or waived fees.

7. CONTRACT ADMINISTRATION: Administration of the contract is a joint responsibility of the TxDOT contract manager and TxDOT purchasing staff. Purchasing staff will be responsible for administering the contractual business relationship with the vendor.

7.1. Any proposed changes to work to be performed, whether initiated by TxDOT or the vendor, must receive final written approval in the form of a Purchase Order Change Notice signed by the authorized TxDOT purchasing agent.

7.2. Upon issuance of contract, TxDOT will designate an individual to serve as the contract manager and point of contact between the agency and the vendor. The contract manager does not have any express or implied authority to vary the terms of the contract, amend the contract in any way, or waive strict performance of the terms or conditions of the contract. This individual’s contract management responsibilities include, but are not limited to:

7.2.1. Monitoring the vendor’s progress and performance and ensuring services conform to established specification requirements.

7.2.2. Managing the financial aspects of the contract including approval of payments.

7.2.3. Meeting with the vendor as needed to review progress, discuss problems, and consider necessary action.

7.2.4. Coordinate access to TxDOT facilities, systems, and staff required to facilitate the work.

7.2.5. Other areas as identified by the State of Texas Procurement and Contract Management Guide version 4.0.