Organization and Resource Models

A SIMPROCESS Organization and Resource Model (referred to here and in other SIMPROCESS documentation as an OrgModel) is an organization chart. It consists of components described below.

  • Org Nodes – Each Org Node represents part of the organization structure being modeled, which might be an individual, department, or other entity. Each Org Node contains fields for defining and describing it in the overall organization, and each can carry Resources with a subset of the characteristics of those defined in a SIMPROCESS model.
  • Links – Links connect Org Nodes and represent the relationships between them. The two types of Links are solid and dotted. A solid Link represents a direct reporting relationship between two Org Nodes, where one is the superior and the other is a subordinate. An Org Node may have only one direct superior; it may have an unlimited number of direct subordinates. A dotted Link represents a support relationship. There are no limits to the number of “supported superior” or “supporting subordinate” relationships that can exist for any Org Node.
  • Text Nodes – Text Nodes provide a convenient way of putting textual information on the graphical OrgModel to help document it and improve its appearance.

 

OrganizationModels

OrgModels are independent of any given SIMPROCESS model so they can be associated with multiple SIMPROCESS models. Likewise, multiple OrgModels can be used within a single SIMPROCESS model. It is a many-to-many relationship.

Why Use OrgModels?

Connect the Process to the Organization

Using SIMPROCESS, you model a “business process,” to include its resources and the entities which move through it, and then simulate the process in order to learn things about it and, ultimately, improve the process. However, the business process being modeled is frequently associated with an organization. Indeed, that organization may be related to multiple business processes, and its OrgModel might therefore lend itself to being assigned in multiple SIMPROCESS models. So the first part of the answer to the question is that creating an OrgModel and assigning it to a SIMPROCESS model allows you to “connect” the business process with a related organization.

Connect the Resources in the Organization to the Process

An organization often has Resources associated with specific parts. Each Org Node in an OrgModel could represent a person, a department, or some other concept needed to properly depict the organization being modeled. In the Demos/CityOrganization OrgModel, the organization is the fictional city of Metropolis, showing how the city’s day to day work gets done. There are other parts not reflected in this OrgModel, but the key organizational parts necessary to operate the city’s justice system are represented. Resources have been defined at various Org Nodes which are needed to accomplish the business of the city’s justice system.

Once an OrgModel is assigned to a SIMPROCESS model, its Resources will appear in that model alongside those which were locally defined. It then is possible to change these Resources’ costs, unit availability or other values originally set in the OrgModel Editor, and to specify additional properties supported directly in SIMPROCESS such as statistics collection, downtime and more.

See the Results

Having done this, not only is the organization from the OrgModel “connected” to the business process in SIMPROCESS, but the Resources themselves are now associated with the appropriate organizational parts. Having specified what statistics to collect, the costs of various Resources and other details, you can then simulate the model to gather the needed information and examine it via the Standard Report and other tools provided in SIMPROCESS. You now have the ability to connect this data back to the organization behind the business process.