From Casetext: Smarter Legal Research

Gurasich v. IBM Ret. Plan

UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA
Jan 29, 2016
Case No. 14-cv-02911-DMR (N.D. Cal. Jan. 29, 2016)

Opinion

Case No. 14-cv-02911-DMR

01-29-2016

JOAN GURASICH, Plaintiff, v. IBM RETIREMENT PLAN, et al., Defendants.


ORDER GRANTING IN PART AND DENYING IN PART DEFENDANTS' MOTION FOR SUMMARY JUDGMENT; GRANTING IN PART AND DENYING IN PART PLAINTIFF'S MOTION FOR SUMMARY JUDGMENT

Re: Dkt. Nos. 35, 42

This is a dispute about entitlement to pension benefits pursuant to the Employee Retirement Income Security Act of 1974 ("ERISA"). Plaintiff Joan Gurasich brings this action against Defendant IBM Retirement Plan ("IBM Plan"), as well as Defendant International Business Machines Corporation ("IBM") as the Plan Administrator. The parties filed cross-motions for summary judgment and partial summary judgment. Defs.' MSJ, Docket No. 35; PL's MSJ, Docket No. 42. Having considered the parties' submissions and oral argument, and for the reasons stated below, Defendants' motion is granted in part and denied in part, and Plaintiff's motion is granted in part and denied in part.

I. FACTS

The facts set forth below are undisputed unless otherwise stated. Plaintiff is a former IBM employee. The parties dispute her entitlement to retirement benefits under the IBM Plan. The parties agree that Plaintiff was vested in the IBM Plan. Their central disagreement is whether Plaintiff's right to pension benefits terminated when she stopped working for IBM. Defendants contend that Plaintiff's pension rights terminated because she transferred employment from IBM to another company as a result of the sale of the IBM business unit where she had been working. According to Defendants, Plaintiff's IBM Plan assets were transferred to her subsequent employer's benefit plan as part of that transaction. Plaintiff contends that she did not end her employment with IBM as part of an IBM asset sale; instead, she voluntarily quit IBM to take a job with Siemens, which happened to be the same company that eventually ended up purchasing her former IBM business unit. Plaintiff argues that she is entitled to pension benefits, as evidenced by the many IBM Plan benefit notices that she received over the years from 1999 until she made a claim for benefits in 2013. She asserts that if the IBM Plan transferred her pension assets to another employer, it had no right to do so.

A. Plaintiff's Employment History

Plaintiff began working for ROLM Corporation ("ROLM") on January 24, 1980. In 1984, IBM acquired ROLM; as a result of that acquisition, Plaintiff became an IBM employee and a participant in the IBM Plan. For example, documentation from 1988 shows that Plaintiff was classified as an IBM employee, assigned an IBM employee number, and identified as an IBM employee on her paychecks and W-2 statements.

After leaving IBM on February 15, 1990, Plaintiff went to work at Siemens PN as the Director of Voice Data Solutions Marketing. Plaintiff worked at Siemens PN from February 19, 1990 until July 24, 1997, and became a vested participant in the Siemens Retirement Plan. On February 1, 2012, Plaintiff began receiving a monthly benefit under the Siemens Retirement Plan which was calculated based on an employment history from January 24, 1980 to July 24, 1997, even though Plaintiff did not begin working for Siemens until February 19, 1990.

The Plan Administrator acknowledged that Plaintiff left her employment with IBM on February 15, 1990. See Administrative Record ("AR") 12, 123. However, in their briefing, Defendants step away from acknowledgement of the February 15, 1990 date, and instead state that "Plaintiff was an employee who was part of [a transfer of 8000 employees from IBM to ROLM] on September 30, 1989." Defs.' MSJ at 8. The significance of Defendants' change of position on this point will become clear in the court's discussion of Plaintiff's first cause of action.

B. Plaintiff's Claim for Benefits Under the IBM Plan

In the years following her separation from IBM, the IBM Plan sent Plaintiff numerous communications stating that she had a vested benefit under that plan. These communications include an August 31, 1999 fax of a notice of deferred vested benefit in the amount of $978.90 [AR 111-113]; an August 27, 1999 cover letter enclosing materials on retirement [AR 100]; a December 14, 2010 cover letter for a mailing regarding the IBM Plan summary annual report and summary plan description [AR 60]; an April 29, 2011 letter enclosing a copy of the 2010 annual funding notice for the IBM Plan [AR 61-67]; an October 14, 2011 notice of a vested benefit in the IBM Plan [AR 68]; an October 24, 2011 monthly pension benefit estimate of $978.90 [AR 69-81]; a January 6, 2012 letter from IBM informing Plaintiff that she had an outstanding vested benefit under the IBM Plan [AR 82]; an April 26, 2012 IBM Plan annual funding notice [AR 83]; and a March 12, 2013 monthly pension benefit estimate of $978.90 [AR 84-96]. The monthly pension benefit estimates state "we have estimated your benefits payable from the Plan based on certain detailed assumptions and data that IBM has in its personnel records. If these records contain any errors, the amounts shown are subject to change." See AR 69-81; 84-96.

On April 2, 2013, Plaintiff sent a Pension Election Confirmation package to the IBM Employee Services Center. On July 10, 2013, Plaintiff called the IBM Employee Services Center and was told that she was not eligible to receive a benefit under the IBM Plan. Plaintiff sent a letter dated August 12, 2013 to the Plan Administrator requesting a written explanation of the basis for the denial of her claim.

On October 1, 2013, the Plan Administrator sent Plaintiff a denial letter, explaining that Plaintiff had terminated her employment with IBM in 1990 pursuant to an agreement between IBM and ROLM, which included a pension asset transfer of Plaintiff's IBM employment service to ROLM for inclusion in any subsequent ROLM pension benefit calculation. The letter stated that because the IBM Plan had already paid a benefit on Plaintiff's behalf for her service from January 24, 1980 to February 15, 1990, Plaintiff was ineligible for any future IBM pension benefit or service calculations. Finally, the letter explained that ROLM had since been acquired by Siemens, and that IBM had made an inquiry to Siemens and determined that Plaintiff was receiving Siemens pension benefits that included her previous IBM service dates. AR 12-15.

On October 8, 2013, Plaintiff's attorneys sent a letter to the Plan Administrator requesting documents related to her claim for benefits. On November 11, 2013, the Plan Administrator responded to Plaintiff's request by forwarding a July 9, 2013 email exchange between Siemens and the IBM Plan that confirmed that Plaintiff's Siemens pension was based on service from 1980 to 1997, plus copies of the 1989 and 1994 IBM Retirement Plans. Plaintiff requested a copy of the 1990 purchase agreement between IBM and ROLM that was referenced in the denial of her claim, but the Plan Administrator did not provide one.

