ESA and NHPA requirements Sample Clauses

ESA and NHPA requirements. All project activities are to be conducted in full compliance with the Endangered Species Act (ESA) and National Historic Preservation Act (NHPA). The project manager shall be responsible for providing the EPA‘s Project Officer all of the necessary documentation to expedite review under ESA and NHPA if required at any time during this project. This information includes, but is not limited to, location of project activities, any threatened or endangered species or habitat which may be affected by the project, whether a site is considered to be of concern by the State Historic Preservation Officer, a list of Tribes who may believe the site or project could disturb cultural resources, and an evaluation as to whether project plans could have adverse effects on endangered species or historic and cultural resources. The contractor will be required to contact local Tribes before digging, sampling, or performing other Phase II assessment work.
Sample 1
AutoNDA by SimpleDocs
ESA and NHPA requirements. The objective of this subtask is to ensure that all project activities are conducted in full compliance with the Endangered Species Act (ESA) and National Historic Preservation Act (NHPA). The Coalition’s Project Manager shall be responsible for providing the EPA’s Project Officer all of the necessary documentation to expedite review under ESA and NHPA if required at any time during this project. This information includes but is not limited to the location of the project, any threatened or endangered species or habitat which may be affected by the project, whether the site is considered to be of concern by the State Historic Preservation Officer, a list of Tribes who may believe the site or project could disturb cultural resources, and an evaluation as to whether project plans could have adverse effects on endangered species or historic and cultural resources. Since a majority of the proposed sites will be located in the downtown and Legacy Crossing areas, the Coalition expects that the impact of ESA and NHPA review for the project will be minimal. The Coalition will provide the required information for ESA and NHPA review without requesting reimbursement for any expenses. In such case where the Coalition’s selected environmental consultant(s) provides review information as a course of conducting an environmental assessment, those costs will be funded as determined through the Phase I and Phase II assessment sub tasks. Specific milestones and deliverables for this subtask include:  Minimum five (5) completed ESA and NHPA determinations from EPA on sites prior to Phase II assessment activities.
Sample 1
ESA and NHPA requirements. ESA and NHPA project review requirements may have been satisfied during the TBA process. Further, the site location in mid-town Anchorage, its known site use over the last 50 years, and the recently completed demolition activities at the site suggest that the cleanup project will not be restricted due to ESA or NHPA considerations. However, MOA and/or its contractors will be prepared to assist EPA in further assessing if the project may adversely affect threatened or endangered species, if the site is of interest to the State Historical Preservation Office, or if the site has cultural value to a local Tribal entity. The following preliminary information is presented towards this end. The U.S. Fish and Wildlife Service’s (USFWS) on-line Threatened and Endangered Species database System (TESS) lists 17 species for the state of Alaska, including nine marine mammals, four bird species, three sea turtles, and one plant species. The USFWS’ April 2007 list of “Endangered, Threatened, Proposed, Candidate and De-Listed Species in Alaska” for non-marine species consists of four bird species, one otter, and one plant species. Of these species, only two have designated critical habitat. Critical habitat for the Spectacled eider is described as being in western and northwestern Alaska (Coastal) while the critical habitat for the Xxxxxxx'x xxxxx also includes southwestern and northern Alaska. Based on this information the project site is therefore not located within a critical habitat for any of the listed threatened or endangered species for Alaska. No funding from Grant Support or Cost Share will be expended for this portion of Task 3.
Sample 1
ESA and NHPA requirements. The objective of this subtask was to ensure that all project activities were conducted in full compliance with the Endangered Species Act (ESA) and National Historic Preservation Act (NHPA). The Coalition was responsible for providing the EPA’s Project Officer all of the necessary documentation to expedite review under ESA and NHPA if required at any time during this project. This information included but was not limited to the location of the project, any threatened or endangered species or habitat which may be affected by the project, whether the property was of concern by the State Historic Preservation Officer, a list of Tribes who may believe the property or project could disturb cultural resources, and an evaluation as to whether project plans could have adverse effects on endangered species or historic and cultural resources. Since many of the proposed properties were in the downtown and Legacy Crossing areas the Coalition provided the required information for ESA and NHPA review without requesting reimbursement for any expenses. In such case where the Coalition’s selected environmental consultant(s) provides review information as a course of conducting an environmental assessment, those costs where funded as determined through the Phase I and Phase II ESA sub tasks.
Sample 1
ESA and NHPA requirements. In order to assist EPA in meeting requirements under the Endangered Species Act (ESA) and National Historic Preservation Act (NHPA), and to prevent delays in the work plan, City staff with assistance from the EC will provide the following information to EPA prior to conducting field activities associated with the Phase II ESA: the location of the project, any threatened or endangered species or habitat which may be affected by the project, whether the site is considered to be of concern by the State Historic Preservation officer (SHPO), a list of Tribes who may believe the site or project could disturb cultural resources, and an evaluation as to whether the plans could have adverse effects on endangered species or cultural resources. In order to do so, City with the EC will send a letter to the SHPO and the Army Corps of Engineers as well as any surrounding Confederated Tribes 30 days prior to submittal to EPA of proposed Phase II activities. The project manager will act as staff lead and communicate with our EPA Project Officer to receive any additional guidance needed on this topic.
Sample 1

