Breakdown Notifications of SIX Sample Clauses

Breakdown Notifications of SIX. In the event of production problems (breakdowns) affecting the participants, the reported support team of the participants affected shall be informed about the occurrence of a breakdown by SIX per e-mail within the periods (response times) specified in Chapter 1. Once the breakdown is removed, SIX shall inform the same recipients that the system is available again. Should the interruptions last longer, SIX shall inform that the breakdown further exists and define a point in time, at which the next information shall be announced. These e-mails shall inform about the occurrence and effect of a breakdown. They shall not provide any information about the cause of such breakdown. For the sake of speed, SIX may send initial information without details of the breakdown. The e-mails shall be written in German and English. Breakdown reports shall be treated confidentially and must not leave the circle of participants and affected users. Forwarding of this information to third parties engaged by the participants (e.g. system operators of the participants) shall be ensured by the participants.
Sample 1Sample 2
AutoNDA by SimpleDocs
Breakdown Notifications of SIX. In the event of production problems (breakdowns) affecting the participants, the reported support team of the participants affected shall be informed about the occurrence of a breakdown by SIX per e-mail within the periods (response times) specified in Chapter 1.3. Once the breakdown is removed, SIX shall inform the same recipients that the system is available again. Should the interruptions last longer, SIX shall inform that the breakdown further exists and define a point in time, at which the next information shall be announced. These e-mails shall inform about the occurrence and effect of a breakdown. They shall not provide any information about the cause of such breakdown. For the sake of speed, SIX may send initial information without details of the breakdown. The e-mails shall be written in German and English. Breakdown reports shall be treated confidentially and may not leave the circle of participants and affected customers. Forwarding of this information to third parties engaged by the participants (e.g. system operators of the participants) shall be ensured by the participants. Breakdown Notifications of the Participants In the course of support operation, the participants may report any breakdowns of production or test systems of SIX to the support team of SIX. Outside the support operation, a central breakdown team of SIX shall be available to the participants. It shall only accept breakdown notifications from the production system; support requests shall not be possible. SIX shall reserve the right to inform the participant about the current breakdown notification upon their corresponding request. Safety-relevant incidents in accordance with Annex 5 shall be reported to SIX immediately.
Sample 1

Related to Breakdown Notifications of SIX

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

  • Accommodations of Spiritual or Cultural Observances Where an employee observes a cultural/spiritual day other than those listed above, the employee shall submit their request in January of each year for the twelve (12) month period following March 1st, identifying the required date they need off.

  • Warranty Affirmations Assurances and Certifications 3.01 Federal Assurances Performing Agency further certifies that, to the extent Federal Assurances are incorporated into the Contract under the Signature Document, the Federal Assurances have been reviewed and that Performing Agency is in compliance with each of the requirements reflected therein.

  • Conditions of Eft Services a. Ownership of Cards. Any card or other device which we supply to you is our property and must be returned to us, or to any person whom we authorize to act as our agent, or to any person who is authorized to honor the card, immediately according to instructions. The card may be repossessed at any time at our sole discretion without demand or notice. You cannot transfer your card or account to another person.

  • WARRANTY, AFFIRMATIONS, ASSURANCES AND CERTIFICATIONS 12 5.1 WARRANTY 12 5.2 General Affirmations 13 5.3 Federal Assurances 13 5.4 Federal Certifications 13 5.5 State Assurances 13 ARTICLE VI. INTELLECTUAL PROPERTY 13 6.1 Ownership of Work Product 13 6.2 Grantee s Pre-Existing Works 14 6.3 THIRD PARTY IP 14 6.4 Agreements with Employees and Subcontractors 14 6.5 Delivery upon Termination or Expiration 15 6.6 SURVIVAL 15 6.7 System Agency Data 15 ARTICLE VII. PROPERTY 15

  • Child Support Enforcement Requirements Contractor is required to comply with the child support enforcement requirements of the County. Failure of the Contractor to comply with all federal, state, and local reporting requirements for child support enforcement or to comply with all lawfully served Wage and Earnings Assignment Orders and Notices of Assignment shall constitute a material breach of the Contract. Failure to cure such breach within 60 calendar days of notice from the County shall constitute grounds for termination of the Contract.

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