5.Tib Bstudio Om User

8/3/2019 5.Tib Bstudio Om User

1/108

TIBCO Business Studio

Organization Modeler Users Guide

Software Release 3.5.2September 2011


2/108

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSEAGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USERLICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THESOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARELICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATEDIN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMSAND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND ANAGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws andtreaties. No part of this document may be reproduced in any form without the written authorization of TIBCOSoftware Inc.

TIBCO, The Power of Now, TIBCO Enterprise Message Service, TIBCO ActiveMatrix and TIBCO Silver areeither registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

All other product and company names and marks mentioned in this document are the property of their

respective owners and are mentioned for identification purposes only.All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFICOPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BEINCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKEIMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED INTHIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDINGBUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright 2005-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information


3/108

TIBCO Business Studio Organization Modeler Users Guide

Contents | iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Changes from the Previous Release of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The Organization Model as an Analysis Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Deploying the Organization Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Using the Organization Model at Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

About Organization Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Benefits of Organization Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

About the Organization Modeler Diagram Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Concepts and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Organization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Hierarchy and Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Capability and Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Resources and BPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

System Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

The Organization Modeler Default Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


4/108


iv | Contents

Chapter 3 Creating an Organization Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating an Organization Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Creating an Organization Model in an Existing Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Creating a Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using Your Own Schema Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Creating Types in the Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Using the Organization Modeler Diagram Editors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Adding Objects in Organization Modeler Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Adding Notes and Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Tailoring the Appearance of Organization Modeler Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Opening an Organization Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Creating an Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Creating an Organization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Creating a Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Creating a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Creating Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Creating Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Creating a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Creating a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Using a Schema in an Organization Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Exporting Organization Model Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Viewing Organization Model Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 4 Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Properties View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Properties View for the Organization Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Properties View for the Organization Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95


5/108


|v

Preface

This guide is intended for business analysts. It describes how to use OrganizationModeler in TIBCO Business Studio. No other software knowledge is required.

Topics

Changes from the Previous Release of this Guide, page vi

Typographical Conventions on page vii

Connecting with TIBCO Resources, page ix


6/108


vi | Preface

Changes from the Previous Release of this Guide

This section itemizes the major changes from the previous release of this guide.

In About Data Types on page 28 in the data types table, EnumerationSubSethas changed to EnumSet, and Enumeration is now Enum.


7/108


Typographical Conventions |vii

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

STUDIO_HOME

Many TIBCO products must be installed within the same home directory. Thisdirectory is referenced in documentation as TIBCO_HOME. The default value ofTIBCO_HOME depends on the operating system. For example, on Windows 7

systems, the default value is C:\Program Files (x86)\tibco

TIBCO Business Studio installs into a directory within . Thisdirectory is referenced in documentation as STUDIO_HOME. The default valueof STUDIO_HOME depends on the operating system. For example on Windows 7systems, the default value is C:\Program Files(x86)\TIBCO\studio-bpm-35.

code fontCode font identifies commands, code examples, filenames, pathnames, andoutput displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

fontBold code font is used in the following ways:

In procedures, to indicate what a user types. For example: Type admin.

In large code samples, to indicate the parts of the sample that are of

particular interest.

In command syntax, to indicate the default parameter for a command. Forexample, if no parameter is specified, MyCommand is enabled:MyCommand [enable | disable]

italic font Italic font is used in the following ways:

To indicate a document title. For example: See TIBCO ActiveMatrix

BusinessWorks Concepts.

To introduce new terms For example: A portal page may contain severalportlets. Portlets are mini-applications that run in a portal.

To indicate a variable in a command or code syntax that you must replace.For example: MyCommandPathName


8/108


viii | Preface

Keycombinations

Key name separated by a plus sign indicate keys pressed simultaneously. Forexample: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after theother. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, forexample, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to applythe information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example,data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Contd)

Convention Use


9/108


Connecting with TIBCO Resources | ix

Connecting with TIBCO Resources

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, andresident experts, a place to share and access the collective experience of theTIBCO community. TIBCOmmunity offers forums, blogs, and access to a varietyof resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO Documentation

After you join TIBCOmmunity, you can access the documentation for allsupported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, pleasecontact TIBCO Support as follows.

For an overview of TIBCO Support, and information about getting startedwith TIBCO Support, visit this site:

http://www.tibco.com/services/support

If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a username, you can request one.
http://www.tibcommunity.com/http://docs.tibco.com/TibcoDochttp://www.tibco.com/services/supporthttps://support.tibco.com/https://support.tibco.com/http://www.tibco.com/services/supporthttp://docs.tibco.com/TibcoDochttp://www.tibcommunity.com/


10/108


x | Preface


11/108


|1

Chapter 1 Getting Started

Topics

Overview, page 2

About the Organization Modeler Diagram Editors, page 7


12/108


2 | Chapter 1 Getting Started

Overview

The Organization Modeler provided as a part of TIBCO Business Studio allowsyou 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:

In the analysis phase of a project, when you are defining the businessprocesses; and

If you are using BPM as your deployment destination, at runtime.

The Organization Model as an Analysis Tool

In the analysis phase of a project you can use Organization Modeler to visualizethe organizational structure that underpins a Process.

The structure of an organization is a fundamental aspect of how the organizationworks.

It shows how people are organized to achieve the objectives of the business.

It models the relationships between enterprise systems relevant to theorganization.

It models the relationships between the different departments that describethe day to day operation of the organization.

It determines how the work that arises from the business processes modeledin TIBCO Business Studio is allocated between different departments andpositions within your organization.

It identifies both concrete resources - people and buildings, for instance - andabstract resources such as roles.

The structure of an organization is a key aspect in the operation of information

systems like human resources, payroll and accounting and businessprocess/workflow systems. These systems require a consistent view of theorganization to operate efficiently.

However, maintaining a consistent view of the organization is difficult for tworeasons:

Modern enterprises are often spread across different locations and haverelationships with extended enterprises. People work in cross-functional

teams which may be spread across different locations and enterprises. This


13/108


Overview |3

makes it hard to identify resources when allocating work within theorganization.

Organizations no longer consist of one global scheme. Organizations are split