Plaintiff appealed the denial of her claim for IBM Plan benefits on December 3, 2013. On March 6, 2014, the Plan Administrator upheld the denial of Plaintiff's claim.

On June 24, 2014, Plaintiff filed a complaint against IBM and the IBM Plan alleging four causes of action. Plaintiff's first cause of action is for recovery of plan benefits under 29 U.S.C. § 1132(a)(1)(B). Her second cause of action, brought against IBM only, is for breach of fiduciary duties under 29 U.S.C. § 1104. Plaintiff's third cause of action is for equitable relief under 29 U.S.C. § 1132(a)(3). Her fourth cause of action is for failure to provide requested plan information under 29 U.S.C. § 1132(c).

II. LEGAL STANDARD

The conventional summary judgment standard applies to Plaintiff's second, third, and fourth causes of action. A court shall grant summary judgment "if . . . there is no genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law." Fed. R. Civ. P. 56(a). The burden of establishing the absence of a genuine issue of material fact lies with the moving party, see Celotex Corp. v. Catrett, 477 U.S. 317, 322-23 (1986), and the court must view the evidence in the light most favorable to the non-movant. See Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 255 (1986). A genuine factual issue exists if, taking into account the burdens of production and proof that would be required at trial, sufficient evidence favors the non-movant such that a reasonable jury could return a verdict in that party's favor. Id. at 248. The court may not weigh the evidence, assess the credibility of witnesses, or resolve issues of fact. See Id. at 249.

To defeat summary judgment once the moving part has met its burden, the nonmoving party may not simply rely on the pleadings, but must produce significant probative evidence, by affidavit or as otherwise provided by Federal Rule of Civil Procedure 56, supporting the claim that a genuine issue of material fact exists. TW Elec. Serv., Inc. v. Pac. Elec. Contractors Ass'n, 809 F.2d 626, 630 (9th Cir. 1987). In other words, there must exist more than "a scintilla of evidence" to support the non-moving party's claims. Anderson, 477 U.S. at 252. Conclusory statements without factual support are insufficient to defeat a motion for summary judgment. Surrell v. Cal. Water Serv. Co., 518 F.3d 1097, 1103 (9th Cir. 2008). Similarly, "[w]hen opposing parties tell two different stories, one of which is blatantly contradicted by the record, so that no reasonable jury could believe it, a court should not adopt that version of the facts" when ruling on the motion. Scott v. Harris, 127 S. Ct. 1769, 1776 (2007).

On an issue where the nonmoving party will bear the burden of proof at trial, the moving party can prevail merely by pointing out to the district court that there is an absence of evidence to support the nonmoving party's case. Celotex, 477 U.S. at 324-25; Soremekun v. Thrifty Payless, Inc., 509 F.3d 978, 984 (9th Cir. 2007). If the moving party meets its initial burden, the opposing party must then set out specific facts showing a genuine issue for trial in order to defeat the motion. Anderson, 477 U.S. at 250; Soremekun, 509 F.3d at 984; see Fed.R.Civ.P. 56(c),(e). The opposing party's evidence must be more than "merely colorable" and must be "significantly probative." Anderson, 477 U.S. at 249-50. Further, the opposing party may not rest upon mere allegations or denials of the adverse party's evidence, but instead must produce admissible evidence showing there is a genuine dispute of material fact for trial. Nissan Fire & Marine Ins. Co. v. Fritz Cos., Inc., 210 F.3d 1099, 1102-03 (9th Cir. 2000). Disputes over irrelevant or unnecessary facts will not preclude a grant of summary judgment. T.W. Elec. Serv., 809 F.2d at 630.

A different standard applies to Plaintiff's first claim for benefits under the IBM Plan. In the ERISA context, summary judgment generally is the vehicle for deciding the case; the factual determination of eligibility for benefits is decided solely on the administrative record, and "the non-moving party is not entitled to the usual inferences in its favor. " Gilliam v. Nevada Power Co., 488 F.3d 1189, 1192 n.3 (9th Cir. 2007); Bendixen v. Standard Ins. Co., 185 F.3d 939, 942 (9th Cir. 1999) overruled on other grounds by Abatie v. Alta Health & Life Ins. Co., 458 F.3d 955, 965 (9th Cir. 2006) (en banc).

Where, as here, the parties have each filed motions for summary judgment, "[e]ach motion must be considered on its own merits." Fair Hous. Council of Riverside Cty., Inc. v. Riverside Two, 249 F.3d 1132, 1136 (9th Cir. 2001). "In fulfilling its duty to review each cross-motion separately, the court must review the evidence submitted in support of each cross-motion." Id.

III. DISCUSSION

Defendants move for summary judgment on all four of Plaintiff's claims. Plaintiff moves for summary judgment on her first and fourth claim.

A. Plaintiff's First Claim: Recovery of Plan Benefits Under 29 U.S.C. § 1132(a)(1)(B)

1. ERISA Standard of Review

ERISA allows a participant in an employee benefit scheme to bring a civil action to recover benefits due under the terms of a plan. 29 U.S.C. § 1132(a)(1)(B). The court applies a de novo standard of review to actions for the recovery of ERISA benefits, unless the plan in question grants discretionary authority to the trustee or fiduciary. Firestone Tire & Rubber Co. v. Bruch, 489 U.S. 101, 114-15 (1989). If a plan unambiguously grants the plan administrator discretionary authority to construe the plan's terms, the court reviews the matter for an abuse of discretion. Metro. Life Ins. Co. v. Glenn, 554 U.S. 105, 111 (2008). The parties stipulated that the abuse of discretion standard applies to Plaintiff's first cause of action. Docket No. 34.

