Inputs and Outputs. You and your Clients may provide content as input to our Services (“Input”) and may receive content as output from the Services (“Output”, together with the Input, collectively, the “Content”). Your and your Clients’ access to and use of the Services, including for the purposes of providing Input to the Services and receiving Output from the Services, is subject to our Prohibited Use Policy. If you choose to make any of your information publicly available through the Services or otherwise, you do so at your own risk.
Inputs and Outputs a) The AI Functionality may require Customer to provide Input, which will be used by the AI Functionality to generate Output. As between Crownpeak and Customer, Customer retains its ownership rights in Input and owns the Output, to the extent permitted by Applicable Law. Crownpeak additionally assigns all its right, title, and interest, if any, in and to Output.
b) AI Functionality may include features which are powered by AI models operated by a third party provider, in which case Customer permits the relevant third party provider of such AI Functionality to use Inputs and Outputs or other Customer Data submitted to the AI Functionality as necessary to provide and maintain the AI Functionality, comply with applicable laws, and enforce its policies. AIl third party providers who process Personal Data can be found on the Crownpeak Subprocessor List in the Crownpeak Governance Center.
c) Where Inputs and Outputs are submitted to a third party provider, those Inputs and Outputs may be retained temporarily by the third party provider as part of the operation of their service.
d) Any third party provider of AI Functionality shall act as a Subprocessor of Customer Data submitted to the relevant AI Functionality, including Personal Data that may be contained in Inputs or other Customer Data. All processing of Customer Data will be governed by the DPA in place between Crownpeak and Customer. In this Addendum, “Subprocessor” and “Personal Data” shall have the meanings given to them in the DPA.
Inputs and Outputs. 3.3.2.1 It is the Contractor’s responsibility to assess the type and quality of data or signal inputs available from the already installed powerhouse instrumentation.
3.3.2.2 The outputs of the prototype Type 1 Optimizer are to be a data field and resulting relative efficiency profile with a corresponding cam curve at two-foot intervals of gross head. The outputs shall be observable on the device and be provided in electronic formats suitable for subsequent analysis on computer.
Inputs and Outputs. Customer retains rights to all Inputs and Input Data, and though Customer has a right to use Outputs generated by the Vendor AI, the Outputs are owned by Vendor. Customer is solely responsible to ensure that all Outputs are checked and validated, that they are fit for purpose and that they are in compliance with Applicable Laws prior to their use. Customer acknowledges and agrees that Input Data may not be kept confidential, and the Input Data and Outputs may be used to further enhance the Vendor AI, as detailed in Section 2.2 above. Further, due to the nature of an AI System, the Output may not be unique across users and the Vendor AI may generate or return the same or similar Output to other customers, Vendor or a third party. If Customer provides Vendor with written notice or otherwise decides that Customer no longer desires to use Vendor AI, Vendor is not required to retain the Inputs, any Input Data or Outputs used or otherwise processed in connection with the Vendor AI.
Inputs and Outputs. The canonical tester theory and its variations make an important assumption about the communication between the sut and the tester, viz. that this communication is synchronous and symmetric. Each communica- tion event is seen as a joint action of the sut and the tester, inspired by the parallel composition in process algebra. This also means that both the tester and the sut can block the communication, and thus stop the other from progressing. In practice, however, it is different: actual communication between an sut and a tester takes place via inputs and outputs. Inputs are initiated by the tester, they trigger the sut, and they cannot be refused by the sut. Outputs are produced by the sut, and they are observed and cannot be refused by the tester.
