Logo

Composite Enrichment

BYOD for Proprietary Indices via Bloomberg

Data Adapter clients can use the BYOD service as a way of providing FundApps with the constituent mappings for Proprietary indices looked up via Bloomberg.

As we don't get constituent data directly from Bloomberg you'll need to implement this using the below steps:

Step 1

Supply Data Adapter with details of your derivative holding on the prop. index, along with a reference to the Index ticker:

PortfolioId AssetId AssetName AssetClass ComponentDataProviderID
GMF prop_future Future on GS Custom Indices GS (a Proprietary Index) Future GSCBCHID Index

Step 2

Supply the Bring Your Own Data service (see: Bring your own data (BYOD) guide for details) with mappings to the referenced proprietary index

CompositeId CompositeIdType ComponentId ComponentIdType Weighting WeightingQuantity
GSCBCHID Index DataProviderId FA0000000001 Isin 0.2 1000
GSCBCHID Index DataProviderId FundApps Equity DataProviderId 0.3
GSCBCHID Index DataProviderId 000000001 Cusip 50000

Step 3

Once sent through, the Data Adapter service will generate the Future on an Index, while the BYOD service will then map any of the components you hold outright to the Index

💡 Note that the service does not call your data provider for additional Instruments

Example

Given the example mappings above, a Data Adapter file which contains:

PortfolioId AssetId AssetName AssetClass ComponentDataProviderID ISIN Quantity
GMF prop_future Future on GS Custom Indices GS (a Proprietary Index) Future GSCBCHID Index 100
GMF test_equity Dummy Equity FA0000000001 100

Would result in two holdings in the resultant FundApps file:

  1. Equity holding in test_equity - 100 of the ISIN: FA0000000001
  2. Future on a proprietary Index (GSCBHID Index)
    1. Of which the Index has a single component of 20% FA0000000001
    2. The other components listed are dropped as the underlying constituent data is not held outright

You will also need to provide FundApps with a Bloomberg Enterprise ID (EID) that has that this third-party data set in it's permissions. For most users with Bloomberg Anywhere access, this will be the UserId they use in Terminals. If users do not have Bloomberg Anywhere, some additional identifiers may also be needed. Note, this EID is at the user level rather than the DL level.

If you do not have a suitable user with these permissions, you will need to first resolve this with Bloomberg and the relevant third-party product provider.