Xmon is TRG Screen's reference data monitoring and cost optimisation platform. It acts as a "smart meter" for your market data, providing real-time visibility into every data request across your organisation. By monitoring consumption patterns between your applications and data vendors, Xmon delivers transparency, identifies cost-saving opportunities, and ensures compliance—all while maintaining data quality and availability.

Key Features

• Real-Time Monitoring: Track all reference data requests as they happen, with complete visibility of fields, securities, and costs. 

• Cost Transparency: See the true cost of every data request with detailed breakdowns by category, asset class, and requesting system.

• Cost Optimisation: Identify savings opportunities through multi-hit analysis, field-level cost assessment, and commercial model optimisation.

• Invoice Reconciliation: Prevent billing errors by independently verifying vendor charges against actual usage.

• Comprehensive Reporting: Access standard and custom reports for usage patterns, cost allocation, and optimisation opportunities.

• Rules Engine: Create and enforce policies to control data usage, preventing costly mistakes and ensuring compliance.

• Xmon Insights Service: Receive expert analysis and recommendations from our team of reference data specialists.

Xmon is a secure, high-performance cloud-based solution that requires no client-side installation. It operates by positioning itself strategically alongside or between your internal systems and market data providers to monitor all data requests and can apply intelligent controls in real-time. There are three ways of connecting with Xmon; Autopilot, Active and Passive. Each mode is described below.

Key Components:

To access the Xmon web console:
‎1. Navigate to xmon.xpansionfts.com in your browser,
‎2. Enter your username and password and click "Login"

Xmon web console is supported by the main browsers, such as Chrome and Internet Explorer.

Note: All user accounts are managed by TRG Screen. If you have not received login credentials, please contact our support team at xmonsupport@xpansionfts.com.

The first time you login to Xmon with the login/password provided by Xmon Support team, you will be asked to change your password automatically.

You can change your password anytime by:
‎1. Clicking on your name in the top-right menu bar,
‎2. Selecting "Change password".

For SSO Users:
‎If your organisation uses Single Sign-On (SSO), password management is handled through your corporate identity system. The "Change password" option will not be available in your Xmon profile when SSO is enabled. Contact your IT administrator to change your SSO credentials.

Note: Pricing Matrices will be configured by the Xmon team as part of your onboarding process. Contact Xmon Support if your rate card has changed.

Pricing matrices are created by the Xmon Support team and reflect current vendor rate cards.

Xmon's pricing functionality allows you to view and understand the cost calculations used for your reference data requests. The system supports two main pricing models that reflect how vendors like Bloomberg structure their charges, Pay As You Go and Band pricing.

To view pricing details, navigate to SETTINGS > PRICING from the main menu. This section displays the pricing matrix associated with each contract.

Click the pencil icon next to any pricing model to view detailed pricing information.

Pay As You Go

This model charges based on individual requests and includes:

• First Request Cost: Corresponds to Bloomberg's "Unique fee" - the initial charge when requesting a security/category combination for the first time in a month.

• Multi-Hit Cost: Corresponds to Bloomberg's "Access fee" - lower charges for repeat requests of the same security/category within the same month.

The pricing matrix will display with:

• Categories listed horizontally (e.g., Security Master, Pricing, History)

• Asset types listed vertically (e.g., Equities, Fixed Income, Derivatives)

• Cost values at the intersection of each category and asset type

Band Pricing

This model groups securities into volume-based pricing tiers, where costs are determined by the total number of unique securities requested over a rolling 4-month period.

Select a Data Category from the drop-down list, at which point the pricing matrix will display with:

• Asset types listed vertically (e.g., Equities, Fixed Income, Derivatives)

• The Security count range per bracket

• The monthly and annual cost.

Note: Data Contracts will be configured as part of your Xmon onboarding process by the Xmon team. To add additional Data Contracts, follow the steps below or contact Xmon Support.

A Data Contract in Xmon represents the commercial agreement you have with a data provider (such as Bloomberg or Refinitiv). This configuration is essential because it defines how Xmon calculates costs, applies pricing models, and manages your vendor relationship within the system.

Every Data Source must be linked to a Data Contract to ensure accurate cost calculations and proper system functionality.

To set up a new Data Contract:

• Navigate to Settings > Data Contracts from the main menu

• Click the Add New button

• Complete the required fields as described below

• Click the Save button to save your configuration

Field Descriptions:

