complicated emulation problem

I am starting a project where we are attempting to emulate a
complicated machine.

The original machine has many modes of operation with settings that
are on/off or variable, some modes and settings affect other parts of
the system, for example if I change a mode and my speed is currently
5000rpm, it may drop to 2000rpm because of the default values for mode
changes. Setting to 10000rpm = pump y coolant, 5000rps = x coolant
500rpm = no coolant etc.

The system is also controlled by two 12" touch sensitive VGA screens.
The screens are populated with buttons, some toggle, some radio some
latching, non latching that control the machine. The screens have
many pages and levels. They, must of course, observe the rules.

There is a main display which is also configurable by the settings
etc.

==

One of the requirements is that the UI controls must be straight
forward to adapt. Also he rules of operation must also be easy to
change.

I've been looking at patterns for some inspiration and two patterns
that spring to mind are the State and Negotiator patterns.

Can anyone offer advice on how to tackle this problem, particularly
how to encapsulate the rules of operation?

Many thanks

Tim
.

Quantcast