Implementation
We engineer it.
Connect it. Test it. Ship it.Custom AI Implementation.
Our engineers build the solution defined in your Blueprint: agents, document processing and integrations with your existing systems. We test it against the acceptance criteria, deploy it with monitoring and access controls, give your team the runbooks, and stay accountable for how it performs.
Talk to our engineersRelease filev1.0
Line-fault agent
Rasikh IndustriesHVAC and ducting plant · Second Industrial City, Riyadh
Test case · integration map
- CMMSWO-1047 opened
- ERPLine 2 orders flagged
- QC logBatch check logged
Acceptance criteriaResult
- 1Arabic shift reports, text and voice, reach the right line and assetMet
- 2Work orders open in the CMMS with asset, line and priorityMet
- 3No line restarts without the maintenance manager's approvalMet
- 4Every action is logged and can be rolled backMet
Approved for release
Maintenance manager, Rasikh Industries
30 Oct 2026
Illustrative examplePrepared by Ting
Built around the operation
The systems
we engineer.
Four kinds of system, built around your process and connected to your data. Here is one night-shift report, followed through all four.
We run these at Ting too: our website agent, lead pipeline and guided audit agent are built and tested the same way.
01
Agentic workflows
Agents that act, handle exceptions and keep multi-step work moving.
02
Document intelligence
Extract, classify and understand documents and unstructured data.
03
Voice & conversational AI
Arabic and English answers from approved knowledge, by chat or voice.
04
Enterprise integrations
Secure, reliable API connections to the systems you already run.
What changedThe fault reached a technician in a minute, the planner knew the impact before the morning shift, and Line 2 restarted only after the manager approved.
Governance in action
Control belongs
inside the workflow.
Unusual requests go to a supervisor. Every action is logged with a timestamp. Any change can be rolled back.
Your data, agreed before we build.
Five things are settled in writing for every system:
- What data the system reads
- Where it is processed and stored
- Who can access it
- What is logged
- How long it is kept
It is written into the Blueprint and checked before go-live.
Original
Planner reviewMove to Line 1 · Held
Original schedule restored
- Line 2 orders
- 3, waiting for WO-1047
- Line 1
- Unchanged
Action history
- Move 3 orders to Line 1 proposed
- Held for the planner
- Original schedule restored
Original schedule restored
- Line 2 orders
- 3, waiting for WO-1047
- Line 1
- Unchanged
Action history
- Move 3 orders to Line 1 proposed
- Held for the planner
- Original schedule restored
Earlier versions
- Original
- Planner reviewMove to Line 1 · Held
Illustrative example
Our implementation process
From Blueprintto handover.
Five stages. Each one adds its section to the release file, and your team can check every one.
Build what your Blueprint defines.
You receiveThe configured solution and its custom components
Connect your systems and data, securely.
You receiveWorking connections to your systems and data
Test with your team, on realistic data.
You receiveTest results agreed with your team
Go live in steps, with monitoring.
You receiveA controlled rollout to production
Train your team and hand it over.
You receiveDocumentation, runbooks and knowledge transfer
Release file · Line-fault agent
01Components
Solution components
| Component | Works with | Access |
|---|---|---|
| C1Shift-report reader | Shift WhatsApp groups, text and voice | Read |
| C2Work-order writer | CMMS | Create, update |
| C3Production check | ERP manufacturing module | Read, flag |
| C4Approval gate | Maintenance manager | Before any restart |
| C5Action log | Every step, timestamped | Reversible |
Built to the approved Blueprint
Integration map
WhatsApp BusinessIn
Receives shift reports
CMMSRead · write
Opens and closes work orders
ERP · manufacturingRead · flag
Reads Line 2 orders, adds flags
QC logAppend
Logs batch checks
Each connection tested end to end with test data
Acceptance test report
| Test | Passed |
|---|---|
| Arabic shift reports, text and voice | 200 / 200 |
| Right asset, line and priority on the work order | 120 / 120 |
| Restart blocked without approval | 40 / 40 |
| ERP and CMMS stay in sync | 60 / 60 |
| Access by role | 25 / 25 |
Signed off with Rasikh's maintenance and production leads
Rollout plan
- 1Shadow run · Line 2The agent drafts, people decide
- 2Live · Line 2Supervisors report through the agent
- 3Live · Lines 1 and 2All three shifts
Monitored
- Wrong-route rate
- Approvals waiting
- Response time
Access roles
- Shift supervisors
- Report
- Maintenance manager
- Approve restarts
- Production planner
- Review schedule changes
- Ting support
- Read the logs
Runbook
Line-fault agent
RB-01 · v1.0
Contents
- 01Solution documentation
- 02Runbook & operations guide
- 03Configuration details
- 04Test results
- 05Known limitations
- Owner
- Rasikh maintenance team
- Support
- Ting
Illustrative example1 / 5
You separately provision hosting, model usage and any required software subscriptions as scoped in the Blueprint.

