Constraint Sample Clauses

Constraint. An upper or lower limit placed on a variable or set of variables that are used by the ISO in its SCUC, RTC or RTD programs to control and/or facilitate the operation of the NYS Transmission Systems. Contingency: An actual or potential unexpected failure or outage of a system component, such as a Generator, transmission line, circuit breaker, switch or other electrical element. A Contingency also may include multiple components, which are related by situations leading to simultaneous component outages. Contract Establishment Date: The date, listed in Attachment L, on which the listed existing agreements which are the source of Grandfathered Rights and Grandfathered TCCs were executed.
AutoNDA by SimpleDocs
Constraint. The functionality mentioned in the deliverables will have to either work within or work around the limitations of the environment. These include browser capabilities, product capabilities, interface capabilities etc. Selectica suggests that the testing environment be restricted to Netscape 4.x and Internet Explorer 4.x (JavaScript 1.2 compliant versions only) on Windows NT, 95 and 98 platforms.
Constraint. A restriction or limitation that influences the project plan. For example, a target date may be a constraint on scheduling. A schedule may be constrained by resource limitations. Configuration Management Method for managing the software builds versions during the project lifecycle. Contract Management Methods and process for controlling and managing the project contract(s).
Constraint. A constraint can be at the position-level or at the velocity level. A constraint can be an equality constraint (target), or an inequality constraint (target_lower / target_upper). A position-level constraint expresses the desire that a given expression evolves towards and follows a given target. The dynamics by which this expression evolves is specified by a value K whose semantics are defined by the solver (see later). A set of constraints can be conflicting, i.e. they cannot be satisfied simultaneously. Constraints with a higher priority are always satisfied before lower priority constraints. To ensure safety, the highest priority constraints cannot be conflicting. Conflicting constraints of the same priority can be given a weight to indicate their importance with respect to each other. Semantically, the constraints specify a Lagrange condition (i.e. enforced along the whole time interval the task controller is active); they do not specify a Xxxxx condition (that only needs to be achieved at the end of the task). A constraint definition is given by: Constraint{ context = <context> name = <string> [optional, default_name<nr>], expr = <expression> target = <value> [optional, 0.0], target_lower = <value> [optional, 0.0], target_upper = <value> [optional, 0.0], K = <value> [optional, defaultK], K_lower = <value> [optional, defaultK], K_upper = <value> [optional, default, weight = <value> [optional, defaultweight], priority = <integer value> [optional, defaultpriority] } The right hand side of expr gives the expression on which the constraint is defined (see appendix A for the syntax of an expression). Name gives the name of the expression. Diagnostic messages can refer to this name. If the name is not specified, a default name and a sequence number is used. context refers to the context where the constraint will be defined. For equality constraints, target refers to the target value of the expression. The controller will try to regulate the robot system such that the expression will evolve towards the specified target value. For inequality constraints target_lower and/or target_upper specify the lower and upper bound for the expression. K specifies how fast you want to regulated towards the given value. In case of a upper and a lower bound (target_lower/target_upper), you can also specify a separate value for K for the upper and lower bound (K_lower/K_upper). weight specifies the weight of the constraint. This weight specifies what happens when there are con...
Constraint. (9) must hold eąuality because otherwise there exists a new contract (M , N , R, P } with M = M + s and N = N + s where s ≤ x — y — M , which would generate a higher payo to the type G manufacturer than the old contract (M, N, R, P } and yield the same cash flow to the type B manufacturer.5; As a conseąuence, constraint (l8) is automatically satisfied. Following the same logic, we can show that S = fx + fkбx — 2y. 2H N?_ih | i ?i UL?|h@U| ti|| ?}c @** | i ?i^ @* |) @?_ i^ @* |) UL?t|h@ ?|t @hi t| ** t@| t i_
Constraint. While our study supported the used of US as an accurate diagnostic tool for detecting tendo-ligamentous and soft tissue related ankle lesions, we couldn’t state that US could ultimately replace the need for the more costly, time-consuming MRI in detecting ankle joint abnormality. This is obviously much needed to elevate a great health burden, and allow easier accessibility for patients to get more timely, less expensive, and less tiring imaging experience.
Constraint. 5.1 The party undertaking a mobile marketing campaign will provide a global "throttling mechanism" capable of managing the number of messages received by an individual consumer. The purpose of the throttle is to effectively manage and limit mobile marketing programs to a reasonable number of programs, defaulted to 3 per day. Consumers will have the option to override the throttle through an additional Opt-in available through the standard channels.
AutoNDA by SimpleDocs
Constraint. Other NGOs Offering Material and Cash Support Jeopardize Commissioners’ Spirit of Volunteerism Issue: Some international NGOs with projects in MHPP areas are offering monetary or in-kind (equipment) incentives which is having is resulting in Xxxx Commissioners having similar expectations from Concern and less willingness to offer their time voluntary. Impact: In some wards this is hindering the development of WHCs and Commissioners’ cooperation as Cabinet members regarding MHPP activities. Actions to Overcome: The MHPP team is discussing the issue with those who have such complaints and reminding them of the importance of sustainability. They have been able to placate some individuals but the issue is still looming.

