iD4ConnectTechnologyScalability

Start small, grow without redoing everything.

A first DataCell on one objective, then others on the same engine, then other sites. What has been built once is reused: you only add what changes.

Request a demo Follow the project

The project we followThe press 2 efficiency DataCell, extended to the whole workshop, then to a second site.

Site 1: press 2, then the whole workshopSite 2: the same DataCell, imported

01Addfloor 1

One more source, not one more project.

Press 3 arrives: its source joins the existing DataCell. One importer can serve several sources, and everything downstream, the business object, the calculation and the outputs, is already in place.

press-3: connected
importer: the same one, reused

See the DataCell

Press 3: one more sourceThe same importer

02Reusefloor 2

Built once, deployed as often as needed.

A chain that works is saved as a blueprint in the library. The creation path then offers it: press 4 is deployed from it, with its own parameters.

blueprint: press efficiency
deployed: presses 3 and 4

One blueprint, deployed three timesIts own parameters, every time

03Separatefloor 3

One objective, one DataCell.

Tracking the workshop's energy has no place in the efficiency DataCell: it has its own DataCell, on the same engine. Each one keeps its own configuration, counters, alarms and log.

DataCells: efficiency, energy
engine: just one

Workshop Energy DataCellThe same engine, another DataCell

04Extendfloor 4

A second site, the same DataCell.

The DataCell exports to a file; beforehand, the screen lists the credentials that travel with it. On the second site's engine, it is imported: iD4Connect Core checks what it accepts and rejects the rest.

site 1: DataCell export
site 2: imported, checked

Site 2: the imported DataCellChecked by its engine

05Overseefloor 5

Each site keeps its own engine.

Each site has its own iD4Connect Core, next to its equipment. The interface reaches each one at its address: nothing is centralized, and a site's data never leaves it.

north site: core.site-nord.lan
south site: core.site-sud.lan

See the architecture

One interface, one engine per siteNothing is centralized

Scalability in exploded view: five floors of a site, one per step, from the project room and the sources at the top to monitoring at the bottom, with the data running through them.

A demo, on your own sites.

We look with you at where to start, and how to extend from there.

Request a demo