Every Answer Shows Its Source
Talk to Machine answers questions in English and Turkish. Each answer gives the number of the instruction or fault record it is based on, so the user can open the original document and check it.
Thursday, November 26 | 9th Pargesoft Summit | Frontier Transformation Thursday, November 26 | 9th Pargesoft Summit | The Marmara Hotel, Taksim Nov 26 | 9th Pargesoft Summit
RegisterCopilot & AI Solutions
Power Platform & Azure
CRM
AI Products
Industry-Specific Products
AI Products
When a machine fails, the information your team needs is often spread across files or held only by experienced staff. At Pargesoft, we bring it together in the Talk to Machine AI assistant. Your team asks in Teams, and the answer comes with the instruction or record number it is based on.
Got a low oil pressure fault on the HP-34 hydraulic press. Has this happened before?
Yes. The same fault was recorded on 14 March 2025 (fault record 400731926): the oil level in the hydraulic unit was low and oil was added. For the steps, see instruction MT-620 and check that it is the latest version.
Use cases
Talk to Machine is used by roles from maintenance technicians to managers, and from health and safety teams to new starters, and each role comes with different questions. Choose a role below to see a sample conversation. The examples are based on use in a pilot installation; machine names, record numbers and figures have been changed.
Who asks A maintenance technician at the HP-34 hydraulic press on Press Line B, looking at a fault on the screen
Got a low oil pressure fault on HP-34. Has this happened before?
Yes, there is a similar record. Fault record 400731926, dated 14 March 2025: the oil level in the hydraulic unit was low and oil was added. The fault lasted 85 minutes and production did not stop. The same machine has 9 more oil top-up records in the last two years.
Which steps do I follow to add oil?
According to the “Adding hydraulic oil” section of instruction MT-620:
Check that this instruction is the latest version.
The door safety switch looks faulty too. Can I bypass it and keep working?
No. Safety devices must not be bypassed. If the switch is faulty, do not run the press; report it to the shift supervisor and the authorised maintenance team. For checking the switch, see the safety section of instruction MT-620.
Result In one conversation the technician sees what was done last time, the steps to follow and the safety boundary. Every piece of information rests on a fault record or an instruction number.
Who asks An operator about to start the hydraulic press at the beginning of a shift
How do I start up the hydraulic press?
There are two hydraulic presses on Press Line B: HP-23 and HP-34. Which one do you mean?
HP-34.
Start-up instruction MT-620 applies to HP-34. In short:
All values are written in the instruction. Check that it is the latest version.
There is a yellow light on the panel. What does it mean?
According to MT-620, the yellow light means the hydraulic oil temperature is above its working range. Do not run the press, and tell the maintenance team. The instruction gives no other step for the operator in this case.
Result The operator reaches the approved instruction for the right machine. When the instruction does not cover a situation, the assistant sends them to the maintenance team.
Who asks A maintenance engineer reviewing the maintenance plan for the press line
Which part group has the most records on HP-34 over the last two years?
HP-34 has 41 fault and maintenance records in the last two years. By part group:
How many of the hydraulic unit records are about adding oil?
Oil was added in 10 of the 17 records. The last three oil top-ups are about 7 weeks apart on average. The records do not name a leak point.
Does the planned maintenance for HP-34 include a hydraulic hose check?
According to the planned-maintenance list, the 6-monthly maintenance of HP-34 includes a visual check of the hydraulic hoses but no pressure test. The last 6-monthly maintenance was done on 12 June 2025.
Result The repeated need for oil and the gap in planned maintenance show up in the same conversation. The engineer gets a starting point, based on the records, for dealing with the issue before it becomes a breakdown.
Who asks A maintenance and production manager preparing for the weekly meeting
Which machines on Press Line B had the most records in 2025?
In 2025, the most records on Press Line B were on these machines:
A record count alone does not show how often a machine breaks down; planned maintenance records are included in these numbers too.
How long did production stop in the HP-34 records?
Production stopped in 5 of the 14 records in 2025, for 6 hours 40 minutes in total. The longest stop was 2 hours 10 minutes, caused by a die clamping fault.
Result The manager gets the summary for the meeting with a few questions. Because it rests on the same records the shop floor uses, the figures come from the same source.
Who asks An HSE specialist who has spotted a hydraulic oil leak on the shop floor
There is a hydraulic oil leak under HP-34. What should we do?
First, follow the emergency instruction:
For dealing with the leak itself, see the “Leaks and seepage” section of instruction MT-620. Check that it is the latest version.
Which daily maintenance instruction applies to this machine, and which version is the latest?
The daily maintenance instruction for HP-34 is GK-MT-086. The latest version in the document list is version 3. Check that the printed copy on the shop floor is this version.
Result In an emergency, the right instruction comes first. Quality also sees which instruction applies, together with its version.
Who asks A new operator learning the daily checks on HP-34 in their first week
What do I check in the daily maintenance of HP-34?
According to daily maintenance instruction GK-MT-086, check these at the start of the shift:
The result of each check goes on the daily check form.
If the oil level is low, can I add oil myself?
No. According to the instruction, adding oil is a job for a maintenance technician. Note it on the daily check form and tell the maintenance team.
Result The new starter reaches the instruction on their own and learns which jobs are theirs and which belong to the maintenance team, without looking for an experienced colleague for every question.
Access to knowledge
In most plants the maintenance knowledge already exists: in instruction binders, in fault records kept in maintenance software such as SAP PM, and with experienced staff. The hard part is reaching it in time when a machine fails, because finding the right record or instruction means searching several sources one by one. At Pargesoft, we connect your instructions and fault records to Talk to Machine, so your team reaches what it needs from Teams, together with its source.
| Question | Today | With Talk to Machine |
|---|---|---|
| Has this fault happened before? | Someone searches the maintenance software record by record | The past record comes back in seconds, with its fault record number |
| Which instruction is valid? | Which version is current is tracked in folders | The answer gives the instruction number and a reminder to check the latest version |
| Which machine do we mean? | Machines with similar names get mixed up | The right machine is found by its machine code and production line |
| How is the job done? | Ask an experienced colleague | Only the steps in the approved instruction. If there is none, the user is sent to the authorised maintenance team |
| How do new starters learn? | Knowledge stays with a few people | Answers with a clear source, available on every shift |

