Extending FactoryTalk View SE with Non-Rockwell Data Products - ES&E Automation Expo 2025

Summary

This video discusses the integration of non-Rockwell data stores with SE (FactoryTalk View SE), focusing on the differences between temporal data stores (like InfluxDB) and traditional relational databases. It highlights the use of InfluxDB, a time-series database, for applications such as IoT monitoring and real-time data analytics. The video explores how SE natively installs InfluxDB and allows for seamless integration with third-party tools like Grafana and PowerBI. While InfluxDB doesn’t replace historian SE, it offers a simpler, less complex solution for certain use cases, especially with real-time, time-stamped data.

Takeaways

• 💡 FactoryTalk View SE can now be extended to use non-Rockwell data stores such as InfluxDB, an open-source time-series database.
• ⚙️ Users must verify End User License Agreements (EULAs) for third-party or open-source software before commercial use to ensure compliance.
• 🕒 Temporal (time-series) data stores differ from relational databases in that they natively manage and query time-based information with automatic timestamping.
• 📊 Relational databases like Oracle, MySQL, and SQL Server are optimized for structured data with defined relationships, while temporal databases like InfluxDB excel at tracking changes over time.
• 🌡️ Temporal data stores are ideal for IoT, sensor monitoring, and real-time analytics—such as tracking temperature, pressure, and machinery metrics.
• 🚀 InfluxDB was first supported in FactoryTalk View SE version 14 via Data Log Pro, and continues to be supported and enhanced in version 15.
• 💾 InfluxDB OSS 2.7 and InfluxDB Cloud Serverless are the officially supported editions for integration with FactoryTalk View SE.
• 🔁 Data Log Pro supports redundancy by logging data to both primary and secondary HMI servers, providing automatic backfill if one server fails.
• 🧠 FactoryTalk View SE with InfluxDB supports up to 50,000 tags at a 1-second scan rate, though performance depends heavily on server hardware specifications.
• 🔍 Visualization and data access can be done through SE trend and data grid objects, web browser objects, or third-party tools like Grafana, Power BI, and Tableau.
• 🧩 InfluxDB does not replace Historian SE—Historian SE is better suited for large-scale, regulated, or validated environments requiring data compression and compliance documentation.
• 🔒 Connecting external applications to InfluxDB requires additional configuration using Influx tools or the provided CLI to manage authentication and access.
• 📚 Multiple Rockwell Knowledgebase articles document the configuration, commands, and setup steps for Data Log Pro and InfluxDB integration.

Q & A

What is the main difference between a temporal data store and a relational database?

A temporal data store is specifically designed for managing time-based information, allowing historical data tracking and queries at specific points in time. In contrast, a relational database is built around structuring data in tables with relationships between them, and it is not inherently geared for time-series data.

Why is time a default component in a temporal data store?

In a temporal data store, the time stamp is part of the storage mechanism itself. This built-in support for time-based data allows easier querying and tracking of historical information over time, which is not typically a feature of relational databases.

What are some use cases for a temporal data store?

Temporal data stores are useful in scenarios where historical records are important, such as IoT monitoring, real-time data analytics, and tracking equipment data like pressures and temperatures over time.

What is InfluxDB, and how is it related to SE (FactoryTalk View SE)?

InfluxDB is an open-source time-series database that records information with a time stamp. It is integrated with FactoryTalk View SE starting from version 14, where it allows users to log and query time-series data. SE automatically installs InfluxDB, making it easy to use without requiring additional configuration.

How does InfluxDB work with FactoryTalk View SE in terms of data logging?

In FactoryTalk View SE, InfluxDB is used for logging time-series data via Data Log Pro, which connects to InfluxDB. This allows for the collection of real-time data without complex setup. The data can be queried, displayed in trend objects, and connected to third-party tools like Grafana or PowerBI.

Can InfluxDB replace Historian SE?

No, InfluxDB is not intended to replace Historian SE. While both are used for storing time-series data, Historian SE is more robust for managing data across multiple sites and is widely used in regulated industries. InfluxDB lacks some features, such as data compression, and may not be suitable for all use cases.

What limitations should be considered when using InfluxDB with FactoryTalk View SE?

While InfluxDB is built into SE by default, it requires additional configuration for external connections, such as connecting third-party tools. Also, there are hardware requirements for large-scale data logging, as the system needs sufficient resources to handle up to 50,000 tags at a 1-second scan rate.

What are the supported versions of InfluxDB for use with FactoryTalk View SE?

FactoryTalk View SE officially supports InfluxDB OSS 2.7 and InfluxDB Cloud Serverless edition for version 15 and beyond. These versions are tested and supported for use in SE environments.

How does InfluxDB provide redundancy in data logging?

InfluxDB in FactoryTalk View SE can be set up with a primary and secondary HMI server, allowing for redundancy. If one server goes down, the other can backfill the data, ensuring no data loss during downtime.

Is it possible to use InfluxDB with external third-party tools?

Yes, InfluxDB supports API connectivity, which allows external tools such as Grafana, PowerBI, and Tableau to pull and visualize data. However, additional configuration is needed to enable secure access to the database from these external applications.