geographically, by product or by markets and these co-exist within onecorporate entity.

Organization Modeler allows you to maintain a model of your enterprisesorganization structure in TIBCO Business Studio. It consists of elements thatrepresent the organizations 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 thatthis 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 applicationconsists of a business process and any supporting material, which can include anorganization model. One organization model can be used by multipleapplications; your business might have different applications for different

business functions, but all of them would need to reference a model of the sameorganization. See the implementation guide for your destination environment fordetails of how to deploy applications.

When you deploy an organization model, any Resources that you have definedare not deployed (with the exception of the Human Resource Type, which mustexist and is always deployed). All other parts of the organization model asdefined in TIBCO Business Studio are deployed. See Resources on page 20 for

further details.

Using the Organization Model at Runtime

At runtime in BPM, how an end users position is defined in the organizationmodel 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 Positionthey hold, the Capabilities or Privileges attributed to them, or both. For example,

a user with an LDAP Administration privilege could be offered all and onlyLDAP work.

Another way to produce an organization model in TIBCO Business Studio is byrefactoring a process to produce an organization. For more details on this, see theTIBCO Business Studio Process Modeling Users Guide.


14/108



About Organization Models

Using the Organization Modeler enables you to create a robust model of yourorganization 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 anyother enterprises that your organization may have a relationship with. Forexample, there may be a company your organization has outsourced part ofits operation to.

Organization Units represent sub-divisions of an Organization. They arecollections of positions which are associated together because they fulfil a

business purpose within the organization. For example, an organization unitcan be a department, project or location.

Positions represent a set of responsibilities for a job. Positions are createdwithin Organization Units. For example, an Administrator in the FinanceDepartment has different responsibilities from an Administrator in theHuman Resources Department.

Groups represent job types within your organization; for example, Chef,Salesman, Doctor and Pharmacist. This is useful for example, if you want toallocate work to a group of people with a specific set of skills. Groups areequivalent to Roles in the Process Modeler - see the TIBCO Business StudioProcess Modeling Users Guide for details.

Capabilities can be applied to Positions and to Groups. They represent theskills within your organization; for example, ability to speak Spanish orcustomer care training.

Privileges represent the authority that Groups, Positions and OrganizationUnits can have within your organization. They can have Qualifiers whichindicate the level of the privilege. For example, an Approval privilege mighthave one qualifier to sign off expenses up to $500, or a higher level of qualifierfor 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 QueryLanguage, which is validated.

System actions are actions that users perform at runtime but that need to beauthorized. They are not defined within Organization Modeler, but you canassociate 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.

O i |5


15/108


Overview |5

Types, in the schema, represent typical elements within your Organization.This enables you to use the schema as a template for the differentorganizational components and ideas that your Organization contains.

Benefits of Organization Models

Creating an Organization Model enables you to provide the following benefitsand capabilities:

take advantage of the capabilities of BPM to distribute work at runtime tothose users who are best suited to carry out a particular task, as determined by

their position within the organization model or by privileges and capabilitiesdefined within the organization model.

when you are defining a process, use expressions to define the participantwho will carry out a task in terms of Organization Modeler entities.

model the way people are organized together within the organization. This isuseful as it enables you to see how people work together and how work isallocated.

model both hierarchical relationships within the organization and also theassociations that exist between cross-functional teams.

model virtual or temporary project teams and positions. This is useful forexample, as you can create project teams irrespective of their physicallocations 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 fordifferent purposes. There may be multiple chains of authority within anorganization.

specify the skills (capabilities) you have within your organization so that youcan 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 genericschema for your Organization Model that enables it to be exchanged withother systems. Using types also gives you the ability to add custom attributesand custom elements to your organization schema.



16/108



specify attributes for types. You can specify an attribute of telephone numberor email address for a resource type, for example, and then values for thatattribute can be assigned to each resource of that type.

About the Organization Modeler Diagram Editors |7


17/108



About the Organization Modeler Diagram Editors

Two graphical editors are provided for producing organization diagrams: An Organization Model Editor for the root Organization Model

An Organization Editor for the diagrams of each Organization included inthe Organization Model

The Organization Model Editor shows a high-level view of the organization ororganizations that you have created. The following example shows anOrganization Model diagram which includes two organizations, one being yourown organization and the second a representation of an external organizationwith which your organization has dealings, in this case an outsourcing company.

Note that an Association has been created between two organization units, one ineach organization, that have a business relationship with each other.

When you create an Organization Model Diagram, a new Organization is

automatically created within the Organization Model. The Organization Editorfor this default Organization opens automatically after you click Finish on theCreate New Organization Model wizard. To view the parent Organization ModelEditor you can navigate to it using the following methods:

Double-click on an existing Organization Model.om file in the ProjectExplorer,

Right-click on an existing Organization Model.om file in the Project Explorer,

and select Open or Open With > Organization Model Diagram Editing,



18/108



From the Organization Editor displaying any Organization in thatOrganization Model, click on the shortcut arrow that is displayed on the

badge.

The Organization Editor shows a more detailed view of one Organization,including the Organization Units and Positions that it includes, and therelationships between them.

The Organization Editor opens:

Automatically for the default Organization that is created when you create anew Organization Model Diagram,

When you double-click on the representation of an Organization in theOrganization Model Editor,

When you double-click on an Organization in the Project Explorer,

The small icon showing a letter i on the title badge of the Organization in thisillustration indicates an information message. In this case it is displayed because

the Organization has no Type assigned to it.



19/108


g g |

From the Organization Model Editor, when you click on the shortcut arrowthat is displayed on the representation of each Organization within the model.



20/108


|

|11


21/108


|

Chapter 2 Concepts and Definitions

This section defines concepts and terminology related to TIBCO Business StudioOrganization Modeler.

Topics

Organization, page 12

Organization Unit, page 13

Hierarchy and Association, page 14

Position, page 15 Group, page 16

Capability and Privilege, page 17

Locations, page 19

Resources, page 20

Queries, page 22

System Actions, page 23

About Data Types, page 28

Schema, page 29

12 | Chapter 2 Concepts and Definitions


22/108


Organization

