Energy Delivery & Consumption Standard (EDCS)

EGA™ Standards & Modules Index

Energy Delivery & Consumption Standard (EDCS)

Architecture: Energy Governance Architecture (EGA™)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: Parent Standard

Governed Space: Physical Energy Delivery, Final Consumption, Delivery Interfaces, Consumption Boundaries, End-

Use Energy Demand, Delivered Energy Quantities, Energy Carrier Compatibility, Consumer-Side Operating

Conditions, Demand Constraints, Consumption Attribution, Measurement Integrity & Delivery-Consumption

Accountability

Standard ID: EGA-EDCS-06

Origin ID: OOF-EGA-EDCS

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. Canonical Definition

Energy Delivery & Consumption Standard (EDCS) is the sixth Parent Standard within Energy Governance

Architecture (EGA™).

EDCS establishes the methodological governance requirements for identifying, characterizing, assessing, validating,

and maintaining evidence-supported representations of physical energy delivery and final energy consumption.

It governs the physical relationship between energy made available at a delivery interface, energy actually transferred

across that interface, energy received within a defined consumption boundary, and energy used by identifiable

consuming systems.

EDCS recognizes that energy generation, transmission, distribution, storage, delivery, and consumption are distinct

physical processes.

Energy generated does not automatically become energy delivered.

Energy transmitted through a network does not automatically become energy received by a final consumer.

Energy available at a delivery interface does not establish that the intended consumer has received or consumed it.

Energy received by a consumer does not automatically establish useful energy output, productive work, or operational

value.

The standard therefore requires explicit separation between energy availability, physical delivery, receipt,

consumption, end-use conversion, and useful output.

It applies to electricity, thermal energy, fuels, hydrogen, mechanical energy, and other physically identifiable energy

carriers.

Its governance requirements are technology-independent, while physical measurement, delivery conditions, and

consumption models remain carrier-specific.

EDCS establishes a traceable governance foundation for determining what energy was delivered, where it crossed a

defined boundary, which consuming system received it, what quantity was consumed, under which operating

conditions, and with what evidence.

Its principal governance output is the Energy Delivery & Consumption Governance Profile.

2. Architectural Position

EDCS governs the final delivery and consumption stage of the primary physical energy lifecycle.

Energy Source & Origin → Energy Generation → Energy Conversion → Energy Transmission & Distribution

↔ Energy Storage → Energy Delivery & Consumption

The preceding standards establish the physical origin, generation, transformation, movement, and storage of energy.

EDCS establishes the boundary at which energy becomes available to a receiving system and the subsequent

physical consumption of that energy.

It does not replace the preceding standards.

It establishes a distinct governance layer connected to them through identifiable physical interfaces, quantities,

operating conditions, and evidence.

3. Core Question

How can physical energy delivery and final consumption be identified, measured, attributed, and validated so

that energy availability, actual delivery, received energy, consumed energy, and useful end-use output remain

distinguishable under real operating conditions?

4. Foundational Principle

Energy delivery and consumption must be governed according to energy physically transferred, received,

and used within defined boundaries under actual operating conditions—not merely contracted quantities,

scheduled supply, nominal demand, installed consumer capacity, or assumed useful output.

The foundational distinctions are:

Scheduled Energy ≠ Delivered Energy.

Available Supply ≠ Actual Delivery.

Delivered Energy ≠ Consumed Energy.

Received Energy ≠ Useful Energy Output.

Installed Consumer Capacity ≠ Actual Consumption.

Energy Demand ≠ Energy Supplied.

Commercial Allocation ≠ Physical Consumption Attribution.

Metered Quantity ≠ Automatically Validated Quantity.

5. Purpose

EDCS establishes a consistent methodological framework for governing the final physical stages of energy delivery

and consumption.

Its purpose is to prevent unsupported equivalence between energy supply commitments, physical delivery,

consumption measurements, and end-use performance.

It enables energy delivery and consumption assessments to remain physically grounded, temporally consistent,

traceable, and interoperable with the wider EGA™ architecture.

6. Governance Objectives

EDCS establishes requirements to:

1. Identify physical energy delivery interfaces.

2. Identify receiving systems and consuming assets.

3. Define delivery and consumption boundaries.

4. Classify relevant energy carriers.

5. Distinguish scheduled, available, delivered, received, and consumed energy.

6. Identify applicable delivery conditions.

7. Assess physical delivery capability and restrictions.

8. Identify actual end-use consumption.

9. Preserve consumer-side operating conditions.

10. Distinguish consumption from useful output.

11. Support evidence-based delivery and consumption measurement.

12. Preserve energy carrier and unit consistency.

13. Prevent unsupported consumption attribution.

14. Identify measurement uncertainty and conflicts.

15. Preserve delivery and consumption continuity.

16. Support machine-readable governance assessments.

7. Governed Space

Physical Energy Delivery, Final Consumption, Delivery Interfaces, Consumption Boundaries, End-Use Energy

Demand, Delivered Energy Quantities, Energy Carrier Compatibility, Consumer-Side Operating Conditions,

Demand Constraints, Consumption Attribution, Measurement Integrity & Delivery-Consumption

Accountability

The governed space begins at an identifiable physical energy delivery interface.

It includes energy transfer into a receiving system, subsequent physical consumption, relevant consumer-side

constraints, measurement evidence, and applicable attribution.

It concludes with an evidence-supported delivery and consumption governance determination.

8. Governed Objects

EDCS governs identifiable physical and assessment objects, including:

Energy Delivery Interface

Energy Receiving System

Energy Consumer

Consuming Asset

Consumption Boundary

Energy Carrier

Delivery Quantity

Received Energy Quantity

Consumption Quantity

Demand Reference

Delivery Condition

Consumer Operating State

Measurement Point

Delivery Assessment

Consumption Assessment

Governance Determination

Each material object must possess a stable identity or traceable reference appropriate to the assessment.

9. Physical Energy Delivery

Physical energy delivery occurs when energy crosses a defined delivery boundary into an identified receiving system.

EDCS requires the delivery boundary to be explicit.

Relevant elements include:

Delivery Interface

Energy Carrier

Physical Direction

Receiving System

Assessment Interval

Delivered Quantity

Measurement Evidence

A contractual delivery obligation does not independently establish physical delivery.

10. Energy Receiving System

An energy receiving system is the physical system that receives energy across an identified delivery boundary.

Examples include:

Industrial Electrical Installation

District Heating Customer Installation

Hydrogen Receiving Facility

Fuel Receiving System

Mechanical Energy Receiving Equipment

The receiving system must remain distinguishable from the final consuming equipment where material.

11. Final Energy Consumption

Final energy consumption represents energy used by an identifiable end-use system within a defined physical

boundary.

It may involve:

Electrical Consumption

Thermal Consumption

Fuel Consumption

Chemical Energy Consumption

Mechanical Energy Consumption

The definition must preserve the applicable physical energy form and accounting boundary.

12. Delivery Boundary

A delivery boundary identifies the physical interface at which energy is transferred into the receiving system.

It may correspond to:

Electrical Connection Point

Heat Delivery Interface

Fuel Transfer Point

Hydrogen Delivery Interface

Mechanical Energy Transfer Interface

The boundary must be physically meaningful and supported by applicable evidence.

13. Consumption Boundary

A consumption boundary identifies the physical extent of the consuming system being assessed.

Relevant boundaries include:

Facility Boundary

Building Boundary

Production Process Boundary

Equipment Boundary

End-Use Service Boundary

Different boundaries may produce different consumption quantities.

They must not be treated as interchangeable.

14. Delivery Versus Consumption

Energy delivered to a receiving system may differ from energy consumed by its final end-use equipment.

Differences may arise from:

Internal Distribution Losses

Intermediate Storage

On-Site Energy Conversion

Auxiliary Consumption

Unmeasured Internal Transfers

Changes in Internal Energy Inventory

EDCS requires these distinctions to remain explicit.

15. Energy Carrier Identification

Every delivery and consumption assessment must identify the relevant energy carrier.

Examples include:

Electricity

Hot Water

Steam

Natural Gas

Hydrogen

Liquid Fuels

Mechanical Energy

Different carriers require appropriate physical measurement and accounting methods.

16. Energy Carrier Compatibility

Energy delivery must be evaluated against the physical requirements of the receiving system.

Relevant characteristics may include:

Voltage

Frequency

Temperature

Pressure

Flow Rate

Fuel Composition

Energy Quality

A compatible nominal energy quantity does not independently establish that the energy can be used by the intended

consumer.

17. Scheduled Energy

Scheduled energy represents an intended or planned energy transfer.

EDCS requires scheduled quantities to remain distinguishable from actual delivered quantities.

A schedule may be modified, interrupted, curtailed, or unfulfilled.

18. Contracted Energy

Contracted energy represents an energy quantity or service established through a contractual arrangement.

EDCS may preserve contractual references where relevant.

However, contractual quantities must not substitute for evidence of physical delivery or consumption.

19. Available Energy Supply

Available energy supply represents energy that may be physically accessible at a defined supply boundary under

applicable conditions.

Availability does not independently establish delivery.

The distinction must remain explicit.

20. Actual Delivered Energy

Actual delivered energy represents the energy quantity physically transferred across the defined delivery boundary

during the assessment interval.

EDCS requires:

Physical Boundary

Energy Carrier

Measurement Interval

Energy Quantity

Measurement Method

Evidence

The quantity must not be inferred solely from a contractual or scheduled value.

21. Received Energy

Received energy represents energy entering the defined receiving system.

Where delivery and receiving boundaries coincide, the quantities may be equivalent.

Where boundaries differ, relevant intermediate transfers or losses must be accounted for.

22. Actual Consumed Energy

Actual consumed energy represents energy used within the defined consumption boundary during the relevant

assessment interval.

EDCS requires the quantity to remain distinguishable from:

Delivered Energy

Received Energy

Stored Energy

Useful Output

Consumption must be supported by appropriate measurement or estimation evidence.

23. Useful Energy Output

Useful energy output represents energy transferred into an intended useful form or service under a defined end-use

boundary.

Examples include:

Useful Heat

Mechanical Work

Process Thermal Energy

Useful Electrical Output from End-Use Conversion

EDCS preserves the distinction between energy consumed and useful output.

Detailed conversion efficiency governance remains within ECS and EELS where applicable.

24. Energy Demand

Energy demand represents the energy requirement associated with a defined consuming system and assessment

interval.

Demand may be:

Forecast

Scheduled

Requested

Observed

Unserved

EDCS requires demand classifications to remain explicit.

25. Demand Versus Consumption

Demand does not automatically establish actual consumption.

A consuming system may request energy that is unavailable or restricted.

Conversely, actual consumption may differ from forecast demand.

EDCS requires both quantities to remain independently identifiable.

26. Unserved Energy Demand

Unserved demand represents a defined energy requirement that was not physically satisfied.

EDCS must preserve:

Demand Reference

Assessment Interval

Relevant Consumer

Delivered or Consumed Quantity

Unserved Quantity

Evidence

An unserved-demand conclusion must not be inferred from incomplete measurement data alone.

27. Delivery Capability

Delivery capability represents the physically permissible transfer of energy across the delivery interface under

applicable conditions.

Relevant restrictions may include:

Interface Capacity

Energy Carrier Conditions

Equipment Availability

Operating Limits

Supporting Infrastructure

Delivery capability must remain distinguishable from actual delivered energy.

28. Consumer-Side Operating Constraints

Consuming systems may be restricted by:

Equipment Availability

Permissible Input Conditions

Temperature Limits

Pressure Limits

Electrical Limits

Process Requirements

EDCS requires material restrictions to remain identifiable.

29. End-Use Equipment Identity

Material consuming equipment must be identifiable where its identity affects the assessment.

Relevant elements include:

Equipment ID

Energy Carrier

Rated Input

Operating State

Consumption Boundary

Evidence

Installed equipment does not automatically establish active consumption.

30. Installed Consumer Capacity

Installed consumer capacity represents the rated or design energy input capability of installed consuming equipment.

It must remain distinguishable from:

Actual Demand

Actual Consumption

Useful Output

Installed capacity does not establish the quantity of energy consumed during a particular interval.

31. Consumer Operating State

EDCS recognizes relevant operating states:

Operating

Standby

Restricted

Unavailable

Under Maintenance

Unknown

The operating state must correspond to the assessment interval.

32. Partial Consumption

A consuming system may receive less energy than requested or operate below its nominal input capacity.

EDCS must distinguish:

Requested Consumption

Permissible Consumption

Actual Consumption

Partial consumption must not automatically be classified as an energy delivery failure.

33. Multiple Delivery Interfaces

A receiving system may receive energy through multiple delivery interfaces.

EDCS requires:

Individual Interface Identity

Energy Carrier

Delivered Quantity

Measurement Boundary

Assessment Interval

Aggregation must avoid double counting.

34. Multiple Consuming Assets

A receiving system may contain multiple consuming assets.

EDCS must preserve material relationships between:

Receiving System

Internal Distribution

Consuming Assets

Measurement Points

Aggregate consumption must not automatically be attributed equally to all assets.

35. On-Site Generation

A consumer may also possess on-site generation infrastructure.

EDCS must distinguish:

Externally Delivered Energy

On-Site Generated Energy

Internally Consumed Energy

Exported Energy

The presence of on-site generation must not invalidate the distinction between delivery and consumption boundaries.

Generation governance remains assigned to EGS.

36. Behind-the-Meter Storage

A receiving system may include internal energy storage.

EDCS must distinguish:

Energy Delivered to the Facility

Energy Charged into Storage

Energy Discharged from Storage

Final Energy Consumption

Storage energy transfers must not automatically be classified as final consumption.

Storage-specific governance remains assigned to ESS.

37. Consumer-Side Energy Conversion

A consuming system may convert delivered energy into another physical form.

Examples include:

Electricity to Heat

Fuel to Mechanical Work

Electricity to Mechanical Work

Steam to Process Heat

EDCS preserves input and output boundaries.

Detailed conversion-process governance remains within ECS.

38. Internal Distribution

Energy may pass through internal infrastructure after crossing the delivery boundary.

Relevant examples include:

Facility Electrical Distribution

Building Heating Circuits

Industrial Steam Networks

Fuel Distribution Lines

EDCS must preserve internal distribution relationships where material to consumption accounting.

39. Internal Delivery Losses

Energy may be lost between the delivery interface and the final consuming asset.

EDCS requires material differences to remain identifiable.

Detailed efficiency and loss assessment may involve EELS.

Unexplained differences must not automatically be classified as verified physical losses.

40. Consumption Measurement

Consumption may be established through:

Direct Metering

Submetering

Process Measurements

Calculated Energy Quantities

Engineering Estimation

The method must correspond to the physical energy carrier and boundary.

41. Delivery Measurement

Delivery measurement must preserve:

Measurement Point ID

Delivery Interface ID

Energy Quantity

Unit

Measurement Interval

Measurement Method

Evidence

Measurement integrity must be evaluated before the quantity is treated as validated.

42. Measurement Point Hierarchy

EDCS recognizes multiple measurement levels.

Delivery Interface Meter

Receiving System Meter

Internal Distribution Meter

Consuming Asset Meter

Process-Level Measurement

Different measurement levels must not be aggregated without accounting for their physical relationships.

43. Measurement Boundary Consistency

Delivery and consumption measurements must use explicitly defined boundaries.

A measurement taken at a facility entrance may differ from a measurement taken at individual consuming equipment.

The difference must be physically interpreted rather than assumed to be measurement error or loss.

44. Measurement Interval Consistency

EDCS requires compatible time intervals for related energy quantities.

Relevant elements include:

Start Time

End Time

Sampling Interval

Aggregation Method

Missing Data

Temporal Uncertainty

Misaligned intervals must not produce unsupported consumption conclusions.

45. Physical Unit Consistency

Energy quantities must use compatible units.

Examples include:

Joules

Kilowatt-Hours

Megawatt-Hours

Gigajoules

Power and energy must remain distinguishable.

Relevant carrier-specific quantities must be converted only through physically justified methods.

46. Thermal Delivery Measurement

Thermal delivery may require measurement of:

Mass or Volume Flow

Supply Temperature

Return Temperature

Fluid Properties

Assessment Interval

Thermal energy calculations must use physically appropriate methods.

47. Fuel Delivery Measurement

Fuel delivery may require:

Delivered Mass or Volume

Fuel Composition

Heating Value Basis

Temperature and Pressure References

Assessment Interval

A fuel volume without appropriate reference conditions may be insufficient to establish its energy content.

48. Electrical Delivery Measurement

Electrical delivery may require:

Active Energy Measurement

Connection Point Identification

Measurement Direction

Assessment Interval

Meter Configuration

Electrical energy delivered must remain distinguishable from installed electrical capacity.

49. Mechanical Energy Delivery

Mechanical energy delivery may involve:

Torque

Angular Displacement

Force

Linear Displacement

Mechanical Power

Operating Duration

Appropriate physical measurement methods must be used.

50. Consumption Attribution

Consumption attribution identifies the physical consuming system or asset associated with an energy quantity.

EDCS requires attribution to be supported by:

Consumption Boundary

Measurement Point

Asset Identity

Physical Connection

Assessment Interval

Administrative cost allocation must not substitute for physical consumption attribution.

51. Shared Consumption Infrastructure

Multiple consuming assets may share delivery or measurement infrastructure.

EDCS must identify:

Shared Interfaces

Common Meters

Internal Distribution

Individual Consumer References

Consumption attribution must preserve any allocation uncertainty.

52. Estimated Consumption

Consumption may be estimated where direct measurement is unavailable.

Relevant methods may include:

Operating-Hour Models

Equipment Load Models

Process-Based Calculations

Engineering Estimates

Estimated consumption must remain explicitly classified.

53. Consumption Reconciliation

EDCS may reconcile:

Delivered Energy

Received Energy

Internal Transfers

Stored-Energy Changes

Consumed Energy

Identified Losses

Reconciliation must use compatible boundaries and assessment intervals.

An unexplained residual must remain identifiable.

54. Consumption Evidence

Relevant evidence may include:

Meter Records

Submeter Records

Equipment Operating Logs

Process Measurements

Engineering Models

Delivery Records

Inspection Evidence

Evidence must correspond to the actual consuming system and relevant assessment period.

55. Evidence Sufficiency

EDCS requires evidence sufficiency to be evaluated against the intended conclusion.

Relevant questions include:

Is the Delivery Interface Identifiable?

Is the Receiving System Identifiable?

Is the Consumption Boundary Explicit?

Is the Energy Carrier Known?

Are Delivered and Consumed Quantities Distinguished?

Are Measurement Intervals Compatible?

Are Material Uncertainties Preserved?

Insufficient evidence must remain explicit.

56. Delivery Evidence Conflict

Conflicts may arise from:

Contradictory Meter Records

Different Delivery Boundary Definitions

Inconsistent Energy Carrier References

Conflicting Delivery Intervals

Incompatible Physical Connection Records

Material conflicts must remain preserved until reconciled.

57. Consumption Evidence Conflict

Conflicts may arise from:

Contradictory Consumption Measurements

Inconsistent Submeter Records

Different Consumption Boundaries

Conflicting Equipment Operating States

Incompatible Estimation Models

Material conflicts must not be silently resolved through unsupported assumptions.

58. Evidence Reconciliation

Reconciliation may involve:

Meter Comparison

Physical Boundary Verification

Measurement Interval Alignment

Equipment Status Review

Engineering Model Review

Energy Carrier Verification

The original evidence and reconciliation justification must remain traceable.

59. Delivery & Consumption Uncertainty

EDCS requires explicit treatment of uncertainty affecting:

Delivered Energy

Received Energy

Consumed Energy

Demand Estimates

Consumer Attribution

Measurement Boundaries

Energy Carrier Conditions

Operating States

Unknown uncertainty must not be represented as zero.

60. Confidence Classification

EDCS applies the EGA™ confidence framework.

Confirmed — Sufficient applicable evidence supports the conclusion.

Reconciled — The conclusion is supported through justified evidence reconciliation.

Estimated — The conclusion relies on explicit modeling or estimation.

Conflicted — Material evidence supports incompatible conclusions.

Unknown — Available evidence is insufficient.

Confidence must apply to the specific delivery, consumption, or attribution conclusion.

61. Governance Determinations

EDCS supports:

PASS — Applicable governance requirements are satisfied.

CONDITIONAL — The conclusion is supported subject to explicit limitations.

FAIL — One or more mandatory requirements are not satisfied.

INDETERMINATE — Evidence is insufficient or materially conflicting.

NOT APPLICABLE — The assessed requirement does not apply.

A PASS does not independently establish contractual compliance, equipment safety certification, regulatory

compliance, or useful-energy efficiency.

62. Delivery & Consumption Accountability

EDCS requires traceable references connecting:

Energy Delivery Interface

Receiving System

Consuming Asset

Energy Quantity

Assessment Interval

Measurement Evidence

Governance Determination

Physical accountability must remain distinguishable from legal liability or commercial settlement.

63. Delivery Continuity

Energy delivery conditions may change over time.

Relevant changes include:

Interface Modification

Supply Restriction

Consumer Connection Change

Meter Replacement

Energy Carrier Change

Delivery Boundary Revision

Historical delivery assessments must preserve the applicable configuration.

64. Consumption Continuity

Consumption patterns may change through:

Equipment Installation

Equipment Removal

Operating Schedule Changes

Process Modifications

Energy Carrier Substitution

Measurement Revisions

EDCS requires material changes to remain traceable.

65. Historical Assessment Integrity

Historical assessments must distinguish:

Physical Valid Time

When the delivery, consumption, configuration, or operating condition physically applied.

Evidence Availability Time

When the relevant evidence became available to the assessment process.

An original historical as-of assessment must use only evidence available by its defined cutoff.

Later evidence may support a separately identified retrospective reassessment.

It must not silently replace the original historical assessment.

66. Evidence Corrections

Corrections must preserve:

Original Record

Corrected Record

Correction Reason

Evidence Availability Time

Affected Assessment References

Corrections must not destroy the historical evidence chain.

67. Cross-Standard Boundary Integrity

EDCS must preserve the distinction between its governed space and adjacent standards.

ESOS — Energy Source & Origin Standard

Establishes source and origin references.

EGS — Energy Generation Standard

Governs physical generation.

ECS — Energy Conversion Standard

Governs physical conversion processes.

ETDS — Energy Transmission & Distribution Standard

Governs external transport infrastructure and flow.

ESS — Energy Storage Standard

Governs storage capacity, operating capability, retention, losses, and continuity.

EDCS governs physical delivery and final consumption.

68. Cross-Cutting Governance Relationships

EDCS supports the following EGA™ standards:

ESBS — Energy System Balancing Standard

Provides evidence about actual demand, delivery, and consumption.

EMRS — Energy Measurement & Reconciliation Standard

Provides delivery and consumption measurement references.

EFAS — Energy Flow Attribution Standard

Provides physical consumption attribution evidence.

EELS — Energy Efficiency & Loss Standard

Provides consumption-side energy quantity and boundary references.

ESRS — Energy Supply Reliability Standard

Provides evidence about delivered energy and unserved demand.

EEIS — Energy Environmental Impact Standard

Provides consumption-related energy carrier and quantity references.

ECDS — Energy Claims & Disclosure Standard

Provides evidence relevant to delivery, consumption, and energy-use claims.

69. Parent Standard Governance Requirements

A conforming EDCS implementation must satisfy the following requirements.

Delivery Identity & Boundaries

1. Establish identifiable physical energy delivery interfaces.

2. Identify relevant receiving systems.

3. Identify material consuming assets.

4. Define delivery boundaries.

5. Define consumption boundaries.

6. Identify relevant energy carriers.

7. Preserve physical delivery directionality.

8. Distinguish delivery interfaces from consumption points.

9. Preserve material physical connection references.

10. Maintain stable delivery and consumption identities.

Delivery & Consumption Quantities

11. Distinguish scheduled from delivered energy.

12. Distinguish contracted from physically delivered energy.

13. Distinguish available supply from actual delivery.

14. Identify actual delivered energy where assessable.

15. Identify received energy where assessable.

16. Identify actual consumed energy where assessable.

17. Distinguish consumption from useful output.

18. Identify relevant demand references.

19. Preserve unserved-demand assessments where applicable.

20. Maintain physical unit and energy carrier consistency.

Operating Conditions & Attribution

21. Identify material delivery conditions.

22. Identify material energy carrier compatibility requirements.

23. Identify relevant consumer-side operating constraints.

24. Preserve consuming equipment operating-state references.

25. Distinguish installed consumer capacity from actual consumption.

26. Identify material internal distribution relationships.

27. Distinguish on-site generation from externally delivered energy.

28. Distinguish storage transfers from final consumption.

29. Preserve material shared consumption infrastructure.

30. Support evidence-based consumption attribution.

Measurement & Evidence

31. Identify relevant delivery measurement points.

32. Identify relevant consumption measurement points.

33. Preserve applicable measurement methods.

34. Align relevant assessment intervals.

35. Evaluate evidence sufficiency.

36. Identify material measurement conflicts.

37. Reconcile conflicting evidence where possible.

38. Preserve unresolved accounting residuals.

39. Evaluate material measurement uncertainty.

40. Apply appropriate confidence classifications.

Governance & Continuity

41. Produce evidence-supported delivery determinations.

42. Produce evidence-supported consumption determinations.

43. Preserve material delivery configuration changes.

44. Preserve material consumption configuration changes.

45. Maintain historical assessment integrity.

46. Preserve original and corrected evidence records.

47. Prevent future-evidence leakage into historical as-of assessments.

48. Maintain cross-standard physical boundary integrity.

49. Support machine-readable governance outputs.

50. Produce an Energy Delivery & Consumption Governance Profile.

70. Governance Logic

Delivery Interface → Receiving System → Energy Carrier → Delivery Boundary → Delivered Energy →

Internal Energy Transfers → Consumption Boundary → Consumed Energy → Measurement Evidence →

Governance Determination

For demand:

Consumer Identity → Demand Reference → Available Delivery → Actual Delivery → Actual Consumption →

Unserved Demand Assessment

For attribution:

Measurement Point → Physical Boundary → Consuming Asset → Energy Quantity → Assessment Interval →

Evidence

For reconciliation:

Delivered Energy → Internal Transfers → Stored-Energy Changes → Consumed Energy → Identified Losses

→ Residual Assessment

The governance logic must preserve the distinction between physical delivery, receipt, and final consumption.

71. Five Core Modules

EDCS consists of five Core Modules.

Module 1 — EDIM: Energy Delivery Identification Module

Operational Role: Establishes the identities, physical boundaries, energy carriers, receiving systems, consuming

assets, and delivery and consumption interfaces required for traceable physical energy delivery and end-use

assessment.

Principal Output: Energy Delivery Identity & Boundary Profile.

Module 2 — DCAM: Delivery Capability Assessment Module

Operational Role: Evaluates physical delivery capability, energy carrier compatibility, delivery interface constraints,

available supply conditions, and the feasibility of specified energy transfers to receiving systems.

Principal Output: Energy Delivery Capability & Constraints Profile.

Module 3 — ECAM: Energy Consumption Assessment Module

Operational Role: Evaluates actual energy consumption, consumer operating states, end-use demand, consumption

boundaries, internal energy transfers, and the distinction between received energy, consumed energy, and useful

output.

Principal Output: Energy Consumption & Demand Profile.

Module 4 — DMAM: Delivery Measurement & Attribution Module

Operational Role: Evaluates delivery and consumption measurements, physical attribution, measurement

boundaries, interval consistency, energy accounting reconciliation, evidence integrity, and uncertainty.

Principal Output: Energy Delivery Measurement & Attribution Profile.

Module 5 — DCCM: Delivery & Consumption Continuity Module

Operational Role: Preserves delivery interface changes, consumer configuration changes, demand and consumption

assessment revisions, measurement corrections, evidence availability, and historical governance integrity.

Principal Output: Energy Delivery & Consumption Continuity Profile.

72. Module Separation

EDIM identifies where energy is physically delivered, which system receives it, and which consuming assets

and boundaries are involved.

DCAM evaluates whether energy can physically be delivered through the identified interface under defined

conditions.

ECAM evaluates what energy is actually consumed, by which system, and under which operating conditions.

