Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
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.
Additional Access Rights For the avoidance of doubt any grant of Access Rights not covered by the Grant Agreement or this Consortium Agreement shall be at the absolute discretion of the owning Party and subject to such terms and conditions as may be agreed between the owning and receiving Parties.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.
Site Access Dell requires the right to access the APEX System in a timely way and as provided in the Service Offering Description to provide the Support Services. Failure to ensure that Customer provides Dell with timely access to a Site will relieve Dell of the Support Services obligations and Dell may also, at Dell’s discretion, suspend the APEX Service.
DOES THE SPR NEED TO BE UPDATED IF INFORMATION CHANGES Yes. It remains a continuing obligation of the principal or his/her authorized agent to update the SPR whenever any of the information provided on the initial form changes. The SPR needs to be filed with the County Department or County Division processing the application or matter. If and when an additional expenditure is incurred subsequent to the initial filing of the SPR, an amended SPR needs to be filed with the County Department or County Division where the original application, including the initial SPR, was filed. In most cases, the initial SPR needs to be filed with the other application forms. The SPR and any update must be filed with the appropriate County Department or County Division not less than seven (7) days prior to the BCC hearing date so that they may be incorporated into the BCC agenda packet. (See Section 2-354(b), Orange County Code.) When the matter is a discussion agenda item or is the subject of a public hearing, and any additional expenditure occurs less than 7 days prior to BCC meeting date or updated information is not included in the BCC agenda packet, the principal or his/her authorized agent is obligated to verbally present the updated information to the BCC when the agenda item is heard or the public hearing is held. When the matter is a consent agenda item and an update has not been made at least 7 days prior to the BCC meeting or the update is not included in the BCC agenda packet, the item will be pulled from the consent agenda to be considered at a future meeting.
Shareholder Account Maintenance (a) Maintain all shareholder records for each account in the Company. (b) Issue customer statements on scheduled cycle, providing duplicate second and third party copies if required. (c) Record shareholder account information changes. (d) Maintain account documentation files for each shareholder.
Access to PHI Business Associate shall provide access to PHI in a Designated Record Set to Covered Entity or as directed by Covered Entity to an Individual to meet the requirements under 45 CFR § 164.524. Business Associate shall provide such access in the time and manner reasonably designated by Covered Entity. Within three (3) business days, Business Associate shall forward to Covered Entity for handling any request for access to PHI that Business Associate directly receives from an Individual.
Distribution and Pool Performance Information Item 1121(a) - Distribution and Pool Performance Information