KPIS AND KVIS VALIDATION Sample Clauses

KPIS AND KVIS VALIDATION. The 5Genesis Framework defines and supports a specific methodology for the management of results and the validation of KPIs and KVIs, in the form of the Analytics Framework. This gives a standardized solution for the management of raw results and provides both a dashboard and REST API for KPIs and KVIs calculations. This solution is based on the usage of a single Results Repository (effectively an InfluxDB database), which is populated with data generated by a set of heterogeneous probes distributed in the infrastructure of the Trial Network. Each probe can generate measurements independently, requiring only that these measurements are tagged following a particular format and that specifies a timestamp centered in UTC. The Analytics Module can make use of this metadata for filtering of stored measurements, for example, to perform calculations only on results that belong to a particular Experiment execution or that were generated during a specific period of time. It should be noted that the description above applies to the results generated within a single Trial Network when using the default Experimentation framework. There are two considerations that are of importance: 4 xxxxx://xxxxxxx.xx/ 5 xxxxx://xxxxxxxxxxxxxx.xxx/ • Experimenters are always able to install alternative solutions that can generate results that are not handled following this methodology. • Experimenters will also need access to measurements generated outside of their Trial Network, for example, events generated as part of the Trial Network’s lifecycle management or from shared components. Regarding the second point above, it is expected that this data will be made available, though filtered, in order to guarantee the privacy and security of other Trial Networks running in the same platform. The specific solution to be used has not been decided at the time of this writing but some possibilities include: • Automatically injecting new entries in the internal Results Repository of the Trial Network. • Giving access to experimenters to a global Result Repository where they can retrieve a limited sub-set of the data contained. • Considering that the Analytics Framework can work with multiple data sources, configure both the internal and global Result Repositories. As is the case with the ELCM, it is expected that the Analytics Framework will be extended and adapted during the course of 6G-SANDBOX.
Sample 1
AutoNDA by SimpleDocs

Related to KPIS AND KVIS VALIDATION

  • Inspection and Testing Each Constructing Entity shall cause inspection and testing of the Interconnection Facilities that it constructs in accordance with the provisions of this section. The Construction Parties acknowledge and agree that inspection and testing of facilities may be undertaken as facilities are completed and need not await completion of all of the facilities that a Constructing Entity is building.

  • Validation To validate the notice requirements outlined in Section 5.3, the Assuming Institution shall provide the Receiver (i) an Affidavit of Publication to meet the publication requirements outlined in Section 5.3(a) and (ii) the Assuming Institution will prepare an Affidavit of Mailing in a form substantially similar to Exhibit 2.3B after mailing the seven (7) day Notice to Depositors as required under Section 5.3(b).

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Inspection and Tests 3.8.1 The Procuring entity or its representative shall have the right to inspect and/or to test the goods to confirm their conformity to the Contract specifications. The Procuring entity shall notify the tenderer in writing in a timely manner, of the identity of any representatives retained for these purposes.

  • Inspections and Testing Each Interconnected Entity shall perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Customer Facility with the Transmission System in a safe and reliable manner. Each Interconnected Entity shall have the right, upon advance written notice, to request reasonable additional testing of an Interconnected Entity’s facilities for good cause, as may be in accordance with Good Utility Practice.

  • MAINTENANCE OF STANDARDS The Employer agrees, subject to the following provisions, that all conditions of employment in his/her individual operation relating to wages, hours of work, overtime differentials and general working conditions shall be maintained at not less than the highest standards in effect at the time of the signing of this Agreement, and the conditions of employment shall be improved whenever specific provisions for improvement are made elsewhere in this Agreement.

  • Maintenance and Testing 54.5.1. Sprint is only responsible for maintaining the facilities that it owns.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Licensure The Contractor covenants that it has:

  • Education and Prevention 6.1 The policy will be discussed and put forward for adoption on site at a meeting of all workers.

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