pipe line connection in oil refinery

Model Catalogue

This is a File Auditing, Management and Model Version Control Tool

The Model Catalogue is designed to allow the engineer to have a structured archiving system to store and retrieve IPM and field model data files. The engineers can thus maintain a complete history of each version of a model as it is developed and maintained over the field life.

The Model Catalogue Explorer is your view into such system. It is a simple, intuitive interface, similar to Windows Explorer.

These are some typical questions that the Model Catalogue should help answer:

  • Which is the latest model for this field?
  • When was this model last updated?
  • What was changed in the model?
  • Who is responsible to update and monitor this field model?

The objective of the Model Catalogue is to:

  • Have available the "Official" or "Published" model - current model
  • Store and have available the most current updated production system, reservoir and process models
  • Enable any authorised party to have access to them
  • Facilitate updating and making copies of any of the model versions - History of model and field development
  • Have one source for all field data files (not just IPM models) on a server or local machine.
  • All versions of the models are preserved with a date and user stamp.

The Model Catalogue stores models in an organised fashion, within a hierarchical tree structured. It is designed to be the central repository of the "official" or "published" production models of a production team within a company so that only the latest, most up to date models of each production element are used for the analysis of the production system.

Production system "models" are created within the Model Catalogue from a Main Model File and any number of auxiliary or associated files. Each Model Catalogue "models" are logical entities. Once a field model has been added to the Model Catalogue it will keep copies of all its versions.

The Model Catalogue is ideal to use where the engineers have a number of well, reservoir, surface and/or process models - production system models to organize, maintain and keep up to date: Many client machines (modelling engineers) would be accessing a common central "model" data storage.

Model Management

Objectives:

– Provide the correct model at any time
– Manage and audit any model update that is carried out
– Vendor neutral
– Keeps the source of information upon which the models are built

Principal Functionality:
– Track changes made to the models/files with corresponding validity dates
– Provide Model/File Access functionality
- Add / Check In / Check Out / Copy
– Users privileges and security
– Processing of the Models/Files through providers (Open Architecture)
– Interfaces for externally driven actions
– Source of DOF Data Model

Key Facts:
• Management of models and related information taken care of by Model Catalogue.
• Workflows can have access to the required model(s) and related information in an organised fashion.
• Any update carried out by an engineer will immediately become available to the system.
• Any change carried out either by an engineer or by an automated workflow is tracked, and hence easily audited.
• Exists as a standalone application and is currently used as a corporate file management system in various companies.