Sector Hails/Reporting Sample Clauses

Sector Hails/Reporting. 25 Each Participating Vessel must notify the Manager, his designated representative, and/or an 26 approved Monitoring Vendor via email, other electronic means, or other means if necessary prior 27 to departing from port on a commercial fishing trip when commercial fishing with gear capable 28 of harvesting regulated groundfish unless otherwise exempted. Such notification shall include 29 vessel name, permit number, and any other information as determined by the Manager. In 30 accordance with and defined by Amendment 16, all Sector vessels will also be required to make 31 a declaration to NMFS via VMS prior to departing port identifying whether they intend to fish in 32 one broad reporting area or multiple reporting areas. Vessels that fish in multiple areas will be 33 required to provide additional daily reports to NMFS as required by Amendment 16. Each 34 Participating Vessel must notify the Manager, his designated representative, and/or an approved 35 Monitoring Vendor via email, other electronic means, or other means if necessary in accordance 36 with Section 5.08 hereof with species-specific landings, and any other information as requested 37 by NMFS.
Sample 1
AutoNDA by SimpleDocs
Sector Hails/Reporting. Consistent with Exhibit E, each Participating Vessel operator will provide a trip start hail prior to departing port at the beginning of a commercial fishing trip when commercial fishing with gear capable of harvesting regulated groundfish. This will be sent as an email via VMS to the dockside monitoring vender who will relay the message to the sector manager and to NOAA Fisheries Office for Law Enforcement (OLE) upon receiving the transmission. The transmission will contain the vessel permit number, trip ID# (VTR number for the first VTR page) and an estimated trip duration. For trips less than 6 hours or occurring less than 6 hours of port, the hail trip start will also provide estimated date and time of arrival to port and estimated date and time of offload. The trip end hail will be sent upon completion of the last tow with required updated information including the estimated time of arrival, time of offload and estimated total weight of each species on board. An alternative timing for the trip end hail may be implemented during the 2010 fishing year if agreed upon by the sector, sector monitoring provider, and NMFS. The dockside monitoring vender will immediately send a confirmation to the vessel that the trip start hail was received; if the vessel does not receive the confirmation within 10 minutes, the captain must contact the vender to confirm the trip start hail via a back up system, e.g., a phone call. A trip end hail will be provided by the vessel operator 6 hours before landing for trips that are at least 6 hours in duration and more than 6 hours from port. This will also be sent as an email through VMS to the dockside monitor provider the message will contain: the vessel permit #, trip ID # (VTR number on the first VTR page), intended offloading location(s) including the dock or dealer, port or harbor and the state. This message will also contain estimated date and time of arrival, estimated date and time of offload and estimated total weight of each species on board. The Dockside Monitoring Provider will relay all information provided in the trip end hail to the sector manager and to OLE as well as provide confirmation back to the vessel operator. If the vessel does not receive confirmation within 10 minutes, the captain must contact the vender to confirm the hail trip end via a back up system, e.g., a phone call. Alternative standards for trips that are at least 6 hours may be implemented during the 2010 fishing year if agreed upon by the se...
Sample 1Sample 2
Sector Hails/Reporting. Each Participating Vessel must notify the Manager, his designated representative, and/or an approved Monitoring Vendor via email, other electronic means, or other means if necessary prior to departing from port on a commercial fishing trip when commercial fishing with gear capable of harvesting regulated groundfish. Such notification shall include vessel name, permit number, sector name, and any other information as determined by the Manager. Notifications received from the vessel will be immediately relayed to OLE upon receipt by the Manager and/or Monitoring Vendor. In accordance with and defined by Amendment 16, all Sector vessels will also be required to make a declaration to NMFS via VMS prior to departing port identifying whether they intend to fish in one broad reporting area or multiple reporting areas. Vessels that fish in multiple areas will be required to provide additional daily reports to NMFS as required by Amendment 16. Each Participating Vessel must notify the Manager, his designated representative, and/or an approved Monitoring Vendor via email, other electronic means, or other means if necessary in accordance with Section 5.08 hereof with species-specific landings, and any other information as requested by NMFS.
Sample 1Sample 2
Sector Hails/Reporting. Consistent with Exhibit G, each Participating Vessel 3 operator must send a trip start hail when required by GARFO and a trip end hail six hours before
Sample 1Sample 2
Sector Hails/Reporting. Consistent with Exhibit E, each Participating 46 Vessel operator will provide a trip start hail prior to departing port at the beginning of a 1 commercial fishing trip when commercial fishing with gear capable of harvesting 2 regulated groundfish. This will be sent as an email via VMS to NOAA Fisheries Office 3 for Law Enforcement (OLE) who will relay the message to the dockside monitoring 4 vender upon receiving the transmission, and the dockside monitoring vendor will relay 5 the message to the sector manager. The transmission will contain the vessel permit 7 time of arrival to port. 9 For trips less than 6 hours or occurring less than 6 hours of port, the hail trip start will 10 also provide estimated date and time of arrival to port and estimated date and time of 11 offload. The trip end hail will be sent upon completion of the last tow with required 12 updated information including the estimated time of arrival, time of offload, estimated 13 total amount of regulated species (in pounds, landed weight), and estimated total weight 14 of each species on board (in pounds, landed weight). An alternative timing for the trip 15 end hail may be implemented during the 2010 fishing year if agreed upon by the sector, 16 sector monitoring provider, and NMFS. The dockside monitoring vender will 18 vessel does not receive the confirmation within 10 minutes, the captain must contact the 19 vender to confirm the trip start hail via a back up system, e.g., a phone call. 21 A trip end hail will be provided by the vessel operator 6 hours before landing for trips 22 that are at least 6 hours in duration and more than 6 hours from port. This will also be 23 sent as an email through VMS to the dockside monitor provider the message will contain: 24 the vessel permit #, trip ID # (VTR number on the first VTR page), intended offloading 25 location(s) including the dock or dealer, port or harbor and the state. This message will 26 also contain estimated date and time of arrival, estimated date and time of offload, 27 estimated total amount of regulated species, and estimated total weight of each species on 28 board. The Dockside Monitoring Provider will relay all information provided in the trip 29 end hail to the sector manager and to OLE as well as provide confirmation back to the 30 vessel operator. If the vessel does not receive confirmation within 10 minutes, the 31 captain must contact the vender to confirm the hail trip end via a back up system, e.g., a 32 phone call. A...
Sample 1Sample 2
Sector Hails/Reporting. Consistent with Exhibit E, each Participating Vessel operator will provide a trip end hail upon completion of the last tow. An alternative timing for the trip end hail may be implemented during the 2012 fishing year if agreed upon by the sector, sector monitoring provider, and NMFS. The trip end hail will also be sent as an email through VMS to the sector manager, the message will contain: the vessel permit #, trip ID # (VTR number on the first VTR page), intended offloading location(s) including the dock or dealer, port or harbor and the state. This message will also contain estimated date and time of arrival, estimated date and time of offload, estimated total amount of regulated species, and estimated total weight of each species on board In accordance with and defined by Amendment 16, all Sector vessels will also be required to make a declaration to NMFS via VMS prior to departing port identifying whether they intend to fish in one broad reporting area or multiple reporting areas. Vessels that fish in multiple areas will be required to provide additional daily reports to NMFS as required by Amendment 16. The sector will submit required reports using the format and procedure prescribed by NMFS.
Sample 1

