/ INDUSTRIAL SOLUTION 09

IT/OT Industrial Data Management (Solution 4.0)

Turn field data into live visibility, rules, alarms and operational action with DataHub.

DataHub combines machine data, smart alarms and notifications, maintenance and spare parts, plus optional warehouse and dispatch processes on one on-premise platform.

Explore the solution
IT/OT Industrial Data Management (Solution 4.0) solution
OSKONIT/OT Industrial Data Management (Solution 4.0)
/ WHY SOLUTION 4.0?

Don't just show scattered machine data on the screen; Transform it into a common, reliable and contextual operation layer that feeds production decisions.

01

Disconnected data islands

Information in PLC, SCADA, meter, quality and business systems lives with different times, names and formats.

02

Context-free machine signals

Raw tag data; When it is not combined due to product, work order, shift, line and stop, it does not turn into a business decision.

03

Transformation remaining in the pilot project

The solution working on a single machine cannot be spread to the facility without a common standard, governance and scalable architecture.

Digital production and industrial data operation
/ FROM FIELD TO DECISIONA digital production that protects existing automation investments and can grow step by step backbone.
/ COMMON LAYER OF TRANSFORMATION

Connect the machine,
give production context to data.

Solution 4.0; It addresses field connectivity, edge processing, common data model, historical storage and enterprise system integration in a single architecture. The aim is not to establish a new data island, but to connect the existing PLC, SCADA, MES and ERP layers with a reliable data backbone.

ConnectDevice and system connection
ContextLine, product and work order context
ConsumeOperation and corporate use
  • Edge priorityField data is collected close to the source, filtered and buffered in a controlled manner in case of connection interruptions.
  • Common name modelSignals of different machines are distributed in the plant, line, cell, equipment and measurement hierarchy is standardized.
  • Open integrationOperational data is presented to dashboards, analytics, MES, ERP and data platforms in a controlled manner.
/ WHAT DOES DATAHUB DO TODAY?

It does more than collect data;
it turns it into operational action.

Modules are enabled as needed. A structure that starts with one line and one critical rule can expand into maintenance, inventory, order and dispatch processes through the same data model.

01 / VISIBILITY

Live plant view

Connection status, live values, history and related files are monitored in a plant, line, machine and device hierarchy from a single point.

02 / RULES

Smart alarms and notifications

Value, threshold and duration conditions are defined together. When an event occurs, the right team is notified by email, Slack, Telegram or an HTTP webhook.

03 / OPERATIONS

One operations console

The operations centre, alarm list, dashboards, users and permissions are managed in one interface, allowing teams to work from the same event record.

04 / MAINTENANCE

Maintenance and spare parts

Maintenance records, part inventory and warehouse locations are linked to equipment, providing immediate access to the right history and available part during a fault.

05 / WMS

Warehouse and dispatch flow

Products, locations, inventory, dispatch orders, picking, packing and mixed-pallet planning can be activated on the same platform as required.

06 / ACCESS

Role and language management

With Turkish, English and German interfaces, the plants, modules and actions available to each user are restricted by role.

/ INDUSTRIAL DATA FLOW

The raw signal moves forward,
turning into usable information.

The animation shows the reliable reception of the field signal at the edge, enriching it with the production context and distributing it to different operational applications through the same model.

/ MODULAR STRUCTURE

Start as needed,
grow with common architecture.

Each capability can be deployed as an independent project; but the data model and integration principles are jointly designed from the beginning.

01 / CONNECTION

Industrial connection

Reliable data collection from PLC, CNC, robot, SCADA, energy analyzer and databases.

02 / EDGE

Data processing in the field

Network and center with filtering, calculation, buffering and local rules reducing the load.

03 / MODEL

Unified data model

Standardization of tags with asset, location, product, shift and work order context.

04 / STORAGE

Live and historical data

Queryable, traceable and scalable storage of high-frequency process data.

05 / INTEGRATION

IT/OT data bridge

Controlled data exchange with MES, ERP, WMS, quality, maintenance, cloud and data lake systems.

06 / APPLICATION

Panel, rules and analytics

Role-based dashboards, notifications, calculated KPIs and operations support applications.

/ DATAHUB INDUSTRIAL DATA PLATFORM

Detect the event,
run the rule and mobilise the right person.

DataHub combines a machine signal with its operational context. The rules engine evaluates value, duration and equipment status together; it records the alarm, shows the event on the trend and sends a notification through the selected channel.

ON-PREMISE SERVEROFFLINE OPERATIONMODULAR GROWTH
DATAHUB / FROM EVENT TO ACTION
Signal → Context → Rule
Alarm → Notification → Action

Live Data · Assets · Rules · Alarms · Operations

ONE PLATFORM / CONTROLLED DATA FLOW
/ SINGLE OPERATIONAL VIEW

From machine status to job result,
on the same screen.

When production, energy, quality and maintenance data are displayed in the context of common time and equipment, teams work with the same reality; cause of deviation becomes visible faster.

LINE 04 / LIVE OPERATION● CONNECTION ACTIVE
OEE82.4%
PERFORMANCE88.7%
QUALITY97.1%
RECENT EVENTS

Filling-02Micro stance · 02:14

Packing-01Speed below target

EnergyShift base load +6%

/ HOW DOES IT WORK?

Start with one line, one rule and one notification;
then scale the same standard across the plant.

  1. 01
    Connect the source

    A PLC, SCADA, meter, database or business system is brought into the platform through the appropriate industrial protocol or interface.

  2. 02
    Build the asset model

    Signals are organised with meaningful names and units in a plant, line, machine and device hierarchy.

  3. 03
    Define the rule

    Value, duration and state conditions such as “current remains above 20 for five seconds” are configured without writing code.

  4. 04
    Verify the event

    The data and exact time that triggered the alarm are shown on the historical trend, making threshold reviews evidence-based.

  5. 05
    Notify the team

    The notification is routed to the relevant team and channel; users see only the plants and events for which they are authorised.

  6. 06
    Expand modularly

    The validated structure extends to new machines, maintenance records, inventory and dispatch operations through the same core.

/ VALUE PRODUCING SCENARIOS

Not the data platform,
operation result.

01

OEE and downtime analysis

Cycle, speed, downtime and quality losses on line, product, shift and cause basis visibility.

02

Energy and resource efficiency

Comparison of electricity, gas, water and auxiliary facility consumption with production quantity and equipment status.

03

Condition and maintenance visibility

Maintenance workflows of meters, alarms, operating time and process deviations feed.

04

Traceable production

Associating product, recipe, material, process value and quality result on the time line.

/ NEXT SOLUTIONSorter Smart Conveyor Systems
/ LET’S DEFINE THE NEXT STEP

Let’s map your IT/OT data
architecture together.

Share your systems, data sources and target use cases with the industrial data engineering team.

Request a data architecture review Your request is routed directly to the relevant engineering team.