<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Transport Tech</title><link>https://transporttech.net/</link><description>System maps for fleet, logistics, transit, vehicle data, and the decisions built on them.</description><item><title>Trace fleet data from vehicle to operator</title><link>https://transporttech.net/systems/fleet-telematics-data-path/</link><guid>https://transporttech.net/systems/fleet-telematics-data-path/</guid><description>Map collection, buffering, transport, normalization, storage, alerts, and operator action as separate reliability boundaries.</description></item><item><title>Route optimization begins with constraint quality</title><link>https://transporttech.net/systems/route-optimization-inputs/</link><guid>https://transporttech.net/systems/route-optimization-inputs/</guid><description>Represent time windows, capacity, service time, road limits, and business priorities before evaluating a solver.</description></item><item><title>A practical map of public-transit data interfaces</title><link>https://transporttech.net/standards/transit-data-primer/</link><guid>https://transporttech.net/standards/transit-data-primer/</guid><description>Separate scheduled service, live vehicle updates, alerts, fares, and rider-facing interpretation.</description></item><item><title>Map failures between a vehicle and a transport platform</title><link>https://transporttech.net/systems/vehicle-platform-failures/</link><guid>https://transporttech.net/systems/vehicle-platform-failures/</guid><description>Use explicit states for device, network, ingestion, processing, and operator-interface failures.</description></item></channel></rss>
