Skip to main content

Elhub Business Information Model (BIM) and Elhub Messaging Interface (EMIF)

Here are the changes related to Elhub Business Information Model (BIM) and Elhub Messaging Interface (EMIF) that will be added with the 15 minute project.

The current version can be found here under "Edielstandard". The new version of BIM and EMIF that will be implemented with the 15-minute project accordingly.


Change log for EMIF Files v2.3

Elhub EMIF WSDL 2.3.zip

  • Bumped version from 2.2 to 2.3

  • Made changes to BIM related to 15 minute resolution in imbalance settlement (see table below for details)

  • Made changes related to technical dept:

    • Changes to boolean elements

      • Type for all boolean elements are changed from xsd:boolean to Elhub_boolean restricting legal values to true and false only. Standard is that 0 and 1 are legal values for boolean in addition to true and false. This restriction has been in place from before but the BIM was never updated. Elements with changed type:

        • ExtendedStorageMeteringValues

        • BlockedForSwitching

        • RequestPositiveAcknowledgement

        • Withdrawn

    • Restriction on dateTime elements  

      • New type: Elhub_dateTime9DecType. Used by the following elements:

        • RegistrationDateTime

        • Creation

        • SnapShotOccurrence

        • InsertDateTime

      • Changed pattern for Elhub_dateTimeType from ".+T.+(Z|[+-].+)" to "[1-9][0-9]{3}-.+T[^.]+(|\.[0-9]{0,3})(Z|[+\-].+)". Used by the following elements:

        • StartOfOccurrence

        • EndOfOccurrence

        • MeterReadingStartDate

        • Start

        • End

        • ReconciliationDate

        • LastMeterReadingDate

        • DeliveryObligationDate

    • Restriction on Metering Point ID

      • Changed from restriction on length only (18 characters) to that all characters must be numeric. Pattern used: "[0-9]{18}"

    • Changes to sorting

      • Alphabetic sorting of XSD elements is done in following order:

        • simpleType elements sorted alfabetically

        • complexType elements sorted alfabetically

      • v2.2 with alphabetic sorting are included in the EMIF files package for easier comparison

  • Updated example XMLs, bindings and SOAP UI files to take into consideration the 2.3 changes to the BIM

Changes to BIM related to 15 minute resolution in imbalance settlement


Change

File / Type

Type / Format

Contained i message(s)

Comment

1

New enumeration:
MeterReadingOccurrenceType

common/Elhub_BusinessDataType.xsd

enum values:
PT5M, PT15M, PT60M, PT1H



2

Add 5 minute resolution to DurationCodeType

common/Elhub_BusinessDataType.xsd,
enumeration: DurationCodeType 

New enum value: PT5M (will not be used a this point)

CollectedData
PriceVolumeCombinationForReconciliation
NotifyValidatedDataForBillingEnergy


3

Add 5 minute resolution to ChannelResolutionType

common/Elhub_BusinessDataType.xsd,
enumeration: ChannelResolutionType

New enum value: PT5M (will not be used a this point)

NotifyStartOfSupply
NotifyMeteringPointCharacteristics
RequestUpdateMasterDataMeteringPoint


4

Add new product codes

common/Elhub_BusinessDataType.xsd,

enumeration: Elhub_ProductIdentifierCode

New enum values:

  • 4700000000301

  • 4700000000302

  • 4700000000303

  • 4700000000101

  • 4700000000201

CollectedData
NotifyStartOfSupply
NotifyMeteringPointCharacteristics
RequestUpdateMasterDataMeteringPoint
PriceVolumeCombinationForReconciliation
NotifyValidatedDataForBillingEnergy

89 (Elhub) is added as valid schemeAgencyIdentifer
for this element since the new enum values are Elhub specific. 

5

Add new business types

common/Elhub_BusinessDataType.xsd,

enumeration: BusinessTypeCode

New enum values: 

  • LS03

  • LS04

  • LS05

  • LS06

  • LS07

  • LS08

  • RE03

  • RE04

  • RE05

  • SE25

  • SE26

  • SE27

  • SE28

  • SE29

  • SE30

  • SE31

NotifyValidatedDataForBillingEnergy
RequestDataFromElhub 
PriceVolumeCombinationForReconciliation


6

New element: MeterReadingOccurrence
after BlockedForSwitching

common/ Elhub_ AggregatedBusinessInformationEntities.xsd

Type: Elhub_DetailMeteringPointCharacteristicType

Type: MeterReadingOccurrenceType

Cardinality: 0..1

NotifyStartOfSupply
NotifyMeteringPointCharacteristics
RequestUpdateMasterDataMeteringPoint
ResponseUpfrontMeteringPointCharacteristics


7

New element: ExcludeFromSettlement
after Resolution

common/ Elhub_ AggregatedBusinessInformationEntities.xsd
Type: Elhub_MeasurementDefinitionType

Type: Elhub_boolean
Cardinality: 0..1

NotifyStartOfSupply
NotifyMeteringPointCharacteristics
RequestUpdateMasterDataMeteringPoint


8

Replace  element : SettlementMethodType
with element: BusinessType

common/ Elhub_ AggregatedBusinessInformationEntities.xsd
Type: Elhub_ReconciliationMeteringPointCharacteristicType

Type: Elhub_BusinessTypeType
Cardinality: 1..1

PriceVolumeCombinationForReconciliation



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.