| Capability (C022):— representing_work_package | Date: 2007/07/11 16:32:00 Revision: 1.12 |
The capability assumes that a product owner wishes to commission one or more support activities to be undertaken as a single package of work. By providing the package with a single identity, further information, such as work authorization, contract details and any general administrative procedures can be attached and managed.
Work packages are not mutually exclusive, the option exists to to create further work packages, even within a single support opportunity, for the management of supplementary emergent work.
The information required to represent a package of work is summarized in the diagram in Figure 1 below and described in the following sections.
The EXPRESS-G shaded in grey is out of scope for this capability but is included for completeness to identify dependant or
related Capabilities. These address the definition of the life cycle opportunity(C020: representing_life_cycle_opportunity) or the identification of target for the work (referencing_product_as_individual![[warning:]](../../../../images/dex/warning.gif){kind=small}
Error C1: Capability referencing_product_as_individual not in dex_index.xml
), the identity of the activities within the work package (C032: representing_activity) and the identity of the person or organization compiling the package (C016: representing_person_organization.
Not include in the diagram is the procedure for requesting and authorizing the work. This is achieved through C066: representing_work_request and C065: representing_work_order.
A Work Package is represented as a Scheme, which is a sub type of Activity_method. In normal usage, the Work Package associates with a defined support opportunity defined through C020: representing_life_cycle_opportunity, taking the Activity found in that capability as its Scheme_subject_assignment. Alternatively, where a support opportunity has not been identified for the completion of the Work Package, the assignment may be made directly to the Product_as_individual that is the target for the work. The option also exists to relate one Work Package with another usiing Scheme_relationship.
The work to be done as part of the Work Package is defined through multiple instances of Capability C032: representing_activity. These are attached to the Work Package using the Scheme_entry_assignment entity. A valid Work Package must contain at least one entry assignment.
Each Work Package must be given an identity for reference purposes. This is achieved using Capability C001: assigning_identifiers.
An example of a Work Package for the for the first service of a bicycle is shown in the Instance Diagram at Figure 2. The diagram includes reference to a second work package, this time for the repair of some faults covered under the guarantee, which will be undertaken concurrently with the service but costed, authorised and paid for as a separate package of work.
This capability "Representing a Work Package" is related to the following capabilities:
Error C1: Capability referencing_documents not in dex_index.xmlThis capability "Representing a Work Package" is dependent on the following capabilities:
© OASIS 2010 — All rights reserved