In applying an abuse of discretion standard, the court's review is limited to the record before the plan administrator. Jebian v. Hewlett-Packard Co. Employee Benefits Org. Income Prot. Plan, 349 F.3d 1098, 1110 (9th Cir. 2003) (citing McKenzie v. General Tel. Co., 41 F.3d 1310, 1316 (9th Cir.1994)). For this reason, in analyzing this claim, the court will not review any evidence outside the administrative record. Under the abuse of discretion standard, a plan administrator's decision "'will not be disturbed if reasonable.'" Day v. AT&T Disability Income Plan, 698 F.3d 1091, 1096 (9th Cir. 2012) (quoting Conkright v. Frommert, 559 U.S. 506 (2010)). This standard requires deference to the administrator's decision unless it is "(1) illogical, (2) implausible, or (3) without support in inferences that may be drawn from the facts in the record." Stephan v. Unum Life Ins. Co. of Am., 697 F.3d 917, 929 (9th Cir. 2012) (quoting Salomaa v. Honda Long Term Disability Plan, 642 F.3d 666, 675 (9th Cir. 2011). However, "ERISA plan administrators do not have unbounded discretion." Booton v. Lockheed Medical Ben. Plan, 110 F.3d 1461, 1463 (9th Cir. 1997). They must obtain relevant information to make the decision, ask for more information if it is needed, and engage in a meaningful dialogue with their beneficiaries. Failure to do so amounts to an abuse of discretion. Id. at 1463-1465.

Thus, the court will not consider the information outside the administrative record relied on by Defendants, including the declaration of William Carlough, the declaration of Mitchell Boomer, Plaintiff's deposition testimony taken during the litigation, and the redacted version of the Master Business Agreement between IBM and Siemens.

When reviewing for an abuse of discretion, the court must consider any conflict of interest. Plaintiff asserts, and Defendants do not dispute and therefore concede, the existence of a conflict of interest. IBM established a trust fund from which IBM Plan benefits are provided. The same entity that funds the IBM Plan also evaluates claims, thereby creating a structural conflict of interest. Metro. Life Ins. Co., 554 U.S. at 112. This is because the employer "both decides who gets benefits and pays for them, so it has a direct financial incentive to deny claims." Saffon v. Wells Fargo & Co. Long Term Disability Plan, 522 F.3d 863, 868 (9th Cir. 2008). This is true even though the funds flow through a separate trust. See Burke v. Pitney Bowes Inc. Long-Term Disability Plan, 544 F.3d 1016, 1026 (9th Cir. 2008).

In the Ninth Circuit, the existence of a conflict of interest is a factor to be weighed in determining whether there was an abuse of discretion. Abatie v. Alta Health & Life Ins. Co., 458 F.3d 955, 965 (9th Cir. 2006) (en banc); Montour v. Hartford Life & Acc. Ins. Co., 588 F.3d 623, 631 (9th Cir. 2009). The presence of a conflict does not convert abuse of discretion review into de novo review, but it does mean that a reviewing court must consider "the conflict of interest in deciding how skeptical to be of the administrator's decision." Salomaa, 642 F.3d at 675. The weight a reviewing court accords to a conflict varies "based on the degree to which the conflict appears improperly to have influenced a plan administrator's decision." Montour, 588 F.3d at 631.

2. Analysis

The business relationships between IBM, ROLM, and Siemens play a role in this case. The connection between these three entities is not clear from the information contained in the administrative record or from the parties' briefing.

The Plan Administrator explained these relationships to Plaintiff on two occasions in denying her claim. In its initial denial letter, the Plan Administrator found that Plaintiff worked for IBM from January 24, 1980 to February 15, 1990, and that her 1990 separation from IBM was the result of an agreement between IBM and ROLM that allowed Plaintiff to become an employee of ROLM. AR 12-13. The Plan Administrator noted that ROLM was later acquired by Siemens. The Plan Administrator stated that the agreement between IBM and ROLM included a transfer of Plaintiff's IBM pension assets for the period of IBM service from January 24, 1980 to February 15, 1990, and that the asset transfer from IBM to ROLM rendered Plaintiff ineligible for pension benefits from IBM for that period of service. Id.

In its subsequent March 6, 2014 denial of Plaintiff's appeal, the Plan Administrator provided a somewhat different timeline and explanation. The Plan Administrator asserted that according to IBM's records, Plaintiff worked for ROLM beginning on January 24, 1980. AR 123-126. In November 1984, IBM acquired ROLM, and ROLM became a wholly owned subsidiary of IBM. On September 30, 1989, a portion of ROLM was sold to Siemens. ROLM Company became a joint venture between IBM and Siemens, and ROLM Systems became wholly owned by Siemens. Id. As explained by the Plan Administrator, on and after September 29, 1989, "some" IBM employees transferred from IBM to Siemens (including ROLM Systems), and "other" IBM employees transferred from IBM to the ROLM Company. Id. Plaintiff terminated her employment with IBM on February 15, 1990. In May 1992, Siemens acquired IBM's share of the ROLM Company. Id. The March 6, 2014 letter does not explain how Plaintiff's employment was affected by each of these business actions, but simply concludes that Plaintiff's IBM pension benefits assets were transferred to the Siemens Retirement Plan "after she stopped working for IBM and started working for Siemens." Id.

Having decided that Plaintiff, along with her IBM Plan pension assets, transferred from IBM to ROLM/Siemens as part of a business transaction, the Plan Administrator determined that Plaintiff was not eligible for IBM Plan benefits because she was a "Former Participant" as defined by the IBM Plan. The 1989 version of the IBM Plan discusses "Former Participant" as follows:

Appendix C - "Divestitures and Acquisitions"

I. Divestitures

A. Certain Participants ("Former Participants") terminated their employment with the Company as part of the sale of parts of the Company's business operations or by the sale of a Domestic Subsidiary to another company. As part of these transactions, some of the assets and liabilities of the IBM Retirement Plan were or will be transferred pursuant to Section 414(l) of the Code to qualified Plans of the acquiring companies... All rights of said Former Participants and their Beneficiaries under the Plan terminate effective upon the transfer of said assets and liabilities....In no event will any Former Participant be entitled to duplicate benefits under this Plan and another employer's Plan with respect to the same period of Continuous Service or for the benefits whose liabilities were transferred to any other employer described herein.
AR 173 (emphasis added). Appendix C goes on to describe a number of employee groups that fall within the description of "Former Participant." AR 173-174

Appendix C to the IBM Plan was amended in 1994. With a few minor differences that are not pertinent to this analysis, the 1989 text of Appendix C quoted above remained the same. Of relevance to this case, the 1994 amendment added the ROLM employee group to the definition of "Former Participants":

