eVISION Blog

The place to find frequent insights from eVision experts, regarding industry news, exciting technology, predictions, platform innovations, and more.

Over the past decade, eVision has been at the forefront of industry developments, supporting global clients in process industries achieve their operational and safety goals with powerful software. 

eVision prides itself on its in-house expertise: an essential requirement when providing solutions for challenges that can have potentially dangerous implications. Understanding every facet of hazardous industries operations lies at the core of everything we do.

We frequently capture some of the thoughts of our staff, which can be read below: the results of collaboration, understanding, and innovation.

Let us call you

  • This field is for validation purposes and should be left unchanged.

BLOG: Interoperability

eVision Chief Architect Damian Hickey talks about how to achieve maximum value from digital innovations, and the software vendors’ collective responsibility to cater for compatibility and interoperability.

Read more here.

 

BLOG: Vision Zero

eVision strongly supports the ambition to achieve “vision zero”: zero accidents and incidents in hazardous workplaces. Read eVision Co-founder Neil Currie’s thoughts on how to effectively walk the path towards vision zero with fit-for-purpose software innovations.

Read more here.

Insight: European Commission H2020 

Predictive risk mitigation has long been the holy grail of hazardous industries solutions development. The ability to mitigate the possibility of dangerous situations occurring is the clearest, yet most complicated step towards Vision Zero, and optimal safe production. eVision had already been tackling this challenge, but since being awarded the H2020-SME instrument phase 2 grant in 2014, this process has been put into high gear, leading to achievements that would have been impossible without H2020.

Read about some of these collaborative achievements here.

GET IN TOUCH

  • This field is for validation purposes and should be left unchanged.