Sector Hails/Reporting Clause Samples

The 'Sector Hails/Reporting' clause establishes the requirement for parties to communicate or report their positions, intentions, or statuses within designated sectors or operational areas. Typically, this involves notifying relevant authorities or counterparties when entering, exiting, or operating within specific zones, such as maritime sectors or airspace regions. By mandating timely and accurate reporting, the clause enhances situational awareness, promotes safety, and ensures compliance with regulatory or operational protocols.
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
View SourceView Similar (3)
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.
View SourceView Similar (3)
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. 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. Alternative standards for trips that are at least 6 hours may be implemented 33 during the 2010 fishing year if agreed upon by the sector, the monitoring provider, and 36 In accordance w...
View SourceView Similar (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.
View SourceView Similar (2)
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...
View SourceView Similar (2)
Sector Hails/Reporting. Consistent with Exhibit G, each Participating Vessel operator must send a trip start hail when required by GARFO and a trip end hail six hours before arrival, or immediately upon leaving the fishing grounds if fishing ends less than six before landing. An alternative timing for the trip end hail may be implemented during the 2023 and 2024 fishing years if agreed upon by the sector, sector monitoring provider, and GARFO.
View SourceView Similar (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.
View Source
Sector Hails/Reporting. Consistent with Exhibit E, each Participating 39 Vessel operator will provide a trip endhailupon completion of the last tow. An alternative 40 timing for the trip end hail may be implemented during the 2012 fishing year if agreed 41 upon by the sector, sector monitoring provider, and NMFS. 43 The trip end hail will also be sent as an email through VMS to the sector manager, the 44 message will contain: the vessel permit #, trip ID # (VTR number on the first VTR page), 45 intended offloading location(s) including the dock or dealer, port or harbor and the state. 46 This message will also contain estimated date and time of arrival, estimated date and time 1 of offload, estimated total amount of regulated species, and estimated total weight of each 4 In accordance with and defined by Amendment 16, all Sector vessels will also be 5 required to make a declaration to NMFS via VMS prior to departing port identifying 6 whether they intend to fish in one broad reporting area or multiple reporting areas. 7 Vessels that fish in multiple areas will be required to provide additional daily reports to 8 NMFS as required by Amendment 16. 10 The sector will submit required reports using the format and procedure prescribed by 11 NMFS.
View Source

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 ▇▇▇▇▇▇@▇▇▇▇-▇▇▇.▇▇▇ 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 a) RECIPIENT must satisfactorily demonstrate the timely use of funds by submitting payment requests and progress reports to ECOLOGY. ECOLOGY reserves the right to amend or terminate this Agreement if the RECIPIENT does not document timely use of funds. b) RECIPIENT must submit a progress report with each payment request. Payment requests will not be processed without a progress report. ECOLOGY will define the elements and frequency of progress reports. c) RECIPIENT shall use ECOLOGY’s provided progress report format. d) Quarterly progress reports will cover the periods from January 1 through March 31, April 1 through June 30, July 1 through September 30, and October 1 through December 31. Reports shall be submitted within thirty (30) days after the end of the quarter being reported. e) RECIPIENT must submit within thirty (30) days of the expiration date of the project, unless an extension has been approved by ECOLOGY, all financial, performance, and other reports required by the Agreement and funding program guidelines. RECIPIENT shall use the ECOLOGY provided closeout report format.

  • 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 11164 et seq. 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.

  • CONTRACT SALES REPORTING Contractor shall report total Contract sales quarterly to Enterprise Services, as set forth below. (a) Contract Sales Reporting System. Contractor shall report quarterly Contract sales in Enterprise Services’ 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. (b) 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 Contract. If there are no Contract sales during the reporting period, Contractor must report zero sales. (c) Due dates for Contract Sales Reporting. Quarterly Contract Sales Reports must be submitted electronically by the following deadlines for all Contract sales invoiced during the applicable calendar quarter: Quarter For Sales Made In Calendar Quarter Ending Contract Sales Report

  • Management Reporting (a) Provide periodic reports, in accordance with agreed upon frequency and content parameters, to the Funds. As reasonably requested by the Funds, the Transfer Agent shall furnish ad hoc reports to the Funds.