Inputs and Outputs Sample Clauses

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.
Sample 1Sample 2
AutoNDA by SimpleDocs
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.
Sample 1
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.
Sample 1
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.
Sample 1

Related to Inputs and Outputs

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group. 5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise. 5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Testing Capabilities 7.2.2.10.2.1 LIS Acceptance Testing is provided where equipment is available, with the following test lines: seven-digit access to balance (100 type), milliwatt (102 type), nonsynchronous or synchronous, automatic transmission measuring (105 type), data transmission (107 type), loop-around, short circuit, open circuit, and non-inverting digital loop-back (108 type), and such other acceptance testing that may be needed to ensure that the service is operational and meets the applicable technical parameters. 7.2.2.10.2.2 In addition to LIS acceptance testing, other tests are available (e.g., additional cooperative acceptance testing, automatic scheduled testing, cooperative scheduled testing, manual scheduled testing, and non-scheduled testing). Charges for such testing are identified in Section 7.3.5.

  • Interconnection Customer’s Interconnection Facilities The Interconnection Customer shall design, procure, construct, install, own and/or control the Interconnection Customer’s Interconnection Facilities described in Appendix A at its sole expense.

  • Verizon OSS Facilities Any gateways, interfaces, databases, facilities, equipment, software, or systems, used by Verizon to provide Verizon OSS Services to ICG.

  • Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.

  • Services and Facilities The Procuring Entity shall make available to the Service Provider the Services and Facilities listed under Appendix F.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!