Settling Disputes Part 2 of 2
NOTICE: WE ARE NOT LAWYERS. WE ARE NOT GIVING LEGAL ADVICE. YOU SHOULD OBTAIN LEGAL ADVICE FROM COMPETENT ATTORNEYS.
 As we posited in Part 1, we don’t think DCMA Contracting Officers are resolving many “contractual issues in controversy by mutual agreement at the contracting officer level” (as is the policy of the U.S. Government and as is established in DCMA’s own guidance to its COs). Instead, our experience has been that COs are simply rubber-stamping a DCAA audit report and issuing it as an attachment to their Final Decision—essentially daring the contractor to take them to court, instead of trying to negotiate an acceptable resolution. That’s the exact opposite behavior of what’s expected and required of a warranted Contracting Officer, yet nobody seems to be holding them accountable for their actions (or inactions).
As we’ve noted in several articles, the two courts in which contract disputes are litigated (the Armed Services Board of Contract Appeals and the U.S. Court of Federal Claims) have a tendency to strictly enforce the rules established by the Contract Disputes Act of 1978 (CDA). For instance, in this case, Judge Firestone of the COFC rejected a Government argument that it was entitled to an equitable adjustment (that would act to offset Raytheon’s claims related to an underfunded pension plan) because a Contracting Officer had never issued a final decision on the matter. Because the Government did not strictly follow the requirements of the CDA, she could not rule on the matter. She wrote—
… the court agrees with Raytheon, and holds that because the government’s claim for the pension surplus as a set-off is governed by the CDA, and because the government did not comply with the CDA, the court does not have jurisdiction over the government’s claim for a set-off based on the Optical segment closing adjustment surplus. … Because the government’s claim … is governed by the CDA, the government must show either that it complied with the CDA or that it is exempt from obtaining an administrative decision from the contracting officer establishing Raytheon’s liability for the surplus. … The fact that there was a decision on Raytheon’s claim does not excuse the government from having to provide its own contracting officer decision. Each specific claim has to have been the subject of a contracting officer decision. … The purpose of this requirement is to ensure that the contractor is on notice of its potential liability. … Here, Raytheon did not have notice of the government’s claim to a pension surplus in connection with the Optical segment closing until trial. … Raytheon would have had no reason to suspect that the government would later seek a set-off. … Thus, Raytheon did not have any notice of the government’s claim, contrary to the requirements of the CDA. … In sum, because the government needed a CDA decision in order to obtain payment from Raytheon for the Optical pension surplus and failed to obtain one, and because the court cannot find any reason for excusing the government’s failure to comply with the CDA’s jurisdictional requirements, this court will not exercise jurisdiction over the government’s claim for a set-off of the pension surplus arising from the Optical segment closing.
[Emphasis added.]
The Courts seem to be even-handed in their handling of the claims. In many other cases, the contractor has seen its claim thrown out of court (in whole or in part) because it did not comply with the requirements of the CDA. As the attorneys at Sheppard Mullin wrote, “there is no shortage of cases in which such appeals are dismissed for lack of jurisdiction because the original requests for payment did not constitute ‘claims’ under the CDA.”
It is important for contractors to understand when they have a claim and when they don’t. The SMRH blog article (link in above paragraph) discussed the Appellate Court decision in Parsons Global Services. Rather than recap the Court’s decision ourselves, we’ll quote from the SMRH attorneys, who wrote—
The case centered on the termination for convenience of several task orders under an indefinite-delivery-indefinite quantity contract awarded by the Army to Parsons for design-build work in Iraq. Parsons had entered into a subcontract with Odell International, Inc. (‘Odell’) to construct health care facilities and deliver medical equipment in Iraq pursuant to the prime contract. Shortly before the task orders were terminated for convenience by the Government, the Defense Contract Audit Agency (‘DCAA’) determined that Odell had been mistakenly billing Parsons using a lower overhead rate than was specified in the subcontract. Odell then invoiced Parsons for the difference, but Parsons refused to pay the invoice and submitted a termination settlement proposal to the Termination Contracting Officer (‘TCO’) without including the disputed Odell costs. Two years later, as part of settlement of the prime contract, DCAA audited Parsons' billed costs, including Odell's costs, and determined that Odell's costs at the higher overhead rate were supported and appropriate. Odell submitted a new invoice for the difference, and Parsons submitted three payment requests for the additional Odell costs to be paid directly by government. The TCO declined to act on the requests to settle directly with Odell. Parsons then submitted a sponsored ‘Certified Claim for Payment’ under the CDA on behalf of Odell to the Procurement Contracting Officer (‘PCO’), and appealed the PCO's denial of the claim to the Armed Services Board of Contract Appeals (‘ASBCA’). The Government moved to dismiss for lack of jurisdiction, arguing that Parsons' routine request for payment to the PCO did not amount to a claim under the CDA. Parsons countered that, because its requests for payment occurred two years after the termination of the task orders and thus could not be subject to routine invoicing and termination procedures, the request was non-routine and sufficient by itself to constitute a claim. The ASBCA sided with the Government and dismissed the claim. On appeal, the Federal Circuit affirmed the ASBCA's decision, holding that Parsons' request for payment was not a claim as defined in FAR 2.101. Under the FAR, demands for payment can be classified as either ‘routine’ or ‘non-routine.’ If the request is ‘non-routine,’ then it constitutes a claim under the CDA so long as ‘it be (1) a written demand, (2) seeking, as a matter of right, (3) the payment of money in a sum certain.’ However, if the request is ‘routine,’ a pre-existing dispute is necessary for it to constitute a claim under the CDA. As the Federal Circuit detailed, non-routine requests for payment typically spring from additional or unforeseen costs not covered by the contract:
Such requests include requests for equitable adjustments for costs incurred from ‘government modification of the contract, differing site conditions, defective or late-delivered government property or issuance of a stop work order’ and other government-ordered changes; for damages resulting from the government's termination for convenience and termination settlement proposals that have reached an impasse; for compensation for additional work not contemplated by the contract but demanded by the government; for the return of contractor property in the government's possession; and for damages stemming from the government's breach of contract or cardinal change to the contract.
In contrast, according to the Federal Circuit, the request for payment of Odell's costs made to the PCO was routine because the costs were explicitly covered by the contract and, but for the billing error, would have been subject to routine invoicing during contract performance. Furthermore, the routine request was not subject to a pre-existing dispute because the PCO, the appropriate official to evaluate the request, never received a proper request for payment prior to the improper ‘Certified Claim for Payment.’
Okay, perhaps that was a bit long-winded, but we think it’s important for you to get the distinction between a routine request for payment made pursuant to contractual terms and conditions, and a non-routine request for payment made based on alleged damages suffered from government action (or inaction). But the point of this article is that even non-routine requests for payment are not disputes within the meaning of the CDA until and unless negotiations have ended because the parties are at an impasse. And DCMA Contracting Offices are responsible for making good faith attempts to resolve non-routine requests for payment so that they don’t ripen into disputes and become claims that have to be heard by the Courts.
The ASBCA thoroughly discussed the role of the Contracting Officer in resolving potential claims in its 1982 decision, Space Age Engineering, Inc., (ASBCA No. 26028). In that pre-Internet decision, the ASBCA Judges wrote—
The contracting officer, when considering claims, serves in a quasi-judicial capacity. He has an obligation to consider all of the relevant and material evidence and to make findings of fact, and to apply the law to the facts found and render a fair, impartial and informed judgment. When a judgment is rendered which is not a fair, impartial and informed one, he has a duty to correct it. This corrective action can cut either way. A denial of a claim may turn into an upholding of a claim or vice versa.
[Emphasis added.]
In that same case, the Government asserted a counterclaim against the appellant (Space Age Engineering). The Government’s counterclaim was the subject of a Contracting Officer’s Final Decision, but the contractor had never been apprised of the facts underlying the counterclaim until it was presented in court. The ASBCA Judges rejected the Government’s counterclaim (even though it had been the subject of a COFD). The ASBCA looked to a then-recent Appellate Decision (Woods Hole), writing—
In the instant case there are a number of similarities to the Woods Hole case. There, as here, the contractor wanted a certain sum of money. There, as here, the Government believed the contractor was not entitled to the sum of money requested. There as here, the contracting officer unilaterally determined and set the amount of money it would pay. There, as here, the Government paid the amount of money it had unilaterally determined should be paid. There, as here, the contractor disagreed and appealed to higher authority. There, as here, while preparing to defend against the appeal Government lawyers concluded that grounds existed upon which to claim back all of the funds previously paid. There, as here, the contracting officer agreed with his lawyers and amended his earlier final decision, by the issuance of another final decision, and demanded the money back which it had earlier paid to the contractor. There, as here, the contracting officer had no contact with the contractor before issuing his second final decision and, obviously, gave him no opportunity to explain, argue or contest the proposed action. We believe that the same result should follow here, as there. The same reasoning is applicable. The least that should have been done was to give the contractor an opportunity to express his views on the proposed action before the contracting officer had reached his decision. We do not know if anything appellent could or would have said would have made any difference to the contracting officer but that is of no consequence. The defect in the process, which both the Court of Claims and the Court of Appeals found, was the failure to hear the other party before rendering a judgment. That failure deprives the decision of any efficacy.
[Emphasis added. Note that Woods Hole was subsequently vacated.]
The result was that the Government’s counterclaim was dismissed and the Government was invited to issue a “proper final decision.”
Another 1982 ASBCA case (Chandler Manufacturing and Supply, No. 27030) included a similar discussion of the need for discussions before a COFD is issued, though the Judges reached a different conclusion in that case. The ASBCA Judges wrote—
In view of appellant's statement in its 29 March 1982 letter of the contracting officer that ‘there has been no negotiating session in the terms of a fair and equitable settlement‘, the Board brought to the parties' attention that a contracting officer's determination of a Government claim against a contractor could possibly be deemed not to be a ‘decision’ within the meaning of Section 6(a) of the CDA unless the contractor has had some opportunity to reply to the claim. … Under the Contract Disputes Act we have continued to require that the contractor must have had an opportunity to express its views or state its position with respect to claims or demands the Government is pursuing against the contractor before a contracting officer could issue a decision pursuant to section 6(a) of the Contract Disputes Act. Even though we are unable to conclude that the contracting officer fully complied with and followed the procedure set forth in DAR app. E, Part 6, the above described circumstances show that the Government presented its position and claims to the contractor and the latter had the opportunity to dispute them. These circumstances provide, although perhaps only in a minimal way, a sufficient basis for the conclusion that the contracting officer's decision of 26 March 1982 regarding the Government's demands against the appellant constitutes a ‘decision‘ within the meaning of section 6(a) of the Contract Disputes Act. The appeal from this decision suffices to give this Board jurisdiction over the subject matter included in the decision.
We want to discuss one more ASBCA case (United Aero, Inc., No. 26967, 1983) where the Judges took a different tack. They wrote—
However [the Government’s] argument does not recognize the facts that (1) the statute is a ‘Disputes' Act, (2) its legislative history shows a purpose to ‘induce resolution of more contract disputes by negotiation prior to litigation’, and (3), of most importance, as noted in Chandler Manufacturing and Supply, supra, the regulations which implement the Act, in DAR 1–314(i), provide for the steps to be taken by a contracting officer ‘when a claim by or against a contractor cannot be satisfied or settled by agreement and a decision on the claim is necessary . . .’ In addition to other requirements specified in the regulation, the contracting officer is required to include in the decision ‘a statement of the factual areas of agreement or disagreement.’(DAR 1–314(i)(2)(iv)) … As demonstrated above, the Board understands the law to have long been clear that contracting officers have not had, and do not have, the power to issue procedurally valid disputes article decisions, which could become final if not appealed, unless, inter alia, there has previously been a dispute concerning a question of fact arising under the contract to decide. Based on the implementing regulations, the rule is comparable under the Contract Disputes Act with respect to claims ‘relating to a contract’. (Section 6(a) of the Act). … Since the Government's purported final decisions were premature, the appeals are subject to dismissal without prejudice.
Readers, note that the ASBCA Judges noted that the intent of the Contract Disputes Act itself was to “induce resolution of more contract disputes by negotiation prior to litigation.” So there is a statutory basis (in addition to the regulatory basis we discussed in Part 1) for the responsibility of Contracting Officers to negotiate contentious issues. Moreover, (as the three cases above show) a failure to discuss/negotiate the issues may lead to a dismissal of any Government claims, because they are procedurally deficient and “premature.”
So what if the Contracting Officer’s Final Decision (COFD) was premature and the Government’s claim is dismissed pending a correction of the procedural defect(s)? Well, let’s say the Government was right up against the six-year statute of limitations found in the CDA. (We assume that you all know about that issue by now, as we written about it extensively.) Let’s say the COFD was issued one day before the expiration of six years. But the COFD was deficient and the Government’s claim was dismissed. Can the Government then remedy the deficient COFD and resubmit its now procedurally sound and “ripe” claim for adjudication?
We don’t think so. We think that a strict reading of the CDA and evolving case law in this area would lead the Court to conclude that it no longer had jurisdiction to hear the matter.
We think this hypothetical situation is all-too-possible, given the DCAA’s well-known backlog of incurred cost audits and the number of aged CAS noncompliances that led to DOD’s “contractor recovery initiative.” We think the Courts may have to decide this issue, sooner or later.
So this stuff matters, whether you are a small business or a major defense contractor. You’ve got to know the different between a difficult routine administrative matter and a dispute that may ripen into a claim. You’ve got to understand the procedures involved in obtaining a COFD and submitting a procedurally sound claim to the Courts for adjudication.
And if you are a DCMA Contracting Officer, we think you better think long and hard about whether you’ve fulfilled your responsibilities in this area. Whether or not you’re being held accountable for compliance, procedural defects may doom the Government’s claims in court.
Settling Disputes Part 1 of 2
This is a topic that’s been much on the mind lately. We’ve alluded to the issue—almost as a throw-away—in several recent blog articles. It’s a complex topic so bear with us if we maunder a bit.
It’s come to our attention that Contracting Officers don’t resolve very many disputes these days. Instead, what we’ve seen is a rash of shoot-from-the-hip Contracting Officer Final Decisions (COFDs)—creating what is essentially a dare to the contractor to litigate the issue, if it thinks it can afford the time and expense to prevail in court.
We can argue about the cause of the situation. Perhaps it’s that the average CO is intimidated by DCAA and knows that if s/he ignores any audit findings, an auditor might get upset and call the DOD Inspector General. Maybe the situation is caused by the well-publicized decline of the necessary skill sets at DCMA, coupled with a decade of agency mismanagement and ineffective organizational structures. Perhaps issues are being given short shrift because the number of COs is well below the level it should be, and the resulting workload is simply too overwhelming to handle. Maybe there’s been a loss of individual CO accountability. Perhaps the issue stems from direction from Fort Lee to quickly “disposition” complex issues so that the reporting metrics look pretty. Maybe the cause is perceived pressure from the looming six-year Statute of Limitations of the Contracts Disputes Act (CDA), leading to a situation where issuing any decision—no matter how dubious the position taken—is better than missing the filing deadline and seeing the Government’s claim thrown out of court without a hearing.
Perhaps the situation we’ve experienced is caused by all of the above reasons, plus more causative factors we can’t even guess at. Hey, it’s all speculation on our part; we don’t work for DCMA.
But whatever the cause, we think the result is undeniable. COs don’t resolve complex issues any more. They don’t negotiate DCAA audit findings (such as cost disallowances or CAS noncompliances). They don’t look to “split the baby” because getting an assured half a loaf now is no longer better than litigating for an entire loaf (plus interest), even when the probability of getting that entire loaf in a judicial award approaches zero.
No, it seems that the prevailing DCMA logic these days is to issue a COFD and let the lawyers handle the rest. In our view, too many DCMA Contracting Officers are ignoring the contractor’s side of the story, and essentially rubber-stamping DCAA audit reports. Aside from the obvious drawbacks with that approach, the problem with that lack of use of “independent business judgment” is leading inexorably to a tsunami of litigation over at the Armed Services Board of Contract Appeals (ASBCA) and the Court of Federal Claims (COFC). Those government lawyers are going to get spread awfully thin trying to handle all the looming contract-related litigation, in our opinion. And while it’s undeniably good news for external counsel, the shareholders of government contractors are going to be seeing some large legal expenses and some large balance sheet reserves in the near future, and they are going to be much less happy than the lawyers. (The contractors’ legal expenses, we should note, will almost certainly be unallowable and come out of company profits.)
Want an example of what we’re talking about? See our article(s) on the Boeing EELV controversy. Boeing and the United Launch Alliance are suing the U.S. Government for some $385 Million (plus interest), simply because the issue had dragged on so long without resolution and the companies needed to file their claim(s) in order to “preserve the ability to recover the money” (according to a Boeing spokesperson quoted in the article to which we linked). We know of other, less public, litigation battles that are being waged at the ASBCA and at the COFC as we write this. Readers, you ain’t seen nothing yet.
This situation should not be happening, according to regulation, agency guidance, and legal precedent. Yet here we are.
As we’ve mentioned before, the FAR requires COs to attempt to settle issues before they ripen into disputes. FAR 33.204 clearly establishes the policy of the U.S. Government thusly—
The Government’s policy is to try to resolve all contractual issues in controversy by mutual agreement at the contracting officer’s level. Reasonable efforts should be made to resolve controversies prior to the submission of a claim. Agencies are encouraged to use ADR procedures to the maximum extent practicable.
Clearly, too many DCMA Contracting Officers are violating this policy and nobody is holding them accountable as individuals. Clearly, DCMA as an agency is not enforcing this policy and nobody is being taken out to the woodshed. Mr. Williams ought to be ashamed that his organization is so ineffectual at resolving “contractual issues in controversy” by “mutual agreement at the contracting officer’s level,” but if nobody is making it into an issue at his level, then why should he worry about it?
Let’s propose right here and now that DCMA get its attorneys together and start tracking (if they do not already do it) the number of cases filed at the ASBCA and COFC that relate to contractual issues in controversy, as well as the number that get mutually resolved at the contracting officer’s level. Further, let’s propose that the claims that make it to the courts, and their ultimate disposition, are tracked so that the number of losers can be reported. Finally, let’s propose that the DCMA attorneys offer feedback to DCMA leadership, identifying the court cases that should never have been litigated, because they should have been mutually resolved at the contracting officer’s level, in accordance with the FAR. (We admit that last one would be more than a little subjective, but you’ve got to start somewhere.)
We think the foregoing metrics would help Mr. Williams (as well as Mr. Kendall and SECDEF Panetta and Congress) assess how well the COs are doing their jobs. If they care about such things.
It’s not as if DCMA hasn’t issued sufficient guidance to its Contracting Officers. It certainly has. They just seem to be able to ignore their guidance with impunity.
The DCMA guidance to its COs (link above) clearly states that “DCMA ACOs [Administrative Contracting Officers] and TCOs [Termination Contracting Officers] have the responsibility and authority to resolve disputes, including through the use of ADR [Alternate Dispute Resolution] methods.” Clearly, DCMA has told its contracting officers that they not only have the authority to settle issues before they end up in court, but that they also have the responsibility to do so.
So why don’t they?
And the DCMA COs aren’t failing in executing just that one particular FAR policy section; indeed, by failing to make a serious attempt to negotiate and resolve issues in controversy, they are also failing to execute that little piece of the FAR that states—
An essential consideration in every aspect of the System is maintaining the public’s trust. Not only must the System have integrity, but the actions of each member of the Team must reflect integrity, fairness, and openness. The foundation of integrity within the System is a competent, experienced, and well-trained, professional workforce. Accordingly, each member of the Team is responsible and accountable for the wise use of public resources as well as acting in a manner which maintains the public’s trust. Fairness and openness require open communication among team members, internal and external customers, and the public.
(See FAR 1.102-1(b)(1).)
If the FAR requires that “each member of the Team is responsible and accountable” for its actions, then why don’t we read about disciplinary actions being taken against those COs who fail to execute their job responsibilities in the proper manner?
Let’s also not forget this bit from FAR 1.602-2(b):”Contracting officers are responsible for ensuring … that contractors receive impartial, fair, and equitable treatment ….” When COs don’t give contractors a fair chance to tell their side of the story, and don’t even make a token attempt to negotiate audit findings, then how is that treatment either fair or equitable? If the CO’s simply rubber-stamp a DCAA audit report and attach it to a COFD, how is that action treating contractors impartially?
Answer: it’s not. And nobody in DCMA or DOD leadership seems to care. They don’t seem to care that the Federal Acquisition Regulations, as well as agency guidance, are being flouted on a routine basis.
The DCMA guidance to its COs also reinforces the need for the COs to use independent business judgment. The guidance states—
A Final Decision must represent the independent decision and determination of the ACO or TCO issuing the decision. While it may be necessary to obtain assistance from legal and other advisors (e.g., Defense Contract Audit Agency auditors, technical specialists, etc.), ACOs or TCOs are responsible for the ultimate decision and must make that decision after thoroughly reviewing all facts and recommendations.
Yes, that’s the standard. And our recent experience has been that it’s only rarely met by DCMA Contracting Officers.
In Part 2 of this topic, we’ll review some ancient ASBCA cases that discuss what happens when a Contracting Officer doesn’t do his/her job properly.
(Hat-tip to Bob Dourandish of Quimba Software for the FAR references.)
|
DOD Accelerates Small Business Subcontractor Payment Acceleration
 We shall endeavor to be brief. Pithy, even.