An Organization represents the top layer of your Organization Model.Organization Units are contained within Organizations.

You can create many Organizations in the Organization Model. This is usefulbecause you may have an enterprise that has relationships with other enterprises.Part of the operation may have been outsourced to another company, for example.In this situation, you can create an Organization in your Organization Model foreach enterprise that your Organization has a relationship with.

An Organization does not necessarily have to represent an organization orenterprise, however. It can represent a department or project. It may make sensefor your business model to create a project as an Organization if the project islarge enough and it consists of several Organization Units, for example.

An Organization can contain many Organization Units.

There are various properties you can assign to an Organization. You could assignan effective start date and end date. This is useful if the out-source company only

has the contract for a set period of time, for example. See Organization Propertieson page 77 for more information.

Organization Unit |13


23/108


Organization Unit

An Organization Unit represents resources that are associated together becausethey fulfil a business need within the organization. For example, an OrganizationUnit can be a department, project or location. Different Organization Unit Typesare provided in the default Schema, and if it suits your organizational structureyou can use them for different levels of organization or other different sorts ofunit that might be present.

An Organization Unit is made up of Positions. A Position represents a set ofresponsibilities for a job of work to be performed in an Organization Unit. AnOrganization Unit can have many Positions.

Organization Units can be linked by relationships. These relationships can linkOrganization Units within the same Organization, or in different Organizations inthe same Organization Model. (They do not link one Organization to another.)

Relationships can be hierarchical or otherwise. In the Organization Modelerdiagram editor they are represented by Hierarchy or Association connections - seeHierarchy and Association on page 14.

An example of a Customer Services Organization Unit that contains SubOrganization Units and Positions is shown below.

You can specify privileges and system actions for an Organization Unit. Anexample of a privilege might be that the Accounts Department can authorizeexpenses up to $500.

For each Organization Unit, there are various properties you can assign. Forexample, you can specify the location of the Organization Unit and how long it

should exist for. See Organization Unit Properties on page 78 for moreinformation.



24/108


Hierarchy and Association

In the Organization Editor, the relationships between Organization Units aredenoted by two similar types of Organization Unit Relationship:

Hierarchy. This indicates a hierarchical relationship, for example between adepartment and its sub-departments.

Association. This can be used to indicate any sort of non-hierarchicalrelationship, depending on your requirements. For example, relationships

between Organization Units may be based on factors such as resource or work

allocation.In the diagram editor, you can see whether a relationship is hierarchical or not

because a Hierarchy is represented by a solid line with an arrowhead, anAssociation by a dotted line. This difference is controlled by one property of theOrganization Unit Relationship, the IsHierarchical property - see Hierarchy andAssociation Properties on page 80. You can edit the value of this property tochange a relationship from Hierarchy to Association, or vice versa, simply bychecking or unchecking a box on the General tab in the Properties view.

The following illustration shows a hierarchical relationship between theCustomer Services Organization Unit and its sub-divisions Call Center and BackOffice, and an Association between Customer Services and Sales.

Position |15


25/108


Position

A Position represents a set of responsibilities for a job of work to be performed inan Organization Unit. A Position can only be assigned to one Organization Unit.It represents the responsibilities of the position within the context of theOrganization Unit. The position of Administrator within the Human ResourcesOrganization Unit may be different to the same position in the FinanceOrganization Unit, for example. An Organization Unit can contain manyPositions.

You can specify an ideal number of people to have in a Position by specifying the

Number field. This does not mean that you must have this number of resources inthat position or that only resources with these requirements can fulfill thisposition. This just enables you to specify what the ideal requirements of theposition are.

You can specify privileges and system actions associated with a Position. As anexample of privileges the Accounts Organization Unit may be able to sign offexpenses up to $500 for example, but the Accounts Manager may be authorized to

sign off expenses up to $1000. Whether positions inherit the privileges specifiedfor an Organization Unit is determined by the run-time environment to which theOrganization Model is exported. It is not defined in the Organization Modeleritself.

For each Position, there are various properties you can assign. For example, youcan specify the location of the Position and how long it should exist for, and youcan also specify Capabilities and Resources for a Position. See Position Propertieson page 82 for more information.



26/108


Group

A Group represents a job type within your organization. It allows resources to begrouped by their job characteristics. These may be general job characteristics orcharacteristics that apply in a particular context. For example, the A-Z InsuranceCompany might have groups for Loss Adjuster or Claims Handler. At the sametime, you may have employees who have specializations in the Home Insurancesector. You may want to group these employees together based on thesespecializations, as shown below.

You do not assign Positions within the organization model, nor named users, to

Groups when you are working with Organization Modeler. Users are assigned togroups at runtime using the Organization Browser in TIBCO Workspace.

Groups can be hierarchical, in other words a Sub Group can be created from aparent Group, or exist along side each other. All members of a sub-group aremembers of the parent Group.

You can specify system actions, capabilities and privileges for Groups. A Groupcan have as many Capabilities as you want. This is useful for example, if you

require resources with particular capabilities. You can group resources togetherbased on their Capabilities.

For each Group, there are various properties you can assign. For example, you canspecify a description and purpose for the Group. See Group Properties on page 84for more information.

Capability and Privilege |17


27/108


Capability and Privilege

Capabilities represent the skills that are available within an organization, forexample language skills or possession of a professional qualification. Once aCapability has been created it can be assigned to Groups and Positions.Capabilities assigned to a Group or Position represent "entry criteria" for thatgroup or position: it is necessary to have that capability in order to be a validmember of the group or position.

Privileges represent the authority that an Organization Unit, Position or Groupcan have within an organization, such as the authority to approve expenditure up

to a defined amount. You can assign Privileges to Groups, Positions andOrganization Units. Privileges may be based on budgets and spending,work/product approval, resource allocation, or other factors. SpecifyingPrivileges enables you to see the chains of authority throughout yourorganization.

You can also associate a system action with a privilege. System actions are tasksthat might need to be authorized in some way. Like Privileges, they can be

assigned to Organization Units, Positions or Groups. At run time, only users whohold the associated privilege are then allowed to execute that system action. SeeSystem Actions on page 23.