AI Maintenance Assistant
Talk to Machine is an AI assistant that answers your maintenance team's questions about machines in a chat. It brings machine instructions, past fault and maintenance records and planned-maintenance lists together in one place, so instead of searching folders, people type their question into Teams. We build the assistant with Microsoft's Copilot Studio, install it in your company's own Microsoft 365 account and connect it to your instructions and fault records.
Talk to Machine answers questions in English and Turkish. Each answer gives the number of the instruction or fault record it is based on, so the user can open the original document and check it.
Users who are not sure what to ask can start from ready-made questions: past faults, daily maintenance checks, machine start-up steps and planned-maintenance summaries. The assistant remembers the conversation, so follow-up questions need no repeating.
For risky work such as electrical, hydraulic, compressed air, press and robot jobs, we write the safety rules with you during setup. On that work the assistant gives only the steps in the approved instruction and does not describe anything the instruction does not contain.
It works inside Microsoft Teams and Microsoft 365 Copilot, which your team already uses, and can be used on a computer, tablet or phone. There is nothing extra to install.
Under the hood
A user types a question into Teams or Microsoft 365 Copilot. Talk to Machine checks it against the safety rules we set with you during setup and builds the answer only from sources that belong to your company: machine instructions, past fault and maintenance records, and the planned-maintenance list. It does not search the internet and does not answer from general knowledge outside those sources.

