Compulsory Occurrence Book Entries. The security personnel on duty must make the following entries in the occurrence book:
Compulsory Occurrence Book Entries Sample Clauses
Related to Compulsory Occurrence Book Entries
Unauthorised Transactions As between you and Stripe, you are responsible for Card Transactions, and fees and penalties Stripe incurs resulting from any Card Authorised User’s failure to (a) exercise reasonable care in safeguarding Cards from loss or theft; or (b) promptly report loss or theft, including fraud. Additionally, to the extent Law permits, if you or a Card Authorised User allows another party to use the Card or Card Account Data for any purpose or if an unauthorised person uses a Card or Card Account Data, you will be liable for that use, including all losses, damages and costs arising out of or relating to that use. To the extent Law permits, Stripe is not liable for any losses, damages or costs to you or your Card Authorised Users arising out of or relating to (y) unauthorised access to or use of a Card or your Stripe Issuing Account; or (z) your failure to use or implement anti-fraud measures, security controls or any other data security measures.
Commercial General Liability – Occurrence Form Policy shall include bodily injury, property damage, personal injury and broad form contractual liability. • General Aggregate $2,000,000 • Products – Completed Operations Aggregate $1,000,000 • Personal and Advertising Injury $1,000,000 • Blanket Contractual Liability – Written and Oral $1,000,000 • Fire Legal Liability $50,000 • Each Occurrence $1,000,000
Alternate Traffic Routing If CLEC has a LIS arrangement which provides two (2) paths to a CenturyLink End Office Switch (one (1) route via a Tandem Switch and one (1) direct route), CLEC may elect to utilize alternate traffic routing. CLEC traffic will be offered first to the direct trunk group (also referred to as the "primary high" route) and then overflow to the Tandem Switch group (also referred to as the "alternate final" route) for completion to CenturyLink End Office Switches.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.
Return or Destruction (a) As requested by the Furnishing Party during the Agreement Term, the Receiving Party will return or provide the Furnishing Party a copy of any designated Confidential Information of the Furnishing Party.
Government Code Claim Requirement No suit for money or damages may be brought against the City until a written claim therefor has been presented to and rejected by the City in conformity with the provisions of San Francisco Administrative Code Chapter 10 and California Government Code Section 900, et seq. Nothing set forth in this Agreement shall operate to toll, waive or excuse Contractor’s compliance with the California Government Code Claim requirements set forth in San Francisco Administrative Code Chapter 10 and California Government Code Section 900, et seq.
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
Global Safeguard Measures 1. The rights and obligations of the Parties in respect of global safeguards shall be governed by Article XIX of GATT 1994 and the WTO Agreement on Safeguards.
Unlisted/Non-Published Subscribers <<customer_name>> will be required to provide to BellSouth the names, addresses and telephone numbers of all <<customer_name>> customers that wish to be omitted from directories.
