Pilot 4a Data Harmonization in Numbers Sample Clauses

Pilot 4a Data Harmonization in Numbers. Table 10 depicts the annotations of the Pilot 4a datasets, an average of 6.5 (median 3) classes is used to annotate the datasets. Table 10: Pilot 4a datasets and their annotations Pilot4a Dataset Number of Annotations from the PLATOON Semantic Data Models MicroGridWeatherStationPilot4a 18 MicroGridPVPilot4a 4 MicroGridBatteryPilot4a 2 MicroGridFSIPilot4a 2 Figure 32 presents the RDF graph with the descriptions of the pilot4a datasets. The blue nodes represent the dataset of the pilot. While the yellow nodes are the annotations of the mentioned datasets. All the datasets in pilot4a are described in the Italian language (IT). The datasets are related to the Energy Management in Microgrids catalog. As we can see in Figure 32, the datasets are annotated with different annotations, which is consistent with the nature of each dataset from the pilot. The dataset MicroGridWeatherStation has most of the annotations in this pilot (18) compared to the other datasets (2-4). Figure 32: RDF Knowledge Base with the Description of Pilot4a Catalog and the Data Source Descriptions.
AutoNDA by SimpleDocs

Related to Pilot 4a Data Harmonization in Numbers

  • Local Number Portability Database 10.6.1 The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. BellSouth agrees to provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Local Number Portability (LNP) The ability of users of telecommunications services to retain, at the same location, existing telecommunications numbers without impairment of quality, reliability, or convenience when switching from one telecommunications carrier to another.

  • National Item Identification Number (NIIN) The number assigned to each approved Item Identification under the Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit non-significant number.

  • Local Number Portability The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. PNP is currently being worked in industry forums. The results of these forums will dictate the industry direction of PNP. BellSouth will provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • T1 IDENTIFICATION PROCEDURES During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • CHILD AND DEPENDENT ADULT/ELDER ABUSE REPORTING CONTRACTOR shall establish a procedure acceptable to ADMINISTRATOR to ensure that all employees, agents, subcontractors, and all other individuals performing services under this Agreement report child abuse or neglect to one of the agencies specified in Penal Code Section 11165.9 and dependent adult or elder abuse as defined in Section 15610.07 of the WIC to one of the agencies specified in WIC Section 15630. CONTRACTOR shall require such employees, agents, subcontractors, and all other individuals performing services under this Agreement to sign a statement acknowledging the child abuse reporting requirements set forth in Sections 11166 and 11166.05 of the Penal Code and the dependent adult and elder abuse reporting requirements, as set forth in Section 15630 of the WIC, and shall comply with the provisions of these code sections, as they now exist or as they may hereafter be amended.

  • Using Student feedback in Educator Evaluation ESE will provide model contract language, direction and guidance on using student feedback in Educator Evaluation by June 30, 2013. Upon receiving this model contract language, direction and guidance, the parties agree to bargain with respect to this matter.

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