SWARM READY ·
Field Operations · Controlled Procedure

VC-SOP-0313 — Pollinator Drone Swarm Operations

The procedure for safe launch, mission tasking, airspace deconfliction, and recovery of the autonomous Pollinator Drone Swarm across the greenhouse canopy and open arboretum bays.

SOP ID: VC-SOP-0313 Rev: C Effective: 2091-03-30 Next Review: 2093-03-30 Owner: Swarm Marshal (OPS-FLD) Approver: Dr. P. L. Isley, CBO Class: Field Operations · Autonomous Systems
The swarm is never unsupervised. A qualified Swarm Marshal holds live abort authority for the full mission. Autonomy operates within a geofence and a hard return-to-base battery floor; no override may disable either. Operations over GCL-3+ zones require Containment concurrence.

1. Purpose

To define the controlled method for operating the Pollinator Drone Swarm — micro-drones performing precision pollen transfer, canopy inspection, and targeted VOC sampling — such that pollination targets are met without specimen damage, airspace conflict, cross-pollination error, or escape from the controlled volume.

2. Scope

Applies to all swarm sorties within the greenhouse canopy zones and open arboretum bays. Higher-level fleet tasking and deconfliction policy is set in VC-SOP-0131; imaging payload work coordinates with VC-SOP-0124 (Spectral Canopy Array). Sensor-node maintenance follows VC-SOP-0501. Excludes off-site field drones.

3. Definitions

TermDefinition
SortieA single launch-to-recovery mission flown by a defined drone group.
GeofenceThe 3-D boundary beyond which a drone cannot fly; breach triggers immediate motor cut or tether.
DeconflictionSeparation of swarm flight volumes from personnel, fixed rigs, and other drone groups.
RTB FloorThe battery state-of-charge at which a drone autonomously returns to its dock, non-overridable.
Cross-Pollination LockA tasking constraint preventing transfer between incompatible or quarantined cultivars.
Marshal HoldA commanded swarm-wide hover-and-await state issued by the Swarm Marshal.

4. Responsibilities

RoleResponsibility
Swarm Marshal (Owner)Authorizes and supervises every sortie; holds live abort/hold authority; owns this SOP.
Swarm TechnicianPerforms pre-flight inspection, dock servicing, and post-flight diagnostics.
Watch CommanderClears the operating volume of personnel; coordinates with Containment for GCL-3+ zones.
CHLORAPlans routes; enforces geofence, RTB floor, and cross-pollination locks; logs telemetry.
PhytoSense MeshSupplies bloom-readiness and target maps used for tasking.

5. Equipment & Pre-Flight

6. Flight Envelope & Limits

ParameterLimitNote
Max drones per sortie48Per zone deconfliction capacity
Min separation (drone–drone)0.4 mEnforced by CHLORA collision mesh
Min standoff (drone–personnel)2.0 mHard geofence around tracked badges
RTB floor25 % SoCNon-overridable
Max wind / airflow (open bay)3.5 m·s⁻¹Sortie scrubbed above limit
Max continuous sortie22 minBattery-bound; rotate groups

7. Procedure

7.1 Pre-Flight & Volume Clearance

  1. Swarm Technician completes the dock checklist; any drone with a rotor, payload, or charge fault is grounded.
  2. Watch Commander confirms the operating volume is clear of personnel, or that all present carry tracked badges for standoff enforcement.
  3. For GCL-3+ zones, Containment concurrence is recorded before launch.
  4. Marshal verifies geofence, RTB floor, and cross-pollination locks on the CHLORA console.

7.2 Mission Tasking

  1. CHLORA generates the pollination route from the PhytoSense bloom-readiness map; Marshal reviews and approves the target set.
  2. Confirm cross-pollination locks exclude any incompatible or quarantined cultivar pairing. A lock conflict blocks tasking.
  3. Assign drone groups to deconflicted sub-volumes; verify min-separation mesh is armed.

7.3 Launch & In-Flight Supervision

  1. Launch in waves no larger than 12 drones; confirm each wave reaches station before the next launches.
  2. Marshal monitors live telemetry: position, SoC, payload state, and separation health.
  3. Issue a Marshal Hold for any anomaly — personnel entry, separation alert, or specimen-damage report — before resuming.
  4. Pollination accuracy is sampled live; a target with repeated transfer failure is flagged for manual follow-up.

7.4 Recovery & Post-Flight

  1. Drones return at the RTB floor or on mission completion; confirm full count docked against launch count.
  2. Any drone unaccounted for triggers a search and a no-launch hold until recovered.
  3. Technician runs post-flight diagnostics; payload residue is decontaminated before next sortie.
  4. CHLORA archives the sortie record and pollination coverage map to metrics.

7.5 Quality Checkpoints

8. Alarm Responses

AlarmIndicationImmediate Action
Separation AlertTwo drones within 0.4 mCHLORA auto-separates; Marshal Hold if it recurs; ground the affected group.
Personnel IntrusionBadge enters operating volumeSwarm holds and retreats to 2.0 m standoff; resume only when clear.
Geofence BreachDrone exits the 3-D boundaryImmediate motor cut / tether recovery; full sortie hold; investigate before relaunch.
Lost CommsMDF link to drone droppedDrone executes autonomous RTB; if non-responsive, declare lost-drone search per 7.4.
Specimen DamageContact/impact reported on a targetMarshal Hold; ground the group; log to monitoring and notify Cultivar Lead.

9. Records

10. References

11. Revision History

RevDateAuthorSummary
A2088-09-15Swarm MarshalInitial issue; geofence and RTB floor established.
B2090-07-08Swarm MarshalCross-pollination locks and personnel standoff added.
C2091-03-30Swarm MarshalWave-launch sequencing and lost-drone no-launch hold formalized. CBO approval.