In this video we talk about Positions and Org Groups in YAWL. These are two further components of the YAWL organisational model. We define an example org chart in the YAWL control centre. The zip file below contains a final ybkp file with the org chart in YAWL.
You can find the supplementary material here.
Hello! Welcome back to the next YAWL tutorial! This one is on org groups and positions. So this is the next component of the YAWL organizational model that you can see on the slide behind me. On this slide, you can see that participants can hold any number of positions. Positions can report to other positions. So this is the relation to the next higher in the hierarchy and positions can also belong to one or more org groups. And all groups form a hierarchy by themselves. The reports to hierarchy and the positions hierarchy can be aligned but don't have to be. So today we will show you how to define such a hierarchy in the YAWL control center. We will not build a workflow this time. Let's draw an organizational chart with some organizational structures and some positions.
So there is a software division. The top organizational structure here and a position called vice president and below that we have a programming department. And perhaps some other structures here. And in the programming department there is a manager. And below that we have team A and team B. And in these teams we have programmer A1, programmer A2, and programmer B1, B2. And now these programmers report to the manager. And the manager reports to the vice president. Let's now enter the org chart we have created in the YAWL control center. So we login as administrator and we go to org data and there, we start with the org groups. And the first or group we will enter is the software division.
And the software division or we have to press new first. So new software division and then the group type is division here and it belongs to no other or group. And we add this. Okay! The next one is the programming department. So we press new, programming department, and this is a department and it belongs to the software division. We add this one. Tthen team A. Team A is a team and this belongs to the programming department. And likewise team B is a team and belongs to the programming department. Now that we have the org groups, we can enter the positions. So we start with the vice president, go to the positions tab: new vice president.
And notice now that we cannot enter the org group at the moment. This is strange. Um ... we first have to add this vice president position and then now we can select the or group. So we say the vice president belongs to the software division. And we can save. The next one is the manager. The manager belongs to the programming department and reports to the vice president. Then programmer A. Programmer A1 is a member of the team A and reports to the manager. And the next one is programmer A2 is member of team A and reports to the manager. And then programmer B1 and programmer B2, team B, and programmer B2 reports to the manager.
Okay! Now they're all in. Before we created the org chart, we have in fact created a user. And the user also has a role and so we need that in order to test our positions and or groups with the workflow. So let's now go to the YAWL editor and select a task here and go to the resourcing.
And you can see, we can enable system offer now. And we offer this to the role programmer. And then in the org structures, we now have org groups and positions. So for example we can say that this should be offered to a member of team A.
And that's how it works. So you've seen that organizational structures and positions are quite expressive and that they are part of every personal management system and this is the bridge from the more role-based workflow into the organization. That's all for today! See you next time!