We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

CARGO AND MAIL Sample Clauses

CARGO AND MAIL thru 5.5 (CO's cargo products) SECTION 6 - RAMP:
CARGO AND MAIL. 5.1. thru 5.5 (CO’s cargo products); at BRO, the employees handling trucking cargo operations will be treated as additional services subject to additional charges hereunder.
CARGO AND MAIL. The Carriers will develop and implement mutually beneficial commercial cooperation programs with respect to the carriage of cargo and mail. Such programs may include, but are not limited to, a separate prorate agreement for interline cargo shipments and an agreement implementing mail codesharing.
CARGO AND MAIL. Handling—General 1.1.1. 5.1.1 (a) Provide (b) Arrange 1. warehouse and storage facility(ies) 2. warehouse handling equipment 3. warehouse handling services

Related to CARGO AND MAIL

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Access to and Maintenance of Auction Records The Auction Agent shall afford to the Company, its agents, independent public accountants and counsel, access at reasonable times during normal business hours to review and make extracts or copies (at the Company's sole cost and expense) of all books, records, documents and other information concerning the conduct and results of Auctions, provided that any such agent, accountant or counsel shall furnish the Auction Agent with a letter from the Company requesting that the Auction Agent afford such person access. The Auction Agent shall maintain records relating to any Auction for a period of two years after such Auction (unless requested by the Company to maintain such records for such longer period not in excess of four years, then for such longer period), and such records, in reasonable detail, shall accurately and fairly reflect the actions taken by the Auction Agent hereunder. The Company agrees to keep confidential any information regarding the customers of any Broker-Dealer received from the Auction Agent in connection with this Agreement or any Auction, and shall not disclose such information or permit the disclosure of such information without the prior written consent of the applicable Broker- Dealer to anyone except such agent, accountant or counsel engaged to audit or review the results of Auctions as permitted by this Section 2.7, provided that the Company reserves the right to disclose any such information if it is advised by its counsel that its failure to do so would (i) be unlawful or (ii) expose it to liability, unless the Broker-Dealer shall have offered indemnification satisfactory to the Company. Any such agent, accountant or counsel, before having access to such information, shall agree to keep such information confidential and not to disclose such information or permit disclosure of such information without the prior written consent of the applicable Broker-Dealer, provided that such agent, accountant or counsel may reserve the right to disclose any such information if it is advised by its counsel that its failure to do so would (i) be unlawful or (ii) expose it to liability, unless the Broker-Dealer shall have offered indemnification satisfactory to such agent, accountant or counsel.

  • Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Operations and Maintenance Seller shall not during the months of June through September inclusive schedule any non-emergency maintenance that reduces the energy generating capability of the Facility by more than ten percent (10%), unless (i) such outage is required to avoid damage to the Facility, (ii) such maintenance is necessary to maintain equipment warranties and cannot be scheduled outside the months of June through September, (iii) such outage is required in accordance with prudent electrical practices, or (iv) the Parties agree otherwise in writing.

  • Workshops During the month of September or October of each year during the term of this Agreement, there shall be held at each University a workshop for Department Chairs at which will be discussed their roles and responsibilities as such. Representatives of the University, at its election, and representatives of the Association, at its election, shall be permitted to participate jointly in such workshop.

  • Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement. (ii) CSXT or NSR, directly or through their respective affiliates, may perform the work which CRC performed prior to the date of this Agreement when (A) CRC does not possess the skills needed for such work, (B) CRC lacks the necessary employees to do such work in a timely fashion, or (C) CRC does not possess the equipment needed to do such work. CRC and the party performing the work shall agree to a reasonable fee for such work prior to performance. CRC, CSXT and NSR may agree to have additional work performed either by CSXT, NSR or their affiliates.

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Account Maintenance Trade Allocations Trade Reporting; (Futures) Daily Trade Checkout Daily Statement Reconciliation

  • Supply and Maintenance of Equipment It is the responsibility of the Employer to furnish and maintain all equipment, machinery and supplies required by employees in the performance of their duties. Employees shall not suffer any loss in salary in the event that they cannot carry out their normal duties by reason of the Employer failing to properly maintain equipment, machinery or supplies or by reason of power failures or other circumstances not attributable to the employees.