In today’s article, you’ll read about integration using the AlisQI API. This has many applications and is very dynamic. Since the AlisQI data model is fully customizable, throughout this integration too, users mimic their operation by adapting the data model to match their situation. Every table and field in this data model is accessible through the API.
How easy is it to integrate your QMS with external systems or devices using the AlisQI API? We’ve invited Rien van der Voorden, Software Developer at Cosun Beet Company to talk about his experience.
The AlisQI API: a quick overview
AlisQI provides an Application Programming Interface (API) to both READ and WRITE all data in the system. This covers all master data as well as transactional (laboratory, shop floor, or quality) data. Using the API, manufacturers can create their own integrations, achieve greater efficiency, and improve their factory’s infrastructure.
The AlisQI API has many applications. We are often surprised by the integrations our customers build. Use cases of the AlisQI API include:
- Master data from ERP to AlisQI
- Manufacturing orders from ERP to AlisQI
- Batch release from AlisQI to ERP
- Specification management (from PLM to AlisQI)
- Quality Data download to ERP or data warehouse
- Instrument, sensor, or SCADA integration
SAP integration using the AlisQI API
In the short interview below, you can find out how Cosun Beet Company integrated their SAP with AlisQI. Cosun Beet Company operates six sugar beet processing plants, producing sugar and sugar specialties in The Netherlands and Germany. With some 850 employees, Cosun Beet Company is one of the most efficient sugar producers in Europe. Their ambition is to be the greenest, most innovative, and most successful sugar beet processor in the world.
Why did you decide for this integration?
Rien: We needed to upgrade our software for the labs. We were using a very old system and started looking for a system or application to replace that software. After we went through various software application programs, we found AlisQI, a cloud-based application, that not only looks nice but is easy to work with.
We have SAP as our backend system, and in SAP we have deliveries, batches, and so much useful data. When AlisQI was chosen as our QMS, it was important to create this integration and have the SAP information in AlisQI. So that’s where we came in and we made an interface from our SAP to AlisQI using the AlisQI API.
What did you expect going into this task? Did the reality match your expectation?
Rien: That first meeting helped not only to ensure that there was no confusion but also set us on the right track. Afterwards, we could make the connection with the API and the transfer information was working. We had some minor questions, and the AlisQI team was just as helpful and responsive.
To be honest, I didn’t even need the information in the documentation. I had a quick read and know that this would have functioned great in case we needed it. I would imagine that if we didn’t have the onboarding meeting and just received the link to the documentation, that would have also been enough. All the info you need is there and clear. It’s presented very straightforward.
How long did it take you to complete the task?
Rien: I’d like to point out that this question is very system dependent. Doing this in SAP, it took me about a day, maybe a bit longer. I imagine that in other systems it takes even less time. It’s all about the system you use to provide information. Still, one day is pretty fast.
Is there anything else that you would like to share (and that other developers using this should know)?
Rien: I’m happy with this integration and I think that it all worked well. I would probably mention to developers where they can find the AlisQI API documentation and say good luck. It’s enough. The documentation is good, and it did what it had to do. So, good luck.