Israelitt v. Enterprise Services LLC

CourtDistrict Court, D. Maryland
DecidedMarch 2, 2021
Docket1:18-cv-01454
StatusUnknown

This text of Israelitt v. Enterprise Services LLC (Israelitt v. Enterprise Services LLC) is published on Counsel Stack Legal Research, covering District Court, D. Maryland primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Israelitt v. Enterprise Services LLC, (D. Md. 2021).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF MARYLAND

JEFFREY ISRAELITT, * * Plaintiff, * v. * Civil Case No. SAG-18-1454 * ENTERPRISE SERVICES LLC, * * Defendant. * * * * * * * * * * * * * * *

MEMORANDUM OPINION Plaintiff Jeffrey Israelitt (“Plaintiff”) filed a Second Amended Complaint against his former employer, Enterprise Services LLC (“Defendant”), alleging discrimination on the basis of disability, wrongful discharge, denial of reasonable accommodations, retaliation, and a hostile work environment.1 ECF 13. Discovery is now concluded. Defendant filed a motion for summary judgment, ECF 48, which I have reviewed along with the relevant exhibits, opposition, and reply. ECF 53, 54. Defendant also filed a motion to reopen discovery, ECF 55, which I have also reviewed along with the relevant exhibits, opposition, and reply. ECF 58, 62. Lastly, Plaintiff filed a motion for leave to file a surreply, ECF 56, which I have reviewed along with the relevant exhibits, opposition, and reply. ECF 57, 59. No hearing is necessary. See Loc. R. 105.6 (D. Md. 2018). For the reasons that follow, I will grant Defendant’s Motion for Summary Judgment in part and deny it in part, deny Plaintiff’s Motion for Leave to File a Surreply, and deny Defendant’s Motion to Reopen Discovery.

1 Plaintiff’s Second Amended Complaint only includes three Counts, but the legal theories listed appear to be encapsulated within those Counts. I. FACTUAL BACKGROUND The facts contained herein are taken in the light most favorable to Plaintiff, the non-moving party. Defendant hired Plaintiff, an Army Veteran, as a senior architect in 2013. He was interviewed by George Romas, who reviewed his resume and conducted a telephonic interview. ECF 53-1 at 2. Romas did not inquire about any disability or medical conditions during the

interview. ECF 53-3 at 24-25. Plaintiff was ultimately hired to be a member of HP’s Cybersecurity Solutions Group (“CSG”). When he started on August 5, 2013, Plaintiff’s job duties included formulating architectural decisions on information systems for government customers and researching innovative technologies to see how they could be used to “create a discriminator for HP in order to win business.” Id. at 24. Plaintiff’s position was “a senior role,” id., and he worked remotely. ECF 48-3 at 96. Plaintiff has long suffered from a medical condition called hallux rigiditis, marked by degenerative changes in his right first metatarsophalangeal joint and right great toe. ECF 53-8. He had cheilectomies in 1993 and 1997. Id. In 2005 and 2018, radiologists examined his foot

and found degenerative changes in the metatarsophalangeal joint. Id. at 1-2. A podiatrist, examining Plaintiff in 2006, stated that he has ‘limited range of motion’ in his toe. Id. at 3. Plaintiff told the podiatrist at that visit that his pain level is 2/10 and “mild.” Id. Plaintiff has also State of Maryland disability placards as a result of his condition. Id. at 4-9. Plaintiff reports that, at times, he “can barely walk” because of pain. ECF 53-2 at 22. Plaintiff walks for physical exercise “a couple of times a week.” Id. at 24-25. As an example, he walks inside a store like Costco for 30-45 minutes, sometimes starting and stopping frequently due to his medical problems. Id. Near the end of August, 2013, HP began determining which of its employees would attend a conference called HP Protect 2013. Initially, Plaintiff was slated to attend the conference, though securing the requisite passes proved less than straightforward. Kevin Doty, a business consultant on the CSG team, told Todd Helfrich, an account executive who offered to secure passes for CSG’s hopeful attendees, that his group had three people they would like to attend the conference, including Plaintiff. ECF 53-11 at 2. Helfrich later notified the group that they had eight CSG

