Reusable Container Circulation Plan Plan reusable container assignments across dispatch, return and cleaning times.
Plan reusable container assignments across dispatch, return and cleaning times. Supply sourceRevision, declared types and locations, containers with exact typeId, locationId and readyMinute, and demands with exact dispatch and return locations, dispatchMinute, returnMinute, cleaningMinutes, quantity and priority. IDs are opaque, case-sensitive ASCII labels of 1 to 48 letters, digits, underscores, periods, colons, pipes or hyphens. All numeric fields are nonnegative safe whole integers in one common minute timeline; each return is strictly after dispatch and return plus cleaning must remain a safe integer. Demands run by earliest dispatchMinute, then lower numeric priority, then supplied demand order. Each demand uses only the exact type and dispatch location with readyMinute at or before dispatch; candidates are chosen by earliest readyMinute and then supplied container order. The entire requested quantity is allocated or the demand returns shortage with no reservations or state changes. A shortage leaves containers available to later demands, and zero quantity needs none. Assigned containers become available at the declared return location exactly at returnMinute plus cleaningMinutes. The report includes ordered demand plans, individual circulation assignments and final container availability in original container order. Total requested quantity counts every demand, allocatedQuantity counts assignments including repeated reuse, and unallocatedQuantity counts all units of shortage demands, not only their numeric shortage. The deterministic greedy ordering is disclosed and is not a global optimum or forecast of future demand. A final location is the location at final modeled availability, not an observed physical location at a common wall-clock time. Up to 128 types, locations, containers and demands and 512 total requested units are supported within the shared 36,000-byte, 6,000-node, depth-24 input profile and 500,000-byte output guard. These are input and result workload bounds. Duplicate IDs, unknown references, invalid timing and unsafe return-plus-cleaning reject the whole request during preflight, even for a demand that would have a shortage. This supplied-record plan does not dispatch or reserve containers, authorize work, infer transit between locations, prove cleaning or physical availability, or promise optimal allocation. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.
Agent API guide → · Website orders show the report on your private order page.
Your input · JSON Load a small example The complete checkout request must fit within 40,000 UTF-8 bytes. Your input is validated again before an order is created.