LIMIS / Data and access

Agree who records, reviews, and has access.

A shared record needs clear responsibilities. Before the pilot, identify who enters readings, who follows up on exceptions, and who approves access.

Responsibilities

Three responsibilities. One shared record.

Operators record the work

Operators record the reading and field notes.

Supervisors follow up

Supervisors check exceptions and decide what needs follow-up.

Technical owners review connections

Operations, IT, and control-system teams review the data source and access path.

The record your team shares.

Actual LIMIS logsheet screen showing recorded process readings, operating ranges and trend charts.
A recorded temperature, its operating range, and recent readings.View full screenshot

Before rollout

Access, history, and retention.

Access and responsibilities
Define the users, account management, and access needed for each role.
Record history and exports
Confirm how entries, edits, review history, retention, and exports will be handled in your deployment.
Plant-system boundaries
LIMIS Connect uses a scoped read-only connection. It does not send commands or change control logic.
Regulated workflows
If your process requires electronic signatures, validation, or a particular standard, check the requirements and supporting evidence.

Before shared use

Agree on the responsibilities.

Tell us who records, who follows up, and who approves access, along with your plant’s record-history and retention requirements.