Why Nexen
Three principles behind the Nexen platform
1
Nexen is the application and orchestration layer
- Business logic, UX, and configuration
- Governance, roles, and access rules
- Fabrity’s own software, licensed to you
2
Heavy engines: best-of-breed, replaceable
- Time-series engine, MQTT broker, protocol gateways
- Proven technologies, not rebuilt from scratch
- Picked to fit your environment, replaceable later
3
Start with the product, adapt from there
- We connect a set of machines.
- You watch it run on your live data.
- Then we discuss integrations and adjustments
The Nexen platform, layer by layer
| Layer | What it does | Nexen module |
|---|---|---|
| Visualization and analytics | Dashboards, machine cards, plant maps, asset trees; ML models and AI agents work on the same data | Nexen Insights Front-end |
| Data access and services | Role-based access, exports, report aggregates, and integrations with MES, QMS, and ERP | Nexen Data Services API + reporting mart |
| Storage | Readings and context data in hot, warm, and cold tiers, with retention set per signal | Nexen Time-Series Store Swappable engine |
| Configuration and management | Unified namespace, asset catalog, data quality rules, and edge device management | Nexen Control Center Web + API |
| Edge acquisition | Reads machine data, normalizes it, checks quality, buffers offline, and publishes to the bus | Nexen Collector Edge worker |
| Machines and OT | Where the signals come from: controllers, meters, sensors, cameras. Nothing gets ripped out—and where a measurement point is missing, we install the meters ourselves | Your existing estate Meters we add where needed |
Across every layer: security to IEC 62443, role-based access with an audit trail, and lineage that traces any number on a dashboard back to the reading it came from.
Nexen Suite—an overview of main functionalities
Where Nexen creates value
Energy and utilities management
Electricity is where most plants start, on meters we add or ones you already have. Gas, water, heat and compressed air run the same way, costed per department.
OEE and downtime analysis
Availability, performance and quality computed from machine signals rather than shift reports. Orders and shifts from your own systems give the numbers their context.
Predictive maintenance
Vibration and temperature sensors go on machines with no controller to read from. Trends and alarms from day one, models once there is enough history.
MES-class systems
Nexen supplies the shop-floor data layer an MES expects to sit on top of. Where no MES is in place, it covers that ground itself.
AI vision
Cameras become a data source, with image analysis running on edge devices. Only the events reach the platform, not the video.
Product quality and process optimization
Process parameters and quality results sit in one store, so a model can show which settings hold quality. Recommended setpoints go through the usual approval.
Emissions and ESG reporting
The same meter readings mapped to CO2, water and waste. Reported figures then come from measurements rather than from a spreadsheet rebuilt each quarter.
Cost and energy per unit produced
Meter readings joined with production counts, so cost per unit stops being a plant-wide average. Per line, per product, per shift if you need it.
Nexen’s logical architecture: from data sources to applications
Data acquisition—how it works in Nexen
How we deploy the Nexen IIoT platform
On-premises
- Process data must stay inside the plant
- The plant has no reliable internet line
- Your IT team already runs its own servers
Hybrid (recommended)
- Data leaves the plant only where your policy allows it
- Acquisition keeps running if the link drops
- Several plants, one central view
Cloud
- Data from every plant lands in one place
- Reporting and analysis load varies through the month
- No servers or databases for your team to maintain
Nexen goes in without touching your OT network
No new way into the OT network
Nexen Collector connects outbound only and reads what your equipment already exposes. Nothing is re-addressed or reprogrammed.
Identity and access by role
Access runs on the directory you already have—AD, Entra ID or Keycloak. Permissions are allow-only and add up across roles.
Control only through the abstraction layer
Writeback is off by default. When on, each command needs an approval, leaves a record and never touches safety logic.
We design against IEC 62443 and NIS2 from the start. Compliance stays yours as the operator; we supply the evidence—zone diagrams, permission matrix, hardening baseline, audit logs.
Production keeps running. Acquisition and changes never halt or destabilize the process.
Start with an audit or a pilot
Workshop and audit
Find out what your data is worth before you spend anything on collecting it.
Pilot or PoC
One line, your machines, your numbers. If they don’t work, you stop there.
Insights on Industrial IoT and AI
LoRaWAN security in production facilities: Secure by design, safe by segmentation
LoRaWAN security explained: discover how encryption, key management, and network segmentation help protect industrial IoT and OT environments.
Industrial telemetry: from data to decision
Industrial telemetry with Nexen Suite turns data into insights for production planning, energy management, and predictive maintenance.
OEE: A basic KPI for optimizing manufacturing processes
OEE (overall equipment effectiveness) is a key KPI for optimizing manufacturing, reducing downtime, improving quality, and boosting production efficiency.
