Improving lifecycle query in integrated toolchains using linked data and MQTT-based data warehousing

The development of increasingly complex IoT systems requires large engineering environments. These environments generally consist of tools from different vendors and are not necessarily integrated well with each other. In order to automate various analyses, queries across resources from multiple tools have to be executed in parallel to the engineering activities. In this paper, we identify the necessary requirements on such a query capability and evaluate different architectures according to these requirements. We propose an improved lifecycle query architecture, which builds upon the existing Tracked Resource Set (TRS) protocol, and complements it with the MQTT messaging protocol in order to allow the data in the warehouse to be kept updated in real-time. As part of the case study focusing on the development of an IoT automated warehouse, this architecture was implemented for a toolchain integrated using RESTful microservices and linked data.Comment: 12 pages, worksho

Using formal methods to develop WS-BPEL applications

In recent years, WS-BPEL has become a de facto standard language for orchestration of Web Services. However, there are still some well-known difficulties that make programming in WS-BPEL a tricky task. In this paper, we firstly point out major loose points of the WS-BPEL specification by means of many examples, some of which are also exploited to test and compare the behaviour of three of the most known freely available WS-BPEL engines. We show that, as a matter of fact, these engines implement different semantics, which undermines portability of WS-BPEL programs over different platforms. Then we introduce Blite, a prototypical orchestration language equipped with a formal operational semantics, which is closely inspired by, but simpler than, WS-BPEL. Indeed, Blite is designed around some of WS-BPEL distinctive features like partner links, process termination, message correlation, long-running business transactions and compensation handlers. Finally, we present BliteC, a software tool supporting a rapid and easy development of WS-BPEL applications via translation of service orchestrations written in Blite into executable WS-BPEL programs. We illustrate our approach by means of a running example borrowed from the official specification of WS-BPEL

Consuming Web Services on Mobile Platforms

Web services are an emerging technology that provides interoperability between applications running in different platforms. The Web services technology provide the best approach to Service Oriented Architecture envision of component collaboration for better business re-quirements fulfilment in large enterprise systems. The challenges in implementing Web services consuming clients for low-resources mobile devices connected through unreliable wireless connections are delimited. The paper also presents a communication architecture that moves the heavy load of XML-based messaging system from the mobile clients to an external middleware component. The middleware component will act like a gateway that lightly com-municates with the device in a client-server manner over a fast binary protocol and at the same time takes the responsibility of solving the request to the Web service.Web Services, SOA, Mobile Computing, Mobile Devices

Achieving manufacturing excellence through the integration of enterprise systems and simulation

This paper discusses the significance of the enterprise systems and simulation integration in improving shop floor’s short-term production planning capability. The ultimate objectives are to identify the integration protocols, optimisation parameters and critical design artefacts, thereby identifying key ‘ingredients’ that help in setting out a future research agenda in pursuit of optimum decision-making at the shop floor level. While the integration of enterprise systems and simulation gains a widespread agreement within the existing work, the optimality, scalability and flexibility of the schedules remained unanswered. Furthermore, there seems to be no commonality or pattern as to how many core modules are required to enable such a flexible and scalable integration. Nevertheless, the objective of such integration remains clear, i.e. to achieve an optimum total production time, lead time, cycle time, production release rates and cost. The issues presently faced by existing enterprise systems (ES), if properly addressed, can contribute to the achievement of manufacturing excellence and can help identify the building blocks for the software architectural platform enabling the integration