Since FBZ have been introduced, they were available within LARA V2.2 as separated airspace definition, available via conventional CACD files import. As NM B2B communication of AUP/UUP requires a data translation into AIXM5.1, some LARA Users were already considering a simple UUIDs mapping in order to keep an user-interface showing "nominal airspace" (e.g. TSA1), while the actual airspace booking was making reference to its associated FBZ (e.g. TSA1Z).

In awaiting full LARA V3.0 functionalities, a LARA V2.2.8.6 release has been made available to support default FUA Restrictions as this was required to start already now operations with LARA V2.2.

A tests campaign has been realized together with AMC Estonia, in order to validate their operational scenarios for AUPs/UUPs publication via NM B2B.

Consult the full test scenarios used to validate Estonian configuration before their start of NM B2B operational usage via LARA V2.2 Client on the 28th of Octobre 2015.

Contact LARA Team for any further information on the operational use and automated configuration for LARA V2.2 support of FBZ and FUA Restrictions.