Language and terminology
Both the field of process management and Comm’ant itself use specific language and terminology. Usually based on world standards and sometimes on specific jargon. To prevent confusion later on, make sure all stakeholders agree upfront on the terminology used. Comm’ant offers the possibility to differ from the standards and use your own terms throughout the software.
This is an overview of the terms used – and their synonyms:
|Process steps, steps
|Set of interconnected actions, possibly with added instructions on HOW to execute them.
|The Application manager has the highest level of rights. He has access to all parts of a system. The Application manager determines users’ access rights and restrictions.
|Divisions, extra (process) level
|This is an additional component e.g. to add an extra illustration or a process overview in a clickable image.
|Files, attachments, instructions, forms
|Additional information, tools, instruments, links to systems. Any extra relevant knowledge that is not an integral part of the process itself.
|Possibility to create an overview by grouping objects. Multiple groupings are possible (main group, subgroup)
|Input/Output, information specifications, results
|Definition of the new information that is created at any time in a process and which is input for one or more other processes internally and/or externally.
|Links between various objects in Comm’ant. For example, a user is linked to a group, a position is linked to an output + role, a document is linked to a process, and so on.
|Positions, Job titles, Special duties
|Collection of positions and meetings, grouped in the organizational structure e.g. by teams or departments. It also includes special duties.
|Key success factors, Process indicators, Key performance indicators
|Definitions of relevant indicators that define the optimal performance and outcome of one or more processes.
|Overview of a selection of processes, showing which information flows from one process to the other (output = input).
|Process editor, Process moderator
|Process developer is a default role in Comm’ant, to automatically link the content manager to his newly created objects.
|A complete overview of all result areas within the organization.
With a distinction in management, primary, and supporting processes.
|Process Chain Manager
|Responsible for the chain of processes
Responsible for an entire Main Process
Is attached to the Main Process
Usually someone in Management.
Usually no Subject Matter Expert (SME)
|Process Content Owner, Process Expert, Process knowledge coordinator
|Responsible for the process description and for a correct description of the agreed way of working. Has, in addition, intimate knowledge of the process itself, or is professionally involved.
|Subprocesses, Process step, Procedure, Process description
|Collection of sequential activities, input and output information. Structured in the SIPOC model or flowchart.
|Policy standards and requirements,
Laws and regulations.
|Definitions of preconditions and standards that must be met by the result of the process or the input/control of the process.
|Risk and Control
|Key risk indicators
|Risk and Control is used to identify risk and describe the control measures that are implemented to manage the risk to an acceptable level. It is preferably connected both to the output and the process.
|Capacity, Authorizations, Relations
|Roles are the link between an Actor and e.g. a Process or specific Output. They specify the delegation of tasks, responsibilities, and authorizations to the Actor.
|Means, tools, applications, modules
|Systems are connected to Information Specifications, to indicate which system or module is used to create, store and deliver the output.
|Everyone who has access to Comm’ant.
Supervisor / Overseer
|Action taken by: