For the Contractor Name: Xxxxx Xxxx Phone: 000-000-0000 Email: xxxxx@xxxxxxxxxxxxxxx.xxx
The Contractor must 16.1.1. treat all Authority Protected Information as confidential and safeguard it accordingly, implementing appropriate technical and organisational measures to protect Authority Protected Information against disclosure; 16.1.2. only use the Authority Protected Information for the purposes of performing its obligations under the Framework Agreement; 16.1.3. only disclose the Authority Protected Information to such Contractor Representatives that are directly involved in the performance of the Framework Agreement and need to know the information; and 16.1.4. not disclose any Authority Protected Information without the prior written consent of the Authority.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
The Contractor A general contractor shall be retained by Tenant to construct the Improvements. Such general contractor (“Contractor”) shall be selected by Tenant from a list of general contractors supplied by Landlord, and Tenant shall deliver to Landlord notice of its selection of the Contractor upon such selection.
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
SCOPE OF THE CONTRACT The Contractor shall perform the Services set out [in Schedule 1] [below2] in accordance with the Contract. [The Contractor’s key personnel assigned to perform the Services are: [provide a list] During the provision of the Services, if substitution of Contractor’s [key personnel] [experts] is necessary, the Contractor shall propose other experts or at least the same level of qualifications for approval by the Fund. [The Contractor shall obtain the Fund’s prior approval in writing before entering into a subcontract for engaging a subconsultant for the performance of any part of the Services.]
Contractor’s Contract Manager The Contractor’s Contract Manager, who is primarily responsible for the Contractor’s oversight of the Contract performance, will be identified in a separate writing to the Department upon Contract signing in the following format: Contractor’s Contract Manager Name Contractor’s Name Contractor’s Physical Address Contractor’s Telephone # Contractor’s Email Address If the Contractor changes its Contract Manager, the Contractor will notify the Department. Such a change does not require an amendment to the Contract.
INDEPENDENT CAPACITY OF THE CONTRACTOR The parties intend that an independent contractor relationship will be created by this contract. The CONTRACTOR and his or her employees or agents performing under this contract are not employees or agents of the AGENCY. The CONTRACTOR will not hold himself/herself out as or claim to be an officer or employee of the AGENCY or of the State of Washington by reason hereof, nor will the CONTRACTOR make any claim of right, privilege or benefit that would accrue to such employee under law. Conduct and control of the work will be solely with the CONTRACTOR.
ADMINISTRATION OF THE CONTRACT 2.2.1 The Architect will provide administration of the Contract as hereinafter described. 2.2.2 The Architect will be the State's representative during construction and until final payment is due. The Architect will advise and consult with the State. The State's instructions to the Contractor shall be forwarded through the Architect. The Architect will have authority to act on behalf of the State only to the extent provided in the Contract Documents, unless otherwise modified by written instrument in accordance with Subparagraph 2.2.10. 2.2.3 The Architect will visit the site at intervals appropriate to the stage of construction to familiarize himself or herself generally with the progress and quality of the Work and to determine in general if the Work is proceeding in accordance with the Contract Documents. However, the Architect will not be required to make exhaustive or continuous on-site inspections to check the quality or quantity of the Work. On the basis of his or her on-site observations as an architect, he or she will keep the State informed of the progress of the Work, and will endeavor to guard the State against defects and deficiencies in the Work of the Contractor. 2.2.4 The Architect will not be responsible for and will not have control or charge of construction means, methods, techniques, sequences or procedures, or for safety precautions and programs in connection with the Work, and he or she will not be responsible for the Contractor's failure to carry out the Work in accordance with the Contract Documents. The Architect will not be responsible for or have control or charge over the acts or omissions of the Contractor, 2.2.5 The Architect shall at all times have access to the Work wherever it is in preparation and progress. The Contractor shall provide facilities for such access so the Architect may perform his or her functions under the Contract Documents.
Responsibilities of the Contractor The Contractor shall provide all technical and professional expertise, knowledge, management, and other resources required for accomplishing all aspects of the tasks and associated activities identified in the Scope of Work. In the event that the need arises for the Contractor to perform services beyond those stated in the Scope of Work, the Contractor and the City shall negotiate mutually agreeable terms and compensation for completing the additional services.