In this article, we told readers about an OMB Memo issued on July 11, 2012. The OMB Memo directed Executive Branch agencies to temporarily (for a period of one year) accelerate payments to Prime Contractors (“to the full extent permitted by law”) so that those Prime Contractors could accelerate payments to their small business contractors. The Primes were to be paid within 15 days, so that they could pay their small business subcontractors within 15 days.
We had more to say about OMB’s direction to modify existing Prime Contracts. We noted a least one carrot and one stick in the OMB’s language. But the key thing we noted was OMB’s definition of “subcontractor”. As OMB defined the term, a “subcontractor” means any person or entity (other than the prime contractor itself) that furnishes supplies, materials, equipment, or services of any kind—either in connection with a prime contract or in connection with the provision of “general supplies” to a prime contractor or higher-tier subcontractor.
So we think that when OMB says it expects Prime Contractors to pay their small business subcontractors more quickly, they are thinking about all small business vendors, not just the actual “subcontractors” who are supporting a prime contract’s statement of work.
Let that concept percolate for a while.
But the point of this article is not to recap the previous article (though we think not enough folks actually read that article.) The point of this article is to inform you that DOD has gotten a jump on the issue. Rather than waiting for the pokey FAR Councils to issue a new contract clause for inclusion in prime contract modifications, the speed demons at the Defense Procurement and Acquisition Policy (DPAP) Directorate decided to issue a DFARS Class Deviation on August 15, 2012, for use by DCMA Contracting Officers.
The Class Deviation provided a new contract clause (entitled 52.232-99, “Providing Accelerated Payment to Small Business Subcontractors—DEVIATION,” August 2012). The clause stated—
-
Upon receipt of accelerated payments from the Government, the contractor is required to make accelerated payments to small business subcontractors to the maximum extent practicable after receipt of a proper invoice and all proper documentation from the small business subcontractor.
-
Include the substance of this clause, including this paragraph (b), in all subcontracts with small business concerns. …
We were fascinated to see the DPAP policy-makers absolutely elide the issue created by OMB’s problematic definition of “subcontractor”. Indeed, making the contract clause a “mandatory flow-down” actually undercuts the OMB definition, since the only subcontracts to which the flow-down requirement can apply are those specifically identified to a DOD Prime Contract. Any small business provider of “general supplies” will not be subject to the flow-down requirement, since the DOD does not have “privity of contract” with those general (indirect) suppliers.
We predict this issue is going to grow into a potential compliance challenge. Stay tuned for more on accelerated small business subcontractor payments.
In Memoriam: Phil Treccagnoli
The death notice for Phil Treccagnoli is short and contained all the salient facts one might expect. It told us that Philip D. Treccagnoli, of Setauket, New York, had passed away on August 14, 2012. It said that Phil was 54 years old, and that he left behind a wife (Kathleen) as well as two children and two step-children. He had three siblings. And that was pretty much that.
But that is very much not that for me, not about Phil. I want to acknowledge that Phil was one of the better people whom I’ve met in this business, and 54 was far too young for him to be taken from his family and from our small Government Accounting/Compliance community.
Did you know Phil? If not, here’s a link to a summary of his professional qualifications. Note that the summary comes from the “Practicing Law Institute,” where Phil was a member of the faculty. The summary shows that Phil had a MBA (Accounting) from Adelphi University, and that he was a member of the American Bar Association’s Section on Public Contract Law, the National Contract Management Association, and the National Defense Industrial Association. It says Phil was a Green Belt in Six Sigma. Phil was also a Partner at PwC, a member of the firm’s Forensic Services/Government Contract Services practice, and specialized in Government contracting matters. It says of Phil—
Phil's primary responsibilities at PwC include executive and Board of Director level client-facing activities, and delivering solutions to clients on complex business matters covering a variety of areas. These areas include public contract accounting, cost accounting, asset management, program and contract management, regulatory compliance, and litigation support. Phil is also a subject matter expert in government contracts, and serves clients in multiple industries including aerospace and defense, construction, industrial products, healthcare and pharmaceutical, automotive, and energy.
From reading the summary, one can see that Phil had roughly 30 years of experience—16 years in industry and 14 years in the world of “public accounting”. While in industry, Phil worked at Fairchild Republic, GEC Marconi, CAE Electronics, and Telephonics. As far as I know, those companies are all located on Long Island, where Phil spent most of his life. During his 16 years in industry, Phil held a variety of Finance and Contracts positions, which gave him a solid experience base to draw from when he joined Ernst & Young.
He worked at both EY and PwC during his tenure in the “Big 4”. Although we both worked for both firms, Phil had left EY (for PwC) before I joined their Government Contract Services practice, and so it was when I subsequently joined PwC myself (in 2005) that we first met.
Let me tell you about Phil. Like many New Yorkers, he was loud and opinionated. But his heart was the biggest thing about him. He had a constant smile and always seemed happy, despite the daily stress of the job. And more importantly, Phil was a “people person.” Now, that’s more rare than you might think, unless you’ve actually spent some time in the dog-eat-dog world of the “professional accounting” firms. Despite the constant pressures, Phil remained in good spirits and was devoted to his people. He was a fanatic about developing people and was a willing mentor to those who sought him out. And for the others, he still cared about them and had a long-term development plan for them in his back pocket, which he was going to use to nudge them in the right direction (whether they knew it or not).
When Phil made Partner at PwC, after years of grinding out client engagements and waiting for the “soundings” to percolate up to leadership, the first thing he did was call me and tell me that the next thing on his agenda was on getting me into the Partnership, so I could join him. That’s the kind of guy that Phil was. He was as generous and big-hearted as I’ve met in this business. (That I ended-up leaving PwC had nothing to do with Phil, and everything to do with my family situation.)
Phil’s other project was to get his “rising star”—Phil Koos—elevated into the Partnership. He was successful in that endeavor. I asked Mr. Koos if he’d like to say anything on this website about Mr. Treccagnoli, and this is what he sent me—
Phil Treccagnoli was a consummate professional whose experience and knowledge with government contracts was extensive. He helped so many clients over the years across various areas of government contracting making it difficult to define just one area to describe Phil's expertise. However, I think most would agree that across all the experience, knowledge and advice that Phil provided to his clients, co-workers and peers, he was considered an industry leader with regard to termination proposals. Phil constantly brought innovative ideas and strategies to his clients with regard to termination proposals which often resulted in significant recovery. Whenever a termination proposal project arose, Phil's effervescent smile always seemed to get a little bigger as he savoured the challenge of these proposals and the ability to strategize and develop methods for enhancing recovery for his clients. Where others saw the black and white of the FAR requirements associated with terminations, Phil always saw the grey and challenged it to bring new and innovative positions. I know some of Phil's greatest professional achievements were positive reactions and decisions by TCOs with regard to the proposals that Phil prepared, led and advised on throughout his career. To that end, one of the greatest moments of many in his career was when an arbitrator, a leader in the government contracting community, stated that the termination proposal Phil prepared for a subcontractor was the best he had seen in his many years of practice. For me, Phil's technical capabilities were incredible and he taught me much throughout our time working together. However, the one thing that I believe Phil may have been even greater at than government contracting was people. Phil had a core belief in people and their capabilities. He allowed those who worked with him to expand themselves, to challenge their abilities and to achieve success unconditionally while always being there to support, guide, and advise. Phil's belief in the human spirit allowed those around him to excel and achieve both personally and professionally. Phil also believed the team was always more powerful than the individual and worked each day to build the strength, cohesiveness and collaboration of his team. He allowed each of us to understand that, through the team, we could drive value and quality, augment our strengths, grow through the strengths of others and progress in our careers. Personally, this went a step further to a friendship that I will always cherish. Phil was one of those few people that you cross paths and count as a close and true friend for life. His unwavering support, steadfast commitment, and positive attitude and smile was so infectious that you could not help but smile when he was present, even on your worst day. Although Phil is no longer here, I know that for his entire team and me, his professional and life advice, leadership, knowledge and people skills will forever be present with each of us and continue to shape our lives, both professionally and personally, forever.
Yes, this is the Phil that I worked with—and counted as a friend—as well.
Another PwC Partner, Glenn Brady, also had some words about Phil that he graciously sent to me. If you don’t know Glenn, then you should know that he also has a big heart and is the epitome of a professional business advisor. Working with Glenn was one of the pleasures of my PwC tenure. Glenn offered these observations about Phil—
I worked of course with Phil from time to time, but not closely, and not for several years. … As a partner Phil was always there for me when I needed him. One specific example was when I had a significant client issue on one client that resulted in [an unplanned] continuation of an engagement, which resulted in needing a partner to step in and kick off and essentially run an engagement for another client. Phil did so without batting an eye. He had to do a fair amount of ramp up in a short amount of time and he threw himself into the project with energy and focus and creativity and the like. I believe this was fueled by his passion for client service and for the values of our partnership in how we work together and how we support our staff. I will miss Phil and his regular check ins on how my beloved Cardinals are doing as well. I only wish his beloved Yankees and my Cardinals made it to the fall classic just one time over the past 10 years or so we worked together. I am sure we would have traded tickets and seen some games together.
That two busy Partners—one of whom had not worked with Phil for several years—would take the time to write and send me the foregoing indicates just how special Phil was to many of us who worked with him.
My heart goes out to Phil’s family, who lost a husband and father too soon. And my heart goes out to Phil’s Partners, co-workers, and employees, who lost a valuable member of their team. We need more like Phil, and not less.
|