Top 5 Control Engineering articles, May 11-17: HMI-historian integration, 7 benefits of HMI-historian integration, feed forwards augmenting PID control, more
Articles about HMI-historian integration, 7 benefits of HMI-historian integration, feed forwards augmenting PID control, data historians and HMIs, and getting an automation project approved were Control Engineering’s five most clicked articles from last week, May 11-17. Miss something? You can catch up here.
Control Engineering Top 5 most read articles online, for May 11-17, covered HMI-historian integration, 7 benefits of HMI-historian integration, feed forwards augmenting PID control, data historians and HMIs, and getting an automation project approved. Link to each article below.
Put big data to work: Use the past to change the future with real-time input. Integrating human-machine interface (HMI) and historian software can produce hybrid screens comparing the past to the present to effectively change the future for the better.
Human-machine interfaces (HMIs) and historians differ but need to be tightly integrated to provide company operations with optimal value. Big data has little value without analysis and access in real time.
Feed forward augmentation is a prediction technique that estimates the output from a proportional-integral-derivative (PID) control algorithm without waiting for the PID algorithm to respond.
Integration guidelines for human-machine interface and historian software should help organizations determine the best combination of data historian and HMI software components to turn big data into a big return on investment.
Build a case to get an automation and controls project approved. Here's how to gain approval for automation project capital expenditures. Such investments can reduce inventory, obsolescence, and expense.
The list was developed using CFE Media's web analytics for stories viewed on controleng.com, May 11-17, for articles published within the last two months.
- Chris Vavra, production editor, CFE Media, firstname.lastname@example.org.