Smart_Actuator Sample Clauses

Smart_Actuator. The Smart_Actuator class represents actuator devices capable or processing complex commands and provide complex actuating mechanisms. Examples of smart actuators can be found in intelligent appliances, such as programmable washing machines or air conditioning systems. Generalizations • Actuator Object Properties • accepted_commands: Smart_Actuator_Command_Information (multiple). The accepted_commands property relates the smart actuator device with the command set it is capable of managing. Data Properties None Restrictions [1] A value actuator may not include in its provided_services property services from the following list: Value_Command_Write_iEi_Service, Reset_Command_Write_iEi_Service. This restriction refines the restriction introduced in the parent class Actuator.
Sample 1
AutoNDA by SimpleDocs

Related to Smart_Actuator

  • Brakes Master cylinder, wheel cylinders, hydraulic lines and fittings, power booster and brake callipers. Excludes linings, pads, drums and discs.

  • Telemetry The Meters shall be capable of sending meter telemetry data, and Seller shall provide Buyer with simultaneous access to such data at no additional cost to Buyer. This provision is in addition to Seller’s requirements under ISO-NE Rules and Practices, including ISO-NE Operating Procedure No. 18.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Local Switching Interfaces 4.2.13.1 Newcomm shall order ports and associated interfaces compatible with the services it wishes to provide as listed in Exhibit A. BellSouth shall provide the following local switching interfaces:

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Cameras j) Portable music player, headphones.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

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