80 Regarding provider selection, the DMS shall be able to add metadata to the message,
stating the list of initial providers in concurrence and the provider that was eventually selected based on the client’s choices.
Those have not been implemented in OWS-9 and may could be considered for future work, if their relevance is confirmed.
16 AIXMWXXM Metadata Compliance
The AIXMWXXM Metadata Compliance is a requirement for the Provenance Tracking Module and the Operator Configuration Module. The provenance metadata generated by
the Provenance Tracking Module and the Operator Configuration Module must conform to ISO 19115 and ISO 19139 requirements which is in line with the metadata
representation of AIXM and WXXM. Developing the metadata generated by the Provenance Tracking Module and the Operator Configuration Module to be in line with
the AIXM and WXXM metadata profile currently under development will allow for compatibly.
17 Appendix: Systems Rules Model Analysis
This section details each of the systems rules models and the analysis behind each of the requirements outlined in the RFQ Section 10 Appendix. The basis of analysis is from an
FAA SWIM Harris NEMS perspective as well as a SESAR SWIM perspective. Harris services the FAA NAS SWIM program office through the deployment of the NAS
Enterprise Messaging Service NEMS. The NEMS is the implementation of the SWIM enterprise service within the NAS.
The SESAR SWIM perspective is represented by ATMOSPHERE and TriaGnoSys.
17.1 SRM 10.1 – Maintain Data Synchronization between Ground and Aircraft Users
Configuration Options Context Description Rationale
Send copies to the dispatch client of all data sent to the aircraft
Ensures all parties receive the same data. Send the type or class of data sent to the
aircraft to the dispatch client with sufficient information to enable the dispatch client to
request the data. Could Be implemented by sending unique “hash tag--
‐like” metadata to the dispatch client of all the data sent to
the aircraft. Minimizes bandwidth by sending only the
types, classes, and metadata to the dispatch client.
Send copies to the dispatch client of selected types or classes of data sent to the
Enables the dispatch client to subscribe to copies of the data sent to the aircraft for
81 aircraft.
discrete sets of data or data products, e.g. NOTAMs Or weather.
17.2 SRM 10.2 – Perform Data Validation
Metric Definitions
Requirements
Timeliness 1 Data is delivered
within its valid timeframe
DMS and EFB software shall evaluate message content for start and end
datetimes to determine whether the message data needs to be flagged when
sent to the aircraft or presented to the user.
Note – applying this evaluation at the aircraft will identify messages that are
within valid time frame when transmitted but not when received at the aircraft.
Software shall enable the user to set a parameter for acceptable range of
variance from valid time frame for transmitting information to the aircraft.
Software shall set the Data Validation Data element appropriate valid time
frame code as noted below: o Within valid time frame
o Outside valid time frame Software shall maintain percent of
failures and reports via the MonitorReport Network Performance
function as a percent per 1,000 messages:
1,000 minus of out-of-valid time frame
msgs Divided by
1,000
82 Timeliness 2
Data represents the most up-to-date
information DMS software shall track and
reference all updates using the time they are issued regardless of the
effective times of the changes until the time of reception to identify the
most up-to-date information.
DMS and EFB software shall transmit new or updated information to the
cockpit as soon as it becomes available at the approved source.
User shall be enabled to set a parameter for acceptable range of variance from
time for transmitting information to the aircraft as measured from the issue
datetime of the message until received.
DMS software shall populate the Data Validation Data element code with
appropriate timeliness factor code, as noted below:
o Meets timeliness factor o Exceeds timeliness factor
The network performance metric shall be defined as communications
performance for transmission of information from the data source to the
cockpit. This performance metric will be defined by intended function and
operational use.
Software shall determine whether messages meet currency time frame
requirement as measured from issue date time through delivery date time
to aircraft. Software shall maintain percent of failures and report via the
MonitorReport Network Performance function:
1,000 minus of msgs not meeting
83
time frame Divided by
1,000 Timeliness 3
Subscribed update intervals are being
complied with Software shall monitor update intervals
to ensure they are being complied with using transmission date time groups
DTGs as the criteria for determining the actual intervals.
Software shall populate the Data Validation Data element code with
appropriate timeliness factor code, as noted below:
o Meets subscribed interval o Exceeds subscribed interval
User shall be enabled to set a parameter for acceptable range of variance from
subscribed update intervals Software maintains percent of failures
and reports via the MonitorReport Network Performance function:
1,000 minus of subscription intervals missed by more than __seconds
Divided by
1,000 Lost Data -applies to
all modes of operation
Broadcast Demand
Contract Determine whether
any messages or data sets were lost
DMS software shall evaluate message content and context to determine that a
message has been lost, e.g., refers to prior content such as NOTAM, TFR
that has not been received, and populates the lost data code in the Data
Validation Data Set.
Software shall populate the Data Validation Data element code with
appropriate lost data code, as noted
84 below:
o No lost data o Previous message not received
Software shall evaluate the frequency at which a message refers to prior
content e.g., NOTAM, SIGMET, TFR, etc. that has not been received.
Software maintains percent of failures and reports via the MonitorReport
Network Performance function:
1,000minus of lost messagesdata sets
Divided by
1,000
17.3 SRM 10.3 – Perform Data Filtering
