Skip to main content

Automation — Hand off the checks you do every day

Automation lets you hand off a check someone repeats every day — "take a look at this every morning" — in a single sentence. You write the sentence, and AI fills in the instructions, tools, timing, and where results go. You preview the result before turning it on. How to build one is covered in Automation. This page lists the fourteen built into Automation › Templates, organized by role. Clicking a template opens it pre-filled with the defaults below; you adjust the timing, recipient, and instructions before saving. The default recipient for every template is "Me" — other people, roles, internal mail, attachments, and messenger channels are added by the creator under "Send".

First — what automation can and can't do​

What it doesRule
Read — look up anomalies · incidents · proposals · documents · time seriesFreely, but only within the creator's permissions and equipment scope
Send — app notifications · internal mail · messenger channels (Teams · Slack) · mail attachments (Excel · CSV · PDF)Only to recipients fixed at creation time. Mail goes only to internal users/roles, and only to addresses on domains the admin has allowed. Messenger goes only to channels the admin has registered. PDF attachments are only added when the PDF conversion service is enabled and responding
Write — things like filing maintenance requests · chasing purchase orders · raising incidentsAlways stops at pending approval. A person must approve it from the proposal card before it goes out
  • Automations written as "when..." mostly work by checking on a set interval and only producing a result when the condition is met. Runs where the condition isn't met are logged only in the run history as "nothing to report" and send nothing. The interval can't be shorter than 30 minutes — only condition monitoring (①), where you set a tag/threshold as a watch condition and the server measures the value itself, can go down to 5 minutes.
  • Numbers come only from values looked up through tools. If a lookup fails, it's recorded as "could not determine" — never written as "no issue".
  • If the server restarts while a run is going, that run is left as "Interrupted". It does not resume, produces no report · card, and sends nothing — Schedule · Alarm runs cut off by a sudden server crash are run again by the queue as a new run → Automation — Execution log statuses
  • The recipient in a template is filled in as "Me". Sending to someone other than yourself, a role, or a messenger channel requires the "Approve — execute incident action" permission.
  • The "Say it like this" examples below are sample phrasings for "Build by conversation". If your sentence names a recipient (e.g. "tell the shift lead"), that role gets filled in, but when you open it by clicking the template, the recipient is "Me".
  • Internal mail requires the admin to have set up a mail server and an allowed mail domain; messenger requires a notification channel to be set up before you can select one → Copilot Admin Console

At a glance​

#TemplateWhoWhen (default)Where results go (default)Human approval
①Condition monitoringEveryoneEvery 30 min — only when the condition is met (down to every 5 min if a watch condition is set)Proposal card + app notificationApprove if filing an incident is proposed
②Morning shift briefingShift leadDaily 06:50Report + app notificationNone (read-only)
③Shift handover noteShift leadDaily, 30 min before shift end (default 05:30 · 13:30 · 21:30)Report + app notificationNone (read-only)
④Recurring alarm cleanupShift leadHourly — only when an equipment item has had the same alarm 5+ times todayProposal cardDecide from the card
⑤Drawing revision noticeShift leadMon–Sat 07:30 — only when a non-current drawing existsProposal card + app notificationDecide from the card
⑥Recurring failure causeMaintenanceDaily 06:00 — only when equipment has recurred more than 3 times in 30 daysProposal cardApprove maintenance request
⑦Instant incident alertMaintenanceWhen a new incident (severity ≥ moderate) is filedSummary + app notificationNone (read-only)
⑧Unresolved incident reminderMaintenanceDaily 08:30 — only when unresolved incidents older than 4 hours existReport + app notificationNone (read-only)
⑨Upcoming preventive maintenanceMaintenanceWeekly, Mon 07:00Report + app notificationNone (read-only)
⑩Weekly equipment reportPlant managerWeekly, Mon 08:00Report + app notificationNone (read-only)
⑪Proposal handling statusPlant managerMon–Sat 17:00Report + app notificationNone (read-only)
⑫AI accuracy checkPlant managerWeekly, Mon 09:00 (last 30 days)ReportNone (read-only)
⑬Delivery risk POsPlant managerMon–Fri 07:00 — only when work is at risk of delayReport + app notificationApprove PO reminder (2-person)
⑭Quality anomaly trackingShift leadHourly — only when a new quality deviation existsProposal cardDecide from the card
  • "Where results go" is given for the default recipient "Me" in every case. "Who" is just the role the template targets, not who it's sent to.
  • ⑤ · ⑬ · ⑭ only appear in the template list when digital thread tools are available. On installations without that connection, these three simply don't appear — other templates and screens are unaffected.
  • Other templates also drop out of the list if a tool they require (time series insights, Platform tag lookup, etc.) isn't available to this installation or this person.
  • ⑤ · ⑥ · ⑦ · ⑨ · ⑭ include document search (rag_search) in their tools when it is available, and use maintenance documents · drawings as evidence. Document search is not a required tool, so even if it is off in the MCP Gateway, the templates are still visible and run without document evidence → MCP Tool Map
  • If anything is missing from the templates, admins see "N templates hidden on this installation" below the template list, along with the reason.
  • Internal mail, attachments (Excel · CSV · PDF), and messenger channels aren't preselected in any template. PDF attachments can only be chosen when the PDF conversion service is enabled and responding; if it's selected but the service doesn't respond, only the PDF is dropped — the mail body and Excel/CSV still go out.

