Functional Elements Clause Samples

The 'Functional Elements' clause defines the specific components, features, or parts of a product, system, or service that are necessary for it to operate as intended. This clause typically outlines which elements must be present and operational, such as software modules, hardware parts, or user interface features, and may specify performance standards or integration requirements. By clearly identifying these essential elements, the clause ensures that both parties understand what is required for the deliverable to be considered complete and functional, thereby reducing ambiguity and potential disputes over whether contractual obligations have been met.
Functional Elements. 3.9.1 All vents, down spouts, electrical conduits, meters, service connections, and other functional elements shall be treated as integral parts of the design. Where appropriate these elements shall be painted to match the colour of the adjacent surface, except where used expressly as an accent. 3.9.2 All mechanical equipment, including rooftop mechanical, exhausts, propane tanks, electrical transformers, and other utilitarian features shall be visually concealed from abutting properties, including municipal rights-of-way, and shall include noise reduction measures.
View SourceView Similar (13)
Functional Elements. All vents, down spouts, flashing, electrical conduits, metres, service connections, and other functional elements shall be treated as integral parts of the design. Where appropriate these elements shall be painted to match the colour of the adjacent surface, except where used expressly as an accent.
View SourceView Similar (8)
Functional Elements. The functional elements of the Two Way TV Engine may be broken down into the following components: • High Level Engine API • Live message Handling • Two Way TV Live Message Protocol • Timing and Synchronisation • Return Path Management • Low Level Abstraction Layer These core components of the Engine offer a common API to the application developer. This API may be in the form of direct function calls or through an event model, depending on target platform. This module provides a standardised API to the application developer. Depending on target platform, this API may be direct function calls, an event model or a combination of the two. In the Reference Architecture, based on an ATVEF compliant receiver, the API is based on a JavaScript event model. The primary purpose of this API is to simplify access to the Two Way TV Engine and the underlying environments API.
View Source
Functional Elements. It is agreed that ADS has specialized information and resources available to the senior and disabled population in Multnomah County, and that it is in the best interest of callers of 211info who are members of this population to have their calls forwarded to the ADS Hotline whenever possible. Consequently, it is agreed that all appropriate aging and disability related questions, including but not limited to • Advocacy • Adult Day Care • Assessment for Services • Caregiver Resources • Financial Assistance • Housing Resources • Insurance Counseling • Legal Assistance • Respite • Transportation • Veterans Services & Benefits will be transferred, or referred, as appropriate, directly from 211 to Helpline during regular business hours, M-F, 8-5. If the call is received after hours, 211 will assist caller as needed, and inform ADS Helpline of any follow up needed the following business day. Additionally, 211 will transfer directly to ADS Helpline 24/7 if the caller indicates a question related to the following areas: • Abuse – seniors or adults with disabilities 18+ • Emergency Food – seniors or adults with disabilities 18 + • Emergency Housing – seniors or adults with disabilities 18 +
View Source

Related to Functional Elements

  • Sub-loop Elements 2.8.1 Where facilities permit, BellSouth shall offer access to its Unbundled Sub-Loop (USL) elements as specified herein.

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).

  • Elements Defines the individual components under each indicator

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation 35.5.1. The charges that CLEC shall pay to Sprint for Collocation are set forth in Table Two of this Agreement. 35.6. Call Related Databases 6.1. The charges that CLEC shall pay to Sprint for Call Related Databases purchased pursuant to Part J are set forth in Table One of this Agreement.