Digitizing an airport process begins with defining the necessary decisions and data. An inspection, maintenance, or risk management application must maintain traceability and offer a controlled way of working when data or communications become unavailable.
What is defined before choosing the technology?
Describe the users, tasks, and the current workflow. For each stage, note the input data, the person responsible, the validation, and the outcome. Identify field work, simultaneous access, offline operations, and shift handovers.
Formulate verifiable requirements: who can modify an observation, who approves it, what happens when a deadline is missed, and what history is kept. Separate the mandatory requirements for the first version from the functionalities that can be introduced later.
How are records and integration designed?
Establish stable identifiers for assets, locations, and documents. Georeferenced data must have a coordinate system and an explicit source. Defects, interventions, and checks must be linked to the same asset without losing the history.
For sensor integration, define the measured quantity, unit, calibration, frequency, timestamp, and validity status. An old value must be distinguished from a current one, and the lack of communication must not be displayed as normal operation.
What must be established for access and continuity?
Define roles, minimum rights, action logging, and approval for sensitive changes. Plan data retention, backups, restoration, and export in a usable format. Test recovery, not just the existence of a backup.
Depending on the organization and the impact on safety, verify the applicability of Part-IS, including Regulation (EU) 2022/1645 for aerodrome operators and targeted AMS providers. An installed application does not equate to demonstrating the compliance of the entire management system.
How is the solution verified before use?
Link each requirement to a test case, an expected result, and evidence. Include incorrect data, network interruptions, unauthorized access, synchronization, and recovery. For reports and calculations, use known datasets and independent verification.
Differentiate support functions from those that can influence an operational decision. The introduction of a system with an impact on operations must be correlated with change management, local procedures, and user training. A prototype should not automatically be treated as a validated system for operation.
What must be included in the delivery and proposal?
Establish documentation, configuration, data import, training, support, and acceptance criteria. Specify ownership of the code, licenses, and maintenance responsibilities. The beneficiary must know how to recover their data and how to request a change.
For proposals, transmit the process, users, sample forms, data sources, and available interfaces. Add field conditions and the operational importance of the system to correctly size development and verification.
Also consult the technical chapter in the guide
Discuss your project with the Sky Meridian team
Hardware and software solution development