Everyone​

① Condition monitoring​

  • Say it like this "Let me know if Injector 2's temperature goes above 80°C"
  • When Checked every 30 minutes. Produces a result only when the specified tag meets the condition. Sustained conditions like "if pressure drops for more than 10 minutes" are checked against tag history to confirm the condition held throughout
  • Result A proposal card (current value · condition · measurement time · what to check first) and an app notification to me. While the condition persists, you won't be notified again the same day
  • Human approval If needed, file an incident is attached to the card, and a person must approve it for the incident to be created
  • Why it's useful Hands off "let me know if this value is exceeded" on the spot

Opening the template shows a watch condition field in settings (tag · comparison · threshold · duration).

Watch conditionWho judges itShortest interval
SetThe server reads and measures the tag value directly. Runs where the condition isn't met don't invoke the AI model — AI writes the card text only when it's met5 min
Not setAI judges based on the condition in the first line of the instructions (e.g. "Watch condition: Injector 2's temperature exceeds 80°C") — AI is invoked every run30 min

If the tag can't be found or the value isn't numeric, it's recorded as "could not determine" — not "condition not met". What the old watch feature did is now built as this template → Automation — Watch Conditions

Shift lead​

② Morning shift briefing​

  • Say it like this "Every morning at 6:50, summarize overnight incidents and alarms and send them to the shift lead via app"
  • When Daily 06:50
  • Result One report — a per-equipment table for the last 12 hours (equipment · open findings · alarm count · attention score · reason to check, up to 10 rows) plus a summary of the top three equipment items to check today. App notification to me
  • Human approval None — read and summarize only
  • Why it's useful Start the shift with a single page instead of checking multiple screens

The numbers in the table are filled in directly by the server from tool results — AI only writes the summary and "reason to check" text. For rows where the AI could not write a reason, the server writes the basis of the attention score in the installation language (e.g. "Equipment anomaly finding (severity high, urgent) categories sensor"). Unreadable values show "—", truncated counts show "N+", and nothing is sent if there's no equipment to list. To send to every shift lead, change the "recipient" and the notify-list under "Send" to the shift lead role.

