System/Network Congestion Sample Clauses

System/Network Congestion. Trading on NSE/BSE is in electronic mode, based on satellite/leased line based communications, combination of technologies and computer systems to place and route orders. Thus, there exists a possibility of communication failure or system problems or slow or delayed response from system or trading halt, or any such other problem/glitch whereby not being able to establish access to the trading system/network, which may be beyond the control of and may result in delay in processing or not processing buy or sell orders either in part or in full. You are cautioned to note that although these problems may be temporary in nature, but when you have outstanding open positions or unexecuted orders, these represent a risk because of your obligations to settle all executed transactions.
System/Network Congestion. Trading on NSE /MCX-SX is in electronic mode, based on satellite/leased line based communications, combination of technologies and computer systems to place and route orders. Thus, there exists a possibility of communication failure or system problems or slow or delayed response from system or trading halt, or any such other problem/glitch whereby not being able to establish access to the trading system/network, which may be beyond control and may result in delay in processing or not processing buy or sell orders either in part or in full. You are cautioned to note that although these problems may be temporary in nature, but when you have outstanding open positions or unexecuted orders, these represent a risk because of your obligations to settle all executed transactions.

Related to System/Network Congestion

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Bandwidth the amount of data (quantified as “Mbps” or “Gbps”) made available to Customer as specified in a Service Order.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.