INDUSTRIAL MANUFACTURING

Governed actions from IT service management into ERP for an industrial manufacturer

Service-desk agents were sending write requests straight into the ERP with no limits, rehearsal or approval, on data refreshed every four hours. Wexa put a governed context layer between them: live ERP context, and four gates on every action.

Download this case as PDF Book a demo

ERP writes passing a policy gate
context tokens per query
ERP context freshness
mean time to repair (target)

CLIENT: Industrial manufacturer ($1.85B revenue, six plants)
REGION: US
WHEN: 2026
ENGAGEMENT: Solution build
WEXA COMPONENTS: Wexa · live ERP context · four-gate action policy · approvals · audit

01Case 17

The challenge

Agent write requests reached the ERP uncapped and unapproved
Four-hourly batch sync meant decisions on stale data
Technicians re-keying between the service desk and ERP

What Wexa built

Live ERP and ITSM context in one graph, replacing the batch sync
Four-gate action flow: policy check, rehearsal (dry run), human approval, governed write
Caps and allow-lists per action type; every write traced to a requester and approver
KPIs tracked: MTTR, PO cycle time (54 h → 24 h target), OEE (76.4% → 85% target)

02Case 17

How it runs on Wexa

FigureHow this use case runs on Wexa: client systems connected, ontology discovered, context graph in the Wexa memory layer, agents and process flows, and governance. Highlighted components are central to this use case.

03Case 17

Results

Measure	Before / without Wexa	With Wexa
Technician hours re-keying between service desk and ERP (120 technicians, six plants)	480 hours a week	120 hours a week
Annual cost of the process	$1M	$259K
Purchase-order cycle time	54 hours	24 hours
Time to implement the AI solution	6 months	6 weeks
AI build cost (one-time)	$480K	$44K
AI operating cost per year (models, infrastructure, upkeep, platform)	$312K	$149K
Total AI cost in year 1	$792K	$193K