Ancillary Data Sample Clauses

The Ancillary Data clause defines the handling, ownership, and use of supplementary information generated or exchanged in connection with the main agreement. This may include metadata, usage statistics, or technical logs that are not the primary subject of the contract but are produced as a byproduct of the parties' interactions. By clarifying rights and restrictions regarding such data, the clause helps prevent disputes over access, confidentiality, or commercial use of ancillary information.
Ancillary Data. During normal operations, the C&DH subsystem shall collect Ancillary Data from Bus and Instrument equipment and forward it [**Redacted**]
View SourceView Similar (8)
Ancillary Data. OSD 2014 ancillary data are extrapolated values based on the latitude and longitude of OSD 2014 sampling stations, from relevant public environmental databases. This was performed by Dr ▇▇▇▇▇▇ ▇▇▇▇▇▇▇ with support from ▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇, Professor ▇▇▇▇▇ ▇▇▇▇▇▇ and Dr ▇▇▇▇▇▇ ▇▇▇▇▇. Since the majority of the OSD Site Coordinators were unable to provide us with an extensive list of environmental metadata, OSD Analysis Consortium collectively decided to extend the set of “overall environmental data”, in order to have the ability to perform in-depth analysis. An “Ancillary Data Request Form” was put together and circulated among OSD Analysis Consortium to allow participants to facilitate their requests for additional data ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/MicroB3-IS/osd-analysis/wiki/Requests-for-ancillary-data. Ancillary data was retrieved from multiple datasets, including ▇▇▇ ▇▇▇▇▇▇▇'▇ dataset [1], which is the most relevant dataset given the nature of the OSD Sites being “coastal” with around 75% of sampling sites being within 10km from the coast. This effort increased the value of OSD 2014 dataset tremendously and has been highly appreciated by OSD Analysis Consortium participants. Final version of OSD 2014 ancillary data is publicly available via GitHub.
View Source
Ancillary Data. Users must be allowed to import and display the follow kinds of data files for use as a reference when delineating TAZ entities: - Shapefiles - Imagery files - Other standard geographic file formats The software will provide at a minimum two layers of boundaries files that the user can select as a starting point for TAZ delineation: - TAZ layer from Census 2000 - Current tracts “Current tracts” are a modified version of Census 2000 tracts that account for adjustment (some county boundary shifts) and re-alignments. The participant can also import a shapefile of another existing geography, and then immediately save and re-title the file for use as a base for the new TAZ plan. All edits to the supplied or imported data will then be saved as a new shapefile reflecting the new 2010 TAZ geography for submission.
View Source

Related to Ancillary Data

  • Ancillary Agreement Any written agreement of the Lessee to which the Lessor is a party or to which the Lessor has consented in writing entered into on or prior to the Delivery Date or any date thereafter in connection with the transactions contemplated by the Operative Agreements, as such agreement may be amended and supplemented from time to time with the consent of the Lessor and delivered to the Owner Trustee, the Indenture Trustee, the Pass Through Trustee, the Subordination Agent, each Liquidity Provider and the Owner Participant. Ancillary Agreement I. The Ancillary Agreement I (Federal Express Corporation Trust No. N676FE), dated the Delivery Date, among the Lessee, the Owner Trustee, not in its individual capacity, but solely as Owner Trustee, the Owner Participant and the Indenture Trustee not in its individual capacity, but solely as Indenture Trustee, as originally executed or as amended, modified or supplemented with the consent of all the parties thereto.

  • Ancillary Services Those services that are necessary to support the transmission of capacity and energy from resources to loads while maintaining reliable operation of the Transmission Provider’s Transmission System in accordance with Good Utility Practice.

  • Ancillary Documents (a) Project Co shall not: (i) terminate or agree to the termination of all or part of any Ancillary Document, except pursuant to Sections 27.3, 49.3 and 50.2 or otherwise to prevent or cure a Project Co Event of Default (provided that commercially reasonable alternative measures would not prevent or cure such Project Co Event of Default); (ii) make or agree to any amendment, restatement or other modification or exercise any of its rights under any Ancillary Document that materially adversely affects Project Co’s ability to perform its obligations under this Project Agreement or that has the effect of increasing any liability of Contracting Authority, whether actual or potential; (iii) breach its obligations (or waive or allow to lapse any rights it may have) or permit others to breach their obligations (or waive or allow to lapse any rights they may have) under any Ancillary Document, if any such breach (or waiver or lapse) would materially adversely affect Project Co’s ability to perform its obligations under this Project Agreement or that have the effect of increasing any liability of Contracting Authority, whether actual or potential; or (iv) enter into, or permit the entry into by any other person of, any agreement replacing all or part of any Ancillary Document, except in the circumstances referenced in Section 8.2(a)(i), without the prior written consent of Contracting Authority, provided that, where consent is requested pursuant to Section 8.2(a)(i) or 8.2(a)(iv), such consent shall not be withheld, and shall be provided within a reasonable time, where the relevant matter referred to in Section 8.2(a)(i) or 8.2(a)(iv) will not materially adversely affect Project Co’s ability to perform its obligations under this Project Agreement or have the effect of increasing any liability of Contracting Authority, whether actual or potential. In the event of termination or agreement to the termination of all or part of any Ancillary Document as described in Section 8.2(a)(i), or the entering into of any agreement replacing all or part of any Ancillary Document as described in Section 8.2(a)(iv), Project Co shall, to the extent applicable, comply with all provisions herein relating to changes in Subcontractors, including Section 49.3. (b) Upon the written request of Contracting Authority or the Contracting Authority Representative, Project Co will deliver or cause to be delivered to Contracting Authority or the Contracting Authority Representative a copy of any notices delivered or received by Project Co under any of the Ancillary Documents.

  • Ancillary Agreements This Agreement is not intended to address, and should not be interpreted to address, the matters specifically and expressly covered by the Ancillary Agreements.

  • Buyer Data for all Defaults by the Supplier resulting in direct loss, destruction, corruption, degradation or damage to any Buyer Data, will not exceed the amount in the Order Form