The ISO 10303-239 PLCS Application Activity Model (AAM) is an IDEF0 representation
of the business activities that set the scope and
information requirements for the PLCS standard. The model is composed of a set of
figures and a set of definitions of these business activities and
their associated information flows.
IDEF0 provides a graphical notation for function modeling of an organization or system.
Activities can be described by their inputs, outputs, controls and mechanisms (ICOMs).
IDEF0 Box and Arrow Graphics
This DEX supports a subset of these business activities and information flows. These
are highlighted in yellow in the figures Figure 1 and Figure 2.
The information flows marked with an asterisk are not explicitly represented within
PLCS. This information is instead transferred by other means, e.g., handled by a document.
The activity labels in the AAM views above have the following definitions:
Analyze support feedback
analysis of support feedback from individual tasks to determine exceptions from the
support solution, exceptional maintenance needs, the impact on operations, and suggestions
for improvement
The ICOM arrow labels in the AAM views above have the following definitions:
APSI
set of information, subject to configuration change management, that is established
to develop and deliver support for a product in focus
NOTE
This term corresponds to the EIA 649 term "product configuration information" which
includes:
product definition information that defines the product requirements, documents the
product attributes and is the authoritative source for configuration definition;
product operational information, used to test operate maintain and dispose of the
product.
APSI and related information
set of assured and related information used to develop and deliver support for a product
in focus, including feedback from using and supporting the product over its life cycle
NOTE
Related information includes records of the history of the usage or support of realized
products, design and support analysis results and reasons why decisions were taken.
Such information includes design and failure analysis records, logistic support analyses,
running hours, environment descriptions, operating profiles; test results, records
of maintenance activities, resources used, and faults found plus any other content
deemed relevant to life cycle support.