Platform components and deployment scenarios

Platform components

Open

• Azure IoT Hub - Azure service used for acquiring sensor data information streams.

• Azure Service Bus – Azure service used for transferring data from IoT Hub to PackOS Application in form of ordered messages and internal event bus for inter-service communication.

• LogiX ODP Processing – Main component for message processing, production and machines state inferring and calculating partial KPI’s in PackOS.  

• LogiX API – Interface to LogiX applications, implements server-side logic of PackOS GUI components.

• LogiX Gateway API – Integration of PackOS application with external systems e.g. Materials/Orders/Work calendar information.

• LogiX Auth - User authentication, integration of LogiX with external identity provider (Azure AD/Okta)

• LogiX Hub – Rights administration inside PackOS application, configuration of plants

• LogiX Notify – Managing and broadcasting notifications to subscribers

• PackOS UI – Web application for end users dedicated to monitoring production

• LogiX Operator Cockpit – Web application for end users dedicated to interact in real-time with platform (i.e. enter current downtime details)

• LogiX Operator Cockpit App – Mobile application available for Android and iOS

Deployment architecture for multiple factories

Open

Scaling strategy for multiply factories

• All factories are connected to one MS Azure Region.

• Components responsible for signal processing and KPI calculations are multiplicated for each factory. 

• Backend services for PackOS Applications are shared between factories. In general, there is no need for additional instances of services in this layer. In case of a large user population these services scale easily.

• If the delays caused by multiregional connections between factories and the PackOS region become unacceptable, installation can be repeated in subsequent regions.