Contacts and Hours of Operation Sample Clauses

Contacts and Hours of Operation. The following Contacts information may be updated and republished anytime by either party upon written notice to the other. Changes will not be maintained within this SLA document. Please notify AT&T of changes at: [*****]. Mobility Network Operations Center (MNOC) 24 x 7 x 365 Incident Management and Emergency Maintenance [*****] [*****] Mobility External Partner Management 8:00 am – 5:00 pm PT Monday – Friday Incident Root Cause Analysis, Performance Reports and Tier 2 Support [*****] Mobility Change Management 8:00 am – 5:00 pm PT Monday – Friday Maintenance Notification – all maintenance [*****] TeleNav Operations NOC # 24 x 7 x 365 Initial Contact, issue reporting. [*****] Xxxx Xxxxxx – IT Admin Xxxxx Xxxx – Network Admin 24 x 7 x 365 Emergency Escalation [*****] [*****] Simon Ma – Director IT 24 x 7 x 365 All Issues, Escalation, and notifications [*****] office [*****] mobile [*****] Certain portions denoted with an asterisk have been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Attention: Simon Ma Title: Director IT Address: 0000 Xxxxx Xx City, State Zip Sunnyvale, CA, 94086 E-mail Address: [*****] Phone Number: [*****] Fax Number: [*****] [*****] Certain portions denoted with an asterisk have been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. The following examples are provided as a template to use for Incident Notification (“Examples A”), Root Cause Analysis (“Examples B”) and Maintenance Requests (“Examples C”). When communicating with AT&T, please include in the Subject field of the email, one of the following: 1. Outage <Initial/Update/Final> and <partner name> and <name of service> 2. Emergency Maintenance <partner name> and <name of service and node> 3. Planned Maintenance <partner name> and <name of service and node> Example A: Incident Notification or Trouble Ticket (send to: [*****])
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Contacts and Hours of Operation. The following Contacts information may be updated and republished anytime by either party upon written notice to the other. Changes will not be maintained within this SLA document. Please notify AT&T of changes at: [*]. AT&T Hours of Operation Role Phone/Email Mobility Network Operations Center (MNOC) 24 x 7 x 365 Incident Management and Emergency Maintenance [*] [*] Mobility External Partner Management 8:00 am - 5:00 pm PT Monday - Friday Incident Root Cause Analysis, Performance Reports and Tier 2 Support [*] Mobility Change Management 8:00 am - 5:00 pm PT Monday - Friday Maintenance Notification - all maintenance [*] AT&T CONFIDENTIAL& PROPRIETARY 21 * Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Tier Title Phone (Office) Phone (Mobile) Email Address 1 Network Operations Center [*] n/a [*] 2 Network Operations Center Manager [*] [*] [*] 3 Director of Operations [*] [*] [*] 4 VP of Operations [*] [*] [*] Product Manager Contact Information Title: Sr. Director, Product Management Address: 0000 Xxxxxxxx Xxx. Xxxxx 000 Xxxx, Xxxxx Xxx Xxxxxxxxxx, XX 00000 Phone Number: [*] Fax Number: [*] AT&T CONFIDENTIAL& PROPRIETARY 22 * Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. AT&T agrees that You will receive the greater of (i) [*] of the “Net Revenue” generated by the sale or other exploitation of the White Label Application under this Agreement (the “Revenue Share”); or (ii) [*] per month per End User. For these purposes, “Net Revenue” means the gross price collected from End Users for the White Label Application (other than any transport or other telecommunications charges), less any credits, sales taxes, use taxes, or other governmental charges (e.g., Universal Service Fee Charges). AT&T will calculate the amount due to be remitted or paid to You (collectively “Remittance”) at the end of every calendar month. You will integrate into the AT&T designated billing vendor (currently QPass) in compliance with QPass requirements. Once integrated, You will have access to the vendor on-line reporting system. In addition, AT&T will provide a statement describing the Remittance due to You, and pay that Remittance to You in United States dollars, within [*] days after the end ...
Sample 1Sample 2
Contacts and Hours of Operation. The following Contacts information may be updated and republished anytime by either party upon written notice to the other. Changes will not be maintained within this SLA document. Please notify Cingular of changes at: *** NSD National Operations Center 24 x 7 x 365 Incident Management and Emergency Maintenance *** MMS External Partner Ops 8:00 am – 5:00 pm PT Monday – Friday Incident Root Cause Analysis, Change Management, Performance Reports and Tier 2 Support *** Change Management 8:00 am – 5:00 pm PT Monday – Friday Maintenance Notification – all maintenance *** Level 1 Network Operations Center Customer Help Desk *** 24/7/365 *** Level 2 Network Operations Center *** *** Business Hours *** Level 3 Production *** *** Business Hours *** MOTRICITY will respond within one business day to all CINGULAR developer support inquires. Developer Care Support & Escalation Process: • Developer contacts the Cingular developer Forum. If the issue is specific to Motricity and cannot be resolved by Cingular it is escalated to tier 2 at MOTRICITY via email or and a ticket ID is issued. • If issue is resolved, close ticket. • If upon thorough investigation, issue cannot be resolved at tier 2, the issue is escalated to Motricity Engineering or Systems resource as appropriate. Issue ownership is maintained by Content & Developer Services representative to preserve developer relationship. • Upon resolution, close ticket. • At any time, developers can reopen closed tickets and process is resumed at the point in which it was closed or escalated. Timeline requirements for Content Qualification and Review will be split into two sections for requirements. The first will be described as the time required having Content launch ready. The second is to have the launch ready Content fully available to Subscribers for purchasing. Time to Launch Ready - The MOTRICITY process for testing and launching applications once they have been submitted shall conform to the following timeline requirements: From a Trusted Content Provider *** From untrusted Content Provider *** A Trusted Content Provider is defined as one who has an established relationship with Motricity as a Content provider. This relationship is characterized as one where the Content provider has: • Taken the Motricity prescribed training on Content onboarding, or has been providing Content for a period of *** or more and has met the detailed Content quality guidelines detailed in the trusted partner program. A Trusted Content ...
Sample 1Sample 2
Contacts and Hours of Operation. The following contact information may be updated and republished anytime by either party upon written notice to the other. Changes shall not be maintained within this SLA document. [******] [******] [******] [******] [******] [******] [******] [******] Except as modified and amended by this Amendment, the terms of the Agreement are ratified and confirmed by the parties hereto. This Amendment is incorporated into and made a part of the Agreement by the parties. [******] Certain portions denoted with an asterisk have been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions.
Sample 1Sample 2
Contacts and Hours of Operation. The following Contacts information may be updated and republished anytime by either Party upon written notice to the other. Changes will not be maintained within this SLA document. Please notify AT&T of changes at: xxx.xxxxxxxx.xxx@xxx.xxx. [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] Attention: [***] Title: [***] Address: [***] City, State Zip [***] E-mail Address: [***] Phone Number: [***] Fax Number: [***] The following examples are provided as a template to use for Incident Notification (“Examples A”), Root Cause Analysis (“Examples B”) and Maintenance Requests (“Examples C”). [***] [***] The following examples are provided as a template to use for Incident Notification (“Examples A”), Root Cause Analysis (“Examples B”) and Maintenance Requests (“Examples C”). [***]
Sample 1
Contacts and Hours of Operation. Contact information may be updated and republished anytime by either party with written notice to the other. Changes shall not be maintained within this SLA document.
Sample 1
Contacts and Hours of Operation. The following Contacts information may be updated and republished anytime by either party upon written notice to the other. Changes will not be maintained within this SLA document. STI Support Center 8:00 am – 5:00 pm PT Monday – Friday VM with notification for after hours Receive and report internal operational issues and maintenance 0-000-000-0000 xxxxxxx@xxxxxxxxxxx.xxx Xxxx Xxxxxxx, STI Support Center Manager 24 x 7 x 365 Escalation – Maintenance and ensure all operational issues are resolved 000-000-0000 wireless xxxx@xxxxxxxxxxx.xxx Xxx Xxxxxxx, VP – Product Management 24 x 7 x 365 Escalation – Ensure all operational issues are resolved 000-000-0000 wireless xxxxxxxx@xxxxxxxxxxx.xxx
Sample 1
AutoNDA by SimpleDocs

