Much like the OT world, the convergence of technology and process optimization has to start with people! Like the early days of process control, most controls engineers were Chemical Engineers that understood the process and became very proficient at control strategy configuration. IT organizations without business process SMEs create delays, opportunities for miscommunication, non eloquent process that can’t take full advantage of modern technologies and architectures.

As an Automation Engineer, I bridge the gap between business units and IT by fostering collaboration: 1. Joint Planning: Aligning on goals and challenges early ensures both teams are on the same page. 2. Cross-Functional Teams: Mixed teams promote shared responsibility and open communication. 3. Real-Time Tools: Platforms like Teams or Slack help share updates and resolve issues quickly. 4. Unified Vision: Shared roadmaps connect automation success to business goals. 5. Training: Educating both sides builds trust and reduces resistance. These steps ensure seamless integration of automation across teams.

As automation professional I feel a major roadblock in harnessing power of IT tools in OT sector has been different protocols at different communication layers in OT and inability of these protocols to be adaptive enough to achieve efficient data flow in between Hardwares located at both ends. For example a HART protocol will not allow data flow to a transmitter from say the internet. The necessary development of the protocols in compliance with cyber security has not happened. In this regard evolution and adaptation of FDI can be a game changer as this standard allows greater access of data generated by field devices to higher level control and host systems.

Transparency! That includes requirements and benefits. Dropping a "problem" on IT for your project is very different than engaging IT early so they understand the overall goal and benefit to the company. These days there aren't many Automation solutions that don't have an IT component for perpetual dataflow or periodic license application, so be ready to discuss minimum functional requirements vs. "nice to have". Build an inclusive team and share the win. The next project will integrate more smoothly.

Identity Best Practices among both the BUs, merge execution centres to add best value to the customer’s, KAM identification Are listed few can be looked at