SDK
Under hösten kommer flertalet kommuner koppla upp sig till SDK med hjälp av SEFOS och detta kommer göras när DIGG öppnar upp sina godkännande processer och gör det möjligt att produktionssätta en SDK lösning.
This means that SEFOS and its partners have the highest possible competence in all parts of the SDK both at a deep technical level and at a higher architectural level.
SEFOS can deliver all the parts needed to test and put into production an SDK environment both on-prem or as a SaaS service.
Expectations for the service have been high, therefore we want to be clear about what is actually included in DIGG and Inera's technical delivery and what functionality the SDK actually has.
The SDK transports information from Organization A to Organization B.
The SDK is based on a technical framework and protocol that is E-Delivery, which has been used for a very long time in e.g. Peppol.
The SDK also contains an identity federation with associated requirements and rules to be able to ensure the identity of the sender and recipient.
The SDK's address book is provided by DIGG and you can look it up there to find your recipient.
Access point
SEFOS SDK AP
Messaging service
SEFOS
Messaging client
Teams with SEFOS Addin
SEFOS for web
An AP in the SDK is a pure e-delivery access point, usually Domibus is used, which connects the organization to the network/federation. The connection to an AP is standardized and several different applications/messaging services can connect to an AP that we provide.
As an approved access point operator, SEFOS and our partners can deliver SDK access points both as a SaaS and on-prem solution.
When SEFOS is used as a messaging service, it will be possible to send the same message to recipients who are connected to SEFOS, SDK or have no connection at all to any of the networks. SEFOS's message service identifies which network can be used and sends the message via the correct network automatically.
SEFOS works, among other things, with the help of an add-in for MS Teams, but there is also SEFOS for web, which is SEFOS's own web interface that works completely without connection to Microsoft Office.
This means that with SEFOS you will have access to two different message clients to the SDK.
Function mailboxes in SEFOS can receive both SEFOS messages and SDK messages with the option of collecting all communications in the same function mailbox.
Just as you can receive SDK messages directly in SEFOS, you can also send SDK messages from SEFOS web service or MS Teams addin.
Are you and your business interested in starting a pilot project with SEFOS as a messaging service?