System Risk Sample Clauses

System Risk. High volume trading will frequently occur at the market opening and before market close. Such high volumes may also occur at any point in the day. These may cause delays in order execution or confirmation.
AutoNDA by SimpleDocs
System Risk. 7.1. The System and Information is provided "as is".
System Risk. □ By using this Service to conduct this transaction and other transactions are transactions of electronic trading system. In case of an order is input incorrectly, the intended order may not be established, or an unintended order may be finalized. □ □ Due to various causes the electronic trading system may not be available temporarily or for a certain period of time such as the Company’s or the customer’s communication/system equipment failure, network disturbance, natural disasters such a earthquake, cyberattacks etc. Also, customer orders may be invalidated due to delay or non-arrival of customer order instruction to our system. Moreover, the Company assumes the right to cancel the customer’s trade execution in case of an electronic trading system failure. □ □ In case of rapid market fluctuations, the price information may be delayed, and there may be a disparity in electronic trading system price and the actual market price. □ □ There might be an abnormal cryptocurrency purchase and trade sale price that might be calculated by the Company’s system. Please note that in case of the Company deems an order to have been established by an abnormal value, the Company may cancel the transaction at its own discretion. □ □ If there is a failure in the system due to external changes etc., the customer may not be able to make an order through the internet (the Company’s website, smartphone website, application), or the customer’s order may be delayed, invalidated etc. that may lead to a risk of a trade failure. □ □ About opportunity loss due to System emergency maintenance, system failure etc., if we cannot identify the customer’s content of the order that was attempted to be placed, the Company shall not assume any responsibility for the opportunity loss. □ . Possibility of Loss occurring due to external causes . □ Loss may occur to the customer due to disasters, public communication failures, delays in record processing in cryptocurrency transfer recording mechanisms (mining approvals etc.), and other circumstances that might be beyond the Company’s control. In such cases, for loss that might incur to the customer due to external causes not relating to the Company, the Company shall not assumes any responsibility. □ . Leakage and Compensation of Deposit Asset Risk . □ By unauthorized internal/external intrusion or cyber attacks etc., when there is a leakage of the customer’s deposit assets, the Company shall compensate for the loss incurred to the customer. Howev...

Related to System Risk

  • 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.

  • 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.

  • System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.

  • System Upgrade Facilities Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • SPRINKLER SYSTEM If there now is or shall be installed in the Building a "sprinkler system", and such system or any of its appliances shall be damaged or injured or not in proper working order by reason of any act or omission of Tenant, Tenant's agents, servants, employees, licensees or visitors, Tenant shall forthwith restore the same to good working condition at its own expense; and if the New York Board of Fire Underwriters or the New York Fire Insurance Rating Organization or any bureau, department or official of the state or city government, shall require or recommend that any changes, modifications, alterations or additional sprinkler heads or other equipment be made or supplied by reason of Tenant's business, or the location of the partitions, trade fixtures, or other contents of the Premises, Tenant shall, at Tenant's expense, promptly make and supply such changes, modifications, alterations, additional sprinkler heads or other equipment.

  • System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Equipment Procurement If responsibility for construction of the Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades is to be borne by the Connecting Transmission Owner, then the Connecting Transmission Owner shall commence design of the Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades and procure necessary equipment as soon as practicable after all of the following conditions are satisfied, unless the Developer and Connecting Transmission Owner otherwise agree in writing:

Time is Money Join Law Insider Premium to draft better contracts faster.