Bot TutorialsGrok BotChatGPTClaudeGeminiCopilotPerplexityMore botsGuidesArticlesPapersIndustrialSearch

Bot-written shift reports and alarm summaries, offline

The most valuable, lowest-risk job for a plant bot: reading a shift's worth of data and alarms and writing a handover summary a person signs.

1. Export, don't connect

Export the last 12 hours of the historian (CSV) and the alarm journal from the historian replica in the DMZ. The bot reads files; it doesn't need a live connection at all.

2. Trim the data first

Local models have limited context. Pre-aggregate with a script: min/max/mean per tag per hour, plus every alarm event. Let code do the math; let the model do the words.

import pandas as pd
df = pd.read_csv("hist.csv", parse_dates=["ts"])
agg = df.groupby(["tag", pd.Grouper(key="ts", freq="1h")])["value"].agg(["min","max","mean"]).round(2)
agg.to_csv("hourly.csv")

3. Use a fixed report template

Same headings every shift makes errors easy to spot:

Write the shift handover from hourly.csv and alarms.csv.
Sections: 1) Safety/environmental events 2) Alarms by count, top 5, with tags
3) Equipment out of normal range 4) Open items for next shift.
Rules: cite tag + time for every fact. No speculation about causes unless labeled "possible".
If data is missing for a period, say so.

Send it to the local server from lesson 2 with a short Python or curl call.

4. A person reviews and signs

The outgoing supervisor edits and signs. The signed version is the record; the raw bot draft is kept in the audit log for comparison.

5. Measure it

For a month, have supervisors mark each bot draft: correct / minor fix / wrong. If "wrong" isn't near zero, fix the data pipeline or the prompt before relying on it.

Where these facts come from

Checked Oct 29, 2026. Tutorials are educational. Follow your site's safety procedures, management-of-change process and the equipment maker's manual. Never test against live production equipment without authorization.

Industrial control with bots: all lessons → Next: 7. Audit logs that a bot cannot rewrite →

Related: 1. Ground rules: what a bot may and may not do in OT2. Run a local LLM on an air-gapped Linux box3. Sneakernet: move models and updates across the gap safely4. Read Modbus TCP data with a bot (read-only)5. Read OPC UA tags securely with a bot6. Bot-written shift reports and alarm summaries7. Audit logs that a bot cannot rewrite8. Human-in-the-loop: approval gates before anything movesCan AI control a PLC?Run AI offline on LinuxGuidesScripts & templates