We set the assistant up so that each user works with their own company account. A document someone cannot normally open stays out of their reach through the assistant too.
The assistant does not search the internet. If your company's sources do not hold the answer, it says so plainly.
Answers about instructions give the instruction number; answers about faults give the fault record number.
Measured in an example deployment at a production plant with 527 technical units (presses, robots and line equipment)
Safety
Safe maintenance starts with following the approved instruction. That is why Talk to Machine does not describe anything an instruction does not contain; it sends the user to the approved instruction and the authorised maintenance team. We set the rules below with you during setup, and they cannot be changed from the chat.
Setup
We set Talk to Machine up in 5 working days and train your teams on their own data, in your company's own Microsoft 365 account. By the end of day five you have a working assistant, a first group of trained users and a handover document.
Day 1
Assigning licenses, preparing the Microsoft 365 environment and access permissions, and organising the folders that will hold the instructions.
End of the day An environment ready for setup
Day 2
Tidying the instructions: duplicates, old versions, machine names. Transferring fault records from the maintenance software and agreeing how they stay up to date.
End of the day Tidy instructions and records
Day 3
Setting up the assistant and its safety rules, making it available in Teams and Microsoft 365 Copilot, and testing it with sample questions.
End of the day A working assistant, test report
Day 4
Hands-on training for technician, operator and engineer groups: asking good questions and the safety rules.
End of the day A first group of trained users
Day 5
Training for the people who will run the assistant in-house: updating instructions, monitoring use and keeping track of the usage allowance. Pilot plan and closing meeting.
End of the day Handover document, pilot plan
Consulting
Installing an AI assistant does not by itself make it follow your safety rules or the way your documents are organised. An assistant that answers from instructions where nobody is sure which version is current makes the right information faster to reach, and a wrong step just as fast to spread.
As the team that built Talk to Machine, we run the setup from start to finish: tidying the instructions, transferring fault records, writing the safety rules and training your users. Pargesoft's experience with Microsoft Copilot Studio and Microsoft 365 Copilot projects goes into making the assistant work safely in your environment.
FAQ
Talk to Machine reads machine instructions from SharePoint and fault and maintenance records from Microsoft Dataverse. Searches in the fault records run through a tool that sends FetchXML queries to Dataverse. We transfer records kept in maintenance software such as SAP PM during setup and keep them up to date in a way we agree with you. Users reach the assistant through Microsoft Teams and Microsoft 365 Copilot.
The example deployment ran at a production plant with 527 technical units (presses, robots and line equipment). In that deployment, Talk to Machine's fault-record query tool searched 42,526 maintenance and fault records in Microsoft Dataverse (June 2022 – July 2026) in 0.4–2.5 seconds. The time the assistant takes to write its answer comes on top of that. In the same deployment, 186 machine instructions and the planned maintenance file in SharePoint were connected to the assistant and refreshed every 4–6 hours. Times vary with each installation's data volume and the question asked.
No. Talk to Machine runs inside Teams and Microsoft 365 Copilot, in your company's own Microsoft 365 account. Users ask their questions from the Teams app on a computer, tablet or phone.
Talk to Machine does not describe steps that are not in an approved instruction; it sends you to the approved instruction and the authorised maintenance team. It refuses requests to disable or bypass safety devices.
No. Talk to Machine does not search the internet and answers only from the sources your company has connected. If the answer is not in those sources, it says it could not find one.
Instructions and records stay in your company's own Microsoft 365 account. Every user signs in with their own company account and reaches only the documents they are allowed to see; the assistant cannot show them a document they could not open anyway. We decide with you during setup which files are connected to the assistant; in the example deployment, a raw file containing staff names and cost data was deliberately left out.
We complete setup and training in 5 working days: preparation, information sources, building and testing the assistant, user training, and admin training and handover, one day each.
Users with a Microsoft 365 Copilot license use the assistant without using up any extra allowance. Shop-floor users without one reach it through Teams, and that use draws on the allowance set aside for Copilot Studio. During the setup week we work out with you which users need which license, based on expected use.
Yes. Talk to Machine works in English and Turkish. During setup, we set the assistant up for the language your instructions and teams use.
The Talk to Machine installation and user guide: installation steps, security roles, making the assistant available in Teams and Microsoft 365 Copilot, limitations and troubleshooting.
When a machine stops, ask Teams instead of searching through folders. To review your instructions, fault records and the teams who will use the assistant, and to agree the scope of the 5-day setup, talk to our specialists.
Plan Your Talk to Machine ImplementationThese are necessary and important cookies. They enable you to create a user account, log in, and navigate our website. If you do not allow the use of these cookies, you may not be able to use various areas of pargesoft.com. Persistent cookies remain on your computer or mobile device after you close your browser or application and are used to recognize you when you return to our website. The maps on our contact pages are provided by Google Maps and load under this category without asking for your separate consent; your IP address and Google's cookies are transmitted to Google in the process. When you use the language switcher we store a cookie named pg_language to remember your choice; it holds only “en” or “tr”, is not shared with third parties, and decides which language opens when you visit the bare domain. Our forms are protected against automated submissions by Cloudflare Turnstile; during that check your IP address and browser information are transmitted to Cloudflare.
These cookies help us understand how visitors use our site: which pages are viewed, how long a visit lasts, where the traffic came from, and whether pages are working without errors. Measurement is performed with Google Analytics 4, and until you allow this category Google Analytics writes no cookie to your device. The data collected is used to produce aggregate statistics and improve the site; it is not used to identify you directly, to build a profile of you, or to show you advertising — advertising-related processing belongs to the separate “Target or Advertising Cookies” category and requires its own consent.
Target or advertising cookies are placed by Pargesoft's advertising networks with Pargesoft's knowledge and consent. The purposes of using these cookies may include: displaying relevant and personalized advertisements, limiting the number of advertisements displayed, measuring the effectiveness of advertising campaigns, and remembering your visit preferences.
Type to search across the whole site.
See all results