Future Brood Document Process Sample Clauses

Future Brood Document Process. All Co-managers and Co-operators will incorporate their planned program of gamete, egg and fish transfers and releases for the coming year (August through July) into the Future Brood Document process coordinated by Washington Department of Fish and Wildlife (WDFW) (Puget Sound Management Plan, 1985). All proposed programs will be exchanged and reviewed by the Co-Managers' and Co-Operators’ fish health staffs for consistency with the Salmonid Disease Control Policy of the Fisheries Co- Managers of Washington State each year. To aid in this review process, the Co-Managers’ and Co-Operators’ fish health staffs will produce and exchange a three (3) year history of regulated and reportable pathogens for all of their facilities by watershed by March 1. Upon final approval, the document will become accepted as the Current Brood Program and all transfers and releases listed within will be approved pending results of any fish health tests required within this policy. Any transfer or release of gametes, eggs, or fish which is not listed in the Current Brood Document requires the requesting Co-manager or Co-operator to notify all relevant Co- Managers a minimum of ten (10) working days prior to the proposed transfer or release. Changes can be made using WDFW's Brood Document Change Form or any other form that supplies similar information. If the transfer or release is consistent with this policy and there are no objections from relevant Co-Managers within ten (10) working days after notification, then the transfer or release is approved. No transfer or release that is inconsistent with this policy’s requirements shall occur unless an exemption is acquired. All Co-manager and Co-operator operated facilities will be required to have a management plan on file that describes containment actions that will be taken in the event that a regulated exotic pathogen or a new pathogen that is causing significant biological loss is detected on site. Management plans will contain the following elements: Process of notifying required Co-Managers and other regulatory authorities of the pathogen detection. 1. Establishment of a pathogen containment area including containment and/or disinfection procedures to prevent the movement of infected stock, equipment and contaminated materials out of the areas affected by the pathogen. 2. Containment of, or disinfection procedures for, the contaminated culture water from the affected stock. 3. Disposal procedures for dead eggs/fish. 4. Destruct...
Sample 1
AutoNDA by SimpleDocs
Future Brood Document Process. All Co-Managers and Co-Operators will incorporate their planned program of gamete, egg, and fish transfers and releases for the coming year (August through July) into the Future Brood Document process coordinated by Washington Department of Fish and Wildlife (WDFW) (Puget Sound Management Plan, 1985). All proposed programs will be exchanged and reviewed by the Co-Managers' and Co-Operators’ fish health staffs for consistency with the Salmonid Disease Control Policy of the Fisheries Co- Managers of Washington State each year. To aid in this review process, the Co-Managers’ and Co-Operators’ fish health staffs will produce and exchange a three (3) year history of regulated and reportable pathogens for all of their facilities by watershed by March 1. Upon final approval, the document will become accepted as the Current Brood Program and all transfers and releases listed within will be approved pending results of any fish health tests required within this policy.
Sample 1

