Drone View Operational Capacity & Automation Roadmap

1. Current Operational Capacity

Our team is currently equipped to handle the end-to-end processing of 2–5 drone flights per day using our established manual workflow.

  • The Primary Bottleneck: While data retrieval from DroneDeploy is efficient, the manual alignment of 3D models (ensuring the new model aligns perfectly with previous iterations) is the most time-intensive step.

  • Status: Stable and reliable for current volumes.

2. Defined Internal Process

We utilise a standardised workflow to ensure consistency across projects:

  1. Access: Clients grant 3d@evercam.io editor access within DroneDeploy.

  2. Ingestion: Our team pulls the 3D Model (OBJ), Orthomosaic (GeoTIFF), and Elevation Model (DEM) directly into the Evercam platform.

  3. Ticketing: We have integrated DroneDeploy "Completed Processing" notifications with our 3D Desk ticketing system. This ensures every flight is logged and tracked immediately upon completion.

  • Note: The Inspection Tool is currently excluded from this specific workflow.

3. Scalability & Thresholds

We have identified clear operational limits to ensure quality control:

  • Optimal Range: 1–5 flights/day (Manual).

  • Critical Threshold: Exceeding 5 flights per day will require the transition to semi-automated or fully automated systems to maintain delivery timelines.

4. Automation Roadmap

To move beyond current manual constraints, the Data Development team has begun exploring the DroneDeploy API. Our transition strategy follows a three-tier evolution:

Phase

Methodology

Description

Phase A

Fully Manual

Current State: Manual downloads, manual alignment, manual delivery.

Phase B

Semi-Manual

In Progress: Automated data fetching via API; manual alignment remains.

Phase C

Fully Automated

Future State: Scripted data fetch, auto-alignment, and automated client delivery.

5. Recommendation & Next Steps

The manual process remains our "gold standard" for reliability until automation is validated. The team is currently evaluating API triggers and auto-ingestion feasibility. A formal recommendation on the timeline for Phase B will be provided following the completion of the API assessment.