Quality deviations are written up and sent for sign-off on the same shift
The shift supervisor posts a few lines on Teams. The AI adds the batch details from SAP, drafts the deviation report and sends it to QA before the shift ends.
- Used day to day by
- Shift supervisors
- Quality team
- Quality head
How it runs with AI
The supervisor posts what happened on Teams in a line or two, straight from the shop floor. The AI asks for anything missing, pulls the batch details and recent checks from SAP, and drafts the report in the plant's own format in SharePoint. QA gets it while the shift is still on and the people involved can still answer questions.
How it is done today
When something goes wrong on a line, the supervisor deals with it first and notes it in the shift logbook. The deviation report gets written later, often the next day, from memory and scattered readings. QA then chases the batch number, the times and the checks, and some reports are still open when the auditor visits.
Step by step
Where the work happens, what the AI does, and where it hands over to a person.
-
Step 1, AI
Reads the supervisor's Teams post and asks what is missing
Needs to know: What the report needs
In
Microsoft Teams -
Step 2, AI
Pulls the batch and its recent quality checks from SAP
Needs to know: Specification limits by product, Line for each batch
In
SAP S/4HANA -
Step 3, AI
Drafts the deviation report in the plant's own format
Needs to know: Plant's report template, Past deviation reports
In
SharePoint -
Step 4, AI
Logs it in the deviation register and sends it to QA
Needs to know: QA officer per shift, Sign-off order
In
SharePoint , Microsoft Teams Exception to step 4
Alerts the plant QA head on Teams if the sign-off is still open after a set time
-
Step 5, Person
Signs the report and decides on the held stock
In
SharePoint
What stays with a person
- Signs the report and decides on the held stock
Apps in this example
- Microsoft Teams
- SAP S/4HANA
- SharePoint
The same flow works with the apps you use.
This fits you if
- Your plants raise more than 30 quality deviations a month
- Deviation reports are often written a day or more after the event
- Supervisors can reach Microsoft Teams on the floor, on a phone or a line tablet
- Batch and process order details live in SAP S/4HANA
- Auditors or customers have asked about late or incomplete deviation records
What to watch for
- The class of the deviation, the root cause and what happens to the held stock are QA's decisions. The AI drafts the report and sends it, and QA signs
- The draft uses what the supervisor posts and what SAP holds, so QA checks the numbers against the line records before signing
- Supervisors can post in their own language. The draft is in English, so QA checks that the meaning carried across
- QA sets up the report template and the sign-off order once, and each sign-off keeps its record in SharePoint for the auditor
