Back to all posts
Plant Data7 min read·October 25, 2026

How Should Production Teams Access Historian Data?

TB
ThynkBlox Automation Team
Automation Engineering

Give users read-only historian access through an approved query or reporting interface, with permissions assigned by role. Define which tags each role can see, whether users can export data, and which query limits apply. Keep administration rights separate, and make access removal part of the handover before anyone starts using the service.

What should read-only historian access allow?

Start with the decisions people need to make. A production supervisor might need shift trends, equipment states and production counts. A maintenance lead might need selected equipment histories. Neither requirement is a reason to grant user-management or historian-configuration rights.

Write the permission boundary as a list of allowed actions. Avoid a request that says only “give the team historian access”.

A reporting role should normally be designed to:

  • Open approved dashboards and reports.
  • Read permitted tags within an agreed history window.
  • Change permitted filters, such as equipment, shift and time range.
  • Export only where explicitly authorised.
  • View the units, timestamps and quality information needed to interpret the results.

Keep changes to stored values, tag configuration, collection settings, permissions and system administration outside that role.

Treat read access, export access and report editing as separate decisions. Someone who needs to inspect a trend does not automatically need to download its underlying records or publish a report for everyone else.

Which interface should production teams use?

Choose an interface that matches the task and can enforce the agreed boundary. For routine production reviews, start with approved reports or dashboards. For investigation, consider a query interface with restricted datasets and controlled parameters.

Ask the system owner to demonstrate the permissions in the proposed interface. A screen labelled “viewer” is not acceptance evidence by itself.

Access routeAppropriate useWhat to specify
Approved dashboardRepeated checks of known measuresVisible tags, filters, refresh behaviour and export rights
Parameter-based reportShift, equipment or batch reviewAllowed parameters, history window and output format
Restricted query interfaceInvestigations requiring flexible selectionPermitted datasets, query limits and cancellation
Scheduled reportRecurring information for a defined audienceRecipient ownership, delivery controls and expiry

Avoid giving users an unrestricted query console simply because it is the quickest route to the data. If flexible queries are necessary, specify the permitted operations and have the administrator demonstrate that writes and administrative actions are denied.

Capture these boundaries in the functional design specification, alongside the report behaviour and acceptance checks.

How should you decide which tags each role can see?

Build the tag list around a purpose and an equipment scope. “All production tags” is too broad unless someone has reviewed what that includes.

For each role, identify the permitted plant areas, equipment groups and measures. Decide separately whether users may browse tag names outside that scope. Treat tag descriptions, calculated values and report drill-downs as part of the same review.

Use the following questions when approving visibility:

  • Which operational decision requires this tag?
  • Does the user need raw history, a summary, or both?
  • Should the role see only its own line or several production areas?
  • Does a calculation use inputs outside the role's permitted scope?
  • Should older history have a different access boundary?

Define what happens when a new tag appears. Prefer a deliberate approval rule over silently adding every new tag to a reporting role.

Also define how reports explain the data. Show units and make time-zone and aggregation choices clear. Agree how missing or poor-quality readings appear. For calculated production measures, our guide to what an OEE number hides provides related questions to ask before relying on a headline figure.

Should read-only users be allowed to export data?

Approve exports explicitly. Make the decision by role, dataset and purpose, rather than treating a download button as a harmless convenience.

Specify whether the role may export a chart image, a summary table or individual historical records. Set an approved time range and record limit for each permitted output. Include spreadsheet connections and automated downloads in the review where those routes are offered.

Treat an exported file as a separate copy: do not assume removing historian access will also remove files already downloaded. Give the team clear instructions on approved storage, sharing and disposal.

For scheduled exports, assign an owner to the recipient list. Require a review when people change jobs or leave the organisation. If the purpose is a shift meeting, consider whether an approved summary meets the need before permitting unrestricted raw-data exports.

How do you control expensive queries?

