complexType FsepIdentifier

diagram |
namespace | https://mmixm.aero/features/4
children | mx:fsepFac mx:fsepFic mx:fsepLocId mx:fsepReferenceId mx:previousFsepFac mx:previousFsepLocId
used by |
elements | Qualification/fsepIdentifier AssetIdentifier/fsepIdentifier
annotation |
documentation
Complex type containing the fsepFac, fsepFic, and fsepLocId.
source | <xs:complexType name="FsepIdentifier"> <xs:annotation> <xs:documentation>Complex type containing the fsepFac, fsepFic, and fsepLocId.</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="fsepFac" type="mb:FsepFacType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The five- character alphanumeric field contains the type of entity in FSEP, including services. This is the field FAC_TYPE in the RMLS/FSEP database. Sample values include the following. ASR: Airport Surveillance Radar ATIS: Automatic Terminal Information System ATCT: Airport Traffic Control Tower BUECS: Backup Emergency Communications Service CFAD: Composite Flight Data Processing Service EADS: En Route Automation Display System</xs:documentation> </xs:annotation> </xs:element> <xs:element name="fsepFic" type="mb:FsepFicType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The Facility Identification Code (FIC) provides the make, model, and class for identifying equipment in FSEP. The make and model codes make up the four-character FIC Code. The FIC Code is mandatory in all non-service records. The FIC Codes established prior to the release of older versions of Order 6000.5 are still valid and remain in the FSEP Desk guides until the equipment is retired from the NAS. Not all legacy codes are changed to the new FIC Code. This is the field FAC_CODE_FACILITY in the RMLS/FSEP database. Sample values include the following. ASR FICs: 53AC, 53AG, SC00 GBAS FICs: NWA0 TBFM FICs: 61UB, AE00</xs:documentation> </xs:annotation> </xs:element> <xs:element name="fsepLocId" type="mb:FsepLocIdType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>This three or four character field contains the city and state where the equipment is physically located. Location identifiers assignment process is detailed in Order 6000.5E, Chapter 3, Section 3.1 Location Identifier Process. This is the field FAC_IDENT in the RMLS/FSEP database but which is typically referred to as LOC_ID. There are three sources for a LOC_ID: 1. A value from the IDENT column in the 7350.9. 2. A value from the IDENT column in the 7350.9 to which a single character suffix is added. The suffix is added when there is more than one instance of the same FSEP Facility at a specific location. An example is the Precision Approach Path Indicators (PAPI) at Boston Logan Airport. There are 4 of these, and each has a different LOC_ID derived from BOS, the identifier for Logan. These are BOS, BOSA, BOSB and BOSC. 3. A made up value starting with a Q. These are known as Q Identifiers and are created when there is no established identifier within 20 miles of the location of the FSEP Facility. Sample values include I90, DAL, TPA, CXYA, DCAP, PUB, ZDCC, DFWA.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="fsepReferenceId" type="xs:integer" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>An internal asset record identifier used by FSEP.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="previousFsepFac" type="mb:FsepFacType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The FsepFac previously associated with this asset, per Order 6000.5 Facility, Service, and Equipment Profile (FSEP).</xs:documentation> </xs:annotation> </xs:element> <xs:element name="previousFsepLocId" type="mb:FsepLocIdType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The FSEP Location Ident that was previously in use by the asset, per Order 6000.5 Facility, Service, and Equipment Profile (FSEP).</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>

element FsepIdentifier/fsepFac

diagram |
namespace | https://mmixm.aero/features/4
type | mb:FsepFacType
properties |
minOcc | 0
maxOcc | 1
content | simple
facets |
Kind | Value | Annotation
pattern | [0-9A-Z]{2,5} |
annotation |
documentation
The five- character alphanumeric field contains the type of entity in FSEP, including services. This is the field FAC_TYPE in the RMLS/FSEP database. Sample values include the following. ASR: Airport Surveillance Radar ATIS: Automatic Terminal Information System ATCT: Airport Traffic Control Tower BUECS: Backup Emergency Communications Service CFAD: Composite Flight Data Processing Service EADS: En Route Automation Display System
source | <xs:element name="fsepFac" type="mb:FsepFacType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The five- character alphanumeric field contains the type of entity in FSEP, including services. This is the field FAC_TYPE in the RMLS/FSEP database. Sample values include the following. ASR: Airport Surveillance Radar ATIS: Automatic Terminal Information System ATCT: Airport Traffic Control Tower BUECS: Backup Emergency Communications Service CFAD: Composite Flight Data Processing Service EADS: En Route Automation Display System</xs:documentation> </xs:annotation> </xs:element>

element FsepIdentifier/fsepFic

