Before anyone confirms that a signal reads correctly on the operator screen, someone has to confirm that the wire carrying that signal is actually connected where the drawing says it should be. Point-to-point checkout is that unglamorous but essential job: methodically verifying that every field conductor lands on the correct terminal and I/O channel, matching the loop drawings, before loops are energized. This guide explains what point-to-point checkout is, how it is carried out, why it comes before loop checks, and how it catches the crossed wires and mislabeled tags that would otherwise surface as baffling faults later.
Point-to-Point Checkout in one line: A point-to-point checkout is the systematic verification that every field wire lands on the correct terminal and I/O channel, matching the loop drawings, before loops are energized. Technicians trace each conductor end to end - often by ringing out continuity - and confirm terminations through junction boxes and marshalling cabinets against the loop sheets, catching crossed wires, wrong terminals, and mislabeled tags at the cheapest possible point.
A field signal travels a long way from an instrument to the control system: out of the device, into a junction box, along a multicore cable, into a marshalling cabinet, across to the I/O card, and onto a specific channel. At every one of those transitions a conductor is terminated on a terminal, and every one of those terminations is an opportunity for a mistake - a wire on the terminal above or below the right one, two wires swapped, a spare pressed into service, a shield grounded in the wrong place. Point-to-point checkout exists to confirm that each of these terminations is correct, one point at a time, against the drawing that says where it should be.
The reference for the check is the loop drawing or loop sheet, which shows the complete wiring for a given loop from the field device through every intermediate termination to the I/O channel. The technician's job is to prove that the physical reality matches that drawing exactly: this conductor, from this device terminal, arrives on this marshalling terminal and this I/O channel, and it carries the tag the drawing assigns. The check is deliberately concerned only with the wiring itself - is it connected correctly and continuously - and not yet with whether the resulting signal reads correctly on a display, which is the loop check's job.
The outcome of a clean point-to-point checkout is confidence that the physical foundation everything else rests on is sound. Once you know every wire lands where it should, a wrong reading later can be attributed to configuration or a device, not to a mystery in the cabling. That is a hugely valuable thing to have nailed down before energizing, because tracing a wiring fault backward from a strange symptom on a live loop is slow, frustrating work compared with catching it methodically beforehand.
The classic method is ringing out the conductors: using a meter or a dedicated tester to confirm continuity from one end of a wire to the other, so the technician can prove that the conductor landed on a particular field terminal is the same one landed on a particular I/O channel. One person may work at the field end while another works at the cabinet, coordinating to confirm each pair, or a single technician may work methodically through a documented sequence. Continuity confirms the two ends are electrically the same wire; the loop sheet confirms they are the correct two ends.
The work proceeds through the physical layers of the wiring system. Terminations are checked at junction boxes and marshalling cabinets, where field cables meet system cables and where a large share of wiring errors hide because the crossovers are easy to make and hard to spot. The check confirms not only continuity but the correctness of the mapping - that the tag on the drawing corresponds to the channel it is wired to - so a wire that is continuous but landed on the wrong channel is still caught. Labeling is verified against the drawing at the same time, because a mislabeled wire is a fault waiting to mislead the next person who works on it.
As the checkout proceeds, discrepancies between the wiring and the drawings are recorded and resolved. Sometimes the wiring is wrong and gets corrected; sometimes the field was wired correctly but the drawing is out of date, in which case the drawing is redlined for as-built correction. This redlining is an important byproduct: point-to-point checkout is one of the moments where the paperwork is reconciled with reality, so the as-built loop drawings that go into the permanent record actually reflect what is installed, which matters enormously for everyone who maintains the system afterward.
Point-to-point checkout sits early in the commissioning sequence, before loops are energized and before loop checks are performed. The logic of the order is simple: there is no value in confirming that a signal reaches the operator screen correctly until you have confirmed the wire carrying that signal is connected correctly, because otherwise a loop check failure could stem from either a configuration issue or a wiring issue, and you would not know which. By clearing the wiring first, a later loop check failure can be attributed to configuration or the device with confidence, which makes the whole commissioning effort faster and less error-prone.
It also precedes and complements the functional testing that proves logic. A functional test assumes the signals it acts on are real and correctly wired; if the underlying wiring were crossed, the test could pass or fail for entirely the wrong reasons. So the disciplined stack is wiring first through point-to-point checkout, signal path next through loop checks, and behavior last through functional testing, each layer resting on the verified one beneath it.
For an operation built from many remote sites feeding a cloud SCADA platform such as Merobix, point-to-point checkout remains firmly a field activity, because the wiring it verifies is physical and local to each wellpad, station, or lift station - none of it lives in the cloud. What the platform changes is the feedback loop: because each site reports into a hosted supervisory system reachable from anywhere, a technician ringing out and correcting terminations at a remote site can have a remote engineer confirm, on the same live displays, that the corrected points now arrive with the right tags and values as soon as the loops are energized. The hands-on wiring verification still has to be done at the site, but the confirmation that it worked can be shared across the field crew and a central team, which is valuable when the same standard site wiring is being checked out across a whole fleet of locations.
A point-to-point checkout verifies the wiring - that every field conductor lands on the correct terminal and I/O channel, matching the loop drawings - without yet caring what the signal reads. A loop check comes next and verifies that a signal travels the wired path and arrives on the operator display with the correct value, tag, and scaling. Point-to-point checkout proves the wire is right; the loop check proves the signal is right.
Because there is no point confirming a signal reaches the screen correctly until you have confirmed the wire carrying it is connected correctly. If the wiring were not verified first, a loop check failure could stem from either a wiring fault or a configuration issue, and you would not know which. Clearing the wiring first means a later loop check failure can be confidently attributed to configuration or the device, which speeds up the whole commissioning effort.
Technicians ring out each conductor with a meter or tester to confirm continuity from one end to the other, proving that a wire landed on a particular field terminal is the same one on a particular I/O channel, while checking each termination against the loop sheet. The work proceeds through junction boxes and marshalling cabinets where errors commonly hide, and labeling is verified against the drawings. Discrepancies are corrected in the field or redlined onto the drawings for the as-built record.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.