If you are involved in project management you may already know that some of the largest owner/operators in the world leverage our Pims software to streamline communication and information exchange between themselves and their contractors, partners, and third party verification organizations. This includes technical information, deliverables and drawings, tag information, request for information, change management, deviation requests, non-conformances and much more.
They reduce project planning, execution and operating costs through centralizing access access to data, less duplication of efforts and datasets across company boundaries and achieve a higher level of project integration and cooperation.
In the early stages of discussions with companies my colleagues and I often have to help them overcome change resistance and the temptation to stick with status quo. Status quo in this case often means having critical business processes continue to rely on e-mails or other rudimentary tools built on Sharepoint and similar.
A key factor to consider is the information security risk. Sticking with manual e-mails and similar tools for critical business process is fraught with risk.
I also come across the argument that “we will just rely on our EPC(M) provider’s system”. Yes, that is great, if they use Omega’s Pims – then you can also use PIE – Pims Information Exchange add-on for easy transfer of data between you and them.
However, how closely have you looked into their systems and their operations of such? Are you confident that your EPC(M) provider have equally rigorous information security processes in place as you? Do they have the same risk vs. cost tolerance level? What happens if their system is compromised – where does that leave you?
Vik Bulletin 