Security Services CONTRACTOR shall provide security services designed for preventing escapes, maintaining order, providing care, custody, control, supervision and management of the inmate population. A successful security program depends heavily on staff training, effective administration, and the establishment of inmate programs. The organization, staffing, and administration of the security program are vital to the Facility. The direction provided by a well-organized and clearly articulated operations manual, and emergency planning provides a solid base for successful administration. The final operations manual shall be submitted to the Bureau prior to the Service Commencement Date and shall be reviewed annually and updated as needed. Documentation of the review shall be provided annually to the On- Site Contract Monitor. Changes to the plan require written permission by the Contract Manager. The Department reserves the right to require changes to plans submitted to the Bureau.
Security Service Tenant acknowledges and agrees that, while Landlord may patrol the Project, Landlord is not providing any security services with respect to the Premises and that Landlord shall not be liable to Tenant for, and Tenant waives any claim against Landlord with respect to, any loss by theft or any other damage suffered or incurred by Tenant in connection with any unauthorized entry into the Premises or any other breach of security with respect to the Premises.
Party Services The Application may display, include or make available third-party content (including data, information, applications and other products services) or provide links to third-party websites or services. You acknowledge and agree that the Company shall not be responsible for any Third-party Services, including their accuracy, completeness, timeliness, validity, copyright compliance, legality, decency, quality or any other aspect thereof. The Company does not assume and shall not have any liability or responsibility to You or any other person or entity for any Third-party Services. You must comply with applicable Third parties' Terms of agreement when using the Application. Third-party Services and links thereto are provided solely as a convenience to You and You access and use them entirely at your own risk and subject to such third parties' Terms and conditions.
Third Party Services Any services required for or contemplated by the performance of the above-referenced services by the Administrator to be provided by unaffiliated third parties (including independent auditors’ fees and counsel fees) may, if provided for or otherwise contemplated by the Financing Order and if the Issuer deems it necessary or desirable, be arranged by the Issuer or by the Administrator at the direction (which may be general or specific) of the Issuer. Costs and expenses associated with the contracting for such third-party professional services may be paid directly by the Issuer or paid by the Administrator and reimbursed by the Issuer in accordance with Section 2, or otherwise as the Administrator and the Issuer may mutually arrange.
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:
Anesthesia Services This plan covers general and local anesthesia services received from an anesthesiologist when the surgical procedure is a covered healthcare service. This plan covers office visits or office consultations with an anesthesiologist when provided prior to a scheduled covered surgical procedure.
Cloud Services You will not intentionally (a) interfere with other customers’ access to, or use of, the Cloud Service, or with its security; (b) facilitate the attack or disruption of the Cloud Service, including a denial of service attack, unauthorized access, penetration testing, crawling, or distribution of malware (including viruses, trojan horses, worms, time bombs, spyware, adware, and cancelbots); (c) cause an unusual spike or increase in Your use of the Cloud Service that negatively impacts the Cloud Service’s operation; or (d) submit any information that is not contemplated in the applicable Documentation.
Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.
Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.
Pharmacy Services The Contractor shall establish a network of pharmacies. The Contractor or its PBM must provide at least two (2) pharmacy providers within thirty (30) miles or thirty (30) minutes from a member’s residence in each county, as well as at least two (2) durable medical equipment providers in each county or contiguous county.
