# Automated Guided Vehicles: Shift-Level Diagnostic Playbook - Canonical: https://pearlgateway.net/docs/automated-guided-vehicles-shift-level-diagnostic-playbook/ - Updated: 2026-10-04T04:42:00+00:00 Automated guided vehicles occupy an unusual position in a warehouse. They are mobile machines, networked devices, and production assets at the same time. A fault that looks like a sensor failure may actually be a charging schedule problem. A navigation deviation may be a floor surface issue. A recurring stop may be a traffic coordination mismatch. This playbook presents a shift-level diagnostic framework for AGV fleets, aimed at operators, maintenance engineers, and controls teams who need a calm, repeatable way to classify symptoms, collect evidence, and decide whether to adjust, escalate, or initiate a deeper engineering investigation. It is not a substitute for OEM procedures and does not override any safety requirement. Lockout/tagout, site-specific work instructions, OEM documentation, and competent engineering judgment always take priority over general diagnostic guidance. ## The Shift-Level Diagnostic Mindset A shift-level diagnostic is not a root-cause investigation. It is a structured first response. The goal is to restore safe functional operation or to create a useful evidence package for the next engineering review. That distinction matters. When a vehicle stops at an unexpected location, a repair technician under time pressure may be tempted to clear the error and return the vehicle to service immediately. That action can hide an intermittent fault and cause a more expensive failure later. The shift-level mindset is to treat every unresolved interruption as a clue, not as an inconvenience. Diagnostic work under time pressure produces interpretation errors. One common error is last-event attribution: when an operator sees an error code close to a known condition, they assume that condition caused the fault. For example, a charger fault appearing just after a vehicle parks may be read as charger contact misalignment. But if three vehicles show the same code on the same charger, the problem may be in the charging zone, the contactor logic, or the fleet manager’s assignment pattern. Another error is code myopia: focusing only on the reported alarm name and ignoring the context before the alarm, such as trajectory deviations during the previous hour, repeated retries, or unusual sounds. Evidence collection should start at the first symptom. Log timestamps, vehicle identifiers, zone names, and any audible or visual cues. The richer the shift-level record, the easier it is for controls engineers to identify patterns that are invisible in a single event. Good evidence does not need to be comprehensive; it needs to be consistent and neutral. Describe what changed, when it changed, and whether it changed alone or with other statuses. A shift report that says “vehicle stopped” is not evidence. A shift report that says “vehicle 12 stopped at aisle C4 at 13:22 after three retries, with no obstacle visible ## 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 automated guided vehicles: shift-level diagnostic playbook using approved site procedures and documented evidence. ## Related Pearl Gateway Guides - [Mobile Robot Mission Recovery: Capacity Planning and Bottleneck Analysis](/docs/mobile-robot-mission-recovery-capacity-planning-and-bottleneck-analysis/) - [Autonomous Mobile Robot Fleets: Lifecycle Upgrade and Obsolescence Strategy](/docs/autonomous-mobile-robot-fleets-lifecycle-upgrade-and-obsolescence-strategy/) - [Automated Guided Vehicles: Lifecycle Upgrade and Obsolescence Strategy](/docs/automated-guided-vehicles-lifecycle-upgrade-and-obsolescence-strategy/) ## Site-Specific Review Worksheet This educational worksheet supports a structured review of automated guided vehicles: shift-level diagnostic playbook. 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 - 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. ### Decision boundaries Use approved site procedures and competent engineering judgment before intervention. General information in the Robotics, AMRs & Automated Handling 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 automated guided vehicles: shift-level diagnostic playbook, 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 automated guided vehicles: shift-level diagnostic playbook, 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. - 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? 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 robotics, amrs & automated handling, 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 automated guided vehicles: shift-level diagnostic playbook. 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 - 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. ### Decision boundaries Use approved site procedures and competent engineering judgment before intervention. General information in the Robotics, AMRs & Automated Handling 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 automated guided vehicles: shift-level diagnostic playbook, 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 automated guided vehicles: shift-level diagnostic playbook, 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. - 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? 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 robotics, amrs & automated handling, 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 automated guided vehicles: shift-level diagnostic playbook. 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 - 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. ### Decision boundaries Use approved site procedures and competent engineering judgment before intervention. General information in the Robotics, AMRs & Automated Handling 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 automated guided vehicles: shift-level diagnostic playbook, 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.