Source: https://www.quantumsteeldesign.com/material-traceability/ Your browser. Your workspace. # Material Traceability Register Connect steel piece marks to heat numbers, suppliers and locally fingerprinted mill-certificate references. Find incomplete material references and print a trace record. Local browser tool. No accounts, uploads or background synchronization. Export backups for records you need to retain. ## How this register works Keep the relationship between a physical material lot and the references used to identify it. Split a mark into separate records when its pieces come from different heats or suppliers. This register records your references; it does not authenticate a certificate or confirm grade, origin, test results, or acceptance. Linked project workspaceChoose an existing [project workspace](https://www.quantumsteeldesign.com/project-workspaces/) or use an unassigned local project. Keep different physical lots on distinct records. Up to 500 records per register and 2 MB for the combined operations backup. Loading local records... ## Reuse an existing reference Read existing local source records, select one row and copy it into the unsaved form. Review the copy before saving. No source record is changed. Available source snapshotRefresh to list sourcesReceipt sources include all typed purchasing project references. Assembly BOM sources are the saved global plan. Workspace takeoffs and drawing registers are limited to the selected project. Repeated copying can create duplicates; reconcile the source and existing ledger first. ## Add or review a record ## Recorded work Filter these project records ## Examples, backups and recovery All four operations tools share one backup. A JSON file includes traceability, fabrication, shipments and transmittals with their linked identifiers. Loading a sample or backup replaces only this open view. An explicit record save or Save loaded view writes the entire current operations view to this browser. Export the existing saved records first before replacing them. [Download fictional sample JSON](https://www.quantumsteeldesign.com/samples/operations-example.json) Load complete operations JSON for reviewIf another tab changes operations, saving stops instead of overwriting its newer records. Export your current view, reload saved data, and reapply the intended change. If browser storage is full or disabled, preserve the form and export the open records before closing. These are independent local copies, not a multi-user audit system. ## Worked example Six B101 beams arrive from one heat. Enter one lot of six with the heat and supplier shown on the checked receiving documentation. If two beams are from another heat, use lots of four and two instead. Select the relevant mill-certificate file to retain its name, byte size and SHA-256 fingerprint. The certificate bytes never enter browser storage. A missing certificate warning remains until a file reference is selected. Use the clearly labeled fictional sample to inspect the relationships between a six-piece material lot, its production stages, a two-piece bundle, and a one-drawing issue. None of these records describes a real customer or project. ### Troubleshooting before the next handoff - Confirm the workspace and mark before copying a source row. A copied snapshot will not update automatically. - Resolve missing or conflicting references through the responsible project team. The tools do not invent approvals. - Print or export the relevant record, check its quantity and revision, and retain an operations JSON backup alongside the controlled project files. ## Questions about material traceability register Does a complete reference establish material compliance? No. Complete means the heat, supplier and file-reference fields are present. Independently check the physical marking, purchase requirements, test information, chain of custody and project acceptance process. Can I open the certificate from this record later? No. The register retains its filename, size and fingerprint, not the file or a durable filesystem permission. Keep the original certificate in your controlled project files and reselect it when comparing fingerprints. Why are receiving records listed from different projects? The purchasing tool uses a typed project reference rather than the workspace identifier. Source choices show that reference. Confirm the intended workspace and piece mark before saving the copied receiving snapshot.