- Elhub gateway
- Direct, system-approved integration with Elhub in five of nine market roles - DDE, AG, DDM, SLR and MDR - with all 71 message types in those roles covered and tested, and DDE and AG in production.
- Message routing
- Intelligent routing and formatting of messages based on type, recipient, and Elhub specifications - automated, with no manual follow-up.
- Format handling
- Automatic conversion between internal and BRS-compliant message formats. The right protocol - always.
- Delivery tracking
- Full traceability for all sent and received messages with acknowledgements, error handling, and audit log.
- The glue between the modules
- SPIRA, SEFTA and RUNA do not read each other's databases. They talk to one another over unpublished APIs through SAMTYGD, and customers reach them over published APIs the same way. That is why one module can be replaced without the others noticing.
- Connectors to the surrounding systems
- The connectors to Elhub, Nord Pool and the Norwegian Mapping Authority are in production. Volue Elsmart and Link Mobility are under development. Towards the NIS systems, RUNA has a tested receiving API for network data, but for incoming messages only, and it has not been verified against Volue Netbas, openNIS or Trimble. The connector in SAMTYGD has not been started. If you need one of them first, the order can be influenced, at this stage customer needs drive the prioritisation.
- End-user consent
- A solar operator who needs to see a customer's consumption today needs an agreement, an integration and a project. Elhub has solved the trust part itself: the end user signs in with BankID at Elhub, picks which metering points the operator may see, and grants access there - no power-of-attorney forms, and no access routed through the operator's own system. We are building this flow into SAMTYGD. The aim is that the entry ticket should be a GLN number and a return URL whitelisted at Elhub, and that the rest is the end user's own choices: how much is shared, which metering points, and for how long - consent is time-bounded from day one, with three years as the default. The flow runs on the third-party role (AG), one of the five roles we hold system approval in. The functionality is under development, not in operation.
- Stop asking
- Most integrations with Elhub end up with a system that asks: has anything new arrived? Has anything arrived now? Each query costs nothing on its own, but it has to be written, operated and monitored, and it sits between the metering value and whoever needs it. We turn it around. SAMTYGD fetches from Elhub, and what is being developed now passes the values on to your system the moment they are fetched. You no longer ask, you receive. The functionality is under development, not in operation.
- Messages you can read
- Our customer deals with SAMTYGD, not with Elhub. So we do not pass the messages on as they arrive: the code values are translated into readable text, and what is not needed is stripped out. What remains is a Tvimenning standard with the same content - without anyone having to look up what a code means in order to understand what happened.
