Reusable Container Wash Batch Plan Plan wash batches for reusable containers on one washer using one caller-supplied program.
Plan wash batches for reusable containers on one washer using one caller-supplied program. Supply sourceRevision, washProgram, washerStartMinute, cycleMinutes, capacity and up to 128 containers with unique id, releaseMinute and dueMinute. The revision, program and container identities are opaque, case-sensitive ASCII labels of 1 to 48 letters, digits, underscores, periods, colons, pipes or hyphens. All times are safe whole integers in one common minute timeline; starts, releases and deadlines are nonnegative, cycleMinutes is positive and capacity is 1 to 128. The deterministic policy starts at washerStartMinute. At each free-washer boundary it selects every available container with releaseMinute at or before that boundary, ordered by earliest dueMinute then original container order, and fills up to capacity. It starts immediately when any container is available, even if a fuller batch could be formed by waiting. If none is available it advances to the earliest remaining release. There is no lookahead or global scheduling optimum. Each batch occupies the half-open interval from startMinute to endMinute and every member becomes clean-ready exactly at endMinute. The next batch may start at that boundary. A container released exactly at a boundary is available then; finishing exactly at its deadline is on time. A deadline before release is valid and any resulting lateness is reported. Cycles retain policy membership order, containerPlans retains original input order and cycleIndex is zero based. Unused capacity is reported per cycle and in total. totalLateMinutes is an exact decimal-string sum; individual times and lateness remain safe integers. Empty containers returns zero cycles and washerStartMinute as finishMinute. Any cycle end beyond the safe-integer range rejects the entire request during preflight before quoting. The shared 36,000-byte, 6,000-node, depth-24 input profile and 500,000-byte output guard apply. These are technical workload bounds. This supplied-record plan does not operate equipment, reserve containers, validate a wash program, establish sanitation or clean status, authorize handling, or model other operational constraints. 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.