← Resource centre
Technical evidence guide
Check that every document belongs to the system and decision in front of you
A credible technical package connects the exact model and options to the installation, software, reference method and acceptance record. Use the checks below during supplier review, detailed engineering, commissioning or a later audit.
Technical evidence guide
Six document groups connect the ordered system to the accepted result
The document is useful when another engineer can connect it to the installed equipment and reproduce the decision it supports.
| Evidence group | What it should identify | Why it matters | What to request |
|---|---|---|---|
| Product identity | Model, sensor or transmitter option, controller, accessories, serial number and software version. | Similar model names can use different interfaces, enclosures or measurement arrangements. | Order configuration, nameplate record, data sheet revision and supplied option list. |
| Performance statement | Material, moisture range, measurement geometry, reference method, dataset and operating conditions behind the figure. | An accuracy value without its tested range and conditions cannot be transferred to another line. | Test or validation report showing sample count, range, residuals, exclusions and applicable limits. |
| Compliance and safety | Exact equipment covered, issuing body, document number, edition, country and installation restrictions. | A component certificate or related-model declaration may not cover the installed system. | Applicable declaration, certificate, manual sections, risk controls and model-to-document match. |
| Mechanical and electrical design | Final dimensions, mounting geometry, product-contact boundary, power, grounding, cables, I/O and guarding. | Commissioning and maintenance depend on the as-built arrangement, not a generic brochure image. | Approved drawings, wiring schedule, photographs, deviations and maintenance-access record. |
| Data and software | Units, scaling, registers, validity states, timestamps, filtering, alarms, user access and configuration version. | A live value loses meaning when the PLC cannot distinguish product, fault, delay or calibration version. | Signal dictionary, register map, backup file, I/O test and change history. |
| Calibration and acceptance | Reference method, sampling plan, calibration range, independent validation, acceptance rule and review triggers. | This record shows where the result is proven and when the relationship needs to be checked again. | Paired dataset, fixed calibration version, acceptance report, responsibilities and routine verification plan. |
Technical evidence guide
Five questions to ask before relying on a file
The document is useful when another engineer can connect it to the installed equipment and reproduce the decision it supports.