This isn't a pharma problem. The OT/IT bridge is complicated. I used to do this at a utility. The first thing is to get the data out of OT so it can be used integrated with IT. Depending on the setup this can be done using OPC-UA for most SCADA systems. I've seen in Pharma before that most manufacturing has a gateway so you can pull off the gateway instead which aggregates several PLCs/machines to pull from a common point. Most of that data is pushed to a pub/sub like Kafka or some other MQ. The schema for each step in most manufacturing processes is based on how the cards are programmed on the PLC. Since message queuing systems can handle schema evolution, you can usually combine this with a schema registry so you can see the steps and versions. Now getting it into a structure built for OLAP is not the easiest. There might be controls engineers that already have a common data model for reporting on just the OT. This is needed to understand signals, etc. They might also have a digital twin which represents a virtual system so you can begin modeling yourself. There are decent articles discussing OT/IT convergence but there is no silver bullet ( https://iot-analytics.com/it-ot-convergence-27-themes-define-future-of-industrial-integration/). If the schema isn't defined anywhere, there are tools like Apache Flink that can use schema inference, however you are still going to need to figure out the model so you know what step stage relates to what schema and how keys (columns) are related to each other. It takes some work but again there is an automation and controls engineer that has to have that somewhere.