Note: Data Sources will be configured as part of your Xmon onboarding process by the Xmon team. To add additional Data Sources, follow the steps below or contact Xmon Support.

Each ‘Data Source’ in Xmon represents a data provider account e.g. Data Licence account.

To set up a new Data Source:

1.Navigate to Settings > Sources from the main menu,

2.Click the Add New button,

3.Complete the required fields as described below,

4.Click the Save button to save your configuration.

Field Descriptions:

Each source type (SFTP, WebAPI, HAPI) requires different credentials mirroring the credentials for the vendor.

SFTP/SFTP+Key:

• Username: Your data provider account username (e.g. dl01234)

• Password: Your data provider account password (case sensitive)

• Private Key: SFTP+Key only – Your data provider Private Key. Upload by clicking on the ‘Choose File’ button and selecting the file from your local drive - password not required.

• Server Address: Your data provider's server address e.g. sftp.bloomberg.com:22

WebAPI:

• Password: Your data provider account password (case sensitive)

• Vendor Remote Certificate: Your data provider Remote Certificate. Upload by clicking on the ‘Choose File’ button and selecting the file from your local drive.

• Server Address: Your data provider's server address e.g. https://dlws.bloomberg.com/dlps:443

HAPI:

• Username: Your data provider Client ID

• Password: Your data provider Client Secret Key

• Server Address: Your data provider's server address e.g. hapi.bloomberg.com or api.bloomberg.com

To edit or delete an existing Data Source, click the pencil or bin icons respectively.

A Data Connector in Xmon represents each internal system or application that requests reference data from vendors. Since systems can have multiple ways of connecting to data providers (different APIs, protocols, or connection methods), each connection channel requires its own connector configuration.

To set up a new Data Connector:

1. Navigate to Settings > Data Connectors from the main menu,

2. Click the Add New button,

3. Complete the required fields as described below,

4. Click the Save button to save your configuration.

Field Descriptions:

▪Username: Create a unique username for this connector's Xmon login. This is what your system will use to authenticate with Xmon. It should be descriptive and follow the naming convention e.g. "orgname_DLnumber_system_environment"

▪Password: Set a secure password for the connector. Your system will use this password to connect to Xmon.

• HAPI:

•Authorisation Key and Secret Key: The ‘Create Rest API Connector’ box below is automatically selected. When the Data Connector is saved, the credentials are created.

•Edit the Data Connector and select ‘Rest Api Connector Details’ to view the newly created credentials.

To Edit or Delete an existing Connector, simply click respectively on the pencil or bin icons.

When a new Connector has been added, it will be highlighted in Orange and a message “Awaiting Activation” will be displayed in the Orange Banner until it has been activated by Xmon support team.

Note: If you use Data Access Permissions to restrict user access to certain data connectors, you will have to add the new connector to the appropriate permission groups. This ensures users can see data from this connector in reports etc. See section 2.18.1 Data Access for additional information.

Mail Groups in Xmon are collections of users who should receive notifications when specific alerts or rules are triggered. Instead of manually entering individual email addresses each time you create a rule, you can create reusable mail groups that organize recipients by role, department, or responsibility.

Mail Groups streamline notification management and ensure the right people are alerted when important events occur in your reference data environment.

You can access Mail Group configuration through either:

• Admin: Click Xmon in the top-left ribbon, select Admin and navigate to Alert Contacts > Definitions

• User Profile: Click on your username in the top-right corner and navigate to Alert Contacts > Definitions

Xmon tracks reference data requests and can validate them against a defined set of cost and/or volume-based rules. Xmon’s powerful rules engine applies controls at the user level, organisation level and levels in-between, and allows proactive data access management to be implemented. Using Active mode, data analytics are computed in real-time and evaluated against access and quota rules to determine whether or not a request should authorised. Each market data request can be validated against one or multiple rules before being sent to the data provider.

There is a range of multiple conditions you can set within a rule. Each rule needs to contain one condition on either Data Contract, Data Source, Data System or Data Connector. Below is a list and description of the conditions:

• Cost: Helps you set cost limit per request/day/month to avoid large cost spikes.

• Volume: Helps you set security count limits per request/day/month.

• Request Type: You can filter requests sent in Ad-hoc pricing with quick data return, as opposed to Scheduled pricing. You can select between Adhoc, One-shot (Scheduled), Daily, Weekly and Monthly.

