Diese Seite ist nur auf Englisch verfügbar.

System components

Generic components

Component Rule Service App

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring-Cloud-Stream

    • Spring-Data-JPA

  • Frontend:

    • JavaScript

    • TypeScript

    • Angular

Purpose:

  • Manage life cycle of rules and rule functions

  • Routing incoming OPP/PPMP data from RabbitMQ to appropriate rule functions in Apache Kafka (stateful or stateless) when rule context matches (device, device type or part type)

Interfaces:

  • HTTPS (REST)

  • Relational DB (JDBC over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

    • incoming OPP/PPMP measurements and machine messages

    • outgoing rule results

  • Kafka (Binary protocol over tcp) (not needed when Rules Management light is active)

    • outgoing PPMP measurements and machine messages

    • incoming rule results

  • Portal for UI-registration

  • MACMA for authentication/authorization

  • MDM for master data

Component Rule Value Provider (RVP)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Provides requested raw previous measurements or/and aggregated values (aggregation function) for given device and measuring points

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data with request for previous raw values or aggregated values

    • outgoing → PPMP data enriched with previous raw values or aggregated values

Component Rule Value Aggregator (RVA)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Aggregates values (aggregation function) for given device and rules

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data which should be aggregated by time (e.g. 1 minute)

    • outgoing → aggregated PPMP data

Component Rule Function Executor (RFE)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Executes functions for incoming messages and publishes their results

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data enriched with previous values and functions to be executed

    • outgoing → PPMP data enriched with rule results (negative and positive)

Component Rule Result Aggregator (RRA)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Manages rule results and provides insights of rule behavior

  • Publishes rule results

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data enriched with rule results (negative and positive)

    • outgoing → PPMP events for positive rule results

Component Stateful Function Executor

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring-Cloud-Stream

Purpose:

  • Enriches incoming PPMP data with historic data

  • Collects historic data of measurement and/or machine messages executes stateful rules when Rules Light is enabled

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Influx DB (HTTPS over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

    • incoming PPMP measurements and machine messages

    • outgoing rule results

Component Condition Monitoring Core

Interface

  • HTTP/HTTPS (REST)

  • Influx DB (HTTPS over tcp)

  • Relational DB (JDBC over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

  • incoming OPP/PPMP measurements and machine messages

  • Portal for UI-registration

  • MACMA for authentication/authorization

  • MDM for master data

  • Deviation Processor

    • outgoing deviations from rule result

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring-Cloud-Stream

    • Spring-Data-JPA

  • Frontend:

    • JavaScript

    • TypeScript

    • Angular

Purpose:

  • receive device information (measurements, events)

  • plot live-, historic-measurements and list events

  • see Condition Monitoring Core Database Schema

  • see Condition Monitoring Core Rest APIs

  • responsible for aggregating deferred OPP/PPMP measurements for displaying in the historic view

  • aggregating deferred OPP/PPMP measurements for displaying in the historic view

  • Integrates data analytics building blocks into the system (ESDS)

Description:

The CM Core component provides the basic features to receive device measurements and events and present them to the user, related to devices.

IAS/BMLP components

Component AI Services

Purpose:

  • Finds a causing event sequences, based on a list of events and a target event

  • see SDM - Concepts

Interfaces:

Description:

Finds a causing event sequences, based on a list of events and a target event.

Component Information Router

Purpose:

Interfaces:

  • HTTPS (PPMPv3 or OPPv0.9) → via ppmpOverRest or oppOverRest configuration in information router

  • RabbitMQ (AMQP 0.9.1 over tcp) → OPPv0.9 via oppOverAmqp configuration in information router

CM Information Router Communication

Description:

Connectivity provides the data from the machines on the shop floor to the upper-level systems and services and vice versa.

Component MACMA (Multitenant Access Control Management Application)

Purpose:

  • Authenticate user

  • Manage authorization (roles, permissions)

  • Administer system usage policy (authentication & authorization)

  • Manage tenants and their relations to each other

  • Provide Java clients / SSO libs

  • See MACMA

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

Description:

MACMA (Multitenant Access Control Management Application) is the central application within BCI to manage tenants, relations between tenants, users, clients and their respective roles.

Component MDM (Master Data Management)

Purpose:

  • Manage device types, measuring points, devices and facilities

  • See MDM

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

Description:

MDM (Master Data Management) is the central application within BCI to manage device types, measuring points, devices and facilities.

Component Portal

Purpose:

  • Manage views and dashboards

  • see Portal

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

Description:

Manages all views and dashboards.

Component Deviation Processor

Purpose:

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

Description:

Manage all arising deviations within the IAS.

Edit this pageDiese Seite bearbeiten

Feedback on this pageFeedback zu dieser Seite