UNIT SCOPE Sample Clauses

UNIT SCOPE. The University recognizes the Union as the exclusive bargaining representative for employees employed in the following classifications whose employment exceeds the lesser of fourteen (14) hours per week or 35% of the normal work week and who are employed more than sixty-seven (67) working days in any calendar year (as specified in the Bureau of Mediation Services Certification Notice, BMS Case No. 93-PCE-1340, dated June 15, 1993), but excluding undergraduate students, managerial, supervisory, and confidential employees and other employees excluded by Minnesota Statutes, (179A.01 - 179A.30).
Sample 1Sample 2Sample 3See All (16)
AutoNDA by SimpleDocs
UNIT SCOPE. The Employer recognizes the Union as the sole and exclusive bargaining representative for all employees of the University of Minnesota employed in the following classifications whose employment exceeds the lesser of fourteen (14) hours per week or thirty-five (35) percent of the normal work week and who are employed more than sixty-seven (67) working days in any calendar year (as specified in the Bureau of Mediation Services Certification Notice, BMS Case No. 81PR-213-A, dated 9/12/80, but excluding students, managerial, supervisory, and confidential employees and other employees excluded by Minnesota Statutes, 179A.01-179A.25).
Sample 1Sample 2Sample 3See All (12)
UNIT SCOPE. The University recognizes the Union as the exclusive bargaining representative for employees employed in the following classifications whose employment exceeds the lesser of fourteen
Sample 1Sample 2Sample 3
UNIT SCOPE. The scope of identifiers declared in the interface section of a unit follows the rules of block scope and extends over all clients of the unit. In other words, programs or units containing uses clauses have access to the identifiers belonging to the interface parts of the units in those uses clauses. Each unit in a uses clause imposes a new scope that encloses the remaining units used and the program or unit containing the uses clause. The first unit in a uses clause represents the outermost scope, and the last unit represents the innermost scope. This implies that if two or more units declare the same identifier, an unqualified reference to the identifier selects the instance declared by the last unit in the uses clause. If you use a qualified identifier (a unit identifier, followed by a period, followed by the identifier), every instance of the identifier can be selected. The identifiers of Object Pascal’s predefined constants, types, variables, procedures, and functions act as if they were declared in a block enclosing all used units and the entire program. In fact, these standard objects are defined in a unit called System, which is used by any program or unit before the units named in the uses clause. This means that any unit or program can redeclare the standard identifiers, but a specific reference can still be made through a qualified identifier, for example, System.Integer or System.Writeln. C h a p t e r‌ Procedures and functions let you nest additional blocks in the main program block. Each procedure or function declaration has a heading followed by a block. See Chapter 7, “Blocks, locality, and scope,” for a definition of a block. A procedure is activated by a procedure statement; a function is activated by the evaluation of an expression that contains its call and returns a value to that expression. This chapter discusses the different types of procedure and function declarations and their parameters.
Sample 1Sample 2
UNIT SCOPE. The University recognizes the Union as the exclusive bargaining representative for employees employed in the following classifications whose employment exceeds the lesser of fourteen (14) hours per week or 35% of the normal work week and who are employed more than sixty-seven (67) working days in any calendar year (as specified in the Bureau of Mediation Services Certification Notice, BMS Case No. 93-PCE-1340, dated June 15, 1993), but excluding undergraduate students, managerial, supervisory, and confidential employees and other employees excluded by Minnesota Statutes, 179A.01 - 179A.30). 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4921 4922 4925 4926 4927 4928 4929 4930 4931 4932 4934 4935 4936 4938 4939 4940 4941 4942 4943 4944 4945 4946 4949 4950 4951
Sample 1
UNIT SCOPE. The Employer recognizes the Union as the sole and exclusive bargaining representative for all employees of the University of Minnesota employed in the following classifications whose employment exceeds the lesser of fourteen (14) hours per week or thirty-five
Sample 1
UNIT SCOPE. The Employer recognizes the Union as the sole and exclusive bargaining representative for all full time and regular part time non-professional employees employed by the Employer on the University Campus in Minneapolis, Minnesota; including Clinic Coordinators, Senior Clinic Coordinators and Senior Intake Representative Leads, excluding business office clerical employees, technical employees, professional employees, managers, confidential employees, guards and supervisors as defined in the National Labor Relations Act, and all other employees (the “Bargaining Unit”).
Sample 1
AutoNDA by SimpleDocs
UNIT SCOPE. The University recognizes the Union as the exclusive bargaining representative for employees employed in the following classifications whose employment exceeds the lesser of fourteen (14) hours per week or 35% of the normal work week and who are employed more than sixty-seven (67) working days in any calendar year (as specified in the Bureau of Mediation Services Certification Notice, BMS Case No. 91-PCE-2009 and 2006, dated February 20, 1991), but excluding undergraduate students, managerial, supervisory, and confidential employees and other employees excluded by Minnesota Statutes, 179A.01 - 179A.25). (See Appendix F for the list of the classifications eliminated/slotted into the classifications listed below) Class Number Class Title 1811 Office Support Assistant 1815 Principal Operations/Student Services Specialist 1826 Principal Office and Administrative Specialist 1858 Principal Accounts Specialist 1865 Executive Operations/Student Services Specialist 1885 Executive Office and Administrative Specialist 1888 Executive Accounts Specialist 1897 Program/Project Specialist
Sample 1

