This deliverable is the final version of the previous deliverable D6.2a about the specifications of the Factory Image that was produced in the first three months of the Task 6.2. At that time the scope of the whole work-package and the interaction with the whole Project was not clear and too many subjects were included in the specifications, although the concept of Factory Image was introduced in D6.2a, there was not a deployment for the Factory Image and it was difficult to visualize the architecture of the Factory Image. By the end of this task the VFF consortium has defined the industrial scenarios, the modules of WP4, and their needs from the Real Factory Data, therefore the scope of the task is more defined and the architecture of the Factory Image has fitted to its scope. As result, real time data is not part of the Factory Image anymore, the acquisition of field data of the activities of logistics, ergonomics of workers, energy consumptions have been removed, and information acquired for not automatic methods such as manually and contextually have been also removed. The purpose of T6.2 task goes beyond some generic specifications of what is a Factory Image and it has become the procedure to design a software architecture for building the Factory Image. The Factory Image is just a snapshot of the Real Factory at a given moment, and how can be it implemented is the aim of this deliverable. As an important difference, the Factory Image implementation is not allowed to acquire real-time data from field because these data cannot be structured according to the Factory Data Model (WP2), in order that Virtual Manager (WP3) can model it, which in turn feeds the functional modules (WP4). Nevertheless, WP6 can acquire real time data and provide information structured according to the Factory Data model to the functional modules of WP4 by means of another functional module: closed loop simulation module. Specifically, the Deliverable 6.2b describes a Factory Image Software Architecture, It starts from an overview of various production realities to explain the practical use of Real Factory Data on the management of the production. Afterwards, the goal of the Task is to describe the scope of the Factory Image, there must be a limit for the kind of the data considered, for the methods used on the acquisition of this data, for the resources used to store locally the data, the re-structuration need to fit Factory Data Model. Therefore, this documents describes the field data types considered and the benefits to collect them; the methods for data acquisition, the storage means and the data feeding mechanism. Finally, these steps of data processing must be integrated in a software tool that is describe as a factory image architecture, explaining the information flow, the data formats and the use cases.
D6.2b Factory Image Specification
2011
Abstract
This deliverable is the final version of the previous deliverable D6.2a about the specifications of the Factory Image that was produced in the first three months of the Task 6.2. At that time the scope of the whole work-package and the interaction with the whole Project was not clear and too many subjects were included in the specifications, although the concept of Factory Image was introduced in D6.2a, there was not a deployment for the Factory Image and it was difficult to visualize the architecture of the Factory Image. By the end of this task the VFF consortium has defined the industrial scenarios, the modules of WP4, and their needs from the Real Factory Data, therefore the scope of the task is more defined and the architecture of the Factory Image has fitted to its scope. As result, real time data is not part of the Factory Image anymore, the acquisition of field data of the activities of logistics, ergonomics of workers, energy consumptions have been removed, and information acquired for not automatic methods such as manually and contextually have been also removed. The purpose of T6.2 task goes beyond some generic specifications of what is a Factory Image and it has become the procedure to design a software architecture for building the Factory Image. The Factory Image is just a snapshot of the Real Factory at a given moment, and how can be it implemented is the aim of this deliverable. As an important difference, the Factory Image implementation is not allowed to acquire real-time data from field because these data cannot be structured according to the Factory Data Model (WP2), in order that Virtual Manager (WP3) can model it, which in turn feeds the functional modules (WP4). Nevertheless, WP6 can acquire real time data and provide information structured according to the Factory Data model to the functional modules of WP4 by means of another functional module: closed loop simulation module. Specifically, the Deliverable 6.2b describes a Factory Image Software Architecture, It starts from an overview of various production realities to explain the practical use of Real Factory Data on the management of the production. Afterwards, the goal of the Task is to describe the scope of the Factory Image, there must be a limit for the kind of the data considered, for the methods used on the acquisition of this data, for the resources used to store locally the data, the re-structuration need to fit Factory Data Model. Therefore, this documents describes the field data types considered and the benefits to collect them; the methods for data acquisition, the storage means and the data feeding mechanism. Finally, these steps of data processing must be integrated in a software tool that is describe as a factory image architecture, explaining the information flow, the data formats and the use cases.I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.