Project Area Statistics Sample Clauses

Project Area Statistics. For all projects, provide an estimate of the Project Influence Zone (PIZ) acres and the Treatment Influence Zone (TIZ) acres.
AutoNDA by SimpleDocs
Project Area Statistics. For all projects, give an estimate of the project area size and include an estimate of the number of habitable structures impacted by the project. Provide the size of the treatment area for projects that include fuels treatment. LRA FRA SRA Habitable Dwellings (# of dwellings): 300 0 5,000 Project Area (acres): 1,105 0 2,788 Fuels Treatment Area (acres): 206 0 310 What SRA Fire Hazard Severity Zones (FHSZ) are in the project area? SRA Fire Hazard Severity Zone ratings are available at: xxxx://xxxxxxx.xx.xxx/fire_prevention/fire_prevention_wildland_zones.php Please provide an approximate number of acres or percentage of the project area in each zone. Very High 3,735 96 % High 0 0 % Moderate 158 4 % Non SRA (Federal or Local Area) 0 0

Related to Project Area Statistics

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Annual Work Plans and Budgets The Recipient shall furnish to the Association as soon as available, but in any case not later than September 1 of each year, the annual work plan and budget for the Project for each subsequent year of Project implementation, of such scope and detail as the Association shall have reasonably requested, except for the annual work plan and budget for the Project for the first year of Project implementation, which shall be furnished no later than one (1) month after the Effective Date.

  • Project Site The “Project Site” is the place where the Work is being carried on.

  • Development Records Each Party shall maintain complete, current and accurate records of all Development activities conducted by it hereunder, and all data and other information resulting from such activities. Such records shall fully and properly reflect all work done and results achieved in the performance of the Development activities in good scientific manner appropriate for regulatory and patent purposes. Each Party shall document all non-clinical studies and Clinical Trials in formal written study reports according to Applicable Laws and national and international guidelines (e.g., ICH, cGCP, cGLP, and cGMP).

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Project Initiation i - Upon final execution of the Agreement with the DISTRICT, the ARCHITECT shall: ♦ Review the Program Management Plan (PMP) with the DISTRICT and its representatives to familiarize them with the proposed tasks and schedule and develop necessary modifications. The PMP defines the Program Master Schedule and Budgets and each Project scope and budget. ii - Within the first week following execution of the Agreement, meet with the DISTRICT and its representatives to prepare a detailed task analysis and work plan for documentation in a computer-generated project schedule. iii - This task analysis and work plan will identify specific tasks including, but not limited to: ♦ interviews, ♦ data collection ♦ analysis, ♦ report preparation, ♦ planning, ♦ Architectural programming, concepts and schematic design preparation and estimating that are part of the work of the Project. Also identified will be milestone activities or dates, specific task responsibilities, required completion times necessary for the review and approval by the DISTRICT and by all regulatory agencies and additional definition of deliverables. iv - Participate in a general Project kick-off meeting to include the ARCHITECT, appropriate sub-consultants, and DISTRICT staff. v - The project kick-off meeting will introduce key team members from the DISTRICT and the ARCHITECT to each other, defining roles and responsibilities relative to the Project. vi - Identify and review pertinent information and/or documentation necessary from the DISTRICT for the completion of the Project. vii - Review and explain the overall project goals, general approach, tasks, work plan and procedures and deliverable products of the Project. viii - Review and explain the task analysis and Project work plan for all parties present; determine any adjustments or fine tuning that needs to be made to the work plan. ix - Review documentation of the Project kick-off meeting prepared by the DISTRICT’S representative and comment prior to distribution. x - Base Drawings and Site Survey Information

  • Development Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

  • Project Information Except for confidential information designated by the City as information not to be shared, Consultant agrees to share Project information with, and to fully cooperate with, those corporations, firms, contractors, public utilities, governmental entities, and persons involved in or associated with the Project. No information, news, or press releases related to the Project, whether made to representatives of newspapers, magazines, or television and radio stations, shall be made without the written authorization of the City’s Project Manager.

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