Galaxy Repository (GR) Access. The use of the Galaxy Repository (GR) Access interface and associated. DLLs by a Non-AVEVA client application is restricted to the physical device where the AVEVA Development Studio License is located.
Galaxy Repository (GR) Access Sample Clauses
Related to Galaxy Repository (GR) Access
Account Access Electronic Check Transactions may only be made from your checking account.
CUSTOMER SERVICE ACCESS The Competitive Supplier agrees to provide, or cause to be provided, certain customer services to Participating Consumers. Such services shall be reasonably accessible to all Participating Consumers, shall be available during normal working hours, shall allow Participating Consumers to transact business they may have with the Competitive Supplier, and shall serve as a communications liaison among the Competitive Supplier, the Town, and the Local Distributor. A toll-free telephone number will be established by Competitive Supplier and be available for Participating Consumers to contact Competitive Supplier during normal business hours (9:00 A.M. - 5:00 P.M. Eastern Standard Time, Monday through Friday) to resolve concerns, answer questions and transact business with respect to the service received from Competitive Supplier. The Town will post program-related information on the Town’s website which will be available to Participating Consumers for general information, product and service information, and other purposes.
Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.
ICANN Access Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC.
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16
Switched Exchange Access Service The offering of transmission and switching services for the purpose of the origination or termination of Toll Traffic. Switched Exchange Access Services include but may not be limited to: Feature Group A, Feature Group B, Feature Group D, 700 access, 800 access, 888 access and 900 access.
User Access Transfer Agent shall have a process to promptly disable access to Fund Data by any Transfer Agent personnel who no longer requires such access. Transfer Agent will also promptly remove access of Fund personnel upon receipt of notification from Fund.
Customer Access The Customer is responsible for the access to the Cloud Services and is responsible for maintaining the confidentiality of its access methods such as usernames and passwords and agrees to notify the Supplier via the Cloud Services support channel if a password is compromised. The Customer is responsible for all activities that occur under its Account.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.
