BI-data Interface

Overview

It is a standard export functionality designed to enable the automated and scheduled export of production data from the RS Production system to external destinations for reporting and analytics. This data can be consumed by BI tools like Microsoft Power BI, Tableau, and Qlik to visualize trends, monitor performance, and support data-driven decisions.

Exports are configurable with flexible options for time intervals, date-time formats, time zones, destinations, and output formats. This supports seamless integration with cloud platforms, on-premise databases, and remote systems.

Destinations

This function offers several different types of destinations:

1. Azure Blob Storage

Ideal for those who want to access data from RS Production while developing applications on Azure.

• File Types Supported: CSV, JSON

• SAS URL (Shared Access Signature):

  • Provides secure, time-bound access to Azure Blob containers.

  • Customer must:

    • Create a storage account in Azure.

    • Create a container with the name same as the installation number (6 digits).

    • Add an access policy specifying start and expiry time.

    • Generate and save the SAS URI for use in RS Production.

• Supports archiving of historical data

2. Local Folder

Suitable for local development projects.

• File Types Supported: CSV, JSON

• Directory:

  • Specify a local directory path on the server hosting RS Production or Edge/OPC service

• Supports archiving of historical data

• Requires Edge service for cloud installations

3. SFTP Server

Suitable for those who develop locally.

• File Types Supported: CSV, JSON

• Required details:

  • Server name (SFTP host)

  • Username

  • Password

  • Directory path to receive the exported files

• Supports archiving of historical data

• Requires Edge service installation for cloud installations using on-premise SFTP service

4. Azure SQL database

Ideal for those who want to use data from RS Production in applications developed on Azure.

• Required details:

  • Server name

  • Username

  • Password

  • Database name

• This export option is compatible only for installations that process a single order or article at a time due to the primary key constraint enforced in the target schema.

5. SQL Server Database

Suitable for local development projects.

• Required details:

  • Server name

  • Username

  • Password

  • Database name

• Requires Edge service installation on on-premises SQL server database selection.

• This export option is compatible only for installations that process a single order or article at a time due to the primary key constraint enforced in the target schema.

Setup Instructions

• Edge service

Learn more about secure communication with the cloud Edge Service . Find details on how to Install Edge Service .

• For SQL database (Azure / on-premise SQL server):

Before enabling this export, the following SQL script must be executed on the destination database server. This script creates the necessary schema structure to receive and store the exported data from RS Production.

BI export database structure.sql

Settings

The Data export settings is available under Settings > Integration. Once enabled, the following parameters must be configured:

1. Time Interval

Select the desired time frame for regular exports:

• Last 30 Days

• Last 7 Days

• From Yesterday

• Today

2. Date and Time Format

Define the date-time format for exported data:

• yyyy-MM-dd HH:mm:ss.fff

• MM/dd/yyyy HH:mm:ss.fff

• yyyy-MM-dd HH:mm:ss.fffzzz

3. Time Zone Selection

Specify the time zone to ensure timestamps in exported data match your organization’s time zone.

• Default: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna

4. Export Scheduling

Configure the frequency at which the export should run, x days at x time.

5. Destination

Choose one of the available destinations:

• Azure Blob Storage

• Azure SQL Database

• SQL Server Database

• SFTP Server

• Local Folder

Data Export Details

The system exports four categories of production data:

1. Settings

Defines OEE calculation logic for each installation:

• Installation information

• OEE calculation flags

  • CalculatePerformanceFromWeightedProducedUnits

  • MicrostopAsPerformanceLoss

  • ReworkAsQualityLoss

2. Stops

Captures detailed information about every stop event per shift at each measure point.

• Installation and measure point details

• Stop timing information (start, end, duration)

• Reason and category of stop

• Station and shift information

• Operator comments

3. Stop Occasions

Provides summarized data about stop intervals across shifts for each measure point. It focuses on broader patterns and reliability metrics rather than individual events.

• Installation and measure point details

• Stop and productive occasion tracking

• Metrics including:

  • Duration

  • Stop quantity

  • MTBF (Mean Time Between Failures)

  • MTTR (Mean Time To Repair)

4. Worktime

Logs the production activity per shift at each measure point, aggregated on an hourly basis.

• Installation and measure point details

• Shift information

• Production order and article information

• OEE metrics including:

  • Total, scheduled and excluded duration

  • Time breakdown (productive, downtime)

  • Unit production metrics

OEE calculation

Availability

((ScheduledDuration - StopDuration - SetupStopDuration - NoWorkTimeStopDuration + (Setting.MicrostopAsPerformanceLoss ? MicroStopDuration : 0)) / 
(ScheduledDuration - ExcludedDuration)) * 100

Performance

It includes four distinct calculations based on the settings specified in the “Setting” table:

1. If both the MicrostopAsPerformanceLoss & CalculatePerformanceFromWeightedProducedUnits settings are enabled:

   C#

   ProductionTimeDuration + MicroStopDuration > 0 ? 
   ((UsedEffectiveTime - (Setting.ReworkAsQualityLoss ? 0 : ReworkedEffectiveTime))/ 
   (ProductionTimeDuration + MicroStopDuration)) * 100 : 100

2. If only the MicrostopAsPerformanceLoss setting is enabled:

   C#

   OptimalProducedUnitsNoMicroStop > 0 ? 
   (OptimalProducedUnitsNoMicroStop > ProducedUnits ? 
   ((ProducedUnits - (Setting.ReworkAsQualityLoss ? 0 : ReworkedUnits)) / OptimalProducedUnitsNoMicroStop) * 100 : 100) : 100

3. If only the CalculatePerformanceFromWeightedProducedUnits setting is enabled:

   C#

   ProductionTimeDuration > 0 ? 
   ((UsedEffectiveTime - (ReworkAsQualityLoss ? 0 : ReworkedEffectiveTime)) / ProductionTimeDuration) * 100 : 100

4. If neither of the settings is enabled:

   C#

   OptimalProducedUnits > 0 ? 
   (OptimalProducedUnits > ProducedUnits ? 
   ((ProducedUnits - (Setting.ReworkAsQualityLoss ? 0 : ReworkedUnits)) / OptimalProducedUnits) * 100 : 100) : 100

Quality

There are two different calculation methods based on the settings defined in the “Setting” table:

1. If the CalculatePerformanceFromWeightedProducedUnits setting is enabled:

   C#

   UsedEffectiveTime - ScrappedEffectiveTime - (Setting.ReworkAsQualityLoss ? ReworkedEffectiveTime : 0) >= 0 ? 
   (UsedEffectiveTime > 0 ? 
   ((UsedEffectiveTime - ScrappedEffectiveTime - (Setting.ReworkAsQualityLoss ? ReworkedEffectiveTime : 0)) / UsedEffectiveTime) * 100 : 100) : 0

2. If no settings are enabled:

   C#

   ProducedUnits - ScrappedUnits - (Setting.ReworkAsQualityLoss ? ReworkedUnits : 0) >= 0 ? 
   (ProducedUnits > 0 ? 
   ((ProducedUnits - ScrappedUnits - (Setting.ReworkAsQualityLoss ? ReworkedUnits : 0)) / ProducedUnits) * 100 : 100) : 0

OEE

((Availability/ 100) * (Performance/ 100) * (Quality/ 100)) * 100