Organizations today manage copious amounts of files and data that are generated during the lifecycle of Major Capital Projects (MCP). Documentation and data generated during MCPs include information regarding conceptual design, front end engineering, detail design, construction, As-building and decommissioning. Additionally, MCPs closely coordinate with partnering stakeholders, monitoring and documenting scope non-conformances, corrective actions, deviations, and MOCs.
As an MCP nears completion, another challenge arises that is the MCP data and file migration to operations. During this time, you will find yourself asking many questions of the ‘what, who, when, how and why’ variety, relating to the many activities and decisions that encompass migration to operations. Defining handover is crucial both in helping manage it and clearly establishing a robust method that is communicated to all key stakeholders during the migration process. Some key questions organizations may ask are:
Migration Data Wrangling Solution
Data wrangling services are ideally positioned to assist with the ‘What, Who, How, and When’ activities relating to MCP handovers. This includes the identification, deduplication, transformation and migration of files and data to target systems while adhering to system attribution and operational requirements.
Collaboration with IT partners that offer global best practices, and leverage domain expertise paired with innovative automated AI solutions to protect and retain the integrity of critical data and files, are key drivers to success during migration from projects to operations.
Identification of files and data
To enable migration of files and data, the MCP must identify the target audience. Managing security protocols, access restricted file exchanges and working environments is imperative during migrations. Restrictions will need to be managed to ensure external organizations or internal personnel do not have direct access to company IP information.
Analyses of organizational MCP and operations information numbering and coding procedures/specifications is fundamental to allow identification of files and data within the MCP environment for migration, and also how that data and information will align to operational requirements. This includes:
Migration of MCP data and files can be challenging, especially if there are hundreds of thousands of files. Files and data need to be accurate, searchable and classified in a manner that allows maximum findability within the target operational system. MCPs need to determine, document and communicate:
Migration content needs to be accurately identified, extracted, classified, attributed and exported into an acceptable format to allow for target system population, or to align with the agreed organizational recipient system/migration requirements.
Operations should be engaged throughout MCP construction, As-building, decommissioning and final handover activities to ensure that operational requirements and interests are maintained. A key time prior to MCP start-up is the process safety start-up review (PSSR). The PSSR team will receive critical files and data that ensures all new or modified facilities/systems are built and installed safely in accordance with MCP design requirements. The successful completion of the pre-safety start-up review should be the trigger to begin migrating MCP information to operations
Migration quality assurance
MCPs need to ensure that migrations are fully tracked and auditable, and should consider creating the following if not already in place:
Principal Consultant, Wipro Limited.
Janine Murray is an IM Consultant with over 15 years of experience in the O&G industry. She has extensive FE/Operations and Major Capital Project (MCP) Information Management experience. She has deep experience with IM brownfield modifications, greenfield enhancements, MCP joint ventures, closeout, and MCP handover to Operations. Additionally, she is experienced with document cleansing and data extraction techniques for digitizing O&G legacy assets.
She can be reached at email@example.com