PEP meaning in oil and gas

Project Engagement Process

This is a process that defines how projects should engage with GOI (Global Operations and Infrastructure). The workflow for PEP is driven through the Unity portal ( which is the portal where ALL projects should be registered for initial engagement with Digital Security and GOI. The primary aim of PEP for GOI is to ensure: * operational impact assessment in a variety of areas - eg. infrastrcuture capacity in the data centre (space, power, cooling), storage capacity, backup capacity, database capacity, network impact, impact on other GOI services, GOI resource impact, clash with other project activities, etc. * GOI opex impact is budgeted for - ie. for the next calendar year. * infrastructure design assessment - check on GOI standards (hardware, and software), and also if engaged early enough GOI can discuss optimal design options. * opportunities for infrastructure re-use, and synergies with other projects and infrastructure are realised, etc. * efficient operational handover is carried out during execute and there is a formal "handshake" that GOI have accepted the infrastructure into formal oeprational support. ALL projects should engage through Unity, though not all projects need to follow PEP - eg. software releases, and some equipment refresh or upgrade activities do not need to follow PEP, and undergo TIP review etc. Failure to register in Unity and gain appropriate GOI review approvals may mean that the projects experience delay due to failure to get changes approved, have resources available, etc.