③ Shift handover note​

  • Say it like this "30 minutes before shift end, send the next shift lead a mail with what happened this shift"
  • When Daily, 30 minutes before shift end. The template calculates times from the installation's shift boundaries (default 06:00 · 14:00 · 22:00), filling in 05:30 · 13:30 · 21:30
  • Result A report (findings from the last 8 hours as a "what · status · next shift's action" table) and an app notification to me. Alarms and ongoing/blocked work are included only if those tools (alarm list, today's work) are connected on this installation
  • Human approval None — read and summarize only
  • Why it's useful "Remaining work," often lost in verbal handovers, is captured in writing

To mail it to the next shift lead, add internal mail under "Send" and pick the role or person under "Notify". Preview again after changing the recipient.

④ Recurring alarm cleanup​

  • Say it like this "If the same alarm fires more than 5 times a day, raise it to the shift lead as a proposal card"
  • When Checked hourly. Produces a result only when the same equipment/alarm combination has occurred 5+ times today
  • Result A proposal card — alarm name · count · last occurrence, plus a one-line cleanup suggestion (e.g. check the setting)
  • Human approval The recipient decides whether to act
  • Why it's useful Turns an alarm you silence every time into "a one-time fix"

⑤ Drawing revision notice — only visible when digital thread tools are available​

  • Say it like this "If a drawing used in today's work has been revised, tell the shift lead before work starts"
  • When Mon–Sat 07:30. Checks the revision of drawings/part numbers used in work in progress or scheduled for today, producing a result only when the referenced revision isn't the latest released one, or an engineering change is in progress
  • Result A proposal card (work order · part number · referenced revision · latest revision · change number) and an app notification to me
  • Human approval The recipient decides
  • Why it's useful You know before starting work on an outdated drawing

Drawings with unknown revision status are separately marked "needs checking" rather than being assumed current.

Maintenance​

⑥ Recurring failure cause​

  • Say it like this "If the same equipment stops more than 3 times a month, find candidate causes and raise it to maintenance"
  • When Checked daily at 06:00. Produces a result only when the same equipment has had 3+ recurring stoppage/anomaly/failure-risk findings in the last 30 days
  • Result A proposal card — candidate causes (up to two per equipment) drawn from similar past waveform cases and maintenance documents, with supporting evidence. Without supporting documents, it's simply marked "needs inspection"
  • Human approval A maintenance request is attached to the card as "pending approval". It must be approved to enter the maintenance system — only attached on installations with an MES connector that can file maintenance requests
  • Why it's useful Turns "it stopped again" into "this is the third time, and here's a possible cause"

⑦ Instant incident alert​

  • Say it like this "When an incident is filed, summarize it immediately to the maintenance Teams channel"
  • When When a new incident (severity ≥ moderate) is filed. The same equipment is notified at most once per 10 minutes
  • Result A summary — two or three sentences on what happened and what to check first. App notification to me
  • Human approval None — read and notify only
  • Why it's useful See what's going on from your phone before you reach the field

To send to a messenger channel (Teams · Slack), add a messenger channel under "Send". Channels are chosen from those the admin registered under Admin › Notification Channels; if no channel is registered or you lack permission to send to others, you can't select one — it falls back to an app notification.

⑧ Unresolved incident reminder​

  • Say it like this "Every morning, summarize for maintenance any incidents that have sat unassigned for over 4 hours"
  • When Daily 08:30. Produces a result only when there are incidents filed more than 4 hours ago that are unassigned or have no action taken
  • Result A report — sorted by severity: equipment · title · severity · reason (unassigned/no action) · elapsed time, plus the top three to pick up first. App notification to me
  • Human approval None — read and notify only
  • Why it's useful No unassigned incident goes unnoticed for a full day

The threshold (4 hours) can be changed in the instructions.

⑨ Upcoming preventive maintenance​

  • Say it like this "Every Monday morning, email maintenance an Excel of equipment that needs inspection"
  • When Weekly, Mon 07:00
  • Result A report — sorted by declining health index: equipment · health index · recent findings · inspection items · supporting documents. App notification to me
  • Human approval None — read and summarize only
  • Why it's useful Schedule inspections when things start degrading, not after they fail

Inspection items are listed only from the equipment manual; if none exists, it's marked "check manual needed". It does not calculate run-hours or maintenance intervals itself. To mail maintenance an Excel file, add internal mail and the recipient under "Send", and pick Excel as the attachment.

Plant manager / Admin​

⑩ Weekly equipment report​

  • Say it like this "Every Monday, build a report of last week's equipment status and email the plant manager a PDF"
  • When Weekly, Mon 08:00
  • Result A report — a per-equipment table for the last 7 days (equipment · finding count · alarm count · health index · one-line assessment, up to 12 rows) with a summary of notably poor equipment. App notification to me
  • Human approval None — read and summarize only
  • Why it's useful No manual assembly of weekly meeting materials

As with ②, the table numbers are filled in directly by the server from tool results. To send the plant manager a PDF, add internal mail and the recipient under "Send", and pick PDF as the attachment — PDF can only be selected when the PDF conversion service is enabled and responding. Reports can also be opened from the "Reports" tab in the automation detail view, as Excel/CSV, or printed. The title of the report · email is automation name · run time, like "Weekly equipment report · 2026-10-19 08:00" every week, and the title the AI wrote is attached as a subtitle → Automation — Report titles

⑪ Proposal handling status​

  • Say it like this "From Monday to Saturday at 5pm, tell me how many of today's proposals were handled"
  • When Mon–Sat 17:00
  • Result A report — counts of today's proposal cards by source and outcome (done · not applicable · in progress · unaddressed), plus still-unhandled cards (cards closed as done/not applicable don't count as remaining). App notification to me
  • Human approval None — read and notify only
  • Why it's useful Know before you leave what's carrying over to tomorrow

