MassDOT Crash Data and Geocoding System RFI.docx

COMMONWEALTH OF MASSACHUSETTS

MASSACHUSETTS DEPARTMENT OF TRANSPORTATION

Request for Information (RFI)

MassDOT Crash Data and Geocoding System

COMMBUYS Bid#: BD-27-1030-0P100-0P110-132187 (this RFI is for ITS81 Cat1 EDM vendors and open to the public)

Table of Contents

RFI Introduction and General Description

MassDOT is seeking information from vendors regarding commercially available Crash Data Management, Geocoding, Safety Analytics, and Public Crash Data Transparency solutions to support the future replacement of the current IMPACT (Interactive Mapping Portal for Analysis and Crash Tracking) platform. We are requesting input on potential approaches, capabilities, and solution architectures to support this initiative.

This effort supports the modernization of how Crash data is managed, geocoded, analyzed, and shared across the Commonwealth. The current environment supports statewide crash processing, geocoding operations, roadway safety analysis, internal reporting, GIS integration, and public access to crash data. While not a primary focus of this effort, MassDOT is also interested in learning about any optional capabilities related to Citation data management and public transparency. MassDOT is seeking to better understand commercially available solutions that improve operational efficiency, analytical capabilities, public transparency, and integration with the Commonwealth's broader technology ecosystem.

MassDOT is primarily interested in commercially available solutions that are currently deployed and operating in production environments, supporting transportation agencies or similar public-sector organizations. Respondents should focus on existing capabilities and operational experience rather than future product roadmaps or planned functionality.

We are seeking information on solutions that provide comprehensive Crash data management, automated and manual geocoding workflows, advanced reporting and self-service analytics, roadway safety analysis, public-facing data portals, and integration with enterprise GIS, roadway inventory, and other business systems. MassDOT is also interested to learn about capabilities that leverage artificial intelligence to improve geocoding accuracy, reduce manual effort, and enhance analysis while maintaining appropriate governance, transparency, and security.

Modernizing the Commonwealth's Crash data environment is a priority for improving roadway safety decision-making, supporting federal and state reporting requirements, increasing operational efficiency, and providing flexible, data-driven tools for both internal users and the public.

Respondents are welcome to propose solutions that combine products or services from multiple organizations. Responses should clearly identify the primary respondent, any subcontractors or partner organizations, the capabilities provided by each, and how the overall solution would be implemented, integrated, and supported.

THIS IS A REQUEST FOR INFORMATION ONLY. Entities responding (“Respondents”) to this Request for Information (RFI) are invited to respond to any or all of the specifics in this document. Responses to this RFI will be used solely to help MassDOT better understand the current marketplace, available technologies, implementation approaches, and industry best practices related to Crash data management, geocoding, safety analytics, and public transparency solutions. The information received may be used to inform the development of a possible future solicitation. This RFI does not in any way obligate MassDOT to issue or amend a solicitation, award a contract, or incorporate any of the RFI provisions or information received into a future procurement. Participation is entirely voluntary and will in no way affect MassDOT’s consideration of any proposal submitted in response to any subsequent solicitation, nor will it provide any advantage or disadvantage to the Respondent in any subsequent procurement that may be issued by MassDOT.

Preamble / History on Current State:

MassDOT maintains a statewide crash data environment supporting crash data management, geocoding operations, roadway safety analysis, internal reporting, GIS integration, and public access to crash information. Crash records originate through the Registry of Motor Vehicles (RMV) and are processed through a series of automated and manual workflows that support geocoding, quality assurance, analysis, reporting, and publication. MassDOT also maintains a separate public-facing Citation Data Portal that provides dashboards, analytical tools, reporting, and public access to statewide citation data.

The current environment has evolved over several years and supports a broad range of operational and analytical functions across multiple MassDOT business units. It includes automated data ingestion, Crash geocoding public workflows, public-facing dashboards, safety analysis tools, GIS integration, reporting capabilities, and transparency services for both Crash and Citation data. While the existing platform provides substantial functionality, it has limitations in flexibility, self-service reporting, integration with modern enterprise data platforms, and the ability to take advantage of emerging technologies such as AI-assisted geocoding and advanced analytics.

The current solution also supports distinct operational and public-facing environments with integrations spanning RMV systems, ESRI GIS services, roadway inventory data, and other enterprise applications. Maintaining these integrations while improving usability, scalability, analytical capabilities, and long-term maintainability is an important consideration for the next generation platform.

Given these considerations, MassDOT is evaluating commercially available solutions that can modernize the Commonwealth's Crash data ecosystem while supporting existing operational workflows, improving analytical capabilities, enhancing public transparency, and providing a flexible foundation for future business and technology needs.

Request For Information

