A MULTI-AGENT SYSTEM FOR THE MANAGEMENT OF ABNORMAL SITUATIONS IN AN ARTIFICIALLY GAS-LIFTED WELL

Figures & data

FIGURE 1 SADIA model.

FIGURE 2 SCDIA model.

FIGURE 3 LAG well agent.

FIGURE 4 Abnormal situations management agent.

TABLE 1 Agent Model for the Controller Agent of the ASMS Agent for a LAG Well

Controller agent
Name	Controller
Position	Third level
Components	NA
Reference Mark	SCDIA
Description	Evaluates the well's monitored behavior, comparing it to the desired
	behavior and it is able to make recommendations for managing the
	abnormal situation.
Tasks
Name	Evaluate condition
Description	Its task is to evaluate the well's condition in order to identify abnormal
	situations and in that case recommend possible corrective actions that
	will maintain the well in the wanted conditions.
Entrance Parameters	Information about the state, countersigns
Exit Parameters	State of the well, corrective actions, plant stoppage alarms, gas and fire
	protection alarms.
Activating Condition	As the agent is created
Ending Condition	As the agent is eliminated
Success Condition	The well functions as there are no abnormal conditions
Failure Condition	There are abnormal conditions that cannot be solved.
Ontology	Abnormal situations management in a well and communication ontology.
Services
Name	Recommend corrective actions
Description	Using the information about the state and the established countersigns,
	the agent is able to recommend possible actions to take in order
	to solve the possible abnormal situations.
Entrance Parameters	Information about the state, countersigns
Exit Parameters	Recommendations of possible corrective actions
Name	Submit alarm activation order for fire and gas protection
Description	When and abnormal situation happens involving a disaster, the agent
	can send an alarm activation order so that the process of protection
	against fire and gas can get started.
Entrance Parameters	Information about the state
Exit Parameters	Fire and gas alarm activation order
Name	Send secure stoppage alarm activation order
Description	When an abnormal situation happens implying danger for the
	monitored well, the staff, or the environment, the agent can send
	an alarm activation order to initiate the secure stoppage procedure.
Entrance Parameters	Information about the state
Exit Parameters	Alarm activation order to initiate the secure stoppage

TABLE 2 Agent-Tasks Relationship

Agents	Tasks
Abnormal Situations Management Agents for a LAG Well
Observation agent	T1. Obtain information about the state
	T2. Request data to the data management agent (AGD)
	T3. Preprocessing of data coming from the process
Controller agent	T1. Diagnosis
	T2. Identification of causes
	T3. Identification of consequences
	T4. Damage degree evaluation
	T5. Changes in intonation parameters
Coordinator agent	T1. Request for the execution of characterization service
	T2. Request for the execution of detailed analysis service
Actuation agent	T1. Execution of corrective actions
	T2. Alarm status register
	T3. Changes in the state of the alarms
Analyzer agent	T1. Abnormal situation analysis
Characterizer agent	T1. Behavior characterization of the CHP variable
	T2. Behavior characterization of the THP variable
	T3. Behavior characterization of the QGI variable
	T4. Behavior characterization of the GLMNP variable

TABLE 3 Agent-Tasks-Data Manager Agent Relationship

Data manager agent	T1. Information search
	T2. Information updates
	T3. Data and communication errors management

TABLE 4 Example of the Task Model: Diagnosis Task of the Controller Agent

Task
Name	Diagnosis
Objective	Diagnose abnormal situation after realizing symptoms
Description	Abnormal situations, possible causes, and possible consequences are identified
	after the detection of symptoms
Precondition	Information about the state of the process
Subtasks	Identification of causes and consequences
Name	Identification of causes
Objective	Identify causes of abnormal situation
Description	Once the abnormal situation has been identified, it is necessary to find out
	the causes
Precondition	Abnormal situation identified
Subtasks	NA
Name	Identification of consequences
Objective	Identify consequences of an abnormal situation
Description	Once the abnormal situation has been identified, it is necessary to find out
	the possible consequences
