Tired of the cumbersome and tedious task of documenting DeltaV Documentation for Phase Classes, Operations and Unit Procedures?
This firm has developed a framework to overcome the tedious task of documentation of batch objects from DeltaV inport/export (FHX) files.
Editing these objects is slow, so Batch-A Tools developed a method to export straight to Excel. Then after updating in Excel they can re-import and generate new FHX files which update the objects in DeltaV. As well, batch objects can be created in Excel through references to DeltaV code snippets (e.g: a code snippet for an action to start a variable speed motor at a certain speed, including confirmation and transition, or a code snippet for actions to present the operator with a prompt with confirmation and transitions to handle different replies).
Here’s a framework which allows for storing/ retrieving batch objects in and from a SQL Server database, and the generation of CHM Files that provide an offline view of configuration.
Lets look at some existing system scenarios:
Your facility has had DeltaV installed and operating well for several years….
Are all your Named Sets documented?
How many duplicate Named Sets have your engineers and consultants created over the years?
Perhaps you’d Like to consolidate and eliminate those rogue Named Sets….
Or, you’re planning on an expansion and you’ve used all the allowable Named Sets..
Or you’ve found some misspelled Text values along the way
Are they all Class Based? If not, would you prefer that?
It’s easy enough to make those existing Phases Class Based…
But what about consistency in ALL Aspects…across ALL your Phases
Presentation within DeltaV? – Do You have Wire Spaghetti?
Step & Transition Numbering? – Sure They were Named/Numbered consistently when the system was commissioned… How about now???
Step & Transition Descriptions? – Do you even have them?, Oh and did you spell check them in DeltaV??
Actions….
Numbering? – Sure They were Named/Numbered consistently when the system was commissioned… How about now???
Execution Order… Have your Delay & Confirmation expressions become burdensome with all the additions/deletions and changes through the years
Are you performing the same function in your code several different ways?
Are you messaging and prompting Operations and Maintenance consistently? Are those messages all spelled correctly?
Parameters…This could be a Scenario all to itself..
Phase
Recipe
Report
Again some familiar questions..
Sure They were Named consistently when the system was commissioned… How about now???
Descriptions? – Do you even have them?, Oh and did you spell check them in DeltaV??
Ranges?
Initial Values?
Engineering Units?
Parameter Deferral?
Grouping?
If interested, send a note to:
Joe Fox: Joe@Batch-A.Com
864 561-0053
Or Martin van Bergeijk: Martin@Batch-A.Com
(+31)(0)183 409292
