|
Market Data Vendor Connectivity
Multi-Vendor Real-Time Market Data Connectivity
Multi-vendor real-time data retrieving and data contributing functions are a standard feature in every Anima-enabled Excel or in any internet browser accessing Anima's live spreadsheet models. Anima's generic real-time data retrieving function, A5Rt, is a high-performance non-volatile Excel function that will trigger value updates only on either actual market data changes or manual spreadsheet recalculation.
Similarly, A5Contribute, Anima's multi-vendor data contributing function provides for the real-time or clocked (maximum frequency) contribution of data either privately for a single user, internally within your team, or externally to market sources. Figure 1 illustrates the use of the real-time functions in Excel.
Structured Market Data Elements
In contrast to A5Rt() which simply operates on the names of standard source, record, and field names, Anima also includes a set of real-time data retrieving functions based on higher level constructs collectively known as Anima's Structured Market Data Elements. A further description of these elements follows.
Real-Time Publishing Contexts
Often yield curves, volatility smiles and other complex enterprise-proprietary analytics should be made available in real time to a large number of mission-critical spreadsheets and client applications. Because of their heavy usage of valuable computation and networking resources, and the importance of consistent numbers for every user, ideally they should be implemented as single execution instances, with their results published on the enterprise's real-time data distribution bus.
Through Anima, any analytic function can be interactively made to execute within a server's "private" environment (a context) that can take real-time data inputs directly from their multi-vendor sources, plus other input parameters settable via Excel functions. At any time, only a single instance of a context will be running. The context computation results are continuously published as a real-time stream into multiple data distribution platforms like Triarch or Tibco/Rv for the consumption of client spreadsheets and applications.
Context Input
Context Input can be any one of the following:
Figure 2 shows an example where some context input arguments are being set from an Excel spreadsheet. Context Output
Depending on the context configuration, the output of the context is converted to the publishing platform's native format. So for example, when publishing on Reuters Triarch the output is sent as a RIC, and on Tibco Rv as an Rv record. If so configured, a context can read a pre-defined layout with platform-neutral field identifiers to be used when formatting the context's output record. Platform-neutral field identifiers are converted to native platform field numbers or names via pre-defined field dictionaries.
|
April 22, 2011 | Zurich Swiss Private Bank purchases iMonIT and will implement internal market data feed with the Anima Enterprise SDK.. refer to
February 15, 2011 | Zurich Sayula's iMonIT detects with in 20 seconds data quality issues of London Stock Exchange's Millennium platform implementation. read on...
May 6, 2010 | Zurich Sayula's iMonIT catches the Fat Finger Flash. refer to
January 21, 2010 | Zurich Sayula's Anima supports IDC's CSP PlusFeed. refer to
August 15, 2009 | Zurich Sayula's Anima supports Morningstar's real-time low latency broadcast feed. refer to
March 1, 2009 | Zurich Leading Swiss Private Bank decides for iMonIT for risk compliance reasons.. refer to
September 30, 2008 | Zurich Sayula Group adds new branch in Switzerland: Sayula Engineering AG. details...
July 10, 2007 | Zurich Global tier-1 Swiss bank purchases Sysula's iMonIT, a vendor latency monitor, to support its client web market data services. refer to
November 20, 2006 | London Wilmott and Sayula announce partnership and joint project to develop real-time collaborative spreadsheet analytical models for the Web. read on...
July 24, 2006 | Brussels Sayula and ITG Consulting announce partnership agreement. read on... |

