Factory edition of iaiops — discrete-manufacturing lines: OPC-UA, Modbus-TCP/RTU, Siemens S7comm (S7-300/400/1200/1500), Mitsubishi MC/MELSEC, Omron FINS (CS/CJ/CP/NX), Allen-Bradley EtherNet/IP (ControlLogix/CompactLogix), EtherCAT (CoE/SOEM), PROFINET (DCP discovery), MTConnect (CNC machine tools), IO-Link (master JSON — sensor-level visibility), MQTT/Sparkplug B/UNS, plus the cross-protocol brain (downtime root-cause, OEE, asset inventory). Use for PLC, CNC, servo/drive bus, name-of-station, tag browse, Unified Namespace, or production-line troubleshooting tasks. Read-first, MOC-gated writes. Also covers Phoenix Contact PLCnext vPLC (via its built-in OPC-UA + Modbus servers).
Data & analysis
iaiops
Try itVendor-neutral, governed industrial/OT data tap + intelligent troubleshooting. Read (and, gated, write) PLCs, controllers, machine tools and IIoT brokers over OPC-UA, Modbus-TCP, Siemens S7comm, Mitsubishi MC, Omron FINS, MTConnect, MQTT/Sparkplug B, Allen-Bradley EtherNet/IP, EtherCAT (pysoem/SOEM), SECS/GEM (semiconductor / display fab equipment over HSMS), PROFINET (DCP discovery), the building edition (BACnet/IP), and Phoenix Contact PLCnext vPLC — plus cross-protocol diagnostics ("no-data" dataflow diagnosis, OPC-UA connection self-diagnosis, subscription health, ISA-18.2 alarm bad-actors, tag/historian health, and the AI downtime root-cause copilot) and analytics (OEE/downtime, asset inventory, OPC-UA HDA, change-of-value). Use when the task names any industrial protocol, a PLC/SCADA/HMI/historian/CNC/RTU/IED, a semiconductor/display fab or SECS/GEM equipment, an electrical substation, an opc.tcp:// or mqtt:// endpoint, OEE/downtime, downtime root-cause, or OT asset inventory. Ro
What it does
Vendor-neutral, governed industrial/OT data tap + intelligent troubleshooting. Read (and, gated, write) PLCs, controllers, machine tools and IIoT brokers over OPC-UA, Modbus-TCP, Siemens S7comm, Mitsubishi MC, Omron FINS, MTConnect, MQTT/Sparkplug B, Allen-Bradley EtherNet/IP, EtherCAT (pysoem/SOEM), SECS/GEM (semiconductor / display fab equipment over HSMS), PROFINET (DCP discovery), the building edition (BACnet/IP), and Phoenix Contact PLCnext vPLC — plus cross-protocol diagnostics ("no-data" dataflow diagnosis, OPC-UA connection self-diagnosis, subscription health, ISA-18.2 alarm bad-actors, tag/historian health, and the AI downtime root-cause copilot) and analytics (OEE/downtime, asset inventory, OPC-UA HDA, change-of-value). Use when the task names any industrial protocol, a PLC/SCADA/HMI/historian/CNC/RTU/IED, a semiconductor/display fab or SECS/GEM equipment, an electrical substation, an opc.tcp:// or mqtt:// endpoint, OEE/downtime, downtime root-cause, or OT asset inventory. Routes to the iaiops MCP server. Read-first; writes are MOC-gated (high risk, dry-run + double-confirm). Do NOT use for IT/network gear, Kubernetes, hypervisors, or backups — those are separate AIops tools.
The skill document
iaiops — ROUTER(识别现场 → 派发 edition skill + MCP profile)
这是路由 skill,本身不含工具表。识别任务的行业/协议 → 转到对应 edition skill
(工具清单、workflow、支持版本矩阵都在那边),并用对应 profile 启动 MCP(IAIOPS_MCP=
环境变量,或等价 sugar 脚本 iaiops-mcp-)。现场只暴露 1-2 个协议 + 跨协议脑,
单会话工具 ~15-30,模型不被淹。
路由表(关键词 → edition skill → MCP profile)
| 任务提到 | edition skill | MCP profile / entrypoint |
|---|---|---|
| SECS/GEM · SECS-II · HSMS · 半导体/显示 fab · wafer · panel · MES equipment · SVID/ECID · recipe | iaiops-fab | IAIOPS_MCP=fab / iaiops-mcp-fab |
| 离散制造产线 · PLC(S7/S7-1200/1500 · 三菱/MELSEC · Allen-Bradley/ControlLogix/CompactLogix · Omron/FINS/SYSMAC CS/CJ/CP/NX)· Modbus · EtherCAT/CoE/SOEM · PROFINET/DCP · MTConnect/CNC 机床 · Sparkplug B/UNS | iaiops-factory | IAIOPS_MCP=factory / iaiops-mcp-factory |
| 流程工业(化工/制药/食品饮料)· HART/HART-IP · 变送器/阀门定位器 · 过程仪表 · DCS 旁路读取 | iaiops-process | IAIOPS_MCP=process / iaiops-mcp-process(有 UNS 时 IAIOPS_MCP=process,sparkplug) |
| BACnet/BACnet-IP · HVAC/暖通 · BMS/楼宇自控 · 厂务/facility · Who-Is · TrendLog | iaiops-building | IAIOPS_MCP=building / iaiops-mcp-building |
| 水处理/水厂 · pH · 浊度/turbidity · 电导率/conductivity · 加药/dosing · 泵站/pump station · 曝气 | iaiops-water | IAIOPS_MCP=water / iaiops-mcp-water |
| 仓储/物流中心 · 输送线/conveyor · 分拣/sorter · AGV/AMR · WMS/WCS · 托盘/穿梭车 · 物料搬运 | iaiops-warehouse | IAIOPS_MCP=warehouse / iaiops-mcp-warehouse |
| 医院设施/clinical facility · 负压/正压隔离病房 · 医用气体 · 手术室环境 · 医疗 BMS | iaiops-clinical | IAIOPS_MCP=clinical / iaiops-mcp-clinical |
| 光伏/PV · 逆变器/inverter · 组串/string · 风电/风机 · 场站 SCADA · 新能源电站 | iaiops-renewables | IAIOPS_MCP=renewables / iaiops-mcp-renewables |
| Phoenix Contact PLCnext / vPLC(虚拟化 PLC,走内建 OPC-UA + Modbus-TCP) | iaiops-plcnext | IAIOPS_MCP=plcnext / iaiops-mcp-plcnext |
| IO-Link · IO-Link master · IODD · 智能传感器/executor 参数 · pdin · ISDU(主站 JSON/REST 接口,只读) | iaiops-factory(楼宇传感器场景 iaiops-building) | IAIOPS_MCP=factory / 单协议 IAIOPS_MCP=iolink / iaiops-mcp-iolink |
- 单协议深用(只有一种设备):直接
IAIOPS_MCP=opcua(或 modbus/s7/mc/fins/eip/mtconnect/ sparkplug/ethercat/secsgem/profinet/bacnet/hart),等价脚本iaiops-mcp-<协议>。 - 跨行业只问 OEE/停机根因/资产盘点/数据质量:任一 profile 均可 —— 跨协议脑
(诊断/OEE/资产/合规)默认随 server 暴露,选覆盖现场协议的 profile 即可;
纯脑场景可用
IAIOPS_MCP=brain/iaiops-mcp-brain(只暴露脑,零协议)。 - 说不清行业但报了协议名:按协议列选含它的最小 profile;都不沾 →
iaiops doctor+protocols_supported先看现场配置了什么。
部署(0.10.0 起:无默认,必须选菜单)
- 裸启动
iaiops-mcp(不设IAIOPS_MCP)不再暴露全部工具:打印选择菜单到 stderr 并 exit 2。必须设IAIOPS_MCP=或用预置入口iaiops-mcp-。IAIOPS_MCP=menu显式打印同一菜单(带各 selection 工具数)后退出。 IAIOPS_MCP=all仍可显式使用(power user;>100 工具时启动日志给洪泛警告)。- 多进程站点(1 脑 + N 协议):跑一个
iaiops-mcp-brain(只脑),协议 server 各自 加IAIOPS_MCP_NO_BRAIN=1(如IAIOPS_MCP_NO_BRAIN=1 iaiops-mcp-opcua)去掉脑, 避免跨 server 工具重名;protocols_supported(发现工具)在 NO_BRAIN 下仍然保留。
Energy 协议 → 另一个包(不在本 server)
IEC 60870-5-104 / IEC-104、DNP3 / outstation、IEC 61850 / MMS / IED、变电站/
substation、电力/能源/utility SCADA → 用独立的 iaiops-energy
(pip install iaiops-energy,然后 iaiops-energy-mcp;
github.com/industrial-aiops/industrial-aiops-energy)。它复用本包的 core + 脑;
monitor-direction only。不要尝试用本 server 的 profile 覆盖能源协议。
安全不变量(所有 edition 一致,路由前先记住)
- Read-first:默认只读;先
protocols_supported看能力、iaiops doctor/doctor验链路,再谈读,最后才谈写。 - 写 = MOC(Management-of-Change):The 10 write tools(
s7_write_db、mc_write_words、fins_write_words、mqtt_publish、eip_write_tag、ethercat_write_sdo、ethercat_set_state、profinet_dcp_set、bacnet_write_property、bas_command)全部risk=HIGH、默认dry_run=True、捕获改前值供 undo(bas_command另对生命安全点一律拒绝)。 - 审批:真实写入需具名审批人 —— CLI
iaiops approve双重确认后才放行。 - 未经授权绝不写生产控制系统;AI 结论仅 advisory,引用真实信号出处,宁可
insufficient_evidence不臆测。 - 各协议的验证状态(✅ 已自测 / 待核实)见 edition skill 的支持版本矩阵,
标
待核实的不得当既成事实。
Setup(各 edition 相同)
iaiops init 交互写 ~/.iaiops/config.yaml;凭据进加密存储
(~/.iaiops/secrets.enc,主密码 IAIOPS_MASTER_PASSWORD)。iaiops doctor
逐端点探活。协议参数、模拟器自测、MCP JSON 示例见 README 与各 edition skill。
Related skills
Process-industry edition of iaiops — chemical / pharma / food & beverage / oil & gas plants: HART-IP process instrumentation (transmitters, valve positioners, loop current), OPC-UA (DCS / gateway read), Modbus-TCP/RTU (skids, analyzers), optional MQTT/Sparkplug B UNS, plus the cross-protocol brain (downtime root-cause, data quality, OEE). Use when the task mentions HART, HART-IP, transmitter, 变送器, valve positioner, process instrumentation, PV/SV/TV/QV, loop current, burst mode, DCS tap, or a process plant. Read-first, MOC-gated writes.
Fab edition of iaiops — semiconductor / display (panel TFT-LCD/OLED) fab equipment over SECS/GEM (SEMI E5 SECS-II, E30 GEM, E37 HSMS) plus OPC-UA for the equipment's internal control layer, with the cross-protocol brain (downtime root-cause copilot, OEE, asset inventory, data quality). Use when the task mentions SECS/GEM, SECS-II, HSMS, GEM host, wafer, panel, fab equipment, MES equipment interface, SVID, ECID, ALID, PPID / process program, recipe list, or a semiconductor / display fab tool. Read-first, MOC-gated writes.
PLCnext / virtualized-PLC edition of iaiops — Phoenix Contact PLCnext Control and vPLC (虚拟化 PLC) reached over its built-in OPC-UA server (opc.tcp 4840) and Modbus-TCP process-data server, plus the cross-protocol brain (dataflow diagnosis, downtime root cause, PdM, OEE, alarm, baseline). A packaging edition — no new connector, no PLCnext-vendor SDK: it routes to the standard OPC-UA and Modbus tools already shipped. Use when the task mentions PLCnext / PLCnext Control / AXC F / vPLC / virtual PLC / 虚拟 PLC / Phoenix Contact controller over OPC-UA or Modbus. Read-first; this edition's tool surface is read-only.
Building edition of iaiops — facility / HVAC / BMS / 厂务 over BACnet/IP (ASHRAE 135): Who-Is discovery, object/point lists, presentValue snapshots, COV capture, TrendLog reads, one MOC-gated property write; plus Modbus-TCP/RTU for meters/chillers and optional plain MQTT for IoT sensors, with the cross-protocol brain. Use when the task mentions BACnet, BACnet-IP, HVAC, AHU, chiller, VAV, BMS, building automation, facility management, 厂务, 楼宇自控, Who-Is, presentValue, or TrendLog; also IO-Link masters for smart building sensors (JSON interface, read-only), and the vendor supervisory-controller REST layer above BACnet (Metasys/OpenBlue, Niagara/oBIX) for point/alarm/trend reads and one MOC-gated command. Read-first, MOC-gated writes.
Vendor-neutral, governed, READ-ONLY energy/substation telecontrol data tap — the energy edition (变电/电力) of Industrial-AIOps. Monitor-direction telemetry over IEC 60870-5-104 (IEC-104: RTU link status, general interrogation, single monitored-point reads by IOA — 遥测/遥信), DNP3 / IEEE 1815 (outstation link status, Class 0/1/2/3 integrity poll), and IEC 61850 MMS (IED logical-device directory, model browse, data-attribute reads) — plus the base cross-protocol brain (dataflow diagnosis, alarm bad-actors, data-quality scorecards, OEE, asset inventory, compliance self-assessment) mounted on the same server. Use when the task names IEC 60870-5-104 / IEC-104 / 104规约, DNP3 / IEEE 1815 / outstation, IEC 61850 / MMS / IED / GOOSE (GOOSE and Sampled Values are NOT supported — MMS reads only), a substation / 变电站 / RTU / SCADA gateway / telecontrol front-end, energy / power / utility SCADA telemetry, or 遥测遥信 / 电力监控. Routes to the iaiops-energy MCP server. Monitor-only by design: no control/operate (CR