diagram |
namespace | https://mmixm.aero/features/4
type | mb:FsepFicType
properties |
minOcc | 0
maxOcc | 1
content | simple
facets |
Kind | Value | Annotation
pattern | [0-9A-Z]{4,5} |
annotation |
documentation
The Facility Identification Code (FIC) provides the make, model, and class for identifying equipment in FSEP. The make and model codes make up the four-character FIC Code. The FIC Code is mandatory in all non-service records. The FIC Codes established prior to the release of older versions of Order 6000.5 are still valid and remain in the FSEP Desk guides until the equipment is retired from the NAS. Not all legacy codes are changed to the new FIC Code. This is the field FAC_CODE_FACILITY in the RMLS/FSEP database. Sample values include the following. ASR FICs: 53AC, 53AG, SC00 GBAS FICs: NWA0 TBFM FICs: 61UB, AE00
source | <xs:element name="fsepFic" type="mb:FsepFicType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The Facility Identification Code (FIC) provides the make, model, and class for identifying equipment in FSEP. The make and model codes make up the four-character FIC Code. The FIC Code is mandatory in all non-service records. The FIC Codes established prior to the release of older versions of Order 6000.5 are still valid and remain in the FSEP Desk guides until the equipment is retired from the NAS. Not all legacy codes are changed to the new FIC Code. This is the field FAC_CODE_FACILITY in the RMLS/FSEP database. Sample values include the following. ASR FICs: 53AC, 53AG, SC00 GBAS FICs: NWA0 TBFM FICs: 61UB, AE00</xs:documentation> </xs:annotation> </xs:element>

element FsepIdentifier/fsepLocId

diagram |
namespace | https://mmixm.aero/features/4
type | mb:FsepLocIdType
properties |
minOcc | 0
maxOcc | 1
content | simple
facets |
Kind | Value | Annotation
pattern | [A-Z0-9]{3,4} |
annotation |
documentation
This three or four character field contains the city and state where the equipment is physically located. Location identifiers assignment process is detailed in Order 6000.5E, Chapter 3, Section 3.1 Location Identifier Process. This is the field FAC_IDENT in the RMLS/FSEP database but which is typically referred to as LOC_ID. There are three sources for a LOC_ID: 1. A value from the IDENT column in the 7350.9. 2. A value from the IDENT column in the 7350.9 to which a single character suffix is added. The suffix is added when there is more than one instance of the same FSEP Facility at a specific location. An example is the Precision Approach Path Indicators (PAPI) at Boston Logan Airport. There are 4 of these, and each has a different LOC_ID derived from BOS, the identifier for Logan. These are BOS, BOSA, BOSB and BOSC. 3. A made up value starting with a Q. These are known as Q Identifiers and are created when there is no established identifier within 20 miles of the location of the FSEP Facility. Sample values include I90, DAL, TPA, CXYA, DCAP, PUB, ZDCC, DFWA.
source | <xs:element name="fsepLocId" type="mb:FsepLocIdType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>This three or four character field contains the city and state where the equipment is physically located. Location identifiers assignment process is detailed in Order 6000.5E, Chapter 3, Section 3.1 Location Identifier Process. This is the field FAC_IDENT in the RMLS/FSEP database but which is typically referred to as LOC_ID. There are three sources for a LOC_ID: 1. A value from the IDENT column in the 7350.9. 2. A value from the IDENT column in the 7350.9 to which a single character suffix is added. The suffix is added when there is more than one instance of the same FSEP Facility at a specific location. An example is the Precision Approach Path Indicators (PAPI) at Boston Logan Airport. There are 4 of these, and each has a different LOC_ID derived from BOS, the identifier for Logan. These are BOS, BOSA, BOSB and BOSC. 3. A made up value starting with a Q. These are known as Q Identifiers and are created when there is no established identifier within 20 miles of the location of the FSEP Facility. Sample values include I90, DAL, TPA, CXYA, DCAP, PUB, ZDCC, DFWA.</xs:documentation> </xs:annotation> </xs:element>

element FsepIdentifier/fsepReferenceId

diagram |
namespace | https://mmixm.aero/features/4
type | xs:integer
properties |
minOcc | 0
maxOcc | 1
content | simple
annotation |
documentation
An internal asset record identifier used by FSEP.
source | <xs:element name="fsepReferenceId" type="xs:integer" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>An internal asset record identifier used by FSEP.</xs:documentation> </xs:annotation> </xs:element>

element FsepIdentifier/previousFsepFac

diagram |
namespace | https://mmixm.aero/features/4
type | mb:FsepFacType
properties |
minOcc | 0
maxOcc | 1
content | simple
facets |
Kind | Value | Annotation
pattern | [0-9A-Z]{2,5} |
annotation |
documentation
The FsepFac previously associated with this asset, per Order 6000.5 Facility, Service, and Equipment Profile (FSEP).
source | <xs:element name="previousFsepFac" type="mb:FsepFacType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The FsepFac previously associated with this asset, per Order 6000.5 Facility, Service, and Equipment Profile (FSEP).</xs:documentation> </xs:annotation> </xs:element>

element FsepIdentifier/previousFsepLocId

diagram |
namespace | https://mmixm.aero/features/4
type | mb:FsepLocIdType
properties |
minOcc | 0
maxOcc | 1
content | simple
facets |
Kind | Value | Annotation
pattern | [A-Z0-9]{3,4} |
annotation |
documentation
The FSEP Location Ident that was previously in use by the asset, per Order 6000.5 Facility, Service, and Equipment Profile (FSEP).
source | <xs:element name="previousFsepLocId" type="mb:FsepLocIdType" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>The FSEP Location Ident that was previously in use by the asset, per Order 6000.5 Facility, Service, and Equipment Profile (FSEP).</xs:documentation> </xs:annotation> </xs:element>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy