SOT
    • Operations manual
      • Overview
      • System architecture and interfaces
      • System requirements
        • Shopfloor Management Essentials database
      • Migration from previous versions
      • Setup and configuration
        • Helm configuration
        • Config Bridge
        • Administration
        • DataCollector v4.1.x
        • Shift Book
        • KPI Reporting
        • Andon Live
        • Databases
        • Service-to-service configuration
        • Recommendations
      • Start and shutdown
      • Regular operations
      • Failure handling
      • Backup and Restore
      • Logging and monitoring
        • Open Telemetry integration
        • Module health endpoints and K8S probes
      • Known limitations
    • Glossary
Shopfloor Management Essentials
  • Smart Operations Toolkit
    • Deviation Processor
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Process Quality
    • AI Services
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
  • Enterprise & Shopfloor Integration
    • Information Router
    • Master Data Management

SOT Learning Portal
  • Shopfloor Management Essentials
  • Operations manual
  • System requirements

System requirements

Resource requirements per pod

The following table outlines the recommended resource requests for each pod. These recommendations assume:

  • No CPU limits[1] are configured.

  • The underlying infrastructure does not employ CPU over-provisioning.

  • The CPU request values are intentionally set low because they represent resources exclusively reserved for the Pod. However, since Pods may occasionally require additional CPU, it’s important to keep extra CPU capacity available to accommodate these temporary spikes and ensure smooth performance.

Failure to meet these recommendations may result in instability or performance degradation. Volume storage is not required.

Service Administration Andon Live ConfigBridge DataCollector KPI Reporting Shift Book Database Migration Job Total

CPU Request[2]

100 milliCPU

400 milliCPU

200 milliCPU

200 milliCPU

150 milliCPU

200 milliCPU

750 milliCPU

2000 milliCPU

Minimum memory

500 MB

1500 MB

500 MB

500 MB

1500 MB

1500 MB

1000 MB

7000 MB

Maximum memory

2048 MB

3000 MB

2048 MB

2048 MB

3000 MB

3000 MB

2000 MB

17144 MB

Mounted Volume Storage

None

None

None

None

None

None

None

None

Required software on cluster

Operating System

Linux with an OCI-compatible runtime (Kubernetes)

Kubernetes Version

1.31 or higher

IAS Helm Schema Version

2.3

Further Software

N/A

Infrastructure services

Service Administration Andon Live ConfigBridge DataCollector KPI Reporting Shift Book Database Migration Job

IAS Portal

Required

Required

Required

Not required

Required

Required

Not required

MACMA

Required

Required

Required

Required

Required

Required

Not required

Master Data Management (MDM)

Not required

Not required

Required

Not required

Not required

Not required

Not required

Data Publisher

Not required

Not required

Not required

Not required

Not required

Optional

Not required

Maintenance Management

Not required

Not required

Not required

Not required

Not required

Optional

Not required

RabbitMQ

Required

Required

Required

Required

Required

Required

Required

Information Router

Not required

Not required

Not required

Required

Not required

Not required

Not required

Deviation Processor

Not required

Not required

Not required

Not required

Optional

Optional

Not required

Messaging middleware

RabbitMQ

Supported Versions

Any version supporting AMQP 0.9.1

Extensions

None

Capacity

Service Capacity

Administration

Consumes notifications from Config Bridge, sends cache refresh notifications for config data in Administration

Andon Live

Consumes notifications from Config Bridge and Administration (e.g., cache refresh notifications)

ConfigBridge

Sends internal communication between modules (e.g., cache refresh notifications for MDM Sync)

DataCollector

Consumes machine telegrams from RabbitMQ

KPI Reporting

Consumes notifications from Config Bridge and Administration (e.g., cache refresh notifications)

Shift Book

Consumes notifications from Config Bridge and Administration (e.g., cache refresh notifications)

Database Migration Job

Broadcasts database migration status

Queues / topics / exchanges

Exchange Used by Created by Description

x.connectivity.opp.v09.shopfloorManagement.changeOver.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.error.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.groupOfPartProcessed.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.jam.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.multiPartProcessed.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.operationModeChanged.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.partMissing.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v09.shopfloorManagement.partProcessed.v09

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.changeoverStart.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.changeoverEnd.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.eventStart.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.eventEnd.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.groupOfPartProcessed.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.jamStart.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.jamEnd.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.multiPartProcessed.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.operationModeChanged.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.partMissingStart.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.partMissingEnd.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.connectivity.opp.v1_0.shopfloorManagement.partProcessed.v1_0

