Use Cases. Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.
Use Cases. To enter into a Use Case, Participant must review and accept the terms surrounding a specific Use Case. The terms of a specific Use Case are set forth in a “Use Case Exhibit” or “UCE” and, upon acceptance, each Use Case Exhibit is subject to the terms of this Master Use Case Agreement and incorporated herein by reference.
Use Cases. All new use cases must be reviewed by the Data Owner or their delegate for acceptable use. All reported data must be aggregated and appropriately de-sidentified unless approved by the Data Owner or their delegate. Any ad hoc analyses or other use of the data, not specified in this Agreement, is not permitted without the prior written agreement of <AA>. Disclosure Reports are only to be disclosed as specified in section 6. Use Cases. Retention Data obtained through this agreement must not be retained outside of <System B>, except as specified in section 6.
Use Cases. The products in Europeana Food & Drink that fall or may fall onto this category are: • Exhibition and virtual exhibition • Semantic demonstrator • Technical demonstrator • e-learning platform/content
Use Cases. Customer will comply with the Use Case Restrictions available at xxxxx://xxxxxxxx.xxxxxxxx.xx/?itemUid=d78e37b4-3cb3-4588-b1e3-a976e2bfc730&source=title..
Use Cases. In this section, we present industry and academic use cases in Cloud computing environments.
Use Cases. The core of the service-oriented FLAME architecture is the capability to decouple the relationship between service instances (management plane) from how packets are being sent between them (control and data plane). In order to describe the advantages of the FLAME architecture, the following use cases have been identified which are described in further detail combined with an exemplary scenario.
Use Cases. The use cases presented in this chapter cover the interlock function as well as the driving mode selection of the EV demo. Precondition: Vehicle in parking mode for maintenance operation Operator opens the HVJB cover. The interlock is opened and thus the battery stops providing energy automatically Precondition: Vehicle running (in any manoeuvre scenario). A fault condition that implies a disconnection of any high voltage connector in the system occurs EVC detect the failure through the HVJBInterlockIn Line. EVC set torque request to 0 to the power electronics. EVC shut down the battery through the signal PowerSourceEnable. EVC check the shutdown execution through the signal MainRelaySts. Precondition: Vehicle speed above 6 km/h Driver presses the Backward driving button. The backward driving mode is forbidden. Precondition: Vehicle in parking mode. Vehicle speed is below 5 km/h. Driver presses the normal driving button and the brake pedal. The D gear mode is enabled. Precondition: Vehicle speed above 6 km/h Driver presses parking mode button and brake pedal. A status change to P will not be accepted above 6 km/h forward speed. In this case no more drive torque is commanded by the accelerator pedal. As soon as the vehicle speed decreases below 6 km/h the parking mode is activated. Precondition: Vehicle speed below 6 km/h Driver presses parking mode button and brake pedal. Parking mode is engaged.
Use Cases. UC1: Engage brake until minor retardation occurs UC2: Engage brake until normal retardation but no wheel lock occurs
