Skip to content

Qynetic

Your factory. Made clear.

See how it works
Explore the flowSelect a part
01 / The factory

Where production happens.

Machine status, alarms and production values are read at the source. Measurement files and other systems can join the same flow.

Explore machine connections
02 / Qynetic Edge

Edge sits inside your factory.

Connected to the same local network as your machines. Collects and buffers even without internet.

How Qynetic Edge works
03 / Qynetic cloud

Secure all the way to Qynetic.

Edge connects outward using encrypted HTTPS on port 443. In the cloud, collected data becomes available for analysis and insight.

Explore the architecture
04 / Your overview

Your whole factory. On your screen.

Follow production, quality and maintenance in one view.

From machine signal to OEE

How it works

From machine signals to a shift report

  1. Connect once

    Choose the signals for a machine in Qynetic Edge. Check a state change and a part count against its operator panel.

    Qynetic Edge
  2. Keep the history

    Each reading stays linked to its machine and time. A shift team can trace a stop or a change in output back to its source.

    Platform architecture
  3. Review the shift

    See how long the machine ran, how many parts passed inspection and where the shift lost production time.

    Qynetic OEE

Before / after

From machine signals to factory results.

Machine data is the starting point. Qynetic connects production and calculates OEE, losses and results across the factory.

Swipe to compare

01

From this

Raw readings from one machine.

NC DATA MONITOR — M70-01
└ M70-01 └ SYSTEM 01
DEVICE DATA / RAW VALUES
TAG / REGISTERVALUE
NC_ID
M70-01
SYS_NO
01
EXEC_STATE
00000001
MODE_FLAG
0x0003
NC_PROGRAM
O1042
PART_COUNT
00000188
CYCLE_SEC
120
SPINDLE_RPM
2400
FEED_MM_MIN
180
OVERRIDE_PC
100
LAST_RESULT
0x00000000
ALARM_CODE
0x0000
[11:42:18] NC01:SYS01 READ_OK
[11:42:18] RX 01 00 C0 00 00 01
[11:42:18] MAP: NC_STATE -> 1
[11:42:19] POLL_INTERVAL=1000
[11:42:19] WAIT_NEXT_CYCLE...
I/O SIGNAL MONITOR / NC01:SYS01
ADDRESS / SIGNALVALUE
X0000 / CYCLE_RUN
1
X0001 / FEED_HOLD
0
X0002 / ALARM
0
X0003 / AUTO_MODE
1
D0100 / PART_COUNT
00000188
D0200 / SPINDLE
2400
D0201 / FEED
180
D0202 / OVERRIDE
100
D0300 / CYCLE_SEC
120
R0400 / PROGRAM
O1042
[11:42:18] X0000=1 X0001=0
[11:42:18] X0002=0 X0003=1
[11:42:18] D0100=188
[11:42:18] BITMASK=0x0009
[11:42:19] READ_STATUS=0x0000
EVENT BUFFER / NC01:SYS01
TIME / EVENTVALUE
11:38:02 / LINK
0x0000
11:38:03 / MODE
0x0003
11:38:04 / EXEC
00000001
11:39:26 / COUNT
00000185
11:40:24 / COUNT
00000186
11:41:21 / COUNT
00000187
11:42:18 / COUNT
00000188
11:42:19 / READ
0x0000
[11:38:02] TCP_CONNECT_OK
[11:38:03] NC01:SYS01 INIT_OK
[11:38:04] MODE=0x0003 STATE=1
[11:42:18] D0100: 187 -> 188
[11:42:18] RX 00 00 00 BC
[11:42:19] RESULT=0x00000000
[11:42:19] BUFFER_END
NC01 · TCP CONNECTED1000 ms
02

To thisQynetic

Factory OEE, production and losses.

oee.qynetic.seDemo
Qynetic OEEDay shift · 06:00–14:00

Factory overview

2 / 3 producing

OEE · 3 machines

Availability
87.8%
Performance
92.5%
Quality
97.8%
Operating time
19 h 45 min
Unplanned stops
2 h 45 min

Production

Good parts

536 / 720

Total
548
Rejects
12
Shift target
720

State distribution