DMAM establishes how delivery and consumption quantities are measured, reconciled, and attributed.

DCCM preserves how delivery systems, consumption systems, measurements, and assessments change

across time.

The modules must remain methodologically distinct while preserving shared physical identities and assessment

references.

73. Module Dependency Flow

EDIM → DCAM → ECAM → DMAM → DCCM

Delivery Identity → Delivery Capability → Consumption Assessment → Measurement & Attribution → Change

& Continuity

The dependency flow establishes the primary methodological sequence.

Feedback and reassessment between modules are permitted where justified.

74. Governance Outputs

The principal output is:

Energy Delivery & Consumption Governance Profile

Supporting outputs may include:

Energy Delivery Identity & Boundary Profile

Energy Delivery Capability & Constraints Profile

Energy Consumption & Demand Profile

Energy Delivery Measurement & Attribution Profile

Energy Delivery & Consumption Continuity Profile

Delivery Interface Register

Receiving System Register

Consuming Asset Register

Energy Carrier Compatibility Record

Delivery Capability Assessment

Delivered Energy Assessment

Received Energy Assessment

Consumption Assessment

Demand Assessment

Unserved Demand Record

Consumption Attribution Record

Measurement Evidence Register

Delivery-Consumption Reconciliation Record

Evidence Conflict Record

Uncertainty Assessment

Governance Determination Record

Outputs must preserve physical boundaries, applicable time references, evidence, confidence, and relevant

governance conclusions.

75. Verification Framework

EDCS supports verification through explicit governance tests.

Delivery Identity Test: Is the physical delivery interface identifiable?

Receiving System Test: Is the receiving system identifiable?

Consumption Boundary Test: Is the consuming system boundary explicit?

Energy Carrier Test: Is the energy carrier correctly identified?

Delivery Capability Test: Is the specified transfer physically feasible?

Delivered Energy Test: Is actual delivery supported by evidence?

Consumption Test: Is actual consumption supported by evidence?

Demand Test: Are demand and consumption distinguished?

Attribution Test: Is consumption physically attributable?

Measurement Test: Are relevant measurements valid and appropriately bounded?

Reconciliation Test: Are material energy differences explained or preserved?

Temporal Integrity Test: Are historical conditions and evidence availability correctly represented?

Determination Test: Does the governance conclusion remain within the supported scope?

76. Non-Conformity Classification

EDCS recognizes:

Delivery Interface Identity Non-Conformity

Receiving System Identity Non-Conformity

Consumption Boundary Non-Conformity

Energy Carrier Compatibility Non-Conformity

Delivery Capability Non-Conformity

Scheduled Energy Misrepresentation

Delivered Energy Measurement Non-Conformity

Received Energy Assessment Non-Conformity

Consumption Assessment Non-Conformity

Demand Classification Non-Conformity

Unserved Demand Assessment Non-Conformity

Consumer Operating State Non-Conformity

Consumption Attribution Non-Conformity

Measurement Boundary Non-Conformity

Measurement Interval Non-Conformity

Energy Reconciliation Non-Conformity

Evidence Sufficiency Non-Conformity

Uncertainty Non-Conformity

Historical Assessment Integrity Non-Conformity

A methodological non-conformity does not automatically establish contractual breach, legal liability, equipment defect,

or regulatory violation.

77. GIE™ Compatibility

EDCS is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

Potential machine-readable objects include:

Delivery Interface

Receiving System

Consuming Asset

Energy Carrier

Delivery Boundary

Consumption Boundary

Delivery Capability

Delivered Energy Quantity

Consumed Energy Quantity

Demand Reference

Measurement Point

Evidence Reference

Physical Valid Time

Evidence Availability Time

Confidence Classification

Governance Determination

A compatible implementation may support automated checks for:

Missing Delivery Identities

Undefined Consumption Boundaries

Unsupported Delivered Energy Claims

Energy Carrier Incompatibility

Demand-Consumption Confusion

Consumption Attribution Conflicts

Measurement Interval Misalignment

Unexplained Energy Accounting Residuals

Historical Evidence Leakage

GIE-Compatible: Yes establishes architectural and methodological compatibility.

It does not establish completed production integration or external certification.

78. Interoperability

EDCS supports interoperability with:

Physical Energy Infrastructure Registers

Energy Management Systems

Metering Systems

Industrial Monitoring Systems

Building Energy Management Systems

District Energy Systems

Storage Management Systems

Energy Governance Assessment Systems

Interoperability requires stable identities, explicit physical boundaries, consistent energy units, temporal references,

and traceable evidence.

No specific proprietary platform is mandatory.

79. Governance Independence

EDCS establishes methodological governance requirements.

It does not act as:

An Energy Regulator

A Grid Operator

An Energy Supplier

A Metering Certification Authority

A Contractual Settlement Authority

A Statutory Compliance Authority

Applicable laws, technical regulations, contractual arrangements, and competent institutional authorities retain their

respective responsibilities.

OOF® defines the methodological reference structure.

80. Assessment Limitations

EDCS conclusions must remain within their supported scope.

A validated delivery measurement does not independently establish:

Energy Source Origin

Generation Efficiency

Network Reliability

Environmental Performance

Commercial Settlement Accuracy

Useful End-Use Efficiency

Those conclusions require the relevant additional evidence and governance assessments.

81. Evidence-Based Governance

EDCS requires conclusions to distinguish:

Declared Information

Observed Physical Conditions

Measured Quantities

Calculated Quantities

Estimated Quantities

Validated Conclusions

Evidence must not be represented as stronger than its actual support.

Uncertainty, missing information, and unresolved conflicts must remain visible.

82. Architectural Integrity

EDCS completes the primary physical energy lifecycle within EGA™.

It establishes the methodological boundary between energy arriving at a receiving system and energy actually used

by consuming systems.

This distinction enables subsequent EGA™ standards to evaluate system balancing, measurement reconciliation, flow

attribution, efficiency, reliability, environmental impact, and claims without conflating physical delivery with final

consumption.

83. Canonical Boundary

Energy Delivery & Consumption Standard (EDCS) governs the identification, characterization, assessment,

validation, and continuity of physical energy delivery and final energy consumption.

It establishes methodological requirements for delivery interfaces, receiving systems, consumption boundaries,

energy carriers, delivery capability, delivered energy, actual consumption, demand, operating conditions,

measurement, attribution, evidence, and historical integrity.

It does not independently govern energy source origin, generation, conversion, external transmission and distribution,

or storage performance.

Those responsibilities remain assigned to the corresponding EGA™ Parent Standards.

Its principal governance output is:

Energy Delivery & Consumption Governance Profile

84. Canonical Closing Statement

Energy is not consumed merely because it has been generated, scheduled, transported, or made available.

Physical delivery must occur.

The receiving system must be identifiable.

The energy carrier must be compatible.

The consumption boundary must be defined.

And the quantity actually used must be distinguished from the quantity expected, contracted, available, or delivered.

EDCS establishes the methodological foundation for these distinctions.

It connects physical energy delivery with receiving systems, end-use equipment, operating conditions, consumption

measurements, demand references, and evidence-based attribution.

It prevents scheduled energy from becoming unsupported delivery claims.

It prevents delivered energy from being automatically represented as final consumption.

And it prevents energy consumption from being confused with useful output.

The final stage of energy governance is not simply determining how much energy reached a destination. It is

establishing what was physically delivered, what was actually consumed, by whom, under which conditions,

and with what evidence.

EDCS establishes that requirement within Energy Governance Architecture (EGA™).

Nahlad

EDCS — Energy Delivery & Consumption Standard

Architecture: EGA™ — Energy Governance Architecture

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Governed Space: Physical Energy Delivery & Final Consumption Governance

Canonical Definition:

EDCS governs how physical energy is delivered to receiving systems and consumed within identifiable operational

boundaries under verifiable conditions.

It ensures that every energy delivery has an identifiable interface, energy carrier, receiving system, physical boundary,

and measurable transfer.

It distinguishes scheduled and available energy from energy actually delivered, received, and consumed.

It requires final energy consumption to remain attributable to identifiable consuming systems, supported by physical

measurements, operating conditions, and traceable evidence.

It governs delivery capability, consumer-side restrictions, energy demand, and measurement integrity so that nominal

capacity or contractual commitments never substitute for verified physical performance.

It establishes continuity and accountability across delivery interfaces, consumption measurements, operational

changes, and historical assessments.

EDCS ensures that energy is not merely supplied or declared as delivered, but physically transferred,

received, consumed, measured, and governed through traceable evidence.

Link: View Standard

About standard

About Energy Delivery & Consumption Standard

(EDCS)

Architecture: EGA™ — Energy Governance Architecture

Parent Standard: Energy Delivery & Consumption Standard (EDCS)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: About Standard

Governed Space: Physical Energy Delivery, Receiving Systems, Delivery Interfaces, Final Energy Consumption,

Consumer-Side Operating Conditions, Energy Demand, Measurement Integrity, Consumption Attribution & Historical

Accountability

Standard ID: EGA-EDCS-06

Origin ID: OOF-EGA-EDCS

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. What Is Energy Delivery & Consumption Standard?

Energy Delivery & Consumption Standard (EDCS) is the sixth Parent Standard within EGA™ — Energy

Governance Architecture.

It establishes the methodological requirements for governing the physical delivery of energy to receiving systems and

the subsequent consumption of that energy within identifiable operational boundaries.

EDCS addresses a fundamental problem in energy governance:

Energy being available, scheduled, or delivered does not necessarily mean that it has been received and

consumed as intended.

A power station may generate electricity without that electricity reaching a particular consumer.

An electrical network may supply a facility without all delivered electricity being consumed by its production

equipment.

A district heating network may deliver thermal energy to a building while internal distribution conditions prevent the

intended heating service.

EDCS establishes how these distinctions must be identified, measured, validated, and preserved.

2. Why EDCS Exists

Energy systems frequently report quantities such as:

Energy supplied.

Energy delivered.

Energy consumed.

Energy demand.

Installed consumer capacity.

Useful energy output.

These quantities describe different physical realities.

Treating them as interchangeable can produce inaccurate energy accounting, unsupported performance claims,

incorrect consumption attribution, and misleading operational conclusions.

EDCS establishes a common governance structure that keeps these quantities separate while connecting them

through evidence.

3. The Fundamental Governance Problem

Consider the following physical sequence:

Available Energy → Delivery Interface → Receiving System → Internal Energy Transfer → Consuming Asset

→ Final Consumption → Useful Output

Each stage introduces a distinct governance question.

Was energy physically available?

Did it cross the intended delivery boundary?

Did the receiving system actually receive it?

Was it transferred to the intended consuming equipment?

How much energy was consumed?

What useful output resulted?

EDCS ensures that evidence supporting one stage is not automatically treated as proof of another.

4. Core Question

How can physical energy delivery and final consumption be identified, measured, attributed, and validated so

that energy availability, actual delivery, received energy, consumed energy, and useful end-use output remain

distinguishable under real operating conditions?

5. Foundational Principle

Energy delivery and consumption must be governed according to energy physically transferred, received,

and used within defined boundaries under actual operating conditions—not merely contracted quantities,

scheduled supply, nominal demand, installed consumer capacity, or assumed useful output.

The governing distinctions are:

Scheduled Energy ≠ Delivered Energy.

Available Supply ≠ Actual Delivery.

Delivered Energy ≠ Consumed Energy.

Received Energy ≠ Useful Energy Output.

Installed Capacity ≠ Actual Consumption.

Energy Demand ≠ Energy Supplied.

Commercial Allocation ≠ Physical Consumption Attribution.

6. What EDCS Governs

EDCS governs the methodological relationship between:

Energy Delivery Interfaces

Receiving Systems

Energy Carriers

Physical Delivery Boundaries

Actual Delivered Energy

Consumption Boundaries

Consuming Assets

Consumer Operating Conditions

Actual Energy Consumption

Energy Demand

Measurement Evidence

Consumption Attribution

Historical Continuity

It establishes how these objects and quantities must be represented to support reliable governance conclusions.

7. Energy Delivery Is a Physical Event

Energy delivery is not established merely because an energy supplier reports that energy was scheduled or allocated.

Physical delivery requires energy to cross an identifiable delivery boundary.

That boundary may be:

An electrical connection point.

A district heating interface.

A fuel transfer point.

A hydrogen delivery interface.

A mechanical energy transfer interface.

EDCS requires the boundary, energy carrier, transfer quantity, and assessment interval to remain identifiable.

8. Energy Receipt Is Not Final Consumption

A receiving system may accept energy without immediately consuming it for its intended end use.

For example, energy may:

Enter internal distribution infrastructure.

Charge an on-site storage system.

Supply auxiliary equipment.

Undergo conversion.

Remain temporarily stored.

EDCS therefore distinguishes energy receipt from final energy consumption.

This distinction is essential for facilities combining generation, storage, conversion, and multiple consuming assets.

9. Energy Consumption Is Not Useful Output

A consuming asset may use energy while producing less useful energy or work than the amount supplied.

An electric motor consumes electrical energy but delivers mechanical output subject to conversion losses.

A heating system consumes energy but may lose part of that energy before it reaches the intended heated space.

EDCS preserves the physical distinction between energy consumption and useful output.

Detailed conversion and efficiency assessment remains governed by the relevant EGA™ standards.

10. Delivery Capability and Physical Constraints

A delivery interface may have a nominal capacity without being able to sustain that capacity under current conditions.

Relevant constraints include:

Interface Capacity

Equipment Availability

Temperature

Pressure

Voltage

Flow Rate

Energy Carrier Compatibility

Supporting Infrastructure

EDCS requires actual delivery capability to remain distinguishable from installed or declared capacity.

11. Demand and Actual Consumption

Energy demand represents a requirement, request, forecast, or observed load associated with a consuming system.

Actual consumption represents energy physically used within a defined boundary.

EDCS distinguishes:

Forecast Demand

Scheduled Demand

Requested Demand

Actual Consumption

Unserved Demand

A demand forecast must not be represented as measured consumption.

Likewise, incomplete delivery does not automatically establish the precise quantity of unserved demand without

appropriate evidence.

12. Physical Consumption Attribution

A facility may contain multiple energy-consuming systems.

A single delivery meter may record total facility energy without identifying how much individual equipment consumed.

EDCS requires consumption attribution to remain connected to identifiable physical boundaries and evidence.

Where direct submetering is unavailable, estimated allocations must remain explicitly classified.

Administrative cost allocation must not be represented as independently verified physical consumption.

13. Measurement Integrity

Reliable delivery and consumption governance requires compatible measurements.

EDCS addresses:

Measurement Point Identity

Physical Measurement Boundaries

Energy Carrier Units

Assessment Intervals

Instrument Evidence

Measured and Estimated Quantities

Measurement Uncertainty

Conflicting Records

Energy measurements taken at different physical boundaries or over different time intervals must not be compared

without appropriate reconciliation.

14. Energy Delivery & Consumption Reconciliation

EDCS supports reconciliation between:

Delivered Energy → Received Energy → Internal Transfers → Stored-Energy Changes → Final Consumption

Where material differences exist, the assessment must consider:

Internal Distribution Losses

Intermediate Storage

Energy Conversion

Auxiliary Consumption

Missing Measurements

Boundary Differences

An unexplained accounting residual must not automatically be classified as a verified physical loss.

15. Technology Independence

EDCS applies across different energy carriers and consuming systems.

Its governance structure can support:

Electricity Distribution to Buildings

Industrial Electrical Consumption

District Heating Delivery

Industrial Steam Consumption

Hydrogen Delivery and Use

Fuel Delivery to Industrial Equipment

Mechanical Energy Transfer

The common methodological logic remains consistent.

Technology-specific measurement and engineering models must still be applied.

16. Five Core Modules

EDCS is implemented through five distinct Core Modules.

EDIM — Energy Delivery Identification Module

Establishes physical delivery identities, receiving systems, consuming assets, energy carriers, and delivery and

consumption boundaries.

Principal Output: Energy Delivery Identity & Boundary Profile.

DCAM — Delivery Capability Assessment Module

Evaluates delivery capability, physical interface restrictions, energy carrier compatibility, and the feasibility of specified

energy transfers.

Principal Output: Energy Delivery Capability & Constraints Profile.

ECAM — Energy Consumption Assessment Module

Evaluates actual consumption, end-use demand, consumer operating states, internal energy transfers, and the

distinction between consumption and useful output.

Principal Output: Energy Consumption & Demand Profile.

DMAM — Delivery Measurement & Attribution Module

Evaluates delivery and consumption measurements, physical attribution, reconciliation, evidence integrity, and

uncertainty.

Principal Output: Energy Delivery Measurement & Attribution Profile.

DCCM — Delivery & Consumption Continuity Module

Preserves delivery interface changes, consuming asset changes, measurement revisions, evidence availability, and

historical assessment integrity.

Principal Output: Energy Delivery & Consumption Continuity Profile.

17. Module Governance Flow

EDIM → DCAM → ECAM → DMAM → DCCM

Delivery Identity → Delivery Capability → Consumption Assessment → Measurement & Attribution → Change

& Continuity

Each module addresses a distinct governance responsibility.

Together, they establish an evidence-supported representation of energy delivery and final consumption.

18. Practical Use Case 1 — Industrial Facility Confuses Delivered

Electricity With Production Consumption

Situation

An industrial facility receives 1,000 MWh of electricity during a reporting period.

The facility reports that its production equipment consumed the full 1,000 MWh.

However, the electricity also supplied:

Building ventilation.

Lighting.

Cooling equipment.

Office infrastructure.

An on-site battery storage system.

The facility has only one main delivery meter.

EDCS Assessment

EDCS distinguishes:

Electricity Delivered to the Facility from Electricity Consumed by Production Equipment.

The main delivery meter supports the total energy delivered at the facility boundary.

It does not independently establish the quantity consumed by production equipment.

Production consumption requires appropriate submetering, process measurements, or explicitly identified estimation

methods.

Governance Determination

FAIL — Total Facility Delivery Incorrectly Attributed to Production Equipment Without Sufficient Evidence.

Methodological Lesson

A valid delivery measurement does not automatically establish valid attribution of energy consumption to

individual consuming systems.

19. Practical Use Case 2 — District Heating Energy Delivered but

Required Heating Service Not Achieved

Situation

A district heating network supplies thermal energy to a commercial building.

The delivery meter records thermal energy transferred at the building's heat interface.

However, the building's internal circulation system is operating under restricted conditions.

Some occupied areas do not receive the intended heating service.

The operator reports that the heating requirement was fully satisfied because thermal energy was delivered to the

building.

EDCS Assessment

EDCS distinguishes:

Thermal Energy Delivered at the Building Interface from Energy Distributed to End-Use Heating Systems and

Useful Heating Service Achieved.

The delivery measurement supports energy transfer at the defined interface.

It does not independently establish that the internal heating system delivered the required service to every intended

area.

The assessment must preserve internal operating restrictions and available evidence about end-use performance.

Governance Determination

CONDITIONAL — Physical Energy Delivery Supported; Full End-Use Heating Performance Not Established.

Methodological Lesson

Energy reaching a consumer boundary does not prove that the intended operational service has been

achieved.

20. Relationship With Energy Governance Architecture

EDCS completes the primary physical energy lifecycle governed by EGA™.

It receives methodological dependencies from:

ESOS — Energy Source & Origin Standard

EGS — Energy Generation Standard

ECS — Energy Conversion Standard

ETDS — Energy Transmission & Distribution Standard

ESS — Energy Storage Standard

It provides delivery and consumption evidence to:

ESBS — Energy System Balancing Standard

EMRS — Energy Measurement & Reconciliation Standard

EFAS — Energy Flow Attribution Standard

EELS — Energy Efficiency & Loss Standard

ESRS — Energy Supply Reliability Standard

EEIS — Energy Environmental Impact Standard

ECDS — Energy Claims & Disclosure Standard

EDCS does not replace these standards.

It establishes the physical delivery and final consumption layer on which their assessments may depend.

21. Governance Outputs and GIE™ Compatibility

The principal governance output is:

Energy Delivery & Consumption Governance Profile

Supporting outputs include:

Energy Delivery Identity & Boundary Profile

Energy Delivery Capability & Constraints Profile

Energy Consumption & Demand Profile

Energy Delivery Measurement & Attribution Profile

Energy Delivery & Consumption Continuity Profile

EDCS is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

A compatible implementation may evaluate:

Delivery Identity

Boundary Consistency

Physical Delivery Capability

Consumption Evidence

Demand-Consumption Distinctions

Measurement Integrity

Consumption Attribution

Historical Assessment Integrity

GIE compatibility does not independently establish completed software integration, regulatory compliance, or external

certification.

22. Canonical Closing Statement

Energy delivery is not the same as energy consumption, and energy consumption is not the same as useful

operational output.

These distinctions determine whether energy systems can be assessed according to their actual physical behavior

rather than assumptions or declarations.

EDCS establishes the methodological structure connecting energy delivery interfaces, receiving systems, consuming

assets, demand, operating conditions, measurements, and evidence.

It prevents scheduled energy from being confused with delivered energy.

It prevents facility-level energy delivery from being automatically attributed to individual consuming assets.

And it prevents energy received by a system from being treated as proof that the intended end-use service was

achieved.

Energy governance reaches the final consumer only when physical delivery, actual consumption, and their

supporting evidence remain independently identifiable and traceable.

EDCS establishes that requirement within Energy Governance Architecture (EGA™).

EDIM — Energy Delivery Identification Module

Architecture: EGA™ — Energy Governance Architecture

Parent Standard: Energy Delivery & Consumption Standard (EDCS)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: Core Module

Governed Space: Physical Energy Delivery Identity, Delivery Interfaces, Receiving Systems, Consuming Assets,

Energy Carriers, Delivery & Consumption Boundaries, Physical Connection Topology, Measurement Point Identity &

Delivery-Consumption Traceability

Module ID: EGA-EDCS-EDIM-01

Origin ID: OOF-EGA-EDCS-EDIM

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. Canonical Definition

EDIM — Energy Delivery Identification Module is the first Core Module within Energy Delivery & Consumption

Standard (EDCS), operating under Energy Governance Architecture (EGA™).

EDIM establishes the methodological governance requirements for identifying, classifying, validating, and maintaining

evidence-supported representations of physical energy delivery interfaces, receiving systems, consuming assets,

energy carriers, delivery boundaries, consumption boundaries, and their physical relationships.

It establishes the identity and boundary foundation required to determine where energy enters a receiving system,

which physical systems are connected, which assets may consume the energy, and how relevant delivery and

consumption objects can be distinguished.

EDIM recognizes that a delivery point, a receiving facility, an internal distribution system, a consuming asset, and a

measurement point are not necessarily the same physical object.

A facility may have several delivery interfaces.

One delivery interface may serve multiple consuming assets.

A consuming asset may receive energy through more than one path.

A meter may measure energy at a boundary that differs from the boundary used for consumption attribution.

A receiving system may also contain on-site generation, conversion equipment, or energy storage.

These relationships must remain explicit.

EDIM therefore establishes a physically grounded identity model that prevents energy delivery interfaces, receiving

systems, consuming assets, and measurement points from being incorrectly treated as interchangeable.

It requires identifiable physical connections, appropriate energy carrier classification, directional relationships, and

traceable evidence supporting the declared system structure.

EDIM does not independently determine delivery capability, calculate actual consumption, reconcile measured

quantities, or govern historical changes.

Those responsibilities remain assigned to DCAM, ECAM, DMAM, and DCCM.

Its principal governance output is the Energy Delivery Identity & Boundary Profile.

2. Operational Role

EDIM establishes the physical identity and boundary governance layer of EDCS.

It governs:

Energy delivery interface identity.

Receiving system identity.

Consuming asset identity.

Delivery boundary identification.

Consumption boundary identification.

Energy carrier classification.

Physical connection topology.

Energy transfer direction.

Internal distribution relationships.

Multiple delivery interfaces.

Shared delivery infrastructure.

Multiple consuming assets.

On-site generation interface references.

Behind-the-meter storage references.

Energy conversion interface references.

Measurement point identity.

Measurement boundary identity.

Asset-to-interface relationships.

Physical evidence.

Identity confidence.

Boundary conflicts.

Machine-readable delivery topology.

Cross-module identity consistency.

EDIM establishes what physical objects participate in energy delivery and consumption and how those objects are

connected.

3. Operational Question

How can energy delivery interfaces, receiving systems, consuming assets, energy carriers, physical

connections, and delivery and consumption boundaries be identified and validated so that energy transfers

can be traced to the correct physical objects without confusing delivery points, meters, facilities, and end-

use equipment?

4. Position in Architecture Governance Flow

Energy Governance Architecture (EGA™)

Energy Source & Origin → Energy Generation → Energy Conversion → Energy Transmission & Distribution ↔

Energy Storage → Energy Delivery & Consumption

Energy Delivery & Consumption Standard (EDCS)

EDIM — Energy Delivery Identification Module

↓

DCAM — Delivery Capability Assessment Module

↓

ECAM — Energy Consumption Assessment Module

↓

DMAM — Delivery Measurement & Attribution Module

↓

DCCM — Delivery & Consumption Continuity Module

EDIM provides the physical identity and topology references required by the subsequent EDCS modules.

5. Governed Space

Physical Energy Delivery Identity, Delivery Interfaces, Receiving Systems, Consuming Assets, Energy

Carriers, Delivery & Consumption Boundaries, Physical Connection Topology, Measurement Point Identity &

Delivery-Consumption Traceability

The governed space begins with an identifiable physical energy delivery interface or receiving system.

It includes relevant energy carriers, receiving assets, consuming equipment, physical connections, internal distribution

relationships, and measurement references.

It concludes with an evidence-supported identity and boundary representation suitable for downstream delivery and

consumption governance.

6. Governed Object

The primary Governed Object is:

An identifiable physical energy delivery interface, receiving system, consuming asset, consumption

boundary, or related connection object associated with a defined energy carrier, physical location, directional

transfer relationship, measurement reference, evidence basis, and governance determination.

Relevant fields include:

Delivery Interface ID

Receiving System ID

Consuming Asset ID

Delivery Boundary ID

Consumption Boundary ID

Energy Carrier ID

Physical Connection ID

Connection Direction

Measurement Point ID

Configuration Reference

Evidence Reference

Physical Valid Time

Evidence Availability Time

Confidence Classification

Governance Determination

7. Scope

EDIM applies to physical delivery and consumption identity governance for:

Electricity Delivery Systems

District Heating Systems

Industrial Steam Systems

Natural Gas Delivery Systems

Hydrogen Delivery Systems

Liquid Fuel Delivery Systems

Mechanical Energy Transfer Systems

Industrial Energy Networks

Building Energy Systems

Hybrid Energy Systems

The identity model is technology-independent.

Physical interface characteristics remain energy-carrier-specific.

8. Foundational Principle

Energy delivery and consumption governance must begin with verifiable physical identities and boundaries—

not assumptions that a facility, meter, delivery point, receiving system, and consuming asset represent the

same object.

Delivery Interface ≠ Receiving System.

Receiving System ≠ Consuming Asset.

Measurement Point ≠ Automatically Delivery Boundary.

Delivery Boundary ≠ Consumption Boundary.

Physical Connection ≠ Verified Energy Transfer.

Installed Asset ≠ Active Consumer.

Administrative Allocation ≠ Physical Connection Evidence.

Declared Topology ≠ Validated Physical Topology.

9. Delivery Identity Reference Model

EDIM establishes the following governance sequence:

Energy Carrier → Delivery Interface → Delivery Boundary → Receiving System → Internal Distribution →

Consuming Asset → Consumption Boundary → Measurement Reference → Evidence → Governance

Determination

The sequence represents a reference model.

Actual systems may contain multiple paths, shared infrastructure, storage, conversion, or bidirectional transfers.

10. Energy Delivery Interface Identity

An energy delivery interface is the identifiable physical connection through which energy may enter a receiving

system.

EDIM must preserve:

Delivery Interface ID

Physical Location

Energy Carrier

Connected Receiving System

Connection Direction

Relevant Equipment

Evidence

An interface identity must not be inferred solely from a commercial account identifier.

11. Delivery Interface Classification

Relevant interface classes include:

Electrical Connection Interface

Thermal Delivery Interface

