Autonomous Driving Software — Ch.12: Outdoor AMR Case Studies [EN]
DEV Community

Autonomous Driving Software - Ch.12: Outdoor AMR Case Studies [EN]

STATERA Library · Series 08 · Volume 12 · Chapter 12 · EN

Source: https://github.com/Statera-Library/08_Vol_12_Autonomous_Driving_Software/blob/main/Chapter_12_Outdoor_AMR_Case_Studies/Chapter_12_Outdoor_AMR_Case_Studies_EN.md

Volume 12. Autonomous Driving Software

Chapter 12. Outdoor AMR Case Studies

12.01. Outdoor Security AMR Autonomous Patrol SW Case

An outdoor security AMR extends autonomous driving software from transportation into persistent physical security operations. Unlike a road vehicle whose primary mission is point-to-point mobility, a patrol robot repeatedly executes routes, observes designated zones, detects abnormal conditions, and reports evidence.

Its software therefore integrates autonomous navigation, perception, mission management, safety supervision, and remote fleet operation into one continuous operational loop.

Operational Design Domain

The operational design domain must describe where and under what conditions autonomous patrol is permitted. Typical environments include:

  • industrial campuses
  • logistics yards
  • ports
  • power facilities
  • apartment complexes
  • fenced infrastructure sites

The ODD specifies road geometry, pedestrian access, allowable speed, lighting, weather, terrain, communication coverage, localization availability, and restricted areas so that autonomy behavior can be constrained to validated conditions.

Software Architecture

A practical software architecture separates sensing, localization, perception, world modeling, behavior planning, trajectory generation, vehicle control, safety supervision, and mission orchestration. This separation allows individual components to evolve without redesigning the complete robot.

Outdoor security operation also requires interfaces to patrol schedules, alarm systems, remote operators, charging infrastructure, maps, and fleet services, making orchestration an important layer above the conventional autonomous-driving stack.

Sensing Pipeline

The sensing pipeline commonly combines LiDAR, cameras, GNSS/RTK, IMU, wheel odometry, and optionally radar or ultrasonic sensors. Raw measurements are timestamped, calibrated, filtered, and transformed into common coordinate frames before fusion.

The resulting representation supports obstacle detection, free-space estimation, localization, and security perception. Sensor-health monitoring is equally important because contamination, glare, rain, vibration, or communication faults can degrade individual sensing channels during long unattended missions.

Localization

Localization normally combines globally referenced and locally referenced estimates rather than depending on one technology. GNSS/RTK can provide accurate outdoor positioning in open areas, while LiDAR localization, visual features, inertial estimation, and wheel odometry maintain continuity near buildings or vegetation.

The localization software should continuously estimate confidence and detect disagreement among sources. When uncertainty exceeds an operational threshold, the system can reduce speed, request recovery, or transition toward a minimal-risk condition.

Perception

Perception transforms sensor observations into an operational model of the patrol environment. The robot must distinguish traversable surfaces from curbs, walls, vegetation, vehicles, pedestrians, temporary objects, and negative obstacles where relevant.

Object detection and tracking provide position, velocity, and trajectory estimates for dynamic agents, while occupancy or traversability representations describe usable space. Security-specific analytics can operate alongside navigation perception without being allowed to compromise safety-critical obstacle detection.

World Model

The world model provides the shared environmental state consumed by planning modules. It combines static map information with dynamic obstacles, localization uncertainty, drivable-area estimates, route constraints, semantic regions, and temporary hazards.

A patrol mission may additionally define checkpoints, observation zones, prohibited areas, speed-limited regions, charging stations, and communication-sensitive locations. Maintaining these elements in a coherent representation reduces inconsistent decisions between mission, behavior, and motion-planning layers.

Mission-Level Software

Mission-level software converts security objectives into executable robot tasks. A patrol schedule may contain route segments, checkpoints, dwell times, inspection actions, camera orientations, and return-to-charge conditions.

Instead of treating the robot as a vehicle following a fixed path, the mission manager maintains task state and determines what should happen next. It can skip inaccessible checkpoints, retry interrupted observations, prioritize alarms, or return to a previously defined safe location after abnormal events.

Behavior Planning

Behavior planning translates mission intent and perceived conditions into driving decisions such as proceed, yield, follow, stop, wait, bypass, re-route, inspect, or return. Outdoor patrol environments are often semi-structured, so purely lane-oriented automotive logic is insufficient.

The planner must handle parked vehicles, pedestrians crossing informal paths, temporary construction barriers, narrow passages, gates, and unexpected obstacles while respecting operational rules and preserving a deterministic safety envelope.

Trajectory Generation

Trajectory generation converts the selected behavior into a dynamically feasible motion sequence. Candidate trajectories are evaluated against obstacle clearance, curvature, steering limits, acceleration, braking capability, terrain constraints, and predicted movement of surrounding agents.

Re-planning occurs continuously as the scene changes. At patrol speeds, smoothness remains useful for sensor stability and mechanical durability, but collision avoidance and reliable stopping distance take precedence when environmental uncertainty increases.

Control Layer

The control layer converts the selected trajectory into steering, propulsion, and braking commands through the drive-by-wire interface. Longitudinal and lateral controllers compensate for vehicle dynamics, actuator delay, payload variation, slope, and surface conditions.

Outdoor platforms require additional attention to wheel slip and traction because wet pavement, gravel, grass, ramps, and uneven surfaces can invalidate assumptions made on uniform roads. Feedback from actuators must therefore return continuously to planning and safety functions.

Safety Supervision

Safety supervision should remain logically independent from normal autonomy wherever practical. Runtime monitors check localization validity, sensor health, obstacle distance, commanded velocity, controller status, communication state, and software heartbeat signals.

