Using Most Common Reports

Processes contain visible and hidden information (in attributes). Generating reports is important for business users to collect and aggregate all the information on a specific topic, which is distributed across different processes.

Reports help to answer questions, such as:

• In which processes and activities are we using which IT-System?
• Who is responsible for which tasks?
• Where do we have many handoffs?
• Can we reduce costs? If yes, where? 
• How much does a specific tasks cost and how long does it take?

The reporting function in SAP Signavio Process Manager is essential for companies as it offers different reports for various purposes. In general, reports are important for management as a basis for decision-making, for stakeholders as a basis for information and for internal/external auditors as proof of controls. 

The following three categories comprise the reports that are frequently used in practice:

In SAP Signavio Process Manager process diagrams can be created and information like costs, cost center, and task duration defined in the attributes of individual tasks.

• Process cost analysis
• Resource consumption analysis

With process model and characteristics reports, you can generate statistics for your diagrams which contain an overview of the elements and attribute values that are found in the selected diagrams.

• Process model metric
• Process characteristics report

The following diagram is an example Process Model Metrics report.

In SAP Signavio Process Manager, all defined responsibilities and also used objects and systems can be aggregated and presented in dedicated reports. Those reports are:

• RACI report
• Responsibility handover report
• IT system usage report
• Document usage report

The following diagram shows an example RACI report.

The following video shows the creation of the first reports listed in the Explorer of SAP Signavio Process Manager.

In SAP Signavio Process Manager process diagrams can be created, which also includes to consider information like costs, cost center, and task duration. 

Those can be defined in the attributes of individual tasks also aggregated in corresponding calculation reports.

Note

After we have added the attribute information to the process, the data is passed to the analysis.

You can now perform two types of analysis. The process cost analysis refers only to the costs and their cost centers and displays them. The resource consumption analysis focuses on the workload – how long it takes to execute a task and how many resources are required for it.

You can run the process cost analysis report under the Reporting tab. The following shows a diagram converted into a process cost analysis report. This report calculates the costs per task, according to frequencies.

The example below shows the diagram converted into a resource consumption analysis report. This report calculates the hours per task according to frequencies.

With the process model and characteristics reports, you can generate statistics for your diagrams. These statistics contain an overview of the elements and attribute values that are found in the selected diagrams.

After selecting the relevant processes, the processes and their properties are converted into a report with corresponding statistics:

This report describes the assignments and gives detailed information about the diagram and attributes.

The process model metrics report gives detailed information on:

• The number of elements.
• The gateways used.
• The number of sub-processes.
• Linked files.
• Dictionary links.

With process model metrics, you can generate statistics.

Statistics are helpful to keep an overview of your processes. You can:

• Check if internal defined standards have been considered.
• Measure how important a process is, for example by the number of handovers or sub-processes.
• Check the status of your process diagram.
• Retrieve key indicators and links to open the modeled process in SAP Signavio.
• Use the links to embed processes internally, for example, intranet.
• Find out how a process is structured.
• See if the process is published and who last edited or saved it.