Emergency Incident Sample Clauses

Emergency Incident. “Code Red” Response Performance Standard – The Contractor shall respond to ninety percent (90%) of all “Code Red” requests within 9 minutes, 59 seconds. The maximum response time is 14 minutes, 59 seconds on any “Code Red” request. All “Code Red” responses shall be made with lights and sirens in operation.
Sample 1Sample 2
AutoNDA by SimpleDocs
Emergency Incident. Report Shows all emergency incidents and related emergency calls/events within a time period. Events Report Shows all events within a time period. Group Airtime Usage Summary Report Provides statistics for selected groups across regions and sites. Summary information is also available in graphical format. Message Trunking Call Events Report Shows all message trunking events within a time period. Single User Agency Report Provides statistics for all users with one agency for a selected time period. System Channel Uptime Report Provides statistics for channel uptime (time a channel was fully functional and capable of passing calls), actual airtime usage, and outage percent. System Channel Usage Report Provides the channel statistics for selected regions and sites for a selected time period. The report provides statistics for each channel at a site. Its information is also available in graphical format. System Customized Report Provides statistics for selected regions and sites. The user can choose different call category combinations to generate custom results. System Profiled Statistics Report Shows system usage on an hourly basis. The report provides an hourly overview of the number of units using a site and the percentage of use of certain call types. System Usage Report Illustrates system usage statistics for a specified region. System Usage by Hour Report Displays airtime, average call duration, and call count for each site on a per-hour basis. System Utilization Report Illustrates the summarized call statistics and unit log-on statistics for a region over a selected time period. The report provides the granted and total call results. System Utilization Detail Report Illustrates the summarized statistics for the system over a selected time period. The report provides data in a table format relative to the type of calls sent over a specific site during a specified time period. The report information is also available in graphical format. User Agency Site Summary Report Provides the summarized statistics for one user agency across a region or selected sites for a selected time period. The report information is also available in graphical format. User Agency Summary Provides the summarized statistics for all user agencies across a region or selected sites for a selected time period. The summary information is also available in graphical format. User Airtime Summary Illustrates the statistics for selected units across a region or selected sites for a select...
Sample 1
Emergency Incident. Driving Contractor shall follow the driving regulations listed in the SIIBM (PMS 902). The SIIBM can be found on the Northern Rockies Coordinating Group's website using the following link: xxxxx://xxxx.xxxx.xxx/nrcc/nrcg/committees/business_committee.htm The Contractor is responsible for complying with all other current federal, state, and local driving regulations and must adhere to ICP or camp speed limits as posted.
Sample 1
Emergency Incident. This term is used to describe any natural or manmade occurrence that results in extraordinary levels of mass casualties, property damage, or disruption that severely affects the population, infrastructure, environment, economy, and/or government functions. This term requires that the incident is of a big enough scale that emergency management operations be coordinated via regional intra-county and regional inter- county entities and agreements.
Sample 1
Emergency Incident. Incident that causes failure of DC-Net data, voice, and/or Wireless LAN service at one or more priority sites.
Sample 1

Related to Emergency Incident

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

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

  • Emergency Duty (1) This clause applies if: (a) an employee is directed to attend for duty to meet an emergency; and (b) the employee would not ordinarily have been on duty at that time; and (c) the employee was not given notice of the direction before ceasing ordinary duty; and (d) the employee is not at a classification above the salary barrier or an AGS fee earner. (2) However, the Secretary may decide that this clause applies to an employee at a classification above the salary barrier (unless they are an AGS fee earner). (3) For the time on duty, the employee is to be paid: (a) at the rate of double time; and (b) for at least 2 hours. (4) The time on duty is taken to include time necessarily spent in travelling to and from duty. (5) This clause does not apply if the employee is subject to a restriction direction. (6) Clause 3.23 (rest relief after overtime) does not apply to overtime worked in circumstances covered by this clause unless the actual time worked is at least 3 hours for each attendance.

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

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

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

  • Emergency Overtime In the event of an emergency as defined in Section 13.15 notwithstanding the terms of this Article, the Agency Head or designee may assign someone to temporarily meet the emergency requirements, regardless of the overtime distribution.

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