Questions on ERT_FD3_LF1 (Pricing Streaming – 3s Conflated)

mohamed.noohaboo

Hello Devs,

I have a few questions on the Pricing Streaming Service (ERT_FD3_LF1) and would appreciate any clarity from the community or dev advocates:

1. Watchlist Size Allowance - Scope of Application: When a contracted watchlist size (e.g. 15,000 RICs) is assigned to a Pricing Streaming account, at what level does this limit apply? Specifically:

• Is it enforced per mount?
• Per Machine ID?
• Per application environment (PROD, TEST, DEV)?
• Or is it shared across the entire account?

I believe this is per machine ID but would be great if you could double-confirm this.

2. Relationship Between the Platform Watch-List Ceiling and the Contracted Allowance: The ERT_FD3_LF1 service specification indicates a watch-list size of 50,000 unique RICs per connection. How does this relate to a contracted watchlist allowance that is lower than this ceiling?

Is the correct interpretation that:

• The 50,000 RIC limit is the technical/platform maximum per connection, and
• The contracted allowance (e.g. 15,000 RICs) is a separate commercial entitlement enforced on top of that?

3. Machine ID Provisioning - Obtaining and Activating Additional IDs: For a Pricing Streaming setup with an entitlement of 4 Machine IDs (5 mounts per ID) across 3 environments (PROD, TEST, DEV), what is the process for provisioning and activating Machine IDs that have not yet been set up? Specifically:

• What steps are required to request and activate additional Machine IDs within an existing entitlement?
• Is any additional configuration, approval, or entitlement change needed from LSEG, or is it a straightforward provisioning request?

Thanks for looking into this!

Jirapongse

@mohamed.noohaboo

Thank you for reaching out to us.

1. The watchlist limit should be associated with the account. For example, this could mean that the total number of active subscriptions for the account must not exceed 15,000 RICs. However, please contact the product team directly to confirm how this limit is applied.
   
2. The server that supports ERT_FD3_LF1 subscriptions also supports Real-Time Optimized users (ELEKTRON_DD). Therefore, the server configuration may need to accommodate the maximum watchlist limit supported for RTO users.
   
   If the account's contracted watchlist size is 15,000 RICs, but the server supports up to 50,000 RICs per connection, the server-side setting should not override the contracted watchlist limit. There should be a component in the backend real-time infrastructure that enforces the contracted watchlist size.
   
3. I am not sure whether the same account can be used across all three environments (PROD, TEST, and DEV). Account configuration is beyond the scope of this forum, so please contact the product team directly for clarification.