Airport Security The Contractor shall be familiar with and conduct its operations in accordance with all regulations and directives of the Authority and the Transportation Security Administration, and any other federal, state or local government having jurisdiction over the airport, with respect to the maintenance of airport security.
E7 Security The Authority shall be responsible for maintaining the security of the Authority premises in accordance with its standard security requirements. The Contractor shall comply with all security requirements of the Authority while on the Authority premises, and shall ensure that all Staff comply with such requirements.
Mobile Deposit Security You will complete each deposit promptly. If you are unable to complete your deposit promptly, you will ensure that your mobile device remains securely in your possession until the deposit has been completed. It is your responsibility to establish and maintain procedures to safeguard against unauthorized deposits. You will notify us immediately by telephone with written confirmation if you learn of any loss or theft of original checks. You will ensure the safety and integrity of original checks from the time of receipt until the time of destruction. If warranted in our reasonable judgment, we may audit and monitor you, and you agree to cooperate with us to permit such monitoring, to confirm that you have satisfied your obligations under this Agreement.
CONTRACT SECURITY 8.2.1 The Contractor shall, prior to the Commencement Date or within the specified time, provide to the Owner any contract security specified in row D.2 of the Information Sheet.
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.
Payment Security To secure all of CAISO’s payment obligations to Owner under this Agreement, CAISO agrees to grant Owner a security interest and lien in the following collateral (collectively, the “Collateral”): (a) all past, present and future accounts and other amounts Responsible Utility owes CAISO at any time pursuant to Section 41 of the CAISO Tariff attributable to invoices submitted by Owner under this Agreement (collectively, the “Accounts”), (b) the RMR Owner Facility Trust Account, all funds in the RMR Owner Facility Trust Account at any time, and all funds paid on account of any Accounts, (c) all proceeds of the Collateral, if any, and (d) all of CAISO’s right, title and interest in the Collateral. CAISO represents and warrants to Owner that (a) CAISO has the authority to grant such security interest, (b) CAISO will have good, marketable and exclusive title to all of the Collateral, (c) such security interest and lien will at all times be a valid, enforceable and first-priority lien on the Collateral, and (d) such security interest will be duly perfected by the filing of a financing statement under the California Uniform Commercial Code describing the Collateral in the office of the Secretary of State of California and the delivery of a written notice of Owner’s security interest to the bank with which the RMR Owner Facility Trust Account is maintained. If CAISO defaults on its obligation to pay under this Agreement, Owner shall be entitled to enforce such securityinterest, to exercise its rights in the Collateral, to collect the Accounts from Responsible Utility, to collect all funds in the RMR Owner Facility Trust Account, and to exercise all other rights and remedies under the California Uniform Commercial Code. CAISO agrees to promptly execute and deliver all financing statements and other documents Owner reasonably requests, including but not limited to a written notice of Owner’s security interest in the Collateral to the bank with which the RMR Owner Facility Trust Account is maintained, in order to maintain, perfect and enforce such security interest.
Bid Security 2.1 Bid security, as a guarantee of good faith, in the form of a certified check, cashier's check, or bidder's bond, may be required to be submitted with this bid document, as indicated on the bid.
2.1.1 Bid security, if required, shall be in the amount specified on the bid. The bid security must be scanned and attached to the “Response Attachments” section of your response or it can be faxed to the Purchasing Office at 000-000-0000. The original bid security should then be sent or delivered to the office of the Purchasing Division, 000 X. 0xx Xx., Xxx. 000, Xxxxxxx, XX 00000 to be received within three (3) days of bid closing.
2.1.2 If bid security is not received in the Office of the Purchasing Division as stated above, the vendor may be determined to be non-responsive.
2.2 If alternates are submitted, only one bid security will be required, provided the bid security is based on the amount of the highest gross bid.
2.3 Such bid security will be returned to the unsuccessful Bidders when the award of bid is made.
2.4 Bid security will be returned to the successful Bidder(s) as follows:
2.4.1 For single order bids with specified quantities: upon the delivery of all equipment or merchandise, and upon final acceptance by the Owners.
2.4.2 For all other contracts: upon approval by the Owners of the executed contract and bonds.
2.5 Owners shall have the right to retain the bid security of Bidders to whom an award is being considered until either:
2.5.1 A contract has been executed and bonds have been furnished.
2.5.2 The specified time has elapsed so that the bids may be withdrawn.
2.5.3 All bids have been rejected.
2.6 Bid security will be forfeited to the Owners as full liquidated damages, but not as a penalty, for any of the following reasons, as pertains to this specification document:
2.6.1 If the Bidder fails or refuses to enter into a contract on forms provided by the Owners, and/or if the Bidder fails to provide sufficient bonds or insurance within the time period as established in this specification document.
User Security You agree to take every precaution to ensure the safety, security and integrity of your account and transactions when using Mobile Banking. You agree not to leave your Device unattended while logged into Mobile Banking and to log off immediately at the completion of each access by you. You agree not to provide your username, password or other access information to any unauthorized person. If you permit other persons to use your Device, login information, or other means to access Mobile Banking, you are responsible for any transactions they authorize and we will not be liable for any damages resulting to you. You agree not to use any personally identifiable information when creating shortcuts to your Account. We make no representation that any content or use of Mobile Banking is available for use in locations outside of the United States. Accessing Mobile Banking from locations outside of the United States is at your own risk.
Security Notwithstanding anything herein to the contrary, except for Section 27, to the extent requested by Indemnitee and approved by the Board, the Company may at any time and from time to time provide security to Indemnitee for the Company’s obligations hereunder through an irrevocable bank line of credit, funded trust or other collateral. Any such security, once provided to Indemnitee, may not be revoked or released without the prior written consent of Indemnitee.
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.]
