Use this when your organisation traces lots and serials in LotTrail and wants CheckStation's records there: which units were made for which job, which lot the source named for each unit, and which inspections were completed with which outcome. CheckStation 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 a second factor verified in the last five minutes. The export works whatever your plan, including after it has ended.
Register this site in LotTrail once
Open Site operations and find Evidence for LotTrail, below Site admission. A supervisor's Site operations is this panel alone. 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
checkstation:01JC3Z5K8Q4N7R2T6V9X0B1D3F. It is this site's, and it never changes. - Source generation, which is the history: 1 to begin with.
- Declared scope code:
checkstation.lottrail-evidence/v1. - Relationships this source can record. Tick exactly inspection 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. CheckStation prepares the export within about a minute; select Check again to see it. The first export holds every unit, job, lot and completed inspection of this site; each later export holds what is new since the one before, and corrections for anything that changed. Records are numbered from 1, with no gaps, and every file says which numbers it holds.
Before the export is written, CheckStation checks with SmartFACT Accounts that you still hold the Owner or Supervisor role here and that your second factor is less than five minutes old. 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. Select Download on each part. Each file's name starts checkstation-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 CheckStation part: admit the earlier part first.
A part marked Corrections withdraws or replaces records already exported. Admit it in its place in the order, like any other part.
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 CheckStation's 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
Each unit is stated once, under its source namespace and unit code. A job is the order code the unit's source named, and a lot is the lot code the source named, under the item code. An inspection is stated with the outcome its newest result records: conforming or nonconforming. When a later source revision names another job or lot for a unit, or an approved correction changes an inspection's outcome, the next export corrects it.
The export never says that a unit was released, held, rejected or had its release revoked: read those decisions in CheckStation. It records no measurements, photographs or people, and it never says that a lot went into a unit. In LotTrail, start from a job to see its units and their inspections, from a lot to see the units the source named it for, or from an inspection to see its unit, the unit's lot and its job. LotTrail's view of physical inputs and outputs has no answer from CheckStation, because CheckStation does not record them.
A record whose values a LotTrail file cannot hold, such as a code or name longer than 120 characters, is left out and listed on the panel with the reason. 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 CheckStation unit with a job, a lot and one inspection is about five events, so that is about 10,000 CheckStation units, and fewer when CheckStation's dataset is investigated together with another. The panel shows how many events this history has exported, so you can compare.