A regional operations team receives a stockpile report from one mine and an earthworks model from a construction site. Both came from drone surveys. One refers to Friday's capture; the other was processed on Friday from images collected earlier. The volume figures use different reference surfaces. Before making a decision, the team has to find out what each delivery actually represents.
For heavy industry, scaling drone use means making site information understandable beyond the crew that collected it. A delivery standard should describe the intended use, evidence of quality and review responsibility while allowing local teams to choose suitable methods. The following approach focuses on consistency across mining, construction and industrial facilities.
Build the standard around recurring decisions
Start with the questions that several sites need to answer. What material is available? Which earthworks area has been completed? What visible constraints need investigation before the next activity starts? Assign an information recipient to each question and agree when the answer will be useful.
Create a small catalogue of deliverables. Progress imagery, an orthomosaic for planning and a survey used for contractual quantity assessment require different evidence. For each item, define coverage, delivery timing, purpose and acceptance criteria. Leave room for another survey method when drone imagery cannot meet the requirement.
A mine stockpile volume, for example, depends on the material boundary and the reference surface selected for the calculation. A construction cut-and-fill comparison also depends on the applicable design revision. A common unit such as cubic metres does not make these quantities interchangeable. The definition of the measurement must travel with the number.
Specify the information that travels with every delivery
Agree a minimum delivery record that internal teams and survey contractors can both supply. It should help someone outside the originating site understand the result without reconstructing the work from emails.
- Site and survey area identifiers, with the intended use of the information.
- Capture date and time, distinguished from processing and review dates.
- Coordinate system, vertical reference and measurement units.
- Delivered products, achieved coverage and gaps or limitations.
- Verification method, check results and uses accepted by the reviewer.
- The producer, the reviewer and the version released for consultation.
Connect that record to the relevant project and files. Define naming conventions, including how a corrected deliverable replaces an earlier version while retaining the history needed for review. A file named “latest” is a poor substitute for a dated release and a stated purpose.
The FHWA's 2023 brief on drone data management examines storage, information sharing and governance for US transportation agencies. It provides useful context for managing growing survey collections. Its institutional and regulatory setting should not be treated as a universal requirement for industrial operators.
Agree acceptance criteria before standardising equipment
Using the same aircraft and camera at every site will not produce identical survey performance. Relief, vegetation, dust, water, occlusion and poorly textured surfaces affect what can be captured and reconstructed. Start with the evidence needed for the intended decision, then establish a suitable acquisition and verification approach.
Image resolution, point-cloud density and positional accuracy describe different aspects of a dataset. The USGS imagery calibration guide published in 2023 explains that ground control and tie-point quality contribute to accuracy independently of ground sample distance. Detailed-looking imagery is not sufficient evidence that a survey meets its acceptance criteria.
A competent technical reviewer should determine whether the delivered data support the agreed use. A dataset may be useful as visual context while remaining unsuitable for quantity assessment. Make that distinction visible to the recipient, particularly when information moves from a site team to a regional or corporate audience.
Give central and local teams clear responsibilities
A central owner can maintain the deliverable catalogue, the delivery record and common performance measures. Local teams understand access, capture windows, industrial activity and restrictions around the survey area. The technical reviewer evaluates fitness for use. The person making the operational decision needs the result and its limitations.
These roles may belong to separate departments or contractors. Name an owner for each handover and establish how questions reach the data producer. Access to a shared map does not by itself grant authority to approve a quantity, change a design or release a work area.
Flight permissions, privacy requirements and industrial access procedures need site-specific checks. A corporate procedure should require those checks and accommodate local conditions. Approval for a flight at one facility does not establish permission to operate at another site or in another jurisdiction.
Keep specialist assessments separate from mapping
Maps and surface models help document visible conditions and provide spatial context. They do not determine a structure's internal integrity. Thermal inspections, geotechnical assessments and maintenance decisions require an appropriate technical scope, instruments and qualified people. Define these as separate tasks whenever the question extends beyond the mapped surface.
Frequency also needs careful wording. A survey records conditions during capture. Comparing successive surveys supports review of changes between those dates; it does not provide continuous surveillance. Describe the observation interval and any coverage limitations so recipients do not infer that the site has been observed since the last capture.
Prove the standard at two contrasting sites
Select one recurring deliverable and two sites with different conditions. Ask each team to prepare its delivery record, complete the review and hand the result to a colleague who did not attend the survey. Can that person identify the capture date, reference system and accepted use without contacting the pilot?
Track first-review acceptance, missing context, requests for additional capture and elapsed time until information reaches its intended recipient. Record why exceptions occur. Flight counts alone are a weak comparison: one site may require fewer flights while producing information that answers its operational question more reliably.
Use the trial to revise the standard and assign responsibility for maintaining it. A new supplier, aircraft or processing method should demonstrate that it can meet the expected deliverable before the approach is extended to other facilities. Keep the evidence from that evaluation with the approved procedure.
Put the platform inside the delivery process
The Maply platform supports viewing maps and models, taking measurements and comparing surveys from different dates. These tools can help teams consult the same site information. Acceptance criteria, technical responsibility and the authority to act remain organisational decisions.
To assess a deployment across several sites, contact the Maply team with a representative delivery, its review requirements and the people who need to use it. A demonstration can then examine how the platform fits the information standard your operations need to maintain.
