Use
When should Shop Doc be generated in the workflow?
After toolpath generation and before release to the machine, because the output depends on the final CAM state and should reflect the exact operations and tools in the programmed part.
What output formats are commonly supported?
Siemens NX Shop Doc commonly supports HTML, PDF, and Excel-based reporting, with PDF often used for shop-floor distribution.
Why is Shop Doc valuable in CNC machining?
CNC execution depends on exact setup data; even small mismatches in tool length, diameter, offsets, or operation order can produce scrap, collisions, or tolerance failure. Shop Doc externalizes that process data into a controlled document.
In a ShopDocs context, USE is not 'User-Defined Setup/Edit'; the documented Siemens NX meaning is Shop Documentation (Shop Doc), a CAM-generated manufacturing report that compiles process information from the NC program into Excel, HTML, or PDF and produces setup sheets, tool lists, operation lists, and cycle-time summaries for operators and production staff.
On the CNC shop floor, Shop Doc is usually printed or posted at the machine during setup to verify tool numbers, cutter geometry, offsets, spindle speed, feed rate, stock allowance, and estimated machining time before the first part is run. In Siemens NX, the programmer generates it after the toolpath is built from the Program or Operation Navigator and outputs PDF, Excel, or HTML based on the selected template. For a millwork or manufacturing assembly line, the same document acts as a controlled traveler showing operation sequence, critical dimensions, and assembly notes. The value becomes clear on multi-shift or recurring jobs because it preserves setup intent without relying on verbal handoff. Templates and configuration files let each shop tailor the report for operator use, management review, or traceability, keeping setup data consistent and auditable from CAM to machine.
Out-of-date tool data: Shop Doc shows a tool diameter or holder assumption that no longer matches the actual tool cart, causing wrong compensation or collision risk from stale documentation.
Incorrect cycle-time trust: The reported time is treated as production truth even though the toolpath changed after generation or simulation was not verified, causing missed delivery windows and overloaded schedules.
Template/configuration errors: A custom shop_doc template or dat file entry is misconfigured, so the report omits a critical note or prints the wrong operation list, leading to operator confusion and the wrong setup being run.