Terminal Infrastructure Charge (TIC Sample Clauses

The Terminal Infrastructure Charge (TIC) clause establishes a specific fee that is levied to cover the costs associated with the use, maintenance, or development of terminal infrastructure at a port or similar facility. This charge typically applies to shipping lines, cargo owners, or other users of the terminal, and is often calculated based on the volume or type of cargo handled. By clearly defining the TIC, the clause ensures that the financial responsibility for infrastructure upkeep is allocated transparently, helping to fund necessary improvements and maintain operational standards at the terminal.
Terminal Infrastructure Charge (TIC. The Initial TIC for the Terminal Component for the Financial Year commencing on the Effective Date, being a charge per tonne of Annual Contract Tonnage for the Terminal Component, is $[insert amount agreed between DBCTM and User or determined by the arbitrator in the event the Initial TIC is referred to arbitration under the Access Undertaking].
View SourceView Similar (5)
Terminal Infrastructure Charge (TIC. (a) Where no Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge (TIC) for that Financial Year, being a charge per tonne of Annual Contract Tonnage, will be calculated as follows:- where:- (b) Where a Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge per tonne of Annual Contract Tonnage to apply for each period "i" in that Financial Year (TICi) shall be calculated as follows:- where:-
View SourceView Similar (5)
Terminal Infrastructure Charge (TIC. (a) Where no Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge (TIC) in respect of a Terminal Component for that Financial Year, being a charge per tonne of Annual Contract Tonnage for the Terminal Component , will be calculated as follows:- where:- RC is the relevant Revenue Cap; and ART is the relevant Aggregate Reference Tonnage. (b) Where a Review Event occurs after 1 July in a Financial Year, the relevant Terminal Infrastructure Charge per tonne of Annual Contract Tonnage to apply for each period "i" in that Financial Year (TICi) shall be calculated as follows:- TIC = RCi where:- RCi is the relevant portion of the Revenue Cap to apply for period "i" to the Terminal Component in the Financial Year; and ARTi is the relevant portion of the Aggregate Reference Tonnage applying to the relevant period "i" to the Terminal Component in the Financial Year.
View SourceView Similar (3)
Terminal Infrastructure Charge (TIC. (a) Where no Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge (TIC) in respect of a Terminal Component for that Financial Year, being a charge per tonne of Annual Contract Tonnage for the Terminal Component , will be calculated as follows:- where:- (b) Where a Review Event occurs after 1 July in a Financial Year, the relevant Terminal Infrastructure Charge per tonne of Annual Contract Tonnage to apply for each period "i" in that Financial Year (TICi) shall be calculated as follows:- RCi where:- RCi is the relevant portion of the Revenue Cap to apply for period "i" to the Terminal Component in the Financial Year; and ARTi is the relevant portion of the Aggregate Reference Tonnage applying to the relevant period "i" to the Terminal Component in the Financial Year.
View SourceView Similar (3)
Terminal Infrastructure Charge (TIC. (a) Where no Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge (TIC) for that Financial Year, being a charge per tonne of Annual Contract Tonnage, will be calculated as follows:- where:- (b) Where a Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge per tonne of Annual Contract Tonnage to apply for each period "i" in that Financial Year (TICi) shall be calculated as follows:- RCi where:- RCi is the relevant portion of the Revenue Cap to apply for period "i" in the Financial Year; and ARTi is the relevant portion of the Aggregate Reference Tonnage applying to the relevant period "i" in the Financial Year.
View SourceView Similar (2)
Terminal Infrastructure Charge (TIC. The Initial TIC for the Terminal Component for the Financial Year commencing on the Effective Date, being a charge per tonne of Annual Contract Tonnage for the Terminal Component, is $[insert amount agreed between DBIM and User or determined by the arbitrator in the event the Initial TIC is referred to arbitration under the Access Undertaking]. The TIC will be amended and adjusted annually and on the occurrence of a Review Event in accordance with Section 11 and Schedule C of the Access Undertaking.¶ DBCT Management will notify the User of any amendment or adjustment to the TIC in accordance with Schedule C of the Access Undertaking. ¶ Any amendment to the TIC will be effective from the date specified in the Access Undertaking.¶
View Source
Terminal Infrastructure Charge (TIC. Where no Review Event occurs after 1 July in a Financial Year, the Terminal Infrastructure Charge (TIC) in respect of a Terminal Component for that Financial Year, being a charge per tonne of Annual Contract Tonnage for the Terminal Component, will be calculated as follows:- where:- RC is the relevant Revenue Cap; and ART is the relevant Aggregate Reference Tonnage. Where a Review Event occurs after 1 July in a Financial Year, the relevant Terminal Infrastructure Charge per tonne of Annual Contract Tonnage to apply for each period "i" in that Financial Year (TICi) shall be calculated as follows:- where:- RCi is the relevant portion of the Revenue Cap to apply for period "i" in the Financial Year to the Terminal Component; and ARTi is the relevant portion of the Aggregate Reference Tonnage applying to the relevant period "i" to the Terminal Component in the Financial Year. The ARR that will apply in each Financial Year be calculated based on: the ARR and principles set out by the QCA in its Final Decision on the ▇▇▇▇▇▇▇▇▇ Bay Coal Terminal Draft Access Undertaking dated [insert] (as amended by the QCA prior to the Commencement Date, if so amended); any amendment to the Access Undertaking or, the relevant ARR, Revenue Cap or Reference Tariff made pursuant to section 6(a); and any amendment to the ARR required to reflect the fees charged to DBCT Management by the QCA in respect of that or any prior period after 1 July 2010 (to the extent not previously recovered) pursuant to the Queensland Competition Authority Regulation 2007 in providing regulatory services in connection with the Terminal. An amendment under this sub-clause (3) may be submitted to the QCA at the same time as the relevant ARR under sub-section (c) below, or as a later amendment to the relevant ARR during the relevant Financial Year. By each 15 May after the Commencement Date, DBCT Management, after consultation with Access Holders, will submit the each relevant ARR to apply for the next Financial Year to the QCA for approval. The Each TIC will be amended annually on 1 July to reflect the new relevant ARR approved by the QCA and any variation to reflect the relevant Increment, the Aggregate Reference Tonnage and the Notional Contract Tonnage applicable for that Financial Year. Any amendment made pursuant to section 5(j) above will be effective from the relevant 1 July. If a Review Event occurs, and where described in section 12.5(o) of the Access Undertaking, after consultation with the User,...
View Source

Related to Terminal Infrastructure Charge (TIC

  • 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 Onvoy’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 use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL 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 Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. 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.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’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 Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ 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 ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as 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

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Critical Infrastructure Subcontracts For purposes of this Paragraph, the designated countries are China, Iran, North Korea, Russia, and any countries lawfully designated by the Governor as a threat to critical infrastructure. Pursuant to Section 113.002 of the Business and Commerce Code, Contractor shall not enter into a subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business and Commerce Code, in this state, other than access specifically allowed for product warranty and support purposes to any subcontractor unless (i) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is majority owned or controlled by citizens or governmental entities of a designated country; and (ii) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is headquartered in a designated country. Contractor will notify the System Agency before entering into any subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business & Commerce Code, in this state.

  • Infrastructure Modification of the location and/or sizing of the infrastructure for the Project that does not materially change the functionality of the infrastructure.