Professional Documents
Culture Documents
Crawford
Crawford
COMPLAINT
Plaintiff Crawford & Company (“Crawford”) brings this action for breach of
Despite Cognizant’s assurances that it would design, deliver and implement fully
experienced serious problems with the software. Even though Crawford notified
1742874.1
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 2 of 23
properly staff the project and to miss important deadlines, all causing significant
own customer relationships. This lawsuit seeks recovery for Cognizant’s breach of
2.
3.
Texas.
4.
citizen of Delaware and Texas), and the amount in controversy in this action
exceeds the sum or value of $75,000, exclusive of interest and costs. Accordingly,
this Court possesses subject matter jurisdiction over this dispute under 28 U.S.C.
§ 1332(a)(1).
1742874.1
2
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 3 of 23
5.
in Gwinnett County.
FACTS
6.
administration services and services for large and complex claims, among others.
7.
expenditure project to update the technology that supports several of its primary
1742874.1
3
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 4 of 23
8.
complex software that costs millions of dollars and requires years to accomplish.
Crawford planned for its ERP to integrate software for different business functions,
including but not limited to “Risktech” software for claims management and
9.
1742874.1
4
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 5 of 23
10.
11.
Exhibit A.
12.
The MSA contemplated that the parties would “enter into one or more
requested by Client [Crawford] (each, and as modified by the parties from time to
time, a “Work Schedule”).” MSA § 1.1. The MSA also provides that “[e]ach
1742874.1
5
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 6 of 23
Work Schedule shall specifically identify this Agreement and indicate that it is
13.
14.
15.
The MSA expressly warrants Cognizant’s work and provides that “the
set forth in the Work Schedule; and the Deliverable will materially conform to the
corresponding product specifications set forth in the applicable Work Schedule for
16.
the warranty, the MSA provides that “Cognizant, at its expense, will promptly use
1742874.1
6
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 7 of 23
itself of all rights and remedies available under applicable law or in equity
(including the right to seek a refund of all fees paid for the impacted
Deliverable(s)).” Id.
17.
The MSA provides that Crawford “may withhold payment of any amount
18.
The MSA allows Crawford to “terminate this Agreement and/or any Work
Schedule without cause upon forty-five (45) days written notice.” MSA § 11.2
19.
Section 7.4 of the MSA provides that Cognizant will cover Crawford’s
20.
1742874.1
7
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 8 of 23
21.
22.
In 2014, Crawford and Cognizant kicked-off Project Atlas and began the
“December 1, 2014 SOW”). Between 2016 and 2018, Crawford and Cognizant
entered into at least seven addenda to the 2014 SOW. The December 1, 2014
SOW along with all its addenda will be collectively called the “2014
23.
prepare the technical design and other documents required for the creation and
1742874.1
8
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 9 of 23
provided for work relating to conversion and testing that would take place for
PeopleSoft Financials.
24.
The 2014 Implementation Work Schedule initially estimated that the total
cost for the services Cognizant was providing was over $2 million.
25.
from November 2016 through August 2018 to address various aspects of the
Cognizant and Crawford executed the “PeopleSoft Common Testing SOW 2016 -
2017,” followed by at least eight addenda, under which Cognizant was to provide
testing services, among others, for various applications to ensure that the new
26.
By early 2017, Crawford and Cognizant entered into a SOW for the official
obligations post “Go Live”—the time when Crawford users would begin using the
1742874.1
9
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 10 of 23
Schedule”). The 2017 Support Work Schedule incorporated the terms of the MSA.
27.
the PeopleSoft software using “modules” for project costing, contracts, billing, e-
28.
The rollout of the PeopleSoft software was to take place in two phases. In
Crawford’s general ledger, accounts payable, travel and expense and revenue
29.
1742874.1
10
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 11 of 23
test”;
unit test.”
30.
The 2017 Support Work Schedule called for Cognizant to have a team of
additional employees to assist offsite and offshore. Cognizant estimated that the
total cost for the “CORE” team through December 2019 would be nearly $1.8
million.
31.
Crawford and Cognizant entered into other Work Schedules as well (all of
which incorporate the terms of the MSA) for the purpose of implementing
PeopleSoft Financials. Those Work Schedules include, but are not limited to Work
1742874.1
11
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 12 of 23
Schedules beginning with SOWs dated February 20, 2017, October 3, 2017,
October 16, 2017, January 3, 2018, June 1, 2018, and August 8, 2018.
32.
Crawford’s finances, the damages resulting from Cognizant’s failure have been
severe.
33.
technical design and coding. Cognizant’s code design problems were not limited
to any one module of PeopleSoft. To the contrary, Cognizant’s code design failed
across the board. And it was clear that Cognizant failed to run a thorough code
deficient coding, which failed to conform to the technical design and unit tests or
34.
For example, under the 2017 Support Work Schedule, Cognizant promised
1742874.1
12
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 13 of 23
35.
But due to several coding issues and a lack of proper testing, the PeopleSoft
36.
testing. The combination of poor coding standards and insufficient testing resulted
effect on the bottom line. And as a public company, these type of issues have the
potential to affect Crawford’s reporting, are a major concern, and have cost
37.
with the project, which resulted in additional cost and delays when the PeopleSoft
1742874.1
13
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 14 of 23
38.
After “Go Live,” in early 2018, when Crawford began to try to use
of the work Cognizant was responsible for involved “batch processing,” such as
found that the report continued to run for several days. These delays prevented the
preparation of timely management reporting, and even the ability to timely produce
hire a third party to identify the problems and recommend remedial measures.
39.
Crawford has experienced a problem with another process, the “flat rate
escrow process.” Cognizant has been unable to identify the root cause of a
Correcting these errors has required significant expense to Crawford who was
required to spend countless hours and fees with external audit teams to avoid even
more dire damages resulting from Cognizant’s failures. And Cognizant has still
1742874.1
14
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 15 of 23
problems and repair them as they are obligated to do under the contracts.
40.
on adjusters to assist its clients, when, for example, a natural disaster occurs. In
that circumstance, Crawford’s global scale allows it to deploy people for clients
who find themselves suddenly inundated with a high volume of claims. As a result
This created major problems for Crawford, including not only the revenue and
financial reporting problems but the predictable damage to morale that happens
41.
Crawford also has significant service fee billing and loss funding problems
issues, among others. System performance issues resulted in several days where
1742874.1
15
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 16 of 23
Crawford was unable to draw from its clients’ bank accounts to fund their loss
shoddy work, caused massive problems for Crawford’s finance and accounting
teams and has caused client dissatisfaction to the point that some customers have
requested that Crawford revert to its pre-PeopleSoft Financials legacy systems, and
42.
Cognizant has failed to meet service level agreements for support incidents
assigned to it. Long delays and backlogs have caused damage to Crawford’s
that never seem to be fixed has caused big problems for Crawford’s internal teams
43.
Despite being aware of these problems, and despite its knowledge that it was
behind target dates on important deadlines, Cognizant has failed to properly staff
the team who is supposed to be dedicated to the work at Crawford (both onsite in
Atlanta and offsite). For example, in September 2018, a key Cognizant employee
1742874.1
16
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 17 of 23
staffed onsite at Crawford went on unplanned leave just before a critical deadline
with no notice to Crawford. More importantly, Cognizant had not planned for and
did not have a plan for how it would proceed to try to meet the deadline in this
44.
person and in writing. Indeed, complaints were made not only by Crawford’s
project manager for Project Atlas, but the issues were so serious that Crawford’s
Chief Global Information Office and Crawford’s Chief Operating Officer escalated
45.
Crawford had worked with Cognizant for years in good faith to implement
1742874.1
17
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 18 of 23
46.
47.
48.
49.
summary of a few of the problems that Crawford has been experiencing with
PeopleSoft.
50.
responded by concluding that all of the problems were “excusable” under the MSA
1742874.1
18
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 19 of 23
and result from actions that were “beyond ‘Cognizant’s reasonable control.’”.
And even though Crawford disputed the invoiced amounts pursuant to the MSA,
stated herein.
52.
The MSA and Work Schedules are valid, binding contracts between
53.
provide the deliverables under the MSA and applicable Work Schedules constitute
54.
Cognizant’s breaches include but are not limited to failures in: technical
1742874.1
19
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 20 of 23
55.
Under the terms of the contract, Crawford timely notified Cognizant of the
56.
described in the Work Schedules); MSA § 8.1 (the express limited warranty) and
others.
57.
Cognizant’s actions breached the SOWs and Work Schedules for the
58.
Cognizant’s actions and failures breached the duty of good faith and fair
dealing.
1742874.1
20
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 21 of 23
59.
contract action.
60.
61.
stated herein.
62.
Pursuant to the Section 7.4 of the MSA, Cognizant owes Crawford for its
which brings “claims” that were “caused directly and proximately by the
§ 7.4.
63.
In addition, Cognizant has acted in bad faith, been stubbornly litigious, and
1742874.1
21
Case 1:19-cv-00674-TCB Document 1 Filed 02/08/19 Page 22 of 23
64.
be proven at trial;
3. That the Court award Crawford its attorneys’ fees and expenses of
provided by law;
6. That the Court award such other and further relief as shall appear just
and proper.
Respectfully submitted,
1742874.1
23