MEMORANDUM OPINION AND ORDER
In this action, plaintiffs allege on behalf of themselves and all others similarly situated that defendant Electronic Data Systems Corp. (“EDS”) miselassified them as exempt, denying them overtime pay for hours they worked in excess of forty per week. This motion seeks certification as a collective action under the Fair Labor Standards Act, 29 U.S.C. §§ 201 et seq. (“FLSA”), to facilitate the sending of notice to potential party plaintiffs. 1 EDS opposes this motion, asserting that plaintiffs cannot show that they are “similarly situated” under the FLSA. For the reasons state below, the motion is GRANTED in part.
BACKGROUND
I. Factual Background
EDS is an information technology (“IT”) outsourcing company. Its personnel work as computer support technicians, analysts, and engineers throughout the world, although the putative plaintiffs here are all in the United States. EDS employees perform a myriad of computer support tasks, ranging from actual physical installation and repair of computers to advising customers on equipment purchases and system upgrades to customization of third-party software applications to meet customers’ needs.
The most specific labels used to classify EDS employees are “job codes,” five-digit numeric codes that correspond to a job title and a job description.
(See
Lesser
Several job codes aggregate into a job progression, which is “designed as a planned progression of work, with each succeeding level becoming more complex and requiring greater knowledge and expertise.” (Id. at 9, 11; see also Lesser Decl. Ex. 36.) For example, the “Service Center” job progression consists of the job titles and codes Service Center Analyst (34530), Service Center Analyst Advanced (34540), and Service Center Analyst Senior (34550). (Lesser Decl. Ex. 36.) The “Business Process Improvement” job progression consists of Business Process Improvement Administrator (50900), Business Process Improvement Analyst (31900), Business Process Improvement Specialist (31901), Business Process Improvement Specialist, Senior (31902), and Business Process Improvement Consultant (31903). (Id.)
The next level of classification involves “job families,” which are “collection[s] of jobs that involve similar types of work.” (Lesser Decl. Ex. 40 at 9.) They describe “a group of jobs relating to the same nature of work ... but requiring different levels of skill, effort, and responsibility.” (Lesser Decl. Ex. 34 at 3.) EDS has twelve different job families, such as “Service Delivery,” “Corporate,” and “Human Resources.” (Lesser Decl. Ex. 40 at 9.) Multiple job progressions aggregate into one job family; for example, the “Service Delivery” job family contains both the “Service Center” and “Business Process Improvement” job progressions. (See Lesser Decl. Ex. 36.)
The job code classification system is intended to ensure compliance with certain labor laws, including the FLSA. Specifically, whether an employee should be classified as exempt under the FLSA is among the most important considerations in assigning his job code. (See Evans Dep. at 77-83; Lesser Decl. Ex 43 at 3 (“Getting the exemption status right is the first and most important step.”).) Indeed, EDS training materials relating to job code selection caution that “THE EXEMPTION STATUS MUST COMPLY WITH THE FAIR LABOR STANDARDS ACT.” (Lesser Decl. Ex. 43 at 2.) EDS assigns job codes to employees through a process called “job analysis,” which is the “[p]rocess of defining a job in terms of its component tasks or duties and the knowledge or skills required to perform them.” (Lesser Decl. Ex. 41 at 3.) The person performing job analysis gathers information about a job’s context, content, specifications, and the materials and equipment used in that job. (Id.) This information, among other things, “[sjupports job code matching” and is “[n]ecessary to ensure compliance with work-related employment laws and regulations.” (Id. at 4.)
The job descriptions associated with a particular job code are intended to be “[a] summary of the most important duties and major responsibilities of the job, including the general nature of the work performed.” (Lesser Decl. Ex. 40 at 13.) EDS training materials advise those as
Instead of centrally assigning job codes, EDS delegates this function to local managers. (See Evans Dep. 38-44.) Although corporate officials are available for “guidance” on job code assignments, the local manager ultimately makes the decision. (Id.) Therefore, EDS contends that despite its “intent” to have employees coded correctly, the “reality” was that managers’ decisions could be incorrect. (Id.) EDS’s internal investigations have found “that some organizations have up to 50% of employees improperly job coded (incorrect job family progression, incorrect level, or incorrect exemption classification).” (Lesser Decl. Ex. 40 at 14.) Indeed, EDS engaged in an internal audit in 2007-08 that resulted in the reclassification of some of its employees. (Evans Dep. at 101-02, 195-203.)
II. Procedural Background
In most cases, the motion to certify a collective action is brought early in the litigation, but one of the cases in this action has been pending since 2006. As such, some explanation of the procedural history of this action is appropriate.
As of the filing of this motion, this action consisted of two cases consolidated for pretrial purposes,
Cunningham, et al. v. Electronic Data Systems Corp., et al.,
No. 06 Civ. 3530, and
Steavens, et al. v. Electronic Data Systems Corp.,
No. 08 Civ. 10409.
2
The
Cunningham
action was commenced on May 10, 2006. In 2006, the parties conducted limited discovery on the issue of whether the “function prong” of the FLSA’s air" carrier exception, 29 U.S.C. § 213(b)(3) applied.
(See Cunningham,
ECF No. 21.) On January 4, 2008, EDS filed a motion for summary judgment on this issue and a motion to dismiss the plaintiffs’ claims that it failed to keep adequate records. The Court issued a Memorandum Opinion and Order dated September 30, 2008 that granted the motion to dismiss but denied the motion for summary judgment on the grounds that EDS had misinterpreted the “control prong” of the air carrier exception.
Cunningham v. Electronic Data Systems Corp.,
On March 5, 2009, the Court consolidated the Steavens and Cunningham actions for pretrial purposes only. (Cunningham, ECF No. 48; Steavens, ECF No. 13.) On August 14, 2009, the plaintiffs in both cases moved to consolidate the actions for all purposes. By Order dated March 30, 2010, the Court denied the motion without prejudice to refiling at the time plaintiffs file motions for class certification. Most recently, on April 7, 2010, plaintiffs filed this consolidated motion seeking conditional certification and court-authorized notice pursuant to 29 U.S.C. § 216(b).
DISCUSSION
I. The Overtime Pay Requirement and Collective Actions Under the FLSA
The FLSA provides that “no employer shall employ any of his employees ... for a workweek longer than forty hours unless such employee receives compensation for his employment in excess of the hours above specified at a rate not less than one and one-half times the regular rate at which he is employed.” 29 U.S.C. § 207(a)(1). This overtime pay requirement, however, is subject to a number of exemptions. For example, the FLSA exempts “any employee employed in a bona fide executive, administrative, or professional capacity.” 29 U.S.C. § 213(a)(1). The statute also contains an exemption for certain computer-related skilled positions. 29 U.S.C. § 218(a)(17).
The FLSA further provides that a collective action “may be maintained against any employer ... in any Federal or State court of competent jurisdiction by any one or more employees for and in behalf of himself or themselves and other employees similarly situated.” 29 U.S.C. § 216(b). Potential “similarly situated” plaintiffs in FLSA collective actions must “opt in” to the suit to benefit from the judgment.
Id.
(“No employee shall be a party plaintiff to any such action unless he gives his consent in writing to become such a party and such consent is filed in the court in which such action is brought.”). This stands in contrast to class action suits under Fed.R.Civ.P. 23, in which individuals are deemed members of the class unless they opt out of the suit.
See Cuzco v. Orion Builders, Inc.,
“Neither the FLSA nor its implementing regulations define the term ‘similarly situated.’ ”
Hoffmann v. Sbarro, Inc.,
Once a court is satisfied that the first-stage inquiry has been satisfied, it conditionally certifies the class and orders notice to putative class members, who are given the opportunity to opt in.
Rubery v. Buth-Na-Bodhaige, Inc.,
“At the second stage, the district court will, on a fuller record, determine whether a so-called ‘collective action’ may go forward by determining whether the plaintiffs who have opted in are in fact ‘similarly situated’ to the named plaintiffs.”
Myers,
II. Heightened Scrutiny
As a threshold matter, EDS argues that the Court should skip the lenient first-stage analysis and apply the more stringent second-stage analysis instead. Because plaintiffs have conducted some discovery, defendant argues that the Court now has a sufficient factual record to conduct the more searching inquiry typically done at the second stage. (See Def.’s Mem. at 15-18.)
EDS’s contention conflicts with the general practice of courts in this Circuit. Even where the parties have undertaken substantial discovery, our courts have continued to use the first-stage certification analysis.
See, e.g., Gortat,
Defendant cites two cases within this Circuit in support of its contention that “[o]nce an adequate factual record pertaining to § 16(b) certification has been developed through discovery, courts routinely recognize that the inception standard is inapplicable even in regard to first phase certification motions.” (Def.’s Mem. at 16.) First, EDS cites
Amendola v. Bristol-Myers Squibb Co.,
Second, EDS cites to
Torres v. Gristede’s Operating Corp.,
04 Civ. 3316(PAC),
EDS also cites to several out-of-Circuit cases to support its position that heightened scrutiny applies here because of the amount of discovery that has taken place. However, in three of the cases cited,
Harris v. FFE Transportation Services, Inc.,
No. Civ. A. 3:05cv0077-P,
III. First-Stage Analysis
Plaintiffs seek to certify three “classes” with exempt job codes as follows: 3
Class A: Service Delivery Job Family — consisting of Systems Administrators (34060, 34070, 34080); Telecommunications Analysts (34500, 34510, 34520), and Service Center Analysts (34530, 34540, 34550)
Class B: Technical Delivery Job Family — consisting of Infrastructure Analysts (34260, 34270, 34280), and Information Analysts (34330, 34200, 34210, 34220); and
Class C: Corporate Job Family — consisting of Information Security Analysts (33700, 33710, 33720, 33730).
(Pl.’s Mem. at 3.)
A. Myers and the First-Stage Test
Before applying the first-stage test to these putative collective action groups, it is necessary to determine how the first-stage test is applied in an FLSA exemption case, since the parties dispute the relevant standard. Plaintiffs maintain that they have satisfied their burden because they “have shown that EDS has the requisite ‘uniform business practice’ — EDS’ ‘Job Analysis’ classification system.” (Pl.’s Reply at 7 (quoting
Damassia v. Duane Reade, Inc.,
No. 04 Civ. 8819(GEL),
The Second Circuit’s recent opinion in
Myers,
however, belies EDS’s argument. “In a FLSA exemption case,” plaintiffs satisfy their burden “by making some showing that ‘there are other employees ... who are similarly situated with respect to their job requirements and with regard to their pay provisions,’ ... who are classified as exempt pursuant to a common policy or scheme.”
Myers,
At oral argument, EDS argued that this would be a misreading of
Myers.
According to EDS,
Myers
instead emphasizes “that the exemption inquiry requires examination of the duties that the employee actually performs, and they involve evidence tending to show that the plaintiffs’ jobs were similar in ways material to the establishment of the exemption criteria.”
Myers,
On the other hand, plaintiffs’ interpretation of their burden creates a lower standard than that which
Myers
endorsed. Plaintiffs contend that their showing of a “uniform business practice” in EDS’s “Job Analysis” system is sufficient, but according to
Myers,
plaintiffs must show that they are similarly situated not only with respect to the employer’s conduct toward them, but also in their job responsibilities. At oral argument, plaintiffs’ counsel conceded that
Myers
set forth this two-pronged inquiry. The test articulated by
Myers,
therefore, requires plaintiffs in FLSA exemption cases to show both that there are other employees who are similarly situated with respect to their job requirements and pay provisions, and that they are classified as exempt pursuant to a common policy or scheme. That showing is sufficient for court-facilitated notice, and courts are not required to engage in a
B. Application of the Myers Test
Plaintiffs have satisfied their burden in this case. First, they have shown that potential plaintiffs were classified as exempt pursuant to a common policy or scheme, namely EDS’s “job analysis” resulting in their classification as exempt.
(See
Pl.’s Reply at 7-8.) It is undisputed that all of the proposed class members are paid on a salaried basis, classified as exempt, ineligible for overtime pay, and do not receive overtime pay; and further, that their job codes determine their exempt status throughout the United States.
(See
Evans Dep. at 131-32, 136-37, 140.) EDS argues that plaintiffs “fail to identify a particular EDS policy or practice that resulted in all 19,500 proposed class members being misclassified as exempt.” (Def.’s Opp’n at 27.) But plaintiffs showing is sufficient to demonstrate a common policy or scheme classifying employees as exempt.
See Lynch,
Plaintiffs have advanced two arguments to show that they are similarly situated with respect to job duties and pay provisions. First, plaintiffs argue that because all opt-in and potential plaintiffs share computer-related responsibilities in a broad sense, they are similarly situated. For example, plaintiffs assert that employees in Class A are similarly situated to each other because they “perform[] non-managerial technical support work that does not involve running EDS’ business; i.e., have as their primary duties installing, maintaining, and/or supporting computer hardware or software.” (Pl.’s Mem. at 7.) They assert that Class B members “all perform similar non-managerial duties consisting of installing, maintaining, and/or supporting computer hardware and/or software.” (Pl.’s Mem. at 10.) Class C members are alleged to be similarly situated because they “performed the same non-managerial duties related to access to the computer networks, providing proper passwords or resetting the passwords of the users of the networks, virus protection and quarantine of websites that have been attacked by viruses, adding websites to a firewall, installing virus protection and detecting and scanning for viruses on end users [sic] computers.” (Pl.’s Mem. at 12.) EDS argues that these descriptions use “imprecise, meaningless terms.” (Def.’s Opp’n at 24.) Additionally, because plaintiffs describe the responsibilities of both Class A and B members as “installing, maintaining, and/or supporting computer hardware and/or software,” EDS maintains that the “ ‘install/maintain/support’ mantra is meaningless in terms of describing exempt duties.” (Id. at 24.)
Defendant has the better of the argument with respect to these descriptions of potential class members’ respon
Plaintiffs’ stronger argument relies on EDS’s own internal structure. According to plaintiffs, because EDS’s “Job Analysis” system was intended to ensure compliance with labor laws, including the FLSA, “EDS knew full well that the job codes assigned to individuals on a prescribed, systematic basis whose importance was emphasized had significance for FLSA purposes.” (See Pl.’s Mem. at 5.) Mindful of the FLSA implications of job coding, “EDS groups employees who perform similar work into ... job codes.” (Pl.s Mem. at 4.) Plaintiffs argue that since EDS itself assigned these job codes to its employees, emphasizing both the FLSA exemption implications of incorrect matching and the importance of creating a substantial match between actual duties performed and the job code assigned, that the use of job codes to group “similarly situated” plaintiffs together is appropriate. The Court agrees.
Plaintiffs are required only to make a “modest” factual showing, and EDS’s own documentation indicates that “[g]etting the exemption status right is the first and most important step” in selecting an employee’s job code and that job codes are “used to identify a given set of duties and responsibilities assigned to individuals whose work is of the same nature and level.”
(See
Lesser Decl. Ex. 38 at 4; Lesser Deck Ex. 43 at 3.) All job codes were associated with job descriptions that had to “be broad enough for use throughout EDS.” (Lesser Decl. Ex. 40 at 8.) “Plaintiffs need not show that they and [other potential plaintiffs] are identically situated, only similarly situated.”
Hallissey v. America Online,
No. 99 Civ. 3785(KTD),
EDS further argues that “Plaintiffs’ reliance on EDS job codes for class certification ... is incompatible with the merits of their claims.” (Def.’s Opp’n at 29.) In support of its argument, EDS relies on the fact that some of the job codes involved here (1) were adjudicated as exempt in a separate class action under California law and (2) are associated with job descriptions that list some exempt duties.
See generally Heffelfinger v. Electronic Data Systems Corp.,
Finding that employees within a single job code are similarly situated, however, does not answer the question of whether the Court should certify plaintiffs’ proposed classes. Plaintiffs have not sought to certify collective actions composed of individual job codes, but of whole job families. Therefore, to answer that question,
Plaintiffs’ argument recited thus far answers only the first of these questions. EDS argues that the answers to the other questions must be in the negative. According to EDS, even assuming that employees within a given job code are similarly situated to each other, it does not follow that employees within a given job family, which contains multiple job codes, are also similarly situated. Plaintiffs counter that “[njotwithstanding that they had different job codes, they were ... part of the same job progression in the same job family, which, as EDS acknowledges, means succeeding levels of similarly situated jobs that become more complex and require greater knowledge.” (Pl.s Reply at 6.)
To the extent that EDS’s argument relies solely on the presence of multiple job codes existing within one job family, it fails, as “[cjourts routinely grant conditional certification of multiple-job-title classes such as Plaintiffs’ class.”
Lewis v. Wells Fargo,
However, this structure does not show that employees in different job progressions, even if in the same job family, are similarly situated, so the third question must be answered in the negative. A job family contains multiple job progressions. (See Lesser Decl. Ex. 36.) The “Service Delivery” job family that plaintiffs seek to certify, for example, appears to include “Business Process Improvement” and “Business Service Analyst” job progressions, whose duties, at least from the job titles themselves, would appear not to be similar to the Service Center Analysts, Telecommunications Analysts, and Systems Administrators that plaintiffs seek to include in Class A. (See id.) This implies that the third question, whether different job progressions can be included in a single class, should be answered in the negative.
The .Court finds it appropriate, therefore, to certify each job progression that plaintiffs identify as containing potential plaintiffs, rather than to certify classes by job family. Although subdivision is typically done at the second stage of litigation, because plaintiffs rely on EDS’s job classi
It may very well be that job duties within a given job code or job progression vary too much to allow an efficient resolution of claims. These inquiries, however, are to be addressed at the second stage of collective-action certification. It is sufficient here that plaintiffs have made a modest showing that they share similar duties and are uniformly subject to EDS’s policy of classifying them as exempt.
IV. Form of Notice
Plaintiffs have included a proposed notice to be sent to potential class members, but EDS has indicated that it objects to the form of the notice. (Def.’s Opp’n at 30 n. 13.) The parties did not address the issue of the propriety of the notice extensively in their papers or at oral argument. Accordingly, the Court declines to address the issue of the form of notice at this time.
CONCLUSION
For the foregoing reasons, the Court GRANTS in part plaintiffs motion to certify [06cv3530 Docket No. 140, 08cvl0409 Docket No. 87] this action as a collective action. The parties are directed to confer about the form and content of the notice that will be sent to potential opt-in plaintiffs. A joint proposed notice shall be submitted to this Court within three weeks of this opinion. If the parties cannot agree on a form of notice, they shall submit letter memoranda by that date.
SO ORDERED.
Notes
. Courts typically speak of “certification” or “conditional certification” of collective actions to facilitate notice, but this refers only to district courts' discretionary power to facilitate the sending of notice to potential class members. “Certification” is neither "necessary nor sufficient” for collective actions under the FLSA, but serves as a useful case management tool.
Myers v. The Hertz Corp.,
. A third case, George v. Electronic Data Systems Corp., 10 Civ. 1155, was consolidated with Steavens and Cunningham after the filing of this motion. All proceedings in George have been stayed pending resolution of this motion.
. These are not true "classes,” but for convenience’s sake, and because the plaintiffs have so styled them, this opinion will refer to "Classes” A, B, and C.
