Activity Data Sample Clauses

Activity Data. Activity Data is any data generated in the providing of services under this Agreement by Passport to Customer and by end users’ interactions with the services or with Passport directly that is not otherwise PCI-DSS information or PII as defined above. Activity Data may include, but is not limited to, user interaction data, geolocation data, opt-in/opt-out status (including compliance logs), purchase and session data, application diagnostic data, service performance data, and support data. Data that is derived from Activity Data is also Activity Data. Activity Data is the sole and exclusive property of Passport. Passport grants Customer an irrevocable, royalty-free, non-exclusive, non-assignable, and nontransferable license to Activity Data for the Term to the extent and in the format that Passport chooses in its sole discretion to expose such Activity Data through its administrative portal or as otherwise agreed upon with Customer and only for Customer’s internal use in connection with the services provided under this agreement.
AutoNDA by SimpleDocs
Activity Data. We will provide you with access to your existing Activity Data promptly following your request.
Activity Data. Activity Identification - Each activity in the Project Schedules shall have an activity identifier (Activity ID). The Contractor shall utilize an Activity ID that is simple and allows space between existing activities for the future addition of activities for continuing sort and display capability. The Activity ID of an existing activity shall not be modified or assigned to another activity. The scope of work for an activity shall not be substantially changed once the Baseline Schedule is approved since this would result in re-use of the Activity ID for a different scope of work. Activity Description - The activity description shall identify the unique scope of the activity. There shall not be any two activities with the same activity description. It shall not be necessary to investigate activity code assignments or logic relationships to identify the scope of an activity. For example, the description "POUR FOOTING" will not be acceptable; the description “POUR FOOTING RAMP RT-Sta. 42+0O-42+5O will be acceptable. At the same time the Activity Description shall be concise enough so as to not require excessive column width in the Oracle Primavera P6 layout. The terms “Miscellaneous," "Misc." or other vague adjectives shall not be used in an activity description. The Contractor shall standardize the use of terms and their spelling in all activity descriptions. Abbreviations used in activity descriptions shall be consistent with the abbreviations used throughout the Contract and the Contractor’s design drawings. Activity descriptions shall not be modified, except at the direction or with the consent of the Authority. Activity DurationUnless otherwise specified construction activities shall have duration from five (5) to thirty (30) working days. At the request of the Authority, the Contractor shall substantiate the need for specific activities having shorter or longer durations than stated herein. After approval of the Baseline Schedule, changes in activity durations shall be addressed exclusively through the use of the Duration Remaining data field. Book 3, Part B, Subpart 8 - Cost and Scheduling Controls Program EXECUTION VERSION Activity Type - The implementation of scheduling software features that may impact schedule calculations shall be in accordance with the software manufacturer’s recommendations unless otherwise directed by the Authority. For example, P6 has the default activity type of “task.” Activity Dates - Early and Late start and finish date...

Related to Activity Data

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

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