An aisle transfer car is the bridge between storage aisles in an automated storage and retrieval system. Its commissioning and acceptance are distinct activities: commissioning proves that the installed equipment behaves as designed under controlled conditions, while acceptance confirms that the observed behavior meets the operating requirements agreed by the user, the integrator, and the equipment supplier. This article provides a technical checklist for both phases, with emphasis on observable symptoms, evidence collection, and the boundaries between mechanical, electrical, and control-system responsibility. Site procedures, lockout requirements, the original equipment manufacturer’s documentation, and the judgment of competent engineers always take priority over any generic checklist.
Purpose and Scope of the Acceptance Run #
The acceptance run is not a single demonstration. It is a structured sequence of inspections, measurements, and functional tests that create a documented baseline for future maintenance and modification. For aisle transfer cars, the scope covers travel along the transfer rail, positioning at each aisle stop, communication with the crane or shuttle controller, load transfer at the interface, and interaction with safety devices. The acceptance team should define the pass/fail criteria before the first test is performed, and every criterion should be traceable to the functional specification or the site’s operating requirements.
Commissioning records serve a second purpose beyond sign-off. They become the reference set for troubleshooting later in the equipment’s life. If a transfer car develops an alignment drift or an intermittent stop position fault, the first question is usually “What was the baseline?” Without clean acceptance data, that question is difficult to answer.
Operating Context and System Boundaries #
An aisle transfer car rarely works alone. It operates under the supervision of a warehouse control system, receives commands from a material flow controller, and physically interfaces with cranes, shuttles, conveyors, lifts, and the rack structure itself. During commissioning, the test team must distinguish between failures that belong to the transfer car and failures that appear when the car exchanges data or loads with neighbouring equipment.
Three typical operating contexts exist. In the first, the transfer car moves a complete storage crane across a rail track that runs perpendicular to the aisles. In the second, the car carries a shuttle or a satellite vehicle that then enters a rack aisle. In the third, the transfer car is itself a unit-load carrier that travels between conveyor stations and rack openings. Each context changes the acceptance emphasis. Crane transfer requires precise rail alignment and wheel gauge control. Shuttle transfer requires reliable power and data coupling between the moving car and the shuttle. Unit-load transfer requires accurate stopping and secure load positioning during traverse.
The system boundary for acceptance should be drawn at the transfer interface. This includes the physical dock point, the electrical or inductive coupling for power and data, and the interlock signals that allow or block load transfer. What happens inside the crane, the shuttle, or the conveyor is outside the transfer car acceptance scope, but the interface signals are not.
Component Interactions to Verify #
Before writing the test sequence, the commissioning team should list every component that influences transfer car behaviour. The mechanical group includes the rail, rail joints, concrete or steel support members, the undercarriage, wheel sets, gearboxes, brakes, and any rail sweep or guide rollers. The electrical group includes the motor, drive inverter, encoder, limit switches, proximity sensors, and the power supply system, whether that is a trailing cable, a busbar and collector, or an onboard battery. The control group includes the programmable logic controller, the position control loop, the communications network, and the upper-level control interface.
Each component interaction must be observed during operation, not just at rest. An encoder may read correctly when the car is stationary but produce a noisy signal under load. A rail joint may appear level when measured with a straightedge but deflect when the wheel passes over it under full load. The acceptance sequence should therefore combine static inspection with dynamic measurement.
Pre-Commissioning Checks #
Pre-commissioning checks are performed without moving the car through a full operating cycle. The purpose is to confirm that the installation is mechanically and electrically sound before energy is applied and motion is attempted. These checks should be documented with photographs, signed inspection sheets, and measured values.
The first group of checks concerns the rail. Measure the rail head width, the gauge distance between the two rails, the alignment along the travel direction, and the level across the width of the rail. Rail joints should be checked for step height and gap width. Do not limit measurement to the joint itself; measure the rail support over the full span, because unsupported sections can deflect under load. Record the measurements in a table that can be compared to the OEM tolerances.
The second group concerns the car structure. Check that the wheel flanges clear the rail head by the specified amount. Confirm that guide rollers, if fitted, are set to the correct gap. Inspect gearbox oil levels, coupling alignment, brake pad thickness, and the condition of the travel wheels. Look for foreign material on the rail surface, particularly in environments where debris or product residue is present.
The third group concerns electrical and control readiness. Confirm that the supply voltage, phase rotation, and grounding are correct. Check the continuity of the data cable, the condition of the slip rings or busbar collectors, and the shielding of the communication cable. Verify that the programmable logic controller contains the expected program version and that the configuration files for the transfer car match the actual hardware layout. Record the software revision and the date it was loaded.
Finally, review the safety system. Confirm that all emergency stop devices, light curtains, pressure-sensitive mats, limit switches, and safety relays are present, correctly wired, and labelled. Do not bypass any safety device during commissioning. If a device appears to be positioned incorrectly or trips during normal operation, stop the commissioning work and contact the responsible engineer or the OEM for a documented decision.
Functional Test Sequence: From Jog to Full Cycle #
The functional test sequence should be progressive. Start with single-axis manual motion, then introduce automatic positioning, then add load transfer, and finally run a full multi-cycle scenario that mimics real warehouse operation.
The first level of testing is manual jog. Operate the car in each direction at creep speed and verify that the direction of travel matches the command from the control panel. Check that the drive responds smoothly and that the brake releases fully when the motor is energised. Listen for unusual noise from gearboxes, bearings, and the wheel-rail interface. Stop the car at several positions along the travel path and confirm that the reported position in the controller matches the physical position measured by a laser distance meter or a steel tape.
The second level is automatic positioning. Send the car to each aisle stop, one at a time, from different starting positions. Record the stopping position, the overshoot, and the time taken to complete the move. Repeat the test at least five times per stop for a high-precision transfer car, or three times per stop for a unit-load carrier, to obtain a reasonable sample of repeatability.
The third level is load transfer. If the car carries a crane, perform a slow-speed transfer with the crane in a safe parked position and verify that the transfer rail aligns with the crane rail at every aisle. If the car carries a shuttle, verify that the shuttle can be driven on and off the car without mechanical binding or sensor misalignment. If the car carries unit loads, place a test load on the car, traverse at normal speed, and confirm that the load remains within its defined position tolerance.
The fourth level is a full cycle. Define a scenario that includes several aisle changes, several load transfers, and a mix of full and empty loads. Run the scenario under automatic control and record any alarms, fault messages, or manual interventions required. The full cycle should be repeated until the system completes at least one cycle without intervention, and ideally several cycles to expose intermittent faults.
Diagnostic Observations During the Test Sequence #
Every fault observed during commissioning should be recorded with objective evidence. A fault description such as “car overshoots” is not sufficient. The record should include the commanded stop position, the actual stop position, the speed profile, the load condition, and the state of the positioning sensor at the moment of overshoot. This information allows the responsible engineer to distinguish between a mechanical braking problem, an encoder scaling error, a drive tuning issue, and a sensor detection delay.
The table below presents common observable symptoms, the evidence that should be collected, and the likely areas to investigate. The table is a guide, not a complete fault diagnosis manual.
| Observable Symptom | Evidence to Collect | Likely Causes to Verify |
|---|---|---|
| Car stops short of the aisle stop position | Final position from the controller, encoder counts at the stop, final approach sensor timing, physical distance measured by laser | Positioning sensor drift, encoder scaling error, brake engaging before the stop command, debris on the rail slowing the car |
| Load shifts during traverse | Accelerometer or vibration data, load position sensor status, speed and acceleration setpoints, footage of the load | Acceleration ramp set too aggressively, rail joint step, wheel flat spots, worn guide rollers, load not centred on the carrier |
| Car aligns with rack but crane interface rejects the transfer | Measured offset between car rail and crane rail, camera or laser measurement of skew, front and rear wheel position values | Asymmetric wheel wear, rail gauge widening, loose coupling between drive and wheels, encoder offset on one axis, thermal growth of the building structure |
| Intermittent loss of communication while the car is moving | Network error counters, timestamped PLC alarms, voltage readings on the data cable shield, signal strength statistics | Busbar contamination or collector bounce, cable reel tension variation, grounding loop on the control cabinet, electromagnetic interference from other drives |
| Safety system trips during normal travel | Which safety zone was active, the state of each safety device at the trip time, the car position, and the travel direction | Safety cam misalignment, bumper creep, sensor sensitivity threshold set too low, vibration-induced false trigger |
Acceptance Criteria and Data Collection #
Acceptance criteria must be numeric, observable, and repeatable. Typical criteria for an aisle transfer car include the maximum allowed stopping position error, the maximum allowed skew between front and rear wheels, the maximum traverse time between specified aisle positions, and the required number of successful cycles without intervention. Each criterion should have a defined test method, a defined sample size, and a defined tolerance for environmental conditions such as temperature and load weight.
Data collection during acceptance should be automated where possible. If the controller can produce a position log, a speed log, and an alarm log, export these records after every test run. If the car has a network connection to the warehouse control system, archive the relevant messages. For manual measurements, use a single person to take the reading and a second person to record it, then sign both the measurement sheet and the data entry.
When a criterion is not met, the acceptance team faces a decision boundary. The first decision is whether the deviation is a genuine fault or a tolerance problem in the test method. If the measurement method itself is uncertain, repeat the measurement before changing any equipment settings. If the deviation is confirmed, the next decision is who has the authority to adjust the relevant component. The commissioning engineer, the OEM representative, or the site maintenance engineer must make the adjustment, depending on the contractual and safety boundaries agreed before the acceptance work began.
After any adjustment, the affected tests must be repeated from the beginning. It is not acceptable to adjust a positioning sensor and then re-test only the final stop. The car must pass the full sequence again because a change to one component can affect the performance of another.
Common Interpretation Errors During Commissioning #
Commissioning teams can easily misinterpret symptoms when they lack a clear baseline. One common error is treating a single successful cycle as proof of consistent behaviour. A transfer car may complete one perfect automatic cycle and then fail the next because of a marginal sensor, an unstable power supply, or a rail section that deflects only when the building temperature rises. Acceptance sampling should be large enough to expose intermittent faults, even if this extends the commissioning schedule.
Another common error is confusing a control-system fault with a mechanical fault. For example, a car that stops inconsistently may appear to have a brake problem when the actual cause is a worn encoder coupling that produces an irregular position feedback signal. The evidence table helps avoid this by requiring the team to collect speed profiles, position words, and mechanical measurements before replacing parts.
A third error is measuring alignment only at the rail joints. Joint measurements are useful, but a rail that is level at every joint can still deflect between supports. The car feels the rail along its entire length, so the acceptance team should measure the rail at mid-span points and record the deflections under a loaded car if possible.
A fourth error is accepting an empty-car test as proof of loaded-car behaviour. The inertia of a loaded crane, shuttle, or unit load changes the acceleration torque, the stopping distance, and the stress on the rail. At least a portion of the acceptance cycle must be conducted with a load that represents the worst-case operating condition. Conversely, empty-car tests are still valuable because they can reveal vibration and noise that a loaded car may mask.
Finally, do not interpret a self-recovering fault as harmless. If a safety device trips and the system resets itself, the trip event must be investigated rather than ignored. An intermittent safety trip during commissioning often becomes a regular production interruption after the system is accepted.
Maintenance Implications After Acceptance #
The acceptance records should be transferred to the maintenance team in a form that can be used as a reference baseline. This includes the measured rail dimensions, the wheel clearances, the positioning repeatability data, the alarm log from the test cycles, and the software configuration. The maintenance team should compare future measurements against this baseline to determine whether the equipment is drifting, wearing, or settling.
Wear rates provide useful maintenance indicators. The first few months of operation typically produce the highest wear as components bed in. If a weekly rail or wheel measurement shows a significant change from the acceptance baseline, the maintenance team should investigate the cause rather than simply continuing with the scheduled lubrication routine. The acceptance data also supports the definition of lubrication intervals, because a car that shows rising drive current or increasing stopping distance may need lubrication sooner than the calendar suggests.
Alignments and tolerances degrade over time due to building settlement, concrete creep, and thermal expansion. A periodic survey of the transfer rail, typically every six to twelve months, should include the same measurement points used during acceptance. If the survey shows a progressive deviation, the next decision boundary is whether the deviation is within the equipment’s adjustment range or whether structural corrections are required. This decision must be made by a structural or mechanical engineer, not by forcing the car to operate outside its designed tolerance.
Safety Boundaries and Decision Handover #
Safety during commissioning and acceptance is not the same as safety during normal operation. The car is being commanded in ways that it may not encounter in daily service, and the surrounding system may not be fully guarded. All personnel involved in the acceptance run should be aware of the test plan, the exclusion zone around the transfer area, and the communication method for stopping the test immediately if a hazard appears.
Lockout and tagout procedures apply to every maintenance step, even short checks such as cleaning a sensor or tightening a coupling. The acceptance team must not bypass or short out any safety device to complete a test. If a safety device conflicts with the commissioning process, the test should be paused and the conflict reported through the site’s formal deviation process. The OEM documentation and the site’s safety rules define how to proceed in that situation.
The decision to hand the transfer car over from the commissioning team to the operations team is a formal boundary. It should occur only after all acceptance criteria are met, all outstanding job cards are either closed or explicitly transferred to a responsible owner, and the maintenance team has received the completed baseline records. From that point onward, changes to the car or its control settings must follow the site’s change control procedure, because the acceptance baseline is no longer valid if the equipment is modified
