/
Release Notes for IFS Workflow 1.3

Release Notes for IFS Workflow 1.3

Search the IFS Workflow Wiki
 

 

Release Type

Minor

Release Date

January 31, 2019

Summary of Changes

The purpose of this document is to provide you with the latest information for the release of IFS Energy & Resources Workflow 1.3.

IFS Workflow is a complete, market-leading workflow engine that leverages ProcessMaker software to provide oil and gas workflows for IFS and other applications used in the industry.

This IFS Workflow release includes the following two workflows:

  • IFS Enterprise Upstream Marketing Election Change

  • IFS Merrick Gathering System Unlock

This release also includes IFS Workflow Engine 1.1:

  • ProcessMaker version 3.2 and all its fixes and enhancements

Going forward, the workflow engine will only need to be updated when ProcessMaker has a new release that is incorporated into IFS Workflow. Workflows will be released more often when they are created.

Although IFS Workflow is a standalone release from other IFS products, some REST Services that are delivered with other IFS products may be required. Additionally, AppLink, which is the routing and security tool for IFS’s REST Services, may also be required. Workflows that require a connection to data sources will always utilize REST Services for these connections. 



Compatibility Matrix

Product Certification

Component

OS Name

OS Version

OS Architecture

Support Status

Certification

Tested

Component

OS Name

OS Version

OS Architecture

Support Status

Certification

Tested

Application Server

CentOS

7.2

x86_64

Supported

Certified

Y



Interoperability Certification

Target Product

Target Version

Contract

Certification Status

Notes

Target Product

Target Version

Contract

Certification Status

Notes

IFS BOLO

13.9.0.0

API 2.8

Planned Certified

Mail Call Log Patch

IFS Excalibur

9.0.20.0

API 2.8

Planned Certified

Mail Call Log Patch

Target Product

Rest Service

Certification Status

Target Product

Rest Service

Certification Status

IFS BOLO 13.8.17.0

API 2.9


IFS Excalibur 9.0.27.0

API 2.9

Ownership Tracking

Certified

 

Minimum System Requirements

This section identifies the recommended hardware requirements for each machine.

Component

Recommended

Component

Recommended

CPU

8 Processor 2.4 GHz or Higher

RAM

32GB RAM minimum

Disk 1

500GB (OS, Application, Logging)

Disk 2

500GB (OS, Application, Logging)

 

Medium sizing for 295 User Peak:

Component

Recommended

Component

Recommended

CPU

12 Processor 2.4 GHz or Higher

RAM

48 GB RAM minimum

Disk 1

500GB (OS, Application, Logging)

Disk 2

2TB (Database Storage)

 

Large sizing for 400 User Peak:

Component

Recommended

Component

Recommended

CPU

16 Processor 2.4 GHz or Higher

RAM

64 GB RAM minimum

Disk 1

500GB (OS, Application, Logging)

Disk 2

3TB (Database Storage)

Server Machine:

Component

Recommended

Component

Recommended

OS

CentOS 7.2

PHP

7.3

Web Server

Apache 2.4

Database

MySQL 5.7

 

Client Machine:

Component

Recommended

Component

Recommended

OS

Windows 7 (32 or 64-bit); Windows 10

Browser

Google Chrome (Recommended), Mozilla Firefox, Microsoft Edge, Microsoft Internet Explorer 11



Release Contents

Enhancements

Module

Feature Name

Summary

Module

Feature Name

Summary

Workflow

IFS Enterprise Upstream Marketing Election Change 

The IFS Enterprise Upstream Marketing Election Change is initiated when the Marketing Group receives an Ownership Change Request from a Working Interest Owner to change their Marketing Election from TIK (Take in Kind) to JOA (Joint Operating Agreement) or vice versa.

This workflow is currently configured for a Marketing Election change from JOA to TIK, or an Owner’s Marketing Election from TIK to JOA. In addition, this process supports Entitlement DOIs that do not have TIK (Take in Kind) Owners in balancing.

The workflow has been automated to support the following features:

  • Expiration of Entitlement and Revenue DOIs in IFS Enterprise Upstream

  • Creation of new Entitlement and Revenue DOIs in IFS Enterprise Upstream

Workflow

IFS Merrick Gathering System Unlock

The IFS Merrick Gathering System has been designed to bring efficiency around the process of unlocking a gathering system to help notify and track effort associated with this event. The process begins in the IFS Merrick system when a user unlocks a gathering system (the gathering system must have the Used By Revenue flag selected). Then, using the IFS Merrick Notification Scheduler, information about the unlocked system is sent to the Revenue Accountants Group to begin preparing for the process of PPA's and other associated tasks.


Additional Reference Material

You may find the following documents useful:

These documents are available on the P2 Store and on this wiki.


Copyright© 2024 IFS AB. Copying prohibited. All rights reserved.