Skip to content

View selected runtime data in the browser

Use authenticated sessions to view tags, alarms, parameters, audit records, and diagnostics, with controlled operations routed through runtime policy.

  • Browser access
  • Authenticated portal
  • Controlled actions
Dashboard
OverviewTag monitorAlarmsDiagnostics
RunningReviewAllowed
TagValueQualityLine.Speed48.2GoodTank.Level72.4Good
Product form Authenticated Web portal ASP.NET Core · .NET 10
Available pages Tags · Alarms · Parameters Includes audit and diagnostics
License model By runtime points Read-only and over-limit states are visible
Current boundary Web trends are partial Production Internet deployment needs separate validation

Implemented core capabilities

Access control

Protect runtime pages with login sessions and application authorization policies.

Tag monitoring

View current tag values and status in the browser; tag pages are presented as monitoring views.

Alarm operation

Review alarms and use acknowledgement, shelving, or unshelving when policy allows.

Parameter operation

View parameters and submit controlled changes through the supervision runtime path.

Audit query

Query operation history and event records for review and troubleshooting.

Diagnostic maintenance

Filter diagnostic records and use implemented retention-cleanup operations.

A clear four-step path

  1. 1

    Authenticate

    Sign in to the protected Dashboard host.

  2. 2

    Monitor

    Open Overview or Tag Monitor and filter runtime information.

  3. 3

    Act

    Handle alarms or submit permitted tag and parameter changes.

  4. 4

    Trace

    Correlate diagnostics, operation history, and event records.

Where this product fits

  • Browser-based management and duty monitoring
  • Remote issue review
  • Authorized remote operations
  • Alarm handling collaboration

Licensing, requirements, and boundaries

Licensing and editions

By licensed runtime points

Runtime capacity is controlled by the Dashboard point allowance in the license.

Authenticated access baseline

Runtime pages are protected by application authentication and authorization policies.

Deployment assessment required

Production exposure requires TLS, proxy, identity, secret, and network-security design.

Technical requirements

  • ASP.NET Core Web Host targeting net10.0.
  • Client use requires a supported modern browser; production browser support is confirmed by project deployment.
  • Server OS, container, reverse-proxy, and service-hosting combinations require deployment validation.
  • Runtime data, history, audit, and diagnostics capacity depend on the project deployment.