Taxonomy Working Group Report Sample Clauses

Taxonomy Working Group Report. 11.1.1 The report of the Taxonomy Working Group (TWG, AC5 Doc12) was presented by the Vice Chair. The Group had four main actions to complete in the last intersessional period. 11.1.2 A review was undertaken of the taxonomic status of the Tristan and Wandering Albatross species. This group used the agreed criteria for such reviews and found that these two taxa should be regarded as separate species, thus confirming the current species list in Annex I to the Agreement. 11.1.3 A review of five recent publications pertinent to albatross and petrel taxonomy was undertaken. This found that there were two schools of thought relating to the taxonomy generally. One approximately followed the taxonomy that ACAP had adopted, while others ‗lumped‘ species together. The Taxonomy Working Group believes that there is a strong logic to following the current ACAP taxonomy. 11.1.4 It was noted that the Convention on Migratory Species (CMS) was considering revising its taxonomy and the Committee agreed that the TWG should draft a letter for the AC Chair to send to the Chair of the Scientific Committee of CMS, recommending adoption of the ACAP taxonomy. The Committee asked that TWG also consider how ACAP could influence the taxonomy of other groups such as the South American Checklist Committee. 11.1.5 The TWG continued the establishment of a morphometric and plumage database to facilitate the taxonomic process, the identification of bycatch specimens, and the long-term storage of valuable data. This database will be incorporated in ACAP‘s main database in the next year. TWG also continued to update the Taxonomy Working Group‘s web-based bibliographic database. 11.1.6 In 2010-11, the TWG will continue to address items in the Advisory Committee Action Plan provided by the Meeting of Parties. In addition, it will respond to the CMS Scientific Committee (see 11.4 above) and will consider ways of influencing other regional/global taxonomy decision committees/groups.
Sample 1
AutoNDA by SimpleDocs

Related to Taxonomy Working Group Report

  • Development Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

  • Working Group 1. The Parties hereby establish a Working Group on Temporary Entry for Business Persons, which shall meet at least once every 3 years or on request of the Free Trade Commission to consider any matter arising under this Chapter. 2. The Working Group's functions shall include: (a) to review the implementation and operation of this Chapter; (b) to consider the development of measures to further facilitate temporary entry of business persons on a reciprocal basis; (c) the identification of measures that affect the temporary entry of business persons under this Chapter; and (d) the observance of the issues established under Article 121 (Cooperation).

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

  • Working Groups From time to time, a Joint Committee may establish and delegate duties to sub-committees or directed teams (each, a “Working Group”) on an “as-needed” basis to oversee particular projects or activities (e.g., joint project team, joint finance group, or joint intellectual property group). Each such Working Group shall be constituted and shall operate as the Joint Committee determines; provided, that each Working Group shall have equal representation from each Party, unless otherwise mutually agreed. Working Groups may be established on an ad hoc basis for purposes of a specific project or on such other basis as the Joint Committee may determine. Each Working Group and its activities shall be subject to the oversight, review and approval of, and shall report to, the Joint Committee that formed said Working Group. In no event shall the authority of the Working Group exceed that specified for the Joint Committee that formed the Working Group. All decisions of a Working Group shall be by unanimous agreement. Any disagreement between the designees of AbbVie and Ablynx on a Working Group shall be referred to the Joint Committee that formed the Working Group for resolution.

  • Project Reports The Recipient shall monitor and evaluate the progress of the Project and prepare Project Reports in accordance with the provisions of Section 4.08 of the General Conditions and on the basis of the indicators agreed with the Association. Each Project Report shall cover the period of one calendar semester, and shall be furnished to the Association not later than one month after the end of the period covered by such report.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.

  • Research Reports Distributor acknowledges that Dealer may prepare research reports relating to the Fund that are not to be used for marketing purposes (“Research Reports”). Distributor hereby authorizes Dealer to use the name of the Fund, Distributor and BREDS in Research Reports.

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