"Former Participants" include, but are not limited to:
....
"ROLM Employees"- Former Participants whose accrued benefits (and the Plan's assets and liabilities to provide said accrued benefits) are transferred by the Company and the fiduciaries to this Plan to either the Siemens Retirement Plan or the ROLM Retirement Plan...all as described in Section 7.2 of the Master Business Agreement Among IBM, Siemens Communications Systems, Inc., and Siemens Aktiengesellschaft, dated as of May 2, 1992.
AR 246-48.

The 1989 IBM Plan was the operative plan for Plaintiff's period of service with IBM. The 1994 Plan was amended to address the divestiture of ROLM employees. In denying Plaintiff's claim, the Plan Administrator relied on both plans, both of which are part of the administrative record. The Plan Administrator's initial denial, (but not the denial on appeal), also references Article 10 E of the IBM Plan, which addresses how to calculate a participant's period of service. Article 10 E does not address benefit divestures and acquisitions, which are governed by Appendix C. Since the Plan Administrator's initial decision was based on a finding that the benefits were divested from IBM, Article 10 E is not applicable.

The starting point in any ERISA benefits analysis is the Plan language. See Day, 698 F.3d at 1096-97. Under the plain language of the IBM Plan, if Plaintiff is a Former Participant, then her rights to benefits terminated "upon the transfer" of her IBM Plan benefits to her transferee employer's benefit plan. As a Former Participant, the IBM Plan would also prohibit her receipt of duplicate benefits from the IBM Plan and the other employer for the same period of covered service. Simply put, if Plaintiff is a Former Participant, the analysis is straightforward. She would have no rights to benefits based on the express language of the IBM Plan.

But therein lies the rub.

Plaintiff contends that she is not a Former Participant because she did not terminate her employment with IBM by transferring to ROLM or Siemens as part of an asset sale. According to Plaintiff, the administrative record clearly shows that she independently separated from IBM and became an employee of Siemens PN in February 1990, more than two years before the sale that is documented in the 1992 Master Business Agreement referenced in Appendix C of the 1994 version of the IBM Plan. Plaintiff points to the following record evidence in support of her contention: 1) her declaration stating that she voluntarily resigned from IBM on February 15, 1990 and began work at Siemens on February 19, 1990 [AR 43]; 2) her W-2 forms showing that she was employed by IBM until she resigned in February 1990 [AR 48-58]; 3) the May 2, 1992 date of execution of the Master Business Agreement between IBM and ROLM; 4) her declaration stating that she never received a notice from IBM or Siemens that her IBM Plan benefits had been transferred [AR 43-47]; and 5) the numerous statements over the years sent to Plaintiff by IBM stating that she was still a participant in the IBM Plan and estimating the specific benefit that would be paid to Plaintiff by the IBM Plan upon her retirement [AR 59-118].

According to Plaintiff, since she did not transfer employment as part of the sale of an IBM business unit to ROLM, she is not a "Former Participant" as defined by the Plan. As such, her benefits under the IBM Plan did not terminate.

Defendants largely ignore Plaintiff's evidence about the timing and reasons for her move from IBM to Siemens in February 1990. They do not attempt to counter her assertion with IBM personnel records or other direct evidence that Plaintiff's employment with IBM actually terminated as a result of the sale and transfer of assets to ROLM or Siemens. In fact, the Plan Administrator's denial letters acknowledge that Plaintiff worked for IBM until February 15, 1990 [AR 12, 123], and Defendants stipulated that Plaintiff began working at Siemens on February 19, 1990. These events occurred after the September 30, 1989 transfer of employees from IBM to ROLM/Siemens that Defendants allege was a part of the May 2, 1992 asset sale between IBM and Siemens. Yet, in the face of these undisputed and objective facts, Defendants still fail to respond to Plaintiff's argument that her date of termination from IBM does not correspond to the date of the transfer of IBM employees, or to the date of the sale of IBM's business.

Instead, Defendants' position rests on an inference they draw from Siemens' representation. The Plan Administrator contacted the Siemens Retirement Plan about Plaintiff's claim, and received an email from Siemens which stated: "We do have a monthly benefit for her of $2,622.71. Her employment history is active from 1-24-1980 terminated 7-24-1997." AR 24. From this Siemens email, the Plan Administrator assumed that Plaintiff must have transferred from IBM, and her IBM Plan benefits must have been transferred with her as part of the asset sale, because she has been receiving benefits under the Siemens plan based on an employment history that includes her dates of service with IBM.

Thus, in its initial denial, the Plan Administrator reasoned that "[s]ince the agreement with ROLM included an asset transfer of your accrued pension benefit, IBM already paid a benefit on your behalf based on the period of service from January 24, 1980 to February 15, 1990. The asset transfer to ROLM made that period of service ineligible for inclusion in any future IBM pension benefit or service calculations. ROLM has since been acquired by Siemens. According to the information provided by Siemens, you have been in pay with a pension since February 1, 2012, that includes your previous IBM service dates." AR 12-13 (emphasis added).

The Plan Administrator's denial of Plaintiff's appeal gives similar reasons:

Siemens has informed us that Ms. Gurasich's pension benefit under the Siemens Retirement Plan is based, in part, on her period of service with IBM on and before February 15, 1990, since her liabilities under the Plan were transferred to the
Siemens Retirement Plan. Since Ms. Gurasich's liabilities under the Plan were transferred to the Siemens Retirement Plan, the liabilities no longer exist in the Plan and Ms. Gurasich is not entitled to a benefit under the Plan. If Ms. Gurasich's benefit under the Plan was not transferred to the Siemens Retirement Plan, Ms. Gurasich would be receiving a smaller benefit under the Siemens Retirement Plan since her benefit under the Siemens Retirement Plan would be based only on service after February 15, 1990.
AR 124-125 (emphasis added).

This sentence is a stretch, for Siemens did not confirm that "[Plaintiff's] liabilities under the Plan were transferred to the Siemens Retirement Plan." That is wholly the Plan Administrator's conclusion. Siemens only confirmed that Plaintiff was receiving benefits based on a period of service dating back to 1980.

The Plan Administrator assumed that Plaintiff's benefit assets must have been transferred, because Siemens otherwise would have no reason to give Plaintiff credit for the ten years of service (1980 to 1990) that she spent working for ROLM and IBM, and not for Siemens. The question then becomes whether the Plan Administrator acted within its discretion in resting its denial on an inference drawn from Siemens' representation, rather than Defendants' own records. Defendants argue that the Plan Administrator made a reasonable inference that Plaintiff's IBM Plan benefits must have been transferred to ROLM/Siemens. They assert that the Plan Administrator did not have an affirmative duty to investigate or respond to Plaintiff's evidence that she was not a "Former Participant."

