Øglænd Integration Hub
One bridge between every internal system — the foundation the AI tools build on.
Data that flows through the hub
Modelled once, governed centrally, served to every app.
Products & SKUs
from M3The full catalogue — families, series, variants.
Bills of materials
from C4 + VaultAssemblies and component structures.
Stock & lead time
from M3Live availability and delivery windows.
Prices & discounts
from M3Customer pricing, agreements, currency.
CAD models
from Vault3D geometry and drawings per article.
Certifications & EPDs
from VaultStandards, approvals, environmental data.
Trusted by design, not by exception
The hub centralises data — so it also centralises control. One owner per entity, one gateway for access, encrypted in flight and at rest, with every read and write traced back to its source system.
Single source of truth
One owner per entity — the hub never invents data, it federates it.
- M3 owns commercials — price, stock, lead time, customer agreements.
- Vault owns engineering — CAD models, drawings, certifications, EPDs.
- C4 owns configuration — valid variants, rules, bill-of-materials logic.
Role-based access control
Who can read or write which entity, enforced at the policy gateway.
- Sales — read price, stock, catalogue; no engineering write.
- Engineering — read/write CAD, BOM structures and certifications.
- Partners & distributors — scoped read of public price + availability only.
Encryption everywhere
Data is protected on the wire and on disk — never plain-text.
- In transit — TLS 1.2+ on every source, hub and app connection.
- At rest — AES-256 on the hub store and its backups.
- Mutual auth (mTLS) on system-to-system source links.
Audit logging & lineage
Every read and write is traced back to its origin system.
- Immutable audit trail — who, what, when, from which system.
- Provenance — each field carries its source (M3 / Vault / C4).
- Tamper-evident logs streamed to a central SIEM.
Data quality & validation
The hub boundary is where messy source data becomes a golden record.
- Schema validation rejects malformed records at ingest.
- Dedup & matching collapses duplicates into one golden record.
- Reconciliation flags drift between source systems.
Compliance & privacy
Contacts and commercial data handled to GDPR and internal policy.
- GDPR — lawful basis, retention limits and erasure for contacts.
- Periodic access reviews — least-privilege re-certified each quarter.
- Secrets in a managed vault — rotated, never in code or config.
Today every tool re-integrates point-to-point with M3, Vault and C4. The hub is the single bridge: data is modelled, governed and served once. The Bid BOM Matcher already reads the product catalogue; once the hub is live it also reads real-time stock, lead time and price — turning a matched bid into a quotable, deliverable order.
- 1
Catalogue & BOM
DoneAlready done in the Bid BOM Matcher.
- 2
Hub: live stock + price
NextReal-time availability and pricing on every match.
- 3
Quote-to-order
One flow across all apps — matched bid to deliverable order.
