Where do I submit my response to the RFP?

    Only responses received via the AusTender platform will be accepted. See the AusTender page for the FIMS RFP here.

    Why do we need a FIMS?

    Airservices has an obligation to ensure the safe integration of drone and other emerging airspace users into Australia's existing conventional aviation ecosystem now and into the future. 

    Given the complexity and large traffic volumes predicted, an automated system that seamlessly facilitates the exchange of information and services will be required.  

    Globally, it is broadly accepted that a FIMS is a core element of the UTM system that will provide this information exchange and support BVLOS operations, access to previously closed airspace, and the management of high density traffic consisting of multiple different air vehicle types.

    What capabilities and services will exist in FIMS?

    Airservices and the Australian Government is continuing to investigate FIMS requirements and functionality needed to ensure lawful operations, to mitigate the range of risks and community impacts, and to ensure efficiency and fair and competitive access to airspace. 

    Two stages of work by Airservices are key to this investigation. The first was through the FIMS Prototype Request for Information (RFI) to seek industry feedback on FIMS requirements and specifications. The second stage is this RFP to develop FIMS prototypes and conduct in-field trials. These stages of work will provide Airservices and the Australian Government with a better understanding of industry capability to deliver a future operational FIMS solution.

    It should be noted that the FIMS concept will continue to mature and evolve through ongoing industry and government stakeholder consultation and collaboration. It does not represent Airservices or the Government’s policy position or pre-suppose the operational FIMS solution. However, all development activities carried out throughout this process have potential to result in commercial outcomes.

    Who is responsible for building a FIMS?

    As Australia’s Air Navigation Service Provider (ANSP), Airservices has a legal obligation under the Air Services Act 1995 to ensure safe, reliable and efficient airspace use for all airspace users in Australian airspace.

    This includes ensuring the safe integration of drones into the existing conventional aviation ecosystem now and into the future.

    In July 2019, the Deputy Prime Minister instructed Airservices Australia to work closely with the Department of Infrastructure, Transport, Regional Development and Communications and CASA to develop and implement a UTM system. 

    What is our approach to UTM?

    As Australia’s Air Navigation Service Provider (ANSP), Airservices is responsible for providing safe, efficient, secure and environmentally responsible services to all airspace users.

    With the ever increasing use of airspace, particularly low level airspace, we need to ensure that new airspace users (such as Unmanned Aircraft Systems (UAS) and Urban Air Mobility (UAM) operators), are safely integrated into Australia’s overall air traffic management system.

    We have established the Integrated Airspace Program with the aim of developing innovative technological solutions and capability to enable us to continue to provide valued airspace management services to our customers and emerging airspace users. Work covered in the Program includes initiatives to enhance drone surveillance at airports, a research and development program with universities and other research organisations, and FIMS development. Further information on the Program and Airservices role in UTM can be found here.

    The Department of Infrastructure, Transport, Regional Development, and Communications is leading a whole-of-government approach to develop a policy relating to emerging aviation technology such as drones and the related infrastructure required to support operations. Australia's proposed UTM architecture, including the role of the FIMS is depicted below.

    Australia's Proposed UTM Architecture