Version 16.5 Features Comparison

This topic summarizes the feature differences between Dataflow Version 20, and Dataflow in Planning Space version 16.5.

PAGE CONTENTS

 

Feature Status

The Feature Status descriptions are used as follows:

  • Web Implementation: Version 20 has a new web-based implementation of a feature that is equivalent to the Version 16.5 feature.
  • Migrated to Version 20: The feature has been migrated to Version 20 using the Windows-based code platform and is mostly unchanged from Version 16.5. Because of the Windows-based platform, it must be accessed in the Planning Space Desktop application. In most cases, a new web-based implementation is in development for a future Version 20 release.
  • Future: The feature is not available yet in Version 20.4; it is planned for a future Version 20 release.
  • Removed: The Version 16.5 feature is not implemented in Version 20.

Data management

Versions

Versions can be deleted. The is a key feature in the Dataflow Version 20 data model; it supports the use case of having multiple versions that branch off from a 'master' ('Live') version which represents the state of the formal planning process. This means that analysis and evaluation tasks can be performed using separate versions, and when completed these can be deleted or merged into the master version. Also, year-on-year updating can be maintained by using multiple versions.

Currency decks are assigned at the version level, rather than at the document level. This simplifies the process of reconciliation of inflation and FX across documents in the same version.

A granular permissions model has been introduced that works with the version model so that data can be protected whilst allowing users permission to perform their own analyses.

'Copy to version' is based on path rather than Id. This removes restrictions that existed on moving documents between versions (previously the document had to be copied from the destination, including parent lineage).

Document Types

Document Types replace the Node Types and Document Templates in Version 16.5.

Scenarios

Scenario Tags have been removed. Scenarios are referenced by name only. The 'GetScenarioDataByTag' expression function has been removed ('GetScenarioData' must be used instead).

A master list of scenarios can be configured for use in dropdown selectors in the UI, and for document creation. Ad hoc scenarios can also be created per each document. Default scenarios can be specified as part of a document template, ensuring that all documents of a certain type are created with a desired set of scenarios.

Scenario cases have been removed, therefore it is no longer possible to 'share' data across scenarios, and each scenario of data is independent. Data must be copied between scenarios as necessary; new tools will be introduced in future Version 20 releases to make the copy process easier. The Bulk Utility and the data loaders (Data Tools workspace) can be used to insert the same data into multiple scenarios.

Properties ('General' variables)

The 'General' category variables have been re-structured as Properties.

A property is a special class of variable that belongs to a document, its value is not configurable in each scenario. A property can use the Scalar or Time Series data types. Properties behave like variables when they are edited in documents: all changes are stored in document revisions.

One important difference is for expressions. A property can be used as part of an expression for a variable, however you can’t reference a scenario variable to set a property, unless the scenario is explicitly defined using the 'GetScenarioData' expression.

An important use of properties is for setting up hierarchy filters in the Manage Data workspace. Filters are a powerful tool for document selection when applying data operations to documents.

Variables

Several variable types have been removed: Well, WellView, and LineItemGrid.

The Well and WellView types are no longer supported because the Legacy Reserves application (Reconciliation and Decline) is not implemented in Version 20. (For users migrating data from Version 16.5, expressions referencing Decline well data will be removed but the values will be retained; it is possible to preserve well data in Version 20 in Text variables.)

The 16.5 Line Item functionality has been replaced by a new implementation of Line Items in Version 20; these can be configured in document type templates for TimeSeriesDouble data. See Variable Data Types.

Expressions

All expressions are now fixed expressions that can only be configured in the document template.

Expressions are referenced by ID, so changing a variable prompt will automatically update all relevant expressions.

All expressions are calculated in monthly periodicity, because all TimeSeries data is saved in monthly periodicity in the database.

Permissions

The document permissions model remains the same, with both document type and document instance level permissions.

There is a critical difference for inherited permissions in the version hierarchy: due to the performance cost of scanning up a hierarchy tree to check permissions, the decision was made that a document’s permissions are assessed directly, ignoring any ancestral dependencies. (Users migrating data from Version 16.5 where access to documents has been controlled via an ancestral document, will need to propagate down permissions from the ancestral document to all of the descendants.)

Document locking Feature Status: Web Implementation

The 'Edit and Publish' mechanism replaces the document locking function in Version 16.5. The 16.5 locking mechanism implicitly locked a document as soon as one user had opened it. This meant that other users (or bulk update processes) could not modify the document, often causing frustration if multiple users were editing the same set of documents.

'Edit and Publish' brings significant improvements. All documents are opened in a read-only state and multiple users can view the same document simultaneously.

A document must be explicitly put into 'Edit' mode to make changes. Changes that are made to the document in Edit mode can be saved and stored only for the user making the changes; this means that the user can work on changes across several Dataflow sessions, can review and validate the changes, and only 'Publish' the document (i.e., insert the changes into the master copy of the document in the database) when ready to do so. While the user has the document in Edit mode, other users can continue to access and use the document (master copy), in its last-published state.

