Emergency Messages Sample Clauses

Emergency Messages. Management agrees with the Union that the urgency of delivering emergency, messages is critical to the employee involved. All such calls will be delivered without undue delay. Under Management's current practice, calling parties may contact the plant by dialing telephone number 636-327- 2501 and be guided by the recording. Emergency telephone calls will be received in the Plant Security Office where they will be logged, initialed, and forwarded to the appropriate party. In addition, the security officers will identify themselves to the caller. A follow-up contact will be made by Security to ensure the message was delivered.
Sample 1
AutoNDA by SimpleDocs
Emergency Messages. Within six (6) months of the effective date of this Franchise, Xxxxxxx agrees to equip the Cable System with an Emergency Alert System with the capability to provide an all channel override of both audio and video signals on all programmed channels for the purposes of making public announcements during times of emergency. This capability shall be facilitated through the use of the dial-up telephone system, using a suitable secure access code, or, alternatively, via a dedicated telephone line by the City’s police/public safety department. A routine testing program providing for at least quarterly activation of the system shall be developed by the City and Grantee.
Sample 1

Related to Emergency Messages

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

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

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

  • Emergency Measures Additional measures and/or other special requirements necessary during periods of critical fire-weather conditions shall be included in the fire prevention and presuppression plan.

  • System Agency Data A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency. B. Grantee has no right or license to use, analyze, aggregate, transmit, create derivatives of, copy, disclose, or process the System Agency Data except as required for Grantee to fulfill its obligations under the Grant Agreement or as authorized in advance in writing by System Agency. C. For the avoidance of doubt, Grantee is expressly prohibited from using, and from permitting any third party to use, System Agency Data for marketing, research, or other non-governmental or commercial purposes, without the prior written consent of System Agency. D. Grantee shall make System Agency Data available to System Agency, including to System Agency’s designated vendors, as directed in writing by System Agency. The foregoing shall be at no cost to System Agency. E. Furthermore, the proprietary nature of Xxxxxxx’s systems that process, store, collect, and/or transmit the System Agency Data shall not excuse Xxxxxxx’s performance of its obligations hereunder.

  • Emergency Meetings Public notice of emergency meetings shall be given as soon as practical, but in any event, before the meeting to news media that have filed a written request for notice. In addition to the other notices specified in this policy, the Superintendent or designee shall post the following on the District website: (1) the annual schedule of regular meetings, which shall remain posted until the Board approves a new schedule of regular meetings; (2) a public notice of all Board meetings; and (3) the agenda for each meeting which shall remain posted until the meeting is concluded. LEGAL REF.: 5 ILCS 120/, Open Meetings Act. 5 ILCS 140/, Freedom of Information Act. 105 ILCS 5/10-6 and 5/10-16. CROSS REF.: 2:110 (Qualifications Term, and Duties of Board Officers), 2:120 (Board Member Development), 2:210 (Organizational Board of Education Meetings), 2:220 (Board of Education Meeting Procedure), 2:230 (Public Participation at Board of Education Meetings and Petitions to the Board), 6:235 (Access to Electronic Networks) Adopted: January 21, 2020

  • Emergency A circumstance requiring immediate action; a sudden, unexpected happening; an unforeseen occurrence or condition.

  • Electronic Media 10.5.1 Where this Agreement or referenced provisions in the Contract Documents require the Project Consultant to provide information or documents in either electronic or magnetic media, the preparation and format of that media shall conform to the Owner's Electronic Media Submittal Requirements (Attachment 3 to this Agreement).

  • Emergency Procedures All residents and guests are required to exit the building during emergencies that require evacuation and follow instructions given by authorized University emergency personnel (e.g., Security Services, Emergency Response Wardens and Building Emergency Captains). Residents and guests FIRE PROCEDURES AND FIRE ALARMS: All residents and guest(s) are required to exit the residences at the sound of a fire alarm. In the event of fire, residents and guest(s) are required to follow instruction given by Fire Services personnel.

  • Electronic Means Delivery of an executed copy of this Agreement by electronic facsimile transmission or other means of electronic communication capable of producing a printed copy will be deemed to be execution and delivery of this Agreement as of the effective date of this Agreement.

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