Steam Delivery Interface

Gas Delivery Interface

Hydrogen Delivery Interface

Liquid Fuel Transfer Interface

Mechanical Energy Transfer Interface

Classification must reflect the actual physical transfer mechanism.

12. Receiving System Identity

A receiving system is the identifiable physical system that accepts energy through a delivery interface.

EDIM must preserve:

Receiving System ID

System Boundary

Connected Delivery Interfaces

Energy Carrier Compatibility

Physical Evidence

The receiving system may contain multiple internal energy-consuming assets.

13. Consuming Asset Identity

A consuming asset is identifiable equipment or a physical subsystem capable of using energy for an end-use process.

Examples include:

Industrial Motors

Heating Equipment

Production Machinery

Compressors

Cooling Systems

Electrical Appliances

Industrial Furnaces

EDIM establishes identity and physical relationships.

It does not establish actual consumption merely because an asset is installed.

14. Delivery Boundary Identification

A delivery boundary establishes where energy crosses into the receiving system for the relevant assessment.

EDIM must preserve:

Boundary ID

Physical Location

Associated Interface

Energy Carrier

Applicable Direction

Evidence

The boundary must correspond to a physically meaningful transfer location.

15. Consumption Boundary Identification

A consumption boundary establishes the physical extent of the consuming system being assessed.

Examples include:

Building Consumption Boundary

Industrial Process Boundary

Production Line Boundary

Equipment Boundary

End-Use Subsystem Boundary

Different consumption boundaries may produce different energy accounting results.

16. Boundary Hierarchy

EDIM recognizes nested physical boundaries.

A facility boundary may contain:

Internal Distribution Boundary

Production Area Boundary

Equipment Boundary

Process Boundary

Nested boundaries must remain identifiable.

The same energy transfer must not be counted repeatedly as independent energy consumption merely because it

crosses multiple nested boundaries.

17. Boundary Overlap

Two assessed boundaries may overlap physically.

EDIM must identify whether the relationship is:

Nested

Partially Overlapping

Separate

Shared

Overlapping boundaries must not be assumed to represent independent energy quantities.

18. Energy Carrier Identity

Each delivery interface and consuming asset must reference the relevant energy carrier.

Examples include:

Electricity

Hot Water

Steam

Natural Gas

Hydrogen

Liquid Fuels

Mechanical Energy

The carrier must be identified sufficiently to support subsequent physical assessment.

19. Energy Carrier Characteristics

EDIM may preserve identity-relevant carrier characteristics.

Examples include:

Electrical Phase and Frequency Classification

Thermal Medium Type

Steam Classification

Gas Composition Reference

Hydrogen Delivery Form

Fuel Type

Detailed operating compatibility is evaluated by DCAM.

20. Physical Connection Identity

A physical connection links identifiable energy system objects.

EDIM must preserve:

Connection ID

Origin Object

Destination Object

Energy Carrier

Physical Directionality

Evidence

Connection identity does not independently establish actual energy flow.

21. Connection Directionality

Connections may support:

Unidirectional Transfer

Bidirectional Transfer

Conditional Directionality

EDIM must distinguish physical capability from actual operating direction.

A bidirectional connection does not establish that energy flows in both directions during every assessment interval.

22. Internal Distribution Identity

Receiving systems may contain internal energy distribution infrastructure.

Examples include:

Electrical Distribution Boards

Industrial Busbars

Heating Circuits

Steam Distribution Pipes

Fuel Distribution Lines

EDIM must preserve material internal distribution relationships where necessary to identify consuming assets.

23. Multiple Delivery Interfaces

A receiving system may connect to several delivery interfaces.

EDIM must identify each interface independently.

Examples include:

Two Electrical Grid Connections

District Heating and On-Site Boiler Interfaces

Multiple Fuel Supply Connections

Multiple interfaces must not be collapsed into a single physical connection without justification.

24. Multiple Receiving Systems

One physical delivery infrastructure arrangement may serve several receiving systems.

EDIM must preserve the relationship between shared infrastructure and distinct receiving systems.

Administrative customer grouping must not substitute for physical system identification.

25. Multiple Consuming Assets

One receiving system may supply many consuming assets.

EDIM must preserve:

Receiving System Reference

Internal Distribution Relationships

Consuming Asset IDs

Consumption Boundary References

The existence of a shared supply does not establish individual consumption quantities.

26. Shared Delivery Infrastructure

Shared infrastructure may include:

Common Transformers

Shared Electrical Feeders

Common Thermal Headers

Shared Gas Distribution Lines

Shared Mechanical Drives

EDIM must identify shared infrastructure where it materially affects physical delivery relationships.

27. On-Site Generation References

A receiving system may contain local generation assets.

EDIM must preserve the physical relationship between:

External Delivery Interface

On-Site Generation Interface

Internal Distribution

Consuming Assets

Generation asset performance remains governed by EGS.

28. Behind-the-Meter Storage References

A receiving system may include energy storage.

EDIM must identify relevant:

Storage Asset References

Charging Connections

Discharging Connections

Internal Distribution Interfaces

Storage capacity and operating behavior remain governed by ESS.

29. Energy Conversion Interface References

A receiving system may contain energy conversion equipment.

Examples include:

Electric Boilers

Heat Pumps

Industrial Furnaces

Electric Motors

Fuel Cells

EDIM identifies relevant physical connections.

Conversion performance remains governed by ECS.

30. Bidirectional Energy Systems

Some receiving systems may both import and export energy.

Examples include:

Facilities With Solar Generation

Battery-Connected Buildings

Vehicle-to-Grid Installations

Industrial Energy Recovery Systems

EDIM must preserve import and export interface relationships.

An importing system must not automatically be classified as exclusively consuming energy.

31. Hybrid Energy Systems

Hybrid systems may use multiple energy carriers.

Examples include:

Electricity and Natural Gas

Electricity and District Heating

Hydrogen and Electricity

Steam and Electrical Energy

EDIM must preserve carrier-specific interfaces and physical relationships.

Different energy carriers must not be merged into an undefined energy transfer.

32. Measurement Point Identity

A measurement point is an identifiable location or logical reference associated with a physical energy measurement.

EDIM must preserve:

Measurement Point ID

Physical Location

Measured Energy Carrier

Associated Interface or Asset

Measurement Boundary

Measurement validity is assessed by DMAM.

33. Meter Identity Versus Measurement Point

A physical meter may be replaced while the measurement point remains unchanged.

Conversely, a single meter may support multiple measurement channels.

EDIM must distinguish:

Meter Device ID

Measurement Point ID

Measurement Channel ID

These identities must not be treated as automatically equivalent.

34. Measurement Boundary Identity

The measurement boundary identifies the physical transfer represented by a measurement.

EDIM must preserve whether the measurement represents:

External Delivery

Internal Distribution

Asset-Level Input

Process-Level Consumption

Exported Energy

A meter reading cannot be reliably attributed without an appropriate boundary reference.

35. Physical Topology

EDIM establishes a traceable representation of physical energy connections.

A topology may include:

Delivery Interfaces

Receiving Systems

Internal Distribution Assets

Storage Assets

Conversion Assets

Consuming Equipment

Measurement Points

The topology must represent actual or explicitly proposed physical relationships.

36. Topology Directionality

Topology must preserve applicable transfer direction.

A physical connection may permit one or more energy transfer directions.

EDIM must not infer actual energy flow solely from the existence of a connection.

37. Topology Completeness

EDIM evaluates whether material physical relationships are represented.

Relevant questions include:

Are All Material Delivery Interfaces Identified?

Are Receiving Systems Connected to the Correct Interfaces?

Are Material Consuming Assets Identified?

Are Shared Connections Represented?

Are Measurement Points Mapped?

Incomplete topology must remain explicit.

38. Topology Evidence

Relevant evidence may include:

Engineering Drawings

Single-Line Diagrams

Piping Diagrams

Equipment Registers

Installation Records

Physical Inspection Records

Commissioning Documentation

Evidence must correspond to the applicable physical configuration.

39. Declared Versus Verified Topology

EDIM distinguishes:

Declared Topology

Documented Topology

Physically Verified Topology

Estimated Topology

A drawing does not automatically establish that the current installation matches the drawing.

Verification confidence must remain explicit.

40. Asset Naming Consistency

Assets may possess multiple identifiers.

Examples include:

Manufacturer Serial Number

Facility Asset Number

Engineering Tag

Metering Identifier

Internal Database ID

EDIM must preserve traceable relationships between identifiers where they refer to the same physical object.

41. Identity Collision

An identity collision occurs when the same identifier is assigned to different physical objects within a namespace that

requires uniqueness.

EDIM must detect and preserve material identity conflicts.

An unresolved collision must not be silently resolved by selecting one object without evidence.

42. Duplicate Object Representation

The same physical object may appear multiple times across data sources.

EDIM must distinguish:

One Physical Object With Multiple Records from Multiple Distinct Physical Objects.

Incorrect duplication may produce false topology or consumption attribution.

43. Unknown Physical Objects

An energy system may contain unidentified connections or consuming assets.

EDIM must preserve:

Unknown Object Reference

Observed Relationship

Evidence

Uncertainty

Unknown objects must not be replaced by invented identities.

44. Physical Boundary Conflict

Boundary conflicts may arise when:

Different Documents Define Different Delivery Points

Meters Are Located Outside the Declared Boundary

Facility Boundaries Overlap

Consumption Assets Are Assigned to Incorrect Systems

EDIM must preserve material conflicts until reconciled.

45. Connection Conflict

Connection conflicts may arise from:

Contradictory Engineering Drawings

Unrecorded Equipment Modifications

Inconsistent Asset Registers

Physical Inspection Findings

Conflicting connections must not be treated as confirmed.

46. Energy Carrier Conflict

A carrier conflict occurs when records assign incompatible energy carrier classifications to the same interface or

asset.

EDIM must preserve the conflicting classifications and supporting evidence.

Carrier compatibility cannot be assumed while the underlying identity remains unresolved.

47. Evidence Sufficiency

EDIM evaluates whether available evidence supports the intended identity and boundary conclusion.

Relevant questions include:

Is the Interface Physically Identifiable?

Is the Receiving System Identifiable?

Is the Consuming Asset Identifiable?

Is the Energy Carrier Known?

Is the Physical Connection Supported?

Is the Measurement Boundary Defined?

Is the Topology Consistent?

Insufficient evidence must remain explicit.

48. Evidence Reconciliation

Reconciliation may involve:

Engineering Documentation Review

Asset Register Comparison

Metering Configuration Review

Physical Inspection

Commissioning Evidence

Connection Verification

Reconciliation must preserve original evidence and the justification for the supported conclusion.

49. Identity Uncertainty

EDIM requires explicit treatment of uncertainty affecting:

Physical Object Identity

Boundary Location

Connection Relationships

Energy Carrier Classification

Measurement Point Mapping

Topology Completeness

Unknown uncertainty must not be represented as zero.

50. Identity Confidence

EDIM applies the EGA™ confidence framework.

Confirmed — Sufficient applicable evidence supports the identity or topology conclusion.

Reconciled — The conclusion is supported through justified evidence reconciliation.

Estimated — The conclusion relies on explicit inference or estimation.

Conflicted — Material evidence supports incompatible conclusions.

Unknown — Available evidence is insufficient.

Confidence must apply to the specific object, boundary, or physical relationship.

51. Governance Determination

EDIM supports:

PASS — Applicable identity and boundary requirements are satisfied.

CONDITIONAL — The conclusion is supported subject to explicit limitations.

FAIL — One or more mandatory requirements are not satisfied.

INDETERMINATE — Evidence is insufficient or materially conflicting.

NOT APPLICABLE — The assessed requirement does not apply.

A PASS does not independently establish delivery capability, actual energy flow, consumption quantity, or regulatory

compliance.

52. Identity Governance Requirements

A conforming EDIM implementation must satisfy the following requirements.

Delivery & Receiving Identity

1. Establish identifiable physical delivery interfaces.

2. Preserve delivery interface identifiers.

3. Identify relevant receiving systems.

4. Preserve receiving system identifiers.

5. Identify material consuming assets.

6. Preserve consuming asset identifiers.

7. Identify relevant energy carriers.

8. Classify physical delivery interface types.

9. Preserve material physical location references.

10. Distinguish administrative identifiers from physical object identities.

Physical Boundaries

11. Define delivery boundaries.

12. Define consumption boundaries.

13. Preserve boundary identifiers.

14. Identify nested boundaries.

15. Identify overlapping boundaries.

16. Distinguish delivery boundaries from measurement points.

17. Distinguish receiving systems from consuming assets.

18. Preserve material boundary evidence.

19. Identify unresolved boundary conflicts.

20. Prevent unsupported boundary equivalence.

Physical Connections & Topology

21. Identify material physical connections.

22. Preserve connection identifiers.

23. Identify connection directionality.

24. Distinguish connection capability from actual flow.

25. Identify material internal distribution relationships.

26. Preserve multiple delivery interfaces.

27. Preserve shared delivery infrastructure.

28. Identify relevant on-site generation interfaces.

29. Identify relevant storage and conversion interfaces.

30. Maintain a traceable physical topology.

Measurement Identity & Evidence

31. Identify relevant measurement points.

32. Distinguish meter devices from measurement points.

33. Preserve measurement boundary references.

34. Identify material topology evidence.

35. Distinguish declared from verified topology.

36. Evaluate identity evidence sufficiency.

37. Identify material identity collisions.

38. Identify duplicate physical object representations.

39. Preserve unresolved connection conflicts.

40. Evaluate identity and topology uncertainty.

Governance & Interoperability

41. Apply appropriate confidence classifications.

42. Produce evidence-supported identity determinations.

43. Preserve stable cross-module object references.

44. Support DCAM delivery capability assessments.

45. Support ECAM consumption assessments.

46. Support DMAM measurement attribution.

47. Support DCCM identity continuity.

48. Preserve applicable temporal references.

49. Maintain machine-readable identity and topology records.

50. Produce an Energy Delivery Identity & Boundary Profile.

53. Governance Logic

Energy Carrier → Delivery Interface → Delivery Boundary → Receiving System → Physical Connection →

Internal Distribution → Consuming Asset → Consumption Boundary → Measurement Point → Evidence →

Governance Determination

For identity:

Physical Object → Identity Reference → Classification → Evidence → Confidence

For boundaries:

Delivery Interface → Physical Boundary → Receiving System → Consumption Boundary

For topology:

Objects → Connections → Directionality → Boundary Relationships → Validation

The governance logic must preserve the distinction between physical identity, connection, measurement, and actual

energy transfer.

54. Governance Outputs

The principal output is:

Energy Delivery Identity & Boundary Profile

Supporting outputs may include:

Delivery Interface Identity Record

Receiving System Identity Record

Consuming Asset Identity Record

Delivery Boundary Register

Consumption Boundary Register

Energy Carrier Identity Record

Physical Connection Register

Connection Directionality Record

Internal Distribution Identity Record

Shared Infrastructure Register

On-Site Generation Interface Record

Storage Interface Reference

Conversion Interface Reference

Measurement Point Identity Register

Meter Device Identity Register

Measurement Boundary Register

Physical Energy Topology Profile

Topology Evidence Register

Declared Topology Record

Verified Topology Record

Identity Collision Record

Duplicate Object Assessment

Boundary Conflict Record

Connection Conflict Record

Energy Carrier Conflict Record

Evidence Sufficiency Assessment

Identity Uncertainty Assessment

Identity Confidence Record

Delivery Identity Governance Determination

Outputs must preserve relevant physical identities, boundary references, connection relationships, evidence,

uncertainty, and governance determinations.

55. Minimum Implementation Framework

A minimum EDIM implementation establishes eight governance layers.

Layer 1 — Delivery Identity

Identify physical delivery interfaces and associated energy carriers.

Layer 2 — Receiving System Identity

Identify receiving systems and their relationships to delivery interfaces.

Layer 3 — Consuming Asset Identity

Identify material consuming assets and their physical relationships to receiving systems.

Layer 4 — Physical Boundaries

Establish delivery, receiving, measurement, and consumption boundaries.

Layer 5 — Connection Topology

Represent material physical connections, internal distribution, directionality, and shared infrastructure.

Layer 6 — Evidence & Uncertainty

Evaluate identity evidence, topology evidence, conflicts, uncertainty, and confidence.

Layer 7 — Governance Determination

Produce evidence-supported identity and boundary conclusions.

Layer 8 — Interoperability & Continuity

Maintain stable object references for DCAM, ECAM, DMAM, and DCCM.

No specific proprietary technology is mandatory.

56. Cross-Module Boundary

DCAM — Delivery Capability Assessment Module

Evaluates physical delivery capability and operating constraints.

EDIM provides delivery interface identities, receiving system references, and physical connection topology.

ECAM — Energy Consumption Assessment Module

Evaluates consumption, demand, and consumer operating conditions.

EDIM provides consuming asset identities and consumption boundaries.

DMAM — Delivery Measurement & Attribution Module

Evaluates measured energy quantities, physical attribution, and reconciliation.

EDIM provides measurement point identities and physical boundary relationships.

DCCM — Delivery & Consumption Continuity Module

Preserves configuration changes, identity revisions, and historical assessment integrity.

EDIM establishes the identities and boundaries whose continuity DCCM governs.

57. Cross-Architecture Boundary

Energy Generation Standard (EGS)

EDIM identifies on-site generation interface relationships without governing generation performance.

Energy Conversion Standard (ECS)

EDIM identifies conversion equipment interfaces without governing conversion efficiency.

Energy Transmission & Distribution Standard (ETDS)

EDIM establishes receiving-side delivery identities while ETDS governs external transport infrastructure.

Energy Storage Standard (ESS)

EDIM identifies storage connections within receiving systems while ESS governs storage identity, capacity, operating

behavior, and retention.

Energy Measurement & Reconciliation Standard (EMRS)

EDIM provides physical measurement point identities and boundary references.

Energy Flow Attribution Standard (EFAS)

EDIM provides physical topology and consuming asset identities required for traceable energy attribution.

58. Verification Framework

EDIM supports verification through explicit governance tests.

Interface Identity Test: Is the delivery interface identifiable?

Receiving System Test: Is the receiving system identifiable?

Consuming Asset Test: Are material consuming assets identifiable?

Carrier Test: Is the energy carrier correctly classified?

Delivery Boundary Test: Is the delivery boundary physically explicit?

Consumption Boundary Test: Is the consumption boundary physically explicit?

Connection Test: Are material physical connections supported by evidence?

Directionality Test: Is connection directionality represented correctly?

Topology Test: Is the material physical topology coherent?

Measurement Identity Test: Are measurement points mapped to appropriate boundaries?

Identity Collision Test: Are conflicting identifiers detected?

Evidence Test: Is identity evidence sufficient?

Uncertainty Test: Are material uncertainties preserved?

Determination Test: Does the conclusion remain within the supported scope?

59. Non-Conformity Classification

EDIM recognizes:

Delivery Interface Identity Non-Conformity

Receiving System Identity Non-Conformity

Consuming Asset Identity Non-Conformity

Delivery Boundary Non-Conformity

Consumption Boundary Non-Conformity

Energy Carrier Classification Non-Conformity

Physical Connection Non-Conformity

Connection Directionality Non-Conformity

Shared Infrastructure Non-Conformity

Topology Completeness Non-Conformity

Measurement Point Identity Non-Conformity

Measurement Boundary Non-Conformity

Identity Collision Non-Conformity

Duplicate Object Non-Conformity

Evidence Sufficiency Non-Conformity

Identity Uncertainty Non-Conformity

Non-conformities must identify the affected physical object, applicable requirement, and supporting evidence.

A methodological non-conformity does not automatically establish equipment failure, legal liability, or regulatory

breach.

60. Practical Use Case 1 — Industrial Facility With One Delivery Meter

and Multiple Consuming Systems

Situation

An industrial facility receives electricity through one main electrical connection.

The facility contains:

Production machinery.

Ventilation systems.

Cooling equipment.

Office infrastructure.

A battery storage system.

The main electricity meter measures total energy crossing the facility delivery boundary.

The facility's internal asset register incorrectly identifies the main meter as the production machinery's consumption

meter.

EDIM Assessment

EDIM evaluates:

Main Delivery Interface → Receiving Facility → Internal Distribution → Consuming Assets → Measurement

Point

The assessment identifies:

The main meter belongs to the facility delivery boundary.

The production machinery is only one of several consuming systems.

The battery storage system is an internal storage asset rather than an ordinary final consumer.

The main meter cannot be assigned exclusively to production machinery.

Individual consuming assets require separate physical identity and boundary references.

Governance Determination

FAIL — Facility Delivery Measurement Point Incorrectly Identified as an Individual Consuming Asset

Measurement Point.

The facility must correct the physical object and measurement boundary relationships.

Methodological Lesson

A measurement point can identify energy entering a facility without identifying which internal asset

consumed that energy.

61. Practical Use Case 2 — District Heating Network With Incorrect

Building Boundary Assignment

Situation

A district heating network supplies three commercial buildings through a shared thermal distribution arrangement.

Each building has an identifiable receiving interface.

However, the operator's asset database assigns one thermal meter to the wrong building.

As a result, delivery records are associated with an incorrect receiving system.

EDIM Assessment

EDIM evaluates:

Thermal Delivery Interface → Physical Connection → Receiving Building → Measurement Point → Boundary

Evidence

The assessment identifies:

Three distinct receiving systems.

Separate physical delivery interfaces.

A measurement point incorrectly associated with one building.

A conflict between the database mapping and the physical connection evidence.

The need to correct the measurement-to-building identity relationship.

Governance Determination

FAIL — Measurement Point Identity Incorrectly Associated With the Physical Receiving System.

The operator must reconcile the meter assignment with the verified physical topology.

Methodological Lesson

A correctly functioning energy meter cannot produce reliable consumer attribution when its physical identity

relationship is wrong.

62. Temporal Integrity & Historical Identity

EDIM requires identity and boundary records to preserve relevant temporal references.

Physical Valid Time

The period during which an interface, connection, boundary, or consuming asset relationship physically applied.

Evidence Availability Time

The time at which supporting evidence became available to the assessment process.

Historical as-of assessments must use only evidence available by their defined cutoff.

Later evidence may support a separately identified retrospective assessment.

It must not silently alter the original historical evidence set.

Material changes in identity or topology are governed through DCCM.

63. GIE™ Compatibility

EDIM is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

Potential machine-readable objects include:

Delivery Interface Identity

Receiving System Identity

Consuming Asset Identity

Energy Carrier Identity

Delivery Boundary

Consumption Boundary

Physical Connection

Connection Directionality

Measurement Point Identity

Physical Topology

Evidence Reference

Confidence Classification

Governance Determination

A compatible implementation may support automated checks for:

Missing Delivery Interface Identities

Unidentified Receiving Systems

Duplicate Consuming Assets

Conflicting Boundary Assignments

Unsupported Physical Connections

Measurement Point Mapping Errors

Energy Carrier Conflicts

Topology Inconsistency

Historical Identity Conflicts

GIE-Compatible: Yes establishes architectural and methodological compatibility.

It does not establish completed production integration, validated software behavior, or external certification.

64. Canonical Boundary

EDIM — Energy Delivery Identification Module governs the identification, classification, validation, and

evidence-supported representation of physical energy delivery interfaces, receiving systems, consuming

assets, energy carriers, physical connections, delivery boundaries, consumption boundaries, and

measurement point identities.

It establishes the physical identity and topology foundation required for subsequent energy delivery and consumption

governance.

EDIM does not independently determine actual delivery capability, measure consumed energy, calculate end-use

demand, reconcile energy accounting, or govern historical configuration changes.

Those responsibilities remain assigned to DCAM, ECAM, DMAM, and DCCM.

Its principal governance output is:

Energy Delivery Identity & Boundary Profile

65. Canonical Closing Statement

Energy cannot be reliably attributed to a consumer until the physical delivery interface, receiving system,

consuming asset, and relevant boundaries are correctly identified.

A facility is not a meter.

A meter is not a consuming asset.

A physical connection is not proof of actual energy transfer.

And an administrative identifier is not automatically evidence of physical identity.

EDIM establishes the methodological structure required to preserve these distinctions.

It connects delivery interfaces with receiving systems, consuming assets, energy carriers, physical connections,

measurement points, and evidence-supported boundaries.

It prevents facility-level delivery records from being incorrectly assigned to individual equipment.

It prevents physical topology assumptions from becoming unsupported energy attribution.

And it creates a stable identity foundation for delivery capability, consumption assessment, measurement, and

continuity governance.

Reliable energy delivery governance begins not with the quantity reported, but with knowing exactly where

energy enters, which physical system receives it, and which assets may actually consume it.

EDIM establishes that identity foundation within Energy Delivery & Consumption Standard (EDCS).

DCAM — Delivery Capability Assessment Module

Architecture: EGA™ — Energy Governance Architecture

Parent Standard: Energy Delivery & Consumption Standard (EDCS)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: Core Module

Governed Space: Physical Energy Delivery Capability, Delivery Interface Capacity, Energy Carrier Compatibility,

Available Supply Conditions, Receiving-System Acceptance Capability, Delivery Operating Constraints, Supporting

Infrastructure Dependencies, Time-Dependent Transfer Feasibility, Delivery Restrictions & Evidence-Based Capability

Validation

Module ID: EGA-EDCS-DCAM-02

Origin ID: OOF-EGA-EDCS-DCAM

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. Canonical Definition

DCAM — Delivery Capability Assessment Module is the second Core Module within Energy Delivery &

Consumption Standard (EDCS), operating under Energy Governance Architecture (EGA™).

DCAM establishes the methodological governance requirements for identifying, assessing, validating, and maintaining

evidence-supported conclusions about the physical capability of an energy delivery interface to transfer a specified

energy carrier into an identified receiving system under defined operating conditions.

It evaluates the relationship between available upstream supply, delivery interface limits, energy carrier

characteristics, receiving-system acceptance capability, supporting infrastructure dependencies, and time-dependent

operating constraints.

DCAM recognizes that an installed connection does not automatically establish the ability to deliver energy at its

nominal rating.

A transformer may have a rated capacity while the upstream feeder is restricted.

A district heating connection may have sufficient nominal thermal capacity while available supply temperature or

circulation flow is inadequate.

A hydrogen delivery interface may support a specified flow rate while the receiving system cannot accept that flow

under its current pressure or storage conditions.

An electrical receiving system may have a connection rating that exceeds the capacity available through a shared

upstream bottleneck.

These conditions must remain distinguishable.

DCAM therefore separates nominal delivery capability, technically available capability, receiving-system acceptance

capability, and the capability feasible for a specified delivery request.

It requires the assessment to consider the complete relevant delivery path, rather than a single equipment rating.

DCAM also distinguishes physical feasibility from contractual entitlement, operational authorization, and actual

delivered energy.

A technically feasible transfer is not necessarily authorized.

An authorized transfer is not necessarily physically feasible.

A physically feasible transfer does not establish that the transfer actually occurred.

DCAM does not independently establish delivery interface identities, calculate actual end-use consumption, reconcile

delivered quantities, or govern historical configuration changes.

Those responsibilities remain assigned to EDIM, ECAM, DMAM, and DCCM.

Its principal governance output is the Energy Delivery Capability & Constraints Profile.

2. Operational Role

DCAM establishes the physical delivery capability and feasibility governance layer of EDCS.

It governs:

Delivery capability assessment identity.

Applicable delivery interface identity.

Receiving-system acceptance capability.

Energy carrier compatibility.

Nominal delivery capacity.

Available delivery capability.

Continuous delivery limits.

Short-duration delivery limits.

Upstream supply dependencies.

Delivery path bottlenecks.

Shared infrastructure restrictions.

Equipment operating limits.

Energy carrier operating conditions.

Time-dependent capability.

Ramp and response constraints.

Delivery duration feasibility.

Supporting infrastructure dependencies.

Receiving-system operating states.

Physical delivery restrictions.

Requested transfer feasibility.

Evidence and uncertainty.

Capability conflicts.

Physical feasibility determinations.

Cross-module interoperability.

DCAM determines whether an identified energy delivery arrangement can physically support a specified energy

transfer under the assessed conditions.

3. Operational Question

