Runs

A run is a piece of work on material: batches go in, outputs come out, and the two have to add up, including what was lost. Every output becomes a new batch in your own yard, ready for the next run or a consignment.

The Runs list

Open Runs in the menu. Each run shows its State, Outputs and when it was Started, grouped into lanes:

Lane	What it means
Draft	Written down, holds no material
Running	Material committed, outputs still short
Sealed	Somebody stood behind it
Abandoned	Given up, material returned, reason on the record

Above the list, RezetHub counts how many running runs are Ready to seal: their outputs account for everything that went in. The count covers every run you hold, not just the ones on the page. Search the runs finds a run by code or kind of work.

Start a run

Select Start a run on the Runs page, or Commit into a run / Start a run with it from a batch. Starting from a batch wires that batch in for you.
Give the run a Label (the run’s code is generated for you) and, if you like, a Description · optional.
Under Kinds of work, tick everything this run does, in the order it does it. Kinds marked System ship with RezetHub; the rest are your organisation’s own. Select + Add a type for your organisation to add one.
Choose the Site the work is done at, the Role, and Who is doing it. The site cannot be changed afterwards. If your organisation has no sites, register one under Facilities first.
Under Connect what goes in, click each batch to wire it in. Only batches with kilograms left are shown; use Search what goes in to find one by code, material, source or region.
Under Attribution, set the Kilograms committed from each batch. You commit kilograms; the percentage is worked out for you. Neither goes above what is left on the batch.
Select Start with (the button shows the total kilograms), or Save draft to keep it for later.

A draft holds no kilograms, so nothing can be committed to it until it is started. To start a saved draft, open it and select Start the run; what it was drafted as stays fixed, and you wire in its sources then.

Rules that apply:

The mass balance is the only thing that can refuse you here. RezetHub checks each batch at the moment you commit from it. If you commit more than is left, the run is refused; take a source off or lower a figure.
A batch nobody has weighed can only go into a run that both sorts and measures it. Tick both Sort and Measure under Kinds of work for that run.
If some commitments are refused after the run opens, the run still exists with what did commit. Select Open the run and commit the rest there.

During a run

The run page shows What went in on the left and What came out on the right, with the balance between them and a drawing of the chain. A commitment cannot be edited; a correction is a new entry.

To commit more material into a running run, use Wire a lot in: choose the batch, enter the Kilograms and select Wire it in.

Record an output

Record each thing that came out, one at a time. Material you do not want is still material: record it, photograph it and weigh it, and it becomes a batch like any other.

Under Record an output, choose What came out. One list holds both materials you grade and products you make; type to search, or select Show the whole catalogue.
Choose the Sourcing (Virgin, Recovered and recycled or Mixed feedstock).
Enter the Kilograms you expect to weigh, and the Actor. The screen tells you how much more this run can take.
If you picked a product spec with variants, choose Which one and enter the Units that came out. The per-unit weight and area come from the spec.
Select Record it.

The output opens as a new batch at the run’s site.

Prove each output

Every output must be photographed before its weight goes on the record.

On the output, select Show the code and scan it with any phone. Photograph the scale first, then the material. See Capture and photo proof.
The photos appear on the output as they arrive.
Enter the Weight the instrument showed and select Record the weight. You type the figure; RezetHub does not read it off the photo for you, but the photos are cited beside it on the record.

To add more photos later, select Show the code · add photos. Nothing already sent is replaced.

To remove a photo, select Remove this photograph on it, choose why it is being removed (for example The frame is too blurred, dark or obscured to read or The frame shows a person or their details) and select Remove it. The removal goes on the record and cannot be undone from the screen. The only photo on an output cannot be removed.

Account for the rest: calculated process loss

When outputs do not yet add up to what went in, the run shows how many kilograms are not accounted for yet. Either:

select Record it as an output, if the difference is material; or
select Calculated process loss, if it stopped being material and there is nothing left to photograph. The kilograms are prefilled from what is unaccounted for; change them if not all of it is loss. Confirm with Declare — … as calculated process loss (the button shows the kilograms), or Not yet to back out.

Declaring loss again replaces the figure, and both declarations stay on the record. RezetHub calls this calculated process loss because it is worked out from the balance, not measured.

Pause and resume

Select Pause, choose why work stopped (for example The line or a machine has stopped or Nobody is on the floor to work the run), and confirm with Pause — the material stays committed.

A paused run keeps its material committed, so nothing else can use it, and it still takes outputs and photos. Select Resume to carry on. Both the stop and the restart stay on the record.

Abandon a run

Select Abandon, choose why the run was given up (for example The equipment could not be brought back into service or The run should never have been opened), and confirm with Abandon — … goes back (the button shows the kilograms), or Keep the run to back out.

The committed kilograms go back to the batches they came from, and the outputs recorded so far go with the run. Nothing is deleted: the run stays on the record as Abandoned, with your reason. Abandoning a draft just moves it to the archive.

If you only need to stop for a while, the dialog offers Pause the run instead.

Seal a run

Sealing says the run’s record is true. It is an operations supervisor’s act.

The panel What has to be true before it will seal lists the conditions:

something went in and something came out (an empty run cannot be sealed);
the balance is closed: in equals out, counting calculated process loss;
every output is finished, weighed and named.

If a seal is refused, the reason shows on the page, for example:

an output has no recorded weight;
an output names a product spec with several variants but no count per variant;
your stream profile requires a field that an output has not answered (the page links the batch that owes it);
kilograms are still unaccounted for.

When the run is ready, select Seal and confirm with Seal — no more changes. Every output is sealed with it, and each becomes a batch that seals and recalls on its own.

Work done somewhere else

When part of the work is done by an outside performer, the run page shows it under Sub-runs · work done somewhere else: the consignment out, the work, and the consignment back in. You weigh what comes back on your own scale and record it on the run. If less comes back than went out, the shortfall is yours to account for before the run seals.