Dimensioning Systems: Commissioning and Acceptance Checklist

Dimensioning systems measure the length, width, height, and, in many configurations, the volume or estimated weight of a parcel as it moves along a conveyor. They feed this data to warehouse management systems, billing platforms, and sortation controls. Commissioning and acceptance is the formal sequence of checks and tests that confirm the installed system operates accurately, repeatably, and safely under real site conditions. It is not the same as factory calibration, and it is not a single-moment check. This article presents a practical checklist for warehouse operators, maintenance engineers, and controls teams planning to commission a dimensioning system or witness its acceptance.

Purpose and Scope of Commissioning and Acceptance #

Commissioning verifies that the dimensioning system is installed correctly and that its measurements meet the operational tolerance agreed by the site and the supplier. Acceptance is the documented confirmation of that state, typically performed before the system is placed into live production. The scope should cover the complete measurement chain: the triggering device, the dimensioning sensor, the conveyor encoder, the system controller, the network link, and the destination database or control system.

Site acceptance is necessary because factory conditions rarely match the operational environment. Conveyor speed, vibration, surrounding light, parcel mix, belt color, and temperature all affect the measurement result. A dimensioner may be accurate on a test bench and still fail on a live line. Likewise, a system that measures well statically may misread on a moving belt. The commissioning process must therefore prove both static and dynamic performance, and it must confirm that the data leaving the system is the data expected by the downstream systems.

The acceptance criteria should be defined before the tests begin. Typical criteria include maximum permissible deviation in each dimension, a minimum repeatability rate across a defined number of runs, and a maximum allowed missing-read rate. These values are site-specific and should be recorded in the project documentation before commissioning starts. Without pre-defined acceptance criteria, the test results cannot be judged objectively.

Dimensioning System Architecture and Component Interaction #

A clear understanding of the system architecture makes commissioning faster and reduces the chance of misdiagnosis. Although dimensioning systems vary by vendor, most share the same logical building blocks: a triggering device, a measurement engine, a conveyor speed reference, a controller, and an output interface.

The triggering device is often a photoelectric sensor, a light curtain, or a presence beam mounted on or near the measurement frame. Its role is to tell the controller when a parcel has entered and left the measurement zone. The trigger defines the start and end of a scan sequence, and its positioning directly affects the measured length.

The measurement engine is the dimensional sensor itself, most commonly a laser scanner, a structured-light camera, or a time-of-flight sensor. It captures a series of profiles or depth images of the parcel as the parcel travels through the zone. Each sensor has a defined field of view, mounting height, and minimum and maximum detectable object size. The gap between the sensor and the conveyor surface is a known calibration parameter, and any change in that gap affects the measured height.

The conveyor encoder, or tachometer, provides a continuous speed reference to the controller. The dimensioning software uses encoder pulses to synchronize the individual profiles captured by the measurement sensor. If the encoder wheel is worn, not fully contacting the belt, or improperly configured for the wheel diameter, every profile is assigned an incorrect distance step, and the calculated length becomes wrong.

The controller combines the profile data, speed data, and trigger events to reconstruct a three-dimensional representation of the parcel. It then extracts the outer dimensions, applies filtering and rounding rules, and formats the output. The output interface delivers the measurement to a programmable logic controller, a warehouse control system, or a warehouse management system. That interface may be an Ethernet connection, a fieldbus, or a serial link, and the mapping of data fields is a common source of acceptance issues.

Interaction of the Components #

A typical measurement sequence works as follows. The trigger detects the leading edge of the parcel and sends a signal to the controller. The controller begins capturing profiles from the measurement sensor. As the parcel moves through the zone, the encoder pulses tell the controller how far the belt has traveled between profiles. When the trigger detects the trailing edge, the capture stops. The controller stitches the profiles into a single point cloud, calculates the parcel dimensions, and transmits the result. This sequence shows why a failure in any single component can produce an incorrect or missing measurement.

Pre-Commissioning Verification #

Before any dimensional test is performed, the physical and electrical installation should be inspected. The measurement frame must be rigidly mounted and square to the conveyor axis. A frame that is tilted, twisted, or not perpendicular to belt travel will produce skewed measurements that get worse as parcel size increases. Use a precision square and spirit level to check the frame alignment. Verify that the sensor-to-belt distance matches the value in the system configuration, and check that the sensor light beam or camera field of view illuminates the full conveyor width without obstruction from conveyor side rails or structural steel.