How can the physical capability of an energy delivery interface be assessed against upstream supply, energy

carrier conditions, equipment limits, receiving-system acceptance capability, shared infrastructure, and time-

dependent constraints so that nominal connection capacity is not confused with operationally feasible

energy delivery?

4. Position in Architecture Governance Flow

Energy Governance Architecture (EGA™)

Energy Source & Origin → Energy Generation → Energy Conversion → Energy Transmission & Distribution ↔

Energy Storage → Energy Delivery & Consumption

Energy Delivery & Consumption Standard (EDCS)

EDIM — Energy Delivery Identification Module

↓

DCAM — Delivery Capability Assessment Module

↓

ECAM — Energy Consumption Assessment Module

↓

DMAM — Delivery Measurement & Attribution Module

↓

DCCM — Delivery & Consumption Continuity Module

EDIM establishes the physical identity and connection references.

DCAM evaluates the feasible transfer capability of those identified arrangements.

ECAM evaluates actual end-use consumption and demand.

DMAM evaluates measurement and attribution.

DCCM preserves changes and historical continuity.

5. Governed Space

Physical Energy Delivery Capability, Delivery Interface Capacity, Energy Carrier Compatibility, Available

Supply Conditions, Receiving-System Acceptance Capability, Delivery Operating Constraints, Supporting

Infrastructure Dependencies, Time-Dependent Transfer Feasibility, Delivery Restrictions & Evidence-Based

Capability Validation

The governed space begins with an identifiable delivery interface, receiving system, and energy carrier.

It includes the relevant physical delivery path, applicable operating conditions, equipment restrictions, upstream

supply dependencies, receiving-system acceptance conditions, and evidence.

It concludes with a bounded, evidence-supported determination of feasible delivery capability.

6. Governed Object

The primary Governed Object is:

An identifiable energy delivery capability assessment associated with a defined delivery interface, receiving

system, energy carrier, physical delivery path, requested transfer conditions, assessment interval, applicable

operating constraints, evidence, uncertainty, and governance determination.

Relevant fields include:

Delivery Capability Assessment ID

Delivery Interface ID

Receiving System ID

Energy Carrier ID

Delivery Path Reference

Nominal Capacity

Available Capacity

Receiving Acceptance Limit

Requested Transfer Quantity

Requested Transfer Rate

Requested Duration

Assessment Interval

Operating Conditions

Constraint References

Evidence References

Confidence Classification

Governance Determination

7. Scope

DCAM applies to physical delivery capability governance for:

Electrical Energy Delivery

District Heating Delivery

Industrial Steam Delivery

Natural Gas Delivery

Hydrogen Delivery

Liquid Fuel Delivery

Mechanical Energy Transfer

Industrial Multi-Carrier Energy Systems

Hybrid Energy Delivery Systems

Technology-independent governance requirements must be supported by carrier-specific engineering assessment

methods.

8. Foundational Principle

Energy delivery capability must be governed according to the physically feasible transfer of a specified

energy carrier through an identified delivery path into a receiving system under actual operating conditions—

not merely the nominal rating of a connection, declared supply availability, contractual allocation, or assumed

consumer acceptance.

Installed Connection ≠ Available Delivery Capability.

Nominal Capacity ≠ Feasible Transfer Capacity.

Upstream Availability ≠ Receiving-System Acceptance.

Carrier Compatibility ≠ Guaranteed Delivery.

Instantaneous Power Capability ≠ Sustained Energy Delivery.

Physical Feasibility ≠ Operational Authorization.

Operational Authorization ≠ Actual Delivery.

Delivery Capability ≠ Final Energy Consumption.

9. Delivery Capability Reference Model

DCAM establishes the following governance sequence:

Delivery Identity → Energy Carrier → Delivery Path → Upstream Availability → Interface Limits → Carrier

Conditions → Receiving-System Acceptance → Supporting Dependencies → Time-Dependent Constraints →

Requested Transfer → Feasibility Assessment → Evidence → Governance Determination

The model requires the material physical restrictions affecting a requested delivery to remain identifiable.

10. Delivery Assessment Identity

Every capability assessment must possess an identifiable reference.

Relevant fields include:

Assessment ID

Delivery Interface ID

Receiving System ID

Energy Carrier ID

Assessment Purpose

Assessment Time

Evidence Cutoff

The assessment identity must remain stable across subsequent reviews.

11. Delivery Interface Reference

DCAM uses the physical delivery interface identity established by EDIM.

The interface reference must identify:

Physical Connection

Receiving System

Energy Carrier

Transfer Direction

Applicable Boundary

An unidentified interface cannot support a confirmed delivery capability determination.

12. Receiving System Reference

The receiving system must be identifiable.

DCAM must preserve the relationship between the delivery interface and the physical system expected to receive

energy.

A receiving system's installed equipment rating does not automatically establish its current acceptance capability.

13. Energy Carrier Identification

DCAM must identify the energy carrier associated with the proposed transfer.

Examples include:

Electricity

Hot Water

Steam

Natural Gas

Hydrogen

Liquid Fuel

Mechanical Energy

Different carriers require different feasibility criteria.

14. Delivery Path Identification

A delivery path represents the relevant physical route through which energy must pass to reach the receiving system.

It may include:

Upstream Supply Interface

Transport Infrastructure

Conversion Equipment

Control Equipment

Delivery Interface

Receiving Equipment

The material path must be sufficiently identified to evaluate its constraints.

15. Nominal Delivery Capacity

Nominal delivery capacity represents a rated or declared capability under specified reference conditions.

DCAM must preserve:

Rated Quantity

Physical Unit

Reference Conditions

Applicable Equipment

Evidence

Nominal capacity must not automatically be represented as currently available capacity.

16. Available Delivery Capability

Available delivery capability represents the transfer capability physically accessible under the assessed operating

conditions.

It may be lower than nominal capacity because of:

Upstream Restrictions

Equipment Derating

Shared Infrastructure Use

Maintenance

Temperature Conditions

Receiving-System Limits

The applicable assessment interval must remain explicit.

17. Requested Delivery

A delivery feasibility assessment must identify the requested transfer.

Relevant fields include:

Requested Energy Carrier

Requested Power or Transfer Rate

Requested Energy Quantity

Requested Start Time

Requested Duration

Required Carrier Conditions

A request lacking material parameters may be impossible to assess conclusively.

18. Power Versus Energy

DCAM distinguishes instantaneous or time-dependent transfer rate from delivered energy quantity.

For electrical delivery:

Power may be expressed in MW.

Energy may be expressed in MWh.

For constant electrical power over a defined interval:

Energy = Power × Duration

For variable power:

Energy = Integral of Power Over Time

A connection capable of 10 MW does not automatically establish that it can deliver 100 MWh over ten hours.

Sustained availability and operating conditions must also be established.

19. Continuous Delivery Capability

Continuous delivery capability represents the transfer rate that may be sustained under defined conditions.

DCAM must preserve:

Continuous Rating

Applicable Duration

Reference Conditions

Operating Restrictions

Continuous capability must remain distinguishable from short-duration peak capability.

20. Peak Delivery Capability

Peak delivery capability represents a higher transfer rate permitted for a limited period under specified conditions.

DCAM must preserve:

Peak Rating

Maximum Duration

Recovery Conditions

Relevant Constraints

Peak capability must not be treated as continuous capability.

21. Delivery Duration Feasibility

A delivery request must be assessed over its intended duration.

DCAM must evaluate whether:

Upstream Supply Remains Available

Equipment Can Sustain the Transfer

Carrier Conditions Remain Acceptable

Receiving-System Acceptance Persists

Supporting Infrastructure Remains Available

A feasible instantaneous transfer may be infeasible over the requested interval.

22. Upstream Supply Availability

DCAM evaluates whether sufficient energy or transfer capability is available upstream of the delivery interface.

Relevant evidence may include:

Supply Capacity Records

Operational Availability Records

Network Constraint References

Generation Availability References

Storage Availability References

Upstream availability must not be assumed from installed capacity alone.

23. Upstream Dependency

A delivery interface may depend on upstream infrastructure.

Examples include:

Electrical Feeders

Transformers

Thermal Distribution Networks

Gas Supply Pipelines

Pumping Stations

Compression Systems

DCAM must preserve material dependencies affecting delivery feasibility.

24. Shared Infrastructure Constraints

Several delivery interfaces may depend on shared infrastructure.

The aggregate nominal capacity of downstream interfaces may exceed the capability of their shared upstream

connection.

DCAM must identify material shared bottlenecks.

Individual ratings must not be added without considering common restrictions.

25. Delivery Bottleneck

A delivery bottleneck is a material restriction limiting feasible transfer through the assessed path.

Potential bottlenecks include:

Upstream Supply Capacity

Transport Equipment

Delivery Interface Rating

Energy Carrier Conditions

Receiving-System Acceptance

Supporting Equipment

The binding constraint may vary over time.

26. Electrical Delivery Capability

Electrical delivery capability may depend on:

Voltage

Current

Frequency

Power Factor

Thermal Equipment Ratings

Protection Settings

Network Operating Conditions

A nominal electrical connection rating must not replace a condition-specific engineering assessment.

27. Thermal Delivery Capability

Thermal delivery capability may depend on:

Supply Temperature

Return Temperature

Mass Flow Rate

Fluid Properties

Pressure Conditions

Heat Exchanger Capability

Thermal transfer capability must use physically appropriate energy and flow calculations.

28. Steam Delivery Capability

Steam delivery capability may depend on:

Steam Pressure

Temperature

Mass Flow

Enthalpy

Steam Quality

Receiving Equipment Requirements

A nominal mass-flow rating does not independently establish the useful thermal energy available to the receiving

process.

29. Gas Delivery Capability

Gas delivery capability may depend on:

Pressure

Flow Rate

Temperature

Composition

Pipeline Conditions

Receiving Equipment Compatibility

Energy delivery capability must not be inferred from gas volume without appropriate energy-content and reference-

condition information.

30. Hydrogen Delivery Capability

Hydrogen delivery capability may depend on:

Delivery Pressure

Temperature

Flow Rate

Hydrogen Purity

Receiving-System Conditions

Compression Dependencies

Hydrogen mass-transfer capability and chemical energy-transfer capability must remain distinguishable.

31. Liquid Fuel Delivery Capability

Liquid fuel delivery capability may depend on:

Pump Capacity

Flow Rate

Pressure

Temperature

Fuel Properties

Receiving Tank Conditions

Volumetric transfer capability must not automatically be represented as energy delivery capability without an

appropriate fuel energy-content basis.

32. Mechanical Energy Transfer Capability

Mechanical energy delivery may depend on:

Torque

Rotational Speed

Force

Linear Velocity

Mechanical Coupling

Equipment Operating Limits

Mechanical transfer capability must be evaluated using physically appropriate relationships.

33. Energy Carrier Compatibility

DCAM requires assessment of whether the delivered carrier meets the receiving system's physical requirements.

Compatibility may depend on:

Electrical Characteristics

Temperature

Pressure

Chemical Composition

Purity

Mechanical Interface Characteristics

A physically connected system may still be incompatible with the available energy carrier conditions.

34. Receiving-System Acceptance Capability

Receiving-system acceptance capability represents the physical ability of the receiving system to accept the proposed

energy transfer.

Relevant restrictions may include:

Input Equipment Ratings

Current Operating State

Temperature Conditions

Pressure Conditions

Storage Inventory

Process Restrictions

Receiving-system acceptance must not be inferred solely from the delivery interface rating.

35. Receiving Equipment Operating State

DCAM recognizes relevant receiving equipment states:

Available

Operating

Restricted

Unavailable

Under Maintenance

Unknown

The state must correspond to the assessment interval.

36. Consumer Demand Versus Delivery Capability

A receiving system may request more energy than the delivery interface can physically support.

Alternatively, available delivery capability may exceed actual demand.

DCAM must distinguish:

Requested Transfer

Feasible Transfer

Actual Consumption

Consumption and demand assessments remain within ECAM.

37. Ramp and Response Constraints

Delivery capability may depend on how quickly the transfer rate can change.

Relevant constraints include:

Ramp-Up Rate

Ramp-Down Rate

Start-Up Time

Minimum Operating Duration

Recovery Time

A requested delivery profile must be evaluated against applicable dynamic constraints.

38. Time-Dependent Delivery Capability

Delivery capability may vary with:

Time of Day

Ambient Conditions

Network Conditions

Equipment Temperature

Maintenance Activity

Shared Infrastructure Loading

A single capacity value may be insufficient to represent the entire assessment interval.

39. Environmental Operating Conditions

Environmental conditions may affect delivery capability.

Examples include:

Ambient Temperature

Cooling Conditions

Water Availability

Weather Exposure

Equipment Thermal State

Material environmental restrictions must be supported by relevant evidence.

40. Supporting Infrastructure Dependencies

Delivery may depend on supporting equipment.

Examples include:

Cooling Systems

Pumps

Compressors

Control Systems

Protection Systems

Power Supplies

A delivery path must not be considered fully available when a mandatory supporting dependency is unavailable.

41. Equipment Derating

Equipment derating reduces permissible transfer capability under specified conditions.

DCAM must preserve:

Original Rating

Derated Capability

Derating Reason

Applicable Conditions

Effective Time

Evidence

Derating must not be confused with permanent installed capacity reduction.

42. Maintenance Restrictions

Maintenance may restrict delivery capability.

DCAM must preserve:

Affected Equipment

Restriction Period

Applicable Transfer Limit

Evidence

Scheduled maintenance and actual equipment unavailability must remain distinguishable.

43. Contingency Conditions

Delivery capability may differ under abnormal or contingency conditions.

Examples include:

Loss of an Upstream Feeder

Failure of a Pump

Transformer Outage

Compressor Unavailability

Contingency capability must be identified separately from normal operating capability.

44. Redundant Delivery Paths

Some receiving systems have multiple delivery paths.

DCAM must distinguish:

Independent Paths

Partially Shared Paths

Fully Shared Dependencies

Redundancy must not be assumed merely because multiple connections exist.

45. Aggregate Delivery Capability

Aggregate capability may depend on several delivery interfaces.

DCAM must evaluate whether the interfaces can operate simultaneously.

The sum of nominal interface ratings must not exceed physically feasible shared-system capability without supporting

evidence.

46. Bidirectional Delivery Capability

Some delivery interfaces support import and export.

DCAM must evaluate the relevant transfer direction separately.

Import capability must not automatically be treated as equivalent to export capability.

47. Feasible Delivery Envelope

DCAM may represent feasible delivery capability as a condition-dependent operating envelope.

Relevant dimensions include:

Transfer Rate

Duration

Energy Carrier Conditions

Receiving-System State

Upstream Availability

Supporting Infrastructure

The envelope must remain linked to its applicable evidence and reference conditions.

48. Requested Transfer Feasibility

DCAM evaluates whether a specified request falls within the feasible delivery envelope.

The assessment must consider:

Requested Rate

Requested Duration

Start Time

Carrier Conditions

Upstream Availability

Receiving Acceptance

Material Dependencies

A request exceeding a verified physical constraint must not receive a PASS determination.

49. Physical Feasibility Versus Authorization

DCAM distinguishes:

Technical Feasibility

Operational Authorization

Contractual Entitlement

Actual Delivery

A transfer may be technically feasible but unauthorized.

A transfer may be authorized but physically infeasible.

DCAM establishes physical feasibility, not independent permission to operate.

50. Actual Delivery Versus Feasibility

A feasible delivery assessment does not establish that energy was actually transferred.

Actual delivered quantities require measurement or other applicable evidence.

Detailed measurement and attribution remain governed by DMAM.

51. Delivery Capability Evidence

Relevant evidence may include:

Equipment Ratings

Engineering Specifications

Operational Telemetry

Network Constraint Records

Maintenance Records

Receiving Equipment Records

Carrier Condition Measurements

Physical Inspection Evidence

Evidence must correspond to the assessed configuration and operating interval.

52. Declared Versus Verified Capability

DCAM distinguishes:

Declared Capability

Rated Capability

Calculated Capability

Measured Capability

Evidence-Reconciled Capability

Declared or rated capability must not automatically be represented as verified available capability.

53. Capability Evidence Sufficiency

DCAM evaluates whether evidence supports the requested conclusion.

Relevant questions include:

Is the Delivery Interface Identified?

Is the Energy Carrier Known?

Is the Delivery Path Sufficiently Defined?

Are Material Bottlenecks Represented?

Is Upstream Availability Supported?

Is Receiving-System Acceptance Supported?

Are Requested Duration and Conditions Known?

Are Material Uncertainties Preserved?

Insufficient evidence must remain explicit.

54. Capability Conflict

Conflicts may arise from:

Contradictory Equipment Ratings

Inconsistent Operating Records

Different Capacity Definitions

Conflicting Receiving-System Limits

Incompatible Upstream Availability Records

Material conflicts must be preserved until reconciled.

55. Capability Reconciliation

Reconciliation may involve:

Engineering Documentation Review

Operational Data Review

Equipment Rating Verification

Constraint Analysis

Physical Inspection

Time-Dependent Assessment

Reconciliation must preserve the original evidence and justification.

56. Capability Uncertainty

DCAM requires explicit treatment of uncertainty affecting:

Upstream Availability

Interface Capacity

Carrier Conditions

Receiving-System Acceptance

Shared Infrastructure Limits

Requested Duration Feasibility

Unknown uncertainty must not be represented as zero.

57. Confidence Classification

DCAM applies the EGA™ confidence framework.

Confirmed — Sufficient applicable evidence supports the capability conclusion.

Reconciled — The conclusion is supported through justified evidence reconciliation.

Estimated — The conclusion relies on explicit engineering estimation or modeling.

Conflicted — Material evidence supports incompatible conclusions.

Unknown — Available evidence is insufficient.

Confidence must apply to the specific delivery capability or feasibility conclusion.

58. Governance Determination

DCAM supports:

PASS — The specified transfer is supported as physically feasible under the assessed conditions.

CONDITIONAL — Feasibility is supported subject to explicit restrictions or limitations.

FAIL — A verified physical constraint prevents the specified transfer.

INDETERMINATE — Evidence is insufficient or materially conflicting.

NOT APPLICABLE — The assessed requirement does not apply.

A PASS does not establish operational authorization, contractual entitlement, actual energy delivery, or final

consumption.

59. Governance Requirements

A conforming DCAM implementation must satisfy the following requirements.

Delivery Assessment Identity

1. Establish an identifiable delivery capability assessment.

2. Preserve the delivery interface reference.

3. Preserve the receiving system reference.

4. Identify the relevant energy carrier.

5. Define the applicable delivery direction.

6. Identify the material delivery path.

7. Define the assessment interval.

8. Preserve the requested transfer parameters.

9. Preserve nominal capacity references.

10. Distinguish nominal from available delivery capability.

Physical Capability & Carrier Conditions

11. Evaluate material upstream supply availability.

12. Identify relevant upstream dependencies.

13. Identify material shared infrastructure restrictions.

14. Evaluate applicable delivery interface limits.

15. Identify material delivery bottlenecks.

16. Evaluate relevant energy carrier conditions.

17. Evaluate receiving-system acceptance capability.

18. Distinguish continuous from peak capability.

19. Evaluate requested delivery duration.

20. Preserve applicable carrier-specific engineering assumptions.

Operating Constraints & Dependencies

21. Identify relevant receiving equipment operating states.

22. Evaluate material ramp and response constraints.

23. Evaluate time-dependent capability restrictions.

24. Identify material environmental operating conditions.

25. Identify mandatory supporting infrastructure.

26. Preserve applicable equipment derating.

27. Identify material maintenance restrictions.

28. Distinguish normal from contingency capability.

29. Evaluate redundant delivery path dependencies.

30. Prevent unsupported aggregation of nominal interface ratings.

Feasibility & Evidence

31. Evaluate applicable bidirectional transfer limits.

32. Establish a feasible delivery envelope where appropriate.

33. Compare requested transfer against verified constraints.

34. Distinguish physical feasibility from authorization.

35. Distinguish feasible transfer from actual delivery.

36. Preserve material capability evidence.

37. Distinguish declared from verified capability.

38. Evaluate evidence sufficiency.

39. Preserve unresolved capability conflicts.

40. Evaluate material capability uncertainty.

Governance & Interoperability

41. Apply appropriate confidence classifications.

42. Produce evidence-supported feasibility determinations.

43. Preserve applicable physical valid time.

44. Preserve evidence availability time.

45. Maintain EDIM identity and topology consistency.

46. Support ECAM demand and consumption assessments.

47. Support DMAM delivery measurement interpretation.

48. Support DCCM capability change continuity.

49. Maintain machine-readable capability assessment records.

50. Produce an Energy Delivery Capability & Constraints Profile.

60. Governance Logic

Delivery Identity → Energy Carrier → Delivery Path → Upstream Availability → Interface Capacity → Carrier

Conditions → Receiving-System Acceptance → Operating Constraints → Requested Transfer → Physical

Feasibility → Evidence → Governance Determination

For capacity:

Nominal Rating → Available Supply → Shared Constraints → Interface Limits → Receiving Acceptance →

Feasible Capability

For time-dependent feasibility:

Requested Rate → Requested Duration → Operating Envelope → Dynamic Constraints → Sustained Delivery

Feasibility

For authorization separation:

Physical Feasibility Assessment → Separate Authority Assessment → Actual Execution → Delivery

Measurement

DCAM governs the physical feasibility assessment, not the complete authorization or execution chain.

61. Governance Outputs

The principal output is:

Energy Delivery Capability & Constraints Profile

Supporting outputs may include:

Delivery Capability Assessment Record

Delivery Interface Capacity Record

Receiving-System Acceptance Record

Energy Carrier Compatibility Assessment

Delivery Path Assessment

Nominal Capacity Reference

Available Capability Assessment

Continuous Delivery Capability Record

Peak Delivery Capability Record

Requested Transfer Profile

Upstream Supply Availability Assessment

Shared Infrastructure Constraint Record

Delivery Bottleneck Assessment

Carrier Operating Condition Record

Receiving Equipment State Record

Ramp and Response Constraint Record

Time-Dependent Capability Profile

Environmental Constraint Record

Supporting Infrastructure Dependency Record

Equipment Derating Record

Maintenance Restriction Record

Contingency Capability Record

Redundant Path Assessment

Aggregate Delivery Capability Assessment

Bidirectional Transfer Assessment

Feasible Delivery Envelope

Requested Transfer Feasibility Assessment

Capability Evidence Register

Capability Conflict Record

Capability Reconciliation Record

Capability Uncertainty Assessment

Capability Confidence Record

Delivery Feasibility Governance Determination

Outputs must preserve applicable physical conditions, assessment intervals, evidence, uncertainty, and governance

determinations.

62. Minimum Implementation Framework

A minimum DCAM implementation establishes eight governance layers.

Layer 1 — Delivery Assessment Identity

Identify the delivery interface, receiving system, energy carrier, and assessment purpose.

Layer 2 — Delivery Path & Nominal Capability

Identify the physical delivery path, nominal ratings, and relevant equipment.

Layer 3 — Upstream Availability & Shared Constraints

Evaluate upstream supply availability, shared infrastructure dependencies, and material bottlenecks.

Layer 4 — Carrier Compatibility & Receiving Acceptance

Evaluate energy carrier conditions and receiving-system acceptance capability.

Layer 5 — Operating Envelope & Requested Transfer

Assess time-dependent operating limits, requested transfer rate, duration, and feasibility.

Layer 6 — Evidence & Uncertainty

Evaluate capability evidence, conflicts, uncertainty, and confidence.

Layer 7 — Governance Determination

Produce an evidence-supported physical delivery feasibility conclusion.

Layer 8 — Interoperability & Historical Continuity

Maintain capability references for EDIM, ECAM, DMAM, and DCCM.

No specific proprietary technology is mandatory.

63. Cross-Module Boundary

EDIM — Energy Delivery Identification Module

Establishes delivery interface identity, receiving system identity, energy carrier references, and physical topology.

DCAM uses these references to evaluate delivery capability.

ECAM — Energy Consumption Assessment Module

Evaluates actual consumption, demand, and end-use operating conditions.

DCAM provides the feasible delivery capability against which demand may be assessed.

DMAM — Delivery Measurement & Attribution Module

Evaluates actual delivery measurements and physical attribution.

DCAM provides capability constraints relevant to measurement interpretation.

DCCM — Delivery & Consumption Continuity Module

Preserves delivery capability revisions, equipment changes, operating restriction history, and historical assessment

integrity.

DCAM establishes condition-specific capability conclusions; DCCM preserves their continuity.

64. Cross-Architecture Boundary

Energy Generation Standard (EGS)

DCAM may depend on generation availability evidence without governing generation capability itself.

Energy Conversion Standard (ECS)

DCAM evaluates delivery-related conversion dependencies without replacing conversion efficiency governance.

Energy Transmission & Distribution Standard (ETDS)

DCAM evaluates receiving-side delivery feasibility using relevant upstream transport constraints.

Energy Storage Standard (ESS)

DCAM may depend on storage availability and discharge capability where storage supplies the delivery interface.

Energy System Balancing Standard (ESBS)

DCAM provides physically feasible delivery capability references for system balancing.

Energy Supply Reliability Standard (ESRS)

DCAM provides delivery constraint evidence relevant to supply reliability assessments.

65. Verification Framework

DCAM supports verification through explicit assessment tests.

Identity Test: Is the delivery interface identifiable?

Path Test: Is the material delivery path sufficiently defined?

Carrier Test: Is the energy carrier correctly identified?

Nominal Capacity Test: Are rated capacities supported?

Upstream Availability Test: Is available supply supported?

Bottleneck Test: Are material shared restrictions represented?

Receiving Acceptance Test: Can the receiving system accept the proposed transfer?

Operating Constraint Test: Are material physical restrictions represented?

Duration Test: Can the proposed transfer be sustained for the requested interval?

Carrier Compatibility Test: Are relevant carrier conditions acceptable?

Feasibility Test: Does the request fall within the supported operating envelope?

Evidence Test: Is the evidence sufficient?

Uncertainty Test: Are material uncertainties preserved?

Determination Test: Does the conclusion remain within the supported scope?

66. Non-Conformity Classification

DCAM recognizes:

Delivery Assessment Identity Non-Conformity

Delivery Path Non-Conformity

Nominal Capacity Misrepresentation

Available Capability Non-Conformity

Upstream Availability Non-Conformity

Shared Infrastructure Constraint Non-Conformity

Delivery Bottleneck Non-Conformity

Energy Carrier Compatibility Non-Conformity

Receiving-System Acceptance Non-Conformity

Continuous Delivery Capability Non-Conformity

Peak Capability Misrepresentation

Duration Feasibility Non-Conformity

Ramp Constraint Non-Conformity

Supporting Infrastructure Non-Conformity

Equipment Derating Non-Conformity

Contingency Capability Non-Conformity

Capability Evidence Non-Conformity

Capability Uncertainty Non-Conformity

Historical Capability Integrity Non-Conformity

Non-conformities must identify the applicable requirement, affected physical object, assessment interval, and

supporting evidence.

A methodological non-conformity does not automatically establish equipment failure, contractual breach, legal liability,

or regulatory violation.

67. Practical Use Case 1 — Electrical Connection Rating Exceeds

Available Upstream Capability

Situation

An industrial facility has an electrical delivery interface rated at 20 MW.

The facility requests a continuous 18 MW supply for four hours.

The upstream electrical feeder is temporarily restricted to 12 MW because of an equipment limitation.

The facility assumes the 20 MW connection rating establishes that the requested delivery is feasible.

DCAM Assessment

DCAM evaluates:

Delivery Interface Rating → Upstream Feeder Limit → Requested Power → Requested Duration → Physical

Feasibility

The assessment identifies:

The delivery interface is rated at 20 MW.

The upstream feeder is restricted to 12 MW.

The requested 18 MW exceeds the verified upstream limit.

The nominal connection rating does not override the upstream restriction.

The requested transfer cannot be supported under the assessed conditions.

Governance Determination

FAIL — Requested Delivery Exceeds Verified Upstream Transfer Capability.

Methodological Lesson

A delivery connection cannot provide more energy-transfer capability than the binding physical constraints

of its relevant supply path permit.

68. Practical Use Case 2 — District Heating Delivery Limited by