Whether positions inherit the privileges specified for an Organization Unit isdetermined by the run-time environment to which the organization model isexported. It is not defined in the Organization Modeler itself.

You can create categories for Capabilities and Privileges. Categories are a way of

grouping your Capabilities and Privileges into meaningful units. You could createa Category for Language and then create Capabilities within that category foreach language spoken in your organization; for example French, Polish, Chineseetc.

You can add extra information about a Capability or Privilege by assigning aQualifier. For example, you may have created a Capability that represents anexam qualification but for a particular Position you may want to qualify that

Capability by specifying a grade as well. To add qualifiers, check the Hasqualifier box on the General tab in the Properties view. The Qualifier tab thenbecomes available. On that tab you can name and describe the qualifyinginformation, and specify a data type that determines its allowable values, and ifrequired specify a default value. For a description of the data types thatqualifying information can have, see About Data Types on page 28. Then, whenyou assign the Capability or Privilege to a Group or Position, you can specify thevalue of the Qualifier by typing it into the Value field on the Capabilities or

Privileges tab.



28/108


You can assign other properties to Capabilities and Privileges. For example, youcan specify a purpose and/or description for the Capability or Privilege, seeCapability Properties on page 86 and Privilege Properties on page 87 for moreinformation.

Locations |19


29/108


Locations

Locations represent the locations that your organization uses. A location may be aplace, an office building, or even a room in an office, depending on yourrequirements. You can create locations in the Organization Model and then assignthem to Organizations, Organization Units and Positions. This enables you to seehow your organization is distributed across its various locations.

You can also specify other properties for Locations. See Location Properties onpage 88 for more information.



30/108


Resources

Resources are used to specify items such as people, equipment or buildings. Youcan use Resources within your organization model to identify such items anddefine how they relate to Organization Units and Positions.

When you create a resource, you can assign various properties to it. See ResourceProperties on page 88.

A resource can be assigned a Resource Type if Resource Types are defined in yourschema, and will have any Attributes defined for that type. For example, you may

want to define attributes of FirstName and Surname for a Resource thatrepresents an employee, or TelephoneNumber for both an employee and foranother type of Resource that represents a meeting room. See Schema on page 29for more information about Schemas and Resource Types.

The following Resource Types are provided in the default Schema:

Durable Resource Type. You can use this for items like buildings which have along lifespan.

Consumable Resource Type.

Human Resource Type. A Human Resource Type must always be present inthe Schema, and there can be only one Human Resource Type present in theschema.

SeeCreating a Schema on page 41 for details of creating a Schema with or withoutusing the standard Types. See Resource Type Properties on page 92 for moredetails of the Human Resource Type.

Resources and BPM

Any Resources that you have defined are not exported to BPM, and are not usedat runtime.

The only exception to this is that the Human Resource type, and any attributes

defined for it, are exported to BPM.

Therefore, a Human Resource type must always be present in the Schema. Even ifyou choose not to include the standard Types in your Schema, a Human Resourcetype is always present, and it cannot be deleted from the Schema.

Resources |21


31/108


Entities within the organization model are mapped to Resources as defined inTIBCO Workspace. You can:

Map BPM Resources, which represent actual user IDs obtained from an

LDAP-compliant directory, to Positions and Groups in the organizationmodel,

Map attributes assigned to the organization models Human Resource Type toLDAP attributes in the LDAP sources you have used.

See the chapter "Using the Organization Browser" in the TIBCO Workspace UsersGuide for details of mapping resources.

This means that any sort of information that you have reflected in definingResources within Organization Modeler, including for example if you have usedResources to represent anything other than users, will not be represented in BPMafter deployment.



32/108


Queries

Queries are a way of identifying an entity within the organization model to use asa suitable participant for a task in a business process.

You can specify queries either:

As strings of text. These are not checked or validated within OrganizationModeler. A business analyst might enter the query as free text, which asolution designer can implement when the analysis is implemented as aprocess for a specific destination environment,

As Resource Query Language (RQL). This is a scripting language which youcan use to write queries specifying which entity within the organizationmodel should be selected for work allocation. It is described in the BPMimplementation documentation. Organization queries entered in RQL arevalidated in TIBCO Business Studio.

System Actions |23


33/108


System Actions

System actions are actions that a user may wish to perform at runtime but thatneed to be authorized, or need to be restricted to users with a certain level ofauthority. These actions might include, for example re-allocating work-items,skipping work-items, viewing another users work list, or administeringresources.

This authorization is implemented by associating system actions with privilegeswithin Organization Modeler. See Capability and Privilege on page 17 for moredetails about privileges. See the BPM Concepts documentation for an introduction

to system actions.

In Organization Modeler:

For the Organization Model, the System Actions tab of the Properties viewlists all the system actions that are available, and any privileges with whicheach is associated.

For Organization Units, Positions and Groups, the System Actions tab of the

Properties view lists the subset of system actions that are available for thatclass of entity, and any privileges with which each is associated.

In all these cases you can associate a system action with one or more privileges.As described in Capability and Privilege on page 17, privileges can havequalifiers which determine the level of the privilege. At run time, only users whohold the associated privilege with any required level of qualifier (or if more thanone privilege is associated with a particular system action, users who hold all theassociated privileges) are then allowed to carry out that system action.

At runtime, BPM maintains a list of system actions and of privileges, as defined inthe organization model, and thus determines whether a user is authorized tocarry out a particular action.

As well as possessing the correct privileges, users may need to belong to anappropriate user access set in order to perform a particular system action. See theTIBCO Workspace documentation for more information on user access sets.

The Organization Admin system action allows the user to see organizationmodels other than the one they are part of, and allows them to view process

instances started by members of these organizations.



34/108


The following system actions can be associated with privileges at theOrganization Model level:

Application Configuration Update configuration files in deployedapplication.

Auto Open Next WorkItem

Open the next work item automatically after theprevious one is opened

Browse Model Browse the organization model

Cancel Process Instance Cancel a process instance.

Cancel Work Item Cancel a work item.

Close Other ResourcesItems

Close work items that are currently allocated toother users

Create Resource Admin Create resources and edit resource information.

