Operational Data Clause Samples

The 'Operational Data' clause defines the rules and responsibilities regarding the collection, use, and management of data generated during the operation of a service or system. Typically, this clause specifies what constitutes operational data, who owns or has access to it, and how it may be used, such as for performance monitoring, troubleshooting, or service improvement. By clearly outlining these terms, the clause ensures both parties understand their rights and obligations concerning operational data, thereby preventing disputes and promoting transparency in data handling.
POPULAR SAMPLE Copied 1 times
Operational Data. Operational Data is data specific to Customer’s operation that is provided by Customer to Passport to be used in the configuration and provision of the Passport System for Customer’s use. Operational Data is specific to Customer’s operation, which is not available to Passport publicly or by other means. Operational Data may include, but is not limited to, zone information, rate information, operational schedules, business metrics, business rules, parking and other inventory and assets, and relevant details of partner agreements. In each case, Operational Data may refer to past, present, or future states of such items. Operational Data is the sole and exclusive property of Customer. Customer grants Passport a perpetual, irrevocable, royalty-free, and non-exclusive license to Operational Data.
Operational Data. As between the End User and KNA, and subject to the terms and conditions of this Agreement, the End User owns and retains all right, title, and interest in Operational Data. “Operational Data” means the data of the environment obtained by the sensors of a B50 during its operations and explicitly excludes all Personal Data (as defined in Section 5.3). The End User hereby grants to KNA a limited, perpetual, nonexclusive, sublicensable, transferable, irrevocable, worldwide license and right to store, use, and copy Operational Data to: (a) fulfill KNA’s obligations to the End User under this Agreement, and (b) develop and improve Software, Services, B50s, and other products and services. Except as provided in this Section 5.2, KNA shall not use Operational Data for any other purpose without the End User’s prior written consent (email being sufficient). To the extent Operational Data is aggregated and not linked to the End User, such data will not be considered Operational Data. The End User acknowledges that it is neither practical nor useful for KNA to provide Operational Data to the End User except as specified in the Subscription Schedule for the particular Services to which the End User has an active subscription.
Operational Data. As between the End User and Brain, and subject to the terms and conditions of this Agreement, the End User owns and retains all right, title, and interest in Operational Data. “Operational Data” means the data of the environment obtained by the sensors of a Robot during its operations and explicitly excludes all Personal Data (as defined in Section 5.3). The End User hereby grants to Brain a limited, perpetual, nonexclusive, sublicensable, transferable, irrevocable, worldwide license and right to store, use, and copy Operational Data to:
Operational Data. “Operational Data” includes key performance indicators, analysis, statistics, benchmarking and other similar operational information generated by the Services or derived from Customer’s use of the Services, but expressly excluding PHI and third-party proprietary information or data. Alli Connect may anonymize and aggregate Operational Data, and use such Operational Data for its business and/or research purposes. Alli Connect shall own all right, title and interest in and to all Operational Data. If and to the extent that Customer may have intellectual property rights in any Operational Data, Customer hereby grants to Alli Connect a non-exclusive, non-transferable, fully paid-up license to use such Operational Data as described in this Section.
Operational Data. User Data does not include non-identifiable information that is automatically collected by accessing Cribl Services and is not Personal Data (“Operational Data”). Specifically, Operational Data includes telemetry data received by Cribl through Cribl Services, statistical data, aggregate summary data, and other information generated by Cribl Services related to the operation or performance of Cribl Services where the information does not include Personal Data. This includes information on the version, instance, and license identifier of the Cribl Services being used, as well as log in dates and times, the number of events used, data volume used, and the number of resources or features such as connections, sources, destinations, and pipelines that are created or used.
Operational Data. Executive owns his personal contact databases and the Transferred Employees own their own personal contact databases contained in Microsoft Outlook. Executive will be entitled to retain the use of CRB’s telephone numbers. CRB will implement a forwarding message for all emails addressed to Executive and Transferred Employees which shall read as follows: “Please note that effective July 1, 2013, ▇▇▇▇▇▇▇▇ ▇▇▇▇▇/▇▇▇▇ ▇▇▇▇▇ and the employees at both the New York and Los Angeles offices of Counsel RB Capital have joined ▇▇▇▇▇ Brothers LLC. ▇▇▇▇▇▇▇▇/▇▇▇▇ can be reached at ▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇. The addresses and phone numbers remain the same.” From the Separation Date through December 31, 2013, Company will cause such forwarding message to be in effect, and will forward to Executive all email messages received by Company and addressed to Executive or Transferred Employees. No personnel of Company or its Affiliates will access or read any emails sent to Executive or the Transferred Employees from the Separation Date through December 31, 2013. After December 31, 2013, such email accounts will be rendered void and unusable by any Party. Following the execution of this Agreement, any other operational intellectual property identified on Schedule 7.9.2 including phone numbers as noted above and the domain name ▇▇▇▇▇▇▇▇▇.▇▇▇ will belong to Executive and to ▇▇▇▇▇▇▇▇ ▇▇▇▇▇; provided that no right to any trademark or trade name of Company or its Affiliates is transferred. Promptly following execution of this Agreement, Company will transfer the domain name ▇▇▇▇▇▇▇▇▇.▇▇▇ to GoDaddy Account # ▇▇▇▇▇▇▇▇ with the Administrative Name ▇▇▇▇▇▇▇▇▇.▇▇▇. Upon such transfer, Company will notify ▇▇▇ ▇▇▇▇▇▇▇ at ▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇ that the transfer has been completed. Executive will cease and cause his Affiliates to cease all use of the term “Counsel” in any domain name on or before September 30, 2013.
Operational Data. Customer shall provide NCPA access to certain real-time operational systems and information (as mutually determined by NCPA and Customer) including, but is not limited to: (i) Supervisory Control and Data Acquisition (“SCADA”) systems, (ii) Programmable Logic Controllers (“PLC”), and (iii) Real-time telemetry and recording devices.
Operational Data. As between City and RideCo, City will own the Operational Data from the Project and City acknowledges and agrees that RideCo is not responsible for any liability arising out of the collection, retention, use, operation and disclosure by City of Operational Data. Subject to the personal data protection undertakings set out in Schedule“C”, City hereby grants to RideCo for the duration of this Agreement a worldwide and royalty-free right and license to access and use the Operational Data for the sole purposes of: (i) providing the Services to City, (ii) assessing the performance of the Services; and (iii) creating Pattern Data (as defined in Section 2.06 below). City is not entitled to receive any compensation or re-imbursement of any kind from RideCo for use of said Operational Data. Except as otherwise expressly permitted in this Agreement, RideCo does not claim any right, title or interest in the Operational Data.
Operational Data. Supplier shall provide Buyer with the following data: hot water in pounds per hour and temperature in degrees Fahrenheit at the turbine inlet valve necessary to operate the plant at the Supply Amount as shown in a preliminary piping or flow diagram provided by Supplier as described in Exhibit 14, the Supply Amounts as listed in Exhibit 13, and up to the total facility capacity as described in Exhibit 1. Subject to Buyer's review and acceptances Supplier may change this data no later than concurrent with completion of item 2(H) in Exhibit 6. This information will be used as a baseline and monitoring tool for items 2(F) and 2(H) in Exhibit 6.
Operational Data. Carrier shall report information related to enrollment status, premium billing and collection data, grace periods, terminations, and other information as required by COMAR 14.35.15.05K, 14.35.15.09A, 14.35.17.03C, and 14.35.17.05, the Carrier Reference Manual, the Annual Letter to Issuers, and in the form and manner indicated in the Carrier Reference Manual and by MHBE in separate guidance.