Temperature and Flow Conditions

Situation

A commercial building is connected to a district heating network.

The delivery interface has a nominal thermal capacity of 5 MW under its design conditions.

The building requests 4 MW of thermal delivery.

However, the available supply temperature is lower than the design reference, and the current permitted flow rate

limits thermal transfer.

An engineering assessment establishes that the interface can deliver only 3 MW under the observed conditions.

DCAM Assessment

DCAM evaluates:

Thermal Delivery Interface → Supply Temperature → Flow Rate → Receiving-System Conditions →

Requested Thermal Power

The assessment identifies:

The nominal 5 MW rating applies under defined design conditions.

The actual supply temperature differs from those conditions.

The available flow rate restricts the feasible thermal transfer.

The requested 4 MW exceeds the supported 3 MW capability.

The nominal rating cannot substitute for condition-specific thermal assessment.

Governance Determination

FAIL — Requested Thermal Delivery Exceeds Physically Feasible Capability Under Current Carrier

Conditions.

Methodological Lesson

Energy delivery capability depends on the physical conditions of the energy carrier and receiving system, not

merely the rated capacity of the connection.

69. Temporal Integrity & Historical Capability

DCAM requires delivery capability assessments to preserve two distinct temporal references.

Physical Valid Time

The period during which the assessed equipment configuration, upstream availability, operating restriction, and

receiving-system condition physically applied.

Evidence Availability Time

The time at which the supporting records became available to the assessment process.

Historical as-of assessments must use only evidence available by the defined cutoff.

Later evidence may support a separately identified retrospective reassessment.

It must not silently replace the original historical evidence set.

Material capability changes and assessment revisions are governed through DCCM.

70. GIE™ Compatibility

DCAM is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

Potential machine-readable assessment objects include:

Delivery Capability Assessment

Delivery Interface

Receiving System

Energy Carrier

Delivery Path

Nominal Capacity

Available Capability

Operating Constraint

Supporting Dependency

Receiving Acceptance Limit

Requested Transfer

Feasible Delivery Envelope

Evidence Reference

Confidence Classification

Governance Determination

A compatible implementation may support automated checks for:

Missing Delivery Path References

Unsupported Nominal Capacity Claims

Unaccounted Upstream Restrictions

Shared Infrastructure Bottlenecks

Carrier Compatibility Conflicts

Receiving-System Acceptance Violations

Requested Duration Infeasibility

Unsupported Feasibility Conclusions

Historical Capability Evidence Leakage

GIE-Compatible: Yes establishes architectural and methodological compatibility.

It does not establish completed production integration, validated software behavior, or external certification.

71. Canonical Boundary

DCAM — Delivery Capability Assessment Module governs the identification, assessment, validation, and

evidence-supported interpretation of physical energy delivery capability through identifiable interfaces into

receiving systems under defined operating conditions.

It establishes methodological requirements for nominal and available capacity, upstream supply dependencies,

delivery path restrictions, energy carrier compatibility, receiving-system acceptance, supporting infrastructure, time-

dependent constraints, and requested transfer feasibility.

DCAM does not independently establish physical delivery identities, calculate actual consumption, reconcile

measured delivery quantities, or govern historical configuration changes.

Those responsibilities remain assigned to EDIM, ECAM, DMAM, and DCCM.

Its principal governance output is:

Energy Delivery Capability & Constraints Profile

72. Canonical Closing Statement

Energy delivery capability is not established by the rating of a connection alone.

A delivery interface may be physically installed but restricted.

An upstream network may be unable to support its nominal capacity.

A receiving system may be unable to accept the available energy carrier conditions.

A transfer may be feasible for a short interval but impossible to sustain.

And a technically feasible transfer may still lack the authority required for execution.

DCAM establishes the methodological structure required to distinguish these conditions.

It connects delivery identity with upstream availability, interface capacity, carrier compatibility, receiving-system

acceptance, operating constraints, and time-dependent feasibility.

It prevents nominal ratings from becoming unsupported delivery guarantees.

It prevents shared infrastructure bottlenecks from disappearing inside aggregated capacity figures.

And it ensures that every feasibility conclusion remains tied to a defined transfer request, applicable physical

conditions, evidence, and uncertainty.

Reliable energy delivery governance requires proof not merely that a connection exists, but that the

requested energy can physically pass through the complete relevant delivery path and be accepted by the

receiving system under the assessed conditions.

DCAM establishes that capability requirement within Energy Delivery & Consumption Standard (EDCS).

ECAM — Energy Consumption Assessment Module

Architecture: EGA™ — Energy Governance Architecture

Parent Standard: Energy Delivery & Consumption Standard (EDCS)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: Core Module

Governed Space: Physical Final Energy Consumption, Consuming Asset Operating States, End-Use Energy

Demand, Consumption Boundaries, Energy Input Conditions, Internal Energy Transfers, Consumer-Side Storage &

Conversion References, Actual Consumption, Unserved Demand, Useful Energy Output Distinction, Consumption

Evidence & Operational Consumption Feasibility

Module ID: EGA-EDCS-ECAM-03

Origin ID: OOF-EGA-EDCS-ECAM

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. Canonical Definition

ECAM — Energy Consumption Assessment Module is the third Core Module within Energy Delivery &

Consumption Standard (EDCS), operating under Energy Governance Architecture (EGA™).

ECAM establishes the methodological governance requirements for identifying, assessing, validating, and maintaining

evidence-supported representations of actual energy consumption by identifiable consuming systems within defined

physical boundaries and assessment intervals.

It evaluates the relationship between energy demand, received energy, internal energy transfers, consuming asset

operating states, energy input conditions, actual consumption, and the distinction between consumed energy and

useful end-use output.

ECAM recognizes that energy delivered to a receiving system does not automatically become final energy

consumption.

Energy entering a facility may be distributed internally, converted, stored, exported, or consumed by multiple assets.

Energy entering a storage system may increase stored energy without constituting final consumption at the assessed

boundary.

Energy entering an end-use conversion process may be consumed while producing a smaller quantity of useful

output.

A consuming asset may possess substantial installed input capacity while remaining inactive during the assessment

interval.

A consumer may request energy that cannot be delivered or cannot be accepted under its actual operating conditions.

These distinctions must remain explicit.

ECAM therefore requires energy consumption assessments to identify the consuming object, applicable physical

boundary, energy carrier, operating state, assessment interval, consumption quantity, demand reference, and

supporting evidence.

It distinguishes observed consumption from forecast, scheduled, requested, modeled, or assumed consumption.

It also distinguishes physical consumption from useful energy output and operational service achievement.

ECAM does not independently establish physical delivery identities, determine upstream delivery capability, govern

detailed measurement reconciliation, or preserve historical configuration changes.

Those responsibilities remain assigned to EDIM, DCAM, DMAM, and DCCM.

Its principal governance output is the Energy Consumption & Demand Profile.

2. Operational Role

ECAM establishes the physical energy consumption and demand assessment layer of EDCS.

It governs:

Consumption assessment identity.

Consuming asset references.

Consumption boundary definitions.

Energy carrier identification.

End-use consumption classification.

Consumer operating states.

Installed input capacity references.

Actual energy input conditions.

Requested energy demand.

Forecast energy demand.

Scheduled energy demand.

Observed consumption.

Consumption duration.

Time-dependent consumption.

Partial consumption.

Standby consumption.

Auxiliary consumption.

Internal energy transfers.

Behind-the-meter storage relationships.

Consumer-side energy conversion references.

Useful energy output distinctions.

Unserved demand assessment.

Consumption evidence.

Estimation and uncertainty.

Consumption governance determinations.

ECAM establishes what energy an identifiable consuming system actually uses under defined physical and

operational conditions.

3. Operational Question

How can actual energy consumption by identifiable end-use systems be assessed against demand, received

energy, physical boundaries, operating states, and energy input conditions so that scheduled demand,

installed capacity, internal transfers, stored energy, and useful output are not incorrectly represented as final

consumption?

4. Position in Architecture Governance Flow

Energy Governance Architecture (EGA™)

Energy Source & Origin → Energy Generation → Energy Conversion → Energy Transmission & Distribution ↔

Energy Storage → Energy Delivery & Consumption

Energy Delivery & Consumption Standard (EDCS)

EDIM — Energy Delivery Identification Module

↓

DCAM — Delivery Capability Assessment Module

↓

ECAM — Energy Consumption Assessment Module

↓

DMAM — Delivery Measurement & Attribution Module

↓

DCCM — Delivery & Consumption Continuity Module

EDIM establishes consuming asset identity and physical boundaries.

DCAM establishes relevant delivery capability and constraints.

ECAM evaluates actual consumption and demand.

DMAM evaluates measurement integrity, reconciliation, and attribution.

DCCM preserves changes and historical continuity.

5. Governed Space

Physical Final Energy Consumption, Consuming Asset Operating States, End-Use Energy Demand,

Consumption Boundaries, Energy Input Conditions, Internal Energy Transfers, Consumer-Side Storage &

Conversion References, Actual Consumption, Unserved Demand, Useful Energy Output Distinction,

Consumption Evidence & Operational Consumption Feasibility

The governed space begins with an identifiable consuming system and its physical energy input boundary.

It includes relevant energy carriers, demand references, operating states, energy input conditions, internal energy

relationships, and actual consumption evidence.

It concludes with an evidence-supported assessment of final energy consumption and applicable demand fulfillment.

6. Governed Object

The primary Governed Object is:

An identifiable energy consumption assessment associated with a defined consuming system, consumption

boundary, energy carrier, operating interval, demand reference, energy input conditions, actual or estimated

consumption quantity, evidence, uncertainty, and governance determination.

Relevant fields include:

Consumption Assessment ID

Consuming Asset ID

Receiving System ID

Consumption Boundary ID

Energy Carrier ID

Assessment Interval

Consumer Operating State

Demand Reference

Consumption Quantity

Consumption Measurement Method

Internal Transfer References

Storage References

Conversion References

Evidence References

Physical Valid Time

Evidence Availability Time

Confidence Classification

Governance Determination

7. Scope

ECAM applies to consumption governance across:

Industrial Electrical Equipment

Building Energy Systems

Industrial Thermal Processes

District Heating Consumers

Fuel-Consuming Equipment

Hydrogen-Using Systems

Mechanical Energy Consumers

Multi-Carrier Industrial Facilities

Hybrid Energy Systems

The governance method is technology-independent.

The physical interpretation of consumption remains dependent on the energy carrier, system boundary, and applicable

engineering model.

8. Foundational Principle

Actual energy consumption must be governed according to energy physically used by an identifiable

consuming system within a defined boundary and assessment interval—not merely energy requested,

scheduled, delivered, received, stored, or assumed to produce useful output.

Energy Demand ≠ Actual Consumption.

Installed Input Capacity ≠ Actual Consumption.

Delivered Energy ≠ Final Consumption.

Received Energy ≠ Consumed Energy.

Storage Charging ≠ Automatically Final Consumption.

Consumed Energy ≠ Useful Energy Output.

Equipment Availability ≠ Active Operation.

Estimated Consumption ≠ Directly Measured Consumption.

9. Consumption Assessment Reference Model

ECAM establishes the following governance sequence:

Consuming Asset Identity → Consumption Boundary → Energy Carrier → Demand Reference → Operating

State → Input Conditions → Actual Energy Use → Internal Transfer Classification → Consumption Evidence

→ Uncertainty → Governance Determination

The sequence must preserve the distinction between physical energy input, internal transfers, and final consumption.

10. Consumption Assessment Identity

Every consumption assessment must possess an identifiable reference.

Relevant fields include:

Assessment ID

Consuming Asset ID

Consumption Boundary ID

Energy Carrier

Assessment Purpose

Assessment Interval

Evidence Cutoff

The assessment identity must remain stable across subsequent reviews.

11. Consuming Asset Reference

ECAM uses consuming asset identities established by EDIM.

The asset reference must identify:

Physical Equipment or System

Receiving System Relationship

Energy Carrier

Consumption Boundary

Applicable Operating State

An unidentified consumer cannot support confirmed asset-specific consumption attribution.

12. Consumption Boundary

A consumption boundary establishes the physical extent of the assessed energy use.

Examples include:

Individual Equipment

Production Process

Production Line

Building System

Facility End-Use Group

Different boundaries may produce different consumption quantities.

The boundary must remain explicit.

13. Boundary Hierarchy

Consumption boundaries may be nested.

For example:

Facility → Production Area → Production Line → Machine

A quantity measured at a parent boundary must not automatically be treated as the sum of independently measured

child consumption quantities without accounting for internal distribution, storage, conversion, and losses.

14. Energy Carrier Identification

Every consumption assessment must identify the relevant energy carrier.

Examples include:

Electricity

Hot Water

Steam

Natural Gas

Hydrogen

Liquid Fuels

Mechanical Energy

Carrier identity must correspond to the physical input of the consuming system.

15. Final Energy Consumption

Final energy consumption represents energy used by an end-use system within the defined assessment boundary.

It must remain distinguishable from energy merely transferred through an intermediate system.

An assessment must identify whether the evaluated object is:

A Final Consumer

An Intermediate Distribution System

A Storage System

A Conversion System

A Hybrid System

The classification depends on the assessment boundary and intended energy accounting purpose.

16. Consumption Classification

Relevant consumption classifications include:

Process Consumption

Building Services Consumption

Thermal Consumption

Mechanical Consumption

Auxiliary Consumption

Standby Consumption

Other Identifiable End-Use Consumption

Classifications must reflect actual physical energy use.

17. Installed Consumer Capacity

Installed consumer capacity represents the rated energy input capability of installed equipment.

ECAM must preserve:

Rated Input

Physical Unit

Reference Conditions

Applicable Equipment

Evidence

Installed capacity must not be represented as actual consumption.

18. Actual Consumer Operating State

ECAM recognizes:

Operating

Standby

Restricted

Unavailable

Under Maintenance

Unknown

The operating state must correspond to the assessment interval.

A system classified as available is not necessarily consuming energy.

19. Active Consumption

Active consumption occurs when the consuming system physically uses energy during the assessment interval.

ECAM must preserve:

Consumer Identity

Energy Carrier

Operating Interval

Consumption Quantity

Evidence

Actual consumption must not be inferred solely from equipment installation or nominal rating.

20. Standby Consumption

Standby consumption represents energy used while equipment remains in a non-primary operating state.

Examples include:

Control Electronics

Heating Elements

Standby Pumps

Monitoring Systems

Standby consumption must remain distinguishable from zero consumption.

21. Auxiliary Consumption

Auxiliary consumption represents energy used by supporting systems.

Examples include:

Cooling Equipment

Ventilation

Control Systems

Lubrication Systems

Supporting Pumps

Auxiliary energy may be material to total end-use consumption.

Its inclusion must follow the defined consumption boundary.

22. Idle Equipment

Idle equipment may consume energy despite not producing its intended operational output.

ECAM must distinguish:

Idle With Energy Consumption

Idle Without Material Energy Consumption

Unknown Idle Consumption

Idle state alone does not establish zero energy use.

23. Consumption Duration

Consumption assessments must identify the relevant operating duration.

For constant power:

Energy = Power × Duration

For time-varying power:

Energy = Integral of Power Over the Assessment Interval

Power and energy must remain distinguishable.

24. Time-Dependent Consumption

Consumption may vary over time.

Relevant variations include:

Operating Cycles

Start-Up Periods

Peak Loads

Partial Loads

Standby Periods

Shutdown Periods

A single nominal operating value may be insufficient to establish actual consumption.

25. Energy Demand

Energy demand represents the energy requirement associated with an identifiable consuming system.

ECAM distinguishes:

Forecast Demand

Scheduled Demand

Requested Demand

Observed Demand

Unserved Demand

Each demand classification must remain explicit.

26. Forecast Demand

Forecast demand represents an estimated future energy requirement.

It may be based on:

Historical Consumption

Operating Schedules

Production Plans

Environmental Conditions

Engineering Models

Forecast demand must not be represented as actual consumption.

27. Scheduled Demand

Scheduled demand represents a planned energy requirement for a defined interval.

It may differ from actual consumption because of:

Equipment Unavailability

Production Changes

Delivery Restrictions

Operational Interruptions

Scheduled demand must remain independently identifiable.

28. Requested Demand

Requested demand represents the energy or transfer rate sought by the consuming system.

ECAM must preserve:

Requested Quantity

Requested Rate

Requested Interval

Consuming System

Applicable Conditions

Requested demand does not establish that energy was delivered or consumed.

29. Observed Demand

Observed demand represents an energy requirement or load established through observation under a defined

measurement or assessment method.

ECAM must distinguish observed demand from accumulated energy consumption.

A measured peak power demand does not independently establish total energy consumed.

30. Demand Fulfillment

Demand fulfillment compares an appropriately defined demand requirement with the quantity or service actually

satisfied.

The assessment must preserve:

Demand Definition

Relevant Consumer

Assessment Interval

Delivered or Consumed Quantity

Applicable Operating Conditions

Demand fulfillment must not be inferred solely from a facility-level delivery measurement.

31. Unserved Demand

Unserved demand represents a defined energy requirement that was not satisfied.

ECAM must identify:

Demand Reference

Assessment Interval

Relevant Consumer

Unserved Quantity

Evidence

An unserved-demand conclusion requires a supported demand baseline.

32. Partial Consumption

A consuming system may operate below its nominal capacity or requested demand.

ECAM must distinguish:

Requested Consumption

Permissible Consumption

Actual Consumption

Partial consumption does not automatically establish a delivery failure.

33. Consumer-Side Operating Constraints

Consumption may be restricted by:

Equipment Availability

Input Temperature

Input Pressure

Voltage Conditions

Process Requirements

Safety-Related Operating Limits

ECAM must preserve material restrictions affecting actual energy use.

34. Input Energy Conditions

Energy consumption may depend on the characteristics of the received energy.

Examples include:

Electrical Voltage and Frequency

Thermal Supply Temperature

Steam Pressure and Enthalpy

Fuel Composition

Hydrogen Purity

Input conditions must be evaluated where material to the consumption conclusion.

35. Received Energy Versus Consumption

Energy received by a facility may be:

Consumed Immediately

Distributed Internally

Stored

Converted

Exported

ECAM must distinguish these outcomes.

Received energy must not automatically be classified as final consumption.

36. Internal Energy Transfers

Internal transfers may occur between:

Facility Distribution Systems

Production Processes

Energy Storage Assets

Conversion Equipment

Consuming Assets

ECAM must preserve material transfer relationships affecting consumption assessment.

37. Internal Distribution

Energy may pass through internal infrastructure before reaching the consuming asset.

Examples include:

Electrical Distribution Boards

Heating Circuits

Steam Headers

Fuel Distribution Lines

Internal distribution energy must not automatically be treated as consumed by the final asset.

38. Consumer-Side Storage

A receiving system may contain energy storage.

ECAM must distinguish:

Energy Delivered to the Facility

Energy Charged into Storage

Energy Discharged from Storage

Energy Consumed by End-Use Equipment

Storage charging must not automatically be counted as final consumption at a boundary that treats storage as an

intermediate energy asset.

The classification must follow the explicit assessment boundary.

39. Storage Inventory Changes

A change in stored energy may explain differences between received and consumed energy.

ECAM must preserve relevant storage references where material.

Detailed storage energy accounting remains governed by ESS.

40. Consumer-Side Energy Conversion

A consuming system may convert energy into another physical form.

Examples include:

Electricity to Heat

Electricity to Mechanical Work

Fuel to Thermal Energy

Steam to Mechanical Work

ECAM must preserve the distinction between energy input and useful output.

Detailed conversion governance remains assigned to ECS.

41. Useful Energy Output

Useful energy output represents energy transferred into an intended useful form under a defined end-use boundary.

Examples include:

Mechanical Work

Useful Heat

Process Thermal Energy

Useful output must not automatically be equated with consumed energy.

42. Operational Service Output

Some energy-consuming systems provide services that cannot be expressed solely as an energy quantity.

Examples include:

Indoor Temperature Maintenance

Industrial Production

Cooling Service

Water Pumping

ECAM may preserve service references.

However, service achievement must not be inferred solely from energy consumption.

43. Consumption Versus Efficiency

Energy consumption and energy efficiency are distinct assessment objects.

ECAM establishes the energy consumed within a defined boundary.

Efficiency assessments require appropriate useful output and input relationships.

Detailed efficiency governance remains assigned to EELS and relevant conversion standards.

44. Multiple Consuming Assets

A receiving system may contain multiple consuming assets.

ECAM must preserve the distinction between:

Aggregate Facility Consumption

Individual Asset Consumption

Shared Auxiliary Consumption

Aggregate consumption must not automatically be attributed equally to all consuming assets.

45. Shared Consumption Infrastructure

Multiple consuming assets may share energy infrastructure.

Examples include:

Common Cooling Systems

Shared Compressed-Air Systems

Central Heating Systems

Shared Industrial Steam Networks

ECAM must preserve shared infrastructure references where material.

Detailed physical allocation and measurement reconciliation remain governed by DMAM.

46. On-Site Generation

A consuming system may receive energy from on-site generation.

ECAM must distinguish:

Externally Delivered Energy

On-Site Generated Energy

Internally Consumed Energy

Exported Energy

On-site generation does not automatically reduce total physical consumption.

It may reduce external energy imports while consumption remains unchanged.

47. Hybrid Consumption Systems

A consuming system may use multiple energy carriers.

Examples include:

Electricity and Natural Gas

Electricity and District Heating

Hydrogen and Electricity

Steam and Electrical Energy

ECAM must preserve carrier-specific consumption quantities.

Different energy carriers must not be combined without compatible energy units and explicit accounting boundaries.

48. Consumption Measurement

Consumption may be established through:

Direct Metering

Submetering

Process Measurements

Calculated Quantities

Engineering Estimates

The measurement method must correspond to the consuming asset and assessment boundary.

Detailed measurement validation remains governed by DMAM.

49. Directly Measured Consumption

Direct measurement provides evidence of energy consumption at an identified measurement boundary.

ECAM must preserve:

Measurement Point

Energy Carrier

Assessment Interval

Measured Quantity

Evidence

A measurement is not automatically attributable to a particular asset unless the physical boundary relationship

supports that attribution.

50. Estimated Consumption

Consumption may be estimated when direct measurement is unavailable.

Relevant methods include:

Equipment Load Models

Operating-Hour Models

Process-Based Calculations

Engineering Estimates

Estimated consumption must remain explicitly classified.

51. Consumption Estimation Assumptions

ECAM requires estimation assumptions to remain identifiable.

Examples include:

Operating Hours

Average Load

Duty Cycle

Equipment Efficiency Assumptions

Input Energy Conditions

Unsupported assumptions must not be represented as measured facts.

52. Consumption Evidence

Relevant evidence may include:

Meter Records

Submeter Records

Equipment Operating Logs

Process Measurements

Production Records

Engineering Models

Inspection Evidence

Evidence must correspond to the assessed consuming system and interval.

53. Evidence Sufficiency

ECAM evaluates whether evidence supports the intended consumption conclusion.

Relevant questions include:

Is the Consuming Asset Identifiable?

Is the Consumption Boundary Explicit?

Is the Energy Carrier Known?

Is the Operating Interval Defined?

Is the Consumption Quantity Supported?

Are Demand and Consumption Distinguished?

Are Storage and Internal Transfers Represented?

Are Material Uncertainties Preserved?

Insufficient evidence must remain explicit.

54. Consumption Evidence Conflict

Conflicts may arise from:

Contradictory Meter Records

Inconsistent Equipment Operating Logs

Different Consumption Boundaries

Conflicting Operating Intervals

Incompatible Estimation Models

Material conflicts must remain preserved until reconciled.

55. Consumption Evidence Reconciliation

Reconciliation may involve:

Meter Comparison

Operating Log Review

Boundary Verification

Engineering Model Review

Interval Alignment

Physical Process Analysis

The original evidence and reconciliation justification must remain traceable.

56. Consumption Uncertainty

ECAM requires explicit treatment of uncertainty affecting:

Consumption Quantity

Operating Duration

Consumer Operating State

Demand Baseline

Storage Transfers

Internal Distribution

Energy Carrier Conditions

Estimation Models

Unknown uncertainty must not be represented as zero.

57. Confidence Classification

ECAM applies the EGA™ confidence framework.

Confirmed — Sufficient applicable evidence supports the consumption conclusion.

Reconciled — The conclusion is supported through justified evidence reconciliation.

Estimated — The conclusion relies on explicit modeling or estimation.

Conflicted — Material evidence supports incompatible conclusions.

Unknown — Available evidence is insufficient.

Confidence must apply to the specific consumption or demand conclusion.

58. Governance Determination

ECAM supports:

PASS — Applicable consumption governance requirements are satisfied.

CONDITIONAL — The conclusion is supported subject to explicit limitations.

FAIL — One or more mandatory requirements are not satisfied.

INDETERMINATE — Evidence is insufficient or materially conflicting.

NOT APPLICABLE — The assessed requirement does not apply.

A PASS does not independently establish energy efficiency, contractual fulfillment, regulatory compliance, or useful

service achievement.

59. Governance Requirements

A conforming ECAM implementation must satisfy the following requirements.

Consumption Identity & Boundaries

1. Establish an identifiable consumption assessment.

2. Preserve the consuming asset reference.

3. Define the consumption boundary.

4. Identify the relevant energy carrier.

5. Define the assessment interval.

6. Preserve the receiving system relationship.

7. Distinguish final consumers from intermediate energy assets.

8. Identify relevant nested consumption boundaries.

9. Preserve material consumption classification.

10. Maintain physical boundary consistency.

Operating State & Consumption

11. Identify relevant consumer operating states.

12. Distinguish installed capacity from actual consumption.

13. Identify active consumption where assessable.

14. Identify standby consumption where material.

15. Identify auxiliary consumption where material.

16. Distinguish idle equipment from zero consumption.

17. Preserve actual consumption duration.

18. Evaluate time-dependent consumption where material.

19. Identify relevant energy input conditions.

20. Preserve material consumer-side operating constraints.

Demand & Internal Energy Relationships

21. Distinguish forecast from actual consumption.

22. Distinguish scheduled from actual consumption.

23. Distinguish requested from actual consumption.

24. Preserve observed demand references where applicable.

25. Evaluate demand fulfillment against a supported baseline.

26. Preserve unserved demand where assessable.

27. Distinguish partial consumption from delivery failure.

28. Identify material internal energy transfers.

29. Distinguish storage charging from final consumption.

30. Distinguish consumed energy from useful output.

Measurement & Evidence

31. Identify relevant consumption measurement methods.

32. Preserve directly measured consumption references.

33. Classify estimated consumption explicitly.

34. Preserve material estimation assumptions.

35. Identify applicable consumption evidence.

36. Evaluate evidence sufficiency.

37. Preserve material evidence conflicts.

38. Reconcile conflicting evidence where possible.

39. Evaluate material consumption uncertainty.

40. Apply appropriate confidence classifications.

Governance & Interoperability

41. Produce evidence-supported consumption determinations.

42. Preserve demand assessment references.

43. Preserve material shared consumption infrastructure.

44. Distinguish externally delivered from on-site generated energy.

45. Preserve carrier-specific consumption quantities.

46. Maintain EDIM identity and boundary consistency.

47. Use relevant DCAM delivery capability references.

48. Support DMAM measurement and attribution assessments.

49. Support DCCM consumption change continuity.

50. Produce an Energy Consumption & Demand Profile.

60. Governance Logic

Consuming Asset Identity → Consumption Boundary → Energy Carrier → Demand Reference → Operating

State → Input Conditions → Actual Energy Use → Consumption Evidence → Uncertainty → Governance

Determination

For demand:

Demand Reference → Requested Quantity → Available Delivery → Actual Consumption → Demand

Fulfillment Assessment

For internal energy relationships:

Received Energy → Internal Distribution → Storage or Conversion → Consuming Asset → Final Consumption

For consumption versus useful output:

Energy Input → Actual Consumption → End-Use Conversion → Useful Output

ECAM governs the consumption assessment and preserves references to adjacent conversion and efficiency

governance.

61. Governance Outputs

The principal output is:

Energy Consumption & Demand Profile

Supporting outputs may include:

Consumption Assessment Record

