Vertex module overview
Vertex is split in different components to be able to be move with the business requirements. These components can have a dependency but are split in runtime so we can have a Vertex application that is horizontally scalable and functionally modular to suite the requirements of that specific Vertex deployment.
Business
These are the components that are closes to the business processes. These modules host the entities that the user will interact with the most and will master the data that will support the business directly.
Vertex CRM
The CRM module is a module that can support with complex contract offering and has a link both the Pricing module as well as the Document Generation module. This enables it to generate standardized documents for effortless communication of offers, contracts and other customer interactions. It can directly request a price from the Pricing engine and use this information in the document send to the customer. With the sites and installations it is also possible to administer complex customers that have multiple sites, metering points and installations/assets. This administration can be used to link these elements to different ancillary services or passive imbalance services. With the
Main processes
- Administer customers with its (primary) contact(s)
- Create contracts and generate offers for both simple and more complex contract with the option to use multiple contract types/phases over time (PPA’s with a different contract for each stage of the construction of a windpark)
- Manage customer / offers for multiple brands
- Administer Sites and Installations for a given customer and apply steering configuration for this assets if applicable
- Create batches and series of batches for (repeating) sales campaigns and have the option to source the volume in advance using Estimated Sales Volumes
Mastered data
- Brands
- Contacts
- Contracts (with versions)
- Contract types
- Control flex assets
- Customers
- Estimated Sales Volumes
- Installations
- Model Contract Template
- Model Pricing Request
- Pricing Request Generator
- Sales Batches
- Sales Batch Series
- Sites
Vertex Portfolio Management
Main processes
- Create portfolios and books
- Administer the commodity types
- Administer the cost products (the actual products sold from PM perspective: for example Commodity or Shaping)
- Administer Supply Agreements which is the volume part of a customer contract. It contains the contractual / expected / actual volume that is delivered to/by a contract and its metering points
- Administer deals / orders that can flow between the supply agreements and a book and between the books (sales book / hedge book / trade book etc) themselves
Mastered data
- Books
- Commodity Types
- Cost products
- Deals (with versions)
- Orders (with versions)
- Portfolios
- Supply agreement (with volumes)
Vertex Pricing
Main processes
- Manage configurable Proposition Templates that administer the pricing calculation rules and the basis for the supply agreement / sales deals that need to be created when a pricing is scored
- Register Pricing Requests
- Create Pricings from the pricing requests and track the pricing results in individual pricing run
- Score a pricing and create a pricing agreement that locks the pricing agreement of a customer contract
- Create and link to the Supply Agreement from the Pricing Agreement and create the initial sales deals from the supply agreement and create the initial sales deals that reflect the deal that has been done with the customer when scoring
- Calculates the performance for individual pricing elements by calculating the pricing costs and comparing them with the pricing results that where offered to the customer
Mastered data
- Contract volume
- Pricing
- Pricing agreement
- Pricing costs
- Pricing results
- Pricing runs
- Pricing value provider values
- Product component (with versions)
- Product elements
- Proposition template
- Sales products (with versions)
- Sourcing agreements
Energy Data Platform
The VERTEX Energy Data Platform is an integrated set of technologies that collectively meets an organization’s end-to-end data needs. It enables the acquisition, storage, preparation, delivery, and governance of data, as well as a security layer for users and applications. Its purpose is to meet new challenges of the Energy Market. It has built-in integrations with energy parties and it is designed to work natively with VERTEX’ core modules.
Nifi & Nifi Controller
Vertex Model Executor
Executes parameterized Jupyter notebooks, manages environment variables and gets secrets from Key Vault. Automatically scales up and down using Horizontal Pod Autoscaling.
Apache Flink
Apache Flink is a framework and distributed processing engine for stateful computations over unbounded and bounded (= batch) data streams. Flink jobs is the preferred solution when fast (distributed) computations are needed on data streams: it features very flexible window definitions. It is a perfect solution for analyzing pattern relationships between streamed events (e.g., for interpolation, extrapolation, classification). When done in real-time, it can provide advanced insights further into the data processing system.
Apache Airflow DAGs
Processing tasks as part of a scheduled workflow orchestrated by Apache Airflow.
Apache Airflow is used for programmatically authoring, scheduling and monitoring workflows (data processing orchestration). Examples of such workflows are quality and completeness checks, after which calculations take place and are brought to an end system. Snapshotting of data, bringing data from A to B based on a schedule.
JupyterHub
Multi-user environment managed by Energy Essentials for script development (notebooks) with relevant packages pre-installed, auto-access to relevant data, secured. The scripts are version controlled (Git) and workflows for deploying Notebooks / models into the VERTEX Energy Data Platform are enforced.
Grafana
Airflow
Seldon Core
Business Process Monitoring
Position management dashboards
Portfolio management reporting API
Supporting services
Kafka
Redis
MinIO
Temporal
In cluster databases
InfluxDB
Druid
Data
The data modules are focussed on providing a very specific data storage. These modules can be used by other modules as a specialized data store. Through the REST API of the data store it can also be used by other applications as a specialized data store.
Vertex TimeSeries
Main processes
- Contains the data model for the TimeSeries metadata and provides the data model for a mssql based datastore
- Has the implementation for 3th party time series data sources through a plugin system
- Provides an time series client to the rest of the modules
Vertex Mastered data
- Time series metadata
- Time series data
Vertex Document Store
Main processes
- Host a structured document store for functional documents that can be:
- Searched: the document store contains a screen where a user can search on various properties of the document like filename, sender, receiver, message id, correlation id
- Identify uploaded documents using the identification method of the strongly typed documents loaded into the document store
- Extract metadata from imported documents to enable processes that need this structured metadata and to help the user handle and find documents
- Add behavior to specific types of documents using document actions: these action can run when a specific type of document is loaded into the system and can trigger other processes to handle/process the content of the document
- Store large payloads for other modules: this is a specialized data store that is optimized for storing large data objects. This feature can be leveraged by other modules that need to store large data objects.
Mastered data
- Documents
- Document groups
Infrastructure
Document generation
Main processes
- Hosts the webservice that facilitates the Word addon for managing templates by a user
- Can generate templates through commands and/or through a service call
- Generates documents server-side in docx or pdf format (without Word installation)
Mastered data
- Document templates