Optical surfaces must be clean and free of scratches. Even a thin film of dust can reduce the contrast or intensity of the sensor signal, especially on dark or non-reflective parcel surfaces. Inspect the trigger sensor and the dimensioning sensor windows, and confirm that the protective glass or housing is in place and undamaged. Check the ambient lighting around the measurement zone. Some sensors work well under natural light but fail under direct sunlight or strong overhead lighting. Record the lighting conditions during the acceptance tests so they can be compared with future measurements.

Electrical and network checks are equally important. Confirm that power supplies are correctly wired, grounded, and not shared with large inductive loads such as motors or solenoid banks. Shielded cables should be terminated according to the OEM instructions. The encoder cable is particularly sensitive to electrical noise, and a noisy encoder signal causes intermittent and unpredictable length errors. Check the network configuration, including IP addresses, subnet masks, and communication timeouts, and verify that the controller can communicate with the downstream system before starting dimensional tests.

All safety-related checks must be performed in accordance with site procedures. Lockout/tagout requirements, guard interlocks, emergency stop functions, and any operator access zones should be confirmed before power is applied. The commissioning team should never bypass a safety device to perform a test. Site safety rules and OEM documentation take priority over any test procedure.

Functional Acceptance Testing #

Functional testing is performed in two phases: static and dynamic. Static tests confirm that the sensor measures a stationary object correctly. Dynamic tests confirm that the measurement remains correct when the object is moving on the conveyor and that the data flow behaves properly.

Static Dimension Verification #

For static tests, use a calibrated test object whose dimensions are known and traceable to a recognized metrology process. The object should be a rectangular box or cube with flat, rigid surfaces. Measure the test object with calibrated equipment before the test day, preferably by a person independent of the system integrator. Record the measured values on the test sheet before any dimensioning test begins.

Place the test object on the conveyor at defined positions within the measurement zone: the left edge, the center, and the right edge. Repeat the measurement several times at each position. Do not move the object between repeat runs, because even a small shift changes the physical reference. Record the displayed dimension and compare it with the known value. Also rotate the object 90 degrees and re-measure, because some dimensioning systems are more accurate in one axis than the other. Test with the object near the front and near the back of the measurement zone to check the field of view limits.

For each static test, calculate the deviation in length, width, and height. A deviation within the pre-defined acceptance tolerance is a pass. A deviation outside the tolerance is a failure, and the commissioning team should investigate the cause rather than simply repeating the test. If the system has a built-in calibration routine, consult the OEM documentation on how to run it correctly and when it is appropriate to do so.

Dynamic Dimension Verification #

Dynamic testing is the most critical phase of acceptance because it exercises encoder accuracy, trigger timing, and the controller’s ability to reconstruct an object in motion. Start the conveyor at the normal operating speed and place the test object on the belt with sufficient clearance from leading and trailing parcels. Run the object through the measurement zone several times, allowing the encoder and controller to behave exactly as they will in production.

Run the test object at several positions across the belt width, and also test with the object skewed slightly relative to the belt direction, as real parcels are rarely perfectly aligned. A skewed parcel will still have a correct bounding dimension, but the system may interpret the orientation differently. Record whether the system reports the parcel’s oriented dimensions or its minimum bounding box, and confirm that this behavior matches the site’s expectation. Height readings should remain constant regardless of belt position, because height is independent of encoder travel. Verify that the measured length does not change when the conveyor speed is varied, since a properly configured encoder should correct for speed changes.

Data flow tests should accompany the dimensional tests. For each run, verify that the output record appears in the downstream system within the expected time, that the dimensions match the displayed value, and that the parcel identifier or tracking label is correctly associated with the measurement. Test for missing reads, double reads, and readings triggered by a gap or gap-indicator flag. If the dimensioning system is integrated with a weigh scale or a volume-conversion step, confirm that the combined data is consistent and that the time stamps of each device are synchronized.

Diagnostic Table for Commissioning Issues #

The table below lists common symptoms observed during dimensioning system acceptance, along with likely causes and the appropriate verification step. It is a practical aid for the commissioning team, not a substitute for the OEM manual or competent engineering judgment.