Import for NASX type definitions. Import for NASX Common Message definitions. This element is the root node for all messages received by the Traffic Flow Management System (TFMS) over the TFMS to Aircraft Situation Display to Industry (ASDI) Interface. Meta data for input messages. This element is the root node for all messages sent by the Traffic Flow Management System (TFMS) over the TFMS to Aircraft Situation Display to Industry (ASDI) Interface. Messages sent to the ASDI may be batched. TODO: Find out the true maximum number of messages the batch may contain. Realization of the asdiMessageType. There exists one asdiMessage element for each individual message of the batch of messages sent from the TFMS to the ASDI. Anyone of the following messages may be contained within the asdiMessage tags. There is only one message per set of asdiMessage tags. The Flight Plan Information Message is used to provide flight plan data for all eligible flight plans. The flightPlanAmendment message provides revised flight plan data as the result of a flight plan being successfully amended. Arrival Information Message is used to provide arrival date and time information for all eligible arriving flights. The Beacon Code Information Message provides beacon code data on eligible flight plans. The Departure Information message is transmitted for all eligible initially activated flight plans. Flight Plan Cancellation messages are used to provide cancellation data for all eligible flight plans. Track Information messages are used to provide a position update along with other information used in a Full Data Block. The messages are transmitted received by TFMS on a cyclic basis on all flat-tracked and non-tentative free-tracked eligible flight plans. Boundary Crossing Update Information (UZ) messages are used to provide current flight plan information on active eligible flights that enter an ARTCC. Generally speaking, the message is an ARTCC boundary crossing message. The purpose of the flightManagementInformation messages is to provide data from the TFMS that is not otherwise available. For example, the message will contain the current prediction of the wheels-up and wheels-down times for a flight, where these predictions are based on all the information available to the TFMS. The Oceanic Report message is transmitted for a flight by the TFMS to the ASDI when the data is available. Indicates the trigger for generation of the message to be sent to ASDI. Meta data for input messages. The asdiMessageType defines the attributes used by the ASDI system for ????. A realization of this complex type should exist for each flight data message that is sent to the ASDI The sourceFacility identifies the facility (Center or TRACON) which generated the original message that triggered this ASDI message to be sent.. The sourceTimeStamp identifies the time the original message that triggered this ASDI message to be sent was sent by the facility identified by attribute sourceFacility. The Aircraft Situation Display to Industry (ASDI) subsystem of the TrafficFlow Management System (TFMS) allows near real-time air traffic data to be disseminated to members of the aviation industry. Schema defines the message set, format and validation rules for messages sent between TFMS and ASDI. Enumerated type used to describe what triggered an ASDI message or event. Amendment Arrival Estimated departure clearance time Departure Flight Plan Cancellation Update 5 minute location update The feedback loop type, sending messages from the FDB back to the parser. An "ARTCC status" message An "update ASD" message A scheduled flight plan from SDB Cancel a scheduled flight An EDCT message Oceanic Update edct-fdb communication FA delay table transaction contants The Global Positioning System's message CDM flight create message CDM flight modify flight cancel message Slot Modify message Release all slots message hold all slots message ground stop message slot assignment message slot create message open slot message CDM FM Simplified Substitution or FM SLot create CDM EDCT Update that Cancels a flight CDM Remove function, to remove a flight or airline Bridge Event Feedback message from FDB back to parser to genereate a new eventlist for off route flights Beacon Code messages CDM Restore function, to restore a flight or airline. Airline early intent flight plans CDM FR message Slot create substitution message message for getting hist rte_etc info through ETMS for FCs and FMs update slave fpa indexes Deletion of a Flight from both master and slave Last entry and max size for the msg table