Communication and control in small batch part manufacturing

This paper reports on the development of a real-time control network as an integrated part of a shop floor control system for small batch part manufacturing. The shop floor control system is called the production control system (PCS). The PCS aims at an improved control of small batch part manufacturing systems, enabling both a more flexible use of resources and a decrease in the economical batch size. For this, the PCS integrates various control functions such as scheduling, dispatching, workstation control and monitoring, whilst being connected on-line to the production equipment on the shop floor. The PCS can be applied irrespective of the level of automation on the shop floor. The control network is an essential part of the PCS, as it provides a real-time connection between the different modules (computers) of the PCS, which are geographically distributed over the shop floor. An overview of the requirements of such a control network is given. The description of the design includes the services developed, the protocols used and the physical layout of the network. A prototype of the PCS, including the control network, has been installed and tested in a pilot plant. The control network has proven that it can supply a manufacturing environment, consisting of equipment from different vendors with different levels of automation, with a reliable, low cost, real-time communication facility

Floor control for multiparty sessions in 3G networks

Value-added services in telecommunication networks may be defined as anything that goes beyond two-party voice calls. This thesis focuses on the floor control issue for multiparty sessions in tomorrow's telecommunication networks. Floor Control enables the control of media streams, e.g., who can be seen and heard when more than one party is exchanging media streams over a network. Several conferencing scenarios have been studied, leading to a definition of the requirements for a generic floor control mechanism. After defining the requirements, we surveyed the related work in the literature (i.e., SIP and PARLAY) to identify whether they provide (or not) the defined requirements. Based on this evaluation, we have proposed an architecture that benefits from the available technologies and which also provides the missing parts in order to achieve a complete solution. We have identified that PARLAY as per today's specification does not fulfill all the requirements for floor control. In addition, we have identified the need for a complete solution for floor control integrating APIs with the protocols. (Abstract shortened by UMI.

Differences in hospital glycemic control and insulin requirements in patients recovering from critical illness and those without prior critical illness

INTRODUCTION: Hospital patients recovering from critical illness on general floors often receive insulin therapy based on protocols designed for patients admitted directly to general floors. The objective of this study is to compare glycemic control and insulin dosing in patients recovering from critical illness and those without prior critical illness. METHODS: Medical record review of blood glucose measurements and insulin dosing in 25 patients under general ward care while transitioning from the intensive care unit (transition group) and 25 patients admitted directly to the floor (direct floor group). RESULTS: Average blood glucose did not differ significantly between groups (transition group 9.49 mmol/L, direct floor group 9.6 mmol/L; P = 0.83). Significant differences in insulin requirements were observed between groups with average daily doses of 55.9 units in patients transitioning from the intensive care unit (ICU) versus 25.6 units in the direct floor group (P = 0.004). CONCLUSIONS: Patients recovering from critical illness required significantly larger doses of insulin than those patients admitted directly to the floor. Managing insulin therapy in patients transitioning from the ICU may require greater insulin doses

Floor Control Protocol for ALX Video Conference Application

With wide deployment of high-speed networks such as vBNS today, video-conference applications over WANs have become increasingly feasible. MMX has proven to be a good desktop video-conference devide for local ATM networks. Now, ALX has been designed to extend MMX\u27s video conferencing capability to IP-over-ATM WANs such as vBNS. In this report, we discuss a floor control protocol for ALX video-conference applications. We first show how an ideal protocol should behave to meet our requirements. Then we compare three protocols based on distributed algorithms, and a protocol based on a centralized algorithm. Based on the comparison and performance analysis, we plan to implement the protocol based on the centralized algorithm for initial test-runs. We also describe what our future work will involve

A Floor Control Server in a Distributed Conference Service

The conferencing systems in IP Multimedia (IM) networks are going through restructuring, accomplished in the near future. One of the changes introduced is the concept of floors and floor control in its current form with matching entity roles. The Binary Floor Control Protocol (BFCP) is a novelty to be exploited in distributed tightly coupled conferencing services. The protocol defines the floor control server (FCS), which implements floor control giving access to shared resources. As the newest tendency is to distribute the conferencing services, the locations of different functionality units play an important role in developing the standards. The floor control server location is not yet single-mindedly fixed in different standardization bodies, and the debate goes on where to place it within the media server, providing the conferencing service. The thesis main objective is to evaluate two distinctive alternatives in respect the Mp interface protocol between the respective nodes, as the interface in relation to floor control is under standardization work at the moment. The thesis gives a straightforward preamble in IMS network, nodes of interest including floor control server and conferencing. Knowledge on several protocols – BFCP, SDP, SIP and H.248 provides an important background for understanding the functionality changes introduced in the Mp interface and therefore introductions on those protocols and how they are connected to the full picture is given. The actual analysis on the impact of the floor control server into the Mp reference point is concluded in relation to the locations, giving basic flows, requirements analysis including a limited implementation proposal on supporting protocol parameters. The overall conclusion of the thesis is that even if both choices are seemingly useful, not one of the locations is clearly the most suitable in the light of this work. The thesis suggests a solution having both possibilities available to be chosen from in separate circumstances, realized with consistent standardization. It is evident, that if the preliminary assumption for the analysis is kept regarding to only one right place for the floor control server, more work is to be done in connected areas to discover the one most appropriate location

Interaction systems design and the protocol- and middleware-centred paradigms in distributed application development

This paper aims at demonstrating the benefits and importance of interaction systems design in the development of distributed applications. We position interaction systems design with respect to two paradigms that have influenced the design of distributed applications: the middleware-centred and the protocol-centred paradigm. We argue that interaction systems that support application-level interactions should be explicitly designed, using the externally observable behaviour of the interaction system as a starting point in interaction systems design. This practice has two main benefits: to promote a systematic design method, in which the correctness of the design of an interaction system can be assessed against its service specification; and, to shield the design of application parts that use the interaction system from choices in the design of the supporting interaction system

Enabling Communication Technologies for Automated Unmanned Vehicles in Industry 4.0

Within the context of Industry 4.0, mobile robot systems such as automated guided vehicles (AGVs) and unmanned aerial vehicles (UAVs) are one of the major areas challenging current communication and localization technologies. Due to stringent requirements on latency and reliability, several of the existing solutions are not capable of meeting the performance required by industrial automation applications. Additionally, the disparity in types and applications of unmanned vehicle (UV) calls for more flexible communication technologies in order to address their specific requirements. In this paper, we propose several use cases for UVs within the context of Industry 4.0 and consider their respective requirements. We also identify wireless technologies that support the deployment of UVs as envisioned in Industry 4.0 scenarios.Comment: 7 pages, 1 figure, 1 tabl

The role of the service concept in model-driven applications development

This paper identifies two paradigms that have influenced the design of distributed applications: the middleware-centred and the protocol-centred paradigm, and proposes a combined use of these two paradigms. This combined use incorporates major benefits from both paradigms: the ability to reuse middleware infrastructures and the ability to treat distributed coordination aspects as a separate object of design through the use of the service concept. A careful consideration of the service concept, and its recursive application, allows us to define an appropriate and precise notion of platform-independence that suits the needs of model-driven middleware application development

A Cloud Platform-as-a-Service for Multimedia Conferencing Service Provisioning

Multimedia conferencing is the real-time exchange of multimedia content between multiple parties. It is the basis of a wide range of applications (e.g., multimedia multiplayer game). Cloud-based provisioning of the conferencing services on which these applications rely will bring benefits, such as easy service provisioning and elastic scalability. However, it remains a big challenge. This paper proposes a PaaS for conferencing service provisioning. The proposed PaaS is based on a business model from the state of the art. It relies on conferencing IaaSs that, instead of VMs, offer conferencing substrates (e.g., dial-in signaling, video mixer and audio mixer). The PaaS enables composition of new conferences from substrates on the fly. This has been prototyped in this paper and, in order to evaluate it, a conferencing IaaS is also implemented. Performance measurements are also made.Comment: 6 pages, 6 figures, IEEE ISCC 201

A SOAP Web Services-Based Architecture for Floor Control in Multimedia Conferencing

Multimedia conferencing applications are an important and widely-used category of Web applications. Floor control is a significant and advanced feature of multimedia conferencing applications. Floor control mechanisms, when introduced in audio/video conferencing, control the media streams such as identifying which participant is allowed to send and who can be seen or heard. This prevents conflict and ensures an optimized use of resources between the conference participants. Floor control is composed of three logical entities: a single floor control server (i.e. entity responsible for managing the floors and their status), one or more floor chairs (moderators), and any number of regular conference participants. This thesis proposes a SOAP Web services based architecture for floor control in multimedia conferencing. Web services are designed to support interoperable machine-to-machine interaction over a network. They are attractive because of their flexibility. There are two types of web services: SOAP Web services and RESTful Web services. In SOAP Web services, interactions between the entities are based on XML and use SOAP, which is embedded in HTTP. RESTful web services are an architectural design style that rely on HTTP, but do not use SOAP. XML is also optional. We propose a set of floor control requirements and use them to review the related work and pinpoint the weaknesses. The proposed architecture includes the main components of floor control. It also includes a comprehensive set of server-side and client-side SOAP web service APIs that expose the floor control capabilities to application developers. The proposed APIs are programming language-independent and provide a higher level of abstraction to the application developers, which enables the interoperability. Furthermore, in the proposed architecture the floor control clients do not interact directly with the floor control server (FCS) but through a gateway accessible using SOAP web services. This opens up the possibility to use different floor control protocols transparently to the floor control clients. Application portability is no longer a problem because floor clients access the floor capabilities independently of the protocol supported by the FCS. We have built a conferencing application with floor control as a proof of concept to demonstrate the new interface for floor control and the feasibility of the proposed architecture. In addition, performance measurements have also been made to evaluate the viability of the architecture