Combined machine time
Operating time 19 h 45 minUnplanned stops 2 h 45 minPlanned stops 1 h 30 min
M70-01
Processing

OEE 81.8%

PO-24018184 / 240
M70-02
Stopped

OEE 71.1%

PO-24019160 / 240
M70-03
Processing

OEE 85.3%

PO-24020192 / 240

Machines

Day shift · 06:00–14:00
M70-01Processing
Availability
90.0%
Performance
92.8%
Quality
97.9%
M70-02Stopped · Material shortage
Availability
80.0%
Performance
91.1%
Quality
97.6%
M70-03Processing
Availability
93.3%
Performance
93.3%
Quality
98.0%

Loss analysis

Day shift · 06:00–14:00

Top stop reasons

Material shortage90 min
Tool change45 min
Adjustment30 min

Calculation inputs

Planned production time
22 h 30 min
Operating time
19 h 45 min
Ideal cycle time
120 s
Total
548
Recorded rejects
12
Availability
87.8%
Performance
92.5%
Quality
97.8%
Machine signals + shift plan + ideal cycle times + recorded rejects

Connect once, use everywhere

Stop building every integration twice

From separate connections to one shared data flow.

Trace a machine

Selecting a machine highlights its four direct point-to-point connections and its single connection to Qynetic Edge, which shares the data with every application.

01

Point to point

16Connections

4 machines × 4 systems = 16 connections, each with its own mappings and failure modes.

02

With Qynetic

8Connections

4 + 4 = 8 connections. Add a machine or a system and you add one connection.

Everything you run today, in one flow

Qynetic Edge is built to connect to machines and systems directly. What already works stays; Qynetic connects to it, adds the analysis layer on top and returns the result where it is needed.

  • Live machine status, alarms and signals

    Qynetic Edge reads machines and PLCs directly, outbound and read-only.

  • Time-stamped history and trends

    Kept as one append-only event log.

  • Process stability and drift (SPC)

    Capability and control limits in Quality, from the same data.

  • OEE, downtime and loss analysis

    Qynetic OEE, with loss analysis across machines.

  • Traceability and genealogy

    One production record linking orders, parts, tools and measurements.

  • Material flow and AMR

    Transport orders and status as events in the same model.

  • Orders and master data from ERP / MES

    Read through configurable connectors, results returned.

  • Reading scanned drawings

    AI is optional. In CIM you can use text recognition to read dimensions, or enter them yourself. Edge, OEE and quality calculations work independently.

Every machine connected once. Every module reads the same model.

Connect a machine

Choose the interface listed in the machine manual. Edge reads its signals on the factory network.

Sources and systems (8)
  • Machines and PLCs
  • Measurement systems
  • Vision and inspection
  • Material flow (AMR, trays)
  • Manual stations
  • MES
  • ERP / order system
  • Other existing systems

For inspection software, MES or ERP, bring a sample export or API response to review the connection.

Integration guide

How did the shift run?

Qynetic OEE puts machine time and good parts on the same shift report.

Example shift

M70-01 · 8 h

81.8%OEE

Run time
405 min
Stops
45 min
Scheduled stop
30 min
Good parts184 of 188
Explore Qynetic OEE

Verifiable, not promised

What you can check yourself

Four properties of how Qynetic is built. Each is described on the architecture and security pages, so you can review it yourself.

  • Outbound-only, read-first

    Qynetic Edge connects outward from the factory network. Read-only monitoring is the first step, and any path that can write to a machine is treated as safety-relevant.

    Read the architecture
  • Machine access

    The standard adapters only read machine signals. Applying an approved tool correction requires a separate local writer and verification at the machine.

    Read about security
  • The origin of every value

    Every value carries its source, when it was generated, when it was received and whether it has been transformed.

    Read the architecture
  • Isolated and traceable

    Isolation between organisations is enforced in the database and tested. Events and approvals can only be appended, and each is attributable to a person, system or agent.

    Read about security

Knowledge

All articles

Common questions

What is Qynetic?

Qynetic is a production monitoring platform from Sweden. It brings machine readings, part counts and inspection results together so shift teams can track downtime, OEE and quality across equipment from different manufacturers.