Related to UNIT SCOPE

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • CONTRACT SCOPE Pursuant to this Contract, Contractor is authorized to sell and provide only those Goods and/or Services set forth in Exhibit A – Included Goods/Services for the prices set forth in Exhibit B – Prices for Goods/Services. Contractor shall not represent to any Purchaser under this Contract that Contractor has contractual authority to sell or provide any Goods and/or Services beyond those set forth in Exhibit A – Included Goods/Services.

  • Service Scope The following Services are covered by this Agreement; o Manned telephone support o Monitored email support o Remote assistance using Remote Desktop and a Virtual Private Network where available o Planned or Emergency Onsite assistance (extra costs apply) o Monthly system health check

  • Agreement Scope The scope of this Agreement is as prescribed in section 46 of the Act, setting out: • the health services to be provided to the State by the HSP, • the TTR in support of the health services to be provided, • the funding to be provided to the HSP for the provision of the health services, including the way in which the funding is to be provided, • the performance measures and operational targets for the provision of the health services by the HSP, • how the evaluation and review of results in relation to the performance measures and operational targets is to be carried out, • the performance data and other data to be provided by the HSP to the Department CEO, including how, and how often, the data is to be provided, and • any other matter the Department CEO considers relevant to the provision of the health services by the HSP. Where appropriate, reference will be made in this Agreement to Policy Frameworks issued by the Department CEO pursuant to Part 3, Division 2 of the Act.

  • Performance Testing (a) All performance tests of the Project, including any Initial Performance Test required in Section 2 of Appendix VIII, will be performed in accordance with the test procedures set forth in Appendix VIII (“Performance Test”), including additional procedures and protocols related to Performance Testing as mutually agreed between Buyer and Seller (“Test Procedures”). Seller shall bear all costs and receive all revenues, if applicable, associated with all Performance Tests. (b) After the Initial Delivery Date and during the Delivery Term, Buyer will have the right to conduct a Performance Test (“Buyer Performance Test”) no more than once a calendar year to demonstrate whether the Project is capable of delivering the Distribution Services at the Contract Capacity. Within 30 calendar days following a Buyer Performance Test, Seller will have the right to retest the Project with a Performance Test (“Seller Retest”). For the avoidance of doubt, the results of any Seller Retest will supersede the results of the preceding Buyer Performance Test. (i) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at or above ninety-nine percent (99%) of the Initial Contract Capacity, the Contract Capacity will remain the Initial Contract Capacity; (ii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at more than or equal to eighty-five (85%) of the Initial Contract Capacity, but less than ninety-nine percent (99%) of the Initial Contract Capacity (“Testing Band”), the Contract Capacity will be automatically adjusted (upwards or downwards) to the capacity commensurate with the amount of Distribution Services the Project delivered during the Performance Test within the Testing Band. (iii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is not capable of delivering Distribution Services of at least eighty-five percent (85%) of the Initial Contract Capacity, an Event of Default shall occur in accordance with Section 7.1(a)(viii).

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Performance Measurement The Uniform Guidance requires completion of OMB-approved standard information collection forms (the PPR). The form focuses on outcomes, as related to the Federal Award Performance Goals that awarding Federal agencies are required to detail in the Awards.

  • Target Population TREATMENT FOR ADULT (TRA) Target Population

  • Performance Management 17.1 The Contractor will appoint a suitable Account Manager to liaise with the Authority’s Strategic Contract Manager. Any/all changes to the terms and conditions of the Agreement will be agreed in writing between the Authority’s Strategic Contract Manager and the Contractor’s appointed representative. 17.2 The Contractor will ensure that there will be dedicated resources to enable the smooth running of the Framework Agreement and a clear plan of contacts at various levels within the Contractor's organisation. Framework Public Bodies may look to migrate to this Framework Agreement as and when their current contractual arrangements expire. The Contractor will where necessary assign additional personnel to this Framework Agreement to ensure agreed service levels are maintained and to ensure a consistent level of service is delivered to all Framework Public Bodies. 17.3 In addition to annual meetings with the Authority's Strategic Contract Manager, the Contractor is expected to develop relationships with nominated individuals within each of the Framework Public Bodies to ensure that the level of service provided on a local basis is satisfactory. Where specific problems are identified locally, the Contractor will attempt to resolve such problems with the nominated individual within that organisation. The Authority's Strategic Contract Manager will liaise (or meet as appropriate) regularly with the Framework Public Bodies' Contract Manager, and where common problems are identified, it will be the responsibility of the Contractor to liaise with the Authority's Strategic Contract Manager to agree a satisfactory course of action. Where the Contractor becomes aware of a trend that would have a negative effect on one or more of the Framework Public Bodies, they should immediately notify the Authority's Strategic Contract Manager to discuss corrective action. 17.4 Regular meetings, frequency to be advised by Framework Public Body, will be held between the Framework Public Bodies' Contract Manager and the Contractor's representative to review the performance of their Call-Off Contract(s) under this Framework Agreement against the agreed service levels as measured through Key Performance Indicators (KPIs). Reports will be provided by the Contractor to the Framework Public Bodies' Contract Manager at least 14 days prior to the these meetings. 17.5 Performance review meetings will also be held annually, between the Authority's Strategic Contract Manager and the Contractor's representative to review the performance of the Framework Agreement against the agreed service levels as measured through Key Performance Indicators. A summary of the quarterly reports will be provided by the Contractor at least 14 days prior to these meetings. 17.6 The Authority will gather the outputs from contract management to review under the areas detailed in the table below. Provision of management reports 90% to be submitted within 10 working days of the month end Report any incident affecting the delivery of the Service(s) to the Framework Public Body 100% to be reported in writing to FPB within 24 hours of the incident being reported by telephone/email Prompt payment of sub-contractors and/or consortia members (if applicable). Maximum of 30 from receipt of payment from Framework Public Bodies, 10 days target 100% within 30 days

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!