Consuming Asset Reference

Consumption Boundary Profile

Energy Carrier Consumption Record

Consumer Operating State Record

Installed Input Capacity Reference

Active Consumption Assessment

Standby Consumption Record

Auxiliary Consumption Record

Consumption Duration Record

Time-Dependent Consumption Profile

Forecast Demand Record

Scheduled Demand Record

Requested Demand Record

Observed Demand Record

Demand Fulfillment Assessment

Unserved Demand Assessment

Partial Consumption Record

Consumer Operating Constraint Record

Internal Energy Transfer Reference

Storage Relationship Record

Conversion Relationship Record

Useful Output Reference

Measured Consumption Record

Estimated Consumption Record

Estimation Assumption Register

Consumption Evidence Register

Consumption Conflict Record

Consumption Reconciliation Record

Consumption Uncertainty Assessment

Consumption Confidence Record

Consumption Governance Determination

Outputs must preserve applicable physical boundaries, energy carriers, assessment intervals, evidence, uncertainty,

and governance conclusions.

62. Minimum Implementation Framework

A minimum ECAM implementation establishes eight governance layers.

Layer 1 — Consumption Identity

Identify the consuming system, receiving system relationship, energy carrier, and assessment purpose.

Layer 2 — Consumption Boundary

Define the physical consumption boundary and relevant internal energy relationships.

Layer 3 — Demand & Operating State

Identify demand references, consuming asset operating states, and material operating restrictions.

Layer 4 — Actual Energy Consumption

Establish measured or estimated consumption quantities and distinguish them from installed capacity and scheduled

demand.

Layer 5 — Internal Transfers & Useful Output

Identify relevant storage, conversion, auxiliary consumption, and useful output distinctions.

Layer 6 — Evidence & Uncertainty

Evaluate consumption evidence, estimation assumptions, conflicts, uncertainty, and confidence.

Layer 7 — Governance Determination

Produce an evidence-supported consumption and demand assessment.

Layer 8 — Interoperability & Historical Continuity

Maintain stable assessment references for EDIM, DCAM, DMAM, and DCCM.

No specific proprietary technology is mandatory.

63. Cross-Module Boundary

EDIM — Energy Delivery Identification Module

Establishes consuming asset identities, receiving system relationships, energy carriers, and physical boundaries.

ECAM uses these references for consumption assessment.

DCAM — Delivery Capability Assessment Module

Evaluates physical delivery capability and receiving-system acceptance constraints.

ECAM uses relevant capability references when evaluating demand fulfillment.

DMAM — Delivery Measurement & Attribution Module

Evaluates measurement integrity, physical consumption attribution, and energy reconciliation.

ECAM provides consumption objects, demand references, and assessed consumption quantities.

DCCM — Delivery & Consumption Continuity Module

Preserves changes in consuming assets, operating configurations, measurements, and historical assessments.

ECAM establishes the consumption assessment objects whose continuity DCCM governs.

64. Cross-Architecture Boundary

Energy Generation Standard (EGS)

ECAM may use on-site generation references without governing generation performance.

Energy Conversion Standard (ECS)

ECAM preserves consumption input and useful output distinctions without replacing conversion assessment.

Energy Storage Standard (ESS)

ECAM identifies storage-related energy transfers without governing storage capacity, retention, or internal energy

accounting.

Energy Measurement & Reconciliation Standard (EMRS)

ECAM provides consumption quantities and boundary references for measurement reconciliation.

Energy Flow Attribution Standard (EFAS)

ECAM provides identifiable consuming assets and consumption assessment references for physical attribution.

Energy Efficiency & Loss Standard (EELS)

ECAM provides consumed energy quantities and useful output references for efficiency and loss governance.

Energy Supply Reliability Standard (ESRS)

ECAM provides demand and unserved-demand references relevant to supply reliability.

65. Verification Framework

ECAM supports verification through explicit governance tests.

Consumer Identity Test: Is the consuming system identifiable?

Boundary Test: Is the consumption boundary explicit?

Carrier Test: Is the energy carrier correctly identified?

Operating State Test: Is the relevant operating state supported?

Consumption Test: Is actual consumption supported by evidence?

Demand Test: Are forecast, scheduled, requested, and actual quantities distinguished?

Duration Test: Is the assessment interval appropriate?

Storage Test: Are intermediate storage transfers distinguished from final consumption?

Internal Transfer Test: Are material internal energy relationships represented?

Useful Output Test: Is consumption distinguished from useful output?

Evidence Test: Is consumption evidence sufficient?

Estimation Test: Are estimation assumptions explicit?

Uncertainty Test: Are material uncertainties preserved?

Determination Test: Does the governance conclusion remain within the supported scope?

66. Non-Conformity Classification

ECAM recognizes:

Consumption Assessment Identity Non-Conformity

Consuming Asset Identity Non-Conformity

Consumption Boundary Non-Conformity

Energy Carrier Classification Non-Conformity

Operating State Non-Conformity

Installed Capacity Misrepresentation

Actual Consumption Assessment Non-Conformity

Standby Consumption Non-Conformity

Auxiliary Consumption Non-Conformity

Demand Classification Non-Conformity

Unserved Demand Assessment Non-Conformity

Internal Energy Transfer Non-Conformity

Storage Consumption Misclassification

Useful Output Misrepresentation

Consumption Measurement Non-Conformity

Consumption Estimation Non-Conformity

Evidence Sufficiency Non-Conformity

Consumption Uncertainty Non-Conformity

Historical Consumption Integrity Non-Conformity

Non-conformities must identify the affected consuming system, applicable requirement, assessment interval, and

supporting evidence.

A methodological non-conformity does not automatically establish equipment defect, contractual breach, legal liability,

or regulatory violation.

67. Practical Use Case 1 — Industrial Equipment Rated Capacity

Misrepresented as Actual Consumption

Situation

An industrial production line contains ten electric motors.

Each motor has a rated input power of 100 kW.

The facility reports that the production line consumed 1 MWh every hour because the combined installed motor rating

is 1 MW.

However, operating records show that only six motors were active during part of the assessment interval, and several

operated below rated input.

ECAM Assessment

ECAM evaluates:

Installed Motor Capacity → Operating States → Actual Input Power → Operating Duration → Energy

Consumption

The assessment identifies:

Combined installed input capacity of 1 MW.

Actual operation below full installed capacity.

Different motor operating intervals.

Missing evidence supporting the assumed constant 1 MW load.

The need for measured or justified estimated consumption.

Governance Determination

FAIL — Installed Equipment Rating Incorrectly Represented as Actual Energy Consumption.

Methodological Lesson

Installed power capacity does not establish energy consumption without evidence of actual operating power

and duration.

68. Practical Use Case 2 — Battery Charging Incorrectly Classified as

Final Facility Consumption

Situation

A commercial facility receives 500 MWh of electricity during a reporting period.

Of that amount, 100 MWh is transferred into an on-site battery storage system.

The facility reports all 500 MWh as final electricity consumption by its end-use equipment.

The battery retains part of the charged energy at the end of the period and discharges another portion during later

intervals.

ECAM Assessment

ECAM evaluates:

Facility Delivery → Internal Distribution → Battery Charging → Stored-Energy Change → End-Use

Consumption

The assessment identifies:

Total electricity delivered to the facility.

Energy transferred into storage.

Energy remaining stored at the assessment boundary.

Energy subsequently discharged.

The need to distinguish storage transfers from final consumption.

Governance Determination

FAIL — Intermediate Storage Charging Incorrectly Classified as Final End-Use Consumption Under the

Defined Assessment Boundary.

Methodological Lesson

Energy entering a storage system is not automatically final consumption when the assessment boundary

treats storage as an intermediate energy asset.

69. Temporal Integrity & Historical Consumption

ECAM requires consumption assessments to preserve two distinct temporal references.

Physical Valid Time

The period during which the assessed operating state, consumption quantity, demand reference, or internal energy

relationship physically applied.

Evidence Availability Time

The time at which supporting evidence became available to the assessment process.

Historical as-of assessments must use only evidence available by the defined cutoff.

Later evidence may support a separately identified retrospective reassessment.

It must not silently replace the original historical evidence set.

Material changes in consuming assets, operating configurations, and assessment records are governed through

DCCM.

70. GIE™ Compatibility

ECAM is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

Potential machine-readable assessment objects include:

Consumption Assessment

Consuming Asset

Consumption Boundary

Energy Carrier

Operating State

Demand Reference

Consumption Quantity

Consumption Measurement Method

Storage Transfer Reference

Internal Energy Transfer

Useful Output Reference

Evidence Reference

Confidence Classification

Governance Determination

A compatible implementation may support automated checks for:

Missing Consumer Identities

Undefined Consumption Boundaries

Installed Capacity Misrepresented as Consumption

Scheduled Demand Misrepresented as Actual Consumption

Storage Transfers Misclassified as Final Consumption

Unsupported Unserved Demand Conclusions

Conflicting Consumption Evidence

Unjustified Estimation Assumptions

Historical Consumption Evidence Leakage

GIE-Compatible: Yes establishes architectural and methodological compatibility.

It does not establish completed production integration, validated software behavior, or external certification.

71. Canonical Boundary

ECAM — Energy Consumption Assessment Module governs the identification, assessment, validation, and

evidence-supported interpretation of actual energy consumption by identifiable consuming systems within

defined physical boundaries and assessment intervals.

It establishes methodological requirements for consuming asset operating states, energy demand, actual

consumption, internal energy transfers, storage and conversion references, useful output distinctions, consumption

evidence, estimation, uncertainty, and governance determinations.

ECAM does not independently establish delivery interface identities, determine upstream delivery capability, perform

detailed measurement reconciliation, or govern historical configuration changes.

Those responsibilities remain assigned to EDIM, DCAM, DMAM, and DCCM.

Its principal governance output is:

Energy Consumption & Demand Profile

72. Canonical Closing Statement

Energy consumption cannot be established from demand, installed capacity, or delivered energy alone.

A machine may be installed but inactive.

A facility may receive energy that is stored rather than immediately consumed.

A consumer may request energy that is never delivered.

And energy may be consumed without producing the intended useful output.

ECAM establishes the methodological structure required to distinguish these conditions.

It connects consuming asset identity with physical boundaries, energy carriers, operating states, demand, actual

energy use, internal transfers, and evidence.

It prevents nominal equipment ratings from becoming unsupported consumption figures.

It prevents energy stored for later use from being automatically classified as final consumption.

And it ensures that consumption conclusions remain traceable to the actual physical behavior of identifiable

consuming systems.

Reliable energy consumption governance requires evidence of what energy was actually used, by which

system, within which boundary, during which interval, and under which operating conditions.

ECAM establishes that requirement within Energy Delivery & Consumption Standard (EDCS).

DMAM — Delivery Measurement & Attribution Module

Architecture: EGA™ — Energy Governance Architecture

Parent Standard: Energy Delivery & Consumption Standard (EDCS)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: Core Module

Governed Space: Physical Energy Delivery & Consumption Measurement, Measurement Boundary Integrity, Energy

Carrier Accounting, Measurement Point Attribution, Temporal Alignment, Internal Energy Transfer Reconciliation,

Storage & Conversion Adjustments, Consumption Allocation, Measurement Uncertainty, Evidence Provenance,

Accounting Residuals & Evidence-Based Delivery-Consumption Attribution

Module ID: EGA-EDCS-DMAM-04

Origin ID: OOF-EGA-EDCS-DMAM

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. Canonical Definition

DMAM — Delivery Measurement & Attribution Module is the fourth Core Module within Energy Delivery &

Consumption Standard (EDCS), operating under Energy Governance Architecture (EGA™).

DMAM establishes the methodological governance requirements for measuring, validating, reconciling, and physically

attributing energy delivered to receiving systems and energy consumed within identifiable end-use boundaries.

It governs the relationship between delivery measurements, receiving-system measurements, internal energy

transfers, consuming asset measurements, storage inventory changes, conversion processes, measurement

uncertainty, and evidence-supported consumption attribution.

DMAM recognizes that a physically valid energy measurement does not automatically establish the correct physical

attribution of the measured quantity.

A meter installed at a facility entrance may accurately measure total imported electricity without identifying how much

energy individual production systems consumed.

A district heating meter may accurately measure thermal energy transferred at a building interface without establishing

the quantity received by individual internal heating circuits.

A facility may import electricity, generate electricity on-site, charge storage, discharge storage, and export energy

during the same assessment period.

A measured quantity may therefore be physically valid while its interpretation, boundary assignment, or consumption

attribution remains incorrect.

DMAM requires energy measurements to be associated with explicit physical boundaries, identifiable measurement

points, appropriate energy carriers, compatible units, defined assessment intervals, and traceable evidence.

It establishes methodological controls for distinguishing directly measured quantities from calculated, estimated,

reconciled, and administratively allocated quantities.

It also requires physical energy accounting to preserve material internal transfers, storage changes, conversion

boundaries, identified losses, and unresolved accounting residuals.

DMAM does not permit an unexplained difference between measured quantities to be automatically classified as a

verified physical loss.

It does not permit a commercial billing allocation to be represented as physical consumption attribution without an

appropriate evidence basis.

It does not permit measured energy at one physical boundary to be treated as measured energy at another boundary

without justified reconciliation.

DMAM does not independently establish physical asset identities, determine delivery capability, define actual end-use

operating behavior, or govern historical configuration changes.

Those responsibilities remain assigned to EDIM, DCAM, ECAM, and DCCM.

Its principal governance output is the Energy Delivery Measurement & Attribution Profile.

2. Operational Role

DMAM establishes the measurement, accounting, reconciliation, and physical attribution governance layer of EDCS.

It governs:

Delivery measurement identity.

Consumption measurement identity.

Measurement point references.

Physical measurement boundaries.

Energy carrier classification.

Energy measurement units.

Meter and measurement channel references.

Measurement directionality.

Delivered energy quantities.

Received energy quantities.

Consumed energy quantities.

Internal transfer measurements.

Import and export separation.

On-site generation references.

Storage charging and discharging references.

Stored-energy changes.

Conversion input and output references.

Auxiliary energy consumption.

Identified physical losses.

Measurement interval alignment.

Measurement completeness.

Physical energy accounting.

Measurement reconciliation.

Accounting residuals.

Shared infrastructure allocation.

Consumption attribution.

Estimation methods.

Measurement uncertainty.

Evidence provenance.

Governance determinations.

DMAM establishes whether reported energy delivery and consumption quantities are physically meaningful, correctly

bounded, appropriately measured, and supportably attributed.

3. Operational Question

How can measured energy delivery and consumption quantities be validated, reconciled, and attributed to the

correct physical systems so that meter readings, internal transfers, storage changes, conversion processes,

and administrative allocations do not produce unsupported energy accounting or consumption claims?

4. Position in Architecture Governance Flow

Energy Governance Architecture (EGA™)

Energy Source & Origin → Energy Generation → Energy Conversion → Energy Transmission & Distribution ↔

Energy Storage → Energy Delivery & Consumption

Energy Delivery & Consumption Standard (EDCS)

EDIM — Energy Delivery Identification Module

↓

DCAM — Delivery Capability Assessment Module

↓

ECAM — Energy Consumption Assessment Module

↓

DMAM — Delivery Measurement & Attribution Module

↓

DCCM — Delivery & Consumption Continuity Module

EDIM provides physical identities, measurement point references, and boundaries.

DCAM provides applicable delivery capability constraints.

ECAM provides consuming asset identities, demand references, and consumption assessment objects.

DMAM evaluates measured quantities, physical attribution, and reconciliation.

DCCM preserves measurement and assessment continuity.

5. Governed Space

Physical Energy Delivery & Consumption Measurement, Measurement Boundary Integrity, Energy Carrier

Accounting, Measurement Point Attribution, Temporal Alignment, Internal Energy Transfer Reconciliation,

Storage & Conversion Adjustments, Consumption Allocation, Measurement Uncertainty, Evidence

Provenance, Accounting Residuals & Evidence-Based Delivery-Consumption Attribution

The governed space begins with identifiable physical measurement points and energy delivery or consumption

boundaries.

It includes measured and estimated energy quantities, relevant physical transfers, internal energy relationships,

accounting methods, evidence, uncertainty, and attribution.

It concludes with an evidence-supported delivery and consumption measurement governance determination.

6. Governed Object

The primary Governed Object is:

An identifiable energy delivery or consumption measurement and attribution assessment associated with a

defined physical boundary, energy carrier, measurement point, assessment interval, energy quantity,

accounting relationship, consuming system, evidence basis, uncertainty, and governance determination.

Relevant fields include:

Measurement Assessment ID

Delivery Interface ID

Receiving System ID

Consuming Asset ID

Measurement Point ID

Meter Device ID

Measurement Channel ID

Measurement Boundary ID

Energy Carrier ID

Measurement Direction

Assessment Interval

Measured Energy Quantity

Calculated Energy Quantity

Estimated Energy Quantity

Storage Change Reference

Conversion Reference

Attribution Method

Reconciliation Residual

Evidence Reference

Confidence Classification

Governance Determination

7. Scope

DMAM applies to measurement and attribution governance across:

Electrical Energy Delivery

Industrial Electrical Consumption

District Heating Delivery

Industrial Steam Consumption

Natural Gas Delivery

Hydrogen Delivery

Liquid Fuel Consumption

Mechanical Energy Transfer

Multi-Carrier Energy Systems

Hybrid Generation-Storage-Consumption Systems

The governance structure is technology-independent.

The physical measurement method must remain appropriate to the energy carrier and system boundary.

8. Foundational Principle

Energy measurement and attribution must be governed according to physically identified measurement

boundaries, validated quantities, consistent assessment intervals, and evidence-supported energy

relationships—not merely meter readings, billing records, estimated allocations, or assumed correspondence

between delivered and consumed energy.

Meter Reading ≠ Automatically Validated Energy Quantity.

Validated Energy Quantity ≠ Automatically Correct Attribution.

Facility Delivery ≠ Individual Asset Consumption.

Commercial Allocation ≠ Physical Consumption Attribution.

Energy Import ≠ Total Energy Consumption.

Storage Charging ≠ Automatically Final Consumption.

Accounting Residual ≠ Verified Physical Loss.

Measurement Precision ≠ Measurement Accuracy.

9. Measurement & Attribution Reference Model

DMAM establishes the following governance sequence:

Physical Boundary → Measurement Point → Energy Carrier → Measurement Method → Energy Quantity →

Assessment Interval → Physical Transfer Relationships → Reconciliation → Attribution → Evidence →

Uncertainty → Governance Determination

Every material measurement conclusion must remain linked to the physical boundary it represents.

10. Measurement Assessment Identity

Every measurement and attribution assessment must possess an identifiable reference.

Relevant fields include:

Assessment ID

Measurement Purpose

Physical Boundary

Energy Carrier

Assessment Interval

Evidence Cutoff

Applicable Consuming Systems

The assessment identity must remain stable across subsequent reviews.

11. Delivery Measurement Identity

Delivery measurement identifies energy transferred across an established delivery boundary.

DMAM must preserve:

Delivery Interface ID

Measurement Point ID

Energy Carrier

Transfer Direction

Measurement Interval

Energy Quantity

A delivery measurement must not automatically be interpreted as final consumption.

12. Consumption Measurement Identity

Consumption measurement identifies energy use associated with a defined consuming system or consumption

boundary.

DMAM must preserve:

Consuming Asset ID

Consumption Boundary ID

Measurement Point ID

Energy Carrier

Assessment Interval

Measured Quantity

The physical relationship between measurement point and consuming asset must be supported by evidence.

13. Measurement Point Identity

DMAM uses measurement point identities established by EDIM.

A measurement point must be associated with a physically meaningful energy transfer or accounting boundary.

An unidentified measurement point cannot support confirmed physical attribution.

14. Meter Device Identity

A meter device is the physical instrument or measuring assembly used to obtain measurement data.

DMAM must distinguish:

Meter Device ID

Measurement Point ID

Measurement Channel ID

Meter replacement must not automatically change the identity of the underlying measurement point.

15. Measurement Channel Identity

A measurement channel identifies a particular measured quantity or signal.

Examples include:

Electrical Active Energy Import

Electrical Active Energy Export

Thermal Energy Transfer

Gas Volume Flow

Fuel Mass Flow

Different channels must not be treated as interchangeable.

16. Physical Measurement Boundary

The measurement boundary identifies the physical transfer represented by the measurement.

Relevant boundaries include:

Facility Delivery Boundary

Internal Distribution Boundary

Storage Charging Boundary

Storage Discharging Boundary

Consuming Asset Input Boundary

Export Boundary

The boundary must remain explicit.

17. Delivery Boundary Versus Consumption Boundary

A delivery boundary may differ from a consumption boundary.

Energy transferred across the delivery boundary may subsequently:

Enter Internal Distribution

Charge Storage

Undergo Conversion

Supply Auxiliary Equipment

Reach Final Consuming Assets

DMAM must preserve these relationships.

18. Measurement Directionality

Energy measurements may represent:

Import

Export

Charging

Discharging

Internal Transfer

Bidirectional Exchange

Directionality must be preserved.

Gross imports and exports must not be silently replaced by net energy where doing so obscures relevant physical

flows.

19. Energy Carrier Identity

Every measurement must identify the relevant energy carrier.

Examples include:

Electricity

Hot Water

Steam

Natural Gas

Hydrogen

Liquid Fuels

Mechanical Energy

Carrier identity must remain consistent with the physical measurement method.

20. Energy Unit Consistency

Energy quantities must use physically compatible units.

Examples include:

Joule

Kilowatt-Hour

Megawatt-Hour

Gigajoule

Power and energy must remain distinguishable.

Conversions must use physically justified methods and applicable reference conditions.

21. Electrical Energy Measurement

Electrical energy measurement may involve:

Active Energy

Import Energy

Export Energy

Power Integration

Measurement Interval

Meter Configuration

Electrical power ratings must not be substituted for measured energy quantities.

22. Thermal Energy Measurement

Thermal energy measurement may involve:

Mass Flow

Supply Temperature

Return Temperature

Fluid Properties

Specific Enthalpy Difference

Assessment Interval

Thermal energy calculations must use physically appropriate relationships.

For a suitable steady-flow model:

Thermal Transfer Rate = Mass Flow Rate × Specific Enthalpy Difference

The applicable assumptions must remain explicit.

23. Gas Energy Measurement

Gas energy measurement may involve:

Measured Volume or Mass

Pressure

Temperature

Gas Composition

Heating Value Basis

Reference Conditions

A gas volume reading must not automatically be treated as a verified energy quantity without an appropriate

conversion basis.

24. Hydrogen Energy Measurement

Hydrogen energy measurement may involve:

Hydrogen Mass

Flow Rate

Purity

Heating Value Basis

Assessment Interval

Lower heating value and higher heating value references must not be mixed without explicit conversion.

25. Liquid Fuel Energy Measurement

Liquid fuel energy measurement may involve:

Fuel Mass or Volume

Density

Temperature

Fuel Composition

Heating Value Basis

Energy content must be established using an appropriate physical reference.

26. Mechanical Energy Measurement

Mechanical energy measurement may involve:

Torque

Angular Displacement

Force

Linear Displacement

Power

Operating Duration

The selected method must correspond to the physical transfer mechanism.

27. Measurement Interval

Every energy quantity must possess an applicable assessment interval.

Relevant fields include:

Start Time

End Time

Time Reference

Sampling Interval

Aggregation Method

A measurement interval must be sufficiently defined to support physical comparison.

28. Temporal Alignment

Related energy quantities must be evaluated over compatible intervals.

Misaligned intervals can produce apparent energy gains, losses, or attribution errors.

DMAM must identify and resolve or preserve material temporal mismatches.

29. Measurement Sampling

Measurements may be obtained through:

Continuous Measurement

Periodic Sampling

Event-Based Measurement

Manual Readings

Sampling methods must remain appropriate to the assessment purpose.

30. Measurement Aggregation

Measured values may be aggregated over time or across assets.

Aggregation must preserve:

Physical Boundary

Energy Carrier

Directionality

Assessment Interval

Source Measurements

Overlapping quantities must not be counted repeatedly.

31. Missing Measurement Data

Measurement records may contain missing intervals.

DMAM must preserve:

Missing Interval

Affected Measurement Point

Estimated or Reconstructed Quantity

Reconstruction Method

Uncertainty

Missing data must not be silently treated as zero consumption.

32. Invalid Measurement Data

Measurement data may be invalid because of:

Instrument Fault

Incorrect Configuration

Communication Error

Unit Misinterpretation

Timestamp Error

Calibration Problem

Invalid data must not support confirmed measurement conclusions without appropriate correction and evidence.

33. Measurement Accuracy

Measurement accuracy concerns agreement between a measured value and the relevant physical quantity.

DMAM must preserve material accuracy limitations.

High numerical precision does not independently establish accuracy.

34. Measurement Calibration

Calibration evidence may support measurement validity.

Relevant fields include:

Instrument Identity

Calibration Reference

Calibration Date

Applicable Range

Measurement Uncertainty

Calibration evidence must correspond to the relevant measurement device and period.

35. Measurement Configuration

Meter configuration may affect reported energy quantities.

Relevant parameters include:

Measurement Scaling

Current Transformer Ratio

Voltage Transformer Ratio

Direction Settings

Channel Configuration

Unit Configuration

Material configuration errors must remain identifiable.

36. Delivered Energy Quantity

Delivered energy represents energy physically transferred across the defined delivery boundary during the

assessment interval.

DMAM must preserve:

Delivery Boundary

Energy Carrier

Transfer Direction

Measured or Estimated Quantity

Evidence

Delivered energy must remain distinguishable from actual end-use consumption.

37. Received Energy Quantity

Received energy represents energy entering the defined receiving system.

Where delivery and receiving boundaries differ, intermediate physical relationships must be considered.

A delivered quantity must not automatically be assigned to a different receiving boundary.

38. Consumed Energy Quantity

Consumed energy represents energy used by an identifiable consuming system within a defined boundary.

DMAM must preserve the relationship between:

Measurement Point

Consuming Asset

Consumption Boundary

Assessment Interval

Energy Quantity

Attribution must be supported by physical evidence.

39. Internal Energy Transfers

Internal energy transfers may occur between:

Facility Distribution Systems

Storage Assets

Conversion Equipment

Auxiliary Systems

Final Consuming Assets

DMAM must identify material transfers required for energy accounting.

40. On-Site Generation Accounting

A facility may generate energy internally.

DMAM must distinguish:

External Imports

On-Site Generation

Internal Consumption

Storage Charging

Exports

External imports alone may not represent total facility consumption.

41. Storage Charging Accounting

Energy charged into storage must be identified separately where material.

DMAM must preserve:

Charging Boundary

Charging Quantity

Assessment Interval

Storage Asset Reference

Charging energy must not automatically be classified as final consumption at an end-use boundary.

42. Storage Discharging Accounting

Energy discharged from storage must be identified separately where material.

DMAM must preserve:

Discharging Boundary

Discharged Quantity

Assessment Interval

Storage Asset Reference

Discharged energy may subsequently supply end-use consumption.

43. Stored-Energy Changes

A change in stored energy may explain differences between delivered and consumed quantities.

DMAM must preserve relevant storage inventory references.

Detailed storage state and retention accounting remain governed by ESS.

44. Conversion Energy Accounting

Energy conversion may alter the energy carrier or form.

DMAM must distinguish:

Conversion Input

Conversion Output

Relevant Losses

Applicable Boundaries

Detailed conversion performance remains governed by ECS.

45. Auxiliary Energy Accounting

Auxiliary equipment may consume energy.

Examples include:

Cooling Systems

Pumps

Compressors

Control Systems

Ventilation

Auxiliary consumption must be included or excluded according to the defined accounting boundary.

46. Physical Energy Losses

Physical energy losses may occur within internal distribution, conversion, or storage.

DMAM may preserve identified losses supported by evidence.

An accounting residual must not automatically be classified as a verified physical loss.

47. Energy Accounting Reconciliation

DMAM supports reconciliation between:

External Energy Imports

On-Site Generation

Internal Energy Transfers

Storage Inventory Changes

Final Consumption

Energy Exports

Identified Losses

The reconciliation must follow a physically coherent boundary and assessment interval.

48. Energy Balance Representation