Through this RFI, MassDOT is not soliciting project proposals, but rather requesting input to validate or refine our assumptions and to better understand available solution approaches, implementation considerations, and estimated implementation timelines. Vendors may describe licensing and pricing structures; however, pricing and fee proposals must not be provided.

MassDOT’s goal is to modernize the current environment while preserving and enhancing the operational capabilities used to manage Crash data, improve our geocoding processes, support roadway safety analysis, provide public access to Crash information, and integrate with enterprise business systems.

Solutions described by Respondents should provide comprehensive capabilities for Crash data management, automated and manual geocoding workflows, advanced reporting and self-service analytics, GIS and roadway network integration, public-facing dashboards and data portals, and enterprise integration through modern APIs and data exchange mechanisms. MassDOT is interested in commercially available solutions that improve operational efficiency, analytical capabilities, public transparency, and long-term maintainability while providing flexibility to support future business and technology needs.

Key Requirements

The following capabilities describe MassDOT's vision for a possible future solution. Respondents should describe how their proposed solution addresses each functional area, including any notable capabilities, implementation considerations, or alternative approaches.

1. Crash Data Management

· Support automated ingestion, management, validation, and quality control of Crash, vehicle, and person data.

· Maintain large historical datasets while supporting ongoing operational processing and audit history.

· Support configurable workflows for data review, correction, and lifecycle management.

· Enable bidirectional integration with RMV and other enterprise systems.

2. Crash Geocoding Operations

· Provide a comprehensive Crash geocoding management environment that includes both automated and manual geocoding workflows.

· Support queue management, work assignment, quality assurance, review and approval processes, and administrative oversight.

· Integrate with MassDOT's GIS (ESRI), roadway inventory, and linear referencing systems.

· Synchronize finalized geocoded locations with source systems.

3. Safety Analytics, Reporting, and Public Data Portals

· Enable authorized users to independently create, modify, publish, and maintain reports, dashboards, and analytical products without vendor involvement.

· Provide advanced query, visualization, mapping, charting, and statistical analysis capabilities for Crash data.

· Support roadway safety analysis including network screening, high-crash location identification, corridor and intersection analysis, crash tree analysis, Test of Proportions, and other safety analysis tools.

· Provide modern public-facing portals supporting dashboards, mapping, reporting, querying, and data extraction for Crash data.

4. Enterprise Integration and Data Architecture

· Integrate with enterprise GIS, roadway inventory, ServiceNow, APIs, and other Commonwealth business systems.

· Support modern data exchange through APIs, scheduled synchronization, streaming, or other integration methods.

· MassDOT is particularly interested in solutions that can participate in the Commonwealth's enterprise data architecture by securely synchronizing operational data with enterprise analytical platforms and cloud data warehouse environments, specifically Snowflake.

· Promote open data access and minimize vendor lock-in through flexible integration and data portability.

5. Artificial Intelligence and Advanced Analytics

· Support AI-assisted capabilities including narrative interpretation, address normalization, confidence scoring, suggested location matching, and automated quality review.

· Provide human-in-the-loop workflows with transparency, auditability, and governance controls for AI-generated recommendations.

· Protect Commonwealth data and ensure AI capabilities do not use Crash data to train public or shared AI models without explicit authorization.

6. Security, Accessibility, and Operations

· Protect sensitive information through role-based access controls, secure APIs, encryption, audit logging, and appropriate separation of public and internal environments.

· Comply with applicable Commonwealth accessibility requirements for public-facing and internal functionality, including dashboards, reports, maps, and analytical tools.

· Support scalable statewide operations, configurable administration, and long-term maintainability.

7. Implementation and Vendor Partnership

· Support a practical implementation approach that includes data migration, training, hosting, ongoing support, and product maintenance.

· Demonstrate successful production deployments supporting comparable transportation agencies or public-sector organizations.

· Ability to work collaboratively with MassDOT to validate business requirements, recommend industry best practices, and adapt the solution as operational and technology needs evolve.

· Provide an estimated implementation timeline and describe key implementation phases and milestones.

8. Optional - Citation Data Capabilities

· While not a primary focus of this effort, MassDOT is also interested in learning about solutions that also support Citation data management, reporting, and public transparency.

· If available, describe capabilities related to citation data management, querying, visualization, dashboards, reporting, data extraction, and public access.

· Describe any existing integrations or analytical capabilities that combine crash and citation data to support safety analysis or public transparency.

Additional Information

· The current environment supports approximately 9 million Crash records, processes statewide Crash updates through nightly automated workflows, supports approximately 65,000 public users, and synchronizes geocoded Crash locations with RMV systems.

· Crash records originate through the Registry of Motor Vehicles (RMV) and are processed through automated and manual workflows that include geocoding, quality assurance, reporting, and publication.

