A couple of weeks back, when I wrote about LSEG’s DataScope Plus [DSP] platform, I received some questions around its ‘sister product’, DataScope Select [DSS].
DSP has been used by our clients to move off legacy feed products DS Equities and DS Fixed Income, but DSS actually has been around for longer.
For those of our clients who are relying on LSEG (f/k/a Refinitiv) data, DSS is the data product of choice, particularly for ad-hoc requests and small- to mid-size instrument portfolios. The most common setup used by our customers for planned data updates:
- Implementation of DSS’ standard templates for Reference Data and Pricing across asset classes, such as ‘Terms & Conditions’, ‘Symbol Cross-Reference’, ‘Bond Schedules’ and ‘EOD Pricing’ respectively;
- Configuration of customized deliveries, combining fields from standard templates into client-specific datasets. Typically, these are cleanly grouped by the various asset classes in scope, to reflect that many attributes pertain to certain asset types only;
- Certain content from the Entity Details and Hierarchy, when company data beyond basic issuer information is to be managed;
- Specifying delivery schedules, with enough lead time prior to internal SLAs. Often, these also are phased by asset classes or the different content needs of the involved consumers to get the latest data just-in-time.
We also frequently see a combination of DSP and DSS. This is purposeful, where the traded (or otherwise relevant) universe of certain asset classes warrants bulk delivery (DSP), while for other asset classes and regions a portfolio approaches are cost-effective (DSP).
DSP is pretty much always accompanied with DSS to facilitate user requests, with proper entitlement and usage control imposed by the Data Management platform, for bespoke reference data and intraday prices, as and when needed.