الفهرس 
INTRODUCTIONOnly 14 pages are availabe for public view
 |  | from | 103 |  |  |
| | | from | 103 | | |
Abstract
Today, automation is used prominently in every major industry. While different industries often use different specialized devices, control systems, and applications, they all share a common, rapidly growing challenge how to share data both amongst all these components and the rest of the enterprise. In the past sharing data with many vendors was producing custom driver problems where each application requires a device or a protocol specific driver to allow it to communicate with each respective device. Drivers are not reusable between applicatIons because each application uses its own data format. OPC enables a control system to retrieve data from all other systems as if they were all from the same vendor. In this thesis we will explains the meaning of OPC and what OPC stands for, origin and uses, general OPC architecture, components, types and connection scenarios. It also explains how OPC get data from Physical I/O to the required application like SCADA or DCS. It has an implementation for a case study for integration between a Distrusted Control System and an Emergency Shutdown System and how to improve it in full details for the required integration and benefits of it. In this thesis we will also introduce the OPC UA and the using of the second generation from OPC which overcomes some of the drawbacks of classic OPC like security, scalability, hard configuration issues and platform implementation. We will explains OPC UA general architecture, aggregating servers, OPC UA protocols, Meta model and how to migrate classic OPC to OPC UA with the two basic approaches wrapping existing servers and directly accessing device data. Integration issues for OPC UA will be discussed in full details. In this thesis we will also expresses the establishment of a real time data communication between two different PLCs from different manufactures.