employees who requested passes and that there would thus be a need “to prioritize attendance.” Id. at 1. The campaign marketing manager observed that they were “scrambling to find the funds to pay for George [Romas] and one of his engineers to attend the event.” ECF 53-10 at 1. Gail Stevens, the capture manager, told the campaign marketing manager, “We would like to have George Romas (CyberSecurity Engineering Lead) and Jeff Israelitt (Lead Architect for our CDM Offering and the Task Orders) attend, and I would like to attend, and I think we might have 1 other person.” Id. Eventually, Helfrich sent Plaintiff a code to attend the conference, however the registration code he sent was one otherwise reserved for customers. ECF 53-13. Plaintiff promptly registered to attend. However, he sought to stay at the event hotel in Washington, DC, rather than to commute

or stay at a nearby location. ECF 53-2 at 113. He asked for a hotel room for persons with disabilities. Id. at 115. Though there were no hotel rooms available initially, Plaintiff worked with HP Protect event staff and eventually secured a room reservation. Id. at 115-116. However, on September 10, 2013 he was informed that his conference registration was invalid, because he had used a customer registration code but was an HP employee. ECF 53-13 at 8. Plaintiff reported the situation to Doty, and Doty in turn relayed the message to Helfrich. Id. at 7. Helfrich responded, “Anyone who used the code and registered with their HP email address likely will be turned down. I have some damage control that I need to do. Gail, George and Anil should be good.” Id. at 6. In the email exchange that followed, Plaintiff requested clarification of the status of his registration from Helfrich and, when that was not forthcoming, followed up with Doty about Helfrich’s unresponsiveness. Id. at 5-6. Doty suggested that Plaintiff coordinate with Romas directly, to which Plaintiff responded referencing several conversations he claimed to have had with Romas regarding the HP Protect conference and his difficulties registering for it. Id. at 3.

Plaintiff told Doty that Romas had “heard that [Plaintiff’s difficulty registering] was as a result of [his] asking the registration team questions,” and that Plaintiff told Romas that “the only question I asked involved disability accommodation for lodging.” Id. Plaintiff then stated that “it appears that this information (medical/disability info that I asked you not to share with anyone) . . . has in itself become the reason I can’t go now.” Id. Doty forwarded Plaintiff’s email to Romas outlining at length his concerns about Plaintiff’s behavior, including alleged statements Plaintiff had made to him about faking his disability and manufacturing lawsuits. Id. at 2. Romas, in response, said, “after about a 45 minute conversation with [Plaintiff] at around 7pm last night [September 12, 2013], he said he would ‘keep his mouth shut’ about this, not attend HP Protect, and hoped that the rest of us would not have any trouble

attending.” Id. at 1. Separately during this same time period, Plaintiff and Romas exchanged several emails between September 13 and 15 regarding Plaintiff’s registration difficulties, in which Plaintiff suggested that Doty, Helfrich, and others thought that his disability accommodation request had “created a problem” by drawing attention to their registrations. ECF 53-16 at 2. Plaintiff ultimately did not attend HP Protect. Plaintiff suggests that his failure to attend had a detrimental impact on his job by virtue of him missing out on the opportunity to “get familiar with HP’s line of products and maybe some services” as well as “networking opportunities.” ECF 53- 2 at 137. Roughly two weeks later, on or around September 30, 2013, Romas reassigned Plaintiff from the two-week sprint teams he had originally been staffed on to longer-term assignments, including working on a project called the “Technology Roadmap.” ECF 48-4 at 6.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

United States v. Diebold, Inc.
369 U.S. 654 (Supreme Court, 1962)
McDonnell Douglas Corp. v. Green
411 U.S. 792 (Supreme Court, 1973)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
St. Mary's Honor Center v. Hicks
509 U.S. 502 (Supreme Court, 1993)
Rhoads v. Federal Deposit Insurance Corporation
257 F.3d 373 (Fourth Circuit, 2001)
Benjamin Reynolds v. American National Red Cross
701 F.3d 143 (Fourth Circuit, 2012)
Lamont Wilson v. Dollar General Corporation
717 F.3d 337 (Fourth Circuit, 2013)
Kaszynski v. Thompson
83 F. App'x 526 (Fourth Circuit, 2003)

Cite This Page — Counsel Stack

Bluebook (online)
Israelitt v. Enterprise Services LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/israelitt-v-enterprise-services-llc-mdd-2021.