Exhibits - Kansas Turnpike Authority

Roadside Toll Collection System RFP Exhibits

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibits

Exhibits

Exhibit A – Project Implementation Schedule

Exhibit B – Payment Schedule

Exhibit C – Price Proposal Instructions

Exhibit D – Forms

Roadside Toll Collection System RFP Exhibit A - Project Implementation Schedule

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit A

Exhibit A Project Implementation Schedule

Roadside Toll Collection System RFP Exhibit A – Project Implementation Schedule

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit A, Page 1 of 3

Major Milestone Description Projected Start

Projected End

RTCS RFP Advertisement 3/18/2021 --

Mandatory Pre-Proposal Scope of Services Meeting 4/1/2021 --

Proposer Questions Due 4/15/2021 --

KTA Responses to all Questions Completed 4/29/2021 --

Proposals (Technical and Price) Due 5/21/2021 --

Contract Award 8/19/2021 --

Notice to Proceed 8/26/2021 --

Project Kickoff Meeting 9/13/2021 --

Project Planning & Documentation Aug 2021 Nov 2021

Project Schedule & Project Management Plan Aug 2021 Sep 2021

Master Test Plan, Software Development Plan, QA Plan, etc. Aug 2021 Nov 2021

System Design & Requirements Sep 2021 Feb 2022

Requirements Review / Business Rules Workshops Sep 2021 Oct 2021

Reports Design Workshops Sep 2021 Oct 2021

System Detailed Design Review Nov 2021

Bill of Materials Nov 2021

Third Party Hardware and Software Documentation Submitted Nov 2021

Draft System Detailed Design Document (SDDD) Approved Dec 2021

Final System Detailed Design Document (SDDD) Submitted Jan 2022

RTCS Installation Design and Documentation Package Approved Feb 2022

System Development, Installation and Test Jan 2022 Jun 2022

Software Development Jan 2022 Apr 2022

System HW & SW Procurement Dec 2021 Feb 2022

System Formal Demonstration Mar 2022

Factory Acceptance Test (FAT) Apr 2022 May 2022

Final Installation Plan Approved May 2022

Back Office System Interface Test Jun 2022 Jun 2022

Installation: (21 ML Tolling Locations / 42 Toll Zones - Preliminary Order) Dec 2023

Construction Package #1 - Construction Complete & Available for RTCS Installation (Note: Gantry may be available for off-roadway installation prior to site completion.)

Estimated First Gantry

Complete: 3/18/2022

All Package #1 Sites Available

for RTCS Installation: 4/25/2022

Toll Location – K11 / K12 (First Toll Location) [ML-01]




Projected End

Installation and Commissioning Test

On-Site Installation Test (OSIT)

Toll Location – K13 / K14 [ML-02]










Complete: 8/12/2022



Toll Location – K09* (NB) [ML-06]












Complete: 9/16/2022











Existing ORT Gantries - Available for RTCS Installation & Transition after Construction Package #3 RTCS Installation Substantially Complete




Projected End

Toll Location – K41 / K42 (Eastern Terminal Transition) [ML-15] Dec 2023

Installation and Commissioning Test Dec 2023

Toll Location – K31 / K32 (East Topeka Transition) [ML-16] Dec 2023


Toll Location – K01 / K02 (Southern Terminal Transition) [ML-17] Dec 2023




Complete: 6/16/2023



Toll Location – K10 (SB)* [ML-06]









All Installation Complete Dec 2023

Parallel Testing, Performance Monitoring and BOS Transition Prep Jun 2022 Dec 2023

Maintenance Plan May 2023

Training Complete May 2023

Go-Live Complete Jan 2024

Final Testing and Implementation Phase Closeout

Formal System Acceptance Testing Jan 2024 Mar 2024

As-Built System Detailed Design Document (SDDD) Approved Jan 2024

As-Built Drawing Package Approved Jan 2024

System Acceptance (Start of Maintenance Phase) Mar 2024

* K10 (SB) [MP 43.08] Tolling Zone is delayed until 8/2023 so construction can align with a planned bridge project.

NOTE: Proposers may identify and propose changes to the interim milestones on the Project Schedule; however, it is critical that the milestone dates in ita licized & bold font are achieved on the dates shown in the schedule.

Roadside Toll Collection System RFP Exhibit B – Payment Schedule

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit B

Exhibit B Payment Schedule


Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit B, Page 1 of 2

A. Payments for Implementation Roadside Toll Collection System Design and Development $ -

Payment Number

Payment Milestone Pay Items % Paid Cum

% Paid KTA Turnpike

A-1 Notice to Proceed Notice to Proceed 5.00% 5.00% $ -

A-2

Roadside Toll System Development and Administration

Project Management Documents Approved: PMP & Project Schedule

2.00% 7.00% $ -

A-3

Roadside Toll System Development and Administration

Project Management Documents Approved: Master Test Plan, QA Plan and SDP, SRD, Preliminary Design

3.00% 10.00% $ -

A-4 Roadside Toll System Design

Business Rules and Design Documents Approved: BRD, ICD, Reports Design and SDDD

5.00% 15.00% $ -

A-5

Roadside Toll System Factory Acceptance Testing (FAT)

Factory Acceptance Test Plan, Test Documentation, and FAT Testing Approved

7.50% 22.50% $ -

A-6

Roadside Toll System On-Site Installation Testing (OSIT)

On-Site Installation Test (OSIT) Plan Approved, Test Documentation, and OSIT Testing Approved - First Site

2.50% 25.00% $ -

A-7 Roadside Toll System Manuals and Training

Manuals Approved and Training Approved 2.00% 27.00% $ -

A-8 Equipment BOM and Advance Ordering Verified

Equipment BOM Approved & Long-lead Items Ordering Verified 5.00% 32.00% $ -

A-9 Roadside Toll System Commissioning

Installation and Commissioning Approved & Ready for Go Live

A-9a Tolling Location 01 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 01

3.00% 35.00% $ -

A-9b Tolling Location 02 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 02

3.00% 38.00% $ -

A-9c Tolling Location 03 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 03

3.00% 41.00% $ -

A-9d Tolling Location 04 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 04

3.00% 44.00% $ -

A-9e Tolling Location 05 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 05

3.00% 47.00% $ -

A-9f Tolling Location 06 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 06

3.00% 50.00% $ -


Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit B, Page 2 of 2

A. Payments for Implementation Roadside Toll Collection System Design and Development $ -

A-9g Tolling Location 07 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 07

3.00% 53.00% $ -

A-9h Tolling Location 08 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 08

3.00% 56.00% $ -

A-9i Tolling Location 09 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 09

3.00% 59.00% $ -

A-9j Tolling Location 10 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 10

3.00% 62.00% $ -

A-9k Tolling Location 11 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 11

3.00% 65.00% $ -

A-9l Tolling Location 12 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 12

3.00% 68.00% $ -

A-9m Tolling Location 13 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 13

3.00% 71.00% $ -

A-9fn Tolling Location 14 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 14

3.00% 74.00% $ -

A-9o Tolling Location 15 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 15

3.00% 77.00% $ -

A-9p Tolling Location 16 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 16

3.00% 80.00% $ -

A-9q Tolling Location 17 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 17

3.00% 83.00% $ -

A-9r Tolling Location 18 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 18

3.00% 86.00% $ -

A-9s Tolling Location 19 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 19

3.00% 89.00% $ -

A-9t Tolling Location 20 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 20

3.00% 92.00% $ -

A-9u Tolling Location 21 Installation and Commissioning Approved and Ready for Go Live - Tolling Location 21

3.00% 95.00% $ -

A-10 Roadside Toll System Acceptance

Operational and Acceptance Test Approved, As-Builts Approved and Implementation Phase Closed Out

5.00% 100.00% $ -

Roadside Toll Collection System RFP Exhibit C – Price Proposal Instructions

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit C

Exhibit C Price Proposal Instructions


Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit C, Page i of i

Table of Contents

1 GENERAL INSTRUCTIONS ............................................................................................................... 1

2 INSTRUCTIONS ON COMPLETING THE PRICE PROPOSAL FORMS ....................................... 2

3 TOTAL PROJECT COSTS .................................................................................................................... 4

4 COMPLETION OF THE ROADSIDE TOLL COLLECTION SYSTEM (RTCS) COST SUMMARY - SHEETS 2, 2-1, 2-1A, 2-2, 2-2A, 2-3, 2-3A, AND 2-4 ................................................ 4

5 COMPLETION OF ROADWAY SUPPORT SYSTEM (RSS) COST - SHEETS 3, 3-1, 3-1A, AND 3-2 .......................................................................................................................................... 5

6 COMPLETION OF ROADSIDE TOLL COLLECTION SYSTEM (RTCS) HARDWARE MAINTENANCE AND SOFTWARE SUPPORT SERVICES COST (BASE AND OPTIONAL EXTENSIONS) SHEETS 4, 4-1 AND 4-1A .................................................................... 6

7 COMPLETION OF ROADWAY SUPPORT SYSTEMS (RSS) MAINTENANCE AND SOFTWARE SUPPORT SERVICES COST (BASE AND OPTIONAL EXTENSIONS) SHEETS 5, 5-1, AND 5-1A ................................................................................................................... 7

8 COMPLETION OF FUTURE ROADSIDE TOLL COLLECTION SYSTEM (RTCS) AET ZONE SYSTEM IMPLEMENTATION COST SHEETS 6 AND 6-1 .................................................. 8

9 COMPLETION OF ADDITIONAL SERVICES RATES - SHEET 7-1 .............................................. 9

10 COMPLETION OF MAINTENANCE MONTHLY COST – SHEET 8............................................. 9

11 COMPLETION OF PAYMENT SCHEDULE – EXHIBIT B .............................................................. 9

12 COMPLETION OF PROJECT SUMMARY - SHEET 1 ..................................................................... 9

13 COST ESCALATION .......................................................................................................................... 10


Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit C, Page 1 of 10

1 GENERAL INSTRUCTIONS

Proposers shall complete their Price Proposals in accordance with the following instructions:

1. The Price Proposal Forms are provided in Excel format worksheets for ease of completion andchecking.

2. Proposers shall submit their Price Proposals on the Price Proposal Forms included in RFP, ExhibitD - Forms. Price Proposals shall be sealed and submitted separate from the Technical Proposalas further instructed in the RFP. Price Proposals shall be submitted in the quantities and manneridentified in the RFP.

3. The Price Proposal Forms shall constitute the full and complete Price Proposal for compensationfor performance of the Contractor’s obligations and Work under the Roadside Toll CollectionSystem project.

4. Proposers must complete the Price Proposal Forms in their entirety. The Price Proposal Formsfor the Project are as follows:

• KTA Turnpike Project Summary – Sheet 1

• Roadside Toll Collection System (RTCS) Cost– Sheets 2, 2-1, 2-1a, 2-2, 2-2a, 2-3,2-3a, and 2-4,

• Roadway Support Systems (RSS) Cost – Sheets 3, 3-1, 3-1a, and 3-2

• Roadside Toll Collection System (RTCS) Hardware Maintenance andSoftware Support Services Cost – Sheets 4, 4-1, and 4-1a

• Roadway Support Systems (RSS) Maintenance and Software Support ServicesCost – Sheets 5, 5-1, and 5-1a

• Future Roadside Toll Collection System (RTCS) AET Zone SystemImplementation Cost – Sheets 6 and 6-1

• Additional Services Rates – Sheet 7-1

• Maintenance Monthly Cost – Sheet 8

• Payment Schedule – Exhibit B

5. Proposers should not fill in any grayed-out cells on the Price Proposal Forms, nor shall Proposersmake any other entry on or alteration to the Price Proposal Forms other than in accordance withthese Price Proposal Instructions.

6. KTA may waive or correct any error appearing in a Proposer’s completed Price Proposal Formsif the correct amount can be clearly ascertained from the information provided; however, KTA isunder no obligation to do so. In the event of an inconsistency between the amount stated innumbers and the amount stated in written words, the amount stated in written words will control.In the event of a mathematical miscalculation, the correct sum will control.

7. An officer of the Proposer or an individual otherwise authorized in writing by an officer of theProposer must sign and date Sheet 1 in the appropriate place as identified.

8. All elements of the Price Proposal must be completed. If zero quantities are included for a lineitem in the Proposal, a zero must be entered into the corresponding cell. In addition, all itemsidentified by KTA in the Price Proposal Forms will be assumed to be included in the Price Proposal.



9. KTA reserves the right to reject Price Proposals that are not completed in accordance with theinstructions set forth herein.

10. Instructions for completion of each of the Price Proposal Forms are provided in Sections 2through 13 below.

11. The Price Proposal shall be inclusive of all costs, fees and applicable taxes needed to meet therequirements of the RFP, included in Section III, Scope of Work and Requirements.Implementation and “Future Zone Type” pricing should be entered in 2022 dollar values.Maintenance labor costs should be entered in 2024 dollar values. No price escalation will beallowed above the costs provided on the Price Proposal Forms to complete the Work, with theexception of the CPI as specifically identified herein.

2 INSTRUCTIONS ON COMPLETING THE PRICE PROPOSAL FORMS

1. There are twenty-four (24) Price Proposal Forms, as detailed above, including six pricing summarysheets (Sheets 1, 2, 3, 4, 5 and 6) and associated Backup information on Backup sheets for eachpricing sheet. Backup sheets for each summary sheet are labeled to identify the correspondingsummary pricing sheet; for example, Sheet 2-1 is a Backup sheet to pricing Sheet 2. Backup sheetsare located following summary sheets 1 through 6. The Additional Services Rates Sheet 7-1,Maintenance Monthly Cost Sheet 8, and Exhibit B Payment Schedule are standalone sheets anddo not require summary sheets.

2. Table 1 below summarizes the 24 Price Proposal forms that shall be completed by all Proposers.Each form is located on a unique sheet in an Excel workbook. The table provides the followinginformation for each form:

a. The sheet number (e.g. 2, 2-1, etc.)

b. The sheet title listed at the top of each sheet

Table 1 – Price Proposal Form Summary

Sheet Number Sheet Title

1 KTA Turnpike Project Summary

2 Roadside Toll Collection System (RTCS) Cost

2-1 Backup - AET 2: RTCS Cost Schedule

2-1a Backup - AET 2: RTCS - Staff and Position Classifications with Rates

2-2 Backup - AET 2+: RTCS Cost Schedule

2-2a Backup - AET 2+: RTCS - Staff and Position Classifications with Rates

2-3 Backup - AET 3: RTCS Cost Schedule

2-3a Backup - AET 3: RTCS - Staff and Position Classifications with Rates

2-4 Backup - Facility Server by Location Cost Schedule

3 Roadway Support Systems (RSS) Cost

3-1 Backup - RSS Cost Schedule

3-1a Backup – RSS - Staff and Position Classifications with Rates

3-2 Backup - RTCS and RSS Initial Spare Parts and Equipment Cost



Sheet Number Sheet Title

4 Base Contract and Optional Extensions - Roadside Toll Collection System (RTCS) Hardware Maintenance and Software Support Services Cost

4-1 Backup - Base Contract and Optional Extensions - RTCS Hardware Maintenance and Software Support Services - Labor and Other Direct Cost Items by Month

4-1a Backup - Base Contract and Optional Extensions - RTCS Hardware Maintenance and Software Support Services - Staff and Position Classifications with Rates

5 Base Contract and Optional Extensions - Roadway Support Systems (RSS) Maintenance and Software Support Services Cost

5-1 Backup - Base Contract and Optional Extensions - RSS Maintenance and Software Support Services - Labor and Other Direct Cost Items by Month

5-1a Backup - Base Contract and Optional Extensions - RSS Maintenance and Software Support Services - Staff and Position Classifications with Rates

6 Future Roadside Toll Collection System (RTCS) AET Zone System Implementation Cost

6-1 Backup - Future Zone Types RTCS Cost Schedule Per Zone

7-1 Additional Services Rates (2022 Values)

8 Maintenance Monthly Cost

Exhibit B Payment Schedule

3. The Price Proposal Forms are password protected and shall not be unlocked by Proposers. Onlyin the unlocked cells may the Proposers enter data.

4. Blue colored tabs represent summary sheets that do not require Proposer input. Green tabsrepresent worksheets that require Proposer input.

5. On most sheets there are formulas that are automatically calculated based on data entered fromelsewhere in the sheet or workbook. Font and background colors are used to indicate differenttypes of cells as follows:

• Black font – Indicates the cell cannot be altered by Proposer.

• Red font – Indicates the Proposer should enter data.

• Light red background – Indicates input required. All such cells should be completedaccordingly.

• Light yellow background – Indicates Proposer must enter data for any applicable item.

• Light green background – Indicates that data has been entered into the cell. Light red andlight yellow background will change to light green when any non-zero data is entered.The background for any cells where the Proposer enters zero (0) will not change colorsin this manner.

6. While KTA has made every effort to ensure the Price Proposal Forms contain accurate formulasand calculation, Proposers are required to independently verify that formulas and calculations arebeing performed correctly.



3 TOTAL PROJECT COSTS

The Proposer’s proposed total price shall be the aggregate of all costs included in Sheet 1. Sheet 1 will automatically roll-up and present the totals from Sheets 2 through Sheet 5. These costs will be totaled and presented in the Grand Total Cost column in the line entitled Total Implementation and Maintenance Cost including Optional Extension Phases.

4 COMPLETION OF THE ROADSIDE TOLL COLLECTION SYSTEM (RTCS) COST SUMMARY - SHEETS 2, 2-1, 2-1a, 2-2, 2-2a, 2-3, 2-3a, AND 2-4

The Proposer’s total price for the Roadside Toll Collection System (RTCS) portion of the Implementation Phase shall be the aggregate of all costs included in Sheet 2 which covers all costs associated with the RTCS portion of the Work for the KTA Turnpike.

The costs for Sheet 2 shall include (without limitation) all Equipment, supplies, Software, parts and materials, overhead, burden, profit, taxes, duties, fees, Contractor-acquired permits, licenses, warranties, and other items necessary to meet the Contractor contractual requirements associated with the RTCS portion of the System. No price escalation will be allowed above the costs provided on the Price Proposal Sheets to complete the Work except as set forth in Section 13.

The prices on Sheet 2 and related Backup sheets shall not include charges and costs associated with the Roadway Support System (RSS) or the Maintenance Phase. These costs shall be provided on separate Price Proposal Sheets as described further below.

To complete Sheets 2, 2-1, 2-1a, 2-2, 2-2a, 2-3, 2-3a, and 2-4 Proposers should do the following:

1. Sheets 2-1, 2-2, and 2-3. In the columns provided under each cost component (Items 1- 9),enter a description for each price element for each component in as much detail as space allows.Moving to the right in the 2nd column (B) enter the quantity for each item and in the 3rd column(C) enter the unit costs. If the item is provided as a lump sum, the quantity should be shown as1. Total item costs will be calculated automatically. Moving to the right, in the 5th column (E),enter the labor costs associated with each of the price elements. The costs for each price elementwill then automatically be calculated and the summary will be shown in the appropriate line itemon Sheet 2. The proposer must complete this process for Zone Type AET 2 (Sheet 2-1), TypeAET 2+ (Sheet 2-2) and Type AET 3 (Sheet 2-3).

2. Sheet 2-4. In the columns provided under each tolling location Items 1 - 21, enter a descriptionfor each price element for each tolling location in as much detail as space allows. Moving to theright in the 2nd column (B) enter the quantity for each item and in the 3rd column (C) enter theunit costs. If the item is provided as a lump sum, the quantity should be shown as 1. Total itemcosts will be calculated automatically. Moving to the right, in the 5th column (E), enter the laborcosts associated with each of the price elements. The costs for each price element will thenautomatically be calculated and the summary will be shown in the appropriate line item on Sheet2.

3. Sheet 2. This sheet will be automatically populated from Sheet 2-1, 2-2, 2-3, and 2-4. NoProposer input is required.

4. Sheets 2-1a, 2-2a, and 2-3a. Enter specific names for the Key Team positions (Items 1-8) forRTCS labor costs related to the Implementation Phase. Enter their specific loaded labor rate inthe rate column and their number of hours. Moving down the sheet, enter additional laborcategories for all labor to be used to complete this Work, including rates and hours. The staff



names are not required for these additional positions (i.e. the staff name cell that are not highlighted in a light red). The total labor dollars will be calculated for each staff person and labor category and a grand total will be calculated. The labor dollar grand total must match the Total on the corresponding zone type sheet (Sheet 2-1, 2-2, and 2-3). A labor check cell is provided to assist Proposers with verifying that the two (2) labor totals are equal. The proposer must complete this process for Zone Type AET 2 (Sheet 2-1a), Type AET 2+ (Sheet 2-2a) and Type AET 3 (Sheet 2-3a).

5 COMPLETION OF ROADWAY SUPPORT SYSTEM (RSS) COST - SHEETS 3, 3-1, 3-1a, and 3-2

The Proposer’s proposed total price for the Roadway Support System (RSS) portion of the Implementation Phase shall be the aggregate of all costs included in Sheet 3. This sheet covers all costs associated with the RSS for the KTA Turnpike to complete the implementation, such as project management, engineering and Design, Software and Testing.

The RSS cost shall include all costs for items identified in line items 1 through 17 of Sheet 3 associated with the RSS cost component. The total price shall include (without limitation) all overhead, burden, profit, taxes, duties, fees, warranties, and other items necessary for the Contractor to complete the Work. The costs shall also include (without limitation) all Equipment, supplies, Software, parts and materials, Contractor-acquired permits, licenses, warranties, and other items necessary to meet the Contractor contractual requirements associated with the RSS Cost. No price escalation will be allowed above the costs provided on the Price Proposal Sheets to complete this Work except as set forth in Section 13.

The prices on Sheet 3 and related Backup shall not include charges and costs associated with the RTCS or the Maintenance Phase. These costs shall be set forth on separate Price Proposal Forms as described in Section 4 above.

Proposers shall complete Sheets 3, 3-1, 3-1a, and 3-2 as follows:

1. Sheet 3-2. This sheet includes Initial Spare Parts and Equipment items for the RTCS and RSSinclude at a minimum spares equivalent to one (1) tolling location of equipment.

In the columns provided under each cost component (Items 1-9 for the RTCS and Items 1-2 forRSS), enter the total quantity in the 2nd column (B) for each listed element required. If the item isprovided as a lump sum, the quantity should be shown as 1. Moving to the right in the 3rd column(C), enter the unit cost for each item. If additional items are required to be included under eachcomponent provided by the Proposer, enter each element name using the additional spacesprovided under the appropriate component section. For all additional items entered, the Proposermust also enter the total quantity and unit cost as described above. Total item costs will becalculated automatically for each item.

The Total RTCS and RSS Initial Spare Parts and Equipment costs will then automatically becalculated and shown in the appropriate line item within item 13 on Sheet 3-1.

2. Sheet 3-1. This sheet provides back up for Sheet 3 cost components 1-12 and 14-17. Enter adescription for each cost component in as much detail as space allows in column (A/B). In column(C), enter the number of units for each component. In column (D) enter the unit cost for theassociated component. If the item is provided as a lump sum, the quantity should be shown as 1.Total unit costs will be calculated automatically. Moving to the right, in the 6th column (F), enterthe labor costs associated with each of the price elements. Please note the following regardingSheet 3-1:



• Line item 13 – Initial Spare Parts and Equipment – One Tolling Location is automaticallypopulated from Sheet 3-2.

The costs for each price element will then automatically be calculated and the summary will be shown in the appropriate line item on Sheet 3.

3. Sheet 3. This sheet is automatically populated from Sheet 3-1. No Proposer input is required.

4. Sheets 3-1a. Enter specific names for the Key Team positions (Items 1-8) for the RSS labor costsrelated to the Implementation Phase. Enter the specific loaded labor rate in the rate column andtheir number of hours. Moving down the sheet, enter additional labor categories for all labor tobe used to complete this Work, including rates and hours. The staff names are not required forthese additional positions (i.e. the staff name cells that are not highlighted in a light red). The totallabor dollars will be calculated for each staff person and labor category and a grand total will becalculated. The labor dollar grand total must match the Total labor dollars on the correspondingsheet (Sheet 3-1). A labor check cell is provided on the bottom of the sheet to assist Proposerswith the verifying that the two (2) labor totals are equal.

6 COMPLETION OF ROADSIDE TOLL COLLECTION SYSTEM (RTCS) HARDWARE MAINTENANCE AND SOFTWARE SUPPORT SERVICES COST (BASE AND OPTIONAL EXTENSIONS) SHEETS 4, 4-1 AND 4-1a

The Proposer’s proposed total price for the Roadside Toll Collection System (RTCS) Hardware Maintenance and Software Support Services shall be the aggregate of all costs included in Sheet 4. This sheet covers all costs associated with the Maintenance of the RTCS for KTA Turnpike.

The costs shall include (without limitation) all Contractor management, administrative and support labor costs, as well as all direct costs associated with maintaining the RTCS system. The total price shall include (without limitation) all overhead, burden, profit, taxes, duties, fees, warranties, Equipment, supplies, Software, parts and materials, Contractor-acquired permits, licenses, warranties, and all other items necessary to meet the Contractor contractual requirements associated with the RTCS Maintenance. All labor rates shall be entered in 2024 dollar values and are to include overhead, burden and profit (“2024 Loaded Labor Rate”). No price escalation will be allowed above the costs provided on the Price Proposal Sheets to complete the Work, except as provided in Section 13.

Proposers shall complete Sheets 4, 4-1, and 4-1a as follows:

1. Sheet 4-1. For the Base Contract for Maintenance (Years 1–7), as well as for the OptionalExtension 1 (Years 1-3) and the Optional Extension 2 (Years 1-3), each year is identified with acorresponding set of Work elements. Starting in column (B), enter the monthly per-zone costassociated with each price element. (Please note that column (C), the monthly labor cost perzone, is automatically populated from Sheet 4-1a and therefore requires no input from theProposer.) Include all other direct, non-labor costs required for each price element. The TotalMonthly costs for each year will then automatically be calculated and the summary will be shownin the appropriate line item on Sheet 4.

2. Sheet 4. This sheet is automatically populated from Sheet 4-1; it requires no input from theProposer.

3. Sheet 4-1a, the Proposer shall do the following:

• Enter specific names for the Key Team positions (Items 1-8) required for the RTCS HardwareMaintenance and Software Support Services portion of the Maintenance Phase.



• Moving down the sheet, enter the names of additional labor categories for all labor to beused. Staff names are not required for these additional positions.

• Enter the 2024 specific loaded labor rate for each Key Team staff member and labor categoryin the 2024 Loaded Labor Rate column.

• For evaluation purposes the Maintenance Year 1 Rate will automatically be populated basedon the 2024 Loaded Labor Rate and no assumed annual escalation.

• Next, enter the annual number of hours for each position/classification required for all tollingzones for Year 1 and Year 2. Hours for Base Contract Years 3 through 7 and OptionalExtensions Years will automatically populate based on Year 2. Labor rates for MaintenanceYears 2 through 7 and Optional Extension 1 and 2 will then automatically populated using anassumed annual escalation of 2% to 3% from the previous year for evaluation purposes. Notethat the actual labor price adjustments will be determined as described in Section 13.

• The total labor dollars will be calculated for each staff person and labor category forMaintenance Years 1 through 7 and each year of the Optional Extensions periods. A grandtotal will be calculated for each year. The Total Monthly Per Zone Cost for each year willthen automatically be calculated and the summary will be shown in the appropriate line itemon Sheet 4-1.

7 COMPLETION OF ROADWAY SUPPORT SYSTEMS (RSS) MAINTENANCE AND SOFTWARE SUPPORT SERVICES COST (BASE AND OPTIONAL EXTENSIONS) SHEETS 5, 5-1, AND 5-1a

The Proposer’s proposed total price for the Roadway Support Systems (RSS) Maintenance and Software Support Services shall be the aggregate of all costs included in Sheet 5. This sheet covers all costs associated with the Maintenance of the RSS for the KTA Turnpike.

The costs shall include (without limitation) all Contractor management, administrative and support labor costs, as well as all direct costs associated with maintaining the RSS Maintenance. The total price shall include (without limitation) all overhead, burden, profit, taxes, duties, fees, warranties, Equipment, supplies, Software, parts and materials, Contractor-acquired permits, licenses, warranties, and all other items necessary to meet the Contractor contractual requirements associated with the RSS Maintenance. All labor rates shall be entered in 2024 dollar values and are to include overhead, burden and profit (“2024 Loaded Labor Rate”). No price escalation will be allowed above the costs provided on the Price Proposal Sheets to complete the Work, except as provided in Section 13.

Proposers shall complete Sheets 5, 5-1, and 5-1a as follows:

1. Sheet 5-1. For the Base Contract for Maintenance (Years 1–7), as well as for the OptionalExtension 1 (Years 1-3) and for the Optional Extension 2 (Years 1-3), each year is identified witha corresponding set of Work elements. Starting in the 2nd column (B), enter the monthly quantityfor each item. In the 3rd column (C) enter the unit cost. If the item is provided as a lump sum, thequantity should be shown as 1. Total item costs will be calculated automatically. Moving to theright, in the 5th column (E), enter the labor costs associated with each of the price elements. Ifadditional items are required to be included under each component provided by the Proposer,enter each element name using the additional spaces provided under the appropriate componentsection. For all additional items entered, the Proposer must also enter the total monthly quantityand unit cost as described above. Include all monthly labor costs and other direct, non-labor costsrequired for each price element. The monthly costs for each price element will then automaticallybe calculated and the summary will be shown in the appropriate line item on Sheet 5.




3. Sheet 5-1a. Proposers shall do the following:

• Enter specific names for the Key Team positions (Items 1-8) to be used for these RSSMaintenance and Software Support Services.

• Moving down the sheet, enter the names of additional labor categories for all labor to beused. Staff names are not required for these additional positions.

• Enter the 2024 specific loaded labor rate for each Key Team staff member and labor categoryin the 2024 Loaded Labor Rate column.

• For evaluation purposes, the Maintenance Year 1 Rate will automatically be populated fromthe 2024 Loaded Labor Rate and no assumed annual escalation.

• Next, enter the annual number of hours for each position/classification required for the RSSMaintenance and Software Support Services for Year 1 and Year 2. Hours for Base ContractYears 3 through 7 and Optional Extensions Years will automatically populate based on Year2. Labor rates for Maintenance Years 2 through 7 and Optional Extension Years 1 and 2 willthen automatically populate using an assumed annual escalation of 2% to 3% from the previousyear for evaluation purposes. Note that the actual labor price adjustments will be determinedas described in Section 13.

• The total labor dollars will be calculated for each staff person and labor category for Years 1through 7 and each year of the Optional Extensions periods. A grand total will be providedfor each year. This labor dollar total must match the total labor dollars for each year on Sheet5-1. A labor check cell is provided on the right-hand column of Sheet 5-1 to assist Proposerswith verifying that the two labor totals are equal.

8 COMPLETION OF FUTURE ROADSIDE TOLL COLLECTION SYSTEM (RTCS) AET ZONE SYSTEM IMPLEMENTATION COST SHEETS 6 AND 6-1

The Proposer’s price for Future Roadside Toll Collection System (RTCS) AET Zone System Implementation Cost shall be the aggregate of all costs included in Sheet 6. This sheet covers all costs required for potential future zone type(s) which may be implemented during the term of the Contract. These future prices are for the purpose of evaluation only.

The total price shall include (without limitation) all overhead, burden, profit, taxes, duties, fees, warranties, Equipment, supplies, Software, parts and materials, Contractor-acquired permits, licenses, warranties, and all other items necessary to meet the Contractor contractual requirements of the Implementation and Maintenance of any optional facilities.

Proposers shall complete Sheets 6 and 6-1 as follows:

1. Sheet 6-1. In the rows provided under each future zone type, enter the quantity for each itemin the Quantity per Toll Zone column (B) and enter the unit cost in the Units ($) column (C). Ifthe item is provided as a lump sum, the quantity should be shown as 1. Include all monthly laborcosts and other direct, non-labor costs required for each price element. The costs for each priceelement will automatically be calculated and the summary cost will be shown in the appropriateline item on Sheet 6.




9 COMPLETION OF ADDITIONAL SERVICES RATES - SHEET 7-1

On Sheet 7-1, the Proposer shall provide a listing of staff positions and loaded hourly labor rates for the purpose of providing pricing for future Work not currently included in Section III, Scope of Work and Requirements. All changes to the Contract involving labor shall use the hourly labor rates in this table. All hourly labor rates shall be stated for the year 2022 and shall be inclusive of burden/overhead and profit. Hourly labor rates shall be adjusted based on changes to the CPI for the previous year as described below.

The Proposer shall also provide the current associated Overhead including burden and Profit rates in the cells identified.

10 COMPLETION OF MAINTENANCE MONTHLY COST – SHEET 8

The Maintenance Monthly Cost sheet summarizes and totals the RTCS and RSS monthly costs for the Base Contract for Maintenance (Years 1–7), as well as for the Optional Extension 1 (Years 1-3) and for the Optional Extension 2 (Years 1-3). The sheet automatically populates the Proposer’s monthly Maintenance cost from Sheets 4 and 5 and combines them to show the Total Maintenance Monthly Cost. No Proposer input is required.

11 COMPLETION OF PAYMENT SCHEDULE – EXHIBIT B

The Payment Schedule sheet applies the Implementation Roadside Toll Collection System (RTCS) and the Roadway Support System (RSS) Design and Development Costs and Hardware, Equipment and Off-the Shelf Software to payment milestones and associated percentages shown in RFP Exhibit B - Payment Schedule. The sheet takes the Proposer’s Implementation price shown on Sheets 2 and 3 and multiplies it by the percentage associated with each payment milestone. The result is a dollar amount to be paid for each milestone. No Proposer input is required.

12 COMPLETION OF PROJECT SUMMARY - SHEET 1

Sheet 1 will automatically summarize the costs and pricing detailed in Sheets 2 through 5. These costs will be totaled and presented in the line entitled Total Implementation and Maintenance Cost including Optional Extension Phases.

Sheet 6 Future RTCS AET Zone System Cost by Zone Type is automatically populated onto Sheet 1 for consideration of future work. These future prices are for the purpose of evaluation only.

To complete Sheet 1, Proposers must do the following:

1. An officer of the Proposer or an individual otherwise authorized in writing by an officer of theProposer is required to enter the price written out in words for the Grand Total Cost.

2. The sheet will need to include a signature and date, along with the authorized officer’s name, title,address and phone number.



13 COST ESCALATION

Pricing that is noted above as subject to adjustment shall be adjusted up or down from the Proposal pricing using the following Bureau of Labor Statistics’ (BLS) Employment Cost (CPI) indices as applicable:

CPI: CUUR0400SA0 Consumer Price Index - All Urban Consumers; West Urban All Items

NOTE: The above index names and numbers were obtained from the Bureau of Labor Statistics (BLS) and were current as of the date this RFP was written. In the event that the BLS updates an index name or number, KTA shall consult the BLS web site to determine the new name and number of the index. More information about the index can be found on the U.S. Bureau of Labor’s website (see http://www.bls.gov/cpi/).

For the purposes of the price proposal calculations, an assumed rate has been included. Adjustments shall be made to future prices based on actual CPI (Labor) for each applicable year. The basis for calculating the actual CPI to be applied shall be as follows:

1. Annual adjustment to prices shall be made using the anniversary date of the start of theMaintenance Phase at which each new Maintenance year begins.

2. In the first applicable year for adjustments (Year 2 of the Maintenance Phase) the reference forthe adjustment calculation shall be the 2024 Loaded Labor Rate provided by Proposers.

The assumed CPI index for evaluation purposes has been applied to the following Cost Worksheets ONLY:

1. Sheet 4 (including Backup sheets 4-1 and 4-1a) and

2. Sheet 5 (including Backup sheets 5-1 and 5-1a).

Adjustments shall be made to future prices in the above sheets based on actual CPI (Labor) for each applicable year. The basis for calculating the actual CPI to be applied shall be as follows:

1. Annual adjustment to prices shall be made using the anniversary date of start of the MaintenancePhase at which each new Maintenance year begins.

2. In the first applicable year for adjustments (Year 2 of Maintenance) the reference period for theadjustment calculation shall be the 2024 Loaded Labor Rate.

3. For the subsequent applicable years of Maintenance, as well as for Optional Extension 1 (ExtensionYears 1-3) and for Optional Extension 2 (Extension Years 1-3), the CPI adjustments shall beapplied against the previous reference year. For example, Maintenance and Software SupportServices pricing shall be adjusted using the index change from Maintenance Year 2 as a referencepoint for adjusting each of the pricing elements identified in the above table).

4. The annual adjustment shall be equal to the cumulative change in the applicable index for the latestprevious 12-month period available at the time of the anniversary date.

5. The applicable index shall be applied as follows:

a. CPI shall be applied when the entire component of the cost is direct Contractor labor.

http://www.bls.gov/cpi/

Roadside Toll Collection System RFP Exhibit D - Forms

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit D

Exhibit D Forms

Form D-1 Proposal Cover Sheet

Form D-2 List of Subcontractors

Form D-3 Recent Client List

Form D-4 Reference Forms Part 1


Form D-6 Requirements Conformance Matrix

Form D-7 Price Proposal Form

Form D-8 Proposer Questions Form

Form D-9 Surety Commitment Letter

Form D-10 Acknowledgement of Receipt of Addenda

Roadside Toll Collection System RFP Exhibit D – Forms – Proposal Cover Sheet

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit D-1

Form D-1 Proposal Cover Sheet

(A Word version of the Proposal Cover Sheet is “paper clipped”

to this KTA RTCS Exhibits file for ease of completion.)

Roadside Toll Collection System RFP Exhibit D – Forms – Proposal Cover Sheet

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibit D-1, Page 1 of 1

KANSAS TURNPIKE AUTHORITY

ROADSIDE TOLL COLLECTION SYSTEM

REQUEST FOR PROPOSALS

EXECUTION: In compliance with this Request for Proposal, and subject to all the conditions herein, the undersigned offers and agrees to furnish any or all Services or goods upon which prices are offered, at the price(s) offered herein, within the time specified herein. By executing this offer, I certify that this offer is submitted competitively and without collusion.

Failure to execute/sign offer prior to submittal shall render Proposal invalid. Late offers are not acceptable.

BIDDER:

STREET ADDRESS: P.O. BOX: ZIP:

CITY & STATE & ZIP: TELEPHONE NUMBER: TOLL FREE TEL. NO:

PRINT NAME & TITLE OF PERSON SIGNING: FAX NUMBER:

AUTHORIZED SIGNATURE: DATE: E-MAIL:

Offer valid for two hundred and forty days (240) days from Proposal Due Date.

Roadside Toll Collection System RFP Exhibit D – Forms – List of Subcontractors


Form D-2 List of Subcontractors

(A Word version of the List of Subcontractors is “paper clipped”


Roadside Toll Collection System RFP Exhibit D – Forms – List of Subcontractors


Please duplicate this page as necessary to provide the requested information.

SUBCONTRACTOR SUBCONTRACTOR SUBCONTRACTOR

Legal Name of Company Company’s FEID Number

Company Contact Name Company Address City, State, Zip Code Company Telephone No.

Company Fax Number Company E-mail address Legal Name of Principal(s)

Address of Principal(s) City, State, Zip Code

Telephone No. of Principal(s)

Fax Number of Principal(s)

E-mail address of Principal(s)

Corporate Number (if applicable)

License Number (if applicable)

Status of License (if applicable)

Work to be Performed

Expected Percentage of Total Work

By: Signature: (1)

President or Vice President Attest: Signature: (2)

Secretary (or Assistant Secretary)

(Affix Corporate Seal) ***********************************************************************************************************

Roadside Toll Collection System RFP Exhibit D - Forms - Recent Client List


Form D-3 Recent Client List

(A Word version of the Recent Client List is “paper clipped” to

this KTA RTCS Exhibits file for ease of completion.)

Roadside Toll Collection System RFP Exhibit D – Forms – Recent Client List


# Name of Client including Address and Telephone # Project Name Project Description Start Date End Date Contract

Amount 001 002

Roadside Toll Collection System RFP Exhibit D - Forms - Reference Forms Part 1



(A Word version of the Reference Forms Part I is “paper clipped”


Roadside Toll Collection System RFP Exhibit D – Forms – Reference Forms Part 1


Proposer Minimum Experience for AET/ORT Proposer shall use this from to clearly demonstrate how it meets the minimum qualification requirements for Proposals with regard to AET or ORT Proposer project experience. Each reference provided may be contacted by KTA. Copy this form as needed to comply with the requirements outlined in the RFP for each of the Implementation and Maintenance Phase minimum requirements. Proposer’s Name: ___________________________________________________________________ Please check off which qualifications requirement this reference is intended to address (you may check more than one box to cover both Implementation and Maintenance requirements as long as the explanation below is sufficiently detailed to cover both).

Implementation Maintenance

Reference Company/Agency Name:

Address:

City:

State: Zip Code:

Phone Number:

Fax Number:

Project Manager Reference:

E-mail:

Alternate Reference*:

Phone Number:

Fax Number:

E-mail:

Alternate Reference Role on Reference Project:

*Must be completed in addition to the Project Manager reference

Proposer’s role on project and years of participation (mm/dd/yy to mm/dd/yy):



Project location, scope, cost, start / end dates:

Operational functionality, facility types (AET, ORT, etc.) number of lanes / plazas, revenue collected, etc.:

Relevant equipment and systems used:

Comparison to KTA requirements: Installed System and Maintenance documented performance, as applicable:

Key Personnel involved and role who are also proposed on KTA project:

Roadside Toll Collection System RFP Exhibit D - Forms - Reference Forms Part 2



(A Word version of the Reference Forms Part 2 is “paper

clipped” to this KTA RTCS Exhibits file for ease of completion.)



Proposer shall use this form for Key Personnel Team member references. Each reference provided may be contacted. Copy this form as needed to comply with the requirements of the RFP and the number of references cited. Key Team Member Proposed Position

Reference Company Name: Address:

City:

State: Zip Code:

Phone Number:

Fax Number:

Project Manager: E-mail:

Number of total years’ experience of Key Personnel team member in similar role to one proposed for KTA:

Reference Project: Key Personnel team member role on reference project, including dates of participation and job description: Description of reference project location, scope, cost, start / end dates, etc.: Operational functionality, number of lanes, plazas, revenue collected, ORT, AET, etc.: Relevant systems used (such as DVAS, MOMS, OCR/ALPR, etc.): Key Personnel team member’s major contributions and highlights:

Roadside Toll Collection System RFP Exhibit D - Forms - Requirements Conformance Matrix


Form D-6 Requirements Conformance Matrix

(An Excel Version of the Requirements Conformance Matrix is “paper clipped” to this KTA RTCS Exhibits file for ease of completion.)

Roadside Toll Collection System RFP Exhibit D-6 - Forms - Requirements Conformance Matrix

Exhibit D-6: Instructions for Completing Requirements Conformance Matrix

1) The Proposer shall complete and submit the Excel version of the Exhibit D-6 Requirements Conformance Matrix. The Matrix cover each of the Requirements set forth in Section III: Roadside Toll Collection System Scope of Work and Requirements.

2) The Proposer shall submit a PDF version of the completed matrix in this Proposal Section 6, in addition to submitting the Excel version of the matrix as directed in Section IV, Proposal Contents and Submission, Section 2.1 Submission of Technical Proposal.

3) Proposers shall not alter the Requirements listed in the Requirements Conformance Matrix in any way and must use the workbooks provided.

4) The following are instructions for completion of Tabs 1 - 3 of the Requirements Conformance Matrix associated with functional Requirements:

a) There are seven columns in Tabs 1 - 3 as follows:

i. No. (Column A): A sequential number that matches the requirement number in the Requirements. ii. Requirements (Column B): A description of each requirement. iii. Status (Column C): Proposer must select one of the four (4) response codes for each Requirement and enter it in this column as further detailed in item “b)” below. iv. Customer Name and Location, If Applicable (Column D): Proposer must indicate the Customer Name and Location where the functionality was deployed or implemented if the Requirement is identified as current or modified. If the software was deployed at more than one customer, the Customer Name and Location is only required for a single customer.v. Source (Column E): Indicate who will be providing the functionality; Proposer (P), subcontractor (S), third party (T), or not applicable (NA).vi. Subcontractor Name and/or 3rd Party Product/Vendor, If Applicable (Column F): If the functionality is provided by a subcontractor or third party then please enter the name of the party or product.vii. Comments (Column G): This field must be completed if the Status code is entered as “N = not provided” for the particular Requirement in order to explain why the Proposer is not complying with this Requirement.

b) Proposers must complete the Status (Column C) in the following manner:

i. Base Product = B: Enter an “B” in this column if the Requirement described is already incorporated into the Proposer’s baseline system and is provided in the proposed KTA Roadside Toll Collection System.ii. Base Modified = M: Enter an “M” in this column if the functionality exists and is provided in the proposed KTA Roadside Toll Collection System but needs to be modified to meet the requirement.iii. New Development = D: Enter a “D” if the Proposer’s baseline system does not currently have the required functionality but the functionality will be provided in the proposed KTA Roadside Toll Collection System and will be developed to meet the requirement.

iv. Not Provided = N: Enter an “N” if the Proposer will not provide the functionality and will not meet the requirement as part of its Proposal. If any row in the Status column is completed as “N” then Proposer must provide an explanation in the Comments (column G) in the corresponding row. The comment field may reference information that is included elsewhere in the Proposal.

5) The following are instructions for completion of Tabs 4 - 8 of the Requirements Conformance Matrix associated with technical and project management requirements:

a) There are four columns in Tabs 4-8 as follows:

i. No. (Column A): A sequential number that matches the requirement number in the Requirements. ii. Requirements (Column B): A description of each Requirement, iii. Compliance (Column C): Proposer must select one of the two (2) response codes for each Requirement and enter it in this column as further detailed in item “b)” below. iv. Comments (Column D): This field must be completed if the Compliance code is entered as “N = no” for the particular Requirement in order to explain why the Proposer is not complying with the Requirements.

b) Proposers must complete the Compliance (Column C) in the following manner:

i. Yes = Y: Enter a “Y” in this column if the Requirement described will be provided in the proposed KTA Roadside Toll Collection System. ii. No = N: Enter an “N” if the Proposer will not meet the associated stated requirement as part of its Proposal. If any row in the Compliance is completed as “N” then Proposer must provide an explanation in the Comments (Column D) in the corresponding row. The comment field may reference information that is included elsewhere in the Proposal.



Required InputsStatus If Applicable Source If Applicable Comments

B-Base ProductM-Base Modified

D-New Development

N-Not Provided*

Customer Name and Location

P-ProposerS-Sub

T-Third PartyNA-Not

Applicable

Subcontractor Name and/or

3rd Party Product/Vendor

Comment required if "Not Provided*", optional otherwise.

1. ROADSIDE TOLL COLLECTION SYSTEM (RTCS) – FUNCTIONAL REQUIREMENTS1.1. Project Overview

The Scope of Work and Requirements involves implementing a new Roadside Toll Collection System (RTCS) on theKansas Turnpike. A map of the project area is shown below in Figure 3-1. The Kansas Turnpike is 236 miles inlength. The Contractor will be responsible for the following for the Contract Term:

· Roadside Toll Collection System · Roadside Toll Collection System Maintenance

The Kansas Turnpike Authority (KTA) (the “Authority”) will perform Tier 1 RTCS Hardware Maintenance with local KTA staff positioned throughout the state to support the entire Turnpike, while the Contractor will perform all other RTCS Maintenance in close coordination with KTA staff.

1.1.1. Kansas Turnpike

The Kansas Turnpike will be tolled using All Electronic Tolling (herein termed “Cashless Tolling”) from theSouthern Terminal (Milepost 16.8) to the Eastern Terminal (Milepost 216.8). The new Cashless Tolling System willbe converted from its current entry/exit ticket-based system to a Mainline Barrier System. The new MainlineBarrier System will be constructed with new mainline gantries (except for the existing open road tolling (ORT)gantries, which will be reused.) The new Mainline Barrier System will be designed so that it is a ‘closed’ systemwith no free movements, meaning that all users will pass through at least one barrier Tolling Location regardlessof origin or destination. The Kansas Turnpike Cashless Tolling System will include a total of twenty-one (21)mainline Tolling Locations, in two directions of travel, for a total of forty-two (42) Toll Zones when completed.

The Cashless Tolling collection methods are assumed to be barrier tolling or segment-based tolling where tolls arecalculated based on a per-mile basis. Each Toll Zone will assess a toll fee based on the length of the segmentbetween the nearest entry and exit locations. All users will be charged a fixed, pre-determined fee based on theirTolling Location, vehicle classification, and payment type (such as Automatic Vehicle Identification (AVI)Transponders or Image-based tolling). A vehicle traveling the full length of the Kansas Turnpike will receivetwenty-one (21) transactions for a trip in one direction. This differs from the current KTA tolling approach whichutilizes a trip building, ticket-based system. The trip building system charges users for their specific trip, takinginto account the user’s entry (origin) and exit (destination) to calculate an individualized fee based on that precisedistance, vehicle class, and payment type (e.g., AVI or cash).

In the new Mainline Barrier System layout, all Toll Zones will be constructed along the turnpike mainline in orderto implement the Cashless Tolling System. The general locations of these installations were selected based onvarious site, traffic, utility, and geometric requirements to best construct the Cashless Tolling gantries andassociated supporting equipment.

· AVI and Image-based tolling;· Twenty-one (21) mainline Tolling Locations (42 Toll Zones) with generally two (2) or three (3) travel lanes and two (2) shoulders in each direction;· Dual gantry design – gantry spacing center-to-center of the box trusses of thirty-one (31) feet;

o Thirty-six (36) new dual-gantry Toll Zones will be constructed on the Mainline and shall have new RTCS Equipment installed;o Six (6) existing ORT dual-gantry Toll Zones shall be retrofitted with new RTCS Equipment at the Southern Terminal (MP 16.8), East Topeka (MP 183), and Eastern Terminal (MP 216.8) Tolling Locations (shown on Figure 3-1);

· All Tolling Locations have a concrete roadway surface through the Toll Zone; and· The KTA will provide at each of the forty-two (42) Toll Zones the following support systems:

o 12’-0”L x 8’-0”W x 9’-0”H Point of Presence (PoP) roadside enclosure building;

No. Requirements





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

o 50kW generator and automatic transfer switch (20kW for single Toll Zone locations);

o Uninterruptible Power Supply (UPS) – APC Smart-UPS 3000VA LCD RM 2U 120V (SMT3000RM2U);

o Propane tank (anticipated to be 1,000 gal) or natural gas at select Toll Zone locations;o 400A electrical service, meter and electrical panels;o Building and lighted parking pull-off area;o Power panels for raw and UPS power; ando Lightning protection.

Forecasted estimated transaction volumes are provided in Attachment 1: Future Project Transactions for RTCSsystem sizing and for capacity planning; however, the delivered RTCS shall handle peak traffic volumes of up to1,500 vehicles per lane per hour.

1.1.2. General Description of Scope of Work

The Contractor shall procure, furnish, Design, test, install, and maintain the toll facilities, including all aspectsrequired to create complete AVI (K-TAG or Interoperable) Transponder-based transactions or image-basedtransactions and transmit the transactions from the roadside to the KTA Customer Service Center (CSC) BackOffice System (BOS). The Scope of Work and Requirements also includes a Digital Video Audit System (DVAS) andToll Host System. Additionally, the Contractor is expected to provide a Complete Transaction, (including fullyformed AVI transactions or fully formed image-based transactions) for processing, reporting, and reconciliationwith the KTA CSC BOS. The RTCS components shall include all Roadside Systems and Roadway Support System(RSS) to provide complete and properly formed transactions ready for processing by the KTA CSC BOS.

The Roadside Systems shall be located at the Tolling Location and shall include but not be limited to the following:

· Toll Zone Controller;· AVI System;· Image Capture & Processing Systems (ICPS);· Automatic Vehicle Detection and Classification (AVDC);· Interfaces to roadside Wrong-Way Vehicle electronic signs (provided by others) and alert/warning notification processing;· Supporting electronics, devices, and associated communications Equipment; and· Facility Servers (optional) to support transaction and image processing, storage, and forwarding from the roadside Tolling Locations.

The RSS shall be located at the KTA Headquarters building in Wichita, KS or at a PoP roadside enclosure building(RSS location to be Approved by KTA during System Design) and shall include the following

· Toll Host System (including transaction processing, reporting, and Automated License Plate Reader (ALPR) / Optical Character Recognition (OCR) processing);· Integrated DVAS;· Integrated Maintenance Online Management System (MOMS);· All required local area networks (LAN); and· Critical Environmental Monitoring System (CEMS).

In addition, the Scope of Work and Requirements for the RTCS includes Project Management, Documentation,Design, Development, integration of a turn-key solution, testing, installation, Commissioning, Maintenance andmonitoring to provide accurate, fully-formed and verified transactions to the KTA CSC BOS for processing.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

The Contractor shall plan and implement a transition to the RTCS that does not impact revenue collection andminimizes inconvenience to customers. The existing Cashless Tolling Lanes are shown in the drawings containedin Attachment 2: KTA Existing ORT Gantry Final Design Plans and typical plans for the new construction sites areshown in Attachment 3: KTA Cashless Tolling - Construction Package 1 - 90% Design Typical Drawings. Additionalplans will be coordinated with the Contractor as the construction packages for the remaining Tolling Zones areavailable. Sample shop drawings for the existing ORT gantry structures are provided in Attachment 4: ORT GantryShop Drawings.

The Contractor shall reuse the existing gantries and PoP roadside enclosure buildings at the six (6) existing ORTToll Zones and may reuse the existing computer racks in these buildings. All other existing equipment shall bereplaced to meet this Scope of Work and Requirements and all Performance Requirements.

For the Project, the Contractor shall coordinate with KTA and KTA’s representatives for all toll System construction-related activities anticipated for this RTCS Project. The Contractor shall provide toll System Design specifications to KTA. The Contractor shall also be required to review the engineering Design and provide feedback and potentialimpacts of the Toll System and its performance early in the Design process.

It is the intent of the Requirements to permit the Contractor the flexibility in the Design and Development of theRTCS to reflect innovation and state-of-the-art, proven technology that is fully capable of meeting the requiredoperational, performance, and contractual Requirements.

Furthermore, it is the intent of KTA to provide the Contractor with a set of Performance Requirements, as detailedin Section 6.6 and Section 8, that are not overly prescriptive and at the same time reflect the minimum tolerableperformance expected of the Contractor to avoid unnecessary impact to the KTA and its customers. KTA alsobelieves these Performance Requirements minimize performance measurement and verification by theContractor for performance compliance reporting.

The Contractor shall be responsible for furnishing and mobilizing all required Equipment, facilities and resourcesto carry out this Scope of Work and Requirements and to meet Contract Requirements. This includes but is notlimited to mobilization; local office space; installation equipment storage; demobilization and site clean-up; allpermits, licenses, fees, insurance and bonds; coordination and cooperation with KTA, third parties, andInteroperable Agencies; maintenance of traffic (MOT); development and production of Documentation, Designdrawings, Plans and schedules; training; testing; safety; cooperation with KTA rules regarding security andrevenue control; and Quality Assurance and Quality Control.

1.2. Roadside Toll Collection System – General Requirements1.2.1. Cashless Tolling Facility Type and Concept

1 Contractor shall provide a Cashless Tolling facility type where all customers pay the tolls electronically. Customerstravel through toll gantries on the roadway at highway speeds.

2 The Cashless Tolling concept shall be barrier-based where vehicles pass through one or more toll facilities on themainline and customers pay a flat toll based on the payment type and vehicle classification at each Toll Facilitythey use.

1.2.2. Payment TypesThe System shall support the following payment types:

3 Electronic payment using a valid AVI Transponder (such as K-TAG or other Interoperable Transponder) in all lanes.

4 Electronic payment using image-based transactions in all lanes. 1.2.3. Hardware and Software General Requirements





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

5

All Hardware and Equipment supplied under this Contract shall be new and certified to have a ten (10) yearminimum service life. Materials and products that have been previously used for development work or theContractor’s internal testing, or items that have been salvaged or rebuilt shall not be permitted to be used inconnection with this Contract.

6 All components, supplies and materials furnished under this Contract for the RTCS shall be new, Commercial Off-the-Shelf (COTS) and field-proven in revenue Operations.

7 All components procured, furnished, and installed by the Contractor shall be available through multiple sourcesidentified by the Contractor and the names of such sources shall be included in the Bill of Materials (BOM) andreadily available to KTA, unless otherwise Approved by KTA during Design.

8 The KTA shall have the right to purchase third-party Equipment directly from the Equipment vendor.

9 All Hardware and Software provided under this Contract shall be supported by their manufacturers, and shall beUpgradeable, maintained, Updated, patched and secured throughout the Contract Term.

10 Proof of purchase in the form of purchase orders, dated invoices and shipping bills shall be retained by theContractor and furnished to KTA in accordance with the Requirements of this Scope of Work and Requirementsand the Contract.

1.2.3.1. MaintainabilityThe RTCS Hardware shall be Designed with the following specifications:

a) modular, replaceable and repairable components to allow for efficient Maintenance;b) all replacements shall be plug compatible with no changes required;c) all components that perform the same function shall be interchangeable;

d) all zone controllers shall be Designed such that they are identical and can be configured to operate through the addition of Hardware pluggable modules and setting of appropriate Software parameters at the specific number of lanes at each site as shown in Table 3-1: Toll Zone Lane Configurations and Attachment 3: KTA Cashless Tolling - Construction Package 1 - 90% Design Typical Drawings;

e) zone controllers shall be expandable for at least one additional travel lane to accommodate future growth without major Hardware or Software modifications; f) where possible, all in-lane Equipment shall use TCP/IP network protocol to communicate with the zone controller;g) Contractor’s electronic Design and installation shall prevent electrical disturbances and noise in the electronics;h) all expansion bus (for example peripheral component interconnect express (PCIe)) shall have a minimum of two (2) spare slots to support the addition of components;i) all field wiring shall be terminated on screw lugs or connectors and all connectors shall be keyed or polarized to prevent incorrect connections;

j) all wiring and connectors shall be labeled and strain relief shall be provided to protect the conductors;

k) surge suppression shall be provided for all field wiring susceptible to lightning or similar surges;l) all lane Equipment shall be fused and protected against over current, over voltage, under voltage and lightning;m) redundant power supplies shall be provided for all required internal DC voltages; andn) all Equipment shall be properly grounded to ensure the safety of Maintenance personnel.

12 If inductive loops are used for tolling, all splices between loop wire and lead-in cable must meet electrical industrystandards and any alternate splicing methods shall be Approved by KTA.

1.2.3.2. Diagnostics

11





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

13

Maintenance personnel shall have easy access to components, and removal, testing, and replacement shall notrequire extensive effort or tools. All test points necessary to diagnose the Equipment while in operation shall beeasily accessible and Light Emitting Diode (LED) indicators shall be provided to assist technicians to identify anddiagnose problems.

14 Equipment mounting and installation Design shall support the Maintenance of Equipment from below on tollgantries as applicable to each Toll Zone.

15 Technicians shall have the ability to connect a laptop or other diagnostic Equipment authorized by KTA inaccordance with KTA policies to troubleshoot the components. Technicians shall have secured and remote accessto the device to monitor its status and to perform diagnostics when the lane is in operation.

16 For easy diagnostic and troubleshooting, all error and event logs shall be consolidated such that all events anderrors associated to a transaction are in a single log. The consolidated error and event logs shall be retainedonline for a Configurable period of time and shall be easily accessible to the technicians.

17 The consolidated error and event logs shall also be transmitted to the MOMS and available to Authorized User inviewable form. Search and filter capability shall be provided to display and review data in the consolidated log forup to 180 Calendar Days of backlog.

18 All diagnostics performed on the Roadway System shall be recorded and automatically reported to the MOMS,including the technician ID, the time the Maintenance was performed, and all status and recovery messages.

19 All diagnostic Software and specialty tools required for support of Maintenance activities shall be supplied by theContractor and KTA shall have full rights and access as further defined in the Contract to such diagnostic Softwareand specialty tools.

20 All diagnostic Software intended for laptop PCs shall function under a KTA-Approved version of MicrosoftWindows operating system.

21 All Software and operating systems shall meet the KTA’s most current technology standards; all such Software andEquipment shall meet the security standards set by KTA and as set forth in Attachment 6: KTA InformationSecurity Overview.

1.2.3.3. Customized Hardware

22

If customized components or controllers are used, the Contractor shall provide detailed Documentation on theDesign, production and testing of these units and shall provide usage rights to KTA. Documentation shall includeelectronic diagrams, component layouts and the detailed Bill of Material listing manufacturers/vendors. TheContractor shall identify all customized components and controllers and indicate their plan to make themavailable for the Contract Term, including the option for placing in escrow.

1.2.3.4. Environmental

23

The RTCS Equipment to be supplied will be installed in areas exposed to the range of climatic conditions found inKansas. In addition to the climatic conditions, the Equipment will also be subjected to harsh environmental factorsnormally found in the operation of a toll lane, such as, but not limited to, car, truck, and bus emissions; industrialexhausts; industrial cleaners; gasoline and car lubricants; Electromagnetic Interference (EMI) and Radio FrequencyInterference (RFI), and vibrations. These conditions shall be taken into account in the Design and selection ofEquipment used on this Project and the Contractor shall ensure that the System works accurately and reliably insuch environment.

24 Lane electronics, zone controllers, Image Capture & Processing System (ICPS) controllers/servers, AVDC systemsand other components shall be able to operate in the enclosed environment in equipment racks installed withinthe PoP roadside enclosure buildings.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

25 All Hardware provided under this Contract shall be corrosion resistant and remain corrosion resistant for theContract Term or ten (10) years, whichever is greater.

26 All lane Equipment and devices shall be Designed to handle snow, heavy rain, fog and mist-like conditions andthere shall be no degradation in the System performance under such environmental conditions.

27 The lane Equipment and devices not in environmentally controlled conditions shall operate with no degradationof performance in ambient air temperature of negative thirty (-30) to fifty-five (55) degrees Celsius, with andwithout direct sunlight, and relative humidity of five to one hundred percent (5% to 100%).

28 During the Design phase, the Contractor shall provide specification sheets that prove the zone controller andsupporting lane electronics, devices, and associated communications Equipment, meet the environmentalspecifications given above. Results of all environmental tests conducted shall be provided to KTA for Approval.

29 All exposed in-lane Equipment, when in its fully assembled configuration, shall not be damaged, nor shalloperational performance or expected lifetime be degraded. During the Design Phase, the Contractor shall providespecifications for the in-lane Equipment for KTA Approval.

1.2.3.5. Assembly

30

All customized Hardware shall be assembled and tested in the Contractor’s fabrication/assembly facilities beforebeing installed in the lane in accordance with KTA Approved test Plan for customized Hardware. All chassis,attachments, and Hardware shall be fabricated with stainless steel, hot dipped galvanized or other materialsresistant to salt exposure and corrosion.

31 All customized Hardware shall be identified and shall undergo a seventy-two (72) hour burn-in test before theyare installed in the lanes, in accordance with KTA Approved test Plan.

32 Customized Hardware assembly shall facilitate easy replacement of failed components in accordance withRequirements of this Scope of Work and Requirements.

1.2.4. Bill of Materials

33 The Contractor shall include the BOM for all Equipment and Hardware supplied for the RTCS. The secondmanufacturer source for all Equipment and Hardware shall be included with any exceptions noted and explained.During the Design Phase the BOM shall be finalized and all changes shall be subject to the Approval of KTA.

34 Prior to purchase of any Equipment and as part of its Design the Contractor shall submit the final BOM to KTA forApproval. No Equipment shall be purchased by the Contractor prior to Approval of the BOM and the Design,unless otherwise authorized in writing by KTA.

35 All Hardware and Software procured under this Scope of Work and Requirements shall be confirmed to be thelatest model/version at the time of purchase with the required warranty, security, Maintenance and supportServices as specified in this Scope of Work and Requirements.

36 Updates to the BOM shall be provided by the Contractor whenever Equipment and Hardware changes occur andat a minimum on a semi-annual basis over the Contract Term. All Equipment and Hardware changes shall besubject to the Approval of KTA.

1.2.5. Spare Parts and Support

37 The RTCS procured, furnished, and installed under this Contract shall allow the Contractor to Maintain and replacetolling parts for the Contract Term. The Contractor shall maintain a sufficient level of spares required to meetPerformance Requirements.

38 This Contract includes the initial quantities of spare parts required for the operation of the Tolling Locationsduring the Contract Term. Costs for the replacement of spare parts during the Contract Term shall be theresponsibility of KTA.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

39 At the end of the Maintenance term, all spare parts inventory shall be turned over to KTA at 100 percent (100%)inventory level. The Contractor shall identify (via the MOMS) the warranty status for each piece of Hardwarethroughout the Contract Term and the warranty period remaining, if applicable.

1.2.6. RTCS Software

40 The operating systems, database, other third-party Software, and RTCS Software procured, furnished, andinstalled by the Contractor shall support real time Operations of the lane and shall be field-proven.

41 The operating systems shall have a clear and documented future Upgrade path and shall be supported for aminimum of ten (10) years. The Contractor shall ensure that the risk of obsolescence to the Hardware isminimized through the selection of the operating System Software and the peripheral Hardware.

42 All RTCS Software developed, furnished, and installed under this Contract shall be warranted against Softwaredefects, security vulnerabilities and deficiencies for the life of the Project.

43 The Contractor shall provide, at their cost, an annual information security risk assessment and a vulnerability scanperformed by a third-party Approved by KTA and in consultation with KTA IT Security. The Contractor shallprovide the assessment results to KTA.

1.2.7. RTCS Toll Facility and Lane Configurations44 The RTCS shall support Cashless Tolling Facilities as described in the Scope of Work and Requirements.

45 The RTCS shall support the lane configurations in Table 3-1: Toll Zone Lane Configurations, Attachment 2,Attachment 3 and dimensions detailed below for each type of Toll Facility.

46

Shoulder lane and travel lane widths may vary slightly by facility, location, lane type and zone, and are detailed inTable 3-1: Toll Zone Lane Configurations. Travel lanes shall be equipped with the required toll collectionsubsystems to accommodate the variation in widths and road curvature. During the detailed Design period, theContractor shall make the required adjustments to the System Design to accommodate for variations in the actuallane widths and curvature. Travel lane widths shall be assumed to be twelve (12) feet.

47

Shoulder lanes shall be equipped with rear-only ICPS, and sensors to trigger the cameras and to detect and framethe vehicle traveling on the shoulder, as required to meet Performance Requirements. Sensor layout and TollZone Design shall ensure that shoulders have full coverage to correctly detect and process vehicles straddling theshoulders.

1.2.8. Roadside Access Requirements1.2.8.1. PoP Enclosure Access

48

KTA will control access to the PoP roadside enclosure buildings via a KTA-provided Access Control and SecurityMonitoring System. Contractor personnel shall use only assigned, individual proximity cards/keys and shall notshare cards/keys with any other individuals or make copies of any assigned cards/keys. Contractor personnel shallimmediately return all assigned cards/keys to KTA upon request.

1.2.8.2. Toll System Software Security

49 Accounts for user access to the System shall require a strong password in accordance with KTA passwordmanagement standards in Attachment 6: KTA Information Security Overview. The access shall be role based andlimited to the authorized Contractor staff and designated KTA personnel.

50 User access security, including sign-on facilities, permission control and access privileges for different levels shallbe provided for the files, directories and application Software and shall be fully Configurable by a systemadministrator.

51 Remote access to all RTCS systems shall be a virtual private network (VPN) client-based and controlled through acentral repository with each user having a unique log-in. The RTCS systems shall be able to operate in stand-alone/local mode when Wide Area Network (WAN) communications are disrupted.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

52

User sign-on, access and access failures, both local and remote, to any element of the RTCS shall be recorded andtracked for security audit proposes and reported to the MOMS. The System shall continuously and automaticallymonitor for unauthorized access; access violations shall be reported to the MOMS as Priority 1 alert. Thesereports shall be provided to KTA within twelve (12) hours of discovery.

53 The Contractor shall develop the access levels, user roles and privileges matrix during System Design with KTAinput and Approval. The System shall allow for additional changes to the access levels, user roles and the additionof personnel in a secure manner.

54 A System level account shall be provided for KTA security systems to perform “credentialed” scans. Additionally,KTA IT Security can request the Contractor to perform any scans and ensuing reports through the Contract Term.

55 The Contractor shall not circumvent KTA Approved System security. All access to the System and Approvedchanges made shall be recorded, monitored, reviewed and audited. Specific requirements for this shall bedeveloped by the Contractor during System Design.

56 Authorized Users shall have access to the zone controller user access logs to audit the System access. 1.2.9. Roadside System Subsystems1.2.9.1. Automatic Vehicle Identification (AVI) System Integration

57

The Contractor will provide the AVI System, including AVI readers and antennas based upon the quantitiesdetermined by the Contractor in consultation with and Approval by KTA. The AVI Equipment provided by theContractor shall be compliant with the KTA, Central U.S. Interoperable (CUSIOP) Partners, and NationalInteroperability (NIOP) requirements and able to read and process the anticipated protocols defined below.

58 The Contractor shall be responsible for the AVI System Equipment installation, integration and Tier 2 and Tier 3Maintenance. KTA will provide Tier 1 Maintenance of the AVI System Equipment.The Contractor shall integrate the RTCS with the AVI System at the Tolling Locations specified in this Scope ofWork and Requirements. These integration Requirements shall include all the following anticipated protocols tobe supported by the RTCS in no specific order of precedence:

a) ISOB 80K (SeGo);b) ISOC (ISO 18000-63) (6C); andc) PS111 (TDM) (IAG/E-ZPass Group).

60 The RTCS shall support AVI readers that have redundancy.

61 The Contractor shall maximize any inherent redundancy built into the AVI readers whereby the failure of themaster or primary reader will result in the reporting of the Transponder reads via the slave or secondary reader.

62 The Contractor shall furnish and install all other Hardware, cabling (including RF, communication, and powercables), connectors and associated mounting fixtures to form a fully functioning AVI System that meets theRequirements of this Scope of Work and Requirements.

63

The Contractor shall be responsible for the physical tuning of the AVI Equipment, and for integrating the AVISystem into the Contractor in-lane Design. In addition, the Contractor shall have the AVI vendor certify that thelanes are tuned to the AVI specifications. All AVI installation, configuration and tuning shall be in compliance withthe AVI vendor Requirements. (NOTE: A frequency assessment was performed for the first five Toll Location sitesfor the 900 MHz to 922 MHz band. Results are shown in Attachment 5: Frequency Assessment for reference bythe Contractor.)

64 The Contractor is responsible for synchronizing all AVI readers that are at close proximity to the Tolling Locationsas required by the AVI vendor.

59





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

65 The AVI System Design shall provide full coverage at all areas of the Toll Zone/lane to read and reportTransponders. Transponders on vehicles straddling the shoulders by a distance of up to four (4) feet shall be readand reported to the zone controller.

66 The Contractor shall support adjustments to the antenna quantity and placement based on the final laneconfiguration.

67 The RTCS integrated with the AVI System shall have the ability to process Transponders mounted on vehiclestraveling in “stop-and-go” and “bumper-to-bumper” traffic and vehicles traveling at speeds of up to 100 mph.

68

The integrated zone controller and AVI System shall be able to read the Transponder and report all KTAInteroperable Transponders and National Interoperable Transponders on vehicles traveling through any area ofthe Toll Zone, including but not limited to: center of lane, traversing lanes, straddling lanes, and straddlingshoulder with no degradation of performance or interference. The Priority of the processing Transponderprotocols will be specified by KTA during the Design process.

69 The read zones in the lanes at a Toll Zone shall be tuned such that Transponders in vehicles traveling in theadjacent lanes, but opposite direction of travel, are not reported by the AVI System.

70 The AVI System will buffer Transponder reads when it is unable to communicate to the zone controller. Whencommunications are restored, the buffered reads shall be reported to and processed by the zone controller.

71 If more than one Transponder is present in a vehicle, the zone controller integrated with the AVI System shallmeet the AVI accuracy Requirements for each Transponder. The Transponders shall be reported separately andtransaction association rules shall be in accordance with the Approved Business Rules and Design.

72

The Contractor shall use the full capability of the selected AVI System to obtain AVI System status in accordancewith the manufacturer specifications and report such status to the MOMS. Loss of communication to any elementof the AVI System shall be immediately detected by the zone controller and reported to the MOMS. TheContractor-provided monitoring logic shall specifically detect any AVI failures and generate alarms when failuresare detected.

73

To support remote access to the AVI System, a user interface shall be provided so that Software lane tuning,diagnostics, configuration changes, and other remote support shall be available to KTA authorized personnel.Setup and configuration of the AVI System shall be achieved remotely and shall not require lane closure except formajor lane tuning; when initially installed; or when a reader or antenna is replaced.

1.2.9.2. Automatic Vehicle Detection and Classification (AVDC) System

74 The Contractor shall analyze the site conditions and Design, procure, furnish and install the required sensors andHardware on all lanes at the specified Tolling Locations as part of the AVDC System that performs in accordancewith Performance Requirements set forth in this Scope of Work and Requirements under all weather conditions.

75

The AVDC System shall determine the vehicle axle count and classify vehicles in accordance with the KTA VehicleClassification Structure for all travel lanes and shall include the logic to handle the exceptions identified.Classification of vehicles traveling on the shoulder lanes is not required; however, the System shall detect vehiclesthat travel on the shoulder and trigger the ICPS.

76 The KTA Vehicle Classification Structure is defined as 2-axle through 9+-axle vehicles.

77 The AVDC System shall accurately detect and classify vehicles traveling in “stop-and-go” and “bumper-to-bumper”traffic, vehicles traveling at speeds up to 100 mph, and vehicles with separation as close as ten (10) feet apart.

78 The AVDC System shall have the ability to detect trailer hitches and ensure that vehicles with a tow are reportedcorrectly as one unit to the zone controller as part of the vehicle transaction data.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

79 The AVDC System shall detect the speed of the vehicle and report the speed to the zone controller as part of thevehicle transaction data.

80 The Contractor shall ensure that there is full sensor coverage at all areas of the Toll Zone/lane and shoulder toaccurately trigger the ICPS and detect and report vehicles traveling the shoulder and vehicles straddling lanes.

81 The AVDC System shall provide vehicle event messages and signals, and vehicle classification data to the zonecontroller. Exception conditions processed by the AVDC System shall be included in the transaction data.

82

The AVDC System shall have adequate redundancy whereby a failure of a single sensor does not completelydegrade lane Operations or the System’s capability to accurately associate Transponders or captured images withthe correct vehicle. Under such degraded conditions, the Contractor shall still be required to meet the Systemaccuracy Requirements.

83

The Contractor shall Design, procure, furnish and install a secondary sensor and Equipment that are part of theAVDC System as a back-up to support image capture and vehicle framing in the event any element of the primarySystem fails or is degraded. The System shall determine the conditions (Configurable) that invoke the use of thesecondary sensors and Equipment.

84

The AVDC System shall report its health to the zone controller and shall provide status when polled. Loss ofcommunication to any element of the AVDC System shall be immediately detected and reported. All health andfailure status messages shall be transmitted and reported to the MOMS. In the event the primary AVDC Systemfails, then the secondary sensors shall be used to capture and process images in accordance with Business Rulesdetermined during Design.

85 In the event there is a Class Mismatch between the AVDC System and the Transponder class, the System shalldefault to the AVDC class and flag the transaction as an unusual occurrence as defined by the Business Rulesduring Design. The ability to enable or disable image capture for a class mismatch shall be Configurable.

86 Wrong-way Vehicle Detection. The AVDC System shall be able to detect and report vehicles traveling in the wrongdirection. In addition, the RTCS shall be able to illuminate electronic wrong-way vehicle signs that are installedand provided by others. The interface to the electronic wrong-way vehicle sign will be defined during Design.

1.2.9.3. Image Capture & Processing Systems (ICPS)

87 The Contractor shall provide an ICPS solution at the Tolling Locations that meets the Performance Requirementscontinuously 24x7 and under all light and climate conditions.

88 The Contractor shall Design, procure, furnish, and install all necessary front and rear ICPS Hardware and Softwarerequired to support image-based tolling and image processing Requirements as set forth in this Scope of Workand Requirements.

89

The Contractor shall Design, procure, furnish, and install cameras in sealed enclosures, lighting, necessary imagetriggers, back-up triggers and the necessary camera controls, and ancillary Hardware and Software required tosupport the image-based transaction processing Requirements as set forth in this Scope of Work andRequirements.

90 Camera control Software shall be provided to automatically adjust the cameras to accommodate varying light andweather conditions to maintain adequate brightness and contrast settings, with or without traffic, to ensureoptimum license plate information capture under all conditions and time of day.

91

Contractor shall install high resolution front and rear color cameras to meet the accuracy Requirements. TheRTCS System shall provide a region of interest (ROI) of the license plate and a general overview for the purpose ofidentifying the vehicle with the transaction/image package provided to the KTA CSC BOS for image-basedtransactions.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

92 The ICPS shall capture and process vehicles traveling in “stop-and-go” and “bumper-to-bumper” traffic, vehiclestraveling at speeds up to one hundred (100) miles per hour, and vehicles with separation as close as ten (10) feetapart.

93 The Contractor shall ensure that there is shoulder coverage and vehicles traveling through any area of the TollZone/lane, including but not limited to shoulder, center of lane, traversing lanes and straddling lanes, shall beaccurately detected and their images captured and processed in accordance with KTA Business Rules.

94 The System shall associate all images captured for a single vehicle to the vehicle transaction including multipleimages captured by the front, rear, and overview cameras, including all captured images for a vehicle straddlingthe lanes.

95 Lights installed by the Contractor in support of the cameras shall not distract motorists traveling in eitherdirection in the lanes. Contractor shall make no assumption of ambient light and the System shall functionwithout any degradation regardless of the ambient light.

96

The Contractor shall procure, furnish, and install the necessary redundant controllers/servers to support the in-lane ICPS Equipment. The Contractor shall provide robust, industrialized platforms and operating systems (PCs orworkstation-type operating systems are not permitted) and the processor speed and memory shall be sufficient toprocess vehicles in real time to meet the vehicle speed and peak traffic volumes of up to 1,500 vehicles per lane,per hour as specified in this Scope of Work and Requirements and as referenced in Attachment 1: Future ProjectTransactions.

97 The ICPS servers may be separate from the zone controller servers.

98 The ICPS shall provide image processing of 100 percent of all transactions, including AVI transactions and image-based transactions with no performance degradation.

99 The System shall store images at the roadside for a minimum of thirty (30) consecutive Calendar Days per lane.

100 The ICPS shall buffer images (retaining an image until its disposition is known) such that no image is lost in orderto support multiple vehicles in the lane and in accordance with KTA Business Rules.

101 The controllers/servers shall support standalone Operations and the roadside storage media shall be sized to holda minimum of thirty (30) Calendar Days of images and data per lane at each of the Tolling Locations under normaloperating conditions.

102

When the storage capacity reaches a Configurable utilization percentage (for example 80 percent), a messageshall be transmitted to the MOMS. Images shall be deleted only after it is confirmed/acknowledged that theimages have been successfully transmitted to the RSS. Any deletion of images shall be automatic, without userintervention, and shall generate a message to be transmitted to the MOMS (Configurable).

103 The ICPS controllers/servers architecture shall have sufficient reliability and/or redundancy such that failure of aprocessor, the communications, board, power supply, disk or other critical unit does not result in loss of imagesand data.

104 In the event communications to the ICPS are lost or any ICPS Hardware becomes non-operational, the ContractorDesign shall ensure that no images and/or data are lost and that all images and associated data are transmitted tothe RSS.

105 The Contractor’s Design shall guarantee transmission of the images and data from the Roadside Tolling System tothe RSS and on to the KTA CSC BOS and shall provide the capability to reconcile images to the transaction data.

106 The Contractor provided RTCS and network architecture shall support the image throughput Requirementsspecified in the Scope of Work and Requirements.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

107 The ICPS shall be capable of transferring images and associated data to the RSS in real-time or in batch modedepending on the ICPS solution and the location of the ALPR/OCR Software. The System shall provide 100 percentreconciliation of all images captured and transferred.

108 The ICPS shall be capable of continuously performing diagnostics and reporting its health to the zone controller orthe MOMS. Loss of communication to any element of the ICPS shall be immediately detected. All health, failureand recovery status messages shall be transmitted and reported to the MOMS.

109 The Contractor shall provide Software tools for verifying the image quality in real-time and adjusting and tuningthe images remotely.

1.2.9.4. Automatic License Plate Recognition (ALPR)/Optical Character Recognition (OCR)

110 The Contractor shall provide an ICPS solution that supports automation, plate type, and primary image selection.

111 The Contractor shall provide ALPR/OCR Software for determining the license plate data (plate number, statejurisdiction and plate type). The ALPR/OCR Software may reside at the RSS level, or the Roadside System level, aslong as it meets the performance and functional Requirements specified in this Scope of Work and Requirements.

112

The System shall correctly identify the state jurisdiction (i.e. state/province), plate type, special characters andstacked characters, and accurately determine the license plate number and provide the result in the requiredKansas Department of Revenue (KDOR) or Department of Motor Vehicles (DMV) format so that the CSC mayprocess without any additional manipulation as required per the Approved ICD. The Contractor shall take intoconsideration the individual state license plate characteristics for the identification of stacked characters, specialtyplates, etc. Attachment 7: Kansas License Plate Guide is being provided as a guide on the specialty plate typesobserved in Kansas, which requires license plate number, license plate state jurisdiction, and plate type to providean accurate ALPR/OCR value.

113

The System shall meet the image processing Performance Requirements specified in this Scope of Work andRequirements. For informational purposes only and based on current violation rates (not current cashcustomers), the license plates for the top twelve (12) states observed on KTA roadways currently are Kansas,Indiana, Texas, Missouri, Illinois, Oklahoma, Colorado, Iowa, Florida, Minnesota, California, and Nebraska.

114 There shall be no backlog in the processing of images for obtaining the license plate data (number, statejurisdiction and plate type) and there shall be server redundancy whereby standby servers are availableimmediately and fully operational in the event of a failure.

115 Any ALPR/OCR Software procured, furnished, and installed under this Contract shall include Software thatenhances and improves the accuracy and efficiency of the ALPR/OCR process.

Authorized Users shall have the ability to configure the Business Rules for auto-processing images wherebyimages identified for auto-processing may be identified to by-pass KTA manual image review. The Business Rulesfor auto-processing to be determined during Design shall include the following criteria:

a) state jurisdiction; b) license plate type; c) confidence level of the license plate number and State;d) vehicle class;e) matching front and rear license plate data; andf) license plate on the error plates list.

117 The RTCS shall associate all images captured for a vehicle as it travels through each of the Tolling Locations on aToll Facility, assign them a unique identifier, and transmit the images to the KTA CSC BOS.

116





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

118

The ICPS shall provide the capability to make available/group all image-based transactions for the vehicle imagebeing reviewed if the vehicle is identified to have driven through other toll plazas on the toll road within aConfigurable period of time before and after the time of the current image-based transaction. This will permitKTA image reviewers to review all images associated with a vehicle and enter the license plate information moreefficiently and accurately.

119

The images identified for the KTA CSC BOS billing and processing shall include, at a minimum, the front and rearoverview image(s) and the associated ROI images. If a front LP is provided as the ROI image on a vehicle withgreater than two axles, the front overview image shall be provided. Other images shall be made available uponrequest. If the vehicle has two rear license plates the ROI from the image that resulted in the highest OCRconfidence shall also be included in accordance with the Approved ICD.

120 The image data associated to each transaction shall be included in the transaction package transmitted to the RSSand then on to the KTA CSC BOS per the Approved ICD.The image data shall include but not be limited to:

a) vehicle identifier data, including grouping information;b) transaction data;c) selected primary image identifier for the fully formed transaction and access to all other associated images;d) license plate data, including license plate number, state jurisdiction and plate type;

e) ALPR/OCR confidence level of the overall license plate number and individual characters (if available);

f) ALPR/OCR confidence level of the state jurisdiction; and g) ALPR/OCR confidence level of the plate type.

122 The ICPS shall provide the capability of detecting image quality degradation in near real-time and generate alarmsthat are reported to MOMS when image quality impacts ALPR/OCR or manual image processing performance.

123 For audit and Maintenance purposes, authorized personnel shall have the capability to view all the images in real-time on any device connected to the RTCS network and verify the ALPR/OCR image processing performance.

1.2.10. Digital Video Audit System (DVAS)

124 The Contractor shall provide an integrated DVAS that provides KTA the capability to investigate lane performanceissues and support KTA in customer dispute resolution.

125 The Contractor shall develop, procure, furnish, and install two or more IP addressable, color video cameras as partof the DVAS at each Toll Zone sufficient to meet the Requirements of this section. The cameras installed shall bethe same at all Toll Zones.

126 Clear, high quality video of each toll lane shall be provided regardless of the ambient lighting and/or weatherconditions at each Tolling Location.

127 Authorized Users shall have the ability to individually setup and configure the cameras, and Configurable settingsshall be available on a per-camera basis.The DVAS shall encompass all Equipment and Software necessary to provide the audit capability described herein,including but not be limited to:

a) digital cameras and any associated lenses, lighting and sensors;b) interface to the zone controllers to capture event data;c) storage media; andd) application to view real-time video and events and playback the information.

129 The DVAS and audit data shall be independent of the transaction data stream provided to the RTCS; however, theDVAS shall be integrated into the Contractor’s System and linked to the transaction to meet the Requirementspecified in this section.

121

128





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

130 The Contractor shall provide Authorized Users the ability to access the DVAS through the RTCS application orthrough a secure application using any KTA authorized workstation connected to KTA System network.

131 The DVAS video and event data shall be available from the Roadway Operations monitoring application andOperations Dashboards to staff when investigating anomalies, and to any Authorized User including auditors andCustomer Service Representatives (CSRs) when reviewing class mismatch transactions and toll disputes.

132 The DVAS shall provide the capability to monitor an overall image of the Toll Zone with the ability to see each laneand the vehicle traveling in that lane, and shall display detailed events for each lane as they occur in real-time. Theevents displayed shall be Configurable by Toll Facility.

133

At a minimum, the DVAS shall display the facility ID, Tolling Location, lane number, transaction number,transaction date and time, Transponder ID, Transponder class, operational mode and the AVDC class. The DVASvideo and data shall be accessible in read-only mode; no changes or alterations to the video or data shall beallowed.

The DVAS screens shall allow the Authorized User to obtain and sort the video/data events through various querycriteria or Configurable report templates finalized during the Design Phase including but not limited to:

a) lane ID; b) vehicle class; c) transaction time; d) payment type; e) transaction time range; f) alarm condition; g) class mismatch condition; h) unusual event conditions; i) operational mode;j) Transponder ID; andk) Transponder status.

135 All detailed data obtained from all subsystems shall be displayed to assist auditors and Maintenance staff with theinvestigation of discrepancies and problems. The DVAS shall perform and display video and data in real-time andshall have the ability to playback events and data.

136

The DVAS shall also have the capacity to record and store up to one-hundred and eighty (180) Calendar Days(Configurable) of video and data to an electronic media for each installed DVAS camera. DVAS video and thecorresponding data (event information and the transaction information) shall be saved together as a unit suchthat when it is moved to a different environment, the video can be replayed with the events being displayed(Configurable) outside the production environment as long as the DVAS replay Software is available.

137 As part of the Design Phase, the Contractor and KTA shall determine the optimum location for the installation ofthe DVAS Equipment to allow for the complete monitoring of each toll lane.

138 The location and number of cameras shall permit the capture of video that allows Authorized Users to identify thevehicle class.

139 The Contractor is responsible for the installation of the DVAS Equipment, including mounting Hardware to thedesignated structure (either toll gantry or separate mounting pole) as well as power and signal cabling betweenthe DVAS Equipment and the storage media.

140 The health of the DVAS shall be monitored and displayed and any problems or failures shall be reported toMOMS.

134





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

141 The DVAS shall be time synchronized to the same source as the zone controllers and interface to the zonecontroller to obtain event data.

142 Identification on the screens shall allow the reviewers to clearly differentiate the lane under review and itsassociated event data.

143 The DVAS shall provide the capability to save the displayed contents of a screen (images and data) andelectronically distribute such information as needed.

144 Controls shall be provided to step forward and backward by frame and display of events shall be synchronized. Alldigitized video and corresponding event data shall be tightly synchronized and stored.

145

The DVAS System shall record a five (5) second looping DVAS video file upon detection of a Wrong-Way Vehicle bythe RTCS AVDC System and the RTCS shall Alert KTA Incident Management Center (KTA IMC) personnel within ten(10) seconds (Configurable) of the vehicle passing through the Toll Zone. The message alert will be prominentlydisplayed on operators’ video wall or monitors.

1.2.11. Hotlist Notification

146 The RTCS shall support the Maintenance and update of a Hotlist that contains Transponder and/or license platenumbers that KTA requires notification on.

147 The Hotlist will be transmitted from the KTA CSC BOS at frequent Configurable increments and when changes tothe list take place.

148 The RTCS or RSS shall provide the capability to Alert authorized personnel if the System detects a Transponderpassing through the Tolling Location that is identified on the Hotlist. The criteria for notification shall include thestatus of the Transponder and presence of the Transponder on the Hotlist.

149 The System shall Alert personnel within ten (10) seconds (Configurable) of the vehicle passing through the TollingLocation if a vehicle on the Hotlist is identified. The Transponder ID and status (if any), and a picture shall beincluded in the Alert.

150 Notification methods shall include but not be limited to text message, email, or system-to-system interface.

151 If a Hotlist notification was successfully transmitted to applicable personnel, the transaction shall have a flagdenoting the transmission of the enforcement notification. This enforcement transmission status shall betransmitted to the KTA CSC BOS.

152 The System shall support the transmission of images (Configurable) to the applicable personnel and shall includethe image of the vehicle and/or the ROI.

1.2.12. Wrong-way Vehicle Notification153 The RTCS shall be able to detect and report vehicles traveling in the wrong direction.

154 The RTCS shall Alert KTA IMC personnel via email and SMS text message within ten (10) seconds (Configurable) ofthe wrong-way vehicle passing through the Toll Zone.

155 The RTCS shall transmit to the KTA IMC a five (5) second looping DVAS video file of the vehicle and the messagealert will be prominently displayed on operators’ video wall or monitors.

156 The RTCS shall interface to an electronic wrong-way vehicle sign (provided by others) located in close proximity(~500 feet) of the Toll Zone to alert a motorist driving the wrong way. The interface to the electronic wrong-wayvehicle sign will be defined during Design.

157 Any wrong-way vehicle transaction shall be transmitted to the KTA CSC BOS with a flag indicating wrong-wayvehicle transaction.

158 The System shall support the transmission of images (Configurable) and shall include the image of the wrong-wayvehicle and the vehicle Region of Interest (ROI).

1.2.13. Zone Controller1.2.13.1. Zone Controller Hardware

159 The Contractor shall Design, procure, furnish and install a zone controller that is capable of supporting theRequirements in this Scope of Work and Requirements.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

160

A fully redundant zone controller shall be Designed, procured, furnished, and installed at each of the Toll Zone asidentified in Attachment 2 and Attachment 3. The zone controller shall be Designed in a redundant configurationwhere there is a single primary zone controller with a “hot standby” secondary zone controller operating inparallel and capable of assuming processing control in the event the primary unit should fail (automatic failover),without requiring human intervention.

161

When any Hardware and/or process on the primary zone controller fails preventing it from processing vehiclesand creating transactions, the secondary zone controller shall assume the functions of the primary zonecontroller. The failover from the primary zone controller to the secondary zone controller shall be transparent tothe rest of the System and shall not require the restart of any subsystems. Only one zone controller at a time shallgenerate revenue transactions.

162 Alarm messages shall be generated and reported to the MOMS when such a failover event occurs. TheContractor’s failover Design shall ensure that there is no loss of revenue or transactions when one of the zonecontrollers fails.

163 The System shall provide Authorized Users the capability to manually and remotely switch the active zonecontroller to and from the primary zone controller to the secondary zone controller. All such events shall berecorded and transmitted to the MOMS.

164

The zone controllers shall be hardened, industrial grade servers and the processor speed and memory shall besufficient to process vehicles in real time to meet the vehicle speed and peak traffic volumes of up to 1,500vehicles per lane, per hour as specified in this Scope of Work and Requirements and as referenced in Attachment1: Future Project Transactions.

165 Storage shall be sized to hold a minimum of thirty (30) Calendar Days of 100 percent of transactions, images andevent data for each lane at the Tolling Location supported by the zone controller.

1.2.13.2. Zone Controller Software

166 The zone controller Software shall interface to the various devices and subsystems for each of the laneconfigurations specified and perform all the functions as described in this Scope of Work and Requirements.

The zone controller located at each of the Tolling Locations shall process all of the data obtained from the othersubsystems and devices as described in this Scope of Work and Requirements to generate a transaction record foreach vehicle passage through the Toll Zone. The zone controller shall:

a) manage the Transponder status list for KTA, all KTA Interoperable agencies, and all National Interoperable Agencies used to validate the status of a Transponder received from the AVI System;b) use the data obtained from the AVI and AVDC systems to assign the Transponder read to the correct vehicle and to frame the vehicle transaction accurately;c) notify the ICPS to capture and process vehicle images in accordance with KTA Business Rules;d) transmit the transaction record to the RSS, including but not limited to the following data: vehicle detection and classification data, Transponder data, Equipment status data, and all other pertinent information regarding the transaction;e) transmit to the MOMS all alarm messages relating to the health of each subsystem, including the health of the primary and secondary (redundant) zone controller. Recovery messages shall also be transmitted and reported; f) vehicle event data and transaction data shall be accessible to the DVAS; andg) transmit to the RSS for further processing all other messages/events in accordance with Approved Interface Control Documents (ICDs).

168 The zone controller Software shall be Configurable and shall be able to support KTA Roadside operational needswithout requiring changes to Software. The Configurable parameters shall be defined and documented during theDesign process. All parameters shall have default values that shall be established during the Design process.

167





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

169 The Contractor shall propose appropriate protocols and data structures to accomplish the communicationsrequired between various peripherals. These protocols and data structures shall be fully detailed and documentedby the Contractor during the Design process and Approved by KTA. Guaranteed transmission protocols shall be used for all messages exchanged between systems including but notlimited to:

a) zone controller; b) ICPS; c) AVI System; d) AVDC System; e) RSS (including Toll Host System and optional Plaza/Facility Server); f) MOMS; g) DVAS; and h) the KTA CSC BOS.

1.2.13.3. Zone Controller Start-Up

171

Upon start-up or initialization, the zone controller shall perform a self-diagnostic test to ensure full SystemOperations. Alarm messages shall be reported for all failure conditions and a notification of the diagnostic checkcompletion shall be displayed on the MOMS monitoring screen. The failure of a critical system shall result in theTolling Location operating under degraded Operations in accordance with Approved KTA Business Rules.

172

The zone controller and the RSS shall together verify that the latest configuration files, Transponder status file,and any other files required to support the lane Operations are present on the zone controller during zonecontroller startup. If the system cannot verify the latest files are present on the zone controller, an alert shall begenerated and sent to MOMS.

1.2.13.4. Zone Operations173 The RTCS shall support the Roadway operation as specified in Section 1.3.

174 In the event of a power interruption the zone controller shall open in the operational mode it was in before it waspowered down.

175 Authorized Users shall have the ability (local and remote) to configure the next operating mode and to gracefullyshutdown the zone controller. Each time a mode change is requested an Alert message shall be sent to theMOMS.

176 When a lane is operating in a mode other than normal open mode (to be finalized during Design), an Alert shall begenerated and sent to MOMS at regular (Configurable) intervals.

177 The RTCS shall support various modes of operation that are managed and initiated by Authorized Users throughthe Toll Host.

178

Transactions shall be processed according to different Business Rules either at the Roadside Systems level or theRSS level based on the mode of operation and the facility type. The Contractor shall be responsible for ensuringthat the AVI and image-based transactions are processed according to KTA Business Rules and transmittedcorrectly to the RSS and then to the KTA CSC BOS.The RTCS shall support the following modes of Operations:

a) Open Mode: All transactions shall be processed normally in an open mode;

b) Closed Mode: Invoked when the lane is closed for toll collection. The System shall use a virtual user ID (a special user ID specifically designed for tracking transactions in certain modes) or an alternative method for tracking vehicles and activity in the closed lanes. The lane shall process transactions similar to an open lane and support the creation of automatic shifts (for transaction reconciliation purposes) if applicable.

170





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

c) Maintenance Mode: Invoked by Maintenance technicians to service the lanes. Transactions created in Maintenance mode are processed as normal transactions but are identified as Maintenance mode transactions and transmitted to the RSS. Transactions that occur during Maintenance mode are not reported as traffic or revenue transactions.

d) Emergency Mode: Invoked by Authorized User either by lane, Toll Zone, or Tolling Location where tolls are suspended for the selected duration for all payment types. Transactions created during emergency mode shall be identified as emergency mode transactions and shall be transmitted to the RSS and to the KTA CSC BOS for reporting processed in accordance with KTA Business Rules to be determined during the Design Phase.

1.2.13.5. Transaction Processing

180 The zone controller shall detect, classify, and frame vehicles, assign the Transponder accurately to the correctvehicle and capture and process the image of the correct vehicle in accordance with KTA Business Rules and thePerformance Requirements specified in this Scope of Work and Requirements.

181 The zone controller shall incorporate logic that will prevent the incorrect assignment of Transponder reads fromvehicles driving in the adjacent general traffic lanes and in the opposite direction of travel. The detailed transaction processing rules shall be defined and finalized during the Design Phase; however, thefollowing basic rules shall apply:

a) The zone controller shall properly associate multiple Transponder reads reported by the AVI System to the vehicle and report the transaction to the RSS;b) any compatible, but non-interoperable Transponder reads shall be reported to the RSS;

c) a minimum of one revenue bearing transaction shall be created for each vehicle that travels through the Toll Zone and the zone controller shall ensure that the transaction is complete prior to transmitting it;

d) the zone controller shall be able to accurately identify, process, and track multiple vehicles in the Toll Zone;

e) the zone controller shall ensure that duplicate Transponder transactions (same Transponder ID) are not reported from the same lane or Tolling Location within a Configurable period of time or consecutively;

f) buffered Transponder reads that are transmitted to the zone controller shall not be assigned to a vehicle by the zone controller but shall be flagged and reported to the RSS for further processing and vehicle assignment; g) the zone controller shall automatically synchronize with the various subsystems to ensure the events in the lane correspond to the transaction generated, andh) the System shall incorporate self-correcting logic to adjust for lane anomalies and event synchronization issues.

The transaction message details shall be defined and finalized during the Design Phase; however, the followingbasic rules shall apply:

a) the RSS shall transmit to the KTA CSC BOS the fully formed and verified image and AVI transactions for processing, reporting, and reconciliation; b) the transaction message shall contain the data required by the KTA CSC BOS to process the Transponder and Image-Based Transactions;c) the transaction message shall contain all data contained in the KTA, CUSIOP, and the National Interoperable file specifications if applicable to the specific Tolling Location; d) each transaction shall contain, and be reported with, various classification data, including AVDC class, Transponder class, and default class;

179

182

183





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

e) each transaction shall contain, and be reported with, various event times, including ‘vehicle entry’ time; ‘ICPS trigger’ time; ICPS capture time; ‘Transponder read’ time; and ‘vehicle exit’ time that shall allow Transponder reads, images and transaction to be associated correctly with the vehicle;

f) each transaction shall contain the toll amount due (based on when the vehicle passed under the Cashless Toll Zone and the toll amount collected (based on the KTA CSC BOS posting disposition); and

g) the System shall assign a lane number to each transaction and report the lane in which the vehicle was detected.

1.2.13.6. Transponder Mapped Class

184 The System shall capture the raw Transponder class obtained from the Transponder data (if available) and mapthat to the KTA mapped class for each of the toll facilities.

185 The System shall retain the raw Transponder class and include that in the transaction data along with the mappedclass for each Toll Facility.

186 If a Transponder has a raw Transponder class that is not mapped to the KTA class then the System shall apply theclass as defined by the Business Rules.

1.2.13.7. Revenue Vehicle Class (KTA Class)

187 The assignment of the revenue vehicle class in normal Operations and in degraded mode of Operations shall be inaccordance with the KTA Business Rules. If no classification data is obtained, a Configurable default revenue classshall be assigned to the transaction and the transaction shall be flagged.

188 The revenue vehicle class shall be used to determine the toll rate amount for a transaction as defined by the KTABusiness Rules. Flags in the transaction shall identify which class was used as the revenue vehicle class.

189 The System shall support axle-based classification where the vehicle class is based on the number of axles on theground when the vehicle drives through the Toll Zone and the toll assessed is based on the number of axles.

190 The System shall have the capability to cap the maximum and minimum (Configurable) axles and class and tocharge a set toll rate per additional axle count.

191

Transactions shall include the AVDC class, raw KTA Interoperable Partner Transponder class (if applicable),mapped Interoperable Partner Transponder class (if applicable) and revenue vehicle class. The revenue vehicleclass assigned in accordance with KTA Business Rules shall be used to determine the toll amount transmitted tothe KTA CSC BOS.

1.2.13.8. Toll Rate DeterminationThe toll rate determination can be performed by the RTCS or the RSS. The toll rate assessed for a vehicle whichtravels through the Tolling Location shall be based on multiple factors, including:

192 The System shall support the determination of the toll rate at the Toll Zone and the RSS.

193

Tolls shall be assessed using the toll rates and schedules established for each Toll Zone. The System shall supportthe toll rate and the KTA Vehicle Classification Structure based on the Tolling Location and facility. The initial tollrates shall be defined during System Design and shall be Configurable to support periodic rate adjustments asApproved by KTA.

194 The toll rate shall be determined in accordance with KTA Business Rules and will vary by vehicle class andpayment type.

195 The System shall have a Configurable default toll rate for each Toll Zone to be used in the event classification datais not available.

196 The System shall support the assessment of toll based on payment type (e.g. AVI, image-based, or non-revenue),vehicle class, lane health, Agency code, and location based on KTA Business Rules.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

197

It is currently envisioned that the KTA CSC BOS will process the Contractor provided image-based transactions andconvert them to I-Tolls, if applicable. The Contractor shall process the transaction dispositions from the KTA CSCBOS, including any adjustment of toll rate for converted I-Toll transactions. Vehicle classification adjustmentsshall also be processed.

198 Home (KTA-issued) non-revenue Transponders shall be charged $0.00 (Configurable) toll rate but Away non-revenue Transponders shall be charged the normal toll rate based on vehicle class and location.

199 Transactions shall be flagged if the AVDC System is operating in a degraded mode.

200 The System shall support the assessment of tolls based on the toll rate schedule and toll rate in effect at the timeof the vehicle passage through the Tolling Location.

201 The System shall support day of the week; weekend/weekday and Holiday toll schedules. 1.2.13.9. Saving of Images202 Images shall be saved for all vehicles under all conditions in accordance with KTA Business Rules.

203 Images shall be captured for all transactions and saved according to the data retention policies described in thisContract.

204 Images saved during ICPS loss of communication event shall be flagged and subsequently matched with thecorrect transaction data when communications with the zone controller resumes. This matching can occur at theRSS, but shall take place in a manner that does not interfere with or degrade real time zone controller Operations.

205

If the AVDC System is not operational but the ICPS trigger is functioning, images shall be saved such that all non-valid Transponder transactions that occur during the AVDC malfunction can be subsequently pursued forcollection. Sufficient data shall be provided in the transactions to allow the RSSs to process such transactions sothat customers are not charged in error when lane operation is degraded.

1.2.13.10. Configuration Files

206 All parameters and settings required to run the zone controller application shall be maintained in configurationfiles. Access to configuration files required to support the zone controller Operations shall be controlled andaccess to these files shall be limited to authorized personnel.

207 The configuration files shall be maintained at the RSS for configuration and version control. All zone controllersshall have default configuration files that shall allow the lane to start-up automatically.

208

Authorized personnel shall be able to make changes to parameters and settings that are defined as Configurablein this Scope of Work and Requirements and in the Approved Design documents. Authorized personnel shall beable to make changes to the configuration files in the field. Changes to configuration files shall be recorded in theMOMS. All changes made to the configuration files in the field shall be synchronized to the master configurationfile that is maintained at the RSS.

209 Each zone controller shall automatically back up its critical configuration files to a back-up server to be used torebuild the master drive in the event of hard disk failures.

1.2.13.11. Zone Controller Interfaces – General Requirements

210 The zone controller shall interface to various devices and subsystems to transmit and obtain data and synchronizethe time.

211 The zone controller shall provide checks on all data it receives from each of the devices and subsystems itinterfaces to and generate alarm messages that are reported to the MOMS.

1.2.13.12. Interface to AVI System

212 The zone controller shall interface with the Contractor-proposed AVI System and transmit all data received fromthe AVI System to the RSS.

213 The zone controller shall have the capability to interface to multiple AVI System vendors and multi-protocolreader products. These AVI interfaces include Kapsch, Neology, STAR Systems, and TransCore multi-protocolreaders.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

1.2.13.13. Interface to AVDC System

214

The zone controller shall interface with the AVDC System to obtain vehicle events that shall permit accuratedetection, classification, tracking and processing of vehicles. Vehicle dimensions, vehicle characteristics and speedinformation shall also be obtained from the AVDC System and reported as part of the vehicle transaction datareported to the RSS for potential use.

1.2.13.14. Interface to ICPS

215

The zone controller shall interface with the ICPS to capture and process images of vehicles in accordance with KTABusiness Rules to be developed during the Design Phase. The vehicle data, ALPR/OCR results and images obtainedfrom the ICPS shall be transmitted to the RSS to support KTA image-based transactions processing Requirementsand the KTA CSC BOS operations Requirements.

1.2.13.15. Interface to DVAS

216 The zone controller shall interface with the DVAS to transmit event data for display on the DVAS. The event datashall be based on the facility type and shall include Transponder reads, ICPS data, and AVDC messages received asthe vehicle travels through the lane.

1.2.13.16. Interface to UPS

217 The zone controller shall interface with the KTA-provided UPS to monitor the UPS performance. The MOMS shalldetect the status of the UPS and Alert technicians when the System is on UPS.

1.2.13.17. Interface to RSS

218 The zone controller shall interface with the RSS to transmit lane data and receive files, commands, messages anddata required for lane Operations. Error detections and data validation checks shall be instituted at both systemsto ensure incorrect or corrupt data is detected and is not inserted into the System.

219 The RTCS shall institute automated methods to determine loss of communications between the zone controllerand the RSS and any failure detected shall be reported to MOMS.

220 Receipt of all files and data shall be acknowledged and any failures in the transmission or detection of data errorsshall be reported to the MOMS.

221 The Contractor shall provide an automated means of synchronizing the zone controller and RSS messages in theevent the zone controllers are replaced, if communications are down, or if data on the zone controller is notretrievable due to a catastrophic failure.

1.2.13.18. Transmitting Data

222

All messages generated at the zone controllers shall be transmitted to the RSS (e.g., Facility Server (if provided) orToll Host System) in real-time using a transport mechanism that performs error detection and correction toguarantee data transmission. All messages shall be uniquely identified and validated at the RSS to ensure thereare no missing or duplicate messages.

223 The System shall support exception handling in accordance with the KTA Business Rules Approved during theDesign Phase. Alarms shall be generated and reported to the MOMS for all exceptions/errors.

224 All failed transactions and exceptions shall be identified and reported.

225 Failure of transmission of data to the RSS shall result in the generation and transmission of alarm message to theMOMS.

226 All messages shall be confirmed as received by the RSS before they are flagged for write-over. In the event ofcommunication failures the messages shall be stored on the zone controller until successful transmission iscomplete and verified.

The zone controller shall transmit to the RSS all data, including but not limited to those identified below:

a) all transaction messages generated in the lanes;b) all alarm and status messages generated in the lanes;227





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

c) all lane operational, communication status and self-health messages;d) all events generated in the lanes that are displayed on the Roadway Operations monitoring screen or are required at the RSS; and e) all events required by the DVAS for real-time review or playback.

1.2.13.19. Receiving Data

228

The zone controller shall support the Transponder Validation List (TVL) for KTA and CUSIOP (currentlyapproximately 30 million transponders) and any other Interoperable Agency lists and shall have the capability tosupport every Interoperable Agency and its assigned Transponder number range as described in the NationalInteroperability specifications and NIOP Agencies and Tag IDs as shown in Attachment 13 - NIOP ICD - Appendix C.

229 The zone controller shall accept comprehensive (complete list once a day) and incremental (changes updated on aConfigurable interval, but not more frequently than every sixty (60) minutes) TVL in accordance with theestablished Business Rules and shall activate the lists upon receipt after validation of the files.

230 The Contractor shall use an effective Design to transmit the files (compress, encode, etc.), store the files and usethe files such that the new list is available at the zone controllers within ten (10) minutes of the RSS receiving thenew list. The format of the file shall be finalized during the Design Phase.

231 The toll rates, toll schedules and the effective date/time shall be downloaded to the zone controller and new tollrates initiated when the toll rate changes.

232 All configuration files and tables needed to support the lane Operations shall be downloaded to the zonecontrollers from the RSS upon confirmed change or at scheduled intervals and activated as required. Versions ofthe Configurable files on each zone controller shall be maintained, tracked, and recorded.

233 All zone controller Software shall be downloaded to the zone controllers from the RSS and versions on each zonecontroller shall be maintained, tracked, and recorded.The Roadside System shall institute checks whereby it detects issues with the data it receives from the RSSincluding but not limited to:

a) incorrect versions of the data received;b) corrupted data received; and c) missing files when a file was expected.

235 The System shall support exception handling in accordance with the KTA Business Rules Approved during theDesign Phase. Alarms shall be generated and reported to the MOMS for all exceptions/errors.

1.2.13.20. Monitor All Lane Equipment for Device Status

236 Each zone controller shall self-monitor the System health of internal components and all associated in-laneEquipment devices for status. All RTCS components, including AVI System, AVDC System and ICPS shall becontinuously polled for status. The health of some digital devices shall be inferred from events.

237

The System shall generate a recovery message and restore its operational status if a device recovers afterreporting a failure. Recovery messages shall be recorded against the original failure work order, shall be reportedthrough the MOMS, and shall be available to authorized staff. Recovery messages shall not close the associatedfailure/work order but shall serve as supporting evidence of an Equipment recovery.

238 All alarm, health, and recovery messages shall be transmitted and reported to the MOMS.

239 If communications from the zone controller to any RSS is unavailable, an alarm message shall be generated andreported to the MOMS.

240 If the lane is operating in any mode other than normal open mode an Alert message shall be generated atConfigurable intervals and reported to the MOMS.

227

234





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

1.2.13.21. Diagnostics and Equipment Malfunction

241

The zone controller Software shall execute periodic diagnostic checks on internal processes, the in-laneEquipment and interfaces. Intelligent peripheral devices shall be interrogated for device status on a regular basis.A device's failure to respond to a status inquiry after a Configurable number of retries shall be regarded by thezone controller Software as an Equipment failure. All failures shall be detected and alarms generated and shall bereported to the MOMS.

242

Diagnostic and self-checks shall take place in all modes of lane operation and the results shall be placed in theassociated zone controller's consolidated log and easily accessible to the technicians. Sanity checks for faultconditions and validations shall be incorporated into the System. Detection of such conditions shall be reported tothe MOMS.

243

Degraded modes of operation shall be supported based on KTA Business Rules developed during the Designprocess, and Approved by KTA. The Contractor shall ensure the RTCS continues to operate without loss of revenueor visible impact to the customer in the event that some components of the RTCS fail and degraded modeOperations occur.

1.2.13.22. Stand-alone Mode of Operation

244 The zone controller shall operate in a stand-alone mode for a minimum of thirty (30) Calendar Days ifcommunications to the RSS is down. When operating in stand-alone mode, the last files downloaded from the RSSshall be used for processing vehicles.

245

The zone controller shall have an available data port to permit on-site manual uploading of Software, TVL, orother pertinent data required for continued operation until communications with the RSS is re-established.Devices utilized to download the TVL to the lanes shall have the capability of synchronizing the current versionswhereby a new TVL is updated on the device within an hour.

246 The System shall provide the capability for Authorized Users to download transactions from the zone controllerand transfer such transactions to the RSS, and from the RSS to the KTA CSC BOS.

247 The System shall provide the capability for Authorized Users to download event/transaction data for manual andstand-alone playback of the DVAS.

248 Upon re-establishing communications with the RSS all back-logged messages, including manually transferredmessages shall be transmitted and synchronized to the RSS without affecting the real time Operations ordegrading the lane Operations.

249 Upon re-establishment of communications and successful transmission of all messages, a recovery message shallbe transmitted to the MOMS.

1.2.14. Critical Environmental Monitoring System (CEMS)The Contractor shall provide a CEMS, which shall consist of an environmental monitoring unit for the HVAC andother environmental conditions at each PoP enclosure and shall include:

a) HVAC status (On/Off);b) Temperature;c) Humidity;d) Utility power;e) Generator status (On/Off);f) Generator propane fuel level;g) Automatic Transfer Switch (ATS) transfer monitor;h) UPS power;i) Smoke detector; andj) Carbon monoxide detector.

251 The CEMS shall provide a useful variety of historical reports and trends for the monitored conditions.

252 The CEMS shall interface with MOMS to generate and transmit alarms, Alerts, recovery messages and operationalstatus.

250





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

253 The CEMS shall be accessible from the KTA HQ and KTA IMC via secure remote access. 1.2.15. Uninterruptible Power Supply (UPS)254 All RTCS Hardware and Equipment shall be on UPS. The UPS shall be supplied by KTA.

255 KTA shall furnish and install an automatic transfer switch (ATS) at each PoP. The Contractor shall interface withthe ATS and the Contractor-provided smart Power Distribution Units (PDUs) to manage the Roadside powerdistribution. Maintenance technicians shall have remote access to manage power to critical devices.

256 Failure of the UPS shall cause the ATS to switch to raw utility power and provide power to the roadside tollingEquipment, allowing toll collection to continue.

257 The Contractor shall furnish and install an electronic interface to the UPS to monitor its UPS performance for alltoll facilities. The MOMS shall detect the status of the UPS and Alert technicians when the System is on UPS.

258 Software drivers shall be developed, furnished, and installed to acquire, display, store and report all parametersprovided as outputs from the UPS.

259 The UPS shall support the RTCS at each Tolling Location for a minimum of one (1) hour. When there is loss ofpower to the Tolling Location, the power will switch to the generator power source.

260 When utility power is restored and Hardware/Equipment is no longer on the UPS a notification shall be reportedto the MOMS.

1.3. Roadside Tolling Facility Server

The provision of a facility server is optional but if the Contractor’s solution includes a facility server, then theRequirements in this section shall be met. The Contractor has the option to use the facility server as an imageserver as long as the Design complies with the Requirements of the Scope of Work and Requirements.

261 The Contractor shall provide one or more facility servers located at a tolling point if it is deemed necessary tomeet the Requirements specified in this Scope of Work and Requirements. A facility server or set of servers cansupport multiple Toll Zones.

The Contractor shall furnish and install a complete Hardware configuration for each facility server to support theavailability, redundancy and Performance Requirements of this Contract including but not limited to:

a) multiple processors;b) dual, redundant, hot-swappable power supplies;c) fault tolerant (RAID) storage devices; and d) backup library.

263 The Hardware solution shall provide high-speed connectivity between all storage, database, application, reportingservers, and backup systems.

264 The facility server shall interface to the zone controller and shall serve as a store and forward server fortransactions and messages.

265 Each facility server shall communicate with the primary and secondary RSS.

266 Each facility server shall be capable of storing transactions and images (if used as a local image server) from the in-lane subsystems for a period of minimum sixty (60) Calendar Days, in the event of a communications failure.

267 The facility server shall be capable of operating in a stand-alone mode for a minimum of sixty (60) Calendar Days ifcommunications to the RSS are down. When operating in stand-alone mode, the last files downloaded from theRSS shall be used for processing vehicles.

262





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

268

The facility server shall have an available data port to permit on-site manual uploading of Software, TVL, or otherpertinent data required for continued lane operation until communications with the RSS are re-established.Devices utilized to download the TVL and rate tables (if applicable) to the facility server shall have the capability ofsynchronizing the current versions whereby a new TVL is updated on the device within an hour of receipt.

269 The System shall provide the capability for Authorized Users to download transactions from the facility server andtransfer such transactions to the RSS.

270 Upon re-establishing communications with the RSS all back-logged messages, including manually transferredmessages, shall be flagged and transmitted to the RSS without affecting the real time Operations or degrading thelane Operations.

271 Upon re-establishment of communications and successful transmission of all messages, a recovery message shallbe transmitted to the MOMS.

272 Failure of any component of the facility server shall be detected and reported to the MOMS. 1.4. Roadway Pavement, Toll Gantry, and PoP Equipment Building Design Support1.4.1. General Design Requirements

273 At the tolling points the Contractor shall install the Roadside Toll Collection System on the infrastructure providedby the KTA as identified further in Attachment 8: Implementation Responsibility Matrix.

274

The Contractor shall work with KTA and provide input into the civil Design and/or construction schedule, andinput for all civil construction work to be performed by others on the Project, including toll gantry; PoP buildings;roadway/pavement, and conduit relative to the aspects that integrate with the Design and installation of theRTCS.

275 The Contractor shall cooperate and provide support as needed to the civil design and construction efforts. Duringcivil design, Contractor support is anticipated to include responses to information requests for clarification onproposed Designs as well as actively reviewing the civil plans and drawings.

276

During construction, KTA will provide shop drawings of the Cashless Tolling Zone infrastructure to the Contractorand the Contractor shall utilize the shop drawings or similar within the context of the toll System functional andPerformance Requirements. Sample shop drawings for the existing ORT gantry structures are provided inAttachment 4: ORT Gantry Shop Drawings.

277 During installation, the Contractor shall provide verification and approval of toll System related elements that KTAis responsible for installing.

278

Upon approval of shop drawings or similar Design elements by the Contractor within the context of Systemfunction and performance, Contractor shall assume responsibility for those elements to the extent that if the civilwork is installed as Designed and does not meet the Performance Requirements of this Scope of Work andRequirements, the Contractor shall be responsible for the costs of redesign, civil rework, and additionalEquipment costs as further set forth in the Contract.

1.4.2. Toll Gantry

279 The Contractor’s Equipment mounting and installation Design for the toll collection Equipment shall take intoconsideration its Maintenance and lane closure constraints.

280

The Contractor shall coordinate in-lane Equipment Design, installation specifications, structural Requirements anddrawings for mounting the Equipment to the overhead toll gantry at each Tolling Location as it relates to theContractor’s Equipment Requirements to KTA, including but not limited to Equipment mounting locations andinstallation instructions for conduit; junction box; electrical Requirements; wind load; Equipment load and powercalculations; deflection and vibration limits for the various tolling Equipment, as well as Contractor Requirementsrelated to special electrical grounding, and isolated circuit integrity by Equipment.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

281 The Contractor shall also review and agree (not certify) to all aspects of toll gantry design drawings submitted byKTA that are related to the toll System Equipment required to meet the Requirements of this Scope of Work andRequirements.

282 The Contractor shall be responsible for all necessary mounting Hardware required to install the toll Equipment oneach gantry at each lane as specified in this Scope of Work and Requirements and shall ensure installation is incompliance with KTA specifications.

283 The Contractor shall be responsible for all Equipment installations, terminations, and connections of Equipmentlocated on the overhead gantry and for connecting such Equipment to the electronics in the PoP roadsideEquipment buildings.

1.4.3. PoP Equipment BuildingOn Cashless Tolling Facilities, a PoP Equipment building with external generator, ATS, UPS, utility power, WANdemark, and HVAC will be provided by KTA at each Tolling Location.

284

A 12’-0”L x 8’-0”W x 9’-0”H prefabricated building will be supplied and installed by KTA and will include HVAC,power, and overhead cable trays. The PoP Equipment building shall house the RTCS Equipment provided by theContractor. All RTCS electronics, devices, servers and associated communications Equipment shall be installed inthe Equipment racks and enclosures. The Contractor shall provide the rack space Requirements to KTA for eachPoP Equipment building at each Tolling Location.

285 The Contractor shall provide detailed drawings of Equipment rack space layout for KTA review/Approval(verification) for consistency of PoP Equipment building Design.

286 The Contractor shall install racks and enclosures within the PoP buildings in accordance with applicable Kansasstate building codes.

287

The Contractor shall install temperature and humidity sensors in the PoP buildings that monitor the temperatureand humidity in those environments. In addition, HVAC status, UPS status, and utility power status shall bemonitored. Alarm messages shall be generated and reported to MOMS when the condition exceeds aConfigurable threshold. The alarm shall be generated at every Configurable interval until the condition falls belowthe Configurable threshold.

288

KTA generally follows Kansas Department of Transportation (KDOT) construction practices. The Contractor shalladhere to the latest version of the KDOT Roadway Standard Drawings and KDOT Standard Specifications: https://kart.ksdot.org/StandardDrawings/Default.aspx https://www.ksdot.org/bureaus/burConsMain/specprov/specifications.asp

289 The Contractor shall review and comment on all aspects of PoP Equipment building Design drawings; powerspecifications, electrical, cabling, and conduit Design; circuit breaker and switches; and grounding Designsubmitted by KTA that are related to the RTCS Equipment.

290 KTA will procure, furnish, and install the conduits between the PoP and the demarcation point on the toll gantry.The Contractor shall procure, furnish and install any conduit required from the demarcation point to theEquipment and between the various components on the toll gantry.

291 The Contractor shall procure, furnish, and install the cables necessary for terminating and connecting the RTCSEquipment on the toll gantry to the electronics in the PoP Equipment building. Cable lengths shall includesufficient service loops to facilitate Maintenance.

292 The Contractor shall procure, furnish, and install any required RTCS Equipment racks in the toll PoP Equipmentbuilding (provided by others).





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

293

KTA is responsible for the RTCS WAN communications. KTA may upgrade the WAN network during theImplementation Phase of the Project. The RTCS network and communications Design must be Approved by KTAand shall conform to KTA IT Communication & Security Policies. All networking Equipment at the toll PoPEquipment building (except for the KTA-provided WAN demark) shall be provided by the Contractor. Theschematic of the current WAN network is shown in Attachment 10: KTA Network Topology.

294 The Contractor shall allocate a range of IP v4 Class C addresses and all networking addressing will be coordinatedwith the KTA. The Contractor provided LAN Equipment shall be capable of supporting IP v6 addresses.

1.4.4. Roadway Pavement

295

During the Design Phase the Contractor shall provide the in-pavement sensor Requirements to KTA, if suchsensors are to be used. The following pavement design information is available for the Kansas Turnpike: Surface course: 12” Concrete Pavement (Uniform)(AE)(Plain)(Macro Fiber Reinforced)

296 The Contractor shall be responsible for the Design and installation of all elements of the RTCS that is applied on orembedded into the pavement to achieve the required System Performance.

297 The Contractor shall coordinate with KTA for the installation of the sensors in the lanes. The location and Designof the pull boxes shall minimize the impact of Maintenance activities on the effected lane.

298 The Contractor shall be responsible for any roadway pavement failure directly caused by the installation of in-pavement sensors for the Contract Term.

1.4.5. Communications

299 KTA will provide, terminate, and test the fiber connections from PoP to PoP (the WAN). KTA is responsible for allnetwork Equipment/switching for the WAN. The Contractor shall be responsible for all elements of the LAN. KTAis responsible for WAN connections to the KTA CSC BOS.

300

Network monitoring Software shall be procured, furnished, and installed on the RSS servers to monitor theSystem network status and communications, including the connection to the KTA CSC BOS. All network alarmsshall be reported to the MOMS. The Software tool shall utilize the Simple Network Management Protocol (SNMP)to poll devices real time for status where possible.

301 If communications to any element of the RTCS is down an alarm shall be generated and reported to MOMS.

302 The Contractor shall provide network security at the RSS locations and shall comply with the KTA Security Policy.

303

The LAN within a toll Equipment building shall be connected by CAT6 (or higher) cabling. The LAN connectionsfrom the PoP to the roadside Equipment may either be CAT6 or multi-mode fiber-optic (MMFO) cable accordingto the Contractor's Design. The WAN physical connectivity between the toll PoP Equipment buildings within theroadside corridors shall be provided by KTA. KTA will be responsible for providing and obtaining the WANconnectivity from any primary or secondary Toll Host locations to the KTA CSC BOS.

304 The Roadside System at the Toll Zones shall be connected and communicate to the primary and secondary RSS.

305 The Contractor shall procure, furnish, and install all required communication Equipment at the toll PoP Equipmentbuilding to support the RTCS LAN. All LAN communications Equipment procured, furnished, and installed underthis Contract shall be able to communicate with the KTA communications Equipment.

306 The Contractor shall coordinate with KTA regarding demarcation points between the on-site fiber network andInternet Service Providers (ISPs). Once network Design is finalized, Contractor shall certify in writing that networkDesign meets all RTCS needs.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

307 The Contractor shall install the secondary RSS at the KTA backup data center in Topeka, Kansas. KTA is responsiblefor the connectivity from this secondary location to the KTA CSC BOS.

308 The Contractor shall work with KTA in Designing the network communication interfaces between the RoadsideSystems, the RSS (including optional Facility Servers and Toll Host Systems, MOMS, and DVAS) and the KTA CSCBOS.

1.4.6. Utility PowerUtility power will be made available to the Contractor at the PoP Equipment building at the Toll Zones.

1.4.7. Generators

309 Authority-provided generators shall be used and the Contractor shall install the electronics that allow theRoadway Systems to communicate to the generator.

310 Software drivers shall be developed, furnished, and installed by the Contractor to acquire, display, store andreport all parameters provided as outputs from the generator.

311 The System shall detect the switch to generator power and report the Alert to the MOMS.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




2. ROADWAY SUPPORT SYSTEM (RSS) – FUNCTIONAL REQUIREMENTS2.1. Roadway Support System (RSS) – General Requirements

312 The Contractor’s central processing system architecture shall include a fully redundant highly available primaryand secondary RSS that meets the functional and Performance Requirements of the Scope of Work andRequirements and is accessible to Authorized Users of the KTA System network.

313 The functions of the Roadside Tolling Facility Server, Toll Host System, Central Image Servers (if provided), DVASand the MOMS shall be part of the RSS.

314 The RSS shall support Cashless Tolling facilities. 315 The toll collection process shall be administered and controlled by RSS provided by the Contractor.

316 The Contractor shall procure, furnish, and install all servers, storage and communications Hardware needed tosupport the Software that meets KTA RTCS Requirements.

317 The Contractor shall install any on-premise primary RSS at the KTA Headquarters Building in Wichita, Kansas.

318 The Contractor shall install any on-premise secondary RSS at the KTA backup data center in Topeka, Kansas.

319 The Contractor shall not incorporate any cloud computing or cloud storage in the RTCS Design or Implementationwithout KTA Approval.

320 The primary and secondary RSS configuration shall meet the Performance and Disaster Recovery Requirements ofthe Contract guaranteeing availability as identified in Section 8.

321 The secondary RSS shall be configured as a “hot stand-by” in an active-active state to allow continuous Operationsin the event of a failure of the primary RSS.

322 The secondary RSS environment shall mirror the primary System in all Hardware and Software configurations, bekept up to date and be capable of performing all functions of the primary RSS as described in this Scope of Workand Requirements.

323 Unless otherwise noted, all Hardware and Software procured under this Scope of Work and Requirements shall beconfirmed to be the latest model and version at the time of purchase.

324

All computers, servers and Hardware procured, furnished, and installed under this Contract shall have the mostcurrent and up-to-date virus, firewall, spam protection and other security Software that protects from virusattacks, unauthorized intrusions and unauthorized access. Virus protection and other Software shall automaticallyobtain Updates according to a recommended (Configurable) Maintenance schedule.

325

Per Attachment 6: KTA Information Security Overview and as applicable, all computers, servers and Hardwareshall automatically detect virus protection and security Updates according to a recommended (Configurable)Maintenance schedule and generate an Alert that is reported to MOMS. Virus protection and security Updates toworkstations shall be automatic but Updates to servers shall be scheduled upon KTA Approval.

326 The System shall detect intrusion attempts and prevent all unauthorized access and intrusions at all levels andreport such events to the MOMS. Any intrusion, compromise or breach must be reported to KTA IT Securityimmediately once detected.

327 A high level of redundancy shall be built into the RSS to support high availability Requirements.The RSS shall support the following general functions:

a) communicate with all the zone controllers in receiving transactions, alarms and other messages and transmitting TVLs, toll rate schedules, and configuration files as defined during System Detail Design Phase;

No. Requirements





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

b) provide real-time Roadway Operations monitoring screens and Dashboards to assist Maintenance and supervisory staff in observing transaction and event data in real-time, including reviewing DVAS image/video and data through these screens;c) provide the ability to remotely operate and control the lanes through real time screens;d) perform transaction processing and toll rate determination based on the transaction type and vehicle class.e) interface with the KTA CSC BOS per the Approved ICD to transmit images, transaction messages for further processing and toll rate schedules and toll rate data and receive TVL, and transaction processing disposition results;f) process I-Toll dispositions for image-based transactions which were converted to I-Tolls at the KTA CSC BOS for Accounts in good standing, including the adjustment of toll rates posted per the Approved Business Rules;g) perform Maintenance management functions of the System, including alarm notification and tracking, Equipment inventory, Maintenance history and other Maintenance related functions, incorporated into the MOMS;h) provide an independent audit of successful receipt of all transactions from the zone controllers to the RSS;i) provide various management reports that assess the operational performance of the System and transaction reconciliation reports as determined by KTA during Design.j) communicate with facility servers (if provided) in receiving transaction, alarm and other messages and transmitting TVLs, toll rates, and Hotlist notifications;k) communicate with the applicable image server(s) for tracking and reconciliation image transmission and transfer status;l) provide the capability to manage toll rates and schedules and transmit the toll rates and schedules to the zone controllers and the KTA CSC BOS;m) provide the capability to enter or obtain employee information defined in the Design Phase such as employee ID, role and access privileges from Active Directory.

2.1.1. Roadway Support System (RSS) Hardware and Third-party Products

The Work under this section shall include all labor, materi-als, and support Services to complete the Design;fabrication; integra-tion; packaging; delivery; testing, and Acceptance of the primary and redundant RSS Hardwareand third-party Software in accordance with the Requirements of this Scope of Work and Requirements.

329 KTA shall have ownership of all Hardware, third-party Software and firmware procured, developed, furnished, andinstalled as part of the RSS.

330

The Contractor is responsible for obtaining all required licenses in the name of KTA. All licenses and media shall beprovided to KTA for all Hardware, third-party Software and firmware. The Contractor shall retain authorizedcopies (backups) for all Software media to use for periodic System Maintenance, Upgrades, or restore, asrequired.

The Contractor shall furnish and install a complete, fully redundant, RSS Hardware configuration needed tosupport the redundancy and Performance Requirements of this Contract, including but not limited to:

a) multi-processors;b) dual, redundant, hot-swappable power supplies;c) storage devices; andd) backup library.

328

331





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

332 The RSS Hardware solution shall provide high-speed connectivity between all storage, databases, servers, andbackup systems. The Hardware solution shall be of high-quality to minimize HDD failures and shall provide forstorage expansion and Upgrades.

333 The System Design and implementation shall ensure the RTCS continues to operate without data loss even if anyunit of the server configuration fails.

334 The Contractor shall provide a test environment that is independent and separate of the production environmentto support testing, including new releases.

335

All components, supplies, Software and materials furnished under this Contract shall be new, COTS and field-proven, and in revenue Operations for two (2) years. KTA is open to innovative solutions for this delivery;therefore, any non-compliance with this Requirement shall be clearly identified in the Requirements ConformanceMatrix.

336 The RSS server configuration, including all major Hardware elements, shall be of the latest Design and incorporatestandard commercial products currently in production.

337 All components procured, furnished, and installed by the Contractor should be multi-sourced and readily availableto KTA.

338 All components procured, furnished, and installed by the Contractor should have the capability of sourcing fromthe same manufacturer or multiple suppliers. The intent is to increase compatibility and reduce maintainabilityproblems.

339 Proof of purchase in the form of dated invoice and shipping bills shall be retained and furnished to KTA inaccordance with the Requirements of this Scope of Work and Requirements and Contract for all Hardwarepurchased by the Contractor.

340 The RSS Hardware shall have a minimum manufacturer support for five (5) years.

341 The RSS Hardware shall be supported for the duration of the Contact after the date of Operational TestAcceptance. During the life of the Contract the Contractor is responsible for ensuring the System is operational inaccordance with the Performance Requirements.

342 The Contractor shall use proven server configurations that support future Upgrades to processors, memory,storage, operating System, database, and other System components. All third-party Hardware and Software andContractor Software shall be Hardware neutral and shall perform without intervention on any Hardware platform.

343

The System architecture shall have expansion capability to support a ten (10) year growth in traffic volumes in itsinstalled Hardware which includes support of AVI and image-based transactions at the Tolling Locations. For thepurposes of calculation, the RTCS shall have the capability to process vehicles in real time to meet the vehiclespeed and peak traffic volumes of up to 1,500 vehicles per lane, per hour as specified in this Scope of Work andRequirements and as referenced in Attachment 1: Future Project Transactions. The system storage capacity shallbe at no more than 50 percent (50%) of capacity at the end of the Contract Term.

344 The operating System for the RSS servers shall be a proven system used widely throughout the United States forintensive database Operations and shall be compatible with the Relational Database Management System(RDBMS) and other tools employed.

345 The operating System for the RSS servers shall consist of a multi-user, multi-tasking operating System.

346 The operating System shall fully utilize the redundant RSS server architecture and shall support all peripheralsdefined in these specifications.

347 The operating System shall also support the proposed communications topology, redundant RSS configuration,and Contractor’s application Software.

348 The Contractor shall provide and maintain supported versions of the operating System for the Contract Term andall Upgrades of the RSS shall be the Contractor responsibility.

349 The operating System shall have a future Upgrade path and be supported for the Contract Term.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

350 The Contractor shall provide a highly reliable and secure RDBMS for the storage of images, video, transactiondata, image-based transaction data, audit data, and all other data, as applicable, for the retention period specifiedin the Scope of Work and Requirements.

351 Contractor shall provide the latest version of the RDBMS that is field-proven to operate in a transaction intensiveenvironment.

352 The RDBMS architecture shall support the RSS functions for each of the Roadways and allow Authorized Usersseamless access to all data.

353 The RDBMS shall be compatible with the operating System and application Software, and shall support theredundant RSS server architecture.

354 The RDBMS shall have an Upgrade path and shall support Upgrades to operating system, application, memory,processors, etc.

355 The RDBMS shall have Maintenance and Upgrade Services from the 3rd party software provider for the ContractTerm. For example Microsoft Software Assurance or Oracle Software Update and License Support or typical shallbe required.

356 The Contractor shall provide and maintain supported versions of the RDBMS for the Contract Term and allUpgrades of the RSS RDBMS to the latest supported version shall be the Contractor responsibility.

357 The RDBMS shall be supported by the Contractor for the Contract Term.

358 The Contractor shall keep all Software instances throughout all environments at the same Software version,configuration and patch level.

2.1.2. Roadway Support System (RSS) Printers

359 The Contractor will not be required to procure, furnish, and install any printers for KTA use as part of the RSS.

360 KTA shall have the ability to print from the RSS interface to any printer connected to the KTA System network.

2.1.3. Roadway Support System (RSS) Uninterruptable Power Supply (UPS)

361 Roadways Support System (RSS) Hardware and Equipment shall be on UPS supplied by KTA and the Contractorshall furnish and install an electronic interface between the RSS and the UPS to monitor the UPS performance.The MOMS shall detect the status of the UPS and Alert technicians when the System is on UPS.

362

Software drivers or interfaces shall be developed, furnished, and installed where required to acquire, display,store and report all parameters provided as outputs from the UPS. The interface shall be designed to providesupport for TCP/IP, SNMP, and/or a web interface that can be used to configure and administer the UPS, as well as support email-based alerting.

2.1.4. Image ServerThe Contractor’s image processing solution shall meet the functional and Performance Requirements of the Scopeof Work and Requirements. The Design shall support latency in the transfer of images to the KTA CSC BOS andprevent loss of images and image-based transactions if there are communications or server issues. If theContractor’s solution includes the provision for a central image server as part of the RSS, then the central imageserver shall be located at a KTA Approved location.The image processing solution shall support, but not be limited to the following general functions:

a) communicate with all of the roadside ICPS for the transmission, tracking, reconciliation and processing of all vehicle images and image-based transactions;b) interface with KTA CSC BOS for the processing and reconciliation of all vehicle's images and image-based transactions;c) support the transfer of images and image-based transactions to the KTA CSC BOS without loss of any image or image-based transaction; andd) provide reconciliation reports as determined by the KTA during Design.

363





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

2.1.5. Data Backup

364 The RSS shall include data backup Software and Hardware that allows remote incremental and full back-up of datawithout manual intervention. Notification on the status of the backup process shall be transmitted to MOMS.

365

During the installation of the RSS servers, the Contractor shall create an image of the completed serverconfigurations, as well as maintain regular local and remote backups. If there is a catastrophic failure that resultsin the loss of data, the Contractor shall provide a means to reconfigure the servers without disruption to tollcollection Operations.

366 The backup Software shall be capable of displaying the backup data in a user-friendly and readable form asdefined during the Design Phase.

367 The Contractor shall provide a solution for data backup storage locally and off-site.2.1.6. Archive and Purge Control Mechanisms

368 Provide the capability for fully automated and Configurable archival and purging of data, images, video and files inaccordance with KTA’s data retention Requirements.

Archival and purge routines shall be Configurable for each impacted data element, including but not limited to:

a) data;b) images;c) video;d) MOMS data;e) System logs; andf) interface files.

Servers shall retain transaction and summarized data, images, MOMS data and System logs, in accordance withthe retention procedures, including but not limited to:

a) Transaction data and all associated images shall be retained online for one-hundred and eighty (180) Calendar Days and then purged;b) DVAS video and other video shall be retained online for one-hundred and eighty (180) Calendar Days and then purged;

c) summarized data shall be retained online for at least ten (10) years and then archived and purged;

d) System logs shall be retained online on the System for one-hundred and eighty (180) Calendar Days and then purged;e) MOMS data shall be retained online for the Contract Term; andf) all other data shall be retained on the System for one-hundred and eighty (180) Calendar Days and then purged.

371 The status of the archival process shall generate a message to be transmitted to MOMS. No transactions shall bedeleted unless confirmed to be successfully archived.

372 The Servers shall be sized to accommodate the restoration of selected archived data (two months minimum).

373 Authorized Users shall be able to generate queries from the restored data.2.1.7. Maintenance Access and Application Access374 KTA technicians and KTA staff shall have ability to access the System and application as applicable. 2.1.7.1. Maintenance Access

375 The Contractor shall procure, furnish, and install the required keyboards, video monitors, mouse(s), and KVMswitches over IP to allow technicians to access all servers, controllers, computers, and devices in order to performdiagnostics.

369

370





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

376 Authorized technicians shall be able to access the System through a secure virtual private network (VPN)connection provided by the Contractor and through any KTA authorized workstation connected to the KTA System network.

377 All Maintenance Hardware and Software installed on the Roadside System and RSS shall comply with KTA securityRequirements.

2.1.7.2. KTA Access

378 Authorized KTA staff shall be able to access the RTCS through a secure virtual private network (VPN) connectionprovided by the Contractor and through any KTA authorized workstation connected to the KTA System network.

379 The RSS shall have a Graphical User Interface (GUI) application which shall be accessible by any KTA authorizedworkstation connected to the KTA System network.

380 Access to the application Software shall not require the installation of any Contractor supplied applicationSoftware on KTA authorized workstations and shall be accessible via External networks via Secure VPN access.Based on the user’s access privileges the appropriate menus shall be made available.

2.1.8. Roadway Support System (RSS) Software

381 The RSS Software shall support the functionality detailed in this section and shall meet the KTA operationalRequirements set forth in this Scope of Work and Requirements and Contract for the Contract Term.

2.1.8.1. Data Communications and Interface Requirements

382 The RSS shall communicate with various other systems for the transmission and receipt of toll collection databased upon the Toll Facility in accordance with Approved ICD.

383 All data; transactions; images; files, and messages transferred between all subsystems shall be guaranteed andhave the required data validation protocols to confirm the accuracy and validity of data transfer.

384 The System shall support error detection and recovery process in accordance with the KTA Business RulesApproved during the Design Phase. Alarms shall be generated and reported to the MOMS for allexceptions/errors.

385 Authorized Users shall have the capability to correct the errors and re-process the data without compromisingSystem security.The RSS shall support the interfaces specified in this Scope of Work and Requirements including but not limitedto:

a) Interface to the zone controllers: If the Contractor’s solution does not include a facility server, the RSS shall receive and store all the messages from the zone controllers in real-time. It shall transmit all data required by the zone controllers to support its operation, including the toll rates and TVL. All data sent to and received from each zone controller and the RSS shall be acknowledged and confirmed.

b) The Hotlist shall be transmitted from the RSS to the Roadside System to support on-site enforcement.

c) Interface to the facility servers (if provided): If the Contractor’s solution includes a facility server, the RSS shall have the capability to transmit all data to and receive data from the facility servers as required in this Scope of Work and Requirements to support lane Operations. All data sent to and received from each facility server at the RSS shall be acknowledged and confirmed.

d) Interface to the KTA CSC BOS: The RSS shall have the capability to transmit AVI transactions to the KTA CSC BOS in real time and in batch mode (at Configurable intervals/transactions) in accordance with the Approved ICD. e) Interface to the image server(s): The RSS shall track and reconcile image transmission and transfer status.

386





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

f) Interface to the MOMS: The RSS shall interface with the MOMS to transmit alarms and RSS operational status including recovery messages.

387 The RSS shall receive a comprehensive TVL from the KTA CSC BOS once a day and incremental TVL Updates notmore frequently than every sixty (60) minutes (Configurable).

388 Toll rate tables shall be transmitted from the KTA CSC BOS to the RSS when rate changes are initiated on the KTACSC BOS.

2.1.8.2. Interface to the Zone ControllersThe RSS shall support the interface to the zone controllers to transmit and receive toll collection data includingbut not limited to:

a) transaction data;b) ICPS images;c) alarm messages;d) remote Authorized User Operations;e) TVL;f) toll rates and schedules; andg) configuration files.

390 All data sent to and received from each zone controller and the RSS shall be acknowledged and confirmed.

2.1.8.3. Interface to the KTA CSC Back Office System The RSS shall communicate with the KTA CSC Back Office per the Approved ICD in real time and in batch mode forthe transmission and receipt of toll collection data including but not limited to:

a) Transaction data upon creation of the fully-formed, pursuable transaction;b) Fully-formed image-based transactions, including image ALPR/OCR results that include license plate number; state jurisdiction and plate type (if applicable) and ALPR/OCR confidence levels for each of these data elements;

c) Processing of Image Toll (I-Toll) transaction dispositions and related toll rate adjustments for I Tolls which are determined and processed in the KTA CSC BOS using the fully-formed image-based transactions;

d) comprehensive TVL once a day and incremental TVL Updates not less often than every sixty (60) minutes (Configurable); e) toll rates and schedules from the KTA CSC BOS;f) transaction reconciliation status;g) Hotlist; and h) Other data files needed for KTA CSC BOS transaction processing.

2.1.8.4. Interface to the Maintenance Online Management System (MOMS)

392 The RSS shall interface with MOMS to transmit alarms and RSS operational status including recovery messagesand operational Alerts.

2.1.9. Version Tracking Requirements

393 The RSS shall maintain records of all versions of the TVL; Hotlist; toll rate schedules; lane configuration files; andlane executable programs that it received and/or created and that were successfully downloaded to the lanes.Receipt of files from the KTA CSC BOS, their version, time of receipt and processing status shall also be tracked.

394 Reports and screens shall be made available to verify the versions and the file download status. Failure in thetransmission of any data to a lane shall result in a failure message being logged and reported to the MOMS.

395 The System shall provide the capability to track the versions of lane executable programs installed at each TollZone location.

389

391





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

2.1.10. Diagnostics

396 The RSS shall provide self-diagnosis functions to detect and report on the status and functioning of the RSSHardware devices, third-party Software, communications, processes, tasks, and Software applications, as definedin the KTA Approved Design Document.

397 All Hardware and Software failures detected shall be reported to the MOMS. 2.1.11. Data Security

398 The Contractor shall ensure that any data records, once entered into the System, cannot be deleted or changed.

399 Data records and files shall only be appended to and not edited or deleted. If manual intervention is required tocomplete the audit and verification process, only Authorized Users shall be permitted to flag a file to ensure theintegrity and provide a complete audit trail.

400 All System access/entry, logins, and modifications (for example, flagging actions) shall be recorded andunauthorized access shall be prevented, logged and reported to KTA IT Security within twelve (12) hours ofdetection.

2.1.12. Transaction Audit and VerificationIt is critical that all messages from the zone controllers are transmitted to the RSS and a verification of this datatransmission shall be performed by the System.

401 The Contractor shall perform automatic audit and verification process that confirms all data transmissionsbetween the zone controller and RSS are successful.

402 The audit process shall be an independent validation of the end of day summary counts from the lane/zonecontroller to the detailed transaction data at the RSS.

403 The RTCS shall perform an independent automatic audit and verification process that confirms all vehiclestraveling through the toll lane are detected and reported as transactions; all transaction transmissions betweenthe zone controller and RSS are successful and the System has the screens and reports to validate the audit trail.

404 If the validation process fails for any reason, failure messages shall be created and reported to the MOMS. If theaudit process determines that vehicles or transactions are missing, the missing information shall be identified andreported to the MOMS.

405 If the audit process is successful, then the audit for the location for the Revenue Day shall be deemed “complete”and System shall track this status of the audit on reports.

406 Once the Revenue Day is “complete” the data reported for that day should not change. Any condition, forexample toll waiving, that results in changes to the data shall be identified and Authorized Users alerted.

2.1.13. Data Summarization

407 In order to support the KTA reporting Requirements, transaction data shall be summarized. The summarizationdetails, including but not limited to summarization date and status shall be recorded to provide an audit trail.

408 In the event additional data is received that changes the summary counts previously generated, then an alarmmessage shall be generated and the System shall automatically re-summarize the data until a Configurable periodhas lapsed after which the re-summarization shall be performed manually.

2.1.14. Data Warehouse

409 The Contractor shall provide a replicated database environment independent and separate of the RSS productionenvironment for reporting and analytics to which KTA shall have full access.

410 The Contractor shall provide validation that any and all data replicated between the production database(s) andthe replicated database is complete and accurate.

411 The replicated database environment shall be updated with all non-sensitive data (production data excluding anyPII related data) at a minimum once per day.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

412 Provide a schema architecture that is simple to understand so that Authorized Users familiar with querycommands can effectively query data for export/input into common business intelligence tools for data reportingand analysis.

2.1.15. Transaction Pre-processing

413 The RSS shall ensure all transactions transmitted to the KTA CSC BOS are transactions that are pursuable andcomply with the ICD specifications.

414 The RSS shall pre-process all transactions in accordance with the Approved Business Rules in order to filterincorrect transactions that may result from Equipment failures and lane logic issues.

415 Transactions that should not be processed further at the KTA CSC BOS shall be identified and flagged and filteredat the RSS and not transmitted to the KTA CSC BOS.

416 The RSS shall identify exceptions, anomalies and other conditions determined during the Design Phase in theevent they have not been filtered at the zone controller; for example, same Transponder read within Configurableconditions.

417 In scenarios where multiple Transponders with valid status are reported, the System shall select one Transponderwith valid status to be included the transaction (per the Approved Business Rules) and transmitted to the KTA CSCBOS and the KTA CSC BOS will post the transaction in accordance with KTA Business Rules.

418

In cases where a Transponder read and an image-based transaction are created for a vehicle (in case of bufferedreads or lane logic issues) then the RSS shall perform the filtering based upon Configurable parameters Approvedduring the Design Phase. In case of buffered read transactions, the Transponder read time shall be used as thetransaction time.

419 Alarm messages shall be created and reported to the MOMS in the event such exceptions identified in this sectionexceed a Configurable threshold.

2.1.16. Roadway Support System (RSS) Application SoftwareThe Contractor shall develop, furnish, and install a single GUI application Software for the RTCS that supports alluser functions for the RSS, including:

a) reporting, MOMS, image processing, and DVAS; b) System architecture to provide the necessary databases to support the synchronization and transfer of the necessary data to support the single GUI requirement; andc) Single Sign On (SSO) capability. All rules for password security such as characters and rotation are enforced and passed between network and application. Any SSO exclusions shall be identified by the Contractor in System Detail Design Phase.

421 Any KTA authorized workstation connected to the KTA System network shall be granted permission to access andrun the GUI application.

422 The GUI application shall be compatible with the KTA Approved current version, or immediate prior KTA Approved version of Microsoft Office and releases of the following browsers, including but not limited to, Microsoft InternetExplorer.

423 Based on the user’s access privileges obtained from Active Directory the appropriate menus, screens, tabs, reportsand other System functionality shall be made available.

424 Changes to the System data and System parameters shall be through screens and only Authorized Users shall haveaccess to these screens.

425 All access to the application and changes to the data shall be recorded and tracked, and the System shall providean audit trail for all data modifications and parameter changes.

426 Authorized Users shall have access to the data modifications and parameter changes initiated by users.2.1.16.1. Graphical User Interface (GUI) Requirements

The GUI Design must include accepted industry design standards for ease of readability, understanding andappropriate use of menu-driven Operations, user customization and intuitive operation.

420





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

The GUI Design and development shall incorporate human factors and usability engineering and be optimized forspeed, as well as provide the following controls, including but not limited to:

a) menus (such as pull down, popup, cascading, leveling, etc.);b) windows (allowing for multiple windows within the application, such as to navigate back without having to re-enter information) c) informational messages;d) positive feedback;e) provide warning and/or confirmation messages when appropriate as defined during the detailed Design Phasef) exception handling and error dialogs, including logging the error;g) control icons, links and action buttons;h) data entry fields, combo boxes, check boxes;i) provide the capability for the user to print screens;j) display (read-only) fields; andk) general and context-specific help menus.

428 Data entry screens shall have Configurable mandatory fields that require data entry prior to continuing throughthe process.Provide field-level validation (server-side enforced) and format verification upon exiting data fields applicable topre-defined formats or standards, including but not limited to:

a) alpha-numeric;b) date;c) time;d) special characters;e) length;f) lane and location ID; andg) Transponder numbers.

430 Provide other formatting masks (server-side enforced) as configured by the System administrator (visible tocertain users but masked for other users), which can be applied to any other field in the GUI.Provide field-level “tooltips” or other interactive help, Configurable by the System administrator, that providespecific guidance on any field presented, including but not limited to:

a) alpha-numeric fields;b) date fields;c) time fields;d) special characters;e) username and password;f) length restrictions;g) lane and location ID; andh) Transponder fields.

432 Online help shall be provided for each screen, each editable field and each selectable option within each screen.

2.1.16.2. Screens and Report Access

433 Capability shall be provided to assign Roadside System Application screens and reports access privileges to usersbased on user level/role, as determined by KTA.

434 Based on the access levels/role a user is assigned to the appropriate menus, screens, tabs, reports and all otherrequired user information shall be displayed.

435 For some screens, certain access levels/roles may only be allowed to view the contents and not allowed to enterany data.

427

429

431





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

436 Access privileges shall be set up to allow KTA authorized personnel to make changes to the access privileges at any time, and shall be based upon access level/role and not at an individual user basis.

2.1.16.3. Roadside System Screens and Reports437 All data entered or generated in the System shall be retrievable through reports and screens.

438 Reports menu shall be organized by category of reports and shall be intuitive to users and easily accessible basedon user access.

439 Data shall be summarized to improve report generation performance and to track changes in data for as-of-datereporting.

440 Reports and screens shall be made available through the System on demand and on an ad-hoc basis; shall havevarious selection and sort criteria, and shall be intuitively Configurable with user selected criteria from drop downdata elements as defined during detailed Design Phase.

441 The location selection criteria shall include Roadway; Tolling Location; lane, and direction of travel.

442 The date selection criteria shall include but are not limited to the ability to generate the same report by hour; day;date range; weekly; monthly; yearly, and year-to-date.

443

Data shall be presented as an accumulation or individually for the selected criteria. This capability shall beConfigurable and applicable to individual Tolling Location and different transaction types whereby the user canchoose the data to be presented as an accumulation of Tolling Locations and/or payment types or as individualTolling Locations and/or payment types.

444 Reports developed shall allow KTA to audit and reconcile the transaction data from RTCS to the transaction dataat the RSS and the KTA CSC BOS in accordance with this Scope of Work and Requirements.

445 Capability shall be provided to manipulate the report data to perform comparative analysis and statisticalcalculations.

446 The Contractor shall provide ad-hoc reporting tools supporting natural language and use of the tools to generatead-hoc reports shall be documented.Provide ad-hoc reporting tool capabilities to Authorized Users to allow the creation and execution of customreports, including but not limited to:

a) drag-and-drop field functionality; b) drill down functionality;c) filtering;d) parameter prompting;e) formula support;f) grouping;g) sorting; andh) stored procedure and function support.

448 The ad-hoc reporting tool shall be COTS Software and be the latest version at the time of Acceptance testing andfield-proven to operate in a transaction intensive environment.

449 The ad-hoc Software shall be compatible with operating System standards and shall be patched and Upgradeableto new versions of the Software and operating System.

450 Ad-hoc report templates created by Authorized Users shall be made available to all Authorized Users. All reports shall show the status of the validation/audit process, as defined by KTA and other relevant statusesthat indicate items, including but not limited to whether:

a) all data has been obtained from the lanes; b) the data has been re-summarized; c) the transactions have been transmitted to the KTA CSC BOS; and d) the report is complete.

452 The date and time of the last transaction processed shall be included in all applicable reports.

451

447





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

453 Once the audit process is completed and Revenue Day is closed, the data on reports for the day shall not changeunless data is re-summarized.

454 All reports shall include individual totals, sub-totals, and grand-totals as appropriate and such totals shall bemaintained when data is exported to other formats.Reports shall have the capability to select the date type, including but not limited to:

a) revenue date;b) transmission date; c) as-of date; d) process date; e) transaction date; orf) a combination thereof, as designated by KTA.

456 Reports shall use conditional formatting to identify exceptions and data that are outside the normal trend.

All reports and screens shall have the capability to be printed or saved in various formats (both compressed anduncompressed), formats to be Approved during the Design Phase including but not limited to:

a) Portable Document Format (PDF);b) plain text format (TXT);c) Microsoft Excel (2016 version and later);d) delimiter-separated values;e) hypertext markup language (HTML); andf) extensible markup language (XML).

458 A report generation feature shall be available for configuration and shall permit an individual with permission torequest selected reports for auto delivery by email or to a designated server according to a routine or custom-specific interval.

459 Selected reports shall be automatically generated and made available to authorized personnel at the start of theBusiness Day or at other appropriate time as designated or requested by KTA.

460 Data from summary reports scheduled to run daily shall be automatically exported daily to a specified file formatand made available on the KTA designated server.

461 The System shall have the ability to drill down all high-level reports/screens to the next level of detail and todetails as determined during the Design Phase.

462 Authorized Users shall have the ability to display and review the ICPS images and DVAS video and event detailsassociated with the selected transaction from the drilled down details.

463

Authorized Users shall also have the ability to view the contents of files that are received by the RSS andtransmitted by the RSS in a readable format. If files are compressed or encrypted, the necessary Software toolsshall be provided to view their contents. If the user selects a specific file, the contents of the file shall be displayedand the user shall have the ability to save the contents as a .csv file and in a useable Excel format.

464 Where applicable, data shall also be presented in graph forms and chart types and the user shall be able to selectpresentation form from a variety of graphic styles. Report designs shall be presented and finalized during theDesign Phase.

465

Data shall be organized and summarized in a manner to allow for report generations within thirty-five (35)seconds for daily reports when less than or equal to 30,000 rows (750 pages) in the report, and within seventy(70) seconds for weekly, monthly, and annual reports when less than or equal to 200,000 rows (8,000 pages) inthe report, of a report generation request. The report execution time shall be based on the reporting serverexecution time statistics calculated during the execution of the report.

455

457





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

466 Additionally, after the deployment and implementation of the System, the need may arise to create additionalreports and modify implemented reports and the Contractor shall support such additions and/or modifications. Itis anticipated that no more than five (5) additional reports.

2.1.16.4. Roadway Support System (RSS) ReportsThe RSS shall provide reports to audit and reconcile the System and validate System performance.

467 Report Designs and templates shall be presented by the Contractor and reviewed by KTA during the Design Phaseand Approved.

468

Transaction Audit Report: This report shows the status of the transaction transmission from the zone controllersto the RSS, the audit status, the failed transactions, all exceptions, and missing transaction sequence numbers ateach of the Tolling Locations. The communication status between the zone controllers to all of the subsystemsshall be displayed. The report shall also include the date the transactions were received at the RSS and the dayslagging. It also shows the transmission status of the transactions to the KTA CSC BOS.

469 System Audit Trail Reports: Weekly and monthly reports shall be made available that show the modificationsmade by the users to system parameters and ability shall be provided to obtain the details of the modifications.

470

System Exceptions Report: The System Exceptions report shall display transactions that are consideredexceptions, including but not limited to duplicate transactions; dual Transponders; RSS filtered transactions andnon-interoperable Transponder reads. Exception handling errors and the disposition of these exceptions shall alsobe displayed along with the transaction.

471 Image Reconciliation Report: The Image Reconciliation report shall provide the ability to match transactions bytype to images and to help identify missing images. These reports shall not only reconcile the actual images savedto what was expected but also verify that the images were successfully transmitted to the RSS.

472

Transaction Reconciliation Summary and Detail Reports: Yearly, quarterly, monthly, weekly, and daily reports thatshow AVI and image-based transaction transmission reconciliation for all of the tolling points. These reports shallvalidate that all of the AVI and image-based transactions received from the lanes were posted to the RSS andtransmitted to the KTA CSC BOS. Reports shall be available by transaction day and transmit day, and transmit dayreports shall show the files transmitted and acknowledged by the receiving system. Transaction Reconciliationreports shall be available summarized and detailed.

473

Toll Rate Schedule Report: This report shall provide user-selectable criteria to include at a minimum, toll rateschedule and payment types. The toll rate for each vehicle class will be displayed by Tolling Location for theeffective date selected. The report shall be used by Operations and management staff to verify future, currentand past versions of released and unreleased toll rate schedules based on the effective date selected.

474 Hardware Status Report: This report shows the Hardware status codes and descriptions based on the selecteddate range, Toll Zone, Lane and type of Hardware failure. This report allows Maintenance staff to audit the stateof all Hardware components in the lanes.

475 Transaction Number Gap Report: This report shall provide information on gaps in transaction numbers based ontolling point and lane for the specified date range.

476

Unusual Occurrence Report: This report shall be used to provide Operations and Maintenance staff withinformation regarding unusual occurrences with lane data to identify potential Hardware issues, Software issuesor other System anomalies. The report shall include the Toll Facility and tolling point and may be filtered byunusual occurrence (UO) code. This report includes lane number, transactions date and time, lane statustransaction number and a description of the UO.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

477

Lane Operations Report: This operational report lists and summarizes vehicle transactions and Equipmentmessages that are generated in the lanes. This report is an audit tool that presents all lane activity for a specifiedlocation and desired transaction date and time period. Numerous selection and filter criteria shall be provided tohelp identify problems. Detailed information regarding the transaction and event shall be included.

478 Transaction Reports: Daily, weekly, monthly, quarterly, and yearly transactions and reports showing traffic andvehicle class by payment type. Class mismatch transactions shall also be identified. Transaction reports shall besummarized and detailed.

479 Transaction Summary Reports: These reports show daily, weekly, monthly, quarterly, yearly, and comparativetransaction and revenue, by vehicle class and payment type. The summary data shall drill down to the TransactionDetail Report.

480 Transaction Detail Report: The transaction details shall be provided in this report including lane status, Equipmentstatus, transaction status and various lane flags. Users shall be able to access the bit descriptions in all caseswhere information is coded. The report shall be used to investigate discrepancies and issues.

481

Transponder Status List Transmission Report: The TVL Transmission report shows the status of the TVLtransmissions to the RSS and to all of the zone controllers. Summary information related to the number ofTransponders, time acknowledged by the zone controller and other data shall be provided to verify results andPerformance Requirements. Time of receipt from the KTA CSC BOS, time of transmission to the zone controllersand the status of the transmission shall be displayed. Lanes not compliant to the Requirements shall be identified.

482 Image Transmission Detail Report: This operational report lists information on images from the lanes for a userdefined lane created date. Capability shall be included to show image records where it took longer than a userdefined number of hours for the image to arrive at the image server(s).

483

Image Processing Performance Report: The Image Processing Performance Report shall display ALPR/OCRperformance statistics by state jurisdiction. Problematic lanes, Tolling Locations and state jurisdictions shall beidentified. The report shall also include a breakdown of the ALPR/OCR performance by confidence levels, ifALPR/OCR is used. The report selection criteria shall include at a minimum state jurisdiction, Tolling Locations,lane and sortable by each selected criteria. The selected criteria shall be defined during the detail Design Phase.

484

File Transfer Performance: This operational report lists files that have been created and sent from the RSS bycomponent for either the created date range or sent date range selected by the user. Information displayedinclude, file information, created date and time, sent date and time and process time. This report verifies Systemcompliance to Performance Requirements. File/data transmissions to the lanes shall include confirmation ofsuccessful delivery at each lane.

2.1.16.5. Monthly Performance ReportsThe RSS shall provide reports to measure compliance to the stated Performance Requirements.

485

Availability – Cashless Tolling Lanes: This report will show each travel lane by location along with uptime,downtime, exception time, availability percentage calculated to 0.001 percent for the reporting period, and pointsassessed per travel lane. The report shall contain a summary, the information from which the Contractor’sMonthly Performance Scorecard is generated.

486

Availability – RSS: This report shall display a list of functional areas (to be determined during System Design)within the RSS along with a drill down to each of the components therein that contribute to the availability of theRSS along with uptime, downtime, exception time, and availability percentage calculated to 0.001 percent for thereporting period, and points assessed per line item. The report shall contain a summary, the information fromwhich the Contractor’s Monthly Performance Scorecard is generated.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

487

Operations – AVI Transaction Transmission Timeliness: This report shall show for each day in the reporting periodtotal AVI transactions sent to the CSC, total number of transactions not sent to the CSC within 120 minutes, andthe percentage of transactions sent to the CSC later than 120 minutes. This report will also contain a summaryshowing the monthly totals for the counted items and the average for the calculated percentages. The summaryinformation will be used on the Contractor’s Monthly Performance Scorecard.

488

Operations – Image Transaction Transmission Timeliness: This report shall show for each day in the reportingperiod total image transactions sent to CSC, total number of image transactions not sent to the CSC within 120minutes, and the percentage of transactions sent to the CSC later than 120 minutes. This report will also contain asummary showing the monthly totals for the counted items and the average for the calculated percentages. Thesummary information will be used on the Contractor’s Monthly Performance Scorecard.

489

Operations – AVI Transaction Accuracy: This report will display the number of AVI transactions reviewed by theQA person(s), the number of AVI transactions that failed the QA accuracy check, and the System calculatedaccuracy calculated to 0.001 percent, as well as the amount of assessed points for the month. The data for thereport will be provided by the KTA (or designee) reviewer, and a screen for this information to be entered into theSystem will be required. This information, once collected and calculated by the System will be used on theContractor’s Monthly Performance Scorecard.

490

Operations – Image Transaction Accuracy: This report will display the number of image-based transactionsreviewed by the QA person(s), the number of image-based transactions that failed the QA accuracy check, and theSystem calculated accuracy calculated to 0.001 percent, as well as the amount of assessed points for the month.The data for the report will be provided by the KTA (or designee) reviewer, and a screen for this information to beentered into the System will be required. This information, once collected and calculated by the System will beused on the Contractor’s Monthly Performance Scorecard.

491

Operations – Image Quality: This report will display for each day in the reporting period, the total number ofimage transactions processed, total number of image transactions rejected (from KTA feedback per the ApprovedICD), total number of images rejected for reasons under control of the Contractor (to be determined duringSystem Design Phase), and the percentage calculated to 0.001 percent. The report shall also have a summaryshowing the monthly totals of each plus the assessed points for the month. The summary information will be usedon the Contractor’s Monthly Performance Scorecard.

492

Operations – CSC File Communications: This report will show for each day in the reporting period any endpoints(zone controllers, etc.) that require the TVL file along with a total number of times within the reporting periodthat the TVL was not received and applied within fifteen (15) minutes. Each of these lines will also show thenumber of Updates not received and applied within fifteen (15) minutes along with the value equal to the numberof Updates received from the CSC minus the number of Updates received and applied. Last column in the body ofthe report is the number of points assessed for each day, the formula to be finalized during System Design.

493 Performance Reporting – Monthly Contractor’s Performance Scorecard: This report is intended to be a single pagequick look at the performance of the Contractor and System for the reporting period. The aforementioned reportswill provide the data that will be used to populate this report, as sample of which is shown in Table 3-4.

494 Performance Reporting – Historical Performance: This report will show the Contractor’s performance on each ofthe Performance Standards for the last twelve (12) months.

2.1.16.6. Dashboards/Real-Time Monitoring





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

495

The Contractor shall provide real-time Dashboards applications developed during the Design Phase to monitor theRTCS in a pictorial and Dashboard view. The Dashboards shall include but not be limited to real-time monitoring of tolling point traffic, Maintenance data, operational modes for Tolling Locations, incident modes/status andSystem performance monitoring. There should be at least one (1) screen that includes monitoringdata/Dashboard for all Tolling Locations.

496 Authorized Users shall have the capability to configure and customize their Dashboard to display the relevantdata/graphs and video. The capability for Dashboard displays that are layer Configurable by the user is highlyencouraged.

497 The Contractor shall provide Authorized Users the capability to view real time DVAS video and also playbackrecorded video via the Dashboard. The event data pertaining to the vehicle in the video shall be displayed on thevideo.

498 Authorized Users shall have the capability to drill down to each lane to review and monitor detailed events asthey occur for each transaction.

499 The Dashboard shall provide full Tolling Location/lane monitoring which has continuous, current monitoringinformation for each lane including Equipment status.

500 Users shall have access to the detailed data and trending graphs directly from the pictorial and Dashboard view.

501 Users shall be able to easily maneuver through screens and view data, and different colors and pictures shall beused to bring critical events to the user’s attention. The use of tooltips is encouraged.

502

Summary data by payment type for all KTA toll facilities and by Tolling Location shall be displayed and users shallhave the ability to drill down to the details. If a specific Tolling Location is selected, transaction and event leveldata by lane shall be made available and users shall have the ability to view the DVAS real-time video andtransaction images through this screen. Real-time video and images should have a Configurable refresh rate.

503 Display various comparative transaction, pricing and revenue trends, and forecasts.

504 All Priority 1 alarms shall be displayed in color and shall be audible to direct attention to the failure. Operationalalerts shall also be displayed on the Dashboard.

505 Users shall be able to easily identify problems (traffic or Equipment) on the lanes and initiate MOMS work orderfrom this interface.

506 In addition, the real-time monitoring shall provide detailed real-time information about the AVI Systemperformance, the AVDC System performance, and the ICPS performance to assist in diagnosing and investigatingproblems. Data pertinent to traffic monitoring and Maintenance shall be displayed in real-time.

2.1.16.7. Maintenance Remote OperationsThe System shall provide the ability to allow Authorized Users to remotely operate the lanes to support the KTAOperations, including but not limited to:

a) remote Update of security patches and Software Updates;b) download TVL and toll rate schedules to selected zone controllers when there are issues;c) manage power distribution systems; andd) reboot the zone controller.

2.1.16.8. User ManagementUser setup and management is a critical task since the user access levels/roles created through the Systemdetermines what privileges and access rights each user is granted.

508 Access to the zone controllers, RSS, the MOMS, and the DVAS shall be controlled through the user accessprivileges set up through the user management module.

509 The user list shall be obtained from the KTA Active Directory maintained by KTA IT or from an Approved source atregular intervals as defined during the Design Phase.

507





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

510 Authorized Users shall have the capability to add new users into the System, to update/modify existing users, andto disable users.

511

The user identification data shall include the user name, job designation and identification number. Each userrecord shall also include a Configurable user expiration date in the System that is defaulted to three (3) years forpermanent employees. The default expiration date is one (1) year for seasonal employees. The System shallmonitor for user expiration dates and shall send Alerts to a supervisory role a Configurable number of Days inadvance of the expiration date.

512

All users shall be assigned a user ID and a default password which they are required to change when firstaccessing the application. All RSS applications shall provide a Single Sign On (SSO) capability. All rules forpassword security as defined in Attachment 6: KTA Information Security Overview are enforced and passedbetween network and application. Any SSO exclusions shall be identified by the Contractor in System DetailDesign Phase.

513 Users shall have the ability to reset/change their password and all security controls shall be instituted to becompliant with standard security Requirements including but not limited to, strength of the password, the reuseof old password, and changing password at Configurable intervals.

514 All users who require access to the lanes, including Maintenance staff, shall be assigned a default PIN which theyshall be required to change at first sign in.

515

Access to all information on the KTA toll collection network shall be limited to designated KTA and Contractorpersonnel and shall be password/PIN controlled. User access security including sign-on facilities, access privileges,user role and different levels of access shall be provided for the application, database, files and directories andshall be fully user Configurable. Specific Requirements shall be developed during the System Design.

516 Authorized Users shall have the ability to configure the access privileges based on user role for all menus, screens,tabs, functions and actions provided in the RSS and the Roadside Systems. All user lane and application privilegesshall be maintained at the RSS and transmitted to other systems for user validation.

517

The Contractor shall develop the matrix of access levels/user roles and allowed privileges during System Designwith the KTA input and Approval. The System shall allow for addition and changes to the access levels/user rolesand addition of personnel in a secure manner. Authorized Users shall have the ability to activate, deactivate, andterminate user’s access to the System in accordance to Approved Business Rules.

518 The Contractor shall not circumvent the KTA Approved System security. Specific Requirements shall be developedby the Contractor during System Design.

2.1.16.9. Toll Rates and Schedule

519 The System shall provide Authorized Users the capability to create and manage toll rates and schedules. GUIcapabilities shall incorporate human factors, exception handling, error dialog, general and context-specific helpand be optimized for speed.

520 At a minimum, capability shall be provided to establish toll rates based on facility, tolling point, vehicle class, orpayment type and shall support time of day and Holiday toll rates as defined during the Design Phase.

521 Authorized Users shall have the capability to pre-establish the effective date/time the toll rates will be enabled.The System shall permit KTA to schedule toll rates and changes in toll schedules in advance of the new ratesbecoming effective.

522 Authorized Users shall have the capability to establish a default toll rate to be used in the event of dataunavailability or other conditions as determined by KTA that would warrant the use of the default toll rate.





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

523 The System shall record and track the toll rate ID and toll schedule ID and their transmission status for auditpurposes.

2.1.16.10. Configurable Parameters

524 The System shall provide the ability for Authorized Users to modify the Configurable System parameters.

525 Any configuration change shall result in the creation of an audit trail and each change shall be identified by aunique identifier.

526 Changes to Configurable parameters can be scheduled to take effect immediately or at a scheduled time asdetermined by the user.

527 The System shall record and track all changes to Configurable parameters for audit purposes.528 When a new parameter takes effect, a notification shall be generated and reported to the MOMS.2.1.16.11. Zone Controller Executable Download

529 The System shall have the capability to download zone controller executable files and all other files required bythe lane for its Operations. All Software Updates shall be coordinated with KTA.

530 Successful download of the files shall be verified and alarm messages generated if any file was not received by anyzone controllers.

531 Where possible, once KTA has Approved a Software release, all System application Updates shall be semi-automated requiring no action by Maintenance personnel.

2.1.16.12. Maintenance Online Management System (MOMS)There shall be a single Maintenance Online Management System (MOMS) that supports the Roadway SystemMaintenance activities and Maintenance Operations.

2.1.16.13. Maintenance Online Management System (MOMS) – General Requirements

532 Provide the MOMS that supports Maintenance Operations for all Software and Hardware provided under thisContract.Provide a MOMS that monitors, Alerts and generates work orders in real-time for all processes, including but notlimited to:

a) communications issues;b) file transmission issues;c) data exceptions;d) Hardware issues;e) Software issues or failures;f) database issues;g) issues with jobs, processes or data flows;h) low storage space for each subsystem (Configurable thresholds);i) CPU utilization (Configurable thresholds);j) CPU load (Configurable thresholds);k) mounts (if applicable); andl) disk IOs.

Provide the MOMS that monitors, Alerts and tracks in real-time unusual activity triggered by users and systems,including but not limited to:

a) Image-Based Transactions above threshold;b) class mismatch and flushed transactions above threshold; andc) other activities that are not normal in daily toll Operations.

Provide the MOMS that includes but is not limited to the following:a) receiving and monitoring status messages of all System Hardware and Software;b) is capable of local work order manual entry or email entry by Authorized Users;

533

534





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

c) storing MOMS data in a relational database to allow for data recovery and flexibility in reporting the raw data (including via Ad-hoc reporting);d) tracking device failures and service requests;e) assigning priorities and actions to events;f) notifying (automatically) Maintenance personnel via reports, text and email;g) assigning work orders to Maintenance personnel;h) reassigning (manually) work orders to other Maintenance personnel;i) escalating (automatically) work orders to other Maintenance personnel;j) recording time of acknowledgement by Maintenance personnel; k) recording time of acknowledgement by all subsequently assigned Maintenance personnel; l) recording time of repair; m) recording time of Equipment and process recovery;n) recording completion of service calls;o) providing automatic Alerts for work orders not closed out in specified time; p) maintaining and tracking Repair Maintenance Activity;q) is capable of accepting and updating work orders via PDA/smart phones entries via secure communications;

r) tracking all System application Software components and Hardware via an asset management module;

s) is user configurable to allow new equipment/devices to be added so that they may be selected from the application menus;t) is capable of role-based security;u) containing an automatic System exception reporting for all processes that are not running;v) containing an automatic System workflow exception reporting for all items that are not processing correctly or are hung in the System;w) providing a time stamp of every activity performed to a ticket throughout its life-cycle; and

x) providing hard copy reports on device failures and trouble resolution status detail which shall include all entries generated by technician or System since the ticket's initial creation, including but not limited to notifications, time recordings and attached documents. The time recordings shall not be changeable by the Contractor without KTA Approval and any changed information shall be tracked and auditable within MOMS.

Provide the MOMS that supports Maintenance functions, including but not limited to:a) automatic System job/workflow/queue exception reporting and Alerting for all elements that are not processing correctly or are hung in the System;

b) issuing electronic notifications via email or text to Maintenance staff when problems are detected;

c) prioritization of failures and Alerts that is Configurable and Alert Authorized Users when configurations are changed;d) for the calculation of response times, repair times, and down time from the data entered by the Maintenance staff and automatically generated by the System; ande) scheduling of preventive Maintenance through the MOMS that generates automatic work orders at the scheduled times.

Provide a MOMS that supports asset management, including but not limited to:a) tracking of all System Hardware and Software items;b) tracking of all System Hardware and Software locations;c) tracking of all System Hardware and Software versions;d) tracking of all Maintenance and service agreements;

535

536





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

e) maintains a list of vendors from where products were procured;f) associates the original purchase order number to the individual item;g) associates the original vendor number to the individual item;h) associates all warranty information to the individual item;i) provides a Configurable Alert prior to warranty expiration; andj) provides a Configurable threshold quantity Alert for spare parts levels.

538 The System will record all configuration data, and will be versioned after each System component change,including application of System patches.

539 Make all MOMS screens available to all Authorized Users from KTA.

540 KTA shall have the ability to configure the Priority level of each alarm and assign and change the escalationattributes.

541 Addition of alarms shall not require any changes to the MOMS and KTA shall have the ability to indicate if analarm should result in the generation of a work order and if an alarm should be considered in performancereporting.

542 Generating (automatically) daily, weekly and monthly Performance Reports as determined by KTA during Design.

543 Provide the capability for Authorized Users to select MOMS operational, management and performance reportconfigurations based on drop down entries based on the following but not limited to closed tickets, open tickets,tickets worked on by specific technicians, device type or other fields as defined during detail Design Phase.

Provide Authorized Users with operational, management and Performance Reports from the MOMS that includebut are not limited to:

a) summarized and detailed alarm history; b) Maintenance paging and response history;c) work order status and tracking;d) Equipment inventory and tracking; e) Equipment availability;f) preventive Maintenance; g) pervasive Maintenance;h) corrective Maintenance; i) response and repair times for each of the priorities;j) Equipment use history;k) Equipment repair history;l) total System availability;m) sub-system availability for the Roadside Systems and RSS; n) Equipment versions, Software versions, firmware versions and serial numbers for all Equipment installed under this Scope of Work and Requirements; o) incident logs and lost revenue estimates;p) MTBF for the preceding and current Maintenance periods and cumulative;q) Performance Reports detailing compliance to the Performance Requirements;r) detailed list of parts replaced as a result of Maintenance actions, with an identification of warranty versus non-warranty replacement;s) status of removed parts and Equipment with an aging status for parts under repair or replacement (serial numbers, being repaired in Maintenance shop, purchase replacement part);t) an exceptions report summarizing all unusual or significant occurrences during the period;u) trend analysis for repetitive failure;v) status of spare parts inventory; and

537

544





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

w) staffing report detailing positions, staff hours worked and performance.

Provide a MOMS that has the ability to receive information (success or failure), including but not limited to:

a) backup;b) time synchronization;c) synchronization of primary and secondary systems;d) Software Updates; ande) file downloads.

546

In order to ensure that all Tolling Locations are functional, all systems are operational, all the processes areworking and file transfers are successful, Authorized Users shall have access to the MOMS screens that can verifythe status of Tolling Locations, the System and various file transfers, including the files transmitted and receivedfrom the KTA CSC BOS.

547 Tolling Locations and System status shall be shown in a pictorial view with the capability to drill down to thedevice causing the Alert and its associated error logs.

548 The MOMS screen shall show if required files were transmitted to all the lanes and what version is in use.

549 Users shall have the ability to re-initiate download in the event transmissions were not successful.

550 Screens shall be available that show all the alarms generated by the various systems and subsystems, includingthe operating System and the database.

551 Failure of all devices, processes, programs, and scheduled tasks shall be forwarded to a MOMS screen that isaccessible to authorized staff.

552 Various events and error logs shall be provided for each program that shall assist the system administrator toinvestigate problems.

2.1.16.14. System Health Monitoring SoftwareProvide a System health monitoring Software that includes but is not limited to:

a) tight integration with the MOMS;b) network health monitoring;c) Hardware health monitoring;d) a Dashboard that graphically displays component’s health;e) comprehensive log reporting and review capabilities; andf) integration with existing KTA monitoring software.

2.1.17. Time Synchronization

554 The RSS server shall be synchronized to a certified source Approved by KTA using standard network time protocol(NTP) at Configurable intervals but at a minimum every five (5) minutes.

555

The zone controllers; AVI systems; AVDC systems; ICPS; image server; OCR server; DVAS, and other serversneeded to support the Requirements of this Scope of Work and Requirements shall be synchronized to aContractor-provided primary NTP appliance within the RSS. Such appliance shall synchronize with KTA's NTPsource and a Stratum 0 or 1 time source. The Contractor shall also supply a secondary time source. Both theprimary and secondary time synchronization sources shall be Approved by the KTA.

556 If needed, synchronization messages shall be sent to devices that do not support off-the-shelf timesynchronization Software.

557 The time synchronization technique shall ensure that under no circumstance shall the possibility arise forduplicate or incorrect transaction time. The time synchronization precision format shall be hh:mm:ss:msms.

558 Alarm messages shall be generated when there are time synchronization failures and when time drifts are morethan a Configurable threshold.

553

545





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

559 The RTCS shall have the capability to handle Daylight Saving Time changes.2.1.18. General Requirements for Interfaces

The Contractor is responsible for working with KTA and the existing contractors in Designing, developing,documenting, testing and implementing all required interfaces. Electronic interfaces are required to provideconnectivity between the KTA Systems (KTA CSC BOS), the RSS and Roadside Systems. The Contractor shall beresponsible for developing the ICDs, and where changes to existing ICDs are required, these documents shall bemodified by the Contractor as part of this Scope of Work and Requirements based on the Contractor solutionduring the Design Phase. The ICDs shall include requirements for data format and transmission, criteria foracknowledgement and validation of transmitted data and procedures for recording and reconciliation, asappropriate for each interface. It is expected that the latest version of the ICDs will be implemented at Go-Liveand that the Contractor shall continue to update the ICDs as appropriate for the life of the Contract.

560 Provide electronic automated interfaces to the systems in accordance with these Requirements.561 Provide for guaranteed transmission of data for all interfaces.562 Provide for 100 percent reconciliation of the transmitted data and files.

563 Provide the capability for Authorized Users to access and view the contents of files, including compressed orencrypted files, which are received and transmitted by the RSS in a readable format. Authorized Users shall havethe capability to save the contents of such files.Provide the capability for real-time alerting to the MOMS of interface and data transmission failures, including butnot limited to:

a) MOMS Dashboard for managing and monitoring interfaces;b) workflow user interface for managing and monitoring steps within each interface;c) status and history of executions;d) comprehensive scheduling of file transmissions;e) comprehensive reporting for inbound and outbound transmissions;f) tight integration with the MOMS and notification of failed transmissions;g) notification of file transmission and receipt status; and h) capability to manually execute a failed transmission.

565 The Contractor shall utilize secure network protocols Approved by KTA for the transfer of data and/or files viainterfaces defined during the Design Phase.

566 Provide the capability to transmit and receive multiple files during each scheduled batch.567 Provide the capability to transmit and receive multiple files in a day.

568 Utilize file naming conventions that prevent the overwrite of data and/or files. For example, include the date andtime of transmission and provide for unique identifiers.

569 Utilize file handling and processing methods that provide a complete log of the data and/or file transfer process.For example, files that are successfully processed are moved to a processed folder.Validate records and identify errors in the received data and/or files, including but not limited to:

a) mandatory fields;b) data formats;c) data validity (such as tolling points and lane numbers);d) duplicate records;e) unexpected response;f) checksum/record count verification; andg) incorrect status.

571 Provide the capability to correct and re-transmit data and/or files.

572 Provide the capability to process re-transmitted data and/or files automatically or manually by Authorized Usersas determined during the Design Phase.

564

570





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

573 Provide the capability to transmit the error details to the transmitting entity, as well as record it in the MOMS.

574 Provide the ability to identify missing records/transactions/images and request the transmission of such missingrecords/transactions/images.

575 Reconcile the transmitted records to the records received and accepted by the receiving entity.Provide the means to identify interface issues by validating the file transmission process, including but not limitedto:

a) creation and transmission of data and/or a file at the scheduled time, even if there are no records to transmit;b) determination if the data and/or a file was transmitted or received at the scheduled time;

c) creation of alerts to the MOMS if data and/or a file was not created or received at the scheduled time;

d) creation of alerts to the MOMS if received data and/or a file was not acknowledged;

e) creation of alerts to the MOMS if records in the received data and/or file had errors when processed;

f) provide details in real-time to the MOMS of each failed record; andg) creation of alerts to the MOMS when a response has not been received for individual records within the expected duration.

577 Provide data and/or file transmission and reconciliation reports as described in these Requirements.Provide a Dashboard that tracks the progress of data and/or file transmissions through each stage and theiracknowledgements by the receiving entity, including but not limited to:

a) transactions eligible for transmission;b) file and/or data created with file name;c) file and/or data transmitted;d) file and/or data received;e) file and/or data accepted;f) file and /or data rejected;g) file and/or data re-transmitted;h) number of records in the file and/or data set; andi) number of failed records.

579 Provide the capability for Authorized Users to configure the relevant parameters related to file and/or datatransmission for each interface.

580 Monitor the disk capacity where files and/or data are deposited and send an alert to the MOMS and interfacesentities (if applicable) if folders are near capacity (Configurable) or full.

581 Provide the capability to automatically archive successfully processed data and/or files after a Configurablenumber of Days.

582 Provide the data to reconcile file transmissions.

583

Conform to any existing ICDs, including any Updates required at the time of Design and develop all new ICDs thathave been identified as “to be developed”. It is the Contractor’s responsibility to ensure all ICDs (includingexisting) are accurate, updated and meet the Requirements of the Scope of Work and Requirements beforedeveloping the interfaces.

2.1.18.1. Roadway Support System (RSS) Interface to the KTA CSC Back Office System

584 The Contractor shall coordinate with KTA to Design and develop a KTA CSC Back Office System RTCS FileExchanges ICD to be Approved during the Design Phase.

585 The Contractor shall Design and develop an interface from the RSS to the KTA CSC BOS to transmit receive andacknowledge 100 percent of all transactional and tag data in accordance with the Approved KTA CSC Back OfficeSystem RTCS File Exchanges ICD.

576

578





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

586 The interface shall be capable of transmitting AVI and image-based transactions, and images to the KTA CSC BOS.

587 The interface shall be capable of receiving TVL and Hotlist files from the KTA CSC BOS.

588 The Contractor shall provide the capability to positively acknowledge (ACK) message receipt, negativelyacknowledge or reject a message (NACK) and reconcile data transmissions to/from the RSS.

2.1.18.2. Roadway Support System (RSS) to Facility Server InterfaceThe provision of a facility server is optional but if the Contractor’s solution includes a facility server, then theRequirements in this section shall be met.

589 The Contractor shall Design and develop an interface from the RSS to the facility Servers (if applicable) to transmit, receive and acknowledge 100 percent of all data in accordance with the Approved ICD.

590 The interface shall be capable of sending TVL, Hotlist, configuration files, Software Updates and toll rates (ifapplicable) to the facility servers.

591 The interface shall be capable of receiving all transactions, alarms and event messages from the facility servers.

592 The Contractor shall provide the capability to reconcile the successful transmission and receipt of all data at theRSS.

2.1.18.3. Roadway Support System (RSS) to Zone Controller Interface

593 The Contractor shall Design and develop an interface from the RSS to the zone controllers to transmit andacknowledge 100 percent of all data in accordance with the Approved ICD.

594 The interface shall be capable of sending TVL, Hotlist, configurations files, Software Updates and toll rates (ifapplicable) to the zone controller.

595 The interface shall be capable of receiving all transactions, alarms and event messages from the zone controller.

596 The Contractor shall provide the capability to reconcile the successful transmission and receipt of all data at theRSS.

2.1.18.4. Image Server to Roadway Support System (RSS) InterfaceReconciliation of images to the image-based transactions and the status of the transfer of images and image-based transactions shall be maintained and reported at the RSS.

597 The Contractor shall Design and develop an interface from the image server(s) to the RSS to transmit and track thestatus of the capture of images by the Roadside Systems for each image-based transaction and the subsequenttransfer of images and image-based transactions to the KTA CSC BOS.

598 The interface shall be capable of sending image reconciliation and transfer status data to the RSS.

599 The Contractor shall provide the capability to reconcile the successful transmission and receipt of all images andimage-based transactions at the KTA CSC BOS.

2.2. Interoperability

600

The Contractor shall support expected growth of KTA’s Interoperable footprint such that it supports the inclusionof multiprotocol readers and Transponders. The Contractor solution shall allow for modifying and adapting theSystem Design to incorporate new readers and support the transition to the new Interoperable solution withlimited interruptions to the revenue collection.The Contractor shall support the following Interoperable Partners:

a) Central U.S. Interoperability Hub (CUSIOP) Standards and Specificationsb) National Interoperability (NIOP) Standards and Specifications

601





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




3. ROADWAY SYSTEM TRANSITIONThe new RTCS will be installed on the Cashless Tolling Facilities on the Kansas Turnpike. Based on the optionsexercised throughout the Contract, other facilities may transition to the new RTCS.

3.1. Roadway System Transition – General Requirements

602 The Contractor shall accommodate the transition of the existing ORT Toll Zones in accordance with the Approvedschedule.

603 The installation of the new toll collection System and its transition to revenue collection shall not impact theOperations of the existing System. It is the Contractor’s responsibility to make sure there is sufficientinfrastructure (space, power, etc.) to support both the existing and replacement systems.

604 The Contractor shall provision for additional conduits and mounting structures needed for the installation of thetoll collection Equipment.

605 Any temporary re-location of existing Equipment shall be identified and documented by the Contractor and allsuch relocations shall be Approved by KTA. The Contractor shall relocate the existing Equipment if Approved.

606 The Contractor’s implementation process shall accommodate all on-site testing at the locations identified by KTA.

607

The KTA CSC BOS supports all KTA existing Toll Facilities and will support any future Toll Facilities implemented inthe state. The KTA CSC BOS will interface to only one RSS (including the Primary and Secondary RSS). As such, theRSS shall be first Commissioned and it shall interface with the KTA CSC BOS to process transactions as soon as thefirst Toll Zone is Commissioned.

608 As it is anticipated that the KTA CSC BOS will be upgraded or replaced at least once during the Contract Term, theContractor shall transition the RTCS to interface with any KTA CSC BOS implemented during the Contract Term.

609 The Contractor schedule shall be sufficiently flexible to accommodate modifications or changes such as earlycompletions or delays in start or completion of phases that would normally be expected in a multi-phase, multi-contractor construction schedule.

610 The Contractor shall accommodate the various phases of the RTCS implementation in accordance with the KTAApproved schedule.

611 All changes to the System to accommodate technology Upgrades and meet the Contract Requirements shall bethe responsibility of the Contractor.

3.2. RTCS System Implementation

612 Upon the successful completion of the Factory Acceptance Test (FAT), the Contractor will be authorized to installthe new RTCS at select Tolling Locations. The primary and secondary RSS shall be installed at the Approvedlocations.

613 The On-Site Installation Test (OSIT) shall be conducted at the selected Tolling Locations and the functions of theRTCS and the RSS including its interface to the KTA CSC BOS shall be verified.

614 Upon the Approval of the OSIT, the Contractor will be given the authorization to Commission the RSS in revenuecollection.

615 The Contractor will be given the authorization to Commission the OSIT lanes in revenue collection and to startinstallation on the remaining lanes in accordance with the Approved installation schedule.

616 The installation, Commissioning and subsequent transition of each toll lane to be available for revenue collectionshall be in accordance with the Approved Transition Plan.

617

After the Roadway is opened to revenue collection on the new toll collection System, the Contractor shall monitorthe System Operations. All toll Equipment shall be configured and tuned to their optimal performance prior to thestart of the Operational Test. The Operational Test shall commence when the Contractor meets the OperationalTest entry criteria.

No. Requirements





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

618 For an existing ORT Toll Zone, and as Approved by KTA, the Contractor shall coordinate with KTA and the existingvendor to de-commission the existing Equipment. KTA is responsible for the removal of all existing Equipment,mounting arms, cabinets and enclosures and their disposal.

619 The Contractor shall procure, furnish, Design, test, install, operate and maintain the Roadside Systems, includingthe redundant Roadside System Hardware, Software, Equipment, Interfaces and communications provided in thetoll Equipment building at each tolling point.

620 The installation and Commissioning of all Tolling Location implementations shall be in accordance with theApproved Transition Plan.

3.3. Transition to Revenue Collection3.3.1. RTCS System Transition Plan

621 The Contractor shall provide a Transition Plan for KTA Approval that addresses the transition of the Roadside andRSS into revenue collection.

622 The Transition Plan shall address all critical transition elements and activities associated with the installation andimplementation of the Roadway System, including the Roadside Systems, RSS, and interfaces to the KTA CSC BOS.

623 The Transition Plan shall address the integration and interface of the RSS to existing interfaces/Equipment (ifapplicable).

624 The Transition Plan shall address, by location, the transition from the current toll collection Equipment at rampsand/or mainline locations to the new toll collection Operations. All temporary changes and modifications to theinfrastructure to accommodate the transition shall be described.

625 The Contractor’s plan for decommissioning of the existing Equipment (where applicable) and their disposal shallbe included.

626 The Transition Plan shall, at a minimum, include the installation, OSIT (or Installation Commissioning Test),revenue collection and Acceptance of the new Roadside Equipment, the transition from current toll collection toOperations under the new System and System Acceptance.

627 The use of the existing infrastructure at the selected Tolling Locations shall be described including Contractor’sapproach to installation that will have minimal impact on current Operations.

628 Any temporary processes implemented to support the transition shall be documented in the Transition Planincluding eventual replacement process if applicable.

629 All points of coordination or reliance on third-party deliverable, for example the WAN communications network,shall be clearly identified in the Transition Plan.

630 The RTCS Transition activities shall be coordinated with KTA and existing system integrators, and Approved by KTAin order to not interfere with on-going and continuing Maintenance and operational Requirements.

In order to ensure a seamless transition, the following activities shall take place prior to opening the TollingLocations in revenue collection.

a) The RSS shall be installed and Commissioned at the primary and secondary locations and its interface to the KTA CSC BOS shall be validated;b) KTA shall confirm the KTA CSC BOS is ready for the RTCS transition and give Approval for Go-Live. At such time, the Roadway System shall be switched to production mode and ready to begin collecting revenue;

c) Upon Approval to proceed with an Installation and Commissioning Test, the Contractor shall conduct such test at each Tolling Location prior to opening each location to revenue collection. The Contractor shall be responsible for scheduling the required lane closures during the installation as Approved by KTA;

d) The MOMS shall be configured for Go-Live; inventory recorded; technicians scheduled, and notifications set up;

631





D-New Development

N-Not Provided*


P-ProposerS-Sub

T-Third PartyNA-Not

Applicable




No. Requirements

e) The DVAS shall be installed and validated and Authorized KTA personnel shall have access to the DVAS;

f) The OSIT shall be conducted and System functionality and performance validated at the OSIT Tolling Locations; andg) An end-to-end test shall be conducted in the RSS and KTA CSC BOS test environments to validate the flow of transactions and images from the RTCS to the KTA CSC BOS.

632 The Contractor shall plan for possible variances in the sequencing of the transition on the different Roadways dueto construction and readiness of the KTA CSC BOS and Operations in its Transition Plan.



Compliance CommentsY - YesN - No

If "Compliance = N" then Proposer must provide an explanation in this column

4. ROADSIDE TOLL COLLECTION SYSTEM INSTALLATION REQUIREMENTSThis section details the Requirements for the installation of the new RTCS, including the RSS. Unless Approved byKTA, no System installation on any Toll Facility shall occur prior to the satisfactory Approval of Installation Designand the FAT for the specific Toll Facility.

4.1. Installation ProgramThe Contractor shall have an Installation Program that addresses all aspects of the installation of the RTCS and theRSS, including all installation Design, submissions and coordination.

633 The Contractor is responsible for the Design, procurement, installation, cabling, configuration, check-off, andtesting of all Hardware, Equipment, communications, Software, and fixtures provided by the Contractor as part ofthe RTCS at each of the Tolling Locations required to meet the Requirements of the Contract.

634 In the event the Contractor decides to re-use existing conduits and junction boxes on existing ORT Toll Zones, theContractor is responsible for ensuring that such elements are in their fully operational condition and will meet theRequirements of the Contract for the Contract Term.

635 The Contractor shall ensure that the Contractor’s installation activities do not interrupt or interfere with theexisting System Operations.

636 The Contractor shall install the RTCS servers, Hardware, and Equipment required by the System in the PoPEquipment building provided by the KTA.

637 The Contractor shall install the RSS at the primary and secondary locations Approved by KTA during System Design.

638 The Contractor shall work with KTA to test the LAN and the connections to the KTA CSC BOS locations. Testing shallinclude expected traffic loads and all types of production operation data.

639 The Contractor shall coordinate all lane closure activities with KTA.

640

On new Tolling Locations, the Contractor shall review and comment on the KTA provided infrastructure installationand verify the site is constructed per Approved civil drawings. The Contractor shall create a site handover checklistbased on the Approved civil drawings and that checklist shall be completed by the Contractor and must beApproved by KTA for each Toll Zone location.

641 The Contractor shall review and comment on the network that will be designed and installed by KTA.

642 The Contractor shall install, configure, and tune the RTCS using the AVI Equipment to the AVI vendor specificationsand shall be in compliance with the KTA Interoperable Partners requirements. In addition, the Contractor shallhave the AVI vendor provide certification that the lanes are tuned to the Approved AVI specifications.

643 The Contractor shall be responsible for procurement, installation, configuration, and testing of all local areanetwork (LAN) communications Equipment and connection to the KTA installed WAN network Equipment in thetoll Equipment building as further set forth in this Scope of Work and Requirements.

644 The Contractor shall be responsible for procurement, installation, configuration, and testing of all appropriate RSSservers, Equipment and Software required by the RSS at the KTA Approved locations and validatingcommunications to its interfacing systems as further set forth in this Scope of Work and Requirements.

4.2. Installation PlanThe Contractor shall submit an Installation Plan that identifies its approach to installation and drawing packagesubmissions, and covers the major elements of the installation, including coordination with KTA, existing systems,and existing system integrators.

No. Requirements

Required Inputs





No. Requirements

Required Inputs

645 The Contractor shall develop an Installation Plan that documents all installation related activities for the Project.The Installation Plan shall be the master document from which the elements of the System shall be installed.

The Installation Plan shall include and define, at a minimum, the following items:a) The installation schedule detailing all activities, shifts and resources for the installation of the RTCS, including third-party, existing system integrator and KTA activities. Once the baseline schedule is Approved by KTA, updates during the installation periods identifying all schedule changes and Work progress in the form of percentage completions shall be submitted to KTA for Approval.b) The minimum resource allocation requirement for any installation phase and segment.c) How the Contractor manages delivery and staging of the RTCS Equipment to be installed, including any staging, installation and testing performed at the Contractor or third-party facilities and their subsequent delivery and installation at the production sites.d) The coordination between other contractors, including KTA, and service providers. e) Coordination of the lane closures with KTA.f) Coordination with KTA for the installation of the RTCS in the PoP Equipment buildings and interface to the generators, ATS, and UPS at Toll Zones.g) Coordination activities as applicable with other third-party entities for the various interfaces.

h) Testing of the Contractor-provided LAN communications for connection to RSS and the KTA CSC BOS.

i) Quality Control, Quality Assurance, inspection, and testing processes including validation of Contractor installation to the Requirements of the Contract installation drawings.j) The order in which Equipment items are to be installed with estimated durations.k) Special or unique installation Requirements.l) A detailed component list and a description of how each item version number and serial number shall be recorded for each installation and configuration into the MOMS.m) Organization Chart defining Key Team Personnel, roles and responsibilities and contact information. All Subcontractors shall be identified.n) Contingency Plan.

4.3. Installation and Construction Coordination and Meetings

During the Project Design, development and installation periods there shall be a series of meetings between theContractor, the existing system integrators, and KTA. During these meetings it shall be required that KTA berepresented to clearly define and develop the installation Requirements, methodology, timetables, test Plans,roles, and contingency Plans. The Contractor is responsible for coordinating and scheduling all meetings necessaryto complete the Design and installation phase of the Project.

647

The Contractor shall schedule, manage and attend weekly installation meetings during the active Design andinstallation phases of the Project and report on progress of the installation. The Contractor shall identify andcommunicate any issues regarding System construction and installation immediately upon discovery to KTA,existing system integrator, and KTA.

648 The Contractor shall ensure that the appropriate personnel are present at these meetings who can represent theContractor’s interest and provide the information necessary in a meaningful manner.

649 Prior to the meeting, the Contractor shall update the installation schedule based on the construction schedule andall changes shall be identified.

646





No. Requirements

Required Inputs

650

The Contractor shall prepare and distribute a meeting agenda at least forty-eight (48) hours prior to the scheduledmeeting. The meeting agenda shall consist of those items pertaining to the installation and schedule for theprevious and current week’s installation efforts and for an agreed to “look ahead” period. The meeting agendashould include any potential risk items identified and corresponding mitigation efforts.

651 It is the Contractor’s responsibility to make sure all issues that arose during the installation activity for the weekare addressed and resolved or is scheduled for resolution.

652 At these meetings, the Contractor shall also be prepared to address any issues or questions raised by othercontractors, KTA or its representative.

653

The Contractor shall document the meeting discussions and distribute the meeting minutes within one (1) Business Day to everyone from the team invited to the meeting. It shall be up to the recipients of the meeting minutes todistribute to other interested parties. The Contractor shall also record and maintain an action items list that tracksall installation related issues.

4.3.1. Construction Coordination with Infrastructure Contractors

654 The Contractor shall coordinate all installation activities with KTA; existing system integrators on existing facilities;and any infrastructure constructors to ensure all RTCS Equipment specifications are addressed in the Design andinstallation of all new or updated Roadway infrastructure.

655 The KTA (or its infrastructure constructor) is responsible for the construction of the overhead structures/tollgantries, installation of the PoP Equipment buildings and provision of the generators, and the Contractor shallcoordinate closely with KTA and KTA third-party contractors. The Contractor shall participate in the Design and installation of the infrastructure on the new Cashless TollingFacilities, including but not limited to:

a) provide all required Design and installation drawings, operating Requirements and installation specifications to KTA for all toll System Equipment provided;b) review and reach consensus of the Tolling physical network Design provided by KTA;c) support and supply all information requested by KTA and Civil Designer in the form of request for information (RFI);d) review all KTA-provided drawings with respect to the toll System;e) reach consensus on all aspects of such drawings related to the toll System; andf) ensure the RTCS infrastructure provided by KTA will meet the Requirements set forth in this Scope of Work and Requirements with regard to such Design.

657

The Contractor shall be responsible for ensuring that the locations, positions, installation, connections and otherelements of the Contractor inputs identified on the Design and installation drawings provided by the Contractor,for all Contractor and KTA-provided Equipment, whether in-roadway, structure/toll gantry mounted, in the toll PoPEquipment building or otherwise located are accurate and correct.

658 Contractor shall also review and provide comment that the installed roadway, infrastructure, structures/tollgantries, PoP Equipment buildings, and generators meet the Design Requirements provided by the Contractor andshall certify in writing such installed work with regard to the Design provided.

659 Contractor shall cooperate with KTA and infrastructure contractors to minimize required number of lane closuresand to maximize the use of other scheduled lane closures where applicable. The Contractor shall transmit all laneclosure requests to KTA for Approval.

656





No. Requirements

Required Inputs

660

Contractor shall work with KTA and agree to a reasonable plan for scheduling and approving lane closures,including a procedure for advance notice of cancellations of lane closures and allowable conditions for suchcancellations as described in this Scope of Work and Requirements. The Contractor is responsible for administeringall lane closures and traffic controls during the installation phase and for all testing through Acceptance.

4.3.2. Construction Coordination with KTA

661 The Contractor shall coordinate all installation activities with KTA and the civil contractor where applicable.Attachment 8: Implementation Responsibility Matrix defines the areas of responsibility for the parties involved inthe Project Design and System installation on the KTA Roadways.

4.4. Compliance to Standards

The Contractor shall adhere to all installation standards, applicable laws, ordinances and codes as required.

The Contractor shall meet all electrical codes, traffic control, seismic considerations, calibration, configuration, andenvironmental Requirements of and including but not limited to:

a) Equipment manufacturer’s;b) NEC;c) UL standards; d) KTA;e) KDOT;f) FHWA;g) MUTCD; h) IEEE (Institute of Electrical and Electronics Engineers); i) OSHA Requirements; and j) any local authorities having jurisdiction.

663

KTA generally follows KDOT construction practices. Unless the Contractor receives written Approval by the KTA,the Contractor shall adhere to the latest version of the KDOT Roadway Standard Drawings and KDOT StandardSpecifications: https://kart.ksdot.org/StandardDrawings/Default.aspx https://www.ksdot.org/bureaus/burConsMain/specprov/specifications.asp

664 The Contractor shall be responsible for all costs associated with any permits, plan reviews, and inspections relatedto toll System work.

665 It shall also be the Contractor’s responsibility to procure all Documentation required to install and adhere to theproper installation standards, law, ordinance, or codes.

666 The Contractor shall procure Services of Subcontractors qualified to work in this industry. If a vendor’s componentrequires a vendor approved installer, the Contractor shall use an approved component installer, including qualifiedvendor staff.

4.5. RTCS Installation RequirementsThe installation responsibilities for the System shall include but not be limited to:

a) HVACs, PoP Equipment buildings, power, ATS, UPS, and external generators will be provided by KTA. The Contractor shall use this infrastructure to power and support all RTCS Equipment on the overhead structures/toll gantries and in the toll PoP Equipment buildings.

662





No. Requirements

Required Inputs

b) The Contractor shall furnish and install all connecting conduit from wire ways and conduits provided and installed by others and/or stub conduits to the Equipment. KTA will install the conduits from the toll PoP Equipment buildings to the demarcation point on the overhead structures/toll gantries.

c) The Contractor shall furnish and install separate ground wires for the RTCS, surge protection devices (SPD), junction boxes, pull boxes, conduits, and other such items as required by the installation standards and Requirements.

d) The Contractor shall furnish and install all wiring for all in-lane Equipment and connections to the Equipment racks in the PoP Equipment buildings using cable management best practices. This includes the proper termination of all power, communication, and RF cables and/or wiring (copper or fiber optic) required to connect the individual components into a fully operational System as specified by the manufacturer.

e) The Contractor shall furnish and install all Equipment racks required for the in-lane electronics and toll network communications in the PoP Equipment building.f) The Contractor shall install all Contractor-provided AVI readers in the PoP Equipment buildings.

g) The Contractor shall furnish and install all zone controller computers and other servers (Hardware and Software) into the Equipment racks and test the connection between the zone controller and the RSS.

h) The Contractor shall furnish and install facility servers (if required) in the Equipment racks, including Software, and test their respective connection to the zone controller and the RSS.i) The Contractor shall furnish and install all electronics and other devices in their respective Equipment racks as required to provide a fully operational System.j) The Contractor shall furnish and install all Equipment mounting brackets to support structures for the installation of all toll System Equipment on the overhead structures/toll gantries.k) The Contractor shall furnish and install the AVDC System Equipment, including in-pavement sensors (if part of Contractor’s Design) and overhead mounted Equipment and controllers as specified by the manufacturer. Includes all the KTA Approved materials, Equipment and supplies required for saw-cutting, wiring and sealing of wires in the roadway.

l) The Contractor shall install the AVI System Equipment, including antennas, readers, related Equipment, cables, and any support brackets required. All AVI mounting Hardware, junction boxes, and cables shall be procured and supplied by the Contractor. m) The Contractor shall time synchronize the RTCS with the AVI System, including the provision of required cables as needed.n) The Contractor shall furnish and install the ICPS Equipment, including cameras, ICPS illumination, and any video controller Equipment, sensors, Software, controllers/servers, or specialty Equipment associated with the ICPS. The Contractor shall configure and tune the cameras to meet the Performance Requirements of the Scope of Work and Requirements.

o) The Contractor shall validate all cable and wire terminations via a test process to ensure that the cable is connected to the correct location on each end and that the cable/wire is properly terminated.

p) The Contractor shall power up and provide a field check out/installation Acceptance test of all systems, to be witnessed and Approved by the KTA or its designated representative. Provide the completed installation checklist as described in this Scope of Work and Requirements.

667





No. Requirements

Required Inputs

q) The Contractor shall tune and test the AVI System, as described in and in full accordance with, manufacturer’s guidelines.

r) The Contractor shall calibrate and test the ICPS in full accordance with manufacturer’s guidelines and to meet the image processing Requirements specified in the Scope of Work and Requirements.

s) The Contractor shall calibrate and test the AVDC System in full accordance with manufacturer’s guidelines.t) The Contractor shall furnish, install, calibrate and test the DVAS cameras and Equipment.u) The Contractor shall integrate, calibrate and test the toll-related elements that are provided by the Contractor.v) The Contractor shall provide all other items, materials, and Equipment to complete installation in accordance with the Contract.

4.6. Roadway Support System (RSS) Installation RequirementsThe Contractor is responsible for installation of all Equipment associated with the RSS Operations identified in thisScope of Work and Requirements at the primary and secondary locations identified in the Scope of Work andRequirements.

668 The Contractor shall coordinate all RSS installations and testing of the LAN/WAN and interfaces to the existingsystems with KTA.

669 The Contractor shall install all RSS, including primary and secondary RSS servers, DVAS, MOMS, and central imageservers (if provided) at the primary and secondary locations specified in the Scope of Work and Requirements andApproved by KTA.

670 All servers, storage devices, communications Equipment, and other RSS Hardware shall be installed in thedesignated locations as prescribed in the drawings submitted by the Contractor and Approved by KTA.

The Contractor is responsible for the following activities, including but not limited to:a) furnish, install, configure and test the necessary servers in accordance with the Approved Design documents; b) furnish, install and test the storage units and back-up devices;

c) validate communications to the network Equipment at the primary and secondary RSS locations;

d) validate communications to the network Equipment at the PoP Equipment buildings;e) establish and validate communications from the RSS to each of the zone controllers at each of the Tolling Locations; f) establish and validate communications from the RSS to the KTA CSC BOS;g) furnish, install and validate third-party Software and Contractor Software on all servers and Equipment required to support the RSS;h) furnish, install, configure and test all servers and Equipment for correct point-to-point installation, proper connectivity, acceptable termination of all cables using cable management best practices and successful communications linkage;i) Configure the RSS support interfaces as defined in the Approved ICDs; andj) All other items, materials, Equipment and Software required to complete installation of a fully functional RSS in accordance with the Contract.

4.7. Installation Checklist

671





No. Requirements

Required Inputs

672 The Contractor shall develop an installation checklist Approved by KTA that tracks the progress and completion ofall RTCS and RSS installation activities for the RTCS installation and for the primary and secondary RSS facilitiesinstallation.

673 The checklist shall be the document detailing those items required for the installation crew and technical team tocomplete the installation process for all Equipment and components, including terminations, connections andconfigurations.

674 A copy of the checklist signed and approved by the Contractor, attesting to the completeness of the installation,shall be provided to the KTA after the completion of the installation activities for each lane at each TollingLocation.

675 The Contractor shall conduct a final inspection of all installations and certify the installation Work.

676 KTA reserves the right to witness the Contractor installation and conduct an independent inspection. TheContractor shall coordinate and support such inspections at each Tolling Location.

677 The checklist shall identify all non-conformances, discrepancies and exceptions and Contractor shall be responsible for all corrections.

678 The checklist shall document all changes identified during the installation process and all such changes shall beApproved by KTA or its designated representative.

4.8. Electrical WorkElectrical Work to be performed under this Contract shall include but not be limited to the following general itemsof Work:

a) Provide and install surge protection devices as required to protect the toll collection Equipment and electronics.

b) Install junction boxes and terminate new cable and conduit attachment devices, where applicable.

c) Bond all conduits, manhole frames, and other conductive items to the grounding System in conformance with the NEC.

680

All electrical Work shall be performed by the Contactor and Approved by KTA in accordance with the applicableregulations. Appropriate NEC compliance shall be adhered to with all electrical articles for installation pertaining towiring, enclosures, and other electrical Equipment in hazardous locations. UL labels shall be provided for allelectrical panel boards, enclosures, and accessories.

681 All electrical Equipment must be inspected prior to installation for defects that could damage the Equipment orharm personnel. Any Equipment found to have defects shall not be installed but shall instead be replaced with afully functioning replacement.

682 All electrical Equipment shall be properly grounded for safety. Equipment shall be furnished with grounding padsor grounding lugs. All ground connections shall be cleaned immediately prior to connection.

683 The Contractor shall provide all grounding material required for installation of the Contractor Equipment and allinstallations shall be in compliance with the applicable standards.

4.9. Lane Closure and Traffic Control

684 Contractor shall perform all MOT activities associated with completing Contractor Work during theImplementation Phase. All lane closures shall be coordinated with KTA and lane closure schedules shall besubmitted to KTA in advance for Approval.

4.9.1. General Requirements and Conditions

679





No. Requirements

Required Inputs

685 Roadside Equipment installation shall be scheduled to minimize traffic delay during the installation process. TheContractor is required to request weekday off-peak hour work and hours, a minimum of 48 hours in advance, asdocumented in Attachment 9 – Special Instructions – Traffic Control Restrictions.

686 For all lane closures the Contractor shall conform to the provisions in the latest version of the KDOT StandardSpecifications for Roads and Structures. The KDOT Standard Specifications for Roads and Structures is located at:https://www.ksdot.org/bureaus/burConsMain/specprov/specifications.asp

687 For all lane closures the Contractor shall conform to the provisions in the latest version of the KDOT RoadwayStandard Drawings. The KDOT Roadway Standard Drawings are located at:https://kart.ksdot.org/StandardDrawings/Default.aspx

688 Roadside Equipment installation shall be scheduled to minimize traffic delay during the installation process. TheContractor shall make every effort to schedule Work around peak traffic movement times.

689 Any Work involving removal/relocation of Equipment (both existing Equipment and the Contractor’s Equipment)(loosening or removal of nuts/screws, cables, connectors etc.) shall be done with appropriate lane closures.

4.9.2. Contingency Plan

690 A detailed Contingency Plan shall be prepared for reopening closures to public traffic. A general Contingency Planshall be included in the Installation Plan.

4.10. Work Standards and Requirements

691 The System Equipment installation shall be performed to an Approved set of Plans, which has previously beensubmitted and Approved by KTA or their designated representative.

692 The Contractor shall provide Project management and oversight of all Work performed. At all times wheninstallation Work is taking place, the Contractor shall have an individual designated in the Organization Chart asSite Manager on-site to supervise the installation.

693 The Contractor shall install the Equipment using experienced and knowledgeable personnel. For example,journeyman electricians shall terminate all cables, wiring, or fiber optic cables.

694 All tools such as crimpers, fiber optic termination tools, and test Equipment shall have been properly calibratedprior to being used.

The Contractor shall provide a safe environment for the installation process in accordance with all applicable local,State and federal requirements, as well as any KTA policies, including those related to COVID-19 as shown inAttachment 12 - KTA COVID-19 Vendor Information. Examples include but are not limited to the following:

a) safety harnesses shall be included and employed on all lifts, and the personnel trained on their use;

b) hard hats and safety vest shall be worn in all construction areas;c) safety toe shoes shall be worn in construction areas and around active roadways while performing installation processes;d) Contractor issued identification badges shall be worn at all times; and e) regular safety meetings shall be scheduled to review safety procedures.

4.11. Design and Documentation during Construction and Installation4.11.1. Engineering Design

695





No. Requirements

Required Inputs

696

The Contractor shall secure the services of a fully-qualified engineering design firm(s) for the purpose ofperforming any necessary infrastructure related engineering Design (civil, structural, electrical, mechanical, andarchitectural) and the preparation of related plans and Documentation under the Contract for any Design thatimpacts life safety.

697 All Design Work shall be performed under the direct supervision of a Licensed Engineer of the appropriatediscipline in the State of Kansas. All design professionals shall be licensed and authorized to practice in the State ofKansas.

698 If the Engineering Design effort is performed by the Contractor, the Contractor shall submit Documentationshowing that the Contractor has met the required qualifications described in this section.

4.11.2. Document Control

699 The Contractor shall maintain a Document Management System to control all Project-related documents anddrawings. Each document shall be properly titled (per an agreed upon naming convention), date updated,numbered by revision and version and shall incorporate signature blocks for authorship and approvals.

700

All Documentation regarding the Roadside System Equipment and RSS Equipment installation shall be maintainedby the Contractor. All drawings and other such Documentation shall be made accessible to KTA for review on aperiodic basis as Approved by KTA. The Contractor shall identify and track the status of all Deliverables/Submittalson the Project via the use of a Contract Data Requirements List (CDRL) maintained by the Contractor.

701 The Contractor shall maintain all non-conformance reports (NCR) submitted by the inspectors and document thecorrection and resolution of all issues identified.

4.11.3. Installation Design and DrawingsThe System Equipment shall be installed on existing infrastructure or overhead structures/toll gantries that will bedesigned and constructed by others separately procured by KTA.

702 The Contractor shall provide the installation Requirements including acceptable tolerances for the SystemEquipment, including all related plans and documents. The Contractor shall be fully responsible for the accuracy of its installation Requirements.

703 The installation Requirements provided by Contractor shall be consistent with those provided in Contractor’sProposal and shall accommodate the Design provided to support the lane configurations listed in Attachment 2and Attachment 3.

704 The Contractor shall certify the installation Requirements provided are accurate and appropriate for its intendedpurpose to the satisfaction and Approval of KTA.

705 Contractor shall indemnify all related parties as more fully described in the Terms and Conditions for any damagesthat result from reliance on the installation Requirements provided by Contractor.

706 The Contractor shall submit shop drawings detailing the installation Design that shall be used on-site forinstallation Work. Detailed drawings shall be provided for each site where Equipment procured and suppliedunder the Contract shall be installed.The Contractor shall submit the following Design drawings as part of the drawing package in accordance with KTAdocumentation submission Requirements for each Tolling Location/site where System Equipment is installed,including but not limited to:

a) detailed installation drawing for each piece of Equipment;





No. Requirements

Required Inputs

b) detailed drawing showing the Equipment mounting brackets and details of their installation to the gantry;c) details related to the range of Equipment adjustments;d) detailed electrical schematics;e) all junction boxes and panels;f) detailed Equipment rack layout and interconnections drawings;g) detailed communications layout;h) detailed conduit layout for power and communications;i) power and communications cabling schedules; and j) pavement installation details for in-pavement sensor installations.

708 The Contractor shall use only the latest Approved drawing version for installation.

709 During installation, the Contractor shall maintain a red line version of the drawing package that is submitted to KTA upon the completion of the installation.

710 Documentation shall include memos denoting changes or modification to Requirements.

711 The Contractor shall submit detailed component level network drawings showing all WAN and LAN connections,including connection to the Roadside Systems, the RSS, and the KTA CSC BOS.

712 Contractor shall utilize a predefined range of IP addresses provided by KTA. An IP schematic shall be submittedthat shows all the IP addresses for all Contractor supplied Equipment on the network.

713 The Contractor shall submit detailed component level primary and secondary server configuration instructions,including storage device mirroring, back-up devices and configuration, and network configuration and testing.

714 The Contractor shall submit detailed instructions on the installation and configuration of the operating System,database, third-party Software, and application Software on the servers as customized for KTA Operations.

715 All testing required to verify successful installation and operation shall also be documented.4.11.4. As-Built Drawings/Documents

716 The Contractor shall update the latest drawings with red-lines as changes are incorporated during the installationand check-out process. At the completion of the installation of the System, the Contractor shall gather all red linedrawings into a single package.

717 The red line drawings shall be verified and then incorporated into a final As-Built Drawing package. This final As-Built Drawing package shall include installation drawings, shop drawings and sketches, and other drawing typesthat may have been used to install the Roadway System.

718 All other Documentation used regarding the installation shall be also be finalized and submitted as part of the As-Built Drawing Submittal.

707





5. ROADSIDE TOLL COLLECTION SYSTEM PROJECT REQUIREMENTS5.1. Roadway System Project Management

The Contractor shall employ a Project Management System that is sufficiently detailed to enable KTA to review and confirm that the Contractor has the necessary management, staff, and controls in place to meet the Requirementsof the Contract.

5.1.1. Program Management and Project Management PlanThe Program Management Plan (PMP) describes how the Contractor plans to implement and manage the Project,including staffing, scheduling and communication procedures for controlling all correspondence, Submittals, andother communications between the Contractor and KTA, and communications with third-party entities and withexisting system integrators. The PMP shall at a minimum include the following elements:

a) Project scope and key Deliverables;b) a description of the management and organization of the program, an organization chart, identification of Key Team Personnel and their responsibilities, percentage commitment to the Project, task leads for each functional area and location and identification of the resources to be used in fulfilling the Requirements of the Contract;c) Project team (Contractor, KTA, KTA Representatives, and existing system integrators) contact information;d) a description of the Project planning, Documentation and reporting methods to be utilized, both for use within the Contractor’s staff and externally to KTA and other entities;

e) A description of the process for communication, escalation and resolution of Project issues with KTA;

f) meeting schedules with KTA and other entities including the form of the meeting;g) inclusion of the Approved Project schedule;h) a description of the process for reporting, updating and tracking the Project schedule and Project performance;i) a description of the coordination process with the Civil Designers and KTA during the tolling infrastructure Design Phase;j) coordination process with KTA and management of the installation drawing review process;k) approach to change management, consistent with Contract Requirements, including a description of the process for documenting and submitting change requests, the Approval process and how the change management approach will be integrated into day-to-day Project management;l) approach to document control, including Software (KTA shall have the capability to download documents using this Software) and tools KTA will use and have read-only access to via the Web;m) approach to risk management;n) approach to Quality Assurance and Quality Control;

o) documenting the invoice submission; invoice backup information; verification, and Approval process;

p) a section with all Approved Project forms including but not limited to, meeting agenda; meeting notes; action items tracking log; monthly progress report; and invoices; andq) an emergency contact list as described further below.

No. Requirements

Required Inputs

719





No. Requirements

Required Inputs

720 The Contractor shall identify the tools and products used to manage the Project including Software developmentlifecycle and the internal controls instituted by the Contractor to guarantee successful delivery of the Project.

721 The Contractor shall develop and submit the Project Management Plan to KTA for review and Approval.The Contractor shall develop and submit the communication procedures to KTA for review and Approval thataddress the following, including but not limited to:

a) Correspondence: Correspondence shall be identified as to originator and designated receiver and include the form of transmission. b) Document control: Tracking of document versions and changes including naming conventions.

c) Invoices: All invoices shall be submitted with accompanying backup information as required by the Contract and consistent with KTA processes and invoicing and auditing policies. The Contractor shall work with KTA to develop the appropriate invoice and back-up materials as a part of the PMP development.

d) Submittals: All Submittals shall be delivered as an enclosure to the Contractor's Submittal letter. Each Submittal letter shall be limited to a single subject or item. The Contractor's letter shall identify the Contract number, Contract name and subject of the Submittal.e) Contract number and Contract name: All items of correspondence, invoices, Submittals and Documentation shall contain the Contract number and the designated Contract name.f) Comments Log: Process for validating that all comments provided by KTA on Contractor Deliverables are successfully addressed.

5.1.2. Contractor’s Project Management Office

723 The Contractor Project Manager shall be 100 percent dedicated to the Project for the Implementation Phase of theContract.

5.1.3. Staffing and Key Personnel

724 The Contractor is responsible for maintaining and assigning a sufficient number of competent and qualifiedprofessionals to meet the Requirements of the Contract.

725 The Contractor shall ensure Key Personnel speak fluent English and be readily accessible to KTA or their authorizedrepresentatives during the Contractor’s performance of this Contract.Contractor shall provide staff at all times sufficient to meet the Project Requirements and Contract. The followingare designated as Key Personnel for this Project and are subject to the Approval, replacement and removalRequirements of KTA for Key Personnel as set forth in the Contract:

a) Project Principal – responsible for the overall conduct and performance of the Project; oversight of the Project; the performance of the Contractor Project Manager and a point of contact for any escalated Project issues that cannot be resolved by the Contractor Project Manager;b) Contractor Project Manager – responsible for all day-to-day Work; the overall execution and delivery of the Project and the day-to-day Contractor contact person on the Project;c) Deputy Project Manager – assists the Contractor Project Manager in the execution and delivery of the Project and the day-to-day Operations;d) Technical Manager, Roadside Systems – responsible for management of all Roadside Systems technology and resources including selection of the lane solutions; peripherals; subsystems; Software development and Systems Maintenance;

722

726





No. Requirements

Required Inputs

e) Technical Manager, RSS – responsible for management of all technology and resources related to the RSS, including Software development, on-going Hardware/Software Maintenance, Equipment and Systems and information security as required to satisfy the Requirements of the Contract;f) Installation Manager – responsible for the installation and Commissioning of the System;

g) Maintenance Coordinator - Responsible for coordinating the Maintenance of the System with KTA staff;

h) Quality Assurance Manager – responsible for consistent quality throughout the Design, Development, Testing and Implementation of the Roadway System through good Quality Assurance and Quality Control practices; andi) Test Manager – responsible for the overall planning and implementation of the Roadway System testing program.

5.1.4. Cooperation with Other Contractors and Providers

727 The Contractor shall cooperate to the fullest extent with KTA and existing system integrators to ensure theRoadway System Implementation and Maintenance do not conflict with or cause any interruption in capability orservice or safety issues to the traveling public or customers or impede KTA’s ability to collect tolls.

The Contractor shall cooperate with KTA, existing contractors, existing system integrators and external parties, asdirected by KTA, to support any activity related to the Roadway System Implementation, including but not limitedto:

a) KTA employees;b) KTA Designated Representatives;c) other third parties, as directed by KTA;d) law enforcement;e) inspectors;f) auditors; andg) all contractors.

729 The Contractor shall cooperate with and immediately notify KTA of any customer complaints and System issuesidentified in the toll lanes or facilities that come to Contractor’s attention during the course of Implementation,Testing, or Maintenance.

730

The Contractor shall provide and maintain a current emergency contact list for KTA’s use at all times for handlingemergencies and escalations. The emergency contact list shall name primary and secondary (multiple secondarycontacts as applicable) points of contact for each anticipated emergency type. The emergency contact list shallname the Contractor’s preferred points of contact, in Order of Precedence and shall include, at a minimum, theContractor Project Manager, deputy Project manager, installation manager, technical manager, technologymanager, and other support staff. The purpose of the emergency contact list is to ensure the Contractor can bereached outside normal working hours to address urgent matters.

5.1.5. Monthly Report and Progress Meeting During the Implementation PhaseMonthly Project reports and progress meetings will enable KTA and the Contractor to monitor the status, progress,and quality of the Work performed on the Project and to take proactive steps to ensure successful delivery of theProject.

728





No. Requirements

Required Inputs

731

The Contractor shall provide and maintain a schedule for monthly progress meetings (in addition to the weeklyDesign/installation meetings during the active Design/installation periods) at a location designated by KTA. Themeeting shall be scheduled no later than the 20th day of the following month and shall cover progress up to the15th of the current month.

732 No less than five (5) Business Days prior to the meeting, the Contractor shall submit a draft monthly progressreport to KTA for the period covering the previous reporting period. KTA shall review and comment on theprogress report prior to or during the meeting.

733 The Contractor shall obtain updated installation status prior to the monthly progress meeting and include suchupdates in the Project Implementation Schedule which shall be submitted with the monthly progress report.

734 The format of the monthly progress report shall be agreed upon as one of the initial Project tasks upon NTP andshall be incorporated by the Contractor into the Project Management Plan.The monthly progress report shall include but not be limited to the following items:

a) a summary outlining progress and status, and percentage of Work performed for each task as compared to planned activities in the Project Schedule. Comments shall be included where appropriate. The summary shall also identify key milestones met and missed in the period. b) an analysis of all critical path tasks, potential risks associated with the tasks and proposed contingency/work around plans to circumvent or mitigate delays to the Project.c) identification of any Approved changes to Approved milestone dates and Approved Project Schedule, clearly noting the details and identifying the Contract Amendment.d) a discussion of schedule compliance and an updated Project Schedule showing current status against the baseline Approved Project Schedule. Past due tasks shall be updated and actual dates shall be recorded for completed tasks.e) construction/installation coordination status; f) an updated action items list that tracks the status of all outstanding action items, activities and issues that need decision/resolution. g) an updated Deliverables list showing submission dates, current version, current review status, responsible party and due date.

h) a payment request, if applicable. Payment requests must identify the payment milestone, number and dollar amount. Payments requests shall be made for completed and Approved milestone payments only.

i) a list of change requests (Contractor and KTA initiated) and their status.j) the previous monthly final meeting minutes.k) a six (6) week look-ahead schedule.

736 No more than five (5) Business Days after the meeting, the Contractor shall submit the final monthly progressreport and draft meeting minutes for KTA’s review and Approval.

5.1.6. Project Meetings

737

In addition to the monthly progress meeting, weekly or bi-weekly Project status meetings, as applicable andApproved by KTA, and other regularly scheduled installation and ad-hoc Project meetings shall be required duringthe course of the Project to address specific Deliverables, Work items, Maintenance procedures and issues as theyarise.The Contractor shall perform the following tasks related to all meetings, including but not limited to:

a) develop and coordinate the Project meeting schedule;

735





No. Requirements

Required Inputs

b) distribute Notices of Project meetings in accordance with document control Requirements;c) prepare the agenda in coordination with KTA;d) attend the meeting with all required staff in attendance; e) prepare minutes of the meeting and forward them to KTA within five (5) Business Days after the day of the meeting; and f) maintain an action item list for each type of meeting, identifying issues that need to be resolved at the Project level.

5.1.7. Project Schedule

The Project schedule is a comprehensive list of Project milestones, activities and Deliverables, with intended startand finish dates, including a detailed Work Breakdown Structure (WBS) that identifies Project tasks down to thework package level and the activities required to complete the work package Deliverables.

The Contractor shall provide and maintain a detailed Project Schedule for the Project in Microsoft Project format(Project 2016 or above) that lists all Project activities and tasks for all Phases of the Project, including but notlimited to:

a) Requirements; b) Design;c) development;d) testing;e) installation;f) transition; and g) deployment and Acceptance of the System at the various Tolling Locations.

740 The Project Schedule shall include coordination with KTA, existing contractors, existing system integrators, and KTAand shall clearly document all interfacing tasks.

741 The Project Schedule shall identify all milestones and tasks, starting with the Notice to Proceed (NTP) through thedate of Acceptance for each Project phase.

742 The Project Schedule shall be resource loaded, shall include all draft submissions and review cycles and shallinclude all tasks required of KTA and other contractors and KTA with critical tasks.

743 The Project Schedule shall identify all critical path tasks and shall be used to manage the Project.

744 The baseline for the Project Schedule shall be submitted to KTA for Approval ten (10) Business Days after NTP.

745 The Contractor shall status and update the Project Schedule on a monthly basis, as identified in the Requirementsfor the Monthly progress report.

746 The Contractor shall use the Project Schedule as the basis for all subsequent schedules and updates throughoutthe duration of the Project.

747 The Contractor shall obtain Approval from KTA for any and all changes to the Approved Baseline Project Scheduleand associated milestones in accordance with the Contract process for changes and Amendments and schedulechanges are not considered Approved unless an Amendment is executed through the Contract.

5.2. End of Contract Transition

738

739





No. Requirements

Required Inputs

The Contractor acknowledges that the Services it provides under the terms of the Contract are vital to thesuccessful operation of the System and that said Services shall be continued without interruption. Upon end of theContract for whatever reason, a successor (KTA or a new contractor) may be responsible for providing theseServices. The Contractor agrees to exercise its best efforts and cooperation to affect an orderly and efficienttransition to a successor in accordance with this Section 5.2 and Section 2.7, Section V – Terms and Conditions.

748 Upon KTA’s written Notice, the Contractor shall furnish transition Services during the last ninety (90) Calendar Daysprior to the end of the Contract Term. The Contractor shall develop with the successor contractor or KTA staff, aContract Transition Plan describing the nature and extent of transition Services required.

749 The Contract Transition Plan and dates for transferring responsibilities for each division of work shall be submittedwithin thirty (30) Calendar Days of such Notice. Upon completion of KTA review, both parties will meet and resolveany additional Requirements/differences.

750 The Contractor shall provide sufficient experienced Roadside System and RSS technical and Software supportpersonnel in each division of Work during the entire transition period to ensure that the quality of Services aremaintained at the levels required by this Contract.

751 The Contractor shall provide sufficient staff to help the successor maintain the continuity and consistency of theServices required by the Contract. The Contractor shall allow the successor to conduct on-site interviews with theemployees.

752 The Contractor shall provide the necessary Software and Systems support Services to assist the successorcontractor in setting up the systems, transfer of appropriate licenses and third-party Software, and transition of alldata required to sustain uninterrupted service as directed by KTA.

753 The Contractor shall make all necessary provisions for transferring any leases or sub-leases held by the Contractorto the KTA, including without limitation, all keys; security codes and other codes and other facility accessinformation or devices.

754 The Contractor shall make all other records, documents, data and Software which is licensed to the KTA andpertaining to the Services rendered for this Agreement available within thirty (30) Calendar Days upon writtenNotice or as otherwise provided in the executed License agreement.

755 The Contractor shall make all operational records, documents, data, Systems, specialty tools and Equipment, andfacilities required to support and maintain day-to-day Services being rendered under this Agreement availablebefore the date of such termination, suspension, or expiration.

5.3. Software Design and Development Requirements

KTA expects the Contractor to propose a baseline product for the Roadside solution and the RSS, and that somecustom development will be required. To ensure the Design Requirements for the Roadway System are fullyunderstood by KTA and the Contractor, a series of Requirements and Design review steps are specified following asequential Design process or waterfall model. Requirements derived during the Design process or waterfall modelwill become part of the Contract Conformed Scope of Work and Requirements Document (CSWRD) shall be thebasis for the Contractor to produce a Requirements Traceability Matrix (RTM). The RTM allows for verification thatthe Requirements are addressed in the Design and documented in the System Detailed Design Document (SDDD)and traced to test procedures that validate the developed Roadway System meets the Contract Requirements. TheRTM shall be the basis for all Design, development and testing efforts and Documentation to be developed by theContractor.





No. Requirements

Required Inputs

756 The Contractor shall establish and maintain an effective Software Design and development program along with adocumented Software Development Life Cycle (SDLC) to ensure compliance with the Requirements of theContract.

757 The Contractor shall employ effective techniques, methodologies and tools to develop the System Requirementsand Business Rules for the Project and deliver the Project.

758 Prior to conducting any workshops, Requirements reviews, focus group meetings and Design reviews, theContractor shall develop the necessary Documentation for KTA review and submit such Documentation ten (10)Business Days prior to such meetings.

759 The Contractor shall provide a Table of Contents for the Design document that identifies the required documentDeliverables and any document templates that will be used to develop the Documentation. Such Documentationshall be tailored for the Project, and the CSWRD shall be used for developing such Documentation.

5.3.1. System Requirements Review (SRR)The Contractor shall conduct a series of System Requirements Review meetings with KTA to outline how theContract Requirements will be met. The outcome of these meetings shall be the Requirements Traceability Matrix(RTM) that will be used to validate each Requirement against a Design item(s), Design Documentation and testingprocedure(s).

760 The Contractor shall conduct a series of System Requirements reviews with user groups to identify user needs.

761 The Contractor shall present lane logic and transaction framing rules of the baseline solution.

762 Contractor’s existing screens and presentation formats tailored to KTA Operations shall be used to solicit userRequirements and feedback.

763 During the System Requirements review phase the Contractor can also present the Contractor’s standard productto KTA, and use the feedback obtained in the presentation in the development of the RTM and SDDD.

5.3.2. Business Rules Development

764 The Contractor shall conduct Business Rules development workshops with the KTA to develop and document theBusiness Rules according to the Business Policies and Procedures for the RTCS, including the Roadside System andthe RSS.

765 The Business Rules workshops can occur concurrent to the System Requirements reviews.

766 The Contractor shall provide Business Rules utilized at other Cashless Tolling Facilities; however, they shall betailored to meet the KTA’s Requirements and shall comply with the Scope of Work and Requirements.

767 The Contractor shall track the Design, development and testing of the Business Rules through the RTM.5.3.3. System Detailed Design Review

Based on the RTM and Business Rules documents, the Contractor will Design the Roadway System and submit apreliminary Design document for KTA to review and provide comments. The Contractor will then conduct a seriesof Design meetings with KTA to address the comments and to create the SDDD, defining how the System Designwill meet the Contract Requirements. Upon the Submittal of an updated SDDD another review cycle will takeplace.

768 The Business Rules document and the RTM shall be used to develop the System Design and the SDDD.769 The Contractor shall schedule Design meetings with KTA to fully understand the Design Requirements.





No. Requirements

Required Inputs

770 The Contractor shall support a phased Design process to support the anticipated phased implementation of theRTCS on the KTA Roadways. The Design process shall accommodate for the changes in technology that is inevitablegiven the duration of the Project.

771 The Contractor shall demonstrate pre-production working products (such as, beta versions) during the Designreview process, and stakeholders shall be walked through the workflow, utilizing screens and data flow diagrams.

772 The Contractor shall trace how the System Design meets the SRD, the Business Rules and the ContractRequirements using the RTM.

773 The Contractor shall conduct as many meetings and submission review cycles as deemed necessary by KTA toaddress all Design issues to KTA’s satisfaction.

5.3.4. Reports Design WorkshopsThe Contractor will conduct a series of workshops with KTA to facilitate the Design of the Roadway System reports.The existing reports shall be used as a basis for the workshops.

774 The Contractor shall employ an effective and productive methodology for Designing and finalizing the reports forthe Project.

775 The reports Design process shall be iterative and the Contractor shall conduct multiple workshops with KTA’sstakeholders, and Contractor shall bring subject matter experts to the meeting.

776 Subject matter experts must provide a means for explaining each report, its intended purpose, columns, fields andcomponents and its connection with other reconciling and validating reports.

777 Report templates from existing operational systems shall be submitted and changes to meet the KTA RoadwaySystem Requirements shall be noted. Sample reports shall have correct and accurate data and shall reconcileacross other reports.

778 Upon receiving feedback from the stakeholder, the Contractor shall develop/modify the reports and resubmit theupdated reports for review.

779 The modified and new reports shall be demonstrated to KTA using accurate and reconciled data. Reports that areexpected to reconcile to one another shall be demonstrated together.

780 The iterative series of workshops and demonstrations shall continue until baseline reports are Approved by KTA.

781 The Approved baseline reports shall be used as the basis for the Design document. 5.3.5. Software Walkthrough

The intent of the Software walkthrough is to provide an overall status on the Contractor’s Software developmentprogress to ensure the Contractor is on track to deliver the Project on schedule and to obtain KTA’s feedback onthe direction of the development prior to the full rollout of the Software.

782 The Contractor shall conduct a series of Software walkthroughs including product demonstrations to solicit inputfrom KTA during the development of the Roadway System.

783 Prior to the Software walkthrough, the Contractor shall develop and submit the use cases that will bedemonstrated to KTA for review and Approval. The walkthrough shall follow the process flow and emulate normalOperations.

784 The product shall be demonstrated in a test environment that allows data to flow as it will in the final integratedSystem.

785 The Software walkthrough shall demonstrate to KTA that the developed Software product meets the technical andfunctional Requirements of the Contract.





No. Requirements

Required Inputs

786 Comments and feedback provided during the Software walkthrough shall be documented and resolved by theContractor and the resolution shall be Approved by KTA.

787

The Contractor shall be responsible for identifying and correcting any Software issues or defects in its Design orproduct that impact the Contractor’s ability to deliver the Roadway System that meets the Contract Requirements.This shall apply to issues or defects found during or after Software walkthrough, the FAT or in the subsequenttesting and Implementation. Any such changes shall be Approved by KTA in writing.

5.4. DocumentationThe Contractor is required to provide various Project; Hardware; Software; Requirements; Business Rules; Design;testing; installation and Maintenance Documentation that include Contractor-developed Documentation and third-party Documentation. All Documentation provided under this Contract shall meet the Requirements describedbelow.

788 The Contractor shall provide and maintain an online, electronic document management System (such asSharePoint) that is accessible to both KTA and the Contractor by username and password, to control all Project-related documents, submissions and drawings.

789 The electronic document management System shall be indexed and searchable.

790 All Project documents submitted under this Contract shall be available to KTA at all times using the online,electronic document management System provided by the Contractor.

791 The Contractor shall maintain a Deliverable tracking list that accurately tracks all Contractor submissions; KTA’scomments review documents; resubmissions and final Approval.

792

Each document shall be properly titled, date updated, numbered by revision and version, and shall incorporatesignature blocks for authorship and Approvals. The Contractor shall provide a logical indexing system making useof documents metadata for ease of access for KTA to locate documents in the electronic document managementSystem.

793 Updated submissions of the document shall also include the red-lined version showing all revisions to thedocument since the last submission.

794 The Contractor shall utilize acceptable standards agreed upon by the Contractor and KTA when updatingdocuments and submitting revisions.

795 All Documentation submitted by the Contractor under this Contract shall be accurate and comply with ContractRequirements. All Deliverables shall be submitted in accordance with the Approved Project schedule.

796 A Table of Contents, for all Documentation that requires one, shall be submitted by the Contractor to KTA forreview and comment prior to the submission of the preliminary draft.

797

The Contractor shall submit a minimum of: a preliminary draft, a final draft and a 100 percent final to KTA forreview and comment. All final documents shall incorporate all KTA’s review comments to KTA’s satisfaction. Eachsubsequent submission of a Deliverable shall also include KTA’s comments review log with the resolution of eachcomment updated by the Contractor.

798 KTA shall have the right to require additional interim drafts from the Contractor at no additional cost should thedraft Documentation submitted not be of adequate quality, have missing or incorrect information or if it does notsatisfactorily address KTA’s review comments.





No. Requirements

Required Inputs

799

KTA shall review and Approve all documents submitted under the Contract. For documents containing less thanone hundred (100) pages, KTA will review and provide comment on preliminary draft documents within ten (10)Business Days. For documents containing more than one hundred (100) pages, KTA will review and providecomment on preliminary draft documents within fifteen (15) Business Days. KTA will review and provide commenton all final draft and final documents within ten (10) Business Days. When multiple documents are submitted toKTA simultaneously, or within one week of each other, the number of Business Days required for review shall beadjusted to reflect the overlapping submissions.

800

KTA will provide the Contractor with written comments on all submitted documents, and the Contractor shallrespond in writing to all comments. A meeting may be conducted to clarify and resolve any remaining questionsand issues concerning the comments and responses provided. The Contractor shall prepare a revised version ofthe document for Approval by KTA.

801 The Contractor shall provide an electronic version of all Contractor developed Documentation for KTA review andApproval. Acceptable electronic formats are Microsoft Office 2016 Suite (or higher), unsecured PDF andprofessional CAD applications for Contractor-prepared Documentation.

802

The Contractor shall update Documentation as changes occur through the Implementation Phase (and theMaintenance Phase) and shall maintain a document Submittals list on the electronic document management siteidentifying all versions of documents, the date submitted, the nature of changes and provide relevant updates toKTA as they are published.

803 The Documentation package for all Submittals as applicable shall include all required electronic media to install,operate and maintain the System/Deliverable/document being supplied.

5.4.1. Requirements Traceability Matrix (RTM)

804 Upon completion of the Requirements and Business Rules review process the Contractor shall deliver an RTM thatdetails all the technical and functional Requirements for the Roadway System.

805 The RTM shall build on the specifications documented in the CSWRD and shall capture all user needs identifiedduring the Requirements and Business Rules review process.

806 Upon Approval of the RTM, this document shall be the basis for functional verification of Design, development andtesting.

807 During the Design and development of the Software, the Contractor shall update the RTM to reflect any changes tothe Requirements that have been Approved by KTA.

808 During Design and testing, the RTM shall be used to verify the System compliance to the Contract Requirementsand test procedures.

809 All changes to the System Requirements during the course of the Project shall be tracked through the RTM.

The RTM shall include, but not limited to:a) listing and categorization of all functional Requirements;b) listing and categorization of all Software related technical Requirements;c) identification of the source of all Requirements and related Business Rules;d) identification of the Design section of the SDDD that addresses the Requirement; ande) identification of the test Phase(s) that address(e)s the Requirement.

5.4.2. Business Rules DocumentAs an outcome of the Business Rules workshops and review meetings, the Contractor will provide a Business RulesDocument.

810





No. Requirements

Required Inputs

The Contractor shall submit a Business Rules Document that includes but is not limited to:a) detailed Business Rules for all aspects of the RTCS, including policies and processes developed by the Contractor and Approved by KTA;b) detailed description of all System Configurable options, ranges and thresholds (Configurable within the System or Configurable by Authorized User) for each Business Rule (if applicable);c) categorization of all Business Rules, providing indication for the source of the Business Rule;d) cross-referencing of all Business Rules to the underlying Requirements; ande) System and operational impacts of each Business Rule.

5.4.3. System Detailed Design Document

812

The Contractor shall develop and submit a System Detailed Design Document (SDDD) that describes the Designspecifications of all Hardware and Software provided as part of the RTCS to meet the Approved ContractRequirements. The SDDD shall demonstrate that the Contractor understands the functional, technical andPerformance Requirements of the RTCS and has the processes, Hardware and Software Design in place to providea high-quality and reliable product that meets the Requirements of the Contract.

813 The SDDD shall be clear, well-written and organized into volumes to manage the submission and review process.

814 The SDDD shall include the use of diagrams, figures, tables and examples, and it shall apply to all environments,including primary and secondary production and testing environment.The SDDD shall include but not be limited to:

a) System architecture, including overall System Design concept;b) in-lane Equipment layout for each Tolling Location type, c) placement of the Equipment on the toll gantry;d) lane layout electrical and logic diagrams;e) image processing details;f) Dashboard layouts and Design;g) the Requirements for all peripheral device Interfaces and control; h) Roadside server Design, including sizing and processing calculations;i) storage system Design, including sizing and processing calculations;j) data backup Systems Design, including sizing and processing calculations;k) network sizing and Design details including IP scheme;l) PoP Equipment building and Equipment rack layout and interconnections;m) PoP Equipment building and Equipment rack space Requirements;n) UPS sizing Requirements for the KTA-provided UPS detailing all Equipment on the UPS(s) and their total power Requirements;o) high System availability Design, including Servers, storage, network, database and application;

p) Disaster Recovery Design, including Servers, storage, network, database, data resiliency and application;

q) Hardware dependencies and inter-dependencies;r) detailed primary and secondary locations rack and server placement Design;s) detailed infrastructure Software Design,t) detailed operating systems Design;

811





No. Requirements

Required Inputs

u) detailed peripherals configurations, including Requirements for all peripheral device Interfaces and control;v) all internal System Interfaces;w) all custom developed Software;x) all Software provided by the Contractor or a third-party;y) Software dependencies and inter-dependencies;

z) detailed database Design, schema and data modeling, including sizing and processing calculations;

aa) Entity Relationship Diagram (ERD);bb) data flow diagrams, state diagrams and data queues;cc) Module level descriptions and interaction among various Modules; dd) detailed description to the Module and/or process level for all of the functions according to the functional Requirements of the System;ee) lane logic and vehicle framing Design and rules with illustrations;ff) degraded mode of Operations and impacts of failures on System Operations;gg) transaction audit and pre-processing;hh) transaction processing Design, including sizing and processing calculations;ii) detailed Interface specifications between all Software components;jj) Design of all System Interfaces (both sides of the Interface), including electronic Interface to the RSS and KTA CSC BOS.

kk) detailed data management Design and processes, including summarization, archiving and purging;

ll) all user Interfaces (including reports and screen formats);mm) System data dictionaries;nn) application performance monitoring Design;oo) access/identity security methodology;pp) environmental specifications;qq) specification sheets for all Equipment;rr) complete Bill of Materials, including Hardware, Software and support including Software Licenses and Maintenance agreements; andss) A logical division and an index of all contents within the SDDD.

816 Upon the completion of the Software development, and prior to the start of the Roadway System formal testing,the Contractor shall submit the Final Updated SDDD that includes all changes/clarifications made during theSoftware development and validation phases.

817 The Contractor shall submit an updated SDDD on an annual basis throughout the Contract Term that includes allchanges/clarifications made during the just-completed year.

5.4.4. RTCS System Installation Design Requirements Package

818 The Contractor shall prepare and submit the RTCS System Installation Design Requirements and Documentationpackage to the KTA for review in accordance with the Approved Project Schedule.

815





No. Requirements

Required Inputs

819

Generally speaking, the Contractor’s Design Submittals will not be required to be signed / sealed by a licensedengineer. However, should the Contractor provide custom manufactured infrastructure that is structural in natureor other structure(s) or appurtenances (e.g. Equipment mounting brackets, Equipment arms, etc.) that have thepotential to impact life safety the Contractor shall secure the services of a fully-qualified engineering design firm(s)licensed in Kansas for the purpose of performing engineering design and the preparation of related Plans andDocumentation under the Contract.

820 The Contractor shall develop a half-size (11’’ by 17”) set of drawings providing sufficient and accurate detail toinstall the System components.

821 In addition, the drawing shall contain notes and other detail defining specific processes that cannot be graphicallydepicted. The notes shall also be used to delineate specifications, tolerances, special conditions, or any otherfactor required to install and integrate a fully functional System.The drawings shall include but not be limited to the following:

a) lane geometry and dimensions of actual size and placement of all Roadside Equipment;b) For existing Roadways, details on all existing Equipment, conduits, junction boxes and panels that will be re-used clearly identifying any temporary installations;c) Equipment bracket mounting detail to the mounting arm;d) specifications and tolerances;

e) conduit and cable schedule showing all conduits, cables and wires used for each Tolling Location;

f) placement of in-road components;g) size and depth of loop cuts;h) for concrete pavement, any requirements or Design parameters related to dowel or tie bars;i) loop tolerances (induction, resistance, impedance, Q factor);j) any specific infrastructure limitations (i.e. proximity of rebar);k) any specific requirement of how the loop cable is placed into the cuts;l) all homeruns from loops;m) any cable twist requirements for loop homeruns;n) placement of overhead sensors;o) details describing termination process for each termination;p) lightning and surge suppression system;q) a graphical diagram of the network connectivity and data flow;r) detailed interconnection diagrams for all Systems;s) detailed electrical schematics; and t) detailed communications layout.

5.4.5. Roadway Support System (RSS) Installation Design and Documentation

823 The Contractor shall prepare and submit the RSS Installation Design and Documentation package to KTA for reviewin accordance with the Approved Project Schedule.

824 The Contractor shall develop a half-size set of drawings (11’’ by 17”) providing sufficient and accurate detail toinstall the System components.The drawings shall include but not be limited to the following:

a) detailed interconnection diagrams for all Systems;b) detailed electrical schematics;c) detailed communications layout;

822





No. Requirements

Required Inputs

d) UPS sizing specifications;e) Equipment rack layout, including power panels and connection to the UPS;f) a detailed diagram of the network requirements and connectivity, including IP scheme;g) server set-up and configuration;h) HVAC requirements;i) other RSS Hardware installation and connections; andj) floor loading calculations.

826 The Contractor shall provide the installation Requirements for the Equipment, including all related Plans anddocuments. The Contractor shall certify the installation Requirements provided as accurate and appropriate for itsintended purpose, to the satisfaction and Approval of KTA.

827 The Contractor shall submit Server room drawings that show the location of the Equipment racks for all RSSEquipment at the primary facility. The layout of the Server components, storage devices and communicationEquipment inside the cabinets shall be clearly presented with actual measurements shown.

828 The Contractor shall submit Server room drawings that show the location of the Equipment racks for all RSSEquipment at the secondary facility. The layout of the Server components, storage devices and communicationEquipment inside the cabinets shall be clearly presented with actual measurements shown.

829 The Contractor shall develop and submit to KTA a half-size (11” by 17”) set of drawings, providing sufficient andaccurate detail to install the System components.

830 The Contractor shall submit UPS sizing information for the primary and secondary facilities, detailing all Equipmenton the UPS and their power specifications.

831 The Contractor shall submit detailed network drawings showing all WAN and LAN connections, including allinterface connections and IP addresses for all Equipment on the network.

832 The Contractor shall submit detailed Server configuration instructions, including the configuration of storagedevices, back-up devices and network connectivity.

5.4.6. Quality Assurance Plan

833 The Quality Assurance (QA) Plan that details the Contractor’s QA Program shall be submitted to the KTA for reviewand Approval in accordance with the Approved Project Schedule.

834 The QA Plan shall include the Contractor’s QA Program through planning, Documentation; Design; development;production; purchasing; testing; installation; Commissioning; transition and Acceptance of all Hardware andSoftware provided under this Contract. The Quality Assurance Plan shall describe the Quality Assurance procedures and methodology for the Project,including but not limited to:

a) quality management and organizational structure;b) System Design;c) Software development and defect management;d) installation including civil installation sign-off;e) Equipment purchase, delivery and validation;f) inspection and verification for in-process, final assembly, unit tests and System testing;g) configuration management;h) change management and change control process;i) training and safety;

825

835





No. Requirements

Required Inputs

j) quality management Documentation;k) transition;l) compliance to Contract Requirements;m) quality review and verification; andn) reporting and metrics.

5.4.7. Software Development Plan (SDP)The Contractor shall develop and submit a Software Development Plan (SDP) to KTA for review and Approval inaccordance with the Approved Project Schedule that includes but is not limited to:

a) Documentation of the Software development approach to the application architecture, behavior, architecture, business processes, security and data structures;b) approach System Design and Development;c) development resources and responsibilities, such as Software developers, system engineers, security engineers, test engineers, Quality Assurance and control personnel, configuration management administrator, Documentation specialists and Project management staff;d) describe natural segregation of development areas or teams, such as development of user Interfaces, development of reports, development of the functionality and development of Interfaces;e) Software development standards;f) security standards;

g) Software development methodology, such as use cases, modeling and other development tools;

h) Software development language strategy, platforms and technologies related to both development and Software Maintenance;i) description of the Software Development Life-Cycle and Maintenance;j) approach to segregation of environments (development, testing and deployment) and the number of environments;k) Maintenance of standard and baseline codes and management of major releases;l) gap analysis of baseline code to Contractor Requirements;m) development problem reporting, defect tracking and remediation;n) code reviews and code development standards;o) source control;p) informal and internal testing methodology;q) regression testing and security and vulnerability testing;r) development and integration approach for the major functional modules;s) Software Quality Control processes;t) Software end-user Documentation review and usability;u) development Documentation;v) technical Software code Documentation and standards for all code;w) Software configuration and change management approach and standards;x) samples of detailed Software Documentation for both external and in-line Documentation;y) Software deployment approach, release management and validation; andz) detailed Documentation of the development environment, including enough information that the environment could be completely replicated.

5.4.8. Master Test Plan (MTP)

836





No. Requirements

Required Inputs

837 The Contractor shall provide to KTA, for review, comment and final Approval a Master Test Plan (MTP) inaccordance with the Approved Project Schedule that outlines the scope and testing concepts to be used toadministrator each test identified in the Contract.

838 The MTP shall document the methodology used to validate the Roadway System compliance to the Requirementsand demonstrate the Roadway System satisfies the technical, functional and Performance Requirements of theContract.

839 The Approved Master Test Plan shall be used as the basis for the detailed test procedures that shall be submittedto KTA for review and Approval. The Master Test Plan shall cover all aspects of the RTCS and the RSS testing from initial development throughdeployment, Roadway Acceptance and Project Acceptance, including but not limited to:

a) overall approach to testing;b) approach to each informal and formal testing;c) approach to creation of data set for each test;d) Software test automation tools utilized for each test;e) approach to validating all System Requirements through the testing methodology;f) approach to validating all System Business Rules through the testing methodology;g) describe the entry and exit criteria for each test;h) document the severity and Priority descriptions and levels for each test;i) include a detailed schedule for each test identifying each test activity and resource;j) describe the methodology for testing the Performance Requirements and sample size for each phase of testing;k) describe the methodology for load testing; l) describe the purpose; scope; duration; System resources, and human resources for all tests identified in the Scope of Work and Requirements;m) approach to validating all reporting Requirements;n) approach to end-to-end testing, validation and Reconciliation;o) approach to interface testing and compliance to standards, p) document how defects will be triaged; tracked; reported; resolved, and retested, including tools used to document defects; andq) a set of regression test procedures that will be exercised each time Software changes are made after the Approval of the FAT.

The Contractor shall provide detailed test procedures for KTA’s Approval for each test outlined in theRequirements and Approved MTP, including but not limited:

a) test logistics including test vehicles; drivers and test Equipment (including test Transponders);b) test scenarios;c) detailed test steps with expected outcomes;d) test entry and exit criteria;e) test preparation;f) test data creation;g) periodic status meetings;h) all necessary human resources; andi) all necessary Hardware and Software.

840

841





No. Requirements

Required Inputs

842 KTA’s Approval of any aspect of testing shall not relieve the Contractor of its responsibility to meet the fullRequirements of the Contract.

843 The Contractor shall update the RTM linking every Requirement to a set of test cases to demonstrate theRequirement has been satisfied and which test satisfied the Requirement.

5.4.9. Maintenance PlanThe Contractor shall submit Maintenance Plans listed below that describes how the Contractor plans to facilitateKTA in performing the Maintenance of the RTCS: Roadside Systems, RSS, and all Hardware at the PoP Equipmentbuilding in accordance with the Requirements of the Contract. The Contractor shall have appropriateDocumentation available to all Maintenance and Software Support personnel, as required to perform theirrespective duties.

5.4.9.1. System Maintenance PlanThe System Maintenance Plan defines the approach to Services, staffing and resources to fulfill the SystemMaintenance Requirements. The Plan shall include:

a) organizational structure, organizational chart and job descriptions and responsibilities;b) detailed matrix of responsibilities (KTA and Contractor);c) staffing Plan;d) approach to staffing and training;e) detailed System monitoring Requirements;f) coverage and personnel locations;g) Third-party System support agreements overview;h) schedule of all System Maintenance activities;i) all System Maintenance related communication methods;j) Maintenance procedures, communication protocols and approval processes for System Upgrades, scheduled Maintenance activities, change management and scheduled downtime;k) Maintenance procedures and communications protocols for unscheduled downtime;l) communication protocol for coordination with KTA Operations and third-party entities;m) communication protocol for coordination with KTA’s existing system integrators;n) trouble reporting processes;o) escalation processes;p) Spare parts levels and reorder thresholds, Equipment and Software warranty tracking and return material processes;q) monitoring the MOMS Dashboard;r) monitoring Maintenance performance for compliance to Performance Requirements;s) sample Maintenance reports;t) Equipment obsolescence/replacement/refresh schedule;u) Upgrades to third-party Software and tools;v) process in place to meet Maintenance Performance Requirements; andw) pervasive methodology and activities.

5.4.9.2. Software Maintenance and Warranty PlanSoftware Maintenance and Warranty Plan shall define the approach to Services, staffing and resources to fulfill theSoftware Maintenance and Warranty Requirements including but not limited to:

a) organizational structure, organizational chart and job descriptions and responsibilities;b) detailed matrix of responsibilities (KTA and Contractor);

844





No. Requirements

Required Inputs

c) staffing Plan;d) approach to staffing and training;e) approach to receiving and prioritizing Software defects (bugs);f) reporting, categorization, prioritization, remediation and disposition of Software defects;g) coverage and personnel locations;h) all Software Maintenance related communication methods;

i) Maintenance procedures, communication protocols and approval processes for Software Upgrades, Software releases, testing, scheduled Maintenance activities, change management and scheduled downtime;

j) Maintenance procedures and communications protocols for unscheduled downtime;k) trouble reporting processes;l) escalation processes;m) sample Maintenance reports;n) Software Updates and testing to comply with Interoperability specification changes, and third-party interface changes;o) Software and security Updates, remediation and testing to be compliant to PCI and KTA Audit Requirements; andp) process in place to meet Maintenance Performance Requirements.

5.4.10. Disaster Recovery PlanThe Disaster Recovery Plan (DRP) shall be a comprehensive, documented statement of actions to be taken before,during and after a disaster to protect and recover the information technology data, assets and facilities of theRTCS.

846 The Contractor shall develop and submit a DRP and subsequent DR Procedures that describe the approach, as wellas activities and procedures that take place in the event of a disaster for each element of the RTCS.

The DRP shall document the Contractor’s approach to recovering from a disaster, including but not limited to:

a) events that constitute a disaster and party responsible for declaration of a disaster;b) assessment of disaster risks;c) mitigation of disaster risks;d) preparations in the event of a disaster;e) disaster declaration and DR process to invoke;f) organization chart illustrating DR team members, roles and responsibilities;g) notification contact list, including contact information;h) notification protocol;i) sites and Equipment for DR, presented in a diagram format;j) DR process initiation and completion checklist;k) Software and data replication processes;l) detailed logistical processes for activation of DR site and systems;m) detailed technical processes for activation of DR site and systems;n) detailed procedures for failover and failback of the RSS including a check list for ensuring that it failed over and failed back properly;o) detailed operational functions for activation of DR site; and

847

845





No. Requirements

Required Inputs

p) detailed technical processes for reactivation of primary site (or moving to a new primary site if the original primary site is destroyed), Operations and Systems.

848 The DRP shall be tested no less than annually.

849 The DRP shall include a Business Continuity Plan (BCP) that details the Contractor’s approach to accommodatingthe personnel, Equipment, Systems, network, applications and data components required to ensure theresumption and continuity of critical Roadway System processes. The BCP shall include but not be limited to:

a) Recovery Point Objective (RPO) maximum acceptable amount of data loss for all critical Roadway System Services after an unplanned data-loss incident, expressed as an amount of time;b) Recovery Time Objective (RTO) maximum acceptable amount of time for restoring a critical Roadway System Services and regaining access to data after an unplanned disruption;c) Level of Service (LOS) the combination of throughput and functionality required to sustain Roadway System business Operations;d) detailed description of how site and System security will be maintained to ensure continued compliance with security Requirements; ande) response plan in the event of a security breach or cyber-attack at the roadside network, or either RSS sites in accordance with the Attachment 6: KTA Information Security Overview.

5.4.11. Training Program and Plan

851 The Contractor shall develop and submit a Training Plan for KTA Approval in accordance with the Approved ProjectSchedule that describes the approach to training supervisors; auditors; administrators; end users; Maintenanceand support personnel.

852 The Training Plan shall describe the plan for training new personnel and shall outline the requiredoperational/Maintenance and System knowledge for each position to be gained from the training.

853 For each position/user type, the plan shall include a training instructor guide, training manual and other materialsto be used in training. The Training Plan also shall include a schedule for follow-up training and continuingeducation for staff.

854 The Training Plan shall provide a plan for cross-training staff from other areas of Operations or management forpeak period, emergency or temporary assignments to provide for staff redundancy. The Training Plan also shallinclude the training schedule for regular staff training and continuing education/training.

The Training Plan shall address the following areas including but not limited to:a) overall description of the training program;b) training techniques;c) training delivery schedule;d) names and descriptions of each training class;e) purpose of each training class;f) who should attend the class;g) qualification requirements for trainer;h) minimum qualifications for personnel attending the class;i) duration of the class;j) training materials, including syllabus, schedule, training goals, manuals, guides, other support materials and techniques to be used;k) data preparation, such as users and test transactions;

850

855





No. Requirements

Required Inputs

l) trainee assessment and scoring methods; m) trainee surveys and feedback; n) required Equipment; ando) facility requirements.

856 Courses shall be limited to a maximum of eight (8) hours per day.

857 The Contractor shall be responsible for maintaining a training database baseline and supporting data files that canbe restored at the beginning of each training session.

5.4.12. Third-Party DocumentationThird-Party Documentation includes standard commercial Documentation for third-party provided Hardware,Software, Services and materials.

858 The Contractor shall catalogue all third-party Documentation and include the catalogue with the third-partydocument submissions.

859

The Contractor shall provide and maintain standard, commercially available, updated Documentation for third-party provided Hardware, Software, Services and materials provided under this Contract. This set of third-partyDocumentation shall be retained at the KTA offices for the duration of this Contract and upon termination of theContract.

860 All updated documents shall show the revisions and also include a version of the clean document.

861 An electronic copy of all third-party COTS Hardware and Software installation and user manuals, with updates,shall be provided to KTA. Acceptable electronic formats are Microsoft Office 2016 Suite or higher, unsecured PDFand professional CAD applications.

862 Documentation shall include sufficient detail to describe the configuration of the Software as it was installed bythe Contractor for the RTCS. These should include any customization or modifications made to the Software orconfigurations specific to the KTA environments.

863 The Contractor shall provide an electronic copy of all Hardware and Software installation and user manuals forcustom-developed (non-COTS) third-party products and Services.

5.4.12.1. Third-Party Software DocumentationThe Contractor shall provide third-party Software Documentation, including but not limited to:

a) all user manuals;b) programmer’s reference manuals;c) warranty Documentation;d) installation manuals;e) Interface documents;f) Maintenance manuals; andg) any other information required to utilize the Software, such as the operating System, utilities, programming languages, application Software and communications Software.

865 The third-party Software Documentation shall be provided by the Contractor in a standard and organized format,with appropriate labels, tabs and cross references to allow KTA to easily access and reference information on eachSoftware component on the System.

5.4.12.2. Third-Party Hardware DocumentationThe Contractor shall provide third-party Hardware Documentation, including but not limited to:

a) all technical manuals;b) operator's guides;c) installation guides;

864





No. Requirements

Required Inputs

d) warranty Documentation;e) Hardware reference manuals;f) available options and versions;g) catalogs, components; andh) illustrated parts lists.

867 The Contractor shall provide all third-party Hardware Documentation in a standard and organized format, withappropriate labels, tabs and cross references to allow KTA to easily access and reference Hardware information oneach Equipment component.

868 Third-party Hardware Documentation shall include sufficient detail to describe the configuration of the Hardwareas it was installed by the Contractor for the Roadway System.

5.5. Manual RequirementsVarious manuals shall be provided as described below to allow KTA to understand the Operations of the RTCS,including the Roadside System and RSS. New manuals developed under this Contract that are not standardcommercial catalogs or manuals, shall meet the Requirements set forth in this section.

869 The Contractor shall submit the Project manuals to KTA for review and Approval in accordance with the ApprovedProject Schedule.

870 Whenever possible, all data shall be printed on 8-1/2” x 11” sheets; foldouts shall be 11” x 17”. Each manual shall include, but not be limited to:

a) a title sheet;b) revision history;c) table of contents;d) list of illustrations (if applicable);e) list of reference drawings and Exhibits (if applicable); andf) a parts list (if applicable).

872 All manuals shall have a consistent look and feel and shall be professionally written and presented in clear andorganized fashion.

873 All manuals prepared for KTA under this Contract shall be produced, or editable, using Microsoft Office 2016 Suite(or higher). In addition, electronic copies of manuals shall be provided in native file format and unsecured PDF, ifrequested by KTA.

874 Any special Software required to produce scalable typefaces or other graphs shall be provided by the Contractor aspart of the Documentation for the manuals.

5.5.1. Manual Submissions and Quantities875 The Contractor shall submit electronic copies of the manuals listed in the table below to KTA.

876 All manuals shall be maintained in electronic format in the Contractor’s document management System.

877 The Contractor shall be responsible for producing an additional quantity of the manuals for the Contractor’s use,sufficient to fulfill the Contractor’s Requirements under the Contract.

5.5.2. Manuals to be Submitted5.5.2.1. RTCS System Maintenance Manual

878 The Contractor shall submit RTCS System Maintenance Manual prepared for properly trained technical personnelassigned to the Maintenance of the Hardware and Software installed under this Contract.The Roadway System Maintenance Manual shall document information required to support RoadsideMaintenance and repair activities, including but not limited to:

871

866





No. Requirements

Required Inputs

a) lane Equipment layout for each Tolling Location Type;b) schematics and layouts of the Hardware in the lane cabinets, Equipment racks and the interconnection diagrams; c) parts lists required to service each piece of Hardware installed under this Contract;d) general and detailed description and concepts of lane Operations and functions;e) detailed lane monitoring activities, specialty tools and schedule;f) detailed Software monitoring activities and troubleshooting procedures;g) Maintenance instructions to repair and replace parts and modules;h) mechanical functions and installation of all Hardware;i) listing of all event and error logs;j) testing and basic troubleshooting procedures; and k) Preventative, pervasive and corrective Maintenance procedures.

The RTCS System Maintenance Manual shall document information required to support RSS monitoring, includingbut not limited to:

a) all Dashboards, monitoring screens, notifications and data that needs to be checked;b) listing of all jobs/process, their dependencies and their schedule;c) listing of all folders and directories that need to be checked; d) details related to the activity that needs to be checked;e) frequency of the validations;f) actions to take when results are not as expected;g) notification and escalation process;h) basic troubleshooting procedures; and i) creation of work orders in MOMS.

881 Provide description about the tools and Software for personnel to record the monitoring activity and instructionsto use the tools/Software. The RTCS System Maintenance Manual shall document information required to support RSS Maintenance andrepair activities including but not limited to:

a) detailed Hardware Maintenance activities and schedule;b) detailed database Maintenance activities and schedule;c) detailed Software monitoring activities and schedule;d) detailed monitoring procedures for file transfers and exception handling;e) detailed procedures and processes for all Maintenance activities;f) detailed procedures for backup, archiving and purging of data;g) detailed procedures for testing DR systems;h) detailed schedule for desktop and peripheral preventive Maintenance activities;i) detailed schedule for all preventative Maintenance activities;j) technical contact lists for all external interfaces and KTA system integrators;k) technical contact lists for Hardware and Software providers; andl) details and copies of all third-party System support agreements.

883 Standard service manuals for commercial products used for the Equipment shall be acceptable if they containsufficient information to properly service the Equipment.

882

879

880





No. Requirements

Required Inputs

884 Large-size logic diagrams and mechanical assembly diagrams do not have to be reduced or incorporated into themanuals if these drawings are provided with the manuals and presented in a useable and durable form.

885 Photographic Documentation of Equipment with appropriate labels and call-outs are satisfactory if they containsufficient information to properly identify components, parts and features.

5.5.2.2. Reconciliation and Audit Manual

886 The Reconciliation and Audit Manual shall detail all procedures used to reconcile the System and audit the tollOperations.

887 The reconciliation of electronic transactions and revenue within the System and reconciliation of transactions tothe KTA CSC BOS shall be fully described.

888 Investigation of variances, discrepancies and exceptions processing shall be described.

889 A detailed description of the screens, reports, and functions shall be provided that will allow a qualified auditor toaccess, understand and work with the all financial aspects of the System.

890 A complete description of all audit procedures and a non-technical description of the screens, reports, andfunctions shall be provided.

891 The manual shall contain illustrations and pictorial diagrams to demonstrate the step-by-step Operations requiredfor performing the audit and reconciliation functions.

892 The manual shall contain Quality Control and audit procedures to ensure Systems, Maintenance, and Operationsmeet the Performance Requirements.

893 Samples of all reports shall be included in an attachment to the manual with any specific instructions that may beapplicable to a given report. Reports included in the Submittal shall have correct and accurate data and thismanual shall be used to train the auditors validate the System.

5.5.2.3. Roadway Support System (RSS) Administrators ManualThe Contractor shall provide an RSS Administration Manual that serves as a guide to the overall management andadministration of the RSS and shall include:

a) description of the programs and processes that need to be monitored to ensure that the System is operational;b) procedures for validating tasks, processes and jobs have successfully completed, and errors and exceptions encountered;c) procedures for validating the successful transfer and receipt of files for all interfaces, including RSS and KTA CSC BOS;

d) a listing of all the error codes, their meaning and potential associated problems shall be included in the manual, with a step by step guide to troubleshooting and correcting the problem, including any specialty tools and/or software currently in use to debug, validate and correct the problem;

e) all database Design, and database Maintenance activities required to keep the System operational shall also be clearly documented, including the scheduling of such activities;f) detailed procedures for backup, archiving and purging data;g) detailed schedule for all preventative Maintenance activities;h) technical contact lists for Hardware and Software providers;i) detailed procedures for monitoring System security;j) details and copies of all third-party System support agreements;

894





No. Requirements

Required Inputs

k) ad-hoc reporting tools and use of the tools to generate ad-hoc reports shall be documented; and

l) details of monitoring tools supplied by the Contractor to include but not limited to Roadway and MOMS Dashboards and MOMS.

5.5.2.4. RTCS System User ManualThe Contractor shall develop and provide a comprehensive set of System Documentation and user manuals for theRTCS System users. At a minimum, the Documentation shall include all user and training manuals, screen layouts,reports definitions and data flow diagrams.

895 The Contractor shall develop and submit RTCS System User Manuals to be used by KTA staff to operate the tollcollection System and for training purposes.

896 The Contractor shall develop a separate manual for each job category that details all the processes, proceduresand policies developed by the Contractor and Approved by KTA required to fulfill the Requirements of eachspecific job description.

897 The manual shall include screen images detailing the step-by-step activities that need to be completed in order tofulfill a specific functionality.

898 The manual shall not include any information that could jeopardize the integrity of toll Operations or the tollcollection System.Each User Manual shall include but not be limited to:

a) step-by-step actions to take to complete an operation;b) screen images detailing the step-by-step activities needed to fulfill a specific functionality;c) flowcharts to provide KTA staff a clear understanding of the workflow;

d) all screens, reports and data fields, clearly explained using sample formats applicable to the RSS; and

e) samples of all reports, included in the manual or as an attachment to the manual, with any specific instructions that may apply to a given report.

5.5.3. As-Built DocumentationPrior to KTA Acceptance of the Roadway, As-Built Documentation shall be provided that documents the finalRoadway System Design and implementation.

5.5.3.1. System Detailed Design Document

900 After the Approval of the System Acceptance Test and prior to KTA Acceptance of the RTCS System, the Contractorshall submit the As-Built SDDD that includes all Software and Hardware changes made during the Systemdevelopment, implementation, and testing phases.

901 The Contractor shall submit an electronic copy of the As-Built SDDD.5.5.3.2. As-Built Drawings

902 The Contractor shall provide to KTA a complete set of As-Built Drawings which shall be delivered in electronicformat for all Equipment installed and furnished under this Contract.

903 As material changes are made to the System the Contractor shall update the As-Built Drawings to reflect thecurrent status.The sets shall include, but not be limited to:

a) all schematics;b) logic diagrams;c) layouts;d) wiring diagrams;

899





No. Requirements

Required Inputs

e) interconnection diagrams;f) all attachment Hardware details; g) installation diagrams;h) cable schedule;i) Interface details;j) facility build-out details; andk) network diagrams, so as to provide a complete record of the As-Built status of the Equipment.

905 All drawing revisions to standard commercial assemblies or components of the Equipment shall be included in theAs-Built Drawing set.

906 All As-Built Drawings shall contain a table of contents that shall include a listing of all drawings with headings fordrawing number, drawing title, revisions number and date, and the type of material list, wiring diagram, wire list,specification control drawing, or similar categories.

907 The Contractor shall update the latest drawings with red lines as changes are incorporated during the installationprocess. At the completion of the installation, the Contractor shall gather all red line drawings.

908 The red line drawings shall be verified and incorporated into a final As-Built Drawing package. This final As-BuiltDrawing package shall include all updated installation drawings, shop drawings and sketches, Plans and otherdrawing types that were used to install the Roadway System.

909 All other Documentation used regarding the installation also shall be finalized and submitted as part of the As-BuiltDrawing Submittal.

5.6. Quality Assurance Program The Contractor shall establish and maintain an effective Quality Assurance (QA) program on all aspects of theProject to ensure compliance with the Contract. This Quality Assurance Plan will detail the process and proceduresinstituted by the Contractor to ensure the QA program is in place.

910 The Contractor shall establish and maintain an effective Quality Assurance (QA) program that ensures adequatequality throughout all areas of Project Contract performance.

911 All supplies and Services under this Contract, whether manufactured or performed within the Contractor's facilitiesor at any other source, shall be controlled by the Contractor at all points necessary to ensure conformance to theRequirements of the Contract.

912 Purchase, delivery, verification, testing and assembly of Equipment, Hardware and Software conducted within theContractor’s facilities and on-site shall be controlled completely by the Contractor.

913 Delivery, verification, testing and assembly of Servers and network Equipment conducted within the Contractor’sfacilities shall be controlled completely by the Contractor.

914 The QA program shall provide for the prevention and early detection of discrepancies and for timely and positivecorrective action.

915 The QA program shall include effective Quality Control of purchased materials and Subcontracted Work.

916 The Contractor shall make objective evidence of quality conformance readily available to KTA, and KTA shall havethe right to review and verify the Contractor’s compliance to the process.

5.6.1. Records

917 The Contractor shall maintain records or data essential to providing objective evidence of quality until theexpiration of the Contract and these records shall be made available to KTA upon request.Quality-related records and data shall include but not be limited to:

a) inspection and test results;

904





No. Requirements

Required Inputs

b) records of Subcontractor QA programs;c) cost records pertinent to Acceptance of nonconforming material;d) inspection check-off of KTA work;e) change request Documentation;f) Design reviews and walkthroughs; andg) results of internal and Contractor audits.

919 Records shall be maintained in a manner that allows for easy access and analysis of the status of the overall QAProgram.

5.6.2. Control of Purchase

920 The Contractor shall be responsible for ensuring that all supplies, components, developmental tools, assemblies,subassemblies, and Services procured from Subcontractors and vendors conform to the technical requirementsand Contract.

921 The Contractor shall have a Quality Control process in place for tracking and handling non-conforming Equipmentand products.

922 The Contractor’s responsibility includes the establishment of procedures for the selection of qualified Suppliers. Inselecting qualified Suppliers, the Contractor shall ensure that the Subcontractors and vendors control the qualityof the supplies and Services provided.

5.6.3. Handling, Storage and Delivery

923 The Contractor shall document the approach to assembly of the Equipment, including the location whereEquipment and Systems are assembled.

924 The Contractor’s QA Program shall provide for adequate and documented handling, storage, preservation,packaging, and shipping instructions to protect the quality of products.

925 All KTA assets shall be tracked and entered into the MOMS inventory and the location of each asset shall berecorded.

926 Any unique or special Requirements applicable to procured items shall be delineated in the procurementdocuments. All procurement documents shall be made available to KTA upon request.

5.6.4. Inspection at Subcontractor-Vendor Facilities

927 KTA reserves the right to inspect, at the source, supplies or Services not fabricated or performed within theContractor’s facility.

928 KTA’s inspection shall not constitute Acceptance, nor shall it in any way replace the Contractor’s inspection activityor relieve the Contractor of the responsibility to furnish an acceptable end product.

5.6.5. Access to/Inspection of Contractor's Facilities

929 Upon request, KTA or its designated representative shall have access to the Contractor’s facilities and personnel.

930 This access may be restricted to those portions of the facilities and personnel involved with or who are otherwiseperforming Work under this Contract.

931 Such access shall be for the purpose of inspecting the facilities; verifying progress; inspection of materials; Work-in-progress; or finished goods, or verifying test performance or results.

932 KTA’s inspection shall not constitute Acceptance or Approval, nor shall it in any way replace the Contractor’sinspection activity or relieve the Contractor of the responsibility to furnish an acceptable end product.

5.7. Training

918





No. Requirements

Required Inputs

The Contractor shall provide comprehensive training for all aspects of the RTCS System, including but not limitedto the Operations, System monitoring, problem detection and resolution, reconciliation and audit, andMaintenance of the RTCS. The training program will recognize and incorporate the plan for KTA to operate the tollcollection System. As such KTA Operations staff will be fully trained to successfully perform all aspects of the tollcollection Operations.

5.7.1. Overview of Training Program

933 The Contractor shall be solely responsible for supplying all items necessary, including but not limited to trainingDocumentation, Software, Hardware and any other Equipment required to complete the delivery of the trainingprogram.

934 The Contractor’s program shall include but not be limited to instruction, models/devices, manuals, diagrams andcomponent manuals and catalogs as required.

935 Where practical and useful, the Contractor’s training shall be hands on and use actual Hardware and Software inthe training environment.

936 The Contractor shall produce all training materials and manuals in electronic copies to be used and printed forfuture training sessions.

937 The Contractor shall ensure KTA or their representatives have the right to attend any training sessions and to makerecordings and copies of all training program materials for their use in training new employees.

938 The Contractor shall obtain releases from all employees/Subcontractors to allow unlimited, royalty free use andcopies of PII compliant recordings and provide the same to KTA upon request.

5.7.2. Training Requirements

939

The Contractor shall provide the training courses listed below for KTA’s personnel in accordance with theApproved Training Plan, including but not limited to the provision of all training manuals (including Contractor-provided manuals or relevant portions thereof), guides, training aids, as well as student and instructor work booksaccompanying the courses listed in the sections below.

940 KTA may require additional courses be offered or additional personnel be provided training. The Contractor shallaccommodate these requests to the extent possible with on-site personnel and Documentation that is readilyavailable.

941 Lane level training shall include an overview of toll Operations and lane peripherals and creation of transactiondata and their flow through the System.

942 All RSS training shall include a review and description of each of the appropriate RSS processes and procedureswith actual RSS Software. All students shall have their own workstation and interact directly with the trainingenvironment.

5.7.2.1. System Operation Overview

943 The Contractor shall provide a System operation overview training course for KTA’s management personnel whorequire a general understanding of all aspects of the operation, including but not limited to personnel from seniormanagement, procurement, information technology, marketing and public information.

944 The System Operations training shall include an overview of all aspects of the RTCS and RSS including Systemarchitecture, roadside devices, lane Operations, security access and monitoring, RSS Operations, DVAS, MOMS,System Operations, interface to the KTA CSC BOS network, and any other operational area of the RTCS.





No. Requirements

Required Inputs

945 System Operation Overview training will be conducted in one session with a class size of up to ten (10) people, fora minimum of four (4) hours.

5.7.2.2. Audit and Reconciliation and Roadway Support System (RSS) Operations

946 The Contractor shall provide an audit and reconciliation training course for KTA’s Operations and auditing staff tounderstand all aspects of the operation, particularly those related to audit and reconciliation.

947 Training shall include step-by-step description of the use of the System application to perform the audit andreconciliation functions.

948 Course shall include training all personnel who require a detailed understanding of the Operations of the RSS andhow to access and view information and reports from the System on items such as status, alarms, performance,transactions and revenue.

949 Audit and reconciliation and Operations training will be conducted in one (1) session with a class size of up to five(5) people, for a minimum of four (4) hours.

5.7.2.3. RTCS Maintenance

950 To be attended by all Maintenance personnel and KTA staff who require a detailed understanding of theMaintenance and troubleshooting for the RTCS, including the Roadside System and RSS (Toll Host System, DVAS,MOMS, Image Servers, etc.). Training shall be a combination of classroom and on the job training (OJT).

951 RTCS System Maintenance training will be conducted in two (2) sessions with a class size of up to eight (8) people,for a minimum of forty (40) hours per session.

5.7.2.4. System Monitoring and Roadway Support System (RSS) Administration

952 The Contractor shall provide a System Monitoring and Administration training course for all personnel who requirea detailed understanding of the System monitoring functions and management and administration of theinterfaces, Software, database, applications, configurations and architecture of the RSS.

The Contractor shall provide various training programs that include but are not limited to:a) an in-depth explanation of the System Operations, including all Interfaces, file/data transfers and interconnections;b) functions of the monitoring and tools used to manage monitoring tasks;c) functions of the DVAS;d) functions of the MOMS;e) RSS logs, error logs and processing of exceptions;f) System dataflow and workflow queues;g) explanation of the Dashboard data and analysis;h) special use and monitoring tools; andi) queries and reports.

954 System Monitoring and RSS Administration training will be conducted in one (1) session with a class size of up tofive (5) people, for a minimum of eight (8) hours.

955 The Contractor shall ensure the System monitoring staff are properly trained in the Requirements of monitoringthe RTCS and its uninterrupted Operations.

956 The Contractor shall provide a minimum of one (1) week of classroom and on-the-job training (OJT) to allpersonnel in their respective area of responsibility before such personnel are assigned monitoring duties.

953





No. Requirements

Required Inputs

957 The Contractor shall provide Documentation this initial training has been successfully completed.

958 All System monitoring personnel shall attend the training sessions. KTA’s technical staff also shall attend alltraining sessions.

959

The Contractor shall keep accurate training records on all Maintenance and Software support services personnel.KTA shall be permitted to review and verify Maintenance and Software support services personnel qualificationsand training records at any time. Evidence of completion of training by Contractor personnel shall be provided toKTA upon request.

5.7.3. Training Facilities

960 The Contractor shall conduct training at classroom facilities provided by the Contractor and Approved by KTA.Following review of Contractor’s Training Plan, KTA will confirm that it has the requisite space to accommodate thelevel of effort and physical requirements for each training session.

5.7.4. Scheduling and Preparation for Training

961 It shall be the Contractor’s responsibility to provide sufficient notice to KTA on the types of training it will provideand the timing for each training session. KTA will identify a list of participants that Contractor shall notify toschedule their participation in the training.

962 The Contractor shall perform all scheduling activities and shall make every attempt necessary to accommodate themaximum number of persons for each training session given scheduling conflicts. Contractor shall providesufficient notice to allow participants a reasonable lead time.

963

The Contractor shall notify KTA of the dates or range of dates it would like to hold a training session at the KTAoffices and shall coordinate with the KTA Project Manager and Administrative services staff to arrange the properclassroom setting and computer Hardware and Software are installed and the space configured for each trainingsession.

5.7.5. Training Materials

964 Draft copies of all training materials shall be submitted to KTA for review, comment and Approval, prior to finalprinting of quantities required for training.

965 KTA shall have the right to require additional interim drafts at no additional cost should draft training materialssubmitted not be of adequate quality or have missing or incorrect information.

966 For each course described in the section above, Contractor shall provide the materials listed below.5.7.5.1. Instructor Guides

The Contractor shall provide an instructor guide for each training course. The guide shall include the followingelements:

a) course agenda;b) course objective;c) procedures for managing training session;d) resource and facilities required, including laptops, power and communications requirements;e) detailed lesson plans;f) a description of training aids and items to aid in on the job performance (e.g., where applicable, pocket guides or reference sheets);g) test to be administered to assure satisfactory completion;h) instructions for using any audio-visual support Equipment or materials; andi) student survey to obtain feedback on the training sessions and the training materials.

5.7.5.2. Training Aids/Devices

967





No. Requirements

Required Inputs

968 The Contractor shall provide training aids such as mock-ups, scale models, overhead displays, videodemonstrations, and simulations as are necessary to successfully complete the course agenda and meet the courseobjective.

969 The Contractor shall provide all the System devices and Hardware required for the training.

970 The Contractor shall provide users a way to access training documents, aids and tips in an online, electronicformat.

5.7.5.3. Student WorkbookFor each course, the Contractor shall provide a student workbook, including but not limited to:

a) course agenda;b) course objectives;c) schedule of sessions;d) copies of all overheads and visuals; ande) lesson outlines and summaries.

972 Materials such as Operations and user manuals may be used to supplement the material provided in the studentworkbook.

973 To the extent that the user manuals (and training aids) are appropriately detailed and fit for training purposes theyshall be used for training. If KTA deems they are not sufficiently detailed then supplementary training materialshall be provided.

974 If such material is used appropriate cross-references shall be included in the Student Workbook so as to identifythe complete set of training materials provided to the student.

5.7.6. Training Room Set-up and Software Installation

975 Contractor shall be responsible for loading any special Software required on the classroom computers (provided by the Contractor).

976 It is the Contractor’s responsibility to ensure that the Software is operating as expected on each of the classroomcomputers.

977 It is the Contractor‘s responsibility to ensure that appropriate communications are in place and devices arefunctioning prior to the start of the training.

971





6. ROADWAY SYSTEM TESTING REQUIREMENTS6.1. Roadway System Testing Concept

KTA is planning a phased testing approach to implement the Kansas Turnpike Cashless Tolling System. Theimplementation of other potential Toll Facilities or additional Toll Zones may occur later, if the option is exercised.Given the extended duration of the Project, and the potential differences in the various Roadway System solutionsover time, the Contractor shall conduct the following tests if the option to implement additional optional TollFacilities or Toll Zones is exercised.

Various tests (outlined for reference immediately below and with detailed Requirements in subsequent sections)shall be prepared and conducted by the Contractor for the implementation of the Kansas Turnpike Cashless TollingSystem. Given the extended duration of the Project, and the potential differences in the various Roadway Systemsolutions over time, the Contractor shall repeat the following tests if the option to implement additional TollFacilities or Toll Zones is exercised.

a) Factory Acceptance Test (FAT);b) On-Site Installation Test (OSIT);c) Installation and Commissioning Test (ICT); andd) System Acceptance Test (SAT).

6.1.1. General The Requirements described in this section detail the labor, materials, facility, and support Services necessary totest the RTCS Roadside Systems and RSS and its interface to the KTA CSC BOS.

The Contractor shall prepare and conduct tests that validate adherence to the Requirements that guided its Designand development, compliance to Approved Design and Business Rules, and demonstrate the RTCS functionality.

The Contractor shall be responsible for all aspects of testing performed as part of the Contract and to provide allnecessary resources and facilities to conduct all tests including but not limited to:

a) test support personnel; b) vehicles and drivers;c) test Transponders;d) test facilities; e) test Equipment, tools and safety devices;f) test schedule and test sequence;g) coordination with KTA and existing system integrators;h) coordination of lane closures and MOT; andi) conducting the test.

The Contractor shall to the extent possible, develop and use specialized automated testing Software including butnot limited to:

a) create test scripts;b) control the automated testing;c) exercise all conditions, configurations and scenarios;d) conduct performance testing;e) conduct security testing;f) conduct regression testing;g) compare actual test outcomes to expected outcomes;h) test reporting;

No. Requirements

Required Inputs

978

980

979





No. Requirements

Required Inputs

i) conduct load testing;j) conduct user Interface testing;k) conduct stress testing;l) WAN and LAN traffic testing;m) conduct sustained operational testing; andn) conduct sustained burn-in testing.

981 The Contractor shall provide a defect tracking system, accessible by KTA, to document and track all defectsidentified as part of RTCS testing and any subsequent actions taken to correct and retest those defects.

The defect tracking system shall be capable of the following, including but not limited to:a) rating (severity) defects;b) categorizing defects;c) prioritizing defects;d) logging the date/time the defect was reported;e) subsystems and test cases impacted by the defect;f) the user who reported the defect;g) the erroneous behavior;h) the details on how to reproduce the defect;i) the developers who worked on the defect and corrective action taken;j) date the defect was corrected and formally re-tested;k) life-cycle tracking; andl) reporting.

6.1.2. Master Test Plan (MTP)

983 The Contractor shall provide to KTA, for review, comment and final Approval a MTP that outlines the scope andtesting concepts to be used to validate the RTCS compliance to the Requirements in the Contract and integrationto the KTA CSC BOS.

984 The Approved MTP shall be used as the basis for the detailed test procedures that shall be submitted to KTA forreview and Approval.

985 The MTP shall cover all aspects of the RTCS Roadside and RSS testing from initial development throughdeployment, Roadway System Acceptance and Project Acceptance as defined in the Approved MTP document asdescribed in Section 5.4.8.

6.1.3. Testing Sequence and LogisticsThe Contractor shall obtain Approval from KTA and shall have met the entry conditions prior to start of each testincluding but not limited to:

a) Approval of all predecessor tests;b) Approved test procedures for each individual test;c) Approved test schedule;d) successful closeout of all outstanding pre-test issues;e) successful dry run testing with results provided to KTA;f) Submittal of the latest Approved version of the Requirements Traceability Matrix showing test validation against the Requirements and any applicable Business Rules; andg) confirmation that both the site(s) and System are ready for testing.

982

986





No. Requirements

Required Inputs

987 After the completion of each test, the Contractor shall submit for KTA’s review and Approval a test report thatdocuments the results of the test.The test report shall address the following, including but not limited to:

a) the test summary;b) the results of each test case;c) any anomalies and issues identified;d) the corrective action/resolution of each item;e) the test data; f) calculations and back-up data supporting compliance to Requirements;g) comments provided by KTA; andh) the results of any re-tests necessary to successfully complete each testing phase.

989 KTA shall participate in the testing and witness each test. KTA shall have full access to the test data and results ofthe test.

990 Testing will not be considered complete by KTA until all anomalies and “punch-list” items are closed-out, and thefinal test report is Approved by KTA.Testing shall occur in the following order, subject to KTA’s Approval of the final MTP and shall include the followingtests for each facility transition at a minimum:

a) Factory Acceptance Test (FAT);b) On-Site Installation Test (OSIT);c) Installation and Commissioning Test (ICT); andd) System and Acceptance Test (SAT).

6.2. Factory Acceptance Test (FAT)

992 A separate and distinct FAT shall be conducted by the Contractor for each solution configuration required by eachof the respective Projects and schedules, including the Kansas Turnpike Cashless Tolling System, as well as anypotential future optional additional Cashless Tolling implementations throughout the state.

993 The FAT shall be conducted by the Contractor at the Contractor’s facility in actual lanes with the complete testRTCS System in accordance with the Approved MTP described in Section 5.4.8. detailed testing procedures andProject schedule.

994 The test configuration shall be representative of the Contractor’s Cashless Tolling solution for each laneconfiguration as required by each of the respective Projects.

995 The FAT shall be conducted by the Contractor to verify that all functional elements of the RTCS System are inconformance with the Contract Requirements and the Approved Design.

996 Upon the successful completion of the FAT exit criteria and Approval of the FAT by KTA, the Contractor shall begiven the authorization to move forward to the OSIT at the selected Tolling Locations.The FAT shall validate that the Roadway System Hardware meets the Requirements of the Contract including butnot limited to:

a) 72-hour burn-in testing for customized and assembled Hardware, andb) Certification of Hardware compliance to environmental Requirements.

The FAT shall validate that the Roadside System meets the Requirements of the Contract including but not limitedto:

a) accurate assignment and proper framing of each vehicle through various traffic conditions and test scenarios;

997

991

988





No. Requirements

Required Inputs

b) accurate capture of images and association of Transponders and images to the correct vehicles;c) accurate classification of vehicles, assignment of toll rates and processing of the transaction; d) compliance to accuracy Requirements;e) all exception processing Requirements;f) correct application of Business Rules;g) degraded mode scenarios; h) all device failure conditions;i) rush-hour traffic scenarios;j) redundancy;k) DVAS capabilities; l) throughput and load testing using simulated data;m) interface to the RSS and CEMS; andn) transaction and image reconciliation.

The FAT shall validate that the RSS meets the Requirements of the Contract including but not limited to:a) user interface and compliance to user interface standards; b) facility Dashboard and monitoring;c) Roadway Dashboards;d) RSS functions;e) DVAS capabilities;f) MOMS;g) transaction audit;h) correct application of Business Rules;i) System performance;j) reporting;k) redundancy;l) System loading;m) compliance of RSS interface to Approved ICDs; and n) ALPR/OCR.

6.3. On-Site Installation Test (OSIT)

1000 The OSIT shall be conducted by the Contractor for each lane configuration at the on-site locations identified by KTA in accordance with the Approved MTP, detailed testing procedures and Project schedule.

1001 The OSIT shall verify the full functionality of the RTCS System and its compliance with the Contract Requirementsand the Approved Design in a controlled, on-site environment using transactions created during both liveOperations and when lanes are closed to traffic.

1002 The testing shall not interfere with the existing KTA System.

1003 Before the commencement of OSIT, all Equipment and Software that are required under the Contract shall be inplace, in a production environment and configured for revenue Operations. The RTCS interfaces to the KTA CSCBOS shall be connected to the respective test environments as Approved by KTA.

1004 In order to test the full functionality of the MOMS and System Monitoring during OSIT, all Equipment shall beentered into the System prior to the start of OSIT and the MOMS shall be configured for full Operations.

999

998





No. Requirements

Required Inputs

1005 The Contractor shall test the vehicle throughput and speed Requirements and generate sufficient transactions toprove the System can process transactions accurately and meet the Performance Requirements.

1006 Performance Requirements shall be verified using a sample size Approved by KTA.

The OSIT shall validate that the RTCS meets the Requirements of the Contract including but not limited to:

a) Operations of in-lane Equipment and their ability to report failures to the MOMS including the UPS;

b) normal and exception processing using multi-vehicle traffic;c) multi-lane and multi-vehicle traffic conditions such as rush-hour traffic (“stop-and-go” and “bumper-to-bumper”), vehicle straddling/changing lanes/merging;d) accurate assignment and proper framing of each vehicle;e) accurate capture and correct association of Transponders and images to the correct vehicle;f) accurate classification of vehicles, assignment of toll rates and processing of the transaction;g) transaction processing during Equipment failures and degraded modes of operation;h) Performance Requirements using live traffic and controlled vehicles;i) redundancy;j) receive and process comprehensive and incremental TVL, Hotlist enforcement notification list and toll rate schedules;k) DVAS functionality;l) security access; m) Interoperability using Interoperable test accounts;n) lane Business Rules; o) interface to the RSS and CEMS; andp) interface to the KTA CSC BOS and, if applicable, to a new KTA CSC BOS.

1008 An Audit of the lanes shall be conducted using live traffic to verify that the RTCS is processing vehicles accuratelyand transactions can be reconciled in the System using the Approved audit tools.

The OSIT shall validate that the RSS meets the Requirements of the Contract including but not limited to:

a) functionality of the RSS and MOMS Dashboards shall be verified as it applies to transactions, alarm and failure monitoring;b) all failure conditions;c) user interfaces and toll collection management functions;d) RSS Business Rules;e) reconciliation of transactions and revenue;f) RSS reports; g) Ad-hoc reporting capability;h) accuracy of Performance Reports;i) interface to the facility server (if applicable);j) interface to the KTA CSC BOS including reconciliation;k) interface to the Roadside systems; l) interface to the CEMS;m) conformance with performance, load and stress test Requirements;

1007

1009





No. Requirements

Required Inputs

n) security Requirements;o) System backup Requirements;p) archival and purging Requirements;q) MOMS asset management; failure notification; work order tracking and performance reporting;r) RSS redundancy Requirements; and s) RSS DR Requirements.

As part of the OSIT, an end-to-end testing shall be conducted that validates the following functionality, includingbut not limited to:

a) System’s ability to process and post transactions to the RSS and on to the KTA CSC BOS;

b) The successful transfer of images from the Roadside Systems to the RSS and on to the KTA CSC BOS;

c) Various transaction posting scenarios that verifies the transaction processing, transaction posting, disposition and reconciliation per the Business Rules; and d) the RTCS System is configured for Go-Live.

6.4. Installation and Commissioning Test (ICT)

1011 The ICT shall be conducted by the Contractor on each Toll Zone as a part of the Contractor’s Roadway Systeminstallation in accordance with the Approved MTP, detailed testing procedures and Project schedule.

1012 The ICT shall validate the functionality and operational status of the lanes including installation and configurationof all Equipment and Software. The lane Operations shall be verified end-to-end upon the completion of theinstallation checkout prior to opening the toll lanes and Equipment sites for revenue collection.

1013 During the ICT every piece of in-lane Equipment and its interface to the lane/zone controller shall be verified to befully operational. The lane/zone controller, its interface to the RSS and the security access system shall bevalidated to ensure that the interfaces are in place and the RTCS is ready for revenue collection.

1014 An ICT shall be conducted on the RSS and shall include the interfaces to the KTA CSC BOS. The Contractor shallsupport the possible Commissioning of the RSS prior to the Commissioning of the Roadside Toll Collection System.

1015 A Commissioning test shall be conducted on the RSS and shall include the image server(s) and the interfaces to theKTA CSC BOS.

6.5. RTCS System Acceptance Test (SAT)

1016 The RTCS SAT shall be conducted by the Contractor in accordance with the Approved MTP, detailed testingprocedures and Project schedule after all lanes have been Commissioned in revenue collection.

1017 The SAT shall be conducted upon authorization by KTA to commence such testing. The RTCS shall be observed inlive revenue Operations by the Contractor and KTA for a minimum of two (2) monthly audit cycles.

1018 The objective of the SAT is to ensure that the RTCS System Software and Hardware functions over the test periodwith limited manual intervention in live Operations. It is intended to confirm that the RTCS and the network aresized, tuned and configured correctly and data is processed without interruption or errors.

1019 The RTCS SAT shall validate the interface of the RTCS System to the KTA CSC BOS, and reconcile the transactionsand images end-to-end.

1010





No. Requirements

Required Inputs

During the test period, System accuracy, performance of the System and Operations shall be validated including:

a) all System accuracy Requirements specified in the Contract using representative sample size for each facility under test;b) all Maintenance Performance Requirements;c) all System Performance Requirements;d) a two-hour vehicle audit during AM and PM peak hours for a total of four (4) hours on each lane at each Tolling Location in test;e) transaction processing in accordance with KTA Business Rules;f) correct classification of vehicles and assignment of toll; andg) monitoring of all interfaces for the accurate transfer and processing of all records.

1021 System reliability and auditability shall be verified manually and through tools and reports provided in the System.

1022 Dashboards and reports shall be verified daily for accuracy and reconciled to Operations and interface files. Allexceptions shall be investigated. Queries and detailed reports shall be generated to validate the daily, weekly,monthly, yearly and comparative reports and compared to reports.

1023 The alarms displayed on the MOMS and all interface status notification shall be verified to be accurate.

1024 Failure of the Roadway System to meet a Performance Requirement shall result in the restart of that particular testuntil such time the accuracy Requirements are met.

1025 The RTCS SAT shall be repeated until KTA is satisfied that the RTCS meets the Contract Requirements as set forth inthe Contract.

6.5.1. Project Acceptance

1026 Upon the successful completion of SAT for the RTCS, the closure of all "punch-list" items and completion andsubmission of all Contract required documents as set forth in the Contract, the Contractor shall be given theProject Acceptance as described in the Contract.

6.6. Performance Requirements - TestingThe Contractor shall provide a RTCS that is Designed to meet the accuracy, performance and throughputRequirements set forth in this Scope of Work and Requirements. The testing logistics required to prove adherenceto these Requirements shall be detailed in the MTP and the test procedures as set forth in the Scope of Work andRequirements.

1027

The sample size for each requirement shall be the greater of N = log (1 - C) / log (A); or 20,000 transactions for theOperations test; where:* N = Number in the sample* C = Confidence level* A = AccuracyA value of 95 percent shall be used for the confidence level. Accuracy and confidence levels are expressed asdecimals.

6.6.1. General Accuracy Requirements

1028 The Contractor shall provide a RTCS that meets the accuracy Requirements described below. The Contractor shallvalidate System compliance to the accuracy Requirement by collecting data to the required sample size in livetraffic Operations as described below for each Requirement.

1029 Data collection shall include the use of live traffic and controlled vehicles intermingled with live traffic emulatingnormal Operations as specified below for each Requirement.

1020





No. Requirements

Required Inputs

1030 Prior to the start of testing the System shall be confirmed to be fully operational and ready for testing.Transactions that fail to meet the Requirements shall be reviewed and audited and anomalies investigated.

6.6.2. Transponder Capture Rate

1031

A Transponder mounted in accordance with the manufacturer mounting instructions shall be captured by the AVISystem under all conditions in this Scope of Work and Requirements with an accuracy of 99.9 percent (no morethan ten (10) missed reads or incorrect captures in ten thousand (10,000) equipped vehicle passages).Modifications to this AVI accuracy Requirement may be required based on future implementation decisionsrequired by the AVI System vendor and Approved by the KTA.

1032 This Requirement applies to all facility types and Tolling Locations based upon the Transponder mix collectedduring the testing period for the given sample size. Testing shall require the use of controlled vehicles with known“good” Transponders intermixing with live traffic to create the required sample size.

6.6.3. Transponder Reporting Accuracy

1033 A Transponder that is detected and read by the AVI reader shall be reported to the zone controller with anaccuracy of 100 percent under all conditions described in this Scope of Work and Requirements. Testing shallrequire the use of Transponder reads collected during live traffic Operations.

6.6.4. Vehicle Detection Accuracy

1034 The zone controller shall detect and report all vehicles traveling through the Tolling Location with an accuracy of99.99 percent under all conditions described in this Scope of Work and Requirements. Testing shall require the useof vehicle data collected during live traffic Operations.

6.6.5. Transponder Association Accuracy

1035 Every Transponder that is reported to the zone controller shall be assigned to the correct vehicle with an accuracyof 99.95 percent under all conditions described in this Scope of Work and Requirements. Testing shall require theuse of controlled vehicles intermixing with live traffic.

6.6.6. Vehicle Classification Accuracy

1036

The zone controller shall classify all vehicles traveling through the Tolling Location in accordance with KTAclassification structure for each Toll Facility with an accuracy of 99.8 percent for Cashless Tolling Facilities under allconditions described in this Scope of Work and Requirements. Testing shall require the use of vehicle datacollected during live traffic Operations.

6.6.7. Image Capture Reporting Accuracy

1037 The System shall capture, report and correctly associate an image to the correct vehicle as defined in KTA BusinessRules with an accuracy of 99.95 percent under all conditions described in this Scope of Work and Requirements.Testing shall require the use of vehicle data collected during live traffic Operations.

6.6.8. Overall Image Quality

1038

For images captured for Image-Based Transactions, 99.95 percent of the images that are included in thecalculation, as defined below, shall have a human readable license plate, state jurisdiction and plate type. Forvehicles identified as requiring front plates the front image shall be used. Testing shall require the use of vehicledata collected during live traffic Operations.

6.6.8.1. License Plates Excluded from the Accuracy CalculationsA plate shall be considered excluded from the Accuracy calculation only when:

a) the vehicle has no plate;





No. Requirements

Required Inputs

b) plate is not in the normal camera field of view because it is not mounted in accordance with State laws;

c) the plate is covered by dirt, a trailer hitch, tailgate, or some other material such that the numbers/letters are not human readable; ord) the plate is damaged so that numbers/letters are not human readable.

6.6.9. Transaction Processing Requirements

1040 All transactions generated by the zone controllers in accordance with the above accuracy Requirements shall bereported and transmitted to the RSS with an accuracy of 100 percent under all conditions described in this Scopeof Work and Requirements. Testing shall require the use of vehicle data collected during live traffic Operations.

6.6.10. False Read Processing

1041

The false read processing (example cross lane reads and duplicate reads) shall be less than 0.001 percent of theTransponder transactions under all conditions described in this Scope of Work and Requirements. Testing shallrequire the use of vehicle data collected during live traffic Operations and test results will be verified bymonitoring the KTA CSC BOS reported issues for accurate Account posting.

6.6.11. Image Transmission Requirements

1042 All image-based transactions and images from the RTCS shall be transmitted to the KTA CSC BOS with an accuracyof 100 percent under all conditions described in this Scope of Work and Requirements. Testing shall require theuse of vehicle data collected during live traffic Operations.

6.6.12. AVI Transaction Transmission Requirements

1043 All AVI transactions from the RTCS shall be transmitted to the KTA CSC BOS with an accuracy of 100 percent underall conditions described in this Scope of Work and Requirements. Testing shall require the use of vehicle datacollected during live traffic Operations.

6.6.13. Audit and Reconciliation Requirements

1044 100 percent of the transactions, images generated in the lanes and created on the RTCS shall be auditable andreconcilable through System Reports and the final transmission status and disposition of the transaction to the KTA CSC BOS shall be tracked and reported.

1039





7. MAINTENANCE AND SOFTWARE SUPPORT SERVICES

The Requirements described in this section detail the Hardware Maintenance and Software and AdministrativeSupport Services for the Roadway System. The Hardware Maintenance and Software and Administrative SupportServices (“Maintenance”) include three (3) Tiers of Maintenance responsibilities defined as follows:

Tier 1 Maintenance (provided by KTA):1. Onsite Hardware Maintenance Services for the RTCS Equipment, Infrastructure and Hardware;2. Onsite Network Maintenance Services for the Roadside Toll Collection System;

Tier 2 Maintenance (provided by Contractor):1. Remote Hardware Maintenance Services for the RTCS Equipment, Infrastructure and Hardware;2. Remote Network Maintenance Services for the Roadside Toll Collection System;

Tier 3 Maintenance (provided by Contractor):1. Remote RTCS System, Server and Database Administration Services; and 2. Software Support Services for the RTCS System.

The Contractor shall provide all Maintenance activities associated with the RTCS Maintenance and SoftwareSupport Services throughout the Contract Term as further set forth in this Scope of Work and Requirements and inSection V, Terms and Conditions. After the Project Implementation Phase, all local, onsite Maintenance (includingEquipment, infrastructure, Hardware, and Network services) for the RTCS will be provided by KTA, while all remoteMaintenance (including Equipment, infrastructure, Hardware, and Network services) for the RTCS shall beprovided by the Contractor as defined in Attachment 11: Maintenance Responsibility Matrix. This section focuseson the Maintenance activities required by the Contractor and the coordination of activities to be performed byKTA.

Tolls incurred by the Contractor, including Subcontractors, suppliers and employees driving private vehicles towork on this project may be credited by the KTA per Section 7.0 in Attachment 9: Special Instructions – TrafficControl Restrictions. The Contractor shall provide complete Tier 2 and Tier 3 Maintenance Services for:

1. All Maintenance Work for a base period of up to 7 years, and2. All Maintenance Work for Two (2) Optional 3-year periods.

7.1. Roadway Maintenance Services – General Requirements

1045 Hardware, Software and System Maintenance Services shall be for a period from Acceptance of the RTCS throughthe end of Contract Term (including extensions) as further set forth in Section V, Terms and Conditions with fullwarranties as further set forth therein.

1046

The Contractor shall be responsible for supporting and maintaining the RTCS System for any time period in whichthe System is installed, Commissioned and placed into revenue service but has not passed required testing. TheMaintenance of the RTCS provided under this Contract prior to Acceptance is not included in the term of theMaintenance and Software Support Services. The Contractor shall coordinate all Maintenance activities with KTAduring this period.

1047 The Contractor shall provide a Software License and associated Escrow as further set forth in Section V, Terms andConditions.

No. Requirements

Required Inputs





No. Requirements

Required Inputs

1048

Maintenance shall include all Services required to maintain the System, including Hardware, Equipment, Softwareand components at the required performance levels. KTA shall not be charged any additional amounts beyondthose included in the Approved Price Proposal for all Services related to Maintenance; notwithstanding theforegoing, Force Majeure events shall be as set forth in the Contract as further set forth in Section V, Terms andConditions.

1049 All Equipment mounting Hardware and brackets provided as a part of this Scope of Work and Requirements shallbe included under Maintenance Services and as such shall be warrantied for the life of the Project.

1050 KTA will provide 100 percent of the Tier 1 local, onsite Roadside Toll Collection System and NetworkCommunication (LAN/WAN) Hardware Maintenance Services.

1051 The Contractor shall provide 100 percent of Tier 2 and Tier 3 remote RSS Hardware, Software, Network, Databaseand System Administration Maintenance Services including operating System and Software security Updates andSystem Monitoring in coordination with KTA.

1052 The Services and Work performed under the Contract are considered highly confidential and the Contractorpersonnel shall at all times comply with KTA security and privacy Requirements. Contractor employees shall notdiscuss their Work with unauthorized personnel or any individuals not directly associated with KTA.

7.1.1. RTCS System Warranty Program

1053 The Contractor shall be responsible for the development, implementation and administration of a WarrantyProgram for all Hardware, Contractor developed Software and third-party Software as further set forth in SectionV, Terms and Conditions.

1054

The Contractor shall maintain warranty records and maintain service agreements for all Hardware and third-partySoftware, and shall review and implement Software Upgrades and available patch reports to keep the RoadwaySystem current per the Approved Configuration Management Plan and as further set forth in Section V, Terms andConditions.

7.1.2. RTCS Maintenance and Software Support Services

The Maintenance and Software Support Services shall include monitoring; preventive; pervasive; corrective;security related and emergency Maintenance Services and certain Upgrades and enhancements to be performedon all elements of the RTCS. Payment for Maintenance and Software Support Services on the RTCS for each Phaseof the Project shall commence after Acceptance. The Contractor shall provide the following RTCS Maintenance andSoftware Support Services at the levels defined in this section.

1055 Detailed assignments of Priority levels to incident types shall be in accordance with the Requirements and shall bedefined and Approved during the Design Phase of the Project.

1056 The Contractor shall monitor the System for failures and alarms, and confirm a MOMS work order has beencreated for each failure as defined regardless of Maintenance Level.

1057 The Contractor shall automate the MOMS work order process to the maximum extent possible to anticipate andautomate work orders. If a MOMS work order has not been created, the Contractor shall create a work order inMOMS and assign it to a technician for Maintenance action or troubleshooting.

1058 The Contractor shall monitor MOMS work orders and initiate corrective actions to meet Requirements forresponse to Maintenance events and incidents that are under the Contractor’s responsibility.

1059 The Contractor shall acknowledge and respond to work orders assigned to the Contractor.





No. Requirements

Required Inputs

1060 The Contractor shall perform the necessary Maintenance or coordinate with KTA to perform the necessary Tier 1Maintenance and close the MOMS work order upon confirmation that the failure has been successfully corrected.The Contractor shall notify KTA that the repair action is complete and work order has been closed.

7.1.3. Upgrades and Enhancements1061 The Contractor shall provide in electronic format all patches and Updates made to the System Software.

1062 The Contractor shall provide release notes in electronic format for KTA Approval which shall contain a descriptionfor the need for the System Software or Hardware change and shall include demonstrated successful internaltesting prior to releasing fixes, patches, Updates, Upgrades, or enhancements to production.

1063 The Contractor shall perform change management and configuration management tasks prior to releasing fixes,patches, Updates, Upgrades, or enhancements to production.

1064

Upgrades and enhancements shall be proposed by the Contractor or requested of the Contractor in accordancewith the Change Order/Extra Work process as set forth in Section V, Terms and Conditions. Examples of Upgradesand enhancements include but are not limited to accommodating major changes to standards, statutes, orInteroperability Equipment, or the addition of new Equipment, or functionality providing demonstrable benefits inperformance, costs or productivity.

1065

Software modifications required to Maintain and support the RTCS System as a part of the normal course ofbusiness shall not be considered Upgrades or enhancements paid for by KTA. These modifications include but arenot limited to version changes; configuration or parameter changes; minor changes to Software or code, such aschanges to the existing ICDs; Software modifications required to ensure Roadway System is compliant to existingstandards; and changes for the Contractor’s benefit that improve the Contractor’s ability and efficiency tomaintain and support the RTCS System.

7.1.4. Software Deployment

1066 The Contractor shall provide a reliable, repeatable, and easy-to-deploy method to update the RTCS Software andRSS Software in all lanes and all environments (production, data warehouse, and test environments) as applicable.

1067 The Contractor shall request Approval from KTA prior to deploying any Software to the RTCS and RSSenvironments.

1068 The Contractor deployment request shall include the purpose, risk level of the Update/patch, primary point ofcontact, rollback process, and other relevant information, via a change request form.

1069 The Contractor shall employ and apply industry standards for enterprise-grade Software deployment and shallprovide Software Updates via easy-to-use executable installer files or similar.

1070 The Contractor shall provide a wizard-like method, so all aspects of the Software Update process are encapsulatedin a single automated installation package, avoiding requiring separate manual processes.

1071 The Contractor shall provide an automated means for the installation to be verified ensuring that the versioninstalled includes all appropriate Software elements (such as executable files, configuration files, components,libraries and registry entries) in place.

1072 The Contractor shall provide full logging of the installation process so issues can be investigated.

1073 The Contractor shall provide a seamless rollback feature as part of the Software installer that will automaticallyreverse the installation and restore its original version in the event a fatal error is encountered during theinstallation process.





No. Requirements

Required Inputs

7.1.5. Maintenance Priorities, Response and Repair Times

Response and Repair time is defined as the combined time from when failure occurred or a problem was reportedto when the repair or correction of the failure occurred; the period of time beginning when the failure occurred(failure time) and ending when the fault condition is corrected and returned to normal Operations.

1074 Response and repair times for every Maintenance event shall be recorded in the MOMS and reported and suchreports shall be provided to KTA in accordance with the reporting Requirements of this Scope of Work andRequirements.

1075 The Contractor shall post a weekly schedule identifying personnel and times for remote and on-call Tier 2 and Tier3 Maintenance. KTA Approval is required for any change in Contractor staff. The Contractor shall provide to KTAthe updated active personnel list and contact information when there is a change in personnel.

1076 The Contractor shall post a weekly schedule identifying KTA personnel and times for on-site and on-call Tier 1Maintenance. The Contractor shall coordinate with KTA to update the KTA active personnel list and contactinformation when there is a change in KTA personnel.

1077 Response to calls and repair times shall be determined by Priority as described below. Contractor failure to meetthe response and repair time criteria described below for Tier 2 and Tier 3 Maintenance shall result in monthly feeadjustments as specified in Section 8.

1078 Regardless of coverage, onsite, remote, or on-call service, acknowledgement of receipt of notification of aMaintenance issue or human acknowledgment of a failure shall not exceed thirty (30) minutes after the failurenotification was recorded or problem was reported.

1079 The Priority of failures shall be defined during the Design Phase. Time to respond and complete repair aredetermined by Priority and is defined as below.

Priority 1: Defined as any malfunction or fault that results in the immediate loss of revenue; security breach;closure of lanes outside of KTA lane closure Requirements; hazard to personnel or driving public; loss of audit data;loss of redundancy in any redundant System components; loss of functionality that impacts Interoperable Agenciesor failure that negatively impacts the RTCS or RSS Operations.

a) For Roadside Systems Maintenance this Priority shall have a two (2) hour time to respond and complete repair.b) For RSS Maintenance this Priority shall have a four (4) hour time to respond and complete repair.

Priority 2: Defined as any malfunction or fault that degrades the System performance but not the operationalability of the System. It includes, but is not limited to inaccurate reporting, inability to reconcile revenue or loss ofSystem functionality that impacts access to data.

a) For Roadside Systems Maintenance this Priority shall have a four (4) hour time to respond and complete repair.

b) For RSS Maintenance this Priority shall have an eight (8) hour time to respond and complete repair.

Priority 3: Defined as any action or event that has the potential to result in a malfunction or degrading of theSystem performance, but has not impacted performance and is not anticipated to immediately impactperformance, including, but not limited to loss of redundancy in any redundant System components.

1082

1081

1080





No. Requirements

Required Inputs

a) For Roadside Systems Maintenance this Priority shall have an eight (8) hour time to respond and complete repair.

b) For RSS Maintenance this Priority shall have a twenty-four (24) hour time to respond and complete repair.

1083

Outages and tasks performed under the Approved preventive Maintenance period shall be defined as Priority 4.The System shall be available and fully operational within the Approved time schedule for such activities and uponcompletion of the preventive Maintenance period. Delays and problems associated with not completing scheduledpreventive Maintenance within the window specified may be included in the Performance Requirementcalculations. Any failures generated or resulting from preventive Maintenance activities shall be accounted for asPriorities 1, 2 or 3 and be addressed in accordance with these Requirements.

7.1.6. Notifications

1084 The entry of a problem (either by the System or an Authorized User) into the MOMS or the presence of a failurenotification shall constitute the start of the acknowledgment time for purposes of measuring the Contractor’sacknowledgment time and response/repair time.For purposes of measurement of performance and for the development of Maintenance policy and procedures,notification of System malfunctions, problems and discrepancies may be provided to the Contractor in three (3)different methods, summarized below.

a) Verbal notification: Defined as an in-person notification or telephone call to the Contractor’s designated Maintenance personnel. In all cases, the first conversation with, or notification of the Contractor shall signify the start of the response time for purposes of measuring the Contractor’s response time. All verbal notifications shall be recorded in MOMS by the Contractor.

b) Written notification: Defined as a written description of a problem or condition, typically provided by KTA or its representative. Written notification can be mailed or emailed to the Contractor. The time of receipt of mail or email shall signify the start of the response time for purposes of measuring the Contractor’s response time. All written notifications shall be recorded in MOMS by the Contractor.

c) MOMS notification: Defined as an automatic notification through the MOMS identifying a problem within the Roadway System that is the Maintenance responsibility of the Contractor and sending out an automatic work order message by email or text to a Contractor’s Maintenance staff to respond to the failure. In addition to the Contractor notification, the work order shall be posted on the MOMS and available via reports. The presence of a MOMS notification in the System shall constitute the start of the response time for purposes of measuring the Contractor’s response time.

d) Generation of Alert: Defined as an automatic creation of an Alert identifying a problem within the Roadway System that is the Maintenance responsibility of the Contractor. The generation of the automatic Alert in the System shall constitute the start of the response time for purposes of measuring the Contractor’s response time.

1086 The Contractor shall coordinate with KTA and provide the KTA IMC with any requests for lane closures to addressemergency corrective repairs.

7.1.7. Recording of Maintenance Activities

1082

1085





No. Requirements

Required Inputs

1087 The Contractor and KTA shall utilize the MOMS for initiating the work orders. MOMS shall be utilized for recordingand tracking all Maintenance and Software Support Services performed on the Roadway System. All Equipmentprovided under this Contract shall be tracked through MOMS from the purchase to their disposal.

1088 In all cases the Contractor is responsible for logging all reported Maintenance activities into the MOMS. TheContractor shall also be responsible for documenting all information and issues related to a failure condition,including all actions taken to complete the correction into the MOMS.

1089 The work order shall contain as much information as possible in order for persons other than the technician or hissupervisor to reasonably determine the fault, when it was worked on, the corrective action and any otherinformation pertaining to the individual Maintenance event, including replacement of parts.

1090 All performance metrics shall be recorded and tracked through the MOMS and compliance to PerformanceRequirements shall be validated using MOMS reports.

1091 It is the Contractor’s responsibility to ensure that all Contractor and KTA Maintenance staff has real-time access tothe MOMS and that all the required connections are established and ongoing to ensure that the Maintenance staffhas secure remote access Approved by KTA. Maintenance staff shall be trained in the use of the MOMS.

7.1.8. AuditsThe Contractor shall completely support KTA in any audit activity relating to KTA’s Roadway System or Operations.In addition, the Contractor shall conduct audits in accordance with the Contractor’s Quality Assurance Program. Alldeficiencies identified through the Audit process shall be successfully corrected by the Contractor. These auditsmay include, but are not limited to the following:

a) internal control procedures;b) revenue/transaction reporting;c) financial audit; andd) System processing and performance.

7.1.9. Security Certification

1093

The Contractor shall perform monthly penetration and vulnerability tests that are scheduled in the MOMS, as wellas every time a new Software release is deployed, or new network Equipment is added or replaced to evaluate thesecurity risk to the RTCS, and identifying potential vulnerabilities. KTA IT shall be a party to these security tests andshall be notified in advance of any scheduled tests.

1094 The Contractor is responsible for correcting all RTCS security deficiencies at the Contractor’s cost and ensuringthere are no security risks.

7.1.10. Cooperation with Other Vendors and Providers

1095 The Contractor shall cooperate to the fullest extent with other contractors and third-party vendors in order toensure that the Roadway System operation and Maintenance do not conflict with or cause any deterrent incapability or service to the traveling public, customers, or KTA.

7.2. Maintenance Responsibilities and ServicesThis section details the Contractor’s responsibilities for providing Maintenance Services and associatedcommunications during this time period including but not limited to:

· Roadside Equipment and Infrastructure Maintenance;· System Hardware Maintenance (servers, storage, network switches, firewalls, routers, etc.);· network administration;

1092





No. Requirements

Required Inputs

· System administration;· database administration;· Software support services;· monitoring services;· System security; and· preventive Maintenance.

In delivering the Maintenance Services, the Contractor shall perform the following Services including but notlimited to:

· remote support of the System;· well documented Maintenance schedules and processes;· KTA Approval for all Maintenance Work;· coordination with KTA on all lane closures;· change control and configuration management;· complete 24x7 Maintenance of the System;· ongoing participation with KTA’s staff and involvement in meetings and processes; and· monitoring of an ample spare parts inventory to meet all Performance Requirements.

7.2.1. RTCS Hardware Maintenance and Software Support ServicesThe Requirements in this section describe Hardware Maintenance and Software Support Services.Monitoring and troubleshooting of the Roadside System including but not limited to:

a) Zone/lane controllers;b) AVI System;c) AVDC System;d) ICPS components and controllers;e) ALPR/OCR Software; f) AVI and Image-based transaction alarms; g) DVAS cameras;h) coordination with KTA for inspection, test and repair of cables, wiring and terminations and any item not in compliance with Contract Requirements will be reported to the Contractor and shall be replaced by the Contractor at no cost to KTA unless such failure is considered non-chargeable as described in Section 8.1.8.1 Non-Chargeable Failures;i) all in-lane System electronics and controllers;j) monitoring and Maintenance of the production, data warehouse and test environments;k) monitoring, Updating, and general Maintenance and troubleshooting of LAN communications, network Equipment, and associated devices; andl) all Roadside Contractor and third-party Software.

1097 Performing routine diagnostics on all in-lane peripherals.1098 Performing routine diagnostics on all in-lane subsystems.1099 Remote monitoring of environmental control devices, UPS, generators, and CEMS devices.1100 Inspection and Maintenance of racks, PoP Equipment buildings, and general supporting infrastructure.

1101 Monitoring and Maintenance of the Roadside System Software processes, Operations, and interfaces to the RSSand to the KTA CSC BOS.

1102 Monitoring real-time Roadway Operations screens and Dashboards and responding to issues.

1096





No. Requirements

Required Inputs

Analyzing periodic, daily and weekly trends to identify problems and initiating investigation and subsequentcorrection including but not limited to:

a) high number of transactions without Transponder;b) high number of class mismatch transactions;c) abnormal changes in traffic counts and class;d) high number of exceptions or unusual occurrences;e) transaction exceptions;f) high number of invalid Transponder transactions;g) abnormal changes in Transponder counts and status changes;h) reduced ICPS Automation Rate;i) reduced ICPS Automation Accuracy; andj) high number of rejected images.

7.2.2. Monitoring and System Administration ServicesThe Requirements in this section describe the Monitoring and System Administration Services.

1104

All System administrative functions, if not automated, shall be performed by the Contractor at regular intervals aspart of the System preventive Maintenance Services according to the Approved Maintenance Plan to ensureSystem performance is optimized. All such System administrative functions shall be scheduled as preventiveMaintenance work orders through MOMS and tracked as defined during the Design Phase.

1105 Continuous monitoring of System Operations shall be performed by the Contractor in conjunction with KTA toverify System is functional; security posture is adequate; processes are being executed as scheduled; files aretransmitted as specified, and System is operating to Contract Performance Requirements.

Continuous monitoring of Operations including but not limited to:a) confirming and verifying receipt of all the MOMS messages and Alerts;b) verifying the MOMS is receiving and processing System events and reporting the correct status;c) evaluating sample transactions data for exception;d) confirming data and image transmission to the RSS;e) verifying processes, programs and scheduled jobs are successful;f) reviewing comparative reports to identify System degradation;g) confirming successful transfer of Transponder status list to the lanes;h) reviewing ALPR/OCR processing results and poor quality images;i) monitoring the DVAS video and event data;j) reviewing sample images from each Tolling Location;k) correcting performance issues identified;l) evaluating storage requirements;m) verify time synchronization is occurring as configured and System clocks are not drifting beyond acceptable threshold; andn) reviewing error logs and Alerts.

1107 Provide continuous 24x7 System administration services coverage on the RSS to ensure that it is performing andwill continue to perform at a satisfactory level.

1108 The Contractor support staff shall be available on-call 24x7 to investigate and perform Maintenance for thosefailures escalated to the Contractor.

1103

1106





No. Requirements

Required Inputs

System administration services shall include monitoring and corrective action to ensure System performance is inaccordance with Requirements of this Scope of Work and Requirements. This shall include but is not limited to:

a) a)monitoring RSS Hardware at the primary and secondary locations including servers, storage devices, and backup systems;b) verifying processes, programs, and scheduled jobs are successful;c) all transactions and images are successfully transmitted to the receiving Systems; d) all messages described in the ICD are being successfully exchanged between the RTCS Systems, CEMS, and KTA CSC BOS;e) confirm applications are functional and available to Authorized Users;f) all scheduled reports are successfully generated and available to Authorized Users;g) all processes are functioning, and data and images are moving successfully though the queues;h) all third-party interfaces are functioning and successfully exchanging files;i) scheduling of preventive, corrective and predictive Maintenance activities;

j) any daily, weekly, or periodic Maintenance required to maintain the System at required performance levels (for example: indexing and tuning databases; archiving and purging in accordance with KTA’s retention policy);

k) maintaining and updating records of all Maintenance events and activities in the MOMS; l) third-party Software or firmware Upgrades, as required and to be compliant to security Requirements, including but not limited to, performing security Software Upgrades, database Upgrades, and operating System Upgrades;m) updates to all Software drivers to meet any new standard Operating System Upgrades as they become available and such Updates shall be deployed in accordance with KTA standards;n) updates to Operating System and Software infrastructure in the production, data warehouse and test environments;o) contact with KTA, Operations and contractors regarding System issues, performance, security posture, Software Release and Maintenance scheduling;p) Approved manual actions, adjustments and Updates to the System data based on predefined criteria to correct issues and as Authorized by KTA;

q) facilitate manual retrieval of data from the zone controllers and download of Transponder Validation List and toll rate and schedule files in the event of extended communications failure to be performed by KTA;

r) re-establishment or re-installation of System files, programs and parameters, as required, following a failure or damage to the System and returning lanes to fully operational condition in coordination with KTA;

s) monitoring of error logs and System logs;t) monitoring and management of up-to-date Software backups (all System Software and data); u) installation of new Software and confirmation of successful installation;v) Software configuration;w) Software version control;x) Software license renewals;y) verify time synchronization is occurring as configured and System clocks are not drifting beyond acceptable threshold;

1109





No. Requirements

Required Inputs

z) assisting KTA Operations staff as requested by KTA; aa) troubleshooting Roadway System issues;bb) creation of Ad-hoc reports requested by KTA;cc) generation of queries as requested by KTA; anddd) analysis of data as requested by KTA.

Software Support Services shall include monitoring and corrective action to ensure System performance is inaccordance with Requirements of this Scope of Work and Requirements, to include database management andoperation. This shall include but is not limited to:

a) investigation and analysis of potential errors and exceptions, and taking preventative or corrective action including correcting the problem and reprocessing the data;b) monitoring of notifications, and initiating corrective actions on application programs to meet Requirements;c) development of defect fixes, security fixes, performance fixes and corrections to the Software and Applications as identified during audits;

d) Updates to the RTCS System and application to support Upgrades to Hardware or third-party Software;

e) Updates to the RTCS, RSS, and application to support all changes to Business Rules, lane configurations, and RTCS Configurable parameters, and deploy changes in production;f) Updates to the RTCS System and application to support minor changes to KTA Interoperable Partner ICD and National Interoperability ICD, including the addition of new Interoperable Partners;g) Updates to the RTCS System and application to support changes to continue its compliance to updated security Requirements; andh) Updates to the RTCS System and application to support legislative and statutory changes.

1111 The Contractor shall perform ALPR/OCR Updates as required to support license plate changes for Kansas platesand the next eleven (11) most frequent visitor states license plates as defined in this Scope of Work andRequirements.

1112

As part of the Software Support Services the Contractor shall develop and test Software as required in accordancewith KTA's Change Order process to accommodate corrective action and changes to Business Rules. Scope shallinclude provision of evidence packages detailing changes for KTA’s review and Approval, installation of newSoftware and confirmation of successful installation.

1113 The Contractor shall monitor all network alerts and alarms, as well as detect intrusion attempts and preventintrusions.

1114 The Contractor shall Upgrade and Update the network security and provide the required Software and monitoringtools to ensure the RTCS System is always in compliance with the most recent penetration and vulnerability testRequirements.

7.2.3. Interoperability RequirementsThe Contractor shall support the following KTA Interoperable Partner and National Interoperability activities asrequired by KTA. Activities include but are not limited to:

a) support KTA Interoperable Partners and National Interoperability Agency testing as requested; b) support substantial changes to the System to meet major modifications to KTA Interoperable Partners and National Interoperability specifications; and c) be compliant with the latest published KTA Interoperable Partners and National Interoperable specifications for the duration of the Contract.

1110

1115





No. Requirements

Required Inputs

7.2.4. Updates to Maintenance Plan and Other Maintenance Related Documentation

1116

The Contractor shall periodically update the Maintenance Plan and other Maintenance Documentation to reflectany changes to the policies or procedures developed by the Contractor and Approved by KTA for the RoadwaySystem Maintenance Services. The Maintenance Plan shall be updated and submitted for review and Approval onan annual basis or as required by KTA on a less frequent basis. However, sections of the Maintenance Plan or itsAppendices shall be submitted for review and Approval as the changes are identified. A version update sheet shallbe included with the Maintenance Plan, and the Maintenance Plan on file shall have the most recent version fromthe configuration management database. A final Submittal of the Maintenance Plan and other MaintenanceDocumentation shall be provided at the end of the Contract Term.

1117 The Contractor shall provide Documentation in electronic format including all patches, Updates, andenhancements made to the System Software (third-party and Contractor) after Acceptance.

7.2.5. Types of Maintenance 7.2.5.1. Preventive Maintenance

1118 The Contractor shall provide and perform remote Tier 1 Preventive Maintenance and coordinate with KTA toperform onsite Tier 1 Preventative Maintenance on the Roadside System Hardware, RSS Hardware, Contractor LANcommunications Equipment and Software in accordance with the Approved Preventive Maintenance Plan.

1119

KTA will inspect all Contractor installed Equipment, both major components and support components (fans,cables, connectors, cabinets, Equipment racks, storage units) that constitute the Roadway System and shall makesuch repairs; cleaning; adjustments, and replacements of components as necessary to maintain the Equipment innormal operating condition in coordination with the Contractor and in accordance with the Approved PreventiveMaintenance Plan.

1120 The Contractor shall provide an Approved Preventive Maintenance Plan which includes a schedule of allpreventative Maintenance activities requiring lane closures for the upcoming month at least five (5) Business Daysbefore the beginning of the month.

1121 The Contractor shall provide changes to the Approved Preventive Maintenance Plan schedule as soon as changesbecome known due to weather, contractor availability, or any other reason.

1122

In addition to required ongoing Contractor monitoring, the servers and data processing units shall be periodicallychecked by the Contractor to verify that storage space is not reaching limits, disks are not fragmented or damaged,Software being used is of latest version per the configuration management and data is being processed andtransferred in an appropriate manner.

1123 Transaction and image processing volumes and times shall be monitored by the Contractor and Systems optimizedfor performance with KTA Approval.

1124 Report generation times, System access times, and System response time shall be monitored by the Contractor toensure performance meets the Contractual Requirements.

1125 The Contractor shall include all Equipment and Systems as part of the preventive Maintenance in accordance withthe original Equipment manufacturer’s guidelines. Any variations or exceptions shall be noted by the Contractorand Approved in advance by KTA.

1126 Preventive Maintenance shall be performed by the Contractor during the normal working hours whenMaintenance technicians are scheduled to be on-site. KTA Approved diagnostic aids, tools and Equipment toperform preventive Maintenance Equipment analysis shall be provided by the Contractor, as necessary.





No. Requirements

Required Inputs

1127 Preventive Maintenance requiring lane closure shall be scheduled by the Contractor for off-peak travel periods;evenings; Saturdays, and Sundays and coordinated with KTA, so that the Work shall not interfere with normaltraffic flow, unless otherwise Approved by KTA.

1128

The Contractor shall provide a preventive Maintenance schedule, to be Approved by KTA, as part of theMaintenance Plan. The schedule shall detail the preventive Maintenance to be performed on each Equipment item and System. The schedule shall provide a description of the Work to be performed, expected duration and thefrequency.

1129

The preventive Maintenance schedule shall be entered by the Contractor into the MOMS and work orders shall beautomatically created to Alert Contractor staff of required preventive Maintenance. Failure of the Contractor toperform required preventive Maintenance in accordance with the Approved schedule shall result in monthly feeadjustments, as specified below in the Maintenance Performance Requirements.

7.2.5.2. Predictive Maintenance

1130

The Contractor shall establish a predictive Maintenance program by which failure analysis can be determined byidentifying potential failures through the MOMS records or data analysis. The failure analysis shall take intoaccount either or both specific components and sub-systems. This information shall then be used to investigateand correct problems and failures that could disrupt toll collection Operations. Examples include the image quality,Image Toll (I-Toll) rate, and reader handshakes.

1131 The Contractor shall maintain all failure analysis Documentation on site and provide the information, includingcharts or other analysis tools, and shall submit the analysis as part of its monthly report.

7.2.5.3. Pervasive Maintenance

1132

The Contractor shall establish a pervasive Maintenance program by which failure analysis can be determined byidentifying continuing or repetitive failures through the MOMS records. The failure analysis shall take into accounteither or both specific components and sub-systems. This information shall then be used to investigate and correctproblems and failures that continue to occur on a particular item of Equipment, sub-system, or component.

1133 The Contractor shall maintain all failure analysis Documentation on site and provide the information, includingcharts or other analysis tools, and shall submit the analysis as part of its monthly report.

7.2.5.4. Corrective Maintenance

All Work performed by the Contractor to correct problems to meet the Requirements of the Contract or Softwaredefects shall be considered as corrective Maintenance. Such problems include but are not limited to:

a) failure of subsystem functions;b) problems identified by the users, including KTA staff, and customers; c) interface issues; d) failure of processes and programs; e) data reconciliation issues; f) report issues;g) application failures;h) toll System network issues;i) inadequate security posture;j) degraded System or component performance; andk) non-conforming availability or MTBF.

1134





No. Requirements

Required Inputs

1135 KTA shall be notified before any corrective Maintenance is performed.

1136 Notwithstanding the foregoing, for repeated failure of Equipment, components, or Systems, the Contractor shallundertake an investigation. If the problem is determined by KTA to be a Pervasive Defect, the Contractor shall beresponsible for resolution as set forth in Section V, Terms and Conditions.

7.2.6. Maintenance Coverage

1137 The Contractor shall provide continuous (24x7) coverage for all monitoring and Maintenance-related activitiessufficient to meet the Performance Requirements of the Contract.

7.2.7. Spare PartsKTA will provide a storage location for the storage of the Roadway System spare parts.

1138 During the Maintenance Phase, KTA will be responsible for the inventory of all spare parts at the storage facilityand will account for all spare parts and shall provide safeguards against theft, damage, or loss of the spare parts.

1139 The spares facility and storage area shall be secured and connected to an up-to-date security network System withalarm notification monitored by KTA. KTA will have full and unrestricted access to the Maintenance and or storagefacility.

7.2.7.1. Spare Parts Inventory Management

1140

KTA will be responsible for the Maintenance of an adequate spare parts inventory during the Maintenance Phase.The Contractor is responsible for monitoring and identifying the existing spare parts inventory, ordering spareparts as required in coordination with KTA, and proposing the quantity needed to maintain the requiredperformance.

1141 The Contractor shall, on a quarterly basis, update and recommend a spare part quantity to be maintained in orderto support the RTCS System functionality and operational readiness.

1142

The Contractor shall be responsible for purchasing and replenishing spare parts inventories to the levels requiredto meet the Performance Requirements. Contractor’s failure to purchase or replenish the spare parts orconsumables to levels necessary to meet the Performance Requirements is not an excusable failure and will notrelieve the Contractor from Performance Requirements or any associated liquidated or actual damages resultingfrom the non-performance.

1143 During the Contract Term, the Contractor shall be responsible for coordinating with KTA for the purchasing of allspare parts and miscellaneous repair items and consumable materials necessary to maintain the RTCS System atthe performance levels specified in the Contract.

7.2.7.2. Spare Part Inventory and Tracking

1144 The Contractor shall be responsible for recording the inventory into the MOMS, monitoring the inventory quantityand ensuring that the inventory is maintained to the levels required by the Contract.

1145 The Contractor shall keep accurate records of all parts entering and leaving inventory including but not limited totime and date part was dispensed, and the location within the RTCS System where the part was dispatched andused.

1146

The Contractor shall also be responsible for tracking of all warranty replacement for Contractor providedEquipment through a Returned Material Authorization (RMA) process. If the replaced part is under warranty, thepart shall be immediately replaced with a new part. If the replaced part is out of warranty, the Contractor shallmake every effort to repair the replaced item to a usable status and place the part back into spares inventory.





No. Requirements

Required Inputs

1147 If the Contractor is unable to repair the part, a new part shall be purchased and placed into spares inventory. Thedetails of the repair efforts, including problem; status; inventory, and repair disposition shall be included in theMOMS inventory and repair database.

7.2.7.3. Procurement and Control of Spare Parts

1148 Thirty (30) Calendar Days prior to placing the RTCS System in revenue collection the Contractor shall havepurchased and have on hand at KTA facilities the agreed upon inventory of spare parts, including at a minimumspares equivalent to two (2) Tolling Locations (four (4) Toll Zones) of Equipment for Cashless Tolling facilities.

1149 The spare parts shall be purchased on behalf of KTA and shall be owned by KTA in a manner to ensure that KTAreceives the maximum benefit from any warranties associated with the spare parts.

1150

The Contractor shall cooperate with and assist KTA to ensure that all spare parts, Equipment and other KTA ownedproperty, which is stored or otherwise located on the Contractor’s property, or in Contractor controlled space,shall not be subject to any risk of being confiscated, claimed, attached, withheld by a landlord, creditor, or similarrisk.

1151

The Contractor shall label/tag all Equipment identifying it as the property of KTA with a KTA specific part or controlnumber and barcode. All spare parts and consumables shall be maintained by the Contractor free and clear of anyliens and encumbrances of any kind. KTA shall have the right to inspect the spares and consumables inventoryupon request.

Provide the capability to enter new inventory items to MOMS via several methods, including but not limited to:

a) manually;b) file upload; andc) barcode (scanner).

1153 Any spare parts that are lost or damaged due to the negligence, intentional act, or omission of the Contractor or itsemployees, Subcontractors, Agents, or invitees shall be replaced by the Contractor at its sole cost.

1154 KTA will have responsibility for storage of spare parts, and the Contractor shall deliver all spare parts to KTA forstorage after receipt of reasonable Notice from KTA prior to the start of the Maintenance Phase.

7.2.8. Repair Depot

1155 The Contractor shall be responsible for providing and staffing a repair depot for the return and repair of RTCSSystem components.

1156 The Contractor shall be responsible for repairing failed RTCS System components and returning them to the spareparts inventory.

1157 Failed components shall be tracked by the Contractor utilizing MOMS, including final resolution. Componenttracking shall include but not be limited to receipt, repair date/information, replace reason, and date of return.

1158 The Contractor shall indicate the details of the repairs performed on any components. This shall include but not belimited to boards and connectors replaced.

1159

If the replaced part is under Warranty, the part shall be immediately replaced with a new part by the Contractor. Ifthe replaced part is out of Warranty, the Contractor shall make every effort to repair the replaced item to a usablestatus and place the part back into spares inventory. Except for pervasive defects, for out of Warrantycomponents, the Contractor shall document why the component could not be repaired and advise KTA that a newspare must be ordered.

1152





No. Requirements

Required Inputs

7.2.9. Annual System Certification

At the end of Year 1 Maintenance, the Contractor shall conduct an annual System-wide Certification that shallinclude tuning of the lanes (including optional annual or less frequent AVI System Certification performed by theAVI Vendor at the request of KTA), Maintenance of the servers and database, and general System check-out. Uponthe completion of the System-wide Certification, the Contractor shall conduct a Certification test similar to theRTCS System Acceptance Test for a duration sufficient to collect the requisite sample size to validate SystemPerformance Requirements. Discrepancies under the control of the Contractor shall be corrected by the Contractorat no additional charge to KTA.

1160 A sample size of 10,000 transactions shall be used to validate each accuracy Requirement. Data shall be collectedfrom all lanes at each Tolling Location.

1161 DVAS recordings shall be performed for a two-hour period in each lane at each Tolling Location and compared tothe transactions to validate vehicle detection accuracy.

1162 A 100 percent end-to-end audit of the System shall be performed for a seven (7) day period to validate transactionand reconciliation Requirements.

1163 Certification reports shall be submitted to KTA for Approval documenting the results of the annual Certification.

7.2.10. Emergency Response ManagementThe Contractor shall have an emergency response management Plan Approved by KTA and the Contractor shallfollow the procedures set forth in this Plan when an emergency situation is invoked.

1164 The Contractor shall immediately respond to any emergency situation and repair the System, as notified by KTA orotherwise, that may arise that has already or could potentially damage the Roadway System. The Contractor shallbe prepared to put forth all necessary resources to divert or correct an emergency condition.

Such emergency conditions shall be handled in accordance with the policies and procedures established by KTA.The following are a few examples of emergency conditions:

a) weather related;b) vehicle accident;c) conditions that invoke the DRP;d) third-party (power outage or communication failure);e) vandalism that causes parts of the Roadway System to be inoperable; andf) detection of security breaches, discovered vulnerabilities and activities that pose a security threat to the toll collection System.

7.2.11. Roadway Support System (RSS) Disaster Recovery (DR)

1166 The Contractor shall perform DR procedures in accordance with the Approved DRP in the event of a disaster andreturn the RSS to a fully operational condition.

1167 The Contractor shall test the DR procedures on a yearly basis during the Contract Term to validate that they arefunctioning per the Design. KTA shall witness the test and the Contractor shall provide a report outlining the test,test results and any anomalies encountered for KTA’s review and Approval.

1168 The Contractor shall address any issues encountered from the yearly DR testing.7.2.12. Incident and Revenue Loss Reporting

1169 The Contractor shall immediately notify KTA of any incident or event whereby the potential or actual loss ofrevenue occurred or could potentially occur. The Contractor shall take immediate action to rectify the conditionand return the Roadway System to normal functioning.

1165





No. Requirements

Required Inputs

1170 A Monthly Incident Report shall be provided by the Contractor that includes a breakdown of lost transaction dataand revenue for each incident. If the condition is determined to be due to the fault of the Contractor, damagesshall be assessed in accordance with the terms of the Contract.

7.2.13. Maintenance Staffing, Materials and Training7.2.13.1. Maintenance Staffing Requirements

The Contractor shall be responsible for maintaining an adequate level of technical staff to perform Maintenanceand Software Support Services on the Roadway System. The Contractor shall ensure that sufficient staffing isavailable to cover all Maintenance activities identified in this Scope of Work and Requirements at all times butparticularly during the following periods:

a) Weekends;b) Holidays;c) personnel on vacation/sick time;d) after regular scheduled Work hours (on call); ande) unexpected emergency or crisis.

The Contractor shall provide personnel to perform the following functions. It shall be the Contractor’sresponsibility to staff at appropriate levels to meet the Requirements, using the Maintenance Plan as the guidelinefor staffing levels and full job descriptions:

a) Maintenance Management / Maintenance Coordinator: The Contractor’s Maintenance Management responsibilities include all Maintenance Coordinator business dealings with the Contractor Project Manager. Responsibilities include single point of contact for all Work-related issues, including System problems, material issues, or Contractor personnel issues. Maintenance Coordinator responsibilities also include support and coordination with KTA Maintenance staff to ensure that Systems are properly functioning and that all local and remote Maintenance and repair Work are properly performed and documented.

b) Monitoring Staff: The monitoring functions shall include the support for the monitoring of the System Operations and ensuring that systems are properly functioning. Additionally, the monitoring staff shall coordinate with KTA in confirming the Maintenance and repair Work are properly performed.

c) Remote Maintenance Technical Staff: Responsibilities include responding to Maintenance activities, Alerts and work orders and coordinating with KTA Maintenance staff for field level preventive Maintenance. Maintenance technicians shall be qualified to troubleshoot Maintenance problems and identify the source of the problem.d) Network Engineering: Network Administration shall include the configuration and Maintenance of the network systems and communications network.

e) Database Administration: Database administration shall include management of the servers and databases. The database administration shall cover all aspects of the System database and ensure the database is optimized for peak performance. The responsibilities include the configuration and operation of the System database and generation of database queries as requested by KTA and other support personnel.

1171

1172





No. Requirements

Required Inputs

f) Systems Engineering: Responsibilities include the configuration and monitoring of all System processing and verifying that all Operations and processes are occurring as scheduled. All MOMS alarms relating to process failures shall be investigated and resolved by the System engineering staff. Systems engineering responsibilities also include ensuring the proper configuration of all servers and coordinating all server Maintenance. System engineering responsibilities also include identifying issues, communicating with the System Software personnel and coordinating resolution of the problem. All user-related problems (application Software) shall also be handled by the System engineering personnel.

g) Software Technical Staff: Responsibilities include responding to Maintenance activities, Alerts and work orders and resolution of Software problems. Software technical staff shall be qualified to troubleshoot Maintenance problems, identify the source of the problem and correct the problem.h) Administrative Staff: Responsibilities include support of the Contractor’s Maintenance organization for the performance of Maintenance functions and to provide adequate phone and administrative support at the remote Maintenance management facility.

7.2.13.2. Tools and Materials

1173

The Contractor shall provide all test Equipment, tools and support including but not limited to monitoring tools,smart phones, laptops, and any other items required for the Maintenance and Software Support staff to performtheir Tier 2 and Tier 3 Maintenance activities. All such devices shall have adequate and up-to-date securitySoftware and be Approved by KTA IT before they are used on the RTCS System network. All required testEquipment, tools and Software tools shall be on site (as required) and in adequate supply, with all requiredpersonnel trained on their use. All test Equipment shall be standard units that are capable of achieving themeasurement they are intended to make. KTA will acquire their own tools and test equipment for their Tier 1Maintenance in coordination with the Contractor’s recommendations based on the above requirements.

7.2.13.3. Training Program

1174

The Contractor shall ensure that Maintenance and Software services staff is properly trained for Requirements ofmaintaining the System. The Contractor shall provide a minimum of two (2) weeks of classroom and On the JobTraining (OJT) to all personnel in their respective area of responsibility before such personnel are assignedMaintenance duties.

1175 During the System Implementation Phase, and prior to System Acceptance and the start of Year 1 Maintenance,KTA Maintenance and technical staff will shadow the Contractor staff and the Contractor shall provide OJT to theKTA Maintenance staff.

1176 The Contractor shall provide personal identity information (PII) training to all personnel Approved to work on theProject who has access to secure and personal information.

1177 The Contractor shall provide trained, qualified technical staff to support the Maintenance and Software SupportServices described in the Scope of Work and Requirements. It is the Contractor’s sole responsibility to developtraining necessary to successfully perform all of the Maintenance actions required to keep the System operational.

1178

The Contractor shall complete all required training and Certifications prior to performing actual Maintenance andSoftware Support Services within a revenue collection environment. In the event changes or modifications aremade to the System Equipment or configuration, supplemental training shall be accomplished prior to the actualservice date for the changes or modifications.





No. Requirements

Required Inputs

1179 Training shall include the Contractor’s safety standards and guidelines and applicable KTA policies and procedures.

1180 The Contractor shall provide Documentation that this initial training has been successfully completed.

The Contractor shall institute various training programs that shall include but not be limited to the following:

a) a thorough understanding and operating knowledge of the MOMS is required of all Maintenance personnel;b) an in depth understanding of the Roadway System and Operations, including all Equipment, Software, interfaces, file transfers and interconnections;c) use of Maintenance Documentation such as Maintenance manuals; drawings; vendor manuals, and parts list;d) functions of the System monitoring tools used to manage the System monitoring tasks;e) preventive Maintenance of all Systems and sub-systems;f) troubleshooting; diagnostics; repair, testing, and Maintenance follow up;g) System logs, errors logs and processing of exceptions;h) System dataflow and workflow queues;i) review of the Dashboard data and analysis;j) discussion on the areas of responsibility;k) special use Maintenance and monitoring tools; andl) queries and reports.

1182 All System Maintenance and Software Support personnel shall attend the appropriate training sessions. KTA staffshall be notified of and invited to attend any or all training sessions two (2) weeks in advance of the training.

1183 All System Maintenance and Software Support personnel shall be trained on scheduling, work assignments,escalation process, transportation requirements and communications;The Contractor shall provide training offered by vendors and original equipment manufacturer (OEM) for Systemcomponents where available and required to properly operate, maintain, test and repair such Equipment andSoftware. Such training shall include but not be limited to:

a) ICPS Equipment;b) AVI Equipment;c) AVDC System;d) lane peripherals devices;e) DVAS;f) MOMS;g) network components and Software provided by the Contractor;h) security Software and security tests;i) storage area network (SAN);j) databases; andk) servers.

7.2.13.4. Training Materials and Ongoing Education

1185 Training material shall consist of Maintenance manuals, vendor manuals and any other Documentation thatprovides for the efficient and effective Maintenance of the System and its components.

1184

1181





No. Requirements

Required Inputs

1186

The Contractor shall hold regular meetings with KTA technical personnel to update Maintenance procedures, bringproposed System changes to the attention of the technical staff and discuss Maintenance issues identified in thefield. The Contractor shall provide KTA with the meeting schedule so that the appropriate KTA staff can attendthese meetings.

1187 KTA shall have the right to make recordings and copies of all training program materials. The Contractor shallprovide releases from all employees/contractors to allow unlimited, royalty free use and copies of recordings.

7.2.13.5. System Documentation

1188 The Contractor shall have appropriate System Documentation available to all Maintenance and Software Supportpersonnel as required to perform their respective duties.

1189

The Contractor shall update the System Documentation to reflect any changes to the System Approved by KTA. Aversion update sheet shall be included with the System Documentation, and the Documentation on file shall havethe most recent version from the configuration management database. A complete submission of the SystemDocumentation shall be made every two (2) years that reflects all Approved changes to date.

7.2.13.6. Training Records

1190 The Contractor shall keep accurate training records on all Contractor and KTA Maintenance personnel. KTA shall bepermitted to audit Maintenance personnel qualifications and training records at any time. Evidence of completionof training by Contractor and KTA Maintenance personnel shall be provided to KTA upon request.

7.2.14. SafetyThe Contractor shall adhere to all applicable safety standards and guidelines for working on or around energizedEquipment and in a Maintenance environment including but not limited to the following:

a) KTA safety procedures and guidelines; b) OSHA (Occupational Safety and Health Administration);c) NEMA (National Electrical Manufacturers Association);d) NEC (National Electrical Code);e) FHWA (Federal Highway Administration); andf) any other local, State, or Federal ordinance, procedure, or guideline that provides for a safe operation and working environment.

7.2.15. Security

1192 All Contractor personnel shall be subject to appropriate security and background checks to the satisfaction of KTA.The Contractor shall obtain written Approval from KTA for all service personnel and each Contractor personnelshall be required to sign an acceptable use agreement.

1193

Contractor’s personnel shall be issued KTA identification badges and shall wear such identification badges at alltimes when on KTA property. Use of such identification badges for purposes other than Work associated with theContract will result in termination of the employee from the Contract and possible other legal or disciplinaryaction.

1194

The Services and Work performed under the Contract are considered highly confidential and the Contractorpersonnel shall at all times comply with applicable current computer and data industry standards with regard todata and information security. All employees of the Contractor shall not discuss their KTA-related Work withunauthorized personnel, or any individuals not directly associated with KTA.

1191





No. Requirements

Required Inputs

1195 KTA will identify and designate a primary point of contact for the Contractor. Under most circumstances, theContractor will limit communication with KTA authorized staff and to KTA’s designated point of contact unlessotherwise directed by KTA.

1196 Discussion by the Contractor of any Services or Work performed under the Contract with the media, in oralpresentations, in written publications, or in any other form, not related to this Contract shall be Approved inadvance by KTA.

7.2.16. Confidentiality

1197 The Contractor shall keep all information regarding its activities pursuant to this Contract confidential and willcommunicate such information only with authorized KTA personnel or designated representatives.

1198 The Contractor personnel shall be required to sign a Non-Disclosure Agreement (NDA) on an annual basis. Theupdated NDA forms shall be submitted with the annual updated Maintenance Plan Documentation.

7.2.17. Maintenance of Traffic (MOT) During the Maintenance Phase

1199 After System Acceptance, KTA will perform all Maintenance of Traffic associated with the System MaintenancePhase. The Contractor shall develop as a part of the Maintenance Plan, an MOT procedure for Approval by KTA.

1200 KTA will adhere to the Approved MOT Plan when setting up, working under MOT and restoring lanes to traffic. Alllane closures shall also be coordinated in advance with the KTA IMC.

7.2.18. Maintenance and Software Support Records

1201 The Contractor shall maintain current, complete and accurate Maintenance and Software Service records for allMaintenance and Software Support Services activities and shall retain for the Contract Term.

1202 KTA shall have access to all Maintenance and Software Service records at any time for review and audit, uponreasonable Notice. The Contractor shall provide monthly reports generated in the System that permits KTA toevaluate Contractor’s Maintenance performance.

1203 The Contractor’s Maintenance Coordinator shall institute procedures that make sure Maintenance staff enterscomplete information into the MOMS before closing a work order or trouble ticket.

1204 All preventive, pervasive and predictive Maintenance activities shall be reported in the same manner as correctiveor emergency Maintenance activities by the Contractor. The information shall be contained on the MOMS andshall be made available through various MOMS reports.

7.2.19. Maintenance Summary Reports

1205 The Contractor shall provide the Maintenance summary reports to KTA on a monthly basis in advance of theMonthly Maintenance and Invoice Review Meeting that shall be scheduled and managed by the Contractor. Theformat of the Monthly reports shall be Approved by KTA and included in the Maintenance Plan.

1206 The Contractor shall provide an annual Executive Summary report to KTA that summarizes the Contractor’sperformance for the Maintenance Year. The format of the Executive Summary reports shall be Approved by KTAand included in the Maintenance Plan.Maintenance summary reports shall also be readily available on-demand through the System in detail or summaryformat to KTA authorized personnel via the network on a daily, weekly, or other time period basis determined byKTA. The Maintenance summary report shall include but not be limited to:





No. Requirements

Required Inputs

a) a summary of the Contractor’s performance for the month under review noting all accomplishments and deficiencies; b) all Maintenance and System Performance Reports that show Contractor’s compliance to Maintenance Performance Requirements; c) detailed listing of failures and the impacted subsystems where Contractor’s and System performance for the month were not in compliance with the Performance Requirements;

d) any exceptions the Contractor believes are non-chargeable failures that Contractor is not responsible for;

e) detailed list of parts replaced as a result of Maintenance actions, with an identification of warranty versus non-warranty replacement;f) status of removed parts and Equipment with an aging status for parts under repair or replacement (serial numbers, being repaired in Maintenance shop, purchase replacement part);g) trend analysis for repetitive failure;h) status of spare parts inventory; i) staffing report detailing positions and staff hours worked; j) staff performance trends; k) Software and firmware releases implemented;l) major Maintenance activities that occurred and are scheduled to occur;m) incidents that invoked emergency response or resulted in loss of toll revenue; andn) summary of work order, Software defects and trouble tickets by Priority and category.

1207





8. PERFORMANCE REQUIREMENTS – MAINTENANCE AND OPERATIONSThe Contractor shall provide a RTCS that is designed to meet the Requirements set forth in this Scope of Work andRequirements during Maintenance and Operations.

The KTA requires the Contractor to continuously maintain and operate the RTCS in accordance with the standardsof performance identified in these Performance Requirements and further, that the Contractor fully meet thesePerformance Requirements, beginning with the first month of Maintenance and Operations. In addition, as part ofthe System Acceptance Test the Contractor shall validate that the RTCS meets the standards of performanceidentified in these Performance Requirements.

KTA intends to focus on the outcomes from the RTCS by minimizing the number of Performance Requirements tobe tracked, monitored and reported while still maintaining a high confidence in the RTCS performance. This isdone by closely aligning performance measurement to the timely transmission of accurate and CompleteTransactions to the KTA Back Office System and availability of the RTCS instead of focusing on the intermediatesteps in the process.

The Contractor’s performance will be monitored by the KTA and shall be rated based on the Contractor’s ability tomeet these Performance Requirements. The Contractor shall use the Approved measurement and reportingmethods developed collaboratively with the KTA during the Design Phase, to report on the Contractor’sperformance against these Performance Requirements. These Performance Requirements reflect the minimum tolerable performance expected of the Contractor to avoidunnecessary impact to the KTA, customers or the general public.

The KTA will utilize a points-based performance scorecard to track the Contractor’s compliance with thePerformance Requirements. If the Contractor fails to meet these Performance Requirements, the KTA will assessnon-compliance points for each failure. Non-compliance points will be summed, the total of which will determineany performance adjustments to be made to the Contractor’s monthly invoice as further detailed below. TheContractor is also subject to direct damages for actual revenue loss.

The Contractor shall use best efforts to minimize the impacts that result from failure to meet the PerformanceRequirements, regardless of whether invoice adjustments are made. Furthermore, the Contractor shall takecorrective action to immediately remedy any failures to meet the Performance Requirements and provide aCorrective Action Plan (CAP) to the KTA for Approval that documents the corrective action taken to prevent futurereoccurrence of the problem associated with the non-compliance.

A summary of the RTCS Performance Requirements is provided in Table 3-3 including measurement frequency andnon-compliance points for each Performance Requirement. Additional detailed information about thePerformance Requirements is provided in the subsequent sections.

8.1. General Performance RequirementsThe Contractor shall be required to meet all Operational Performance Requirements detailed herein and as part ofthe Monthly Invoice provide reports that show compliance to the defined Performance Requirements includingdetails of failures that resulted in the non-compliance.

1208 The Contractor shall Design, implement, Maintain and Operate the RTCS to meet the Performance Requirementsspecified herein.

1209 The Contractor shall facilitate performance monitoring by reporting performance in clearly measurable and easy tounderstand terms and reports.

No. Requirements

Required Inputs





No. Requirements

Required Inputs

1210 The KTA will conduct a review of the Contractor’s performance on a monthly basis, utilizing a combination ofreports generated by the System, including MOMS, and other Approved reports provided by the Contractor, asdetermined by the KTA to be necessary.

1211 The Contractor shall immediately notify the KTA of any failure observed by the Contractor whereby actual loss ofrevenue occurred or the potential for losses exist.

1212

If resolution of any failure is under the Contractor’s control and/or responsibility, the Contractor shall take actionto correct the failure condition and return the RTCS to normal functioning in accordance with the Contract. If thefailure condition is determined to be due to the Contractor’s fault and it results in failure to meet the PerformanceRequirements, the KTA will assess non-compliance points for each failure as described in this Performance Sectionand may be subject to other remedies in accordance with the Contract.

8.1.1. Performance MeasurementPerformance will be measured in categories that align with the primary functions of the RTCS. These categoriesare:

• Availability• Operations

Each of these categories represents a group of functions within the RTCS and each function includes individual KeyPerformance Indicators (KPIs), which will be used to measure the Contractor’s performance in meeting thePerformance Requirements.

The specific method of measuring the Contractor’s performance will vary depending on the KPI being measured,but will generally be measured against the Performance Requirement on a monthly basis. Regardless of how a KPIis measured, the Contractor shall provide reporting for all performance measures monthly.

The amount by which the KPI is missed matters in determining how well the RTCS is performing so the non-compliance points for a particular failure are increased as the deviation from the KPI increases. For example, theCashless Tolling lane is required to be available 99.95 percent of the time and the actual availability was measuredto be 99.85 percent. The Contractor would be assessed 1 non-compliance point. If the availability was measuredto be 99 percent, the Contractor would have been assessed 10 non-compliance points.

Table 3-3 provides a summary of the KPIs for the Contractor. A detailed description of each KPI and its associatedPerformance Requirement is provided in the subsequent sections.

8.1.2. Performance Scorecard

Each KPI is assigned a weighted point value as shown in the above Table 3-3. The value of the non-compliancepoints (“points”) assigned depends on the severity of the failure and its potential impact on the KTA’s business.

The Contractor shall Design and develop Performance measurement reports including the Monthly PerformanceScorecard. An example of a monthly Performance Scorecard is provided in Table 3-4. Failure to comply with thePerformance Requirement for each KPI will result in the KPI’s associated non-compliance points being applied tothe Contractor’s Monthly Performance Scorecard. If the accumulated non-compliance points reach a specifiedthreshold, the Contractor’s invoice for the month will be adjusted by a percentage of the total invoice value, asshown in Table 3-5.

8.1.3. Non-Compliance Performance Adjustments





No. Requirements

Required Inputs

The Contractor’s performance score shall be generated and determined each month by adding the points assessedfor non-compliance in each performance category as described above. A performance adjustment will be made tothe monthly invoice in each month that the Contractor exceeds the allowable number of non-compliance points.The maximum monthly adjustment amount that may be made by the KTA to the Contractor’s monthly invoice is 25percent.

8.1.4. EscalationNon-compliance points will accrue as follows:The first month that a specific Performance Requirement is not met will result in the assessment of the initial valueof the non-compliance points assigned in Table 3-5.

• If a specific Performance Requirement is not met again for a second consecutive month, the non-compliance points will be double the points assessed for all failures of that Performance Requirement for that month.

• If a specific Performance Requirement is not met again for a third consecutive month (and for subsequent consecutive non-compliant months thereafter), the non-compliance points will be set at quadruple the points assessed for all failures of that Performance Requirement for that month (and assessed quadruple the points for any subsequent non-compliant months.)

8.1.5. Direct DamagesThe Contractor may be charged Direct Damages related to Performance Requirement failures as defined in theContract Documents.

8.1.6. KTA Identified Anomolies and Research RequestsIn addition to the Contractor’s monitoring of the RTCS performance, the KTA will also review System andperformance data and perform tests as deemed necessary. The KTA may identify data which may indicate a failureto meet one (1) or more of the performance standards. As a result of the KTA’s activities, the KTA may requestthat the Contractor research and/or provide additional data, identify the extent of the problem or explanationrelated to anomalies or trends identified by the KTA.

1213 The Contractor shall respond and fulfill the KTA’s requests for research, analysis and/or explanation and providefeedback/report within not less than one (1) week or not more than one (1) month as agreed to by the KTA.

8.1.7. Corrective Actions

Failure to meet a Performance Requirement does not relieve the Contractor of the requirement to complete theactivity associated with the Performance Requirement. The Contractor shall identify the failure condition, takeimmediate action to remedy the condition and ensure that corrective action is taken to prevent repeated failuresin the future. This will be documented in a Corrective Action Plan (CAP). For example, if the Contractor fails tocompletely and accurately transmit the transactions to the KTA CSC BOS within the time required by thePerformance Requirement, the transactions must still be completely and accurately transmitted and theContractor must identify the root cause of the failure, identify the extent of the problem and provide a plan toprevent future occurrences.

1214

Any failure to meet a Performance Requirement that requires the completion of a specific action(s), which is notcompleted in accordance with the Requirement, does not relieve the Contractor of the responsibility to perform inaccordance with the RTCS Requirements. The required specific action(s) must be completed within forty-eight (48)hours. For example, if the Contractor fails to transmit all transaction files to the KTA within two (2) hours, the filesmust still be sent to the KTA.





No. Requirements

Required Inputs

1215 The Contractor shall develop a CAP for each failure to meet a Performance Requirement identifying the rootcause(s) and providing a plan to rectify the current situation, if applicable, and prevent future occurrences.

1216 The CAP provided by the Contractor shall be in a format Approved by the KTA.

1217 The Contractor shall submit a CAP for each failure to meet a Performance Standard for KTA’s review and Approval.Until the KTA Approves the CAP the failure shall not be considered resolved.

The CAP shall identify the subsystem(s), component(s), processes and activities associated with the failure to meeta Performance Requirement in sufficient detail to allow the KTA to understand the issue and why the proposedsolution will prevent future occurrences. The RTCS elements include but are not limited to the elements below:

a) Vehicle Throughput Rate;b) Transponder Capture Rate;c) Transponder Reporting Accuracy;d) Vehicle Detection Accuracy;e) Transponder Association Accuracy;f) Vehicle Classification Accuracy;g) Image Capture Reporting Accuracy;h) License Plate Extraction (ALPR/OCR) Accuracy;i) Image Quality;j) Assignment of the Correct Toll to the Transaction;k) Transaction Processing Requirements;l) False Read Processing;m) Image Transaction Transmission Requirements;n) AVI Transaction Transmission Requirement; ando) Toll Facility Speed Accuracy.

8.1.8. Non-Chargeable and Chargeable FailuresFor purposes of calculating Performance Requirements, chargeable and non-chargeable failures are defined asfollows:

• Non-Chargeable Failures are those failures identified in the following section. Non-compliance points will not be assessed for non-chargeable failures.• Chargeable Failures are any failures not specifically identified as non-chargeable. Non-compliance points will be assessed for chargeable failures.

8.1.8.1. Non-Chargeable FailuresNon-chargeable failures shall include:

a) Force Majeure, as defined in the Contract Documents;b) vandalism;c) failure of a test facility or test instrumentation;d) System component failures caused by externally applied stress conditions outside of the Requirements of this Scope of Work and Requirements;e) System component failures caused by environmental or operating conditions outside of the Requirements of this Scope of Work and Requirements;

f) normal operating adjustments as allowed in the Test Procedure or Maintenance Plan, as applicable;

1218

1219





No. Requirements

Required Inputs

g) failures where the KTA has Approved to waive a chargeable failure in advance; andh) failures that are customer or KTA user induced, or are caused by a Third-Party Service Provider not under the Contractor’s control as determined by the KTA.

8.1.8.2. Chargeable Failures1220 Chargeable failures shall include any failures not specifically identified as non-chargeable.8.1.9. Acknowledgement of All Priority Events

1221 The Contractor shall acknowledge receipt of all Priority events within thirty (30) minutes of failure/eventnotification.

1222 For the purposes of assessing monthly fee adjustments, 95 percent of failure or Priority events shall beacknowledged within thirty (30) minutes of receipt.

1223 The Contractor may be assessed a monthly fee adjustment of $250 if the acknowledgment percent is below the 95percent threshold every month for every Priority event not acknowledged within the time frame specified in theseRequirements.

8.1.10. Time to Respond and Repair (TTRR) for Tier 2 and Tier 3 MaintenanceThe Contractor shall respond to and complete repair of Priority 1 failures/events as follows:

a) Roadside Systems: respond and complete repair within two (2) hours of failure/event notification.

b) RSS: respond and complete repair within four (4) hours of failure/event notification.

1225 The Contractor may be assessed monthly fee adjustments of $100 per occurrence for every additional delay of one(1) hour to respond and complete repair of Priority 1 failures/events.The Contractor shall respond to and complete repair of Priority 2 failure/events as follows:

a) Roadside Systems: respond and complete repair within four (4) hours of failure/event notification.

b) RSS: respond and complete repair within eight (8) hours of failure/event notification.

1227 The Contractor may be assessed monthly fee adjustments of $100 per occurrence for every additional delay of two(2) hours to respond and complete repair of Priority 2 failures/events.The Contractor shall respond to and complete repair of Priority 3 failures/events as follows:

a) Roadside Systems: respond and complete repair within eight (8) hours of failure/event notification.

b) RSS: respond and complete repair within twenty-four (24) hours of failure/event notification.

1229 The Contractor may be assessed monthly fee adjustments of $100 per occurrence for every additional delay of two(2) hours to respond and complete repair of Priority 3 failures/events.

8.1.11. Mean Time Between Failure (MTBF)The RTCS shall be required to meet specific minimum duration Requirements for components and subsystems incontinuous operation. This time requirement is defined as the MTBF. Although the Contractor will not be chargednon-compliance points for not meeting the specified MTBF, the Contractor shall report on the MTBF each month.Many Equipment failures cause the Contractor to not meet one or more of the Performance Requirementsresulting in non-compliance points.

1230 The Contractor shall provide all third-party MTBF on individual components to be used in the System. 1231 The Contractor shall report on the MTBF for all components of the RTCS each month.

MTBF Requirements for all components of the RTCS shall meet the MTBF as specified below:a) Redundant Zone Controller - 20,000 hoursb) Automatic Vehicle Identification (AVI) System - 20,000 hours

1224

1226

1228





No. Requirements

Required Inputs

c) Automatic Vehicle Detection/Classification (AVDC) System - 20,000 hoursd) Image Capture & Processing System (ICPS) - 20,000 hourse) RTCS Servers - 50,000 hoursf) Network Devices - 50,000 hours

1233 The reliability of the System components shall be calculated based on the following MTBF calculation:MTBF = # units x test period (hours)/# failures

8.1.12. Performance Reporting

The Contractor shall provide the KTA a Monthly RTCS Performance Report package that includes the Contractor’sPerformance Reports and Monthly Scorecard. The Contractor’s Performance Report package will include a seriesof reports detailing the Contractor’s performance against each Performance Requirement and details related tothe failure events that resulted in the non-compliance. The Contractor’s Performance Report package shall containall information necessary for the KTA to verify the Contractor performance as reported by the Contractor.

1234 The Contractor shall describe in detail how the performance against a Requirement will be tracked, tested andreported, identifying specific reports and data elements. In the case of a KPI which cannot be tracked by theSystem, the form of manual tracking or testing must be described and included in the Maintenance Plan.

1235 The Contractor shall prepare and submit to the KTA the Performance Report package on an agreed-upon day eachmonth as defined in these Requirements.

1236

The Performance Report package shall include a Performance Scorecard calculating the non-compliance pointsassessed that month, if applicable, a series of reports, one (1) per Performance Requirement detailing theContractor’s performance against the Requirement that month supporting the Scorecard for each KPI, and ahistorical report detailing the Contractor’s performance against each Requirement for the most recent twelve (12)months. See Section 2.1.16.5 for details on these reports. Copies of all CAPs related to failures for that monthmust be Approved and included.

1237 The Contractor shall provide the required Performance Report package to the KTA before an invoice will beconsidered for payment.

1238 Performance reporting by the Contractor and any associated adjustments related to Performance Requirementsshall begin for the period beginning on the first day of the Maintenance Phase and shall continue for the durationof the Contract.

8.2. RTCS Performance Requirement Details

These KPIs are based on performance that is measured in calendar hours, Days and minutes as applicable. Anyissues outside of the Contractor’s control that affects its ability to meet a KPI should be noted, documentedappropriately with sufficient detail, and discussed as part of Monthly RTCS Performance Reviews.

The KTA places a great deal of importance on the controls the Contractor has in place for the RTCS and theeffectiveness of those controls. The KTA will monitor the Contractor’s performance for compliance with thePerformance Requirements. The Contractor will be required to meet all RTCS Performance Requirements asdetailed in these Requirements.

8.2.1. Cashless Tolling Lane Availability

1232





No. Requirements

Required Inputs

Tolls are collected 24 hours a day, 7 Days a week and as such the Cashless Tolling Lanes must achieve a high degreeof availability. The Cashless Tolling Lane is viewed as a function; a combination of Hardware and Software thatbuilds accurate and Complete Transactions. This Requirement will measure the function; thus, if one of tworedundant components are not working, yet the component still performs the function as Approved in Design, itwould not be counted against availability.

Each Cashless Tolling Lane with all of its subsystems properly functioning and available to collect revenue and sendrequired transactions and images to the RSS 99.95% of the time excluding scheduled and Approved Maintenance. Availability shall be calculated based on the following calculation: Availability = 1- (chargeable downtime min / (minutes in period-exception min in period))

a) System reporting detailing the Cashless Tolling Lane availability along with MOMS and help desk tickets, work orders and feedback from customers, Back Office staff, KTA staff and consultants will be utilized to identify availability failures.

b) For any month in which ALL components of the Cashless Tolling Toll Zones are not fully available and operational at least 99.95 percent of the time excluding scheduled and Approved Maintenance, the Contractor shall be assessed 1.0 point for each 0.1 percent or portion thereof below the Performance Requirement.

8.2.2. Roadway Support System (RSS) Availability

Tolls are collected 24 hours a day, 7 Days a week and as such the RSS must achieve a high degree of availability.

The RSS with all of its devices, Software, applications and processes properly functioning and available to theAuthorized Users, successfully transmitting transactions to the KTA CSC BOS, and communicating with the in-lanesystems 99.95% of the time excluding scheduled and Approved Maintenance.Availability shall be calculated based on the following calculation: Availability = 1- (chargeable downtime min / (minutes in period-exception min in period))

a) System reporting detailing the RSS availability along with MOMS and help desk tickets, work orders and feedback from customers, Back Office staff, KTA staff and consultants will be utilized to identify availability failures.b) For any month in which ALL components of the RSS are not fully available and operational at least 99.95 percent of the time excluding scheduled and Approved Maintenance, the Contractor shall be assessed 1.0 point for each 0.1 percent or portion thereof below the Performance Requirement.

8.2.3. AVI Transaction Complete and Timely Transmission

The Contractor shall be responsible for the timely processing of AVI transactions. The KTA is subject to statutoryrequirements and is obligated to customers and Interoperable Agencies to process all transactions in a timelymanner. The Contractor’s performance in this area has a direct impact on the KTA’s revenue stream.

The Contractor shall process and transmit 99.995 percent of AVI transactions to the KTA CSC BOS within 120minutes after the vehicle travels through the tolling point.

a) System reporting detailing the transaction date/time and the date/time that the transaction was acknowledged by the Back Office will be compared to a matching Back Office Report.

1240

1241

1239





No. Requirements

Required Inputs

b) The Back Office validates the transactions to ensure that they comply with the agreed upon ICD and transactions which do not meet the ICD will be rejected as incomplete or inaccurate. Unless a rejected transaction is corrected and resubmitted within the 120 minutes transmission period, they will not meet this KPI.

1242 For any month in which 99.995 percent of the AVI transactions are not transmitted in accordance with theApproved ICD to the Back Office, the Contractor shall be assessed 1.0 point for each 0.1 percent or portion thereofbelow the Performance Requirement.

8.2.4. Image Transaction Complete and Timely Transmission

The Contractor shall be responsible for the timely processing of image transactions. The KTA are subject tostatutory requirements and are obligated to customers and Interoperable Agencies to process all transactions in atimely manner. The Contractor’s performance in this area has a direct impact on the KTA’s revenue stream.

The Contractor shall process and transmit 99.995 percent of image transactions to the KTA CSC BOS within 120minutes after the vehicle travels through the tolling point. This includes providing all image processing todetermine the required plate data.

a) System reporting detailing the transaction date/time and the date/time that the transaction was acknowledged by the Back Office will be compared to a matching Back Office Report.b) The Back Office validates the transactions to ensure that they comply with the agreed upon ICD and transactions which do not meet the ICD will be rejected as incomplete or inaccurate. Unless a rejected transaction is corrected and resubmitted within the 120 minutes transmission period, they will not meet this KPI.

1244 For any month in which 99.995 percent of the image transactions are not transmitted in accordance with theApproved ICD to the Back Office, the Contractor shall be assessed 1.0 point for each 0.1 percent or portion thereofbelow the Performance Requirement.

8.2.5. AVI Transaction AccuracyThe Contractor shall be required to accurately process AVI transactions. Errors can result in the customers beingcharged at the incorrect rate or necessitate image review when the Transponder is not read; such errors impactcustomer service, public perception and KTA costs.

The Contractor shall correctly build the AVI transaction including all the necessary transaction componentsincorporating inputs from the AVI, AVDC, and ICPS subsystems to accurately identify the toll amount, the type oftransaction, the vehicle class and all other required transaction data. The Contractor shall also correctly determineand provide the plate information for all images using ALPR/OCR and other techniques to maximize accuracy andincrease automation. Ultimately the AVI transaction shall be correctly associated to the vehicle with the correctAVI transponder, classification, toll amount, front and rear images, and ALPR/OCR license plate data (including thelicense plate number, state jurisdiction, plate type, and associated ALPR/OCR confidence levels).

a) Feedback from customers, Back Office staff, KTA staff and consultants will be utilized to identify inaccurate or incomplete transactions.b) KTA will utilize trend reporting to identify transactions, or lanes/zones for further review to identify possibly inaccurate transactions.c) Transactions rejected by the Back Office will also be reviewed for accuracy.d) KTA may conduct unannounced controlled testing in live traffic as well.

1245

1241

1243





No. Requirements

Required Inputs

1246 For any month in which the AVI transaction accuracy falls below 99.90 percent, the Contractor shall be assessed1.0 point for each 0.1 percent or portion thereof below the Performance Requirement.

8.2.6. Image Transaction AccuracyThe Contractor shall be required to accurately process image transactions. Errors in identified images can result inthe incorrect customer being billed and/or the customer being billed at the incorrect rate; such errors impactcustomer service and public perception.

The Contractor shall correctly build the image transaction including all the necessary transaction componentsincorporating inputs from the AVI (if applicable), AVDC and ICPS subsystems to accurately identify the toll amount,the type of transaction, the vehicle class and all other required transaction data. The Contractor shall alsocorrectly determine and provide the plate information for all images using ALPR/OCR and other techniques tomaximize accuracy and increase automation. Ultimately the image transaction shall contain the correctclassification, toll amount, front and rear images, and correct license plate data (including the license platenumber, state jurisdiction, plate type, and associated ALPR/OCR confidence levels).

a) A statistically significant sample set of image transactions will be selected by the System (random sample) based on the number of images processed that month and provided to KTA for their QA review of the image processing outputs.b) In addition, transactions which were successfully disputed for the reason that the image was incorrectly formed by the RSS shall be added to the errors for that month. c) Feedback from customers, Back Office staff, KTA staff and consultants will be utilized to identify inaccurate or incomplete transactions.d) KTA will utilize trend reporting to identify transactions, or lanes/zones for further review to identify possibly inaccurate transactions.e) Transactions rejected by the Back Office will also be reviewed for accuracy.f) KTA may conduct unannounced controlled testing in live traffic as well.

1248 For any month in which the image transaction accuracy falls below 99.90 percent, the Contractor shall be assessed1.0 point for each 0.1 percent or portion thereof below the Performance Requirement.

8.2.7. Image Quality

The ability to be paid for image transaction relies upon the capture of images of sufficient quality for image reviewprocessing. If the image quality is poor, image review will take longer and ultimately images may be rejected. TheContractor’s performance in this area has a direct impact on the KTA’s revenue stream.

The RTCS shall provide images of sufficient image quality to achieve the Contractor’s desired automation rate andKTA’s Requirements such that less than 0.1 percent of the images are rejected for reasons under the Contractor’scontrol. Reject reasons not under the Contractor’s control are:

a) the vehicle has no plate;

b) plate is not in the normal camera field of view because it is not mounted in accordance with state laws;

c) the plate is covered by dirt, a trailer hitch, tailgate, or some other material such that the numbers/letters are not human readable; ord) the plate is damaged so that numbers/letters are not human readable.

1247

1249





No. Requirements

Required Inputs

1250 The number of image transactions rejected for reasons within the Contractor’s control will be compared to thenumber of image transactions processed that month to calculate whether or not the Contractor’s image qualitymet the standard.

1251 For any month in which the image quality falls below 99.90 percent, the Contractor shall be assessed 1.0 point foreach 0.1 percent or portion thereof below the Performance Requirement.

8.2.8. ICPS Automation RateThe Contractor shall be required to accurately determine license plate data (including the license plate number,state jurisdiction, plate type, and associated ALPR/OCR confidence levels) using advanced ALPR/OCR techniquesand to achieve automation rates that will assist the KTA to reduce manual image review processing time andincrease transaction accuracy.

1252 The ICPS provided by the Contractor shall provide trustworthy (highly confident) ALPR/OCR automation for at least70 percent of transactions that also meet the ICPS Accuracy Performance Requirements in this section.

1253 The number of transactions that meet the Contractor-established trustworthy (highly confident) threshold for ICPSAccuracy will be compared to the total number of transactions processed that month to calculate whether or notthe Contractor’s ICPS automation met the standard.

1254 For any month in which the ICPS automation rate falls below 70 percent, the Contractor shall be assessed 1.0 pointfor each 1.0 percent or portion thereof below the Performance Requirement.

8.2.9. ICPS Automation AccuracyThe Contractor shall be required to accurately determine license plate data (including the license plate number,state jurisdiction, plate type, and associated ALPR/OCR confidence levels) using advanced ALPR/OCR techniquesand to achieve automation rates that will assist the KTA to reduce manual image review processing time andincrease transaction accuracy.

1255 The ICPS provided by the Contractor shall provide accurate ALPR/OCR license plate data (including the licenseplate number, state jurisdiction, plate type, and associated ALPR/OCR confidence levels) with an accuracy of 99.95percent or more for transactions deemed trustworthy (highly confident) for automation.

1256 A statistically significant sample set of transactions designated by the Contractor as trustworthy (highly confident)will be selected by the System (random sample) based on the number of transactions processed that month andprovided to KTA for their QA review of the ICPS accuracy.

1257 For any month in which the ICPS automation accuracy falls below 99.95 percent, the Contractor shall be assessed1.0 point for each 0.1 percent or portion thereof below the Performance Requirement.

8.2.10. Back Office File CommunicationsThe KTA CSC BOS will create daily Transponder Status List files, and periodic toll rate files and Hotlist files. Receiptof files from the KTA CSC BOS, their version, time of receipt and processing status shall also be tracked. Updates tosome or all of these files will happen at intervals of no less than sixty (60) minutes. The Contractor shall provideKTA or their designee access adequate to validate application of Updates to files at locations within the system oftheir choosing.

The Contractor shall receive, process, transmit and apply 100 percent of the files and updates as applicable inaccordance with these Requirements.

a) Daily files – Files transmitted daily will be tracked by the System and reported to KTA. 1 point will be assessed for each day wherein the daily file(s) were not applied within fifteen (15) minutes of arrival to the RTCS System. 1258





No. Requirements

Required Inputs

b) Incremental File Updates – KTA or designee will select locations and acquire validation data from the CSC to verify Updates have been applied to files in downstream portions of the RTCS System. 1 point will be assessed for each day wherein one or more incremental update files were not applied within ten (10) minutes of arrival to the RTCS System.

1259 For any month in which the files and Updates are not applied within the applicable time (15 minutes for daily filesand 10 minutes for Updates), the Contractor shall be assessed a maximum of 2 points per day for any files notreceived and processed within the applicable time.

8.2.11. Wrong-Way Vehicle Detection and NotificationThe Contractor shall be required to accurately detect Wrong-Way Vehicles traveling in the wrong direction and toproperly send notifications and alerts per the Requirements.The Contractor shall accurately detect 100 percent of vehicles traveling in the wrong direction and shall sendnotifications and alerts in accordance with these Requirements.

a) The AVDC System shall detect and report vehicles traveling in the wrong direction.b) Electronic wrong-way vehicle signs (provided by others) shall be illuminated.

c) The DVAS shall record a five (5) second looping DVAS video file upon detection of a Wrong-Way Vehicle.

d) The RTCS shall transmit the DVAS video file to the KTA IMC and transmit an alert to KTA IMC personnel (via email and SMS text message) within ten (10) seconds of the vehicle passing through the Toll Zone.

e) The message alert shall be prominently displayed on the operators’ video wall or monitors at the KTA IMC.

f) The System shall transmit a vehicle transaction to the KTA CSC BOS with a flag indicating wrong-way vehicle transaction.g) The System shall transmit images of the Wrong-Way Vehicle and the vehicle Region of Interest (ROI) to the KTA CSC BOS.

1261 For any day in which a Wrong-Way Vehicle is not accurately detected and properly reported, the Contractor shallbe assessed 1.0 point.

1260


Roadside Toll Collection System RFP Exhibit D - Forms - Price Proposal


Form D-7 Price Proposal Form

(An Excel Version of the Price Proposal Form is “paper clipped” to this

KTA RTCS Exhibits file for ease of completion.)

Roadside Toll Collection System RFP Exhibit D-7 - Forms - Price Proposal

Grand Total Cost ($)

$ -

$ -

-$

$ -

$ -

$ -

$ -

$ -

$ -

$ -

$ -

-$

-$

Per Zone Roadside Cost ($)

$ -

$ -

$ -

Grand Total Dollars

Officer Signature Date

Future Zone AET 2: 2 travel + 2 shoulders

Future Zone AET 3: 3 travel + 2 shoulders

Future Zone Expand from AET2+ to AET 3

Sheet 1KTA Turnpike Project Summary

(Summary Only - No Proposer Input Required)

Description of Items

Implementation Phase

Extension #1 RSS Maintenance and Software Support Services Cost (Sheet 5)

Roadside Toll Collection System (RTCS) Cost (Sheet 2)

Extension #2 RSS Maintenance and Software Support Services Cost (Sheet 5)

Total Implementation Phase

Roadway Support System (RSS) Cost (Sheet 3)

Maintenance Phase

Total Optional Extension Phases

RTCS Hardware Maintenance and Software Support Services Cost (Sheet 4)

RSS Maintenance and Software Support Services Cost (Sheet 5)

Extension #1 RTCS Hardware Maintenance and Software Support Services Cost (Sheet 4)

Optional Extension Phase

Extension #2 RTCS Hardware Maintenance and Software Support Services Cost (Sheet 4)

TOTAL IMPLEMENTATION AND MAINTENANCE COST

TOTAL IMPLEMENTATION AND MAINTENANCE COST INCLUDING OPTIONAL EXTENSION PHASES

Total Maintenance Phase


Future RTCS AET Zone System Implementation (by Zone Type) (Sheet 6)



Toll Zone/Type Total # of Toll Zones

Hardware Cost Per Toll Zone ($)

Labor Cost Per Toll Zone ($)

Total Cost Toll Zones ($)

K1 - AET 2 1 -$ -$ $ -

K2 - AET 2 1 -$ -$ $ -

Facility Server (Sheet 2-4) -$ -$ $ -

Total Tolling Location 1 $ -

K3 - AET 2 1 -$ -$ $ -

K4 - AET 2 1 -$ -$ $ -



K5 - AET 2 1 -$ -$ $ -

K6 - AET 2 1 -$ -$ $ -



K7 - AET 2 1 -$ -$ $ -

K8 - AET 2 1 -$ -$ $ -



K9 - AET 2 1 -$ -$ $ -

K10 - AET 2 1 -$ -$ $ -



K11 - AET 2 1 -$ -$ $ -

K12 - AET 2 1 -$ -$ $ -



K13 - AET 2 1 -$ -$ $ -

K14 - AET 2 1 -$ -$ $ -



Sheet 2Roadside Toll Collection System (RTCS) Cost(Summary Only - No Proposer Input Required)

Tolling Location 1Southern Terminal**

Tolling Location 2Mulvane K-53 | US-160

Tolling Location 3Haysville-Derby 71st | Mulvane K-53

Tolling Location 4Wichita I-135/I-235 | Haysville-Derby

Tolling Location 5Wichita K-15 | I-135/I-235

Tolling Location 6Wichita US-54, US-400, Kellogg | K-

15

Tolling Location 7Wichita K-96 | US-54 Kellogg








K15 - AET 2 1 -$ -$ $ -

K16 - AET 2 1 -$ -$ $ -



K17 - AET 2 1 -$ -$ $ -

K18 - AET 2 1 -$ -$ $ -



K19 - AET 2 1 -$ -$ $ -

K20 - AET 2 1 -$ -$ $ -



K21 - AET 2 1 -$ -$ $ -

K22 - AET 2 1 -$ -$ $ -



K23 - AET 2 1 -$ -$ $ -

K24 - AET 2 1 -$ -$ $ -



K25 - AET 2 1 -$ -$ $ -

K26 - AET 2 1 -$ -$ $ -



K27 - AET 2 1 -$ -$ $ -

K28 - AET 2 1 -$ -$ $ -



K29 - AET 2 1 -$ -$ $ -

K30 - AET 2 1 -$ -$ $ -



Tolling Location 8Andover 21st | Wichita K-96

Tolling Location 9El Dorado US-254 | Andover 21st

Tolling Location 10El Dorado US-77 | US-254

Tolling Location 11Cassoday K-177 | El Dorado US-77

Tolling Location 12Emporia I-35 | Cassoday K-177

Tolling Location 13Council Grove US-56 | Emporia

Tolling Location 14Topeka I-470 | Council Grove US-56

Tolling Location 15Topeka K-4 | I-470








K31 - AET 2 1 -$ -$ $ -

K32 - AET 2 1 -$ -$ $ -



K33 - AET 3 1 -$ -$ $ -

K34 - AET 3 1 -$ -$ $ -



K35 - AET 2+ 1 -$ -$ $ -

K36 - AET 2+ 1 -$ -$ $ -



K37 - AET 3 1 -$ -$ $ -

K38 - AET 3 1 -$ -$ $ -



K39 - AET 2+ 1 -$ -$ $ -

K40 - AET 2+ 1 -$ -$ $ -



K41 - AET 2+ 1 -$ -$ $ -

K42 - AET 2+ 1 -$ -$ $ -



42 $ - $ - $ - ** Existing ORT Gantries are located at K01 & K02 (Southern Terminal), K31 & K32 (East Topeka), and K41 & K42 (Eastern Terminal).

AET 2: 10' shoulder + 2 X 12' travel + 10' shoulder AET 2+: 10' shoulder + 2 X 12' travel + 10' shoulder - To be expanded from 2 Travel Lanes to 3 Travel Lanes during the Contract Term and should be designed and planned accordingly. AET 3: 10' shoulder + 3 X 12' travel + 10' shoulder

Total RTCS Cost

Tolling Location 16East Topeka: I-70**

Tolling Location 17Lecompton K-10 | Topeka I-70 | K-4

Tolling Location 18Lawrence US-59S | Lecompton K-10

Tolling Location 19Lawrence: US-59, US-40

Tolling Location 20Tonganoxie-Eudora: 222nd St |

Lawrence US-40 US-59

Tolling Location 21Eastern Terminal**



Item # Description Unit Cost ($)

1 System Hardware, Third Party Software, Installation and Commissioning not Otherwise Covered LS $ -

2 Communications Equipment LS $ -

3 Zone Controller Software Costs LS $ -

4 Software (GUI, Back-end), Host System, MOMS, DVAS and License LS $ -

5 Design Documentation LS $ -

6 User, Maintenance, and Project Documentation LS $ -

7 Training (manuals, materials and delivery) LS $ -

8 Factory Acceptance Test (FAT) LS $ -

9 On-Site Installation Test (OSIT) LS $ -

10 Installation and Commissioning Test (ICT) LS $ -

11 System Acceptance Test (SAT) LS $ -

12 Third Party Warranty and Licenses LS $ -

13 Initial Spare Parts and Equipment - Two (2) Tolling Locations (4 Toll Zones) LS $ -

14 Insurance and Bonding LS $ -

15 Project Management LS $ -

16 Engineering and Design LS $ -

17 Transition Costs LS $ -

$ - Total RSS Cost

Sheet 3Roadway Support System (RSS) Cost




Item # Description of Items Total Monthly Cost ($) Per Toll Zone # of Toll Zones Monthly Cost ($) Annual Cost ($)

Base Contract Maintenance Costs

1 Year 1 of Maintenance -$ 42 -$ -$







Total RTCS Hardware Maintenance and Software Support Services Base Contract Cost (Maintenance Years 1 - 7) -$

Optional Extension 1 Costs

8 Extension 1 - Year 1 of Maintenance -$ 42 -$ -$



Total Extension 1 Cost -$





Total Extension 2 Cost -$

-$

Sheet 4Base Contract and Optional Extensions

Roadside Toll Collection System (RTCS) Hardware Maintenance and Software Support Services Cost(Summary Only - No Proposer Input Required)

Total Base and Optional RTCS Hardware Maintenance and Software Support Services



Item # Description of Items Monthly Cost ($) Annual Cost ($)


1 Year 1 of Maintenance $ - $ -







Total RSS Maintenance and Software Support Services Base Contract Cost (Maintenance Years 1-7) $ -


8 Extension 1 - Year 1 of Maintenance $ - $ -



Total Extension 1 Cost $ -





Total Extension 2 Cost $ -

$ -

Sheet 5Base Contract and Optional Extensions

Roadway Support System (RSS) Maintenance and Software Support Services Cost (Summary Only - No Proposer Input Required)

Total Base and Optional RSS Maintenance and Software Support Services



Item # Description of ItemsPer Zone Roadside

Implementation Cost ($)

Future Roadside System Cost (by Zone Type)

1 Future Zone AET 2: 2 travel + 2 shoulders $ -

2 Future Zone AET 3: 3 travel + 2 shoulders $ -

3 Future Zone Expand from AET2+ to AET 3 $ -

4 Facility Server (assumed to be the same as base contract)

Sheet 6Future Roadside Toll Collection System (RTCS) AET Zone System Implementation Cost

(Informational Purposes Only - No Proposer Input Required)



Lane Types & Item Description Quantity per Toll Zone Unit ($) Total Unit ($) Labor ($) Total Cost ($)

1. Redundant Toll Zone Controller and In-lane Electronics Servers 0 -$ -$ -$ -$ Cable and Connectors 0 -$ -$ -$ -$

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total Redundant Toll Zone Controller and In-lane Electronics -$ -$ -$ 2. AVI SystemReader Modules 0 -$ -$ -$ -$ Antennas 0 -$ -$ -$ -$

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total AVI System -$ -$ -$ 3. AVDC SystemOverhead Scanners 0 -$ -$ -$ -$ In-pavement Sensors 0 -$ -$ -$ -$ Cables and Connectors 0 -$ -$ -$ -$

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total AVDC System -$ -$ -$ 4. ICPSRear Cameras 0 -$ -$ -$ -$ Front Cameras 0 -$ -$ -$ -$ Illumination 0 -$ -$ -$ -$ Servers 0 -$ -$ -$ -$ Cables and Connectors 0 -$ -$ -$ -$

0 -$ -$ -$ -$ Total ICPS -$ -$ -$

5. Communications Equipment0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total Communications Equipment -$ -$ -$ 6. Equipment Enclosures and RacksEquipment Enclosures 0 -$ -$ -$ -$ Equipment Racks 0 -$ -$ -$ -$

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total Equipment Racks -$ -$ -$ 7. DVASCameras 0 -$ -$ -$ -$ Servers 0 -$ -$ -$ -$ Cable and Connectors 0 -$ -$ -$ -$

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total DVAS -$ -$ -$

Sheet 2-1 Backup AET 2: RTCS Cost Schedule

Zone Type: AET 2 (10' shoulder + 2 X 12' travel + 10' shoulder)




Sheet 2-1 Backup AET 2: RTCS Cost Schedule

8. Critical Environmental Monitoring System (CEMS)Critical Environmental Monitoring System 0 -$ -$ -$ -$

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total CEMS -$ -$ -$ 9. Installation and Commissioning Test

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total Commissioning Test -$ -$ -$

Total -$ -$ -$

Labor Check (from Sheet 2-1a, cell F50) should equal cell E76 -$

Note 1: All hardware/software provided under this Contract should be included in these costs.Note 2: Use the additional rows as needed to itemize each componentsNote 3: All hardware/software costs are Year 2022 costs.Note 4: Single redundant zone controller is inclusive of two redundant units in all cases in the schedules.Note 5: Costs must include all in-lane installation costs, including cost of installation check and inspection as detailed in the Scope of Work



Item # Staff Names Position/Classification

Rate Hours Total Labor Cost

1 Project Principal -$ 0 -$ 2 Contractor Project Manager -$ 0 -$ 3 Deputy Project Manager -$ 0 -$ 4 Technical Manager, Roadside Systems -$ 0 -$ 5 Installation Manager -$ 0 -$ 6 Maintenance Coordinator -$ 0 -$ 7 Quality Assurance Manager -$ 0 -$ 8 Test Manager -$ 0 -$ 9 CADD Technician -$ 0 -$ 10 Configuration Manager -$ 0 -$ 11 Database Administrator -$ 0 -$ 12 Database Analyst -$ 0 -$ 13 Drafter/CAD-Operator -$ 0 -$ 14 Electrician Helper -$ 0 -$ 15 Finance Manager (Design/Implementation) -$ 0 -$ 16 Finance Manager (Operations) -$ 0 -$ 17 Hardware Engineer/Lead -$ 0 -$ 18 Installation Supervisor -$ 0 -$ 19 Installation Technician -$ 0 -$ 20 Licensed Electrical Engineer -$ 0 -$ 21 Licensed Electrician -$ 0 -$ 22 Maintenance Manager -$ 0 -$ 23 Maintenance Supervisor -$ 0 -$ 24 Maintenance Technician -$ 0 -$ 25 Network Administrator -$ 0 -$ 26 Network Engineer -$ 0 -$ 27 Operations Manager -$ 0 -$ 28 Production Manager -$ 0 -$ 29 Scheduler -$ 0 -$ 30 Senior Maintenance Technician -$ 0 -$ 31 Software Architect -$ 0 -$ 32 Software Development Engineer -$ 0 -$ 33 Software Development Manager -$ 0 -$ 34 Software Lead -$ 0 -$ 35 Software Programmer I -$ 0 -$ 36 Software Programmer II -$ 0 -$ 37 Software Programmer III -$ 0 -$ 38 Staging/Configuration Techs -$ 0 -$ 39 System Administrator -$ 0 -$ 40 System Analyst -$ 0 -$ 41 System Design Manager -$ 0 -$ 42 Systems Engineer -$ 0 -$ 43 Technical Writer -$ 0 -$ 44 Tester -$ 0 -$ 45 Training Manager -$ 0 -$ 46 Transition Manager -$ 0 -$ 47 -$ 0 -$ 48 -$ 0 -$ 49 -$ 0 -$ 50 -$ 0 -$ 51 -$ 0 -$ 52 -$ 0 -$ 53 -$ 0 -$ 54 -$ 0 -$ 55 -$ 0 -$

Total Labor Cost -$

Loaded Hourly BillingRates by Task

Sheet 2-1a BackupAET 2: RTCS - Staff and Position Classifications with Rates

Roadside System CostZone Type AET 2





0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total AVC System -$ -$ -$ 4. ICPSRear Cameras 0 -$ -$ -$ -$ Front Cameras 0 -$ -$ -$ -$ Illumination 0 -$ -$ -$ -$ Servers 0 -$ -$ -$ -$ Cables and Connectors 0 -$ -$ -$ -$

0 -$ -$ -$ -$ Total ICPS -$ -$ -$



0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total DVAS -$ -$ -$

Sheet 2-2 Backup AET 2+: RTCS Cost Schedule

Zone Type: AET 2+ (10' shoulder + 2 X 12' travel + 10' shoulder) May be expanded from 2 Travel Lanes to 3 Travel Lanes during the Contract Term and should be designed and planned accordingly.




Sheet 2-2 Backup AET 2+: RTCS Cost Schedule


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


Total -$ -$ -$








Total Labor Cost -$

Sheet 2-2a BackupAET 2+: RTCS - Staff and Position Classifications with Rates


Roadside System CostZone Type AET 2+





0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total AVC System -$ -$ -$ 4. ICPSRear Cameras 0 -$ -$ -$ -$ Front Cameras 0 -$ -$ -$ -$ Illumination 0 -$ -$ -$ -$ Servers 0 -$ -$ -$ -$ Cables and Connectors 0 -$ -$ -$ -$

0 -$ -$ -$ -$ Total ICPS -$ -$ -$



0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total DVAS -$ -$ -$

Sheet 2-3 Backup AET 3: RTCS System Cost Schedule

Zone Type: AET 3 (10' shoulder + 3 x 12' travel + 10' shoulder)




Sheet 2-3 Backup AET 3: RTCS System Cost Schedule


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$


Total -$ -$ -$








Total Labor Cost -$

Sheet 2-3a BackupAET 3: RTCS - Staff and Position Classifications with Rates


Roadside System CostZone Type AET 3




Facility Server

1. Tolling Location 1 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total Facility Server - Tolling Location 1 -$ -$ -$













Sheet 2-4 Backup Facility Server by Location Cost Schedule


















Total Facility Server - Tolling Location 21 -$ -$ -$ Note 1: All hardware/software provided under this Contract should be included in these costs.Note 2: Use the additional rows as needed to itemize each componentsNote 3: All hardware/software costs are Year 2022 costs.Note 4: Single redundant zone controller is inclusive of two redundant units in all cases in the schedules.Note 5: Costs must include all in-lane installation costs, including cost of installation check and inspection as detailed in the Scope of WorkNote 6: See Sheet 2 for individual tolling location details.



# Unit Unit ($) Total Unit ($) Labor ($) Total Cost ($)

1System Hardware, Third Party Software, Installation and Commissioning not Otherwise Covered

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 2 Communications Equipment

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 3 Zone Controller Software Costs

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 4 Software (GUI, Back-end), Host System, MOMS, DVAS and License

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 5 Design Documentation

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 6 User, Maintenance, and Project Documentation

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$

Sheet 3-1 Backup RSS Cost Schedule

Zone Controller Software Licenses

Network Switches

Installation Manual

Total Software (GUI, Back-end), Host System, MOMS, DVAS and License

Total Design Documentation

Total User, Maintenance and Project Documentation

System Requirements DocumentLane Design Document

Host SoftwareMOMSDVAS

Total Zone Controller Software Costs

Total Communications Equipment

System Detail Design Document

Critical Environmental Monitoring System OCR/ALPR Software

Project Plans

Documents/ManualsMaintenance Manual

Business Rules Document


LAN Hardware and Installation

Total System Hardware, Third Party SW and Installation not Otherwise Covered

Host Servers - equipment, purchase, install, configure and test

Other Third-party Software

HDD StorageBack-up Library






7 Training (manuals, materials and delivery)0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 8 Factory Acceptance Test (FAT)

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 9 On-Site Installation Test (OSIT)

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 10 Installation and Commissioning Test (ICT)

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 11 System Acceptance Test (SAT)

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 12 Third Party Warranty and Licenses

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 13 Initial Spare Parts and Equipment - Two (2) Tolling Locations (4 Toll Zones)

-$ -$ -$ -$ -$ -$

Total System Acceptance Test

Total Third Party Warranty and Licenses

OS Licenses

RSS Initial Spare Parts and Equipment (From Sheet 3-2)

Total Installation and Commissioning Test

Total Training

Total Factory Acceptance Test

Total On-Site Installation Test

Total Initial Spare Parts and Equipment

RTCS Initial Spare Parts and Equipment (From Sheet 3-2)

Maintenance Training

DB Licenses






14 Insurance and Bonding0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 15 Project Management

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 16 Engineering and Design

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$ 17 Transition Costs

0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

-$ -$ -$

-$ -$ -$

-$

Total Project Management

Total RSS Costs

Insurance Bid BondPayment and Performance Bond

Total Insurance and Bonding

Total Transition Costs

Labor Check (from Sheet 3-1a, cell F50) should equal cell F168

Lane Installation Design Drawings

Total Engineering and Design





1 Project Principal -$ 0 -$ 2 Contractor Project Manager -$ 0 -$ 3 Deputy Project Manager -$ 0 -$ 4 Technical Manager, Roadway Support Systems -$ 0 -$ 5 Installation Manager -$ 0 -$ 6 Maintenance Coordinator -$ 0 -$ 7 Quality Assurance Manager -$ 0 -$ 8 Test Manager -$ 0 -$ 9 CADD Technician -$ 0 -$

10 Configuration Manager -$ 0 -$ 11 Database Administrator -$ 0 -$ 12 Database Analyst -$ 0 -$ 13 Drafter/CAD-Operator -$ 0 -$ 14 Electrician Helper -$ 0 -$ 15 Finance Manager (Design/Implementation) -$ 0 -$ 16 Finance Manager (Operations) -$ 0 -$ 17 Hardware Engineer/Lead -$ 0 -$ 18 Installation Supervisor -$ 0 -$ 19 Installation Technician -$ 0 -$ 20 Licensed Electrical Engineer -$ 0 -$ 21 Licensed Electrician -$ 0 -$ 22 Maintenance Manager -$ 0 -$ 23 Maintenance Supervisor -$ 0 -$ 24 Maintenance Technician -$ 0 -$ 25 Network Administrator -$ 0 -$ 26 Network Engineer -$ 0 -$ 27 Operations Manager -$ 0 -$ 28 Production Manager -$ 0 -$ 29 Scheduler -$ 0 -$ 30 Senior Maintenance Technician -$ 0 -$ 31 Software Architect -$ 0 -$ 32 Software Development Engineer -$ 0 -$ 33 Software Development Manager -$ 0 -$ 34 Software Lead -$ 0 -$ 35 Software Programmer I -$ 0 -$ 36 Software Programmer II -$ 0 -$ 37 Software Programmer III -$ 0 -$ 38 Staging/Configuration Techs -$ 0 -$ 39 System Administrator -$ 0 -$ 40 System Analyst -$ 0 -$ 41 System Design Manager -$ 0 -$ 42 Systems Engineer -$ 0 -$ 43 Technical Writer -$ 0 -$ 44 Tester -$ 0 -$ 45 Training Manager -$ 0 -$ 46 Transition Manager -$ 0 -$ 47 -$ 0 -$ 48 -$ 0 -$ 49 -$ 0 -$ 50 -$ 0 -$ 51 -$ 0 -$ 52 -$ 0 -$ 53 -$ 0 -$ 54 -$ 0 -$ 55 -$ 0 -$

Total Labor Cost -$


Roadway Support Systems Cost

Sheet 3-1a BackupRSS - Staff and Position Classifications with Rates



Spare Parts Description Total Quantity Unit ($) Total Unit ($)

Roadside Toll Collection System (RTCS)

1. Redundant Toll Zone Controller and In-lane Electronics¹Servers 0 -$ -$ Hard drive 0 -$ -$ Serial Controllers 0 -$ -$ Power Supply 0 -$ -$ Cables and Connectors 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total Redundant Toll Zone Controller and In-lane Electronics¹ -$ 2. AVI SystemAVI Reader Modules 0 -$ -$ AVI Antennas 0 -$ -$ Cables and Connectors 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total AVI System -$ 3. AVDC SystemPrimary AVDC Sensor 0 -$ -$ AVDC Detector Cards 0 -$ -$ Cables and Connectors 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total AVDC System -$ 4. ICPSFront Cameras 0 -$ -$ Rear Cameras 0 -$ -$ Illuminators 0 -$ -$ Servers 0 -$ -$ Hard drive 0 -$ -$ Cables and Connectors 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total ICPS -$

Sheet 3-2 Backup RTCS and RSS Initial Spare Parts and Equipment Cost

(Two (2) Tolling Locations (4 Toll Zones))





5. Communications EquipmentSwitches 0 -$ -$ Power Supply 0 -$ -$ Router 0 -$ -$ GBICs 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total Communications Equipment -$ 6. Equipment Enclosures and RacksEquipment Enclosures 0 -$ -$ Equipment Racks 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total Equipment Racks -$ 7. DVASCameras 0 -$ -$ Servers 0 -$ -$ Hard Drive Storage 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total DVAS -$ 8. Critical Environmental Monitoring System (CEMS)Critical Environmental Monitoring System (CEMS) 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total CEMS -$ 9. Facility Server

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total Facility Server -$

RTCS Initial Spare Parts and Equipment -$





Roadway Support Systems (RSS)

1. System HardwareServers 0 -$ -$ Hard drive 0 -$ -$ Miscellaneous 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total System Hardware -$ 2. Communications EquipmentLAN Equipment 0 -$ -$ Power Supply 0 -$ -$

0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$

Total Communications Equipment -$

RSS Initial Spare Parts and Equipment -$

Total RTCS and RSS Initial Spare Parts and Equipment -$

(One Tolling Location)



Description of Items Monthly Direct Costs ($)per Zone

Monthly Labor ($)per Zone

Monthly Total Cost ($)per Zone


Year 1 of Maintenance - Monthly RTCS Hardware Maintenance and Software Support Services

Labor -$ -$ Material, Tools and Occupancy -$ -$ Other -$ -$ OCR/ALPR Software -$ -$ Cloud-based Operations Expenses (OpEx) - IF APPLICABLE

Cloud-based OpEx - Production Solution -$ -$ Cloud-based OpEx - DR Solution -$ -$ Cloud-based OpEx - Production Storage - Data -$ -$ Cloud-based OpEx - Production Storage - Images -$ -$ Cloud-based OpEx - Data Transmission Costs -$ -$ Cloud-based OpEx - Data Analytics / BI -$ -$ Cloud-based OpEx - Other -$ -$

Maintenance Payment of Performance Bond (X%) -$ -$ Total Monthly Year 1 -$ -$ -$









Sheet 4-1 BackupBase Contract and Optional Extensions

RTCS Hardware Maintenance and Software Support Services -Labor and Other Direct Cost Items by Month















RTCS Hardware Refresh (If Necessary) -$ -$ Maintenance Payment of Performance Bond (X%) -$ -$

Total Monthly Year 5 -$ -$ -$



















Extension 1 Year 1 of Maintenance - Monthly RTCS Hardware Maintenance and Software Support Services



Maintenance Payment of Performance Bond (X%) -$ -$ Total Monthly Extension 1 Year 1 -$ -$ -$











0.0% 2.0%

2024 Loaded Labor Rate

Year 1Rate

Year 1 Hours

Year 1 Total Labor Cost

Year 2Rate

Year 2Hours

Year 2Total Labor Cost

1 Project Principal -$ -$ 0 -$ -$ 0 -$ 2 Contractor Project Manager -$ -$ 0 -$ -$ 0 -$ 3 Deputy Project Manager -$ -$ 0 -$ -$ 0 -$ 4 Technical Manager, Roadside Systems -$ -$ 0 -$ -$ 0 -$ 5 Installation Manager -$ -$ 0 -$ -$ 0 -$ 6 Maintenance Coordinator -$ -$ 0 -$ -$ 0 -$ 7 Quality Assurance Manager -$ -$ 0 -$ -$ 0 -$ 8 Test Manager -$ -$ 0 -$ -$ 0 -$ 9 CADD Technician -$ -$ 0 -$ -$ 0 -$ 10 Configuration Manager -$ -$ 0 -$ -$ 0 -$ 11 Database Administrator -$ -$ 0 -$ -$ 0 -$ 12 Database Analyst -$ -$ 0 -$ -$ 0 -$ 13 Drafter/CAD-Operator -$ -$ 0 -$ -$ 0 -$ 14 Electrician Helper -$ -$ 0 -$ -$ 0 -$ 15 Finance Manager (Design/Implementation) -$ -$ 0 -$ -$ 0 -$ 16 Finance Manager (Operations) -$ -$ 0 -$ -$ 0 -$ 17 Hardware Engineer/Lead -$ -$ 0 -$ -$ 0 -$ 18 Installation Supervisor -$ -$ 0 -$ -$ 0 -$ 19 Installation Technician -$ -$ 0 -$ -$ 0 -$ 20 Licensed Electrical Engineer -$ -$ 0 -$ -$ 0 -$ 21 Licensed Electrician -$ -$ 0 -$ -$ 0 -$ 22 Maintenance Manager -$ -$ 0 -$ -$ 0 -$ 23 Maintenance Supervisor -$ -$ 0 -$ -$ 0 -$ 24 Maintenance Technician -$ -$ 0 -$ -$ 0 -$ 25 Network Administrator -$ -$ 0 -$ -$ 0 -$ 26 Network Engineer -$ -$ 0 -$ -$ 0 -$ 27 Operations Manager -$ -$ 0 -$ -$ 0 -$ 28 Production Manager -$ -$ 0 -$ -$ 0 -$ 29 Scheduler -$ -$ 0 -$ -$ 0 -$ 30 Senior Maintenance Technician -$ -$ 0 -$ -$ 0 -$ 31 Software Architect -$ -$ 0 -$ -$ 0 -$ 32 Software Development Engineer -$ -$ 0 -$ -$ 0 -$ 33 Software Development Manager -$ -$ 0 -$ -$ 0 -$ 34 Software Lead -$ -$ 0 -$ -$ 0 -$ 35 Software Programmer I -$ -$ 0 -$ -$ 0 -$ 36 Software Programmer II -$ -$ 0 -$ -$ 0 -$ 37 Software Programmer III -$ -$ 0 -$ -$ 0 -$ 38 Staging/Configuration Techs -$ -$ 0 -$ -$ 0 -$ 39 System Administrator -$ -$ 0 -$ -$ 0 -$ 40 System Analyst -$ -$ 0 -$ -$ 0 -$ 41 System Design Manager -$ -$ 0 -$ -$ 0 -$ 42 Systems Engineer -$ -$ 0 -$ -$ 0 -$ 43 Technical Writer -$ -$ 0 -$ -$ 0 -$ 44 Tester -$ -$ 0 -$ -$ 0 -$ 45 Training Manager -$ -$ 0 -$ -$ 0 -$ 46 Transition Manager -$ -$ 0 -$ -$ 0 -$ 47 -$ -$ 0 -$ -$ 0 -$ 48 -$ -$ 0 -$ -$ 0 -$ 49 -$ -$ 0 -$ -$ 0 -$ 50 -$ -$ 0 -$ -$ 0 -$ 51 -$ -$ 0 -$ -$ 0 -$ 52 -$ -$ 0 -$ -$ 0 -$ 53 -$ -$ 0 -$ -$ 0 -$ 54 -$ -$ 0 -$ -$ 0 -$ 55 -$ -$ 0 -$ -$ 0 -$

Grand Total Labor Cost -$ -$

% increase/decrease from previous year #DIV/0!

Note 1: CPI Composite of 2% - 3% used for evaluation purposes. CPI adjustments will be made to the Monthly Maintenance Cost based on actual CPI change for the previous year as further described in the Price Proposal Instructions.

Sheet 4-1a Backup Base Contract and Optional Extensions

RTCS Hardware Maintenance and Software Support Services - Staff and Position Classifications with Rates


Escalation % (Over Previous Year)


Loaded Hourly Billing Rates Year 1 of Maintenance




1 Project Principal2 Contractor Project Manager3 Deputy Project Manager4 Technical Manager, Roadside Systems5 Installation Manager6 Maintenance Coordinator7 Quality Assurance Manager8 Test Manager9 CADD Technician10 Configuration Manager11 Database Administrator12 Database Analyst13 Drafter/CAD-Operator14 Electrician Helper15 Finance Manager (Design/Implementation)16 Finance Manager (Operations)17 Hardware Engineer/Lead18 Installation Supervisor19 Installation Technician20 Licensed Electrical Engineer21 Licensed Electrician22 Maintenance Manager23 Maintenance Supervisor24 Maintenance Technician25 Network Administrator26 Network Engineer27 Operations Manager 28 Production Manager29 Scheduler30 Senior Maintenance Technician31 Software Architect32 Software Development Engineer33 Software Development Manager34 Software Lead35 Software Programmer I36 Software Programmer II37 Software Programmer III38 Staging/Configuration Techs39 System Administrator40 System Analyst41 System Design Manager42 Systems Engineer43 Technical Writer44 Tester45 Training Manager46 Transition Manager474849505152535455

Grand Total Labor Cost

% increase/decrease from previous year




Item # Staff Names Position/Classification3.0% 3.0%

Year 3Rate

Year 3Hours


Year 4Rate

Year 4Hours


-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!














Year 5Rate

Year 5Hours


Year 6Rate

Year 6Hours


-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!














Year 7Rate

Year 7Hours


Extension Year 1Rate

Extension Year 1Hours

Extension Year 1

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!

Optional Extension 1

Loaded Hourly Billing RatesExtension Year 1 of Maintenance















Extension Year 2

Total Labor Cost



Extension Year 3

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!

Optional Extension 1 Optional Extension 1
















Extension Year 1

Total Labor Cost



Extension Year 2

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!

Optional Extension 2 Optional Extension 2Escalation % (Over Previous

Year)Escalation % (Over Previous

Year)Loaded Hourly Billing Rates

Extension Year 1 of MaintenanceLoaded Hourly Billing Rates

Extension Year 2 of Maintenance









Item # Staff Names Position/Classification3.0%



Extension Year 3

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$

#DIV/0!

Optional Extension 2Escalation % (Over Previous





Description of Items # Units Unit ($) Total Unit ($) Labor ($) Total Monthly Cost ($)

Labor CheckE * # months

Labor Check From Sheet 5-1a

Base Contract

Year 1 of Maintenance: Monthly RSS Maintenance and Software Support Services Management/Supervision -$ -$ Software Management -$ -$ System and Database Admin -$ -$ System Monitoring -$ -$ Upgrades 0 -$ -$ -$ -$ Materials 0 -$ -$ -$ -$ Equipment 0 -$ -$ -$ -$ Network Management and ISP Fees 0 -$ -$ -$ -$ Cloud-based Operations Expenses (OpEx) - IF APPLICABLE

Cloud-based OpEx - Production Solution 0 -$ -$ -$ -$ Cloud-based OpEx - DR Solution 0 -$ -$ -$ -$ Cloud-based OpEx - Production Storage - Data 0 -$ -$ -$ -$ Cloud-based OpEx - Production Storage - Images 0 -$ -$ -$ -$ Cloud-based OpEx - Data Transmission Costs 0 -$ -$ -$ -$ Cloud-based OpEx - Data Analytics / BI 0 -$ -$ -$ -$ Cloud-based OpEx - Other 0 -$ -$ -$ -$

0 -$ -$ -$ -$ Total Year 1 Monthly RSS Maintenance and Software Support Services -$ -$ -$ -$ -$

Year 2 of Maintenance: Monthly RSS Maintenance and Software Support Services

Management/Supervision -$ -$ Software Management -$ -$ System and Database Admin -$ -$ System Monitoring -$ -$ Upgrades 0 -$ -$ -$ -$ Materials 0 -$ -$ -$ -$ Equipment 0 -$ -$ -$ -$ Network Management and ISP Fees 0 -$ -$ -$ -$ Cloud-based Operations Expenses (OpEx) - IF APPLICABLE








RSS Maintenance and Software Support Services - Labor and Other Direct Cost Items by Month















RSS Hardware Refresh (If Necessary) 0 -$ -$ -$ -$ 0 -$ -$ -$ -$

Total Year 5 Monthly RSS Maintenance and Software Support Services -$ -$ -$ -$ -$


















Optional Extension Costs

Extension 1 Costs

Extension 1 Year 1 of Maintenance: Monthly RSS Maintenance and Software Support Services



0 -$ -$ -$ -$ Services -$ -$ -$ -$ -$

Extension 1 Year 2 Maintenance: Monthly RSS Maintenance and Software Support Services



0 -$ -$ -$ -$ Total Extension 1 Year 2 Monthly RSS Maintenance and Software Support Services -$ -$ -$ -$ -$ Extension 1 Year 3 of Maintenance: Monthly RSS Maintenance and Software Support Services



0 -$ -$ -$ -$ Services -$ -$ -$ -$ -$








Extension 2 Costs




0 -$ -$ -$ -$ Services -$ -$ -$ -$ -$




0 -$ -$ -$ -$ Services -$ -$ -$ -$ -$




0 -$ -$ -$ -$ Services -$ -$ -$ -$ -$



0.0% 2.0%

2024 Loaded Labor Rate

Year 1Rate

Year 1 Hours


Year 2Rate

Year 2Hours


1 Project Principal -$ -$ 0 -$ -$ 0 -$ 2 Contractor Project Manager -$ -$ 0 -$ -$ 0 -$ 3 Deputy Project Manager -$ -$ 0 -$ -$ 0 -$ 4 Technical Manager, Roadway Support Systems -$ -$ 0 -$ -$ 0 -$ 5 Installation Manager -$ -$ 0 -$ -$ 0 -$ 6 Maintenance Coordinator -$ -$ 0 -$ -$ 0 -$ 7 Quality Assurance Manager -$ -$ 0 -$ -$ 0 -$ 8 Test Manager -$ -$ 0 -$ -$ 0 -$ 9 CADD Technician -$ -$ 0 -$ -$ 0 -$ 10 Configuration Manager -$ -$ 0 -$ -$ 0 -$ 11 Database Administrator -$ -$ 0 -$ -$ 0 -$ 12 Database Analyst -$ -$ 0 -$ -$ 0 -$ 13 Drafter/CAD-Operator -$ -$ 0 -$ -$ 0 -$ 14 Electrician Helper -$ -$ 0 -$ -$ 0 -$ 15 Finance Manager (Design/Implementation) -$ -$ 0 -$ -$ 0 -$ 16 Finance Manager (Operations) -$ -$ 0 -$ -$ 0 -$ 17 Hardware Engineer/Lead -$ -$ 0 -$ -$ 0 -$ 18 Installation Supervisor -$ -$ 0 -$ -$ 0 -$ 19 Installation Technician -$ -$ 0 -$ -$ 0 -$ 20 Licensed Electrical Engineer -$ -$ 0 -$ -$ 0 -$ 21 Licensed Electrician -$ -$ 0 -$ -$ 0 -$ 22 Maintenance Manager -$ -$ 0 -$ -$ 0 -$ 23 Maintenance Supervisor -$ -$ 0 -$ -$ 0 -$ 24 Maintenance Technician -$ -$ 0 -$ -$ 0 -$ 25 Network Administrator -$ -$ 0 -$ -$ 0 -$ 26 Network Engineer -$ -$ 0 -$ -$ 0 -$ 27 Operations Manager -$ -$ 0 -$ -$ 0 -$ 28 Production Manager -$ -$ 0 -$ -$ 0 -$ 29 Scheduler -$ -$ 0 -$ -$ 0 -$ 30 Senior Maintenance Technician -$ -$ 0 -$ -$ 0 -$ 31 Software Architect -$ -$ 0 -$ -$ 0 -$ 32 Software Development Engineer -$ -$ 0 -$ -$ 0 -$ 33 Software Development Manager -$ -$ 0 -$ -$ 0 -$ 34 Software Lead -$ -$ 0 -$ -$ 0 -$ 35 Software Programmer I -$ -$ 0 -$ -$ 0 -$ 36 Software Programmer II -$ -$ 0 -$ -$ 0 -$ 37 Software Programmer III -$ -$ 0 -$ -$ 0 -$ 38 Staging/Configuration Techs -$ -$ 0 -$ -$ 0 -$ 39 System Administrator -$ -$ 0 -$ -$ 0 -$ 40 System Analyst -$ -$ 0 -$ -$ 0 -$ 41 System Design Manager -$ -$ 0 -$ -$ 0 -$ 42 Systems Engineer -$ -$ 0 -$ -$ 0 -$ 43 Technical Writer -$ -$ 0 -$ -$ 0 -$ 44 Tester -$ -$ 0 -$ -$ 0 -$ 45 Training Manager -$ -$ 0 -$ -$ 0 -$ 46 Transition Manager -$ -$ 0 -$ -$ 0 -$ 47 -$ -$ 0 -$ -$ 0 -$ 48 -$ -$ 0 -$ -$ 0 -$ 49 -$ -$ 0 -$ -$ 0 -$ 50 -$ -$ 0 -$ -$ 0 -$ 51 -$ -$ 0 -$ -$ 0 -$ 52 -$ -$ 0 -$ -$ 0 -$ 53 -$ -$ 0 -$ -$ 0 -$ 54 -$ -$ 0 -$ -$ 0 -$ 55 -$ -$ 0 -$ -$ 0 -$

Grand Total Labor Cost -$ -$

% increase/decrease from previous year #DIV/0!





RSS Maintenance and Software Support Services - Staff and Position Classifications with Rates






1 Project Principal2 Contractor Project Manager3 Deputy Project Manager4 Technical Manager, Roadway Support Systems5 Installation Manager6 Maintenance Coordinator7 Quality Assurance Manager8 Test Manager9 CADD Technician10 Configuration Manager11 Database Administrator12 Database Analyst13 Drafter/CAD-Operator14 Electrician Helper15 Finance Manager (Design/Implementation)16 Finance Manager (Operations)17 Hardware Engineer/Lead18 Installation Supervisor19 Installation Technician20 Licensed Electrical Engineer21 Licensed Electrician22 Maintenance Manager23 Maintenance Supervisor24 Maintenance Technician25 Network Administrator26 Network Engineer27 Operations Manager 28 Production Manager29 Scheduler30 Senior Maintenance Technician31 Software Architect32 Software Development Engineer33 Software Development Manager34 Software Lead35 Software Programmer I36 Software Programmer II37 Software Programmer III38 Staging/Configuration Techs39 System Administrator40 System Analyst41 System Design Manager42 Systems Engineer43 Technical Writer44 Tester45 Training Manager46 Transition Manager474849505152535455







Year 3Rate

Year 3Hours


Year 4Rate

Year 4Hours


-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!














Year 5Rate

Year 5Hours


Year 6Rate

Year 6Hours


-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!














Year 7Rate

Year 7Hours




Extension Year 1

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!





Year)












Extension Year 2

Total Labor Cost



Extension Year 3

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!





Optional Extension 1Optional Extension 1












Extension Year 1

Total Labor Cost



Extension Year 2

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$ -$

#DIV/0! #DIV/0!

Optional Extension 2 Optional Extension 2













Item # Staff Names Position/Classification3.0%



Extension Year 3

Total Labor Cost

-$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$ -$ 0 -$

-$

#DIV/0!






Description of Items Quantity per Toll Zone Unit ($) Total Item

Cost ($)

Future Zone AET 2: 2 travel + 2 shoulders - 1. Redundant Toll Zone Controller and In-lane Electronics 0 -$ -$ 2. AVI System 0 -$ -$ 3. AVDC System 0 -$ -$ 4. ICPS 0 -$ -$ 5. Communications Equipment 0 -$ -$ 6. Equipment Cabinets/Enclosures and Racks 0 -$ -$ 7. DVAS 0 -$ -$ 8. Commissioning Test 0 -$ -$

Total -$ Future Zone AET 3: 3 travel + 2 shoulders - 1. Redundant Toll Zone Controller and In-lane Electronics 0 -$ -$ 2. AVI System 0 -$ -$ 3. AVDC System 0 -$ -$ 4. ICPS 0 -$ -$ 5. Communications Equipment 0 -$ -$ 6. Equipment Cabinets/Enclosures and Racks 0 -$ -$ 7. DVAS 0 -$ -$ 8. Commissioning Test 0 -$ -$

Total -$ Future Zone Expand from AET2+ to AET 3 - 1. Redundant Toll Zone Controller and In-lane Electronics 0 -$ -$ 2. AVI System 0 -$ -$ 3. AVDC System 0 -$ -$ 4. ICPS 0 -$ -$ 5. Communications Equipment 0 -$ -$ 6. Equipment Cabinets/Enclosures and Racks 0 -$ -$ 7. DVAS 0 -$ -$ 8. Commissioning Test 0 -$ -$

Total -$ Note 1: All hardware/software provided under this Contract should be included in these costs.Note 2: All hardware/software costs are Year 2022 costs.

Note 5: Assume all shoulder lanes shall be equipped with rear-only Image Capture & Processing Systems (ICPS), and sensors to trigger the cameras and detect and frame the vehicle traveling on the shoulder, as required to meet performance requirements.

Sheet 6-1 Backup Future Zone Types RTCS Cost Schedule Per Zone

2022 Values

Note 3: Single redundant zone controller is inclusive of two redundant units in all cases in the schedules.Note 4: Costs must include all in-lane installation costs, including cost of installation check and inspection as detailed in the Scope of Work.



Overhead including Burden 0.0000%

Profit 0.0000%

STAFF POSITION/CLASSIFICATION LOADED HOURLY RATE

Project Principal -$ Project Manager -$ Deputy Project Manager -$ Technical Manager, Roadside Systems -$ Technical Manager, Roadway Support Systems -$ Installation Manager -$ Maintenance Coordinator -$ Quality Assurance Manager -$ Test Manager -$ CADD Technician -$ Configuration Manager -$ Database Administrator -$ Database Analyst -$ Drafter/CAD-Operator -$ Electrician Helper -$ Finance Manager (Design/Implementation) -$ Finance Manager (Operations) -$ Hardware Engineer/Lead -$ Installation Supervisor -$ Installation Technician -$ Licensed Electrical Engineer -$ Licensed Electrician -$ Maintenance Manager -$ Maintenance Supervisor -$ Maintenance Technician -$ Network Administrator -$ Network Engineer -$ Operations Manager -$ Production Manager -$ Scheduler -$ Senior Maintenance Technician -$ Software Architect -$ Software Development Engineer -$ Software Development Manager -$ Software Lead -$ Software Programmer I -$ Software Programmer II -$ Software Programmer III -$ Staging/Configuration Techs -$ System Administrator -$ System Analyst -$ System Design Manager -$ Systems Engineer -$ Technical Writer -$ Tester -$ Training Manager -$ Transition Manager -$

-$ -$ -$ -$ -$ -$ -$ -$ -$ -$

Sheet 7-1Additional Services Rates (2022 Values)

Note 1: CPI adjustments will be made to the Cost based on actual CPI change for the previous year as further described in the Price Proposal Instructions.




RTCS Maintenance Monthly Cost ($)

Per Toll Zone (Sheet 4-1)

# of Toll ZonesTotal RTCS Maintenance

Monthly Cost ($)

RSS Maintenance Monthly Cost ($)

(Sheet 5)

Total Maintenance Monthly Cost ($)


Year 1 of Maintenance -$ 42 -$ $ - $ -








Extension 1 - Year 1 of Maintenance -$ 42 -$ $ - $ -







Sheet 8Maintenance Monthly Cost



Roadside Toll Collection System RFP Exhibit D – Forms – Price Proposal

-$

Payment Number

Payment Milestone Pay Items % PaidCum

% PaidKTA Turnpike

A-1 Notice to Proceed Notice to Proceed 5.00% 5.00% -$

A-2Roadside Toll System Development and Administration

Project Management Documents Approved: PMP & Project Schedule

2.00% 7.00% -$

A-3Roadside Toll System Development and Administration

Project Management Documents Approved: Master Test Plan, QA Plan and SDP, SRD, Preliminary Design

3.00% 10.00% -$

A-4 Roadside Toll System DesignBusiness Rules and Design Documents Approved: BRD, ICD, Reports Design and SDDD

5.00% 15.00% -$

A-5Roadside Toll System Factory Acceptance Testing (FAT)

Factory Acceptance Test Plan, Test Documentation, and FAT Testing Approved

7.50% 22.50% -$

A-6Roadside Toll System On-Site Installation Testing (OSIT)

On-Site Installation Test (OSIT) Plan Approved, Test Documentation, and OSIT Testing Approved - First Site

2.50% 25.00% -$

A-7Roadside Toll System Manuals and Training

Manuals Approved and Training Approved 2.00% 27.00% -$

A-8Equipment BOM and Advance Ordering Verified

Equipment BOM Approved & Long-lead Items Ordering Verified 5.00% 32.00% -$

A-9 Roadside Toll System Commissioning Installation and Commissioning Approved & Ready for Go Live

A-9a Tolling Location 01Installation and Commissioning Approved and Ready for Go Live - Tolling Location 01

3.00% 35.00% -$

A-9b Tolling Location 02Installation and Commissioning Approved and Ready for Go Live - Tolling Location 02

3.00% 38.00% -$

A-9c Tolling Location 03Installation and Commissioning Approved and Ready for Go Live - Tolling Location 03

3.00% 41.00% -$

A-9d Tolling Location 04Installation and Commissioning Approved and Ready for Go Live - Tolling Location 04

3.00% 44.00% -$

A-9e Tolling Location 05Installation and Commissioning Approved and Ready for Go Live - Tolling Location 05

3.00% 47.00% -$

A-9f Tolling Location 06Installation and Commissioning Approved and Ready for Go Live - Tolling Location 06

3.00% 50.00% -$

A-9g Tolling Location 07Installation and Commissioning Approved and Ready for Go Live - Tolling Location 07

3.00% 53.00% -$

A-9h Tolling Location 08Installation and Commissioning Approved and Ready for Go Live - Tolling Location 08

3.00% 56.00% -$

A-9i Tolling Location 09Installation and Commissioning Approved and Ready for Go Live - Tolling Location 09

3.00% 59.00% -$

A-9j Tolling Location 10Installation and Commissioning Approved and Ready for Go Live - Tolling Location 10

3.00% 62.00% -$

A-9k Tolling Location 11Installation and Commissioning Approved and Ready for Go Live - Tolling Location 11

3.00% 65.00% -$

A-9l Tolling Location 12Installation and Commissioning Approved and Ready for Go Live - Tolling Location 12

3.00% 68.00% -$

A-9m Tolling Location 13Installation and Commissioning Approved and Ready for Go Live - Tolling Location 13

3.00% 71.00% -$

A-9n Tolling Location 14Installation and Commissioning Approved and Ready for Go Live - Tolling Location 14

3.00% 74.00% -$

A-9o Tolling Location 15Installation and Commissioning Approved and Ready for Go Live - Tolling Location 15

3.00% 77.00% -$

A-9p Tolling Location 16Installation and Commissioning Approved and Ready for Go Live - Tolling Location 16

3.00% 80.00% -$

A-9q Tolling Location 17Installation and Commissioning Approved and Ready for Go Live - Tolling Location 17

3.00% 83.00% -$

A-9r Tolling Location 18Installation and Commissioning Approved and Ready for Go Live - Tolling Location 18

3.00% 86.00% -$

A-9s Tolling Location 19Installation and Commissioning Approved and Ready for Go Live - Tolling Location 19

3.00% 89.00% -$

A-9t Tolling Location 20Installation and Commissioning Approved and Ready for Go Live - Tolling Location 20

3.00% 92.00% -$

A-9u Tolling Location 21Installation and Commissioning Approved and Ready for Go Live - Tolling Location 21

3.00% 95.00% -$

A-10 Roadside Toll System AcceptanceOperational and Acceptance Test Approved, As-Builts Approved and Implementation Phase Closed Out

5.00% 100.00% -$

Exhibit B - Payment Schedule

A. Payments for Implementation Roadside Toll Collection System Design and Development


Roadside Toll Collection System RFP Exhibit D - Forms - Proposer Questions Form

Kansas Turnpike Authority (KTA) March 18, 2021 Exhibits D-8

Form D-8 Proposer Questions Form

(A Word version of the Proposer Questions Form is “paper clipped”


Roadside Toll Collection System RFP Exhibit D – Forms - Proposer Questions Form


Proposer Questions

Kansas Turnpike Authority (KTA)

# Page Section Section Description Proposer Question KTA Response

1.

2.

3.

4.

Roadside Toll Collection System RFP Exhibit D - Forms - Surety Commitment Letter


Form D-9 Surety Commitment Letter

(A Word version of the Surety Commitment Letter is “paper


Roadside Toll Collection System RFP Exhibit D - Forms - Surety Commitment Letter


CONSENT OF SURETY TO: Kansas Turnpike Authority We have reviewed the proposal of

(Proposer) (Address) for the Roadside Toll Collection System for which Proposals will be received on:

(Proposal Due Date)

and wish to advise that should this Proposal of the Proposer be accepted and the Contract awarded to,

such Proposer, this company agrees to become the surety and provide the Payment and Performance

Bonds required by the Contract for both the Implementation and Maintenance Phases. Such bonds will be

in the amounts identified in the Price Proposal as referenced in the RFP Section I-4.1 Notification of

Awards with terms of the bonds as also provided in that section.

We are duly authorized to do business in the State of Kansas. Surety Company/Address:

____________________________________

____________________________________ ____________________________________

____________________________________ (Authorized Signature) ATTEST: ___________________________________ [Attach Power of Attorney] (Corporate Seal, if any. If no seal, write “No Seal” across this place and sign.)

Roadside Toll Collection System RFP Exhibit D – Forms – Acknowledgement of Receipt of Addenda


Form D-10 Acknowledgement of Receipt of Addenda

(A Word version of the Acknowledgement of Receipt of Addenda is “paper


Roadside Toll Collection System RFP Exhibit D – Forms – Acknowledgement of Receipt of Addenda


ACKNOWLEDGEMENT OF RECEIPT OF ADDENDA

The Proposer shall acknowledge receipt of each addendum to this Request for Proposal by completing this form and including same in the Technical Proposal. Addenda Date By Failure to confirm receipt of addenda may result in rejection of the Proposer’s Proposal. Dated , 2016 Legal Name of Firm By Signature Title NOTE: Attach additional pages as necessary

Exhibits - Kansas Turnpike Authority

Documents

Transcript of Exhibits - Kansas Turnpike Authority