...
The diagram below shows the AIXM classes, including the relevant data types and code lits, needed to encode that information.
To encode the hours of operation of a radio navigation and landing aid In AIXM 5 the NavaidOperationalStatus class has to be used.
It is possible to code the availability of a Navaid and also of a NavaidEquipment.
As a general rule the availability of a NavaidEquipment should only be coded in case of a navaid composed of more than one navaid equipments, whereas at least one of them has a different availability than the others. If for one navaid equipment the availbility is coded, the availability has to be coded for all other navaid equipments of that navaid. For the navaid itself no availability will be coded. E.g. for a VOR/DME, in case the DME and VOR have different working hours, the availability will be ecoded for both navaid equipments separately, but not for the navaid).
In case of a navaid composed of one single navaid equipment or a navaid composed of more navaid equipments all having the same working hours, the availability will only be coded for the Navaid, it is not necessary to copy it for the individual navaid equipment(s) ( e.g. in case of a ILS where all components (LOC, GP, Markers) have the same working hours, the availability will only be coded for the navaid).
Info | ||
---|---|---|
| ||
Are this rule ok (see also below) , or shall the availability also if it is the same always be copied to all navaid equipments the navaid is composed of? If the working ours the navaid equipment is different, shall also the availability of the navaid be coded with "PARTIAL" an dno timesheet? |
The NavaidOperationalStatus class carries two attributes:
The signalType attribute indicated the type of information transmitted by a navaid or other radio emission source (e.g. azimuth or distance) .
Info | ||
---|---|---|
| ||
How shall this attribute be used? Does it make sense to define tham at all, A DME per see has a signattype Distance, etc. How can this be coded by using timesheet? |
The operationalStatus indicates the state of the navaid:
OPERATIONAL | Operating normally. | |||||
UNSERVICEABLE | Not available. | |||||
ONTEST | On test, do not use. | |||||
INTERRUPT | Expect interruptions of the signal. | |||||
PARTIAL | Operating with limited capabilities. For example, used when just the DME part of a VOR/DME is working.
| |||||
CONDITIONAL | Operative subject to published limitations or conditions. | |||||
FALSE_INDICATION | Giving false indication, do not use. | |||||
FALSE_POSSIBLE | False indication possible, use with caution. | |||||
DISPLACED | Displaced | |||||
IN_CONSTRUCTION | In Construction | |||||
OTHER | Other |
For the AIP data set the default value for the hours of operation for a navaid will be 'OPERATIONAL'. Most of the others status are only relevant for an application of the Digital NOTAM concept.
Info | ||
---|---|---|
| ||
In case a navaid is not operational H24, the rest of the time it shall be coded as unservicable? Rule to be added? |
For details of how to encode the Timesheet see topic Schedule [TSH]).
Coding Rules for Hours of Operation for Navaid
Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
---|---|---|---|---|
NAV-501 | Either the availability of the Navaid or the all the instances of NavaidEquipment the Navaid is composed shall only be coded. | Minimum AIP Data set | TBD | |
NAV-502 | The availability of a NavaidEquipment shall only be coded in case of a Navaid composed of more than one NavaidEquipment, whereas at least one of them has a different availability than the others. | Data consistency | TBD | See open question above |
NAV-503 | If for a Navaid composed of more than one NavaidEquipment, the availability of one of its NavaidEquipment is coded, the availability shall be coded for all other NavaidEquipment instances of that Navaid as well. | Data consistency | TBD | See open question above |
NAV-504 | If a Navaid is composed of more than one NavaidEquipment, the availbilty is coded for the instances of NavaidEquipment are not exactly the same the availabililty of the Navaid shall not be coded. | Data consistency | TBD | See open question above |
NAV-505 | If a Navaid is composed of one single NavaidEquipment the availability shall only be coded for the Navaid, | Data consistency | TBD | See open question above |
NAV-506 | If a Navaid is composed of more than one NavaidEquipment all having exactly the same availability, the availability shall only be coded for the Navaid, (it is not necessary to copy it for each instance of NavaidEquipment). | Data consistency | TBD | See open question above |
Coding Examples
See topic Navaid [NAV]