Real use cases

Ontology in action

Five sectors. Five critical problems. One intelligence layer.

Each use case reveals the same pattern: data trapped in silos, blind decision-making and money evaporating. Ontology connects everything in under 5 seconds.

Key enterprise ontology use cases

  • Logistics: critical order detection and automatic route reassignment in under 4 seconds.
  • Retail: connecting stock, online sales and physical store to eliminate stock-outs.
  • Construction: integrating BIM, ERP and subcontractors to prevent cost overruns and delays.
  • Consulting: unified view of teams, projects and margins to maximise profitability.
  • Manufacturing: predictive maintenance and quality control connected to production planning.
01
Logistics

The ghost container devouring your margin

3 warehouses · 40 vehicles · 120 employees

Paso 1

El problema de los silos

ERP (SAP)
How much has been invoiced
Where the goods physically are right now
TMS
Truck C-14 is on the A-4 heading south
What order it carries or if the client has complained 3 times this month
WMS
200 pallets in the Getafe warehouse
40 pallets belong to an urgent order from a client with health score 34
HR
Driver Pedro has been driving for 9h
His route includes a critical delivery to a VIP client

An urgent order sits in the warehouse for 72 hours because the WMS doesn't know the TMS has an empty truck 15 km away. The operations director finds out on Monday, after the client has called 4 times.

Paso 2

Mapeo ontológico

Order_4782
status: in_warehouse · priority: urgent · value: €12,400
live
Client_Seur
health_score: 34 · complaints_month: 3 · revenue: €890K
live
Warehouse_Getafe
occupancy: 87% · urgent_pallets: 40
live
Truck_C14
position: A-4 km 32 · load: empty · fuel: 72%
live
Driver_Pedro
hours_driven: 9.1h · mandatory_break_in: 54 min
live
Conexiones en el grafo
Order_4782 → stored_in → Warehouse_Getafe
Order_4782 → belongs_to → Client_Seur (health_score: 34)
Truck_C14 → operated_by → Driver_Pedro
Route_Madrid_South → passes_near → Warehouse_Getafe (15 km)
Paso 3

Decisión y acción de la IA

It's 13:36. The AI agent detects that Order_4782 has been in the warehouse for 71h, the client just filed their 4th complaint, Truck_C14 has just unloaded 15 km away, and the driver has exactly 54 minutes before mandatory rest — enough to pick up and deliver.

1
Reassign Order_4782 to Truck_C14
1.2s
2
Generate loading order at Warehouse_Getafe
0.8s
3
Notify Driver_Pedro of new stop
0.4s
4
Update client ETA to 14:45
0.6s
5
Block 15% discount (no longer needed)
0.3s
Tiempo total: 3.3 seconds
Paso 4

Impacto en el negocio

€372K/year
+ €890K client retention
4 silos conectados
€372,000/year in unnecessary discounts eliminated
Client with €890K/year revenue retained
71h warehouse time reduced to 4h
Zero risk of tachograph fines (up to €4,600/infraction)
Siguiente sector
02
Retail

The store that runs out of stock on its biggest sales day

25 stores · e-commerce · electronics chain

Paso 1

El problema de los silos

POS
Gran Vía sold 14 AirPods today
Central warehouse is at zero and next restock takes 5 days
E-commerce
23 units available (ERP data)
ERP hasn't synced the 14 in-store sales
Marketing
Campaign tomorrow with AirPods at 30% off
Actual stock: 9 units across the entire chain
Purchasing
Standard restock in 2 weeks
The campaign will generate demand for 400+ units

The campaign launches, 400 people buy online, only 9 can be fulfilled. 391 cancellations, 200 negative Google reviews, customer service collapses for 3 days.

Paso 2

Mapeo ontológico

Product_AirPods
real_stock: 9 · ERP_stock: 23 · sell_rate: 3.2 units/hour
live
Campaign_Email_2803
status: scheduled · audience: 45,000 · product: AirPods
live
Supplier_Apple_Dist
urgent_lead_time: 3 days · surcharge: +18%
live
Central_Warehouse
AirPods_stock: 0 · next_restock: 14 days
live
Online_Channel
displayed_stock: 23 (FALSE) · conversion: 4.2%
live
Conexiones en el grafo
Product_AirPods → real_total_stock → 9 (discrepancy with ERP: -14)
Campaign_Email_2803 → promotes → Product_AirPods
Campaign_Email_2803 → estimated_demand → 420 units
Online_Channel → displays_available → 23 (FALSE data)
Paso 3

Decisión y acción de la IA

It's 18:45 the day before the campaign. The AI agent detects real stock is 9 (not 23), the campaign will generate demand for 420 units, and the supplier can do an urgent shipment in 3 days.

