Why use this template
Under the Irish BIM Mandate, ISO 19650-2 information exchanges are mandatory on all public works above €20M as of June 2025, and on every public project from end of 2027. When you commission a drone survey as part of that workflow, the survey data needs to slot into the project Common Data Environment (CDE) with the right level of detail, naming convention and exchange container.
This template gives you a one-page information exchange specification you can drop into an Employer’s Information Requirements (EIR) document or a BIM Execution Plan (BEP), plus a LOD matrix covering every deliverable a drone survey typically produces.
Section 1. Information exchange metadata
- Project reference: [PROJECT-REF]
- Information exchange ID: [IE-01, IE-02, …]
- Delivery team: [UAS operator name]
- Task information delivery plan (TIDP) reference: [TIDP-REF]
- Master information delivery plan (MIDP) reference: [MIDP-REF]
- Exchange format: IFC 4, LAS/LAZ 1.4, DWG 2018, GeoTIFF, PDF/A-1b
- Coordinate reference system: Irish Transverse Mercator (EPSG:2157)
- Vertical datum: Malin Head (OSGM15 geoid model)
- Naming convention: ISO 19650-2 Annex A compliant (Project-Originator-System-Zone-Level-Type-Role-Classification-Number)
Section 2. LOD / LOIN matrix for UAS deliverables
| Deliverable | LOD | Geometric accuracy | Alphanumeric data |
|---|---|---|---|
| Orthomosaic (GSD ≤ 2 cm) | LOD 200 | 15-25 mm H | Capture date, GSD, coordinate system |
| Digital Terrain Model (DTM) | LOD 300 | 20-35 mm V | Filtering method, point density, GCP residuals |
| Digital Surface Model (DSM) | LOD 300 | 20-35 mm V | Processing software, version, date |
| LAS/LAZ point cloud | LOD 300 | 25-40 mm absolute | Classification scheme, point density, sensor metadata |
| As-built feature survey (DWG) | LOD 400 | 15-25 mm H, 20-35 mm V | Layer standard, attribute schema, coordinate list |
| Volumetric calculation | LOD 300 | ±1.5% (with 6+ GCPs) | Base surface, calculation method, confidence interval |
| Residuals / QA report | – | PDF/A-1b | Check point residuals, RMSE, date, signed by CRP |
Section 3. Naming convention examples
- DSI-SURV-XX-ZZ-M3-S-UAS-EX-001 (federated point cloud, existing conditions, IE-01)
- DSI-SURV-XX-ZZ-M2-D-UAS-OR-001 (orthomosaic, federated level)
- DSI-SURV-XX-ZZ-DR-A-UAS-TR-001 (residuals report, task delivery role)
Section 4. Exchange requirements checklist
- Information delivery matches the defined LOIN (Level of Information Need)
- All files submitted via the project CDE in the WIP or SHARED container as appropriate
- Revision code updated at each exchange (P01, P02, C01, A1)
- Suitability code matches ISO 19650-2 Annex A (S1, S2, S3, S4, A1, A2, B1, etc.)
- All files named in compliance with the project information protocol
- Coordinate and vertical datum stated on every drawing and model file
- Metadata container (XML or JSON) accompanies every binary deliverable
- Residuals and QA report signed by the Chief Remote Pilot
Need this customised for a specific project? If you are preparing a tender, condition survey, or project handover and need this tailored to your site, asset type, or regulatory context, we can usually turn a custom version around in a day. Talk to our team or browse the full Assets Hub for more templates.