Form, Timelines and Consolidation Sample Clauses

Form, Timelines and Consolidation. A grievant or the UNION shall file a grievance in writing within fifteen school days after the occurrence of the event giving rise to the alleged violation, or within fifteen school days from the time the grievant or the UNION should reasonably have become aware of the occurrence of the event giving rise to the alleged violation, whichever is later, except, in the case of a salary grievance, the grievant or the UNION may file a salary grievance within three calendar years if the date on which the salary grievance arose. The grievance shall describe the violations alleged, including the article and section of this Agreement, and include a brief statement of facts sufficient to inform the principal or head administrator of the specific complaint and desired outcome. If two or more grievants have the same grievance, the UNION may file a joint grievance and process them as a single grievance.
AutoNDA by SimpleDocs

Related to Form, Timelines and Consolidation

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Selection of projects and financial parameters 4.1 Open calls and availability of funds (including number of calls, duration of calls, and estimated size):

  • Implementation Report Within 150 days after the Effective Date, Extendicare shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • Effect of Addenda, Bulletins, and Change Orders No special implication, interpretation, construction, connotation, denotation, import, or meaning shall be assigned to any provision of the Contract Documents because of changes created by the issuance of any (1) Addendum, (2) Bulletin, or (3) Change Order other than the precise meaning that the Contract Documents would have had if the provision thus created had read originally as it reads subsequent to the (1) Addendum, (2) Bulletin, or (3) Change Order by which it was created.

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

  • ECR Number Environmental Commitment Record Requirements Description of ADOT Responsibilities TMP-3 The following measures will be implemented for the Selected Alternative: • All equipment exhaust systems will be in good working order. Properly designed engine enclosures and intake silencers will be used. • Equipment will be maintained on a regular basis. New equipment will be subject to new product emission standards. • Stationary equipment will be located as far away from sensitive receivers as possible. • Construction-related noise generators will be shielded from noise receivers (e.g., use temporary enclosures to shield generators or crushers, take advantage of site conditions to provide topographic separation). • Construction alerts will be distributed to keep the public informed of construction activities, and a toll-free number for construction-related complaints will be provided. • During the design phase, hours of operation will be evaluated to minimize disruptions during construction. ADOT to oversee for compliance TMP-4 Congestion from construction-related traffic will create temporary impacts in the project vicinity. The magnitude of these impacts will vary depending on the location of the sources of the fill material and of the disposition sites for surplus material, the land uses along the routes, the duration of hauling operations, staging locations, and the construction phasing. To identify acceptable routes and times of operation, ADOT, or its representative, will prepare an agreement with local agencies regarding hauling of construction materials on public streets. ADOT to oversee for compliance TP Attachment 000-0 Xxxxx Xxxxxxxx Xxxxxxx Project Record of Decision (ROD) Developer’s Environmental Commitment Requirements The following table includes the Project-specific environmental commitments as written in the ROD, with minor modifications for clarification purposes. As it relates to these Technical Provisions, references to freeway, project, South Mountain Freeway, proposed action, proposed freeway, and Selected Alternative mean the Project, and references to contractor mean Developer. Developer shall comply with and perform all of the contractor and ADOT requirements, including the ADOT obligations, commitments, and responsibilities, identified in the following table, except to the extent of those requirements that are specifically identified in the third column, entitled “Description of ADOT Responsibilities,” which are not delegated to Developer.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Audit Requirements for Recipients of State Financial Assistance For purposes of this paragraph, the word "Contractor" shall be deemed to mean "nonstate entity," as that term is defined in section 4-230 of the Connecticut General Statutes. The Contractor shall provide for an annual financial audit acceptable to the Client Agency for any expenditure of State awarded funds made by the Contractor. Such audit shall include management letters and audit recommendations. The State Auditors of Public Accounts shall have access to all records and accounts for the fiscal year(s) in which the award was made. The Contractor shall comply with federal and State single audit standards as applicable.

  • Certification Regarding Use of State Funds If Party is an employer and this Agreement is a State-funded grant in excess of $1,001, Party certifies that none of these State funds will be used to interfere with or restrain the exercise of Party’s employee’s rights with respect to unionization.

  • 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.

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