Fishery Observer/At-Sea Monitor III - The Fishery Observer Sample Clauses

Fishery Observer/At-Sea Monitor III - The Fishery Observer. At-Sea Monitor
AutoNDA by SimpleDocs
Fishery Observer/At-Sea Monitor III - The Fishery Observer. At-Sea 41 Monitor III shall meet and perform all the General Requirements 42 specified in C.4.3.2a, perform all duties of Fishery observer/At-Sea 43 Monitor II and the following additional duties: 44 May act as field coordinator of lower graded fishery observer/At-Sea 45 Monitors. 46 Demonstrates extensive familiarity of methods, procedures and 47 management to ensure proper day-to-day operations. 48 Shifts from one type of responsible technical assignment to other 49 types, which are different in terms of equipment used, of data 50 used, and uses to which data will be put. 51 Makes estimates of amounts and species composition of fish caught, 52 retained and discarded, utilizing knowledge of various 53 statistically valid sampling, sub-sampling methods and 54 dichotomous keys. 55 According to established standards and detailed procedures, records 56 data on appropriate forms and logs, some of which may be 57 electronic and provide recommendations for updates.

Related to Fishery Observer/At-Sea Monitor III - The Fishery Observer

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • STUDENT DIRECTORY INFORMATION Upon enrolling in the Dual Credit program, each Student’s general directory information (defined by the College, pursuant to FERPA, to exclude student addresses) will become part of the College’s student general directory information, and will be subject to the Texas Public Information Act.

  • Engagement of the TAM Representative Outside of Red Hat Standard Business Hours If you have purchased Premium Red Hat Software Subscriptions, you will receive 24x7 Support for Severity 1 and 2 issues through Red Hat’s 24x7 Production Support teams and not necessarily from your assigned TAM representative. Red Hat’s 24x7 Production Support team will be responsible for addressing issues, but will consult with your TAM representative, as your TAM representative is available, for advice and to gain a better understanding of your infrastructure, environment and specific needs. If you have purchased multiple TAM Service Subscriptions in each of Red Hat’s primary Support Regions, you will receive the benefit of extended TAM Service coverage hours, but you should follow the same process and contact the Red Hat 24x7 support numbers at xxxxx://xxxxxx.xxxxxx.xxx/support/contact/technicalSupport.html.

  • How Non-network Providers Are Paid If you receive care from a non-network provider, you are responsible for paying all charges for the services you received. You may submit a claim for reimbursement of the payments you made. For the limited circumstances listed below, your copayment and deductible will apply at the network level of benefits: • emergency care (emergency room, urgent care and ambulance services); • we specifically approve the use of a non-network provider for covered healthcare services, see Network Authorization in Section 5 for details; • covered healthcare services are rendered by a non-network provider at a network facility outside of your control; • otherwise, as required by law. For those circumstances where we cover services from a non-network provider, we reimburse you or the non-network provider, less any copayments and deductibles, up to the lesser of: • our allowance; • the non-network provider’s charge; or • the benefit limit. You are responsible for the deductible, if one applies, and the copayment, as well as any amount over the benefit limit that applies to the service you received. You are liable for the difference between the amount that the non-network provider bills and the payment we make for covered healthcare services. Generally, we send reimbursement to you, but we reserve the right to reimburse a non-network provider directly. We reimburse non-network provider services using the same guidelines we use to pay network providers. Generally, our payment for non-network provider services will not be more than the amount we pay for network provider services. If an allowance for a specific covered healthcare service cannot be determined by reference to a fee schedule, reimbursement will be based upon a calculation that reasonably represents the amount paid to network providers. For emergency services, we reimburse non- network providers, in accordance with R.I. Gen. Laws § 27-18-76, the greater of our allowance, our usual guidelines for paying non-network providers, or the amount that would be paid under Medicare, less any copayments or deductibles. Payments we make to you are personal. You cannot transfer or assign any of your right to receive payments under this agreement to another person or organization, unless the R.I. General Law §27-20-49 (Dental Insurance assignment of benefits) applies. For information about network authorization requests to seek covered healthcare services from a non-network provider when the covered healthcare service cannot be provided by a network provider, please see Network Authorization in Section 5.

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Observers One or more non-voting observers to the Board and/or its committees may be selected by the Shareholders. Any such observer shall hold such position until the observer’s successor is selected, or until the observer’s resignation or removal. An observer may resign by written notice to the Corporation. The resignation is effective on its receipt by the Corporation or at a subsequent time as set forth in the notice of resignation. Subject to the provisions of any Shareholder Agreement, an observer may be removed, with or without cause, by the Shareholders, and thereupon the term of the observer who shall have been so removed shall forthwith terminate. Each observer shall be entitled to attend all meetings (including telephonic meetings) of the Board and the Board’s committees to which it has been granted observer rights. Each observer shall be entitled to receive (x) notices of all meetings of the Board and the Board’s committees to which it has been granted observer rights and (y) all information delivered to the members of the Board and the Board’s committees to which it has been granted observer rights in connection with such meetings, in each case to the extent and at the same time such notice and information is delivered to the members of the Board and its committees. Notwithstanding the foregoing, the Chairperson of the Board (if the office is filled) or the President & CEO shall (a) excuse any observer from any portion of a Board meeting or a meeting of its committees to the extent such observer’s participation in such meeting is reasonably likely to adversely affect the attorney/client privilege of the Corporation and its legal advisors and (b) withhold information from any observer delivered to the Board and the Board’s committees to which it has been granted observer rights prior to a meeting of the Board or, as the case may be, such committee, in each case if the Chairperson of the Board (if the office is filled) or the President & CEO believes there is a reasonable likelihood that the receipt of such information by the observer may adversely affect the attorney/client privilege of the Corporation and its legal advisors.

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • LICENSE HOLDER CONTACT INFORMATION This noƟce is being provided for informaƟon purposes. It does not create an obligaƟon for you to use the broker’s services. Please acknowledge receipt of this noƟce below and retain a copy for your records. Davidson Bogel Real Estate, LLC 9004427 xxxx@xx0xx.xxx 214-526-3626 Licensed Broker /Broker Firm Name or Primary Assumed Business Name License No. Email Phone Xxxxxxx Xxxxxx Xxxxx XX 598526 xxxxxx@xx0xx.xxx 214-526-3626 Designated Broker of Firm License No. Email Phone Xxxxxxxxxxx Xxxx Xxxxxx 672133 xxxxxxx@xx0xx.xxx 214-526-3626 Licensed Supervisor of Sales Agent/ Associate License No. Email Phone N/A N/A N/A N/A Sales Agent/Associate’s Name License No. Email Phone Buyer/Tenant/Seller/Landlord Initials Date Regulated by the Texas Real Estate Commission InformaƟon available at xxx.xxxx.xxxxx.xxx

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

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