For a defined facility boundary and assessment interval, a simplified accounting relationship may be represented as:

External Imports + On-Site Generation = Final Consumption + Exports + Net Increase in Stored Energy +

Identified Losses + Accounting Residual

This relationship applies only where all terms are defined consistently and internal transfers are not double-counted.

Energy conversion and carrier-specific accounting may require additional terms or separate carrier balances.

The residual must remain identifiable.

49. Accounting Residual

An accounting residual represents the difference between the supported energy input and output terms of a defined

balance.

Possible causes include:

Measurement Uncertainty

Missing Data

Boundary Misalignment

Unrecorded Transfers

Incorrect Storage Changes

Unidentified Losses

A residual is not automatically a verified physical loss.

50. Residual Classification

DMAM may classify residuals as:

Within Supported Measurement Uncertainty

Explained Through Reconciliation

Unresolved

Materially Conflicted

The classification must reflect the available evidence.

51. Consumption Attribution

Consumption attribution identifies the physical consuming system associated with an energy quantity.

DMAM requires:

Consuming Asset Identity

Consumption Boundary

Measurement Point

Energy Carrier

Assessment Interval

Evidence

Attribution must remain physically justified.

52. Direct Consumption Attribution

Direct attribution may be supported by a measurement point dedicated to an identifiable consuming asset.

The physical relationship between the measurement point and asset must be validated.

A meter label alone is insufficient where contradictory topology evidence exists.

53. Shared Measurement Attribution

A shared meter may measure several consuming assets.

DMAM must distinguish:

Measured Aggregate Consumption

Individually Measured Consumption

Estimated Individual Consumption

Unallocated Consumption

The aggregate quantity must not automatically be attributed equally to all assets.

54. Consumption Allocation Methods

Where direct measurement is unavailable, allocation may use:

Operating-Hour Models

Equipment Load Models

Process-Based Calculations

Engineering Estimates

Allocation methods must preserve assumptions, limitations, and uncertainty.

55. Commercial Versus Physical Allocation

Commercial allocation may assign energy costs to departments, tenants, or business units.

Physical consumption attribution requires an appropriate physical evidence basis.

DMAM must not represent administrative cost allocation as independently verified energy consumption.

56. Attribution Confidence

Attribution confidence depends on:

Physical Topology Evidence

Measurement Boundary Integrity

Measurement Validity

Allocation Method

Assessment Interval

Uncertainty

A valid aggregate meter reading does not independently establish confirmed individual asset attribution.

57. Measurement Evidence

Relevant evidence may include:

Meter Records

Calibration Records

Meter Configuration Records

Engineering Drawings

Physical Inspection Records

Operating Logs

Storage State Records

Conversion Process Records

Estimation Models

Evidence must correspond to the applicable physical configuration and assessment interval.

58. Evidence Sufficiency

DMAM evaluates whether evidence supports the intended measurement or attribution conclusion.

Relevant questions include:

Is the Measurement Point Identifiable?

Is the Physical Boundary Explicit?

Is the Energy Carrier Known?

Is the Measurement Interval Defined?

Is the Quantity Valid?

Are Material Internal Transfers Represented?

Are Storage Changes Accounted For?

Is the Attribution Method Supported?

Are Material Residuals Preserved?

Insufficient evidence must remain explicit.

59. Measurement Evidence Conflict

Conflicts may arise from:

Contradictory Meter Readings

Inconsistent Meter Configuration

Different Measurement Boundaries

Misaligned Assessment Intervals

Conflicting Storage Records

Incompatible Attribution Models

Material conflicts must remain preserved until reconciled.

60. Evidence Reconciliation

Reconciliation may involve:

Meter Comparison

Calibration Review

Configuration Verification

Boundary Verification

Interval Alignment

Storage State Review

Physical Energy Balance Analysis

Reconciliation must preserve the original evidence and justification.

61. Measurement Uncertainty

DMAM requires explicit treatment of uncertainty affecting:

Measured Energy Quantities

Meter Accuracy

Sampling and Aggregation

Measurement Boundaries

Storage Adjustments

Conversion Accounting

Consumption Allocation

Accounting Residuals

Unknown uncertainty must not be represented as zero.

62. Confidence Classification

DMAM applies the EGA™ confidence framework.

Confirmed — Sufficient applicable evidence supports the measurement or attribution conclusion.

Reconciled — The conclusion is supported through justified evidence reconciliation.

Estimated — The conclusion relies on explicit modeling or allocation.

Conflicted — Material evidence supports incompatible conclusions.

Unknown — Available evidence is insufficient.

Confidence must apply to the specific measurement, reconciliation, or attribution conclusion.

63. Governance Determination

DMAM supports:

PASS — Applicable measurement and attribution requirements are satisfied.

CONDITIONAL — The conclusion is supported subject to explicit limitations.

FAIL — One or more mandatory requirements are not satisfied.

INDETERMINATE — Evidence is insufficient or materially conflicting.

NOT APPLICABLE — The assessed requirement does not apply.

A PASS does not independently establish energy efficiency, contractual settlement accuracy, regulatory compliance,

or useful operational output.

64. Governance Requirements

A conforming DMAM implementation must satisfy the following requirements.

Measurement Identity & Boundaries

1. Establish an identifiable measurement and attribution assessment.

2. Preserve relevant delivery interface references.

3. Preserve relevant consuming asset references.

4. Identify applicable measurement points.

5. Distinguish meter devices from measurement points.

6. Identify relevant measurement channels.

7. Define physical measurement boundaries.

8. Identify the relevant energy carrier.

9. Preserve measurement directionality.

10. Maintain measurement boundary consistency.

Measurement Quantity & Time

11. Preserve appropriate energy units.

12. Distinguish power from energy.

13. Define applicable measurement intervals.

15. Preserve measurement sampling methods.

16. Preserve material aggregation methods.

17. Identify missing measurement data.

18. Identify invalid measurement data.

19. Preserve material calibration evidence.

20. Preserve relevant meter configuration references.

Energy Accounting & Reconciliation

21. Identify delivered energy quantities.

22. Identify received energy quantities where assessable.

23. Identify consumed energy quantities where assessable.

24. Preserve material internal energy transfers.

25. Distinguish external imports from on-site generation.

26. Identify material storage charging and discharging.

27. Preserve relevant stored-energy changes.

28. Identify material conversion energy relationships.

29. Preserve identified physical losses separately from residuals.

30. Maintain a physically coherent energy reconciliation.

Attribution & Evidence

31. Identify material accounting residuals.

32. Classify residuals according to supporting evidence.

33. Preserve consuming asset attribution references.

34. Support direct attribution with physical evidence.

35. Distinguish aggregate from individual consumption.

36. Preserve material shared measurement relationships.

37. Identify applicable allocation methods.

38. Distinguish commercial from physical allocation.

39. Evaluate attribution evidence sufficiency.

40. Preserve material measurement and attribution conflicts.

Governance & Interoperability

41. Reconcile conflicting evidence where possible.

42. Evaluate material measurement uncertainty.

43. Apply appropriate confidence classifications.

44. Produce evidence-supported measurement determinations.

45. Produce evidence-supported attribution determinations.

46. Maintain EDIM identity and boundary consistency.

47. Preserve relevant DCAM capability references.

48. Preserve relevant ECAM consumption references.

49. Support DCCM measurement and assessment continuity.

50. Produce an Energy Delivery Measurement & Attribution Profile.

65. Governance Logic

Measurement Point → Physical Boundary → Energy Carrier → Measurement Method → Energy Quantity →

Assessment Interval → Energy Accounting → Reconciliation → Physical Attribution → Evidence →

Governance Determination

For delivery:

Delivery Interface → Delivery Meter → Delivered Energy Quantity

For consumption:

Consuming Asset → Consumption Boundary → Consumption Measurement → Consumed Energy Quantity

For reconciliation:

Energy Inputs → Internal Transfers → Storage Changes → Final Consumption → Exports → Identified Losses

→ Accounting Residual

For attribution:

Measured Quantity → Physical Connection → Consuming Asset → Attribution Method → Confidence

The governance logic must preserve the distinction between measurement validity and physical attribution validity.

66. Governance Outputs

The principal output is:

Energy Delivery Measurement & Attribution Profile

Supporting outputs may include:

Measurement Assessment Record

Delivery Measurement Record

Consumption Measurement Record

Measurement Point Register

Meter Device Register

Measurement Channel Register

Measurement Boundary Profile

Energy Carrier Measurement Record

Measurement Directionality Record

Measurement Interval Record

Temporal Alignment Assessment

Measurement Sampling Record

Measurement Aggregation Record

Missing Data Record

Invalid Measurement Record

Calibration Evidence Record

Meter Configuration Record

Delivered Energy Quantity Record

Received Energy Quantity Record

Consumed Energy Quantity Record

Internal Transfer Record

On-Site Generation Accounting Record

Storage Charging Record

Storage Discharging Record

Stored-Energy Change Reference

Conversion Energy Accounting Record

Auxiliary Consumption Record

Physical Loss Reference

Energy Reconciliation Record

Accounting Residual Record

Residual Classification Record

Consumption Attribution Record

Shared Measurement Allocation Record

Attribution Method Record

Measurement Evidence Register

Evidence Conflict Record

Evidence Reconciliation Record

Measurement Uncertainty Assessment

Measurement Confidence Record

Measurement Governance Determination

Attribution Governance Determination

Outputs must preserve applicable physical boundaries, energy carriers, assessment intervals, evidence, uncertainty,

and governance conclusions.

67. Minimum Implementation Framework

A minimum DMAM implementation establishes eight governance layers.

Layer 1 — Measurement Identity

Identify measurement points, meter devices, measurement channels, and associated physical objects.

Layer 2 — Physical Measurement Boundaries

Define delivery, receiving, internal transfer, and consumption measurement boundaries.

Layer 3 — Measurement Quantity & Time

Establish energy carriers, units, measurement methods, directionality, and assessment intervals.

Layer 4 — Energy Accounting

Represent delivered energy, received energy, internal transfers, storage changes, consumption, exports, and

identified losses.

Layer 5 — Reconciliation & Attribution

Reconcile physically related quantities, preserve accounting residuals, and attribute consumption to identifiable

systems.

Layer 6 — Evidence & Uncertainty

Evaluate measurement evidence, calibration, configuration, conflicts, allocation assumptions, and uncertainty.

Layer 7 — Governance Determination

Produce evidence-supported measurement and attribution conclusions.

Layer 8 — Interoperability & Historical Continuity

Maintain stable measurement and attribution references for EDIM, DCAM, ECAM, and DCCM.

No specific proprietary technology is mandatory.

68. Cross-Module Boundary

EDIM — Energy Delivery Identification Module

Establishes physical delivery interfaces, receiving systems, consuming assets, measurement point identities, and

boundaries.

DMAM uses these references for measurement and attribution.

DCAM — Delivery Capability Assessment Module

Evaluates physical delivery capability and operating constraints.

DMAM may use relevant capability evidence when evaluating measurement plausibility.

ECAM — Energy Consumption Assessment Module

Evaluates actual consumption, demand, and end-use operating conditions.

DMAM validates measurement relationships and attribution supporting consumption conclusions.

DCCM — Delivery & Consumption Continuity Module

Preserves measurement configuration changes, meter replacements, evidence corrections, and historical assessment

integrity.

DMAM establishes measurement and attribution records whose continuity DCCM governs.

69. Cross-Architecture Boundary

Energy Conversion Standard (ECS)

DMAM preserves conversion input and output references without replacing detailed conversion energy accounting.

Energy Storage Standard (ESS)

DMAM uses storage charging, discharging, and stored-energy change references without replacing storage-specific

measurement and retention governance.

Energy Transmission & Distribution Standard (ETDS)

DMAM governs receiving-side delivery and consumption measurements, while ETDS governs transport flow and

accounting.

Energy Measurement & Reconciliation Standard (EMRS)

DMAM provides delivery and consumption measurement records for wider system-level reconciliation.

Energy Flow Attribution Standard (EFAS)

DMAM provides physically bounded consumption attribution evidence for wider energy flow attribution governance.

Energy Efficiency & Loss Standard (EELS)

DMAM provides validated energy quantities and identified loss references for efficiency and loss assessment.

Energy Claims & Disclosure Standard (ECDS)

DMAM provides evidence relevant to delivery, consumption, and energy-use claims.

70. Verification Framework

DMAM supports verification through explicit governance tests.

Measurement Identity Test: Is the measurement point identifiable?

Boundary Test: Is the measured physical transfer explicitly defined?

Carrier Test: Is the energy carrier correctly identified?

Unit Test: Are physical units appropriate and consistent?

Directionality Test: Are imports, exports, charging, and discharging correctly distinguished?

Interval Test: Are related measurement intervals compatible?

Measurement Validity Test: Is the measured quantity supported by appropriate evidence?

Storage Accounting Test: Are material stored-energy changes represented?

Conversion Accounting Test: Are material conversion relationships represented?

Reconciliation Test: Are physical energy accounting relationships coherent?

Residual Test: Are unexplained differences preserved rather than misclassified?

Attribution Test: Is consumption assigned to the correct physical system?

Evidence Test: Is the supporting evidence sufficient?

Uncertainty Test: Are material uncertainties preserved?

Determination Test: Does the governance conclusion remain within the supported scope?

71. Non-Conformity Classification

DMAM recognizes:

Measurement Assessment Identity Non-Conformity

Measurement Point Identity Non-Conformity

Meter Device Mapping Non-Conformity

Measurement Boundary Non-Conformity

Energy Carrier Measurement Non-Conformity

Physical Unit Non-Conformity

Measurement Directionality Non-Conformity

Measurement Interval Non-Conformity

Measurement Sampling Non-Conformity

Measurement Configuration Non-Conformity

Calibration Evidence Non-Conformity

Delivered Energy Accounting Non-Conformity

Consumption Measurement Non-Conformity

Storage Accounting Non-Conformity

Conversion Accounting Non-Conformity

Energy Reconciliation Non-Conformity

Accounting Residual Misclassification

Physical Consumption Attribution Non-Conformity

Shared Measurement Allocation Non-Conformity

Measurement Evidence Non-Conformity

Measurement Uncertainty Non-Conformity

Historical Measurement Integrity Non-Conformity

Non-conformities must identify the affected measurement, physical boundary, assessment interval, applicable

requirement, and supporting evidence.

A methodological non-conformity does not automatically establish meter malfunction, contractual breach, legal liability,

or regulatory violation.

72. Practical Use Case 1 — Facility Electricity Imports Incorrectly

Reported as Total Consumption

Situation

An industrial facility records 800 MWh of electricity imports during a reporting period.

The facility also operates an on-site solar generation system producing 200 MWh.

During the same period:

150 MWh of solar generation is consumed directly.

50 MWh is exported.

No material stored-energy change occurs.

The facility reports that total electricity consumption equals the 800 MWh imported from the grid.

DMAM Assessment

DMAM evaluates:

Grid Imports → On-Site Generation → Internal Consumption → Exports → Energy Reconciliation

The supported simplified accounting relationship is:

800 MWh Imports + 200 MWh On-Site Generation = Final Consumption + 50 MWh Exports

Assuming the stated quantities share the same boundary and interval, with no material storage change or

unaccounted losses:

Final Consumption = 950 MWh

The reported 800 MWh represents grid imports, not total facility electricity consumption.

Governance Determination

FAIL — External Energy Imports Incorrectly Represented as Total Facility Electricity Consumption.

Methodological Lesson

A facility's grid import meter may accurately measure purchased electricity while failing to represent total

physical consumption when on-site generation contributes energy.

73. Practical Use Case 2 — Shared Meter Consumption Incorrectly

Attributed to One Production Line

Situation

A manufacturing facility contains three production lines supplied through a shared electrical distribution board.

One meter records 600 MWh of electricity consumed by the combined distribution group during the reporting period.

The facility's accounting system assigns the entire 600 MWh to Production Line A.

However, physical connection records show that Production Lines B and C are also supplied through the same

measurement boundary.

No individual production line submeters are available.

DMAM Assessment

DMAM evaluates:

Shared Meter → Physical Distribution Boundary → Connected Production Lines → Consumption Attribution

The assessment identifies:

The 600 MWh measurement represents aggregate consumption for the shared distribution group.

The measurement does not independently establish individual production line consumption.

The allocation to Production Line A lacks physical attribution evidence.

Individual consumption requires appropriate submetering or an explicitly justified estimation method.

Any estimated allocation must preserve assumptions and uncertainty.

Governance Determination

FAIL — Aggregate Measured Consumption Incorrectly Attributed to a Single Consuming Asset Without

Sufficient Physical Evidence.

Methodological Lesson

A valid aggregate energy measurement cannot establish individual consumer attribution when multiple

consuming systems share the same measurement boundary.

74. Temporal Integrity & Historical Measurement

DMAM requires measurement and attribution assessments to preserve two distinct temporal references.

Physical Valid Time

The period during which the measurement, meter configuration, physical boundary, consumption relationship, or

energy accounting condition applied.

Evidence Availability Time

The time at which the supporting evidence became available to the assessment process.

Historical as-of assessments must use only evidence available by their defined cutoff.

Later evidence may support a separately identified retrospective reassessment.

It must not silently replace the original historical evidence set.

Meter replacements, measurement corrections, boundary revisions, and assessment changes are governed through

DCCM.

75. GIE™ Compatibility

DMAM is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

Potential machine-readable assessment objects include:

Measurement Assessment

Measurement Point

Meter Device

Measurement Channel

Physical Measurement Boundary

Energy Carrier

Energy Quantity

Assessment Interval

Energy Accounting Relationship

Storage Change Reference

Conversion Reference

Accounting Residual

Consumption Attribution

Evidence Reference

Confidence Classification

Governance Determination

A compatible implementation may support automated checks for:

Missing Measurement Point Identities

Incorrect Measurement Boundary Assignments

Energy Carrier Unit Conflicts

Import-Export Directionality Errors

Measurement Interval Misalignment

Storage Accounting Omissions

Unsupported Energy Reconciliation

Residual Misclassification

Unsupported Consumption Attribution

Historical Measurement Evidence Leakage

GIE-Compatible: Yes establishes architectural and methodological compatibility.

It does not establish completed production integration, validated software behavior, or external certification.

76. Canonical Boundary

DMAM — Delivery Measurement & Attribution Module governs the identification, validation, reconciliation,

and evidence-supported physical attribution of energy delivery and consumption measurements within

defined physical boundaries and assessment intervals.

It establishes methodological requirements for measurement point identity, physical boundary integrity, energy carrier

accounting, measurement validity, temporal alignment, internal energy transfer reconciliation, storage and conversion

references, consumption attribution, accounting residuals, evidence, uncertainty, and governance determinations.

DMAM does not independently establish physical delivery identities, determine delivery capability, define consuming

asset operating behavior, or govern historical configuration changes.

Those responsibilities remain assigned to EDIM, DCAM, ECAM, and DCCM.

Its principal governance output is:

Energy Delivery Measurement & Attribution Profile

77. Canonical Closing Statement

An energy measurement becomes meaningful only when the physical quantity, measurement boundary, time

interval, and associated system are correctly identified.

A meter may be accurate while its assigned consumer is wrong.

A facility may import less energy than it consumes because of on-site generation.

A storage system may receive energy that is not yet final consumption.

And an unexplained energy balance difference may represent missing evidence rather than verified physical loss.

DMAM establishes the methodological structure required to govern these distinctions.

It connects measurement points with physical boundaries, energy carriers, energy quantities, internal transfers,

consuming systems, and evidence-supported attribution.

It prevents valid meter readings from becoming unsupported consumption claims.

It prevents accounting residuals from being automatically classified as physical losses.

And it ensures that delivery and consumption quantities can be reconciled without concealing uncertainty, double

counting, or incorrect physical assignments.

Reliable energy accounting requires more than knowing how much energy a meter recorded. It requires

establishing what was measured, where it was measured, how it moved through the system, and which

physical consumer can legitimately be associated with that quantity.

DMAM establishes that measurement and attribution requirement within Energy Delivery & Consumption

Standard (EDCS).

DCCM — Delivery & Consumption Continuity Module

Architecture: EGA™ — Energy Governance Architecture

Parent Standard: Energy Delivery & Consumption Standard (EDCS)

Category: Physical Energy Lifecycle Governance

Subcategory: Energy Delivery & Consumption Governance

Type: Core Module

Governed Space: Energy Delivery & Consumption Configuration Continuity, Delivery Interface Changes, Receiving-

System Modifications, Consuming Asset Lifecycle, Physical Boundary Revisions, Delivery Capability Changes,

Consumption Assessment Continuity, Measurement Configuration History, Evidence Corrections, Temporal Integrity,

Historical Reconstruction, Governance Determination Continuity & Traceable Energy System Evolution

Module ID: EGA-EDCS-DCCM-05

Origin ID: OOF-EGA-EDCS-DCCM

Version: 1.0

Status: Canonical Open

Effective Date: 26.10.2026

Authority: OOF® — OriginOpen® Foundation

Protection: (MIP) Methodological Intellectual Property

Compatibility: Methodology OS — Modular Compatibility

GIE-Compatible: Yes

AI-Readable: Yes

Canonical Language: UCL — Universal Canonical Language (English)

1. Canonical Definition

DCCM — Delivery & Consumption Continuity Module is the fifth Core Module within Energy Delivery &

Consumption Standard (EDCS), operating under Energy Governance Architecture (EGA™).

DCCM establishes the methodological governance requirements for preserving the identity, configuration, evidence,

assessment history, and traceable continuity of physical energy delivery and consumption systems as their

operational conditions and physical relationships change over time.

It governs how delivery interfaces, receiving systems, consuming assets, physical boundaries, connection topology,

delivery capabilities, operating restrictions, consumption assessments, measurement configurations, and attribution

relationships are maintained across successive physical and methodological states.

DCCM recognizes that energy delivery and consumption systems are not static.

A facility may install a new delivery interface.

A consuming asset may be replaced.

A production line may be transferred to another electrical distribution circuit.

A district heating meter may be replaced without changing the underlying measurement point.

A receiving system may gain on-site generation or energy storage.

An operating restriction may temporarily reduce delivery capability.

A historical measurement may later be corrected after calibration evidence becomes available.

These events may affect physical identities, assessment boundaries, measured quantities, attribution relationships,

and previously issued governance conclusions.

DCCM requires such changes to remain traceable without silently overwriting the evidence and determinations

associated with earlier system states.

It distinguishes the time when a physical change occurred from the time when evidence of that change became

available.

It distinguishes a corrected historical assessment from the assessment originally issued using the evidence available

at that time.

It requires material changes to preserve the relationship between the previous configuration, the change event, the

resulting configuration, affected assessments, and supporting evidence.

DCCM also establishes controls for historical reconstruction, versioned governance profiles, unresolved change

conflicts, and the continued interpretability of energy delivery and consumption records.

DCCM does not independently establish original physical identities, determine delivery capability, calculate

consumption, or validate measurement quantities.

Those responsibilities remain assigned to EDIM, DCAM, ECAM, and DMAM.

Its principal governance output is the Energy Delivery & Consumption Continuity Profile.

2. Operational Role

DCCM establishes the change, historical integrity, and continuity governance layer of EDCS.

It governs:

Delivery and consumption configuration history.

Physical object continuity.

Delivery interface changes.

Receiving-system modifications.

Consuming asset replacement.

Asset retirement and commissioning.

Physical connection changes.

Delivery boundary revisions.

Consumption boundary revisions.

Energy carrier changes.

Shared infrastructure changes.

On-site generation integration.

Storage integration.

Conversion equipment changes.

Delivery capability revisions.

Operating restriction history.

Consumption assessment revisions.

Measurement point continuity.

Meter device replacement.

Measurement configuration changes.

Consumption attribution revisions.

Evidence availability history.

Historical as-of assessments.

Retrospective reassessments.

Governance determination history.

Change conflict management.

Cross-module continuity.

Machine-readable historical records.

DCCM ensures that energy delivery and consumption governance remains traceable across changing physical

configurations and evolving evidence.

3. Operational Question

How can changes to energy delivery interfaces, receiving systems, consuming assets, physical boundaries,

operating constraints, measurements, and consumption attribution be governed so that current assessments

remain accurate while historical system states, evidence availability, and previously issued governance

determinations remain independently reconstructable?

4. Position in Architecture Governance Flow

Energy Governance Architecture (EGA™)

Energy Source & Origin → Energy Generation → Energy Conversion → Energy Transmission & Distribution ↔

Energy Storage → Energy Delivery & Consumption

Energy Delivery & Consumption Standard (EDCS)

EDIM — Energy Delivery Identification Module

↓

DCAM — Delivery Capability Assessment Module

↓

ECAM — Energy Consumption Assessment Module

↓

DMAM — Delivery Measurement & Attribution Module

↓

DCCM — Delivery & Consumption Continuity Module

DCCM preserves the temporal integrity of the physical identities, delivery capability assessments, consumption

assessments, and measurement relationships established by the preceding modules.

Its continuity requirements apply across the full EDCS assessment lifecycle.

5. Governed Space

Energy Delivery & Consumption Configuration Continuity, Delivery Interface Changes, Receiving-System

Modifications, Consuming Asset Lifecycle, Physical Boundary Revisions, Delivery Capability Changes,

Consumption Assessment Continuity, Measurement Configuration History, Evidence Corrections, Temporal

Integrity, Historical Reconstruction, Governance Determination Continuity & Traceable Energy System

Evolution

The governed space begins with an identifiable energy delivery or consumption configuration and its associated

evidence.

It includes physical changes, configuration revisions, measurement modifications, assessment corrections, and

historical governance relationships.

It concludes with an evidence-supported continuity record capable of distinguishing previous, current, and

retrospectively reconstructed system states.

6. Governed Object

The primary Governed Object is:

An identifiable delivery and consumption continuity record associated with a physical energy system,

configuration version, change event, affected delivery or consumption objects, physical valid time, evidence

availability time, supporting evidence, historical assessment relationships, uncertainty, and governance

determination.

Relevant fields include:

Continuity Record ID

Delivery Interface ID

Receiving System ID

Consuming Asset ID

Configuration Version ID

Change Event ID

Previous Configuration Reference

Resulting Configuration Reference

Affected Boundary References

Affected Measurement References

Affected Assessment References

Physical Valid Time

Evidence Availability Time

Assessment Issuance Time

Evidence Reference

Confidence Classification

Governance Determination

7. Scope

DCCM applies to continuity governance across:

Electrical Energy Delivery Systems

Industrial Energy Consumption Systems

District Heating Consumers

Industrial Steam Systems

Fuel Delivery and Consumption Systems

Hydrogen Delivery Systems

Mechanical Energy Transfer Systems

Hybrid Energy Facilities

Multi-Carrier Energy Systems

The governance structure is technology-independent.

Physical changes must remain interpretable according to the relevant energy carrier and system configuration.

8. Foundational Principle

Energy delivery and consumption governance must preserve the relationship between physical system

states, configuration changes, evidence availability, and governance determinations so that present

knowledge cannot silently rewrite the operational reality or evidentiary basis of the past.

Current Configuration ≠ Historical Configuration.

Physical Change Time ≠ Evidence Availability Time.

Meter Replacement ≠ Automatically New Measurement Point.

Asset Replacement ≠ Automatically Same Physical Identity.

Corrected Measurement ≠ Original Measurement Record.

Retrospective Assessment ≠ Original Historical Assessment.

Latest Evidence ≠ Evidence Available at the Historical Cutoff.

Configuration Continuity ≠ Unchanged Physical System.

9. Continuity Reference Model

DCCM establishes the following governance sequence:

Existing Configuration → Change Event → Change Evidence → Affected Objects → Physical Valid Time →

Resulting Configuration → Assessment Impact → Historical Record Preservation → Governance

Determination → Continuity Profile

The sequence must preserve both the physical history and the history of knowledge about that physical system.

10. Continuity Record Identity

Every continuity assessment must possess an identifiable reference.

Relevant fields include:

Continuity Record ID

Governed System ID

Change Event ID

Assessment Purpose

Assessment Time

Evidence Cutoff

The continuity record must remain distinguishable from the physical asset and its configuration versions.

11. Physical System Identity Continuity

