Use Case Sample Clauses
A Use Case clause defines the specific situations, scenarios, or purposes for which a product, service, or agreement is intended to be used. It typically outlines the permitted applications or contexts, such as specifying that a software license is valid only for internal business operations or that a product may only be used in non-commercial research. By clearly delineating the acceptable uses, this clause helps prevent misuse, sets expectations for both parties, and reduces the risk of disputes over unauthorized or unintended applications.
Use Case. The purpose of tokens in 'read' and 'bring online' primarily is to steer data streams or better to steer the location of files. The space reservation aspect of tokens is of minor interest. An example is that the same dataset may be needed by the reprocessing system as well as for FTS export or user analysis. It would be envisioned that this file is served to the various competing processes by different locations in the system mainly not to interfere or slowdown expensive reprocessing.
Use Case. In order to evaluate the prototype, a dedicated server was setup in AUTH data center with the following specifications: • Operating System: Windows 2008 Server 64bit • CPU: 2 Xeon CPUs 2.5Ghz • RAM: 4 GB • Hard Disk: 20GB (SAS) plus 60GB (SATA) Remote access and networking were also established and the prototype application was installed and tested continuously during the last stages of development from September 2011 to November 2011. The final test was conducted from the 22nd to the 24th of November 2011. A ping server with high traffic was monitored during this time and 2 URL filters were set a) *▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇* and
Use Case. Autopilot Drone (AD) Overview
Use Case. For use by Client and in assessing and managing risk with respect to Regulatory Compliance Obligations (as defined in Section 1 of the Additional Terms and Conditions)
Use Case. The Contextualising Tool
Use Case. Fiat On-Ramp and Off-Ramp • Fiat-to-crypto conversion • Crypto-to-fiat settlement • Payment rail connectivity ▇▇▇▇▇▇.▇▇▇ enables regulated movement between fiat and digital assets. Nomyx coordinates these flows while enforcing identity, compliance, and transaction policies. Customer Integrations (To Be Defined) Customer-specific integrations may include, but are not limited to: • Front-end applications (web or mobile) • Core banking or payment systems • ERP, treasury, or accounting platforms • Internal compliance, risk, or reporting systems (Details of such integrations, including scope, responsibilities, timelines, and technical requirements, will be defined in a separate integration specification or statement of work at a later date, except that the Custom Integration, Configuration, Platform Extension or Development Deliverables agreed as of the Effective Date are set out in Appendix C). Customer Project T7X Assets LLC, together with its affiliates and Approved Sublicensees, is renewing its engagement with Nomyx under a single, consolidated agreement. T7X operates a digital asset exchange for real-world assets, supporting the trading and custody of tokenized securities and cryptocurrencies with integrated identity and compliance controls, and a Regulation A capital-raising platform (the Launch Pad) that enables issuers to structure, launch, and administer tokenized securities offerings. Both platforms are built on the Nomyx technology stack. Licensee’s use of the Nomyx Platform for the Customer Project is subject to Sections 3.2 and 10 of the Agreement. [***]
Use Case. MTQIP shall share MTQIP aggregated data set data with the Anesthesiology Performance Improvement and Reporting Exchange (ASPIRE) for the purpose of perioperative care quality improvement. ASPIRE may use MTQIP data for identification of patient outcomes. In exchange for sharing MTQIP data for the purpose(s) articulated ASPIRE will in turn share ASPIRE data with MTQIP to assist MTQIP to understand the relationship between anesthesia variables and outcome(s) to improve care and will be used in accordance with all uses enumerated in the Agreement. This Amendment, coupled with the underlying terms and conditions of the Agreement, contains and merges all of the terms and conditions between the parties with respect to the subject matter hereof without modifications. Participant: By: Print name: Title: Date of Signature: Address for Notice: Regents of the University of Michigan: By: Print name: _Jeanne ▇▇▇▇▇▇▇▇▇▇ Title: Chief Compliance Officer Date of Signature: Address for Notice: University of Michigan NCRC MTQIP Building 16, room 139E ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇▇▇▇, ▇▇ ▇▇▇▇▇-▇▇▇▇
Use Case. MTQIP shall share MTQIP aggregated data set data with the Anesthesiology Performance Improvement and Reporting Exchange (ASPIRE) for the purpose of perioperative care quality improvement. ASPIRE may use MTQIP data for identification of patient outcomes. In exchange for sharing MTQIP data for the purpose(s) articulated ASPIRE will in turn share ASPIRE data with MTQIP to assist MTQIP to understand the relationship between anesthesia variables and outcome(s) to improve care and will be used in accordance with all uses enumerated in the Participant’s current Data Use Agreement.
Use Case. In order to demonstrate the problem of guaranteeing QoS requirements, in a network with limited link capacity, this section presents a use case, which exemplifies the relation be- tween link utilisation and E2E delay. The use case acts a the reference scenario throughout the work of this project. Among current techniques for guaranteeing QoS in IP networks, there are Integrated services (IntServ), Differentiated services (DiffServ) and Multi-Protocol Label Switching (MPLS). IntServ suffer from not being scalable in larger backbone networks, due to its need for state information for every flow. DiffServ schedules packet transmission on a configured per-hop basis, hence it cannot guarantee E2E requirements. MPLS can set up tunnels throughout the network, in order to allocate bandwidth E2E, but only based on a simple counter value and not from a view of the global network state. However, combining MPLS and DiffServ can provide a synergy, where MPLS handles the path selection and DiffServ determines how to schedule packets along the way. But this also introduces the need for further distributed state information to map between Label Switched Paths (LSPs) and output queue, which again will decrease the scalability aspect of the solution. Furthermore, the technique is still not aware of the global network state and cannot adapt to the current networking conditions. The three techniques are all described in more detail in appendix B. The use case is based on the assumption, that an Internet Service Provider (ISP) is creating one tunnel per user, with a single scheduling policy for the tunnel, in order to maintain scalability as discussed above. That is, no configured per-hop behaviour for different traffic types within the tunnel, hence aggregating all traffic from one user into a single queue. To stress the fact that the network has limited link capacity, the network topology for the use case only has a single link in the backbone, thus no option for re-routing the traffic along another and less congested path. Combined with the assumption above, all traffic is transmitted via the backbone using a single output queue only, since a queue per user in the backbone is also not a viable solution in an ISP network. These descriptions are used for creating the network topology, which is introduced in the following section.
Use Case. In this section, we develop a realistic use case to illustrate the application of the energy aware SLA and the VNFD extension.