Use Case Description Sample Clauses

Use Case Description. The introduction of a massive number of renewable energy sources such as solar panels require a highly monitored distribution grid that can coordinate energy producers and consumers in real-time. This relies on a large number of automatic measuring devices such as PMUs (Phasor Measurement Units), with real-time data collection and synchronization carried out by PDCs (Phasor Data Concentrators). These devices, already in use on the high voltage grid, provide the data used to compute the grid state estimate for monitoring and control applications.
Use Case Description. Unqork will be used as the platform for the build of [Name of Application] for [Description of use case, applicable user base and division of Customer if relevant] (the “Use Case”). Utilization of the Use Case for the benefit of any other subsidiaries or affiliates of Customer, in regions other than the United States, or for capabilities other than as stated above, will require an amendment to this Order or additional Order(s) to be negotiated by the Parties. Unqork will provide to Customer the necessary Access Credentials to allow Customer and its Authorized Users to access the Use Case upon execution of this Order or, if different, on the Start Date specified in Section 4 of this Order.
Use Case Description. TerraviewOS, is a unified platform for viticulture, enables the grower to manage information from many sources, returning high-value info such as yield estimation, smart irrigation, and disease prediction and diagnosis. Since TerraviewOS is cloud- based, a key problem is the interaction with on-field devices in the presence of poor network connectivity. Operations such as drone aerial surveys (approximately 30-40GB of data for a modest area of 10 hectares) may return their valuable results with large delays, resulting in potentially poor user experience or indeed non- operation for customers.
Use Case Description. Mobile robots for Industry 4.0, smart logistics, and retail are resource-constrained and battery-powered mobile robots that operate in shared spaces with humans and other IoT devices, such as elevators, automatic doors, and other mobile robots. For autonomous operation, mobile robots are equipped with sensors and high-performance computational algorithms that (1) need considerable computing power and (2) need to be executed at the highest speed.
Use Case Description. The problem arises when different or seemingly conflicting access privileges are expected to occur regarding models, datasets and other services. A client needs to validate a model against confidential data to which he might have no access. Regarding user privileges, the following alternative cases may occur: Access to the test dataset Access to the QSAR model Yes/Yes Yes/No No/Yes No/No The most representative cases are the Y/Y and the N/N case (as the Y/N and N/Y cases are actually sub-cases of the N/N case). In case that the user has access both to the test dataset and the QSAR model (Y/Y), the framework has to take care of the access privileges on any resources (datasets) created as predictions from the model so that confidential information will not leak from the validation service. Current access control infrastructure of OpenTox, combined with the REST architecture, caters for the protection of all these resources. In the second case, where the user has not access either to the model or to the test dataset, it becomes evident that a second user with enhanced privileges has to intervene and perform the validation on behalf of the first user exposing back to him just the validation report but no information regarding the test set and/or the model. For validation purposes OpenTox can provide a facility to test (Q)SAR models remotely against confidential datasets without getting access to the actual entries of the database to ensure security and confidentiality of proprietary data.
Use Case Description. ‌ In June 2018 the project has started as a collaboration between two universities: the VU Amsterdam and UNIMAS. In the first week of June there was a lot of field work, where information was collected from local communities and different stakehold- ers. A few use cases were collected. The banana use case amongst others was picked as one of the use cases that have a lot of potential. Stakeholders that are involved in this use case are farmers, the agricultural department, and the banana chips factory. Fortunately, the BannaTree team has the chance to meet and interview all parties. Below, all the interviews are summarized to get an overview of all the information that was collected from the use case.
Use Case Description. A software application that enables state and local governments and their partners (each, a “Customer”) to effectively manage and distribute rental housing assistance and other qualified funds, in compliance with the Consolidated Appropriations Act 2021 (ERAP 1) (the “Rent Relief Platform”) and the American Rescue Plan Act – the Emergency Rental Assistance Program (ERAP2) The Rent Relief Platform has been adapted to take into account additional guidance for ERAP 2 and remains functional and compliant in accordance with the requirements of ERAP 1.

Related to Use Case Description

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Site Description {Buyer Comment: Provide a legal description of the Site, including the Site map.}

  • Service Description 2.1 General

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Work Description T-804 Opening Roads - Removal of closure devices, cleaning ditches, removing berms, and blading the traveled-way T-811 Closing Roads - Entrance treatment for 150' cross-rip; debris block (slash, earth, berm, rocks, etc.) + seed + water bar T-811 Closing Roads - Water bar frequency per BMPs for remainder of road T-811 Closing Roads - Engineering Rep. or Construction Inspector must be notified prior to performing closeout 9314A Single Lane / Level 1 NFSR 9314 0.00 END 0.20