SEMDA-3 goals and differences to V2

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 version 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.