Related to Constraint

  • Constraints The Joint Committee on Benefits will not make any changes to the plan provisions that would increase the costs of health and welfare benefits or disability benefits for individual employers or reduce plan provisions without the agreement of the Parties to this Agreement. The Joint Committee shall be authorized to determine appropriate use of the Article 9.1.3 savings from the 1998-2001 agreement (in the amount of $71,849) and to allocate the funds to that use.

  • Workloads (a) The parties agree that patient care is enhanced if concerns relating to professional practice, patient acuity, fluctuating workloads and fluctuating staffing are resolved in a timely and effective manner.

  • Downtime Due to the nature of server provision, downtime and lost transmissions may occur as part of routine maintenance. You are advised to maintain a copy of your account status and details of Content purchased.

  • Traffic The provisions in this Section apply regardless how the ISP-bound traffic is determined.

  • Workload An employee who believes that her workload is unsafe or consistently excessive shall discuss the problem with her immediate supervisor. If the problem is not resolved in this discussion, the employee may seek a remedy by means of the grievance procedure. If the matter is not resolved in the grievance procedure, it may be referred to troubleshooter who shall:

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Service Outages (a) Service Outages Due to Power Failure or Disruption. 911 Dialing does not function in the event of a power failure or disruption. If there is an interruption in the power supply, the Service, including 911 Dialing, will not function until power is restored. Following a power failure or disruption, you may need to reset or reconfigure the Device prior to utilizing the Service, including 911 Dialing.

  • Transit Traffic The following rates will apply:

  • Maintenance Outages If Seller reasonably determines that it is necessary to schedule a Maintenance Outage, Seller shall notify Buyer of the proposed Maintenance Outage at least five (5) days before the outage begins (or such shorter period to which Buyer may reasonably consent in light of then existing conditions). Upon such notice, the Parties shall plan the Maintenance Outage to mutually accommodate the reasonable requirements of Seller and the service obligations of Buyer; provided, however, that, unless Buyer otherwise consents, such consent not to be unreasonably withheld, no Maintenance Outage may be scheduled between the hour ending 0700 through the hour ending 2200, Monday through Saturday, during the time period commencing on May 15 and concluding on September 15. Notice of a proposed Maintenance Outage shall include the expected start date and time of the outage, the amount of Capacity of the Facility that will not be available, and the expected completion date and time of the outage. Seller shall give Buyer notice of the Maintenance Outage as soon as Seller determines that the Maintenance Outage is necessary. Buyer shall promptly respond to such notice and may request reasonable modifications in the schedule for the outage. Seller shall use all reasonable efforts to comply with any request to modify the schedule for a Maintenance Outage. Seller shall notify Buyer of any subsequent changes in Capacity available to Buyer or any changes in the Maintenance Outage completion date and time. As soon as practicable, any notifications given orally shall be confirmed in writing. Seller shall take all reasonable measures and exercise its best efforts in accordance with Prudent Electrical Practices to minimize the frequency and duration of Maintenance Outages.

Time is Money Join Law Insider Premium to draft better contracts faster.