The court disagrees. The Plan Administrator is not entitled to rest its decision on an inference when it had the ability to confirm the facts themselves, especially where Plaintiff provided concrete contrary evidence that she did not change employment through a business transfer. Kunin v. Benefit Trust Life Ins. Co., 910 F.2d 534, 538 (9th Cir.1990) (burden is on plan to obtain adequate information to make decision). Denial of benefits without relevant information, especially personnel and benefits records in the control of a plan administrator, amounts to an abuse of discretion. Booton v. Lockheed Med. Ben. Plan, 110 F.3d 1461, 1463-64 (9th Cir. 1997) (observing that "[l]acking necessary - and easily obtainable - information, Aetna made its decision blindfolded," and finding that denial of a claim without obtaining relevant information is an abuse of discretion).

Defendants do not cite to evidence demonstrating that the Plan Administrator checked IBM employment records to verify the circumstances of Plaintiff's separation from employment. See Defs.' MSJ at 8; MSJ Reply at 8; Opp. to Pl.'s MSJ at 5 (describing actions taken by the Plan Administrator to determine Plaintiff's eligibility for benefits under the IBM Plan). Defendants also fail to identify evidence that the Plan Administrator investigated whether Plaintiff's pension benefits actually transferred to a ROLM or Siemens plan, even though there is reason to believe that such information may exist. Id. ERISA section 209 required IBM to indefinitely maintain any and all records "sufficient to determine the benefits due or which may become due." 29 U.S.C. § 1059(a)(1). IBM repeatedly sent Plaintiff monthly benefit estimates of $978.90 under the IBM Plan, and those notices state that "we have estimated your benefits payable from the Plan based on certain detailed assumptions and data that IBM has in its personnel records." See AR 69-81; 84-96, 111-113 (emphasis added).

Defendants cite two Fifth Circuit cases for the proposition that the Plan Administrator had no affirmative duty to investigate a plaintiff's claim for benefits under the plan. Truitt v. Unum Life Ins. Co. of Am., 729 F.3d 497, 509-512, n.7 (5th Cir. 2013), cert. denied, 134 S. Ct. 1761 (2014) (holding that the administrator did not have an affirmative duty to investigate the accuracy of third party information about a claimant's physical condition); Vega v. Nat'l Life Ins. Servs., Inc., 188 F.3d 287, 297-99 (5th Cir.1999)(en banc), overruled on other grounds by Metro. Life Ins. Co. v. Glenn, 554 U.S. 105 (2008) (holding that if the claimant has relevant information in her control, it is not only inappropriate but inefficient to require the administrator to obtain that information in the absence of her active cooperation and noting that the information at issue from claimant's personal physician could more easily have been obtained by the claimant than by the administrator).

This court is bound by Ninth Circuit law, not that of the Fifth Circuit. In any event, the Fifth Circuit's rulings in Truitt and Vega are not inconsistent with this court's holding. Those cases eschew the creation of an affirmative obligation on the part of the plan administrator to investigate the applicant's claim related to information about the claimant's physical condition that was outside of the administrator's control. Neither of these cases addressed the issue of a plan administrator's obligation to review its own personnel records. Following Ninth Circuit precedent, this court finds that IBM abused its discretion by assuming objectively confirmable facts -- that Plaintiff transferred her employment as part of the sale of a business, and that her IBM Plan assets transferred to ROLM or Siemens as a result of that sale -- rather than verifying them through review, or at least attempted review, of information within its own control. In light of Plaintiff's submission of evidence that her employment with Siemens was unrelated to the sale of an IBM business unit, IBM could not rely on an inference, at least not without having consulted its own records first.

Defendants attempt to shift responsibility to Plaintiff, pointing out that Plaintiff never explained why she was receiving benefits under the Siemens plan for service beginning January 24, 1980. They argue that Plaintiff never submitted her Siemens plan documents, which could have established that her benefits under the Siemens plan do not reflect a transfer of benefits from IBM to Siemens. However, Defendants never requested that Plaintiff submit the terms of her Siemens plan, and thus cannot base its denial on Plaintiff's failure to do so. See 29 C.F.R. § 2560.503-1(g)(1)(iii) (notification of adverse benefit determination shall include a description of any additional material or information necessary for the claimant to perfect the claim and an explanation of why such material or information is necessary); Booton, 110 F.3d at 1465 (if the plan is unable to make a rational decision on the basis of the materials submitted by the claimant, it must explain what else it needs). Where the relevant information is within the Plan Administrator's control, it is not appropriate for the Plan Administrator to shift the burden to Plaintiff to prove that IBM did not transfer her benefits.

Moreover, Plaintiff asserts that even if the IBM Plan did transfer her benefits, it did not have the authority to do so, because she was not a Former Participant under the terms of the Plan. Plaintiff contends, and Defendants do not address and therefore concede, that the IBM Plan only allowed transfers of benefits for "Former Participants." AR 173. Plaintiff notes that except for the exemption carved out for "Former Participants," under Article 22 of the IBM Plan, "[n]o benefit payable under the Plan shall be subject to alienation, sale, transfer, assignment, pledge, attachment, garnishment, lien, levy or like encumbrance." AR 163.

It is impossible to ignore the undisputed fact that Plaintiff has been receiving ten extra years of service credit through her Siemens Retirement Plan benefits. The Siemens plan is not part of the administrative record, but it is hard to believe that it provides such generous terms. The court notes the possibility that the IBM Plan erroneously transferred Plaintiff's pension assets to ROLM/Siemens without her authorization, after mistakenly concluding that she transferred from IBM as part of the business unit sale. If Siemens has been overpaying Plaintiff's pension benefits due to an unauthorized transfer by the IBM Plan, that is not a matter that can be sorted out here.

The court's finding that IBM abused its discretion by rendering a decision without the benefit of information within its control is further buttressed by consideration of the structural conflict. Indeed, in Abatie, the Ninth Circuit expressly noted that a court may weigh a structural conflict more heavily if the administrator "fails adequately to investigate a claim or ask the plaintiff for necessary evidence." Abatie, 458 F.3d at 968; Booton, 110 F.3d at 1463-64 and n.6 (in discussing defendant's failure to investigate, court notes that "[a]lthough we do not find that Aetna's actions were malicious, we are concerned that it had little incentive to come to grips with Booton's claims.").

In one respect, the Plan Administrator gave "inconsistent reasons for denial," which also permits the reviewing court to weight a structural conflict more heavily. Abatie, 458 F.3d at 966-67. The initial denial letter states that the transfer of Plaintiff's benefits occurred pursuant to an agreement between IBM and ROLM. AR 12. ("Your separation from IBM in 1990 was the result of an agreement between IBM and ROLM that allowed you to become an employee of ROLM. The agreement also included a pension asset transfer that was essentially a transfer of your IBM employment service to ROLM for inclusion in any subsequent ROLM pension benefit calculations for you." (emphasis added)). On appeal, the Plan Administrator said that the agreement was between IBM and Siemens. AR 124. ("The transfer of Ms. Gurasich's liabilities under the Plan was a result of an agreement between IBM and Siemens to transfer a portion of IBM's business to Siemens and a portion to the ROLM Company joint venture"). This difference should have underscored the importance of investigating the exact circumstances of Plaintiff's movement from IBM to Siemens, especially in light of the fact that Plaintiff presented concrete evidence demonstrating that she was not transferred as part of a sale.

