Use case 02 · Pharma engineering · Process 2.2

Compliance figure,
ready on day one.On the first working day, a robot checks every PM work order for a signed, approved checklist and builds the compliance report using the planner’s own rule.

Read-only in the document system
PM compliance · last month Sample
~450work orders
● On time, checklist approvedCompliant
● Completed lateLate
● Completed, no documentReminder
● Not completedOpen
Compliance rule Rule
Compliant means completed on time and the signed checklist is Approved. The same rule the planner uses.
Current process estimates
~450
PM work orders checked every month
2 days
to build the report by hand, order by order
~3h
from start of run to a review-ready report
Estimated
4 classes
every order classified with a next action
How it was done

Two systems, 450 orders, checked one by one.

Pull last month’s
PM work orders
→
Check which are
technically complete
→
Search the
document system
→
Confirm the signed
checklist is there
→
Calculate
compliance %
About 2 daysOrders completed in SAP without a signed checklist don’t count as compliant, so every one had to be checked by hand.
How it works now

Every work order, every checklist,
checked on the first working day.

One robot reads both systems, classifies every order and prepares the report. The planner reviews it before it goes anywhere.

Each PM work orderfrom last month, ~450 in all
Technically complete (TECO)?
Signed checklist found & Approved?
Finished by the planned date?
CompliantOn time, checklist approved.● Counted
YesYesYesNoNoNo
Not completedShown as open in the report.● Planner
No documentReminder lists the WO numbers. More than one file → manual check.● Engineer
Completed lateCounted as not compliant, shown by area.● Planner
Compliance % by area and overall · the planner’s own rule · existing report format
Report draft→Planner reviews→Site head & QA
Where the robot stops

Automation handles the work.
People own the decisions.

Read-only in the document system: nothing uploaded, approved or changed.
A work order with more than one checklist file is listed for a manual check.
The report goes to the site head and QA only after the planner reviews and forwards it.
Reminders list each engineer’s missing documents in one mail.
Why it works

Missing documents chased while people still remember the job.

Same rule and report format the planner already uses
Reminders go out in the first days of the month
A person signs off a figure used in management review
Your audit-readiness check

How audit-ready is
your PM record today?

Answer four questions to see where your compliance figure is exposed. Share your workflow and we’ll show how many orders are missing approved checklists and how fast the report could be ready.

Example from this case~450 PM orders checked in about 2 days → about 3 hours to a review-ready report
Assess my PM compliance gap
For a detailed estimate, we’ll ask
PM orders per monthDays to build the reportOrders missing documentsWho signs off the figure
Quick self-check
Is your PM compliance figure ready in the first 2 working days?
Does every completed PM order have an approved checklist by month end?
Are engineers reminded about missing documents without anyone chasing?
Is the figure reviewed before it reaches management?
planner time a robot could hand back

Audit-ready every month.
Without the two-day hunt.

Move from order-by-order checking to a report that’s ready for review on day one.

Book a 20-min walkthrough

Indicative benefits based on the client's current process estimates. Final savings and automation feasibility depend on SAP PM and document system access, master data quality and pilot validation. Client details withheld.

© BillionApps · billionapps.aiUse case 02 · Pharma engineering · Process 2.2