Skip to content

Explanation

Understanding-oriented background for Cloud-Native DCS. Read these before you author your first recipe. They explain the ISA-88 vocabulary, the template-and-binding model, and how alarms and interlocks work. With that grounding, the how-to guides in Batch Operations read as "oh, I've seen this before".

Three of the pages below (the Adaptation Guide, Alarms and Interlocks, and Debugging a Running Batch) are task-oriented how-to guides. They live in this section because each one teaches the underlying model (templates and bindings, the two alarm/interlock layers, the procedural execution tree) through a worked task, and they're the natural next read after the conceptual pages.

Sections

  • Mental Models — how Cloud-Native DCS concepts map to the ISA-88 vocabulary and to control systems you've used before.
  • Adaptation Guide (how-to) — when to clone a library template, when to parameterize, and when to write something new, taught through a worked clone → rebind → run example.
  • Parameter Binding — how recipe parameters flow from master recipe to running batch, and why bindings are evaluated when they are.
  • Alarms and Interlocks (how-to) — the difference between the two, where each is configured, and how they interact with phase state, with three worked alarm patterns.
  • Debugging a Running Batch (how-to) — what to look at when a batch is stuck or behaving unexpectedly, before you reach for raw logs.
  • Procedural SFC Dialect — how Sequential Function Charts work in this DCS: actions with temporal extent, waitForAction, and why we don't use IEC 61131-3 action qualifiers.
  • GitOps for Automation Engineers — how the UI bridges a DeltaV-style workflow to the underlying GitOps substrate, and what the product decides versus what your deployment instance decides.
  • UI Deployment Topologies — the supported configurations for splitting dev and prod, from single-namespace through laptop-mode developer workstations.
  • Batch Operations — task-oriented guides for running batches and authoring recipes.
  • Libraries — runnable example recipes, phases, and control modules you can clone and adapt.
  • Terminology — the project's glossary of ISA-88 and Kubernetes terms.