Non-Specific Tasks Sample Clauses

Non-Specific Tasks. 1. The Second Party may be asked to perform miscellaneous activities as directed by the Contract Administrator using Second Party’s staff on shift. These activities may include but are not limited to preparing space for new tenants or cleaning an area after the space has been vacated. Should a task require additional staff or equipment then pricing submitted on the Second Party’s Bid Sheet shall be used for calculating such service. End of Section
AutoNDA by SimpleDocs

Related to Non-Specific Tasks

  • Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Product Specific Terms these terms apply to specific Products referenced in this section.

  • CLOUD SPECIFIC TERMS AND CONDITIONS To the extent that Contractor has received an award for Lot 3, Cloud, the following terms and conditions apply to Lot 3, Cloud. For the duration of an Authorized User Agreement, the Cloud Solution shall conform to the Cloud Solution Manufacturer’s specifications, Documentation, performance standards (including applicable license duration, warranties, guarantees, Service Level Agreements, service commitments, and credits). PROTECTION OF DATA, INFRASTRUCTURE AND SOFTWARE Contractor is responsible for providing physical and logical security for all Data, infrastructure (e.g. hardware, networking components, physical devices), and software related to the services the Contractor is providing under the Authorized User Agreement. All Data security provisions agreed to by the Authorized User and Contractor within the Authorized User Agreement may not be diminished for the duration of the Authorized User Agreement without prior written agreement by the parties amending the Authorized User Agreement.

  • Definitions Specific to Special Terms The words and phrases listed below, as used in this Contract, shall each have the following definitions:

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • Classification Specifications The Employer agrees to supply the President of the Union or his/her designate with the classification specifications for those classifications in the Bargaining Unit.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Core Profession Specific 3.1.1 Develop, implement and review communication strategies, tools and guidelines Profession-specific services, as listed in the National Board’s regulatory plan and annual budget.

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