Importing establishes source units; issuance freezes the instructions each unit will use. Neither action records physical execution. You need Supervisor authority and assigned normal releases for the families in the file.
Validate the source file
Prepare one row per identified unit in the supported UTF-8 CSV. Keep the exact required headers: job_id, unit_id, source_revision, family_id and drawing_revision. Use customer_code and option.<name> only as the mapping permits. Source revisions are positive whole numbers without leading zeros; identifiers retain their case, spaces and leading zeros.
On Work, choose the source namespace and file, then inspect the import preview. Check every row's identity, revision, family and decision. A malformed file, unknown field, invalid option, stale revision or conflict prevents acceptance of the whole file. Correct the approved source rather than manually disguising a bad cell.
Accept only the reviewed preview. If it is stale, prepare and review again. An identical revision and payload is unchanged; different content under the same revision is a conflict. A higher revision creates retained source history. A job or unit omitted from a file is not a cancellation instruction.
Review and issue
Select up to 100 units with no current work. Open the issue preview and check each unit's ready, blocked or already-issued result, release and source revision. Investigate blocked units before expecting them to be included.
Submit the ready batch shown by the preview. WorkSteps rechecks it and issues the whole submitted batch or none. It does not silently substitute a newer source or release. A stale preview or another person's issuance requires a fresh view.
Open each relevant traveller and confirm its identity, release, source revision and lookup reference. Hand that reference to the station with the physical unit. The operator still has to claim the attempt.
Protect work when source data changes
A higher source revision arriving while work is open creates a hold; the old traveller stays frozen. Ask the source owner what changed and follow holds and handovers. Do not reissue under a different identity to avoid that review.
If the issue response is lost, reconcile or inspect the original result before submitting another operation. Keep connection guidance available to the shift.
Read why a preview stopped
The unit CSV is bounded to 5 MiB and 5,000 data rows. Split a larger authorised export deliberately without changing its identities or revisions; a truncated file is not an acceptable substitute.
For a selected issuance row, use Explain this preview. Check the saved source revision, release and original resolution, including selected or omitted slots and blocking reasons. The explanation preserves that preview's decision; it does not issue the unit or make missing engineering input valid. If current source or release state differs, return to a fresh preview before issuing.