Evaluation Process
A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory.
B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as:
1. Reviewing the employee’s performance;
2. Identifying ways the employee may improve their performance;
3. Updating the employee’s position description, if necessary;
4. Identifying performance goals and expectations for the next appraisal period; and
5. Identifying employee training and development needs.
C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file.
D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal.
E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure.
F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.
Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.
Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may
(i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014.
(b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”).
(c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.
(d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website.
(i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i).
(ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute.
(iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator.
(iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.
(v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below.
(e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e).
(i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2.
(ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11.
(iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions.
(iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors.
(v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder.
(f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6.
(g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).
Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles:
(a) Such schedules shall be established by mutual agreement of the Home and the Union;
(b) These schedules may pertain to full-time and/or part-time employees;
(c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations;
(d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules;
(e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis.
(f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).
Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;
Manufacturing Technology Transfer Upon AbbVie’s written request with respect to a given Collaboration CAR-T Product and Licensed Product, Caribou shall effect a full transfer to AbbVie or its designee (which designee may be an Affiliate or a Third Party Provider) of all Materials and Know-How Controlled by Caribou relating to the then-current process for the Manufacture of such Collaboration CAR-T Product and any corresponding Licensed Products (each, a “Manufacturing Process”). Caribou shall provide, shall cause its Affiliates to provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to provide, all reasonable assistance requested by AbbVie to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to implement each Manufacturing Process at the facilities designated by AbbVie. If requested by AbbVie, such assistance shall include facilitating the entering into of agreements with applicable Third Party suppliers relating to such Collaboration CAR-T Product and any corresponding Licensed Products. Without limitation of the foregoing, in connection with the Manufacturing Process and related transfer:
(a) Caribou shall, and shall cause its Affiliates to, make available to AbbVie (or its Affiliate or designated Third Party Provider, as applicable), and shall use Commercially Reasonable Efforts to assist AbbVie in causing all Third Party Providers to make available to AbbVie, from time to time as AbbVie may request, all Materials and Manufacturing-related Know-How Controlled by Caribou relating to each Manufacturing Process, including methods, reagents and processes and testing/characterization Know-How, and all documentation constituting material support, performance advice, shop practice, standard operating procedures, specifications as to Materials to be used, and control methods, that are necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party manufacturer, as applicable) to use and practice such Manufacturing Process;
(b) Caribou shall cause all appropriate employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility at mutually convenient times to assist with the working up and use of each Manufacturing Process and with the training of the personnel of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to the extent necessary or reasonably useful to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice such Manufacturing Process;
(c) Without limiting the generality of this Section 4.4.2, Caribou shall cause all appropriate analytical and quality control laboratory employees and representatives of Caribou and its Affiliates, and shall use Commercially Reasonable Efforts to assist AbbVie in causing all appropriate analytical and quality control laboratory employees and representatives of Third Party Providers, to meet with employees or representatives of AbbVie (or its Affiliate or designated Third Party Provider, as applicable) at the applicable manufacturing facility and make available all necessary equipment, at mutually convenient times, to support and execute the provision of all applicable analytical methods and the validation thereof (including all applicable Know-How, Information and Materials Controlled by Caribou, and sufficient supplies of all primary and other reference standards);
(d) Caribou shall, and shall cause its Affiliates to, take such steps, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers take such steps, as are necessary or reasonably useful to assist AbbVie (or its Affiliate or designated Third Party Provider, as applicable) in obtaining any necessary licenses, permits or approvals from Regulatory Authorities with respect to the Manufacture of the applicable Collaboration CAR-T Products and corresponding Licensed Products at the applicable facilities; and
(e) Caribou shall, and shall cause its Affiliates to, provide, and shall use Commercially Reasonable Efforts to assist AbbVie in causing Third Party Providers to provide, such other assistance as AbbVie (or its Affiliate or designated Third Party Provider, as applicable) may reasonably request to enable AbbVie (or its Affiliate or designated Third Party Provider, as applicable) to use and practice each Manufacturing Process and otherwise to Manufacture the applicable Collaboration CAR-T Products and corresponding Licensed Products.
Ordering Process 6.4.1 CLEC, or CLEC's agent, shall act as the single point of contact for its End User Customers' service needs, including without limitation, sales, service design, order taking, Provisioning, change orders, training, maintenance, trouble reports, repair, post-sale servicing, Billing, collection and inquiry. CLEC's End User Customers contacting Qwest in error will be instructed to contact CLEC; and Qwest's End User Customers contacting CLEC in error will be instructed to contact Qwest. In responding to calls, neither Party shall make disparaging remarks about each other. To the extent the correct provider can be determined, misdirected calls received by either Party will be referred to the proper provider of local Exchange Service; however, nothing in this Agreement shall be deemed to prohibit Qwest or CLEC from discussing its products and services with CLEC's or Qwest's End User Customers who call the other Party seeking such information.
6.4.2 CLEC shall transmit to Qwest all information necessary for the ordering (Billing, Directory Listing and other information), installation, repair, maintenance and post-installation servicing according to Qwest's standard procedures, as described in the Qwest Product Catalog (PCAT) available on Qwest's public web site located at xxxx://xxx.xxxxx.xxx/wholesale/pcat. Information shall be provided using Qwest's designated Local Service Request (LSR) format which may include the LSR, End User Customer and resale forms.
6.4.3 Qwest will use the same performance standards and criteria for installation, Provisioning, maintenance, and repair of services provided to CLEC for resale under this Agreement as Qwest provides to itself, its Affiliates, its subsidiaries, other Resellers, and Qwest retail End User Customers. The installation, Provisioning, maintenance, and repair processes for CLEC's resale service requests are detailed in the Access to OSS Section of this Agreement, and are applicable whether CLEC's resale service requests are submitted via Operational Support System or by facsimile.
6.4.4 CLEC is responsible for providing to Qwest complete and accurate End User Customer Directory Listing information including initial and updated information for Directory Assistance Service, white pages directories, and E911/911 Emergency Services. The Ancillary Services Section of this Agreement contains complete terms and conditions for Directory Listings for Directory Assistance Services, white pages directories, and E911/911 Emergency Services.
6.4.5 If Qwest's retail End User Customer, or the End User Customer's New Service Provider orders the discontinuance of the End User Customer's existing Qwest service in anticipation of the End User Customer moving to a New Service Provider, Qwest will render its closing xxxx to the End User Customer, discontinuing Billing as of the date of the discontinuance of Qwest's service to the End User Customer. If the Current Service Provider, or if the End User Customer's New Service Provider orders the discontinuance of existing resold service from the Current Service Provider, Qwest will xxxx the Current Service Provider for service through the date the End User Customer receives resold service from the Current Service Provider. Qwest will notify CLEC by Operational Support System interface, facsimile, or by other agreed-upon processes when an End User Customer moves from the Current Service Provider to a New Service Provider. Qwest will not provide the Current Service Provider with the name of the New Service Provider selected by the End User Customer.
6.4.6 CLEC shall provide Qwest and Qwest shall provide CLEC with points of contact for order entry, problem resolution and repair of the resold services. These points of contact will be identified for both CLEC and Qwest in the event special attention is required on a service request.
6.4.7 Prior to placing orders on behalf of the End User Customer, CLEC shall be responsible for obtaining and having in its possession Proof of Authorization (POA), as set forth in the POA Section of this Agreement.
6.4.8 Due Date intervals for CLEC's resale service requests are established when service requests are received by Qwest through Operational Support Systems or by facsimile. Intervals provided to CLEC shall be equivalent to intervals provided by Qwest to itself, its Affiliates, its subsidiaries, other Resellers, and to Qwest's retail End User Customers.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users.
2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status.
2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
Manufacturing (a) The Supplier shall without limitation be responsible, at no additional cost to the Purchaser, for: sourcing and procuring all raw materials for the Products; obtaining all necessary approvals, permits and licenses for the manufacturing of the Products; providing sufficient qualified staff and workers to perform the obligations under this Purchase Agreement; implementing and maintaining effective inventory and production control procedures with respect to the Products; and handling other matters as reasonably requested by the Purchaser from time to time.
(b) The Supplier shall not change any process, material, component, packaging or manufacturing location without the Purchaser’s express prior written approval.
Bidding Process 3.1. Bidding shall generally commence based on the sequence of the lot being shown on the PAH Website. However the Auctioneer has the right to vary the sequence without having to give prior notice to the intended bidders.
3.2. It shall be the responsibilities of the E-bidders to login through PAH website to wait for the turn to bid for the property lot in which they intend to bid.
3.3. The Auctioneer has the discretion to set a new reserve price in the event that there is more than one (1) registered bidder.
3.4. The amount of incremental bid will appear on the website prior to the commencement of the auction.
3.5. Registered online Bidders shall start bidding online by pressing the BID Button using their own gadgets with internet connection. If your bid is the highest, it will be denoted by a Green Coloured Box otherwise it will be a Red Coloured Box The highest bid shall flash 10 seconds (subject to change) interval for four (4) times " Calling Once, Calling Twice, Last Call and Sold". E-bidders may submit their bid at any of these stages of biddings by pressing the BID button. The successful bidder's bid will be denoted by a green coloured screen. The highest bidder shall be declared as the successful purchaser upon the fall of the hammer.
3.6. In the event that there is no bid after forty(40) seconds from the time of commencement of the auction, the auction shall be aborted.
3.7. Any bid once entered by the registered online E-bidders shall be binding and the bid shall not be withdrawn or retracted in any manner whatsoever after the fall of the hammer.
3.8. Both the successful and unsuccessful bidders will be notified by the Auctioneer through the website and also via E-mail where further directions are given in order to conclude the sale of the auction property.
3.9. In the event of any dispute, the decision of the Auctioneer shall be final and binding on all bidders.
3.10. Unsuccessful E-bidders shall have the deposit refunded to the same bank account from which the deposit transfer was made within two (2) working days from the date of auction.
3.11. The information shown and/or prompted on the screen handled by the PAH website in regards to the auction in particular the increment of the bidding price during the bidding process and the declaration of the successful bidder shall be final and conclusive.
