Small wind / Buyer questions
Procurement and engineering handover
Does an online match prove that every file in a PLC handover is current?
The short answer
An online and offline comparison checks the objects and attributes supported by the engineering tool. Siemens documents this type of comparison in TIA Portal. A match can support identification of a particular controller project state, while other files, devices or runtime values can lie outside the compared scope. A handover should record which controller and project were compared and how the other required items were verified.
Identify the comparison scope
Record the engineering tool version, project and device identity, connection target and the selected comparison mode. Ask which types of objects the displayed result includes. In a hypothetical project the controller objects compare as expected while a separate operator panel or an external parameter file is outside that comparison. A green indicator can be accurate within its own boundary and still leave another deliverable unverified.
Read the differences as evidence
Preserve the results for the relevant objects, including any items skipped, unsupported or intentionally changed. Ask the integrator to identify the approved treatment of differences. A comparison of program objects and a comparison of live operating values are different observations. Keep the project that was compared and any relevant separate records with their own timestamps and versions.
Close the handover by component
Have the responsible controls reviewer record which components are supported by the comparison and which require a separate check. The record should include the approved source project and the actual site target without placing credentials in a general handover. A later technician can then reproduce the comparison and see exactly what a match meant at the time it was recorded.
Sources
Examples are illustrative. Confirm product-specific performance, compatibility and supply scope in the applicable documents.