Virtual Perimeter

A Virtual Perimeter is defined by geographic coordinates (e.g., GPS, RFID beacons) or relative positions within a digital map, not by physical walls or tape. This allows for:

• Dynamic reconfiguration: Boundaries can be changed in software without moving physical assets.
• Layered enforcement: Multiple perimeters (e.g., warning, soft-stop, hard-stop) can be superimposed on the same physical area.
• Precision: Boundaries can conform to complex, irregular shapes that would be impractical with physical barriers.

The primary function is to regulate which agents (AMRs, manual vehicles, personnel) can enter or exit. This is governed by:

• Authorization Policies: Rules based on agent identity, role (e.g., forklift, pedestrian robot), or attributes (e.g., current task, load type).
• Policy Decision/Enforcement Points (PDP/PEP): The system component that evaluates requests (PDP) and the component that blocks or permits movement (PEP).
• Temporal Constraints: Access may be granted only during specific time windows or based on dynamic scheduling.

Virtual Perimeters are stateful boundaries that generate events. Key triggers include:

• Entry/Exit Events: Logging when an authorized or unauthorized agent crosses the boundary.
• Occupancy Events: Triggering alerts if the number of agents inside exceeds a zone capacity limit.
• Dwell Time Alerts: Flagging an agent that remains stationary inside a zone beyond a configured threshold, which may indicate a fault. These events feed into audit logs and can trigger automated workflows, such as notifying a supervisor or initiating a safety protocol.

A perimeter is not isolated; its effectiveness depends on integration with the broader fleet orchestration system.

• Real-Time Localization: Relies on continuous, accurate position data from agents (e.g., via UWB, LiDAR SLAM, GPS).
• Dynamic Context: Access decisions can incorporate real-time data like agent battery level, task priority, or zone congestion.
• Orchestration Feedback: Violations or access grants directly influence the central planner, which may reroute other agents or reallocate tasks.

Virtual Perimeters implement critical safety logic for heterogeneous environments.

• Graceful Degradation: Protocols for loss of positioning signal, often defaulting to a safe stop.
• Emergency Overrides: Protocols like Emergency Zone Clearance to instantly vacate a zone.
• Violation Response: Defines hierarchical responses to unauthorized entry, from audit logging and warnings to immediate software stop commands.
• Mutual Exclusion: Can be configured as a Mutual Exclusion Zone where only one agent is allowed at a time to prevent collisions.

Perimeters are managed as digital assets within the orchestration platform.

• Declarative Configuration: Often implemented as Zone Configuration as Code, where boundaries and policies are defined in version-controlled files (e.g., YAML, JSON).
• Visual Management: Operators typically define and monitor perimeters through a graphical map interface.
• Lifecycle States: Perimeters have states (e.g., ACTIVE, INACTIVE, QUARANTINE) managed by a Zone State Machine.
• Auditability: All configuration changes, access decisions, and violations are logged for compliance and analysis.

Virtual perimeters create safety-critical no-go areas around hazardous machinery, maintenance personnel, or unstable inventory. These zones enforce mutual exclusion, ensuring autonomous mobile robots (AMRs) and manual vehicles like forklifts cannot enter while a hazard is present.

• Dynamic Activation: Zones can be activated based on real-time sensor data (e.g., a door opening, a person detected).
• Protocol Integration: Triggers emergency zone clearance commands or reroutes agents via priority-based routing.
• Example: A perimeter around a charging station prevents traffic while a robot is plugged in, managed by a zone state machine.

Software-defined boundaries secure areas containing sensitive, high-cost, or regulated goods (e.g., pharmaceuticals, electronics). Access is governed by strict spatial authorization policies and role-based access control (RBAC).

• Audit Trail: All access attempts are recorded by zone audit logging systems for compliance.
• Temporal Controls: Access may be restricted to specific temporal access windows or authorized personnel shifts.
• Integration: Often works in tandem with physical security systems, with the virtual perimeter providing the logical access layer.

Perimeters act as virtual staging areas or buffers to sequence the flow of agents through a process, preventing congestion. This is a key tool for spatial-temporal scheduling and load balancing.

