Back

D3.8 - Selected legacy systems/interfaces that will be supported by the interoperability framework

 

Title 

Selected legacy systems/interfaces that will be supported by the interoperability framework

Editor

UNINOVA

Executive Summary

The deliverable D3.8 “Selected legacy systems/interfaces that will be supported by the interoperability framework” is focused on the identification and analysis of interoperability needs between C2NET and the existing legacy systems used in the frame of each industrial pilot’s use cases. At this point of the project the final selection of legacy systems that need to be supported is still preliminary as the work concerning requirements and validation scenarios of WP1 is ongoing. Also the specification on how interoperability is going to be designed and implemented will be continued in deliverable D3.5 “1st Modular Architecture and Tools for Interoperability”. 
 
The Enterprise Interoperability Framework (EIF) standard supports the analysis that allows to position interoperability solutions within three different perspectives. Indeed, the EIF provides the method to identify which barriers are addressed (conceptual, technological, organizational), at which interoperability level (business, process, applications, data), and what is the best approach (federated, unified, integrated) for implementing such solution. Hence data collection and exchange formats, standards for communication, web-service integration, among other interfacing techniques are already briefly analysed in the document. 
 
Targeting to provide a generic solution that can be applied to other manufacturing scenarios, and also in the spirit of re-usage of previous research results and/or existing tools, the DCF interoperability framework considers prominent software that might be necessary to consider along the project development. It is analysed how the C2NET services and interoperation is changed when facing relevant software solutions used in supply-chain and manufacturing industries, such as Business Intelligence, SCADA, Hardware or Middleware, as well as solutions that may be reused in the interoperability framework itself (e.g. Enterprise Service Bus ESB, middleware platforms like FI-WARE adapters, etc.). 
 
In summary, the main results from deliverable D3.8 are: 
  • The proposition and description of the EIF as the reference framework to analyse and describe the interoperability solutions; 
  • The identification and preliminary analysis of the interoperability needs with the legacy systems used in the industrial pilots according with their category. 
    • 9 different ERP Systems have been analysed, out of which we consider that the following 5 will be supported in C2NET: FuturMaster (Interface for SAP), QUALIAC, MSOffice, NOVATEC ERP (Proprietary) and Softmais. 4 others are yet under analysis depending on the requirements and the scenarios: BAAN IV, Microsoft Dynamics, SAP (depending on the pilot) and Technician Reporting System. 
    • 10 different legacy systems for Monitoring and Control have been analysed, out of which we consider that the following 3 will be supported in C2NET: Code Readers (depending on the pilot) and specific APIs, Ignition and Softingal. 4 others are yet under analysis depending on the requirements and scenarios: Engel e-factory2, Just in Sequence, Microsoft Dynamics CRM and Touch Screen Applications. Code Readers for pilot 3 are not directly supported since they are interfaced through the Softingal system for pilot 2 they will not be supported. And 3 legacy systems used in pilot 2: Business Object, Cognos and Transportation Tracking Systems will not be supported by C2NET platform. 
    • 5 different legacy systems for Database Management have been analysed, out of which we consider that the following 3 will be supported in C2NET with a direct interface: PFDC Historical Data Warehouses, Firebird and SQL Servers. 2 others are yet under analysis depending on the requirements and scenarios: LM7 WMS /Manhattan WMS and FH Local Server Storage. 
  • The identification and preliminary analysis of other prominent software solutions that could either support the development of the C2NET solutions or should be supported for the C2NET exploitation. This analysis complements the one made in deliverable D2.3 “Selection Technologies and Development Process Guideline Document”. We have focused on the interoperability capabilities the C2Net should provide when using 6 different system types, i.e., for Business Intelligence (9), for Enterprise Services Bus (13), for Manufacturing Execution Systems (8), for SCADA (3), for Hardware and Middleware Standards (5) and finally other solutions (5) that resulted from project partner’s involvement in other projects. Also in this case nothing decisive has been selected, nevertheless some have already been put aside due to the potential of overlapping with similar solutions, partners experience among others. 

WP/Task

WP3/T3.3

 

 

 

Previous