Pilot hardware from stock
Evaluation kits and pilot quantities ship from stock, so a proof of concept starts in days.
Direct access to Perinet engineers
While you build a proposal, you talk to the people who designed the hardware and firmware.
Help building your first application
Templates and a ready-to-use container development environment get your team started. Perinet maintains the base software.
Cross-border projects stay yours
Open a project in one country and deliver it in another, and it stays with you.
The non-invasive path
Keep the control system. Add an independent data path to IT.
Most brownfield data projects stall at the control system. Getting a signal out means PLC changes, new tags, a gateway, and somebody's validated code. Perinet takes the signal beside the controller instead.
Stays as it is · control path unchanged
The transmitter and the loop, the PLC and its code, the SCADA and the validation all stay exactly as they are.
You add · an independent data path
periNODE or periSNOOP at the signal; one hybrid SPE run to the cabinet, data and 24 V together, daisy-chained; MQTT (secured) and HTTPS REST into your application, with X.509 certificates on every device.
periNODE takes counts, pulses, status contacts and analogue outputs from the terminal block or a newly added sensor. periSNOOP sits in an existing 4-20 mA loop, isolated, with a fail-safe relay; the PLC sees the same current it always did. Both publish over one hybrid Single Pair Ethernet (SPE) cable, data and 24 V together, back to periSTART and standard Ethernet. One run to the cabinet, not one per sensor.
The control architecture stays as it is. Your monitoring data has its own path.
What you install
| Group | Products | Role in a retrofit |
|---|---|---|
| Smart Components | periNODE (4-20 mA, 0-10 V, GPIO, Modbus), periSNOOP, periSWITCH, periSTART | Turn existing sensors and signals into IP-native network participants. Daisy-chain them, then hand over to standard Ethernet. |
| Modular edge computer | periMICA | Runs the MQTT broker, SQL database, dashboards, Node-RED bridges (for example MQTT to OPC UA) and the PKI in containers, at the edge. Your application can run here too. |
Interfaces your IT side already speaks. MQTT (secured) for telemetry, events and logs; HTTPS REST for configuration and reads. Any MQTT broker, SQL database, SCADA, historian or cloud that subscribes; no Perinet middleware in the path. X.509 client certificates on every device, issued and managed by PKI2go on periMICA. Zero-configuration discovery via mDNS; configuration in a browser.
Perinet is built for monitoring and data acquisition around the control system, not for replacing it. Hard real-time control stays on PROFINET or EtherCAT. periSNOOP specifications · Also work with machine builders? Explore periCORE.
Partner economics
Your value is in the solution, not the box
Your customer pays for the application: the OEE system, the energy dashboard, the maintenance service. Perinet is the standard hardware and connectivity layer under it, so your engineers spend less time rebuilding data acquisition and more time on the solution. Perinet hardware is standardised and its price is public, which makes your quote easy to defend.
Build it once, bill it on every site
The second installation is largely a copy of the first. Same devices, same topology, same containers on periMICA. You productise the solution once, and each rollout is still a billable integration project, with far less engineering behind it. Adaptation is software, not wiring.
Engineering hours go into the application, not the plumbing
No register mapping, no PLC tag work, no gateway configuration. Each device announces itself on the network (mDNS), serves its own web interface, and publishes MQTT and HTTPS REST out of the box. Commissioning is done in a browser. The hours you save go into the parts of the project only you can deliver, or into a sharper quote. More contribution margin per engineering hour.
Pilots inside the sales cycle
Live data in front of your customer before the purchase order, not after.
Keep the PLC. Remove the engineering needed to get plant data into IT.
Where partners are already using it
How partners build on Perinet
Zentinel MDS (Spain, Portugal, Latin America) is one of the partners building its own solution on periMICA and periNODE. Perinet supplies the field-data layer. Zentinel supplies the application, the dashboards, commissioning and the customer relationship. The four deployments below are theirs.
OEE on existing packaging lines
Speed, good and reject counts, run and downtime. A chocolate manufacturer needed live OEE without touching machine controls. Signals read from the existing lines. Installed in a few hours during normal operation. Data in SQL; availability, performance and quality dashboards on top.
Read the use case →
Legacy PET blow-moulding retrofit
Blank and bottle counts, jam-level signals, status lights, taken from a machine the customer wanted to keep. Machine and controls untouched. SQL database connected to the MES.
Read the use case →
Compressed-air monitoring
Pressure and flow read from the instrumentation already on the lines, in place of periodic manual audits. Stored in open SQL on a periMICA edge server; partner dashboard for live and historical analysis.
Read the use case →
Production counts into SAP S/4HANA
One pulse per finished part, taken from the terminal block or a newly added sensor. periMICA writes to a SQL database; SAP HANA reads it live through Smart Data Access. No replication platform.
Read the use case →
What Perinet commits to
How we work with integration partners
01
Evaluation hardware, then pilot stock
We ship an evaluation kit to your engineering team so you can verify the encrypted MQTT payload in your own broker, SCADA or database before you quote anything. Within a week of the kit arriving, a Perinet engineer runs a setup call with your team. We confirm kit availability and terms in our reply. Pilot quantities ship from stock; rollout quantities follow a standard lead time we agree with you at project planning.
02
Help building your first application
We walk your engineers through the first steps and help you start building your application. Templates and an easy-to-start container environment on periMICA are part of those first steps. Keeping the base software current over its lifecycle is our responsibility.
03
Cross-border projects stay with you
If you open a project in one country and it is delivered in another, your partner contract protects you as the partner who initiated it.
04
Reseller terms when your volume grows
Place an initial stock order and you become a Perinet reseller, with reseller pricing set in your partner contract.
How to start
Step 1
Evaluate
Evaluation kit on your bench.
Step 2
Set up
Setup call with a Perinet engineer within a week of the kit arriving.
Step 3
Pilot
Pilot from stock on a live customer project.
Step 4
Become a reseller
Reseller agreement with an initial stock order, once your volume justifies it.
Perinet is a good fit if you
- retrofit existing production equipment rather than build greenfield lines
- deliver OEE, energy, condition-monitoring or maintenance applications, or MES and ERP integration
- need plant data without rewriting PLC applications
- already work with MQTT, SQL, SCADA, historians or industrial IT
- want one architecture you can productise and repeat across customer sites
- have measurement points spread across a machine or line, two or three sensors at a time, where a remote I/O station does not pay off
Not the right tool for hard real-time control. That stays on PROFINET or EtherCAT, and we say so.
Questions integrators ask
Before you sign up
We sell to and through approved channel partners. Enquiries from your region go to our regional partner, and one-off orders go to catalogue distributors such as DigiKey and Farnell.
The partner who initiates it. If a project starts in one country and is delivered in another, your partner contract protects you as the initiating partner.
Catalogue distributors serve one-off units and regions without a Perinet partner. Project quantities, pilot stock, engineering support and deal registration come through the partner relationship.
Reseller pricing starts with an initial stock order, and terms are set in the reseller agreement. Territory exclusivity applies at distributor level and is not part of the integrator programme.
From Perinet. Place an initial stock order and you become a Perinet reseller with reseller pricing. Otherwise you buy per project at end-customer pricing.
No mandatory training. Within a week of your kit arriving, a Perinet engineer runs a setup call and sets up a container development environment for your first application. Documentation is public.
No. Perinet delivers the connection from sensor to IP network. Control, SCADA and cloud stay with the systems your customer already runs.
Devices publish MQTT and HTTPS REST natively. For OPC UA targets, a Node-RED container on periMICA bridges MQTT to OPC UA.
No, and it is not meant to be. Perinet carries monitoring, energy, quality and condition data that has no cycle-time requirement. PROFINET and EtherCAT stay where they are.
Every device carries its own X.509 certificate; communication is encrypted; clients without a valid certificate are refused. Security is at the device, not only at the perimeter, which is where the EU Cyber Resilience Act is heading.