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.