Related to ESA and NHPA requirements

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • Tax Requirements The Participant is hereby advised to consult immediately with his or her own tax advisor regarding the tax consequences of this Agreement. The Company or, if applicable, any Subsidiary (for purposes of this Section 28, the term “Company” shall be deemed to include any applicable Subsidiary), shall have the right to deduct from all amounts hereunder paid in cash or other form, any Federal, state, local, or other taxes required by law to be withheld in connection with this Award. The Company may, in its sole discretion, also require the Participant receiving shares of Common Stock issued under the Plan to pay the Company the amount of any taxes that the Company is required to withhold in connection with the Participant’s income arising with respect to this Award. Such payments shall be required to be made when requested by the Company and may be required to be made prior to the delivery of any certificate representing shares of Common Stock. Such payment may be made (i) by the delivery of cash to the Company in an amount that equals or exceeds (to avoid the issuance of fractional shares under (iii) below) the required tax withholding obligations of the Company; (ii) if the Company, in its sole discretion, so consents in writing, the actual delivery by the exercising Participant to the Company of shares of Common Stock other than (A) Restricted Stock, or (B) Common Stock that the Participant has not acquired from the Company within six (6) months prior to the date of exercise, which shares so delivered have an aggregate Fair Market Value that equals or exceeds (to avoid the issuance of fractional shares under (iii) below) the required tax withholding payment; (iii) if the Company, in its sole discretion, so consents in writing, the Company’s withholding of a number of shares to be delivered upon the exercise of the Stock Option other than shares that will constitute Restricted Stock, which shares so withheld have an aggregate fair market value that equals (but does not exceed) the required tax withholding payment; or (iv) any combination of (i), (ii), or (iii). The Company may, in its sole discretion, withhold any such taxes from any other cash remuneration otherwise paid by the Company to the Participant.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Time Requirements The Independent Contractor will not be required to follow or establish a regular or daily work schedule, but shall devote during the term of this Agreement the time, energy and skill as necessary to perform the services of this engagement and shall, periodically or at any time upon the request of the Company, submit information as to the amount of time worked and scope of work performed.

  • Health Requirements A. Provider shall remain in compliance with all applicable federal, state, county, and municipal, statutes, laws, ordinances, regulations, and guidelines, as well as any Board guidelines, policies, and rules in effect now or later, and as amended from time to time related to COVID-19. B. Provider shall comply with evolving requirements to protect the health and safety of Student Participants and staff, as expressed in local, and state guidance from various government agencies. This includes, but is not limited to, adhering to all health and safety guidelines issued by CPS, IDPH, and CDPH related to COVID-19. Provider acknowledges these health and safety guidelines are subject to change. C. Required health and safety practices may vary across age groups and settings. Provider shall comply, at a minimum, with all health and safety mandates issued by the State of Illinois and the City of Chicago and guidance from the Illinois State Board of Education (“ISBE”). D. Under Chicago’s March 19 Public Health Order, congregate facilities (such as long-term care facilities, childcare settings, correctional facilities, etc.) must immediately report to CDPH clusters of COVID-19 patients, defined as two or more confirmed cases of COVID-19 occurring within 14 calendar days of each other at a facility. To report positive cases, Provider must complete the COVID-19 Online Case Report Form found at the following website: xxxxx://xxxxxx.xxx.xxxxxxxx.xxx/surveys/?s=FR7MAJAY84. A copy of the current COVID-19 Online Case Report Form is attached and incorporated into this Supplemental Scope as Attachment A. Provider must also comply with additional operational, reporting and tracing requirements established by CPS. E. As of July 13, 2020, interim guidance issued by CDPH encourages notification for every COVID-19 case. For more information, see CDPH Interim Guidance on Management of COVID 19 Cases in Childcare Settings (“CDPH Guidance”) at the following link: https://xxx.xxxxxxx.xxx/content/dam/city/depts/cdph/HealthProtectionandResponse/Interim% 20Guidance%20on%20Management%20of%20COVID 19%20Cases%20in%20Childcare%20Settings%2007.13.

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

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