Use this when your organisation traces lots and serials in LotTrail and wants WorkSteps' records there: which units your sources named for which job, and which procedures were completed for each unit, as normal work or as rework. WorkSteps writes them as files LotTrail admits as they stand. It sends nothing and connects to nothing: you download the files here and a LotTrail Supervisor admits them there, one at a time. You need the Owner or Supervisor role, at the real site, and recent Accounts authentication: every action asks for your authenticator if you have not used it in the last five minutes. The export works whatever your plan, including after it has ended, and after the site is closed until its read and export date.
Register this site in LotTrail once
Open Plan and usage and find Evidence for LotTrail. Under To register this source in LotTrail it shows four values, named as LotTrail's Create a declared dataset form names them:
- Source instance ID, such as
worksteps:01JC3Z5K8Q4N7R2T6V9X0B1D3F. It is this site's, and it never changes. - Source generation, which is the history: 1 to begin with.
- Declared scope code:
worksteps.lottrail-evidence/v1. - Relationships this source can record. Tick exactly procedure context and context reference, and nothing else.
Copy each value with its Copy button and give them to the person who creates the dataset in LotTrail, with the data owner and permitted readers your organisation chooses. A dataset in LotTrail keeps these values for good. LotTrail's own steps are in admit a SmartFACT product's export.
Export new records
Select Export new records. WorkSteps prepares the export within about a minute; select Check again to see it. The first export holds every job, unit and completed procedure of this site; each later export holds what is new since the one before. Records are numbered from 1, with no gaps, and every file says which numbers it holds.
Before the export is written, WorkSteps checks that the person who asked still holds the Owner or Supervisor role at this site. If the export did not finish, the panel says why. No record was given a number, so the next export starts where that one did.
A busy site's first export is several parts, each a file of up to about 580 units. Select Download on each part. Each file's name starts worksteps-lottrail-, sorts in the order the parts are admitted, and is kept here for a day. After that, Write again writes the same file, byte for byte, with the same checksum.
Admit the parts in order, one at a time
The panel lists the exports newest first, and each export's parts in order. Start with the oldest export and with part 1 of each. Every part says which part to admit before it. In LotTrail, stage one part, compare its File checksum with the Checksum the panel shows for that part, accept it, and only then stage the next.
LotTrail does not stop a part being admitted out of turn. If you stage a part that skips records, LotTrail warns that records are missing and asks for a second tick before it will accept the file. Do not tick it for a WorkSteps part: admit the earlier part first.
An export with nothing new is one file with no records. Admit it too: it moves the time LotTrail says its records reach.
When a part was skipped or lost
If a later part was accepted in LotTrail before an earlier one, LotTrail refuses the earlier part as it was written. Open If a part was skipped or lost, choose the skipped part and the latest part LotTrail has accepted, and select Write this part. The file holds exactly the skipped part's records, stated as the later part stated its coverage, so LotTrail accepts it and the gap closes. It is listed under the parts written that way.
If a part's file is no longer kept here, select Write again on that part.
When the history starts again
After this installation is restored from a backup, the record numbers given since that backup cannot be trusted, so the panel asks you to start the next history before anything more is exported. Select Start history 2 (or the next number). Everything is then exported again from record 1 under the new source generation, and LotTrail needs a new dataset with that generation: register it as before. The same happens if WorkSteps' mapping ever changes its scope code.
You can also start a new history yourself, with a reason, under Start a new history, for example when a dataset in LotTrail cannot be put right. Do this only when the LotTrail data owner has agreed, because it means a new dataset and admitting every part again.
What the export says, and what it does not
A job is stated under the source that named it, by its job ID. A unit is stated by its unit ID under its source and its job, because a unit ID means one thing only within its job: unit 00001 of two jobs is two units. A completed procedure is stated as a work record named by the attempt's lookup token, the WS- code on the unit's reference, with the status completed, or completed rework for rework. Each unit is linked from its job, and each work record from its unit. Nothing WorkSteps exports changes once written, so a WorkSteps export never holds corrections. A concern recorded later against a completion leaves its work record as it was; rework appears as a further work record for the same unit.
WorkSteps records no lot, component serial or quantity, so the export never says what went into a unit. It holds no step evidence, photograph, reading, person, hold, or work that was not completed. In LotTrail, start from a job to see its units and their completed procedures, or from a work record to see its unit and the unit's job. LotTrail's view of physical inputs and outputs has no answer from WorkSteps, because WorkSteps does not record them. To follow a job into another product's dataset, start a second search there from the same job ID. Where CheckStation holds the same unit under the same unit code, a LotTrail Supervisor can join the two with a reviewed identity link, one pair at a time.
A record whose values a LotTrail file cannot hold is left out and listed on the panel with the reason: a job ID longer than 120 characters, which WorkSteps accepts up to 128, or a source name and job ID that together pass 120 characters. A unit whose job is left out, and a completed procedure whose unit is, are left out with it. Every file from then on says the history is incomplete. Correct the record at its source if you can; it is tried again at every export.
How much LotTrail can investigate
LotTrail refuses an investigation over 50,000 events across the datasets chosen. A WorkSteps unit with one completed procedure is four events (the unit, its job link, the work record and its link), so that is about 12,500 WorkSteps units, and fewer when units are reworked or when WorkSteps' dataset is investigated together with another. The panel shows how many events this history has exported, so you can compare.