How to model roles (
) and related attributes
|
Roles add additional characteristics to resources. For example, an Employee resource could have the role of Customer Service Representative, Supervisor, or Manager. You can optionally specify the roles that are required to complete any task that you model. You can add costs and availability to roles. For example, a certain role might cost $20 an hour and be available from Monday to Friday only.
Roles can also have qualifications, which are used to model requirements. For example, a System Administrator role could have the following qualifications:
For each role, you can also specify one or more qualifications. For example, a System Administrator role could have the following qualifications:
When you create a resource, such as an individual employee, you can add the roles for which that resource is qualified. For each qualification that a role has, you can specify a value. For example, the qualifications for a System Administrator role could have values like the ones listed in the following table.
Qualifications can also be used to specify the characteristics of resources other than people. For a fuel resource, for example, you could add a role to specify the type of vehicle or furnace that uses the resource. Then, you could add a fuel consumption qualification to the role to specify how much fuel the resource requires. Parent topic: Creating roles Related concepts
|
Adding qualifications to roles A qualification defines and measures specific qualities and requirements for a role.
You define the characteristics of a role by adding qualifications to it, which enables you to add required qualifications to tasks and to specify the qualifications provided by individual resources. To add qualifications to a role, complete the following steps:
You have defined the characteristics of a role. You can add roles to individual resources and specify values for the qualifications. You can also add required roles to a task or process and then specify the values of the qualifications required to complete the task or process. |
Costs can be associated with resources and roles.
The following different types of costs can be modeled:
A one-time cost is a cost that is incurred when a resource is first used in the process. This cost is incurred once per process for the specific resource. It can be used to reflect the cost of purchasing a resource that is required for the process. You can associate one-time costs with individual resources, bulk resources, or roles. A cost per time unit is a cost that increases with the amount of time the process uses the resource. An example of a cost per day is the rental of a piece of equipment required for the process. An example of a cost per hour is a contractor who is paid an hourly amount. You can associate costs per time unit with individual resources or roles.
A cost per quantity is a cost that increases with the amount of the resource that the process requires. For example, hydro has a cost per kilowatt hour. You can associate costs per quantity unit with bulk resources.
A cost per quantity and time unit is a cost that increases with both the amount of the resource and the time for which it is required. You can associate costs per quantity and time unit with bulk resources. An example is the cost of a rental space, say 12 000 USD per square foot per month. You set a monthly duration by specifying it as a number of days, for example, 30 days.
A cost has two parts, the amount of the cost and the currency. Currencies are specified using ISO symbols, such as USD for United States dollar or EUR for euro.
If you model costs for both resources and roles, the resource cost takes priority. Role cost is used only if no other cost is associated with the resource.
Parent topic: Adding costs Related tasks
|
You may want to specify when a resource or role is available, or how much of a bulk resource is available. If you do not specify an availability, it is assumed that the resource or role is always available.
To specify the availability of a resource or role, complete the following steps:
If the resource or role is affected by more than one timetable, you can add another timetable in the same way.
Parent topic: Creating resources and roles
|
Exporting roles
| Element | WebSphere Integration Developer | WebSphere MQ Workflow Buildtime | WebSphere Studio Application Developer Integration Edition |
|---|---|---|---|
|
Role |
(not supported)
|
Role. Not all attributes of FDL Person/Role/Organization are populated. |
(not supported)
|
|
Role requirement |
(not supported - use a human task)
|
Staff assignment. Only limited staff assignment is supported. See Staff activity generation. |
BPEL staff activity.
Only role requirements of Person or Staff or their subtypes are supported. If a role is assigned to a task or process and the associated resource definition is Person or Staff (or a subtype of these), during the export, a staff activity with a potential owner is created. If you want to specify editor or reader instead of potential owner, you must manually update the generated BPEL file. See Staff activity generation for information. |
Creating roles
- Creating roles
You can define roles to add additional characteristics to resources.
- Adding availability
You may want to specify when a resource or role is available, or how much of a bulk resource is available. If you do not specify an availability, it is assumed that the resource or role is always available.
- Adding costs
You may want to model the cost of using a resource or a role. If a resource has a cost assigned to it, as well as a cost assigned to the role it carries out, the resource cost takes priority.
Role model example
- Roles (Team Lead)
- Timetables (Day Shift)
- Task Resource Assignment (Kim Lee is assigned to Review Loan Application task)
- Business Process Management: Modeling through Monitoring Using WebSphere V6.0.2 Products
- WebSphere business process management zone (IBM Developerworks)
- WebSphere Business Modeler certification exam 992 prep, Part 2: Model business processes
No comments:
Post a Comment