Real use cases

Ontology in action

Five sectors. Five critical problems. A single intelligence layer.

Each use case shows the same pattern: data trapped in silos, decisions made blindly and money evaporating. Ontology connects everything in less than 5 seconds.

Main enterprise ontology use cases

  • Logistics: critical order detection and automatic route reassignment in less than 4 seconds.
  • Retail: connecting stock, online sales and physical store to eliminate inventory breaks.
  • Construction: BIM, ERP and subcontractor integration to prevent overruns and delays.
  • Consulting: unified view of teams, projects and margins to maximize profitability.
  • Manufacturing: predictive maintenance and quality control connected to production planning.
01
Logistics

The phantom 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 on the A-4 heading south
What order it carries or if the customer has complained 3 times this month
WMS
200 pallets in the Getafe warehouse
40 pallets correspond 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 is stuck for 72 hours in the warehouse because the WMS doesn't know the TMS has an empty truck 15 km away. The operations director finds out on Monday, when the client has already 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 · billing: €890K
live
Warehouse_Getafe
occupancy: 87% · urgent_pallets: 40
live
Truck_C14
position: A-4 km 32 · load: empty · fuel: 72%
live
Driver_Pedro
driving_hours: 9.1h · rest_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 warehouse for 71h, the client has opened their 4th complaint, Truck_C14 just unloaded 15 km away and the driver has 54 minutes before mandatory rest — just 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 ETA to client to 14:45
0.6s
5
Block 15% discount (unnecessary)
0.3s
Tiempo total: 3.3 seconds
Paso 4

Impacto en el negocio

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

The store that runs out of stock on its busiest day

25 stores · e-commerce · electronics chain

Paso 1

El problema de los silos

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

The campaign launches, 400 people buy online, only 9 units exist. 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_replenishment: 14 days
live
Online_Channel
stock_shown: 23 (FALSE) · conversion_rate: 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 → shows_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 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 for 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 billing protected (campaign rescheduled with real stock)
€3,400 surcharge vs €12,000 customer service collapse avoided
+14% rotation in stagnant products through cross-channel reassignment
Siguiente sector
03
Construction

The project that bleeds money without anyone noticing

8 simultaneous projects · 180 workers · 35 subcontractors

Paso 1

El problema de los silos

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

The project is delayed 3 weeks. Penalty: €8,000/day. The subcontractor claims an overrun that nobody can verify because the data is in 5 different systems.

Paso 2

Mapeo ontológico

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

Decisión y acción de la IA

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

1
Reassign 6 steelworkers from Getafe → Valdebebas
1.0s
2
Prioritize steel order for Valdebebas, delay Alcorcón
0.9s
3
Recalculate schedule: delay from 18 → 4 days
1.3s
4
Formal alert to Ferrallux: documented SLA breach
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 penalty avoided in a single project
€60,000 overrun claim blocked with automatic documentation
6 idle steelworkers reassigned at no additional cost
Steel stockout avoided (double shutdown 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 for 3 weeks
Hours (Toggl)
340h billed of 500h sold
The remaining 160h require 3 weeks and there's only 1 consultant (capacity: 80h)
ERP
60% of the project invoiced
The actual hour cost has increased 25% by using more expensive profiles
HR
Carlos assigned 100% to Telefónica
His real load is 145% because he covers incidents on 2 more projects
PM (Asana)
3 deliverables pending closure
The client hasn't responded to emails for 8 days

The project is delivered 4 weeks late with 8% margin (sold at 35%). Carlos leaves due to burnout (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_response: 8 days · contract: €180K
live
Consultant_Carlos
load: 145% · overtime: 62h · rotation_risk: HIGH
live
Final_Deliverable
remaining_hours: 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
Unassign Carlos from incidents on Acme and Deloitte
0.8s
3
Alert to 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
Mark 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 retention (savings: €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 largest order of the quarter
ERP (SAP)
Renault order: 340,000 pieces, delivery 04/20
The machine producing it shows signs of failure
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 overconsumption
Purchasing
Spare parts stock for standard maintenance
The PH-07 O-ring has 12-day lead time and stock: 0
Commercial
Renault penalty: 0.5%/day of delay
There is risk of unplanned shutdown

PH-07 breaks down. Part takes 12 days. Line 2 stops for 14 days. Penalty: €84,000. Renault opens a 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
pieces: 186K/340K · deadline: 04/20
live
Client_Renault
billing: €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 pieces/day · efficiency: 89%
live
Conexiones en el grafo
Machine_PH07 → produces → Order_Renault_Q2 (154K pieces remaining)
Machine_PH07 → health_score: 41 → estimated_failure: 7-10 days
Client_Renault → penalty → 0.5%/day on €1.2M
Quality_Rejects → correlation → Overconsumption_PH07 (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, failure probability 87%, Renault order at risk, spare not in 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 days)
1.1s
3
Increase production on Lines 1 and 3 to cover deficit
1.0s
4
Recalculate planning: delivery viable by 04/19
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 record)
Shutdown cost: €2,740 (planned) vs €196,000 (unplanned)
768 defective parts/day eliminated — savings: €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 + client retention €890K 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's Ontology doesn't generate new data. It connects the data that already exists and allows AI agents to act with total context in less than 5 seconds.

What is an ontology?

Do you recognize any of these problems?

If your company operates with 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.