Related to Sector Hails/Reporting

  • Sales Reporting Requirements This is a requirement of the TIPS Contract and is non-negotiable. By submitting this proposal, Vendor certifies that Vendor will properly report all TIPS sales. With the exception of TIPS Automated Vendors, who have signed an exclusive agreement with TIPS regarding reporting, all TIPS Sales must be reported to TIPS by either: (1) Emailing the purchase order or similar purchase document (with Vendor’s Name, as known to TIPS, and the TIPS Contract Name and Number included) to TIPS at xxxxxx@xxxx-xxx.xxx with “Confirmation Only” in the subject line of the email within three business days of Vendor’s acceptance of the order, or; (2) Within 3 business days of the order being accepted by Vendor, Vendor must login to the TIPS Vendor Portal and successfully self-report all necessary sale information within the Vendor Portal and confirm that it shows up accurately on your current Vendor Portal statement. No other method of reporting is acceptable unless agreed to by the Parties in writing. Failure to report all sales pursuant to this provision may result in immediate cancellation of Vendor’s TIPS Contract(s) for cause at TIPS’ sole discretion.

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

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11165.7, AB 1432, and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • Time Reporting ‌ The Employer may require employees to accurately report time worked in accordance with a positive time reporting process as determined by the Agency.

  • CONTRACT SALES REPORTING Contractor shall report total contract sales quarterly to Enterprise Services, as set forth below.

  • MASTER CONTRACT SALES REPORTING Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below.

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

  • Program Reporting Contractor shall provide such data as may be required by the Board, in the form required by the Board to fulfill its obligations as a public school district, as well as academic, financial and other program records and reports as requested by the Board for program accreditation, monitoring, payment, and auditing. Such data and reports shall include, but not be limited to, all of the following:

  • Required Vendor Sales Reporting By responding to this Solicitation, you agree to report to TIPS all sales made under any awarded Agreement with TIPS. Vendor is required to report all sales under the TIPS contract to TIPS. If the TIPS Member entity requesting a price from the awarded Vendor requests the TIPS contract, Vendor must include the TIPS Contract number on any communications with the TIPS Member entity. If awarded, you will be provided access to the Vendor Portal. To report sales, login to the TIPS Vendor Portal and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS.

  • 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: For Calendar Quarter Ending Master Contract Sales Report Due 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 0.74 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 .0074. 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.

Time is Money Join Law Insider Premium to draft better contracts faster.