INITIATING/PROCESSING ULP'S Sample Clauses

INITIATING/PROCESSING ULP'S. Section 1. Before the Association or the Employer files an unfair labor practice (ULP) charge with the Federal Labor Relations Authority (FLRA) at the regional or national level, the parties shall attempt to informally resolve the charge in the following manner: A. The filer of the ULP charge will notify the charged party, either orally or in writing, that a ULP charge may be filed. Upon receipt of oral or written notification by the charging party, the charged party may request a meeting with the charging party for the purpose of attempting to informally resolve the charge. The period of time for attempted informal resolution shall not exceed fifteen (15) calendar days, starting from the time of receipt of oral or written notification by the charged party. This fifteen (15) day period may be extended if mutually agreed by the parties. B. Upon request of the charged party, the parties shall meet within the fifteen (15) day period to attempt to informally resolve the issue. Regarding ULP's at the regional level, said meeting shall be at the Association representative's work site unless the Employer provides the Association represen- tative official time with travel and per diem to travel to the Employer's work site. C. If the ULP charge is not resolved during this period, the charging party may elect to formally file the charge immediately following the meeting. D. These proceedings do not apply to ULP charges filed by individuals. Section 2. ULP charges filed on behalf of the Association or the Employer shall be filed only by authorized officials or staff at the regional or national level.
Sample 1Sample 2
AutoNDA by SimpleDocs
INITIATING/PROCESSING ULP'S. Section 1. Before the Association or the Employer files an unfair labor practice (ULP) charge with the Federal Labor Relations Authority (FLRA) at the regional or national level, the parties shall attempt to informally resolve the charge in the following manner: A. The filer of the ULP charge will notify the charged party, either orally or in writing, that a ULP charge may be filed. Upon receipt of oral or written notification by the charging party, the charged party may request a meeting with the charging party for the purpose of attempting to informally resolve the charge. The period of time for attempted informal resolution shall not exceed fifteen (15) calendar days, starting from the time of receipt of oral or written notification by the charged party. This fifteen (15) day period may be extended if mutually agreed by the parties. B. Upon request of the charged party, the parties shall meet within the fifteen (15) day period to attempt to informally resolve the issue. Regarding ULP's at the regional level, said meeting shall be at the Association representative's work site unless the Employer provides the Association representative official time with travel and per diem to travel to the Employer's work site. C. If the ULP charge is not resolved during this period, the charging party may elect to formally file the charge immediately following the meeting. D. These proceedings do not apply to ULP charges filed by individuals. Section 2. ULP charges filed on behalf of the Association or the Employer shall be filed only by authorized officials or staff at the regional or national level. Section 3. The time periods in this Article shall be tolled during all recess periods in excess of four (4) days. In the event of a government furlough/shutdown, the time periods shall be tolled from the start of the furlough/shutdown until five (5) days after the end of the furlough/shutdown to allow for schools and the Employer to return to normal functions. All time limits in this procedure may be extended or curtailed in writing by mutual consent of the parties. Section 4. In the event that the fifteen (15) day period in Section 1 of this Article would result in the ULP being untimely filed under the FLRA deadlines for the filing of a ULP, the fifteen (15) day period will be waived.
Sample 1
INITIATING/PROCESSING ULP'S. Section 1. Unless there are 30 days or less remaining in the period for a timely filing of the charge, before the Association or the Employer files an unfair labor practice (ULP) charge with the Federal Labor Relations Authority (FLRA) at the regional or national level, the parties shall attempt to informally resolve the charge in the following manner: A. The filer of the ULP charge will notify the charged party, either orally or in writing that a ULP charge may be filed. Upon receipt of oral or written notification by the charging party, the charged party may request a meeting with the charging party for the purpose of attempting to informally resolve the charge. The period of time for attempted informal resolution shall not exceed fifteen (15) calendar days, starting from the time of receipt of oral or written notification by the charged party. This fifteen (15) day period may be extended if mutually agreed by the parties. B. Upon request of the charged party, the parties shall meet within the fifteen (15) day period to attempt to informally resolve the issue. Regarding ULP's at the regional level, said meeting shall be at the Association representative's work site unless the Employer provides the Association representative official time with travel and per diem to travel to the Employer's work site. C. If the ULP charge is not resolved during this period, the charging party may elect to formally file the charge immediately following the meeting. D. These proceedings do not apply to ULP charges filed by individuals. Section 2. ULP charges filed on behalf of the Association or the Employer shall be filed only by authorized officials or staff at the regional or national level. INITIALS: DoDEA: FEA: DATE:
Sample 1

