HELP_Alerts_Proposal_RFP_549-26_-_InformationLogistics.pdf

www.ilogcorp.com

OHIO DEPARTMENT OF TRANSPORTATION

Request for Proposal No. 549-26

Wireless Emergency Alert Services

Submitted by: Information Logistics, Inc.

October 20, 2025

Contents Executive Summary

1. Introduction & Understanding of Proposal Purpose

About Information Logistics (ILOG)

ODOT RFP 549-26 and HELP Alerts: Overview & Understanding

2. Scope of Work & Requirements

2.1 Service Requirements

2.1.1 Web-Based IPAWS WEA Delivery

2.1.2 Map-Based Polygon Targeting

2.1.3 Ohio Highway System Mapping

2.1.4 Dissemination to Cellular Carriers

2.1.5 Secure Workflow for Alert Review via ODOT’s Traffic Management Center

2.1.6 Two-Way Communication Capability

2.1.7 Subscription-Based Updates

2.1.8 Easy Opt-Out Mechanism

2.1.9 Drivewyze Integration

2.1.10 Event Reporting

2.1.11 PDF Export of Reports

2.1.12 Production and Test Environments

2.1.13 Operational Live Service

2.1.14 Ready for Immediate Use

2.2 Technical Support & Maintenance

2.3 Training

3. Qualifications & Experience

3.1.1 FEMA’s AOSP List

3.1.2 Deployment to similar size/scope agencies

4. Contract Information

4.1 Duration

4.2 Pricing

4.3 Deductions

5. Proposal Submission Requirements

6. Demonstration Period

Executive Summary The Ohio Department of Transportation (ODOT), in partnership with the Ohio Turnpike Infrastructure Commission (OTIC), seeks a robust Wireless Emergency Alert (WEA) service to enhance public safety during catastrophic transportation incidents and emergencies.

Information Logistics, Inc. (ILOG) is pleased to offer its IRIS HELP Alerts solution; a mature, proven, web-based emergency alerting platform. IRIS HELP Alerts has been adopted by many transportation agencies and is currently deployed and operational within ODOT.

HELP Alerts is designed to deliver IPAWS-compliant WEA messages to motorists and facility occupants in real time, using geofenced targeting and secure workflows. The system supports two-way communication, opt-in/opt-out functionality, and integration with third-party platforms such as Drivewyze. It also includes comprehensive reporting, training, and technical support.

This proposal confirms that HELP Alerts meets or exceeds all requirements outlined in RFP No. 549-26. The system is fully operational, requires no additional development, and is ready for immediate use. ILOG brings extensive experience in emergency communications for transportation and is committed to supporting ODOT’s mission to improve safety and situational awareness across Ohio’s transportation network.

1. Introduction & Understanding of Proposal Purpose Information Logistics, Inc. (ILOG) is pleased to submit this proposal in response to RFP No.

549-26 issued by the Ohio Department of Transportation (ODOT).

About Information Logistics (ILOG) ILOG is a small technology company headquartered in southern New Jersey, primarily serving the transportation industry. ILOG’s mission is twofold; to help transportation agencies achieve “vision zero” with innovative, practical technology solutions, and to provide the highest quality communication services, the most responsive customer service and the most skilled engineers and technicians in the industry to fully support its clients' technology needs.

The company currently offers full suites of travel information services including

• Interactive web maps and websites

• Subscriber services

• IVR systems and digital assistants

• Mobile apps for traveler services and problem reporting, incident response and communication, dynamic tolling information, and various other functions

• Alexa/Siri/Google talents

• Internet radio

• Multi-channel remote video streaming from mobile devices

• Precisely getting location data from travelers in distress and distributing alerting information to internal responders and public information navigation/alerting systems through third party partnerships.

We are experts at data integration and accommodating multiple security protocols for accessing the data. We do the work to have our systems ingest and normalize available data sources in their current formats, rather than forcing data sources to adjust to our native formats.

However, we are likely best known as innovators. ILOG has received numerous awards for its first-of-a-kind hands-free mobile apps, for special implementations of 511 Traveler Information solutions, and for HELP Alerts, our communications tool for emergency situations, when every second counts.

