Benefits of Organization Models

Creating an Organization Model enables you to provide a number of benefits and capabilities.

Using the Organization Model, you can:

  • take advantage of the capabilities to distribute work at runtime to those users who are best suited to carry out a particular task, as determined by their position within the organization model or by privileges and capabilities defined within the organization model.
  • when you are defining a process, use expressions to define the participant who will carry out a task in terms of Organization Modeler entities.
  • model the way people are organized together within the organization. This is useful as it enables you to see how people work together and how work is allocated.
  • model both hierarchical relationships within the organization and also the associations that exist between cross-functional teams.
  • model virtual or temporary project teams and positions. This is useful for example, as you can create project teams irrespective of their physical locations or job status.
  • specify locations so that you can view how your organization is distributed across its various locations.
  • specify privileges so that you can view the chains of authority in your organization. Authority is not always hierarchical; it is often given for different purposes. There may be multiple chains of authority within an organization.
  • specify the skills (capabilities) you have within your organization so that you can view what skills are available and what skills your organization may need to acquire.
  • specify types for certain elements within the organization. Some extended enterprises refer to organizational concepts differently, for example, region vs. district. By specifying types for particular elements, you create a generic schema for your Organization Model that enables it to be exchanged with other systems. Using types also gives you the ability to add custom attributes and custom elements to your organization schema.
  • specify attributes for types. You can specify an attribute of telephone number or email address for a resource type, for example, and then values for that attribute can be assigned to each resource of that type.