ASN-GW FAILOVER Sample Clauses

ASN-GW FAILOVER. Verify the following when an ASN-GW fails (for instance loss of power): [***]
AutoNDA by SimpleDocs

Related to ASN-GW FAILOVER

  • Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.

  • HORIZONR Gateway HORIZONR Gateway provides customers with the ability to (i) generate reports using information maintained on the Multicurrency HORIZONR Accounting System which may be viewed or printed at the customer’s location; (ii) extract and download data from the Multicurrency HORIZONR Accounting System; and (iii) access previous day and historical data. The following information which may be accessed for these purposes: 1) holdings; 2) holdings pricing; 3) transactions, 4) open trades; 5) income; 6) general ledger and 7) cash.

  • Payment Failure Any Credit Party (i) fails to pay any principal when due under this Agreement or (ii) fails to pay, within three Business Days of when due, any other amount due under this Agreement or any other Credit Document, including payments of interest, fees, reimbursements, and indemnifications;

  • Virus Management Transfer Agent shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within the Transfer Agent environment.

  • Epidemic Failure In the event that CONTRACTUAL PRODUCTS under warranty have the same or similar functional defect during a time period of three (3) months and the number of defected CONTRACTUAL PRODUCTS exceed [***] of the quantity delivered within this time period, this [***] = CERTAIN INFORMATION ON THIS PAGE HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. shall be an “Epidemic Failure” as mentioned in the following. The term “Epidemic Failure” shall exclusively apply to delivered CONTRACTUAL PRODUCTS with a number of pieces of more than ten thousand (>10.000) during three (3) months. If either CONTRACTUAL PARTY learns of the existence or likely existence of an Epidemic Failure, then such CONTRACTUAL PARTY will inform the other CONTRACTUAL PARTY as soon as possible. The CONTRACTUAL PARTIES shall then work together to jointly devise a containment action plan. As soon thereafter as reasonably possible, the CONTRACTUAL PARTIES will develop a corrective action plan to remedy the Epidemic Failure. Phoenix Contact shall use its best efforts to implement such remedy as quickly as possible at Phoenix Contact’s own expense, which efforts shall include receiving all shipments of affected Product back (freight collect), repairing or replacing all such affected Products in accordance with the agreed remedy devised by the Parties, shipping the repaired or replaced Products back to ENPHASE at Phoenix Contact’s expense, and implementing the agreed remedy in all newly manufactured Products. Phoenix Contact shall be responsible for the reasonable following costs and expenses actually incurred and substantiated as a result of all aspects of implementing the agreed remedy on the affected Products: reasonable costs of the retrieval, packing, shipping and transportation of such Products, and the re-deployment of repaired or replacement Products (including all labor, consulting, contractor and the like charges, incurred by ENPHASE, only if Phoenix Contact has agreed in writing that ENPHASE is allowed to do the aforementioned activities). For the avoidance of doubt all damages defined in Article 11.4 shall be direct damages and shall be subject to Article 14.2.

  • Year 2000 Compatibility Borrower shall take all action necessary to assure that Borrower's computer based systems are able to operate and effectively process data including dates on and after January 1, 2000. At the request of Bank, Borrower shall provide Bank assurance acceptable to Bank of Borrower's Year 2000 compatibility.

  • WHEXXXX xs xxxx of a plan of reorganization, RESTART PARTNERS, L.P., a Delaware Limited Partnership ("Restart"), may acquire an ownership interest in Elsinore Corporation ("Elsinore") or the Four Queens, Inc. ("FQI");

  • Payment in the Event Losses Fail to Reach Expected Level On the date that is 45 days following the last day (such day, the “True-Up Measurement Date”) of the Final Shared Loss Month, or upon the final disposition of all Shared Loss Assets under this Single Family Shared-Loss Agreement at any time after the termination of the Commercial Shared-Loss Agreement, the Assuming Institution shall pay to the Receiver fifty percent (50%) of the excess, if any, of (i) twenty percent (20%) of the Intrinsic Loss Estimate less (ii) the sum of (A) twenty-five percent (25%) of the asset premium (discount) plus (B) twenty-five percent (25%) of the Cumulative Shared-Loss Payments plus (C) the Cumulative Servicing Amount. The Assuming Institution shall deliver to the Receiver not later than 30 days following the True-Up Measurement Date, a schedule, signed by an officer of the Assuming Institution, setting forth in reasonable detail the calculation of the Cumulative Shared-Loss Payments and the Cumulative Servicing Amount.

  • Warranty Period The warranties set forth in Clauses 12.1.1 and 12.1.2 shall be limited to those defects that become apparent within **** after Delivery of the affected Aircraft (the “Warranty Period”).

  • Acceptance Testing The MCP must have the capability to report all elements in the Minimum Data Set as set forth in the ODJFS Encounter Data Specifications and must submit a test file in the ODJFS-specified medium in the required formats prior to contracting or prior to an information systems replacement or update. Acceptance testing of encounter data is required as specified in Section 29(a)(v) of this Appendix.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!