⑫ AI accuracy check​

  • Say it like this "Every Monday, report how accurate the AI's anomaly judgments were over the last 30 days"
  • When Weekly, Mon 09:00 — always looks at the trailing 30 days (no calendar-month schedule)
  • Result A report — totals of correct/false-alarm/missed/precision for AI anomaly judgments, plus equipment with low precision. Equipment with too little sample data is marked "insufficient sample". No report is produced if AI determines there's nothing to report
  • Human approval None — read-only
  • Why it's useful Judge how much to "trust" the AI with numbers, not a feeling → AI Findings and Accuracy · Accuracy / Benchmarks

Templates visible only with digital thread tools​

⑤ Drawing revision notice (above, under "Shift lead") and the two below.

⑬ Delivery risk POs​

  • Say it like this "Every weekday morning at 7, email the plant manager an Excel of POs at risk of delay, and draft a reminder"
  • When Mon–Fri 07:00. Produces a result only when work is at risk of delay against a customer PO
  • Result A report — customer PO · work order · root-cause material PO · need-by date · recovery option impact. App notification to me. For order lines needing a reminder, a PO reminder draft is attached as "pending approval"
  • Human approval Reminders require approval before they go out. By default, PO reminders require approval from two different people (two-person approval) → Permissions
  • Why it's useful Learn of delivery risk the day materials are delayed, not the day before delivery

To mail the plant manager/purchasing an Excel file, add internal mail under "Send", choose recipients under "Notify", and pick Excel as the attachment. The PO reminder draft is only attached on installations with an SCM connector that can issue reminders.

⑭ Quality anomaly tracking​

  • Say it like this "If a quality deviation occurs, trace work orders that used the same lot and raise it to the shift lead"
  • When Checked hourly. Produces a result only when a new quality deviation (nonconformance/inspection failure) occurred in the last hour
  • Result A proposal card — other work orders that used the same process/material lot as that part number/lot, i.e. the scope of impact. If nothing is connected, it's marked "no connection found"
  • Human approval The recipient decides
  • Why it's useful Connects "a defect occurred" directly to "how far did it spread"

Build it yourself if there's no matching template​

Templates are a starting point. Writing a sentence or two in "Build by conversation" under Create Automation fills in a draft the same way — for example: "When a new incident comes in, find past corrective actions for the same equipment and summarize candidate causes," or "Every Monday at 9, build a report of last week's maintenance performance." Available tools are limited to the read tools visible to this installation and this person.