What problem does Qynetic solve?

Manufacturing data is fragmented across machines and systems, so causes that span domains — for example tool wear that causes dimensional drift — are hard to see. Qynetic normalises that data into one model and surfaces the most important issues with evidence, so people do not have to search dashboards.

Can we keep our existing MES or ERP?

Yes. You can start with readings from one machine. If you also need order numbers or part revisions from another system, check which exports or interfaces your site can share.

Who is Qynetic for?

Discrete manufacturers with demanding quality requirements — for example precision machining and medical device manufacturing — that run machines, measurement and enterprise systems from several vendors.

What is Factory Director?

The Factory Director demo shows a shift team how to review open issues in order of severity. Each example links a suggested action to the readings or events behind it.

How does Qynetic help improve Cpk?

Qynetic does not improve Cpk by itself. It computes capability and drift from measurement history and correlates them with tool, program, machine and material, so engineers can find and fix the cause faster.

FAQ

From one finished part to shift OEE

At 11:42:18, machine M70-01 finishes a part. Select a stage to follow the reading through this example shift.

Follow a reading

The part counter advances.

The control on M70-01 records another finished part while program O1042 runs. The operator can compare the reading with the counter on the lathe.

Follow a machine signal
Machine
M70-01
Counter register
D0100 / PART_COUNT
Spindle speed
2,400 rpm

Edge records one completion.

Edge compares the verified counter with its previous reading and sends the difference. The event carries the machine identity and source time, so it can be attributed to the right shift.

How Edge collects events
Event
production.completed
Quantity
1
Machine and time
M70-01 · 11:42:18

184 good parts at shift close.

The shift totals 188 parts, 4 rejects and 405 minutes running. The shift plan allows 450 production minutes, with an ideal cycle of two minutes per part. Together these readings give the three OEE factors.

See the OEE calculation
Availability
90%
Performance
92.8%
Quality
97.9%
Explore the full platform map
Sources
Machines and PLCs
Connected to Qynetic Edge
Measurement systems
Connected to Qynetic Edge
Vision and inspection
Connected to Qynetic Edge
Material flow (AMR, trays)
Connected to Qynetic Edge
Manual stations
Connected to Qynetic Edge
Existing systems
MES
Connected to Qynetic Edge
ERP / order system
Connected to Qynetic Edge
Other existing systems
Connected to Qynetic Edge
Edge
Qynetic Edge
Connected to Machines and PLCs, Measurement systems, Vision and inspection, Material flow (AMR, trays), Manual stations, MES, ERP / order system, Other existing systems, Event log
Core
Event log
Connected to Qynetic Edge, Manufacturing model, Factory Memory, Customer systems (API)
Manufacturing model
Connected to Event log, Analysis layer
Analysis layer
Connected to Manufacturing model, OEE, Quality, APC, Tool Manager, CIM, Planner, Maintenance, Factory Memory, Factory Director, Customer systems (API)
Modules
Factory Director
Connected to Analysis layer, OEE, Quality, APC, Planner, Maintenance, Tool Manager, Factory Memory, Engineers and managers, Operators
Quality
Connected to Analysis layer, Factory Director, APC, CIM, Engineers and managers
APC
Connected to Analysis layer, Factory Director, Quality, Tool Manager
Tool Manager
Connected to Analysis layer, Factory Director, APC, Maintenance
CIM
Connected to Analysis layer, Quality, Customer systems (API)
OEE
Connected to Analysis layer, Factory Director, Planner, Operators
Planner
Connected to Analysis layer, Factory Director, OEE, Maintenance, Operators
Maintenance
Connected to Analysis layer, Factory Director, Planner, Tool Manager, Engineers and managers
Factory Memory
Connected to Analysis layer, Factory Director, Event log
People and systems
Operators
Connected to OEE, Planner, Factory Director
Engineers and managers
Connected to Maintenance, Quality, Factory Director
Customer systems (API)
Connected to CIM, Event log, Analysis layer

Book a call about your factory

Tell us what you make and which machines you run, and we will walk through how Qynetic fits. If you would rather get news and early access, join the waitlist.