Provisioning 2.4.1 BellSouth shall provision services during its regular working hours. To the extent OneTone requests provisioning of service to be performed outside BellSouth’s regular working hours, or the work so requested requires BellSouth’s technicians or project managers to work outside of regular working hours, overtime charges set forth in BellSouth’s intrastate Access Services Tariff, Section E13.2, shall apply. Notwithstanding the foregoing, if such work is performed outside of regular working hours by a BellSouth technician or project manager during his or her scheduled shift and BellSouth does not incur any overtime charges in performing the work on behalf of OneTone, BellSouth will not assess OneTone additional charges beyond the rates and charges specified in this Agreement.
2.4.2 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by OneTone (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx OneTone for each additional dispatch required to provision the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Maintenance of Service rates from BellSouth’s XXX Xx. 0 Xxxxxx, Xxxxxxx 13.3.1.
Provisioning Line Splitting and Splitter Space 3.8.1 The Data LEC, Voice CLEC or BellSouth may provide the splitter. When CCI or its authorized agent owns the splitter, Line Splitting requires the following: a non- designed analog loop from the serving wire center to the network interface device (NID) at the end user’s location; a collocation cross connection connecting the loop to the collocation space; a second collocation cross connection from the collocation space connected to a voice port; the high frequency spectrum line activation, and a splitter. The loop and port cannot be a loop and port combination (i.e. UNE-P), but must be individual stand-alone network elements. When BellSouth owns the splitter, Line Splitting requires the following: a non designed analog loop from the serving wire center to the network interface device (NID) at the end user’s location with CFA and splitter port assignments, and a collocation cross connection from the collocation space connected to a voice port.
3.8.2 An unloaded 2-wire copper loop must serve the end user. The meet point for the Voice CLEC and the Data LEC is the point of termination on the MDF for the Data LEC's cable and pairs.
3.8.3 The foregoing procedures are applicable to migration to Line Splitting Service from a UNE-P arrangement, BellSouth Retail Voice Service, BellSouth High Frequency Spectrum (CO Based) Line Sharing.
3.8.4 For other migration scenarios to line splitting, BellSouth will work cooperatively with CLECs to develop methods and procedures to develop a process whereby a Voice CLEC and a Data LEC may provide services over the same loop.
Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection.
1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.
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:
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 a 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.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Extended Local Calling Scope Arrangement An arrangement that provides a Customer a local calling scope (Extended Area Service, “EAS”), outside of the Customer’s basic exchange serving area.
Preventive Care and Early Detection Services This plan covers, early detection services, preventive care services, and immunizations or vaccinations in accordance with state and federal law, including the Affordable Care Act (ACA), as set forth below and in accordance with the guidelines of the following resources: • services that have an A or B rating in the current recommendations of the U.S. Preventative Services Task Force (USPSTF); • immunizations recommended by the Advisory Committee on Immunization Practices of the Centers for Disease Control and Prevention; • preventive care and screenings for infants, children, and adolescents as outlined in the comprehensive guidelines supported by the Health Resources and Services Administration (HRSA); or • preventive care and screenings for women as outlined in the comprehensive guidelines as supported by HRSA. Covered early detection services, preventive care services and adult and pediatric immunizations or vaccinations are based on the most currently available guidelines and are subject to change. The amount you pay for preventive services will be different from the amount you pay for diagnostic procedures and non-preventive services. See the Summary of Medical Benefits and the Summary of Pharmacy Benefits for more information about the amount you pay. This plan covers the following preventive office visits. • Annual preventive visit - one (1) routine physical examination per plan year per • Pediatric preventive office and clinic visits from birth to 35 months - 11 visits; • Well Woman annual preventive visit - one (1) routine gynecological examination per plan year per female member.
Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.
Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.
