Technical prerequisites Sample Clauses

Technical prerequisites. In order to use API-money, the User must necessarily possess up-to-date Equipment to access and use the Partner Website.
Sample 1Sample 2
AutoNDA by SimpleDocs
Technical prerequisites. Any of the following web browsers without a private plugin enabled, company extension or any other modification to the browser.  Chrome Version 52.0.2743 or later  Firefox Version 56.0 or later  Edge 38.14393 or later  Safari on Mac/Iphone (windows is not supported) Internet access  with no particular limit,  and sufficient ADSL connection speed. Compatibility on own networks subject to proxy rules, routing or firewall, for example, are part of our professional services. Our solutions are mobile and tablet responsive.
Sample 1
Technical prerequisites. 11.1. Customer acknowledges that connecting Custo- mer’s Sensors to the AERO Service is a prerequisite for using the AERO Service’s features and functionalities. In order to enable Xovis to carry out an Initial Sensor Con- figuration or a Sensor Re-Configuration at a later stage, Customer shall provide to Xovis exclusive remote access to any such Sensor which is or shall be connected to the AERO Service. Upon the Initial Sensor Configuration or any Sensor Re-Configuration by Xovis, neither Customer nor any other third-party is supposed to access any such Sensors or to change any of its configurations. 11.2. Customer shall ensure in its sphere of influence that all technical pre-requisites, which will allow a proper use of the AERO Service, are met. Customer shall in parti- cular comply with Xovis’ system requirements with regard to the AERO Service as specified in the Service Description in its then-current version. 11.3. Customer is responsible for maintaining its ICT facilities and systems including the Sensors in a fully operative, functional and secure mode and for procuring and maintaining network connections with sufficient band- width to ensure data transmission from Sensors to the AERO Service is and remains established in such manner that the in- and outbound data exchange with the AERO Service is and remains ensured in a sustainable manner. Customer’s Subscription does in no way add or convey a Xovis warranty with regard to Sensors or any other devices or software not purchased or subscribed to under Custo- mer’s AERO Subscription. Customer is responsible for installing and operate Sen- sors according to the applicable Xovis specifications for such Sensors. Unless included in Customer’s service plan or in the backup and restore section of the Service Description, Customer will remain full responsible to back-up and/ or otherwise protect all data against loss, damage, or destruction. 11.4. After Initial Sensor Configuration or a subsequent Sensor Re-Configuration by Xovis, Customer shall not change the then-current mounting location of the relevant Sensor or such Sensor’s location set-up (e.g., mounting object between Sensor and floor, changing entrances etc.) or to negatively affect the configuration and counting abi- lities of the Sensor in whatever manner. Customer must inform Xovis in advance of any plans to physically move Sensors or perform any work that may obstruct Sensors‘ field of view. 11.5. Customer shall use commercially reasonable en...
Sample 1
Technical prerequisites. To allow access to the services, the customer and/or the user shall: - have internet access and/or a 3G or 4G connection.
Sample 1
Technical prerequisites. To be able to participate to the Openstream Monetisation Program, the Publisher has to use the Stream or Podcast URL provided by Openstream.
Sample 1
Technical prerequisites. In the event that TouchStar installs call center systems on behalf of Reseller, Reseller shall provide to TouchStar any and all information on Technical Prerequisites reasonably requested by TouchStar in order to assist TouchStar in the installation of the applicable call center system.
Sample 1
Technical prerequisites. Customer acknowledges that connecting certain of Customer’s sensors to the Xovis Flow Service is a prerequisite for using the Xovis Flow Service’s features and functionalities. In order to enable Xovis to carry out an Initial Sensor Configuration or a Sensor Re-Configuration at a later stage, Customer shall provide to Xovis exclusive remote access to any such sensor which is or shall be connected to the Xovis Flow Service. Upon the Initial Sensor Configuration or any Sensor Re- Configuration by Xovis, neither Customer nor any other third-party is supposed to access any such sensors or to change any of its configurations. Customer shall ensure in its sphere of influence that all technical pre-requisites, which will allow a proper use of the Xovis Flow Service, are met. Customer shall in particular comply with Xovis’ system requirements with regard to the Xovis Flow Service as specified in the Service Description in its then-current version. Customer is responsible for maintaining its ICT facilities and systems including the sensors in a fully operative and functional mode and for procuring and maintaining network connections to ensure data transmission from sensors to the Xovis Flow Service is and remains established in such manner that the in- and outbound data exchange with the Xovis Flow Service is and remains ensured in a sustainable manner. Customer’s Subscription does in no way add or convey a Xovis warranty with regard to sensors or any other devices or software not purchased or subscribed to under Customer’s Subscription. After Initial Sensor Configuration or a subsequent Sensor Re-Configuration by Xovis, Customer shall not change the then-current mounting location of the relevant sensor or such sensor’s location set-up (e.g. mounting object between sensor and floor, changing entrances etc.) or to negatively affect the configuration and counting abilities of the sensor in whatever manner. Customer acknowledges that it is Customer’s sole responsibility to ensure the network connectivity and security of its own ICT facilities and systems, including but not limited to the sensors used and connected with the Xovis Flow Service. Customer shall use commercially reasonable endeavors to ensure that no Malicious Code is being exported or uploaded to the Xovis Flow Service from ICT systems and facilities in Customer’s sphere of influence.
Sample 1
AutoNDA by SimpleDocs

Related to Technical prerequisites

  • Technical Training The CAISO and the Participating TOs shall respond to reasonable requests for support and provide relevant technical training to each other’s employees to support the safe, reliable, and efficient operation of the CAISO Controlled Grid and to comply with any NERC or WECC operator certification or training requirements. Examples of such technical training include, but are not limited to: (1) the theory or operation of new or modified equipment (e.g., control systems, Remedial Action Schemes, protective relays); (2) computer and applicator programs; and (3) CAISO (or Participating TO) requirements. The Parties shall enter into agreements regarding the timing, term, locations, and cost allocation for the training.

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

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

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.

  • Standard Work Week The standard work week for full-time employees covered by this Agreement shall be forty (40) hours, exclusive of the time allotted for meal periods, consisting of five (5) consecutive work days followed by two (2) consecutive days off. The week shall commence with the shift that includes 12:01 A.M. Sunday of each calendar week and end at the start of the shift that includes 12:00 midnight the following Saturday. The Employer retains the right to modify the work schedules to meet operational needs.

  • Technical Safeguards 1. USAC and DSS will process the data matched and any data created by the match under the immediate supervision and control of authorized personnel to protect the confidentiality of the data, so unauthorized persons cannot retrieve any data by computer, remote terminal, or other means. 2. USAC and DSS will strictly limit authorization to these electronic data areas necessary for the authorized user to perform their official duties. All data in transit will be encrypted using algorithms that meet the requirements of the Federal Information Processing Standard (FIPS) Publication 140-2 or 140-3 (when applicable). 3. Authorized system users will be identified by User ID and password, and individually tracked to safeguard against the unauthorized access and use of the system. System logs of all user actions will be saved, tracked and monitored periodically. 4. USAC will transmit data to DSS via encrypted secure file delivery system. For each request, a response will be sent back to USAC to indicate success or failure of transmission.

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