Integrations
Connects to what you already run. Doesn’t replace it.
Your ERP stays in charge of inventory and purchasing, and your plant controls keep running the line. InduBatch takes from each what the GMP batch record needs.
- PLCs
- Plant tablets
- Downtime, output and rejects
- ERP
- Microsoft Entra ID
- On-premises Active Directory
- Corporate email
- Analytical instruments
- Duplicate blocking
- Controlled printing
- Excel
- Bulk upload
- OpenAI, Gemini or Claude
- Malware scanning
- External portal
Connections
What connects, and what for.
Plant floor
- PLCs OEE
Process variables with history, linked to the batch being made, and a channel heartbeat so you know capture is alive.
- Plant tablets DMS · BR
Batch record forms are assigned to each device, which reports its signal and pending sync queue.
- Downtime, output and rejects OEE
Plant data capture feeds OEE, equipment reliability and usage-based maintenance.
Corporate systems
- ERP MT
Products, orders and batches kept in sync with your corporate system, which keeps inventory and purchasing.
- Microsoft Entra ID
Sign-in with the company account, configured per company.
- On-premises Active Directory
Authentication against your own directory servers.
- Corporate email
Delivery through your company SMTP server: signature codes and system notifications.
Laboratory
Outputs and documents
- Controlled printing DMS · BR
A local agent sends authorized copies to the printer, with watermark and numbering, without dialogs.
- PDF
Batch records, certificates of analysis, reference documents and validation reports.
- Excel
List exports with the columns each user chooses.
- Bulk upload DMS · BR
Migration of existing documents into document management.
External services
- OpenAI, Gemini or Claude DMS · BR
The writing assistant uses the provider your company chooses; the author reviews every suggestion and usage is audited.
- Malware scanning PX
Every attachment arriving through the portal is scanned with Microsoft Defender before it can be opened.
- External portal PX
Suppliers and clients sign in through a deployment separate from the internal application.
How we integrate
Rules that don’t change with integration.
A poorly built integration is the fastest way to push uncontrolled data into a validated system.
Imported data isn’t approved on its own
A result coming from an instrument enters as captured and goes through the same second-person review and signature as a typed one.
You know whether a connection is alive
The PLC channel and every device report a heartbeat. A gap in capture shows up; it isn’t filled in.
Each system owns its part
The ERP keeps inventory and purchasing; the formula that gets executed and its signed approval live in InduBatch.
Nothing listens where it shouldn’t
The print agent only serves its own machine and allowed origins, and the external portal runs apart from the internal application.
Questions
What IT and plant teams usually ask.
Which PLCs can be connected?
Plant monitoring already runs with PLCs in production. While preparing the demo we review the make, model and protocol of yours to confirm the connection.
Which ERP does it integrate with?
ERP integration is in production. We review yours with your IT team to define what gets synchronized: products, orders and batches.
Are lab instruments connected online?
They integrate through the file each instrument exports, with a configurable mapping. That keeps the original file and its hash as evidence of where every number came from.
Do we need to install anything on user machines?
Not to use the suite, which runs in the browser. Only workstations that print controlled copies need a local print agent.
Does the AI see our documents?
Only the text the author sends to the assistant, to the provider your company configured. Nothing is inserted without the author’s review, and every use is audited.
Let’s review your systems before the demo.
Tell us which PLCs, ERP and instruments you use, and we’ll prepare the demo with those connections.