ITEMS IDENTIFIED IN FDU’S Sample Clauses

ITEMS IDENTIFIED IN FDU’S. The FSP map (Appendix C) identifies, where applicable, the locations of the following items that were in effect four months prior to the submission date of this FSP:  Forest Development Units (new and existing);  Ungulate winter range area;  Wildlife habitat areas;  Fisheries sensitive watersheds;  Lakeshore management zones;  Scenic Areas;  L1 Lakes;  Community Watersheds;  Old growth management areas;  Areas where commercial timber harvesting is prohibited by an enactment;  Areas within all FDU’s that are subject to a Timber Sales Licence, a Cutting Permit or a Road Permit (i.e. those areas that were in effect at the commencement date of this FSP)
AutoNDA by SimpleDocs

Related to ITEMS IDENTIFIED IN FDU’S

  • De-identified Information De-identified Information may be used by the Operator only for the purposes of development, product improvement, to demonstrate or market product effectiveness, or research as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Operator agrees not to attempt to re-identify De-identified Information and not to transfer De-identified Information to any party unless (a) that party agrees in writing not to attempt re- identification, and (b) prior written notice has been given to LEA who has provided prior written consent for such transfer. Operator shall not copy, reproduce or transmit any De-identified Information or other Data obtained under the Service Agreement except as necessary to fulfill the Service Agreement.

  • If Identified If the HSP is Identified it will:

  • Use of De-identified information De-identified information may be used by the Contractor for the purposes of development, research, and improvement of educational sites, services, or applications, as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Contractor agrees not to attempt to re-identify de-identified Student Data.

  • Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • User Identification 6.2.5.1 Access to each Party’s corporate resources will be based on identifying and authenticating individual users in order to maintain clear and personal accountability for each user’s actions.

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Vendor Identity and Contact Information It is Vendor’s sole responsibility to ensure that all identifying vendor information (name, EIN, d/b/a’s, etc.) and contact information is updated and current at all times within the TIPS eBid System and the TIPS Vendor Portal. It is Vendor’s sole responsibility to confirm that all e-correspondence issued from xxxx-xxx.xxx, xxxxxxx.xxx, and xxxxxxxxxxxxxxxx.xxx to Vendor’s contacts are received and are not blocked by firewall or other technology security. Failure to permit receipt of correspondence from these domains and failure to keep vendor identity and contact information current at all times during the life of the contract may cause loss of TIPS Sales, accumulating TIPS fees, missed rebid opportunities, lapse of TIPS Contract(s), and unnecessary collection or legal actions against Vendor. It is no defense to any of the foregoing or any breach of this Agreement that Vendor was not receiving TIPS’ electronic communications issued by TIPS to Vendor’s listed contacts.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

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