SEMDA 3.0
In previous years, numerous local club management systems (Local CMS) have been created for Rotary clubs. The administration of membership and club information is consistently a crucial component of such systems. Nevertheless, all Rotary entities are affiliated with the global organization Rotary International (RI), making RI's IT framework the primary source and authority for all club and member information. Clubs are required to either handle their membership information within the RI system (MyRotary) or ensure that the data is synchronized between the local CMS and RI to maintain the accuracy of both systems.
The task of keeping data updated in two separate locations manually is quite labor-intensive. This process also leads to numerous mistakes. Consequently, an automated synchronization tool known as SEMDA was created and launched in Sweden a few years back. Currently, SEMDA 2.0 utilizes the RI interface (RI API) to facilitate data synchronization among various local CMS and the RI system.
The need for innovative features and technological advancements necessitates a fresh approach to software development. SEMDA 3.0 is an entirely new offering that has been created from the ground up. On September 1, 2023, RCS assumed control of the SEMDA product and its branding.
The objectives of SEMDA 3.0 and the distinctions from the existing version are outlined here.
TIMELINE
The transition to SEMDA 3.0 is scheduled for the middle of 2025.
You can access more comprehensive technical details here.
Flexible recipient lists facilitate communication
The existing recipient groups only partially achieve the intended goal. In practice, more adaptable combinations of recipients (members) are necessary for disseminating information.
For this purpose, more adaptable recipient lists are set to be developed in the future (scheduled for Q2 2025). These lists can be generated by inputting different filter criteria and utilized immediately for dispatching newsletters or emails. If you wish to reuse this list at a later time, it can be stored as a static recipient group.
The existing predefined dynamic or static recipient groups will remain unchanged (there is a plan to slightly decrease the number of predefined recipient groups) and can be utilized when generating the necessary recipient lists. When dynamic lists are included, they are transformed into a static list.
Events: Registration option for “invited persons” only
Already implemented – see March 2025 - R1.4.07
There is frequently a requirement to facilitate event registration exclusively for a specific group of attendees. This feature is expected to be implemented in Q2 2025.
The selected participants are included in the event, and the event is designated with an appropriate registration option. In the future, adaptable distribution lists will also be accessible for choosing the preferred participants.
