What will historize when an application engine is properly configured for historization?

When an application engine is properly configured for historization, it captures and stores data from both the object attributes specifically configured for historization and the engine attributes. This comprehensive historization allows for a detailed analysis not only of the operational parameters of the objects being monitored but also of the performance and resource metrics of the engine itself.

Object attributes are crucial because they represent the actual data points relevant to the processes being observed, such as temperature readings, pressure levels, or production counts. These attributes are configurable based on the specific needs of the application, allowing users to select which data should be historized for reporting and analysis.

In addition to this, engine attributes provide insights into the health and performance of the application engine that performs the historization. This includes data like CPU usage, memory consumption, and throughput rates. Collecting both types of data ensures a holistic view of the system's operation, enabling better performance monitoring, troubleshooting, and optimization.

By historizing both object attributes and engine attributes, organizations can have comprehensive datasets that enhance operational decisions, improve maintenance strategies, and provide valuable insights into both the processes being monitored and the assets executing those processes.