Everything You Want to Know About Agilium

We can set up a trial workspace for you, available for 7 days.

Yes, through a web address: a link to your document management system, your intranet or any tool available online.

The two complement each other:
you sign in with your Agilium account;
activities link to the documents in your document management system: procedures, work instructions, forms;
processes are displayed directly in Agilium.
A linked document opens in Agilium with the user’s own permissions, so no one sees a document they are not allowed to access.

No. Agilium’s process mapping module works on its own, with its own accounts.

Yes, by creating several projects: by site, by subsidiary or by management system. Each project has its own process map, mini-site and share links.

The interface and the processes are available in 7 languages: French, English, German, Italian, Spanish, Portuguese and Polish. Each reader chooses their own language, and notification emails follow the recipient’s language.

Yes. You write in your reference language, then translate into the languages you turn on. A dedicated screen lists everything still to be translated: activities, descriptions, swimlanes, process names, resources. You can also export the texts, have them translated and import them back. There is only one diagram: just the display language change

A process being edited is locked for everyone else, who can see who is editing it. There is no risk of overwriting a colleague’s work.

There are three roles:

A modeler draws their first process within an hour, thanks to ready-to-use templates, drag and drop, and automatic alignment and layout.

No. AI import rebuilds a process from an image, a PDF page or a text describing it. Swimlanes, steps and flows are recognised, then laid out automatically. You check and correct the result before creating the process. BPMN files can be imported directly.

Modelers discuss each process in a comment thread attached to it, with mentions and email notifications. For readers, a “Suggest an improvement” link can point to the contact of your choice.

• Diagrams: PDF with title block, PNG, vector SVG
• RACI matrix and role sheets: Excel, plus PDF for role sheets
• Translations: CSV and JSON

Yes, a published process or project can be embedded in a web page.

Processes published within the last 30 days carry an “Updated” badge. A “Latest updates” list shows the version, date and reason for each change.

Viewing, yes: it adapts to small screens. Modeling is done on a computer, with a recent browser (Chrome, Edge, Firefox or Safari).

Not necessarily. There are two options:

• a “Reader” account, which gives access to the mini-site after signing in;
• a share link, with no account, which you can protect with a password, set to expire, and revoke at any time.

Each project has its own viewing mini-site: process tree, search, clickable diagrams, and the detail of each activity (description, who does what, links). Nothing to install: a web browser is all you need.

It goes to a recycle bin, along with all its sub-processes. An administrator can restore it for 30, 60 or 90 days, depending on your setting.

The bowtie diagram lets you show threats, the top event, consequences and barriers, with five severity levels.

Each activity carries a RACI (Responsible, Accountable, Consulted, Informed) linked to your resource repository: functions, teams, sites. From it, the tool automatically produces:

• the RACI matrix of a process or project, exportable to Excel;
• the role sheet of each resource: all its activities across every process, in Excel or PDF;
• the anomalies: activities with no one responsible, unused resources, broken links.

On each published process: version number, publication date, author, approver, reason for the last change and date of the last review. The same information appears in the title block of PDF exports, along with the statement “Uncontrolled document when printed”.

You set a review period for the organisation (6 to 36 months), which you can adjust for each process. The dashboard flags processes due for review and those that are overdue. Owners receive an email reminder 30 days before the due date, then on the due date. If nothing has changed, one click on “Reviewed without changes” is enough: the review date is recorded without creating a new version.

No. Readers only see published versions. A process being edited keeps showing its latest approved version until the next one is published.

No. You assign approvers process by process, for example the process owner. Assignments are inherited: an approver named on a macro-process covers all its sub-processes, unless you name other approvers further down.

Yes. With the approval workflow turned on, an author submits a version for approval. Readers only see it once it is approved. A rejection comes with a reason and is sent to the author by email.

Work in progress is saved automatically. Publishing creates a numbered version (1.0, 2.0…) with its date, its author, the person who published or approved it, and the reason for the change. Previous versions remain available to modelers and can be restored.

It covers what the standard expects from a process approach and from controlled documented information:
process map and interactions;
responsibilities;
identified versions;
approval before release;
periodic review;
access to the current version.
It does not replace your management system: it handles the “processes” part of it.

Yes. The administrator picks a theme for the whole organisation (colours, shape style). Every diagram follows it, so the presentation stays consistent whoever the author is.

Yes. Clicking a process on the map opens its flowchart. Clicking an activity opens its sub-process or its activity sheet: description, responsibilities, links to the relevant documents and websites (up to 10 links per activity).

No. The tool uses a small set of shapes that anyone can read without training: activity, decision, start, end, sub-process. If you already have processes in BPMN, you can import them.

• Process map (overview, macro-processes)
• Swimlane flowchart, horizontal or vertical
• SIPOC
• Turtle diagram
• Bowtie diagram for risk analysis

Ready-to-use templates exist for each one, and you can save your own templates.

A drawing tool produces pictures. Agilium’s process mapping module manages a process repository:
processes are linked to one another;
every published version is kept, with its author and approver;
roles (RACI) can be used in tables;
teams always see the latest approved version, never a stray file.

It lets you describe your processes, get them approved, and then make them available to the whole company in a form anyone can read without training. You start from an overall process map and drill down into each process. Every activity shows who does what and links to the right documents.

Yes. The Process Mapping module lets you draw swimlane flowcharts. Each step is assigned to an actor (person, team or role), and you define roles with a RACI matrix: who does the work, who approves, who is consulted, who is informed. On the Agilium platform, the flowchart is then attached to the dedicated tab of the process record, alongside inputs, outputs and stakeholders.

You can start with nothing finalised. The tool is designed to build your process map step by step. Start with your priority processes, those causing the most issues or audited first, then add the rest over time, without waiting to have modelled everything. If you already have diagrams (Visio, image, scanned document), AI import redraws them so you don’t have to start from scratch. The structure grows with you: you add levels, processes and links to your documents and KPIs as your quality system takes shape.

Yes, the “Documents,” “NC,” “Actions,” and “Audits” tabs are visible in the process record.