Reasonable Released Time Sample Clauses

Reasonable Released Time. Grievance meetings normally will be scheduled by the District so as not to conflict with assigned duties. However, if the meeting is expected to be of such duration that it would extend beyond the normal business hours of the District's Central Office, the District shall provide released time with no loss of pay to one (1) authorized representative of the Federation so that the session can be accommodated within such business hours.
Sample 1Sample 2Sample 3See All (34)
AutoNDA by SimpleDocs
Reasonable Released Time. Grievance adjustment activities for the grievant and Association representative shall be handled as follows:
Sample 1Sample 2Sample 3See All (10)
Reasonable Released Time. Employees shall be entitled to (paid) released time under the following circumstances:
Sample 1Sample 2Sample 3See All (5)
Reasonable Released Time. Grievance meetings normally will be scheduled by the District and Federation at mutually acceptable times. Reasonable release time shall be granted for the processing of grievances.
Sample 1Sample 2Sample 3See All (5)
Reasonable Released Time. Reasonable released time will be provided a designated representative for the purpose of representing a grievant pursuant to this Article when meetings or appointments are mutually scheduled by the District and the Association.
Sample 1Sample 2Sample 3See All (4)
Reasonable Released Time. Reasonable released time will be provided shop stewards for purposes of representing the grievant pursuant to this Article (see 8.1.8).
Sample 1Sample 2Sample 3
Reasonable Released Time. 28 Grievance meetings normally will be scheduled by the District so as not to 29 conflict with student services. However, if the meeting is expected to be of 30 such duration that it would extend beyond the normal business hours of 31 the District's central office, the District shall provide released time with no 32 loss of pay to one authorized employee-representative of the Association 33 so that the session can be accommodated within such business hours. 34 This shall constitute "reasonable periods of released time" within the 35 meaning of Government Code Section 3543.1 (c).
Sample 1
AutoNDA by SimpleDocs
Reasonable Released Time. 18 Grievance meetings shall be scheduled during District Office business hours at a time mutually 19 agreed upon by the grievant and the District so as to minimize the inconvenience to the District 20 and at the same time afford the grievant a full opportunity to produce witnesses when necessary, 21 in support of the grievant's position. However, if scheduling is necessary during normal working 22 hours, the District shall provide released time with no loss of pay to the grievant, witnesses and 23 CSEA representative. This shall constitute "reasonable periods of released time" within the 24 meaning of Government Code Section 3543. 1 (c).
Sample 1

Related to Reasonable Released Time

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). However, it is expressly agreed that University will not provide to Contractor, and Contractor will never seek to access, any University Records that contain personally identifiable information regarding any individual that is not available to any requestor under the Texas Public Information Act, Chapter 552, Texas Government Code, including “directory information” of any student who has opted to prohibit the release of their “directory information” as that term is defined under the Family Educational Rights and Privacy Act, 20 USC §1232g (FERPA) and its implementing regulations. [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 CFR Part 160 and subparts A and E of Part 164 (collectively HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS 165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.]

  • Loop Testing/Trouble Reporting 2.1.6.1 NOW will be responsible for testing and isolating troubles on the Loops. NOW must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, NOW will be required to provide the results of the NOW tests which indicate a problem on the BellSouth provided Loop.

  • Updated Information Submission by Developer The updated information submission by the Developer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. Developer shall submit a completed copy of the Large Generating Facility data requirements contained in Appendix 1 to the Large Facility Interconnection Procedures. It shall also include any additional information provided to Connecting Transmission Owner for the Interconnection Feasibility Study and Interconnection Facilities Study. Information in this submission shall be the most current Large Generating Facility design or expected performance data. Information submitted for stability models shall be compatible with NYISO standard models. If there is no compatible model, the Developer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Developer’s data is different from what was originally provided to Connecting Transmission Owner and NYISO pursuant to an Interconnection Study Agreement among Connecting Transmission Owner, NYISO and Developer and this difference may be reasonably expected to affect the other Parties’ facilities or the New York State Transmission System, but does not require the submission of a new Interconnection Request, then NYISO will conduct appropriate studies to determine the impact on the New York State Transmission System based on the actual data submitted pursuant to this Article 24.3. Such studies will provide an estimate of any additional modifications to the New York State Transmission System, Connecting Transmission Owner’s Attachment Facilities, or System Upgrade Facilities or System Deliverability Upgrades based on the actual data and a good faith estimate of the costs thereof. The Developer shall not begin Trial Operation until such studies are completed. The Developer shall be responsible for the cost of any modifications required by the actual data, including the cost of any required studies.

  • Correction of Personal Information 8. Within 5 business days of receiving a written direction from the Public Body to correct or annotate any personal information, the Contractor must annotate or correct the information in accordance with the direction.

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