Abaco EVDM is a modular Solution aimed to address the need of Financial Institutions to manage Market Data (Real Time / Infra Day / End Of Day), Reference Data and CorAx following an intelligent and optimized approach
The solution is compliant to Data Vendor policies, but is able to reduce at minimum the Market Data Yearly cost for each client
There are different modules developed in order to address different client needs: Analysis of Data Usage by Users and Applications, Compliance Analysis of invoices received from Providers, Intelligent Capture, Caching and Distribution of Data, Entitlement and Compliance Reporting
The modules can be combined together in order to accommodate what each client would like to obtain from the solution
The Analysers
To allow customers to keep under control the use of Market Data, Abaco provides many analysers each developed in order to capture all facets of the service which is parameterized
All Analysers have the ability to provide the customer a clear picture of what are the applications that consume Market Data or which are the Users that have been provided Terminals and how much and to what % of the service fee (or the total) they are absorbing in such a way to suggest the most proper mode of allocation of the related costs
For the service the provider are used to bill in advance a budget usage plus an invoice for the over consumption at the end of the period, our Analysers have also the ability to alert clients when data usage is exceeding predefined thresholds.
The Connectors
The connectors to the Data Feed both for Real Time than
EoD / InfraDay flows are based on SuperConnector (Abaco
proprietary technology)
Their basic functionality ensures efficient and customized
management of the process of acquiring information from
the Provider. The Connectors can be engaged by
Processes or End Users via structured files sent to them or
detected in shared directory or via GUI
Each connector has a Graphic User Interface through
which is easy and intuitive the creation of new requests to
Providers and the related output file in the desired mode by
setting each output field both in terms of content (the
original or a modified value of the Provider applying
calculations, IF , ...) that in relation to the format or to the
desired position within the records
All Connectors incorporate intelligent analysis tools
required to deal with, for example tools able to prevent the
transfer to the required target Provider of double or multiple
refer to the instruments for the same fields
The Data Switch
The Data Switch combines the functionality of two
connectors and allow to direct to another provider
native calls made to interact with a different one,
returning to the application that had made the request
an output consistent to the standard one it was
expecting to receive from the switched provider
Redirection can be total or partial affecting the entire
data set or just part of it, depending on the customers
needs
To better manage these activities mapping tables of
the main identifiers of financial instruments (ISIN , Ric,
BBG Ticker, Valoren, CUSIP, Sedol, ... ), of the
counterparties identification codes (LEI, BBG Unique
Identifier , ... ) as well as of the fields list available
within the different the Data Provider flows are cabled
and kept up to date within the Data Switch
The Intelligent Data Mixer
The EVDM solution can rely on an Intelligent Data Mixer
that is able to manage the requests coming from each
application and split it in two or more requests, dispatch
them to the assigned Providers, compact the various
output files received and send back to the application a
unique output file written in the language the application
expects to receive.
Usually this module is bought from clients when there is
the need to achieve optimization ($$) splitting the requests
versus the cheaper providers (according to client’s
contracts) for each type of data without requesting any
change to the way each application requests the data they
need.
Another area of application is the one connected to the
need of a duplication (or multiplication) of the source of
acquisition of the data in order to perform a quality check
on the same: in this case is the EVDM Data Mixer that is
meant to send the requests to the various Vendor data that
have been configured starting from a simple list of ISIN or
other identification codes of the financial instruments
The Entitlement
The Entitlement aims to enable EVDM customers or other
proprietary or branded EDM solutions (i.e.: GoldenSource,
Markit EDM, SmartCo, Access Control, ... ) to manage the use
of the data made available in a manner consistent with the
Policy of the data Providers, of the Data Owners (Third Party
like ICAP, Tullet, BGC, ... , Exchanges, Index Producers, ... )
and the contracts entered by clients with them
The parameters available in the module allow clients taking
into account information concerning the Entity from which the
Data request comes from (i.e.: Main, Branch, Sudsidiary, …),
the area where it is positioned the application requesting the
data (i.e.: Front, Middle, Back), the type of data required for
each single call, the next use that will be made of the data, ... ,
and enable them to automatically block escaping the single
request when not consistent with the profiles declared during
the configuration
All the data consumption of the different applications
connected to the EDM platform within a time period defined by
the client is tracked and that information is made available in
standard or customized reports for internal or external audit
The Data Caching
The EVDM Data Cahing is a module built to optimize
request versus a single provider avoiding duplicating
totally or partially equal data request related to
Intraday, End Of Day or Reference data.
The Module can be programmed in the way it can:
learn autonomously the type of fields that it
needs to request and store for each provider in
order to enlarge the list of fields requested and to
avoid multiple hits
manage different intervals of "freshness" for each
type of data available in the IntraDay Cache
depending on the different application requesting
the same data and also for the type of End of
Day Data (especially when related to Reference
Data).