Problem Definition Sample Clauses

Problem Definition. 1.1.1 The Nature of Energy Flows
AutoNDA by SimpleDocs
Problem Definition. Customer shall record the following information for reference and provide it to Upland: (a) error messages and indications that Customer received when the malfunction occurred; (b) what the user was doing when the malfunction occurred; (c) what steps Customer has taken to reproduce the malfunction; (d) what steps Customer may have already taken to solve the problem; and (e) system logging Severity Impact 1 Production system Defect that prevents business critical work from being done, no Workaround exists, and Defect impacts most Users; or Defect causes a material loss of Customer Data in production system; or Security-related Defect. 2 Production system Defect that prevents business critical work from being done and a Workaround exists; or Defect violates the material specifications in the Documentation and impacts Customer’s production system.
Problem Definition. To assist in expeditiously resolving Customer’s problem, the Customer should record the following information for reference and should provide the information to Alchemy: (a) error messages and indications that Customer received when the malfunction occurred, (b) what the user was doing when the malfunction occurred, (c) what steps Customer has taken to reproduce the malfunction, (d) what steps Customer may have already taken to solve the problem and (e) product version.
Problem Definition. The following standard problem definitions will apply to the performance of Member Youth Services under this Service Level Agreement. Priority 1 Mission critical Serious service, and/or financial impact Priority 2 Extremely urgent Significant service and/or financial impact Priority 3 Urgent Medium service and/or financial impact Priority 4 Medium priority Minimal service and/or financial impact Priority 5 Low Priority No service and/or financial impact
Problem Definition. As mentioned earlier, members in a distributed comput- ing environment can be distributed over the Internet. Fur- thermore, the members can be at a workstation, a laptop, or even at a mobile computer. Conventional group key agreement protocols request all members to contribute to a GK. Consequently, a low performance member or a member located on a high network latency area could MAC (Media Access Control) address [9] by checking his member information DB. After approving members iden- tification, all members start to generate a group key by sending his blind key to the GCS who collects all blind keys and store them into the Blind Key Queues (BKQ) in order of arrival. Then the GCS informs participants who will join the next level of the group key generation. A group controller server (GCS) is similar to the Vir- tual Synchrony [16] that uses a client daemon program to manage membership. The Virtual Synchrony (VS) dae- mon runs on each members machine and synchronizes with other VSs to update membership whenever mem- bership changes. Each member can know other members status due to VS. TGDH uses a VS for maintaining mem- berships. However, Using VS involves complex processes to synchronize with all other VS daemons because mem- bers request a lot of message exchanges to update their status. In the mean time, the QGDH establishes a GCS server instead of running VS daemons on all members machines. Therefore, only one machine in the proposed protocol takes a responsible for a GCS. Current group communication protocols use a self- Figure 2: Queue-based group Xxxxxx-Xxxxxxx entity model Figure 3: The blind key queues in group controller server signed certificate for member authentication, which has a well-known weakness in that members cannot ensure that the name on the public key is really a true member’s to measure members computing power and the other is to measure network latency. These two factors directly affect the performance of a GKGP. No matter how high perfor- xxxxx the machine, if the time taken for communicational messages to traverse the network is long, then the member must be regarded as low performance. Therefore, BKQ is a simplest way to measure for computing power and net- work latency at once. The number of levels in the GKGP can be determined by a group size. If the group size is n, then the number of levels is log2(n + 1). In the first level, all members are required to generate a blind key. In the next level, The GCS assigns two blind keys...
Problem Definition. To construct a device allowing a bilateral amputee to swing a golf club consistently and effectively. Our primary goal is to create a device that allows a bilateral amputee to use their everyday prosthetic arms to swing a golf club. Our secondary goal is creating a device that also functions in a way so that anyone can test it, including people who have full use of both arms. This secondary goal is necessary because upper extremity bilateral amputees are extremely rare. By designing a device that anyone can test, we can allot ourselves more time to make proper adjustments to our device in the future. Our final goal is to design a device that the amputee can independently attach and detach from the golf club, allowing them to play golf independently without the assistance of others.
Problem Definition. To assist in expeditiously resolving Licensee’s problem, the Licensee should record the following information for reference and should provide the information to ElementLMS: (a) error messages and indications that Licensee received when the malfunction occurred, (b) what the user was doing when the malfunction occurred, (c) what steps Licensee has taken to reproduce the malfunction, (d) what steps Licensee may have already taken to solve the problem and (e) product version.
AutoNDA by SimpleDocs
Problem Definition. In this section we propose a key agreement scheme for secure home networks that would: 1) Allow devices to join the network while main- taining backward secrecy; 2) Allow devices to seamlessly leave the net- work while maintaining forward secrecy; 3) Leverage the fact that a returning device was previously part of the network to allow this device to seamlessly rejoin the network.
Problem Definition. The objective of outpatient scheduling is to find an appointment system for which a particular measure of performance is optimized in a clinical environment – an application of resource scheduling under uncertainty.” (Xxxxxxx & Xxxxx, 2003, p.520) The design of an appointment system can in fact be seen as the design of a set of rules that 1) determines how patients will be assigned to appointment times (i.e. how the empty schedule will be filled up) and 2) guides the execution of the obtained schedule on the appointment day itself. Designing this set of rules boils down to making decisions regarding a set of control parameters and mechanisms. In the process of designing an appointment system, the following questions should be addressed: - How many patients should be given the same appointment time? - How many patients are given an identical appointment time at the start of a session? - What should the interval between two successive appointment times be? - Will patients be assigned to appointment times and will appointment intervals vary depending on the patient class they belong to or will there be no patient classification? - How will no-shows, walk-ins, urgent patients, emergencies and/or second consultations be dealt with? - How many appointments will be scheduled per clinic session? - Will patients be scheduled in an offline or online manner, in a static or dynamic way? - What queue discipline will be used? Thus, the problem of outpatient scheduling essentially comes down to the problem of determining the way in which patients will be scheduled and the way in which the schedule will be executed. Designing this set of rules is done in such a way that a particular measure of performance is optimized. Various such criteria to evaluate the performance of an appointment system exist. Examples are patient waiting time, doctor overtime or doctor utilization. Making decisions on how to design the appointment system based on these criteria can be complicated, since some of the criteria are competing and thus making decisions in favor of one of the criteria can possibly negatively influence another criterion. Furthermore, multiple stakeholders are involved (patients, doctors, administrators, …) each of which attaches varying importance to the different criteria. The decisions to be made when designing the appointment system will be influenced by several factors, specific to the clinical environment for which the system is designed. These factors that character...
Problem Definition. Customer shall record the following information for reference and provide it to Iternal: (a) Defect messages and indications that Customer received when the malfunction occurred; (b) what the User was doing when the malfunction occurred; (c) what steps Customer has taken to reproduce the malfunction; (d) what steps Customer may have already taken to solve the problem; and (e) system logging.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!