We are an international financial services provider. Due to regulatory requirements, we are looking for process management software.
We therefore have the following requirements for the software, which should be met:
- Links/cross-references between and within pages or documents
- Exportable reports via parameters (see parameterization) including time stamps, if necessary for further processing in a BPM tool
- Assignment of tasks (e.g., revision of text passages) including assignment of deadlines
- Subscription to pages or documents
- Highlighting of changed pages or documents (cf. green asterisk in MS Sharepoint)
- Distinction between editing version (only visible to editor group) and frozen or released version (visible to all users) – can this be mapped in rights assignment?
Pure process management view:
- Creation of diagrams according to BPMN 2.0 standard
- Process database-based, not diagram-based (diagrams to be created only ad hoc as part of optimization measures)
- Definition and maintenance of process parameters
- Process master data: Owner, software, resources, criticality, trigger, input, output
- Nice-to-have: BCM/structure analysis: IT components including their restart times
- Simulation parameters: Max. throughput times, costs, capacities, probabilities for decision fields
- Self-configurable parameters
- Linking of processes/process structure (previous/subsequent processes, main/sub-process relationship)
- Nice-to-have: Automatic tree representation based on the process structure (graph representation)
- Performing simulations based on BPMN 2.0 diagrams and process parameters
- Performing statistical evaluations of parameters and simulation results (what-if analyses)
- Nice-to-have: Intelligent evaluation of parameters and simulations, i.e., concrete optimization suggestions based on simulations (e.g., suggestions such as “If more resources, then throughput time lower”)
- Nice-to-have (ideal world): Possibility for process mining, i.e., evaluation of digital traces of real process instances by connecting to the databases of other software (only useful if central software is used, e.g., when using SAP). See the example of a well-known process mining software
- History of simulations and analyses (including note-taking option)
- History of parameters
Explicitly not a requirement from a process management perspective:
- A workflow engine. Should be a pure administration and analysis tool, not a tool for digitizing processes.
- Documentation and publication of processes. This tool is intended for process management only.
- Windows-compatible
- Open whether on-premises, intranet, or web-based (cloud/data center, at least according to EU standards)
5-10 software workstations are planned.