ARC: The Airsuv Reference Capture System
Every article published in these Insights has described the same principle from a different angle.
Inspection data is only valuable when it is structured, repeatable, and complete. Repeatability is what separates a flight from an inspection system. Compliance begins before take-off.
None of those articles named the system behind them. This one does.
Why I Built ARC
When I started operating commercially in drone inspection, the most consistent problem I encountered was not technical. The aircraft worked. The sensors worked. The problem was that two operators flying the same asset would produce completely different datasets. There was no shared standard for what constituted complete coverage. No defined viewpoints. No documented basis for what had been captured and what had not.
Engineering teams and asset managers were receiving datasets they had to interrogate before they could trust. Was the soffit fully covered? Were all antenna faces captured? Was the thermal pass flown at the right altitude and spacing to be IEC 62446-3 compliant? Nobody could answer those questions from the data alone. The uncertainty was baked in.
That is not a technical problem. That is a methodology problem.
I built ARC — the Airsuv Reference Capture system — to fix it. Not to impress clients with a named system, but because a named, documented, binary pass/fail standard is the only way to guarantee that the dataset leaving site is complete. Every time.
What ARC Is
ARC is a five-layer, binary pass/fail capture framework. Every Airsuv inspection mission — regardless of sector, asset type, or scale — is structured to all five layers. All five must be completed before the dataset leaves site. No layer may be skipped, abbreviated, or substituted.
Binary pass/fail means exactly that. There is no partial credit. No annotation that says 'mostly complete'. The layer either meets the defined parameters or the mission is not finished.
ARC-1 — Asset Overview — Full asset geometry, orientation, and environmental context established from a minimum of four directional angles.
ARC-2 — Surface Coverage — 100% surface coverage at consistent distance, angle, and overlap. The primary data layer. No gaps. No exceptions.
ARC-3 — Structural Detail — All structural and mechanical features captured with front, side, and context views. Every feature that requires explanation in the record is documented.
ARC-4 — Close-Range Capture — Close-range detail of all points of interest identified during ARC-2 and ARC-3. Drone stationary at point of capture.
ARC-5 — Conditions Record — Site access, ground conditions, and environmental context. The conditions log required for IEC 62446-3 reporting and RAMS documentation.
What ARC Means for Standards Compliance
ARC is how Airsuv meets the requirements of applicable industry standards — not by reference but by structure.
IEC 62446-3 requires specific capture conditions for solar thermal inspection: irradiance above 600 W/m², defined flight parameters, and a conditions log. ARC-2 delivers the compliant flight path and thermal replication. ARC-5 delivers the conditions log. The standard defines the requirement. ARC defines how it is met.
Historic England HEAG317 requires systematic photographic coverage of heritage fabric, non-contact throughout, and a documented record of what was captured. ARC-1 through ARC-3 deliver that record. The non-contact requirement is not a constraint on ARC — it is built into the system.
RF-aware protocol for cell tower operations requires defined standoff distances from active antenna faces and a structured capture of all antenna sectors, RRU/RRH units, and connection hardware. ARC-3 defines exactly that capture. The 15-metre standoff is standard operating procedure, not a site-by-site decision.
What ARC Guarantees for the Client
When a dataset leaves an Airsuv mission site, the client's engineering team can rely on three things.
First, coverage is complete. ARC-2 is 100% surface coverage with no gaps and no exceptions. If a section of the asset was not captured to standard, the mission is not complete. The data does not leave site.
Second, the dataset is immediately usable. ARC organises data by structure element, elevation, span, or layer — consistent with the client's workflow. No additional processing is required before the engineering team can begin their work.
Third, the capture is repeatable. ARC defines the parameters — altitude, distance, overlap, viewpoints — that allow the same asset to be captured the same way on every subsequent mission. Condition changes can be compared across time. Degradation can be measured. Maintenance planning can be justified with evidence.
ARC Across All Six Sectors
ARC applies to every sector Airsuv operates in. The five layers remain constant. The parameters within each layer — altitude, distance, overlap, capture sequence — are adjusted to the asset type and applicable standard.
Infrastructure: soffits, abutment faces, and structural joints captured to ARC-2 grid at 2.5–3.5m. Powerline: span-by-span conductor and insulator coverage. Solar: IEC 62446-3 aligned grid with thermal replication. Cell tower: height-band systematic coverage with per-sector antenna face capture. Heritage: HEAG317-aligned elevation coverage, non-contact. Commercial: flat roof thermal replication, RGB pass followed immediately by thermal pass on identical path.
Different assets. Same standard. Every time.
ARC is the reason Airsuv's data leaves site complete or does not leave site at all.
That is not a marketing claim. It is the operating standard that every ARC-structured mission is built on.
Full sector detail — including ARC application per sector and standards alignment — is on the Services page at airsuv.uk/services.
