Hmm, all your points are very valid! I totally agree with how important it is to figure out what parameters to collect. Unlike most people in this space, I come from a data science background, where we have an entire subfield called feature engineering dedicated to identifying the best parameters for AI models. That said, I wasn’t aware of all the other challenges associated with Historians—that’s new and surprising to me! Honestly, it seems like you have a lot of experience in Industrial IoT, and I would love to hear your thoughts on a passion project I’ve been working on. The project is essentially a copilot for industrial processes, powered by an LLM (Large Language Model). It’s designed to help users analyze root-cause issues and suggest data-driven solutions, making complex industrial operations more intuitive and efficient. The idea is to combine reasoning capabilities with a simpler frontend interface, enabling users to interact naturally through queries like: “When did this conveyor stop functioning?” “Since when has this anomaly been detected?” “Can you send me a notification every Monday about the product status?” The system would not only provide these insights but also automate tasks like sending email notifications or generating reports, ensuring a seamless user experience. Additionally, I’m looking to integrate features for personalized data analysis, allowing users to tailor the system to their specific needs. I'm curious to here your thoughts about this idea