A document revision is created only when the user performs the Publish action. This eliminates what happens in Version 16.5 where it can be necessary to create 'intermediate' revisions that are actually work-in-progress and do not need to be permanently stored.

Workflows Feature Status: Web Implementation

The Dataflow Workflow functions are replaced by the Orchestrator and Dataflow Workflow Utility functions in Version 20.4.

The Orchestrator will support workflow operations for all Planning Space applications - but currently only implemented for Dataflow.

Reporting

Feature Status: Migrated to Version 20

Reporting has a 'front end' in the web-based Manage Data workspace for generating report outputs from documents (see Reporting).

The configuration and design of reports uses the 'Report Designer' tools migrated from Version 16.5, and accessed in the Dataflow Configuration workspace (see Reports).

A fully web-based reporting function, usable for all of the Planning Space applications, will be implemented in a future Version 20 release.

Data tools

Feature Status: Migrated to Version 20

All except one of the Version 16.5 data loaders have been migrated to Version 20, in the Data Tools workspace. See Data Tools workspace.

The exception is 'Load from PalantirCASH' which has been removed. This is because the CX Suite applications are not implemented in Planning Space Version 20.

The migrated data tools will be replaced by web-based tools in a future Version 20 release.

Planning Space Data Connector (PDC)

Feature Status: Migrated to Version 20

The Planning Space Data Connector add-on for Excel is available in version 20.4 Update 10 and later.

Hierarchy tools

Data Utility Feature Status: Web Implementation

The Documents and Bulk Utility web-based interfaces provide replacement functionality.

Data Aggregator and Data Propagator Feature Status: Web Implementation

Version 20 functions are in the Manage Data workspace.

Bulk Calculate Feature Status: Web Implementation

Version 20 function is in the Manage Data workspace.

Change Dates Feature Status: Web Implementation

Version 20 function is in the Bulk Utility.

Update Currency Settings Feature Status: Web Implementation

The Version 20 data model has currency deck assignment at the version level.

An Update Currency Settings function for bulk editing of variables in documents is included in Version 20.4. This has comparable functionality to the 16.5 Update Currency Settings tool.

Bulk Rename Feature Status: Future

To be implemented in the Bulk Utility in a future Version 20 release.

Bulk Change To Feature Status: Future

To be implemented in the Bulk Utility in a future Version 20 release.

Data Batching Feature Status: Web Implementation

New Orchestrator and Dataflow Workflow Utility functions in Version 20.4.

List Update Utility Feature Status: Future

This will be implemented as web-based functionality in a future release.

Complex Attachment Loader Feature Status: Future

This is not yet implemented in Version 20.

Update Reserves Change Reasons Feature Status: Removed

Not needed in Version 20 because the Legacy Reserves application is removed. Revision Tags provide equivalent functionality for integration between Dataflow and the new Planning Space Reserves application.

Scenario Designer Feature Status: Removed

Not required for scenarios in the Version 20 data model. Equivalent functionality is implemented in the Dataflow management tools.

Configuration

The Dataflow Configuration workspace mostly contains management tools that are migrated from Version 16.5. Improved and web-based functionality will be introduced in future Version 20 releases.

Migrated management tools:

  • Variables
  • Templates
  • Tags (note: Scenario Tags do not exist in Version 20)
  • Reports (Report Designer)
  • Lists
  • Currencies
  • Prices
  • Enersight Connnections
  • Audit Log
  • Unlock Templates
  • License Manager

New management tools:

  • Scenarios

Removed management tools:

  • Import List Data (implemented in the Lists management tool; see Lists manager)
  • Workflows (Orchestrator and Dataflow Workflow Utility functions are implemented in Version 20.4)
  • Dashboard Map (the Dataflow Dashboard function is not implemented in Version 20.4)
  • Unlock Documents (not required; replaced by the 'Edit and Publish' mechanism for Dataflow Documents)

Integration of Dataflow with other applications

Economics and Financials Feature Status: Migrated to Version 20

Dataflow linking to Economics and Financials, including 'Pivot and Aggregate' linking, is implemented in Version 20.4.

Economics and Financials data can be input to Dataflow using the Data Tools 'Load from Economics' and 'Load from Financials'.

Legacy Portfolio Feature Status: Removed

The Version 16.5 Portfolio application is removed from the standard configuration in Version 20. Replacement fuctionality is provided by the new Planning Space Portfolio.

Legacy Reserves Feature Status: Removed

The Version 16.5 Reserves application (Reconciliation and Decline workspaces) is not implemented in Version 20. Replacement fuctionality is provided by the new Planning Space Reserves.

Other Quorum Software applications

PlanningSpace Version 20.4 supports integration with other Quorum Software applications including Enersight and PetroVR.