Elements of Organization Models

Using the Organization Modeler enables you to create a robust model of your organization.

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.
  • 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.