Futility Sample Clauses

Futility. Plaintiff contends that Xxxxxxxxx’s breach of fiduciary duty counterclaims are futile. An amendment is futile where it “would not withstand a motion to dismiss.” Shoshone Indian Tribe of the Wind River Reservation v. United States, 71 Fed. Cl. 172, 176 (2006). The party seeking leave “must proffer sufficient facts supporting the amended pleading that the claim could survive a dispositive pretrial motion.” Kemin Foods, X.X. x. Pigmentos Vegetales Del Centro S.A. de C.V., 464 F.3d 1339, 1354-55 (Fed. Cir. 2006); see also Dotcom Assocs. I, LLC v. United States, 112 Fed. Cl. 594, 598-99 (2013).
AutoNDA by SimpleDocs
Futility. Xxxxxxx argues that the motion for leave to amend should be denied because the three proposed amendments to the complaint are futile. (D.I. 190 at 11–18) Xxxxxxx argues the additional claims in the amended complaint fail to state a claim under Fed. R. Civ. P. 12(b)(6). (Id.) The standard for assessing the futility of an amendment under Fed. R. Civ. P. 15(a) is the same standard of legal sufficiency applicable under Fed. R. Civ. P. 12(b)(6). City of Cambridge Ret. Sys.
Futility. The Court now moves to Xxxxxxxx’x contention that permitting the proposed amended complaint would be futile because it would not survive a motion to dismiss. The Court begins with Xxxxxxxx’x argument that Xxxxxxx lacks standing to bring a derivative claim on behalf of Plant 64 DCMC before turning to the viability of each claim in the amended complaint.
Futility. “An amendment to a pleading will be futile if a proposed claim could not withstand a motion to dismiss pursuant to Rule 12(b)(6).” Xxxxxxxxx v.
Futility. [11] In United States x. Xxxxxxx, we concluded that Native Americans charged with violating the Eagle Act could make an as-applied challenge to the Act’s permit- ting system without applying for permits if they demonstrated that ‘‘it would have been futile ... to apply for permits.’’ 297 F.3d 1116, 1121 (10th Cir.2002) (en banc). Citing our decision in Xxxxxxx, the dis- trict court here found ‘‘futility in the appli- cation process.’’ Gov’t App. 190. On this basis the court concluded that the Eagle Act, without an effective permitting sys- tem, substantially burdened Mr. Xxxxxx’s religion in a manner more restrictive than is necessary. Examining the record and reviewing this conclusion de novo, see Xxxx, 466 U.S. at 501, 508, 104 S.Ct. 1949, we disagree. While the district court cited Xxxxxxx in making its finding of ‘‘futility,’’ it also acknowledged that it was really deciding a fundamentally different issue than arose there. In Xxxxxxx, the defendants were not members of a federally recognized tribe, and were therefore explicitly forbid- den from applying because ‘‘the application itself require[d] certification of member- ship.’’ 297 F.3d at 1121; see 50 C.F.R. § 22.22(a)(5). In other words, it was legal- ly futile for them to apply because they were legally ineligible. In contrast, Mr. Xxxxxx, who is a member of a federally recognized tribe, ‘‘does not have the same impediment.’’ Gov’t App. 190. He is xx- xxxxx eligible for a permit, and so far as we know may receive one if he applies. The district court nonetheless concluded that it was ‘‘clear’’ from the record that Mr. Fri- day would not have received a permit if he had applied for one, even though he is legally eligible: The Defendant and the tribal members testifying on his behalf were not aware of the possibility of obtaining a permit to take an eagle. The statute expressly contemplates a permitting process for the taking of eagles for Indian religious purposes, relying on the Secretary of the Interior to implement regulations to make this accommodation to our Native Americans. Yet, testimony at the hear- ing revealed that as recently as 2003, the Secretary had not delegated the au- thority to process fatal take permits for Indian religious purposes. The evidence is that prior to 2003, only four such applications were submitted—three were issued and one denied Al- though the Fish and Wildlife Service utilizes outreach programs in an attempt to increase the understanding of its Re- pository progr...

Related to Futility

  • Utility Any service provided by an outside source or manufactured in-house that facilitates building operations (e.g., gas, water, electricity, fire suppression water, fire alarm systems).

  • 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.

  • 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.

  • Preventive Maintenance The Contractor shall provide necessary preventive maintenance, required testing and inspection, calibration and/or other work necessary to maintain the equipment in complete operational condition during the warranty period.

  • 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.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

  • Uncontrollable Forces 12.1 Section 14.1 of the CAISO Tariff shall be incorporated by reference into this Agreement except that all references in Section 14.1 of the CAISO Tariff to Market Participants shall be read as a reference to the Scheduling Coordinator and references to the CAISO Tariff shall be read as references to this Agreement.

  • Underutilization Underutilization of Interconnection Trunks and facilities exists when provisioned capacity of trunks in service for more than six (6) months is greater than the current need. This over-provisioning is an inefficient deployment and use of network resources and results in unnecessary costs. Those situations where more capacity exists than actual usage will be handled in the following manner: a. If a final trunk group is under seventy-five percent (75%) of CCS capacity or a high usage trunk group is under 90% of CCS capacity on a monthly average basis, for each month of any three (3) consecutive months period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty-five percent (25%) excess capacity. In all cases POI requirements and grade of service objectives shall be maintained. b. CLEC will send an ASR to CenturyLink to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!