In sum, the court finds that the Plan Administrator abused its discretion by denying Plaintiff's claim based on an inference drawn from another employer's records, rather than reviewing records within its own control. In reaching this conclusion, the court gives some weight to the structural conflict, as the Plan Administrator failed to adequately investigate the claim even though Plaintiff brought concrete and undisputed factual discrepancies to its attention.

B. Plaintiff's Second and Third Claims: Breach of Fiduciary Duties Under 29 U.S.C. § 1104 and Equitable Relief Under 29 U.S.C. § 1132(a)(3)

Defendants move for summary judgment on Plaintiff's second claim for breach of fiduciary duties and her third claim for equitable relief. Plaintiff concedes that because the court has awarded her benefits under the IBM Plan in her first cause of action, she is not entitled to further relief under her second and third claims. PL's Opp'n to Defs.' MSJ at 13. Therefore, the court need not reach these issues.

C. Plaintiff's Fourth Claim: Failure to Provide Requested Plan Information Under 29 U.S.C. § 1132(c)

Plaintiff brings a claim for statutory penalties pursuant to 29 U.S.C. § 1132(c)(1)(B), based on Defendants' undisputed failure to produce the Master Business Agreement ("MBA") during the administration of Plaintiff's claim. Both Plaintiff and Defendants move for summary judgment on this cause of action.

The MBA is the May 2, 1992 agreement between IBM, Siemens Communication Systems, Inc., and Siemens Aktiengesellschaft that is referenced in Appendix C of the 1994 version of the IBM Plan. AR 246. Although not specifically identified, the Plan Administrator referenced the MBA in the initial denial letter as well as the denial of Plaintiff's appeal. The October 1, 2013 initial denial letter stated that "[y]our separation from IBM in 1990 was the result of an agreement between IBM and ROLM that allowed you to become an employee of ROLM. The agreement also included a pension asset transfer that essentially was a transfer of your IBM employment service to ROLM for inclusion in any subsequent ROLM pension benefit calculations for you." AR 12. In the denial of Plaintiff's appeal for benefits, the Plan Administrator referenced an "agreement between IBM and Siemens to transfer a portion of IBM's business to Siemens and a portion to the ROLM Company joint venture." AR 124.

The court is not able to review the entire MBA because neither party submitted a full copy of the document as part of the summary judgment record. Defendants filed Section 7.2 of the MBA. It is heavily redacted. Carlough Decl. Ex. C [Docket No. 39-1].

Plaintiff asserts that Defendants violated two separate ERISA disclosure requirements which should result in an award of civil penalties under section 1132(c)(1)(B). First, she argues that Defendants were required to produce the MBA during the administration of her claim pursuant to 29 U.S.C. § 1024(b)(4). Second, she contends that Defendants' failure to produce the MBA resulted in a violation of 29 C.F.R. § 2560.503-1, which is an implementing regulation for 29 U.S.C. § 1133. Defendants respond that Plaintiff's claim fails as a matter of law because section 1024(b)(4) does not require production of the MBA, and because violations of 29 C.F.R. § 2560.503-1 are not enforceable through the civil enforcement penalty provision in section 1132(c)(1).

29 U.S.C. § 1132(c)(1)(B) renders a plan administrator liable for civil penalties for failure to comply with its disclosure requirements. The section states: "[a]ny administrator ... who fails or refuses to comply with a request for any information which such administrator is required by this subchapter to furnish to a participant or beneficiary.... may in the court's discretion be personally liable to such participant or beneficiary in the amount of up to $100 a day from the date of such failure or refusal, and the court may in its discretion order such other relief as it deems proper." 29 U.S.C. § 1132(c)(1)(B). As a statutory penalty provision, section 1032(c)(1) must be strictly construed. Serpa v. SBC Telecomm., Inc., No. C03-4223 MHP, 2004 WL 3204008, at *3 (N.D. Cal. Dec. 8, 2004) (collecting cases).

By regulation, the maximum penalty is now $110 per day. 29 C.F.R. § 2575.502c-3.

As an initial matter, the court notes that the plain language of section 1132(c)(1) authorizes liability for civil penalties only against the plan "administrator," which in this instance is IBM (see Compl. ¶ 3 [Docket No. 1]; Amended Answer ¶ 3 [Docket No. 28]). For this reason, the IBM Plan is not a proper defendant; the court will analyze this claim only as to IBM, as the Plan Administrator.

1. IBM Was Not Required to Produce the MBA Under Section 1024(b)(4).

Section 1024(b)(4)'s disclosure requirement states, in pertinent part:

The administrator shall, upon written request of any participant or beneficiary, furnish a copy of the latest updated summary[] plan description, and the latest annual report, any terminal report, the bargaining agreement, trust agreement, contract, or other instruments
under which the plan is established or operated.
29 U.S.C. § 1024(b)(4) (emphasis added).

As with section 1132(c)(1), the text of section 1024(b)(4) makes plain that the "administrator" is the only proper defendant to a claim alleging a violation of this section. See Moran v. Aetna Life Ins. Co., 872 F.2d 296, 299-300 (9th Cir. 1989). Thus, as with section 1132(c)(1), this threshold issue prevents Plaintiff from sustaining a section 1024(b)(4) claim against the IBM Plan.

Plaintiff argues that the MBA falls within the purview of section 1024(b)(4) because it is a "contract or other instrument under which the plan is established or operated." According to Plaintiff, IBM's failure to provide the MBA therefore results in a violation of section 1024(b)(4)'s disclosure requirement.

The Ninth Circuit narrowly construes the disclosures required by section 1024(b)(4). In Hughes Salaried Retirees Action Committee v. Administrator of the Hughes Non-Bargaining Retirement Plan, 72 F.3d 686 (9th Cir.1995) (en banc), the Ninth Circuit noted that the Supreme Court "characterized the documents subject to [section 1024(b)(4)'s] disclosure requirements as 'governing plan documents,'" which are those that "provide individual participants with information about the plan and benefits." 72 F.3d at 689-90, (citing Curtiss-Wright Corp. v. Schoonejongen, 514 U.S. 73 (1995)). The Hughes en banc decision rejected the original panel's interpretation that the statute requires disclosure of all documents that are "critical to the operation of the plan," holding that such a generalized disclosure obligation would mandate production of nearly any conceivably related document. Id. at 690. The en banc court held instead that section 1024(b)(4) "requires the disclosure of only the documents described with particularity [in the statute] and 'other instruments' similar in nature" to the specifically described documents. Id. at 691.

