The complete module page

Process Intelligence: how your company really works

Every company process rebuilt from start to finish from the history the system already keeps, with nothing to set up: purchasing, contracts, billing, tickets, studio, dropouts, deliveries and 60 more ready-made processes. The process map as it actually happened, the paths cases took, bottlenecks, rework, policy rules with who follows them and who does not, period and group comparison, email alerts, a forecast of the cases that will run late, likely cause, estimated cost, a simulator and improvements measured before and after.

This is the whole module on a single page: the dashboard screens, the seventy processes that come ready, every functional area with each feature listed one by one, the design decisions that explain why the module only reads and never changes anything in the others, the boundaries with other modules and a glossary of process mining terms.

  • 70ready-made processes across 12 areas, read from the history the system already keeps
  • 33policy rules switched on out of the box, such as whoever requests does not approve
  • 0setup to get started: the first read runs within 30 minutes
  • 36months of history on the Complete plan, 12 on Essential
  • 1click between any number and the cases behind it

Inside the module

8 screens, in the order the work happens

Six menu entries, in the order management uses them. Processes and Cases at risk show how things are moving and what will run late, Out of policy and Alerts tell you when someone needs to look, Improvements measures whether a change worked, and Settings keeps only what the company changed in what comes ready.

01

Monitor

How each process is moving and what will run late.

4 screens
  • ProcessesOne card per process, grouped by area: cases, average time, share within policy, rework and what is in progress, always compared with the previous period of the same length.
  • ProcessThe process opened in tabs: map, paths, bottlenecks, rework, policy, forecast, comparison, likely cause, cost, people, simulator and the case list, all sharing the same filter for period, status, step and attribute.
  • CaseThe timeline of one case: each step with its date, the wait since the previous one, what was redone, what broke policy and, for those with people access, who did it.
  • Cases at riskOpen cases most likely to miss their deadline, across all processes, with the most critical processes on top and the likely completion date of each.
02

Act

When someone needs to look, and what to do next.

2 screens
  • Out of policyThe queue of cases that broke a rule and have not been handled yet, most severe first, with a record of what was done and a spreadsheet of the whole queue.
  • AlertsThe numbers the company wants to watch, with a limit, a window of days and the emails of who receives them, the status of each one and the history of every time it crossed the limit.
03

Improve and adjust

The measured change and what the company customized.

2 screens
  • ImprovementsEach procedure change with a target, the date it took effect, a task for whoever leads it and the automatic measurement that compares cases before and after.
  • SettingsHourly labor cost, minutes per step, when a case counts as stalled, processes switched on, target lead time, rules, step names, reading status and the log of who looked at time per person.

The problem and the fix

What changes in management’s day to day

The pain

The board asks why some purchases go out in two days and others take three weeks, and nobody can answer without opening request after request.

With Partiu Formatura

The map shows every step and every hand-off with the median wait, and Bottlenecks ranks waits by how many cases waited times how long. The first line is where to start.

The pain

The flow drawn in the procedures manual says one thing, and day-to-day work does another.

With Partiu Formatura

Paths lists the exact sequences cases followed. The first one is usually the expected path; the others show shortcuts, loops and skipped steps, each with how many cases and how long.

The pain

Policy says whoever requests does not approve, but nobody checks whether that happens.

With Partiu Formatura

The rules come ready and switched on, per process: mandatory order, four eyes, deadline, repetition limit and what should never happen. A case that breaks a rule goes into the handling queue, and high-severity ones notify management.

The pain

A class contract blew its deadline and management only found out when the client complained.

With Partiu Formatura

Cases at risk shows, every day, the open cases that will probably miss the target lead time, with the likely completion date, while there is still time to act.

The pain

We changed the procedure two months ago and nobody knows whether it improved or it just feels that way.

With Partiu Formatura

The improvement stores the date the change took effect and compares cases before and after. The result says target met, target missed, worse, or that the difference could still be chance.