It is our belief that innovation is a culture where collaborators present problems and devise solutions, so we listen carefully to our clients.

The ODOT RFP requests the functionality and workflow that is fulfilled by ILOG’s HELP Alerts system which is currently in use by ODOT and many other transportation agencies.

We are the original creators of the proposed system flow and UI, and the works are protected by registered copyrights. We warrant that there are no claims of intellectual property infringement against this system.

We thank you for the opportunity to present this proposal and look forward to answering your questions and demonstrating exactly how ILOG and ODOT together can move the mark toward vision zero.

ODOT RFP 549-26 and HELP Alerts: Overview & Understanding The background and intentions listed in this RFP clearly delineate ODOT’s and OTIC’s objectives for a system to address the special communications needs that arise during catastrophic emergencies so that the agencies can:

• Communicate with travelers stuck in the area of the emergency.

• Warn travelers before entering the emergency area.

• Alert and divert commercial vehicles at major decision points before approaching the emergency area and backlog.

• Enhance the agencies’ situational awareness, and

• Access the proposed solution as a web-based service.

To perform these functions, ODOT and OTIC require

• Software that has been approved as a FEMA Alert Origination Software Provider who can send WEA Alerts for distribution through participating carriers.

• The ability to define an emergency area through mapping tools on a map that has been configured to Ohio’s roadway system and ODOT facilities.

• The ability for travelers or visitors/employees of ODOT facilities to opt-in and opt-out for on-going two-way communications so that ODOT can continue to provide safety guidance without issuing additional WEA alerts.

• Reporting mechanisms during and after emergency events.

ILOG’s HELP Alerts platform was purpose-built to meet these needs of transportation agencies.

Our proposed solution is HELP Alerts. A mature and proven, web-based emergency alerting system, HELP Alerts, fulfills every requirement of this RFP. Additionally, the platform is improving with new functionality, new integrations and even user interface (UI) changes suggested by HELP Alerts users. ILOG keeps in close contact with the FEMA IPAWS lab to be sure that our system offers the easiest user experience, the most advanced tools and is well prepared for changes and updates to the WEA program. We firmly believe in sharing information with our users so that best practices and corresponding system improvements rise to the surface.

The HELP Alerts system has been implemented in multiple transportation agencies nationwide. It is currently used by ODOT, where the system is branded “OHGO Connect”, and contains WEA templates for transportation events, required monthly test (FEMA competency test requirements for COG holders) and for ASAP events surrounding ODOT facilities.

The following sections will address each item listed in the Scope of Work and Requirements and will describe how HELP Alerts meets and/or exceeds each item.

2. Scope of Work & Requirements

2.1 Service Requirements

HELP Alerts meets or exceeds all service requirements outlined in Section 2.1 of the RFP:

2.1.1 Web-Based IPAWS WEA Delivery

HELP Alerts is a secure, web-based platform that enables authorized users to originate and send IPAWS-compliant Wireless Emergency Alerts (WEA). The system is accessible via standard web browsers and requires no local installation, ensuring rapid deployment and ease of use across agencies.

The HELP system is fully redundant and load balanced. This means that multiple, identical webservers and databases support the system. If any component should fail, access to

HELP remains uninterrupted by directing requests to an identical operational system. It also means that ongoing system updates can almost always be accomplished without maintenance windows requiring downtime.

2.1.2 Map-Based Polygon Targeting

The system includes an intuitive, map-based interface that allows users to draw custom polygons directly on the map to define the target alert area. This ensures precise geotargeting of WEA messages to affected zones, minimizing over-alerting and maximizing relevance.

The base map for the system is a Google map, which provides familiarity as well as the Google map layers to see map, satellite or pegman views.

Polygons are easily drawn on the map using the drawing tools. If you want to change a shape that you just drew, you can simply click the “Clear” tool on the map, and the errant polygon disappears, but the event information you entered is unchanged.

2.1.3 Ohio Highway System Mapping