1
Correct online stock from 23 → 9 units
0.9s
2
Pause email campaign (blocked by stock)
0.7s
3
Generate urgent purchase order: 500 units
1.1s
4
Reschedule campaign to D+4
0.5s
5
Notify Commercial Director
0.4s
6
Reassign 5 units from Alcalá store → online
0.8s
Tiempo total: 4.4 seconds
Paso 4

Impacto en el negocio

€79K sales
+ €85K reputation
5 silos conectados
391 cancellations and ~200 negative reviews prevented
€79,380 in revenue protected (campaign rescheduled with real stock)
€3,400 surcharge vs €12,000 customer service collapse avoided
+14% rotation in slow-moving products via cross-channel reassignment
Siguiente sector
03
Construction

The site that bleeds money without anyone noticing

8 simultaneous sites · 180 workers · 35 subcontractors

Paso 1

El problema de los silos

ERP (Sage)
Valdebebas site: €2.4M, 45% certified
On-site performance has dropped 30% in 2 weeks
Planning
Structure due by April 15
Rebar subcontractor is 5 days behind
Access control
12 rebar workers entered today
20 are needed to meet the milestone
Purchasing
40 tonnes of steel ordered for Valdebebas
Alcorcón needs 25 tonnes and the supplier only has 50
Safety
Partial stoppage at Getafe
Nobody in Planning has recalculated the impact

The site is delayed 3 weeks. Penalty: €8,000/day. The subcontractor claims an overrun that no one can verify because the data is in 5 separate systems.

Paso 2

Mapeo ontológico

Site_Valdebebas
budget: €2.4M · certified: 45% · slippage: +11 days
live
Milestone_Structure
date: 15/04 · real_progress: 62% · performance: -30%
live
Subcontractor_Ferrallux
workload: 3 sites · delay: 5 days · staff: 12/20
live
Material_Steel_B500
supplier_stock: 50t · orders: 40+25t (deficit: 15t)
live
Site_Getafe
status: partial_stoppage · reason: missing_harnesses
live
Conexiones en el grafo
Site_Valdebebas → requires → Milestone_Structure (deadline: 15/04)
Milestone_Structure → depends_on → Subcontractor_Ferrallux
Subcontractor_Ferrallux → assigned_to → Valdebebas + Alcorcón + Getafe
Material_Steel → deficit → 15t (orders: 65t vs stock: 50t)
Site_Getafe → stoppage → impacts → Ferrallux availability
Paso 3

Decisión y acción de la IA

It's 08:15. Access control logs 12 rebar workers at Valdebebas (20 needed). The AI agent detects Getafe has 8 idle workers, prioritises steel for Valdebebas and documents the subcontractor's SLA breach.

1
Reassign 6 rebar workers from Getafe → Valdebebas
1.0s
2
Prioritise steel order for Valdebebas, defer Alcorcón
0.9s
3
Recalculate schedule: delay from 18 → 4 days
1.3s
4
Formal alert to Ferrallux: SLA breach documented
0.7s
5
Notify Management: penalty reduced €144K → €32K
0.5s
Tiempo total: 4.4 seconds
Paso 4

Impacto en el negocio

€112K penalty
+ €60K contractual
5 silos conectados
€112,000 in penalties avoided on a single site
€60,000 overrun claim blocked with automatic documentation
6 idle rebar workers reassigned at no extra cost
Steel stock-out avoided (estimated dual-stoppage cost: €35,000)
Siguiente sector
04
Consulting

The invisible consultant billing zero

60 people · 15 active projects · €4.8M/year

Paso 1

El problema de los silos

CRM (HubSpot)
Client Telefónica: €180K contract, NPS 6/10
The assigned senior consultant hasn't logged hours in 3 weeks
Time (Toggl)
340h logged of 500h sold
Remaining 160h need 3 weeks and only 1 consultant is available (capacity: 80h)
ERP
60% of the project invoiced
Real hourly cost is 25% higher due to more expensive profiles
HR
Carlos assigned 100% to Telefónica
His actual load is 145% because he covers incidents on 2 other projects
PM (Asana)
3 deliverables still pending
The client hasn't replied to emails in 8 days

The project delivers 4 weeks late at 8% margin (sold at 35%). Carlos leaves due to burnout (replacement cost: €45,000). Telefónica doesn't renew the €180K annual contract.

Paso 2

Mapeo ontológico

Project_Telefonica
hours: 340/500 · margin: 8% · health_score: 38
live
Client_Telefonica
NPS: 6/10 · no_reply: 8 days · contract: €180K
live
Consultant_Carlos
load: 145% · overtime: 62h · churn_risk: HIGH
live
Final_Deliverable
hours_remaining: 160 · deadline: 3 weeks
live
Renewal_Pipeline
value: €180K · probability: 25%
live
Conexiones en el grafo
Project_Telefonica → assigned_to → Consultant_Carlos (load: 145%)
Project_Telefonica → belongs_to → Client_Telefonica (health_score: 38)
Final_Deliverable → requires → 160h in 3 weeks (1 resource, capacity: 80h)
Renewal_Pipeline → depends_on → Client satisfaction (health_score: 38)
Paso 3