Data Collector

Information Router

Information Router will put machine telegrams on this exchange

x.nexeed.integration

ConfigBridge

Operator

Global integration exchange

x.smc.andon

Andon Live

Andon Live

Exchange used by AndonLive to send real-time updates to other AndonLive instances (used to synchronise statistics on terminals)

x.smc.datacollector.public

Data Collector

Data Collector

Other SCSs can push messages to be processed by Data Collector. Currently used by Packaging Control to send part messages

x.smc.datacollector.public.processedParts.deadletter

Data Collector

Data Collector

Deadletter exchange for x.smc.datacollector.public

x.smc.integration-inbound

Config Bridge

Config Bridge

Exchange that receives all integration event from x.nexeed.integration

x.smc.internal-common

All

All

Exchange for SCS internal messages (s2s communication like cache invalidation etc.)

x.smc.opp.shopfloorManagement.changeOver.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.error.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.groupOfPartProcessed.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.jam.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.multiPartProcessed.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.operationModeChanged.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.partMissing.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.shopfloorManagement.partProcessed.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.changeOver.start.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.changeOver.end.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.event.start.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.event.end.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.groupOfPartProcessed.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.jam.start.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.jam.end.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.multiPartProcessed.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.operationModeChanged.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.partMissing.start.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.partMissing.end.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.opp.v1_0.shopfloorManagement.partProcessed.deadletter

Data Collector

Data Collector

Deadletter exchange for machine telegrams

x.smc.shiftbook.downtime.<Tenant-ID>

Shift Book, Data Publisher

Shift Book

Exchange where downtime changes for tenant specified in <Tenant-ID> are published

x.smc.shiftbook.shift.<Tenant-ID>

Shift Book, Data Publisher

Shift Book

Exchange where shift changes for tenant specified in <Tenant-ID> are published

x.smc.shiftbook.testrun.<Tenant-ID>

Shift Book, Data Publisher

Shift Book

Exchange where test runs for tenant specified in <Tenant-ID> are published

Databases

The SCS contains 2 distinct database types:

  1. Config Bridge Database: Only exists once and contains the connection strings of all Essentials Databases

  2. Essentials Database: Exists once per tenant (meaning one Oracle schema per tenant) and contains only data of that tenant. We use this to separate data of different tenants.

TenantConnectionStringMapping

  • Shopfloor Management Essentials database

Configbridge database

This is the database dedicated to ConfigBridge.

Supported Versions

Oracle 19c Enterprise, SQL Server >= 2019

DBs / Schemas / Users

Requires access to a dedicated database (SQL Server) or schema (Oracle). User scripts that create all the necessary DB Objects in that schema/database need to be executed manually for now an can be found Database scripts for Configbridge Database.

Required Privileges

Sys/SA user privileges for creating the database and the user.

Relative Capacity

10 MB / 1 tenant

Deployment modes

Shopfloor Management Essentials consists out of three functional modules: - Shift Book (required) - KPI Reporting (optional) - Andon Live (optional)

The modules: - Administration - ConfigBridge - DataCollector are supporting modules which are required as well.

Administration

Required

Andon Live

Optional

ConfigBridge

Required

DataCollector

Required (MES DataCollector PDA could be used instead)

KPI Reporting

Optional

Shift Book

Required

DataCollector

This image shows the different possible setup to supply the SM modules with data:

datacollector scenarios

DataCollector PDA (MES, Windows server)

DataCollector v4.1 is the predecessor of the Shopfloor Management IAS DataCollector. IT can be used instead of the IAS DataCollector. This can be a good approach for migration scenarios.

Hardware requirements:

CPU Clock Rate

2 GHz

CPU Cores

2

RAM

3000 MB

Local File Storage

5 GB

Software requirements:

Operating System

Windows Server >= 2019

Dotnet Framework Runtime

4.8.0[]
1. spec.resources.limits.cpu or spec.containers[].resources.limits.cpu.
2. spec.resources.requests.cpu or spec.containers[].resources.requests.cpu.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2026, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses