Read-only boundary
No writeback, no control changes, no equipment command pathway.
Governance
Built to protect the control boundary.
LIMIS is designed for executive, IT, OT, security, and engineering review. It reads approved plant context into workflows while keeping control systems outside the product boundary.
For the sponsor, this rigor has a practical payoff: a security and OT review with less ambiguity, clearer approval paths, and a pilot that stays focused instead of becoming an IT project.
System boundary
Approved source stays the source.
The historian or approved integration endpoint remains the operational source. LIMIS makes approved readings useful inside the work context where operators and leaders use them.
Blocked
Plant control layer
SCADA, DCS, PLCs, MES, control networks, and plant-floor systems stay inside their existing boundary.
Approved
Approved data endpoint
Historians or integration services expose reviewed data through the customer's approved path and scoped account.
Visible
LIMIS workflow layer
Operators, supervisors, and leaders see approved context inside rounds, checks, exceptions, handoffs, and records.
Governed by design
Clear controls. Shared responsibility.
Governance should reduce ambiguity before launch. LIMIS keeps the operating model plain enough for site teams to inspect and specific enough for technical review.
Access controls
Role-based access across IT, OT, operations, quality, and leadership users.
Data security
Encryption in transit and at rest, with customer ownership preserved.
Audit and traceability
Completion records, comments, timestamps, exceptions, and review status.
Plain language review
What LIMIS does and does not do.
Governance review should answer four questions: what can LIMIS read, who approved the access, who owns the record, and what LIMIS can never change.
What LIMIS does
- ✓Reads approved historian or integration endpoint data.
- ✓Presents plant context inside operator workflows.
- ✓Supports governed pilot validation and audit-ready records.
- ✓Uses approved access configured for visibility.
What LIMIS does not do
- ×Not a control system.
- ×Not an OT access project.
- ×Not a historian, SCADA, DCS, or MES replacement.
- ×Does not create a plant control path.
MOC pathway
Plant teams define review path, change expectations, source systems, readiness gates, and launch ownership.
Service account
Access is scoped through an approved service account or equivalent reviewed integration pattern.
Data ownership
The customer owns the data. LIMIS presents approved context inside the workflow layer under the agreed model.
Operational evidence
Auditability comes from submitted records, review history, user roles, exceptions, and timestamps.