Monte Sano Research Corp. v. Kratos Defense & Security Solutions, Inc.

99 So. 3d 855, 33 I.E.R. Cas. (BNA) 1626, 2012 Ala. LEXIS 70, 2012 WL 1890683
CourtSupreme Court of Alabama
DecidedMay 25, 2012
Docket1101484
StatusPublished
Cited by10 cases

This text of 99 So. 3d 855 (Monte Sano Research Corp. v. Kratos Defense & Security Solutions, Inc.) is published on Counsel Stack Legal Research, covering Supreme Court of Alabama primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Monte Sano Research Corp. v. Kratos Defense & Security Solutions, Inc., 99 So. 3d 855, 33 I.E.R. Cas. (BNA) 1626, 2012 Ala. LEXIS 70, 2012 WL 1890683 (Ala. 2012).

Opinions

MAIN, Justice.

Monte Sano Research Corporation (“MSRC”), Steven L. Thornton, and Steven B. Teague appeal from a preliminary injunction entered by the Madison Circuit Court against them in an action brought by Kratos Defense & Security Solutions, Inc., a California-based aerospace and defense contractor (“Kratos Defense”); Digital Fusion, Inc. (“DFI”), an Alabama-based holding company, and Digital Fusion Solutions, Inc. (“DFSI”), a Florida corporation and a subsidiary of DFI (hereinafter referred to collectively as “Kratos”),1 alleging breach of the duty of loyalty, breach of contract, tortious interference with business and contractual relationships, and civil conspiracy. Additionally, Kratos sought injunctive relief.

MSRC was formed in 2009 to procure government subcontract work at Redstone Arsenal in Huntsville. Thornton and Teague were employees of DFI, which also engaged in government subcontract work; they became employees of Kratos when Kratos Defense merged with DFI in 2008. Kratos terminated Teague’s employment on June 23, 2011. Thornton resigned from Kratos four days later.

An explanation of the nature of government contract work is essential to an understanding of this case. The United States Army awards government contracts to service providers at Redstone Arsenal in Huntsville under what is referred to as an AMCOM Express contract.2 Pursuant to the AMCOM Express contract, entities compete within a “domain” for an award of multi-year blanket purchase agreements (“BPAs”) from the Army. There are four separately recognized contracting domains: (1) logistics; (2) programmatic; (3) technical; and (4) business and analytical. Those entities that are awarded BPAs are referred to by the Army as “prime contractors.”

Before competing for a BPA award, a prospective prime contractor assembles a BPA team, a group that -will be available to assist it in performing specific work as[858]*858signments. A BPA team includes the prospective prime contractor and its employees, subcontractors and employees of the subcontractors, and other team members. The BPA team members, including subcontractors and their employees, would be qualified in the specific domain related to the specific work assignment for which the team is competing.

An award of a BPA, however, does not guarantee that a prime contractor will receive contractual work assignments in the future. Rather, a BPA entitles a holder to bid competitively against other prime contractors for awards of specific work assignments known as “task orders.” In soliciting task-order-proposal information from prime contractors, the Army releases a task-order request for quote (“TORFQ”). In turn, prime contractors can send the TORFQ to their BPA team members to solicit information for a team response. After evaluating submitted proposals, the Army awards a task order directly to a prime contractor. The task order includes a “statement of work” or an assignment, a technical description from the Army explaining the work to be performed. Often, the task order will also be accompanied by one or more “technical instructions,” a subset of a task order, that addresses a particular area of work and specifies how the Army wants the prime contractor to perform it. Technical instructions that may more closely reflect new information or changed priorities are usually issued after a task order is awarded. The prime contractor places BPA team members alongside “technical monitors,” government personnel who monitor the progress and the performance of government contracts, to perform the assigned work. The subcontractor or team member is paid for its time on the specific task through the prime contractor.

The technical monitors seek input from subcontractors and other team members working in their areas. They solicit from task-team members a rough order of magnitude (“ROM”). A ROM, which is similar to a budget, provides the technical monitor an allocation of specific labor categories, hours necessary to complete the task, and rates.

In 2005, the Army awarded Computer Science Corporation (“CSC”), a BPA within the technical domain, but not within the logistics, programmatic, or business and analytical domain. Kratos Defense was part of CSC’s BPA team and appeared to perform work only in the technical domain. The Army awarded CSC its first task order, task order 10, pursuant to the BPA in September 2005. Under task order 10, Kratos Defense obtained work assignments over the next five years, during which what the parties describe as a “merger” of Kratos Defense and DFI occurred.3 Kratos Defense received subsequent task orders under CSC’s BPA.

Also in 2005, DFI, which contracted with prime contractors to provide technical, scientific, and engineering support to the Army and which later merged with Kratos Defense, employed Thornton, who served as vice president of engineering development, and Teague, who was employed as director of weapons development and integration. Thornton supervised approximately 50 employees and oversaw approximately $9 million in revenue. Teague supervised 12 to 14 employees. At the time of this litigation, Thornton had worked in the engineering-services area of government contracts for more than 24 years and had established and maintained business associations with several technical monitors during that time. Teague had also established relationships with a number of [859]*859technical monitors during his 14 years in the industry.

Both Thornton and Teague signed various employment forms while they were employed with DFI and later with Kratos indicating that they were “at will” employees. When Kratos Defense merged with DFI in 2008, Thornton signed an “Employment and Retention Agreement” with Kra-tos that contained a “Non-Competition and Non-Interference” provision and a “Confidential Information and Non-Disclosure” provision. The noncompetition and noninterference provision, which prohibited employees from competing with Kratos, being involved with Kratos’s competitors, soliciting Kratos’s customers, and soliciting Kratos’s employees, were applicable for two years from December 24, 2008, the effective date of the agreement, which was the date of the merger of Kratos Defense and DFI. Thus, that provision expired in late December 2010. The confidential information and nondisclosure provision was not limited in time, but included restrictions concerning Kratos’s intellectual property, trade secrets, and any information concerning the business affairs of the business, and any notes, analyses, compilations, studies, summaries, and other material prepared by or for Kratos. Teague did not sign an “Employment and Retention Agreement.”

Both Thornton and Teague signed forms acknowledging receipt of the “KRATOS Handbook for Digital Fusion Employees” (“the handbook”). The handbook discussed the continuing “at-will” nature of the employment relationship of former DFI employees in three places. The handbook addressed nonsolicitation of Kratos employees and forbade any Kratos employee, for one year after the termination of his or her employment, from soliciting or encouraging any Kratos employee to leave Kratos’s employ. The handbook outlined expectations for the use of trade secrets and confidential information by Kratos’s employees.

In February 2009, Thornton and Teag-ue, who were both employed by Kratos at the time, met with Doyle McBride, a NASA consultant who had never been employed by Kratos, to discuss starting a new company to perform government contract work.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
99 So. 3d 855, 33 I.E.R. Cas. (BNA) 1626, 2012 Ala. LEXIS 70, 2012 WL 1890683, Counsel Stack Legal Research, https://law.counselstack.com/opinion/monte-sano-research-corp-v-kratos-defense-security-solutions-inc-ala-2012.