P7 — Flagship Final step in the CDL pipeline

Automatic
Code Maker™

ACM‑Engine‑for‑Excel — FRS to DCS Code, Automatically

ACM is the crown jewel of the CDL suite. It reads the completed FRS data from P6 — the CCM Step Interaction Matrix, I/O assignments, root tags, and step transitions — and converts everything directly into production-ready DCS control code.

No manual transcription. No interpretation errors. No gap between what the FRS specifies and what gets programmed into the control system. Every line of generated code is traceable back to a specific step, tag, or transition condition in the FRS.

Buy Now Request a Demo

DCS platforms supported

Manual transcription steps

100%

FRS-traceable code output

Direct FRS input — no re-entry

ACM Generated Code — Emerson DeltaV (Example)

// ACM Auto-Generated Step Logic
// Source: FRS Reactor-UM / Step S03
// ACM-Engine-for-Excel v4.2 | CDL

MODULE REACT_UM_S03
  DESCRIPTION "Feed System Preparation"

  STEP S03_ENTRY:
    // Pre-conditions from FRS C4
    IF FV101.POS = "CLOSED"
    AND FV102.POS = "CLOSED"
    THEN
      OPEN(XV100)
      START(P100)
      SET_SP(FIC100, 25.0)

  TRANSITION S03_TO_S04:
    PI100.PV > 2.5
    AND XV100.POS = "OPEN"
    AND TIMER(10) = "ELAPSED"
END_MODULE

Generated from P6 FRS C5 Matrix — traceable to P4 SOP p-Code — zero manual edits required

The Problem ACM Solves

Eliminating the Most Error-Prone Step in Every Control System Project

In every traditional SBC implementation, the final step is the same: an engineer sits down with the completed FRS and manually programs the DCS. Step by step, tag by tag, transition condition by transition condition. It is slow, expensive, and error-prone.

Even experienced engineers make transcription errors under time pressure. And when errors are discovered during commissioning — the most expensive possible moment — they require rework in both the DCS and the FRS documentation. ACM eliminates this entire category of risk.

Reads the P6 FRS C5 CCM Step Interaction Matrix directly — no re-entry
Generates complete step logic, transition conditions, and CCM activations
Produces all I/O assignments, root tag mappings, and setpoint definitions
Creates DCS-specific code in the target vendor's format
Every generated code element is traceable to its FRS source
Supports multiple DCS targets from a single FRS source

Without ACM — Traditional Approach

Manual FRS-to-DCS Programming

Engineer reads FRS and manually types each step into DCS

Transcription errors introduced step-by-step under time pressure

Discrepancies between FRS document and DCS code are common

Changes require updating FRS, then re-programming DCS manually

No traceability between code lines and FRS source requirements

Errors discovered at commissioning = expensive rework

↓ Replace with ACM

With ACM — Automatic Generation

FRS Data → DCS Code in One Operation

ACM reads P6 FRS C5 matrix directly — zero manual re-entry

Entire step library generated in a single operation

Code guaranteed to match FRS specification exactly

FRS changes regenerate code automatically — no manual sync

Every code element tagged back to FRS source (step, CCM, tag)

Logic validated by P6 simulation before code generation

Supported Systems

Four DCS Platforms — One FRS Source

ACM generates vendor-specific code for the four most widely deployed DCS platforms in continuous process industries. The same P6 FRS file is the source for all targets — switching DCS vendor does not require re-designing the FRS.

Emerson

DeltaV Distributed Control System

Generates DeltaV-native module code including sequential function chart (SFC) logic, phase logic blocks, and I/O channel assignments in DeltaV module format. Ready for direct import into the DeltaV engineering workstation.

SFC Phase Logic Module Code I/O Assignment DeltaV Import Format

Honeywell

Experion Process Knowledge System

Produces Experion-compatible control module logic with sequential control module (SCM) structure, phase logic, and tag database entries. Aligned with Honeywell's ACE programming environment requirements.

SCM Logic Phase Definitions Tag Database ACE Format

ABB

System 800xA Process Automation

Generates 800xA-compatible function block code including Sequential Function Chart elements, Batch Phase Manager logic, and object type definitions for ABB's Control Builder M engineering environment.

SFC Elements Phase Logic Object Types Control Builder M

Industrial IT

XML-Based Engineering Format

Produces structured Industrial IT XML format — a vendor-neutral intermediate representation that can be imported into compatible engineering environments or used as the basis for custom DCS integrations beyond the three named platforms.

Industrial IT XML Step Structure Transition Logic Vendor-Neutral

