Skip to main content
Jira progress: loading…

TRFM

Transformation Engines

1. Overview

Transformation Engines (TRFM) are micro-engines responsible for converting data between units, formats, and structural representations while preserving semantic meaning.

TRFM engines ensure that data is normalized and interoperable across computation, aggregation, and reporting layers.

TRFM is an engine type within the MICE taxonomy.

2. Design Principles

  1. Semantic Preservation
    Transformations must not change the meaning of the data.

  2. Reversible Where Possible
    Transformations should be reversible or traceable.

  3. Explicit Mapping Rules
    All transformations are defined by explicit, versioned rules.

3. Scope of Responsibility

3.1. What TRFM Engines Do

  • Unit conversion (e.g. kg → tons)
  • Format conversion (e.g. XML → JSON)
  • Structural reshaping of payloads
  • Normalization of representation

4. What TRFM Engines Do Not Do

  • ❌ Compute new values (CALC)
  • ❌ Validate correctness (VALI)
  • ❌ Aggregate across entities (AGGR)
  • ❌ Estimate missing data (SEM)

5. Inputs

  • Validated input or output payloads
  • Transformation rule definitions
  • Target schema or unit context

6. Outputs

  • Transformed payload
  • Transformation metadata
  • Provenance references

TRFM outputs commonly feed:

  • AGGR
  • Reporting pipelines
  • Interoperability layers

7. Canonical Identification

  • Engine Type: TRFM
  • USO Code: TRFM
  • Category: Micro Engine (MICE)
  • CALC — Calculation Engines
  • VALI — Validation Engines
  • AGGR — Aggregation Engines

Status: Stable
Owner: Computation Hub / MICE



GitHub RepoRequest for Change (RFC)