A safety cage can reject unsafe commands even when the primary planner considers them valid. Depending on the detected fault, the robot may reduce speed, stop immediately, execute a controlled stop, enter a minimal-risk condition, or request intervention from a remote operator.

Degraded Operation

Autonomous patrol also requires explicit handling of degraded operation. Loss of RTK correction does not necessarily require an immediate emergency stop if another validated localization mode remains available, whereas simultaneous localization degradation and obstacle-sensing failure may require termination of autonomous movement.

This motivates a degradation-state machine that maps combinations of component health and environmental conditions to permitted capabilities rather than representing the entire autonomy stack with a simple healthy-or-failed state.

Security Perception

Security perception forms a second interpretation layer over the navigation scene. Depending on the application, software may detect unauthorized presence, prolonged loitering, intrusion into restricted zones, abandoned objects, open gates, smoke-like visual anomalies, or other predefined events.

These detections should be treated as evidence with confidence and context rather than automatic conclusions. Temporal tracking, repeated observations, sensor corroboration, and remote confirmation can reduce false alarms in changing outdoor environments.

Event Handling

When an event is detected, the robot should preserve operational context rather than transmitting only an alarm flag. Relevant data can include time, robot pose, sensor observations, object tracks, event classification, confidence, and a short history before and after detection.

The mission manager may command the robot to stop at a safe observation point or reposition within predefined constraints. Remote personnel can then review the evidence and determine whether escalation, continued observation, or mission resumption is appropriate.

Connectivity

Connectivity must be treated as an operational resource rather than an assumption. High-bandwidth video may be available only in portions of a patrol area, while safety-critical autonomy must continue locally at the edge.

The robot therefore performs perception, localization, planning, control, and immediate safety decisions onboard. Cloud or on-premise systems can handle mission assignment, fleet monitoring, historical storage, analytics, software distribution, and operator interfaces without becoming mandatory participants in every real-time driving cycle.

Fleet Management

A fleet-management layer becomes important when multiple security AMRs share a facility. It assigns patrol regions, avoids redundant coverage, coordinates charging, tracks robot health, and redistributes missions when one robot becomes unavailable.

The fleet system can also maintain common maps and temporary operational restrictions. However, each robot should retain enough local autonomy to stop safely and manage short communication interruptions rather than depending on continuous centralized motion commands.

Energy Planning

Long-duration patrol introduces energy as part of autonomy planning. Battery state, predicted route consumption, environmental temperature, payload power, compute load, and distance to charging infrastructure affect whether a mission can be completed safely.

Charging should therefore be represented as a mission behavior rather than a separate maintenance activity. The system can reserve sufficient energy for recovery, schedule charging between patrol cycles, and interrupt lower-priority tasks before energy margins become operationally unsafe.

Validation

Validation of the complete system requires more than measuring perception accuracy or trajectory-tracking error independently. Scenario-based testing should combine pedestrians, vehicles, blocked routes, localization degradation, sensor faults, communication loss, weather variation, low illumination, emergency stopping, and mission recovery.

Simulation can provide repeatability and large scenario coverage, while closed-course and operational field testing reveal interactions with surfaces, lighting, radio conditions, contamination, and human behavior that are difficult to model completely.

Operational Data

Operational data closes the development loop. Disengagements, false alarms, emergency stops, localization confidence drops, unusual obstacle configurations, planner failures, and operator interventions can be recorded as structured events.

Engineers can reconstruct these cases, classify their causes, reproduce them in simulation, and convert representative failures into regression scenarios. In this way, fleet operation becomes a source of evidence for continuous improvement rather than merely the final stage after software deployment.

The complete patrol case demonstrates why outdoor AMR autonomy is a system problem rather than a collection of isolated algorithms. Sensor processing, traversability estimation, object tracking, localization, behavior planning, trajectory generation, control, safety, mission management, fleet operation, and data feedback must cooperate under changing real-world conditions.

This case therefore integrates the major autonomous-driving software functions developed across the volume into one persistent robotic operational workflow.

12.02. Outdoor Inspection AMR Infrastructure Survey Case

An outdoor inspection AMR transforms autonomous mobility into a persistent infrastructure surveying platform capable of collecting spatial, visual, thermal, and condition data while moving through large facilities. Unlike a patrol robot focused primarily on security events, an inspection AMR must coordinate vehicle motion with measurement quality.

Navigation, sensor positioning, inspection sequencing, localization, data acquisition, and quality verification therefore operate as a tightly integrated software workflow.

Typical deployment environments include:

  • rail facilities
  • industrial plants
  • ports
  • construction sites
  • utility corridors
  • bridges
  • tunnels
  • campuses
  • large logistics complexes

These environments contain paved roads, gravel, ramps, curbs, narrow passages, machinery, pedestrians, temporary structures, and changing work zones. The operational design domain defines terrain, allowable speed, inspection distance, weather limits, localization availability, communication coverage, and areas requiring supervised operation.

The software architecture combines an autonomous-driving stack with an inspection mission layer. Sensor processing, localization, traversability estimation, object detection, behavior planning, trajectory generation, control, and safety supervision provide mobility, while mission orchestration manages inspection routes, measurement points, sensor activation, data capture, and survey completion.

This separation allows the same mobile platform to support different inspection payloads without redesigning the complete autonomy system.

Navigation sensors can include LiDAR, cameras, GNSS/RTK, IMU, wheel odometry, radar, and ultrasonic sensing, while inspection payloads may contain high-resolution cameras, thermal imagers, 3D scanners, acoustic sensors, or other application-specific instruments.

The software must distinguish navigation observations from inspection measurements while maintaining common timestamps and coordinate frames. Accurate synchronization allows every captured measurement to be associated with the robot pose and inspection

Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.