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: [*****])
Appears in 2 contracts
Samples: License and Service Agreement (TNAV Holdings, Inc.), License and Service Agreement (TNAV Holdings, Inc.)
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 [*****] Licensor Hours of Operation Role Phone/Email 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. 49 AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement CONFIDENTIAL TREATMENT Licensor Service Level Agreement – Product Manager Contact Information 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. 50 AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement CONFIDENTIAL TREATMENT EXAMPLE A 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: [*****])
1. Title of Incident
2. Brief Description of Incident
a. Should include scope (AT&T service impacted)
3. Start Date and Time
4. Information Service Resolution Date and Time
Appears in 1 contract
Samples: License and Service Agreement
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 Emerging Application NOC (MNOCEAN) 24 x 7 x 365 Incident Management and Emergency Maintenance [*****] [*****] Tier 1 and Tier 2 Support * * * 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 [* * * Reporting Administrator Submits Service Level Reports and Root Cause Analysis Attention: * * * *****] 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* This redacted material has been omitted pursuant to a request for confidential treatment, and notifications [*****] office [*****] mobile [*****] Certain portions denoted with an asterisk have the material has been omitted and filed separately with the Securities and Exchange CommissionSEC. Confidential treatment has been requested with respect to the omitted portions. Attention: Simon Ma Title: Director IT Service Level Manager Address: 0000 601 100xx Xxx. XX, Xxxxx Xx City000 Xxxx, State Zip SunnyvaleXxxxx Xxx Bellexxx, CA, 94086 EXX 00000 X-mail xail Address: [*****] * * * Phone Number: [*****] * * * Fax Number: [400-000-0000 Motricity Customer Care Contact Information Primary Contact (Single Point of Contact) 24 X 7 Contact Name Service Operations Center (SOC) / Carrier Care Title N/A Phone * * * Email * * *@Mxxxxxxxx.xxx Level 0 Xxxxxxxxxx Xxxxxxx Xxxx * * * Title Manager, Service Operations Phone * * *- Mobile Email * * *@Mxxxxxxxx.xxx Level 0 Xxxxxxxxxx Xxxxxxx Xxxx * * * Title Director, Commercial Operations Phone * * * - Mobile *****] [*****] Certain portions denoted with an asterisk have * This redacted material has been omitted pursuant to a request for confidential treatment, and the material has been filed separately with the Securities and Exchange CommissionSEC. Confidential treatment Email * * *@Mxxxxxxxx.xxx Level 3 Escalation Contact Name * * * Title Vice President, Managed Services Phone * * * - Mobile Email * * *@xxxxxxxxx.xxx Engineering contact: *** This redacted material has been requested omitted pursuant to a request for confidential treatment, and the material has been filed separately with respect to the omitted portionsSEC. 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: [* * *****])
Appears in 1 contract