Skip to content
Skild Robotics Operations

ABM operations manual

Note. The local extract is dated Mar 31, 2026. The Drive Google Doc owned by anway@skild.ai is dated Apr 14, 2026 — about 2 weeks newer. Re-check on work computer; this SOP captures the Mar 31 version. See BACKLOG B-A4.

Scope

This is the customer-facing operations manual for the GO2W-26 robot at LaGuardia Airport (LGA) under the ABM tenancy. It defines what operators do, in what order, with what safety expectations.

Purpose

This operating manual provides the information needed to safely operate, monitor, and maintain the GO2W-26 robot deployed at New York LaGuardia Airport (LGA). The robot is intended to perform assigned duties within the airport environment — where pedestrian traffic, constrained spaces, security procedures, and time-sensitive operations require consistent, predictable behavior and clear operator oversight. [SOURCE: ABM Ops Manual §"Introduction"]

How to use this manual

Document scope & assumptions

This manual assumes the robot is deployed under an approved LGA operational plan with designated operating zones and trained personnel available for oversight. It does not replace airport regulations, security requirements, or emergency response procedures. Operators are responsible for ensuring the robot is used only as authorized and that any safety or security concerns are escalated immediately. [SOURCE: ABM Ops Manual §"Document scope and assumptions"]

Operation workflow

1. Report on-site & coordinate escort

See /sites/lga/overrides/ §“Escort protocol”.

Key points:

  • Arrive at scheduled report time.
  • Confirm whether an escort is required.
  • (Skild operators) contact escort via Slack: name, role, location, planned start, intended area.
  • Exception: Kai is exempt from the escort step. [SOURCE: ABM Ops Manual §1]

2. Pick up the robot

  • Proceed to ABM office (or designated storage/hand-off location).
  • Hand-off inspection:
    • Robot physically intact.
    • All accessories present (extra batteries, charging brick, controller, tablet, TSA docs if applicable).
    • No loose parts, exposed wires, dragging items.
  • If anything looks abnormal or missing, stop and resolve before continuing. [SOURCE: ABM Ops Manual §2]

3. Gate pass & TSA

  • Obtain valid gate pass for intended terminal area + time window.
  • Pass TSA following all security personnel instructions.
  • After clearing TSA, verify robot and accessories are still secure.
  • Exception: if the robot is stored within Terminal B, the TSA step precedes step 2 (robot pickup). [SOURCE: ABM Ops Manual §3]

4. Identify and confirm the operating area (CCA, CCB, or Food Court)

Acceptable operating areas:

  • CCA
  • CCB
  • Food Court (current operating space as of Mar 31, 2026)

Visually identify boundaries and conditions:

  • Pedestrian density.
  • Temporary obstructions (queues, cleaning equipment, construction barriers).
  • Surface conditions (wet floors, uneven thresholds, mats, rugs, slopes).
  • Local restrictions or instructions posted by airport / ABM.

Confirm a safe staging spot where the robot can be powered on without blocking walkways. If the intended zone is unusually crowded / obstructed / restricted: identify a safe alternate staging position and coordinate any changes with the remote operator. [SOURCE: ABM Ops Manual §4]

5. Power on the robot & establish remote-operator communication

  • Move to the selected staging spot.
  • Power on per /robots/go2/setup/pre-flight-checklist/ and /robots/go2/.
  • Allow boot + self-checks to complete. Do not move into traffic flow until fully ready.
  • Send initial Slack status message to remote operator including:
    • Robot powered on.
    • Current location (terminal + area + landmark).
    • Any immediate operational constraints.
    • Ready confirmation.
  • Remain available for follow-up. [SOURCE: ABM Ops Manual §5]

Navigation & active monitoring

Route selection (on-site operator owns ground truth)

  • After arrival in assigned area, on-site operator selects a route appropriate for current conditions.
  • Consider: pedestrian traffic, temporary obstacles, local restrictions, emergency access (do not block emergency corridors or exits), safety restrictions (geofenced locations, buffer away from escalators and stairs).
  • Determine number of loops realistic for shift duration, battery level, expected traffic.
  • Communicate to remote operator: route name/description, starting location + direction of travel, number of loops, any known constraints. [SOURCE: ABM Ops Manual §1 "Route Selection and Loop Plan"]

