Experiments and measurement of KPIs Sample Clauses

Experiments and measurement of KPIs. A minimal set of experiments are summarized in Table 3. These experiments are intended to test the core functionalities of the city-wide storytelling experience. Experiment scenario #1 will explore the story computations and frontloading of assets on a small scale. The experiment will occupy a small area and persist for a number of days in order to test system capabilities. Experiment scenario #2 will explore a larger narrative that occupies more area of the urban environment. This area is determined by constraints imposed by the FLAME enabled environment described in Section 5.3. The experiment duration will persist over weeks to collect data from users. Experiment scenarios #1 and #2 will measure the previously described KPIs associated with authentication, storage, availability and processing. Experiment scenario #3 explores the storage and retrieval of the user’s personalized experience. At a minimum, this will explore the construction of a story graph associated with the user’s personalized experience. This story graph will be used in a post process to create a video summary that depicts the locations visited and visualizes the virtual narrative presented to the user. A stretch goal is to explore the storage and retrieval of the AR visualizations of the user. This will represent the user’s actual experience with the narrative. As a post process, the user generated content will be mixed with the pre-existing narrative.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Experiments and measurement of KPIs

  • ACCURACY OF CUSTOMER’S PLANS AND MEASUREMENTS a) The Company is entitled to rely on the accuracy of any plans, specifications and other information provided by the Customer. The Customer acknowledges and agrees that in the event that any of this information provided by the Customer is inaccurate the Company accepts no responsibility for any loss, damages or costs howsoever resulting from these inaccurate plans, specifications or other information.

  • Interim Measures 6.1 The Parties acknowledge that the British Columbia Claims Task Force made the following recommendation concerning interim measures:

  • Safety Measures Awarded vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Awarded vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage.

  • DEMONSTRATIONS/SAMPLES 9.1 Bidders shall demonstrate the exact item(s) proposed within seven (7) calendar days from receipt of such request from the Owners.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

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

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.

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