Severity 1 Case Handling Sample Clauses

Severity 1 Case Handling. For all Level 1 severity issues (“Severity 1”), LeanDNA shall provide electronic updates to Customer regarding its progress toward resolution of Severity 1 issues at regular intervals, initially targeted to be no more than every 30 minutes (or as the parties may otherwise agree) until a resolution or work-around has been provided. Reproducible errors that cannot promptly be resolved will be escalated to LeanDNA engineering personnel for further investigation and analysis before being returned to the Customer for additional information. Updates will be provided via email or other means as agreed upon.
AutoNDA by SimpleDocs

Related to Severity 1 Case Handling

  • SCOPE OF SERVICES/CASE HANDLING A. Upon execution by Xxxxxx, Attorneys are retained to provide legal services for the purpose of seeking damages and other relief in the Litigation. Client agrees that Xxxxxx may choose to associate additional law firm(s) and/or lawyer(s) to represent Client in connection with the investigation and prosecution of the rights Client has as a purchaser of publically traded securities of Xxxxxx, and Client understands that such representation shall be on the same terms as those described in this agreement.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Downtime Due to the nature of server provision, downtime and lost transmissions may occur as part of routine maintenance. You are advised to maintain a copy of your account status and details of Content purchased.

  • COMPLAINTS HANDLING 44.1 Either Party shall notify the other Party of any Complaints made by Other Contracting Bodies, which are not resolved by operation of the Supplier's usual complaints handling procedure within five (5) Working Days of becoming aware of that Complaint and, if the Supplier is the Party providing the notice, such notice shall contain full details of the Supplier's plans to resolve such Complaint.

  • Network Congestion Reduced Speed for Routing or Answering 911 Dialing Calls. There may be a greater possibility of network congestion and/or reduced speed in the routing of a 911 Dialing call made utilizing the Service as compared to traditional 911 dialing over traditional public telephone networks.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Reactivation To reactivate suspended Service, you must bring your account current through the month of reactivation by making payment in full of any outstanding balance, fees and other applicable charges. In addition, we may require a deposit before reactivating your Service. The amount of the deposit will not exceed one year of monthly fees. Any amounts deposited by you will appear on your statement as a credit, and service charges and other fees will be invoiced as described above. If you fail to pay any amount on a subsequent xxxx, the unpaid amount will be deducted each billing cycle from the credit amount. Credit amounts will not earn or accrue interest.

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

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