Condition-triggered task dispatch
Asset alarms and maintenance schedules create jobs automatically. Rules pick the technician by skill, proximity and availability, and the job arrives on their device with the asset’s history and live readings.
Field Operations
Half of every operational failure is a person who was never told.
Teams, tasks, checks and proof of work in the same layer as the assets they are sent to — so dispatch is driven by condition instead of by phone call.
- Built for
- Field service, maintenance and contractor managers
- Connects
- Assets, mobile devices and work orders
- Deploys
- Sovereign cloud, private cloud or on-site
/ The shift /
What is actually happening today — and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01Work is dispatched by conversation.
Which means it is not recorded, not prioritised, and not measurable.
- 02Proof of work is a photograph in a chat group.
Somewhere.
- 03The asset and the job live in different systems.
So nobody can say which sites consume the most field time, or why.
/ How it works /
From signal to decision in four moves.
Each step runs on the shared IoT Cube foundation, so nothing here is a separate system to maintain.
- 1
Connect assets and crews
Asset sensors, QR and NFC tags, mobile devices and lone-worker units report into the same layer as the jobs.
- 2
Join asset, job and person
Every job is linked to the asset it concerns, the site it sits on and the qualified person assigned to it.
- 3
Decide who goes
Condition alarms and schedules create jobs, and rules assign them by skill, location, availability and priority.
- 4
Prove the work
Technicians complete digital checklists with photos, readings and scans, and the evidence closes the job and the alarm together.
/ What you get /
Capability, not just visibility.
Digital checklists and proof of work
Configurable forms require photos, readings, signatures and QR or NFC scans. Submissions are timestamped and geotagged, so completion is evidenced, not asserted.
Location awareness and lone-worker safety
Crew location is shown against jobs during working hours. Missed check-ins, man-down or panic events alert a supervisor with the worker’s last known position.
Crew and contractor performance
Response, travel, time on site and first-time completion are recorded per job, so performance compares fairly by site, job type and contractor.
One record for asset, job and person
Each asset’s record shows every alarm, job, visit and technician, so repeat faults and field time can be traced to the site that causes them.
Offline working with sync
The mobile app stores jobs, forms and asset data on the device. Work is captured without coverage and synchronised, in order, when the device reconnects.
/ Use cases /
Where teams put it to work first.
Dispatch from asset alarms
Create a job when an asset raises an alarm, and assign the nearest qualified technician with the history and live readings.
Verify contractor work
Check photos, scans, readings and timestamps for each job before a contractor invoice is approved.
Protect lone workers
Alert a supervisor with last known position when a technician misses a check-in or raises a panic event.
Work without coverage
Capture checklists, readings and evidence offline at remote sites, and sync them in order when the device reconnects.
/ Benefits by team /
Every team gets a different answer from the same record.
01
Operations
Work is raised by condition and assigned by skill and location, so dispatch no longer depends on phone calls.
02
HR
People, skills and shifts come from workforce systems, and field time is attributable by site, asset and job type.
03
HSE
Lone-worker check-ins, man-down and panic events reach a named supervisor, with every response recorded.
04
Finance
Contractor payment follows evidenced completion, and jobs without proof are returned before invoices are approved.
/ In practice /
What it looks like on an ordinary Tuesday.
Three moments where the platform earns its place. Scenarios are illustrative.
The signal
A booster pump at an unmanned site outside Al-Kharj reports a low-pressure alarm at 06:30.
- 1
The platform creates a job and assigns the nearest qualified technician.
- 2
The technician receives the asset history and live readings on the way.
- 3
The fix is logged with photos and the alarm clears against the same job.
The outcome
The job starts from the alarm, not from a phone call.
/ Technology /
Four layers. One record underneath.
Device-neutral at the bottom, open at the top, and sovereign all the way through.
01
Devices in the field
Keep the hardware you already have
- Mobile devices
- Lone-worker and panic devices
- Asset tags and QR/NFC
- Vehicle telematics
02
Connectivity & protocols
Any carrier, any protocol
- MQTT
- LoRaWAN
- NB-IoT / LTE-M
- BLE
- NFC and QR
- 4G/5G via any Saudi carrier
- Satellite for remote sites
03
IoT Cube platform
Sovereign, multi-tenant, AI-neutral
- Workflow automation
- Asset & identity record
- Geospatial engine
- Edge buffering
- Rules & alerting engine
- Role-based access & audit
04
Your systems of record
Data lands where decisions are made
- HR and workforce systems
- Work order and CMMS
- Payroll
- Contractor portals
/ What you measure /
Numbers that replace arguments.
The indicators this solution produces continuously, per asset, per site and per contract.
Alarm-to-dispatch time
Time from an asset alarm or scheduled trigger to a job being assigned to a person.
Time to site
Time from job assignment to the technician checking in at the asset.
First-time fix rate
Share of jobs closed on the first visit without a return trip.
Evidenced completion
Share of closed jobs with required photos, readings and scans attached.
Field time by site
Technician hours spent per site, asset and job type over a period.
Lone-worker response
Time from a missed check-in or panic alert to a supervisor response.
/ Rollout /
Start with one decision. Scale what works.
- Phase 1
Map jobs, assets and crews
We review how work is raised and dispatched today, which assets generate it, and who does it — employees and contractors.
- Phase 2
Pilot one region’s crews
One region’s assets, technicians and checklists move onto the platform, with alarms and work orders connected.
- Phase 3
Prove condition-led dispatch
Jobs are raised from real alarms and closed with evidence, and supervisors confirm dispatch no longer depends on a phone call.
- Phase 4
Extend to every region
Remaining regions, contractors and job types join on the same forms and rules. Weeks, not quarters, per wave.
/ Security & sovereignty /
Sovereign is a place, not a promise.
In-Kingdom residency
Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.
Built to national controls
Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.
Isolated by tenant
Tenant isolation, role-based access and a full audit trail across users, actions and devices.
Your cloud or site
Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.
/ Built on IoT Cube /
Runs on the platform, not beside it.
Products already running this solution on the shared foundation.
Built on IoT Cube
Humify
AI-powered GCC HR platform for payroll, attendance, recruitment, leave, employee records and workforce operations.
Built on IoT Cube
Zaps
AI sales command centre for KSA and GCC teams, with AI agents that work the pipeline.
Built on IoT Cube
tracking.me
Saudi AI and IoT fleet tracking, telematics, RFID, tyre management and connected mobility solutions.
Built on IoT Cube
livixa.ai
AI voice agents that automate customer calls, lead qualification, appointments, follow-ups and business workflows.
/ Questions /
Frequently asked.
Is this a workforce app?
It is the connection between the asset and the workforce. If you already have a field app, we can feed it instead of replacing it.
Will it work where there is no signal?
Yes, offline with sync on return.
Does it connect to our CMMS and HR systems?
Yes. Jobs can be created in or received from your work order system, and people, skills and shifts come from HR, through APIs, webhooks or scheduled files.
How is worker location data handled?
Location is personal data. Tracking can be limited to working hours or active jobs, access is role-based and logged, and data stays in the Kingdom — designed to support your PDPL obligations.
Can contractors use it without joining our network?
Yes. Contractors get restricted accounts that show only their jobs and sites, and their completion evidence lands in the same record as your own crews.
Can we build our own checklists?
Yes. Forms and checklists are configured without code, with required photos, readings, signatures and QR or NFC scans to prove the technician was at the asset.
/ Explore more /
Other solutions on the same foundation.
Fleet & Asset Operations
Know where assets are, how they are performing, and where attention is needed.
Cold Chain & Compliance
Monitor conditions continuously and create the operational record while products move.
Driver Safety & Journey Management
Connect journeys, behaviour, safety events and operational response.
Bring us the decision that takes too long today.
Start with the problem. IoT Cube provides the foundation underneath.