One of the most appealing aspects is that, as a system administrator, maintenance is very easy to access and manage. For example, scripts can be implemented and applied directly, which provides a high level of flexibility. In particular, the designer tool supported by the IDE allows individuals with basic IT knowledge to learn and use it with ease for maintenance and management tasks.
Additionally, the system demonstrates a very high level of stability. Our company continues to operate in an on-premises environment and interfaces with other systems such as SAP and WMS. There have been no critical errors when integrating with legacy systems, and most LIMS-related issues can be resolved by the IT team through error log analysis without requiring support tickets. Therefore, its compatibility and integration with legacy systems are highly effective.
Finally, another advantage is the strong level of security and control. Since the system is managed in-house, sensitive data can be handled more securely, and administrators have full control over configurations, access, and updates. This makes it easier to enforce internal policies and quickly respond to any potential issues. Review collected by and hosted on G2.com.
From a total cost of ownership (TCO) perspective rather than a technical standpoint, the licensing and annual maintenance fees (AMP) are relatively expensive. Our company uses SAP, where options such as PMC (7-year) user licenses can be selected depending on the company’s situation. However, in the case of LIMS, there are only FCL and DCL options available, and the cost of upgrading from DCL to FCL was about three times higher compared to SAP.
Additionally, I believe the AMP should be adjusted based on the actual level of effort required, as it tends to increase every year. Review collected by and hosted on G2.com.