The disadvantages of Infor CloudSuite are related to Absence Management. There are too many setups for users to establish absence plans, formulas, and calculations. It is not straightforward and is too deeply embedded. It is very easy in Lawson itself, but in Infor CloudSuite, it is more complicated for users. On the benefit side, there is no auto-enrollment for Absence Management. When there is a new employee, they are not auto-enrolled. You need to enroll them every time. If you want to change an employee to a different benefit plan, you need to do it manually. It does not work according to the eligibility group. It will just give you the details, requiring manual enrollment. For the next release to make Infor CloudSuite better, I would want to see improvements in Absence Management and auto-enrollment.
In Germany, there aren't enough IT specialists for customization and software development, causing projects to take too long. This lack of resources is a significant issue in the customization process. Improvement is needed in resources for customizing the solution.
Infor has brought a new approach called the sixty, thirty, and ten approaches. This approach is called the Infor Deployment Method, which involves interacting with the customers to gather the requirements. In the first stage, we will categorize the requirements into categories, which are sixty, thirty, and ten. Sixty is the core application where no tweaking is required, so those are standard solutions. Whatever customers tell our company as a requirement, we will analyze whether this is a standard solution or a box solution or whether customization or modifications are needed, and based on that, we can categorize it. So, the majority of the customers' business processes will fall under the sixty category, meaning it doesn't need any tweaking or modifications as it can remain as a standalone vanilla tool. Slight configurations are needed when it comes to the thirty category. Some data changes, some process tweaking, some label changes, and a little bit of configuration to suit the customer requirements will be categorized into thirty categories. Whereas ten, there is another leftover ten out of one hundred percent, sixty is standard, thirty is configuration-related, and ten is unique since we have to develop and enhance according to the customer's business. We will categorize requirements and analyze the ten percent category. Addressing the ten percent requirement will be challenging because we need to customize it. Customization has been easy in ERP because Infor has introduced a new module called extensibility, where we can enhance the solution by customization without touching the core solution. The time taken to address the ten percent requirement will be challenging in terms of understanding the requirement, mapping the requirement, testing, and deployment because those are unique to each customer. Rest ninety percent, we don't have any challenges with the tool. For the quality department, there is a module called quality, and I feel it has to be a little bit simplified. Implementation-wise, there are no challenges in the tool. When we implement the quality modules, for the end user who does the installation, the tool has to be more simplified. For example, if you inspect the product dimension, let's say the dimension is from one centimeter to ten centimeters, and if there is a criterion that the product should fall under five centimeters and seven centimeters, then it is shown. The range between five and seven cannot be given here, so the quality model should be simplified by providing the ranging facility.
There is room for improvement in the pricing. For us, it's the pricing aspect. Since we're South African, it's difficult when it's a dollar-based product.
Infor CloudSuite is a comprehensive suite of cloud-based ERP software designed to streamline various business processes. It offers core functionalities such as financial management, supply chain management, production management, and CRM. The suite is tailored to specific industries, including manufacturing, food and beverage, healthcare, automotive, and distribution, each featuring industry-specific solutions. Being cloud-based, Infor CloudSuite provides scalability, automatic updates, and...
Understanding more about how Birst can actually be a profitable aspect of being implemented into Infor CloudSuite is important.
The disadvantages of Infor CloudSuite are related to Absence Management. There are too many setups for users to establish absence plans, formulas, and calculations. It is not straightforward and is too deeply embedded. It is very easy in Lawson itself, but in Infor CloudSuite, it is more complicated for users. On the benefit side, there is no auto-enrollment for Absence Management. When there is a new employee, they are not auto-enrolled. You need to enroll them every time. If you want to change an employee to a different benefit plan, you need to do it manually. It does not work according to the eligibility group. It will just give you the details, requiring manual enrollment. For the next release to make Infor CloudSuite better, I would want to see improvements in Absence Management and auto-enrollment.
In Germany, there aren't enough IT specialists for customization and software development, causing projects to take too long. This lack of resources is a significant issue in the customization process. Improvement is needed in resources for customizing the solution.
The price of the solution is not good. In Europe, it's difficult to find people who already know Infor, which was a problem during implementation.
Infor has brought a new approach called the sixty, thirty, and ten approaches. This approach is called the Infor Deployment Method, which involves interacting with the customers to gather the requirements. In the first stage, we will categorize the requirements into categories, which are sixty, thirty, and ten. Sixty is the core application where no tweaking is required, so those are standard solutions. Whatever customers tell our company as a requirement, we will analyze whether this is a standard solution or a box solution or whether customization or modifications are needed, and based on that, we can categorize it. So, the majority of the customers' business processes will fall under the sixty category, meaning it doesn't need any tweaking or modifications as it can remain as a standalone vanilla tool. Slight configurations are needed when it comes to the thirty category. Some data changes, some process tweaking, some label changes, and a little bit of configuration to suit the customer requirements will be categorized into thirty categories. Whereas ten, there is another leftover ten out of one hundred percent, sixty is standard, thirty is configuration-related, and ten is unique since we have to develop and enhance according to the customer's business. We will categorize requirements and analyze the ten percent category. Addressing the ten percent requirement will be challenging because we need to customize it. Customization has been easy in ERP because Infor has introduced a new module called extensibility, where we can enhance the solution by customization without touching the core solution. The time taken to address the ten percent requirement will be challenging in terms of understanding the requirement, mapping the requirement, testing, and deployment because those are unique to each customer. Rest ninety percent, we don't have any challenges with the tool. For the quality department, there is a module called quality, and I feel it has to be a little bit simplified. Implementation-wise, there are no challenges in the tool. When we implement the quality modules, for the end user who does the installation, the tool has to be more simplified. For example, if you inspect the product dimension, let's say the dimension is from one centimeter to ten centimeters, and if there is a criterion that the product should fall under five centimeters and seven centimeters, then it is shown. The range between five and seven cannot be given here, so the quality model should be simplified by providing the ranging facility.
There is room for improvement in the pricing. For us, it's the pricing aspect. Since we're South African, it's difficult when it's a dollar-based product.
They could include marketing automation for the product.