511 Advanced Traveler Information System Services

The Vendor is required to provide 511 advanced traveler information system hosting, maintenance, performance monitoring, data integration, and user support across all traveler information channels.
Solution shall emphasize reliability, maintainability, usability, scalability, cybersecurity, and accessibility, providing an intuitive experience that promotes safe and efficient mobility statewide.
- Functional requirements
1. Website (WS)
•    The system shall include a publicly accessible website at www.511ga.org that is accessible through a standard web browser (e.g., google chrome, Microsoft edge) and shall support current and new major browser versions for the duration of the contract.
•    The website map shall use GIS data sources (e.g., shapefiles, geodatabases) to render geographically accurate maps.
•    The website shall display GIS-based data layers including county boundaries, mile markers, rest areas, ports of entry, and evacuation routes.
•    The website map shall allow users to configure GIS layers and display layers from third-party GIS systems.
•    The website shall provide the ability to display, query, sort, and filter 511 data on a GIS-based map.
•    The website shall represent each data point on the map using an icon or symbol that is unique to its data type.
•    The website shall allow users to toggle layers on and off to customize the map display.
•    The website shall clearly identify the version control information.
•    The website shall allow operators to update, verify, and publish traveler information, such as event details, lane closures, and incident impacts, either directly within the website or through its integrated backend system.
•    The website shall allow users to select and view specific regions or corridors within state.
•    The website shall allow users to search by route number, city, landmark, or by entering origin and destination locations to view roadway events and conditions along their intended travel path.
•    The website shall provide route-specific information including estimated travel time, incidents, and construction impacts.
•    The website shall allow users to create and manage personalized travel routes and favorite devices through a registered account.
•    The website shall allow registered users to configure and receive route-based alerts via email or text message.
•    The website shall provide filtering capabilities by event type, severity, direction, and time of report.
•    The website shall provide hyperlinks to relevant department resources, social media pages, and partner websites.
•    The website shall include a section explaining 511 system features and use.
•    The website shall include a “contact us” form or equivalent method for public inquiries, and all submissions shall be routed to a designated department email inbox (currently [email protected]).
•    The website shall include a news or announcements section for safety alerts, travel forecasts, and maintenance updates, and “code-red” style banner alerts for major events that require heightened user attention.
•    The website shall provide authorized operators with a web-based interface to create, schedule, and manage alerts, news items, and announcements, including the ability to define start and end times for when each message is displayed.
•    The website shall include external links to 511 systems of neighboring states and national traveler information resources.
•    The website shall display live camera feeds and image snapshots provided by department video system.
•    The website shall display events, dynamic message sign (DMS) messages, and vehicle detection system (VDS) data provided by department ATMs.
•    The website shall display weather radar imagery, forecasts, and alerts from the national weather service (NWS).
•    The website shall display user-reported events, hazards, and incidents received from Waze and shall allow filtering by the Waze-supplied confidence levels before they are displayed to the user.
2. Mobile application (MA)
•    The system shall include native mobile applications for iOS and android platforms that provide equivalent functionality to the 511 website.
•    The mobile applications shall support current and commonly used operating system versions and device types needed to serve the majority of active users.
•    The mobile applications shall use the same user account credentials as the website.
•    The mobile applications shall provide real-time traveler information, including incidents, construction, DMS messages, camera snapshots, live camera video feeds, and route conditions.
•    The mobile applications shall support user geolocation, route-based alerts, and the ability for users to save and managed preferred routes and locations.
•    The mobile applications shall provide configurable push notifications for incidents, lane closures, or other traveler alerts relevant to a user’s saved routes or locations.
•    The mobile applications shall synchronize with the same data sources as the website to ensure consistency of information across all platforms.
•    The mobile applications shall allow users to provide feedback, report issues, or request assistance through integrated forms or contact links.
•    The mobile applications shall synchronize each user’s saved routes, locations, preferences, and notifications with their website account, and vise-versa.
3. Telephone system (TS)
•    The system shall include a telephone-based traveler information service accessible by dialing “511” from any phone within the state.
•    The telephone system shall provide an IVR interface offering voice-enabled access to traveler information, including traffic conditions, incidents, and construction updates.    
•    The telephone system shall route callers to a live department center operator or other designated support resource based on the caller’s request or service needs.
•    The telephone system shall provide both English and Spanish language options for callers.
•    The telephone system shall capture and report configurable call routing data, queue statistics, and performance metrics (e.g., call volume, average call time) for department review and system monitoring.
•    The telephone system shall maintain data consistency with the 511 website and mobile applications.
•    The telephone system shall support a configurable 511 menu structure and content delivery format that may be updated at any time and shall not implement modifications without written approval from department.
•    The telephone system shall apply routing logic consistent with department call-handling policies, ensuring that each call type is directed to the appropriate support lines or resources based on predefined rules established by department.
•    The telephone system shall provide accessibility services for audio-impaired users and maintain high-quality, intelligible voice audio throughout the call flow.
4. Data reporting (DR)
•    The system shall allow data to be exported in csv and pdf formats.
•    The system shall allow users to select which data elements (e.g., fields, columns, attributes) are included in an export.
•    The system shall allow users to filter which data records are exported based on user-defined criteria.
•    The system shall provide all underlying data elements, analytics outputs, and export functions necessary for the offeror to produce the monthly 511 program report.
5. Data storage (DS)
•    The system shall retain all traveler information data, including current and historical events, DMS messages, and system logs.
•    The system shall collect and store all ATMs data ingested, processed traveler information, operator actions, and dissemination logs.
•    The system shall log all operator actions, data updates, alerts, and API transactions for auditing and system integrity.
•    The system shall retain all data in accordance with department data retention policy.