Common Database Sample Clauses

Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or as Allowable Expenses, calculated on a FTE cost and direct out-of-pocket cost basis.
AutoNDA by SimpleDocs
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Co-Developed Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis.
Common Database. If deemed appropriate by the JDC, BMS and EXEL will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Co-Developed Products. BMS and EXEL shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable BMS and EXEL and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, [*] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24b-2 of the Securities Exchange Act of 1934, as amended. such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. BMS’ and EXEL’s costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis.
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by the Party designated by the JDC for the receipt, investigation, recordation, communication, and exchange (as between the *Confidential Treatment Requested. Parties) of data arising from Clinical Trials for Collaboration Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties to fulfill their reporting obligations under applicable Law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such data shall be included as an element of Development Costs or as Commercialization Costs, as applicable, calculated on a FTE cost (calculated at the FTE Rate) and direct out-of-pocket cost basis.
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by the Party designated by the JDC for the receipt, investigation, recordation, communication, and exchange (as between the [ * ] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24b-2 of the Securities Exchange Act of 1934, as amended. Parties) of data arising from Clinical Trials for Collaboration Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties to fulfill their reporting obligations under applicable Law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such data shall be included as an element of Development Costs or as Commercialization Costs, as applicable, calculated on a FTE cost (calculated at the FTE Rate) and direct out-of-pocket cost basis.
Common Database. If deemed appropriate by the JDC, BMS and EXEL will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between BMS and EXEL) of data arising from clinical trials for Products. BMS and EXEL shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable BMS and EXEL and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. BMS’ and EXEL’s costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or as Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis.
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or as Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis. [ * ] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24B-2 of the Securities Exchange Act of 1934, as amended.
AutoNDA by SimpleDocs

