Utility Services Company agrees to pay the full cost and expense associated with its use of all utilities, including but not limited to water, sanitary sewer, electric, storm drainage, and telecommunication services.
Infertility Services This plan covers the following services, in accordance with R.I. General Law §27-20-20. • Services for the diagnosis and treatment of infertility if you are:
Verizon Retail Telecommunications Service Any Telecommunications Service that Verizon provides at retail to subscribers that are not Telecommunications Carriers. The term “Verizon Retail Telecommunications Service” does not include any Exchange Access service (as defined in Section 3(16) of the Act, 47 U.S.C. § 153(16)) provided by Verizon.
Local Utility Services XOOM is an independent retail marketer of natural gas and is not affiliated with your local utility. Your local utility will continue to deliver your natural gas, read your meter, send your bill, and make necessary repairs. Your local utility will also respond to emergencies and provide other basic utility services as required. XOOM is not an agent of your local utility and your utility will not be liable for any of XOOM’s acts, omissions, or representations.
AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.
Network Resource Interconnection Service (check if selected)
Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.
Surgery Services This plan covers surgery services to treat a disease or injury when: • the operation is not experimental or investigational, or cosmetic in nature; • the operation is being performed at the appropriate place of service; and • the physician is licensed to perform the surgery. Preauthorization may be required for certain surgical services. Reconstructive Surgery for a Functional Deformity or Impairment This plan covers reconstructive surgery and procedures when the services are performed to relieve pain, or to correct or improve bodily function that is impaired as a result of: • a birth defect; • an accidental injury; • a disease; or • a previous covered surgical procedure. Functional indications for surgical correction do not include psychological, psychiatric or emotional reasons. This plan covers the procedures listed below to treat functional impairments. • abdominal wall surgery including panniculectomy (other than an abdominoplasty); • blepharoplasty and ptosis repair; • gastric bypass or gastric banding; • nasal reconstruction and septorhinoplasty; • orthognathic surgery including mandibular and maxillary osteotomy; • reduction mammoplasty; • removal of breast implants; • removal or treatment of proliferative vascular lesions and hemangiomas; • treatment of varicose veins; or • gynecomastia. Preauthorization may be required for these services.
Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.