• Data System: Enables you to filter or apply the rules on one or more system names.

• Data Source: Enables you to filter or apply the rules on one or more data sources.

• Data Connector: Enables you to filter or apply the rules on one or more data connectors.

• Data Contract: Enables you to filter or apply the rules on one or more data contracts.

• Specific days and times: Select the time and date range to monitor specific requests with conditions Days Applied, Start Time Applied and End Time Applied.

• Data Type: Filter on particular data category.

• Field List: Enables you to filter requests on one or more specific fields.

• Security ID: Create a rule based on Security ID.

• Instrument Type: Enables you to filter or apply the rules on one or more instrument types.

• New Category: Enables you to be alerted on a category not requested in the previous month.

• Response ID: Enables you to filter requests for a specific response ID.

• Source Contributor: Is used to alert you of requests using a specified pricing source/contributor.

• Tag Filter: Enables you to filter on requests with a particular Tag value.

You can configure one of the following Actions: Block (only for Active monitoring of requests), Warn or Require Manual Approve.

NB When using Rule Frequency = ‘Per day’ or ‘Per month’, a quota will be computed and displayed on the Dashboard to see the aggregated value of the selected indicator for the current period.

2.8.1Creation

2.8.2Order and Priority

2.8.3Filter Rules

As Xmon is a fully hosted solution the creation, modification and deletion of users is administered by Xpansion team. Please contact us at xmonsupport@xpansionfts.com for any queries.

Your current user access rights can be viewed by clicking on ‘username’ (top-right of ribbon), then navigate to the ‘Permissions > User Assignment’ section:

Click on the ‘pencil / edit’ button to view user access for each user.

There are three different type of users:

When the ‘Real-Time exchange subscription’ module is activated, you will access the list of Real-Time users to configure in the menu ‘Settings’ > ‘END USERS’. Each user will correspond to an individual in the company that has an account to receive Real-Time prices and has a list of Exchanges he subscribes.

To define a new END USER, go to the menu ‘Settings’ > ‘END USERS’ click on ‘Add New’ button, input the below information and hit ‘Submit’ when finished.

To Edit or Delete an existing END USER, simply click on the icons or, respectively.

When the ‘Real-Time exchange subscription’ module is activated, you will access the list of the Real-Time and Delayed price exchanges defined in your data contract universe in the menu ‘Settings’ > ‘MARKETS’. During the implementation of Xmon the initial list of Price Exchanges will be uploaded. Afterwards, the Administrator of the system will have the possibility to view, edit and insert new exchanges.

To define a new EXCHANGE, go to the menu ‘Settings’ > ‘EXCHANGES’ click on ‘Add New’ button, input the below information and hit ‘Submit’ when finished.

To Edit or Delete an existing EXCHANGE, simply click on the icons or, respectively.

The FX table is used to convert the cost of Exchanges subscription quoted in a foreign currency into USD for consolidation purposes.

The FX table is automatically populated with EOD prices from the ECB website: https://www.ecb.europa.eu/stats/exchange/eurofxref/html/index.en.html

They can be found in the menu ‘SETTINGS’ > ‘FX’ as shown in the screenshot below:

Fixed cost can be associated with a Data Contract so Xmon can have a full picture of the data cost. For instance, fixed cost can be used to model annual data download subscriptions which will not be counted individual requests (like ‘Back Office files’ for Data License contract or ‘Real-Time Terminal’ cost by user for RT Contracts).

The configuration of the Fixed cost is done in the menu ‘SETTINGS ‘> ‘FIXED COSTS’. Click on the ‘Add New’ button and define the fields as described below:

Note: The amount of the fixed cost is defined at the ‘Data Contract’ level when selecting this fixed cost to apply to a particular contract.

To Edit or Delete an existing Connector, simply click on the icons or, respectively.

The factor matrix will be applied to the standard pricing matrix in order to adjust the cost to the real effective cost after Optimisation is done within the Bloomberg billing process. This way, the factor is mapped to the vendor Optimisation factor on the itemised invoice.

The factor is input as a 100% of application. Hence 75 means that a factor of 75% will be applied to the unit cost coming from the standard pricing matrix/rate card, which needs to be applied manually.

Step 1: To define a new matrix for a Data Source, you first need to tick ‘Apply Discount Factor Matrices’ in the definition of the given Data Source.

