Virtual Entity & IoT Service Clause Samples

POPULAR SAMPLE Copied 1 times
Virtual Entity & IoT Service. The Virtual Entity and IoT Service Functionality Groups include functions that relate to interactions on the Virtual Entity and IoT Service abstraction levels respectively. Figure 16 shows how the abstraction levels and how they are related. On the left side of Figure 16 the physical world is depicted. In the physical world there are a number of sensors and actuators that respectively capture and allow the change of certain aspects of the physical world. The Resources associated to the sensors and actuators are exposed as IoT Services on the IoT Service Level. Example interactions between applications and the IoT system on this abstraction level are “Give me the value of Sensor 456” or “Set Actuator 867 to On”. Applications can only interact with these services in a meaningful way, if they already know the semantics of the values, e.g. if Sensor 456 returns the value 20, the application has to be programmed or configured in such a way that it knows that this is the indoor temperature of the room of interest, e.g. Room 1.

Related to Virtual Entity & IoT Service

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (▇▇▇▇▇://▇▇▇▇▇.▇▇▇.▇▇▇▇▇.▇▇.▇▇/tpasscmblsearch/index.jsp) or by contacting

  • Outpatient Dental Anesthesia Services This plan covers anesthesia services received in connection with a dental service when provided in a hospital or freestanding ambulatory surgical center and: • the use of this is medically necessary; and • the setting in which the service is received is determined to be appropriate. This plan also covers facility fees associated with these services. This plan covers dental care for members until the last day of the month in which they turn nineteen (19). This plan covers services only if they meet all of the following requirements: • listed as a covered dental care service in this section. The fact that a provider has prescribed or recommended a service, or that it is the only available treatment for an illness or injury does not mean it is a covered dental care service under this plan. • dentally necessary, consistent with our dental policies and related guidelines at the time the services are provided. • not listed in Exclusions section. • received while a member is enrolled in the plan. • consistent with applicable state or federal law. • services are provided by a network provider.

  • Cloud Computing State Risk and Authorization Management Program (TX-RAMP In accordance with Senate Bill 475, Acts 2021, 87th Leg., R.S., pursuant to Texas Government Code, Section 2054.0593, Contractor acknowledges and agrees that, if providing cloud computing services for System Agency, Contractor must comply with the requirements of the state risk and authorization management program and that System Agency may not enter or renew a contract with Contractor to purchase cloud computing services for the agency that are subject to the state risk and authorization management program unless Contractor demonstrates compliance with program requirements. If providing cloud computing services for System Agency that are subject to the state risk and authorization management program, Contractor certifies it will maintain program compliance and certification throughout the term of the Contract.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.