The Track & Trace
The Track & Trace
net/publication/270214069
CITATION READS
1 769
2 authors:
Some of the authors of this publication are also working on these related projects:
Eye ball tracking based communication and mobility with paralyzed people View project
All content following this page was uploaded by Qurban A Memon on 06 January 2015.
Abstract: This paper addresses intelligent communication among device entities to solve two issues in a
distributed industrial control environment: Network related bottlenecks; and intelligent control in the presence
of real time requirements. This work attempts to address customized design, development and implementation
aspects of the Distributed Control System (DCS) for process control in an environment of intelligent field
devices and Programmable Logic Controllers (PLC). The three key components; system architecture,
configuration, network and communication parameters are presented in detail. The proposed solution
architecture consists of two layer approach: use of decentralized intelligent agents at the local process level,
and use of real time operating system at the main controller level. The problems and challenges faced by such
a customized design of DCS are discussed and possible remedies are presented.
Keywords— Distributed control, Network control system, Profibus, Intelligent agents, Profinet
Profibus-enabled
Profibus-enabled
device
device
Profibus-enabled
device
Interface
}
Ontology
develop the agent role called CF to manage cluster
DAML File(s)
directory and cluster ontology. CF
Using assistance from DAML-based ontology, the Cluster
members of the cluster are able to form clusters Directory
and communicate with other agents, as shown in Figure 3. Linking CF with DAML
Figure 2. The interaction among domain ontology,
CD and CF can be best understood using Figure 3. 1. <cluster:CF rdf:ID="theCF">
Figure 3 shows how CF gets access to DAML files 2. <cluster:agentName>"CF"</cluster:agentName>
and facilitates the common goal of the cluster. 3. <cluster:agentDescription>
4. "DCS Cluster Facilitator"
There are tools available like Jena semantic web
5. </cluster:agentDescription>
[26] that can be used to handle the Cluster 6. <cluster:locator>
Directory built using DAML, and to develop a 7. "http://dcs.ee.uaeu.ac.ae/DCS/agent/CF"
Java class “Directory”. 8. </cluster:locator>
From discussions above, the main functions of CD 9. </cluster:CF>
can be summarized, as: 10.
11. <cluster:Cluster rdf:ID="DCSCluster">
• Add the information of an agent.
12.<cluster:clusterName>"DCS"</cluster:clusterName>
• Remove the information of an agent. 13. <cluster:clusterDescription>
• Get the list of agent names of all members. 14. "Distributed Control System"
• Get the information of individual agent by 15. </cluster:clusterDescription>
name. 16. <cluster ontology>
17. "http://dcs.ee.uaeu.ac.ae/DCS/ontology/dcs.daml"
• Get ontology used by members in the cluster.
18. </cluster:ontology>
• Add external ontology if provided by an agent. 19.
Keeping this local process in perspective and 20. <cluster:hasCF rdf:Resource="#theCF"/>
using the main functions of CD, the partial 21. <cluster:consistOf rdf:Resource="#agent1"/>
directory can be described as shown in Figure 4. 22. <cluster:consistOf rdf:Resource="#agent2"/>
The Figure 4 shows information of CF (lines 1-9) 23. </cluster:Cluster>
and members of cluster (lines 20-22), the cluster
Figure 4: DCS Cluster Directory
directory also records meta-data about cluster such
as cluster name (line 12), cluster description (lines from the Figure 5 that when distributed field
13-15), ontology used in cluster (lines 16-18), and device agent joins the cluster, it informs CF about
so on. corresponding ontology it provides (Figure 5(a)).
Thus the CF maintains local process ontology plus
An Example: Here, we consider a distributed the distributed field device ontology. This means
control environment and consider how a that ontology can be updated (Figure 5(b)), when
distributed field device agent may help achieve ever any agent joins the cluster to perform a
task of a user agent. It should be reminded here common goal. When user agent wants to perform
that all members’ domain knowledge (ontology) a task, it asks CF about domain ontology and the
may not be the same, and that some agents may agents that provide external capability. In
provide knowledge of the specific field device. In response, CF informs the user agent if ontology is
fact, all agents hold basic cluster ontology (the to be acquired (Figure 5(c)). Thus, the user agent
knowledge of the local process) provided by CF, can communicate with the distributed field device
that is, for example, user agent holds basic agent (Figure 5(d)).
knowledge of the local process but does not
understand the knowledge that a distributed field 4.2 Global Process
device holds. Through DAML-based ontology, This process handles core mechanism that glues
members can communicate with other to acquire organization’s local process to main global
requested service, as shown in Figure 5. It is clear process. This process may handle many functions
for example: how library of information collecting User
agents is to be created; what do these agents do; agent
d
how do they communicate with each other; how c
deadlocks are to be removed; definition of main DCS ontology
of this process is only a technology mismatch, and kernel and runtime system security
that if only small scale changes are to be decided
at the global level like reconfiguration of device memory