Data Mediation Overview

Mediation rules are used to define a precedence/authority between sources providing data for the same fields. Typically the result of a mediation rule is filter out a value from the update if we previously applied data from a more authoritative source on that particular field. It's definitely worth noting these rules are by field as there is no authoritative source for all fields. References to 3rd party and airline data are used to indicate data received from ATD-2 partner airlines and 3rd party data providers.

Rule	Description	Sources Involved	Fuser Fields
AcidRule	Prefer the ACID value from FAA systems. Priority order: TFMS_Flight, TBFM, or ASDEX TFMS_Terminal	All	acid
AerodromeRule	TFMS (Flight plan), TFMS (Flight plan amend), TBFM TFMS (Flight schedule), TFMS (Flight create), TFMS (Flight modify), TFMS_Terminal Airline data (when available) 3rd party source (when available)	TFMS, TBFM, TFMS_Terminal, Airline Data, 3rd Party Data, FUSER	arrivalAerodrome departureAerodrome
AircraftRegistrationRule	Using a source priority for setting the aircraft registration (tail). Priority order: TFMS_Terminal, ASDE-X Airline data (when available) 3rd party source (when available)	TFMS_Terminal, Airline Data, 3rd Party Data, ASDE-X	aircraftRegistration aircraftAddress
AircraftTypeRule	If we have a known aircraft type do not overwrite it with an unknown aircraft type.	All	aircraftType
AirlineParkingGateRule	The airline parking gate rule. For ATD-2, gate information was derived primarily from participant airline and 3rd party sources. Note: The actual parking and predicted parking gate values are set by other sources. Also note stand = parking gate. Priority order: Airline data (when available) 3rd party source (when available) TFMS_Terminal	Airline Data, 3rd Party Data	departureStandAirline arrivalStandAirline
ArrivalRunwayEstimatedTimeRule	Use TFMS_Flight times for the arrivalRunwayEstimatedTime until we start getting arrival times from TBFM.	TFMS_Flight, TBFM	arrivalRunwayEstimatedTime
BeaconCodeRule	Prefer beacon code from ASDEX, TFM, FUSER. SFDPS would also be good to use, however it is not currently integrated.	ASDEX, TFM, FUSER, SFDPS, IDAC, FLIGHTHUB_POSITION	beaconCode
DepartureStandEstimatedTimeRule	The DepartureStandEstimatedTime is an estimated out time from any external source that is not an airline or flight plan source. Currently, 3rd party source is the only such source. 3rd party source	3rd Party Data	departureStandEstimatedTime
RouteOfFlightRule	Prefer routes from TFMS_Flight source. This fixes an issue where TBFM only sends filed (nasRouteText) route before takeoff, then switches to the pref route (localIntendedRoute). TFMS_Flight sends the pref route from the beginning.	TFMS_Flight, TBFM, FUSER	routeText departureFixSourceData arrivalFixSourceData departureFixEstimatedTime arrivalFixEstimatedTime
EramIdentifierRule	Prefer ERAM sources for the ERAM identifiers. Currenly, we use TFMS_Flight messages triggered by ERAM, but eventually, SFDPS would be better, once it is integrated.	TFMS_Flight, FUSER, SFDPS, IDAC	computerId eramGufi sourceFacility
SensitiveDataRule	Priority for external sensitive data flag. Priority is: TFM, TFM-TFDM, SFDPS 3rd party source (when available)	TFM, TFM-TFDM, 3rd Party Data, ASDEX	sensitiveDataExternal
StandActualTimeRule	Priority for setting the actual "stand" / gate times. Priority is: Airline data (when available) TFMS_Terminal TFMS_Flight STBO 3rd party source (when available)	Airline Data, TFMS_Terminal, TFMS_Flight, STBO, 3rd Party Data	departureStandActualTime arrivalStandActualTime
RunwayActualTimeRule	Priority for setting the actual take off and landing times is: STBO (position derived) Airline data (when available) TFMS_Terminal TFMS_Flight 3rd party source (when available) Not that TFMS is a lower priority source because both OOOI data from airlines and TFMS AZ/DZ messages are mapped to the actual runway times. Airline ON and OFF data is accurate, but the AZ/DZ messages based on ERAM track data are inaccurate.	Airline Data, TFMS_Terminal, TFMS_Flight, STBO, 3rd Party Data	departureRunwayActualTime arrivalRunwayActualTime
StaleUpdateRule	Filters out updates to individual data elements if the incoming message is stale, relative to the most recent time the data element was last updated.	All	All
TmaIdacSwimSystemPriorityRule	Use values from TBFM SWIM over NASA TBFM other than fields listed the row below. Typically this would mean we would use common fields like a route of flight from TBFM SWIM over NASA TBFM.	TBFM (NASA)	All fields not included in the list in the next row
TmaNasaSystemPriorityRule	Use these values from a NASA TBFM system over any other source. Do not overwrite them with values from another source. In particular do not let allow TBFM SWIM to overwrite NASA TBFM for these values.	TBFM (NASA)	arrivalRunwayAssigned arrivalRunwayEstimatedTime (ETA) arrivalRunwayMeteredTime (STA) arrivalRunwayMeteredTime.frozen arrivalRunwayMeteredTime.value extensions.tbfmExtension.arrivalRunway extensions.tbfmExtension.arrivalRunwaySta extensions.tbfmExtension.arrivalRunwayTraconAssigned extensions.tbfmExtension.arrivalRunwayAssignmentFrozen

	+ Freedom of Information Act + Budgets, Strategic Plans and Accountability Reports + The President's Management Agenda + NASA Privacy Statement, Disclaimer, and Accessibility Certification + Inspector General Hotline + Equal Employment Opportunity Data Posted Pursuant to the No Fear Act + Information-Dissemination Priorities and Inventories		Curator: Victoriana Delossantos NASA Official: Al Capps Last Updated: May 22, 2019