Venue Security Sample Clauses

Venue Security. Caterer agrees that no Caterer personnel will be allowed in any University venue unless a University representative is present. Caterer agrees that arrival and departure from venue will occur at times stipulated by the Statement of Work unless otherwise authorized by the venue manager.
AutoNDA by SimpleDocs
Venue Security. Venue security in accordance with Section V(B). ZZBBB. “Suites” shall mean the suites identified in the Plans and Specifications. AAACCC. “Team Store(s)” shall mean the merchandise store(s) located within the‌‌ Venue, which are more specifically described in the Plans and Specifications.
Venue Security. 5.1. We will make arrangements for the Venue to be opened and locked after your specific event. You agree to notify us as soon as you become aware that your specific event may, or will, start later or end earlier than specified on your Booking Form.
Venue Security. Client shall provide adequate security and crowd control measures during Artist’s performance. Any damage or loss to Artist’s equipment or belongings resulting from inadequate security of venue will be Client’s responsibility to reimburse artist for damages within 5 business days of date of event.
Venue Security. DALTON shall determine and make arrangements at their expense for adequate law enforcement security during the EVENT week (typically Wed-Mon) which needs to include: venue internal, external, traffic control and law enforcement services including 24 hour security for EVENT aircraft and venue through local law enforcement officers and/or a private security group for the entire term of the Event. Any additional security services for event entry and crowd screening, private areas and other requirements deemed necessary for the EVENT will be the responsibility of WODG.

Related to Venue Security

  • Site Security While providing services at a DSHS location, the Contractor, its agents, employees, or Subcontractors shall conform in all respects with physical, fire, or other security regulations specific to the DSHS location.

  • JOB SECURITY 23.01 Subject to the willingness and capacity of individual employees to accept relocation and retraining, the Employer will make every reasonable effort to ensure that any reduction in the work force will be accomplished through attrition.

  • Supplemental Pricing Documents No response Optional. If when completing Pricing Form 1 & Pricing Form 2 you direct TIPS to view additional, alternate, or supplemental pricing documentation, you may upload that documentation.

  • Alternate or Supplemental Pricing Documents No response Optional. If when completing Pricing Form 1 & Pricing Form 2 you direct TIPS to view additional, alternate, or supplemental pricing documentation, you may upload that documentation.

  • SOFTWARE SECURITY If applicable, BA warrants that software security features will be compatible with the CE’s HIPAA compliance requirements. This HIPAA Business Associate Agreement-Addendum shall supersede any prior HIPAA Business Associate Agreements between CE and BA. EXHIBIT E

  • NOTE For Community-­‐Based TLDs Only] Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-­‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]

  • Guidance Note Customer to insert liability limits which are appropriate for its requirements and represent the right apportionment of risk between the Customer and the Supplier. The aim should be to establish liability ceilings reflecting a combination of the best estimate of the losses that the Customer might suffer in the event of a default by the Supplier, the likelihood of those losses occurring and the value for money considerations in limiting liability A Party shall not be responsible for any Loss under this Contract if and to the extent that it is caused by the default of the other (Default on the part of the Supplier and Customer Cause on the part of the Customer). Subject to Clauses 37.1, 37.2 and 37.6 in no event shall either Party be liable to the other for any: loss of profits; loss of business; loss of revenue; loss of or damage to goodwill; loss of savings (whether anticipated or otherwise); and/or any indirect, special or consequential loss or damage. The Supplier shall be liable for the following types of Loss which shall be regarded as direct and shall (without in any way, limiting other categories of Loss which may be recoverable by the Customer) be recoverable by the Customer: the additional operational and/or administrative costs and expenses arising from any Material Breach; any regulatory losses, fines, expenses or other Losses arising from a breach by the Supplier of any Law. No enquiry, inspection, approval, sanction, comment, consent, or decision at any time made or given by or on behalf of the Customer to any document or information provided by the Supplier in its provision of the Services, and no failure of the Customer to discern any defect in or omission from any such document or information shall operate to exclude or limit the obligation of the Supplier to carry out all the obligations of a professional supplier employed in a client/customer relationship. Save as otherwise expressly provided, the obligations of the Customer under this Contract are obligations of the Customer in its capacity as a contracting counterparty and nothing in this Contract shall operate as an obligation upon, or in any other way xxxxxx or constrain the Customer in any other capacity, nor shall the exercise by the Customer of its duties and powers in any other capacity lead to any liability under this Contract (howsoever arising) on the part of the Customer to the Supplier. For the avoidance of doubt any liabilities which are unlimited shall not be taken into account for the purposes of establishing whether the limit in Clause 37.3.1 has been reached. Nothing in this Clause 37 shall act to reduce or affect a Party’s general duty to mitigate its loss.

  • Conflict of Interest Questionnaire - Form CIQ No response Do not upload this form unless you have a reportable conflict with TIPS. There is an Attribute entitled “Conflict of Interest Questionnaire Requirement” immediately followed by an Attribute entitled “Conflict of Interest Questionnaire Requirement – Form CIQ – Continued.” Properly respond to those Attributes and only upload this form if applicable/instructed. If upload is required based on your response to those Attributes, the Conflict of Interest Questionnaire – Form CIQ must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded at this location. Vendor’s Warranties, Terms, and Conditions (Supplemental Vendor Information Only)

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