LIMIS

LIMIS Connect

Live first. Analytics after validation.

A secure, read-only bridge brings approved operational data into the workflow layer only where it is needed. No control changes. No hidden plant-floor pathway.

Request Pilot Review Governance
LIMIS web dashboard showing operational logsheet records and trend context. Live operations review

Plant data to workflow

The connection pattern protects operations.

LIMIS Connect does not ask a plant to change control logic. It makes approved readings visible inside logsheets, rounds, exceptions, and reviews so teams can act with better context.

DCS / PLCSignals
HistoriansContext
MES / LIMSRecords
Other systemsApproved
Read-only LIMIS Connect

Governed bridge for workflow context.

Live Operations

Recent readings, status, trend context, and quality flags where work is happening.

Analytics

Post-validation analysis only after source quality, workflow fit, and governance are trusted.

Tier 1

LIMIS Connect Live

Recent and live plant context inside operator workflows.

  • ✓Approved historian or integration endpoint remains the source.
  • ✓Readings, trends, out-of-range context, and data quality flags appear beside the workflow.
  • ✓Designed as the fastest governed path to first-site value.

Tier 2

LIMIS Connect Analytics

Long-range operational insight after Live is validated.

  • ✓Shift comparisons, multi-month trends, and repeated exception patterns.
  • ✓Analysis grounded in validated workflow records and approved readings.
  • ✓Expanded only when the Live foundation has earned trust.

Sequence

The sequence protects the plant.

Start with a useful, bounded live-data view. Validate the source, workflow, and ownership model. Then decide whether analytics is ready.

01

Live first

Bring trusted readings into the active workflow.

02

Validate

Review data quality, context, and adoption with site teams.

03

Govern

Document boundaries, access, owners, and review gates.

04

Decide

Use pilot proof to choose the next workflow or site.

05

Analyze after

Add analytics only when the foundation is trusted.

Compatibility

Connects to the systems you already run.

LIMIS Connect reads from approved sources through standard, reviewable integration patterns — no rip-and-replace.

Historians & sources

AVEVA / OSIsoft PI, AspenTech IP.21, Honeywell PHD, Canary, GE Proficy, and similar approved endpoints.

Protocols

OPC UA / OPC DA, REST API, ODBC / SQL, and MQTT, depending on the source.

MES / LIMS

Reads approved records from common MES and LIMS systems. [Confirm specific systems.]

Effort to connect

A typical read-only connection is stood up in about 1–2 weeks using an approved service account.

Deployment

Cloud, private, or edge — you decide.

Deployment and data residency are decided with your IT and OT teams up front. Full detail lives on the Security page.

Where it runs

Cloud SaaS by default, with private / on-prem options for sites that require data to stay on their network.

Where data lives

Hosted in [region] in a dedicated tenant, with air-gapped options on request.

Data flow

One-way, outbound from the approved source only. No inbound path to control systems.

Read-only by design

LIMIS Connect is built for visibility, not command, control, writeback, or equipment operation.

Source remains source

Historians and approved endpoints continue to own operational readings. LIMIS presents context inside work.

Reviewable pathway

IT, OT, security, engineering, and operations can review the access pattern before launch.

Measured expansion

Live creates the evidence needed to decide whether analytics, additional workflows, or additional sites are ready.