Skip to content
Skild Robotics Operations

Incident response (LGA)

Scope

LGA-specific incident response and reporting workflow. Extends /general/incident-response/ with LGA-specific intake form, dashboard, and escalation expectations.

Purpose

LGA operates inside a regulated environment (airport security, ABM tenant agreement). Incidents have a higher visibility and a tighter escalation expectation than purely internal incidents. [SOURCE: ABM Operations Manual §"Issue Reporting" + §"Document scope and assumptions"]

Required inputs / tools

Reportable issues (LGA)

All reportable issues from /general/incident-response/, plus the LGA-specific:

  • Robot entered an unapproved zone (outside CCA / CCB / Food Court). Reportable; can jeopardize the deployment. [SOURCE: SOP V3 LGA §"Stay Within the Assigned Zone"]
  • Airport security or law enforcement interaction.
  • Public injury or property damage within the terminal.
  • TSA-related issue at gate pass / transit.
  • Robot left unsecured at shift end (locked box check failed).

Procedure

During — On-site safety intervention

The on-site operator must be prepared to intervene if the remote operator loses connection or control: [SOURCE: ABM Ops Manual §4 "On-Site Oversight and Safety Intervention"]

  • Take appropriate safety action per site procedure (initiate stop, move the robot to a safe staging position, or use the emergency stop if required).
  • If the environment has changed materially from when it was mapped, communicate with the remote operator that re-mapping is required.

If a battery swap is needed (level < 25%):

  1. Inform the remote operator that a battery change is about to occur.
  2. Only after acknowledgement / coordination, proceed with powering the robot down as required and completing the battery replacement. [SOURCE: ABM Ops Manual §4]

Key principle: If there is any uncertainty about control or safety, the robot should be placed into a safe state (pause/stop) until the situation is resolved. [SOURCE: ABM Ops Manual §4]

After — Report submission (remote operator)

  1. Open the LGA intake form (link above).
  2. Capture, at minimum: [SOURCE: ABM Ops Manual §5; SOP V3 §XX; April 2026 ABM SOP §XX]
    • Time and location — terminal + zone (CCA / CCB / Food Court) + nearby landmark.
    • What the robot was doing (starting a loop, turning a corner, docking attempt, etc.).
    • Operational mode (autonomous or teleop).
    • Observed symptoms and any alerts on screen.
    • Corrective actions taken and the outcome.
    • Environmental factors (crowd density, obstacles, layout changes).
    • Photographic documentation if available.
  3. Submit.
  4. Post a brief Slack summary in the deployment channel with the form link.

After — Site / ABM escalation

  • Collision, injury, or airport escalation → notify management directly, before filing the form if time-critical. [SOURCE: SOP V3 §XX; April 2026 ABM SOP §XX line 710]
  • Notify Skild through the designated Slack channel.
  • ABM site coordinator (handle TBD) for any incident affecting ABM tenancy / public visibility.

Completion criteria

A route run is considered complete when: [SOURCE: ABM Ops Manual §"Completion Criteria"; SOP V3 §XVIII]

  • Planned loops executed (or run intentionally ended for safety/operational reasons).
  • Robot in a safe state (stopped/paused in staging position).
  • Any encountered issues are documented in the form by the remote operator.
  • On-site + remote have communicated end-of-run status and next steps.
  • Robot returned to safe staging area and securely locked in storage box before on-site operator departs.

Common LGA-specific failure modes

IssueLikely causeAction
Robot drifted into unapproved zone during teleopOperator lost zone-awarenessImmediate stop + return + report. Treat as reportable even if no other harm. [SOURCE: SOP V3 LGA]
Crowd unexpectedly dense in assigned zoneConcert / event / weather diversionPause; identify safe alternate staging spot; coordinate any change with remote operator. [SOURCE: SOP V3 LGA §"Identify and Confirm the Operating Area"]
Robot unable to navigate due to recent layout changeMapped environment changedCommunicate with remote operator that re-mapping is required. [SOURCE: ABM Ops Manual §4]
Approaching battery limit but route loop not completeSpare not staged, or 20% triggered before swapNotify remote at 25%, swap with acknowledgement. [SOURCE: SOP V3 §XVI]
Approached by airport security mid-runAuthority interactionCooperate; sit the robot during conversation; offer to connect them with management; report after. [SOURCE: SOP V3 §IV]

Escalation severity ladder (LGA)

  1. Standard operational (localization loss, missed waypoint, app glitch) → file LGA form; resume.
  2. Hardware anomaly → file form, do not resume until cleared.
  3. Airport / ABM-visible incident (zone violation, security interaction, public-facing event) → notify management first, then file.
  4. Injury or property damage → first aid / 911 per protocol; notify management; file; preserve scene for investigation if possible.

Source notes

  • [SOURCE: GO2_Standard_Operating_Procedure_V3.docx] §IV (Security cooperation), §XV-XX (operations + reporting).
  • [SOURCE: ABM Operations Manual.docx] (Mar 31, 2026) §4 (On-Site Oversight + Safety Intervention), §5 (Issue Reporting), §“Completion Criteria”.
  • [SOURCE: GO2_Standard_Operating_Procedure_ABM.docx] (April 2026, Tyler Kugima) §XX Incident Reporting (form URL line 713, escalation lines 710–711). Authoritative for ABM-LGA.
  • [SOURCE: ABM Go2 Incident Report Form] — LGA intake.
  • [SOURCE: ABM Go2 Incident Dashboard] — Drive spreadsheet.