...
Meridix Studio has support for multiple customers in a single system where each customer can get its own part of the system and work in isolation even though they reside in an larger system with multiple customers. This allows a companies to have one single Meridix Studio installation where all their customers reside. This is used by for example carriers (operators) that have a platform that contains can contain thousands of customers, in these cases a multi customer Meridix installation i set up. (A Meridix installation has support to scale both up and out to allow very large numbers of customers, read more about Meridix scaling possibilities here)
...
As mentioned in the previous section Meridix Studios available reports is built up by creating modules for the platforms that we want to support. To add support for reports targeting a new platform Meridix needs to create a new module were the platforms source data is handled and interpreted. Once this is done the newly created module can be hooked into the Meridix engine and all the functionality such as the many report grouping options, subscription reports and Excel exports etc will be handled by the Meridix Studio main system. Therefor we can easily add support for new releases of existing platforms and add support for new or future platforms without needing to "reinvent the wheel" each time.
This makes Meridix Studio an ideal solution for companies that sells or works with multiple platforms since once they have learned to use Meridix Studio all the knowledge can be applied even if the target platform changes.
...
Meridix has support for multiple languages (English and Swedish, at the time of writing Danish translations is being created) and can easily be translated to additional languages if required (more information about translations). Our current plan is to support all the Nordic languages within the next two year.
Branding and theming
Meridix Studio has a very extensive branding support, where the user interface can be changed per installation through our theme package model. This allows a customer to easily modify their installations user interface so that it matches their company profile. Logos, colors, fonts, icons and export appearance and much more can be customized without requiring custom binary builds of the system. This is ideal when the report system should be integrated in a portal or be sold as part of a suite of other products. Read more about or branding and theming support here.
...
Meridix can be used as a stand alone product with no integration except of for the report source data import, but it can also be connected and integrated with other systems to allow seamless logins from an existing portal portals or let another system load use the report engine through the Meridix web/http based API.
Catalog synchronization
For larger customer there are usually thousands or even tens of thousands of numbers/users/extension etc. that should be targeted when creating reports. If the user where forced to manually enter this information into Meridix it would be a daunting and error prone task that probably would get out of sync quite fast since organizations changes, new users/numbers is added and removed on a daily basis. To enable Meridix to work even for large organizations the system has full support for synchronization against external catalogs, this is the recommended way of handling the catalog in Meridix i.e. you define a synchronization against a master catalog that Meridix mirrors, then there are zero administration of keeping Meridix up to date with information/catalogs in other systems.
SSO - Single Sign On and existing portal integration support
Meridix Studio can easily be integrated into an existing portal and the login can be transparent to the end users through the single sign on support. And if with the branding and theming support the Meridix user interface can be restyled to allow users to in a way so that users do not know that they left the portal. Example: if a customer/reseller has an existing customer portal an SSO can be setup so that existing portal users can be logged in into a Meridix Studio installation branded in the same way as the portal so that the end users wont know they left the portal at all, the login is handled automatically and Meridix can be opened in a iframe or as a new window depending on the portal design. Read more about our SSO support here.
HTTP API - Custom user requirements
No system can probably handle all user every single users requirements out of the box, there will always be end users with very specific requirements therefor Meridix Studio has an very extensive HTTP based API that allow end users and customers to integrate Meridix into other products or systems through its API (Application Programming Interface). Users can then create reports, edit users, handle scheduled reports through their program language of choice. Read more about our API support here.
...