Delete LDAP Admin Delete LDAP containers.

Delete Resource Admin Delete resources.

Export LDAP Admin Export LDAP container and resource mappinginformation.

Handle Process Migration Authorizes the migration of a process from oneversion to another. If you do not have the system

action set, you cannot migrate the process.

Import LDAP Admin Import LDAP container and resource mappinginformation.

LDAP Admin List resources in an LDAP container.

List Process Template

Audit Trail

Not currently used.

Open Other ResourcesItems

Not currently used.

Open Work Item AuditTrail

Not currently used.

Organization Admin Allows the user to see organization models otherthan the one they are part of.

System Actions |25


35/108


Pend Work Item View "pended" work items, i.e., work items thathave been hidden until a specified date/time, orperiod of time has expired.

Purge Process Instances Not currently used.

Query Process Instance View list of process instances.

Query Process Template View list of process templates.

Read Parameters View and edit resource attributes in theOrganization Browser.

Read Push Destinations View and edit push destinations.

Reallocate To Offer Set Reallocate the work item to the offer set

Reallocate Work Item ToWorld

Reallocate the work item to all users

Resolve Resource Used by many functions to access resourceinformation.

Resource Admin View list of resources in a group or position.

Resume Process Instance Resume an instance of a process that has beensuspended

Schedule Work Item Schedule a work item

Set Deadline Expiration Set the time for a deadline to expire

Set Priority Set the priority for a work item

Set Resource Order FilterCriteria

Not currently used.

Show Process InstanceAudit Trail Not currently used.

Skip Work Item Skip a work item in a work list

Start Business Service Start an instance of a business service.

Start Process Start an instance of a process

Suspend Process Instance Suspend a currently running instance of a process



36/108


The following system actions are considered "scoped", that is, they are set onspecific groups, organization units, and positions using the OrganizationModeler. The scoped system actions are specifically used to control access to, andfunctions from, supervised work views.:

Suspend Work Item Not currently used. (There is no means tosuspend a work item -- you can suspend aprocess instance, which causes associated work

items to become suspended -- but no separatefunctions for work items.)

User Admin

(Business Studio actuallyshows that as "UserSettings")

Controls whether or not user settings will bepersisted.

View Work List Create a supervised work view that eithercontains work items offered to an organizationalentity, or that are currently in the Inbox of anindividual resource.

Work Item Allocation Allocate a work item

Write Parameters Edit resource attributes in the Organization

Browser.

Write Push Destinations

Close Other Resources Items Controls whether you can choose tocancel a work item in a supervisedwork view for another resource.

Open Other Resources Items Not currently used.

Open work items that are currently

allocated to other users

Reallocate To Offer Set Controls whether you can choose toreallocate a work item to a specificperson in the original offer set.

Reallocate Work Item To World Not currently used.

Reallocate the work item to all users

System Actions |27


37/108


Set Resource Order Filter Criteria Not currently used.

Set filter criteria for a resource order

View Work List Controls access to supervised workviews:

To create a supervised work viewfor an organizational entity, youmust possess the privilegeassigned to the system action,BRM.viewWorkList, on the group,

organization unit, or position. To create a supervised work view

for an individual resource, youmust possess the privilegeassigned to the system action,BRM.viewWorkList, on a specificposition to which the resource has

been mapped.

Work Item Allocation Not currently used.

Allocate a work item


About Data Types


38/108


About Data Types

The following elements of an Organization Model can have data types:

Schema Type attributes, see Attributes on page 33.

Qualifying information for Capabilities and Privileges, see Capability andPrivilege on page 17.

The table below describes the data types that these elements can have.

Type Description

Text Any combination of alphanumeric characters.

Integer A whole number, including zero and negative numbers.

Boolean A value of True or False, or blank.

Decimal Any number, positive or negative, up to the number ofdecimals you specify.

DateTime A date and time in the format of the locale on yourmachine.

Date Any date in the format of the locale on your machine.

Time Any time in the format of the locale on your machine.

EnumSet A data type that can contain a list of values. Selectingthis type enables you to specify a set of enumeratedvalues.

Enum An enumerated type. Selecting this type enables you tospecify an enumerated value. Each Enum is one of thelist of values that make up an EnumSet.

Schema |29

Schema


39/108


Schema

Organization Modeler enables you to create an embedded Schema for use in thedefinition of your organization model.

Using a Schema, you can specify Types that you intend to use for certain elementswithin your organization. By setting up these types, you can create a genericmodel or template for your organization model. Defining different Types ofOrganization, Organization Unit, Position, Resource and so on, and choosing anddefining Attributes for those Types, enables you to extend the model provided bythe default schema until it is a close representation of the components that make

up the organization that you wish to model.

The containment relationships between components can also be defined in theschemas Types. For example, from an Organization element that you haveassigned an Organization Type, Organization Modeler enables you to create achild Organization Unit of a defined type, because the relationship between thetwo Types is described in the schema.

An example of this is shown below. One type of Organization - the Public

Company organization type - is defined in the standard Schema. One type ofOrganization Unit element - Head Department - is defined as a Member of thatOrganization Type. If your Organization is defined as a Public Company, and youright-click in the Organization Editor to add an Organization Unit, you can selecteither an un-Typed Organization Unit, or a Head Department unit.

This allows you to create specific organizational structures in a Schema, so thatwhen you need to create an instance of that structure in your organization model,

you can use the structures defined in the Schema. For example, you may want tocreate an organization structure for temporary projects that consists of specificOrganization Units and Positions. You can create this structure in a Schema thencreate an instance of a temporary project based on the Schema. See Using aSchema in an Organization Model on page 69 for more information.

The benefits of Schemas are:

They can be used as templates for organization models that need to be

exchanged between systems. Some extended enterprises refer to


organizational concepts differently, for example, "region" vs. "district". By


40/108


g p y p g yspecifying types for particular components, you create a generic schema foryour Organization Model that enables it to be exchanged with other systems.

They enable you to create a language or vocabulary to express theorganization concepts that are applicable to your organization.

They enable you to create additional semantic data for your existingorganization concepts. For example, for a Position whose type is Manager,you could create an attribute called bonus to specify what type of bonusshould be given.

