Governed Metrics, Auditable Calculations, and Full Provenance
EKAS governance is built around deterministic, versioned metric definitions and full data lineage. Every calculation is traceable, auditable, and reproducible — critical for manufacturing environments that answer to finance teams, customer audits, and regulatory bodies.
Versioned Metric Definitions
Every metric in EKAS — OEE, downtime tracking, First Pass Yield, capacity utilization — is defined in versioned SQL with a cryptographic hash. When metric logic changes, the version increments and the hash updates. Historic calculations remain tied to the definition that generated them.
- SQL logic stored in version-controlled catalog
- SHA-256 hash on every metric definition
- Historic results tied to definition version
- No silent drift in calculation methods
Full Data Provenance
Every metric result includes the full provenance chain: which SQL definition executed, which data source provided the input, how many records were queried, and the UTC timestamp of calculation. Audit trail is automatic, not optional.
- SQL hash and catalog version on every result
- Data source, record count, and timestamp
- Query execution plan logged for review
- IATF 16949 audit trail by design
Role-Based Metric Access
Not all metrics should be visible to all users. EKAS enforces role-based access to metric definitions, dashboards, and export capabilities. Plant managers see shift performance; executives see portfolio-level trends; finance sees cost attribution.
- Role-based dashboard and report access
- Metric visibility controlled by tenant policy
- Query permissions enforced at database layer
- Audit log of who accessed what, when
Zero-Compromise Release Policy
EKAS enforces a four-tier defect classification. Priority 0 defects — incorrect financial results, access control violations, incorrect OEE calculations — block all releases until fully resolved. Every defect at any priority triggers documented root cause analysis, corrective action, and preventive measures, with an immutable audit trail.
This standard exists because manufacturing teams make real operational decisions from EKAS outputs. A wrong cost figure or a bypassed access control is not a UX issue — it is an operational and compliance risk. The zero-compromise policy treats it accordingly.
See Governance in Action
Bring a question about metric traceability. We'll show you the full provenance chain.