Protocols & Standards⏱ ~1 minNO

BRS

BRS Business Requirement Specification BRS-NO Elhub BRS Prosesspesifikasjon Forretningsprosess Elhub

Elhub’s process specifications. Each BRS describes one market process step by step - who sends what, when, and what happens when something fails.

Definition

BRS stands for Business Requirement Specification. These are Elhub’s normative documents for how the market processes in the Norwegian electricity market are to be carried out. Each process has its own numbered BRS - supplier switch, move-in, start of supply, submission of metering values, and so on. The document describes the parties, the order of the messages, which fields are mandatory, which deadlines apply, and how exceptions are handled. The BRS documents are what let two systems from different vendors interoperate without agreeing anything bilaterally: both implement the same specification. They are revised regularly, and a change to a BRS usually means participants have to retest before it goes into production.

In practice

In practice the BRS documents are the arbiter when something goes wrong between two participants: is the deviation a breach of the specification, or a reading both could have made? That makes BRS coverage a concrete measure of how far an integration has come - “all 71 message types in the approved roles covered” says more than “we are integrated with Elhub”. When a BRS is revised it is usually the testing, not the code, that takes the time. That is exactly what STUBB is built for: running the processes against a simulated Elhub before they reach production.

Suggest a correction

BRS

Definition

In practice

See also:

You might also like