The Ninth Circuit reinforced its narrow reading of section 1024(b)(4)'s disclosure requirement in Shaver v. Operating Engineers Local 428 Pension Trust Fund. 332 F.3d 1198, 1201-02 (9th Cir. 2003) (applying the interpretive principle of ejusdem generis to the term "other instruments," noting that the statute "mentions only legal documents that describe the terms of the plan, its financial status, and other documents that restrict or govern the plan's operation"). Citing Hughes, Shaver held that "'[other] instruments' refers to '...documents that provide individual participants with information about the plan and benefits.'" 332 F.3d at 1202. Shaver concluded that the statute did not mandate the disclosure of itemized expenditure lists, which at most related "only to the manner in which the plan is operated." Id.

Therefore, to fall within the definition of "contract, or other instruments under which the plan is established or operated," Plaintiff must show that the MBA "provides participants with information about the plan and benefits," or otherwise qualifies as an instrument similar in nature to the documents specifically enumerated in the statute. Plaintiff puts forward no evidence of this. For this reason alone, Plaintiff's claim that IBM was required to produce the MBA under section 1024(b)(4) fails.

Plaintiff also has put forth no evidence that the MBA is an instrument "under which the [IBM Plan] is established or operated." There is no evidence that the IBM Plan was "established under" the MBA. Indeed, the MBA is dated May 2, 1992, which is after the establishment of the 1989 IBM Plan. AR 248. Obviously, the 1989 IBM Plan makes no reference to the MBA.

Nor does Plaintiff point to any provision of the MBA suggesting that the IBM Plan was "operated under" it. Instead, Plaintiff sidesteps the statutory language by arguing that the IBM Plan was "operated according to" the contract between IBM and Siemens, because the 1994 IBM Plan makes reference to the MBA. Pl.'s Reply in Supp. of MSJ [Docket No. 52] at 20. But "operated according to" is not the same as "operated under," which is the statutory test the court must apply here. The parties cite only one reference to the MBA in the 1994 IBM Plan. As set forth above in the court's analysis of Plaintiff's first cause of action, Appendix C to the 1994 Plan identifies "Former Participants," which include certain ROLM employees whose pension benefits were transferred by the IBM Plan "as described in Section 7.2 of the Master Business Agreement Among IBM, Siemens Communications Systems, Inc., and Siemens Aktiengesellschaft, dated as of May 2, 1992." AR 246-48. This sole reference demonstrates that the MBA was a business agreement regarding the sale of a portion of IBM's business, which also allowed for a transfer of assets and liabilities for certain IBM transferred employees under the terms of the IBM Plan to either the Siemens Retirement Plan or the ROLM Retirement Plan, such that the transferred employees became "Former Participants" under the terms of the IBM Plan. AR 248.

Section 7.2 of the MBA merely provides that IBM will transfer the accrued pension benefit liability for "each employee transferred to ROLM Company or ROLM Systems on September 30, 1989." Following such transfer, "the Siemens Retirement Plan and the ROLM Company Retirement Plan shall be solely responsible for the payment of the IBM Transferred Employees' benefits assumed by each such plan." MBA, Section 7.2, Carlough Decl. Ex. C [Docket No. 39-1 at 2]. --------

Plaintiff does not, and cannot, make an argument that the MBA somehow changed the terms of the Plan itself, or that the MBA provided information necessary for the calculation of benefits, such that the IBM Plan was "operated under" the MBA. For example, the MBA did not include any valuation information that the Plan Administrator needed to calculate benefits. Cf. Werner v. Morgan Equip. Co., 15 Employee Benefits Cas. (BNA) 2295, 2301, 1992 WL 453355 (N.D.Cal.1992) (stock valuation report is an instrument under which a plan is established or operated when the plan measures benefits by the value of stock); Lee v. Dayton Power & Light Co., 604 F. Supp. 987, 1002 (S.D. Ohio 1985) (manual containing charts essential to the calculation of benefits is an instrument under which the plan is established or operated).

In sum, Plaintiff has put forth no evidence to demonstrate that the MBA is an "instrument" under which the IBM Plan was "established or operated." Plaintiff has failed to establish her claim for section 1132(c)(1)(B) penalties to the extent it is based on IBM's alleged violation of section 1024(b)(4) disclosure requirements.

2. A Violation of 29 C.F.R. § 2560.503-1(h)(2)(iii) Does Not Trigger Liability Under 29 U.S.C. § 1132(c)(1)(B)

Plaintiff also contends that Defendants' failure to produce the MBA violated 29 C.F.R. § 2560.503-1(h)(2)(iii). Section 2560.503-1 is an implementing regulation for 29 U.S.C. § 1133, which provides that benefit plans must give adequate notice of a denial, as well as provide for full and fair review of the denial of a claim for benefits:

"In accordance with regulations of the Secretary, every employee benefit plan shall--(1) provide adequate notice in writing to any participant or beneficiary whose claim for
benefits under the plan has been denied, setting forth the specific reasons for such denial, written in a manner calculated to be understood by the participant, and (2) afford a reasonable opportunity to any participant whose claim for benefits has been denied for a full and fair review by the appropriate named fiduciary of the decision denying the claim."
29 U.S.C.A. § 1133.

29 C.F.R. § 2560.503-1(h) specifies that ERISA plans must "establish and maintain a procedure by which a claimant shall have a reasonable opportunity to appeal an adverse benefit determination to an appropriate named fiduciary of the plan, and under which there will be a full and fair review of the claim and the adverse benefit determination." In order to provide a claimant with a reasonable opportunity for a full and fair review of a claim, a benefits plan must "[p]rovide that a claimant shall be provided, upon request and free of charge, reasonable access to, and copies of, all documents, records, and other information relevant to the claimant's claim for benefits...." 29 C.F.R. § 2560.503-1(h)(2)(iii).

