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. Hover any node to see what it does and how it talks to the rest.
Three deliberate decisions sit behind the diagram — and each one is the reason the architecture stays maintainable as it grows.
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.
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.
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 diagram is only interesting because of what travels along it. Here is what those moving dots actually represent.
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.
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.
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.
We will map your systems onto this picture — the ERP you actually run, the CAD you actually use — and show you what the connections do live.
Request a Demo