Skip to main content

Planning behavior

The public contract exposes operating facts and business choices. Provider credentials and optimizer implementation details remain service configuration.

Request controls​

  • Planning dates and customer windows.
  • Warehouses, customer properties, handover points, and current Nugget state.
  • Accepted movement legs and the proposed movement legs for a booking check.
  • Driver and lorry availability.
  • Driver qualifications, lorry equipment, and Nugget capacity.
  • Whether an empty Nugget must come from a warehouse and whether multi-Nugget work may split across lorries.
  • Current Fleet Check allowances when available.

Service defaults​

  • PTV credentials, HGV matrix generation, and matrix caching.
  • The deployed HGV vehicle profile and traffic model.
  • Solve-time limits, optimizer weights, and fallback policy.
  • Hexaly licence concurrency and request admission.
  • Independent result validation and technical evidence.

Adding a business control​

If a recurring operational choice needs to vary per booking or manifest request, it should become a named business field in this contract. Examples include a required arrival date, a fixed driver assignment, or a customer-approved alternative window.

Raw optimizer weights, solver switches, PTV credentials, and licence settings are not request fields because they are implementation and service-safety controls. The response identifies the policy, road profile, traffic model, planner backend, and validation result that were actually used.