ESA and NHPA requirements Sample Clauses

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 5 completed ESA and NHPA determinations from EPA on sites prior to Phase II assessment activities.
Sample 1
AutoNDA by SimpleDocs
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
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. Specific deliverables for this task concluded with the following:
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
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. Specific deliverables for this task concluded with the following:  Six (6) completed ESA and NHPA determinations from EPA on properties prior to Phase II ESA activities. Candidate Property Identification The objective of this subtask was to provide a methodology for the selection and review of properties that will receive EPA funds through this project. As noted in the previous subtask, an initial inventory of properties was conducted during the grant application phase. This inventory led to the selection of six (6) initial properties that were identified and proposed for assessment. The grant included $375,750 for Hazardous Substances and $99,950 for Petroleum Substances for training, community outreach, hazardous waste assessment, and cleanup planning. Five (5) of the six (6) properties utilized hazardous waste funding and one utilized petroleum funds. See Appendix B on Page 25 for six (6) Summary Property Reports and Photos. Overall, the funded grant activities included contracting with two environmental consulting firms who completed the following project activities and deliverables: o Prepared a Master Quality Assurance Project Plan (QAPP). o Six (6) Individual QAPP and four (4) Q...
Sample 1

Related to ESA and NHPA requirements

  • HIPAA Requirements The Parties agree that the provisions under HIPAA Rules that are required by law to be incorporated into this Amendment are hereby incorporated into this Agreement.

  • 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. Item Not Received additional requirements 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 7.4.1 Workers’ 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.

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

  • TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.

  • 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 This is an active trip that requires you to make a realistic assessment of your health. To enjoy the trips as intended, a minimum level of fitness is required. All Participants are expected to be in active good health, to be comfortable traveling as part of a group, and to be ready to experience cultural differences with grace. Air Journey will require prior notice if any participant has any physical or other condition or disability that would prevent them from participating in active elements of any trip and/or could create a hazard to him or herself or to other members of the group. Air Journey may require guests to produce a doctor’s certificate certifying that they are fit to participate. Any physical condition requiring special attention, diet, or treatment should be reported in writing when the reservation is made. We will make reasonable efforts to accommodate Participants with special needs; however, we cannot accommodate wheelchairs. . Walking and climbing stairs are required in many hotels and airports, and are part of many excursions. If you require a slower pace, extra assistance, or the use of a cane or walking stick, arrangements will be made for private touring at each destination, if necessary, at the discretion of our Journey staff. Any extra cost for such arrangements will be the responsibility of the Participant. If you would like to forego some of the scheduled sightseeing to rejuvenate and relax, please feel free to do so at any time. Acting reasonably, if Air Journey is unable to properly accommodate the need of the person(s) concerned or believes that health and safety may be compromised, Air Journey reserves the right to refuse participation. Air Journey also reserves the right to remove from the trip, at the participant’s own expense, anyone whose physical condition or conduct negatively impacts the enjoyment of the other guests or disrupts the tour. Malaria and other diseases may be present in some of the countries featured in this itinerary; proof of yellow fever inoculation may be required. For the latest recommendations on specific health precautions for the areas you will visit, consult your physician and the Centers for Disease Control. The participant represents that neither he nor she nor anyone traveling with him or her has any physical or other condition or disability that could create a hazard to himself or herself or other members of the tour. Itinerary Changes The itinerary and Journey leaders are subject to modification and change by Air Journey. Every reasonable effort will be made to operate the Journey as planned; however, should unforeseen world events and conditions require our itinerary to be altered, Air Journey reserves the right to do so for the safety and best interest of the group without prior notification or consultation. The operation of these flights is subject to the foreign governments involved granting landing rights for the flight. If the air carrier cannot obtain these rights for any particular flight leg of the Journey, that flight leg will be canceled and alternative arrangements may be made, at the discretion of Air Journey. Every effort will be made to operate tours as planned but alterations may occur after the final itinerary has been issued.

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

  • Local Law Requirements Spain. With respect to Customers domiciled in Spain, in the event of any conflict between any statutory law in Spain applicable to Customer, and the terms and conditions of this Agreement, the applicable statutory law shall prevail.

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