HELP Alerts is pre-configured Google mapping, which standardizes the display of Ohio’s state highway system, including major interstates, state routes, and local roads. Real-time Google traffic is displayed on the map, enabling ODOT users to view the extent of the traffic incidents, supporting accurate polygon creation and situational awareness. Alternate traffic data sources can be made available on the map, with a map control that allows ODOT users to switch between the data sources.

The system has been designed with an open data structure so that it can be expanded to meet your evolving emergency event management requirements. In the context of mapping capabilities, this means that as additional ODOT-specific data is available and needed in the HELP system, the data can be added to the map as additional interactive map layers.

As examples, these layers could be mile markers, CCTV cameras, construction zones, or resource locations.

ILOG has also partnered with HAAS Alert and the HELP system is able to display the active locations of HAAS equipped vehicles on the map, along with the emergency area polygon and other ODOT data layers. Please note that adding some of these layers may incur additional charges beyond the proposal.

2.1.4 Dissemination to Cellular Carriers

The HELP Alerts platform integrates with FEMA’s IPAWS system to disseminate WEA messages to participating cellular carriers. Alerts are delivered to mobile devices located within the defined polygon, regardless of whether the emergency area polygon is on or off the highway system, including ODOT facilities.

The HELP Alerts system is currently used by ODOT, where the system is branded “OHGO Connect”, and contains WEA templates for geofenced transportation events, required monthly tests (FEMA competency test requirements for COG holders) and for events involving ODOT facilities, called ASAP events. The HELP system can be expanded to contain templates for other event types as use cases/applications for the system expands.

ILOG stays on top of changes to FEMA’s IPAWS system, making sure that any new requirements are developed and tested before FEMA implements the changes in their production environment. We also meet with FEMA’s IPAWS lab regularly to review the HELP system, new features that have been implemented, and to solicit their advice on questions that our agency users have asked of us.

2.1.5 Secure Workflow for Alert Review via ODOT’s Traffic Management Center HELP Alerts includes a built-in workflow process that is configured to each agency’s preferences by leveraging the system’s role-based access and ability to distribute notifications based on either role/user preferences or agency business rules. The workflow/event approval process is secure, role-based, and auditable, ensuring that only authorized personnel can transmit alerts.

For basic event creation and WEA issuance, the following roles are commonly used by agencies to facilitate workflow.

• Admins – Staff who create the original alert details and draw the emergency area shape.

• Super Admins – Designated staff who receive an email or text notification that a new event was created and who approve the Admin’s initial event or adjust the event details before it goes to an IPAWS admin for WEA-issuance approval. This level is not used in the current ODOT system.

• IPAWS Admins – Designated staff who receive an email or text notification that an emergency event is created and waiting for their approval to issue the WEA alert.

The IPAWS admin approves the event to be issued as-is, or sends it back to the Admin for correction, along with guidance for what needs to be changed. As soon as the event is approved by an IPAWS admin, the WEA is immediately issued for the alerting area specified.

There is also a read-only role available, which agencies assign to staff who need to see the details of the emergency event as it unfolds, but who do not need the ability to add or modify information in the HELP system.

A recent enhancement to the HELP system added a new role to the system, based on integration with Drivewyze commercial vehicle alerting system. The capabilities of the Drivewyze role can be assigned to separate staff or can be added to any other role (except read only). The Drivewyze integration is discussed in section 2.1.9.

2.1.6 Two-Way Communication Capability

In addition to WEA delivery, HELP Alerts supports two-way communications. When an ODOT operator initiates a HELP event with two-way communication, a public-facing website is activated, and its URL link is automatically added to the WEA message. This website presents information about the emergency event and contains an opt-in for the public to receive ongoing incident updates and guidance from ODOT, and to select their message delivery as via SMS text messaging or automated phone calls.

The opt-in process helps impacted travelers to receive official communications, but it also provides ODOT with demographic information about the travelers through a few questions that are asked on the public website opt-in page. These questions can be changed for each event, but by default indicate the number of opt-in travelers, the type of vehicle they are in, and their location. These demographics are presented in the ODOT administrative dashboard and traveler locations are plotted on the admin map.

