At a glance
Use the current delivered outputs for the identified part and agreed setup. Availability, revision identity and manufacturing validation are different things.
01
Start with the part and revision
The client Portal brings order information and production outputs into the same workflow. Before retrieving files, check the part reference and current revision context rather than relying only on a filename saved on a local computer.
The website’s Part Workspace example shows revision context and the actual output list. It is example data from the Portal, not a customer case study or a promise that every output type is included.
02
Read availability for each output
The supported output types in the workflow include NC code, setup-sheet PDF and DXF unfold. The deliverables for a particular part depend on the agreed scope and machine/postprocessor setup.
- Available: the Portal shows an output that can be retrieved through the applicable download action.
- Not produced for this part: that output has not been provided for the shown part; it is not a hidden download.
- Expected but absent: clarify the agreed scope and output status before relying on the package.
03
Download the order’s outputs together
The delivered order workspace provides a Download Package (ZIP) action. It retrieves the available production outputs for the order together, so you do not have to download each file separately.
Complete the acknowledgement shown by the Portal before using the download action. The package contents depend on the outputs actually delivered for the order; it does not create missing setup sheets or DXF files.
Working with multiple input files and receiving a ZIP package are separate capabilities. ZIP is not accepted by the current source-upload controls. Use STEP/STP or IGES/IGS geometry and PDF references there; discuss DXF or drawing-only work before submission.
04
Make changes explicit
A geometry change, revised drawing or different intended setup needs to be connected to the affected order and part. Use the Portal’s revision workflow where available, and clarify the change and intended source revision.
A newer local file or an edited filename does not itself make an output current. Follow the current and superseded indications in the Portal and resolve any mismatch before using the files. If a revision action is unavailable, contact us to discuss the next step.
05
Keep delivery and production validation distinct
Delivery means the agreed programming outputs have been made available through the service workflow. It does not replace the customer’s machine setup, first-piece checks or shop-floor validation.
Before handing the files to production, make the intended machine, part reference, revision and agreed outputs clear to the people using them. Raise missing or conflicting information rather than filling gaps by assumption.
This guide explains the collaboration workflow. Agreed scope and setup-specific technical review determine the work for each client.