📌 What Are Production Entity Connections?

Every factory has the data — temperatures, pressures, cycle times, test results, work order statuses. The problem is that it usually lives in places your operators can't see in real time: a PLC on the line, a SCADA screen in a control room, an ERP database upstairs, an MQTT broker that IT set up last year.

Production Entity Connections in Next Plus pull that data straight onto your machines, lines, and cells — so the same screen your team uses for work orders also shows live equipment values, current status, and what's happening right now.

No more walking to a control panel to check a temperature. No more pasting cycle times from a report. The data shows up where the work happens.

🏭 First, What Is a Production Entity?

A Production Entity is anything physical you want to track in Next Plus — a CNC, a furnace, a mixer, a weighing scale, a full assembly line. Each one has its own page with statuses (Running, Down, Setup, Fault), triggers, and live parameters.

A Connection is how Next Plus reads live values off that physical resource. One Production Entity can pull data from several sources at the same time — for example, a temperature from a PLC, a last-test-result from a database, and a cycle counter from a sensor — all on one screen.

🛠 The Four Connection Types

Next Plus supports four ways to bring live data in. Each one fits a different kind of source.

Connection Type	When to Use	Common Example
OPC UA	PLCs, SCADA systems, historians — anything on the factory floor that already speaks the standard industrial protocol	Reading temperature and pressure from a Siemens PLC
SQL	Data that already lives in a database — MES, ERP, LIMS, historian SQL views	Pulling the latest QA test result for a serial number
API	Custom integrations — your own scripts, vision systems, test benches, or anything that can make an HTTP POST	A Python script pushing per-batch test results from a custom rig
MQTT	Modern IoT setups, sensors, and gateways that publish messages to a broker	Streaming live values from a wireless sensor network

Not sure which one fits? In most cases the choice is made for you by the equipment — if it speaks OPC UA, you use OPC UA. If your data is already in a database, SQL is the easiest path. If you have a custom data source or your own integration code, API is the path. If your factory has gone the IoT route, MQTT is built for it. Your CS team will help you pick.

📊 What You Get Once It's Connected

Once a Production Entity is reading live data, several things light up across Next Plus:

Live dashboards — values update on screen in real time, so operators and shift leads see the current state without refreshing
Automatic status changes — a furnace can flip itself to "Down" when temperature drops below a threshold, no human input needed
Triggers and alerts — get notified the moment a parameter crosses a limit
OEE & KPI calculations — uptime, performance, and quality numbers built from real data, not estimates
Historical reports — every value is logged, so audits, root cause analysis, and trends all work without extra steps

🔒 Read-Only, Always

A question we hear a lot from IT and plant engineering teams: "Is Next Plus going to control my machines?"

No. Every connection type is strictly read-only. Next Plus reads values from your equipment and databases — it never writes back, never sends commands, never changes settings. Your PLC engineers stay in control of what happens on the line; Next Plus just makes the data visible where the work happens.

🏭 Common Scenarios

⚙️ PLC on the Line — OPC UA

Before: Operators walked to the PLC panel every shift to write down temperatures and cycle counts on paper.

After: An OPC UA connection reads those same values once a second straight onto the Production Entity. The shift report builds itself.

→ Outcome: No clipboards, no transcription errors, complete history.

🗄 Test Result in the ERP — SQL

Before: QA results lived in the ERP, but operators on the line couldn't see them without logging into a separate system.

After: A SQL connection pulls the latest test result every 10 seconds and shows it on the workstation's PE screen.

→ Outcome: One screen, one source of truth, faster decisions.

🔧 Custom Test Rig — API

Before: A custom-built test bench ran a Python script to record results into a local spreadsheet. The results lived on one PC and nobody else saw them in real time.

After: The Python script makes an API push to Next Plus every time a test finishes. The result lands on the test bench's Production Entity immediately.

→ Outcome: Custom equipment is a first-class data source — no spreadsheets, no manual entry, no waiting.

📡 Wireless Sensor — MQTT

Before: A cold-chain sensor logged temperature every minute but the data sat on the sensor's own dashboard.

After: An MQTT connection subscribes to the sensor's topic. Values arrive in Next Plus in real time and trigger an alert if they drift.

→ Outcome: Compliance becomes automatic, problems get caught before they spoil a batch.

💡 Real-Life Examples By Industry

Here's what this looks like across different kinds of factories. See if one of these sounds like yours:

🏥 Medical Devices

Use Case 1: Autoclave Temperature Monitoring

Before: Sterilization cycles required manual chart recorders and someone watching the dial.
Connection: OPC UA reads autoclave temperature and pressure directly from the PLC into the Production Entity.
Benefits:

✅ Continuous validation evidence
✅ Audit-ready logs
✅ Alerts the moment a cycle drifts

Use Case 2: Batch Release From QA Database

Before: Release decisions waited on QA emailing the test report.
Connection: SQL pulls the latest QA verdict for the active lot onto the line's Production Entity.
Benefits:

✅ Operators see release status in real time
✅ ISO 13485 traceability
✅ Faster device release

🧃 Food & Beverage

Use Case 1: Cold-Chain Sensors

Before: Freezer temperatures were checked by hand twice a shift.
Connection: MQTT streams sensor readings continuously. Triggers fire if temperature drifts out of range.
Benefits:

✅ HACCP-ready continuous monitoring
✅ Early warnings before product is at risk
✅ Full audit trail

Use Case 2: Filling Line Throughput

Before: OEE was guessed at the end of the shift from production logs.
Connection: OPC UA pulls live counter and status data off the line PLC.
Benefits:

✅ Real OEE numbers, not estimates
✅ Shift performance visible live
✅ Downtime caught immediately

✈️ Aerospace & Defense

Use Case 1: Torque Test Bench

Before: Torque values were captured on the test bench's own screen and re-entered into the batch record.
Connection: OPC UA reads values directly from the test bench controller onto the Production Entity.
Benefits:

✅ Zero transcription errors
✅ Per-serial-number traceability
✅ Faster audit evidence

Use Case 2: SAP Work Order Status

Before: Operators couldn't see the SAP status of the work order they were running.
Connection: SQL reads the current work order status from the SAP database and shows it on the line.
Benefits:

✅ Live ERP-to-floor alignment
✅ Fewer wrong-order runs
✅ Less back-and-forth with planning

🧪 Pharma / Cosmetics

Use Case 1: Mixer Cycle Monitoring

Before: Batch records included mixer speed and time written manually after the cycle.
Connection: OPC UA reads mixer parameters live for the full duration of the batch.
Benefits:

✅ Complete batch profile, automatically
✅ GMP-compliant electronic records
✅ Easy deviation investigation

Use Case 2: Stability Lab Results From LIMS

Before: Stability data lived in the LIMS and was reviewed weekly.
Connection: SQL pulls the latest result per batch into the Production Entity.
Benefits:

✅ Daily visibility into stability
✅ Faster trend detection
✅ Smoother batch release

📱 Electronics Assembly

Use Case 1: Solder Reflow Profile

Before: Reflow oven profiles were documented on paper attached to each tray.
Connection: OPC UA reads oven temperatures and conveyor speed live, tied to each batch.
Benefits:

✅ Digital reflow profile per batch
✅ Process control visibility
✅ No paperwork on the line

Use Case 2: ICT Test Results From MES Database

Before: Functional test results were reviewed in a separate MES screen.
Connection: SQL pulls the latest pass/fail per serial number onto the Production Entity.
Benefits:

✅ One screen for the operator
✅ Faster rework decisions
✅ Better serial-level traceability

Even if your equipment or process isn't in this list — we've got options.

Whether you're dealing with:

Older machines that still expose data through OPC UA or Modbus gateways
Existing MES, ERP, or LIMS databases your team already trusts
Custom equipment or scripts that can push data over HTTP
Modern IoT sensors publishing to a broker
A mix of all of the above across the same line

We'll help you map it out.

Use the chat button to start a conversation.

🤔 When Should You Consider a Connection?

If any of these sound familiar — it's time:

Operators are checking values on a separate screen and writing them down
Your OEE numbers are estimates, not real measurements
You want alerts the moment something goes wrong, not at the end of the shift
Audit evidence is scattered across systems instead of attached to the batch
The data exists somewhere — but not where the work happens

🚀 How to Get Started

Step 1 – Find the data
What value does your team wish they could see live? A temperature? A test result? A counter?
Step 2 – Find the source
Is it on a PLC, in a database, or coming from a sensor? That tells us which connection type to use.
Step 3 – Set it up together
Your CS team will guide you and your IT through the network, credentials, and configuration.
Want help mapping it out?
Contact us via chat and we'll walk through what's available at your factory.

🔌 Production Entity Connections: Pull Live Data From Machines, Sensors & Databases