PredCo Data Core

The data centralization stack underneath every PredCo solution.

Manufacturing data is stranded across machines, cameras, ERP, documents, and field logs, in five different shapes with no shared identifier. The Data Core ingests all of it, resolves it into one governed source of truth, and serves it through a single contract. Every solution we ship reads from it.

Signal types5
PerimeterYours
Source of truthOne
Signal → decisions
  • Machine & PLCTelemetry
  • VisionCamera feeds
  • ERPTransactions
  • ComplianceDocuments
  • ServiceField logs
Five signal types, one perimeter, one source of truth

Every AI project in manufacturing dies in the same place.

Not in the model. In the eighteen months spent trying to get five incompatible systems to agree on what a part, a machine, and a shift actually are.

01
Five data shapes, no shared key
Telemetry, video, transactions, documents, and field logs each arrive in their own format, cadence, and identifier scheme.
02
Point tools multiply the problem
Each new vendor builds its own integration and its own copy of the data. Six tools later there are six versions of the truth.
03
Documents are a dead end
Supplier declarations, service reports, and drawings hold critical operational data that no system can query.
04
Governance is retrofitted
Lineage and access control get bolted on after deployment, which is exactly when an auditor asks how a number was produced.

The Data Centralization Stack

Heterogeneous shopfloor signals become one governed source of truth. Select any layer to inspect what it does.

Data flows upwardSelect a layer to inspect it
queryable intelligence · one contract
governed records + metadata
Layer 04 of 06

Unified Data Core

Three stores under one governance layer: time-series for signals, structured for transactions and BOMs, object for documents and video. Lineage and access control sit across all three.

INMapped, resolved records
OUTGoverned records + metadata
Modules in this layer
Version ControlLineage & Audit TrailRole-Based Access ControlModel Registry
Without this layer

There is no single answer to what is true — only six dashboards and a meeting to decide which one to believe.

mapped · parsed · resolved
typed, buffered data
raw signal · OT stream + IT batch
Five signal typesOne perimeterOne source of truth

21 modules, assembled into solutions.

Nothing here is bespoke. Every PredCo solution is composed from these modules, which is why the second use case on a site costs a fraction of the first. Open any module to see how it works.

Data & Integration

Getting every signal in, whatever shape it arrives in.

Governance & Trust

The reason a regulator, an auditor, or a customer will accept the output.

Intelligence

The models, and the plant context that makes them worth trusting.

Action & Delivery

Turning a finding into something a person actually does.

Built to clear an enterprise and public sector gate.

The technical evaluation is rarely the hard part. Licensing structure, data residency, and documentation are.

Licensed as one stack
The Data Core is licensed once. Solutions are enabled on top of it rather than procured as separate disconnected tools.
Sovereign by default
On-premise, air-gapped, or in-country cloud. Data residency is a deployment choice, not a paid upgrade.
Tender-ready specification
We supply the technical specification, architecture, and compliance documentation your procurement process needs.
No rip and replace
The Data Core reads your existing SCADA, ERP, CMMS, and historian. Nothing gets migrated to make it work.

The specification sheet.

What your IT and OT teams will want to see before the first workshop.

Deployment models
On-premise · Air-gapped · Private cloud · Hybrid
Edge inference
NVIDIA Jetson / IGX, or customer-supplied GPU
Industrial protocols
OPC-UA · Modbus TCP · MQTT · BACnet · M-Bus
Enterprise systems
SAP S/4HANA & ECC · Oracle · MS Dynamics · Maximo
Engineering systems
Teamcenter · Windchill · Aras
Camera support
Any RTSP / ONVIF feed, no replacement required
Identity & access
SAML 2.0 · OIDC · Azure AD · Okta · role-based
Egress
Optional. Air-gapped deployments fully supported.
Now onboarding new deployments

Bring one problem. We'll show you the deployment.

A 30-minute working session with our engineering team. No slideware. Bring a real operational problem and leave with a concrete view of what a PredCo deployment looks like for your plant.

4 hrs
Average response time
4–6 wks
Kickoff to live pilot
On-prem
Sovereign deployment supported