Reporting is a monthly project of its own
Someone spends the first week of every month pulling exports together. The reward is a picture of a month that has already finished.
Business
Targets and projects, measured from live data
A KPI that reads the same records as the operation cannot drift from it. Neither can a project status that is assembled from the work rather than typed into a slide.
Four tools · Reads from every module · Where the board-level view comes from
Illustrative product view with sample data. Request a live walkthrough.
Before Caspian ERP
The number on the slide is nobody’s number
By the time a KPI has been exported, pasted, reformatted and presented, it belongs to the person who built the deck rather than to the operation.
Every department reports a different truth
Procurement counts orders one way, finance counts them another, and the meeting is spent reconciling definitions instead of making decisions.
Project status is a feeling
Progress is described rather than measured, and the first hard evidence of a slip is the deadline itself.
What it does
The layer that turns operations into management information
Four tools, deliberately. This module does not try to be a BI suite — it reads the records the rest of the platform already keeps.
KPIs defined once, measured continuously
Set the target, the owner and the period, and let the value come from the underlying records.
- Targets with owners, periods and thresholds
- On-track, at-risk and missed states visible without interpretation
- History kept, so a trend is a trend and not a memory
- The same figure everyone sees, because there is only one
A dashboard people actually open
The KPI dashboard is a live view, not a monthly artefact.
- Current state across every tracked KPI on one screen
- Drill from a number toward the records behind it
- Filter to the department or site you are accountable for
- No export step between the operation and the view
Projects with scope and progress
Projects hold the work, the people and the state — and stay linked to what is happening elsewhere in the platform.
- Project register with owner, dates and status
- Detail view holding scope, progress and the team
- Tasks and meetings attached rather than tracked separately
- Visible to the people doing the work, not only to the sponsor
Management reporting without the assembly
When the KPI and the record are the same object, the monthly pack stops being a build.
- Numbers that reconcile with finance because they share a source
- Period comparisons available without rebuilding a spreadsheet
- Owners accountable for their own KPIs in the same system they work in
- Nothing to re-key between the operation and the board pack
Every tool in the module
Four tools that sit above the rest
Small module, large leverage — it depends on every other one.
KPIs
Define the indicators your organization is managed by — target, owner, period and threshold — and track them against live records.
KPI Dashboard
The current state of every tracked KPI on one screen, with the trend and the gap to target.
Projects
The project register: owner, dates, status and budget, with the work attached rather than described.
Project Detail
One project in full — scope, progress, the team on it, and the tasks and meetings that move it forward.
Connected, not bolted on
A KPI is only as good as the record beneath it
This module has almost no data of its own. That is the point.
Safety performance
Observation rates, open incidents and overdue actions are counted from the HSEQ register rather than reported by hand.
Financial performance
Budget against actual comes from the same ledger your accountant works in, so the two versions cannot disagree.
Delivery
Project progress is built from tasks, meetings and actions people are already completing in Efficiency.
Who lives in it
The management layer, without a separate system
Three people who currently share a spreadsheet.
General manager
Opens one dashboard and sees whether the organization is on target, without waiting for a monthly pack to be assembled.
Project manager
Runs the project where the work happens, so status is a consequence of the work rather than a separate reporting task.
Department head
Owns a handful of KPIs, sees them in the same system they run their department in, and is measured on live numbers.
Yours to shape
Define what your organization is actually managed by
No two operations track the same indicators. Nothing here is hard-coded.
- Create your own KPIs with the targets, periods and thresholds you use
- Assign each KPI an owner, so accountability has a name on it
- Decide which departments can see which KPIs and projects
- Run projects with your own status values and stages
- Hide the module entirely if you manage by department rather than by KPI
Business · Settings
| Setting | Value |
|---|---|
| KPI period | Monthly |
| At-risk threshold | 85% of target |
| KPI visibility | Owner + managers |
| Project statuses | Custom (5) |
| Dashboard refresh | Example |
Business questions we get asked
Do KPIs update automatically?
They read from the records the rest of the platform keeps, so the figures move as the work does. What you define is the indicator, its target and its owner — not the number itself.
Is this a replacement for a BI tool?
No, and it does not pretend to be. It is the management view of the data already in Caspian ERP. If you need modelling across external sources, export and use your BI tool — the value here is that no export is needed for the everyday view.
Can a project span several modules?
That is the normal case. A project usually pulls in tasks and meetings from Efficiency, spend from Finance and people from HR. The project record is where they are seen together.
Who can see the dashboard?
Whoever you allow. KPI visibility is permission-controlled like everything else, so you can publish some indicators organization-wide and restrict others to their owner and the management team.