Development of FMS-P7 Text automatically translated in your browsing language Automatically translated

In accordance with the bid submitted by the successful tenderer, the contracting authority (hereinafter: AK) operating Frequency Management Information System (hereinafter: FMS) further development and modification of its workflows through computer programming within the framework of a contract for works. In addition to the needs of the FMS phase 6 development, further development needs have emerged, which AK aims to implement. In view of the fact that AK does not have the source code of the IT system in question, the contractor receiving the development must arrange for the acquisition of the right to use the source code. 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 announcement. The documentation refers to XML files conforming to the SpectraExchange XML format with the abbreviation ‘SpEx_XML’. The version that works with AK at the time of writing this documentation is 2.61.0. I. Development needs: 1. On-line ITS station authorization: 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 Permission Modification process. 3. Change the selection of the fee discount. 4. GDPR requirements. 5. Supporting the reporting of ship stations in maritime service: Both the 2019 autumn release and P6 have taken steps to enable the RAINWAT agreed ITU notification of ship stations from the FMS licensing database. Unfortunately, the changes made are not complete and sufficient and have not been integrated into the authorisation process. The Contracting Authority endeavours 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 registered during the issuance of the radio licence. 6. Monthly reporting of designated ATIS and MMSI codes: Currently, the creation of this list is not solved, not supported. The list should be created on the first day of each month without user intervention, with the file name: ATIS_Brussel_MMM_COUNTRY_Date("yyy-mm").txt and put it in the snapshot folder. For example: ATIS_Brussel_HNG_2024-07.txt The list shall include the data of each floating vessel (where the fields SH_CALL or SH_CALL_INLAND are filled in, taking into account 2.5.2 above), which is valid at the time the list is drawn up and has a ‘final’ radio licence. 7. SpectraExchange XML update: All fields used in Aeronautical and Maritime must be included in SpEx_XML Export/Import reporting and read by Sp+ at import according to the previous Principles (Phase6). This includes updating the XSD descriptor file ‘SPECTRAexchange.xsd’ and the XML description and examples text ‘SpectraExchange XML description.doc’. In addition, it should be possible to close the Open Interface Export window quickly with the exit button even after a larger data set (approximately 6000 hosts) has been published, 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+ Browser Update: Due to the resulting database changes, the Browser tables also need to be updated to perform queries and bulk changes. A solution based on technology other than Sp+ Browser, but functionally identical, is also acceptable 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 any other public procurement documents for the prior information notice. Text automatically translated in your browsing language Automatically translated

72262000 - Software development services