Related to Future Brood Document Process

  • Document Imaging Investor shall be entitled, in its sole discretion, to image or make copies of all or any selection of the agreements, instruments, documents, and items and records governing, arising from or relating to any of Company’s loans, including, without limitation, this Agreement and the other Transaction Documents, and Investor may destroy or archive the paper originals. The parties hereto (i) waive any right to insist or require that Investor produce paper originals, (ii) agree that such images shall be accorded the same force and effect as the paper originals, (iii) agree that Investor is entitled to use such images in lieu of destroyed or archived originals for any purpose, including as admissible evidence in any demand, presentment or other proceedings, and (iv) further agree that any executed facsimile (faxed), scanned, emailed, or other imaged copy of this Agreement or any other Transaction Document shall be deemed to be of the same force and effect as the original manually executed document.

  • Document Review (a) During the Evaluation Period, Purchaser and the Licensee Parties shall have the right to review and inspect, at Purchaser’s sole cost and expense, all of the following which, to Seller’s Knowledge, are in Seller’s possession or control (collectively, the “Documents”): all existing environmental reports and studies of the Real Property, real estate tax bills, together with assessments (special or otherwise), ad valorem and personal property tax bills, covering the period of Seller’s ownership of the Property; Seller’s most current lease schedule in the form attached hereto as Exhibit F (the “Lease Schedule”); current operating statements; historical financial reports; the Leases, lease files, Service Contracts, and Licenses and Permits. Such inspections shall occur at a location selected by Seller, which may be at the office of Seller, Seller’s counsel, Seller’s property manager, at the Real Property, in an electronic “war room” or any of the above. Purchaser shall not have the right to review or inspect materials not directly related to the leasing, maintenance and/or management of the Property, including, without limitation, Seller’s internal e-mails and memoranda, financial projections, budgets, appraisals, proposals for work not actually undertaken, income tax records and similar proprietary, elective or confidential information, and engineering reports and studies. (b) Purchaser acknowledges that any and all of the Documents may be proprietary and confidential in nature and have been provided to Purchaser solely to assist Purchaser in determining the desirability of purchasing the Property. Subject only to the provisions of Article XII, Purchaser agrees not to disclose the contents of the Documents or any of the provisions, terms or conditions contained therein to any party outside of Purchaser’s organization other than its attorneys, partners, accountants, agents, consultants, lenders or investors (collectively, for purposes of this Section 5.2(b), the “Permitted Outside Parties”). Purchaser further agrees that within its organization, or as to the Permitted Outside Parties, the Documents will be disclosed and exhibited only to those persons within Purchaser’s organization or to those Permitted Outside Parties who are responsible for determining the desirability of Purchaser’s acquisition of the Property. Purchaser further acknowledges that the Documents and other information relating to the leasing arrangements between Seller and Tenants are proprietary and confidential in nature. Purchaser agrees not to divulge the contents of such Documents and other information except in strict accordance with the confidentiality standards set forth in this Section 5.2 and Article XII. In permitting Purchaser and the Permitted Outside Parties to review the Documents and other information to assist Purchaser, Seller has not waived any privilege or claim of confidentiality with respect thereto, and no third party benefits or relationships of any kind, either express or implied, have been offered, intended or created by Seller, and any such claims are expressly rejected by Seller and waived by Purchaser and the Permitted Outside Parties, for whom, by its execution of this Agreement, Purchaser is acting as an agent with regard to such waiver. (c) Purchaser acknowledges that some of the Documents may have been prepared by third parties and may have been prepared prior to Seller’s ownership of the Property. PURCHASER HEREBY ACKNOWLEDGES THAT, EXCEPT AS EXPRESSLY SET FORTH IN SECTION 8.1 BELOW, SELLER HAS NOT MADE AND DOES NOT MAKE ANY REPRESENTATION OR WARRANTY REGARDING THE TRUTH, ACCURACY OR COMPLETENESS OF THE DOCUMENTS OR THE SOURCES THEREOF. SELLER HAS NOT UNDERTAKEN ANY INDEPENDENT INVESTIGATION AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DOCUMENTS AND IS PROVIDING THE DOCUMENTS SOLELY AS AN ACCOMMODATION TO PURCHASER.

  • Document Retention The Firm shall maintain for review by Citizens any documentation, receipts, files, invoices and time-keeping records in support of all disbursements for at least three (3) years after the file is closed by the Firm. Additional document retention requirements may be specified in the Firm’s Contract for Legal Services with Citizens. Citizens will not honor fees or expenses associated with audit preparation, proceedings or resolution, unless the expenses are requested and pre-approved by Citizens (i.e. copying services, delivery services, etc.).

  • Payment Process Subject to the terms and conditions established by the Agreement, the pricing per deliverable established by the Grant Work Plan, and the billing procedures established by Department, Department agrees to pay Grantee for services rendered in accordance with Section 215.422, Florida Statutes (F.S.).

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

  • Plan Document Acknowledgment By accepting the RSUs, you acknowledge that you have received a copy of the Plan, reviewed the Plan, the Agreement and this Addendum A in their entirety and fully understand and accept all provisions of the Plan, the Agreement and this Addendum A. In addition, you further acknowledge that you have read and specifically and expressly approve without limitation the following clauses in the Agreement: Section 4 (Responsibility for Taxes); Section 7 (Acknowledgement of Nature of Plan and RSUs); Section 8 (No Advice Regarding Grant); Section 9 (Right to Continued Employment); Section 11 (Deemed Acceptance); Section 13 (Severability and Validity); Section 14 (Governing Law, Jurisdiction and Venue); Section 16 (Electronic Delivery and Acceptance); Section 17 (Xxxxxxx Xxxxxxx/Market Abuse Laws); Section 18 (Language); Section 19 (Compliance with Laws and Regulations); Section 20 (Entire Agreement and No Oral Modification or Waiver); Section 21 (Addendum A); Section 22 (Foreign Asset/Account Reporting Requirements and Exchange Controls); and Section 23 (Imposition of Other Requirements).

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Plan Document Acknowledgement The Participant acknowledges that the Participant has read and specifically and expressly approves the following sections of the Agreement: Section 1: Grant of RSU Award; Section 2: Delivery; Section 3: Compliance with Laws and Regulations; Section 4: Rights as Shareholder; Section 5: Stop-Transfer Orders; Section 6: Taxes and Disposition of Shares; Section 7: Nature of Grant; Section 8: No advice Regarding Grant; Section 11: Governing Law; Venue; Section 15: Electronic Delivery; Section 16: Exhibit A; Section 18: Imposition of Other Requirements; and the Data Privacy section of this Exhibit A.

  • Consultative Process This Agreement recognises a commitment of the parties to develop working arrangements which will bring success to the operations of the Company through the ability to implement flexible work arrangements to meet the requirements of customers and the personal, study or family commitments of employees.

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