How to Report an Incident Sample Clauses

How to Report an Incident. In order to expedite the resolution of Incidents, NT expects that Customer will make every attempt possible to:
AutoNDA by SimpleDocs
How to Report an Incident. In order to accelerate the resolution of Incidents, SPARKnit expects that Customer will make every attempt possible to:
How to Report an Incident. In order to expedite the resolution of Incidents, CFEngine expects that Customer will make every attempt possible to:

Related to How to Report an Incident

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

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

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

  • Reporting of Reportable Events If Xxxxx determines (after a reasonable opportunity to conduct an appropriate review or investigation of the allegations) through any means that there is a Reportable Event, Xxxxx shall notify OIG, in writing, within 30 days after making the determination that the Reportable Event exists.

  • EFFECTIVE DATE AND NOTICE OF NONLIABILITY This Agreement shall not be effective or enforceable until it is approved and signed by the State Controller or its designee (hereinafter called the “Effective Date”), but shall be effective and enforceable thereafter in accordance with its provisions. The State shall not be liable to pay or reimburse Contractor for any performance hereunder or be bound by any provision hereof prior to the Effective Date.

  • Reporting of Unauthorized Disclosure The Contractor shall immediately report to the State any unauthorized disclosure of confidential information.

  • WHO WILL REVIEW THE INFORMATION DISCLOSED ON THE RELATIONSHIP DISCLOSURE FORM AND ANY UPDATES? The information disclosed on this form and any updates will be a public record as defined by Chapter 119, Florida Statutes, and may therefore be inspected by any interested person. Also, the information will be made available to the Mayor and the BCC members. This form and any updates will accompany the information for the applicant’s project or item. However, for development-related items, if an applicant discloses the existence of one or more of the relationships described above and the matter would normally receive final consideration by the Concurrency Review Committee or the Development Review Committee, the matter will be directed to the BCC for final consideration and action following committee review.

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Reporting of Disclosures The MCP agrees to promptly report to ODM any inappropriate use or disclosure of PHI not in accordance with this Agreement or applicable law, including a breach of unsecured PHI as required at 45 CFR 164.410 and any security incident the MCP has knowledge of or reasonably should have knowledge of under the circumstances.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

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