Step 2: Once the Data Source has been defined with ‘Apply Discount Factor Matrices’ ticked, go to the menu ‘SETTINGS’> ‘FACTOR MATRICES’, select a data source and the applicable pricing matrix/rate card.

Warning: Once defined, the factor matrix needs to be activated in the definition window of the Data Source by marking the field ‘Apply Discount Factor Matrices’.

Xmon allows you to define tags at the request level to identify and classify your requests easily to support your downstream reporting. Xmon permits you to set up to 5 different tags. The tags assigned to the request can then be seen in the table REQUESTS in the DASHBOARD menu or extracted in the STD03 Standard Reports in .csv format.

1.To create Tags, go to the SETTINGS > TAGS menu, edit ‘Tag1’ and input a short name into Label field and click on ‘Submit’:

2.In each request file, typically in the HEADER, add a line starting with the logic:

#tag [Tag1.Label]=Value of Your Tag

Example:

#tag Jobname=QA_Pricing

For WebAPI Calls, the .xml format should follow the sample below:

<xmon xmlns="https://xmongw.xpansionfts.com">

<jobname>QA_Pricing</jobname>

</xmon>

3.Process the request file as usual. To view the tag assigned to that request in the Xmon Dashboard, select the ‘Column chooser’ button on the Top-Right of your REQUESTS table in the Dashboard menu and select the Tag name:

Through annual bulk data file subscriptions, Bloomberg allows institutions to better manage costs associated with large-scale data usage. The subscription covers defined field sets, asset types, or regions for a one-time annual fee, eliminating any monthly per-security charges.

The Bulk Data Definition section in Xmon allows you to:

• define annual bulk data subscriptions (like Bloomberg Back Office files) with their associated costs, security types, and field coverage,

• enable Xmon to run cost simulations comparing your current ad-hoc requests against bulk file alternatives,

• help determine whether existing bulk subscriptions are cost-effective or if new bulk subscriptions would reduce overall Bloomberg spend.

To define the Bulk Data files in Xmon:

• Go to the menu SETTINGS > BULK DATA.

Create a new Bulk Data Definition:

• To create a new subscription, click the ‘Add new’ button.

• Populate the fields Name, Annual Cost and Description, and select Security Types present in your bulk data subscription.

• If you already subscribe to this Bulk data subscription, tick the ‘Subscribed’ box.

• Use the Fields Selection Builder to select fields from the list of templates oryou’re your own list using the ‘User Input’ section.

• When done click on Save in the top right corner.

Permissions specify what tasks users can perform and what features users can access. To access the Profile Data Access, go to the menu ADMIN (click your name in the top-right corner) > PERMISSIONS > DATA ACCESS. You can enable user permissions in permission sets and custom profiles.

2.17.1Profile Data Access

2.17.2User Assignment

The real-time Dashboard in Xmon enables you to view the pre-defined rules and their current quota level, the Month-To-Date consumption as well as the most recent requests.

The Dashboard has an Auto Refresh mode (every 30 seconds) which you can activate by clicking on the ‘Autorefresh’ button on the top right of the screen. The default setting for a new session is ‘OFF’.

3.1.1Quotas, Rules and Modifiers

3.1.2‘Month-To-Date’ Widgets

3.1.3‘Monthly Subscriptions’ widget

3.1.4‘Requests’ Dashboard

Once a request is raised it is automatically picked up by Xmon and validated versus any rule(s) that might apply. The request will display one of the statuses below, as applicable:

Active Mode Processing Statuses:

• Sending (Auto): Request has passed all rule validations and is being automatically forwarded to the vendor for processing

• Sending (Manual): Request was manually approved after being flagged and is now being sent to the vendor

• Waiting Source: Request file has been uploaded to the vendors servers and Xmon is awaiting the response file

• Received: The vendor has successfully processed the request and returned the response data to your system

Control & Approval Statuses:

• Blocked: Request has been stopped due to rule violations and will not be sent to the vendor

• Pending Manual: Request requires manual approval due to cost thresholds, compliance rules, or other configured conditions

• Manually Rejected: User has reviewed and rejected a pending request, preventing it from being sent to the vendor

Error & Timeout Statuses:

• Time Out (Manual): Request was pending manual approval but exceeded the configured timeout period and was automatically cancelled

• Time Out (Source): The vendor did not respond within the expected timeframe and the connection timed out

• Error: Technical error occurred during request processing due to formatting issues, system problems, or other technical reasons