A physical energy system may remain identifiable across changes to its internal configuration.

DCCM must distinguish:

Persistent System Identity

Physical Asset Identity

Configuration Version Identity

Change Event Identity

These references must not be treated as interchangeable.

12. Configuration Version Identity

Each material configuration state must possess an identifiable version reference.

Relevant fields include:

Configuration Version ID

Applicable Physical Objects

Physical Connection Topology

Relevant Boundaries

Effective Period

Supporting Evidence

A configuration version must represent a defined physical state.

13. Previous Configuration

DCCM must preserve the configuration that applied before a material change.

Relevant information includes:

Delivery Interfaces

Receiving Systems

Consuming Assets

Physical Connections

Measurement Points

Operating Constraints

The previous configuration must remain independently reconstructable.

14. Resulting Configuration

DCCM must preserve the configuration resulting from a material change.

The resulting configuration must identify:

Added Objects

Modified Objects

Removed Objects

Changed Connections

Revised Boundaries

Affected Measurements

The resulting configuration must not overwrite the previous state.

15. Change Event Identity

Every material change event must possess an identifiable reference.

Relevant fields include:

Change Event ID

Change Type

Affected Physical Objects

Physical Effective Time

Evidence Availability Time

Supporting Evidence

Change events must remain traceable.

16. Change Classification

DCCM recognizes:

Physical Installation

Equipment Replacement

Equipment Removal

Connection Modification

Boundary Revision

Operating Restriction Change

Measurement Configuration Change

Assessment Correction

Evidence Update

Different change types may require different continuity controls.

17. Delivery Interface Changes

Delivery interfaces may be:

Installed

Modified

Reconfigured

Disconnected

Replaced

DCCM must preserve the previous and resulting interface relationships.

A new physical connection must not automatically inherit an unrelated historical interface identity.

18. Receiving-System Modifications

Receiving systems may undergo:

Expansion

Subdivision

Integration

Equipment Replacement

Internal Distribution Changes

DCCM must preserve material changes affecting delivery and consumption assessments.

19. Consuming Asset Lifecycle

Consuming assets may pass through:

Installation

Commissioning

Operation

Modification

Decommissioning

Replacement

DCCM must preserve the applicable lifecycle state and supporting evidence.

20. Asset Replacement

A replaced asset may retain the same operational role while possessing a different physical identity.

DCCM must distinguish:

Previous Physical Asset

Replacement Physical Asset

Operational Role Continuity

Identity Relationship

Replacement must not erase the previous asset's assessment history.

21. Asset Retirement

A retired consuming asset must remain identifiable in historical records.

DCCM must preserve:

Asset ID

Retirement Event

Effective Time

Historical Assessment References

Retirement must not remove evidence supporting previous consumption assessments.

22. Asset Commissioning

Newly commissioned equipment may alter energy demand and consumption relationships.

DCCM must preserve:

Commissioning Date

Asset Identity

Connected System

Applicable Consumption Boundary

Evidence

Commissioning records must not automatically establish actual energy consumption.

23. Physical Connection Changes

Connections may be:

Added

Removed

Rerouted

Reclassified

Reversed

DCCM must preserve topology changes affecting delivery and consumption attribution.

24. Delivery Boundary Revisions

A delivery boundary may change because of physical reconfiguration or revised assessment scope.

DCCM must distinguish:

Physical Boundary Change

Administrative Boundary Redefinition

Measurement Boundary Correction

These events have different implications for historical records.

25. Consumption Boundary Revisions

A consumption boundary may expand, contract, or be redefined.

DCCM must preserve the relationship between the previous and revised boundaries.

Consumption quantities calculated under different boundaries must not be compared as equivalent without

appropriate reconciliation.

26. Boundary Versioning

Material boundaries must possess version references where their definitions change.

Relevant fields include:

Boundary ID

Boundary Version

Physical Extent

Effective Period

Evidence

Boundary versioning must support historical reconstruction.

27. Energy Carrier Changes

A receiving system may change its energy carrier.

Examples include:

Natural Gas to Electricity

Fuel Oil to District Heating

Steam to Electrical Heating

DCCM must preserve the previous and resulting carrier relationships.

Carrier changes must not erase historical consumption records.

28. Shared Infrastructure Changes

Shared infrastructure may be modified.

Examples include:

Transformer Replacement

Distribution Board Reconfiguration

Thermal Header Modification

Gas Pipeline Rerouting

DCCM must preserve affected receiving systems and consuming assets.

29. On-Site Generation Integration

A facility may install on-site generation.

DCCM must preserve changes to:

Energy Import Relationships

Internal Distribution

Export Interfaces

Consumption Accounting Boundaries

On-site generation integration may affect historical comparability.

30. Energy Storage Integration

A receiving system may add or remove storage.

DCCM must preserve:

Storage Asset Identity

Charging Interface

Discharging Interface

Relevant Measurement Points

Effective Configuration

Storage integration may change the relationship between delivered and consumed energy.

31. Energy Conversion Changes

Conversion equipment may be installed, replaced, or reconfigured.

DCCM must preserve material changes to:

Input Energy Carrier

Output Energy Carrier

Conversion Equipment Identity

Physical Connection Relationships

Detailed conversion performance remains governed by ECS.

32. Delivery Capability Changes

Delivery capability may change because of:

Equipment Replacement

Network Reinforcement

Operating Restrictions

Shared Infrastructure Changes

Receiving-System Modifications

DCCM must preserve the relevant capability assessment versions.

33. Temporary Delivery Restrictions

Temporary restrictions may affect delivery capability during a defined interval.

DCCM must preserve:

Restriction Identity

Affected Interface

Restriction Start

Restriction End

Supporting Evidence

A temporary restriction must not automatically become a permanent capacity revision.

34. Permanent Capability Revisions

Permanent capability changes may result from physical modifications.

DCCM must preserve the previous and resulting capability references.

A revised capacity rating must not silently replace the rating applicable to earlier assessments.

35. Consumer Operating Configuration Changes

Consuming systems may change their operating configuration.

Examples include:

Production Line Reconfiguration

Equipment Control Changes

Load Redistribution

Operating Schedule Changes

DCCM must preserve material changes affecting consumption assessment.

36. Consumption Assessment Revisions

Consumption assessments may be revised because of:

New Measurements

Corrected Asset Relationships

Revised Operating Logs

Updated Estimation Models

Boundary Corrections

Revisions must remain distinguishable from original assessments.

37. Demand Assessment Continuity

Demand references may change over time.

DCCM must preserve:

Forecast Versions

Scheduled Demand Revisions

Requested Demand Changes

Observed Demand Records

A later forecast must not replace an earlier forecast in a historical assessment.

38. Measurement Point Continuity

A measurement point may remain physically meaningful across meter replacements.

DCCM must distinguish:

Measurement Point Identity

Meter Device Identity

Measurement Channel Identity

Configuration Version

Continuity must follow the physical measurement boundary.

39. Meter Device Replacement

Meter replacement must preserve:

Previous Meter ID

Replacement Meter ID

Measurement Point ID

Replacement Time

Configuration Evidence

The replacement must not erase previous meter records.

40. Measurement Configuration Changes

Meter configuration may change.

Relevant changes include:

Scaling Factors

Transformer Ratios

Direction Settings

Measurement Channels

Sampling Intervals

DCCM must preserve configuration versions and effective periods.

41. Measurement Boundary Changes

A measurement boundary may change because of physical reconfiguration or corrected mapping.

DCCM must preserve:

Previous Boundary

Revised Boundary

Affected Measurements

Effective Time

Evidence

Measurements from different boundaries must not be treated as directly equivalent without appropriate assessment.

42. Measurement Corrections

Historical measurements may require correction.

Relevant causes include:

Meter Configuration Error

Incorrect Scaling

Timestamp Error

Invalid Measurement Data

Boundary Misassignment

DCCM must preserve original values, corrected values, correction reasons, and evidence.

43. Original Measurement Preservation

Original measurement records must remain distinguishable from corrected records.

A correction must not silently overwrite the original evidence.

Where source systems do not preserve originals, the resulting historical limitation must be recorded.

44. Consumption Attribution Changes

Consumption attribution may change when:

Assets Are Reconnected

Meters Are Reassigned

Consumption Boundaries Change

New Submeters Are Installed

DCCM must preserve the applicable attribution method and period.

45. Allocation Method Revisions

Estimated consumption allocation methods may change.

DCCM must preserve:

Previous Allocation Method

Revised Allocation Method

Effective Period

Affected Consumption Records

Supporting Justification

Historical comparisons must identify material methodological differences.

46. Physical Valid Time

Physical valid time represents when a physical configuration, operating condition, measurement relationship, or

energy system state applied.

DCCM must preserve relevant physical validity intervals.

Physical validity must not be inferred solely from the date a record was entered into a database.

47. Evidence Availability Time

Evidence availability time represents when supporting information became available to the assessment process.

DCCM must preserve the availability time of material evidence.

Evidence availability time may differ from physical valid time.

48. Assessment Issuance Time

Assessment issuance time identifies when a governance determination was produced.

DCCM must distinguish:

Physical Valid Time

Evidence Availability Time

Assessment Issuance Time

These timestamps serve different purposes.

49. Historical As-Of Assessment

A historical as-of assessment evaluates a defined past state using evidence available by a specified cutoff.

DCCM requires:

Assessment Cutoff

Applicable Configuration

Eligible Evidence

Historical Governance Rules

Original Determination

Evidence becoming available after the cutoff must not be silently included.

50. Retrospective Reassessment

A retrospective reassessment evaluates a historical physical state using evidence obtained later.

DCCM must preserve:

Original Assessment Reference

New Evidence

Reassessment Date

Revised Determination

Reason for Revision

The retrospective result must remain distinguishable from the original historical assessment.

51. Historical Reconstruction

Historical reconstruction establishes the physical configuration and evidence-supported relationships applicable to a

defined past interval.

It may require:

Configuration Versions

Change Events

Physical Valid Time

Measurement History

Evidence Availability Records

Reconstruction must preserve uncertainty where historical evidence is incomplete.

52. Historical Evidence Integrity

DCCM requires original evidence references to remain traceable.

Relevant evidence includes:

Engineering Drawings

Asset Registers

Meter Records

Operating Logs

Maintenance Records

Configuration Records

Inspection Evidence

Later corrections must not erase the original evidentiary record.

53. Governance Determination History

Governance determinations may change because of new evidence or revised configurations.

DCCM must preserve:

Original Determination

Original Evidence Basis

Revised Determination

Revision Reason

Revision Time

A later PASS must not silently replace an earlier FAIL.

54. Assessment Comparability

Historical assessments may use different:

Physical Boundaries

Equipment Configurations

Measurement Methods

Energy Carriers

Allocation Methods

DCCM must identify material differences before assessments are compared.

55. Change Impact Assessment

A material change may affect several governance objects.

DCCM must evaluate impacts on:

Physical Identity

Delivery Capability

Consumption Assessment

Measurement Boundary

Attribution Relationship

Historical Comparability

Change impact must remain traceable.

56. Cross-Module Change Propagation

DCCM preserves change relationships across EDCS.

A delivery interface modification may require:

EDIM Identity Review

DCAM Capability Reassessment

ECAM Consumption Boundary Review

DMAM Measurement Mapping Review

DCCM records the resulting assessment dependencies.

57. Change Evidence Sufficiency

DCCM evaluates whether evidence supports the change conclusion.

Relevant questions include:

Is the Change Event Identifiable?

Are Affected Objects Known?

Is the Physical Effective Time Supported?

Is the Previous Configuration Preserved?

Is the Resulting Configuration Supported?

Are Affected Assessments Identified?

Is Evidence Availability Time Preserved?

Insufficient evidence must remain explicit.

58. Change Conflict

Conflicts may arise from:

Contradictory Installation Dates

Inconsistent Asset Registers

Conflicting Meter Replacement Records

Unrecorded Physical Modifications

Different Boundary Histories

Material conflicts must remain preserved until reconciled.

59. Change Reconciliation

Reconciliation may involve:

Engineering Documentation Review

Asset Register Comparison

Maintenance Record Review

Meter Configuration Review

Physical Inspection

Historical Data Comparison

Reconciliation must preserve the original evidence and justification.

60. Continuity Uncertainty

DCCM requires explicit treatment of uncertainty affecting:

Change Event Timing

Physical Configuration History

Asset Identity Continuity

Boundary Revisions

Measurement Corrections

Historical Attribution

Evidence Availability

Unknown uncertainty must not be represented as zero.

61. Confidence Classification

DCCM applies the EGA™ confidence framework.

Confirmed — Sufficient applicable evidence supports the continuity conclusion.

Reconciled — The conclusion is supported through justified evidence reconciliation.

Estimated — The conclusion relies on explicit reconstruction or estimation.

Conflicted — Material evidence supports incompatible conclusions.

Unknown — Available evidence is insufficient.

Confidence must apply to the specific historical configuration, change event, or continuity relationship.

62. Governance Determination

DCCM supports:

PASS — Applicable continuity and historical integrity requirements are satisfied.

CONDITIONAL — The conclusion is supported subject to explicit limitations.

FAIL — One or more mandatory continuity requirements are not satisfied.

INDETERMINATE — Evidence is insufficient or materially conflicting.

NOT APPLICABLE — The assessed requirement does not apply.

A PASS does not independently establish energy delivery capability, consumption accuracy, regulatory compliance, or

equipment reliability.

63. Governance Requirements

A conforming DCCM implementation must satisfy the following requirements.

Configuration & Physical Identity Continuity

1. Establish identifiable continuity records.

2. Preserve persistent physical system references.

3. Distinguish physical object identity from configuration version.

4. Establish identifiable configuration versions.

5. Preserve previous configuration references.

6. Preserve resulting configuration references.

7. Identify material change events.

8. Classify material change types.

9. Preserve affected physical object references.

10. Maintain traceable configuration relationships.

Delivery & Consumption Changes

11. Preserve delivery interface changes.

12. Preserve receiving-system modifications.

13. Preserve consuming asset lifecycle events.

14. Distinguish replacement assets from previous physical identities.

15. Preserve material connection topology changes.

16. Preserve delivery boundary revisions.

17. Preserve consumption boundary revisions.

18. Preserve energy carrier changes.

19. Preserve relevant shared infrastructure changes.

20. Preserve material storage and conversion integration changes.

Capability, Consumption & Measurement History

21. Preserve delivery capability assessment revisions.

22. Preserve temporary operating restrictions.

23. Preserve permanent capability changes.

24. Preserve consuming asset operating configuration changes.

25. Preserve consumption assessment revisions.

26. Preserve demand assessment versions.

27. Maintain measurement point continuity.

28. Preserve meter device replacement history.

29. Preserve measurement configuration versions.

30. Preserve consumption attribution method revisions.

Temporal Integrity & Historical Evidence

31. Preserve physical valid time.

32. Preserve evidence availability time.

33. Preserve assessment issuance time.

34. Establish explicit historical as-of cutoffs.

35. Exclude post-cutoff evidence from original as-of assessments.

36. Preserve original historical assessment records.

37. Distinguish retrospective reassessments from original assessments.

38. Preserve original measurement records during correction.

39. Maintain historical configuration reconstruction capability.

40. Preserve governance determination history.

Governance & Interoperability

41. Evaluate material change impacts.

42. Preserve cross-module change dependencies.

43. Evaluate change evidence sufficiency.

44. Preserve material change conflicts.

45. Reconcile conflicting evidence where possible.

46. Evaluate material continuity uncertainty.

47. Apply appropriate confidence classifications.

48. Produce evidence-supported continuity determinations.

49. Maintain machine-readable historical configuration and assessment records.

50. Produce an Energy Delivery & Consumption Continuity Profile.

64. Governance Logic

Existing Configuration → Change Event → Physical Effective Time → Evidence Availability → Affected

Objects → Resulting Configuration → Assessment Impact → Historical Preservation → Governance

Determination

For physical continuity:

Physical Object → Configuration Version → Change Event → New Configuration Version

For measurement continuity:

Measurement Point → Previous Meter → Replacement Event → New Meter → Measurement Continuity

For historical assessment:

Historical Cutoff → Eligible Evidence → Applicable Configuration → Original Determination

For retrospective reassessment:

Original Assessment → Later Evidence → Reassessment → Revised Determination → Preserved Original

Record

The governance logic must preserve both physical change history and the chronology of evidence availability.

65. Governance Outputs

The principal output is:

Energy Delivery & Consumption Continuity Profile

Supporting outputs may include:

Continuity Assessment Record

Physical System Identity Continuity Record

Configuration Version Register

Previous Configuration Profile

Resulting Configuration Profile

Change Event Register

Delivery Interface Change Record

Receiving-System Modification Record

Consuming Asset Lifecycle Record

Asset Replacement Record

Asset Retirement Record

Connection Topology Change Record

Delivery Boundary Revision Record

Consumption Boundary Revision Record

Energy Carrier Change Record

Shared Infrastructure Change Record

On-Site Generation Integration Record

Storage Integration Record

Conversion Equipment Change Record

Delivery Capability Revision Record

Operating Restriction History

Consumption Assessment Revision Record

Demand Assessment Version Record

Measurement Point Continuity Record

Meter Replacement Record

Measurement Configuration History

Measurement Correction Record

Consumption Attribution Revision Record

Physical Valid Time Record

Evidence Availability Record

Assessment Issuance Record

Historical As-Of Assessment Record

Retrospective Reassessment Record

Historical Reconstruction Profile

Governance Determination History

Change Impact Assessment

Change Evidence Register

Change Conflict Record

Change Reconciliation Record

Continuity Uncertainty Assessment

Continuity Confidence Record

Continuity Governance Determination

Outputs must preserve applicable physical configurations, change relationships, temporal references, evidence,

uncertainty, and governance conclusions.

66. Minimum Implementation Framework

A minimum DCCM implementation establishes eight governance layers.

Layer 1 — Physical Identity Continuity

Establish stable references for delivery interfaces, receiving systems, consuming assets, and relevant measurement

points.

Layer 2 — Configuration Versioning

Preserve identifiable previous and resulting physical configurations.

Layer 3 — Change Event Governance

Identify material changes, affected objects, change types, and physical effective times.

Layer 4 — Assessment Impact

Evaluate impacts on delivery capability, consumption assessments, physical boundaries, measurements, and

attribution.

Layer 5 — Temporal & Historical Integrity

Preserve physical valid time, evidence availability time, historical cutoffs, original assessments, and retrospective

reassessments.

Layer 6 — Evidence & Uncertainty

Evaluate change evidence, conflicts, reconciliation, historical reconstruction limitations, and uncertainty.

Layer 7 — Governance Determination

Produce an evidence-supported continuity and historical integrity conclusion.

Layer 8 — Interoperability & Historical Preservation

Maintain machine-readable change relationships and historical assessment references across EDIM, DCAM, ECAM,

and DMAM.

No specific proprietary technology is mandatory.

67. Cross-Module Boundary

EDIM — Energy Delivery Identification Module

Establishes delivery interface identities, receiving systems, consuming assets, physical boundaries, and topology.

DCCM preserves how those identities and relationships change over time.

DCAM — Delivery Capability Assessment Module

Evaluates physical delivery capability under defined operating conditions.

DCCM preserves capability assessment versions, operating restriction history, and configuration changes.

ECAM — Energy Consumption Assessment Module

Evaluates actual consumption, demand, and consumer operating states.

DCCM preserves consumption assessment revisions and changes affecting historical comparability.

DMAM — Delivery Measurement & Attribution Module

Evaluates measurement validity, energy accounting, reconciliation, and physical attribution.

DCCM preserves meter replacements, measurement configuration changes, corrected records, and attribution

revisions.

68. Cross-Architecture Boundary

Energy Generation Standard (EGS)

DCCM preserves delivery-side consequences of generation integration without replacing generation asset continuity

governance.

Energy Conversion Standard (ECS)

DCCM preserves conversion interface changes relevant to delivery and consumption assessments.

Energy Transmission & Distribution Standard (ETDS)

DCCM preserves receiving-side consequences of transport network connection changes.

Energy Storage Standard (ESS)

DCCM preserves storage integration changes affecting delivery and consumption boundaries.

Energy Measurement & Reconciliation Standard (EMRS)

DCCM provides historical measurement configuration and correction references for wider reconciliation.

Energy Flow Attribution Standard (EFAS)

DCCM provides historical physical topology and attribution method references.

Energy Claims & Disclosure Standard (ECDS)

DCCM preserves the historical evidence and assessment versions supporting energy delivery and consumption

claims.

69. Verification Framework

DCCM supports verification through explicit governance tests.

Continuity Identity Test: Is the governed physical system identifiable across changes?

Configuration Test: Are previous and resulting configurations preserved?

Change Event Test: Are material changes identifiable?

Physical Time Test: Is the effective time of each material change supported?

Evidence Time Test: Is evidence availability time preserved?

Asset Replacement Test: Are previous and replacement assets distinguishable?

Boundary Revision Test: Are physical boundary changes traceable?

Capability History Test: Are historical delivery capability assessments preserved?

Measurement History Test: Are meter replacements and configuration changes traceable?

Correction Test: Are original and corrected records distinguishable?

Historical As-Of Test: Does the assessment exclude evidence unavailable at its cutoff?

Retrospective Test: Are later reassessments distinguished from original historical assessments?

Determination History Test: Are previous governance determinations preserved?

Uncertainty Test: Are material historical uncertainties explicit?

Governance Test: Does the continuity conclusion remain within the supported evidence?

70. Non-Conformity Classification

DCCM recognizes:

Continuity Record Identity Non-Conformity

Physical System Identity Continuity Non-Conformity

Configuration Version Non-Conformity

Change Event Identification Non-Conformity

Previous Configuration Preservation Non-Conformity

Resulting Configuration Preservation Non-Conformity

Delivery Interface Change Non-Conformity

Consuming Asset Lifecycle Non-Conformity

Asset Replacement Identity Non-Conformity

Physical Boundary Revision Non-Conformity

Delivery Capability History Non-Conformity

Consumption Assessment Revision Non-Conformity

Measurement Point Continuity Non-Conformity

Meter Replacement History Non-Conformity

Measurement Correction Integrity Non-Conformity

Consumption Attribution History Non-Conformity

Physical Valid Time Non-Conformity

Evidence Availability Time Non-Conformity

Historical As-Of Evidence Leakage

Retrospective Assessment Misclassification

Governance Determination History Non-Conformity

Change Evidence Sufficiency Non-Conformity

Continuity Uncertainty Non-Conformity

Non-conformities must identify the affected physical system, change event, historical interval, applicable requirement,

and supporting evidence.

A methodological non-conformity does not automatically establish equipment failure, contractual breach, legal liability,

or regulatory violation.

71. Practical Use Case 1 — Production Line Reconnected Without

Updating Historical Consumption Attribution

Situation

An industrial facility operates three production lines.

During January, Production Line A receives electricity through Distribution Board 1.

On 1 February, the facility reconnects Production Line A to Distribution Board 2.

The asset database is updated to reflect the new connection.

However, the previous connection record is overwritten.

A later energy assessment uses the current topology to attribute January electricity consumption.

DCCM Assessment

DCCM evaluates:

January Configuration → Reconnection Event → February Configuration → Historical Measurement Mapping

The assessment identifies:

Production Line A was connected to Distribution Board 1 during January.

The connection changed on 1 February.

The current topology differs from the historical topology.

The previous connection record was not preserved.

January consumption cannot be attributed using the February configuration without additional historical

evidence.

Governance Determination

FAIL — Historical Physical Connection Configuration Was Not Preserved, Producing Unsupported

Retrospective Consumption Attribution.

Methodological Lesson

Current energy system topology cannot be used as a substitute for the physical configuration that existed

during a historical consumption period.

72. Practical Use Case 2 — Historical Meter Correction Improperly

Replaces Original Assessment

Situation

A commercial building records 400 MWh of electricity consumption for March.

An energy governance assessment is issued on 10 April using the measurement evidence available at that time.

On 20 May, a meter configuration error is discovered.

A justified correction establishes that the March consumption quantity should have been 440 MWh.

The operator updates the database and replaces the original March assessment without preserving the previous

result.

DCCM Assessment

DCCM evaluates:

Original Measurement → Original Assessment → Later Evidence → Measurement Correction → Retrospective

Reassessment

The assessment identifies:

The original assessment was based on 400 MWh.

The correction evidence became available after the original assessment.

The corrected quantity is 440 MWh.

The original assessment must remain traceable.

The revised conclusion must be identified as a retrospective reassessment.

The original and corrected evidence sets must remain distinguishable.

Governance Determination

FAIL — Original Historical Assessment Was Overwritten Instead of Preserved Alongside the Evidence-

Supported Retrospective Correction.

Methodological Lesson

Correcting historical energy data must improve the evidentiary record without erasing what was originally

known, reported, and assessed.

73. Temporal Integrity & Historical Reconstruction

DCCM requires historical governance to preserve three distinct temporal dimensions.

Physical Valid Time

When a physical configuration, connection, operating restriction, measurement relationship, or consumption condition

applied.

Evidence Availability Time

When evidence supporting the relevant physical state became available to the assessment process.

Assessment Issuance Time

When the governance determination was produced.

Historical as-of assessments must be reconstructed using the applicable physical configuration and evidence

available by the defined cutoff.

Later evidence must not be silently introduced into the original assessment.

Retrospective reassessments must preserve:

Original Assessment ID

Original Evidence Set

Original Determination

New Evidence

Reassessment ID

Revised Determination

Revision Justification

This establishes the distinction between historical operational reality and the evolution of knowledge about that reality.

74. GIE™ Compatibility

DCCM is designed for methodological compatibility with GIE™ — Governance Intelligence Engine.

Potential machine-readable governance objects include:

Continuity Record

Physical System Identity

Configuration Version

Change Event

Previous Configuration

Resulting Configuration

Physical Valid Time

Evidence Availability Time

Assessment Issuance Time

Measurement Correction

Historical As-Of Assessment

Retrospective Reassessment

Governance Determination History

Evidence Reference

Confidence Classification

A compatible implementation may support automated checks for:

Missing Configuration Versions

Unrecorded Delivery Interface Changes

Asset Identity Replacement Conflicts

Historical Boundary Misapplication

Missing Meter Replacement History

Overwritten Measurement Evidence

Unsupported Retrospective Attribution

Historical As-Of Evidence Leakage

Missing Original Governance Determinations

Untraceable Assessment Revisions

GIE-Compatible: Yes establishes architectural and methodological compatibility.

It does not establish completed production integration, validated software behavior, or external certification.

75. Canonical Boundary

DCCM — Delivery & Consumption Continuity Module governs the preservation, validation, and evidence-

supported reconstruction of physical energy delivery and consumption identities, configurations,

boundaries, measurements, assessments, and governance determinations across time.

It establishes methodological requirements for configuration versioning, change event identity, physical object

continuity, delivery interface modifications, consuming asset lifecycle, capability revisions, measurement corrections,

evidence availability, historical as-of assessment, retrospective reassessment, and governance determination

continuity.

DCCM does not independently establish original delivery identities, calculate physical delivery capability, determine

actual consumption, or validate measured energy quantities.

Those responsibilities remain assigned to EDIM, DCAM, ECAM, and DMAM.

Its principal governance output is:

Energy Delivery & Consumption Continuity Profile

76. Canonical Closing Statement

An energy system's current configuration cannot be allowed to erase the physical and evidentiary reality of

its past.

Delivery interfaces change.

Consuming assets are replaced.

Energy carriers and physical boundaries evolve.

Meters are reconfigured.

Measurements are corrected.

And governance conclusions may change when new evidence becomes available.

DCCM establishes the methodological structure required to preserve these transitions.

It connects physical system identity with configuration versions, change events, assessment impacts, measurement

history, and evidence availability.

It prevents current topology from being incorrectly applied to historical energy consumption.

It prevents corrected measurements from silently replacing original records.

And it ensures that every material governance revision remains traceable to the physical change or new evidence that

justified it.

Reliable energy governance requires more than an accurate picture of the present. It requires the ability to

reconstruct what physically existed, what evidence was available, what conclusions were reached, and why

those conclusions later changed.

DCCM establishes that continuity requirement within Energy Delivery & Consumption Standard (EDCS).