REFERENCE / TERMINOLOGY
A shared vocabulary for
perimeter-sensing discussion.
This reference explains high-level terms used across New Ark public material. Each definition describes an information or governance concept; it is not an operating instruction, a product specification, or a promise of site outcome.
Browse definitionsUSE BOUNDARY
Definitions explain concepts; they do not prescribe activity.
These entries are not operating instructions and do not provide target selection, sensor positioning, thresholds, algorithms, response sequences, signal control, interference, navigation manipulation, or performance claims. Site conditions, permissions, engineering review, accountable personnel, and written validation remain decisive.
13 definitions
01 / ACOUSTIC INFORMATION
Sound-related information in context
High-level terms for passive acoustic inputs and their interpretation in a changing industrial environment.
Passive acoustic information
Sound-related input without RF transmission to acquire it.
Sound-related observations collected through microphones or acoustic devices. Their interpretation depends on local noise, weather, terrain, structures, installation context, data quality, and authorised review.
Microphone array
A coordinated group of microphones used to collect sound-related information.
An arrangement of microphones that can provide a project with a structured acoustic input. It does not by itself identify an aircraft, establish a location, or create an operational decision.
Acoustic signature
A project term for observable sound-related characteristics.
A description of sound-related characteristics that may be reviewed against project-defined records or context. Public material does not disclose thresholds, model internals, or classification methods.
Fibre-optic UAV context
A context in which some usual radio-linked observations may differ.
A project-level description for aircraft configurations using a physical fibre connection. Information availability varies by equipment, environment, permissions, and site evidence; the term does not establish a universal sensing gap or outcome.
02 / COMPLEMENTARY INPUTS
Different evidence, different conditions
Terms for information sources that may be compared only within authorised, site-defined review conditions.
RF reception
Authorised receipt and review of radio-frequency information.
A possible information input in applicable contexts. Its observability, legality, interfaces, and treatment are project-defined and must not be inferred from a public explanation.
EO/IR observation
Visible-light and infrared observation as a separate evidence type.
Electro-optical and infrared observations may offer a different perspective, subject to lighting, visibility, line of sight, environment, permissions, and the project’s review process.
Multi-sensor corroboration
Comparing authorised information sources before assessment.
A governed review practice in which different evidence types are compared alongside site context and uncertainty. It does not guarantee identification, reduce false alarms to a fixed level, or replace accountable personnel.
C2 information context
A project term for governed coordination and audit context across authorised systems.
A high-level reference to information coordination, review roles, and audit context that may be relevant to a project. Interfaces, authority, data treatment, and permitted scope remain project-defined; the term does not prescribe controls, signalling, or response methods.
03 / GOVERNANCE & VALIDATION
Accountability before conclusions
Terms that describe safe siting, human authority, and written project evidence without prescribing activity.
Safe-offset deployment
Reviewing information inputs from external safe buffers rather than core hazard areas.
An engineering and site-governance principle that begins with hazardous-area classification, external safety buffers, assessable mounting zones, certification, interfaces, and operator authority. It is not a placement recipe.
Accountable human review
Authorised personnel assess evidence, uncertainty, and site rules.
A defined role for people who review information within permissions, safety constraints, governance requirements, and documented project responsibilities. Sensors and software do not substitute for this role.
Written validation
An agreed, site-specific record of questions, responsibilities, and evidence.
A documented project process that sets the review scope, acceptance questions, evidence treatment, roles, and boundaries. Public pages cannot replace field engineering, authority review, or written agreement.
Protected services
Essential services and activities whose continuity is considered in a project review.
A project-governance term for services, operations, people, or dependencies that require explicit consideration before information is collected, interpreted, shared, or relied on. It does not promise uninterrupted operation or prescribe an intervention.
Privacy boundary
The authorised limits on personal or sensitive information in a project context.
A documented boundary covering lawful purpose, minimisation, access, retention, and review of information that could affect people or sensitive operations. It is a governance control, not a data-collection instruction.