|
Technical Description - PLCS Application Activity Model
|
The PLCS (AP239) Application Activity Model (AAM) was created during the early phases of the PLCS development. IDEF0 was the modelling language used to devlop the AAM. Its initial purpose was to define the scope of AP239, and to identify what information needed to be represented in the imformation model. Now it is a good aid to understanding the scope and information requirements defined in this application protocol. The model is presented in the standard ISO 10303-239:2005 document as a set of figures that contain the activity diagrams and a set of definitions of the activities and their data.
The model is included in the ISO 10303-239:2005 standard. Click here to view the model section of the standard (A link to the model...)
The viewpoint of the model is that of the life-cycle owner who acquires the product-in-focus and strives to maximise value over the complete life cycle of the product, by taking whatever actions are necessary to deliver the required operational capability at minimum life cycle cost.
The purpose of the model is to represent the activities and information flows supported by Application Protocol 239 Product Life Cycle Support (PLCS). The set of products to be supported is known as the "product in focus" or PIF.
The text in this section was copied from (http://standards.ieee.org/reading/ieee/std_public/description/se/1320.1-1998_desc.html).
The IDEF0 function modeling language is designed to represent the decisions, actions, and activities of an existing or prospective organization or system. IDEF0 graphics and accom-panying texts are presented in an organized and systematic way to gain understanding, support analysis, provide logic for potential changes, specify requirements, and support system-level design and integration activities. IDEF0 may be used to model a wide variety of systems, composed of people, machines, materials, computers, and information of all varieties and structured by the relationships among them, both automated and nonautomated.
For new systems, IDEF0 may be used first to define requirements and to specify functions to be carried out by the future system. As the basis of this architecture, IDEF0 may then be used to design an implementation that meets these requirements and performs these functions. For existing systems, IDEF0 can be used to analyze the functions that the system performs and to record the means by which these are done.