As the event continues, ODOT can send updates/instructions to travelers, or to groups of travelers (e.g. to all passenger vehicles, or all school buses) without sending numerous additional WEA messages - and travelers can respond to the ODOT text messages. From the administrative dashboard, ODOT operators can view messages from travelers and respond to them individually or in groups.

The system has an additional communications component that enables ODOT admins to create a survey on the fly, and view travelers’ responses as part of the opt-in user grid. In one view, Admins can see each user, their location, and all other information collected, such as location, vehicle type, fuel level, HVAC operating, or any other event-appropriate survey responses.

The website/SMS/IVR automated phone interactions described are not enabled when one-way alerting (WEA) is selected for the event. If two-way communications are not needed for the event, ODOT operators can simply initiate a one-way event to issue a WEA-only notification.

A note regarding text messaging short codes.

The HELP system uses text messaging as the main distribution of non-WEA messages between ODOT and travelers, via a dedicated short code (a 5-digit code), not a long code (a 10-digit phone number). While short codes are more difficult to acquire and more expensive to maintain than long codes, the benefits of a short code for this application are significant.

A dedicated short code:

• is consistent. Your HELP alert will come from a constant, 5-digit number.

• has better deliverability and is faster than a long code. Since short codes are vetted by carriers, they have greater reliability and are less likely to be spam-filtered.

• has a much greater throughput than long codes. Short codes allow up to 400 messages per second (long codes can send up to 30). For example, if the DOT has a rapidly changing event with 5,000 opt-in users, and sends a message to all users, a short code will send all messages in about 13 seconds. The long code will send them in in about 167 seconds – just under 3 minutes. This difference makes all the difference when every second counts.

ILOG’s commitment to providing the best technology means that we will use the most rapid and reliable delivery available. ILOG will provide and maintain the HELP short code and respond to ongoing carrier compliance audits as a part of the standard system maintenance.

2.1.7 Subscription-Based Updates

When an ODOT admin creates a HELP Alert and selects the two-way communication option, the HELP system establishes a website with event information and to allow opt-in for ongoing two-way communications.

When the WEA alert is sent to people inside the event polygon, the WEA message is appended with the URL of the HELP event website. Recipients of the WEA message simply click on the WEA-embedded URL to get to the site and opt-in to receive ongoing updates via SMS text or automated phone call. Once subscribed, they receive follow-up messages/situational changes/guidance and instructions from ODOT until the incident is resolved, or the subscriber opts-out.

Communications are managed by admin operators who access the HELP Alerts Admin panel through a secure, authenticated web page. Using a simple interface, these Admins can select to send messages to all registered users or any subset of registered users, simply by clicking on the appropriate checkbox and typing in the message that is to be sent via SMS/phone.

Whether there are 50 people opted-in or 50,000 people opted-in, the messaging process is the same and is easily and rapidly accomplished.

If citizens respond to the text messages from ODOT, ODOT operators can view all incoming messages on a consolidated messages screen, or as threaded communications associated with each registered user. ODOT operators can then choose to respond directly to individual citizens, if an individual response is warranted.

2.1.8 Easy Opt-Out Mechanism

HELP Alerts provides a simple opt-out process via SMS, allowing users to unsubscribe from incident notifications at any time simply by typing the keyword “STOP” as a text reply to any message they have received from the system. By texting back the keyword “INFO” to any message, users will receive more detailed instructions about the system and about opting out. These keywords and their functions comply with SMS/carrier requirements.

Regardless of keywod use, all subscribers are automatically opted-out of notifications when the emergency event is closed, and their phone numbers are obfuscated from the system.

2.1.9 Drivewyze Integration

The HELP Alerts platform is integrated with Drivewyze Smart Roadways. ODOT Administrators can send Drivewyze Emergency Alerts to its extensive network of in-cab systems in commercial vehicles. These safety alerts can be sent to commercial vehicles who are within the emergency area, approaching the area, or who are near decision points where they can select an alternate route.

The user interface for Drivewyze Emergency Alerts has been developed to closely resemble the HELP Alerts administrative interface. The similarities between the two user experiences help to minimize training and maximize efficiency.

