Target Selection Process Sample Clauses

Target Selection Process. Bayer, CRISPR and the Company shall each be able to nominate Targets by providing written notice to the Management Board, which notice shall include the indication in the Fields (based on scientific publications and data) for which such Target is expected to be Targeting as determined by Bayer or CRISPR in good faith (except as provided below). If the Management Board approves such nominated Target, such Target shall be included in the Initial Business Plan or the next Rolling Business Plan, as applicable. If there is a dispute within the Management Board as to the indication for such Target (i.e., the proposed Target may have an indication for a different Field than that proposed) or if the Management Board otherwise does not approve the inclusion of such Target, then the matter shall be escalated in accordance with the procedures set forth in Section 12.1.
AutoNDA by SimpleDocs
Target Selection Process. On or within 10 days of each anniversary of the Effective Date during the Research Term (including the 3rd anniversary of the Effective Date), Pfizer and Cellectis will meet, either in person or by phone, to designate additional Targets as either Pfizer Targets, Cellectis Program Targets, or Other Cellectis Targets (“each such date a “Target Designation Date”). The order of designation will be, subject to the limitations set forth in Sections 2.2.2 and 2.3.2: (i) Pfizer designates a Pfizer Target, (ii) Cellectis designates a Cellectis Target (either a Cellectis Program Target or an Other Cellectis Target) (iii) Pfizer designates a Pfizer Target, (iv) Cellectis designates a Cellectis Target (either a Cellectis Program Target or an Other Cellectis Target), (v) Pfizer designates a Pfizer Target and (vi) Cellectis designates a Cellectis Target (either a Cellectis Program Target or an Other Cellectis Target). The Parties hereby acknowledge and agree that neither Party will be able to designate a Target as a Pfizer Target, Cellectis Program Target or Other Cellectis Target, as applicable, if such [***] = CONFIDENTIAL TREATMENT REQUESTED Target has previously been designated a Pfizer Target, Cellectis Program Target, Other Cellectis Target, or Servier Target. Following the 3rd anniversary of the Effective Date, Cellectis will have the right, but not the obligation, to nominate any additional Targets as Other Cellectis Targets.
Target Selection Process 

Related to Target Selection Process

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

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

  • Selection Procedure 10.2.4.1 Internal applicants shall be defined as all applicants with seniority in accordance with Article 12.5. 10.2.4.2 In filling a posted vacancy, first consideration shall be given to internal applicants who meet the stated qualifications. All Faculty members who meet the stated qualifications for the posted vacancy shall be interviewed by the Selection Committee. Past service and evaluations shall be considered by the Committee. The best qualified candidate shall be recommended for appointment to the position. 10.2.4.3 Where the qualifications of two or more of the applicants are relatively equal, the applicant with the greatest seniority shall be recommended for appointment to the position. 10.2.4.4 In establishing the qualifications, and in evaluating the qualifications and past performance of the applicants, the committee shall act in good faith, in a fair and reasonable manner, and shall not act in an arbitrary or discriminatory fashion. 10.2.4.5 Following the interviews, the committee will submit its recommendations containing a list of qualified candidates in order of preference, through the appropriate Xxxx to the President or delegate. 10.2.4.6 New faculty members shall be appointed only when there are no qualified internal applicants. 10.2.4.7 If there are no qualified internal applicants, the selection committee may consider external applications, in accordance with the procedure outlined above. 10.2.4.8 Internal applicants will be advised as soon as possible of the selection committee's decision that the committee will be considering external applications in accordance with Article 10.2.4.7.

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

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

  • Selection Procedures In selecting the Loan Assets to be Pledged pursuant to this Agreement, no selection procedures were employed which are intended to be adverse to the interests of the Lenders.

  • Selection Criteria Each Contract is secured by a new or used Motorcycle. No Contract has a Contract Rate less than 1.00%. Each Contract amortizes the amount financed over an original term no greater than 84 months (excluding periods of deferral of first payment). Each Contract has a Principal Balance of at least $500.00 as of the Cutoff Date.

  • Shift Selection Employee assignments within the Patrol Bureau will occur between approximately April 1-15 and shall be awarded based upon seniority. Approximately three (3) months before then the Department will publish a call for written requests on shift assignment. Employees will make their first three (3) choices known. Employees will learn of the assignment, including days off associated with their assignment, immediately after the bidding process is completed. Assignments will take effect on the schedule immediately following July 1st. Residence Hall assignments will be made prior to all others. No officer will be required to work a Residence Hall assignment in consecutive years. Assignment of the remaining officers will begin with selection(s) for day and night shifts. The bid for assignments will continue until all positions are filled. The following general rules apply to assignments: 1. During the term of this Agreement, no employee will be reassigned to a different shift other than the shift awarded by seniority except in situations where the University cannot continue to provide police services. In the event a shift reassignment must occur, it will be offered to volunteers based on seniority. If there are no volunteers it will be assigned to the least senior officer in the department. 2. Shift selection shall be an appropriate subject for the Joint Labor/Management Committee. 3. If a shift becomes available as a result of trainees being released for duty, and if there is at least four (4) months until the next shift change, the shift will be posted and awarded by seniority. The new trainee released for duty will take the senior officers shift. If no employee desires the shift, the trainee scheduled for assignment will be assigned that shift. The parties recognize that for the betterment of the Department it may be necessary to assign a trainee to a specific shift. 4. Voluntary shift trades will be allowed as long as overtime costs are not incurred. 5. Except in a bona fide emergency, no employee shall be assigned to work more than sixteen (16) hours in a twenty-four (24) hour period, provided however employees may volunteer to work up to eighteen (18) hours in a twenty-four (24) hour period.

  • ONLINE PUBLIC AUCTION PROCESS Bidders may browse through the PAH Website and select the properties they wish to bid online.

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