Purchase of 2 Instrument Flight Procedure Design Software Licenses including a maintenance and support system
DALO is for Air Navigation Services purposes planning to procure 2 (two) new Instrument Flight Procedures Design software (IFPD) licenses. The IFPD software to be procured shall assist the Royal Danish Air Force (RDAF) procedure designers in creating, converting and maintaining instrument flight procedures.
The contractor will be responsible for the installation, testing, training and setting-to-Work of the IFPD Software. The contractor must have an, by DALO, acceptable quality assurance management system.
The RDAF instrument flight procedure design office is an integrated part of the military aeronautical information service function. The office is responsible for creating and maintaining instrument flight procedures to a number of civil and military aero-dromes for use by the RDAF flying units. Until 2009 all of the Danish military instrument flight pro-cedures were based upon Terminal Instrument Procedures (TERPS criteria).
The transition of criteria from TERPS to International Civil Aviation Organizations Procedures for Air Navigation Services, Aircraft Operations (ICAO PANS OPS) with the add-on of NATO Allied Air Traffic Control Publication (AATCP-1) began in late 2009 and is currently ongoing. All the military instrument flight procedures are being converted and in some cases completely revised.
In three airports — 1 of which is entirely civil — the promulgated Instrument Landing System (ILS) glide slope is 2.75° and the Required Navigational Performance (RDH) some places as low as 34 ft. It is therefore essential that the flight procedure design software is flexible enough to also cover these non-standard conditions.
The RDAF flight procedure design office is also responsible for instrument flight procedures to some remote airstrips in Greenland, one of which is as far north as 81.5°N. It is therefore equally essential that the flight procedure design software is capable of working at such high latitudes.
The RDAF flight procedure design office is also contributing to the development of contingency procedures (1 engine out) for the RDAF transport aircraft. The software should therefore be able to work with parameters that are outside PANS OPS criteria.
The RDAF is an expeditionary air force for which reason the office could be faced with a requirement of creating or validating instrument flight procedures to in principle any place in the world. The office has already assisted a NATO partner in creating instrument flight procedures to one of its air bases. Only some countries within NATO have ratified the use of NATO AATCP-1 for which reason the requirement could be procedures based on ‘pure' PANS OPS criteria. It is therefore essential that the flight procedure design software is flexible enough to allow the user to select which criteria to apply.
The IFPD software will be operated on two independent stand-alone computers. Due to the need for mobility it is the intention to install the software on laptops with only one display. When working in the office, the laptop will normally be sitting in a docking station with an extra display attached and network (internet) connection. When working ‘in the field', network may not be available. It is therefore essential that connection to a network is not required for license validation etc.
The acquisition of the 2 (two) IFPD software licenses should be supported by a 5 (five) year maintenance and support service system, with an option to prolong the maintenance and support service system for additional 5 (five) years — 1 (one) year at a time.
Further in regards to the acquisition of the 2 (two) IFPD software licenses, DALO wishes to include 1 (one) initial education/training course for 2-3 (two/three) employees, with an option to order 5 (five) additional education/training courses within the entire Contract period.
Deadline
Fristen for modtagelse af bud var på 2015-04-10.
Indkøbet blev offentliggjort på 2015-02-21.
Leverandører
Følgende leverandører er nævnt i tildelingsbeslutninger eller andre indkøbsdokumenter:
Hvem?
Hvad?
Hvor?
Indkøbshistorik
Dato |
Dokument |
2015-02-21
|
Udbudsbekendtgørelse
|
2015-08-14
|
Bekendtgørelse om indgåede kontrakter
|