1.
XML
Schema:
a.
DataManagement/ApplicCrossRefTable.xsd
i. Add a choice between productAttributeList and a new empty
element noProductAttribute in the element applicCrossRefTable .
b.
DataManagement/ProductCrossRefTable.xsd
i. Add a choice between product (maxOccurs unbounded) and a new
empty element noProduct
in the element productCrossRefTable .
c.
DataManagement/CondCrossRefTable.xsd
i. Add a choice between existing
sequence (condTypeList, condList, incorporation?) and a new empty element noCond in the element condCrossRefTable .
d.
DataManagement/DmStatus.xsd
i. Add a choice between existing structure
(displayText, assert, evaluate)
and a new empty element allProducts
and a new empty element noProduct
in the element applic .
2.
Specification
change:
a.
Update
section “3-3-1 Applicability management” / “1. General”
Applicability
provides the mechanism to identify the context for which a data module or parts
of a data module are valid for one or more configurations.
The
applicability mechanism is supported by the applicability annotations and
formula within data modules (in DM Status XML fragment) and by three specific
data module types:
·
the
Applicability Cross-reference Table (ACT) data module
·
the
Conditions Cross-reference Table (CCT) data module
·
the
Products Cross-reference Table (PCT) data module
·
The ACT,
CCT and PCT data modules are supported by the ApplicCrossRefTable.xsd,
CondCrossRefTable.xsd and ProductCrossRefTable.xsd schemas, respectively.
Applicability is managed for
technical (aircraft related) and non-aircraft related content.
b.
Update
section “3-3-1 Applicability management” / “2.1. ACT: Applicability Cross-reference Table”
The Applicability Cross-reference Table
(ACT) data module is used to declare product attributes. A product attribute is
a property of the Product that affects the applicability of technical content.
Product attributes are properties of the Product that are typically set at the
time of manufacture of a product instance and will usually not change
throughout the service life of a product instance. Examples of product
attributes are model, series, and serial number.
The ACT is also delivered with
non-aircraft related content, containing a specific flag to indicate that there
are no product attributes.
[…]
c.
Update
section “3-3-1 Applicability management” / “2.2. CCT: Conditions Cross-reference Table”
The Conditions Cross-reference Table
(CCT) data module is used to declare any condition that can affect
applicability of data. Conditions can be technical, operational, environmental,
or any other type that can affect technical content. Technical conditions are
typically tied to the configuration of the Product, such as service bulletins
or modifications.
The CCT is also delivered with
non-aircraft related content, containing a specific flag to indicate that there
are no conditions.
[…]
d.
Update
section “3-3-1 Applicability management” / “2.3. PCT: Products Cross-reference Table”
The Products Cross-reference Table (PCT)
data module is a repository for defining product instances and associating
values to product attributes and conditions for each product instance. It is a
formal method for defining product instances and the configuration of each
product instance.
The definition of a product instance in
the PCT data module includes a list of assignments of actual values to product
attributes and conditions for the product instance. Each assignment must
include the following information:
·
a
reference to the product attribute or condition
·
an
indicator whether this is a product attribute or condition
·
the actual
value
For each product in the PCT, only the
valid configuration data known at the time of generation of the Data Module
shall be provided.
The PCT is also delivered with
non-aircraft related content, containing a specific flag to indicate that there
are no products.
[…]
e.
Update
section “3-3-1 Applicability management” / “3.2. Applicability annotation of
the data module”
The applicability annotation of the data
module provides the configuration characteristics of the whole data module, to
be able to apply a filtering mechanism.
For a data module providing
non-aircraft related content, the applicability annotation contains a specific
flag to indicate that there are no products.
Using the Applicability cross-reference
table data module, the applicability annotation provides resolved configuration
data by giving the related products (aircraft defined within the PCT data
module) and conditions (such SB "pre" and "post" conditions
defined in the CCT data module).
The data module applicability annotation
has two logical branches which are used for separate purposes:
·
A human
readable applicability annotation ("displayText") which provides
human readable applicability information. This branch can be used in
conjunction with the other branch as required.
·
A
computable applicability annotation ("assert" and
"evaluate") which provides applicability information in a computable
format which can be used to support dynamic filtering of the annotated content.
An alias to indicate that all
products can be used instead of the two logical branches, defining that the
data module is applicable to all products defined in the PCT.
[…]
3.
CSDD
Update:
a.
Entry
Applicability Annotation
APPLICATION IN SPECIFICATIONS
Add noProduct and allProducts
element (DmStatus schema)
b.
Entry
Product
APPLICATION IN SPECIFICATIONS
Add noProduct element
(ProducCondRefTable schema)
c.
Entry
Product Attributes
APPLICATION IN SPECIFICATIONS
Add noProductAttributes element (ApplicCrossRefTable
schema).
d.
Entry
Product Condition
APPLICATION IN SPECIFICATIONS
Add noCond element (CondCrossRefTable
schema)