Hardware Table 1-1. Milestone Payment Schedule Milestone Name Triggering Percent of Mobilization Notice to Proceed and Approval of Responsibility Matrix 10% Management/QA Plans Approval of Program Management and Quality Assurance Plans 5% Design Acceptance Approval of the Business Rules Document, Detailed Design Document and Requirements Traceability Matrix 10% Reports Design Acceptance Approval of the Reports Detailed Design Document 5% Factory Test Approval Approval of the Factory Test Report 10% Approval of Plans: Training Installation Transition Data Migration Approval of all Plans listed 10%
Available to generate Transaction Records during all periods when Tolling Point is scheduled to be open per agreed schedule. See Sections 3.6.1.1 and 6 Available: All aspects of the Roadside subsystems are performing all functions necessary to generate Transaction Records and notify and the customer through the lane during the period of measurement. This shall exclude any planned maintenance activities. below the Service Level Plaza Functions Availability Percentage of time that all Plaza Subsystems be Fully Available. Plaza Subsystems: See Sections 3.6.1.2 and 6 Fully Available: All aspects of the Plaza Subsystems are operational and performing their required functions. One (Plaza-wide) One Month Total number of hours during the month. Total Number of Hours that all Plaza Subsystems were Fully Available 99% $250 for every hour below the Service Level
Back Office Functions Availability Percentage of time that all Back Office Subsystems (except for the Website) be Fully Available. Back Office Subsystems: See sections 3.6.1.3 and 6 Fully Available: All aspects of the Back Office Subsystems (except for the Website Subsystem) are operational and performing their required functions. One One Total number of hours during the month. Total Number of Hours that all Back Office subsystems (except for the website) were available 99% $250 for every hour below the Service Level Host Availability Percentage of time that all of the required Host Functions be Fully Available Host Functions: See Sections 3.6.1.4 and 6 Fully Available: All of the required Host Functions are performed by either the Primary Host Subsystem or the Secondary Host Subsystem One One Month Total number of hours during the month. Total number of Hours that all Host Subsystems were Fully Available 99.5% $400 for every hour below the Service Level
Website Availability Percentage of time that the Website Functions shall be Fully Available. Website Functions: See Sections 3.6.1.4 and 6 Fully Available: All aspects of the website are operational and performing their required functions. One One Month Total number of hours during the month. Total Number of Hours that all Website was Fully Available 99% $300 for every hour below the Service Level - Table 7-3. Accuracy Performance Indicators # Name Performance Measure Definitions Number of Measurements Period of Measurement Denominator Numerator Service Level Liquidated Damages Assessment Vehicle Detection and Transaction Generation Accuracy Percentage of vehicles passing a Tolling for which the NTCS generates one and only one transaction. Tolling Each toll lane in a single direction One for each Tolling (2N, 3N, 4N, 5N, 5S, 6N, 6S, 7S, 8S, 9S, and 10S) Monthly Total number of vehicles passing the Tolling Point. Total number of vehicles that generated one and only one transaction record. 99.90% $1,000 for every 0.1% below the Service Level
Axle Counting Accuracy Percentage of vehicles passing a Tolling Point for which the NTCS correctly reports the number of axles. Tolling Each toll lane in a single direction One for each Tolling Point (2N, 3N, 4N, 5N, 5S, 6N, 6S, 7S, 8S, 9S, and 10S) One Month number of vehicle records generated Total number of vehicle records that contain the correct axle count 99.80% $100 for every 0.1% below the Service Level MacPass RFID Capture Rate Accuracy Percentage of vehicles passing a Tolling Point for which the NTCS correctly reports at least one RFID Transponder (Tag) ID if a tag has been correctly mounted (according to manufacturer specification). Tolling Point: Each toll lane in a single direction One for each Tolling Point (2N, 3N, 4N, 5N, 5S, 6N, 6S, 7S, 8S, 9S, and 10S) One Month number of vehicles passing all Tolling Points with a correctly mounted tag. number of vehicles passing all Tolling Points with at least one correctly reported Tag ID. 99.80% $100 for every 0.1% below the Service Level Vehicle Framing Accuracy Percentage of vehicles passing a Tolling Point for which the NTCS correctly assign all data captured (tag reads, vehicle axles, toll collector inputs, etc.) and include it in the recorded transaction Tolling Point: Each toll lane in a single direction One One Total number of vehicle records captured. Total number of vehicle records correctly aligned with all captured data. 99.80% $100 for every 0.1% below the Service Level
Transaction Transfer, Storage, and Retention Percentage of transactions correctly transferred from the Tolling Point to the Host database. Tolling Point: Each toll lane in a single direction One One Month Not Applicable Not Applicable 100% Expected Revenue Lost - Table 7-4. Timeliness Performance Indicators # Name Performance Measure Definitions Number of Measurements Period of Measurement Denominator Numerator Service Liquidated Damages Assessment
TI-01 Transaction Records submitted to the Host database The average time to successfully transmit Transaction Records to the Host database, in seconds. Measurement of the time period shall begin with the time the vehicle exits the Tolling Point or the transaction is completed at any other subsystem Transaction Records: Any toll transaction, payment, deposit, tag sale, replenishment, etc. generated by any of the NTCS Subsystems Tolling Point: Each toll lane in a single direction One One Month Total number of Transaction Records generated by all NTCS Subsystems. Total number of Transaction Records successfully transferred to the Host Database in the required time frame. 60 Seconds $500 for every second above the Service Level TI-02 Timeliness of TVL Updates to Roadside The average time to successfully update MacPass status changes in all lane controllers, in seconds. The time period starts when the transaction that causes the status update posts to the database. One One Month Total number of status changes Total number of updates that are completed in all lane controllers in the required time frame. 60 Seconds $500 for second above the Service Level TI-03 Timely Report Generation (<1,000,000 Records in the Report) Average time to generate a report, in seconds. One One Month Total number of reports generated Total number of reports generated in the required time frame. 30 Seconds $250 for second above the Service Level
TI-04 Timely Report Generation (>=1,000,000 Records in the Report) Average time to generate a report, in seconds. One One Month number of reports generated Total number of reports generated in the required time frame. 120 Seconds $250 for every second above the Service Level TI-05 Timely Submission of Monthly KPI Report The KPI Report shall be submitted no later than the 10th business day of the month covering the previous calendar month One One Month Not Applicable Not Applicable 10th business day of the month $200 for every day past the due date TI-06 Timely Maintenance Response – Priority One The TSI Respond to Notification of a Priority One issue within a required time frame Respond: The TSI calls/texts the assigned contact at the Bridge Notification: An alert or alarm generated by the NTCS or a phone or email from Bridge personnel Each Occurrence Not Applicable Not Applicable Not Applicable 60 minutes June – September 120 minutes October - May $100 for 15 minutes past required time
TI-07 Timely Maintenance Response – Priority Two The TSI shall Respond to Notification of a Priority Two issue within a required time frame Respond: The TSI calls/texts the assigned contact at the Bridge Notification: An alert or alarm generated by the NTCS or a phone or email from Bridge personnel Each Occurrence Not Applicable Not Applicable Not Applicable 120 minutes June – September 180 minutes October - May $50 for every 15 minutes past required time TI-08 Timely Maintenance Response – Priority Three The TSI shall Respond to Notification of a Priority Three issue within a required time frame Respond: The TSI calls/texts the assigned contact at the Bridge Notification: An alert or alarm generated by the NTCS or a phone or email from Bridge personnel Each Occurrence Not Applicable Not Applicable Not Applicable 240 minutes June – September 360 minutes October - May $50 for every 15 minutes past required time
B. Address all aspects of this section, including: Provide a sample of each standard report that is available from the proposed system. The sample reports must be generated utilizing real data from a production system. The sample reports may be sanitized by redacting agency or customer information. Sample reports will be excluded from the page limit and should placed in an appendix to this TRG. Specify the proposed reporting software product(s). Describe the functionality for reports supporting trails on transaction processing and account management activity performed by the system or users. Describe how the solution would meet the key performance indicators. Describe the “ad-hoc” reporting functionality to be provided. If this solution has been deployed and is collecting revenue, provide location(s), point(s) of contact, and any differences from the required solution. [Provide a description of what or how for this section. Delete this text when completed] [If the solution has been deployed in revenue collection (Question A-3) provide a list of locations and a point of contact for each. Delete this text when done.] 6.7.4 Finance/Audit Subsystem Requirements A. Will the Proposer meet requirements as stated in the referenced section of the RFP? (1) Proposer Response: Check One Yes, as stated No, will not meet at all __________________________________________________ (2) Proposer Response: If “Yes” then Check One: Meeting these requirements requires no additional development Meeting these requirements requires minimal additional development Meeting these requirements requires significant additional development __________________________________________________ (3) Proposer Response: If “Yes, then Check One: This solution has been deployed in revenue collection This solution has not been deployed in revenue collection
Test Reports 3.7.3 5 days after successful completion of each test 7 days Individual Test Plans 3.7.4.1 through 3.7.4.5 30 days prior to start of the test 14 days Backup and Disaster Recovery Plan 3.8 15 days after approval of DDD 21 day Installation Plan 3.9 60 days prior to installation 21 days Transition Plan 3.10 90 days to beginning of installation 21 days Data Migration Plan 3.11.2 120 days prior to revenue collection 21 days Training Plan 3.12 90 days prior to beginning of installation 21 days Maintenance Plan 3.13 60 days prior to beginning of Phase III (Warranty) 21 days Succession Plan 3.14 90 days beginning of Phase IV (Maintenance) 21 days Toll Collector’s Manual 3.15.1 30 days prior to Toll Collector Training 14 days Plaza Supervisor’s Manual 3.15.2 30 days prior to Plaza Supervisor Training 14 days Vault Operations Manual 3.15.3 30 days prior to Vault 14 days
Operation Training Reports Manual 3.15.4 30 days first training class (of any kind) 14 days Maintenance and Service Manual 3.15.5 30 days to Maintenance Training 14 days Auditor’s Manual 3.15.6 30 days to Auditor Training 14 days Shop Drawings 3.16 15 days prior to beginning of manufacturing 14 days Lists and Catalogs 3.17 30 days after approval of Detailed Design Document 14 days Drawings 3.18 30 days revenue collection begins 21 days