Related to INITIATING/PROCESSING ULP'S

  • Sub-processing 11.1 The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub- processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement. 11.2 The prior written contract between the data importer and the sub-processor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the sub-processor shall be limited to its own processing operations under the Clauses. 11.3 The provisions relating to data protection aspects for sub-processing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established, namely ........................................ 11.4 The data exporter shall keep a list of sub-processing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5(j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • THIRD-PARTY CONTENT, SERVICES AND WEBSITES 10.1 The Services may enable You to link to, transfer Your Content or Third Party Content to, or otherwise access, third parties’ websites, platforms, content, products, services, and information (“Third Party Services”). Oracle does not control and is not responsible for Third Party Services. You are solely responsible for complying with the terms of access and use of Third Party Services, and if Oracle accesses or uses any Third Party Services on Your behalf to facilitate performance of the Services, You are solely responsible for ensuring that such access and use, including through passwords, credentials or tokens issued or otherwise made available to You, is authorized by the terms of access and use for such services. If You transfer or cause the transfer of Your Content or Third Party Content from the Services to a Third Party Service or other location, that transfer constitutes a distribution by You and not by Oracle. 10.2 Any Third Party Content we make accessible is provided on an “as-is” and “as available” basis without any warranty of any kind. You acknowledge and agree that we are not responsible for, and have no obligation to control, monitor, or correct, Third Party Content. We disclaim all liabilities arising from or related to Third Party Content. 10.3 You acknowledge that: (i) the nature, type, quality and availability of Third Party Content may change at any time during the Services Period, and (ii) features of the Services that interoperate with Third Party Services such as Facebook™, YouTube™ and Twitter™, etc., depend on the continuing availability of such third parties’ respective application programming interfaces (APIs). We may need to update, change or modify the Services under this Agreement as a result of a change in, or unavailability of, such Third Party Content, Third Party Services or APIs. If any third party ceases to make its Third Party Content or APIs available on reasonable terms for the Services, as determined by us in our sole discretion, we may cease providing access to the affected Third Party Content or Third Party Services without any liability to You. Any changes to Third Party Content, Third Party Services or APIs, including their unavailability, during the Services Period does not affect Your obligations under this Agreement or the applicable order, and You will not be entitled to any refund, credit or other compensation due to any such changes.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Testing Procedures Testing will be conducted by an outside certified Agency in such a way to ensure maximum accuracy and reliability by using the techniques, chain of custody procedures, equipment and laboratory facilities which have been approved by the U.S. Department of Health and Human Services. All employees notified of a positive controlled substance or alcohol test result may request an independent test of their split sample at the employee’s expense. If the test result is negative the Employer will reimburse the employee for the cost of the split sample test.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Testing-the-Waters Materials If at any time following the distribution of any Written Testing-the-Waters Communication there occurred or occurs an event or development as a result of which such Written Testing-the-Waters Communication included or would include an untrue statement of a material fact or omitted or would omit to state a material fact necessary in order to make the statements therein, in the light of the circumstances existing at that subsequent time, not misleading, the Company will promptly notify the Representatives and will promptly amend or supplement, at its own expense, such Written Testing-the-Waters Communication to eliminate or correct such untrue statement or omission.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

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