• Capacity Management: A zone capacity limit controls how many agents can wait at a packing station queue.
• State Dependencies: A zone's state (e.g., PACKING_STATION_READY) can be a precondition for an agent to leave a buffer zone, coordinated by the zone orchestration engine.
• Example: Robots wait in a virtual holding zone until a CNC machine's cycle completes, signaled via the zone handshake protocol.

In flexible warehouses, perimeters can be dynamically allocated to create one-way lanes, temporary crosswalks, or to isolate congested aisles. This enables real-time zone deconfliction.

• Adaptive Routing: The orchestration middleware uses zone states to inform real-time replanning engines.
• Priority Handling: Implements zone priority override to create clear paths for high-priority agents or emergency responders.
• Use Case: During peak picking, a main aisle is converted to a southbound-only lane via a virtual perimeter, with northbound traffic rerouted.

Virtual perimeters enforce operational rules defined by external regulations or internal standards. This is the classic geofencing application, triggering alerts or limiting speeds.

• Environmental Controls: Restricting diesel vehicles to certain areas to maintain air quality standards.
• Speed Governance: Automatically reducing agent speed within perimeters around pedestrian zones.
• Proof of Compliance: Boundary violation detection logs provide auditable records for regulatory requirements.

Perimeters logically partition a workspace to isolate different fleet types, software versions, or for safe testing of new agents. This supports heterogeneous fleet orchestration.

• Development Sandboxes: New navigation software is tested within a confined virtual area before full deployment.
• Role Segregation: Separates areas for heavy payload AMRs from smaller collaborative robots using attribute-based access control (ABAC).
• Quarantine Functions: A zone quarantine protocol can isolate an agent behaving erratically for diagnosis.

Role-Based Access Control (RBAC) is an authorization model that grants access to zones based on an agent's assigned role, not its individual identity. In a warehouse, roles like Forklift, AMR, or Maintenance Technician have predefined permissions for different Virtual Perimeters.

• Core Principle: Permissions are attached to roles, not users.
• Administrative Benefit: Simplifies policy management; adding a new forklift automatically grants it the 'Forklift' zone permissions.
• Contrast with ABAC: RBAC is static (role-based), while Attribute-Based Access Control (ABAC) is dynamic (condition-based).

Attribute-Based Access Control (ABAC) is a dynamic authorization model that evaluates a set of attributes against policies to grant or deny zone access. Access to a Virtual Perimeter can depend on attributes like agent_type=AMR, battery_level>20%, task_priority=HIGH, or current_load=EMPTY.

• Policy Structure: Uses IF-THEN rules (e.g., IF agent_type == 'Forklift' AND has_certification == TRUE THEN ALLOW entry).
• Flexibility: Enables complex, real-time access decisions based on the current operational context.
• Use Case: Allowing only high-priority, charged AMRs into a high-throughput packing zone.

A Mutual Exclusion Zone (MUTEX Zone) is a specific type of Virtual Perimeter where a concurrency control policy ensures only one agent is permitted inside at any time. This is critical for safety in areas like narrow aisles, charging docks, or maintenance bays.

• Concurrency Control: Implements a software lock on the geographic area.
• Prevents: Collisions, deadlock, and interference between agents.
• Protocol: Agents must request and receive a token before entry, releasing it upon exit.

These are the core architectural components that enforce Virtual Perimeter rules.

• Policy Decision Point (PDP): The 'brain.' This component evaluates an access request (e.g., 'Agent 123 requests entry to Zone A') against all current policies (RBAC, ABAC) and renders an Allow or Deny decision.
• Policy Enforcement Point (PEP): The 'gate.' This component intercepts the agent's request, queries the PDP, and enforces its decision by physically or logically granting or blocking access.

This separation of concerns is a standard pattern in secure access control systems.

A Zone State Machine is a computational model that defines the discrete operational states of a Virtual Perimeter and the events that cause transitions between them. This brings deterministic behavior to dynamic zones.

Common States:

• AVAILABLE: Open for authorized entry.
• OCCUPIED: An agent is inside.
• RESERVED: Booked for a future task.
• QUARANTINE/LOCKED: Closed due to hazard or failure.
• MAINTENANCE: Under human service.

Transition Events: AGENT_ENTRY, AGENT_EXIT, EMERGENCY_STOP, SCHEDULED_LOCK. The state machine ensures consistent system reactions to these events.