Special Processing Statuses:

• Processed: Request has been analysed and costed by Xmon but not sent to the vend (used in passive monitoring or autopilot mode)

• Adjustment: Manual cost adjustment entry created for invoice reconciliation purposes

• Adjustment Cancelled: Previously created bill adjustment has been deleted and removed from reporting.

3.3.1Daily Cost Reporting

3.3.2Daily Volume Reporting

3.3.3Review the Response Time of a Data Provider

Cost & Usage Explorer is Xmon’s Business Intelligence reporting tool that transforms raw usage data into actionable insights. This reporting tool enables you to:

1.Build customised reports tailored to specific analysis needs.

2.Share insights with stakeholders across your organisation.

3.Facilitate data-driven discussions about cost optimisation.

4.Support strategic decision-making with comprehensive analytics.

Navigate to REPORTS > COST & USAGE EXPLORER

The information used to populate the various dashboards comes from two sources:

Verification Report Based Analysis:

1.Invoice Timeseries - Cost trends and patterns over time

2.Invoice Analysis - Historical cost profiles from Detailed Itemised Invoice data

3.Invoice Breakdown By Filename

Request-Based Analysis:

1.Monthly Running Cost - Cost allocation across systems using Pay As You Go pricing

2.Heatmap Scheduled Pricing - Band pricing model simulation

Invoice Timeseries and Invoice Analysis provide a detailed cost profile over the last 12 months, based on the Detailed itemised invoice.

Monthly Running Cost is based on request data using Pay As You Go pricing model and offers a cost allocation per system:
‎

Complementing the Monthly Running Cost is the Heatmap Scheduled Pricing, simulating the and pricing model:

A new dashboard can easily be created by clicking on the

How to create a New Tile:

In order to create a new graph tap . You will then see a different range of reports. In order to create an Xmon Cost Profile you need to select the User Report Cost Analysis.

Main Xmon Data Model to use

Then you can easily set a title and click on dimensions and measures to select them from your report. Also, users can visualise the report by choosing from a variety of different tables, graphs and colours. Applying a FILTER for specific dates will produce more customized results.

Xmon's comprehensive reporting suite provides on-demand access to detailed analytics and operational insights. Navigate to Reports > Standard Reports to generate and download any report instantly.

3.5.1Request Level Analysis Reports:

3.5.2Simulation & Cost Optimisation Reports:

3.5.3Technical Reports:

3.5.4RT Entitlements Reports:

3.5.5Itemised Invoice (Verification Files) Reports:

A report of cost summary by the end user can be viewed in the menu ‘REPORTS’ > ‘SUBSCRIPTIONS’.

It will display the list of all End Users defined and assigned to a Real-Time type of data contract. Along with the attributes of the end user the report will display its fixed cost contribution and its specific exchange subscriptions cost.

Fixed Cost:

Fixed cost per end user is calculated as the sum of all fixed costs of type ‘per user’, plus the sum of all fixed costs of type ‘per contract’ divided by the total number of end users assigned to the same Real-Time data contract.

Subscription cost:

A detailed list of exchange costs can be displayed on the right-hand side of the list by clicking on the ‘Detail’ icon as shown below. The ‘As Of’ field allows you to view the audit of its previous consumption of exchange subscriptions.

This is possible to compare Subscriptions between multiple users and identify in 1 click their differences of subscriptions. Simply hold ‘Ctrl’ and select multiple users, then hit ‘Compare’ and use ‘Details’ button to show the list of exchanges in common or differences.

The report accessed through the menu ‘REPORTS’ > ‘EXCHANGES’ displays the sum of subscription costs across all End Users in the list of exchange by exchange.

If two end users are subscribing to ‘Vienna Stock exchange’, which has an individual subscription cost of USD 66.00, the line for this exchange will display USD 132.

Once the monthly Detailed itemised invoice has been uploaded in the menu ‘DATA OPS’> ‘IMPORT DATA’ > ‘DETAILED ITEMISED INVOICE’ and it has been processed overnight, a report will show the reconciliation of request files processed in Xmon versus the file processed by the data vendor for the selected month.

To view the report, go to the menu: REPORTS > REQUEST FILES RECONCILIATION, select the applicable month and click the ‘Run’ button

This report allows you to validate that all of your systems are connected to Xmon and is monitoring your whole environment. It will also show the requests which have passed through Xmon but have not been processed by the data vendor.

