At rideOS, we’re always looking for new ways to help our customers be successful, which means solving the truly complicated issues around routing and optimizing their vehicle fleets. Routing is a problem that is complicated to manage and expensive to build, and existing solutions are often inaccurate or don’t allow for customization. We’re excited today to launch our standalone Routing APIs, which will address these concerns head on. For the first time, customers can now integrate with our Routing APIs without also using our optimization and dispatch products. We’re focusing on providing the most accurate ETAs and customizable routes for our customers, without compromising performance or scalability.
Accurate ETAs are one of the most important parts of running a delivery or ridehail service. Our API tailors paths and ETAs to the specific data and driving expectations of our customers. We build personalized models that dynamically tune to predict the actual path that will be taken by our customer vehicles, and we are able to adjust those models to account for customer-specific delays. We also provide a number of tunable knobs for our ETAs that allow for further customization. These include statistical correction factors based on ATA data or the option to use different models to estimate ETAs (e.g. predictive, real time, or worst-case).
The rideOS Routing API allows for vehicles to avoid certain streets or maneuvers, as well as other custom features.
Customized routing functionality is also something that our new Routing APIs provide. Our constraints functionality provides customers the ability to allow or exclude certain streets and areas, as well as avoid specific maneuvers, based on the needs or limitations of their vehicles. All of our customizations are configurable via routing profiles that can be assigned on a vehicle-by-vehicle basis or created for the whole fleet. Some of these customizations can now easily be changed by the customer via the Routing Profile API. Using routing profiles you are now able to configure the routing behavior once and use it consistently through all of our products. Our routing is basemap-agnostic; we use generic geometry-based input for constraints and can ingest customer-specific basemaps.
Along with these new features, we’re ensuring that performance and scalability stay top of mind. Our solution allows customers to scale their operations with low latency. We have a scalable data ingestion pipeline, where global real-time traffic is updated every 5 mins, global map updates happen every day, and constraint data updates happen in less than a minute.