Maintenance logs are kept in SharePoint or Excel, and Teltonika and PLC counters track operating hours, but nobody reads them until a machine stops. The solution reads the logs, failure records, counter data and manufacturer intervals, builds a list of upcoming work, reminds the people responsible in Teams and flags repeated failures, while the maintenance manager plans the work.
Built for ISO 27001NIS2 DORA
The maintenance department in a manufacturing company has several data sources: an Excel or SharePoint log of completed work or an Odoo maintenance module, the mechanics' failure records in the shift log, intervals given in manufacturer manuals and operating hour counters that live in Teltonika telematics for forklifts or in PLC controllers for the lines. When to change the oil on a press, when to check the compressor belts, when to do the annual inspection is known by the maintenance manager from memory or from a sheet they keep themselves. When they are on holiday, intervals get skipped. It is even harder to notice that the same machine had five similar failures in three months, each one fixed but never investigated, until the line finally stopped.
We connect Claude through the API to your maintenance logs in SharePoint or Excel or to the Odoo maintenance module, to operating hour data from a Teltonika or PLC export, and to Teams. Every week the model reads the new maintenance and failure records, compares them with manufacturer intervals, the actual operating hours from the counters and the rules you set, and builds a list of upcoming work: what, on which machine, by when, and from which source the interval was taken. The responsible mechanics receive reminders in Teams or by e-mail with a link to the record. In parallel, the model analyses failure descriptions and flags repeated failures of the same machine or component, even when they are described in different words, and puts them into one note for the mechanic with the history of the records. The maintenance manager sees the list and the notes, plans the work themselves against the production schedule in Business Central or your planning system, changes priorities and approves, while the solution assigns nothing and never creates work orders in Odoo or the log on its own. The model runs on the Anthropic API or Amazon Bedrock in an EU region without training on your data, and all reminders and notes are kept in a log.
Four steps from input to a record in your system, with human approval wherever there is risk.
Every week the flow picks up new records from SharePoint or Excel maintenance logs or the Odoo maintenance module, failure records from the shifts and operating hour counters from a Teltonika or PLC export. Manufacturer intervals and your rules are kept in one SharePoint table for each machine.
Claude compares completed work with the intervals and with the actual operating hours from Teltonika or the PLC and builds a list of upcoming work with a deadline and a source. Machines whose interval has already been missed are flagged first.
The people responsible receive reminders in Teams or by e-mail with a link to the log entry. The maintenance manager reviews the list, aligns it with the production schedule in Business Central or the planning system and approves the work plan. Work orders reach Odoo or the log only after that approval.
The model flags failures of the same machine or component described in different words and puts them together with the history and counter readings. Every month we review the rules and intervals when new equipment or Teltonika devices appear.
Reading maintenance and failure records from SharePoint, Excel logs with an agreed structure or the Odoo maintenance module, and operating hours from a Teltonika or PLC export through an API or files.
The manufacturer intervals for each machine, your rules, the counter source and the responsible people in one SharePoint table, maintained by the maintenance department.
A weekly list of upcoming work for the manager, reminders to the responsible people in Teams and notes on repeated failures with the counter history.
The history of all reminders, notes and approvals, and our support when equipment, the Teltonika or PLC export, Odoo or the responsible people change.
Claude through the API + maintenance logs in SharePoint or Excel or the Odoo maintenance module, operating hours from a Teltonika or PLC export, reminders in Teams. We connect through an API, a scheduled file export or an e-mail flow, depending on your equipment and version. See the service page for details and limits.
We take operating hour data from a Teltonika platform report export or its API, and from PLCs through an export from your SCADA or data acquisition system, depending on the equipment. The solution is not connected directly to the equipment or controllers, it only reads summary readings. We choose the integration method after a check, and we do not claim an official partnership with these vendors.
Yes. We start with an Excel or SharePoint log with an agreed structure, and mechanics photograph paper records into a designated folder, from where they are recognised. Many customers later move to the Odoo maintenance module or another CMMS with their data already in order.
No. The solution only reads, analyses and reminds. Work orders in Odoo or the log are created and approved by the maintenance manager, and the solution is not connected to PLCs or equipment control systems, it only reads exported counter data.
Nonconformance reports arrive from Microsoft Forms, shift logs and e-mails, and the quality manager retypes them into Excel to see trends.
Customer orders arrive in Outlook as e-mails, PDFs and Excel attachments in different formats, and a sales rep retypes each one into Business…
An operator looks for the process sheet in a SharePoint folder by the machine, or asks the foreman, who gives the same answer for the tenth time…
Every material shipment arrives with an invoice, a delivery note and a declaration of conformity, the purchase order sits in Business Central, SAP…
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
AI systems are deployed with protection against data leakage and model abuse.
The AI security programme and its controls are managed following the ISACA methodology.
AI risks are identified and managed like any other IT risk.
We reply within 1 business day