When you use a Schema within the Organization Modeler you can either:

Use the default Schema, which comes delivered with standard Types for theschema elements,

Create an empty Schema which does not contain any standard Types (exceptfor the Human Resource Type, which must always be present).

You can also decide to use a mixture of the two approaches by adding your owntypes to the default schema.

The Organization Modeler Default Schema

When you create certain components within your Organization Model, theOrganization Modeler enables you to allocate standard types to thesecomponents. Not all the components within the Organization Modeler have astandard type. The following table describes the components that have typesprovided in the default schema, what they are, and what members each of those

types contains:

Component Standard Type Unit Members Position Members

Organization Public Company Head Department

Organization Unit Department Type DepartmentBusiness Unit

Team

ManagerMember

Position Standard Position Type

Location Standard Location Type

Resource Human Resource TypeConsumable Resource TypeDurable Resource Type

Schema |31

When you create an Organization Model, you can decide whether to use the


41/108


Standard Types provided by the Organization Modeler, create new Types, orcreate your own Schema, depending on your requirements.

When a component that has a standard type defined for it is created, you canassign the type in the Properties View for the component. By default no type isassigned, as in the following illustration. You can assign a type by clicking

and selecting either the standard type or any other type that has beendefined.

The following diagram shows the default schema as it appears in the ProjectExplorer, if you chose to apply it when creating the project:



42/108


Schema |33

The following diagram shows how the default schema reflects an organizationalt t


43/108


structure.

In this diagram:

Public Company is the delivered Organization type.

Head Department is an Organization Unit type that is a member of PublicCompany. This type has a multiplicity defined as 0..1, so there can only be oneHead Department.

Department, Business Unit and Team are the other Organization Unit types

delivered. All of these need to be in a hierarchical relationship with anothertyped organization unit as their parent. The hierarchy does not need to be thatshown in the diagram, however; any one of the delivered organization unitscan be the parent of any other.

Attributes

For each of the Types in the schema you can create Attributes. An Attributeenables you to add some extra semantic information to each individual type. Forexample, for a Position whose type is Manager, you could create an Attributecalled bonus to specify what type of bonus should be given to this Position. TheStandard Position Type in the default schema has the attribute Contract Typeassigned to it. The Standard Location Type delivered in the default schema hasthe following attributes already defined:

Country


State


44/108


City

Street

Postcode

When you create an attribute, you must specify a data type that determines itsallowable values. For a description of the data types an attribute can have, seeAbout Data Types on page 28.

Members

For the Organization Type and Organization Unit Type you can create Members.The following table describes what Members you can create for each type:

The use of Members enables you to group together a set of Position Types andOrganization Unit Types into meaningful units. Once you have created your

Organization Unit Types and Position Types, you can create a template structureby grouping them together within an Organization Type or Organization UnitType as Members of that Type. An illustration of the Department type deliveredin the default schema is shown below.

Do not change the data type of an Attribute assigned to any Type in the Schema,once the Organization Model including it has been deployed to the BPM

Directory Engine. Since multiple versions of a Model can exist in BPM, changingthe data type of an Attribute between versions can create inconsistencies.

Type Members

Organization Type Unit Members

Organization Unit Type Unit Members, Position Members

Schema |35

The Department, Business Unit and Team Organization Unit Types have beengrouped together in the Department organization unit type as unit members of


45/108


grouped together in the Department organization unit type as unit members ofthe type. This means that when an Organization unit element is created in anOrganization Model using the default schema, these elements are available from

the Add Child menu, from the context menu or from the palette. This isillustrated below.

When you subsequently add an Organization Unit to your Organization diagram,you can select one of these Elements from the Element field on the General tab,and assign it to the new Organization Unit.

See Using a Schema in an Organization Model on page 69 for more information.

Multiplicity

You can specify whether TIBCO Business Studio needs to allow for multiplecopies of an element. The following table describes the multiplicity values youcan specify:

Indicator Meaning

0..1 No instances or one instance (optional).

0..n Multiple instances from zero to n where n isgreater than zero.

0..* Any number of instances; * denotes that there isno limit.


Indicator Meaning


46/108


n..m Multiple instances where n and m are zero ormore. For example:

1..21..*

The latter would mean that there must be atleast one instance, but there is no upper limit.

|37

Chapter 3 Creating an Organization Model


47/108


This section describes how to create a basic Organization Model using theOrganization Modeler in TIBCO Business Studio.

Topics

Creating an Organization Model, page 38

Creating a Schema, page 41

Using the Organization Modeler Diagram Editors, page 47

Opening an Organization Model, page 58

Using a Schema in an Organization Model, page 69

Exporting Organization Model Documentation, page 72

38 | Chapter 3 Creating an Organization Model

Creating an Organization Model


48/108


An Organization Model must be contained within a special folder. To do this, you

can either:

create a new Analysis Project or BPM Developer Project;

or:

add an Organization Model special folder to an existing project.

Creating a ProjectTo create an organization model in a new project:

1. Select File > NewAnalysis Project or File > New BPM Developer Project.

2. The New Project wizard is displayed. Enter a name for your project in theProject name field and click Next.

3. In the Asset Type Selection dialog, ensure that the Organization Model boxis checked. Check any other boxes that you require to create the componentsyou need for your project. Click Next.

4. The Organization Model dialog may be displayed next. However, if you

selected any items other than Organization Model in the Asset TypeSelection dialog, you may see other dialogs before this one is displayed.

This accepts default values for Location, ID, Version, Status and DestinationEnvironments. For more details about these fields and about the New Projectdialog, see the TIBCO Business Studio Process Modeling Users Guide.

Creating an Organization Model |39

In the Organization Model dialog, ensure that Create initial OrganizationModel is checked. In the Filename field, enter a name for the Organization


49/108


Model file. Click Finish.

5. If you are not already in the Modeling perspective, you are prompted toswitch to it. Click Yes to switch perspective.

Leave the Create default schema typesbox checked to use the deliveredschema.

Check the Apply default Organization Type to Organizationbox if you wantthe Organization Type delivered in the default schema to be applied to theinitial organization created. If not, leave it unchecked.

