What is HANDSAL?
HANDSALTvimenning’s EDI server for bilateral message exchange: receives, translates, routes and acknowledges messages between companies and marketplaces. is Tvimenning's EDIFACTElectronic Data Interchange For Administration, Commerce and Transport - UN standard for electronic data exchange. server for bilateral message exchangeMessages travel directly between two parties, without passing through a shared hub. The opposite of the centralised model Elhub is built on. Also called point-to-point.. In markets without a central hub, market messages still travel from party to party, in EDIFACT. That is not a transitional arrangement, it is how the market works, and anyone operating there has to handle it from day one. In Sweden the format is called EdielNordic profile of the EDI EDIFACT standard - used for electronic message exchange in the Nordic power market via Elhub.. That makes HANDSAL the transport layer beneath SEFTAValidation, estimation, and editing with versioned time series, traceability, and export-ready data.. SEFTATvimenning’s VEE engine: validates, estimates and edits metering series with versioned time series and a full audit trail, before data goes to Elhub. is our metering data handling, built for more than one market - but in an EDIFACT market the messages have to be carried by something, and that is the job HANDSAL does. The dependency runs one way: without a transport layer, the multi-country part of SEFTA does not work outside Norway. SEFTA has been run against synthetic, realistic data - not put into operation. For anyone who wants to influence the direction, now is when that is possible.
Key features
We tell you when something did not arrive
Most EDIElectronic Data Interchange - standardised electronic exchange of business documents between systems. tools tell you what arrived. The expectation module lets you define when a message is due, and raises an alert when it fails to appear - across three levels, from a notice on the dashboard to escalation to the on-call group. The same idea appears in SEFTA's rule engine, as heartbeat. That is a design principle here, not a coincidence.
Nine message types in bilateral exchange
MSCONSEDIFACT message format for exchange of metering data in the electricity market - used in Elhub to transmit hourly, daily and monthly values between market participants., UTILTSThe six characters in UTILMD, INVOIC and CONTRL are not abbreviations someone invented locally. Each message type is its own standard in the UN EDIFACT directory, and the name is a six-character mnemonic., UTILMD, INVOIC, PRODAT, DELFOR, REQDOC, CONTRL and APERAK. The acknowledgements are included because they are half the work.
Quarantine instead of silence
Messages from unknown senders, or with syntax errors, are placed in quarantine with an interface where an operator can approve, reject or inspect the raw data. Together with the partner register and the address register, this is built by people who have operated EDI, not merely integrated it.
Complements SAMTYGD - no overlap
SAMTYGDA shared integration layer to the modules, the surrounding systems and market hubs such as Elhub. handles regulated market messages toward central hubs such as ElhubNational hub for metering data and market processes in the Norwegian electricity market.. HANDSAL handles bilateral EDIFACT directly between market parties. Together they cover the whole communication picture.
The part that is not EDI, but always comes along
The scheduler fetches prices, invoices and files from external sources on a fixed schedule, over HTTP, FTP, SFTPThree different file transfer protocols that are often confused. FTPS is FTP with security added; SFTP is something else entirely that inherited the name. or email. It is rarely what sells a system, and often what decides whether anyone actually escapes manual work.
Results you can expect
- ✓One infrastructure layer for multiple protocols
- ✓Faster access to new markets
- ✓An alert when a message fails to arrive, not just a receipt for what did
- ✓Messages that fail stop in quarantine, not in silence
- ✓Prices and invoices fetched on schedule, not by hand
Get started quickly
HANDSAL is built for rapid implementation. Typical setup takes weeks, not months.
- Dedicated implementation support
- Integration with existing systems
- Training for your team
- Ongoing support after go-live
How HANDSAL can be run
Self-hosted on your side
On your own server, with data in your own infrastructure. Full control, no traffic through an outside party.
A VM we operate
We install and operate it; you still own the data. A middle path for those who want control without the operational burden.
Fully managed cloud service
Operated by us. Data sits with Tvimenning, never with an external message broker that sees the traffic.
Ready to see HANDSAL in action?
Book a demo and we will show you how HANDSAL can solve your specific challenges.