Code Generation Process

From Completed FRS to Deployable DCS Code

ACM follows a structured five-step process to convert P6 FRS data into DCS code. Each step is traceable and auditable — and the entire process can be re-run whenever the FRS is updated, keeping code and specification in perfect sync.

Select DCS Vendor Target

Choose the target DCS platform from the supported vendors. The same FRS file can generate code for multiple targets — useful for validation or multi-vendor projects.

Map User CM/CCM Library to DCS Library

The User CM and CCM modules from P5/P6 are mapped to the corresponding function blocks or module types in the selected DCS vendor library. This mapping is done once per project.

Generate CDL Detailed Design Specification (DDS)

ACM reads the complete P6 FRS — C5 matrix, B1 I/O, B2 root tags, B4 alarms, C2 steps, C4 transitions — and compiles the CDL DDS as an intermediate structured representation.

Generate DCS Code from DDS

The CDL DDS is translated into the selected DCS vendor's code format — step logic, phase definitions, I/O channel assignments, setpoints, alarm definitions, and all associated configuration data.

Generate DCS Detailed Design Specification

A DCS-specific DDS is produced alongside the code — documenting every generated element in the target vendor's terminology for handover to the commissioning team and site records.

ACM Generated Outputs per UM

Step Logic Code

Complete SFC/step module for each UM step — entry actions, active actions, exit actions

Transition Condition Code

All step-to-step transition logic — tag comparisons, timers, logical combinations

CCM Module Instantiation

All CM and CCM modules instantiated with correct I/O assignments and root tag mapping

Setpoint Definitions

All setpoints, ramp rates, and operational limits from FRS B3/B4 applied to each CCM per step

Alarm Definitions

All alarm tags, priorities, setpoints, and suppression logic from FRS B4 in DCS format

DCS Detailed Design Specification

Complete DCS-specific DDS documentation — every generated element recorded for commissioning handover

End-to-End Traceability

Every Line of Code Traceable to its Source SOP

One of ACM's most significant value propositions — especially for regulated industries — is the unbroken chain of traceability from the original Standard Operating Procedure through to every line of deployed DCS code.

Because each stage of the CDL pipeline produces structured, referenced data that the next stage consumes, ACM can produce a complete traceability matrix linking each code element back through the FRS, URS, p-Code, and all the way to the original SOP narrative.

This level of traceability is essential for pharmaceutical, chemical, and nuclear process industries where automation systems must be validated and audited against documented requirements.

Traceability Chain — SOP to DCS Code

SOP Standard Operating Procedure Source narrative

↓

P4 CDL p-Code & Step Actions XML export

↓

P5 URS — Requirements Document A3 SOP, A5 Steps

↓

P6 FRS — C5 CCM Step Matrix C7 Code output

↓

P7 ACM — Generated DCS Code Deployed to DCS

Every element in the generated code references its P6 FRS source — step ID, CCM module, tag, or transition condition. The complete traceability matrix is included in the DCS DDS output.

Pipeline Complete

From Plant Assessment to Deployed DCS Code — Seven Steps

ACM is the final step in the CDL pipeline. Every phase from P1 to P7 has contributed to this moment — the deployment of fully specified, traceable, ISA‑106-compliant DCS code generated directly from your SOP library.

Plant Assessment

IPA

Level of Automation

LOA

Trend Builder

OTB

SOP Converter

SOP

URS Builder

URS

FRS Engine

FRS

Automatic Code Maker

ACM — Deploy

Licensing

Purchase ACM

ACM is available via our online store or by invoice. It is typically licensed together with P6 FRS Engine — service engagements covering P6 + P7 are available for teams implementing their first ACM code generation project.

Option 1 — Recommended

Purchase via Online Store

Browse and purchase ACM directly through our Sellfy store. Instant access after payment.

Click Buy Now or visit the store
Select ACM Engine and add to cart
Proceed to checkout and complete purchase
Download link sent immediately after payment

Go to Store

Option 2 — Invoice

Purchase Directly from Us

For corporate procurement requiring a formal invoice with bank transfer details.

Select ACM Engine in the store and capture your cart
Email product list to sales@CtrlDesigner.com
We prepare and send a formal invoice with bank details
Send payment to our bank account

Email Sales

Request a 30‑Minute Zoom Demo

A comprehensive presentation of the full ACM package — including a live FRS-to-code generation walkthrough for a sample UM — is available by Zoom. Contact us at info@CtrlDesigner.com with your company email.

Request Demo

AutomaticCode Maker™