Network and Outage Contingency Sample Clauses

Network and Outage Contingency. In case of a network issue, the gates will go into an “Emergency Mode” and open for any ticket that is scanned. During this Emergency Mode, all transactions are stored directly on the gate in the Axess Controller. As soon as the network connection is re-established, all data is pushed to RTP. The Pick Up Box is not operational during a network outage, as it will try to check the validity of the voucher on the RTP server for each ticket it should produce. The only option during the outage is visiting a ticket window for ticket fulfilment of e-commerce purchases.
AutoNDA by SimpleDocs

Related to Network and Outage Contingency

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

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

  • Maintenance Outages If Seller reasonably determines that it is necessary to schedule a Maintenance Outage, Seller shall notify Buyer of the proposed Maintenance Outage at least five (5) days before the outage begins (or such shorter period to which Buyer may reasonably consent in light of then existing conditions). Upon such notice, the Parties shall plan the Maintenance Outage to mutually accommodate the reasonable requirements of Seller and the service obligations of Buyer; provided, however, that, unless Buyer otherwise consents, such consent not to be unreasonably withheld, no Maintenance Outage may be scheduled between the hour ending 0700 through the hour ending 2200, Monday through Saturday, during the time period commencing on May 15 and concluding on September 15. Notice of a proposed Maintenance Outage shall include the expected start date and time of the outage, the amount of Capacity of the Facility that will not be available, and the expected completion date and time of the outage. Seller shall give Buyer notice of the Maintenance Outage as soon as Seller determines that the Maintenance Outage is necessary. Buyer shall promptly respond to such notice and may request reasonable modifications in the schedule for the outage. Seller shall use all reasonable efforts to comply with any request to modify the schedule for a Maintenance Outage. Seller shall notify Buyer of any subsequent changes in Capacity available to Buyer or any changes in the Maintenance Outage completion date and time. As soon as practicable, any notifications given orally shall be confirmed in writing. Seller shall take all reasonable measures and exercise its best efforts in accordance with Prudent Electrical Practices to minimize the frequency and duration of Maintenance Outages.

  • Network Upgrades The Transmission Owner shall design, procure, construct, install, and own the Network Upgrades described in Attachment 6 of this Agreement. If the Transmission Owner and the Interconnection Customer agree, the Interconnection Customer may construct Network Upgrades that are located on land owned by the Interconnection Customer. Unless the Transmission Owner elects to pay for Network Upgrades, the actual cost of the Network Upgrades, including overheads, shall be borne initially by the Interconnection Customer.

  • Network Resource Interconnection Service (check if selected)

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Line Outage Costs Notwithstanding anything in the NYISO OATT to the contrary, the Connecting Transmission Owner may propose to recover line outage costs associated with the installation of Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades on a case-by-case basis.

  • Forced Outages During any forced outage, the NYISO or Connecting Transmission Owner may suspend interconnection service to the Interconnection Customer to effect immediate repairs on the New York State Transmission System or the Distribution System. The NYISO shall use Reasonable Efforts to provide the Interconnection Customer with prior notice. If prior notice is not given, the NYISO shall, upon request, provide the Interconnection Customer written documentation after the fact explaining the circumstances of the disconnection.

  • BELLSOUTH OUTAGE Because BellSouth's equipment has varying degrees of impact on the service provided to the CLECs, restoring service from damaged BellSouth equipment is different. The outage will probably impact a number of Carriers simultaneously. However, the ECC will be able to initiate immediate actions to correct the problem. A disaster involving any of BellSouth's equipment locations could impact the CLECs, some more than others. A disaster at a Central Office (CO) would only impact the delivery of traffic to and from that one location, but the incident could affect many Carriers. If the Central Office is a Serving Wire Center (SWC), then traffic from the entire area to those Carriers served from that switch would also be impacted. If the switch functions as an Access Tandem, or there is a tandem in the building, traffic from every CO to every CLEC could be interrupted. A disaster that destroys a facility hub could disrupt various traffic flows, even though the switching equipment may be unaffected. The NMC would be the first group to observe a problem involving BellSouth's equipment. Shortly after a disaster, the NMC will begin applying controls and finding re-routes for the completion of as much traffic as possible. These reroutes may involve delivering traffic to alternate Carriers upon receiving approval from the CLECs involved. In some cases, changes in translations will be required. If the outage is caused by the destruction of equipment, then the ECC will assume control of the restoration.

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