Related to Common Database

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Password To enable you, and only you, to use the Service, you will be asked to choose a password when you register and are accepted as a customer of the Service. This password is stored in encrypted form by us. You are responsible for maintaining the confidentiality of your Financial Institution customer number and password. No one at Financial Institution has access to your Accounts passwords or user ID's. You are responsible for uses of the Service whether or not actually or expressly authorized by you. Therefore, it is important that you DO NOT SHARE YOUR ACCOUNT NUMBER OR PASSWORD WITH ANYONE FOR ANY REASON. No one at Financial Institution will know or need to know your password, and Financial Institution employees will never ask for your password. If you wish to make a transfer to an Account of another person, you will be asked to provide a separate code word or phrase (the "Shared Secret") that is known only to you and to the person to whom you are transferring the funds (the "Recipient"). We recommend that you do not use commonly used words, phrases or dates. In order to complete the transfer, the Recipient must provide the Shared Secret and certain other identifying information. YOU AGREE THAT YOU WILL NOT GIVE THE SHARED SECRET TO ANYONE EXCEPT THE RECIPIENT FOR ANY REASON. YOU FURTHER AGREE THAT YOU WILL INSTRUCT THE RECIPIENT NOT TO GIVE THE SHARED SECRET TO ANYONE ELSE FOR ANY REASON. In the Event of Unauthorized Transfer If you believe your password or Shared Secret has been lost or stolen, or that someone has transferred or may transfer money from your Account without your permission, contact us using the instructions on our site. Consumer Liability You agree to notify us AT ONCE if you believe your password has been lost or stolen. Telephoning us promptly is the best way to protect yourself from possible losses. If you never tell us, you could lose all of the money in your account (plus your maximum overdraft line of credit). However, if you tell us within 2 business days, you can lose no more than $50 if someone used your password without your permission. If you do NOT tell us within 2 business days after you learn of the loss or theft of your password, and we can prove we could have stopped someone from using your password without your permission if you had told us, you could lose as much as $500. You can see a complete statement of all your funds transfers effected or pending at any time by clicking on the History tab. If your statement shows transfers that you did not make, notify us AT ONCE. If you do not tell us within 60 days after the transfer was posted to your statement, you may not get back any money you lost after the 60 days, if we can prove that we could have stopped someone from taking the money if you had told us in time. If a good reason (such as a long trip or a hospital stay) kept you from telling us, we will extend the time periods.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

  • Passwords Passwords are an important aspect of computer security. A poorly chosen password may result in unauthorized access and/or exploitation of Placer County’s resources. All users, including contractors and vendors with access to the County’s systems, are responsible for the creation and protection of passwords and additionally any updates to County Password policies must be followed. Users must not use the same password for Placer County accounts and personal accounts. The reliability of passwords for maintaining confidentiality cannot be guaranteed. Always assume that someone, in addition to the intended or designated recipient, may read any and all messages and files. Any user suspecting that his/her password may have been compromised must, without delay, report the incident to Placer County IT.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer. Confidentiality

  • Contract Database Metadata Elements Title: Spencerport Central School District and Spencerport Paraprofessional Association, New York State United Teachers (NYSUT), American Federation of Teachers (AFT), AFL-CIO (2015) Employer Name: Spencerport Central School District Union: Spencerport Paraprofessional Association, New York State United Teachers (NYSUT), American Federation of Teachers (AFT), AFL-CIO Local: Effective Date: 07/01/2015 Expiration Date: 06/30/2018 PERB ID Number: 6253 Unit Size: Number of Pages: 27 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT between the SUPERINTENDENT OF SCHOOLS SPENCERPORT CENTRAL SCHOOL DISTRICT Town of Ogden, Gates, Greece and Parma and SPENCERPORT PARAPROFESSIONAL ASSOCIATION July 1, 2015 - June 30, 2018 TABLE OF CONTENTS ARTICLE PAGE PREAMBLE 1 RECOGNITION 1 ELIGIBLITY FOR BENEFITS 1 ARTICLE 1 DUES DEDUCTION 2 ARTICLE 2 SICK LEAVE 2 ARTICLE 3 PERSONAL LEAVE 3 ARTICLE 4 ILLNESS IN FAMILY 4 ARTICLE 5 FAMILY MEDICAL LEAVE ACT 4 ARTICLE 6 HEALTH INSURANCE 5 ARTICLE 7 WORKER'S COMPENSATION 8 ARTICLE 8 BEREAVEMENT 9 ARTICLE 9 SNOW DAYS AND EMERGENCY CLOSING 9 ARTICLE 10 JURY DUTY 9 ARTICLE 1 WORK YEAR 9 ARTICLE 12 EXTRA HOURS WORKED 10 ARTICLE 13 1:1 AIDES 10 ARTICLE 14 LUNCH & BREAKS 10 ARTICLE 15 LONGEVITY 10 ARTICLE 16 PAID HOLIDAYS 1 ARTICLE 17 SALARY 12 ARTICLE 18 UNUSED SICK DAYS AT RETIREMENT 14 ARTICLE 19 GRIEVANCE PROCEDURE 15 ARTICLE 20 UNPAID LEAVE OF ABSENCE 17 ARTICLE 21 SENIORITY, ASSIGNMENT, AND LAYOFF 18 ARTICLE 22 VACANCY NOTIFICATIONS 20 ARTICLE 23 CREDIT FOR IN-SERVICE COURSES 20 ARTICLE 24 PROBATIONARY PERIOD 21 ARTICLE 25 FLEXIBLE SPENDING ACCOUNT 21 ARTICLE 26 ATTENDANCE INCENTIVE 21 ARTICLE 27 PERSONNEL FILES 22 ARTICLE 28 EVALUATIONS 22 ARTICLE 29 EARLY DISMISSAL - i - 22 ARTICLE 30 DIRECT DEPOSIT 23 ARTICLE 31 PAYROLL DEDUCTION 23 ARTICLE 32 PAYROLL DISTRIUBTION 23 ARTICLE 33 CONFORMITY OF LAW 23 ARTICLE 34 CHAPERONING AND PROCTORING 23 ARTICLE 35 BUS ATTENDANTS 24 ARTICLE 36 DURATION OF AGREEMENT 24 P R E A M B L E The Spencerport Central School District and the Spencerport Paraprofessional Association desire to enter into the agreement in order to effectuate the provisions of the Public Employees' Fair Employment Act and to encourage and increase the effective and harmonious work relationship between the district and the paraprofessionals who comprise the unit members within the bargaining unit represented by the association. The association hereby reaffirms that it will not engage in any strike, or cause, instigate, encourage, assist or condone any strike. The district recognizes the right of these unit members to organize and to bargain collectively through the association on such matters as salaries, hours and other terms and conditions of employment. The agreement is made and entered into on the 23rd day of June, 2015, by and between the Superintendent of Schools, SPENCERPORT CENTRAL SCHOOL DISTRICT, Spencerport, New York, hereinafter referred to as the "district," and the unit members of this unit of aforementioned school district, represented by the SPENCERPORT PARAPROFESSIONAL ASSOCIATION, hereinafter referred to as the "association." RECOGNITION Pursuant to the New York State Public Employees Fair Employment Act, the Board of Education of Spencerport Central School District has recognized the Spencerport Paraprofessional Association, hereinafter referred to as "association," as the exclusive negotiating representative for all Accompanists, Bus Attendants, Licensed Practical Nurses, Microcomputer Maintenance Technicians, School Aides and Teacher Aides employed by said district. ELIGIBILITY FOR BENEFITS All unit members employed by the District on June 30, 2000, while serving in a 27.5 (or more) hours per week position, will be considered as “full time” and will receive all of the benefits of unit members working 30 or more hours per week as detailed in Articles 2, 3, 4, 6, and 12 of this agreement. All unit members hired after June 30, 2000 are eligible for all of the benefits as detailed in Articles 2, 3, 4, 6, and 12 of this agreement and considered “full time” when serving in a 30 (or more) hours per week position. Any unit member hired after July 1, 2000 in a 30 (or more) hours per week capacity who is involuntarily reduced to at least 27.5 hours per week will receive the benefits associated with “full time” employment (Articles 2, 3, 4, 6, and 12). Spencerport Paraprofessional Association - 1 - July 1, 2012 - June 30, 2015

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