Figure 2: Architecture of an agent.
If an urgent message is received, the reactive
layer will be triggered, and the agent will execute
according to the most similar rule in rules library
without thinking. The reactive rules library could be
modified in accordance with the experience
automatically.
If the message is not urgent, the agent will
‘think’ for a while about how to respond. In this
period, agent uses its special ability to process this
information and then make decision with the
consideration of mental state, knowledge and its
goal. After the agent’s action is executed, if the
action really works, the agent will record this action
as a paradigm into reactive rules library and update
the mental state, knowledge base if necessary.
When the agent finds the job got from the
message is too difficult to accomplish, three options
are available: (1) if the agent know who can help it,
it will ask for help directly to that agent; (2) if the
agent has no idea who is the right agent, it will
contact the management agent to try to organize a
cooperation coalition; (3) if no one responds its
request, abandoning the goal is its last choice.
The special capability mentioned above is the
agent’s ‘survival skill’ encapsulated in information
processing module (IPM). Different method in IPM
determines different type of agent. As shown in
figure 1, ten kinds of agent are designed in this
system:
(1) Local and remote GUI agent: local and
remote graphical user interfaces (GUI) are used by
the operator users to display monitoring and
diagnosis results, initiate diagnostic processes, give
a phonic or flaring alarm, and receive user’s
instructions locally and extendedly.
(2) Management agent: management agent is
used to decompose task and start organizing
cooperation as mentioned in section 2.1.
(3) Conflict resolution agent: a conflict
resolution mechanism is required to investigate
whether the diagnostic results, as reported by
different diagnostic agents, are contradicting or
completing each other. The diagnostic agents do not
communicate with each other to merge their
knowledge, but do report their diagnosis to a conflict
resolution agent. For this purpose, the history credit
evaluation of a diagnosis agent is important. Beyond
this, knowledge of relations among the components
and among the possible failures which may be
related within the components, need to be well
known (H.Worn 2002).
(4) Directory facilitator agent: the directory
facilitator (DF) agent is responsible for
communication and agent management. It can
provide the naming service, represent the authority
in the platform and also provide Yellow Pages
service by means of which an agent can find other
agents providing the services he requires in order to
achieve his goals. All the capabilities of the
registered monitoring and diagnostic agents and the
available CORBA functionalities are managed by
the facilitator agents.
(5) Data access agent: what data access agent can
do has discussed as an example in section 1.
(6) Clustering agent, Relative Principal Com-
ponent Analysis (RPCA) agent, Parallel Diagonal
Recurrent Neuron Network (PDRNN) agent and
Fuzzy Neural Network (FNN) agent: these agents
are dealing with monitoring and diagnosis process
which will be discussed in next section.
3 INTELLIGENT MONITORING
AND DIAGNOSIS PROCESS
Faults diagnosis for complex control system is the
process of mining valuable omen variables from
mass data collected by sensors and mapping omen
variables to faults modes. Thereby data mining plays
an important role in diagnosis. In this paper, a new
hybrid intelligent monitoring and diagnosis method
is proposed in figure 3. This method divided the
process of data mining and fault mode mapping into
several independently data fusion modules, which
are implemented by agents:
(1) Database: database is made up with two main
storage areas, which correspond to history and
online data access respectively. History data are
used for intelligent data mining, executed by
collaborated agents, and real time data are collected
by the data access agent from sensors.
Other Agent
Reactive
Rules
Information
Processing
Mental
State
Knowledge Goal
Urgent
Ambient
Not urgent
Decision
Making
Perception
Agent
Deliberation Layer
Reactive Layer
Communication
Action
A HYBRID INTELLIGENT MULTI-AGENT METHOD FOR MONITORING AND FAULTS DIAGNOSIS
157