Precondition	Abnormal situation identified
Subtasks	NA

FIGURE 5 Diagram of the sequences of the control holding conversation.

TABLE 5 Example of the Coordination Model

Conversation: Control Getting
Objectives	Determination of control actions
Agents	Observation, coordination, actuation
Initiator	Observer
Conversation acts	Obtaining information about state of the well, request for
	diagnosis agents services, execution order
Precondition	State of the process
Termination condition	Action or error execution order
Description	The object of the controller agent is to execute the necessary
	actions before an abnormal situation, for this, it interacts
	with the observer, coordinator and actuation agents.
Coordination Scheme
Following objective	To plan the interactions between the observation, coordinator,
	and actuation agents
Type	Predefined
Default coordination	Centralized through message exchange mechanisms, in order
	to relate the agents present in the conversation
Planning
Type	Predefined
Technique	There are request protocols between the observer and the
	coordinator agents
Communication Mechanism
Type	Direct
Technique	Message exchange
Meta language	Agents communication language (ACL-FIPA)
Ontology	Abnormal situations management in a LAG well, of communication

TABLE 6 Example of the Communication Model

Communicating Act: Trial Request
Name	Trial request
Type	Request
Objective	Trial request
Agents	Controller, coordinator agent
Initiator	Controller
Precondition	Request for analysis of abnormal situation
Termination condition	Acceptance of request
Conversations	Control holding
Description	The controller agent requests the coordinator agent to contact the
	analyzer agent in order to revise in detail a given abnormal situation.
Communicating Act: Execution Order
Name	Execution order
Type	Inform
Objective	Send an execution order for an action
Agents	Controller, actuation
Initiator	Controller
Precondition	Action to be executed
Termination condition	Sending of action to be executed
Conversations	Control holding, executing actions
Description	The controller agent sends an execution order of certain action to
	the actuation agent.

TABLE 7 Example of the Intelligence Model

Reasoning Mechanism
Information source	Agente de observación, Agente Coordinador, SGS
Activation source	Intervention
Inference type	Deductive
Reasoning strategy	Expert system
Learning Mechanism
Type	Adaptive
Representation technique	Rules
Learning source	Failures or success
Updating mechanism	Previous experiences are used for updating knowledge.

TABLE 8 Composing Rules of the Inference Motor of the Controller Agent

Rule Number	Rule Description
1	Determines whether the web is actually producing by the use of a flux sensor.
2	Determines when there is a difference between the sign well producing
	(obtained by rule 1) and the sentry stored well category.
3	Determines when there is a break in the production line while the web
	is operating.
4	Determines changes on the artificial lifting through comparison of the & artificially designed method with the operation method.
5	Determines when gas is being injected to a GL well.
6	Determines when a GL well is closed without authorization.
7	Determines when the gas-lifting flux is obstaculized and the well is not being
	supplied.
8	Determines a rupture in the connecting line between the multiple GL and
	the GL well while it is receiving GL gas.
9	Determines when the production line of a GL well is blocked or closed.
10	Determines a possible communication between the pipe and the coating
	in continuous GL wells.
11	Determines possible communication between the pipe and the coating in
	continuous GL wells.
12	Determines a major pipe-coating communication. A major communication
	is defined as the cause of a drastic fall in production.
13	Determines possible blocking or erosion of the merla valve.
14	Determines when there are problems with the control loop or the merla valve.
15	Determines infiltrations of the merla valve.
16	Determines problems with the gas flux at the control loop or at the actuator
	of the valve decrease.

FIGURE 6 Structure of the AMSA JAVA packages.

FIGURE 7 AMSA classes diagram.

FIGURE 8 Process flow chart.

FIGURE 9 Multi-agents platform in the applications server.

FIGURE 10 Actuation agent screen.

FIGURE 11 Alarms summary of the well CL226.