Access to the Drivewyze module of HELP Alerts is role/permission based and can be granted as a stand-alone role or can be added to an existing agency user’s permission profile.

There are several special features for Drivewyze Alerts entered through the HELP system:

• The Drivewyze Alert can be geographically placed anywhere within the state or across state lines – i.e. you are not restricted by a state boundary for entering the alert. This enables ODOT to warn commercial traffic of an issue at or near a state line or causing/resulting from a backup that extends into an adjoining state.

• From a workflow perspective, Drivewyze entries do not require IPAWS-admin level approval so that once a Drivewyze alert is created, it can be sent immediately.

• Drivewyze alerts can be scheduled to start and end automatically at a future time.

• A Drivewyze alert can be issued with or without a corresponding HELP alert.

• The HELP Drivewyze management screen allows admins to view active alerts, historical alerts and scheduled alerts

The integration with Drivewyze enables ODOT operators to manage multiple emergency communications through one HELP Alerts interface.

2.1.10 Event Reporting

HELP Alerts automatically logs and timestamps key activities including event area, message content, approval actions, IPAWS approver actions, and delivery confirmations.

These logs are accessible to authorized users for review and audit purposes and contain all the demographic information such as traveler location and number of registered users. It is important to note that the HELP Alerts system does not store any personally identifiable information (PII) once an event is closed so that registrants’ phone numbers are anonymized and not available in reports.

From the logged data, a variety of reports are available, including:

• Situation Reports (Sitreps): a summary of key event details and messaging performed while an event is still active, reporting up-to-the-minute information available.

• After-action reports: a summary of key event details and messaging performed during an event which is now closed.

• IPAWS Request history for each event including the request content and response content.

• Event summary reports specified by date and detail level.

• Map visualization of activations by date.

In addition to the standard reports, an API containing key event information is included with the system so that ODOT can easily pull information into other agency dashboards or reports.

2.1.11 PDF Export of Reports

Situation reports (Sitreps) and after-action reports (described in section 2.1.10 above) can be viewed in PDF format and downloaded on demand. Details contained in the after-action reports are also available in the Event summary reports that are downloaded in Excel format.

After action reports and IPAWS request history logs are retained in the HELP system for the duration requested by the agency, up to 5 years.

It is important to note that the system will not systematically report or display the phone numbers of subscribers for PII considerations.

2.1.12 Production and Test Environments

The HELP Alerts system includes both a live/production environment and a functionally identical training environment. These two environments are separate systems and have separate login credentials so that risk of a training exercise accidentally being entered into the production system is minimized. Both the training and production environments are available 24x7 to all participating agencies.

By making the training environment available 24x7, training and exercises can be easily scheduled for all staff shifts. Per FEMA requirements, the training environment is equipped with the agency’s demo COG ID so that monthly required testing with FEMA can be performed without affecting the production system or issuing a live WEA.

Users who have credentials for the training system and production system are usually the same people, with the same roles and permissions in both environments. However, there can be additional people in the training system, or existing users may be assigned additional roles in the training system so that they can gain familiarity and procedural/functional competence before they get credentials in the production system.

User management for users among all the state’s participating agencies can be performed within the HELP system by authorized ODOT staff or it can be done by ILOG support staff with authorization.

The training environment is used not only for refreshing and practicing skills but is also used to test-out/train-on new functions and features in the system, prior to the new items being promoted to the production system. This process allows time for users to see and practice new items/changes well before a live emergency event occurs. ILOG will always work closely with ODOT staff to coordinate any changes to the system.

2.1.13 Operational Live Service

The HELP Alerts system, branded as OHGO Connect, as described, is currently operational and actively sending IPAWS WEA messages (as required in Section 2.1.1), as well as sending Drivewyze Emergency Alerts.

Branded as OHGO Connect for ODOT, the system has been in use by ODOT since 2021.

Other transportation agencies, such as TxDOT, GDOT, NCDOT, ALDOT, NJDOT are also actively utilizing HELP Alerts for a wide variety of use cases. Roadway emergencies due to crashes, floods, blizzards, hazmat spills, bridge strikes, hostage situation, police activity, fog, wildfire smoke, and building fires alongside the highway are just some of the situations where the HELP alerts system has been activated and demonstrated its reliability, flexibility and effectiveness in real-world scenarios.

2.1.14 Ready for Immediate Use

The services described above are available out-of-the-box and are currently in use by ODOT, which is called OHGO Connect in Ohio.

No additional development, customization, or configuration is required to continue using HELP Alerts under a new contract.

2.2 Technical Support & Maintenance

ILOG has assigned a dedicated Project Manager to serve as the single point of contact for ODOT. All authorized users of the ODOT system will have access to ILOG’s technical support via email to a special address (for non-critical questions) and via phone call to the 24x7 support hotline (for critical issues). The support hotline is answered by ILOGs own staff of systems professionals who either can resolve the issue, or who can rapidly escalate the issue to the proper ILOG staff. If ODOT requests a change to ILOG’s appointed project manager, a replacement will be assigned.

Your Project Manager along with ILOG’s technical support team, is committed to maintaining the Support Response Times for the “High Requirements” level as outlined in ODOT’s standard terms & conditions.

Routine maintenance is performed on a rolling basis, with no downtime or service interruptions due to the redundant architecture of the system. Maintenance activities are performed sequentially on individual machines by taking one machine out of service (while the redundant machines assume the full workload). The out-of-service machine has updates/patches applied and is then thoroughly tested by ILOG staff before it is put back into the mix of operational redundant machines. This is repeated with the next redundant machine until all are updated. The entire update process is performed first on ILOG’s development environment so that any problems with the routine maintenance will become evident before updates are applied to the training system or production systems. Then the process repeats by updating each individual machine in the redundant training systems.

Only after development and training systems have all been updated and thoroughly tested, does the process repeat for the production system.

The most important part is that all of this is done with no interruption in service to our users.

ILOG can share the rolling maintenance schedule with ODOT.

There may be a time when there is a significant change to the system that could potentially cause some system downtime. If such an interruption is possible, ILOG will schedule the maintenance with at least seven-days’ notice and can re-check with ODOT just before beginning the production maintenance so that we can be sure conditions on ODOT roadways are such that an emergency situation is not in progress or soon anticipated.

To further remediate the possibility of outages, ILOG hosts HELP Alert systems in multiple regions of AWS.

HELP Alerts is TxRAMP certified and with a fully redundant disaster recovery failover environment that has been tested as recently as October 2025.

2.3 Training

ILOG provides a variety of training offerings.

Synchronous hands-on training via live instructor either in person or via on-line meeting.

• Annual hands-on training sessions scheduled cooperatively with you and ILOG for your authorized users.

• Periodic training scheduled by ILOG multiple times per year, attended by any/all agency clients.

• Annual tailored training sessions upon request for different user roles (Admin vs.

IPAWS Admin vs. Drivewyze admin, etc.) for your agency or in cross agency sessions.

Asynchronous training via recorded training videos and written materials.

A library of training videos, one-page functional guides, and user manuals is always available in the HELP Alerts “Resources” section for quick onboarding of new users or overall refreshers. As new features are added to the system, ILOG updates the library of training materials. These videos and materials include overall system training as well as training for specific individual skills.

Training Videos include:

• IPAWS Admin (Full system)

• Logging into the HELP Alerts System

• Creating an Event Closure and the Approval Process

• Managing an Event and Communicating with Registered Participants

• Using the HELP Command Module

• Using the Resources Tab and Closing an Event

• Creating and Managing Drivewyze Emergency Alerts

Guides and Manuals include:

• User Guide (full system)

• Quick Reference Guide - New Event Entry

• IPAWS Admin User Guide

• Drivewyze Emergency Alerts Management User Guide

ILOG also coordinates an annual User Group meeting, where the community of users can share tips, discuss their own best practices, ask questions, request new general features, or attend mini training sessions.

Ad-hoc training sessions can also be arranged anytime.

