Trust & security
Measured reality. Controlled access. Accountable delivery.
Airscope combines field planning, quality-controlled asset digitisation and controlled browser access to help industrial teams use measured site context with confidence.
Trust overview
Trust is designed across the field-to-model workflow.
01
Safe field delivery
Plan access, people, equipment and site controls around the asset and operating environment.
02
Measured outputs
Define the deliverable, capture approach, reference method and verification steps before release.
03
Controlled access
Provide approved users with browser-based access under documented platform and project controls.
04
Accountable delivery
Maintain named owners, documented systems and current evidence for project and platform assurance.
Information security
Security controls for operational asset information.
Control descriptions are confirmed against the relevant project, platform configuration and current evidence rather than presented as universal promises.
Penetration testing
Airscope’s platform and security environment have undergone penetration testing.
Further information can be provided through an appropriate procurement or security review.
User access
Permissions and user lifecycle arrangements are defined for the applicable project and deployment.
Authentication
Available authentication options and client requirements are confirmed during scoping.
Hosting and residency
Hosting location and data-residency requirements are established for the proposed environment.
Data protection
Current encryption, transfer and handling controls can be reviewed with authorised stakeholders.
Monitoring and response
Applicable logging, monitoring and incident-response arrangements are documented and reviewed.
Recovery and retention
Backup, recovery, retention and deletion requirements are agreed for the project context.
Vulnerability management
Testing and remediation evidence is shared at the appropriate disclosure level.
Project offboarding
Access changes, handover and closure requirements are addressed through controlled project processes.
Measured-output assurance
The deliverable is defined before the capture begins.
Airscope aligns the capture plan and outputs to the decisions the asset team needs to make. Processing and quality checks are recorded against the agreed scope before release.
01
Define use and detail
Start with the decision, users and required output.
02
Plan capture and reference
Select methods and controls for the operating context.
03
Capture field reality
Collect the agreed spatial and visual information.
04
Process and check
Verify outputs against documented scope and criteria.
05
Release controlled outputs
Publish or hand over only the agreed deliverables.
Accuracy, point spacing, resolution and photogrammetric ground sampling distance describe different measures. Project claims are stated against their applicable output, method and acceptance criteria.
Field safety
Plan the work before people and equipment mobilise.
Capture planning works with the site’s controls. Digital access supports preparation and review; it does not replace required physical inspections or operating safeguards.
Site interfaces
Align activity with permits, access requirements and client operating controls.
Operating environment
Plan for remote, offshore, work-at-height and live-plant conditions where applicable.
People and equipment
Select competent personnel, capture methods and equipment for the approved scope.
Change and learning
Use documented hazard, incident and change-management processes throughout delivery.
Management systems
Documented systems. Current evidence. Precise claims.
Assurance is presented at the scope supported by current evidence, the certified legal entity and the project context.
Quality management
Environmental management
Health and safety management
Information security management
Current management-system evidence can be requested for procurement review, subject to the relevant entity, scope and disclosure requirements.
Data and delivery questions
What your team can establish before a project starts.
Where will project data be hosted?
Hosting and residency are confirmed during project scoping based on the proposed service, client requirements, data classification and deployment.
Who can access the digital twin?
Access is provided to approved users under the permissions and project controls agreed for the deployment.
How are users added, changed and removed?
User lifecycle arrangements, responsible roles and response processes are confirmed in the project’s access model.
What data formats and handover options are available?
Outputs and handover formats are agreed against the intended downstream use, source data, project scope and client systems.
How are retention, backup and deletion handled?
Applicable retention, recovery and deletion requirements are documented for the relevant project and hosting arrangement.
How does Airscope work with client security and site requirements?
Security, procurement and site-control requirements are identified during scoping and incorporated into the agreed delivery approach.
What assurance material is available during procurement?
Current policies, summaries, certificates and testing evidence appropriate to the review can be supplied subject to approval, relevance and confidentiality requirements.
Procurement and IT review
Need evidence for your evaluation?
Tell us which controls, certifications or delivery requirements your team needs to assess. Airscope will provide current material that is appropriate to share, subject to confidentiality requirements.