Fault Incidents Sample Clauses

Fault Incidents. 7.4.1 During the staffed hours of the NMC. When the NMC receives information on a fault incident it is logged. Where the fault is with the System, a fault response as per Section 7.3 is initiated. Where the fault incident is not with the System, but is within the responsibility of the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Client and the NMC / on-call engineer cannot agree which severity level should be allocated to the fault, the matter will be referred to each representative’s immediate superior for determination. During any disagreement, between the Client and the Service Provider, on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 Outside the staffed hours of the NMC the scheduled on-call engineer will be alerted to all relevant alarms raised by the Service Provider's SCADA / automated alarm system. The relevant information will be communicated to the NMC the following morning for processing as per Section 7.3. 7.4.4 The following list describes the fault level categories.
Sample 1Sample 2Sample 3See All (16)
AutoNDA by SimpleDocs
Fault Incidents. 7.4.1 During the staffed hours of the NMC. When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Client, and/or any Authorised Representative nominated by the Client, and the NMC / on-call engineer cannot agree which severity level should be allocated to the fault, the matter will be referred to each representative’s immediate superior for determination. During any disagreement between the Client, and/or any Authorised Representative nominated by the Client, and the Service Provider on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 Outside the staffed hours of the NMC the scheduled on-call engineer will be alerted to all relevant alarms raised by the Service Provider's SCADA / automated alarm system. The relevant information will be communicated to the NMC the following morning for processing as per Section 7.3. 7.4.4 The following list describes the fault level categories.
Sample 1Sample 2Sample 3See All (8)
Fault Incidents. 7.4.1 During the staffed hours of the NMC. When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Client, and/or any Authorised Representative nominated by the Client, and the NMC / on-call engineer cannot agree which severity level should be allocated to the fault, the matter will be referred to each representative’s immediate superior for determination. During any disagreement between the Client, and/or any Authorised Representative nominated by the Client, and the Service Provider on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 Outside the staffed hours of the NMC the scheduled on-call engineer will be alerted to all relevant alarms raised by the Service Provider's SCADA / automated alarm system. The relevant information will be communicated to the NMC the following morning for processing as per Section 7.3. 7.4.4 The following list describes the fault level categories. Level 1 >= Main Transmitter Site Faults 5. Total loss of, or a reduction in Power greater than Lower Failure Threshold in, the output of any main transmission site. 6. Total failure of the primary distribution system (Microwave Radio Links system) at the site or location. Level 2 >= Priority Relay or Priority Transposer Site Faults 5. Total loss of, or a reduction in Power greater than Lower Failure Threshold in, the output of any priority transposer or priority relay transmission site. 6. Total failure of the secondary distribution system (Rebroadcast) at a priority transposer site. Level 3 >= Transposer or Relay Site Faults 5. Total loss of, or a reduction in Power greater than Lower Failure Threshold in, the output of any transposer or relay transmission site. 6. Total failure of the secondary distribution system (Rebroadcast) at a transposer or re-transmitter site.
Sample 1Sample 2Sample 3See All (8)
Fault Incidents. 7.4.1 When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 Subject to Clause 3 (Term), the Client may from time to time require the Service Provider to investigate documented generalised complaints concerning the Client’s coverage/signal strength in areas where adequate coverage is predicted by the Service Provider.
Sample 1
Fault Incidents. 7.4.1 When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 Subject to Clause 3 (Term), the Client may from time to time require the Service Provider to investigate documented generalised complaints concerning the Client’s coverage/signal strength in areas where adequate coverage is predicted by the Service Provider. 7.4.2.1 The Service Provider will be entitled to levy additional fees for such work, where such work is not covered by a pre-existing obligation under this Agreement and where the investigation proves that coverage/signal strength is as predicted. The Service Provider will conduct two investigations (maximum of three man days each) per Audio Stereo Pair(s)per year without levying additional fees. 7.4.2.2 The Service Provider will not be entitled to levy additional fees for such work, where such work is covered by a pre-existing obligation under this Agreement and where the investigation proves that coverage/signal strength is not as predicted. The Client may be entitled to a Service Credit under Section 11 in this situation.
Sample 1

Related to Fault Incidents

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Accidents If a death, serious personal injury or substantial property damage occurs in connection with CONTRACTOR’s performance of this Agreement, CONTRACTOR shall immediately notify Mendocino County Risk Manager's Office by telephone. CONTRACTOR shall promptly submit to COUNTY a written report, in such form as may be required by COUNTY of all accidents which occur in connection with this Agreement. This report must include the following information: (1) name and address of the injured or deceased person(s); (2) name and address of CONTRACTOR's sub-contractor, if any; (3) name and address of CONTRACTOR's liability insurance carrier; and (4) a detailed description of the accident and whether any of COUNTY's equipment, tools, material, or staff were involved.

  • Technical and Organisational Measures (1) Before the commencement of processing, the Supplier shall document the execution of the necessary Technical and Organisational Measures, set out in advance of the awarding of the Order or Contract, specifically with regard to the detailed execution of the contract, and shall present these documented measures to the Client for inspection. Upon acceptance by the Client, the documented measures become the foundation of the contract. Insofar as the inspection/audit by the Client shows the need for amendments, such amendments shall be implemented by mutual agreement. (2) The Supplier shall establish the security in accordance with Article 28 Paragraph 3 Point c, and Article 32 GDPR in particular in conjunction with Article 5 Paragraph 1, and Paragraph 2 GDPR. The measures to be taken are measures of data security and measures that guarantee a protection level appropriate to the risk concerning confidentiality, integrity, availability and resilience of the systems. The state of the art, implementation costs, the nature, scope and purposes of processing as well as the probability of occurrence and the severity of the risk to the rights and freedoms of natural persons within the meaning of Article 32 Paragraph 1 GDPR must be taken into account. [Details in Appendix 1] (3) The Technical and Organisational Measures are subject to technical progress and further development. In this respect, it is permissible for the Supplier to implement alternative adequate measures. In so doing, the security level of the defined measures must not be reduced. Substantial changes must be documented.

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