Web Interface Sample Clauses
The Web Interface clause defines the requirements and standards for any online platform or portal provided under the agreement. It typically outlines how users will access the web interface, the functionalities it must offer—such as data entry, reporting, or account management—and any security or accessibility standards it must meet. By specifying these details, the clause ensures that both parties have a clear understanding of the expectations for the web-based system, reducing the risk of disputes over usability or performance.
Web Interface. Customers who do not register their address with Masergy will be sent to the default emergency call center when they dial 9-1-1. A trained agent at the default emergency call center will ask for the name, telephone number and location of the end user calling 9-1-1, and then contact the local emergency center for such end user in order to send help. Examples of situations where 9-1-1 calls are sent to the default emergency call center include when there is a problem validating an end user's address, the end user is identified with an international location, or the end user is located in an area that is not covered by the landline 9-1-1 network. For purposes of 9-1-1 service, Customer may register an address with Masergy for the outbound calling line ID for either (i) each individual phone line ID or (ii) a single phone line ID, if Customer chooses to utilize a single phone line ID for all outbound calls. If the outbound calling line ID does not have a registered 9-1-1 address with Masergy, the call will be transferred to the default emergency response center without a corresponding address.
Web Interface. NTS will provide the Customer with password controlled access to a web interface where the Customer can view Device Performance Statistics.
Web Interface. The Web Interface is deployed in the demilitarized zone (DMZ). It provides users with access to SEMS applications hosted on a Citrix XenApp Server (a.k.a. Presentation Server) through a standard Web browser. The Web Interface works with the Citrix NetScaler Gateway to provide a logon interface and facilitates authentication and authorization of connection requests to the applications published.
Web Interface. 3.1 The Authority must only gain access to SPEAR via the SPEAR Internet Site using the Web Interface and must not use any program other than a standard internet browser to connect to SPEAR. The access granted is subject to compliance by the Authority and all Authority Users with this Agreement, the Common Rules, all User Manuals issued by the Department under clause 9 and all relevant Statutory Provisions.
3.2 Without limiting the foregoing, the Authority must not connect to SPEAR directly using any software application other than a standard internet browser unless such form of connection (commonly known as application to application environment) is approved in writing by the Department which approval may be withheld subject to satisfaction of appropriate standards.
3.3 The Department reserves the right to change the Web Interface or other aspects of SPEAR (including software required for access) from time to time.
Web Interface. We provide a msrw an application which provide a web based JSON service allowing JSON requests to control the acquisition of data from an msr. This Is documented in web_msr.pdf. These wrapper classes did not handle quoted parameters correctly. This has been resolved.
Web Interface. The web interface of this module presents the user with the necessary forms for the following tasks: • Preview on the client applications that he already registered • View on the details for particular application • Edit the information about the chosen application • Add new app • Remove a registered application • Request new client key-secret pair • Request access token for instant access The web interface acts as the client part in a client-server architecture. The communication with the server – Chon CMS Plugin – is done via HTTPS – either standard web browser POST/GET or AJAX. These extenstions make up the backend for the Web Interface and provide basic CRUD functions for the registered applications and functions for retrieval of the consumer key-secret pairs and access token (re)generation.
Web Interface. The LMI Universal web application allows users anywhere on the network with appropriate network access to view current status, a list of “incidents” (radiation alarms or instrument failures), or to view a particular instrument’s readings in graph form. The user need only use a standard web browser such as Internet Explorer or Mozilla Firefox to access the webpage. To access the webpage, enter the URL of the web application. This is typically:
Web Interface. The Surveyor must only gain access to SPEAR via the SPEAR Internet site using the Web Interface and must not use any program other than an Internet browser to gain such access.
Web Interface. 4.1 Help Feature. Help may be accessed by clicking on the Customer Service button near the bottom of the main PowerCAMPTM screen or by contacting the AER help desk.
4.2 Logging into Web Control Application ***
Web Interface. The access to the use case information, performance data and resulting graphics of the OpenQKD use cases is secured through user authentication and can be accessed over ▇▇▇▇▇://▇▇▇▇▇▇▇▇-▇▇▇▇▇▇▇.▇▇▇▇▇▇▇.▇▇/gui/ being the login page (fig. 2)