| DEX: (D004) work_package_definition — Work Package Definition | Date: 2007/09/14 16:11:29 Revision: 1.86 |
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.
IDEFØ provides a graphical notation for function modeling of an organization or system. Activities can be described by their inputs, outputs, controls and mechanisms (ICOMs).
This DEX supports a subset of these business activities and information flows. These are highlighted in yellow in the figures Figure 1, Figure 2, and Figure 3.
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:
activity to control work in progress to achieve efficient attainment of support opportunity objectives in accordance with a support schedule including: releasing tasks on which work may begin; monitoring task progress; certification of successfully completed tasks and release of the product for use when all actions are complete
NOTE
This activity implements and manages achievement of a support schedule. The activity controls the physical performance of the actions required to service, repair, test, overhaul, modify, calibrate or inspect a product needing support as specified by the task specification within the support solution definition or commissioning schedule. This activity includes:
action to create a schedule for a support opportunity including the identification of objectives; the identification, sequencing and scheduling necessary tasks, and arranging the provision and disposal of all necessary resources such as materials, labour, support equipment, facilities and, documentation to be available at appropriate times and locations
NOTE Support schedules may have different planning horizons such as annual, quarterly, monthly, weekly, and daily. One schedule may be a decomposition of another. Support tasks should be scheduled against a specific products or support element. Each schedule may be progressively refined and expanded until it defines the timing and location for all tasks applicable to the support opportunity in question.
The ICOM arrow labels in the AAM views above have the following definitions:
support solution definition that is authorized for use in providing support or disposal to one or more product or support element
task on which work may begin
work orders and work requests that result from the configuration change management process
NOTE Change directives serve as controls on the implementation or investigation of an identified change. Change directives include change orders, change tasks, change plans and change requests.
instructions or policies from beyond the model boundary that initiate or constrain support activities from concept through disposal
NOTE
These directives may include:
work request identifying additional support tasks that may be needed to restore products to serviceable conditions
identification of the resources needed to support scheduled work at one or more support opportunities
systematic plan or arrangement for performing one or more support tasks
NOTE The status of the schedule may change as it develops. The support schedule may include a maintenance schedule defining work to be performed on the product needing support. A support schedule may also define tasks applicable to support elements or required resources such as the calibration of a test instrument.
information on the progress of activities in relation to a support schedule
NOTE This information on status is transient and will change as the work progresses.
© OASIS 2010 — All rights reserved
