Document Structure. 2.1 In general, the Agreement will consist of the following documents, whereby in the event of any inconsistency or conflict between or among provisions of the following documents, the contents of the document first listed shall have precedence and shall prevail over the documents listed later, in descending order:
a) The Internet Services Master Agreement (if entered into);
b) The Change Order Form (only in relation to the relevant Order Form);
c) The Order Form/the Order Confirmation;
d) The Services Specification;
e) The Support and Service Level Schedule;
f) The General Conditions; and
g) The LeaseWeb Policies.
2.2 If LeaseWeb has accepted the applicability of Customer’s general conditions in writing, and there is a conflict or inconsistency between any of the provisions of these General Conditions and one or more of the provisions of Customer’s general conditions, the provisions of these General Conditions shall prevail.
2.3 LeaseWeb is entitled to amend the General Conditions, the Services Specification, the Support and Service Level Schedule and the LeaseWeb Policies. Such amendment also applies to existing Orders for Services, unless LeaseWeb states otherwise. The amendments come into effect thirty (30) days after the announcement or on a later date stated in the announcement. The announcement may be made through the Customer Portal and/or the API. If Customer does not wish to accept an amendment that relates to an existing Order, it can terminate the Agreement in relation to that existing Order with effect from the date on which the amendment comes into force. The written cancellation must have been received by LeaseWeb within fourteen (14) days after LeaseWeb’s announcement of the amendments. No such termination rights shall exist if: (a) the amendment is solely for the benefit of the Customer; (b) Customer is offered the option to refuse the amendment; (c) the amendments are required by law; or (d) the amendment does not adversely affect Customer’s use of the Services.
Document Structure. 2.1 In general, the Agreement will consist of the following documents, whereby in the event of any inconsistency or conflict between or among provisions of the following documents, the contents of the document first listed shall have precedence and shall prevail over the documents listed later, in descending order:
a) The Master Services Agreement (if entered into);
b) The Change Order Form (only in relation to the relevant Order Form);
c) The Order Form/the Order Confirmation;
d) Data Processor Agreement (if concluded);
e) The Services Specification;
f) The Support and Service Level Schedule;
g) The General Conditions; and
Document Structure. This document is comprised of the following chapters:
Document Structure. Section 3.0 details the three opportunity analyses. Supporting information for Section 3.0 is contained in the Appendices. Appendix A contains the Minnesota wants and needs definitions, Appendix B contains the Minnesota services definitions, Appendix C contains the demand weight analysis data, and Appendix D contains the demographic analysis data. Section 4.0 details the strength relationship analysis.
Document Structure. This document is structured to capture the key conditions of the agreement in a logical order. It is understood that the agreement may be changed at any time by the mutual consent of both parties using the revision history and approval records contained in the Document Distribution, Approval and Revision History.
Document Structure. The remainder of this report is organised to describe the design of the whole D4Science “system” to the reader through different views each adding more detail to the previous. Section 2 introduces the D4Science Reference Model, i.e. the concepts and relations among them characterising the overall system. Section 3 describes the gCube Reference Architecture, i.
Document Structure. 2.1 The Agreement will consist of the following documents, whereby in case of conflict or inconsistency between these documents, the document first listed shall prevail over the document listed later:
(i) the Order Form(s);
(ii) the Datacenter Services Master Agreement (if concluded);
(iii) the Services Specifications;
(iv) General Conditions; and
(v) the Policies.
2.2 The applicability of purchase terms or other terms and conditions of Customer or third parties is hereby expressly excluded.
2.3 If Evoswitch has accepted the applicability of Customer’s general terms and conditions and there is a discrepancy, conflict, or a dispute by and between any of the provisions of these general conditions and one or more of the provisions of Customer’s general conditions, the provisions of Evoswitch’s General Conditions shall govern and prevail.
2.4 Evoswitch is entitled to issue new versions and thereby amend any of the applicable documents set forth in Clause 2.1. Such amendment also applies to existing Agreement for Services, unless Evoswitch states otherwise formally in writing. The amendments come into effect fourteen (14) days after the announcement or on a later date stated in the announcement. The announcement may be made on Evoswitch’s website and/or through the Customer Portal. If Customer does not wish to accept an amendment that relates to an existing Agreement, the Customer has the right to terminate that Agreement with effect from the date on which the amendment comes into force solely by means of a written formal Notification for termination that must have been received by Xxxxxxxxx within fourteen (14) days after Evoswitch’s announcement of a new version of any of the document, unless (a) the amendment is solely for the benefit of the Customer; (b) the amendments are required by law; or (c) the amendment does not materially and adversely affect Customer’s use of the Services.
Document Structure. This section describes the structure of the document. - Section 1 is this introduction - Section 2 describes the service components - Section 3 define the services terms and conditions of usage
Document Structure. The document is structured as follows:
Document Structure. Following above concept, a set of six evaluation criteria was defined in order to evaluate all use cases. They are presented in chapter
