User Interfaces Sample Clauses

User Interfaces. Prior to launch of any Information Service, LICENSOR will submit the user interface for such Information Service to AT&T for review and approval or disapproval.
Sample 1Sample 2
User Interfaces. It is of utmost importance for a solution to have a wide range of user interfaces allowing a convenient interaction with the testbed. We present here the major ones classified by category. It is important that any singular testbed belonging to the federation can use its own user interfaces and still have access to the federated resources. This is not compatible to the possibility of having an extra UI shared by the federated testbeds. • sfi.py (in the Generic SFA wrapper codebase) • omni: xxxx://xxxx.xxxxxx.xxx.xxx/gcf/wiki/Omni • sfaclientlib (in the Generic SFA wrapper codebase) • java client library [no url] • sface: xxxx://xxx.xxxxxx.xx/?p=xxxxx.xxx;a=summary • MySlice (recommended): xxxx://xxx.xxxxxxx.xxxx (see Section 4.4) • XXXXXX webUI (now integrated with the current clearinghouse implementation)
Sample 1
User Interfaces. 1) The system will normally be operated through a remote interface using a SCADA setup based on the Cromi software. 2) In Cromi, the communication of variables is based on OPC connection between the SCADA server software and the high level control system (Schneider PLC) and data is logged into SQL database (local, remote or both). 3) A cloud based SQL database will be set up that will allow the project stakeholders to access the operational data over the internet. 4) VTT has Matlab scripts written for extracting the data from the SQL database that may be shared to the project participants. Participants may also develop their own tools to access the data on the server, if preferred.
Sample 1
User Interfaces. The main user interface to Porto is a scripting shell based on ECMAScript. It will be possible to use the scripting both as batch processes and as an interactive process. Different Porto-modules and extensions can be loaded at run-time.
Sample 1
User Interfaces. User interfaces must be developed for the functions described in Section 4. Standard drop-down lists are used wherever possible to present standard values for selection by the User. Command buttons, Pop-up windows, and other aids should be used where possible to make the product easier to use. Online help should be available for each screen developed for this application. Web page formats must follow the State of Washington guidelines found at the following web site: Information Technology Division March 16, 2010 Page 12 Planning and Project Office SRS version 2.1 This section specifies the functional capabilities of the product. These requirements are organized by the major functions described in section 2.2.
Sample 1
User Interfaces. All users will interact with PACIS II via a Graphical User Interface (GUI).
Sample 1
User Interfaces. Activities Business Objects Business Objects Interface Proxies Interface Proxies Naming/ Trading Service Transaction Service Workflow Facility Solution Component Solution Component Interface Skeletons Interface Skeletons Activities Activities Business Objects Interface Proxies Business Objects Interface Proxies Extent Extent Application Application
Sample 1
User Interfaces. The default language for Acsepto and CTM download user interfaces (messages and screens, online documentation) is English.
Sample 1

Related to User Interfaces

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • 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.

  • Network Interface Device 4.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 on-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. 4.1.1 BellSouth shall permit Al-Call to connect Al-Call ’s loop facilities to on-premises wiring through the BellSouth NID or at any other technically feasible point.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • 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.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

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