Skip to main content
Layer researchLine of business and OT

Line-of-business & OT

By Murali SidLinkedInPublished

Status: complete (published 2026-08-19). Scope finalized at Batch C kickoff with maintainer POV; see findings.md and sources.md.

Scope inventory (v0)

  • Estate: EAM/CMMS, WMS, MES, field force scheduling and dispatch, GIS, historians, IoT and telemetry platforms; utilities stack (SCADA, ADMS, OMS, AMI), public sector case management
  • Boundary architecture: OT/IT segmentation (Purdue model, DMZs, data diodes), IEC 62443 and NERC CIP constraints, industrial protocols (OPC UA)
  • Agent stance per loop: read-only insight, advisory recommendation, supervised actuation; agents never inside safety-instrumented loops; digital twins and simulation as the safe interface
  • Work surfaces: work order lifecycle, outage and incident workflows, field crew assistance as primary agent entry points

Challenged-default candidates

Digital twin platforms as agent prerequisites vs direct historian access; vendor OT-AI suites vs IT-side advisory agents. Each track proposes its final list at kickoff.

Files

findings.md and sources.md carry this track's research. The scoping brief and the vendor map were archived on 2026-08-23 (see archive/, decision D038).

Cite this page

Written by Murali Sid, Founder and AI Systems Architect, last updated 18 September 2026. Licensed CC BY-SA 4.0, so quote it freely with attribution.

Murali Sid (2026). Line-of-business & OT. Agentic Architecture Skills. https://www.agenticarchitectureskills.com/library/layers/r05-lob-and-ot

Machine-readable version of this page: /library/layers/r05-lob-and-ot.md

On this page