The court finds that alleged violations of 29 C.F.R. § 2560.503-1(h)(2)(iii) cannot form the basis for imposition of civil penalties under 29 U.S.C. § 1132(c)(1)(B). Section 1132(c) liability is limited to the plan administrator's failure to provide information required by "this subchapter." 29 U.S.C. § 1132(c). As such, it does not extend to information identified in implementing regulations, such as 29 C.F.R. § 2560.503-1, which are not explicitly required in the statutory subchapter. See, e.g., Prado v. Allied Domecq Spirits & Wine Grp. Disability Income Policy, 800 F. Supp. 2d 1077, 1101 (N.D. Cal. 2011). Nothing in the statutory scheme suggests that an ERISA claimant may bring an action for civil penalties under section 1132(c) for a plan's failure to comply with a regulation. Id.

The court's decision is in line with numerous district court decisions in this circuit, like the Prado court, which have followed the First, Third, Sixth, Seventh, and Eighth Circuits in finding that a plaintiff cannot recover section 1132(c) penalties for a violation of section 1133's implementing regulations. These courts have concluded that (i) the plain language of section 1132(c) provides penalties only for violations of "this subchapter," which does not include regulations implementing section 1133; and (ii) that section 1133, which imposes obligations only on benefit plans, cannot impose liability on a plan administrator under section 1132(c). See Care First Surgical Ctr. v. ILWU-PMA Welfare Plan, 2014 WL 6603761, at *21-23 (C.D. Cal. July 28, 2014) (collecting cases); Bielenberg v. ODS Health Plan, Inc., 744 F. Supp. .2d 1130, 1143 (D. Or. 2010) ("This court is persuaded by the reasoning of the other circuits which have addressed the issue and declines to impose liability under 29 USC § 1132(c) for a violation of the regulations to 29 USC § 1133"); see also Medina v. Metro. Life Ins. Co., 588 F.3d 41, 48 (1st Cir. 2009) ("It is well established that a violation of § 1133 and its implementing regulations does not trigger monetary sanctions under § 1132(c)"); Brown v. J.B. Hunt Transport Servs., Inc., 586 F.3d 1079, 1089 (8th Cir. 2009) ("[W]e agree with our sister circuits that a plan administrator may not be penalized under § 1132(c) for a violation of the regulations to § 1133"); Wilczynski v. Lumbermens Mut. Cas. Co., 93 F.3d 397, 405-07 (7th Cir. 1996).

Plaintiff relies on two cases, neither of which address the issue of whether violations of 29 C.F.R. § 2560.503-1(h)(2)(iii) are enforceable through section 1132(c)(1)(B). In Crotty v. Cook, 121 F.3d 541 (9th Cir. 1997), the plaintiff's claim for section 1132(c) penalties was based on the plan administrator's failure to provide the summary plan description, which is a document specifically enumerated in section 1024(b)(4). 121 F.3d at 547. Crotty did not reach the question of whether this failure also constituted a violation of 29 C.F.R. § 2560.503-1, and if so, whether such a violation would independently trigger liability under section 1132(c). See also Care First Surgical Ctr. 2014 WL 6603761, at *23 n.71 (stating that Crotty involved penalties for a violation of section 1024, and thus was distinguishable from the plaintiff's claim that the defendant had violated section 2560.503-1). It is not clear why Plaintiff cites Russo v. Hartford Life & Accident Ins. Co., No. CIV. 00-938-LSP (CGA), 2002 WL 32138296, (S.D. Cal. Feb. 5, 2002), because the case does not involve section 1132(c), or a civil penalty remedy, at all. Russo discusses the duty to provide information under 29 C.F.R. § 2560.503-1, and held that the defendant's failure to provide required information could be remedied through supplementation of the administrative record. 2002 WL 32138296, at *4-5, *8.

The court grants summary judgment in favor of Defendants on Plaintiff's fourth claim for section 1132(c) civil penalties.

D. Remand to the ERISA Plan Administrator Is Inappropriate

Finally, the parties disagree as to whether remand to the Plan Administrator is appropriate in light of the court's determination that the Plan Administrator abused its discretion in denying Plaintiff's claim for benefits.

"[R]emand for reevaluation of the merits of a claim is the correct course to follow when an ERISA plan administrator, with discretion to apply a plan, has misconstrued the Plan and applied a wrong standard to a benefits determination." Saffle v. Sierra Pac. Power Co. Bargaining Unit Long Term Disability Income Plan, 85 F.3d 455, 461 (9th Cir. 1996) (ordering remand where plan administrator had abused its discretion by misinterpreting the plan's definition of "total disability"). However, remand is not always appropriate. "[A] plan administrator will not get a second bite at the apple when its first decision was simply contrary to the facts." Grosz-Salomon v. Paul Revere Life Ins. Co., 237 F.3d 1154, 1163 (9th Cir. 2001) (affirming district court's award of benefits and denial of request to remand where plan administrator "applied the right standard, but came to the wrong conclusion.").

In granting Plaintiff's motion for summary judgment on her claim for benefits under the IBM Plan, this court found an abuse of discretion where the Plan Administrator failed to review information under its control to investigate undisputed contradicting evidence submitted by Plaintiff. Under such circumstances, it would be inappropriate to remand the matter to give the Plan Administrator a "second bite."

IV. CONCLUSION

For the foregoing reasons, the court grants summary judgment in favor of Plaintiff on her first claim for benefits under the IBM Plan, and orders the payment of benefits in accordance with this order.

The court does not reach Plaintiff's second and third causes of action, as Plaintiff concedes that if she is awarded benefits under the IBM Plan through her first claim, she is not entitled to further relief through those claims.

The court grants summary judgment in favor of Defendants on Plaintiff's fourth claim for civil penalties under 29 U.S.C. § 1132(c).

IT IS SO ORDERED. Dated: January 29, 2016

/s/_________

Donna M. Ryu

United States Magistrate Judge


Summaries of

Gurasich v. IBM Ret. Plan

UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA
Jan 29, 2016
Case No. 14-cv-02911-DMR (N.D. Cal. Jan. 29, 2016)
Case details for

Gurasich v. IBM Ret. Plan

Case Details

Full title:JOAN GURASICH, Plaintiff, v. IBM RETIREMENT PLAN, et al., Defendants.

Court:UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF CALIFORNIA

Date published: Jan 29, 2016

Citations

Case No. 14-cv-02911-DMR (N.D. Cal. Jan. 29, 2016)

Citing Cases

Zavislak v. Netflix, Inc.

Gurasich v. IBM Ret. Plan, No. 14-CV-02911-DMR, 2016 WL 362399, at *11 (N.D. Cal. Jan. 29, 2016).…

Metro. Life Ins. Co. v. Metro. Life Ins. Co.

"Section 2560.503-1 is an implementing regulation for 29 U.S.C. § 1133, which provides that benefit plans…