Interagency Project Scoping Sample Clauses

Interagency Project Scoping. Effective and early interagency collaboration and cooperation are crucial to the success of the one shared analysis process. Initiation of project coordination and the formal designation of a Project Coordinator are described in Section II. If the steps described in Section II.B have not been taken, they should occur as part of project scoping. During early scoping and consultation, Project Coordinators will identify the issues and concerns listed in Section II.B.2.e. to the maximum extent possible. The Project Coordinators will also identify the decisions that are required by their agency in order for the project to move forward, and whether additional analysis is necessary for these decisions. These needs will be addressed in the analysis done for the project. In identifying the decisions required, the Project Coordinators will identify the anticipated level of NEPA required for their agency to support the decision: Categorical Exclusion (CE), Environmental Assessment (EA), or EIS. Agencies will cooperate in addressing issues as early as possible to identify information needs and avoid late- arising concerns. Resolution of issues will be documented in agency files for reference and consistency through the life of the project.
AutoNDA by SimpleDocs
Interagency Project Scoping. Effective and early interagency cooperation is crucial to the success of the One Shared Analysis process. Initiation of project coordination and the formal designation of a Project Coordinator are described in Section 4 Project Coordination. If the steps described in Section 4 have not been taken, they should occur as part of project scoping. 1. During early scoping and consultation, Project Coordinators will identify to the maximum extent possible: a. Potential inconsistencies with land management plans. b. Anticipated social, economic, and environmental impacts. c. Travel demand estimates of the highway, forest system, or NFS/Public Lands road. d. Potential recreation sites and activities, physical and permitted. e. Endangered, threatened, proposed, or sensitive species inventories, biological evaluations, and biological assessment requirements. f. Existing and potentially needed wildlife crossings or fish passage. g. Potential historic properties, or other resources that will be protected under Section 4(f) (23 U.S.C. 138, 49 U.S.C. 303). h. Public lands survey monuments, location and protection. i. Potential staging, stockpile or storage areas. j. Timber clearing, means of removal and appraisal. k. Material sources disposal sites and borrow pits. l. Public involvement requirements for each agency. m. Other issues of special concern. 2. The Project Coordinators will also identify the decisions that are required by their agency in order for the project to move forward, and whether additional analysis is necessary for these decisions. These needs will be addressed in the analysis done for the project. 3. In identifying the decisions required, the Project Coordinators will identify the anticipated level of NEPA required for their agency to support the decision: categorical exclusion, environmental assessment or environmental impact statement. 4. The lead agency will ensure that the clearances received for the transportation project inclu de the regulatory requirements of other agencies who are not party to this MOU, including, but not limited to, ESA Section 7 Consultation with the U.S. Fish and Wildlife Service, a Section 404 under the Clean Water Act permit from the U.S. Army Corps of Engineers, and Section 106 of the National Historic Preservation Act consultation with the State Historic Preservation Office. 5. Agencies will cooperate in addressing issues as early as possible to identify information needs and avoid late-arising concerns. Resolution of i...

Related to Interagency Project Scoping

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • E-Verify Program Grantee certifies that it utilizes and will continue to utilize the U.S. Department of Homeland Security's E-Verify system to determine the eligibility of: A. all persons employed to perform duties within Texas during the term of the Grant Agreement; and B. all persons, (including subcontractors) assigned by the Grantee to perform work pursuant to the Grant Agreement within the United States of America.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master 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. 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 Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • EDD Independent Contractor Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the state.” The term is further defined by the California Employment Development Department to refer specifically to independent Contractors. An independent Contractor is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • Safety Program The Contractor shall design a specific safety program for the Work for the site(s). The Contractor shall establish and require all Subcontractors to establish reasonable safety programs. The Contractor shall also submit its standard monthly safety reports to the Owner and Design Professional. No imposition of responsibility on the Contractor for safety under this Contract shall relieve any subcontractor of its responsibility for safety of persons or property on or near the Project Site. The Contractor shall include in his plant he names of the person in charge of Safety.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

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