Related to Contacts and Hours of Operation

  • Hours of Operation You can access automated account information through the Service 7 days a week, 24 hours a day. There may be times, however, when all or part of the Service is unavailable due to system outages or maintenance. We assume no responsibility for any damage or delay that may result from such unavailability.

  • PERIOD OF OPERATION Subject to certification, this Agreement shall come into force from the first pay period commencing on or after 1st December 2002 and shall remain in force until 31 October 2005.

  • Date of Operation 3.1 This Agreement remains in force until 2/7/2027. The agreement will continue to apply beyond its expiration date until it is replaced in accordance with the FW Act.

  • Statement of Operations Statement of Changes in Net Assets.

  • DATE AND PERIOD OF OPERATION 3.1 This Agreement will operate from the date seven (7) days after it is approved by the FWC and shall have a nominal expiry date of 2 July 2027. By no later than 2 July 2026 the Employer intends to commence discussions concerning a replacement enterprise agreement. This Agreement will continue to operate after its nominal expiry date unless it is replaced by another enterprise agreement or terminated in accordance with the Fair Work Act.

  • Continuity of Operations Engage in any business activities substantially different than those in which Borrower is presently engaged, (2) cease operations, liquidate, merge, transfer, acquire or consolidate with any other entity, change its name, dissolve or transfer or sell Collateral out of the ordinary course of business, or (3) pay any dividends on Borrower's stock (other than dividends payable in its stock), provided, however that notwithstanding the foregoing, but only so long as no Event of Default has occurred and is continuing or would result from the payment of dividends, if Borrower is a "Subchapter S Corporation" (as defined in the Internal Revenue Code of 1986, as amended), Borrower may pay cash dividends on its stock to its shareholders from time to time in amounts necessary to enable the shareholders to pay income taxes and make estimated income tax payments to satisfy their liabilities under federal and state law which arise solely from their status as Shareholders of a Subchapter S Corporation because of their ownership of shares of Borrower's stock, or purchase or retire any of Borrower's outstanding shares or alter or amend Borrower's capital structure.

  • CONTINUITY OF OPERATION Section 1: No Strikes, Work Stoppages or Lockouts

  • Cessation of Operations Any cessation of operations by Borrower or Borrower admits it is otherwise generally unable to pay its debts as such debts become due, provided, however, that any disclosure of the Borrower’s ability to continue as a “going concern” shall not be an admission that the Borrower cannot pay its debts as they become due.

  • SUSPENSION OF OPERATIONS Concessionaire shall, at the direction of Department, immediately suspend, delay or interrupt Concessionaire’s operation of all or any part of the Concession Premises for such period of time as Department may determine to be appropriate to protect the Concession Premises and/or public health, safety, and welfare due to the occurrence of hazardous work conditions, emergency conditions, and/or any other cause including, but not limited to, Concessionaire's failure to perform any of the covenants, agreements, and conditions contained in this Agreement on its part to be performed. Concessionaire hereby waives any claim, and Department shall not be liable to any party claiming through Concessionaire, for damages, payment abatement, or compensation as a result of Department's actions under this Paragraph or this Agreement. Department's suspension of Concessionaire's operations shall be in addition to any other right or remedy available by law or in equity.

  • Commencement of Operations The Partnership shall not begin operations on its Leases unless the Managing General Partner is satisfied that necessary title requirements have been satisfied.

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