Departments

Modeling organizational units in Docusnap365 – to structure the relationships between people, applications, business services, and processes. Without hierarchies, role models, or responsibility definitions.

Objective

In Docusnap365, departments or organizational units can be defined as independent objects and embedded into the model structure.

The goal is to represent the organizational structure of a company at a high level, allowing people, applications, business services, and processes to be assigned and visualized within the model.

This chapter explains how departments are modeled in Docusnap365 and how they can be linked to other objects.

Scope of Functionality

The current functionality for modeling departments includes:

  • Creating departments

    • Manually via the user interface or automatically via the REST API
  • Linking to other objects, such as:

    • People who are organizationally assigned to the department
    • Applications used or managed by the department
    • Business services associated with the department
    • Processes that are carried out or supported by the department
  • Dependency diagram

    • Visualization of all modeled relationships between a department and its related objects
    • Supports navigation and structural understanding – without hierarchy or role modeling

Example Use Cases

  • Which people belong to a specific department?

    • Visible through the modeled relationship
  • Which applications are used or managed by a department?

    • Recognizable through the assignment in the model
  • Which business services are associated with a department?

    • Derivable from the structural relationship
  • Which processes are executed within a department?

    • Traceable through the process relationship in the model