See Creating a Schema on page 41 for further details.


Creating an Organization Model in an Existing Project

To add an Organization Model to an existing project:


50/108


To add an Organization Model to an existing project:

1. Right-click the project where you want to add the Organization Model and

select New > Folder. The New Folder dialog is displayed.

2. In the Folder Name field, type Organization. Click Finish to close the dialog.

3. Right-click on the Organization folder and select Special Folders > Other >Use as Organization Models Folder. If you right-click on the Organizationfolder now, the option to create a new Organization Model is now available.

Creating a Schema |41

Creating a Schema


51/108


The Organization Schema is contained in the Organization Model file (named by

default organizationmodel.om, where organization is the name of the organizationfor which you are creating the Organization Model). See Schema on page 29 formore information about Schemas.

To create the default schema, when you are creating an organization model, eitheras part of creating a new project or separately, ensure that you leave the Createdefault schema types checkbox selected.


If you select the Apply default Organization Type to Organization checkbox,the default Organization Type (called Public Company) from the defaultschema is applied to the initial Organization that is automatically created as


52/108


schema is applied to the initial Organization that is automatically created aspart of this Organization Model. If you leave this checkbox empty, the

Standard Organization Type is not applied.Note that if you do not select Create default schema types, the Apply defaultOrganization Type to Organization checkbox is not available:

4. Click Finish. The default schema is created. It is displayed in the Project

Explorer as illustrated on page 31. See The Organization Modeler DefaultSchema on page 30 for more information.

Using Your Own Schema Types

If you want to create your own schema, follow the same procedure described inCreating a Schema on page 41, but do not select the Create default schema

checkbox. A schema is still created, but it does not include the standard typesprovided with the default schema. The only type created is one Resource type, theHuman Resource Type.

The following illustration shows what is visible in the Project Explorer when youhave created a non-default schema:

Note that unlike the Human Resource Type created in the default schema, thisone has no attributes defined.


Creating Types in the Schema

If you are building your own schema, you need to create the types that make it


53/108


up. If you are using the default schema provided, you can create new types to addto the schema in the same way as you would for a new schema. You can alsomodify the types provided. This enables you to extend the default schemaprovided by setting up additional attributes to define more closely the elementsthat make up the organization you wish to model.

Creating a Location Type

To create a location type, do the following:

1. In the Project Explorer, expand the Schema folder for your OrganizationModel.

2. In the Schema folder, right-clickLocation Typesand select Add Child >Location Type. A new Location Type is created.

3. Click the General tab in the Properties view. In the Label box, type the nameof the Location Type.

4. Click the Attributes tab. Click to add an attribute. Type in the name andselect a type for the Attribute from the Type drop-down list. See Attributes onpage 33 for more information about the types you can specify. You can alsoadd a default value for the Attribute, depending on your requirements.

5. Click to remove attributes.

Creating an Organization Type

To create an Organization type, do the following:


2. In the Schema folder, right-clickOrganization Typesand select Add Child >Organization Type. A new Organization Type is created.

3. Click the General tab in the Properties view. In the Label box, type the name

of the Organization Type.


4. To add an Organization Unit as a member to the Organization Type:

a. In the Unit Members box, click . Type the name of the member in theL b l fi ld S M b 34 f i f ti b t l t


54/108


Label field. See Members on page 34 for more information about elements.

b. To specify that the member should be of a particular Organization UnitType, click on the Type field and then click the button that then

becomes available.

c. The SelectType dialog is displayed. Click on the Organization Unit Typeyou require, and the click OK.

5. In the Multiplicity field, type in the multiplicity you want.

6. Click to remove Organization elements.

7. Click the Attributes tab. Click to add an attribute. Type in the name andselect a type for the Attribute from the Type drop-down list. See Attributes onpage 33 for more information about the types you can set for attributes. Youcan also add a default value for the Attribute, depending on yourrequirements.


Creating an Organization Unit Type

To create an Organization Unit type, do the following:


2. In the Schema folder, right-clickOrganization Unit Typesand select Add

Child > Organization Unit Type. A new Organization Unit Type is created.3. Click the General tab in the Properties view. In the Label box, type the name

of the Organization Unit Type.

4. To add another Organization Unit as a member to the Organization Unit Type:

a. In the Unit Members box, click . Type the name of the member in theLabel field. See Members on page 34 for more information about elements.

b. To specify that the member should be of a particular Organization UnitType, click on the Type field and then click the button that thenbecomes available.

c. The SelectType dialog is displayed. Click on the Organization Unit Typeyou require, and the click OK.



6. To add a Position as a member to the Organization Unit Type:

a. In the Position Members box, click . Type the name of the member inthe Label field See Members on page 34 for more information about


55/108


the Label field. See Members on page 34 for more information aboutelements.

b. To specify that the member should be of a particular Position Type, clickon the Type field and then click the button that then becomesavailable.

c. The SelectType dialog is displayed. Click on the Position Type yourequire, and the click OK.


8. Click to remove Position and Unit elements.

9. Click the Attributes tab. Click to add an attribute. Type in the name andselect a type for the Attribute from the Type drop-down list. See Attributes onpage 33 for more information about the types you can specify for Attributes.You can also add a default value for the Attribute, depending on yourrequirements.


Creating a Position Type

To create a Position type, do the following:


2. Right-click Organizationand select Add Child > Position Type. A newPosition Type is created.

3. Click the General tab in the Properties view. In the Label box, type the nameof the Position Type.

4. Click the Attributes tab. Click to add an attribute. Type in the name andselect a type for the Attribute from the Type drop-down list. See Attributes onpage 33 for more information about the types you can specify. You can also

add a default value for the Attribute, depending on your requirements.5. Click to remove attributes.

Creating an Organization Unit Relationship Type

To create an Organization unit relationship type, do the following:

1. In the Project Explorer, expand the Schema folder for your Organization

Model.


2. In the Schema folder, right-clickOrganization Unit Relationship Typesandselect Add Child > Organization Unit Relationship Type. A newOrganization Unit Relationship Type is created.


56/108


