SAFE HARBOR PROTOCOL Sample Clauses

SAFE HARBOR PROTOCOL. To promote safety at sea, the Sector sets forth the following protocol for variance from the landing ports listed. If for reasons beyond a vessel operators control such as severe weather, mechanical failures, compromised hull integrity, instances of pump failures and danger of sinking, crew injury or life threatening illness and any other emergency situations that may arise, a sector vessel may enter a port other than those listed as “Landing Ports” to ensure the safety of the vessel and it’s crew. If the vessel has been selected for dockside monitoring, the vessel will not offload fish, until a dockside monitor is present, or a waiver has been granted. The vessel operator must contact the Dockside Monitoring vendor to obtain a waiver from dockside monitoring for the trip. The vessel operator may request and be granted a waiver from dockside monitoring due to the situations described here in Section 23.7. In addition, the vessel operator may request and be granted a waiver from dockside monitoring if either the Coast Guard (“CG”), Environmental Police (“EP”), or NOAA’s Office of Law Enforcement (“OLE”) are on scene and determine it is necessary for offloading to occur in order to improve a safety or vessel integrity concern.
Sample 1Sample 2Sample 3See All (18)
AutoNDA by SimpleDocs
SAFE HARBOR PROTOCOL. To promote safety at sea, the Sector sets forth the following protocol for 3 variance from the landing ports listed. If for reasons beyond a vessel operators control such as 4 severe weather, mechanical failures, compromised hull integrity, instances of pump failures and 5 danger of sinking, crew injury or life threatening illness and any other emergency situations that 6 may arise, a sector vessel may enter a port other than those listed as “Landing Ports” to ensure the 7 safety of the vessel and its crew. In the event that a Sector Vessel must utilize this safe harbor
Sample 1Sample 2Sample 3See All (14)
SAFE HARBOR PROTOCOL. 17 To promote safety at sea, the Sector sets forth the following protocol for variance from 18 the landing ports listed. If for reasons beyond a vessel operator’s control such as severe 19 weather, mechanical failures, compromised hull integrity, instances of pump failures and 20 danger of sinking, crew injury or life threatening illness and any other emergency 21 situations that may arise, a sector vessel may enter a port other than those listed as 22 “Landing Ports” to ensure the safety of the vessel and its crew. In the event that a Sector 24 OLE of when and where they had to seek safe harbor within 6 hours of this entering the 25 port. 27 2.3. Administrative
Sample 1Sample 2See All (6)
SAFE HARBOR PROTOCOL. To promote safety at sea, the sector sets forth the following protocols for 3 variance from the landing ports listed. If for reasons beyond a vessel operators control such as 4 severe weather, mechanical failures, compromised hull integrity, instances of pump failures and 5 danger of sinking, grew injury or life threatening illness and any other emergency situations that 6 may arise, a sector vessel may enter a port other than those listed as “Landing Ports” to ensure the 7 safety of the vessel and its crew. In the event that a sector vessel must utilize this safe harbor 8 protocol, they must notify the sector manager and NMFS OLE of when and where they had to 3 Prohibition on combining small-mesh exempted fishery and sector trips 5 The exemption applies to sector trips only and is intended to allow a vessel to catch small-mesh species 6 after targeting groundfish. Under this exemption, a sector vessel must fish with trawl nets that meet 7 current regulatory requirements and sector exemptions during the first part of the trip, but may switch to 8 modified small-mesh gear for the second portion of the trip. The small-mesh portion of the trip must be 9 fished in the Sector Small-Mesh Fishery Exemption Area, described below, and must use the modified 10 small-mesh gear described below. A vessel may land xxxxxxx, longfin squid, mackerel, xxxxxxx and other 11 species permitted for retention in small-mesh exempted fisheries, provided the vessel still meets the 12 requirements of those fisheries. For more information on small-mesh fishery exemptions and permitted 13 species see: 14 xxxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxxx.xxx/regs/infodocs/small_mesh_exemptions.pdf 15 Vessels may not fish the small-mesh portion of their trip using this exemption in the Southern 16 Windowpane Accountability Measure Areas, where they overlap with the exemption area. 1 • A drop chain sweep with a minimum drop of 12 inches (30.48 cm) in length, with a 24 inch 2 headrope setback; or 4 • A large mesh belly panel with a minimum mesh size of 32 inches (81.28 cm), with the meshes 5 hung on the half (hanging ration of 2:1); or 7 • An excluder grate secured forward of the codend with an outlet hole forward of the grate with bar 8 spacing no more than 1.97 inches (5.00 cm) wide. 10 In order to use this exemption, the following additional conditions and restrictions apply:
Sample 1Sample 2See All (5)
SAFE HARBOR PROTOCOL. To promote safety at sea, the Sector sets forth 12 the following protocol for variance from the landing ports listed. If for reasons 13 beyond a vessel operators control such as severe weather, mechanical failures, 14 compromised hull integrity, instances of pump failures and danger of sinking, 15 crew injury or life threatening illness and any other emergency situations that may 16 arise, a sector vessel may enter a port other than those listed as “Landing Ports” to 17 ensure the safety of the vessel and its crew. In the event that a Sector Vessel must 18 utilize this safe harbor protocol, they must notify their Manager and NMFS OLE 19 of when and where they had to seek safe harbor within 6 hours of this entering the 20 port. 24 2.3.1. Fishing in US/CA Areas 25 26 Sector participating vessels may fish in the both the Eastern and Western 27 US/Canada Areas. When reporting their catch to the Sector Manager, the 28 operators of all Sector member vessels will specify the volume of catch 29 and discards from each area. 30 31 Members electing to enter the Eastern US/CA area are required to comply 32 with the observer notification reporting and VMS reporting requirements 33 for that area.
Sample 1
SAFE HARBOR PROTOCOL. To promote safety at sea, the Sector sets forth the following protocol for variance from the landing ports listed. If for reasons beyond a vessel operators control such as severe weather, mechanical failures, compromised hull integrity, instances of pump failures and danger of sinking, crew injury or life threatening illness and any other emergency situations that may arise, a sector vessel may enter a port other than those listed as “Landing Ports” to ensure the safety of the vessel and its crew. In the event that a Sector Vessel must utilize this safe harbor protocol, they must notify their Manager and NMFS OLE of when and where they had to seek safe harbor within 6 hours of this entering the port.
Sample 1
SAFE HARBOR PROTOCOL. To promote safety at sea, the Sector sets forth the following protocol 16 for variance from the landing ports listed. If for reasons beyond a vessel operators control such as 17 severe weather, mechanical failures, compromised hull integrity, instances of pump failures and 18 danger of sinking, crew injury or life threatening illness and any other emergency situations that 19 may arise, a sector vessel may enter a port other than those listed as “Landing Ports” to ensure the 20 safety of the vessel and its crew. In the event that a Sector Vessel must utilize this safe harbor 22 harbor within 6 hours of this entering the port.
Sample 1
AutoNDA by SimpleDocs

Related to SAFE HARBOR PROTOCOL

  • Safe Harbor Provisions This Section 24.1 is applicable only to Generation Interconnection Customers. Provided that Interconnection Customer agrees to conform to all requirements of the Internal Revenue Service (“IRS”) (e.g., the “safe harbor” provisions of IRS Notice 2016-36, 2016-25 I.R.B. (6/20/2016)) that would confer nontaxable status on some or all of the transfer of property, including money, by Interconnection Customer to the Interconnected Transmission Owner for payment of the Costs of construction of the Transmission Owner Interconnection Facilities, the Interconnected Transmission Owner, based on such agreement and on current law, shall treat such transfer of property to it as nontaxable income and, except as provided in Section 24.4.2 below, shall not include income taxes in the Costs of Transmission Owner Interconnection Facilities that are payable by Interconnection Customer under the Interconnection Service Agreement or the Interconnection Construction Service Agreement. Interconnection Customer shall document its agreement to conform to IRS requirements for such non-taxable status in the Interconnection Service Agreement, the Interconnection Construction Service Agreement, and/or the Interim Interconnection Service Agreement.

  • Safe Harbor The recipient government will then compare the reporting year’s actual tax revenue to the baseline. If actual tax revenue is greater than the baseline, Treasury will deem the recipient government not to have any recognized net reduction for the reporting year, and therefore to be in a safe harbor and outside the ambit of the offset provision. This approach is consistent with the ARPA, which contemplates recoupment of Fiscal Recovery Funds only in the event that such funds are used to offset a reduction in net tax revenue. If net tax revenue has not been reduced, this provision does not apply. In the event that actual tax revenue is above the baseline, the organic revenue growth that has occurred, plus any other revenue-raising changes, by definition must have been enough to offset the in-year costs of the covered changes.

  • System for Award Management (XXX) Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a XXX.xxx proof of registration and Commercial and Government Entity (CAGE) number. Grantee will continue to maintain an active XXX registration with current information at all times during which it has an active award under this Agreement.

  • Switching and Tagging Rules Each Party shall provide the other Parties a copy of its switching and tagging rules that are applicable to the other Parties’ activities. Such switching and tagging rules shall be developed on a non-discriminatory basis. The Parties shall comply with applicable switching and tagging rules, as amended from time to time, in obtaining clearances for work or for switching operations on equipment.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing iNetworks traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to iNetworks, the subtending arrangements between iNetworks Tandems and iNetworks End Offices shall be the same as the Tandem/End Office subtending arrangements that iNetworks maintains for the routing of its own or other carriers’ traffic.

  • Code “Code” means the Internal Revenue Code of 1986, as amended.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Loop Testing/Trouble Reporting 2.1.6.1 TeleConex will be responsible for testing and isolating troubles on the Loops. TeleConex must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, TeleConex will be required to provide the results of the TeleConex test which indicate a problem on the BellSouth provided Loop.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

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