← Return to the planisphereUP Robotics · industrial demonstrator

UP ROBOTICS · ZAGREB · INDUSTRIAL DEMONSTRATORThe codebase that survives contactO1 CORPUS · O4 EVALUATION HALFPLC CABINETMANIPULATOR CELLLINEPLC codeLADDER LOGIC · IEC 61131-3Robot programsMANIPULATOR · CELL · GRIPPERSCADA configsSUPERVISORY · HMI · ALARMSMaintenance logsEVENTS · FAULTS · REPAIRSSYMPHONY SUBSTRATEHalf of the held-out task instances · O4STREAM · MAINTENANCE LOGSevents · faults · repairs
Years of maintenance-engineer log entries — fault descriptions, repair notes, replacement-part references. The closest thing the system has to its own rationale layer; supplies half of the O4 held-out task instances.
UP Robotics · Zagreb · Croatia

UP Robotics

The Croatian industrial-automation shop whose production-system codebase the SYMPHONY substrate has to survive contact with. Demonstrator partner; supplier of half the held-out task instances for the O4 evaluation.


I · Role

The industrial coalface

UP Robotics is the engineering shop that supplies SYMPHONY’s industrial-automation demonstrator codebase. Where Newcastle contributes the mathematical primary source, CREATE the architectural primary source, and Real AI the integration and coordination, UP Robotics contributes the production system that the substrate has to survive contact with.

Industrial code does not behave like open-source code. It is structured by IEC 61131-3 conventions, written in vendor-specific dialects (KRL, KAREL, RAPID, URScript, ladder logic, structured text), versioned across decades, and lived in by a small number of maintenance engineers whose institutional memory is the system’s rationale layer.

II · Four data streams

What UP Robotics contributes to the substrate

Istream

PLC code

Ladder diagrams, structured text and function block diagrams from the programmable-logic controllers that run the line. Real-time-predictable, rarely commented, decades of authorship.

IIstream

Robot programs

Vendor-specific motion routines, path libraries, calibration files for the manipulators and end-effectors. Often touched by many engineers over a single system's life.

IIIstream

SCADA configs

Supervisory-control configurations, HMI screens, alarm databases, historian tags. The layer operators see — the one that survives engineer turnover.

IVstream

Maintenance logs

Years of maintenance-engineer log entries — fault descriptions, repair notes, replacement-part references. The closest thing the system has to a rationale layer.

III · Why this matters

Without a real industrial system, SYMPHONY is a paper claim

A neuromimetic knowledge substrate that works on a curated open- source benchmark but breaks on production industrial code is a publication, not a contribution to European industrial competitiveness. The O4 benchmark mixes 100 instances from OSS issue trackers with 100 instances from UP Robotics’s maintenance logs precisely to surface this failure mode if it exists.

O4 evaluation protocolM30 decision milestone

200 engineering-task instances. Half sourced from open-source issue trackers, half from UP Robotics’ maintenance logs. Threshold: ≥ 20 % relative F1 improvement on task-relevant- subgraph recovery and ≥ 15 % expert-rated actionability, averaged across task classes — against three named baselines (frontier LLM agent, EAKG static-analysis pipeline, LLM + RAG).

If improvement holds on OSS but fails on industrial code, the §1.3 alternative path narrows the claimed scope and documents the domain-transfer gap as a scientific finding. The fact that this alternative exists at all is what makes the protocol honest.

IV · The exploitation vehicle

Real AI × UP Robotics — the joint venture

UP Robotics and Real AI have agreed in principle on a joint venture as the primary exploitation vehicle for the SYMPHONY substrate. UP Robotics brings the customer relationships in industrial automation across Croatia and the wider region; Real AI brings the foundation-model engineering and the coordinator role. Read the full go-to-market and IP plan in the proposal.