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 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 follows condition.
- 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 happens 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, so it is neither recorded nor measurable.
- 02Proof of work is a photograph in a chat group, somewhere.
- 03The asset and the job sit in different systems, so nobody can say which sites consume the most field time.
/ 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 jobs.
- 2
Join asset, job and person
Every job is linked to its asset, its site and the qualified person assigned.
- 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 checklists with photos, readings and scans, and the evidence closes job and alarm together.
/ What you get /
What field operations gives you.
Digital checklists and proof of work
Configurable forms require photos, readings, signatures and QR or NFC scans, and submissions are timestamped and geotagged.
Location awareness and lone-worker safety
Crew location shows against jobs during working hours. Missed check-ins, man-down or panic events alert a supervisor with last known position.
Crew and contractor performance
Response, travel, time on site and first-time completion are recorded per job, comparable 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 trace back to the site causing them.
Offline working with sync
The mobile app stores jobs, forms and asset data on the device, and captured work synchronises in order on reconnection.
/ Use cases /
Where teams put it to work first.
Dispatch from asset alarms
Create a job from an asset alarm and assign the nearest qualified technician, with 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, syncing in order on reconnection.
/ 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.
02
HR
People, skills and shifts come from workforce systems, and field time is attributable by site 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 approval.
/ In practice /
Three moments from a working week.
Each one starts with a signal and ends with someone acting on it. The 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.
/ 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 /
The numbers this produces.
Measured 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.
- 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 sign off the dispatch rules.
- Phase 4
Extend to every region
Remaining regions, contractors and job types join the same forms and rules, region by region.
/ Security & sovereignty /
Where your data lives, and who can reach it.
- In-Kingdom residency
- Built to national controls
- Isolated by tenant
- Your cloud or site
/ Built on IoT Cube /
Products already doing this.
Each one runs this solution on the shared foundation.
Built on IoT Cube
Humify
AI assisted HR for the GCC: attendance, payroll, leave, requests, recruitment and the whole employee lifecycle.
Built on IoT Cube
Zaps
AI sales command centre for KSA and GCC: CRM, pipelines, leads, meetings, field activity, invoicing.
Built on IoT Cube
tracking.me
AI and IoT fleet management for Saudi Arabia: routing, driver safety, predictive maintenance, RFID and tyre management.
Built on IoT Cube
livixa.ai
AI agents that answer calls, reply on chat and WhatsApp, qualify leads and book appointments, in Arabic and English.
/ Questions /
Frequently asked.
It is the connection between the asset and the workforce. If you already have a field app, we feed it jobs and take back completion.
/ Explore more /
Other solutions on the same foundation.
See field operations on your own assets.
Bring the hardware you already run. We will connect a sample of it and show you the operating picture it produces.