Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Getting Started : Overview

Overview
The Organization Modeler provided as a part of TIBCO Business Studio allows you to define the organizational structure of your enterprise and the relationships between the different components (for example, organization units and positions) within your organization.
Organization models are useful both:
The Organization Model as an Analysis Tool
In the analysis phase of a project you can use Organization Modeler to visualize the organizational structure that underpins a Process.
The structure of an organization is a fundamental aspect of how the organization works.
The structure of an organization is a key aspect in the operation of information systems like human resources, payroll and accounting and business process/workflow systems. These systems require a consistent view of the organization to operate efficiently.
However, maintaining a consistent view of the organization is difficult for two reasons:
Organization Modeler allows you to maintain a model of your enterprise’s organization structure in TIBCO Business Studio. It consists of elements that represent the organization’s entities, their attributes and the relationships between them.
Organization Modeler does not produce an organization chart; it does not identify named individuals. But it enables you to model your organization abstractly. Managers need to be able to develop robust models of their organization so that this information can be shared by people and systems.
Deploying the Organization Model
To be used at runtime an organization model must be deployed to a BPM server. In BPM an organization model is seen as part of an application. The application consists of a business process and any supporting material, which can include an organization model. One organization model can be used by multiple applications; your business might have different applications for different business functions, but all of them would need to reference a model of the same organization. See the implementation guide for your destination environment for details of how to deploy applications.
When you deploy an organization model, any Resources that you have defined are not deployed (with the exception of the Human Resource Type, which must exist and is always deployed). All other parts of the organization model as defined in TIBCO Business Studio are deployed. See Resources for further details.
Using the Organization Model at Runtime
At runtime in BPM, how an end user’s position is defined in the organization model can be used to determine what type of work is presented to them. Customized role-based clients can offer work to users depending on the Position they hold, the Capabilities or Privileges attributed to them, or both. For example, a user with an ‘LDAP Administration’ privilege could be offered all and only LDAP work.
About Organization Models
Using the Organization Modeler enables you to create a robust model of your organization within TIBCO Business Studio. It enables you to create the following elements that will make up your Organization Model:
Organizations represent both the organization you are modeling and any other enterprises that your organization may have a relationship with. For example, there may be a company your organization has outsourced part of its operation to.
Organization Units represent sub-divisions of an Organization. They are collections of positions which are associated together because they fulfil a business purpose within the organization. For example, an organization unit can be a department, project or location.
Positions represent a set of responsibilities for a job. Positions are created within Organization Units. For example, an Administrator in the Finance Department has different responsibilities from an Administrator in the Human Resources Department.
Groups represent job types within your organization; for example, Chef, Salesman, Doctor and Pharmacist. This is useful for example, if you want to allocate work to a group of people with a specific set of skills. Groups are equivalent to Roles in the Process Modeler - see the TIBCO Business Studio Process Modeling User’s Guide for details.
Capabilities can be applied to Positions and to Groups. They represent the skills within your organization; for example, ability to speak Spanish or customer care training.
Privileges represent the authority that Groups, Positions and Organization Units can have within your organization. They can have Qualifiers which indicate the level of the privilege. For example, an Approval privilege might have one qualifier to sign off expenses up to $500, or a higher level of qualifier for approval of budgets up to $10,000.
Locations represent the physical locations that are used by your organization.
Resources are used to specify items such as people, equipment or buildings.
Organization queries are specified either as strings of text, which is not checked or validated within Organization Modeler; or in Resource Query Language, which is validated.
System actions are actions that users perform at runtime but that need to be authorized. They are not defined within Organization Modeler, but you can associate Privileges with a list of available system actions in order to specify the level of authorization that a user needs to carry out an action.
Types, in the schema, represent typical elements within your Organization. This enables you to use the schema as a template for the different organizational components and ideas that your Organization contains.
Benefits of Organization Models
Creating an Organization Model enables you to provide the following benefits and capabilities:

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved