The Industrial Information Hub from Siemens ist an Industrial Edge app created for vertical data integration from OT to IT. It creates a scalable and reliable architecture to integrate manufacturing data from shopfloor all the way up to the cloud. 
The future proof solution for any industry
The information hub makes transforms any production facility into a smart factory by upgrading it with the latest edge technology. 

• Realize any IIoT use case
• Built in security features
• Open API and vendor independence 
• Semantic data access
• Asset management

From Edge to Cloud
The information hub takes care of all data integration from the shop floor to the cloud. It gathers data through a wide range of connectors and makes live data access possible on every layer up to the cloud (bi-directional). A process historian is included in the runtime as well that can synchronize the storage with parent devices and ultimately the cloud. The built in semantic graph allows for smart data access and plug and play solutions. The built in security makes the IIH robust against malicious access and allows for safe cloud synchronization. 

Robustness and availability through edge technology
The Information Hub can be installed locally and in the cloud. When a cloud synchronization is activated, it can buffer data in case of disconnect for weeks. This increases the robustness of your factory. 
Scalable Architecture
The Information hub is based on a microservice architecture with the convenience of a monolithic engineering user interface. Every component including the connectors, backend and cloud synchronization is managed centrally. Even if you create your own connectors, they can be configured in this UI. The microservices allows to utilize many edge devices at the same time and connect them. This allows for any quantity structure as the hardware can scale with the requirements. For more information check out our SIOS entry. 

Industrial Security
The Information Hub puts data security first. It meets the highest security requirements and standard required in manufacturing and cloud computing. The end user has full control over his data, access and updates. 

Why it is called Information Hub rather than Data Hub
Many data managing systems like based on MQTT suffer from the fact that making sense out of the data is often very difficult. A flat list with often thousands of variables is tricky to use and retrieving them automatically is nearly impossible. 
The Information hub resolves this by mapping all tags onto an OPC UA structure. This is highly standardized and anyone can pick the standard of his choice (in form of a companion specification) from the internet. This makes data retrieval much easier as there are assets for each machine with the corresponding signals inside. On top of this, the user can then create different views of his data to organize it even better (for example a special folder for energy data). Finally the Information Hub has a built in semantic graph. It is generated automatically from the OPC UA on the fly and can be queried. This allows other applications to retrieve information about machines directly and generically. This allows for self updating dashboards, automatic KPI calculation and much much more.  

Vendor Independence 
The Information Hub is not only vendor independent but has completely open APIs. Endusers can create new connectors for it and have full access to all APIs. This allows for better flexibility and the ability to change to more modern components at a later time. 

Compatibility 
The IIH seamlessly integrates into your existing environment. Connectors can be downloaded from the edge app store or created by the user. Cloud integration and device to device sync is included in the feature set. 

Easy entry and no risk investment
The IIH comes with several option packages. The main functionality comes for free and you only require a Hub access and one device to get started. Only 3rd party connectors are not included. This allows you to test and even productively use the Information Hub at no risk. The monetized versions include the device to device synchronization, semantic access and cloud sync. 

Requirements:
Please visit our SIOS entry for a full list of components required. Minimum set of components is: (IIH-Common Configurator, IIH-Core (Free), Registry Service, One connector)