OrderRun can send the units it releases to KitProof, so each unit becomes a job with one kit to check, without a CSV import. Nothing arrives until the Owner connects the site, and nothing becomes work until a Supervisor accepts a delivery. When OrderRun released a unit on a FactorySpec result, which can happen only once FactorySpec has qualified the unit's product family, KitProof keeps that result's reference and shows it. It never uses it to decide what goes in the kit.
Connect the site
The Owner does this, on Team & stations. The OrderRun section appears there only for the Owner, and only while SmartFACT Accounts lists both KitProof and OrderRun for your organisation.
Choose Connect to OrderRun. Accounts asks for your authenticator code if you have not given it in the last five minutes. Connecting is also your permission, for each accepted delivery, to let OrderRun read whether that delivery's kits are verified, one exact kit at a time. The section then shows how many deliveries are waiting, how many could not be fetched and how many were accepted, and whether a field map is approved.
If the section says this KitProof service does not hold OrderRun's registration yet, there is nothing to connect: ask whoever runs your SmartFACT service. If it says Accounts cannot be checked just now, try again later. Records already made stay readable either way.
Disconnect from OrderRun stops new deliveries and messages. Deliveries, jobs and the evidence permissions already given stay. Withdraw a permission on evidence read permissions if you need to.
Prepare and approve the field map
Under Configuration, open OrderRun field map. It says how each column of your published source map is filled for an OrderRun unit: from an OrderRun field, by its exact name, or with a fixed value. KitProof fills the job, source revision, line and units columns itself, so each unit becomes its own job with one line and one kit.
Once the site is connected, an Author chooses the source map, fills each column and chooses Save for review. A Reviewer then checks the draft shown and chooses Approve this field map, with an authenticator code from the last five minutes. Only the approved map is used.
A changed map applies to deliveries prepared after the change. Units already accepted are not imported again, so a correction reaches new units only. A preview prepared under the earlier map cannot be accepted until a Supervisor prepares it again.
Decide a delivery
A Supervisor does this. Under Jobs, Units from OrderRun lists each delivery with its state. Open one. KitProof has already fetched it, checked that it is exactly what OrderRun announced and previewed its units as an ordinary import, one job per unit. Read the preview as you would a CSV file (import jobs).
- Accept the whole delivery makes every unit a job in one step and tells OrderRun. Each kit's expected contents come from the site's active release, as for any job.
- Refuse the delivery needs a reason, which OrderRun sees. Leave out names and other personal details. Nothing is imported, and OrderRun is told whether the units could not be mapped, failed KitProof's checks or were refused by you.
- Prepare the preview again after the field map or the active release changed.
- Fetch again when the delivery could not be fetched, or refuse it.
A unit already here, sent again unchanged, shows as "Already here: stays as it is". Its job, its kit and any kit check already made stay exactly as they are. When OrderRun has replaced a unit already here, the page says so: accepting holds the old unit's job, so its kit is no longer checked, and the unit that replaced it is its own job. Recorded results stay as they were.
A later delivery from OrderRun can replace one still waiting. The earlier one then shows as replaced by a later delivery, and OrderRun is told.
FactorySpec results on a unit
FactorySpec's results are for evaluation only today, and OrderRun releases no unit on one. A result appears here only once FactorySpec has qualified a product family for production. Until then no delivery has a FactorySpec result column and no job names one.
Once a family is qualified, OrderRun may release a unit of that family on a FactorySpec result: FactorySpec's worked-out components, cut sizes and values for that configured unit. When it does, the delivery's Units table has a FactorySpec result column, with each unit's reference (FS followed by the result's identifier) or None. After you accept, the job made from that unit says which FactorySpec result and release OrderRun released it on.
KitProof keeps the reference, the result's and the release's identifiers and two fingerprints of the result exactly as OrderRun sent them, and includes them in the site's complete export. It does not recalculate anything from them, does not read FactorySpec, and sends nothing of them back. The kit's expected contents still come from your active release. If they disagree with what FactorySpec worked out, take it to your Author and the person who owns the product's definition. Do not change the kit at the station.
A delivery can stop at the fetch because what OrderRun sent is outside the agreed format, or carries a FactorySpec result that does not match its own fingerprint. Fetching again gets the same delivery. Refuse it with a short reason: OrderRun records it as a failed check against those units, and nothing is imported.
What OrderRun is told
OrderRun is told when a delivery is accepted or refused, and when a kit made from one of its units is started, verified, or raised as an exception at a station. Each message names the unit, its job and the station only: no readings, results or people. Kit stations find the job from OrderRun's own unit label as well as KitProof's kit references.
If OrderRun does not take a message, the Owner sees it on Team & stations under Messages OrderRun did not take, with the problem. Once the problem is resolved, choose Send again: the same message is sent again unchanged.