Project Identification & Prioritization Sample Clauses

Project Identification & Prioritization. Provide support in developing and maintaining a performance management identification and selection process to assist agencies in organizational analysis, development of a set of evaluation criteria, and applying a selection approach to identify the projects that provide the most benefit to the agency.
AutoNDA by SimpleDocs

Related to Project Identification & Prioritization

  • T1 IDENTIFICATION PROCEDURES During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.

  • Product Identification Before removal from Sale Area, unless Contracting Officer determines that circumstances warrant a written waiver or adjustment, Purchaser shall:

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

  • Contractor’s Staff Identification Contractor shall provide, at Contractor’s expense, all staff providing services under this Contract with a photo identification badge.

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

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

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

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • ADMISSION REQUIREMENTS FOR SENIOR COLLEGE PROGRAM  The A.A. degree and a minimum GPA of 2.00  Grade of C or better in a credit-bearing mathematics course worth three or more credits*  Grade of C or better in freshman composition, its equivalent, or a higher-level English course* *(Effective 10/1/08, per University policy) Students who wish to transfer but do not meet all of the above requirements or are unable to enroll within two years after graduation will receive admission consideration under our standard transfer credit policies. Total transfer credits granted toward the baccalaureate degree: 60 Total additional credits required at the senior college to complete baccalaureate degree: 60 Total credits required for the B.A. in Global History: 120

  • Secure Information Handling and Transfers 7.1 Physical and electronic handling, processing and transferring of DWP Data, including secure access to systems and the use of encryption where appropriate.

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