APPLICATION SPECIFIC CONTROLLERS Sample Clauses

APPLICATION SPECIFIC CONTROLLERS. A. Application Specific Controllers shall be stand-alone, microprocessor based Direct Digital Controllers with sufficient EEPROM memory to handle its operating system, database and programming requirements. The controllers shall be clearly labeled as to controller type, where it is to be installed, and software address (if applicable). The controller shall be fully tested upon installation to ensure that it is properly matched to the equipment it is controlling. B. The controller shall communicate with other devices on the communication network and be fully integrated with the other system components. C. The hardware shall be suitable for the anticipated ambient conditions. 1. Controllers used outdoors and/or in wet ambient shall be mounted within waterproof enclosures, and shall be rated for operation at --40°F to 155°F. 2. Controller used in conditioned ambient shall be mounted in dust-proof enclosures, and shall be rated for operation at 32°F to 120°F. D. Terminal Unit Controllers
AutoNDA by SimpleDocs

Related to APPLICATION SPECIFIC CONTROLLERS

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

  • State Specific Contract Form Observe the state of the Seller on the Contract, if the Seller lists an address in Alaska, Arkansas, Delaware, North Carolina, Virginia, Maryland, Montana, Connecticut, Vermont, Louisiana or Mississippi, confirm the form number on the Contract is on the List of Approved Contract Forms, for the corresponding state.

  • Other Controller Audit Any other Controller may audit SAP’s control environment and security practices relevant to Personal Data processed by SAP in line with Section 5.1 only if any of the cases set out in Section 5.1 applies to such other Controller. Such audit must be undertaken through and by Customer as set out in Section 5.1 unless the audit must be undertaken by the other Controller itself under Data Protection Law. If several Controllers whose Personal Data is processed by SAP on the basis of the Agreement require an audit, Customer shall use all reasonable means to combine the audits and to avoid multiple audits.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Escrow Format Specification 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.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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