Set query limits alongside permissions. A read-only designation should never be your evidence that a query is acceptable for the available service capacity.

Agree limits for:

  • The history window requested in one query.
  • The number of tags selected together.
  • The smallest permitted time interval.
  • Returned records and export size.
  • Concurrent queries and automatic refresh.
  • Query duration, cancellation and timeout behaviour.

Choose actual limits through testing on the intended reporting route. Include a representative shift review, a long-range investigation and simultaneous use by the expected audience.

Define what users see when they reach a limit. Give a clear explanation and a useful next step, such as narrowing the time range or requesting a scheduled report. Do not resolve a rejected query by granting broader privileges.

Where larger investigations are necessary, ask the system owner to assess a separate reporting copy or scheduled extraction. Define its refresh delay and make that delay visible to readers.

What would an access request look like in practice?

The following example is illustrative, not a recommended permission set for every plant.

A production supervisor needs to review a packaging line after each shift. The agreed request could read:

Permission areaIllustrative agreement
IdentityNamed user assigned to the packaging-supervisor role
Tag visibilityApproved counts, run states and downtime tags for the assigned line
HistoryRecent shifts through a parameter-based report
ExportsSummary table only, saved in the approved team location
Query controlsFixed tag selection and bounded time-range filters
AdministrationNo configuration, account management or stored-data changes
RemovalRole owner requests removal when the assignment ends

The request should name both the person approving the business need and the administrator implementing it. Give each role an owner who can explain why its permissions remain necessary.

How should you test access before handing it over?

Test with an ordinary reporting account. Use both allowed and forbidden actions; a successful dashboard login proves only part of the design.

Before handover, check that:

  • Approved tags and reports are available.
  • Unapproved tags remain inaccessible through search, direct queries and drill-downs.
  • Attempts to change data, configuration or permissions are rejected.
  • Export restrictions apply to each enabled download route.
  • Oversized queries meet the agreed limit behaviour.
  • Units, timestamps, quality indicators and refresh information are understandable.
  • Removing the role prevents further access through the enabled routes.

Keep a record of the expected and observed result for each check. Resolve failed boundaries before widening access.

How should access be removed?

Agree the removal process before onboarding users. Name the role owner, the administrator responsible for removal and the events that trigger it.

Include job changes, temporary assignments, contractor departures and people leaving the organisation. Review ongoing membership as well as individual removal requests.

Cover more than the interactive login. Include active sessions, saved connections, issued access credentials and scheduled report recipients wherever these exist. Test removal using a representative account and verify that previously working routes now refuse access.

Keep integration identities separate from personal reporting access, with their own owner and removal process. Avoid sharing a reporting account across a shift team.

What common mistakes should you avoid?

Copying an administrator's permissions. Build the reporting role from the required actions and datasets.

Hiding controls without testing permissions. Verify that forbidden actions fail through every enabled route.

Approving exports by default. Decide what may leave the reporting interface and who may receive it.

Leaving queries unbounded. Agree workload limits and test their behaviour before handover.

Treating a dashboard as a control screen. Keep this access pattern for historical review and reporting. Requests to operate equipment, change settings or support safety-related decisions require a separate design review; involve a qualified assessor for safety-related design.

For help defining the access boundary and acceptance checks, see our automation services.

What are the frequently asked questions?

Can production users have read access without administration rights?

Make that a selection and acceptance requirement for the chosen interface. Have the administrator demonstrate permitted reads and rejected administrative actions using the proposed reporting role.

Does read-only access include permission to download data?

Specify downloads separately. A role may be approved to view a report while being denied exports, subject to the controls available in the chosen interface.

Who should approve access?

Assign approval to the person accountable for the dataset and operational purpose. Have an administrator implement the approved role and record who owns future membership reviews.

What if the interface cannot enforce the required restrictions?

Do not describe that route as meeting the requirement. Use a narrower approved report, assess another interface, or revise the design with the system owner before granting access.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.