The pain

One branch takes twice as long as another on the same process, and each blames the system.

With Partiu Formatura

Compare puts both groups side by side in the same period, points to the steps where the wait changes most and the paths one branch takes and the other does not.

The pain

To follow a process, someone builds a spreadsheet every Monday with what is stalled.

With Partiu Formatura

The alert measures on its own every hour and sends an email when the number crosses the limit: stalled cases, share within policy, rework, average time or cases at high risk of delay. When it returns to normal, it closes on its own.

The pain

Rework looks small because each send-back is just one more click.

With Partiu Formatura

Rework adds up the redone steps, compares the time of cases with and without loops and, on the Complete plan, estimates how much of the process cost went into redoing work.

How it works

From stored history to a measured change

  1. 1

    The system reads what already exists

    Every 30 minutes, the module reads the history that purchasing, contracts, billing, tickets, studio and the other modules already record, and only fetches what is new. Nothing needs to be typed.

  2. 2

    Each case gets its whole story

    Loose steps become the timeline of each case, with the wait between them, what was redone and the status: in progress, stalled, completed or canceled.

  3. 3

    The process shows up as it is

    The map, paths, bottlenecks and rework show the real process. Every number opens the cases behind it.

  4. 4

    Policy is checked

    The process rules are verified on every case. What breaks a rule goes into the handling queue and, when severe, notifies management.

  5. 5

    What will run late shows up early

    Every day, each open case gets a likely completion date and the chance of missing its deadline, and alerts notify you when a number leaves its limit.

  6. 6

    The change is tested and measured

    The simulator shows the likely effect of a change before making it, and the improvement measures afterwards whether the effect happened.

How the system behaves

9 decisions that explain everything else

They explain why the system sometimes does not do what you might expect, and why that is intentional.

Read only, never change

The module does not alter a purchase, contract, ticket or anything in other modules. It reads the history, builds the story and points. The fix happens in the source module, with the usual authority and record.

No setup to start

The seventy processes and thirty-three rules come ready. A process from a module the company does not use shows no data. The first read runs within 30 minutes of subscribing.

Every number opens the cases

A bottleneck, a broken rule or an odd path are clickable and open the cases behind them. A number that leads to no case helps nobody act.

Median, not average

One case forgotten for six months cannot change the picture of the process. Time and wait show as the median, with the time of 9 in 10 cases next to it.

Forecast with the time already waited

A case stuck for 20 days at approval is compared with those that also stayed there at least 20 days. Without that, every forecast for a late case would say it finishes tomorrow.

Better only when it is not chance

Comparison and improvements only say better or worse when the difference is too large to be chance. Otherwise they say it is too early to tell.

People have their own access

Seeing who did each step is a separate permission, every query with names is logged, and the artificial intelligence never receives a name. The module is for understanding the process, not ranking people.

Default rules live in the product

The company stores only what it changed: a deadline, a severity, a rule switched off. A future improvement to the ready-made rules reaches whoever did not customize.

Alerts do not become noise

One email per day per alert, only within the company’s hours, and the alert closes on its own when the number returns to normal.

The boundaries

Where the stories come from

The module never keeps a second copy of anything. It reads what already exists and returns what it produced through the same path as the rest of the platform.

Purchasing

Request, quotation, supplier order and receiving, with who requested and who approved.

Contracts

From sending to signature and invoicing, with the loops for adjustments.

Finance

Payables, installment billing, payment plan changes and reimbursements.

Compliance Control

Occurrences, controls and the compliance the process also needs to meet.

Company Map

The class, contract and installment behind each case, navigable from it.

Governance

Who sees what, and what runs without anyone asking

4 separate permissions

