Pipelines Canada Sample Clauses

Pipelines Canada. Pe Ben Industries Company Ltd. Pentzien Canada, Inc. Premay Pipeline Hauling Ltd. RPA Contracting Ltd.
AutoNDA by SimpleDocs
Pipelines Canada. Pe Ben Industries Company Ltd. Pentzien Canada, Inc.
Pipelines Canada. Pe Ben Industries Company Ltd. Pentzien Canada, Inc. Permanent Concrete Premay Pipeline Hauling Ltd. ROK Pipeline Inc. RPA Contracting Ltd. Xxxxxx X. Xxxxxxxxxx (Div. of Xxxxxx XxXxxxxx Ltd.) Subcor Inc. Summit Pipeline Services Ltd. Supernal Welding and Consulting Ltd. True Test Pipeline Services X.X. Xxxxxxxxx Company Limited Universal Pipeline Enterprises Ltd. Waschuk Pipe Line Construction Ltd. 2007/2010 - 52 - MAST-D 0000 - 00xx Xxxxxx X.X., Xxxxxxxxxx, XX 00000 202.429.9100 Fx: 202.429.0316 0000 - 00xx Xxxxxx X.X., Xxxxxxxxxx, XX 00000 202.429.9100 Fx: 202.429.0316 74 X’Xxxxx Ave., St. John’s, NL X0X 0X0 709.738.1750 Fx: 709.738.1760 E: xxxxx@xxxxxxxxxx.xxx XXXXX XXXXX XX Xxx 00000 Xx. Xxxxx Xx., Port Xxxxx, XX V3H 2C0 604.934.4863 F: 604.936.3165 E: xxxx.xxxxxx@xxxxx.xxx XXXX XxXXXXXX #000 - 00 Xxxxxxxxx Xxxx, Xx. Xxxxxx, XX X0X 0X0 780.418.2775 Fx: 780.418.2776 E: xxxxxxxxx@xxxx.xxx XXXX XXXXX 00000 Xxxxxx Xxxxx RR#4, Thamesford, ON N0M 2M0 519.461.0677 Fx: 519.461.0978 E: xxxxxx@xxxxxxxx.xxx XXXX-XXXX. XXXXX 0000 Xxxxxx Xxx-Xxxxx, Ville Ste-Xxxxx, QC J3E 1Y2 514.326.9412 Fx: 514.326.9417 E: xxxx0@xxxxxxxxx.xx XXX XXXXXXXX 00 Xxxxx Xxx Xxxx Xxxx., Xxxxxxxxxxxxx, XX X0X 0X0 902.569.5063 Fx: 902.569.2865 E: xxxxxxxxxxx@xxxxxxxxxxxxx.xxx 2007/2010 - 53 - MAST-D XXXX XXXXXXX, Business Manager 0000 Xxxxxx Xxx., Xxxxxxx, XX X0X 0X0 604.291.8831 Fx: 604.473.5235 E:xxxxxxxx@xxxx000.xxx XXX XxxXXXXXX, Business Manager 00000 - 000 Xxxxxx, Xxxxxxxx, XX X0X 0X0 780.483.0955 Fx: 780.483.1998 E:xxxxxxxxxx@xxxx000.xxx XXXXX XXXXXXX, Business Manager 0000 Xxxxxxx Xxxxx, Xxxxxxxxx, XX X0X 0X0 306.665.7718 Fx: 306.665.0998 E:xxxx000@xxxxxxx.xxx XXX XXXXXX, Business Manager 0000 Xxxx Xx., Xxxxxxxx, XX X0X 0X0 204.786.8658 Fx: 204.786.6578 E:xxxxxxx@xx000.xx.xx XXXXXXX XXXXXXXXX, Business Manager 000 Xxxxxx Xxxx, Oakville, ON L6L 6X8 905.469.9299 Fx: 905.469.3007 E:xxxxxxxxxx@xxxx000.xxx XXX XXXXXXXXXX, Business Manager 000 Xxxxxxxx Xxx., Dartmouth, NS B3B 2A9 902.865.8844 Fx: 902.864.0676 E:xxxxx000@xx.xxxxxxxxxx.xx 0000/0000 - 00 - XXXX-X XXXXX XXXXXXXXXX, Business Manager 000 Xxxx Xxxxxx X., Xxxxx Xxxx, NB E2L 4E3 506.635.1110 Fx: 506.635.1656 E:xxxx000@xxxxx.xx.xx XXXX XXXXXXX, Business Manager #000 - 00 Xxxxxxxxxxxx Xxx., Xx. Xxxxx, XX X0X 0X0 709.747.9040 Fx: 709.747.6760 E:xxxxx@xxxx000.xxx XXXXX XXXXXXXX, Business Manager 000 Xxxxxxxxx Xxxxx, Charlottetown, PE C1A 8K4 902.892.3662 Fx: 902.892.4286 0000/0000 - 00 - XXXX-X

Related to Pipelines Canada

  • Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.

  • Transportation Services i) In the event that transportation services for a student served by CONTRACTOR pursuant to an Individual Services Agreement are to be provided by a party other than CONTRACTOR or the LEA or its transportation providers, such services shall be reflected in a separate agreement signed by the parties hereto, and provided to the LEA and SELPA Director by the CONTRACTOR. Except as provided below, CONTRACTOR shall compensate the transportation provider directly for such services, and shall charge the LEA for such services at the actual and reasonable rates billed by the transportation provider, plus a ten percent (.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • Logistics The Client shall arrange their own transportation and accommodation, unless Client and Performer agree otherwise. If requested, the Performer shall arrange transport within Ostrava, and provide accommodation in a hotel.

  • Food Services The School District will provide for all applicable Student meals as required by State and Federal law and School District rules and procedures as applicable when students attend a College site. Students may purchase food from College food service facilities when on the College campus.

  • TRANSPORT SERVICES Upon the conclusion of such multilateral negotiations, the Parties shall conduct a review for the purpose of discussing appropriate amendments to this Agreement so as to incorporate the results of such multilateral negotiations.

  • Interconnection Customer’s Interconnection Facilities The Interconnection Customer shall design, procure, construct, install, own and/or control the Interconnection Customer’s Interconnection Facilities described in Appendix A at its sole expense.

  • Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!