Tagging Provision

Find out how easy it can be to add metadata tags to content

Project Description/Issue

The client is a joint-venture (JV), operating one of the largest, most complex fields in the Middle East. The joint-venture was taking over an asset from the long-term operator, and faced a number of contractual challenges in obtaining legacy content built-up over decades, as well as preparing to take over the operatorship of the field. The client therefore had limited access to the existing content, limited knowledge of the field itself, and a looming deadline to achieve readiness. In one example of the challenges facing the JV, when asked how many wells the field had, there were more answers than people asked.

Flare’s Approach

Flare provided a service to pilot the Catalog software. This involved collaboration with the client to understand the current information available, identify what questions users might ask, and building the knowledge base of assets.

During the discovery phase of the engagement, new terms were also added to the Flare Taxonomies, reflecting the complexity of the field. This is normal and is part of the service offered by Flare. All wells were added to the Reference data system, as were any known aliases or unusual terms.

Using a combination of manual review, and automated tagging, over 12M files were organised and tagged, making them visible within the Catalog and supported by Taxonomies. This included sophisticated approaches to tagging content with standard names, supported by aliases. Flare also attempted to reduce information overload by tagging at an appropriate level within folder hierarchies – as sometimes several thousand items on a network drive do not require tagging – rather one item would be sufficient, e.g. Reservoir Model.

As information was tagged and reviewed by the deployment team, more terms and aliases were added to well names to support future searches.

The solution used Flare Taxonomies, Cortex and the Catalog, to provide visibility over available information resources.

Benefits/Outcomes

All content was tagged at the appropriate level, using common and agreed naming standards.

Good information structure helped reduce information overload.

It was easy to find information, irrespective of the search terms used by the individual technical staff.

The pilot was successful and since taking over operatorship, the client is now considering the use of Flare’s Folio application to manage working and final content.