Current status:
VPN connection is established and traffic is visible.. David González will provide details on the intermittent disconnections, which are believed to originate from the VPN rather than the antenna or the R5 system itself.
Look of the button trail speed vector fixed – minor issue found during deployment on a separate web page for you to review. Next update will address it fully.
- DataBeacon → to discuss internally about recording the data from Gloucester Francisco Rodríguez
Next steps:
Action | Comments | Estimated date | CAA involvement | ||
|---|---|---|---|---|---|
1 | Pre-FAT cloud verification | EGBJ to check the cloud build for any software changes.
| 2025.10.03 | ||
2 | VPN stability | As of 2025.09.19, VPN is not stable. We have a similar installation in other airports w/o problems. We will be collecting metrics on this in the next days. | 2025.10.03 | ||
3 | Antenna configuration | One antenna needs a re-configuration, in contact with manufacturer, but the antenna needs connected. We need Roger to work on this.
| 2025.10.03 | ||
4 | FAT | DB. Full functional and performance tests of the local build. Produce a signed FAT report. EGBJ to inform CAA. | 2025.10.10 Friday | Information | |
5 | Shipment | DB to ship equipment. | 2025.10.13 | N | |
6 | Regulatory Alignment | DB to issue CAP670 compliance matrix, first version of manuals, and FAT report. | 2025.10.13 | Not at this stage | |
7 | Local Installation | DB to support to the onprem installation. | not before 2025.11.10 | ||
8 | SAT | DB to deliver SAT model. | not before 2025.11.10 | Normally Y | |
9 | Safety Case & Final Approval | EGBJ to produce a document explaining why it is safe to use Romeo5. It should include Compliance Matrix, FAT, SAT, risk matrix, and trials results. DB to support Safety Case documentation. | Coordinate duration of trial period and documentation based on CAP670. |