3. Qualifications & Experience

3.1.1 FEMA’s AOSP List

Information Logistics’ HELP Alerts has been on FEMA’s “List of Alert Origination Software Providers (AOSP) with IPAWS” since 2021.

3.1.2 Deployment to similar size/scope agencies

Information Logistics, Inc. (ILOG) is a New Jersey-based, employee-owned small business specializing in internet technologies for the transportation and legal sectors. For over 25 years, ILOG has focused on communications for the transportation industry, with a mission to keep travelers informed and safe through high-quality services and responsive support.

In 2018, ILOG launched HELP Alerts, a traveler communication system designed for emergencies. The platform, built for reliability and uptime, integrates FEMA’s WEA system along with web, voice, SMS text, and IVR technologies. The objective behind creating the HELP system was to enhance public access to information and guidance from an official agency source, and to assist with providing additional intelligence to help with the agency’s response throughout critical situations. We hoped our technology would help reduce fatalities, alleviate secondary situations, reduce unneeded strain on response resources and provide comfort to travelers who would understand that the DOT knows they are out there. While it is difficult to quantify secondary crashes that didn’t happen, or travelers who did not call 911 looking for how long a backlog would continue, or lives that could have been lost if they had not been guided away from a flooded area, anecdotally we are told by our clients that the HELP system is working well.

ILOG follows strict QA/QC procedures. Each system is monitored with external automated monitoring tools that notify ILOG staff 24x7, should any performance threshold be reached.

Additionally, every client’s system is manually tested for access every weekday. At least once a month, each system is tested end to end by ILOG staff as part of the regular maintenance procedures. In addition to the redundancy described, to remediate the possibility of outages, ILOG hosts HELP Alert systems in multiple regions of AWS. with a fully redundant disaster recovery failover environment that has been tested as recently as October 2025. The system security procedures are robust and have recently passed the requirements for TxRamp certification.

ILOG regularly reaches out to FEMA, to industry partners and to transportation agency professionals to make the HELP system evolve into a more useful tool improving safety.

From the design of the user interfaces to data integrations to partner integrations, ILOG aimed to make the system reach as many people as possible, requiring the least bandwidth possible, available on the greatest number of devices possible, and with the largest 3rd party distribution possible to assist with preventing, managing, and resolving critical roadway situations. ILOG will continue to evolve this system with new features and intuitive, low bandwidth user experience.

ILOG has long-standing relationships with major transportation agencies and currently the HELP system is successfully deployed in state Departments of Transportation in NJ, AL, NC, TX, GA, VA, and OH. It is currently being set up in other locations, including regional transportation agencies. We will gladly share references upon request.

4. Contract Information

4.1 Duration

HELP Alerts is currently available and already deployed for Ohio DOT, as OHGO Connect. If awarded, the system will be maintained through the contract term ending June 30, 2027, with optional extensions as requested by ODOT.

4.2 Pricing

HELP Alerts is offered as Software as a Service (SaaS). The pricing provided in the Price Proposal includes all overhead, labor, equipment, materials and incidentals to achieve the requirements of the RFP, including system maintenance and ongoing upgrades, as well as technical support and training. Updates to the platform are included in the yearly service price.

4.3 Deductions

ILOG understands the ODOT will impose a deduction of the monthly service fee for any unscheduled outages that are no fault of the state.

5. Proposal Submission Requirements Information Logistics, Inc. (ILOG) acknowledges and fully understands the requirements outlined in Sections 5.1 through 5.3 of the RFP. ILOG will submit the proposal and pricing information through Ohio Buys, before 1PM (Eastern) on Tuesday October 21, 2025.

ILOG is committed to delivering a comprehensive and responsive proposal that clearly outlines our approach to providing the requested services. We fully acknowledge and accept the scope, terms, and requirements detailed in the RFP. The proposed system is copyrighted, so we would request that any images from the system or description of workflow, along with pricing, be considered as proprietary information.

6. Demonstration Period We welcome the opportunity to participate in a Demonstration Period to further explain or validate technical capabilities and ensure alignment with ODOT’s business needs.