Relating a Language to Process Control

Process Control applications were traditionally implemented as part of the basic support for the associated control equipment, without special extra cost to the user. As a consequence, there was an incentive to develop a general practice that was clear, effective, quickly implemented, and cheap. In parallel many processes are the result of separate process contractor design organizations, which also favor simple standardized designs and design practices. More recently the industry has evolved to separate design charges and even consultants that carry out that design effort, removing some of the former discipline.

Process Control has evolved beyond the continuous feedback control (and relay logic control) which represented a large part of this early practice. These newer dimensions are now often implemented using conventional computer programming practices. The Control Idiom (as developed here) was invented as a way of formalizing the traditional approach to continuous feedback control, both for clarity and to support integration of this function with the other newer aspects of Process Control. Traditional practice provided the Idioms the kind of completeness and uniformity needed to support a full blown Intent Based Programming structure. The complete proposed Language uses other strategies for clarifying those newer dimensions of the practice not subject to the desired level of formalization:

ICL Example

Idiom Statement