Lines are local
Production printers sit behind facility networks and are often attached to dedicated workstations.
Manufacturing
Print the traveler, label, or ticket when the work order changes.
RocketPrint does not replace the MES or ERP. It gives that system a consistent way to deliver physical output to the computer and queue already serving each work area.
Work-order event → station printer
Use job titles and source fields to keep the print record connected to the originating workflow.
The operational gap
The system of record and the production printer live in different worlds.
Work orders are coordinated centrally while labels, travelers, and tickets must appear beside a specific operation.
Formats vary
A product label may be ZPL while a traveler or inspection sheet is PDF.
Reprints need intent
A legitimate reprint and an accidental retry must not be treated as the same event.
The RocketPrint path
Make printing an explicit step in the work-order lifecycle.
The manufacturing system decides what changed and where the work is assigned; RocketPrint delivers the resulting artifact.
Choose the trigger
Release, line assignment, operation completion, or another state change creates the print intent.
Resolve the station
Map the assigned line or work center to the appropriate printer ID.
Name and send the job
Include the work-order reference and a key specific to that artifact and revision.
What changes
Physical output follows the production decision.
Line-specific routing
The assignment in the source system determines the printer.
Format flexibility
Raw label languages and PDF documents use one API surface.
Intentional reprints
A new revision or authorized reprint can use a new key; infrastructure retries reuse the original.
Job evidence
The source, title, timestamps, and failure reason create a support trail.
Start with one printer
Make the physical step part of the workflow.
Install RocketPrint Station beside a printer, send one request, and keep the job ID. That is the whole path.