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
Configuration Options Context Description Rationale
By message type or class of data Align with the Message Types from
Populate Priority and Security Data Fields By issue time for types for data–range of
parameters Range of parameters associated with the
Message Types By effective time for types of data-range
of parameters Range of parameters associated with the
Message Types If multiple values are available, enable
selection of average value, standard deviation value, range of values, preferred
providers For example, if multiple sensor sources are
available and provided for an area, enable the user to select a means to reduce the
data to a relevant value, e.g., multiple temperature sensors at an airport.
Enable selection or input of a specific geo- reference for sensor data
For example, user might select RVR For the eastern--
‐most of two parallel runways because the swamp outside the airport
tends to produce mist that reduces visibility for that runway.
85 By expiration time - Range of parameters
Range of parameters associated with the Message Types
Enable selection of any data within a geo- referenced area, e.g. X miles either side of
route and including vertical range for a 3- D area
The AOC can set this based on a pilot profile and can upload to the EFB. This
geo-referenced area can also be pilot- selectable.
Enable selection of “Trend” For a specific event
This rule allows an operator to select a data point, e.g. weather event, and indicate how
much history of the event is desired for a trending display.
17.4 SRM 10.4 – Manage Subscription and Data Request Configurations
System Rule Context Description Rationale
DMS and EFB systems shall contain configurable profiles for subscriptions and
data requests that are managed by both the aircrew and the dispatcher
Subscriptions have a couple of characteristics that have an impact:
They publish a complete stream of data.
They publish updates to a data set. In the latter case, the subscriber must
perform a data request to ensure it has a current copy of the complete data set that
can then be updated. The Profiles associated with this system rule enable the
user to designate which subscriptions require a “pre--
‐load” Of the complete data set and then to request that data.
Configuration profiles shall be capable of alignment with specific flight plans.
Configuration profiles will be used repetitively for common routes.
Users shall be able to store profiles keyed at least to flight or route and pilot.
Configuration profiles will be used repetitively for common routes and pilots
may have specific needs for specific data or different parameters, e.g., miles to either
side of the route.
Configuration profiles shall enable the user to plan deviations from a flight plan
or establish ad hoc situations for obtaining As part of both pre
‐flight and en route strategic planning, dispatchers and pilots
will need to obtain data that supports these
86 needed flight planning information.
planning activities. Update interval timeframes shall be
configurable by subscription, e.g., NAS program or other source of data
The user will establish update intervals that support his or her need for frequency of
data.
Request-response configurations shall be enabled for those subscriptions that
require a pre ‐load of the data when
updates only are issued with the subscription
Data request ‐response configurations are
important because in many instances activation of a subscription only provides
updates. In Those instances, activation of the subscription must also be accompanied
for a data request to pre
‐load a baseline of the data.
User shall be able to select data sets that are not on the flight plan, e.g., select
specific items or events, or expand the geospatial scope of the subscription.
As part of both pre-flight and en route strategic planning, dispatchers and pilots
will need to be obtain data that support these planning activities.
Subscription parameters associated with a configuration profile shall be capable of
being downloaded to an EFB. In consideration of aircrew workload,
subscription profiles need to be pre-loaded into the EFB.
The OWS-9 RFQ CFP Annex B System Rules Model SRM defines the following system rules for the Data Prioritization Module
17.5 SRM 10.5 – Populate Priority and Security Data Fields
