The NEO Platform

NEO PI

NEO PI captures, contextualizes and preserves every reading from every sensor, machine and piece of equipment on the plant floor — and gives that history back as a single source of truth, queryable and auditable.

A complex network of interconnected industrial sensors and machines in a pharmaceutical manufacturing plant, with a centA complex network of interconnected industrial sensors and machines in a pharmaceutical manufacturing plant, with a cent

Key capabilities

No more orphan data
Sensors recording into spreadsheets, isolated dataloggers or systems nobody ever queries.
Context, not just a number
24.7 means nothing. "Cold room temperature, cold chain area, good quality, 14:32" means everything.
Raw data preserved forever
What arrived from the device is immutable and never deleted — a prerequisite for any defense in an audit.
Batch records fed automatically
Eliminate manual transcription of process values into the batch record.
Connect what you already have
No need to replace the installed base — PI adapts to the equipment protocol, not the other way around.

NEO PI is not a sensor database. It is your plant’s memory: what happened, when, at what measurement quality, and under which process asset.

The name is no accident. NEO PI plays the same role a classic process information system plays in a plant — with one difference: it was born to operate inside a regulated ecosystem, integrated with the electronic batch record.

See it running

A walkthrough of the console: live dashboard, asset navigation, trends and audit trail.

Connections

LoRaWAN
Long-range, low-power wireless sensors — cold rooms, warehouses, areas with no network infrastructure. Multiple measurements per transmission.
OPC-UA
The modern automation standard — PLCs, SCADA and control systems. Preserves the OPC server’s statusCode and sourceTimestamp.
OPC-DA
Legacy equipment still in operation — reads value, quality and timestamp in the classic standard.
MQTT
Industrial IoT brokers, edge gateways, devices publishing to topics.
HTTP / REST
Any system able to POST — point-to-point integrations, proprietary gateways, lab scripts.

When the format is proprietary: codecs

Not every manufacturer follows a standard. A codec is a declarative expression that translates a vendor’s raw payload into measurements — configured through the interface, tested before saving, with an AI-assisted draft from a sample payload. In practice: equipment sending {"temp_raw":247} starts recording 24.7 °C without a line of code and without waiting for a release.

Data goes out too: forwarding

Forwarding rules deliver readings to external systems by webhook (HMAC-signed, token-authenticated) or MQTT publication, with optional payload transformation, batched delivery, a durable retry queue and automatic shutoff when a destination keeps failing.

Context, not an identifier

Navigate by plant › area › asset instead of by a raw device identifier. Every element carries its live measurements, its properties and its permissions.

Jerarquía de activos — planta, área y activo con mediciones en vivo

Overlaid trends

Several sensors on the same chart over any date range, with aggregations from raw to monthly and CSV export.

Tendencias — varios sensores superpuestos en un rango de fechas

Integration with NEO EBR

The electronic batch record drives production: procedures, work orders, in-process controls. Historically, process values reach that record by manual transcription — an operator reads the display and types. That is simultaneously the slowest and the most fragile step of the record: subject to misreading, typing errors and delay, and it demands second-person review precisely because of that.

With NEO PI, the value comes from the historian:

  • the in-process control in NEO EBR reads the measurement directly from the corresponding asset in PI
  • the value arrives with its origin timestamp and quality, not the time someone typed it
  • the batch record points to immutable data, traceable back to the raw event
  • out-of-range deviations stand out against the full history, not an isolated point

EBR consumes PI through the Read API: a navigable namespace (site/area/asset/measurement), current-value reads, history queries with aggregations, and live event subscription over SSE — all authenticated by scoped read keys that limit each consumer to exactly the assets and measurements it should see.

That API is an open protocol, and nothing about it is NEO-specific. NEO W&D reads dispensing weights from it the same way, and any third-party system — MES, LIMS, ERP, a BI tool — consumes it over plain REST and SSE. PI is a layer your plant owns, not a captive component of one suite.

How the data flows

Data enters through any of the protocols, is preserved raw, gains asset context in the Asset Framework, and leaves by three paths.

Plant floor
  • Machines and PLCs
    reactors · lines · filling — OPC-UA, OPC-DA
  • Equipment
    cold rooms · autoclaves · stability chambers — LoRaWAN
  • IoT devices
    wireless sensors · gateways — MQTT, HTTP, codecs
NEO PI
  • Ingestion
    raw preserved, immutable
  • Time series
    tag catalog · aggregations
  • Asset Framework / UNS
    site › area › asset › measurement
Consumption
  • NEO EBR
    batch record — Read API, scoped key
  • NEO W&D
    weighing and dispensing — same open API
  • Operations and Quality
    trends · investigation
  • Third-party systems
    MES · LIMS · ERP · BI — REST, SSE, forwarding

What each team gains

For Quality
  • Immutable, permanent raw data
    The original event is never deleted or edited. Any number on screen traces back to what the device actually sent.
  • Hash-chained audit trail
    Configuration changes are recorded in a chain with integrity verification — retroactive tampering is detectable.
  • Electronic signature (21 CFR Part 11)
    On sensitive operations, with a signing PIN distinct from the login password and a meaning declared at the moment of signing.
For Operations
  • Real real-time
    Readings appear as they arrive, with no page reload.
  • Failure recovery
    Events that could not be decoded stay visible and can be reprocessed after the fix — nothing is lost silently.
  • Role-based permissions
    With roles the organization customizes itself.
For IT and Automation
  • No rip-and-replace
    Five native protocols plus codecs for everything else.
  • No lock-in
    Data leaves by API, forwarding and live subscription — PI is a layer, not a final destination.
  • Unified Namespace aligned
    ISA-95 / IEC-62264: semantic hierarchy, current state, event-driven ingestion and decoupled publication. Container deployment, multi-architecture.
For the Business
  • Less manual transcription
    In the batch record — fewer errors, less rework, less review time.
  • Shorter deviation investigations
    History is contextualized and available, not scattered across dataloggers and spreadsheets.
  • A base for what comes next
    Continuous monitoring, trend analysis and process alarms finally have somewhere to read from.
Let’s digitize your operation.
Talk to an expert

Explore more