· MassDOT is interested in solutions that support both internal operational users and public-facing services while maintaining appropriate separation of sensitive and publicly accessible data.

· Integration with enterprise GIS, roadway inventory, RMV systems, ServiceNow, and other Commonwealth business systems is an important consideration.

· Flexibility, self-service reporting, open integration, and minimizing reliance on vendor-developed reports are key objectives.

· MassDOT is interested in solutions that leverage artificial intelligence to improve geocoding accuracy, operational efficiency, and analytical capabilities while providing appropriate governance, transparency, and protection of Commonwealth data.

· MassDOT is interested in learning about Respondents’ experience supporting statewide transportation agencies or similar public-sector organizations with Crash data management, geocoding, roadway safety analysis, public transparency, and enterprise GIS integration.

MassDOT is interested in receiving information from Respondents outlining their recommended approach to implementing a Crash Data Management, Geocoding, Safety Analytics, and Public Transparency solution, including:

· An overview of the proposed solution, including Crash data management, geocoding workflows, reporting and analytics, public-facing capabilities, GIS integration, and enterprise data integration.

· A proposed implementation approach, estimated timeline and key milestones. Vendors may describe licensing and pricing structures; however, pricing and fee proposals must not be provided.

· Examples of similar implementations or relevant experience supporting state transportation agencies or comparable public-sector organizations, including production deployments for Crash data management, geocoding, roadway safety analysis, and public transparency.

· Whether major capabilities are provided natively within the proposed solution, through configurable functionality, or through integrated third-party products or subcontractors.

· Description of comparable production deployments, implementation experience, and the scale of existing customer environments.

· Whether Respondent’s solution is modern, scalable, and user-friendly, and supports statewide operations, reduces reliance on vendor-developed functionality, improves analytical capabilities and public transparency, and provides a flexible foundation for future business and technology needs.

Please see Response Submissions section below for additional submission instructions.

General Instructions & Information

Information Obtained

THIS IS A REQUEST FOR INFORMATION ONLY. Nothing in this RFI shall be interpreted as a commitment on the part of MassDOT to procure or enter into a contract with any Respondent or any other party.

This RFI will be distributed electronically by posting it on COMMBUYS. All Respondents are responsible for checking COMMBUYS for any addenda or modifications made to the RFI subsequent to the initial posting on COMMBUYS.

Response Submissions and Calendar

Respondents are invited to submit one (1) electronic copy of their responses by August 28th, 2026 at 5PM. A late response may be disregarded.

All responses must include on the first page the official name of the entity submitting the response. Please consecutively number all pages of the response.

Although the responses may include supplemental materials, they should be limited to twenty-five (25) pages (single-sided in 12-point font) and focused specifically on the subjects contained in this RFI.

Respondents must submit responses via COMMBUYS.

Potential for Informational Sessions

Some Respondents may be invited to provide a capability briefing or demonstration of their product/solution.

MassDOT may request additional information from Respondents, including further explanation or clarifications, during the review process.

Respondent Questions

Respondents may only make inquiries and request clarification concerning this RFI by submitting questions via the COMMBUYS Q&A button under this RFI bid number.

Responses to inquiries and clarification questions will be provided electronically to all interested parties via a posting on COMMBUYS.

Respondents may not communicate directly or indirectly with any employee of MassDOT regarding this RFI, except as specified in this RFI.

Respondents may contact the MassDOT Procurement Contact identified below if the RFI is incomplete or if information is missing. Respondents experiencing technical problems accessing information or attachments stored on COMMBUYS should contact the COMMBUYS Helpdesk at COMMBUYS@state.ma.us or the COMMBUYS Helpline at 1-888-MA-STATE.

MassDOT Contact Information Please direct all communications to the following MassDOT contact:

REVIEW RIGHT, PUBLIC RECORDS, COST, AND OTHER

Responses to this RFI may be reviewed and evaluated by any person(s) at the discretion of MassDOT, including independent consultants retained by MassDOT now or in the future.

All responses to this RFI will be a public record under the Commonwealth’s Public Records Law, Massachusetts General Laws Chapter 66 Section 10, regardless of confidentiality notices set forth on such writings to the contrary.

All responses and other documents submitted in response to the RFI become the property of MassDOT. MassDOT is under no obligation to return any documents submitted by a Respondent.

By submitting a response, Respondents agree that any cost incurred in responding to this RFI, or in support of activities associated with this RFI, shall be the sole responsibility of the Respondent. MassDOT shall not be held responsible for any costs incurred by Respondents in preparing their respective responses to this RFI.

Respondents are responsible for entering content suitable for public viewing, as all the responses and questions are accessible to the public. Respondents must not include any information that could be considered personal, security sensitive, inflammatory, incorrect, collusive, or otherwise objectionable, including information about the Respondent’s company or other companies.

image1.jpeg