Development of FMS-P7

Text automatically translated in your browsing language

In accordance with the bid of the Winning Bidder, the Contracting Authority (hereinafter: AK) operating Frequency Management IT System (hereinafter: FMS) further development and modification of its work processes through computer programming within the framework of a business contract. In addition to the requirements of the FMS Phase 6 development, further development needs have emerged, the implementation of which AK aims to achieve. In view of the fact that AK does not have the source code of the relevant IT system, the contractor winning the development must ensure that the right to use the source code is obtained. AK does not wish to obtain the right to use the source code of the modified FMS system that meets the requirements set out in the tender. The documentation refers to XML files in the SpectraExchange XML format with the abbreviation ‘SpEx_XML’. Version running at AK at the time of writing this document is 2.61.0. I. Development needs: 1. On-line ITS station approval: An On-Line authorisation procedure for ITS base stations should be established, modelled on the authorisation process for 72 GHz broadband systems. 2. Replace the diagrams of the frequency assignment and the Permit Modification process. 3. Change the choice of tariff discount. 4. GDPR requirements. 5. Support for the declaration of terminals in maritime service: Both the Autumn 2019 release and P6 have taken steps to enable the RAINWAT ITU reporting of ship stations from the FMS Licensing Database. Unfortunately, the modifications made are not complete and sufficient and have not been integrated into the authorisation process. The Contracting Authority’s intention is to ensure that the Interface ‘.txt’ file required for the ITU notification of floating vehicles (where the SH_MMSI_DSC field is not empty) is available at the end of the authorisation process with the data recorded during the issuance of the radio licence. 6. Monthly reporting of assigned ATIS and MMSI codes: This list is currently unsolved and unsupported. The list should be created on the first day of each month without user intervention, the file name is: ATIS_Brussel_MMM_COUNTRY_Date("yyyy-mm").txt and move it to the snapshot folder. For example: ATIS_Brussel_HNG_2024-07.txt The list shall include the data of each floating vehicle (where SH_CALL or SH_CALL_INLAND is completed – taking into account 2.5.2 above) which is a valid and ‘final’ radio licence at the time the list is drawn up. 7. SpectraExchange XML update: All fields used in Aeronautical and Maritime shall be included in the SpEx_XML export/import reporting and read by Sp+ upon import according to the previous principles (Phase6). In particular, the XSD descriptive file ‘SPECTRAexchange.xsd’ and the text containing the XML description and examples ‘SpectraExchange XML description.doc’ should be updated. In addition, it should be possible to quickly close the Open Interface Export window with the exit button even after a larger set of data (about 6,000 stations) has been displayed, so that the user does not have to wait for a long time. SpectraEMC should be able to read an XML file according to the current SPECTRAexchange.xsd and export it accordingly. 8. Sp+ Update your browser: Due to changes in the database, the Browser tables also need to be updated to make queries and bulk changes. A solution based on a different technology than the Sp+ Browser, but functionally identical, can also be accepted from the supplier. Further detailed requirements are set out in field BT-24 (point II.2.4) and in the Technical Specifications issued as part of the Public Procurement Documents to be issued at the start of the procedure, with the proviso that AK does not provide other public procurement documents for the prior information notice.

72262000 - Software development services