---
title: "SEMDA-3 Goals and differences to V2"
slug: "semda-3-goals-and-differences-to-v2"
updated: 2025-03-27T07:04:39Z
published: 2025-03-27T07:04:39Z
canonical: "docs.rotary-polaris.ch/semda-3-goals-and-differences-to-v2"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rotary-polaris.ch/llms.txt
> Use this file to discover all available pages before exploring further.

# SEMDA-3 Goals and differences to V2

## SEMDA-3 Version goals

1. Provide API suitable for interactive and non-interactive applications
2. Allow immediate display of validation errors to the user.
3. Increase data quality in RI
4. Reduce support effort in the clubs, in SEMDA and in RI
5. Dissolve the dependency of local CMS on the RI availability and performance
6. Decouple the dependency of Local CMS on the RI-API structures
7. Hide future changes of RI-API
8. Provide advanced consolidated functions not available in RI-API
9. Provide scalable message-based API serving multiple local CMS
10. Simplify operations and reduce operations costs of SEMDA and of the Local CMS
11. Enforce technological renewal of the product

## Major differences to SEMDA-2

- No exchange of XML files containing all data. **API only.**
- Data changes applied to RI in near time.
- No daily batch processing
- No emails sent by SEMDA to clubs informing them about errors.
- No SEMDA error reports
- No intermediate database in SEMDA. RI requests are securely queued.
- No SEMDA GUI
- SEMDA Infrastructure located and operated in Switzerland instead of Sweden
- Different implementation language and tools
- Different operations & support organization (Cloudtec & Polaris team)
- The local CMS vendor must have a valid contract with RCS in order to use SEMDA.

Application Programming Interface, a set of protocols and tools for building software applications, allowing different systems to communicate.

Rotary Communication Services Switzerland-Liechtenstein