Invoice reconciliation provides the user the opportunity to compare and analyse Bloomberg's invoice with Xmon’s estimates by highlighting any differences for the selected month. In order to use this function, you need to make sure that you’ve uploaded the invoice (Please refer to How to upload the Bloomberg Invoice). Once invoice .csv file has been uploaded the Invoice Reconciliation report can be easily found under the menu REPORTS > INVOICE RECONCILIATION.

The Details tab will help you analyse the costs and spot any differences.

You'll find the Cost Optimisation feature in REPORTS > COST OPTIMISATION. This smart analysis tool looks at your market data usage and spending to give you automated recommendations based on your requests integrated in Xmon. It scans your consumption patterns and creates a clear summary of practical insights, showing you exactly how much you could save with each one. The current month's analysis shows your total potential savings up front, with everything organised by impact - so you can easily spot and tackle the biggest opportunities first.

Click the DATA USAGE SUMMARY link to access deeper analytics at both field and request levels – see the next section for more details.

This Data Usage summary page is designed to view a summary of potential areas of savings that can be pointed out by Xmon Reporting. Each scenario is represented as a tab so the user can focus onto the area of savings that is most pertinent to him.

3.7.1Request Analysis

3.7.2Repeat Costs

3.7.3Multi Hit Analysis

3.7.4Cost Per Field

3.7.5Linked Categories

3.7.6Not Downloadable

3.7.7Pricing Model Optimization

Xmon is now able to define vendor bulk data files and run cost simulation based on all requests monitored in Xmon for a given month. This will help answer the question whether bulk data purchase is more cost effective compared to data purchased using ad-hoc models. If you do have a bulk file subscription, Xmon will indicate whether it makes sense to keep it. Setting up this two-step simulation in Xmon is very simple.

First, create a definition of the bulk file, which includes the annual cost and data available in that file:

Second, run the analysis for a selected month. The results will be displayed in a summary table:

The SEARCH menu can be found in the ‘DATA OPS ‘> ‘SEARCH’

The search engine enables users to retrieve any requests monitored by Xmon in the path and also enable them to enrich the Tags or to exclude requests from Pricing after seeing in the DETAILED ITEMISED INVOICE if some of the request files haven't been processed by Bloomberg. Hence it gives the opportunity to carefully look through requests, fields and securities.

4.1.1Bloomberg Fields

4.1.2Securities

4.1.3Requests

The security level reconciliation helps the user see the details of each security based on the contract, date and the status. It can be found under the ‘DATA OPS’ > ‘SECURITY LEVEL RECONCILIATION’.

Security Level Reconciliation is compromised by two sub-categories. By SecurityID & Data Category and the Not Found in Detailed Itemised Invoice.

4.2.1By SecurityID & Data Category

4.2.2Not Found in Detailed Itemised Invoice

4.3.1How to define Bill Adjustment

4.3.2How to upload the Bloomberg Invoice

4.3.3How to upload Detailed Itemised Invoice

4.3.4How to upload Excel Add-In

4.3.5How to Simulate a Request

4.3.6How to upload Real-Time BB Entitlements Files for Application

4.3.7How to Upload Custom Fields

4.3.8How to configure Auto-tagging of requests

This Recommendation history table shows a summary of the recommendations that have been identified by both the end user of Xmon and the Xpansion team when analysing the data download cost profile.

This provides the opportunity to set identified and realized savings in order to reduce future costs. It involves the creation and maintenance of a plan, such as the recommendation, purpose, status and comment. They are all explained by the actions that need to be taken from the client in order to achieve the pre-defined goals for cost reductions. Recommendation History can be found in ‘DATA OPS’ > ‘RECOMMENDATION HISTORY’

• Raised on: The date whereas the recommendation has been raised

• Implementation Date: The date whereas the recommendation will take action

• Monthly Savings: The monthly cost of the recommendation (Regular savings)

• One-Off Savings: This is one-off saving and doesn’t have any multiplication

• Identified Saving: The monthly cost multiplied by the number of months between the current date and the “Raised on” date + One-off cost

• Realized Saving: The monthly cost multiplied by the number of months between the current date and the “Implementation date” + One-off cost if a task has been implemented.

• Purpose: Cost reduction, Cost avoidance, Compliance and Reference Data Entitlement

• Status: Not Action, In progress and Complete

In order to add a new Recommendation simply tap on the and the below window editor will be shown: