521BScoreSheet.xlsx
XLSX spreadsheet 83 KB Posted
- Attached to
- Competitive Selection OH|DOT521B26-1
- Contract number
- DOT521B26-1
- Issued by
- Ohio
About this file
The document is a scoring sheet for a state and local contract solicitation, specifically a competitive bid evaluation for transportation data and analytics services. The primary proposers are ROADLINK DATA SOLUTIONS LLP, INRIX INC, and SEADS Technology. The evaluation process involved a comprehensive technical scoring methodology with multiple evaluation categories, weighted scoring, and responsive/non-responsive determination criteria.
The contract appears to be for transportation-related data services, including speed data, route coverage, segmentation, APIs, analytics tools, and various performance metrics. INRIX INC was the highest-scoring proposer with 850 out of 1300 possible points, and the only fully responsive bidder besides ROADLINK DATA SOLUTIONS LLP. INRIX's monthly cost was $109,540 (broken down as $69,540 for data services and $40,000 for analytics tools), with their proposal demonstrating extensive coverage, advanced analytics capabilities, and additional performance features beyond the base requirements. ROADLINK and SEADS Technology were deemed non-responsive due to incomplete proposals, particularly around route and segmentation information.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Summary Cost per Quality Point (CPQP) = (Proposer’s Total Submitted Monthly Cost/ Total Technical Score)
Proposer 1: ROADLINK DATA SOLUTIONS LLP Proposer 2: INRIX INC Proposer 3: SEADS Technology Proposer 4: 0 Proposer 5: 0
| Technical Score | 15 | Technical Score | 850 | Technical Score | 25 | Technical Score | Technical Score |
| Cost | Cost | $ 109,540 | Cost | Cost | Cost | ||
| CPQP | NR | CPQP | 128.87 | CPQP | NR | CPQP | CPQP |
Responsive? Non-Responsive Responsive? Yes Responsive? Non-Responsive Responsive? Yes Responsive? Yes
Proposer 6: 0 Proposer 7: 0 Proposer 8: 0 Proposer 9: 0 Proposer 10: 0
| Technical Score | Technical Score | Technical Score | Technical Score | Technical Score |
| Cost | Cost | Cost | Cost | Cost |
| CPQP | CPQP | CPQP | CPQP | CPQP |
Responsive? Yes Responsive? Yes Responsive? Yes Responsive? Yes Responsive? Yes
Proposer 1 Proposer: ROADLINK DATA SOLUTIONS LLP
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | X | 15 | Vendor did not indicate average penetration rate within Ohio. | 0 | ||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | X | NR | Vendor did not provide information on routes or shape file. | 1 | ||||||
| 1.3.2 Segmentation* | 5 | X | NR | Vendor did not provide information on segmentation. | 1 | ||||||
| 2. Prequalification Questionnaire* | 0 | X | NR | Vendor did not fill out the questionnaire. | 1 | ||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | See Note in total technical score. | 0 | ||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 15 | Vendor failed to meet the high resolution segmentation requirements which considers them non-responsive. Per the RFP, non-responsive proposers will be disqualified from consideration and cost proposal will neither be opened or considered. | 3 | ||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Non-Responsive | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 2 Proposer: INRIX INC
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | X | 25 | 0 | |||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | X | 50 | Coverage % exceeds for SHS per table in RFP (Excluding non cardinals 99.98% from analysis) | 0 | ||||||
| 1.3.2 Segmentation* | 5 | X | 25 | 0 | |||||||
| 2. Prequalification Questionnaire* | 0 | X | 0 | 0 | |||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | X | 25 | 0 | |||||||
| 3.1.2 Dangerous Queueing* | 3 | X | 15 | 0 | |||||||
| 3.1.3 Bottleneck Data* | 5 | X | 25 | 0 | |||||||
| 3.1.4 Map Tile Service* | 5 | X | 25 | 0 | |||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | X | 50 | 0 | |||||||
| 3.2.2 Dangerous Queueing API* | 3 | X | 15 | 0 | |||||||
| 3.2.3 Bottlenecks API* | 5 | X | 25 | 0 | |||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | X | 50 | 0 | |||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | X | 20 | MAP-21 dashboard (included "additional" tools) | 0 | ||||||
| 4.1.2 User Delay Cost | 2 | X | 10 | 0 | |||||||
| 4.1.3 Performance Charts | 5 | X | 50 | travel time comparison and cumulative distribution charts (included "additional" tools) | 0 | ||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | X | 50 | Weather overlay; Corridor Speed Bins (included "additional" tools) | 0 | ||||||
| 4.1.5 Bottleneck Visualization | 3 | X | 15 | 0 | |||||||
| 4.1.6 Trend Map | 3 | X | 30 | Temporal Comparison Maps; energy use and emissions trend map (included "additional" tools) | 0 | ||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | X | 10 | 0 | |||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | X | 25 | 0 | |||||||
| 4.2.2 User Delay Cost API* | 5 | X | 25 | 0 | |||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | X | 10 | Includes additional performance metrics from what were requested (such as turn ratios, extensive delay calculations); Also includes a Signals API; | 0 | ||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | X | 30 | Response shows historical availability exceeding the 97% requirement | 0 | ||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | X | 10 | 0 | |||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | X | 10 | 0 | |||||||
| 6.3 Data Quality | 5 | X | 50 | Response demonstrates higher % observed conditions than required | 0 | ||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | X | 50 | Includes quicker response time than required & escalation contact information | 0 | ||||||
| 7.2 Ongoing Support | 5 | X | 25 | 0 | |||||||
| 8. Training | 5 | X | 25 | 0 | |||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | X | 25 | 0 | |||||||
| 9.2 Experience with Transportation Use Cases | 5 | X | 50 | Table shows extensive use of INRIX data by multiple public agencies | 0 | ||||||
| Max Possible Points | 1300 | Total Technical Score** | 850 | 0 | |||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | $ 69,540 | ||||||||||
| Analytics Tools | $ 40,000 | ||||||||||
| Total Cost | $ 109,540 |
Proposer 3 Proposer: SEADS Technology
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | X | 25 | 0 | |||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | X | NR | Vendor did not provide any information about routes or shape file. | 1 | ||||||
| 1.3.2 Segmentation* | 5 | X | NR | See Note in total technical score. | 1 | ||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 25 | Vendor failed to meet the high resolution segmentation requirements which considers them non-responsive. Per the RFP, non-responsive proposers will be disqualified from consideration and cost proposal will neither be opened or considered. | 2 | ||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Non-Responsive | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 4 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 5 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 6 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 7 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 8 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 9 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
Proposer 10 Proposer:
| Category | DNM | Partially Meets | Meets | Exceeds | Score | Notes | Non-Responsive? | ||||
| Weight | 0 | 3 | 5 | 10 | |||||||
| I. Requirements/Specifications | |||||||||||
| 1. Background | 0 | ||||||||||
| 1.1 Proposal Purpose | 0 | ||||||||||
| 1.2 Data Collection | 5 | 0 | |||||||||
| 1.3 Data Coverage | 0 | ||||||||||
| 1.3.1 Routes* | 5 | 0 | |||||||||
| 1.3.2 Segmentation* | 5 | 0 | |||||||||
| 2. Prequalification Questionnaire* | 0 | 0 | |||||||||
| 3. Required Data and Services | 0 | ||||||||||
| 3.1 Data and Services | 0 | ||||||||||
| 3.1.1 Speed Data* | 5 | 0 | |||||||||
| 3.1.2 Dangerous Queueing* | 3 | 0 | |||||||||
| 3.1.3 Bottleneck Data* | 5 | 0 | |||||||||
| 3.1.4 Map Tile Service* | 5 | 0 | |||||||||
| 3.2 Data Application Programming Interface (API) Requirements | 0 | ||||||||||
| 3.2.1 Speed Data APIs* | 10 | 0 | |||||||||
| 3.2.2 Dangerous Queueing API* | 3 | 0 | |||||||||
| 3.2.3 Bottlenecks API* | 5 | 0 | |||||||||
| 3.3 Data Querying/Download Tool Requirements | 10 | 0 | |||||||||
| 3.4 Initial Data and Services Load Schedule | 0 | ||||||||||
| 4. Required Analytics Tools and Services | 0 | ||||||||||
| 4.1 Speed Data Analytics Tools | 0 | ||||||||||
| 4.1.1 Performance Report | 2 | 0 | |||||||||
| 4.1.2 User Delay Cost | 2 | 0 | |||||||||
| 4.1.3 Performance Charts | 5 | 0 | |||||||||
| 4.1.4 Space-Time Congestion Visualization | 5 | 0 | |||||||||
| 4.1.5 Bottleneck Visualization | 3 | 0 | |||||||||
| 4.1.6 Trend Map | 3 | 0 | |||||||||
| 4.1.7 Real-Time Speed and Incidents Map | 2 | 0 | |||||||||
| 4.2 Analytics Application Programming Interface (API) Requirements | 0 | ||||||||||
| 4.2.1 Performance Report API* | 5 | 0 | |||||||||
| 4.2.2 User Delay Cost API* | 5 | 0 | |||||||||
| 4.3 Initial Analytics Tools Load Schedule | 0 | ||||||||||
| 5. Optional Data, Services, and Tools | 0 | ||||||||||
| 5.1 Traffic Signal Analytics Tools/Platform (Bonus Points) | 1 | 0 | |||||||||
| 5.2 Additional Data, Services, and Tools | 0 | ||||||||||
| 5.3 Initial Load Schedule for Optional Data, Services, and Tools | 0 | ||||||||||
| 6. Availability and Accuracy | 0 | ||||||||||
| 6.1 Data Availability | 3 | 0 | |||||||||
| 6.2 Data Accuracy | 0 | ||||||||||
| TABLE 13: Speed Difference Ranges for Scoring | 2 | 0 | |||||||||
| TABLE 14: Speed Data Latency Ranges for Scoring | 2 | 0 | |||||||||
| 6.3 Data Quality | 5 | 0 | |||||||||
| 7. Support | 0 | ||||||||||
| 7.1 Technical Support | 5 | 0 | |||||||||
| 7.2 Ongoing Support | 5 | 0 | |||||||||
| 8. Training | 5 | 0 | |||||||||
| 9. Qualifications and Experience | 0 | ||||||||||
| 9.1 Qualifications | 5 | 0 | |||||||||
| 9.2 Experience with Transportation Use Cases | 5 | 0 | |||||||||
| Max Possible Points | 1300 | Total Technical Score** | 0 | ||||||||
| * If Proposer does not, at a minimum, meet the requirements set forth in this section, Proposer is considered non-responsive. | |||||||||||
| ** If Proposer does not reach a minimum total technical score of | 600 | , Proposer is considered non-responsive. | |||||||||
| Is Proposer Responsive? | Yes | ||||||||||
| Bid Price (Monthly Cost) | |||||||||||
| Data and Services | |||||||||||
| Analytics Tools | |||||||||||
| Total Cost | $ - |
File details come from the government source that posted it. Updated .