Dewatering (a) Where the whole of a site is so affected by surface water following a period of rain that all productive work is suspended by agreement of the Parties, then dewatering shall proceed as above with Employees so engaged being paid at penalty rates as is the case for safety rectification work. This work is typically performed by Employees engaged within CW1, CW2 or CW3 classifications. When other Employees are undertaking productive work in an area or areas not so affected then dewatering will only attract single time rates. (b) Where a part of a site is affected by surface water following a period of rain, thus rendering some areas unsafe for productive work, consistent with the Employer’s obligations under the OH&S Act, appropriate Employees shall assist in the tidying up of their own work site or area if it is so affected. Where required, appropriate Employees will be provided with the appropriate PPE. Such work to be paid at single time rates. Productive work will continue in areas not so affected. (c) To avoid any confusion any ‘dewatering’ time which prevents an Employee from being engaged in their normal productive work is not included in any calculation for the purposes of determining whether an Employee is entitled to go home due to wet weather (refer clauses 32.4 and 32.5)
Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.
Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, 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 Ymax, 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, Ymax 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, Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Ymax and Verizon. Ymax’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 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 Xxxx 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 (3) consecutive calendar traffic study months. 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’s performance in connection with these Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.
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:
Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.
Stormwater Management a) The Owner AGREES to implement the requirements incorporated in the Draft Plan Conditions attached as Schedule “F” and any reports submitted to Kawartha Region Conservation Authority and the City pertaining to: i) pre and post development run-off flows and water balance calculations, and the intended means of conveying stormwater flow from each Lot, Block and the entire proposed Plan of Subdivision; ii) the anticipated impact of the Plan of Subdivision on water quality and phosphorus control, as it relates to fish and fish habitat once adequate protective measures have been taken; iii) the means whereby erosion and sedimentation and their effects will be minimized on the site during and after construction; iv) the site soil conditions, including grain size distribution profiles; v) a site grading plan. b) The Owner AGREES to erect and maintain all stormwater management and erosion and sedimentation control structures operating and in good repair during the construction period, in a manner satisfactory to Kawartha Region Conservation Authority and the City. c) Prior to the execution of this Agreement, the Owner AGREES to confirm to the City that Conservation Authority has reviewed and approved the stormwater management report and plan, erosion and sedimentation plan, and final Lot Grading Plans as required under this Section. a) UPGRADES TO EXISTING STORM SEWER b) UPGRADES TO EXISTING SANITARY SEWER
Purpose of Interconnection Facilities Except as may be required by Applicable Laws and Regulations, or as otherwise agreed to among the Parties, the Interconnection Facilities shall be constructed for the sole purpose of interconnecting the Large Generating Facility to the Participating TO’s Transmission System and shall be used for no other purpose.
Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:
Interconnection Facilities 4.1.1 The Interconnection Customer shall pay for the cost of the Interconnection Facilities itemized in Attachment 2 of this Agreement. The NYISO, in consultation with the Connecting Transmission Owner, shall provide a best estimate cost, including overheads, for the purchase and construction of its Interconnection Facilities and provide a detailed itemization of such costs. Costs associated with Interconnection Facilities may be shared with other entities that may benefit from such facilities by agreement of the Interconnection Customer, such other entities, the NYISO, and the Connecting Transmission Owner. 4.1.2 The Interconnection Customer shall be responsible for its share of all reasonable expenses, including overheads, associated with (1) owning, operating, maintaining, repairing, and replacing its own Interconnection Facilities, and