Inputs and Outputs Sample Clauses

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.
Sample 1
AutoNDA by SimpleDocs
Inputs and Outputs. ‌ The analytics system only accepts xAPI as input format. Traces from games need to be formatted in xAPI using the Serious Game application profile, a standardized vocabulary to describe game interactions13. The complete vocabulary for serious game xAPI traces expected by the Analytics components is available at the ADL website14. This profile is going to be extended for BEACONING to consider geolocalization information. The analytics outputs include dashboards and alerts with the information of the analysed traces. Further details can be found in deliverable D4.6 Game Analytics and adaptation component design of WP4 Platform Development and Ecosystem Integration.
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

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.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • 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.

  • 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.

  • Services and Third Party Materials A. The tvOS Software may enable access to Apple’s iTunes Store, App Store, Game Center, iCloud and other Apple and third party services, and web sites (collectively and individually, “Services”). Such Services may not be available in all languages or in all countries. Use of these Services requires Internet access and use of certain Services may require an Apple ID, may require you to accept additional terms and may be subject to additional fees. By using this software in connection with an Apple ID, or other Apple Service, you agree to the applicable terms of service for that Service, such as the latest iTunes Store Terms and Conditions, which you may access and review at xxxx://xxx.xxxxx.xxx/legal/itunes/ ww/.

  • 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 CBB.

  • 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.

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