Decisión y acción de la IA

It's 09:00 Monday. Carlos logs 11h from Friday. The AI agent connects: health_score 38, 80h capacity deficit, Carlos at 145% load, client unresponsive for 8 days, and 2 junior consultants available at 40%.

1
Reassign 2 junior consultants (60%) to the project
1.1s
2
Remove Carlos from incidents on Acme and Deloitte
0.8s
3
Alert Managing Partner: client at risk, health_score 38
0.5s
4
Schedule call with client: project review
0.7s
5
Recalculate real margin with current profiles
1.0s
6
Flag renewal as "at risk"
0.6s
Tiempo total: 4.7 seconds
Paso 4

Impacto en el negocio

€180K renewal
+ €45K talent
5 silos conectados
€180,000/year contract renewed through early intervention
Margin recovered: from 8% to 22% (€25,200 additional)
Carlos goes from 145% to 95% load — talent retained (saving: €45,000)
Management sees all 15 projects as live objects in real time
Siguiente sector
05
Industrial Manufacturing

The machine that warns before it breaks

3 production lines · 200 employees · 45 clients

Paso 1

El problema de los silos

SCADA/MES
Press PH-07 consumes +22% energy
That machine produces the quarter's largest order
ERP (SAP)
Renault order: 340,000 parts, due 20/04
The machine producing it is showing failure signs
CMMS
PH-07 review scheduled for May
Parameters suggest failure in 7-10 days
Quality
+3.2% rejected parts this week
It comes from PH-07 and correlates with over-consumption
Purchasing
Spare parts stock for standard maintenance
PH-07's O-ring has 12-day lead time and zero stock
Commercial
Renault penalty: 0.5%/day of delay
There is an unplanned stoppage risk

PH-07 breaks down. Part takes 12 days. Line 2 stops for 14 days. Penalty: €84,000. Renault opens a supplier file and the company loses next year's tender (€3.8M).

Paso 2

Mapeo ontológico

Machine_PH07
consumption: +22% · vibration: +15% · rejects: +3.2% · health_score: 41
live
Order_Renault_Q2
parts: 186K/340K · deadline: 20/04
live
Client_Renault
revenue: €1.2M · penalty: 0.5%/day · tender_2027: €3.8M
live
Spare_ORing
stock: 0 · urgent_lead_time: 4 days (+65%)
live
Production_Line_2
capacity: 24K parts/day · efficiency: 89%
live
Conexiones en el grafo
Machine_PH07 → produces → Order_Renault_Q2 (154K parts remaining)
Machine_PH07 → health_score: 41 → estimated_failure: 7-10 days
Client_Renault → active_penalty → 0.5%/day on €1.2M
Quality_Rejects → correlation → PH07_Overconsumption (R²: 0.94)
Paso 3

Decisión y acción de la IA

It's 06:12. PH-07 registers a vibration spike. The AI agent detects: health_score 41, 87% failure probability, Renault order at risk, spare part out of stock but available urgently in 4 days.

1
Reschedule PH-07 maintenance: from May → this Saturday
0.9s
2
Urgent purchase order for O-ring (4-day delivery)
1.1s
3
Increase production on Lines 1 and 3 to cover deficit
1.0s
4
Recalculate production plan: Renault delivery viable on 19/04
0.8s
5
Notify Plant Manager + Commercial Director
0.5s
6
Reduce PH-07 speed by 15% until repair
0.4s
Tiempo total: 4.7 seconds
Paso 4

Impacto en el negocio

€84K penalty
+ €3.8M tender
6 silos conectados
€84,000 penalty completely prevented
€3.8M future tender protected (clean supplier record)
Stoppage cost: €2,740 (planned) vs €196,000 (unplanned)
768 defective parts/day eliminated — saving: €4,200/week

The pattern is always the same

The data is there. The value is there. Trapped between silos that don't talk to each other.

Sector ROI Tiempo Silos
Logistics
€372K/year + €890K client retention 3.3 seconds 4
Retail
€79K sales + €85K reputation 4.4 seconds 5
Construction
€112K penalty + €60K contractual 4.4 seconds 5
Consulting
€180K renewal + €45K talent 4.7 seconds 5
Industrial Manufacturing
€84K penalty + €3.8M tender 4.7 seconds 6

Intellico Ontology doesn't generate new data. It connects what already exists and lets AI agents act with full context in under 5 seconds.

What is an ontology?

Recognise any of these problems?

If your company runs on more than 3 systems that don't talk to each other, you have a silo problem. We can diagnose it in a 30-minute session.