Showing posts with label Control module. Show all posts
Showing posts with label Control module. Show all posts

Monday, 8 December 2008

The Next WBF topic

I see that the next WBF is dedicated to “Expanding the horizons of manufacturing”.
That leaves plenty of scope in North Carolina I guess. I was going to suggest "Manufacturing models for a Sustainable future", maybe for the the next one. Or perhaps it fits in with expanding out horizons, so I hope those who are currently working on their presentations for the North Carolina conference will consider the issues in their papers.
I know that we are in a global economic crisis, for maybe a few years. Economic models have long process lags. But the process I am talking about when I refer to the future is much slower moving. And it is one of the areas where those involved in manufacturing can help, from minimising energy consumption to using sustainable resources. Even a control module, such as an agitator or pump can be controlled in ways that save energy, higher up the levels more can be done. I am sure that the forum can find many people with great things to say on the topic.

Monday, 13 October 2008

Alarms and Equipment States


How many reports on hazardous incidents have you read about where the alarms presented to the operators were excessive and the resulting confusion contributed to the incident.

I was reminded by this article

Why Is Safety so HARD?

The problem has been known and understood for decades, and now we all know that alarms should be suppressed when they are not relevant, and that when they are they should be prioritised.

But engineering a solution is time consuming and expensive.

The solution has to be specified, reviewed and approved, and maintained as operating experience is gained and the solution is modified, via an approved change process of course.

Typically these are described by text, cause and effect matrices and logic diagrams.  

Mostly the cause and effect matrices describe the responses to potential hazardous events, such as process upsets. The matrices do not often cover the alarms, although some do mention them typically in notes. Some control system actually support Cause and Effect matrix based design, and can translate them into control logic. For example Siemens has one

These are much more constrained than the typical excel version that people produce.

 

Using a state model provides a highly efficient way to define the enabling of alarms. The safety system, as a complete entity is defined in terms of possible states, a method that vastly reduces the number of states that have to be considered.

Then each possible alarm can be considered for it relevance in each state, producing an Alarm State Matrix. 




Tuesday, 26 August 2008

Equipment Heavy,Recipe 'Lite'

A friend commented privately about my blog that it is equipment heavy. 

I take that as a compliment, it is my hope that this blog, and my software will help to improve Equipment Control.

I think he also means that the blog is Recipe 'Lite', so it's time to talk more about how I view the Recipe and Procedural side of Control.

I am sure that good equipment control makes recipes simpler. And Recipes Can Be Simple (or Lite). 
And intrinsically I think they are and I think that the S88 originators (and it goes back long before S88) knew that.

A recipe describes how to make stuff given some equipment.

A recipe does not care how to control equipment, it does not even need to define the chemistry, which means that it can be described very easily. And as Part 1 says, a Procedure should be essentially an Ordered Set - or sequence.

It is the sort of thing that operators have done for many decades.

Please readers, when you see anything that claims S88 compliance or benefits or profits or whatever, remember that S88 is not about how to program a control system.

Saturday, 16 February 2008

Control modules

And how great control modules are pure S88.
Control modules know nothing about the stuff you are making. They do not even know how stuff might be made. Part 1 is clear about that, as the recipe has no interface with control modules.
That does not mean that they cannot do a lot, in fact they are the bedrock of any application. The better they are, the easier the rest is.
'Primitive' Control Modules handle the Inputs and Outputs, from the plant and the operator and from higher levels in the system. They then make sense of it, setting and monitoring the state of the physical equipment that is connected the to IO and driving things like Faceplates.
Primitive Control Modules can be quite intricate, and supposedly simple things like motors can have a surprising number of states and parameters. They are little models in theselves.
Higher level Control Modules such as a PID loop or a one that handles a valve cluster also have states and parameters etc. They may even have sequences to move from one state to another or to perform a cyclic function. Some S88 practitioners choose to all these sequences 'Phases'.
I don't like to, but that is another story that I will return to.
I also use Control Modules for things like resource management - take a look at this Cyclic Request Handler . This is a small simple module to share a common resource among a number of users. These request the resource via a boolean flag, like holding your hand up in class.
They remove that flag when their demand no longer exists. The Module just looks at each in turn, and supplies if the 'hand is up'
The method guarantees First come at most Nth Served where N is the number of users. It is easy state control and avoids needing any form of queue and could easily be implemented in a PLC. Is it a Control Module? If not what is it? I hope Part 5 will find a space for it, and not a procedural one, as it does not need to know anything about making stuff!