CDL For Excel - Overview

Author

CTRL Designer LLC

1 Introduction

CTRL Designer LLC (CDL) is a leading provider of SBC state-based control (procedural control) based on ISA106 solutions to the process industries.

Its software portfolio and work processes help process control engineers develop an overall process control design and convert it automatically to the selected control system code. These solutions allow users to make smarter decisions to improve safety, reliability, efficiency, and sustainability.

The products are divided into phases:

P1- Industrial Plant Assessment™ (IPA)
P2- Level of Automation (LoA) [Service]
P3- Operating Trends for Excel™ (OT)
P4- Standard Operating Procedure Analyzer™ (SOP)
P5-URS-to-FRS-Builder-for-Excel™ (URS)
P6-FRS-Engine-for-Excel™ (FRS)
P7-ACM-Engine-for-Excel™ (ACM)

The P3- Operating Trends for Excel™ (OT) is reviewed in this section.

1.1 CDL-ISA106 work process

The CDL Work process is developed using the V-Model defined in ISA106.

Using the V-model and work process defined in ISA106, the tasks can be defined in five part

Project Identification
- Collect Data
  - P&ID
  - SOP
  - IO Database
  - Etc
- Develop User Requirement Specification (URS) per plant
- Generate a draft of Functional Requirement Specification (FRS) for each unit
Project Definition
- Finalize the Functional Requirement Specification (FRS) for each unit
Detailed Design
- Generate Detailed Design Specification (DDS) (CDL Version)
- There are two options:
  - Option A: Main Automation Contractor (MAC) to develop code
  - Option B: Generate code internally using Automatic Code Maker (ACM)
Code Development
Code Simulation

The State-Based Control development is based on two key criteria:

Development of the Mode of Operation (MofO) and Steps for the plant and its associated units.
- SBC of Plant Start-up, Run, and Shutdown Steps required to orchestrate the unit mode of operation
- The units per their mode of operation from above with drive their steps
Conversion of Standard Operation Procedure (SOP) to Actions for the Unit Steps.

2 Phase 1 - Project Identification

The project identification phase of project is to develop a package for internal review to decide if the company desire to build the selected plant.

This phase is divided into two parts and executed by the owner:

Develop the URS package, and review with project team
Develop the FRS package, and review with project team

2.1 Develop the URS package

The following tasks:

Collect data
Develop OT for Plant
Develop URS
Generate Draft FRS files

This part of the project is represented in slide below

In the above slide,:

Green rectangles represent data (xls files)
Blue circle represents CDL Engine (xlsm files)
The Table shows the which of the five engines of the CDL Tools for Excel is being used

2.1.1 Collect data

The following data should be collected

N	What	Description
1.01	P&ID	All P&ID for the UM
1.02	Narrative	AO Control Strategy Narrative
1.03	Narrative	DO Digital Strategy Narrative
1.04	P&ID-Tag-List	List of all Tags in P&ID for UM
1.05	Control Structure	AO and DO Control Strategies
1.06	Standard Operating Procedure	How to start up, run and shutdown a unit
1.07	Overview	Overview with proposed Steps/Transition
1.08	Review with operation

2.1.2 Develop OT for Plant

In first step review and customize the book of convention (BOC) (Shown as (3) )

Use the CDL-P3-Operational-Trend-Builder-for-Excel.xlsm Engine (shown as (1) ) to do:

N	What	Description
2.01	Define Plant
2.02	Divide the Plant to Units
2.03	Identify EM within UM
2.04	Define major steams connecting units (MV)
2.05	Define the MV movement defined in the (SOP)
2.06	Build Trends PA =< UM	Build Trends
2.07	Build Dynamic PA =< UM	Build Dynamic
2.08	Add Mode of Operation, PA Steps and UM Mode of Operation	Add MofO
2.09	Review with operation

2.1.3 Develop URS for Plant

Use the CDL-P5-URS-to-FRS-Builder-for-Excel.xlsm Engine (shown as (2) ):

Do the following tasks

N	What	Description
3.01	Review the following worksheets {Tasks}
3.02	A1-Process-Description	optional
3.03	A2-Process-Control-Objectives	optional
3.04	A3-Level-of-Automation	optional
3.05	A4-PA-UM-Process-Diagram	from OT
3.06	A5-Start up-Run-Shut Down	from OT
3.07	B1-Instrumentation	required
3.08	B2-PA-UM-Definition	required
3.09	B3-UM-Limits	optional
3.10	Assign UM and EM to {B1-Instrumentation}	Add information for this UM
3.11	Define UM type in {B2-PA-UM-Definition}	required
3.12	Export FRS initial files	required
3.13	Review with operation

2.1.4 Generate FRS draft files

This is shown in the slide below. The letters A,B,.. represent different UM names

2.2 Develop the FRS package

The FRS package development requires to do the following

Generate OT for a selected FRS (Say FRS A)
Review CM and CCM libraries
Adding Detail to FRS and Generating DDS

The above is represented in the slide below.

2.2.1 Generate OT for a selected FRS (Say FRS A)

Please do the following tasks

N	What	Comments
1.01	Select a Unit	Add information for this UM
1.02	Define MV, CV and DV	Add information for this UM
1.03	Add the MV movement defined in the (SOP)	Use User-MCD-Tasks
1.04	Add the CV movement defined in the (SOP)	Use User-MCD-Tasks
1.05	Add the DV movement defined in the (SOP)	Use User-MCD-Tasks
1.06	Build Trends	Build Trends
1.07	Build Dynamic	Build Dynamic
1.08	Add Mode of Operation, UM Steps	Add MofO
1.09	Review Steps	Define Unit Steps
1.10	Review with operation

2.2.2 Adding Detail to FRS and Generating DDS

The FRS files will be developed using FRS Engine and is done using the following tasks

N	What
0	Develop P3-OT-Operational-Trends for Unit
1	Part 1 – Assign IO to CCM and CM
2	Part 2 – Mode of Operation, Steps and Transitions
3	Part 3 – Build CCM-Steps Matrix
4	Part 4 – Review CCM-Steps Matrix Dynamically
5	Part 5 – Review the pCode and Dictionary
6	Part 6 – Build and Modify DSS and SOP