Presence detection is the invisible gatekeeper of a modern warehouse. It tells a conveyor whether a carton has reached a stop, tells an automated guided vehicle whether a pallet is still in the pick bay, and tells a machine-vision system whether the object it sees is actually the object the controller expects. Commissioning and acceptance are therefore not simply the moment a sensor’s indicator turns green. They are the disciplined process of proving that the entire chain—mounting, optics, signal path, logic, output, and operator interface—behaves correctly under the conditions the equipment will face in production. This article provides a technical checklist and acceptance framework that can be adapted by site teams, reviewed by maintenance engineers, and used by controls engineers before a presence detection system is handed over to operational service.
Operating Context and System Boundaries #
Before any test is performed, the commissioning team must define what the presence detection system is being asked to prove. The same sensor can be installed in different contexts with entirely different acceptance criteria. On a conveyor transfer, the function may be “carton present in the lift zone for at least 500 milliseconds.” At a truck dock, the function may be “no personnel or equipment within the sweep area before the door closes.” These are different functions, and the acceptance evidence for one does not validate the other.
The operating context should also include the physical environment: dust and packaging film in the air, high ambient light, reflection from closely spaced racking, vibration from nearby conveying equipment, temperature swings near loading doors, and the presence of forklift traffic that could knock a bracket out of alignment. A detection system that passes every functional test on a clean bench may fail within an hour on a dusty, vibrating transfer deck. The acceptance process must therefore include not only the sensor’s published behavior but also the real conditions at the installation point.
The system boundary matters for acceptance as well. The sensor, its cable, the connector, the PLC input, the control logic, and the downstream indication or actuator all belong to the same function. A “presence detection failure” in production is often diagnosed later as a damaged connector pin or a misconfigured PLC input rather than a failed sensor optic. For this reason, commissioning documentation should clearly state which components are inside the acceptance boundary. If the sensor is supplied by one vendor and the controller by another, the site engineer is responsible for defining the interface expectations, not the individual vendors.
Component Interactions That Influence Acceptance #
Presence detection is a signal chain, and every link in that chain contributes to the accepted behavior. The sensor itself produces a switching state or a measured value. That output travels through a cable and a connector into a controller. The controller interprets the signal according to its configured logic, and then acts on it through a PLC input, a high-speed counter, a vision system, or a direct relay output. The acceptance test must verify the final action as well as the intermediate state.
Consider a simple inductive proximity sensor wired into a PLC input. The sensor’s LED lights when a steel pallet stops in the detection zone. The PLC input may never turn on if the sensor output type does not match the PLC input type, if the common wire is not referenced to the same circuit ground, or if the PLC slot is assigned to a different address. Conversely, the PLC input may remain on because the sensor is bonded over a dark-on configuration that was not recorded in the control drawing. The interaction between the sensor’s switching logic and the controller’s logic inversion is a frequent source of acceptance confusion.
Software debounce and scan time also interact with the sensor’s physical response time. A fast through-beam sensor may detect an object for only 20 milliseconds if the object passes on a narrow edge. If the PLC scans its input every 40 milliseconds, it can miss the event entirely unless the system design contains a latching relay or a high-speed input module. During commissioning, do not assume that a healthy sensor produces a healthy PLC signal. Simulate the event with a high-speed test and observe the actual controller state.
Power quality is another interaction that deserves attention. Sensor outputs are semiconductor devices; they can ride through a brief voltage dip, but they can also reset unpredictably if the power supply falls below the specified minimum. On a large conveyor system, motor starting can pull the DC bus down significantly. Measure the DC voltage at the sensor’s terminals while an adjacent motor starts, or while a forklift charges. This test is rarely performed at initial commissioning, and it is the single most valuable early-warning check for intermittent sensor resets.
Pre-Commissioning Readiness Checks #
Start the acceptance process with a documented readiness walkdown. This step catches most installation errors before any power is applied. At a minimum, the following items should be confirmed and recorded:
- The sensor part number, firmware revision, and configuration profile match the approved engineering drawing. A different variant of the same housing may have a different nominal sensing range or output polarity.
- Mounting brackets are rigid, bolted to structure rather than to vibration-prone sheet metal, and positioned so that the detection zone cannot be struck by a pallet or a load handler.
- Power supply voltage and current capacity are adequate for the sensor and any connected loads. Verify the rated voltage using the OEM datasheet, not the sensor’s label alone.
- Cables are routed away from high-current motor cables, secured at both ends, and installed with sufficient strain relief at the connector. The enclosure cable glands must be tightened to maintain the rated ingress protection.
- Lenses, reflectors, and detection windows are clean and undamaged. Remove protective film, adhesive residue, and any temporary packaging.
- The surrounding area has no temporary obstructions that would change the detection zone once commissioning finishes. Stored pallets, ladders, and building columns are all potential false-target sources.
- All personnel involved in the test have reviewed the site’s energy-isolation procedure and the relevant OEM documentation.
- Operating mode, active mission or route, and the exact sequence state.
- Alarm history, device state changes and controller timestamps.
- Physical observations such as alignment, contamination, wear, obstruction and load condition.
- Recent maintenance, software changes, parameter changes and recurring work orders.
- Upstream and downstream readiness, including blocked, starved and unavailable conditions.
- Is the observed condition repeatable, and has the equipment boundary been stated clearly?
- Are mechanical, electrical, controls, software and process explanations being considered independently?
- Does the proposed action alter a safety function, protected access rule, alarm priority or recovery sequence?
- Can the result be measured with an agreed baseline rather than operator impression alone?
- Will the change remain valid across product sizes, routes, modes, shifts and degraded conditions?
- Is there a documented rollback point and a named owner for follow-up observation?
- Operating mode, active mission or route, and the exact sequence state.
- Alarm history, device state changes and controller timestamps.
- Physical observations such as alignment, contamination, wear, obstruction and load condition.
- Recent maintenance, software changes, parameter changes and recurring work orders.
- Upstream and downstream readiness, including blocked, starved and unavailable conditions.
</
Practical Review Table #
| Review area | Evidence | Interpretation caution |
|---|---|---|
| Operating state | Mode, sequence step, mission and interlock status | Expected holds can resemble equipment faults. |
| Physical condition | Alignment, wear, contamination, obstruction and load condition | One visible defect may be a consequence rather than the cause. |
| Event history | Time-aligned alarms, input changes and recent interventions | Unaligned clocks can reverse the apparent event order. |
| Validation | Controlled test result under representative conditions | A single successful cycle does not establish long-term reliability. |
Apply this table to presence detection: commissioning and acceptance checklist using approved site procedures and documented evidence.
Related Pearl Gateway Guides #
Site-Specific Review Worksheet #
This educational worksheet supports a structured review of presence detection: commissioning and acceptance checklist. Begin by identifying the equipment boundary, control ownership, operating modes, material characteristics, upstream dependencies and downstream consequences. Record what the system is expected to do, what was actually observed and which evidence is time-aligned. Avoid changing several variables at once, because simultaneous changes make cause and effect difficult to establish.
Evidence to collect #
Decision boundaries #
Use approved site procedures and competent engineering judgment before intervention. General information in the Sensors, Identification & Machine Vision library cannot determine whether a specific machine is safe to enter, restart or modify. Preserve original settings, document authorized adjustments and establish a rollback point before controlled testing. When evidence conflicts, stop and resolve the timestamp, naming or measurement discrepancy before drawing a conclusion.
Closeout record #
A useful closeout record states the symptom, confirmed cause, evidence, corrective action, validation method, residual risk and follow-up owner. It should also identify whether the event exposed a design weakness, maintenance gap, training issue, spare-parts issue or monitoring blind spot. This turns a single recovery into reusable reliability knowledge without treating one observation as universal.
Evidence Matrix for Operational Review #
| Evidence group | Questions to answer | Why it matters |
|---|---|---|
| Sequence state | What mode, step, mission and interlock state were active? | Separates a physical problem from an expected control hold. |
| Material condition | Were load dimensions, orientation, stability and spacing within the intended envelope? | Explains faults that appear random when only controller data is reviewed. |
| Device evidence | Which inputs changed, in what order, and against which timestamp? | Supports repeatable diagnosis instead of component substitution by guesswork. |
| Change history | What maintenance, configuration, software or process change preceded the symptom? | Helps define a useful comparison window and rollback boundary. |
For presence detection: commissioning and acceptance checklist, the matrix should be completed with evidence from the same event window. Mixing observations from unrelated shifts can create a convincing but false causal story. If timestamps are inconsistent, establish which controller, server or operator record is authoritative before comparing event order.
Trend evidence is more useful when the measurement definition remains stable. Record units, sampling interval, filtering, equipment mode and product family. A rising fault count may reflect increased throughput rather than deteriorating equipment, while a stable count can hide deterioration if production volume has fallen.
Implementation and Governance Questions #
Before changing a maintenance task, control parameter or operating method related to presence detection: commissioning and acceptance checklist, define ownership and approval boundaries. Identify who can authorize the change, who validates it, how the previous state will be restored and which operating conditions must be represented during the test.
Temporary workarounds should be visible in shift handover and maintenance records. An undocumented workaround can become the new normal and obscure the original defect. Closeout should distinguish containment, corrective action and systemic prevention so later teams do not assume that a restarted system has been permanently repaired.
This governance context is especially important in sensors, identification & machine vision, where local changes can affect upstream release logic, downstream capacity, inventory state or recovery behavior outside the immediate machine boundary.
Site-Specific Review Worksheet #
This educational worksheet supports a structured review of presence detection: commissioning and acceptance checklist. Begin by identifying the equipment boundary, control ownership, operating modes, material characteristics, upstream dependencies and downstream consequences. Record what the system is expected to do, what was actually observed and which evidence is time-aligned. Avoid changing several variables at once, because simultaneous changes make cause and effect difficult to establish.
Evidence to collect #
Decision boundaries #
Use approved site procedures and competent engineering judgment before intervention. General information in the Sensors, Identification & Machine Vision library cannot determine whether a specific machine is safe to enter, restart or modify. Preserve original settings, document authorized adjustments and establish a rollback point before controlled testing. When evidence conflicts, stop and resolve the timestamp, naming or measurement discrepancy before drawing a conclusion.
Closeout record #
A useful closeout record states the symptom, confirmed cause, evidence, corrective action, validation method, residual risk and follow-up owner. It should also identify whether the event exposed a design weakness, maintenance gap, training issue, spare-parts issue or monitoring blind spot. This turns a single recovery into reusable reliability knowledge without treating one observation as universal.
