Provision of Continence Supplies Sample Clauses

Provision of Continence Supplies a. You must provide continence management products that are of an appropriate standard to meet the assessed needs of each Resident, as set out in the Care Plan.
AutoNDA by SimpleDocs

Related to Provision of Continence Supplies

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Technical and Interconnection Requirements 2.1 Consumer agrees that his Rooftop Solar PV System and Net Metering System will conform to the standards and requirements specified in the Policy, Regulations and Supply Code as amended from time to time.

  • Flow Down Provisions Grantee must include any applicable provisions of the Contract in all subcontracts based on the scope and magnitude of work to be performed by such Subcontractor. Any necessary terms will be modified appropriately to preserve the State's rights under the Contract.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties have agreed to use One-Way Interconnection Trunks for the delivery of traffic from PCS to Verizon, PCS, at PCS’s own expense, shall:

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

  • Regulatory Good Standing Certification - Explanation - Continued If Vendor responded to the prior attribute that "No", Vendor is not in good standing, Vendor must provide an explanation of that lack of good standing here for TIPS consideration. No response

Time is Money Join Law Insider Premium to draft better contracts faster.