Five dedicated permissions. Seeing the processes does not grant access to people’s names or costs, and whoever configures does not need to see time per person.

  • ManagementProcesses, cases at risk, out of policy, alerts and improvements, without people’s names.
  • PeopleWho did each step and time per person, with every query logged.
  • CostsEstimated cost in reais, per step, per case and in the simulator.
  • Improvements and settingsSimulator, scenarios, improvements and queue handling; and processes, target lead time, rules, step names, hourly cost and alerts for whoever configures.

What runs on its own

Reading and measuring run without anyone remembering. Reading the same stretch of history twice duplicates nothing, and a failure halfway makes the next read start from the right point.

  • History readEvery 30 minutes, only what is new in each process switched on, with the touched cases recalculated.
  • Status of open casesEvery night, open cases are reviewed: what went without movement becomes stalled, and rule deadlines are checked.
  • ForecastEvery night, on the Complete plan, each open case gets a likely completion date and a risk of delay.
  • AlertsEvery hour, the alerts switched on are measured, and those on the list receive the day’s email when the number crosses the limit.
  • Severe out of policyEach case that breaks a high-severity rule notifies management once.
  • Improvement measurementEvery night, ongoing improvements compare cases before and after.

In practice

4 everyday situations, from problem to result

01

The approval that held purchases back

The scenario

Event purchases took eleven days on average, and the purchasing team blamed suppliers.

With the system

Bottlenecks showed that eight of the eleven days were the wait between the approval request and the approval, and the likely cause pointed to requests above a certain amount, which all went to a single person.

The result

Approval authority was split, the improvement was created with a five-day target, and the measurement confirmed the drop two months later.

02

The contract about to miss its deadline

The scenario

Class contracts had to be signed within fifteen days, and delays only surfaced when the committee complained.

With the system

With a fifteen-day target lead time, Cases at risk began showing every morning the contracts stuck in legal review at high risk, and an alert sent an email when there were more than five.

The result

Review started being driven by the day’s list, and late contracts dropped by half in the quarter.

03

Whoever requests does not approve

The scenario

Purchasing policy forbade the same person from requesting and approving, and internal audit wanted to know whether that was followed.

With the system

The four-eyes rule was already on. The Out of policy queue showed the cases where the same person requested and approved, each with the case open to check.

The result

The cases were handled with a record, the approval setup was fixed in the purchasing module, and the queue stayed empty from then on.

04

Two branches, the same process

The scenario

One branch resolved internal tickets in two days, the other in five, with the same systems team.

With the system

Compare put both side by side and showed the whole difference was in the wait before triage, and that the slow branch had a path with a send-back the other did not have.

The result

Triage was unified, and the path with the send-back disappeared in the next month’s comparison.

Glossary

Process mining terms, in plain words

The dashboard is written in Portuguese. If you arrived looking for the industry terms, this is what each one means inside it.

Process miningMineração de processos
Rebuilding how a process really happens from the history systems record, instead of interviews and flowcharts.
CaseCaso
One occurrence of the process: request 4812, the Law class contract.
ActivityEtapa
Each step that happened in the case, with its date and who did it.
VariantCaminho
The exact sequence of steps a case followed. Cases with the same sequence follow the same path.
BottleneckGargalo
The hand-off between two steps where the most cases wait the longest.
ReworkRetrabalho
A repeated step or a loop back to an earlier step, such as a purchase sent back for correction.
ConformancePolítica
The rules the process should follow, checked on every case.
Segregation of dutiesQuatro olhos
The rule that the same person cannot do two steps that control each other, such as requesting and approving.
Target lead timePrazo-alvo
How many days the process should take from the first to the last step.
MedianMediana
The middle value: half the cases took less, half took more. It is not pulled by one forgotten case.
Predictive monitoringPrevisão
The likely completion date of an open case and the chance it misses its deadline, calculated from similar cases in the history.

See how your company really works, with nothing to set up

We can open the module with your company’s real history, show the map of the processes that weigh the most, the bottlenecks, what is out of policy and the cases that will run late, and talk about the right plan for your operation.