Cost and Method of Delivery Sample Clauses

Cost and Method of Delivery. The method and cost of delivery will be subject to agreement between the Parties. 交付成本和方式:交付方式和成本由双方约定。
AutoNDA by SimpleDocs

Related to Cost and Method of Delivery

  • Delivery Points ‌ Project water made available to the Agency pursuant to Article 6 shall be delivered to the Agency by the State at the delivery structures established in accordance with Article 10.

  • Delivery Point (a) All Energy shall be Delivered hereunder by Seller to Buyer at the Delivery Point. Seller shall be responsible for the costs of delivering its Energy to the Delivery Point consistent with all standards and requirements set forth by the FERC, ISO-NE, the Interconnecting Utility and any other applicable Governmental Entity and any applicable tariff.

  • NETWORK INTERCONNECTION METHODS 64.1 This Section sets forth the terms and conditions for Network Interconnection Methods (NIMs) provided between CenturyLink and CLEC for the Interconnection Facilities established between the Parties’ networks. Additionally, this Section describes the physical architecture for the Interconnection of the Parties’ facilities and equipment required for the transmission and routing of Local Traffic, ISP-Bound Traffic, IntraLATA LEC Toll Traffic, VoIP-PSTN Traffic, Transit Traffic and Jointly Provided Switched Access Service Traffic.

  • Project Delivery Contractor shall construct the Project in accordance with the Contract Documents, and Contractor shall deliver the Project completed in accordance with the Contract Documents, substantially free from defects, and within the Contract Time.

  • Service Delivery Grantee shall:

  • Interconnection Points 8.5.1 The IP of a Party (“Receiving Party”) for Measured Internet Traffic delivered to the Receiving Party by the other Party shall be the same as the IP of the Receiving Party for Reciprocal Compensation Traffic under Section 7.1 above.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Signaling Parameters All SS7 signaling parameters will be provided in conjunction with traffic exchange trunk groups, where and as available. These parameters include Automatic Number Identification ("ANI"), Calling Party Number ("CPN"), Privacy Indicator, calling party category information, originating line information, charge number, etc. Also included are all parameters relating to network signaling information, such as Carrier Information Parameter ("CIP"), wherever such information is needed for call routing or billing. GTE will provide SS7 via GR-394-SS7 and/or GR-317-SS7 format(s).

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

Time is Money Join Law Insider Premium to draft better contracts faster.