Solution architecture

Pro.File PLM solution architecture: one platform at the center, everything else earns its place around it.

Pro.File holds the master data. Each Cre8tive solution connects to it for one clear job, and your ERP sits on the other side, reached through two purpose-built connections, not a tangle.

PLM connectionERP connectionMoving dots show data traveling both ways · hover a node for details

The map

Hub, spokes, and one supplement

Revalize Pro.File sits at the center as the system of record. Five Cre8tive solutions connect to it as spokes, each one solving a single problem, none of them talking to each other. The Reports & Extensions Library supplements the platform from the inside. Your ERP sits off to one side, reached only through Cre8 Hub and the Document Viewer Portal.

Reading the map

Why it is shaped this way.

Three deliberate decisions sit behind the diagram, and each one is the reason the architecture stays maintainable as it grows.

Spokes never touch each other

Every solution connects to the platform, not to its neighbors. Nothing breaks when one is added, upgraded, or left out, and there is never a question about which system owns the data.

The ERP gets two doors, not a tunnel

Engineering data reaches Epicor Kinetic, or whatever you run, through Cre8 Hub, and its users reach drawings through the Document Viewer. Two purpose-built paths, each one auditable on its own.

The library is part of the core

Reports and extensions run inside Pro.File itself: nothing to host, nothing to connect. That is why the map draws the library docked to the hub instead of orbiting it.

The architecture at work

Three journeys across the map.

The diagram is only interesting because of what travels along it. Here is what those moving dots actually represent.

PLM → Cre8 Hub → ERP

A released BOM reaches the shop floor

Engineering releases a revision in Pro.File. Process Task Automation advances the change process and sets the status; Cre8 Hub sees the release, maps the structure, and writes the parts and BOM into Epicor Kinetic. Nobody re-types a part number, and the two systems agree on what is current.

ERP → Document Viewer → PLM

An operator needs the drawing behind a work order

The work order in ERP names a part. The Document Viewer Portal resolves it against Pro.File and returns the current released drawing: read-only, in a browser, with no PLM license and no printed copy to go stale on a bench.

Portal → PLM

A problem found on the floor gets back to engineering

The same operator raises a problem report from the portal, with a photo, against the exact part and revision. It lands in Pro.File where engineering already works, and Process Task Automation moves it into the review queue without anyone chasing it.

See it live