Asset history
Every change to status, condition and health score, with the reason and who or what caused it.
Status changes, approvals, maintenance, stock movements and automated actions are all recorded with who did them and why. When an auditor, regulator or lawyer asks, the answer is already there.
An audit trail should not be a report you prepare at year end. In Mintema, every part of the platform keeps its own record as the work happens.
Every change to status, condition and health score, with the reason and who or what caused it.
Every inspection, work order and purchase decision, with the approver, comment and signature.
Every step of every job, from request to close, with dates and people.
Every movement of every part. Mistakes are corrected with new entries, never erased.
Every rule that ran, what triggered it and what it did.
Who signed in and who changed access, for security reviews.
One approval started a chain of events. Open any event to see exactly what changed.
Span 02 · Principal 2026 · by S. Nabil at 02:14:07
| Field | Before | After |
|---|---|---|
| Status | In review | Approved |
| Signature | — | e-signed |
Expansion joint J1 · by State engine at 02:14:08
| Field | Before | After |
|---|---|---|
| Lifecycle status | In service | Restricted |
| Reason | — | Inspection C4 |
Lanes 1–2 northbound · by Impact rule #12 at 02:14:08
| Field | Before | After |
|---|---|---|
| Status | Open | Restricted |
| Source | — | Joint J1 |
Command Center · 3 rooms · by Automation at 02:14:09
| Field | Before | After |
|---|---|---|
| Severity | — | Emergency |
| Type | — | Structural |
Bearing B2-West · by Device TM-17 at 02:16:40
| Field | Before | After |
|---|---|---|
| tilt_deg | 0.61 | 0.93 |
| Quality | good | good |
Comment: crew dispatched · by Control Room A at 02:21:03
| Field | Before | After |
|---|---|---|
| Ack | pending | acknowledged |
| Comment | — | Crew N-2 dispatched |
User R. Darwish · by M. Kamel at 09:02:55
| Field | Before | After |
|---|---|---|
| Inspections.Approve | denied | granted |
| Scope | Bridges | Bridges |
Illustrative event stream. Hash values are shortened for display.
Important values change only through approvals, jobs and documents, not by editing a field.
Each change records who or what caused it: a person, an inspection, a job or a rule.
Nothing is overwritten. Corrections are added, so the original stays visible.
History on every record, and reports for auditors.
A bridge was restricted. The record shows the approved inspection behind it, the part, the score, who approved it and what else was affected.
Nobody approves their own work. Exceptions need a permission and a reason. Deletions need confirmation. The record shows each control at work.
Staff change and contractors leave. The history of every asset stays with the asset, for decades if needed.
The record pays for itself the first time a regulator, auditor or lawyer asks a question.
You can show what you knew, when, and what you did about it.
Evidence is already on record, so audits take days instead of weeks.
Every decision has a name and a reason, which leads to better decisions.
What happened to an asset stays with it when people move on.
Have a question that is specific to your organisation? A solution engineer will answer it against your own assets, processes and data.
No. Corrections are added as new entries, so the original stays visible.
The old and new value, when it happened and what caused it: a person, an inspection, a job or a rule.
Yes, with the approver, the decision, the comment and, where required, a signature.
Yes. Every movement is recorded and nothing is erased.
We will run an inspection, a job and a rule during the call, then show you the record each one left behind.