3. Click the General tab in the Properties view. In the Label box, type the nameof the Organization Unit Relationship Type.

4. Click the Attributes tab. Click to add an attribute. Type in the name andselect a type for the Attribute from the Type drop-down list. See Attributes onpage 33 for more information about the types you can specify. You can alsoadd a default value for the Attribute, depending on your requirements.


Creating a Resource Type

To create a resource type, do the following:


2. In the Schema folder, right-clickResource Typesand select Add Child >Resource Type

. A new Resource Type is created.3. Click the General tab in the Properties view. In the Label box, type the name

of the Resource Type.

4. Click the Attribute tab. Click to add an attribute. Type in the name andselect a type for the Attribute from the Type drop-down list. See Attributes onpage 33 for more information about the types you can specify. You can alsoadd a default value for the Attribute, depending on your requirements.


Using the Organization Modeler Diagram Editors |47

Using the Organization Modeler Diagram Editors


57/108


Organization Modeler provides two graphical editors for producing organization

diagrams:

An Organization Model Editor for the root Organization Model diagram

An Organization Editor for the diagrams of each Organization included in theModel

The Organization Model Editor shows a high-level view of the organization ororganizations that you have created. The following example shows an

Organization Model diagram which includes two organizations, one being yourown organization and the second a representation of an external organizationwith which your organization has dealings, in this case an outsourcing company.

The Organization Model Editor opens when you:

Double-click on an Organization Model .om file in the Project Explorer,

Right-click on an Organization Model .om file in the Project Explorer, andselect Open or Open With > Organization Model Diagram Editing,

From the Organization Editor displaying any Organization in thatOrganization Model, click on the shortcut arrow that is displayed on the

badge.


The Organization Editor shows a more detailed view of one Organization,including the Organization Units and Positions that it includes, and therelationships between them.


58/108


The Organization Editor opens:

Automatically for the default Organization that is created when you create anew Organization Model Diagram,

When you double-click on the header part of the representation of anOrganization in the Organization Model Editor,

When you double-click on an Organization in the Project Explorer,


From the Organization Model Editor, when you click on the shortcut arrowthat is displayed on the representation of each Organization within the model.


59/108


Adding Objects in Organization Modeler Diagrams

You can add objects to Organization Modeler diagrams in any of several ways:

Using the tools on the diagram editors palette

Using the pop-up icons

Using the context menu

Using the Project Explorer

Using the Palette

To add an object to an organization diagram, you can use the tools provided onthe diagram editors palette.

In the Organization Model Editor, the following tools are always available in thepalette:

Organization

Association


If you have applied a Schema to your organization model, and it contains anyOrganization Types, tools for adding these will also be available. For example, ifyou have used the standard Schema but added a new Organization Type to it,both the Standard Organization Type and the additional one will be available in


60/108


both the Standard Organization Type and the additional one will be available in

the palette, as in the following illustration.

In the Organization Editor, the following tools are always available in the palette:

Organization Unit

Position

Hierarchy

Association


Additional tools are available if you have applied a Schema to your organizationmodel. If you have applied the Standard Organization Type to the Organization,the palette contains the following tools for the elements that are defined in thatStandard Organization Type:


61/108


S O g o ype

Similarly, if the Organization that you are editing has a different or modified Typeapplied, tools are included in the palette for the elements that are defined for thatType. The following illustration shows an example. Here an Organization is usedthat has two Organization Unit Types defined.

The availability of these tools on the palette is dynamic; if you add a new Type tothe Schema, it is immediately made available on the palette.

To use any of these tools, you can either:

Select the required tool and drag and drop on to the diagram, or

Head Unit Member Unit

Manager Position

Member Position

Note that the Sub Unit element is not available from the palette.


Click on the required tool in the palette to select it, and click on the diagram.

Where you should drop, or click, depends on the object you are adding:

For Organization and Organization Unit (including Types of Organization


62/108


g g ( g yp g

Unit), use the empty part of the diagram. For Position (including Types of Position), drop into or click on the position

compartment of an Organization Unit - that is, the empty space below the titlebar.

For Hierarchy or Association, drop into or click on the Organization Unitwhere the connection is to start from, and drag the connection to theOrganization Unit where it is to end.

When you add an Organization, Organization Unit, or Position object, the Labelfield on the title bar is automatically selected. Enter a name for the object.

Using the Pop-up Icons

An alternative method of adding objects is to use the pop-up icons that areavailable. If you hover your mouse over the empty area of the diagram, an iconappears. In the Organization Model Editor, this is the Add Organization icon.Move your cursor on to the icon to display the Add Organization label as shownin the following illustration, and then click to create a new Organization in thediagram.

In the Organization Editor, hovering your mouse in the empty area produces theAdd Organization Unit icon, which works in the same way as the AddOrganization icon. Similarly, hovering your mouse over the Positioncompartment of an Organization Unit displays the Add Position icon, as shownin the following illustration.


You can add a connection between two objects in a diagram by clicking anddragging one of the handles that are displayed when you hover your cursor overthe object. Click the handle and drag to the object to which you want to connect,as shown in the following illustration.


63/108


Using the Context Menu

You can add objects to the organization diagram by right-clicking in theOrganization Editor and selecting the object you require from the context menuthat is displayed.

If you right-click on the background of the Organization Editor, you can select: An Organization Unit with no Type defined;

If the Organization has the Standard Organization Type set, a Head Unit,Member Unit, or Sub Unit;

If the Organization is set to another Type of Organization defined in theSchema, an Organization Unit of any of the Types defined for thatOrganization Type.

If you right-click on an Organization Unit in the diagram, you can select:

A Position with no Type defined;

This process creates a Hierarchy. If you want a non-hierarchical connection, youcan change it to an Association as described in Hierarchy and Association

Properties on page 80.


If the Organization Unit has an Organization Unit Type set, a Position of anyof the Types defined for that Unit Type.


64/108


Using the Project Explorer

You can also add objects to the diagram editor from the Project Explorer, by.

1. Selecting the parent in the Project Explorer.

5.Tib Bstudio Om User

Documents

Transcript of 5.Tib Bstudio Om User