<?xml version="1.0" encoding="ISO-8859-1"?><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<front>
<journal-meta>
<journal-id>0012-7353</journal-id>
<journal-title><![CDATA[DYNA]]></journal-title>
<abbrev-journal-title><![CDATA[Dyna rev.fac.nac.minas]]></abbrev-journal-title>
<issn>0012-7353</issn>
<publisher>
<publisher-name><![CDATA[Universidad Nacional de Colombia]]></publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id>S0012-73532010000300021</article-id>
<title-group>
<article-title xml:lang="en"><![CDATA[TOWARDS MODULAR AND COORDINATED MANUFACTURING SYSTEMS ORIENTED TO SERVICES]]></article-title>
<article-title xml:lang="es"><![CDATA[HACIA UM SISTEMA DE MANUFACTURA MODULAR Y COORDINADO CON ORIENTACIÓN A SERVICIOS]]></article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname><![CDATA[GARCIA MELO]]></surname>
<given-names><![CDATA[JOSÉ ISIDRO]]></given-names>
</name>
<xref ref-type="aff" rid="A01"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname><![CDATA[JUNQUEIRA]]></surname>
<given-names><![CDATA[FABRÍCIO]]></given-names>
</name>
<xref ref-type="aff" rid="A02"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname><![CDATA[EIGI MIYAGI]]></surname>
<given-names><![CDATA[PAULO]]></given-names>
</name>
<xref ref-type="aff" rid="A03"/>
</contrib>
</contrib-group>
<aff id="A01">
<institution><![CDATA[,University of Valle  ]]></institution>
<addr-line><![CDATA[ ]]></addr-line>
</aff>
<aff id="A02">
<institution><![CDATA[,University of São Paulo Escola Politécnica ]]></institution>
<addr-line><![CDATA[São Paulo ]]></addr-line>
<country>Brazil</country>
</aff>
<aff id="A03">
<institution><![CDATA[,University of São Paulo Escola Politécnica ]]></institution>
<addr-line><![CDATA[ ]]></addr-line>
</aff>
<pub-date pub-type="pub">
<day>00</day>
<month>09</month>
<year>2010</year>
</pub-date>
<pub-date pub-type="epub">
<day>00</day>
<month>09</month>
<year>2010</year>
</pub-date>
<volume>77</volume>
<numero>163</numero>
<fpage>201</fpage>
<lpage>210</lpage>
<copyright-statement/>
<copyright-year/>
<self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_arttext&amp;pid=S0012-73532010000300021&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_abstract&amp;pid=S0012-73532010000300021&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://www.scielo.org.co/scielo.php?script=sci_pdf&amp;pid=S0012-73532010000300021&amp;lng=en&amp;nrm=iso"></self-uri><abstract abstract-type="short" xml:lang="en"><p><![CDATA[Nowadays, there is a trend for industry reorganization in geographically dispersed systems, carried out of their activities with autonomy. These systems must maintain coordinated relationship among themselves in order to assure an expected performance of the overall system. Thus, a manufacturing system is proposed, based on "web services" to assure an effective orchestration of services in order to produce final products. In addition, it considers special functions, such as teleoperation and remote monitoring, users' online request, among others. Considering the proposed system as discrete event system (DES), techniques derived from Petri nets (PN), including the Production Flow Schema (PFS), can be used in a PFS/PN approach for modeling. The system is approached in different levels of abstraction: a conceptual model which is obtained by applying the PFS technique and a functional model which is obtained by applying PN. Finally, a particular example of the proposed system is presented.]]></p></abstract>
<abstract abstract-type="short" xml:lang="es"><p><![CDATA[Actualmente, una tendencia es la reorganización industrial en sistemas geográficamente dispersos, en la ejecutando sus actividades con autonomía. Estos sistemas deben establecer relaciones coordinadas a fin de asegurar el funcionamiento general del sistema. Así, este trabajo propone un sistema de manufactura basado en "web service" para asegurar una efectiva orquestación de servicios para producir productos finales. Adicionalmente, es considerado funciones especiales, tales como teleoperación y el monitoreo remoto, solicitaciones online de usuarios, entre otras. Considerando el sistema propuesto como un sistema a eventos discretos (DES), técnicas derivadas de la rede de Petri (PN), incluyendo las de Production Flow Schema (PFS), pueden ser utilizadas en un abordaje PFS/PN para modelado. El sistema es abordado en diferentes niveles de abstracción: uno conceptual, el cual es obtenido aplicando técnicas PFS, y un modelo funcional, el cual es obtenido aplicando PN. Finalmente, el trabajo presenta un ejemplo del sistema propuesto.]]></p></abstract>
<kwd-group>
<kwd lng="en"><![CDATA[manufacturing system]]></kwd>
<kwd lng="en"><![CDATA[distributed system]]></kwd>
<kwd lng="en"><![CDATA[web service]]></kwd>
<kwd lng="en"><![CDATA[teleoperation]]></kwd>
<kwd lng="es"><![CDATA[Sistema de manufactura]]></kwd>
<kwd lng="es"><![CDATA[sistema distribuído]]></kwd>
<kwd lng="es"><![CDATA[Web Service]]></kwd>
<kwd lng="es"><![CDATA[teleoperacion]]></kwd>
</kwd-group>
</article-meta>
</front><body><![CDATA[ <p align="center"><b><font size="4" face="Verdana, Arial, Helvetica, sans-serif">TOWARDS   MODULAR AND COORDINATED MANUFACTURING SYSTEMS ORIENTED TO SERVICES </font></b></p>     <p align="center"><i><b><font size="3" face="Verdana, Arial, Helvetica, sans-serif">HACIA   UM SISTEMA DE MANUFACTURA MODULAR Y COORDINADO CON ORIENTACI&Oacute;N A SERVICIOS </font></b></i></p>     <p align="center">&nbsp;</p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>JOS&Eacute; ISIDRO GARCIA MELO </b>    <br>   <i>Mechanical Engineering School, University of Valle, Cali, Colombial. <a href="mailto:Jose.i.garcia@correounivalle.edu.co">Jose.i.garcia@correounivalle.edu.co</a></i> </font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>FABR&Iacute;CIO JUNQUEIRA </b><i>    <br>   Escola Polit&eacute;cnica, University of São Paulo, São Paulo, Brazil. <a href="mailto:fabri@usp.br">fabri@usp.br</a></i> </font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>PAULO EIGI MIYAGI </b><i>    <br>   Escola Polit&eacute;cnica, University of São Paulo, São Paulo, Brazil.</i> <i><a href="mailto:pemiyagi@usp.br">pemiyagi@usp.br</a></i></font></p>     <p align="center">&nbsp;</p>     ]]></body>
<body><![CDATA[<p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Received for review September 23<sup>th</sup>, 2009, accepted March 2<sup>th</sup>, 2010, final version April, 7<sup>th</sup>, 2010</b></font></p>     <p>&nbsp;</p> <hr>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>ABSTRACT:</b> Nowadays, there is a trend for industry reorganization in   geographically dispersed systems, carried out of their activities with autonomy.   These systems must maintain coordinated relationship among themselves in order   to assure an expected performance of the overall system. Thus, a manufacturing   system is proposed, based on "web services" to assure an effective   orchestration of services in order to produce final products. In addition, it   considers special functions, such as teleoperation and remote monitoring,   users' online request, among others. Considering the proposed system as   discrete event system (DES), techniques derived from Petri nets (PN), including   the Production Flow Schema (PFS), can be used in a PFS/PN approach for   modeling. The system is approached in different levels of abstraction: a   conceptual model which is obtained by applying the PFS technique and a   functional model which is obtained by applying PN. Finally, a particular   example of the proposed system is presented.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>KEYWORDS:</b> manufacturing system, distributed   system, web service, teleoperation.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>RESUMEN:</b> Actualmente,   una tendencia es la reorganizaci&oacute;n industrial en sistemas geogr&aacute;ficamente   dispersos, en la ejecutando sus actividades con autonom&iacute;a. Estos sistemas deben   establecer relaciones coordinadas a fin de asegurar el funcionamiento general   del sistema. As&iacute;, este trabajo propone un sistema de manufactura basado en <i>"web service"</i> para asegurar una efectiva   orquestaci&oacute;n de servicios para producir productos finales. Adicionalmente, es   considerado funciones especiales, tales como teleoperaci&oacute;n y el monitoreo   remoto, solicitaciones online de usuarios, entre otras. Considerando el sistema   propuesto como un sistema a eventos discretos (DES), t&eacute;cnicas derivadas de la   rede de Petri (PN), incluyendo las de Production Flow Schema (PFS), pueden ser   utilizadas en un abordaje PFS/PN para modelado. El sistema es abordado en   diferentes niveles de abstracci&oacute;n: uno conceptual, el cual es obtenido   aplicando t&eacute;cnicas PFS, y un modelo funcional, el cual es obtenido aplicando   PN. Finalmente, el trabajo presenta un ejemplo del sistema propuesto.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>PALABRAS CLAVE:</b> Sistema   de manufactura, sistema distribu&iacute;do, <i>Web   Service</i>, teleoperacion. </font></p> <hr>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>1. INTRODUCTION</b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Recently,   the demands on manufacturing enterprises have strongly increased to face global   competitiveness and to obtain a quickly response</font> <font size="2" face="Verdana, Arial, Helvetica, sans-serif">to   changes in customer requests. As a result, these enterprises are continuously   reviewing and updating their structures to improve their flexibility,   reconfigurability and interoperability &#91;1&#93;. In general, the new structures need   to deal with heterogeneous systems and their communication   incompatibility. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif"> It due to the diversity of involved resources   (devices, protocols, programs) implement in the manufacturing process. This increases the complexity of the overall system. Thus, specialists indicate a modular approach   based on the definition of functionalities &#91;2&#93;. Here, the term functionality   represents a set of operations in the same scope. In this sense,   service-oriented architecture (SOA) has emerged as a way to implement distributed computing system, where a functionality of each module can be requested from   other modules as a service, either locally or remotely, over   a     communication   network &#91;3&#93;. </font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Web   service (WS) is an instance of this architecture &#91;2&#93;. It relies on a set of   standards including: simple object access protocol (SOAP), web services   description language (WSDL), and universal description, discovery and   integration (UDDI) to support autonomy and interoperability among applications   developed in different languages and running on different platforms or   operating systems &#91;4&#93;. &#91;5&#93;   presents an architecture for the integration of WS devices with enterprise applications. &#91;2&#93; summarizes different implementations of   service-oriented systems in industrial applications such as: manufacturing and   logistic system, train car management system, control system for semiconductor   processing equipment. In this context, coordinated teleoperated systems have arisen as an alternative solution   to meet actual demands, such as structural flexibility, autonomy,   interoperability, among others. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">These   systems encapsulate several productive modules that work coordinately in an   autonomous    way    to   produce a final product. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">These   modules can be installed in a distributed and geographically dispersed  configuration  &#91;6&#93;. In this context, this research presents   architecture for the integration and coordination of manufacturing systems in a   service-oriented approach. The characterization of this architecture can be   divided into two main steps. First, the plants and set of machines that compose   the manufacturing system must be structured as modules, and their functional   operations are grouped according their functionality that represents the module   service. In this sense, a module can offer several services. Second, in   accordance to the overall manufacture process (to produce a final product), a   service is defined to integrate and coordinate different manufacturing system   modules involved. The resulting system is called coordinated teleoperative   manufacturing system (CTMS). In other words, it defines a hierarchical structure   to reach a service orchestration of manufacturing modules. In fact, this system   is being implemented based on an advanced Internet infrastructure provided by   the FAPESP TIDIA/KyaTera program &#91;7&#93;. This program considers a collaborative   environment based on a Fiber-to-the-Lab network with at least 1.2 Gbps-speed   average. This research addresses the   problem of characterization of CTMS with remote monitoring and control of   manufacturing processes without time constraint. In this sense, initially, the   solution adopted in this work considers a coordinated transnational   architecture. The proposal also considers new challenges for the monitoring and   teleoperation of the different activities involved with coordinated,   distributed and dispersed manufacturing systems. The term teleoperation   represents a human operators' support in situations such as: conflicts   arbitration, definition of productive activities to be executed, among others.   Nonetheless, the CTMS involves different kinds of functions and activities, and   their    modeling    and   analysis   are  not trivial. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Therefore,   a procedure for CTMS characterization is presented here. The characterization   task is based on the specification of CTMS as a discrete event system (DES);   then, techniques derived from interpreted Petri net (PN) are considered for   system modeling, and analysis &#91;8&#93;. PN is a graphical and mathematical modeling   technique, characterized by their ability to handle operation sequence,   parallelism, conflict and mutual exclusion &#91;9&#93;. PN has been used for modeling   dynamic systems in a wide range of areas. In &#91;10&#93;, an environment for   distributed modeling and simulation of productive system was proposed. In &#91;11&#93;,   it was used to specify a distributed system protocol. In &#91;12&#93;, a technique   based on PN called "open workflow net" is presented, which simplifies the WSs   definition, integration,  and   coordination. In &#91;13&#93;, open workflow nets are   used to represent both basic and structured activities of standard coordination   of WSs, called business process execution language (BPEL). </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">This   work is organized as follows. In section 2, the framework adopted for the   development of this work is described. Section 3 presents the proposal for the   CTMS modeling procedure. In section 4, an example illustrates the proposed   procedure. Finally, in section 5, the main conclusions are presented.</font></p>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>2. ARCHITECTURE DESCRIPTION</b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   architecture considered is based on SOA, promoting interactions among   customers, teleoperator, and resources involved in a distributed manufacturing   system, as shown in <a href="#fig01">Fig. 1</a>.</font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig01"></a><img src="/img/revistas/dyna/v77n163/a21fig01.gif">    <br>   Figure 1. </b>Architecture for coordinated teleoperative manufacturing systems (CTMS)</font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "customers"</i> are people who have access to the system by the <i>customer´s</i> <i>interface</i> with an identification and password. Also, users can   check the production order status, cancel orders, and make new orders. Order is   the customers' request execution.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "request manager"</i> <i>service</i> is a WS that exposes the   functionality to manage customer requests. In fact, it interacts with the <i>"customer´s interface"</i>, the <i>"integration and coordination"</i> <i>service</i>, and other entities such as <i>"database"</i> and <i>"request observer"</i> in order to schedule the <i>"customer"</i> requests. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "request observer" </i>ensures that the number of customer orders   being processed do not exceed the number of resources available in the CTMS. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "database of CTMS" </i>is an entity that stores information   about: <i>"customers"</i>, <i>"customer"</i> requests, tracking <i>"customers"</i> requests. This information   allows scheduling <i>"customer"</i> requests   and tracks their execution. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "integration and coordination"</i> <i>service</i> is a WS that orchestrates the involved WSs to produce a final product.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The <i>"teleoperative manufacturing system"</i> <i>service</i> exposes each manufacturing system module of CTMS. This   service encapsulates several components, such as: <i>"teleoperative productive system"</i> <i>service</i>, <i>"teleoperators", "teleoperator´s   interface"</i>, <i>"teleoperative"</i> <i>service</i>, <i>"supervisory control"</i>, <i>"local   control"</i>, <i>"database of system module"</i> and <i>"devices"</i>.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "teleoperative productive system"</i> <i>service</i> is a WS. It exposes the productive   functionality of manufacturing system module that represents its service, and   enables a loosely interaction, by command messages, between the manufacturing   module and the <i>"integration coordination"</i> service.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "teleoperators"</i> are special users that interact by the <i>"teleoperator´s interface"</i>. They can   choose between two operational modes for the <i>"devices"</i> under their responsibility: teleoperation or monitoring   modes. Teleoperation mode means that the <i>"teleoperator" </i>can interact with the <i>"devices"</i> from a remote location to decide about their next actions. On the other hand,   in the monitoring mode, <i>"teleoperators"</i> are passive elements, and the decisions are previously programmed in the<i> "teleoperative"</i> service.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The <i>"teleoperative" service</i> is a WS which exposes the teleoperation   functionality. It permits <i>"teleoperators</i>",   geographically dispersed, to manage the execution productive process. In this   sense, a loose interaction between <i>"supervisory   control"</i> and <i>"teleoperators"</i> allows managing the execution of  the   module   productive     process. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "supervisory control"</i> is a task controller that interacts with the <i>"teleoperative productive system"</i> <i>service</i>,<i> "teleoperative" service</i>, and <i>"local   control"</i>, to manage the productive activities,   according   to  the  operational mode. </font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "local control"</i> contains a set of functional blocks, each one   responsible for executing a productive activity. The <i>"supervisory control"</i> requires these functional blocks to assure the normal productive process   performance. In this sense, several <i>"local   control"</i> modules can be controlled  by  the  same <i>"supervisory control".</i> </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "database of system module"</i> is the entity that stores information   about each manufacturing system module, such as: execution of module productive   process, "<i>devices", </i>and <i>"tele-operators"</i>. This information is   used in all the process steps, for example, to estimate process time and   maintenance time. Moreover, its main purpose is to be a gateway between fast   Internet operations (activities that take milliseconds or seconds to be   performed) and productive operations (activities that take minutes or hours to   be performed). The characterization of database is out of scope due the fact   that temporal  constraints   are   not  considered here. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The<i> "devices" </i>are control elements at shop floor level such as sensors   and actuators that allow developing   manufacturing activities. </font></p>     <p>&nbsp;</p>     <p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>3.   MODELING PROCEDURE APPROACH </b></font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   procedure is divided into two parts. The aim of the first one is modeling and   analysis procedure to define the services, or functionalities perfectly   defined, of autonomous sub-systems (modules) that integrate the CTMS. This part   of the procedure is composed of five stages (<a href="#fig02">Fig. 2</a>).</font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig02"></a><img src="/img/revistas/dyna/v77n163/a21fig02.gif">    <br>   Figure 2.</b> Procedure   to model the services of each CTMS modules</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage A1: Scope about each manufacturing   system module    <br>   At   this stage, the functional characteristics of each manufacturing system module   is identified and documented initially in an informal mode. The information   collected is used to make a preliminary analysis and to identify relevant data   from each module. In this sense, the aim here is getting knowledge about the   manufacturing system to define its limits without a formal representation.</font></p>     ]]></body>
<body><![CDATA[<p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage A2: Definition of each manufacturing   system module    <br>   The   information obtained at stage A1 is used to establish the manufacturing system   module requirements. These requirements are presented as a set of functional   operations, and are defined using UML use case diagram. In this sense, a module   service represents a set of clearly defined functional operations..</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage A3: Conceptual and functional   modeling of each manufacturing system module    <br>   The   modeling of each manufacturing system module represents all functional   operations defined through the UML use case diagrams in the pre stage. It is   systematically developed in accordance with a hierarchical approach using the   PFS/PN methodology &#91;14, 15&#93;. Initially, using the PFS, a conceptual model is   developed for each functional operation. It is mapped into the PFS activity.   Then, gradually, a refinement is conducted to obtain its detailed functional   model in an interpreted PN. To compose the PN models, the transition fusion   approach is used &#91;16&#93;.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage A4: Model analysis    <br>   Aimed   to validate and verify the functional requirements of the modules, the   functional models in PN obtained at stage A3 are submitted to a structural and   dynamic behavior analyses, based on PN properties. The properties investigated in the models are:   deadlock, stability of its dynamic behavior, existence of specified states, for   example, prohibited states, achievable and critically unreachable states, among   others. Thus, this work explores a formal analysis techniques of PN combined   with simulation techniques. Here, the software HPSim  is used in the  development of this work. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage A5: Componentization    <br>   Once   the manufacturing system module has been defined, the different activities can   be arranged, according   to   their   function,   in   components. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Next, the complementary part of the proposed procedure   is presented. The focus here is the composition and coordination of different   activity modules of the manufacturing systems that compose the CTMS. This part   of the procedure  is  carried  out in three stages (<a href="#fig03">Fig. 3</a>). </font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig03"></a><img src="/img/revistas/dyna/v77n163/a21fig03.gif">    ]]></body>
<body><![CDATA[<br>   Figure 3.</b> Procedure to   integrate and coordinate CTMS modules</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage B1: Definition of the composition and   coordination process    <br>   This stage should consider the overall production   process or, in other words, the sequence of operations from the customers'   requests to the end of the process, to obtain the final product. This sequence   of operations is exposed as a service, and for each manufacturing system module   involved in the process, a functional operation is defined. The requirements of   process flow are established using UML use case diagram for each coordinated   functional operation.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage B2: Functional modeling of   composition and coordination process    <br>   Using the PFS/PN methodology, the functional   composition and coordination model is obtained. Initially, each coordinated   functional operation is mapped into an activity defined in PFS. Afterwards,   through a refinement of the PFS model that is gradually conducted, its   functional model in interpreted PN is derived.</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage B3: Model analysis    <br>   Once the functional models of CTMS are obtained, the   structural and behavior analysis based on PN properties of these models are   conducted in order to validate and to verify if the requirements and   functionalities of CTMS are completed.</font></p>     <p>&nbsp;</p>     <p><font face="Verdana, Arial, Helvetica, sans-serif"><font size="3"><b>4.  APPLICATION   EXAMPLE </b> </font></font></p> <font face="Verdana, Arial, Helvetica, sans-serif"><font size="2">     <p>In   this example, the CTMS is composed by the following manufacturing sub-systems:   work-piece supply sub-system, work-piece inspection sub-system, pallet   transportation sub-system, and product assembly sub-system. In addition,   interfaces must be considered for teleoperators and customers interaction.   These sub-systems are treated as modules that are interconnected by a   communication network and evidently they must work coordinately to produce a customers' requested product.   This disperse manufacturing system is emulated through a flexible assembly   system installed at the University of São Paulo (USP).</p>     ]]></body>
<body><![CDATA[<p>The   "work-piece supply" module executes the service that removes a work-piece from   a buffer/magazine and puts it in a specified position in the "work-piece   inspection" module. The "work-piece inspection" module executes services   related to quality control and identification of the work-pieces physical   characteristic; the approved ones are put on a free pallet of the "pallet transportation"   module, which moves the pallet to the "product assembly" module. When a pallet   with a work-piece reaches the "product assembly" module, a robot performs   different assembly activities. The assembly service is carried out in three   stages. Initially, the work-piece is placed onto an appropriate base where the   product assembly is realized, i.e., according to the work-pieces physical   characteristics, the specified parts are assembled. After the assembly process   is over, the final product is put on a free pallet for the "pallet   transportation" module to leave the system. The type and number of products for   assembly are defined and requested by the customer via Internet. Every module   can be monitored and teleoperated via Internet. In the monitoring mode,   information of each module function is provided to its operator in order to   ensure the monitoring of remote production process execution. In teleoperation   mode, the operator can also provide a series of commands for   the  execution  of   the   production  process. </p>     <p>In   order to provide the product requested by the customers, a coordinated work is established among   the   modules   involved  in  the  CTMS. </p>     <p>Due   to the limited space available for this text, just a sample of some results is   presented here. In this sense, the "work-piece supply module" and its services   are used to illustrate the procedure    proposed    for    CTMS    modeling. </p>     <p>. Stage A1: Scope about each manufacturing   system module    <br>   The   aim of the "work-piece supply module" is to provide a work-piece for the   "work-piece inspection module". The pneumatic actuator devices need a minimum   of 6 bar (87 PSI) operating pressure, and electro-mechanical devices need a 24V   electrical energy source. Concretely, three actuators, five electro-valve and   six sensors (five magnetic, and an optic one) are  used to  carry the work-piece supply service.</p>     <p>. Stage A2: Definition of each manufacturing   system module    <br>   The   information obtained from the previous stage is used to define the work-piece   supply module behavior and functional operations. These operations are   represented in a UML use case diagram (<a href="#fig04">Fig. 4</a>). In this sense, this module   provides functional operations for the <i>"CTMS"</i> and <i>"teleoperator" </i>actors.   The <i>"CTMS"</i> can invoke the <i>"work-piece   request"</i> and the<i> "available" </i>operations.   Once the <i>"work-piece request"</i> functional operation is activated, it   calls the <i>"execution request"</i> function to develop the work-piece process. To execute the work-piece process,   the device activities are activated by the <i>"execution   activities"</i> function in accordance with the incoming signal from the <i>"telecommand   request"</i> function. Meanwhile, the <i>"available"</i> functional operation indicates the available conditions of the module to meet a   request. It consults other two functions accounting for checking the status of <i>"devices"</i> and <i>"teleoperator"</i>, i.e., <i>"device   available"</i> and <i>"teleoperator   available". </i>The <i>"teleoperator"</i> can request the <i>"teleoperator access"</i> functional operation to access the module   under his responsibility, and the <i>"telecommand   request"</i> functional operation, in which he can execute the teleoperation   activities.</p>     <p align="center"><b><a name="fig04"></a><img src="/img/revistas/dyna/v77n163/a21fig04.gif">    <br>   Figure 4.</b> Work-piece   supply module definition</p>     <p>. Stage A3: Conceptual and functional   modeling of each manufacturing system module    ]]></body>
<body><![CDATA[<br>   In <a href="#fig05">Fig. 5</a>, the refinement of the <i>"work-piece request"</i> functional operation   is shown. It presents the sequence of activities performed in the work-piece   service. Initially, the functional operation is mapped into a PFS activity.   Thus, &#91;incoming work-piece request&#93; activity is activated when a   work-piece request message is received. Then, &#91;sending execution request&#93;   activity prepares and sends a message to activate the &#91;execution request&#93; activity, which is an activity defined in   accordance with the work-piece process that executes the manufacturing tasks.   Next, a "stand by" state is instanced. Then, the &#91;incoming execution notification&#93; activity is activated when a   message from the &#91;execution request&#93; activity is received with the execution status.   Finally, the &#91;sending work-piece notification&#93; activity is executed,   sending back a message to the CTMS. </p>     <p align="center"><b><a name="fig05"></a><img src="/img/revistas/dyna/v77n163/a21fig05.gif">    <br>   Figure 5.</b> Refinement of the &#91;work-piece request&#93; activity</p>     <p><a href="#fig06">Fig.   6</a> presents the refinement of the &#91;execution   request&#93; activity. Initially, the &#91;incoming execution request&#93;   activity is activated when a request message is received. Next, a cycle of   process activity requests based on telecommand response is carried out.   Therefore, the &#91;sending a telecommand request&#93; activity prepares and sends a request message, which activates   the &#91;telecommand request&#93; activity<b>. </b>Based on the   response of telecommand, received by the &#91;incoming telecommand response&#93;   activity<i>,</i> a request message is sent   by the &#91;sending execution request&#93;.<b> S</b>tate information of shop-floor-devices,   is received by the &#91;incoming execution   notification&#93; activity after the activity execution and it is registered   by the &#91;tracking device request&#93; activity. </p>     <p align="center"><b><a name="fig06"></a><img src="/img/revistas/dyna/v77n163/a21fig06.gif">    <br>   Figure 6.</b> Refinement of the &#91;execution request&#93; activity</p>     <p>The   &#91;telecommand   request&#93; activity is   detailed in <a href="#fig07">Fig. 7</a>. It is activated when a message is received by the &#91;incoming   telecommand request&#93; activity. The requester message is   registered by the &#91;registration    telecommand   request &#93;   activity. </p> </font></font>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig07"></a><img src="/img/revistas/dyna/v77n163/a21fig07.gif">    <br>   Figure 7.</b> Refinement of the &#91;telecommand request&#93; activity</font></p> <font face="Verdana, Arial, Helvetica, sans-serif"><font size="2">     <p>Depending   on the operation mode, the activation of the &#91;monitoring mode&#93; activity or &#91;teleoperation mode&#93; activity   is selected. The register of the telecommand status is carried out by the &#91;telecommand state actualization&#93; activity. Finally, a message with the   status of telecommand is sent back by the &#91;sending telecommand response&#93; activity. </p> </font></font><font face="Verdana, Arial, Helvetica, sans-serif"><font size="2">     ]]></body>
<body><![CDATA[<p>The &#91;teleoperation mode&#93; activity is detailed in <a href="#fig08">Fig. 8a</a>. This   activity is developed concurrently with the &#91;teleoperation function&#93; activity. Therefore, its first   activity is completed by the &#91;incoming telecommand state inquiry&#93; when it receives a request message about the state of telecommand from &#91;sending telecommand state request&#93; activity.   Then, a wait state is instanced until the &#91;sending telecommand state&#93; activity prepares and sends a status response message to the &#91;incoming telecommand state response&#93; activity.   After that, it keeps waiting until the &#91;sending   telecommand authorization&#93; activity sends a telecommand message to the &#91;incoming telecommand authorization&#93; activity. </p> </font></font>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig08"></a><img src="/img/revistas/dyna/v77n163/a21fig08.gif">    <br>   Figure 8.</b> Refinement of the &#91;teleoperation mode&#93; activity</font></p> <font face="Verdana, Arial, Helvetica, sans-serif"><font size="2">     <p>At   this refinement point, a functional model is generated (<a href="#fig08">Fig. 8b</a>). In this way,   the requester transition (T1b) sends a telecommand state request message to its   paired requested transition (T1a). Similarly, the requester transition (T2a)   sends the corresponding telecommand response message    to   its   requested    transition   (T2b). </p>     <p>Finally,   the requester transition (T3b) sends a telecommand authorization message to its   paired requested transition (T3a), which received the information.</p>     <p>. Stage A4: Model analysis    <br>   Based   on PN properties, to validate and to verify the functional correctness of   work-piece supply services, the state space of the functional model is   generated. From a specific initial state (initial marking of PN) behavioral   properties of the module are verified through the state space resulting from   the transitions firing of PN. Examples of such properties are the absence of   deadlock in the supply service, the possibility of always reaching a given   state, and the delivery guarantee of a given service. The HPSim tool was used   here for the model simulation, and to validate it.</p>     <p>. Stage A5: Componentization    <br>   According   its functionality, the activities of "work-piece supply module" are classified   into five components: <i>"teleoperative   work-piece supply"</i> <i>service, "teleoperation"</i> service, <i>"supervisory   control"</i>,<i> "local control"</i>, and<i> "teleoperator´s interface"</i> (<a href="#fig09">Fig. 9</a>). </p>     <p align="center"><b><a name="fig09"></a><img src="/img/revistas/dyna/v77n163/a21fig09.gif">    ]]></body>
<body><![CDATA[<br>   Figure 9.</b> Components of the <i>"</i>work-piece supply module<i>"</i>:   (a) <i>"</i>teleoperative  work-piece supply<i>"</i> service, (b) <i>"</i>teleoperative<i>" </i>service,   (c) <i>"</i>teleoperator´s interface<i>"</i>, (d) <i>"</i>supervisory control<i>"</i>,   (e) <i>"</i>local control<i>"</i></p>     <p>The <i>"teleoperative work-piece supply"</i> <i>service </i>is a WS that exposes the productive functionality of a module as a service.   It can be accessed via communication network.</p>     <p>The <i>"teleoperation"</i> <i>service </i>is a   WS that permits a loosely interaction between <i>"supervisory control"</i> and <i>"teleoperator"</i> to set the supply process activity execution.</p>     <p>The <i>"supervisory control"</i> coordinates the execution of the supply process in   the <i>"local control"</i>, based on the information received from the <i>"teleoperator"</i>.</p>     <p>The <i>"local control"</i> defines and executes interactions with devices located   at shop-floor devices    to    develop    the   process   activities. </p>     <p>Next, the proposed procedure is applied to compose and   coordinate the services of all the modules that compose the CTMS.</p>     <p>. Stage B1: Definition of the composition,   and coordination process    <br>   In <a href="#fig10">Fig. 10</a>, the <i>"integration and coordination" service </i>definition is presented. Thus, the   composition and coordination of functionalities of different manufacturing   systems involved in the final product process are defined using the UML use   case diagram. </p>     <p align="center"><b><a name="fig10"></a><img src="/img/revistas/dyna/v77n163/a21fig10.gif">    <br>   Figure 10.</b> Definition of   "integration and coordination" service</p>     ]]></body>
<body><![CDATA[<p>At this level of abstraction, the CTMS is related with   the following actors: <i>"customers"</i>,<i> "requester observer"</i>,<i> "work-piece supply module"</i>,<i> "work-piece inspection module"</i>,<i> "pallet transportation module"</i>, and <i>"product assembly module".</i></p>     <p>The CTMS exposes the functional operations, <i>"new request register"</i> and <i>"request register inquiry",</i> allowing <i>"customers"</i> to send new product requests   and to monitor requests previously made. </p> </font></font>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The <i>"request observer" </i>requests the <i>"state   request inquiry" </i>functional   operation. If the system has productive resources to meet a costumer   request, the <i>"coordination available" </i>functional operation is used and an instance functional operation of <i>"tracking   request"</i> is activated. To   permit an incoming response message   from <i>"work-   piece supply module"</i>,  the <i>"work-piece supply response"</i> functional operation is available. In   the same way <i>"work-piece   inspection response"</i>,<i> "pallet transportation response",</i> and<i> "product assembly response"</i> operations permit an asynchronous interaction with the actors: <i>"work-piece   inspection module"</i>, <i>"pallet transportation module"</i>, and <i>"product   assembly module"</i>, respectively. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage B2: Functional modeling of   composition and coordination process    <br>   </font><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Initially,   each functional operation is mapped into a PFS activity. For instance, <a href="#fig11">Fig. 11</a> shows the <i>"work-piece supply response"</i> operation as &#91;work-piece supply response&#93; activity. It is activated when a   response message from the "work-piece supply module" is received. In this   sense, its first activity is &#91;incoming work-piece supply response&#93;. After that, the &#91;sending correlation request&#93; activity prepares and sends a request   message to validate the incoming message. </font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig11"></a><img src="/img/revistas/dyna/v77n163/a21fig11.gif">    <br>   Figure 11.</b> Definition of   the &#91;work-piece supply response&#93; activity</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Then,   the &#91;work-piece supply response&#93; activity waits for the   response. If the message is validated, the next activity, &#91;sending   working-piece inspection request&#93;<b>,</b> is activated. Finally, a register of process execution is carried   out with the activation of &#91;sending tracking request&#93; activity and sending its information   through the &#91;incoming tracking notification&#93; activity. </font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">The   functional and interpreted PN model of &#91;sending correlation request&#93;<b>, </b>&#91;incoming correlation notification&#93;<b>, </b>and &#91;correlations request&#93; activities are   shown in <a href="#fig12">Fig. 12</a>, where the requester transition (T1a) sends a correlation   request for its paired requested transition (T1b). Then, a state for preparing   the correlation is met (L2b). The incoming message is compared with the   customer request being validated. This procedure is executed in the internal   transition (T2b). The response is represented by the transitions pair (T2a,   T3b), where T3b is a requester transition to send a notification message, and   T2a is a requested transition to receive the message. </font></p>     <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b><a name="fig12"></a><img src="/img/revistas/dyna/v77n163/a21fig12.gif">    ]]></body>
<body><![CDATA[<br>   Figure 12.</b> Functional   model of &#91;sending correlation request&#93;, &#91;incoming correlation notification&#93;,   and &#91;correlations request&#93; activities</font></p>     <p><font size="2" face="Verdana, Arial, Helvetica, sans-serif">. Stage B3: Model analysis    <br>   </font><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Once   the PN functional models of CTMS are obtained, an analysis of interactions is   conduced. Considering specific scenarios, i.e., initial state (PN initial   marking), the state space is obtained. The state space allows verifying the   process definition, for example, if the process activity is properly performed,   or identifies conflicts in messages broadcast. The validation of the model is   carried out through structural analysis of the PN and simulation techniques   using the HPSim tool.</font></p>     <p>&nbsp;</p>     <p><b><font size="3" face="Verdana, Arial, Helvetica, sans-serif">5.   CONCLUSIONS </font></b></p> <font size="2" face="Verdana, Arial, Helvetica, sans-serif">     <p>Increased demand and technological advances, with   respect to hardware and information technology (as shown by the internet   infrastructure provided by the KyaTera project) encourages the adoption of more   flexible productive structures. The proposed approach considers the iterations   among teleoperators, productive resources and customers, and also the fact that   they can be geographically dispersed. Teleoperators can act in two ways: monitoring   and teleoperating. To characterize the dispersed productive system, a modeling   and analysis procedure was also proposed based on a formal tool, derived from   interpreted PN that permits validation     and   verification    of requirements. </p> </font>     <p>&nbsp;</p>     <p><b><font size="3" face="Verdana, Arial, Helvetica, sans-serif">6.  ACKNOWLEDGMENTS</font></b></p> <font face="Verdana, Arial, Helvetica, sans-serif">     <p><font size="2">The authors would like to thank the partial financial support of the   Brazilian governmental agencies CNPq,    CAPES,   and FAPESP, specially the TIDIA/KyaTera committee.</font></p>     <p>&nbsp;</p> </font>     ]]></body>
<body><![CDATA[<p><font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>REFERENCES</b></font></p> <font face="Verdana, Arial, Helvetica, sans-serif">     <!-- ref --><p><font size="2"><b>&#91;1&#93;</b> WU, B.; XI, L.-F.; and ZHUO, B.-H. Service-oriented communication architecture for automated manufacturing system integration. International Journal of Computer Integrated Manufacturing, 21 (5), 599-615, 2008.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000134&pid=S0012-7353201000030002100001&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;2&#93;</b> KOMODA, N. Service oriented architecture (SOA) in industrial systems. Proc. of IEEE Conf. on Industrial Informatics, 1, 1-5, 2006.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000135&pid=S0012-7353201000030002100002&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;3&#93;</b> ROSEN, M.; LUBLINSKY, B.; SMITH, K.T.; and BALCER, M.J., Applied SOA Service-Oriented Architecture and Design Strategies. Indiana, Wiley Publishing, 2008.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000136&pid=S0012-7353201000030002100003&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;4&#93;</b> CERAMI, E. Web Service Essentials. O'Really, 2002.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000137&pid=S0012-7353201000030002100004&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;5&#93;</b> MOREIRA, S.L.; SPIESS, P.; GUINARD, D.; KOHLER, M.; KARNOUSKOS, S.; and SAVIO, D. SOCRADES: a web service based shop floor integration infrastructure. Proc. of International Conference for Industry and Academia, Zurich, Switzerland , 50-67, 2008.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000138&pid=S0012-7353201000030002100005&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;6&#93;</b> GARCIA MELO, J.I.; JUNQUEIRA, F.; MORALES, R.A.; and MIYAGI, P.E. A procedure for modeling and analysis of service-oriented and distributed productive systems. Proc. of CASE'08 the IEEE Conf. on Automation Science and Engineering, 1, 941-946, 2008.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000139&pid=S0012-7353201000030002100006&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;7&#93;</b> TIDIA-KyaTera - Advanced Internet Program, FAPESP, Brazil. Available: <a href="http://kyatera.incubadora.fapesp.br" target="referencia">http://kyatera.incubadora.fapesp.br</a> &#91;January, 8th, 2007&#93;.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000140&pid=S0012-7353201000030002100007&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;8&#93;</b> MIYAGI, P.E. Controle Program&aacute;vel: Fundamentos do Controle de Sistemas a Eventos Discretos. São Paulo, Ed. Edgard Blücher, 1996. (In Portuguese).     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000141&pid=S0012-7353201000030002100008&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;9&#93;</b> AGUIRRE, L.A.; BRUCIAPAGLIA, A.H.; MIYAGI, P.E.; and CALDEIRA, R.H. Enciclop&eacute;dia de Autom&aacute;tica. Editora Edgard Blucher, 1, 2007.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000142&pid=S0012-7353201000030002100009&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;10&#93;</b> JUNQUEIRA, F.; and MIYAGI, P.E. A new method for the hierarchical modeling of productive systems. IFIP International Federation for Information Processing, V. 220, Information Technology for Balanced Manufacturing Systems, Ed. V. Shen, Boston: Springer, 479-488, 2006.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000143&pid=S0012-7353201000030002100010&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;11&#93;</b> KANESHIRO, P.J.I.; GARCIA MELO, J.I.; and MIYAGI, P.E. Modeling of collision resolution algorithm in Lonworks networks. Proc. of IMECE´07 the ASME International Mechanical Engineering Congress, Seattle. USA , 2007.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000144&pid=S0012-7353201000030002100011&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;12&#93;</b> MASSUTHE, P.; REISIG, W.; and SCHMIDT, K. An operating guideline approach to the SOA. Techn. Report 191, Humboldt-Universit at zu Berlin, 2005.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000145&pid=S0012-7353201000030002100012&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;13&#93;</b> LOHMANN, N. A feature-complete Petri net semantics for WS-BPEL 2.0. Proc. of FABPWS'07 the Workshop on Formal Approaches to Business Processes and Web Services, 1, 21-35, 2007.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000146&pid=S0012-7353201000030002100013&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;14&#93;</b> HASEGAWA, K.; TAKAHASHI, K.; and MIYAGI, P.E., Application of the Mark Flow Graph to represent discrete event system and system control. Trans. of the Society of Instrument and Control Engineer, 24, 67-75, 1988.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000147&pid=S0012-7353201000030002100014&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;15&#93;</b> JUNQUEIRA, F.; and MIYAGI, P.E. Modelagem e Simulação Distribu&iacute;da de Sistema Produtivo Baseados em Rede de Petri. SBA - Sociedade Brasileira de Autom&aacute;tica, 20, 1-19, 2009.     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000148&pid=S0012-7353201000030002100015&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --><!-- ref --><br>   <b>&#91;16&#93;</b> GOMES, L.; and BARROS, J. Structuring and composability issues in Petri nets modeling. IEEE Trans. on Industrial Informatics, 1, 112-123, 2005.</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[&#160;<a href="javascript:void(0);" onclick="javascript: window.open('/scielo.php?script=sci_nlinks&ref=000149&pid=S0012-7353201000030002100016&lng=','','width=640,height=500,resizable=yes,scrollbars=1,menubar=yes,');">Links</a>&#160;]<!-- end-ref --> ]]></body><back>
<ref-list>
<ref id="B1">
<label>1</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[WU]]></surname>
<given-names><![CDATA[B.]]></given-names>
</name>
<name>
<surname><![CDATA[XI]]></surname>
<given-names><![CDATA[L.-F.]]></given-names>
</name>
<name>
<surname><![CDATA[ZHUO]]></surname>
<given-names><![CDATA[B.-H.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[Service-oriented communication architecture for automated manufacturing system integration]]></article-title>
<source><![CDATA[International Journal of Computer Integrated Manufacturing]]></source>
<year>2008</year>
<volume>21</volume>
<numero>5</numero>
<issue>5</issue>
<page-range>599-615</page-range></nlm-citation>
</ref>
<ref id="B2">
<label>2</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[KOMODA]]></surname>
<given-names><![CDATA[N.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[Service oriented architecture (SOA) in industrial systems]]></article-title>
<source><![CDATA[Proc. of IEEE Conf. on Industrial Informatics]]></source>
<year>2006</year>
<numero>1</numero>
<issue>1</issue>
<page-range>1-5</page-range></nlm-citation>
</ref>
<ref id="B3">
<label>3</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[ROSEN]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
<name>
<surname><![CDATA[LUBLINSKY]]></surname>
<given-names><![CDATA[B.]]></given-names>
</name>
<name>
<surname><![CDATA[SMITH]]></surname>
<given-names><![CDATA[K.T.]]></given-names>
</name>
<name>
<surname><![CDATA[BALCER]]></surname>
<given-names><![CDATA[M.J.]]></given-names>
</name>
</person-group>
<source><![CDATA[Applied SOA Service-Oriented Architecture and Design Strategies]]></source>
<year>2008</year>
<publisher-loc><![CDATA[Indiana ]]></publisher-loc>
<publisher-name><![CDATA[Wiley Publishing]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B4">
<label>4</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[CERAMI]]></surname>
<given-names><![CDATA[E.]]></given-names>
</name>
</person-group>
<source><![CDATA[Web Service Essentials]]></source>
<year>2002</year>
<publisher-name><![CDATA[O'Really]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B5">
<label>5</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[MOREIRA]]></surname>
<given-names><![CDATA[S.L.]]></given-names>
</name>
<name>
<surname><![CDATA[SPIESS]]></surname>
<given-names><![CDATA[P.]]></given-names>
</name>
<name>
<surname><![CDATA[GUINARD]]></surname>
<given-names><![CDATA[D.]]></given-names>
</name>
<name>
<surname><![CDATA[KOHLER]]></surname>
<given-names><![CDATA[M.]]></given-names>
</name>
<name>
<surname><![CDATA[KARNOUSKOS]]></surname>
<given-names><![CDATA[S.]]></given-names>
</name>
<name>
<surname><![CDATA[SAVIO]]></surname>
<given-names><![CDATA[D.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[SOCRADES: a web service based shop floor integration infrastructure]]></article-title>
<source><![CDATA[Proc.]]></source>
<year>2008</year>
<conf-name><![CDATA[ International Conference for Industry and Academia]]></conf-name>
<conf-loc>Zurich </conf-loc>
<page-range>50-67</page-range></nlm-citation>
</ref>
<ref id="B6">
<label>6</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[GARCIA MELO]]></surname>
<given-names><![CDATA[J.I.]]></given-names>
</name>
<name>
<surname><![CDATA[JUNQUEIRA]]></surname>
<given-names><![CDATA[F.]]></given-names>
</name>
<name>
<surname><![CDATA[MORALES]]></surname>
<given-names><![CDATA[R.A.]]></given-names>
</name>
<name>
<surname><![CDATA[MIYAGI]]></surname>
<given-names><![CDATA[P.E.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[A procedure for modeling and analysis of service-oriented and distributed productive systems]]></article-title>
<source><![CDATA[Proc.]]></source>
<year>2008</year>
<conf-name><![CDATA[ IEEE Conf. on Automation Science and Engineering]]></conf-name>
<conf-loc> </conf-loc>
<page-range>941-946</page-range></nlm-citation>
</ref>
<ref id="B7">
<label>7</label><nlm-citation citation-type="book">
<collab>TIDIA-KyaTera</collab>
<source><![CDATA[Advanced Internet Program]]></source>
<year></year>
<publisher-name><![CDATA[FAPESP]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B8">
<label>8</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[MIYAGI]]></surname>
<given-names><![CDATA[P.E.]]></given-names>
</name>
</person-group>
<source><![CDATA[Controle Programável: Fundamentos do Controle de Sistemas a Eventos Discretos]]></source>
<year>1996</year>
<publisher-loc><![CDATA[São Paulo ]]></publisher-loc>
<publisher-name><![CDATA[Edgard Blücher]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B9">
<label>9</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[AGUIRRE]]></surname>
<given-names><![CDATA[L.A.]]></given-names>
</name>
<name>
<surname><![CDATA[BRUCIAPAGLIA]]></surname>
<given-names><![CDATA[A.H.]]></given-names>
</name>
<name>
<surname><![CDATA[MIYAGI]]></surname>
<given-names><![CDATA[P.E.]]></given-names>
</name>
<name>
<surname><![CDATA[CALDEIRA]]></surname>
<given-names><![CDATA[R.H.]]></given-names>
</name>
</person-group>
<source><![CDATA[Enciclopédia de Automática]]></source>
<year>2007</year>
<publisher-name><![CDATA[Edgard Blucher]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B10">
<label>10</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[JUNQUEIRA]]></surname>
<given-names><![CDATA[F.]]></given-names>
</name>
</person-group>
<collab>International Federation for Information Processing</collab>
<source><![CDATA[Information Technology for Balanced Manufacturing Systems]]></source>
<year>2006</year>
<page-range>479-488</page-range><publisher-loc><![CDATA[Boston ]]></publisher-loc>
<publisher-name><![CDATA[Springer]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B11">
<label>11</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[KANESHIRO]]></surname>
<given-names><![CDATA[P.J.I.]]></given-names>
</name>
<name>
<surname><![CDATA[GARCIA MELO]]></surname>
<given-names><![CDATA[J.I.]]></given-names>
</name>
<name>
<surname><![CDATA[MIYAGI]]></surname>
<given-names><![CDATA[P.E.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[Modeling of collision resolution algorithm in Lonworks networks]]></article-title>
<source><![CDATA[]]></source>
<year></year>
<conf-name><![CDATA[ ASME International Mechanical Engineering Congress]]></conf-name>
<conf-date>2007</conf-date>
<conf-loc>Seattle </conf-loc>
</nlm-citation>
</ref>
<ref id="B12">
<label>12</label><nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[MASSUTHE]]></surname>
<given-names><![CDATA[P.]]></given-names>
</name>
<name>
<surname><![CDATA[REISIG]]></surname>
<given-names><![CDATA[W.]]></given-names>
</name>
<name>
<surname><![CDATA[SCHMIDT]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
</person-group>
<source><![CDATA[An operating guideline approach to the SOA: Techn. Report 191]]></source>
<year>2005</year>
<publisher-loc><![CDATA[Berlin ]]></publisher-loc>
<publisher-name><![CDATA[Humboldt-Universit]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B13">
<label>13</label><nlm-citation citation-type="confpro">
<person-group person-group-type="author">
<name>
<surname><![CDATA[LOHMANN]]></surname>
<given-names><![CDATA[N.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[A feature-complete Petri net semantics for WS-BPEL 2.0]]></article-title>
<source><![CDATA[Proc.]]></source>
<year>2007</year>
<conf-name><![CDATA[ FABPWS'07 the Workshop on Formal Approaches to Business Processes and Web Services]]></conf-name>
<conf-loc> </conf-loc>
<page-range>21-35</page-range></nlm-citation>
</ref>
<ref id="B14">
<label>14</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[HASEGAWA]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
<name>
<surname><![CDATA[TAKAHASHI]]></surname>
<given-names><![CDATA[K.]]></given-names>
</name>
<name>
<surname><![CDATA[MIYAGI]]></surname>
<given-names><![CDATA[P.E.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[Application of the Mark Flow Graph to represent discrete event system and system control]]></article-title>
<source><![CDATA[Trans. of the Society of Instrument and Control Engineer]]></source>
<year>1988</year>
<volume>24</volume>
<page-range>67-75</page-range></nlm-citation>
</ref>
<ref id="B15">
<label>15</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[JUNQUEIRA]]></surname>
<given-names><![CDATA[F.]]></given-names>
</name>
<name>
<surname><![CDATA[MIYAGI]]></surname>
<given-names><![CDATA[P.E.]]></given-names>
</name>
</person-group>
<article-title xml:lang="pt"><![CDATA[Modelagem e Simulação Distribuída de Sistema Produtivo Baseados em Rede de Petri]]></article-title>
<source><![CDATA[Sociedade Brasileira de Automática]]></source>
<year>2009</year>
<numero>20</numero>
<issue>20</issue>
<page-range>1-19</page-range></nlm-citation>
</ref>
<ref id="B16">
<label>16</label><nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[GOMES]]></surname>
<given-names><![CDATA[L.]]></given-names>
</name>
<name>
<surname><![CDATA[BARROS]]></surname>
<given-names><![CDATA[J.]]></given-names>
</name>
</person-group>
<article-title xml:lang="en"><![CDATA[Structuring and composability issues in Petri nets modeling]]></article-title>
<source><![CDATA[IEEE Trans. on Industrial Informatics]]></source>
<year>2005</year>
<numero>1</numero>
<issue>1</issue>
<page-range>112-123</page-range></nlm-citation>
</ref>
</ref-list>
</back>
</article>
