04 How it works: graphs, meaning, agents, and why codes aren't enough
Educate
14:30
Coffee
14:45
05 Workshop: map your world, find the wicked questions
Work
15:45
Wrap-up & next steps
Why we're here
What we want you to leave with
Inspiration
A picture of what becomes possible when data, not software, sits at the centre of a substation project or a wind farm.
Vocabulary
Semantic models, knowledge graphs, agentic programming: enough to judge what is real, what is hype, and what it means for your systems.
A shortlist
Two or three use cases worth piloting, ranked by you: by business impact and by whether the data is already there.
Who we are
QAECY builds Cue
Cue reads an organisation's documents and data, recognises the things they are about, and connects every mention into one knowledge graph: the Cue Index. People and AI agents can then ask it questions, with a source behind every answer.
Philipp DohmenCEO & co-founder
Manos ArgyrisCTO & co-founder
Mads Holten RasmussenCIO & co-founder
Your turn
Around the table
Who are you and what do you work on?
Where does information get lost between design, yard and operations?
If your data could answer one question tomorrow, what would you ask?
Two businesses
Two businesses, one data question
Substations
Design, plan and build offshore and onshore substations.
Different businesses, same question: how do you get the most out of data that mostly comes from others: clients, OEMs, TSOs, suppliers?
01
You don't run software. You run on data.
01 The landscape
Ten systems, ten pictures of your world
ERP
Finance, purchasing, stock, hours
CRM
Customers, bids, contracts, change requests
CAD & 3D
Models, line lists, equipment lists
Document control
Specs, drawings, transmittals, comments
Planning
Schedules, baselines, look-aheads
Weight control
Weight reports, CoG, lift studies
Yard progress
Spreadsheets, punch lists, photos
QHSE
Procedures, NCRs, incidents, audits
Maintenance
Work orders, assets, spare parts
HR & competence
Certificates, training, crews
And in between: Excel exports, e-mail, Teams, status meetings, copy-paste. People are the integration layer.
Every system has its own picture of your world. None of them is yours.
01 Time
Applications come and go. The data stays.
An offshore substation outlives three or four generations of every application around it. Each switch is a migration, and every migration loses context.
01 The ERP question
Why roll out another traditional ERP?
The traditional rollout
You adapt your processes to the vendor's data model
Multi-year implementation, and a lot of consultants
Customisation is expensive and locks you in further
Engineering, the yard and the field still live outside it
The data-centric way
Model your world as you see it: substations, modules, zones, turbines, tasks
Agents build the interfaces each team needs, in days
Swap applications, keep the data. Open standards: RDF, OWL, SPARQL
Keep ERP for what it's good at: finance, payroll, purchasing
Not "no ERP". ERP as one source among many, not as the model of your company.
01 What changed
When software is cheap, the model is the asset
AI agents now write working software from a description. When an interface costs days instead of months, you stop buying one big system and bending to it.
You generate the interfaces each team needs, all on one shared model of your world.
Semantic modelyour world, your words
Weight dashboard
Yard progress
Bid assistant
Technician briefing
Change impact
Customer portal
Interfaces
Spares finder
01 Semantic model
Your world, described in your words
Facts the model holds
OSS-2has partTopside
Module M3containsTransformer T1
T1must satisfyREQ-0412
T1delivered underPO 4500-1832
WP-214located inZone L2-B
InspectionfollowsPR-118 rev 8
Engineering, ERP, CRM, schedule and O&M: one graph, one identifier per thing.
01 Combine
What if it all came together?
ERP
Cost, purchase orders, deliveries, hours
CRM
Customers, contracts, change requests
Yard progress
% complete per zone, punch items, photos: live
Location-based schedule
Which crew works where, and when
One connected model of OSS-2
Reality vs. plan, per location, as it happens
Cost and change traced to the zone and the customer
Early warnings, before the schedule slips
01 Live from the yard
See the topside as it really is
Progress per zone from the yard, compared with the plan for that zone this week.
On planAheadSlightly behindBehind
61 %
complete
68 %
planned, wk 33
Two zones behind. One waits for piping, one for a late PO. Both reasons come from other systems.
Illustrative
01 Location-based schedule
Plan vs. reality, per location
Each line is a trade moving through the topside. Where two lines meet, two crews want the same zone at the same time.
Illustrative
01 Ask
Questions no single system can answer
Which late purchase orders block zones where E&I starts in the next six weeks?
ERPScheduleModel
Three POs: cable trays (L3-A), UPS (L3-C), HVAC dampers (L2-C). First impact in week 35.
How does our E&I productivity per zone compare with plan, and with OSS-1?
YardScheduleHistory
−14 % on L2. OSS-1 had the same dip on deck 2: late piping handover.
Which customer change requests touched the transformer bays, and what did they cost?
CRMERPDocuments
CR-019 and CR-031: 11 documents revised, +€0.42 M, +18 t.
If module M3 slips two weeks, when is the earliest sail-away?
ScheduleModelWeather
Week 47 instead of 45, unless L3 gets an E&I night shift (cost estimate attached).
Illustrative answers
01 Keep the clay wet
Don't freeze the design before you have to
Most early decisions aren't taken because they must be. They're taken because nobody can see what depends on them.
Decide nowTransformer configuration: 70-week lead time puts it on the critical path.
Keep openGIS layout: nothing depends on it until week 30.
01 The last responsible moment
Know the consequences before freedom runs out
Freedom to change drops fast. Knowledge about consequences arrives late, usually when steel is being cut. Connected data moves that knowledge forward, so you can decide later and with better information.
01 How
What keeps the clay wet
Decisions as data
Every decision linked to its assumptions, the requirements behind it and the items it fixes. Change an assumption, see which decisions wobble.
Options side by side
Carry two or three configurations in the model and compare weight, cost and schedule on demand, not in a two-week study.
Real deadlines
The last responsible moment, computed from supplier lead times (ERP) and the installation sequence (schedule), not from habit.
Impact on demand
"What changes if…" answered in minutes. Late changes stop being scary when you can see exactly what they touch.
02
Substations: design & planning
02 Boundary conditions
The design starts outside the design
Before the first line is drawn, the seabed, the sea, the wind farm, the vessels and the market have already decided a lot.
Most of it arrives as reports and spreadsheets from other parties, and it changes along the way.
02 Boundary conditions
What sets the boundaries? Let's talk.
Seabed & geotechnics
Soil profiles, CPTs, boulders, UXO, scour
How late can new CPT data still change the pile design?
Metocean
Waves, wind, current, air gap, ice
Who owns the design basis when the data is updated?
The wind farm
Capacity, number of turbines, array voltage, layout
What changes on the topside if the client adds 100 MW?
Grid connection
TSO requirements, grid codes, onshore connection point
Where do grid-code changes enter your design?
Installation vessels
Crane capacity, availability, weather windows
What if the heavy-lift vessel slips six weeks?
Ports & yard
Quay capacity, draught, laydown, load-out
Which yard limits shape the module split?
Permits & environment
Consent conditions, piling noise, marine life
Which consent conditions reach the detailed design?
Supply chain
Lead times for transformers, GIS, cables; prices
Which long-lead items decide the schedule today?
Which of these arrive as data, which as PDFs, and who tells you when they change?
02 Boundary conditions
One outside fact, a chain of decisions
Follow a single boundary condition into the design.
Heavy-lift vesselCrane capacity and availability in the installation window
Max lift weightTopside incl. rigging, contingency and weight growth
Transformers & module splitTwo large units or three smaller ones? One lift or two?
Layout & deck heightsBays, fire walls, CoG envelope
Jacket & pilesLoads checked against the seabed data
The vessel slips six weeks. Someone has to remember which studies, drawings and purchase orders depend on it, and who owns them.
In a graph
The constraint is linked to everything it limits. Change it, and the whole chain lights up, with the documents and owners attached. That is what keeps the clay wet.
02 Anatomy
One asset. Many thousands of facts.
Thousands of requirements, tens of thousands of documents, hundreds of suppliers, and it has to work for decades without anyone living on it.
02 Use cases
Where Cue helps in design & planning
Requirements traceability
Every clause from client specs, grid codes and standards, linked to the item that must satisfy it, with status.
SpecsStandardsDatasheets
Change impact
A change request in, a full impact out: weight, CoG, documents, POs, schedule.
CRMModelERPSchedule
Weight & CoG control
Weight reports reconciled with the model and vendor data continuously, not only at milestones.
Weight reportsVendor dataModel
Interface management
Jacket, topside, cables, TSO, client: every interface as data, with an owner, a status and the correspondence behind it.
Interface registerE-mailMinutes
Tender & reuse
"Have we done this before?" Similar past projects, their lessons and their real numbers.
Past projectsERPLessons learned
Document control
Latest revision, open comments, who is waiting on whom: asked, not searched.
DMSTransmittalsComments
02 Use case · Requirements traceability
From clause to component, with evidence
Client technical specification · rev 4p. 112
7.3 Main power transformers
7.3.2 The EQUIPMENTmain power transformers shall have a sound power level not exceeding VALUE85 dB(A) at MODEONAF cooling.
7.3.4 Tank and radiators shall be protected for corrosivity category STANDARDCX per ISO 12944.
7.3.7 Transport weight per unit shall not exceed VALUE285 t.
7.3.9 ACTIVITYFactory acceptance tests shall be witnessed by the ORGCompany.
Requirement
Linked to
Evidence
Status
REQ-0412 Sound ≤ 85 dB(A)
T1, T2
Datasheet rev C: 82 dB(A)
Compliant
REQ-0415 Coating CX
T1, T2 tanks
Coating spec CS-07
Compliant
REQ-0419 Weight ≤ 285 t
T1, T2
Vendor GA rev B: 291 t
Deviation Query raised
REQ-0421 FAT witnessed
T1
ITP rev 2
Open
Across the project: 1,284 requirements in 46 specifications. 37 have no linked item yet.
Illustrative
02 Use case · Change impact
CR-031: the customer asks for +10 % transformer rating
What does it touch? Today: two weeks of meetings. With a connected model: a query.
+18 t topside weight, CoG +0.6 m east: jacket & lift check
11 documents to revise across 3 disciplines
PO 4500-1832 variation: +9 weeks, set-in moves to week 40
Illustrative
02 Onshore
Same model, other end of the cable
Signal lists and protection settings kept consistent from offshore to onshore
TSO and grid-code requirements traced like client specs
One interface register for both ends of the export cable
02 Use case · Tender & reuse
"Have we done this before?"
We're bidding a 1.2 GW AC offshore substation for the North Sea, delivery 2030. What have we done that's similar, and what did we learn?
Searched 14 past projects: specs, lessons learned, ERP actuals
Ranked by capacity, voltage, region and topside type
Pulled the three lessons that cost the most
Project
Similarity
Topside
Lesson that cost the most
Project A 900 MW · North Sea · 2023
High
3,900 t
Late transformer vendor data caused three weight re-baselines
Project B 1.0 GW · Baltic · 2025
High
4,400 t
E&I started before piping handover: 11 % productivity loss
Project C 750 MW · Irish Sea · 2021
Medium
3,100 t
J-tube design frozen too late for the cable installer
Lessons learned A, B, CERP actualsClose-out reports
Illustrative: project names anonymised
03
Wind farm O&M: taking over parks
A different business: running existing wind farms after the OEM, and growing it.
03 Where Semco comes in
A park comes with ten years of someone else's data
Build
OEM service & warranty Vestas, Siemens Gamesa
Independent O&M: Semco the business to grow
Life extension or repowering
Year 0~ Year 1–10Year 10+Year 25+
You inherit the history
OEM service reports, SCADA history, component swaps and retrofits. In OEM formats and codes, and rarely complete.
Productive from day one
Known issues, procedures, spare parts and bulletins have to be understood before the first boat leaves.
Know the park before you bid
Growing means winning more parks. The faster you read a data room, the sharper the price and the lower the risk.
03 The fleet
Every park you take over is a new fleet, with someone else's paperwork
Years of OEM service reports, SCADA history and modifications
Different turbine types, codes and document systems per park
Technicians, certificates, vessels, weather windows, spare parts
03 Use cases
Where Cue helps in wind farm O&M
Takeover & due diligence
Read the data room before the bid, and turn it into one history per turbine after the win.
OEM reportsSCADARegisters
Predictive maintenance
Signals plus context: which turbine, which component, why now, and what it shares with failures elsewhere.
SCADACMSInspectionsBulletins
Work-order preparation
Everything the team needs for this task on this turbine, in one pack, before they leave port.
CMMSProceduresHistory
Spares & logistics
In stock, on the vessel or eight weeks away, matched against the weather window.
ERPVessel planForecast
Competence & briefings
New park, new turbine type: who knows the procedures, and who needs a briefing first?
HRTrainingProcedures
Reporting & contracts
The owner's report written from field data, and every task checked against the service agreement.
Requirements change faster than people can read them. The gap is where incidents and rework come from.
Illustrative
03 From requirements to formats people use
Cue knows what changed, for whom, for which task
Procedures & revisionsOEM service bulletinsHSE alerts & regulationsTurbine historyLessons learnedTraining records
Compares revisions, matches them to the task, the turbine and the person, and writes the briefing from the sources.
Podcast briefing
Eight minutes on the CTV transit
Video instructions
Step by step, in the technician's language
AR guidance
At the component, hands-free
Check & sign-off
Three questions, acknowledged, traceable
03 Podcast briefing
Briefed on the boat, not on paper
Morning briefing WTG C03 · Tue 12 Nov
02:41 / 08:12EN · DA · PL
PR-118 rev 8SB-2026-14C03 history
HostMorning. You're heading to C03 today: pitch bearing inspection on blade B. Two things have changed since you last did this task.
ExpertFirst, greasing. It's no longer "until you see fresh grease". It's 380 grams per nipple, at most two strokes every ten seconds. The OEM found seal-lip damage from over-greasing; that's service bulletin 14.
HostSecond: C03 had grease leakage at segment 4 in March. Photograph every segment this time; the photos go straight into the work order.
ExpertSeal kits are already on the vessel. Weather window closes at three. Stay safe out there.
Illustrative script, generated from the sources shown
03 Video instructions
Generated from the procedure, rendered from the model
00:00
1 · Lock the pitch systemRotor lock engaged, pitch in maintenance mode.PR-118 §3.1
00:24
2 · Clean the seal areaLint-free cloth, all segments.PR-118 §4.2
00:51New in rev 8
3 · Grease: 380 g per nippleMax. 2 strokes per 10 s. Don't over-grease.PR-118 §4.3 · SB-2026-14
01:20New in rev 8
4 · Photograph each segmentUploads straight to WO-88140.PR-118 §4.5
Rendered in the technician's language: EnglishDanskPolskiDeutsch
03 AR in the field
Hands-free, at the bolt, always the current revision
Step-by-step guidance anchored to the component
Changes since your last visit flagged in view
Torque values logged by the tool, straight into the work order
WO-88231WTG D04 · TOWER T2/T3REC ●
03 Closing the loop
Field data flows back
Photos, torque values and findings from the task go back into the Cue Index. Fleet patterns surface, procedures get better, and the next briefing is sharper.
Fewer repeat visitsEvidence for the ownerWarranty claims with proof
04
How it works
Semantic models, knowledge graphs and agents, without the hype.
04 From documents to answers
Read. Recognise. Connect.
1
Read every page
Inspection of TURBINEWTG C03 on DATE14 Mar 2026 by PERSONJ. Pedersen found grease leakage at LOCATIONsegment 4 of the blade B pitch bearing, per DOCUMENTPR-118 rev 7.
PDFs, scans, spreadsheets, drawings, e-mail, in any language.
2
Recognise the things
WTG C03Turbine · 214 mentions
PR-118Procedure · 8 revisions
J. PedersenTechnician · 61 tasks
Segment 4Location on bearing
"C03", "WTG-C03" and "turbine C3": one thing, not three.
3
Connect into a graph
Every fact keeps a link to the page it came from.
Stop searching. Start asking.
04 What is a graph?
Things, and how they relate
Nodes
The things: a turbine, a bearing, a bulletin, a person.
Edges
How they relate. Named, directed, and data in their own right, not hidden in a join table.
Properties
The details, on nodes and on edges.
No fixed shape
A new kind of thing or relation is just another node or edge.
04 Knowledge graph 101
A fact is three things
Transformer T1— must satisfy →REQ-0412Subject, predicate, object: a fact that people and machines can both read.
has partlocated inmust satisfydelivered underfollows
Defined once, in Semco's terms. Changes when your business changes, not when a vendor releases.
Instances: your facts
OSS-2Module M3T1REQ-0412L2-BWP-214WTG C03
Millions of them, from every system and document, each with one identifier.
Open W3C standards: RDF · OWL · SPARQLNo lock-in: your graph is portableOne identifier per thing, across every system
04 Why graphs are flexible
New questions, new edges. Nothing breaks.
Day 1 · asset register
Turbines and their parts, with RDS-PP codes as properties.
Day 30 · a bulletin arrives
Two new kinds of edge. The register is untouched.
Day 90 · logistics
Tasks, vessels and weather join. Day-1 questions still work.
Tables: new tables, a migration, and every report that joins them needs fixing. So the change is postponed.
Graph: add the edges. The model grows with the business, one question at a time.
04 Querying by meaning
Ask for what things are, not what they're called
The ontology says
Component
Rotating equipment
Bearing
Pitch bearing
Main bearing
Yaw bearing
Gearbox
Generator
# Which bearings come from a batch named in SB-2026-14?SELECT?bearing?turbineWHERE {
:SB-2026-14:appliesTo?batch .
?bearinga/rdfs:subClassOf*:Bearing ;
:fromBatch?batch ;
:partOf?turbine .
}
Asking for Bearing also finds pitch, main and yaw bearings, because the ontology says they are bearings.
Ask for Rotating equipment and gearboxes and generators come along. Nobody had to tag them twice.
"C03", "WTG-C03" and "turbine C3", in English, Danish or OEM speak, point to one identifier.
04 Agents query by meaning too
An agent reads your vocabulary, then asks the graph
Which turbines have bearings from the batch in SB-2026-14, and were any of them greased the old way since March?
index_schemaRead the vocabulary: Bearing, Batch, Bulletin, Task, Procedure
index_searchFind SB-2026-14 and the batch it names
index_traverseFollow applies to → from batch → part of → inspected
Keep tasks done under PR-118 rev 7 or earlier
The agent never needs your table names. It reads what your things mean, over MCP, and every step stays traceable.
Answer
9 turbines in 2 parks carry bearings from batch 7731. 3 were greased under rev 7 since March: B05, C03, E02.
SB-2026-14WO-87112WO-87440WO-87903
Suggested next step: brief the C03 crew before Tuesday.
Illustrative · tool names from the Cue MCP server
04 RDS-PP
A code for every thing
The Reference Designation System for Power Plants gives each object in a wind farm or substation an unambiguous, hierarchical code.
#DK.NSA01Conjoint the plant
=G001Main system wind turbine 1
MDA10System rotor system
BT002Basic function temperature measurement
=
Function
What it does. The backbone of the designation.
−
Product
What realises it: the transmitter -BT001 and its cable -WG001.
+
Location
Where it sits: in a cabinet (+) or in a space such as the nacelle (++).
Valuable: one code across owner, OEM and service company, and asked for by many owners.
VGB / vgbe RDS-PP for wind; example after soedera.eu
04 Codes and graphs
A code shows one perspective. A graph carries many.
RDS-PP · function aspect
RDS-PP says what a thing is and where it sits. The graph keeps that, adds what it is connected to, and links the owner's, the OEM's and your own codes for the same bearing.
×
by
