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.
Adverse Events Subsequent to the date hereof, there shall not have occurred any of the following: (i) a suspension or material limitation in trading in securities generally on the New York Stock Exchange, the NASDAQ National Market or the NASDAQ Global Market, (ii) a general moratorium on commercial banking activities in the People’s Republic of China or New York, (iii) the outbreak or escalation of hostilities involving the United States or the People’s Republic of China or the declaration by the United States or the People’s Republic of China of a national emergency or war if the effect of any such event specified in this clause (iii) in your reasonable judgment makes it impracticable or inadvisable to proceed with the public offering or the delivery of the Shares on the terms and in the manner contemplated in the Prospectus, or (iv) such a material adverse change in general economic, political, financial or international conditions affecting financial markets in the United States or the People’s Republic of China having a material adverse impact on trading prices of securities in general, as, in your reasonable judgment, makes it impracticable or inadvisable to proceed with the public offering of the Shares or the delivery of the Shares on the terms and in the manner contemplated in the Prospectus.
Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.
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.
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.
Emergency Work Employees who are required to report for emergency work on non- workdays, or outside of their regular hours of work on a scheduled workday or on holidays which they are entitled to have off, shall be paid overtime compensation for the actual work time and for travel time in connection therewith, but such travel time shall not exceed one-half (1/2) hour.
Progress Reports The Recipient shall submit to the OPWC, at the OPWC's request, summary reports detailing the progress of the Project pursuant to this Agreement and any additional reports containing such information as the OPWC may reasonably require.
Emergency Maintenance LightEdge reserves the right to perform emergency Service maintenance as needed outside the Scheduled Maintenance window, in which case LightEdge will make a reasonable effort to notify the Customer if feasible under the circumstances. Any such maintenance will be considered an “Emergency Maintenance”. All Service SLAs will apply during Emergency Maintenance.
Notice of Suits, Adverse Events Furnish Agent with prompt notice of (i) any lapse or other termination of any Consent issued to any Borrower by any Governmental Body or any other Person that is material to the operation of any Borrower's business, (ii) any refusal by any Governmental Body or any other Person to renew or extend any such Consent; and (iii) copies of any periodic or special reports filed by any Borrower with any Governmental Body or Person, if such reports indicate any material change in the business, operations, affairs or condition of any Borrower, or if copies thereof are requested by Lender, and (iv) copies of any material notices and other communications from any Governmental Body or Person which specifically relate to any Borrower.
Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.