# Material Transport Scheduler

> Schedule shared vehicles and inspect travel and waiting times. Plan material moves on a shared fleet using fixed travel times or a network of shared route segments.

Part of usefulweb.app (https://usefulweb.app/). Results are deterministic calculations from the inputs and the listed assumptions; the API returns exactly what the web page shows.

## Use it
- Human interface: https://twinworkstransportscheduler.usefulweb.app/ (interactive tool at https://twinworkstransportscheduler.usefulweb.app/tool)
- JSON API: POST https://twinworkstransportscheduler.usefulweb.app/api/v1/calculate with a JSON object of inputs (schema: https://twinworkstransportscheduler.usefulweb.app/api/v1/tool)
- OpenAPI: https://twinworkstransportscheduler.usefulweb.app/openapi.json
- MCP (Streamable HTTP): https://twinworkstransportscheduler.usefulweb.app/mcp - tool `twinworks_transport_scheduler`

## Inputs
- trips (textarea): Trips: name, request time, loaded travel, empty return (seconds) - Without a network, use name, request, loaded time, empty return. With a network, use name, request, pickup location, destination. Times are seconds.
- network (textarea): Optional route network: location A, location B, travel seconds, capacity - One two-way shared segment per row. When supplied, requests use pickup and destination names and vehicles start at the depot.
- depot (text): Initial depot location for network mode - All vehicles start here; after a delivery each stays at its destination.
- vehicles (number): Number of identical vehicles

## Method
- Sort requests by time and use listed order for ties.
- Fixed-time mode assigns each request to the vehicle available earliest and includes empty return.
- Network mode assigns the first idle vehicle, computes shortest travel-time paths to pickup and destination, and queues vehicles FIFO at capacity-limited two-way segments. Vehicles stay at their last delivery location.

## Limits
- Standalone fleet estimate, separate from the Twinworks production model. Network paths minimize uncongested travel time and do not reroute dynamically; intersections, loading, charging and breakdowns are not modeled.