It is the process of setting up and maintaining a new project into the production-forecasting module of upstream operations management. A project is like a folder with a collection of scenarios. The scenarios may contain a collection of networks, which are a collection of network objects. This entire process of creating a new project and defining the components inside – scenario, networks, network objects, and linking the network objects is termed as Manage Project

This process not only lets you create a new project and the components inside, but also lets you define projects, scenarios, networks or network objects using existing components. Existing components here mean scenarios, networks, network objects, links, and so on. You can also view, modify (edit) or delete a project or the components (as mentioned above) underneath.

The next logical step after Manage Project is Manage Access where the application assigns you roles to perform necessary actions in the project. The application thus needs to allow for creation of user groups, object groups, constraints right matrix, approval right matrix. The application creates special user groups for forecast coordinators to delegate and forecast stakeholders to view results.

It is the process of assigning and revoking access rights of users for master data like projects, constraints, and so on.

You can create user groups and object groups through this application. You then use these user groups and object groups to maintain access right matrices for projects and constraints. In addition, this process lets gives you the rights to approve a project and to view results. Nested user group and object group creation is also possible though this process.

Manage Access comes as the next logical step after Manage Project, where you are assigned roles to perform necessary actions in the project (which are created in Manage Access). The application thus needs to allow for creation of user groups with relevant permissions and assign them to object groups.

It is the process of capturing various constraints (Potential, Capacity, Risk, Opportunity and Events) for network objects in a scenario.

You can define a constraint as an optimal performance or restriction of an object

You can create constraints with an object in a production network or can bring it in from another scenario when you copy the scenario.

You can add constraints manually or upload them using the pre-defined template that contains all the details against each object. Multiple constraint values can exist against every measurement for different effective periods.

An object can have more than one constraints for the same constraint type.

You capture constraints for measurements at network objects. Measurements are for the combination of mediums and dimensions (for example, OIL_VOLUME, GAS_ENERGY).

You then use constraints to calculate the forecast results

It is the process of preprocessing scenarios and calculating the production forecast (future predication of hydrocarbon production) and submitting the forecast results for approval in the forecasting module.

Calculation will be possible after successful creation of projects with valid scenarios in it that further contain production networks with existing or future object. These objects will be associated with constraints (Potential/Capacity/Risk/Opportunity) and events (Planned Events). Once the constraints, events, and other transactional data added to objects and preprocessing is successful, then calculation engine needs to be run to calculate the forecast.

It is the process of viewing the production forecast results at a scenario or network or network object level.

It is the process of approving the forecast after your submission. The application also considers multi- level approvals and these levels of approval will be dependent on the configuration by the user. The approver can either approve or reject the forecast depending on the forecast results displayed at that level. Once you have done the final level of approval, the forecast is ready for publishing.

Publish Forecast is the process of publishing the forecast after all levels of approvals are done.

It is the process of allowing the user to create custom hierarchy as part of the solution.

You can create a custom hierarchy and its respective nodes for certain effective dates, and also edit or delete the hierarchy as per requirements. Once you save the hierarchies, you can map them to any object (for example, it will be mapped in the project setup screen). You can use the created hierarchies to view result reports aggregated as per the levels of the hierarchy.

It is the process of providing you with the capability of uploading data from a local machine or server onto the UOM application.

You might need to input large amounts of data, be it projects, scenarios, networks, network objects, constraints and events linked at objects, forecast results. To overcome the tedious activity of manually inputting data, this application lets you upload data. Here you can enter data (project, scenario, networks, objects or constraints and events, forecast results) into a pre-loaded format and upload it onto the application. The application then reads the information out of the template and puts it up into a system understandable language into the UOM module.

The templates will contain columns relevant to the information required for the respective data set and relevant to the user (depends on user permissions) for the user to fill in and upload.