+30 210 220 8436
+30 210 220 8436
KIREAS Fabric

OT/IT integration through one governed data layer.

KIREAS Fabric puts a governed data layer between the plant floor and the enterprise. Plant data is normalized, given context and exposed through one documented API, so OEE, MES, ERP and BI tools consume the same model instead of each building its own connection to the machines.

The plant floor and the enterprise have always been separate stacks. Fabric is the layer where they meet: OT data flows up, IT requests come down, and both sides work from one model they trust. We scope it as a design phase first, with the data model and API as the deliverable.

The documented data model is the main deliverable, and it belongs to you. Your own team can maintain and extend it, and no system is tied to a single integrator.

Network cables connected to a switch in a rack
The challenge

Why point-to-point integration breaks.

  • ERP, MES, BI and cloud tools each connect to the plant floor in their own way.
  • Each connection can only be maintained by the people who built it.
  • The same signal carries different names and meanings in different systems.
  • IT and OT each own half of the problem, and nobody owns the boundary between them.
  • Every new consumer of plant data reopens the question of how far the control network is exposed.
What we deliver

What KIREAS Fabric delivers.

Normalized plant data

Data from multiple PLCs and SCADA systems normalized to OPC UA through Kepware.

A shared semantic model

Assets, signals and their context organized in one consistent model, agreed with both OT and IT.

One documented API

Standard REST and OPC UA interfaces that ERP, MES, BI and cloud consumers use in the same way.

A controlled OT/IT boundary

A segmented architecture in which plant data reaches the enterprise side over authenticated, encrypted OPC UA, so no DCOM traffic crosses the boundary.

Documentation you own

The data model and the API documented and handed over as your asset, not a black box.

How it is built

What the layer is built from.

Proven products from our partners, each in the layer it does best — integrated and commissioned by our engineers.

  • KepwareNormalizes heterogeneous PLC and SCADA data to OPC UA and links a plant-side server to a server in the DMZ over encrypted OPC UA.
  • Velotic Data HubContextualizes plant data into one semantic model and exposes standardized APIs. A new product: we confirm availability and fit with Velotic when we scope the project.
  • Proficy HistorianHolds the plant history. Where the plant already runs Proficy, the governed layer can sit on its REST API and read-only SQL access.
  • Proficy Operations HubConsumes the governed data for web applications and connects to REST, SQL and OPC UA sources.
How we deliver

How we deliver it.

  1. 01

    Scope sources and consumers

    Which plant systems, which enterprise consumers, which entities, and whether each flow is read-only or bidirectional.

  2. 02

    Design the model

    We agree the semantic model and its governance with an OT owner and an IT sponsor, so both sides sign off.

  3. 03

    Build the layer and its interfaces

    Connectivity, context model and APIs, tested against the agreed consumers.

  4. 04

    Document and hand over

    The model and API documentation become your asset, handed over to the team that will maintain them.

FAQ

Questions we are often asked.

Will enterprise systems be able to write to our PLCs?

Only where you decide they should. Each data flow is defined as read-only or bidirectional during scoping, with both the OT and the IT owner involved.

Do we have to replace our existing integrations at once?

No. The layer can go live between the agreed plant sources and a first enterprise consumer; further connections are scoped afterwards.

Who owns the data model?

You do. The model and the API are documented and handed over, so your own team, or any integrator you choose, can maintain them.

How does this relate to KIREAS Data Foundation?

Data Foundation connects and historizes the plant. Fabric sits above it and gives every enterprise system one governed way in to that data.

Map your plant-to-enterprise data flows.

Book a 30-minute engineering call. Bring the list of systems that need plant data, and we will sketch where a governed layer fits.

GET IN TOUCH

Got a plant-floor problem worth talking about?

BOOK A DISCOVERY CALL

30 minutes with an engineer.

No sales-engineer hand-off. You speak to the same person who'd scope, design, and commission the project. Tell us what's running, what's drifting, and what would change the P&L — we'll come back with a phased approach and a budgetary number.

OFFICEDimitriou Gounari 96, Marousi 151 25, Athens
HOURSMon–Fri · 09:00–17:00 EET
Contact Form epikoinonias