Start of navigation (remote operator)

Real-time monitoring (remote operator)

Continuously monitor:

  • Alerts and system warnings (safety triggers, navigation warnings, sensor issues, protective stops).
  • Robot pose on map (correct localization, on planned path).
  • Watch for unexpected pose jumps, drift, or routing anomalies.
  • Be prepared to pause, reroute, or stop and restart if risk signals appear. [SOURCE: ABM Ops Manual §3]

On-site oversight & safety intervention

  • Supervise based on current autonomy stage (L0 — within arm’s reach as of Mar 31, 2026).
  • Primary responsibility: public safety and immediate physical oversight.
  • Watch pedestrian interactions; anticipate conflict zones (tight corners, queues, merges).
  • Confirm robot is not blocking entrances or emergency pathways.
  • Ensure robot does not enter restricted or unintended areas.
  • Be prepared to intervene if remote loses connection or control.
  • Communicate re-mapping need if environment changed materially.
  • Battery swaps: below 25%, inform remote and only proceed after acknowledgement. [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]

Issue reporting (remote operator)

  • Document operational issues using the designated Google Form as soon as the issue is resolved.
  • Contact on-site operator if physical intervention is needed.
  • Reportable issues list: see /general/incident-response/ (same list).

Completion criteria

A route run is complete when:

  • Planned loops executed OR run intentionally ended due to safety / operational constraints.
  • Robot returned to a safe state (stopped/paused in a staging position).
  • Issues encountered are documented in the Google Form by remote operator.
  • On-site + remote have communicated end-of-run status and next steps.
  • Robot is returned to safe staging area and securely locked in storage box before on-site operator departs. [SOURCE: ABM Ops Manual §"Completion Criteria (End of Route Run)"]

Autonomy stages

StageNameSupervision
L0Data Collect — Within Arm’s ReachOn-site operator within arm’s reach. No conversations. No distractions. Maintained for 5 full shifts after any major software change.
L1Locally Supervised — Line of SightOn-site maintains continuous line of sight.
L2Remotely Supervised — Not Line of SightRemote monitoring authoritative; on-site presence not required at all times.
L3Fully AutonomousNo continuous human supervision required.

Current stage (Mar 31, 2026): L0. Stages do not progress without explicit Skild / ABM alignment. [SOURCE: ABM Ops Manual §4 + SOP V3 §"Autonomy Stages"]

Source notes

  • [SOURCE: ABM Operations Manual.docx] (Mar 31, 2026). Maintainers: Anway Shirgaonkar, Robert Belle-Isle, Laura Kasimatis, Jimit Gandhi. Drive Google Doc (Apr 14, 2026; ~2 weeks newer): https://docs.google.com/document/d/1mSJ8zEmercxNjWOYGTjA-eZUKJ8hk1EQ9jsyYjkSGEs/edit
  • Cross-validated against [SOURCE: GO2_Standard_Operating_Procedure_V3.docx] §“Site-Specific — LGA Terminal B” — content largely matches.
  • Comparative reference: [SOURCE: GO2_Standard_Operating_Procedure_ABM.docx] (April 2026, Tyler Kugima) — operator field reference; agrees with this manual on the topics they cover.

Conflict / open items

  • ABM Ops Manual local extract (Mar 31) is older than the Drive Google Doc (Apr 14). Refresh on work computer (BACKLOG B-A4).
  • Track.Go2.ABM.LGA/GO2_LGA_ABM_Intelligence/12_SOPs/ may contain LGA-specific SOPs that overlap this doc. Not yet enumerated (BACKLOG B-A5).
  • Relationship between this doc (customer-facing operations manual) and the April 2026 GO2 ABM SOP (operator field reference) is unclear — may be separate documents.