Contention. 4.2.1 Before implementing a contention-based system for the display and reporting of London Stock Exchange Data, Customers must contact the London Stock Exchange for written approval of their proposed system. Please note that prior approval of a contention system does not constitute acceptance of the reported number of Devices or Unique User Ids. 4.2.2 A contention system may be employed as an element of Operational Controls to allow a defined number of Devices or Unique User Ids to access London Stock Exchange Data concurrently. To conform to the requirements for contention, the Data must: a) be continuously updated – snapshot services are not permitted; b) have an auditable limit to the number of concurrent accesses; c) require all Devices or Unique User Ids to contend for access to the Data (no Devices or Unique User Ids with dedicated access to be included). 4.2.3 Any contention system that operates to include different categories of access, such as Member Professional users, Non-Member Professional users and Private Investors, must operate separate contention pools (with respective contention pool limits) for each category. 4.2.4 Please note that contended access is not permitted on Xxxxxxx Xxxxxxxx Xxxxx 0 Xxxx Xxxxxxx. 4.2.5 Contention may not be employed on a service or system based on rapid snapshots of data that give the impression of continuously updating. 4.2.6 Once the contention limit is reached, no further accesses may be permitted until a Device or Unique User Id has logged off. 4.2.7 A Device or Unique User Id cannot be logged off automatically by the Redistributor at any point, with the exception of after the close of the trading day. Once a Device or Unique User Id has logged off, the screen must be cleared of Data and prevented from receiving further updates until the Device or Unique User Id logs on again. 4.2.8 A subscriber to a service can actively choose to assign their rights to the Redistributor to be logged off after a reasonable amount of time. One example of this is a ‘pop-up’ box that would appear after a reasonable period of inactivity asking whether the subscriber would like to be logged-off. We would also accept the subscriber agreeing to a disclaimer before accessing the service, informing them of this condition of service. 4.2.9 Billing is based on the maximum concurrent Device or Unique User Id limit. Under exceptional circumstances, where user numbers are particularly high, the contention limits may be exceeded. In this instance the higher level must be reported on the terminal declaration for the whole month. 4.2.10 All records of customer usage and limit levels must be retained for audit purposes.
Appears in 11 contracts
Samples: Real Time Market Data Agreement, Real Time Market Data Agreement, Real Time Market Data Agreement