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.

  • Initiating Interconnection 4.1 If ENT determines to offer Telephone Exchange Services and to interconnect with Verizon in any LATA in which Verizon also offers Telephone Exchange Services and in which the Parties are not already interconnected pursuant to this Agreement, ENT shall provide written notice to Verizon of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.2 The notice provided in Section 4.1 of this Attachment shall include (a) the initial Routing Point(s); (b) the applicable technically feasible Point(s) of Interconnection on Verizon’s network to be established in the relevant LATA in accordance with this Agreement; (c) ENT’s intended Interconnection activation date; (d) a forecast of ENT’s trunking requirements conforming to Section 14.2 of this Attachment; and (e) such other information as Verizon shall reasonably request in order to facilitate Interconnection. 4.3 The interconnection activation date in the new LATA shall be mutually agreed to by the Parties after receipt by Verizon of all necessary information as indicated above. Within ten (10) Business Days of Verizon’s receipt of ENT’s notice provided for in Section 4.1of this Attachment, Verizon and ENT shall confirm the technically feasible Point of Interconnection on Verizon’s network in the new LATA and the mutually agreed upon Interconnection activation date for the new LATA.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC 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 CSTC 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 CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC 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 CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

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

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

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