Time of Incidents Sample Clauses

Time of Incidents. During the period December 2007 – January 2008, 67% (six out of nine) of the total number of actual incidents occurred between 1800 hrs and 0559 hours. This is expected since ships are most vulnerable under the cover of darkness. This is comparable to the period December 2006 – January 2007 where 90% (nine out of ten) of the total number of actual incidents occurred during the same time. 1800 hrs to 2359 hrs 2400 hrs to 0559 hrs 0600hrs to 1159 hrs 1200 hrs to 1759 hrs Total December 2007- January 2008 1 5 2 1 9 December 2006- January 2007 9 1 10 Table 8 – Local time of incidents (December 2007-January 2008 and December 2006-January 2007) 10 Figure 1 : Location of incidents during December 2007 – January 2008 Part 3 - Details of Selected Incidents
Sample 1
AutoNDA by SimpleDocs
Time of Incidents. In October 2007, eight out of ten reported incidents occurred between 1800 hrs to 0600 hrs. This is expected as ships are most vulnerable during the hours of darkness, and is comparable to October 2006 when nine out of 12 reported incidents occurred during the same time frame. 1800 hrs to 2359 hrs 2400 hrs to 0559 hrs 0600hrs to 1159 hrs 1200 hrs to 1759 hrs October 2007 1 7 1 1 October 2006 3 6 2 1 Table 7 – Local time of incidents during October 2007 and October 2006 Fig Figure 1 : Location of All Incidents in July 2007 Figure 2 : Location of All Incidents in October 2007 Part 3 - Details of Selected Incidents
Sample 1
Time of Incidents. In February 2008, 75% (three out of four) of the total number of actual incidents occurred between 0000 hrs and 0559 hrs. This is comparable to February 2007 when 67% (two out of three) incidents occurred during the same time. 1800 hrs to 2359 hrs 0000 hrs to 0559 hrs 0600hrs to 1159 hrs 1200 hrs to 1759 hrs Total February 2007 2 1 3 Table 8 – Local time of actual incidents (February 2008 and February 2007) Figure 2 : Location of incidents during February 2008 Part 3 - Details of Selected Incidents
Sample 1
Time of Incidents. Table 7 shows the local time of actual and attempted incidents in April 2008 and April 2007. In April 2008, 13 out of the 14 reported incidents occurred between 1800hrs to 0559hrs. This is comparable to April 2007 when eight out of the 11 reported incidents occurred during the same period. This is expected since ships remain most vulnerable during hours of darkness. 1800 hrs to 2359 hrs 2400 hrs to 0559 hrs 0600hrs to 1159 hrs 1200 hrs to 1759 hrs April 2007 3 5 1 2
Sample 1

Related to Time of Incidents

  • 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

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

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

  • Reporting Security Incidents The Business Associate will report to the County any Incident of which the Business Associate becomes aware that is:

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

  • Types of Disciplinary Action It is the intent of the District to establish disciplinary procedures which are commensurate with the reasons or causes for disciplinary action. The principle of progressive discipline should be applied when repeated action is necessary. The following types of disciplinary action are listed in order of their increasing severity.

  • CHANGE OF CIRCUMSTANCES The Company will, at any time during the pendency of a Placement Notice advise the Agent promptly after it shall have received notice or obtained knowledge thereof, of any information or fact that would alter or affect in any material respect any opinion, certificate, letter or other document required to be provided to the Agent pursuant to this Agreement.

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

  • Reporting Unsuccessful Security Incidents Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

  • Causes The contract may be terminated before the stated completion date by any of the following conditions.

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