01
Incident management
A full cycle with reference numbers, priorities, statuses and response targets, plus a work log per incident.
Maintenance operations platform
Run incidents and field work from one system.
Idrak connects reporters, supervisors and technicians in a clear workflow that records ownership, work, materials and approval, then turns those events into operational reporting.
For O&M contractors, facilities teams and in-house maintenance departments
Bilingual interface and a safe product experience built on synthetic data
See the whole operation.
One workspace gives the team a shared view of active incidents, ownership, work status and issued materials.
Idrak
Incidents and maintenance management
Unified operations view
What needs the team’s attention now
148
Total incidents
31
Open
22
In Progress
7
Pending
Latest incidents
View all- Open
Cooling pump trips at full load
INC-2026-MNT-00125
- In Progress
Lighting outage in the north corridor
INC-2026-ELC-00312
- Pending
Water leak under a roof tank
INC-2026-CIV-01042
- Resolved
Weak radio coverage at the gate
INC-2026-COM-00087
Designed for operations and maintenance environments
When the process is fragmented, the operational picture disappears.
A call starts the incident, chat follows it and a spreadsheet summarises it later. Ownership, timing and operational evidence get lost between those tools.
- No shared reference
- The report arrives without one record for the discussion, work and decision.
- Unclear ownership
- Work moves between departments and people without a reliable current owner.
- Late documentation
- Work is recorded after it happens, weakening both accuracy and timing.
- Materials detached from work
- Parts are issued outside the incident, obscuring cost and actual consumption.
From report to close, in steps everyone can see.
Every step is a status from a closed list or an action written to the activity log — no free text, no end-of-month memory.
- Open
The report arrives
From phone or desktop, with a reference number generated on submission, a department, a priority and a location.
- In Progress
Work begins
A supervisor assigns the report to a technician or transfers it to another department; the action is logged and the recipient is notified.
- Pending
Waiting for a part or decision
When work cannot continue, the reason is recorded and the incident moves to pending until the team can resume.
- Resolved
Resolved, sent for approval
A resolved incident waits for the supervisor’s approval, or is sent back for rework with a written reason.
- Closed
Closed
After approval it closes, the reporter rates the fix, and reports read from the events as they were recorded.
Operations workspace
What Idrak does
02
Inventory and spare parts
Item catalogue, per-department stock and reorder thresholds — and issuing happens from inside the incident.
03
Equipment custody
Check-out and return with documented condition, and a panel showing each technician what they hold now.
04
Work permits
Issue, track and link to incidents, with attachments and scoped permissions.
05
Precise roles and permissions
Super admin · department manager · technician · reporter — with grant and revoke down to a single person.
06
The conversation lives in the record
Comments and attachments, an @mention that notifies one named person in their own language, and an internal note the reporter never sees — the discussion stays attached to the incident, not scattered across a chat app.
Trust
Clear controls for sensitive operational data.
Idrak builds protection and governance into the operating workflow, with the information technology and procurement teams need collected on a dedicated review page.
Review trust and security- Organisation data isolated inside the database, not only in the interface.
- Two-factor authentication for the highest administrative account and an immutable audit log.
- Clear data-residency options and verifiable contracting information.
Start with the workflow you want to improve.
We review your operating environment, users and deployment requirements, then define a clear scope around the way your team works.
Send your request
Share the team size and operations you want to organise.
Review the workflow
We discuss roles, incidents, reporting and deployment requirements.
Receive a clear scope
We provide a written next step based on the agreed need.
Could Idrak fit your operation?
Explore the product directly, or request a session to review incident flow, field work and your team’s requirements.