Purpose, Scope Specifications Sample Clauses

Purpose, Scope Specifications. The purpose of the BOUNCE semantic model is to effectively represent and model all data that will be collected and analyzed within the BOUNCE platform. This model will be used to integrate, homogenize and semantically uplift the various data available. The steps to integrate the available data are shown in Figure 2. Initially the ontology is identified or generated based on the data available at the sources. In some cases, it is common to adopt ontologies partially covering the domain and extending them to be able to model the remaining data of interest as well. Then ontologies are used in order to define the mappings, i.e. programmatic correspondences between ontological terms and the various data fields. Based on those mappings, data integration engines can automatically homogenize and semantically uplift available data. The whole workflow is usually an iterative process. When the underlying data is mapped to the sources, the ontology as well as the integrated data might need to be updated.. More details on this process will be provided in D3.4 Solutions for Data Aggregation, Cleaning, Harmonization & Storage.
Sample 1
AutoNDA by SimpleDocs

Related to Purpose, Scope Specifications

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Vehicle Base Specifications Note: The actual vehicle awarded may exceed the minimum specifications stated below. The Authorized User may elect to add additional Options, delete Options, or substitute a vehicle feature that is an Option with another Option. See Contract Section III.6

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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