A typical way of representing organizational structures is the organizational chart. In this chart, organizational units (as task performers) and their interrelationships are represented according to the structuring criteria selected.

Organizational units are the performers of the tasks that must be carried out in order to achieve the business objectives.

Organizational units are linked via relationships. The following figure shows an example.

For a more precise specification of the hierarchical relationships, a distinction is made between various connection types that may exist between organizational units. In this context, a connection may have one of the following meanings:

If functional responsibilities are recorded, the organizational chart illustrates the distribution of the business tasks.

The Position object type is provided to represent individual positions within the company, for example, positions for which descriptions exist. This object type is illustrated in the following figure. Multiple positions can be assigned to an organizational unit. The meaning of the connections corresponds to the interaction between organizational units.

Individual persons in the company can be assigned to the positions and organizational units. ARIS offers separate objects for persons, which is illustrated in the following figure. The assignment of an individual person to an organizational unit shows that this person is assigned as an employee to this organizational unit, whereas the assignment to an individual position defines the current staffing in the company. An example is shown in the following figure.

Organizational units and persons can be typified. For example, you can define for each organizational unit whether it is a department, a main department, or a group. Persons can be assigned to the Department head, Group leader, or Project manager roles, for example.

This typification is represented by the Organizational unit type and Role objects provided for this purpose. An example of the typification of organizational units and persons is shown in the following figure.

Using these object types enables you to depict general business rules derived from concrete organizational units or employees. Thus, in process chains, it is possible to define that only specific roles may carry out a function or have access to an information object.

The modeling of the organizational structure of the company is the starting point for the network topologies to be defined at the design specification level, which are to support this organizational structure as best as possible. Included in the definition of the network topology are network connections and network nodes, which may be found at particular locations of the company. The location of an organizational unit is therefore the most important link between requirements definition and design specification of the organization view. Thus, the location of every organizational unit is already defined in the requirements definition. An example is shown in the following figure.

Locations may be arranged in any required hierarchy. A location can be an entire plant, a building or, for a more detailed examination, an office through to an individual workstation in a room. This makes it possible, in the design specification, to assign network nodes of a network to individual workstations of the organizational unit. For example, the design specification may stipulate that a total of 3 network nodes must be available in a particular office (room 202).

The following figure shows an example of a location hierarchy.