An agreed flow of events between the actors in the power market, such as a supplier switch or a move-in and move-out, with defined messages, deadlines and failure cases.
Definition
A market process is not a system but a choreography. It describes which actors send what to whom, in which order, within which deadlines, and what happens when something is rejected. In the Norwegian model the processes are defined in ElhubNational hub for metering data and market processes in the Norwegian electricity market.'s BRSElhub’s process specifications. Each BRS describes one market process step by step - who sends what, when, and what happens when something fails. documents, and they are the same for everyone: a supplier switchProcess where an electricity customer changes their power supplier - handled through standardised messages via Elhub. must look identical whether it comes from a grid companyCompany that owns and operates electricity grids and is responsible for power supply to end users. with a hundred thousand metering points or from a new entrant with a few hundred.
That is what makes the processes the real integration requirement. A system can speak the correct protocol and still be useless, because it handles the happy path and not the rejections. Most production failures live in the branches: a deadline that expires, a message arriving out of order, an acknowledgement that never came.
The market processes are the reason a test rig exists. An integration seeking approval has to show that it behaves correctly through the whole process, not merely that it can get a message through. STUBB simulates the counterparty so the processes can be run with both normal flows and failure cases before anything goes into production, and SAMTYGD is built to handle them in operation. When we say a product is verified against simulated market interfaces, it is the market processes that have been verified.
In practice
The market processes are the reason a test rigA setup that simulates the counterparty in an integration, so that behaviour can be exercised, failure cases included, before anything goes into production. exists. An integration seeking approval has to show that it behaves correctly through the whole process, not merely that it can get a message through. STUBBTvimenning's simulator platform for integration testing - we build mock environments of the counterparties your systems talk to, so they can be tested without touching production. simulates the counterparty so the processes can be run with both normal flows and failure cases before anything goes into production, and SAMTYGDTvimenning platform for Elhub integration - handles all message types and processes to Elhub. is built to handle them in operation. When we say a product is verified against simulated market interfaces, it is the market processes that have been verified.
