The PLCS initiative will not attempt to define the functionality to be provided in an integrated product database. In a shared access environment, decisions on how much of the PLCS data model to implement, whether to add additional information and what functionality to provide, will be left to the discretion of implementers.
The PLCS Initiative will develop a set of Interchange Specifications, to define some standardized subsets of the data model for use as neutral exchange formats. The relationship of these Interchange Specifications to the existing and emerging STEP formats – APs, Conformance Classes, Modules, Part 21 Files, SDAIs etc. – has yet to be determined.
A methodology will also be provided for establishing additional user defined Interchange Specifications. Consideration will be given to developing a registration mechanism.
The required set of Interchange Specifications has yet to be fully defined. Possible candidates are listed below.
PLCS will provide a comprehensive capability to exchange information about the identification of products and related items.
Many exchanges of product data need to link information to elements in the product physical or functional breakdown structure.
PLCS will provide a comprehensive capability to define and exchange the product configuration structure for the whole or any part of the product, including relevant meta-data to enable the status and significance of the exchanged data to be understood. This will address all stages of the product its life cycle: as REQUIRED, as DESIGNED, as BUILT and as MAINTAINED (See Section 6.1)
PLCS will also provide a capability to attach any kind of information object to the product structure, with appropriate linkage to the physical or functional breakdown, and to other related data elements.
PLCS will provide a capability to communicate a defined set of supportability characteristics of the product (reliability, mean time to repair etc.), including the de-composition and allocation of targets to components of the product, based on a physical or functional breakdown.
The same structure will also be able to communicate other types of requirement (e.g. performance capability) although these may not be modelled in detail. Opportunities for co-operation with the System Engineering AP project New Work Item (SC4 document N674) will be actively explored for modelling system requirements.
PLCS will provide a generic capability (not detailed modelling) to communicate different operating and usage scenarios related to a product.
PLCS will provide a capability to establish and communicate a classification of maintainer skill levels, supported by textual description.
PLCS will provide a capability to describe and exchange information related to predicted failures of the product and its components. This will be achieved by developing entity-attributes to relate product failure modes, failure consequences and failure diagnostic information to elements of the product breakdown (functional or physical). Failure descriptions, consequences and diagnostic characteristics will be held as text or information objects but not modelled in detail.
PLCS will provide a capability to describe and exchange information about the maintenance tasks to be performed on the product and related components under different usage scenarios. Tasks can be linked to elements of the physical or functional breakdown. The full capability of the NCDM[3] in this area will be supported.
PLCS will provide a capability to define the nature and extent of feedback information which maintainers are required to provide.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.