01
Inline · structural · permanent
Lineage by default
Source system, load run, timestamp, row hash: recorded on every record, every load. The record of where the data came from is created with the data itself.
iMC(InFocus Metadata Client).
Data you can trust from the moment it arrives. Connect all of your sources with lineage, quality, provenance, governance, and PPDM-standard identifiers captured inline with every ingestion, never retroactively.
Inline with every ingestion
Identity attached the moment it arrives.
iMC is not a separate cataloging project. Metadata is captured at the same moment as the record, creating a trusted foundation without a second pass.
Source → BronzePer record · every load
RECORD
+ Lineage
load run · source · hash
RECORD
+ Quality
per-record score
RECORD
+ Dimensions
PPDM keys
RECORD
+ Event
provenance fired
Raw record in · trusted record stored
No retroactive cataloging
The cheapest record to fix is the one that never entered the warehouse dirty.
Every data team pays the same tax: discovered bad data, weeks after the fact. By the time a quality failure surfaces in a dashboard, it has already propagated through silver and gold layers, into reports, into decisions, and into questions you cannot answer with confidence.
Without iMC
LineageReconstructed by hand
QualityAudit, weeks later
DimensionsReconciled per-report
ProvenanceSlack thread
With iMC
LineageInline · per record
QualityAt ingestion
DimensionsPPDM-resolved
ProvenanceQueryable · day one
Five capabilities
Four moves at ingestion. One audit trail.
iMC runs inline with every pipeline. Every load captures metadata, validates rules, persists results, and emits a signed audit. None of it is a separate workstream.
02
Per-record · inline · fail fast
Quality at ingestion
Rules execute as part of the load itself, against every record. Failures surface immediately, before bad data propagates to silver, gold, or anything that depends on it.
03
Standards-aligned · versioned
Dimension resolution
Raw values from source systems become PPDM-standard identifiers at the moment they enter the platform. Cross-source questions become routine queries, not reconciliation projects.
04
mTLS · Vault · smoke-test gated
Security and trust
Mutual TLS enforced end-to-end with no disable flag. Credentials flow from Vault at runtime. Zero secrets in logs, outputs, or audit trails: by construction.
05
Immutable · signed · PPDM-aligned
Audit and compliance
Every record is timestamped, sourced, scored, and resolved. Every deployment produces a signed ledger entry. Audit queries are routine SQL.
In production
Every record arrives with a complete identity.
100%
Provenance · every record
26w → 3h
Platform deploy time
62+
Wells live · single client · growing to ~500
0
Untracked actions
- Single E&P Operator Deployed
Want the full iMC brochure?
The platform architecture, all five capabilities, in-production case study, and what changes when metadata is structural.