Data Sharing Plan Sample Clauses

Data Sharing Plan. As of August 27, 2014, all NIH-funded research that generates large-scale human or non-human genomic data, as well as the use of these data for subsequent research, must follow the NIH Genomic Data Sharing (GDS) Policy (for complete details, refer to: xxxx://xxxxxx.xxx.xxx/grants/guide/notice-files/NOT-OD-14-124.html; see also, xxxx://xxx.xxx.xxx). Large-scale data include genome-wide association studies (GWAS), single nucleotide polymorphisms (SNP) arrays, and genome sequence, transcriptomic, metagenomic, epigenomic, and gene expression data, irrespective of funding level and funding mechanism (e.g., grant, contract, cooperative agreement, or intramural support). NIH Institutes or Centers (ICs) may expect submission of data from smaller scale research projects based on the state of the science, the programmatic priorities of the IC funding the research, and the utility of the data for the research community.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Data Sharing Plan. The Parties shall cooperate in good faith and shall use commercially reasonable efforts to enter into a binding agreement within one hundred twenty (120) days of the Effective Date setting forth the terms, conditions, rights and obligations of each Party with respect to the sharing of Client Data under this Agreement and the Prospective Agreements between the Parties, their respective business units and their respective Affiliates (the “Data Sharing Plan”). For the avoidance of doubt, for the purposes of this Article II (other than Section 2.01(i)) and the Data Sharing Plan, the term Data shall be understood to include only non-consumer Data, and with respect to Data provided by Amex, shall be understood to include only Data derived from the GCP Business. The Data Sharing Plan shall include, at a minimum, the terms and conditions set forth in this Section 2.01, including: (i) types of Data required to be shared by each Party and each respective business unit or Affiliate thereof; (ii) forms and formats of Data to be shared; (iii) the specific business units or Affiliates of each Party who shall have access to each type of Data and the extent of such access; (iv) Data privacy, protection and retention policies, including with respect to creation and provision of Masked Data and required demographic and firmographic information to be provided with such Masked Data; and (v) Data governance processes.
Sample 1
Data Sharing Plan. The Evaluation Plan approved by the US Department of Education for the Arizona GEAR UP 2012-19 grant requires that NAU obtain the following data: (1) Course titles for any developmental (remedial) courses in English and math taken by GEAR UP students; (2) Grades earned by GEAR UP students in developmental (remedial) courses including withdrawals and incompletes; and (3) GEAR UP students’ end of freshman year GPA based on a four-point scale. CFR 99.31 (a) (6)(i), allows GEAR UP Partners to release of specified identified student level academic information to NAU GEAR UP under the exception outlined in 34 CFR § 99.31 (which provides that schools can disclose, without consent, students’ education records to authorized representatives for purposes of evaluating a federally-funded program, as long as data security requirements are met). S ee Attachment 4 for the mutually agreed upon Data Sharing Plan. GEAR UP students’ academic data is provided solely for the purposes of program management, study, evaluation and required reporting of GEAR UP’s effects on students’ retention and success in postsecondary education. GEAR UP Partner will follow established security protocols when submitting student data to NAU GEAR UP. NAU will ensure to the greatest extent practicable that it will use Personally Identifiable Information (PII) only for the authorized purpose; and that it will protect the PII from unauthorized disclosure or other uses. Any unauthorized disclosure of confidential student information is a violation of the Family Education Rights and Privacy Act of 1974 (FERPA) and implementing regulations found in 34 CFR Part 99. Any such disclosures shall not be permitted to occur. NAU assures GEAR UP Partner that any reports on the shared data will be written so that no individual will be identified directly or by deduction. While in possession of these data and in order to meet Department of Education GEAR UP program objectives, NAU shall permit only GEAR UP staff to have access to the data. NAU also agrees to contract with a qualified third party to store data in a secure area and to prevent unauthorized access. Per NAU requirements, all data collected through this agreement will be archived at the conclusion of this project for a period of five years and then destroyed.
Sample 1
Data Sharing Plan. If the proposal is expected to generate environmental data, a Data Management Plan is required. The Data Management Plan should address the requirements in this section of the Announcement. i. Environmental data and information collected or created under NOAA grants or cooperative agreements must be made discoverable by and accessible to the public, in a timely fashion (typically within two years), free of charge or at no more than the cost of reproduction, unless an exemption is granted by the NOAA Program. Data should be available in at least one machine-readable format, preferably a widely used or open-standard format, and should be accompanied by machine-readable documentation (metadata), preferably based on widely used or international standards. ii. Proposals submitted in response to this Announcement must include a Data Management Plan of up to two pages describing how these requirements will be satisfied. The Data Management Plan should be aligned with the Data Management Guidance provided by NOAA in the Announcement (component viii. of this section). The contents of the Data Management Plan (or absence thereof), and past performance regarding such plans, will be considered as part of proposal review. A typical plan should include descriptions of the types of environmental data and information expected to be created during the course of the project; the tentative date by which data will be shared; the standards to be used for data/metadata format and content; methods for providing data access; approximate total volume of data to be collected; and prior experience in making such data accessible. The costs of data preparation, accessibility, or archiving may be included in the proposal budget. Accepted submission of data to the NOAA National Centers for Environmental Information (NCEI) is one way to satisfy data sharing requirements; however, NCEI is not obligated to accept all submissions and may charge a fee, particularly for large or unusual datasets. The NOAA Program is not offering specific data management technical guidance. Proposals are to describe their proposed approach. Use of open standard formats and methods is encouraged. For more information about data sharing in this program, contact the agency official listed in Section VII. of this funding announcement. iii. NOAA may, at its own discretion, make publicly visible the Data Management Plan from funded proposals, or use information from the Data Management Plan to produce a formal metad...
Sample 1

Related to Data Sharing Plan

  • Data Sharing The GRANTEE BENEFICIARY agrees to share data with the AGENCY as deemed necessary by AGENCY, in its sole discretion, for expenditure validation, trend review, and performance monitoring.

  • Profit Sharing Plan Under the Northrim BanCorp, Inc. Profit Sharing Plan (the “Plan”), Executive shall be eligible to receive an annual profit share based on performance as defined by the Board of Directors. Executive will be classified in the Executive tier under the Plan’s Responsibility Factors. If Employer is required to prepare an accounting restatement due to “material noncompliance of the Employer,” the Employer will recover from the Executive any incentive compensation during the three (3) years prior to the date of the restatement, in excess of what would have been paid under the restatement. Executive’s signature on this Agreement authorizes Employer to offset or deduct from any compensation Employer may owe Executive, any excess payments (in whole or in part) that Executive may owe Employer due to such restatement(s).

  • Retirement Plans (a) In connection with the individual retirement accounts, simplified employee pension plans, rollover individual retirement plans, educational IRAs and XXXX individual retirement accounts (“XXX Plans”), 403(b) Plans and money purchase and profit sharing plans (“Qualified Plans”) (collectively, the “Retirement Plans”) within the meaning of Section 408 of the Internal Revenue Code of 1986, as amended (the “Code”) sponsored by a Fund for which contributions of the Fund’s shareholders (the “Participants”) are invested solely in Shares of the Fund, Transfer Agent shall provide the following administrative services: (i) Establish a record of types and reasons for distributions (i.e., attainment of eligible withdrawal age, disability, death, return of excess contributions, etc.); (ii) Record method of distribution requested and/or made; (iii) Receive and process designation of beneficiary forms requests; (iv) Examine and process requests for direct transfers between custodians/trustees, transfer and pay over to the successor assets in the account and records pertaining thereto as requested; (v) Prepare any annual reports or returns required to be prepared and/or filed by a custodian of a Retirement Plan, including, but not limited to, an annual fair market value report, Forms 1099R and 5498; and file same with the IRS and provide same to Participant/Beneficiary, as applicable; and (vi) Perform applicable federal withholding and send Participants/Beneficiaries an annual TEFRA notice regarding required federal tax withholding. (b) Transfer Agent shall arrange for PFPC Trust Company to serve as custodian for the Retirement Plans sponsored by a Fund. (c) With respect to the Retirement Plans, Transfer Agent shall provide each Fund with the associated Retirement Plan documents for use by the Fund and Transfer Agent shall be responsible for the maintenance of such documents in compliance with all applicable provisions of the Code and the regulations promulgated thereunder.

  • Retirement Plan The 2.7% at 55 retirement plan will be available to eligible bargaining unit members covered by this Section 6.1.

  • Supplemental Retirement Plan During the Contract Period, if the Executive was entitled to benefits under any supplemental retirement plan prior to the Change in Control, the Executive shall be entitled to continued benefits under such plan after the Change in Control and such plan may not be modified to reduce or eliminate such benefits during the Contract Period.

  • SERP Executive is a participant in the BB&T Corporation Non-Qualified Defined Benefit Plan (the “SERP”). The SERP was formerly known as the Branch Banking and Trust Company Supplemental Executive Retirement Plan. The SERP is a non-qualified, unfunded supplemental retirement plan which provides benefits to or on behalf of selected key management employees. The benefits provided under the SERP supplement the retirement and survivor benefits payable from the Pension Plan. Except in the event the employment of Executive is terminated by the Employer or BB&T for Just Cause and except in the event Executive terminates Executive’s employment for any reason other than Good Reason and such termination does not occur within twelve (12) months after a Change of Control (or, if later, within ninety (90) days after a MOE Revocation), the following special provisions shall apply for purposes of this Agreement: (i) The provisions of the SERP shall be and hereby are incorporated in this Agreement. The SERP, as applied to Executive, may not be terminated, modified or amended without the express written consent of Executive. Thus, any amendment or modification to the SERP or the termination of the SERP shall be ineffective as to Executive unless Executive consents in writing to such termination, modification or amendment. The Supplemental Pension Benefit (as defined in the SERP) of Executive shall not be adversely affected because of any modification, amendment or termination of the SERP. In the event of any conflict between the terms of this Section 1.7.7(i) and the SERP, the provisions of this Section 1.7.7 (i) shall prevail. Executive hereby agrees and consents to Employer’s amendment of the SERP to comply with Section 409A.

  • Staffing Plan The Board and the Association agree that optimum class size is an important aspect of the effective educational program. The Polk County School Staffing Plan shall be constructed each year according to the procedures set forth in Board Policy and, upon adoption, shall become Board Policy.

  • Savings Plan Executive will be eligible to enroll and participate, and be immediately vested in, all Company savings and retirement plans, including any 401(k) plans, as are available from time to time to other key executive employees.

  • Group Insurance Plan The carriers, coverage, and terms and conditions of participation under the District’s Group Insurance Plan are subject to change in accordance with the applicable provisions of Title I, Division 4, Chapter 10 of the California Government Code (Section 3500 et seq.) (Xxxxxx‐Milias‐Xxxxx Act). a. The District contracts with CalPERS for health plan coverage for all regular and newly hired employees (eligibility to be defined by the “CalPERS health plan”). Booklets on the insurance plans will be available to all participants. b. Employees may choose from the available plans offered by CalPERS. Additional premiums will be borne by the employee through payroll deductions and paid to CalPERS by the District each month; and the additional cost for monthly premiums will be deducted evenly from the first and second payroll period of each month. To the extent allowed by law, the District will attempt to deduct the employee’s premium contribution from pre‐tax dollars.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

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