Configuring SEL RTAC for Local Data Viewing

When the utility-hosted web viewer fails, the RTAC may still be receiving the substation data; the practical question is whether you need a quick live-value check, a local operator display, or a separate SCADA system for routine operations and history.

Which viewing path matches the operator’s need?

Three approaches fit the described signal path: inspect live values through the RTAC’s browser interface, build an HMI tied to RTAC tags, or connect a separate SCADA front end. They differ in effort and capability. A browser view is a quick diagnostic or occasional glance, not a full operator workstation. An HMI adds a purpose-built display, while a separate SCADA system is the stronger path when users need logging, trends, alarms, or a larger operating environment.

Approach	Location or tool	Best fit	Constraint to check
Live tag view	RTAC web page or configuration software online view	Occasional inspection of current values	Not a user-friendly display for continuous operator use; browser features can depend on RTAC firmware.
RTAC HMI	SEL Diagram Builder and RTAC HMI feature	Local display for a defined set of values	Check HMI licensing, RTAC loading, and limits in logging and trending.
Separate SCADA	External SCADA front end communicating with RTAC	Routine operations, more functionality, or data history	Requires configuration and a suitable RTAC protocol server; may add software and engineering cost.

For a once-a-day glance, begin with the live tag view: it is the lowest-effort option described. For an operator who needs a screen throughout a shift, evaluate an HMI but test its performance on the actual RTAC. If the requirement includes sustained trends or data retention, evaluate a separate SCADA or logging system instead of expecting the HMI to supply historian functions.

What does the RTAC browser show?

The RTAC receives data from the office-side DAQ EtherPolls and forwards data to the power provider in the stated arrangement. A failure in the provider’s web viewer does not by itself show that the RTAC has stopped receiving those values. Logging into the RTAC’s own web page can provide access to live data through its tag processor when that capability is enabled.

Use this view to answer a narrow question: is a particular value arriving at the RTAC now? It is not equivalent to a designed operator display. An online tag list is less convenient for scanning many points, and the evidence describes it as unsuitable for someone to watch all day. The RTAC web interface can also vary by firmware; the dashboard’s Licensed Features link may not appear on every version.

Check the value’s freshness as well as its displayed magnitude. Compare the point with a known field condition or with the source device’s indication, and inspect communication status for the relevant client or server protocols in the RTAC configuration software. A visible value alone does not prove the point is updating or that its engineering meaning is correct.

When is the configuration software online view useful?

The RTAC configuration project provides another live inspection path. The described workflow is to obtain the configuration software, retrieve or import the RTAC configuration file, open it in the software, and use its online function to inspect live values and protocol connection status. The named software is SEL-5033 AcSELerator RTAC. Confirm the exact software and project compatibility against documentation for the RTAC model.

This approach is useful during troubleshooting because it connects the displayed value back to the configured tag and communications setup. It is not the same as installing an HMI or building a routine operator application. Treat the project as a production configuration: use an authorized account, preserve a known-good copy, and avoid downloading changes just to inspect data. Keep the examination online/read-only unless an approved change is planned.

Where the browser tag view offers a quick glance, the project’s online view offers a more engineering-oriented way to examine data and connectivity. Neither supplies long-term trend storage by itself. Use the external logging or SCADA path when historical records are part of the requirement.

Should you build an RTAC HMI?

An RTAC HMI can present selected values on a purpose-built display, but verify the feature and license before investing engineering time. In the RTAC browser dashboard, check Licensed Features for an HMI license. If the link is absent, firmware may be a factor; consult model-specific documentation or SEL rather than assuming the option is unavailable. The HMI feature may require licensing, and pricing can depend on the account and quote, so confirm current terms directly.

With the required feature available, SEL Diagram Builder is the identified tool for creating the HMI. SEL relay templates may also be available to account holders. Plan the screen around the values operators need, and confirm that the relevant RTAC tags are exposed correctly. A display that renders values is not automatically a historian: the RTAC HMI has limited data logging and trending capability in the described experience.

Performance is a deciding criterion. An HMI can run slowly enough to be unusable on a particular RTAC configuration. Before committing to it for continuous use, ask SEL to assess expected RTAC loading before and after adding the HMI, then test response under representative operating conditions. Do not treat claims of a typical upgrade duration or cost as a guarantee for the installed model or project.

When does a separate SCADA front end fit better?

A separate SCADA front end is the better candidate when the need extends beyond a local glance: multiple operator screens, data retention, or more capable trends and alarms. The stated architectural requirement is to configure a DNP3 server in the RTAC so the external SCADA system can retrieve RTAC data. Confirm the required server configuration and point mapping for the installed project and the chosen SCADA driver.

Some SCADA products can import RTAC tags, which can reduce the effort of bringing in a large point set. For a small number of tags and one screen, a lightweight or free option may be sufficient; licensing, feature limits, support, and deployment requirements must be checked for the selected product. If the application requires durable historical data, define where the data will be stored and how the front end consumes it. A relational database is one possible architecture, but select it based on retention, reporting, and operational requirements rather than assuming the RTAC HMI will fill that role.

For straightforward local visibility, a second SCADA system may be unnecessary. For operators relying on the display during normal work or needing history, the additional configuration can be justified by the richer front end and dedicated logging capability.

How should you bring up a local view safely?

Use a staged decision process so a screen project does not obscure a communications fault or introduce an unplanned production change.

1. Confirm the data path. Identify the target points and verify that their values reach the RTAC from the DAQ EtherPolls. Check relevant protocol connection status and compare sample values with a known source indication.
2. Try live inspection first. Log in to the RTAC web page and look for the live tag processor view. If you have the authorized project and SEL-5033 AcSELerator RTAC, open the matching configuration and use its online view to inspect values and client/server status.
3. Classify the use case. Choose direct live inspection for occasional checks; evaluate an HMI for a limited local display; select a separate SCADA front end when operators need sustained functionality or historical data.
4. Check prerequisites. For an HMI, inspect Licensed Features, verify model and firmware support in the applicable documentation, and confirm licensing. For external SCADA, plan the RTAC DNP3 server setup, point mapping, and data storage requirements.
5. Assess loading and change risk. Ask SEL about RTAC loading before and after adding HMI features. Back up the existing project and schedule configuration or firmware changes through the site’s normal change process. Review firmware changes against model-specific documentation and the installation’s cybersecurity requirements.
6. Build and test the selected display. Create only the needed screen and points initially. Test with representative communications and operating conditions before relying on it for routine work.

How do you verify the replacement view?

Test the entire chain rather than just whether a value appears on a screen. Confirm that the RTAC point changes when the source changes, that the displayed point is the intended tag, and that a lost source communication is visible through an appropriate status indication. Check for stale or frozen values as well as incorrect values.

For an HMI, inspect screen responsiveness and RTAC loading under representative conditions, then validate each displayed value against the project tag and a trusted source. For external SCADA, verify the DNP3 server connection, point mapping, update behavior, and any configured storage or trend display. Confirm the operator display remains useful during a communications interruption and recovers when communications return. Finish by documenting which values were checked and the observed connection status; only then place the local view into routine use.

Frequently asked questions