Panel II: Transitioning SBIR: What Are the Issues for Prime Contractors?

Publication Details

Dr. Gansler, standing in temporarily for the moderator, observed that while the discussion today focused primarily on DoD and NASA—agencies that buy extensively from the SBIR companies they support—the overall National Academies study would also address the programs of the other agencies, which purchase less from their former grantees. For those agencies, he said, the committee would still have to address the question of how to better align the SBIR programs with agency activities.

Moderator: Max V. Kidalov

Senate Committee on Small Business and Entrepreneurship

Mr. Kidalov began by seconding the remarks of his Congressional predecessor, Mr. Greenwalt, to reaffirm the interest of Congress in the success of the SBIR program in general and in Phase III commercialization in particular. He introduced the panel members and suggested several themes for the discussion. He said Congress was interested in hearing about (1) the challenges and obstacles to integrating SBIR firms and SBIR products into systems and platforms developed by companies, and (2) best practices that had been observed by the panelists. He expressed interest in hearing about minority assistance programs and programs such as the mentor-protégé program, along with any lessons the SBIR program could learn from them. Finally, he encouraged more discussion of intellectual property and its role in the relationship between prime contractors and subcontractors.

Richard H. Hendel

Boeing Corporation

Mr. Hendel began with a description of Boeing Corporation. Its largest segment is the Commercial Airplanes Organization, and next in order is the Integrated Defense Systems, created several years ago out of two divisions, Military Aircraft and Missiles, and Space and Communications. The company also has a “Phantom Works” group that performs a large part of the company’s research and development and that initiates engineering technology efforts and new programs. The company manufactures many defense-oriented systems, including military aircraft, transport aircraft, bombers, weapons, space and communications, large-scale, integrated future combat systems, and advanced technology projects. The company functions in many locations in the United States and abroad; the Phantom Works organization is headquartered in St. Louis with personnel in four or five other locations. Phantom Works develops such projects as advanced systems, prototyping, the unmanned combat aerial vehicle, and many exploratory concepts.

Long Involvement with SBIR

Boeing’s involvement in SBIR dates from the years 1991-1992, before the merger between Boeing and McDonnell-Douglas; since then the joint company’s SBIR activities have been merged as well. Most of Boeing’s interaction with small firms through SBIR has occurred in the Phantom Works (PW) program, which he said had done a good job of supporting them. Boeing personnel were currently working with small businesses on 27 SBIR contracts: 4 in Phase I, 22 in Phase II, and 1 in Phase III. He estimated that over the years, Boeing had worked with nearly 200 SBIR projects. Their interaction included support in the form of follow-on with the companies and tracking the development of their technology. He also participated in national SBIR conferences, such as the recent Navy Opportunity Forum in Reston, Virginia.

He said that Boeing’s management had recently decided to increase the emphasis on SBIR. One result of this increase in emphasis, he reported, is that he had been asked two months earlier to increase the time he spends on the program from 25 to 100 percent.

Boeing’s SBIR Procedures

Boeing had developed its own SBIR procedures. One was to poll all of their technologists and researchers to review the SBIR topics at primarily four agencies—DoD, NASA, Homeland Security, and the National Science Foundation— and report on any that interested them. The office would then assemble a list of those projects and share the list with small businesses, both at conferences and by an external mailing list. The intent is to provide a point of contact at Boeing where small businesses can talk about their interests and those of Boeing, and how they might fit together. The list also helps Boeing track the technologies being developed by the companies. If asked, the company will provide a letter of interest and support for their Phase I and Phase II proposals. Sometimes the companies ask Boeing to collaborate with them, such as when they lack certain facilities or other capabilities. Companies have used the flight simulation labs, for example, and asked for other assistance via a statement of work. Such relationships are advantageous to both parties because Boeing is a potential customer for the technology being developed.

The office was trying to track all such involvement, along with the results, and issue to Boeing management a quarterly status or activities report on all interactions with small businesses, including any efforts to advance the program internally. While awareness of the SBIR program was high in the Phantom Works, Mr. Hendel wanted to expand this across the Integrated Defense Systems and its large programs, such as the F/A-18, the Joint Direct Attack Munitions, the C-17s, and the Delta launch vehicles programs. There he had found limited awareness of the SBIR program, and he wants to elicit more involvement from those programs.

He mentioned that over the years, Boeing had been involved in submitting topics to the agencies, some of which end up in agency solicitations. The best way to meet technology needs, he said, was to develop more collaboration between the programs, and between the small businesses and the large businesses. He said that both the Multi-mission Maritime Aircraft and Future Combat Systems programs were very interested in having Boeing submit potential topics for them to evaluate as candidates for solicitations.

Some Boeing Success Stories

He offered some recent Boeing success stories, which reinforced the points that SBIR is not a linear process and that success does require time. First was a Virtual Cockpit Development Program, where Microvision was the prime and Boeing the sub-contractor. They had won Phases I and II awards, an initial Phase III contract was signed in 1999, and additional awards came in 2000 and 2001 from the Army for flight-testing. One goal of the program was to replace all the gauges in helicopters with a helmet-mounted virtual cockpit, and the program had progressed to the stage of flight-testing.

Another success was the Advanced Adaptive Autopilot, an Air Force project under the Joint Direct Attack Munitions (JDAM) program. Guided Systems Technology was the prime contractor with Boeing the sub-contractor. Guided Systems worked with Phantom Works to develop this technology so that it could be incorporated into munitions.

A third success was the Cruise Missile Autonomous Routing System (CMARS) for the Tomahawk Mission Planning System. Scientific Systems Co. was the prime contractor and Boeing the sub-contractor. Boeing became involved with CMARS from its role as the mission planning system prime on the Tomahawk project, and Boeing had worked with Scientific Systems since 1999 during Phase I and II contracts. This project illustrated the non-linear aspect of development, he said, with Phase II work starting in 1999 and a Phase III award from the Navy not beginning until 2004. Great patience is sometimes required to develop long-term partnerships that pay off.

He listed a series of questions that companies need to consider when working with the SBIR program:

  • Is there a champion in the agency who can help from the beginning through insertion and implementation?
  • Does the agency really want the technology, and will it accept it after development?
  • Does the capability offer benefit at a system level?
  • Does the benefit justify the transition costs?
  • Can the prime contractor itself find champions for their programs, and also act as a champion for a technology being developed through Phase I and Phase II awards?

Advantages of a Team Approach

The funding issues discussed for agencies are relevant for the prime contractors as well, said Mr. Hendel. That is, companies need to find ways to fence off some money that can be earmarked definitely for Phase III projects. This was necessary to develop the technology not only through the Technology Readiness Levels (TRL) 4 and 5, for SBIR Phases I and II, but also to push the TRL higher to levels 7, 8, and 9 so it is ready for insertion into a prime contractor’s program. In consulting with others at Boeing, he had heard suggestions in favor of a team approach in linking the small business, the prime contractor, and the customer early in managing the technology. Such interaction can prevent the isolation of activities in silos and promote collaboration.

He said that intellectual property (IP) issues, which concern many participants in SBIR programs, had so far not been an issue for Boeing as it worked with partner companies. The small companies owned the technology, and both companies worked on it.

He ended with two points of advice. First, he noted that small businesses with successes in SBIR Phase II did not approach Boeing on a regular basis to inquire about interacting with Boeing programs. Mr. Hendel said Boeing would welcome more such approaches. Second, he noted that a technology can have a negative impact on development logistics when it is inserted inappropriately downstream. He cautioned that this could sometimes be a reason for those working at a logistical support level to resist the insertion of a technology.

Mario Ramirez

Lockheed Martin

Mr. Ramirez, who is the officer responsible for small business participation on the Joint Strike Fighter (JSF) program of Lockheed Martin, opened his presentation by describing his company as a lead systems integrator and information technology company. Lockheed Martin does 80 percent of its business with the DoD and other U.S. federal agencies, and therefore, he said, “We certainly understand the urgency of establishing a corporate strategy to leverage in the SBIR program.”

Currently, Lockheed Martin was in the process of establishing a task force to determine the current levels of SBIR involvement across its five business segments. The initial meeting was due to be held shortly, with the objective of taking the actions necessary to establish and integrate an overall SBIR strategy. He said that SBIR was an important component of the JSF program.

To make the SBIR program work, he said, data collection on new programs is critical. This process requires that the customer, the integrated product teams, and the supply chain collaborate to identify needs. These needs, in essence, determine the program’s priorities and long-range needs. A second necessary element is the annual review cycle of technology, which leads to better opportunities to provide feedback in the overall SBIR process. Feedback is critical for both development cycles and integration, he said, and this approach enables the parties involved to align with long-range strategies and technology baselines for technology development.

Understanding the Customer’s Needs

The company works with both capability roadmaps and technology roadmaps, drawn up by its engineers in partnership with the customer. This process gives Lockheed Martin a better understanding of the customer’s needs, which is critical; enables the development of program priorities; and provides opportunities to integrate SBIR technologies into overall product roadmaps. Drawing up a complete corporate technology roadmap requires that SBIR is part of the picture. The company feels that SBIR awards of significant scope should be brought into product domain working groups and incorporated into the roadmaps, as appropriate. To make successful transitions to Phase III, SBIR technologies must be integrated into an overall roadmap.

Among the examples of what is working, he mentioned the Lockheed Maritime Systems and Sensors, which had 10 years of experience working with the Navy and partnering on SBIR technologies. The company planned to take such successes into account when conducting its analysis. Boeing had also had some early successes in the Joint Strike Fighter program, including the award of a Phase III contract for $6 million. They had also done well at integrating their supply chain and had captured an award at a sub-tier supplier for $100,000 plus options. He was proud of these early successes and predicted more.

A Need to Improve Procedures

At the same time, he saw procedures that could be improved. These included a need for strategic technology portfolios to assess strategic planning and provide clarity on reform acquisition needs. Also needed was better insight into the activities of laboratories, which at times competed with one another. He said that the goal for each laboratory should be to focus on its strengths. Once those are well known, it would be possible to provide a more systematic approach to communicate and share SBIR technologies throughout the company’s engineering community—a critical step in assessing the company’s needs in relation to the topics available.

Also, technology transition must be well coordinated and must include the customer, the supply chain, and small businesses. This coordination, he said, should also include advanced technology demonstrations, which should be used to integrate multiple SBIR awards into a complex weapons system. By brokering half a dozen such topics, advanced technology demonstrations could offer significant insight into the challenges of integrating these topics into a major weapons system. Too much leveraging of the advanced technology demonstrations, however, could make programs less risk-tolerant.

Sharing Responsibility

Another key element was how best to share responsibility. Lockheed Martin’s government partners had many ongoing responsibilities, and SBIR was only one of many tasks. He said that the program could benefit by allowing a prime and/or supplier to share those responsibilities and offer the partnership as a technical point of contact.

Another issue that could be improved he called “produceability.” That is, when an SBIR technology is judged to be ready for Phase III, a concern is not only whether the technology is sufficiently mature, but also whether the small business can produce it in the quantity required to sustain production. In addition, does the small business have the capital to make the significant investment required to support production?

Finally, although Lockheed Martin had not had difficulties with SBIR partners in assigning rights to intellectual property, the entrance into a Phase III contract would be the time to review any IP issues that need to be addressed.

He reviewed several procedures that might be adapted for use in the SBIR program. One was the Navy Advanced Technology Review Board’s process to evaluate across programs to produce more effective transition of new technology. Also, he said he would like to create a version of the Joint Strike Fighter Science and Technology Advisory Board (JSTAB), a high-level S&T board that reviews programs’ priorities. The JSTAB team consists of the program office, the contractor team, and S&T organizations of every service partner. Team members review technologies and establish priorities. He said that during the upcoming business segment analysis, when the company’s five business segments will be evaluated, these two programs would be reviewed for lessons that might be applied to SBIR.

Developing a More Strategic Outlook

The fundamental challenge to improving the program, he said, was to develop a more strategic outlook. This would include a focus on long-term results, which is not always popular with the small business community. To maximize market impact, small business innovations must be aligned with the needs of government and the prime contractor; doing so can lead to more rapid and collaborative development of new technologies via technology mining. He said that Lockheed Martin had begun to regard this aligning process as an opportunity to engage more small business concerns. This process could be advanced by scouting small innovative research firms at the Navy Opportunity Forum and the DoD Phase II conference, for example, and by a greater commitment to outreach. This outreach should include the company’s small business liaison officers, the technology leads, and business development specialists to produce an integrated effort that can address the concerns of small business.

Building a Relationship between Prime Contractors and Small Businesses

Lockheed Martin also intended to build more formal business relationships with its small businesses, which are critical to successful Phase III transitions. This process must begin with joint visits to customers when both sides can discuss product discriminators, areas for further investigation and collaboration within Lockheed’s own Independent Research and Development (IR&D) and Cooperative Research and Development Agreement (CRADA) technology culture.27 These relationships would also help integrate the SBIR technologies and firms, and allow Lockheed to demonstrate its successes and build formal partnerships.

To bring a project to technological maturity, Mr. Ramirez said, it is critical to have adequate funding on hand. When a technology at a TRL of 4 or 5, for example, must be brought rapidly to a 7 or 8 for transition to the warfighter, the contractor needs to be able to deploy a financial incentive rapidly.

In summary, he said, Lockheed Martin believes that SBIR collaborations are attractive across the corporation. Initial explorations had created synergies across the five different business segments, and the SBIR task force was seeking to ensure that the necessary support elements are integrated into the strategic plan. This process was evolving, he concluded, with the objective of integrating senior management, mid-management, and operational personnel. This integration is essential because technology acquisitions decisions are made at the intersections of these levels.

John P. Waszczak

Raytheon Company

Mr. Waszczak introduced himself as director of advanced technology and SBIR-STTR at Raytheon Missile Systems (RMS), in Tucson, Arizona. He began by saying that a good deal of consensus had already been built during the conference. He said he would add to the discussion by recounting the process he had followed at Raytheon and some of the lessons that had been learned.

Raytheon’s SBIR staff had spent a good deal of time with John Williams of the Navy SBIR program and Douglas Schaffer of the Missile Defense Agency (MDA), attempting to spread the SBIR program across the other services and agencies with which Raytheon worked. He cited a substantial opportunity for not only Raytheon but also for the small business partners who stood to benefit from the $2 billion spent annually on this program.

Raytheon, which is divided into seven business units, had 80,000 employees and revenues of $20.2 billion in 2004. In addition to Raytheon Missile Systems, in Tucson, the company consisted of Space and Airborne Systems, Raytheon Aircraft, Integrated Defense Systems, Raytheon Technical Services Company, Intelligence and Information Systems, and Network Centric Systems. One of these divisions, Integrated Defense Systems (IDS), had been working formally with SBIR for about two and a half years. Raytheon Missile Systems had been involved for about one year, and the company was in the process of integrating SBIR relationships across the corporation and corporate offices.

His division, Raytheon Missile Systems, was interested in the high-tech capabilities of potential SBIR partners. RMS produces a substantial portion lot of the missile systems procured by the U.S. government and allied nations. RMS products include air-to-air systems, surface Naval air defense, and standard land-to-air missiles, and its activities are classified under areas such as ergonomics, guided projectiles, directed energy weapons, kinetic kill vehicles, advanced programs (Mr. Waszczak’s group), and land combat.

Using SBIR to Leverage Emerging Technologies

He said that Raytheon was focusing its activities on SBIR and STTR in order to leverage the technology emerging from the DoD portion of those programs (about half the total program value), as well as technology from the other SBIR agencies. SBIR is an integrated part of the company’s strategic plan to enhance supplier diversity; half to two-thirds of a typical program in which RMS participates goes to subcontracts, and more than half of the companies supplying technology to Missile Systems are “small.”28 Raytheon aligns itself with both large and small businesses to ensure that the company is well represented in strategic technologies. Small businesses, he said, represent the “technology engine” of Raytheon and of the country, so that the company needs to develop better ways of integrating SBIR/STTR technologies in order to deliver the best value to its customers.

Raytheon sees SBIR as an extension of its R&D program. In Missile Systems, the ratio of development spending to research spending is about 3:1, and a goal is to find and maintain the best balance. While the Technical Director focuses on Internal Research and Development (IRAD), Mr. Waszczak focuses mostly on outside R&D, spending about 90 percent of his time on SBIR or STTR. He is looking for more opportunities for rapid technology development and insertion by establishing long-term relationships with key small businesses and strengthening relationships with customers by helping them get the right technologies to the warfighter quickly. He said that his goal was to better coordinate the activities of the government, the small businesses, and prime contractors like Raytheon.

The Need for Integrated Roadmaps

To move toward this goal, Raytheon Missile Systems worked with the Technical Director to make sure that an engineer’s technology roadmap includes not just IRAD, but also other areas of R&D, including SBIR and STTR. “That’s very important and critical,” he said. “We’re not funding engineers just to go to IRAD or a program office unless they have an integrated plan and can show how all the pieces fit together.”

Each product line vice-president is named a “lead,” including Mr. Waszczak who is the lead for Advanced Programs. The lead’s goal is to interface effectively with the customer on technology roadmaps and to ensure that the company is working on the right technologies. He said that in expanding RMS, the product line leads provide direct links to the program managers in government. The “pull” from program managers or program executive officers is a key to technology development, as well as to effective research. The program offices are backed up by other functional groups, such as engineering. These functional groups drive the execution, based on guidance from the program offices.

This organizational system, developed within Raytheon Missile Systems and extended to Integrated Defense Systems, was now being expanded across the rest of the business units. At the corporate level, the vice-president of technology coordinated the leads that had been identified at each unit.

He then discussed “key entry points” to the SBIR process, from a prime contractor’s point of view. Raytheon emphasized the entry point of Phase II to form relationships with small firms. But being involved in Phase I and Phase II, while offering near-term opportunities, was not always sufficient, he said. The company must not only discern what is being done now, but also what is about to be done. This stage of proactive involvement he called “Phase Zero,” the time to identify the technologies and projects about to be funded, allowing the company to prepare for future opportunities as well as present ones. (See Figure 16.)

FIGURE 16. SBIR key entry points.


SBIR key entry points.

Benefits of SBIR and STTR to Raytheon

He listed many benefits available to Raytheon Missile Systems by working with the SBIR and STTR programs. Among near-term business advantages were the abilities to help program managers solve problems, reduce costs and risks, and find alternative solutions. They worked with the advanced program managers and directors for each product line—the people concerned with tomorrow’s needs rather than just today’s deliveries and customer requirements.

Other benefits came from the SBIR’s “phase transition” emphasis where RMS helped small businesses develop new components and worked with new programs to help integrate mission systems. In addition, RMS benefited by exposure to more acquisition candidates.

Box AKeys to a Prime’s Success in Leveraging SBIR Technology

  • Effective collaboration between government, small business, and prime.
  • Work with government project managers to achieve “program manager pull.”
  • Make business case through focus on strategic technologies.
  • Show how the SBIR adds value for company.
  • Communicate effectively, internally and externally.
  • Develop streamlined, user-friendly IT processes.
  • Make SBIR part of company and customer tech roadmaps.
  • Identify lead people in each product line.
  • Identify lead people for key technology areas.
  • Show how metrics flow downstream.

He showed some of the success metrics he had developed for this conference, with the key metric technology that advances to Phase III. He also focused on technologies that could be considered strategic and those on which RMS worked closely with a small business. One goal was to make sure that Raytheon’s engineer on a particular program was responsible to the program manager within a small business, that the requirements were understood, and that the partners were working in coordinated fashion. For two important metrics—SBIR/STTR technologies leveraged and support contracts from SBIR awardees—RMS goals were exceeded by more than 100 percent. Raytheon had engaged three dozen small businesses in Phase I, two dozen in Phase II and, the key metric, three dozen in “Proposals open,” the threshold to Phase III. Each transition to Phase III would mean creation of a new program and a return on Raytheon’s investment.

Raytheon Success Stories

He said there had been many “success stories” of SBIR projects in which RMS had participated. A summary included the Mark 54 Torpedo Array Nose Assembly, with Materials System, Inc.; the EKV (Exo-Atmospheric Kill Vehicle), with Vanguard Composites; guided projectiles, with Versatron (now part of General Dynamics), the Navy, and the Army; and dozens of Phase I and Phase II projects across Raytheon. All of them were considered strategic technologies, not commodity-related projects, he said, because of the limited resources available. He also mentioned the success of about half a dozen “mentor/protégé” relationships ongoing within Raytheon. Successful mentor/protégé relationships with small high-tech firms represented potential SBIR-STTR working partners for the company.

He showed a diagram of SBIR processes and interfaces he described as “a complicated spaghetti chart,” making the point that each time a prime like Raytheon works with a small business, the two partners should mutually create a roadmap to guide the development of the technology. Raytheon had developed a model that began with sharing capabilities and technology roadmaps for missile systems or concepts; then discussing with the customer the program evolution and enabling technologies required; identifying technology gaps; working with customers to develop program roadmaps; and moving the technology through the different SBIR phases, from Phase Zero to Phase III. Those SBIR awards can provide RMS with a valuable link to the overall program by providing the strategic technology enablers needed, as well as a competitive advantage or “discriminator.”

Mr. Waszczak moved to a list of major issues facing prime contractors, and some recommendations to deal with them:

  • Lack of Efficient Links to Small Businesses. Prime contractors need more forums to permit effective matchmaking across all organizations. Examples include the Navy Technology Assistance Program, PEO-IWS (Integrated Warfare Systems) matchmaking, PEO-W (Strike Weapons and Unmanned Aviation) solicitation requests, teaming with the Missile Defense Agency (MDA), and gap analysis with small businesses. Raytheon attended showcase forums like the Navy Forum and the DoD National Forum, where they had the opportunity to meet with small firms. These forums also provided benchmarks to measure how well Raytheon was doing in technology development compared to other organizations and agencies.
  • Inadequate SBIR Database for Awards and Solicitations. Unless these data are updated more often than every 6, 9, or even 12 months, opportunities to interface with contractors receiving those awards are missed. The databases should be up-to-date, searchable, and organized by common standards.
  • Cultural Differences. Prime contractors, government, and small businesses must all make culture changes to make more effective use of SBIR. Prime contractors must educate their leadership, which Raytheon is attempting to do, seek a diversity of suppliers, and overcome the “not invented here” syndrome. Engineers need to be alert for technologies being developed by others. Government agencies must involve prime contractors early, in “Phase Zero.” Agencies must also plan early for the transitions from Phase II to Phase III, and encourage and educate small businesses to contract prime contractors for support. Small businesses need to recognize that the real payoff is in Phase III, not in Phase II. This realization should increase their motivation to form partnerships with prime contractors.
  • Hesitancy on the Part of Small Businesses to Work with Prime Contractors. A leading cause of hesitancy is concerns over data rights. Mr. Waszczak said that Raytheon was working to educate small businesses about rights and to alleviate their concerns—for example, by using the proper MDA non-disclosure agreement clauses. This, he said, is essential for building trust between prime contractors and small businesses. Prime contractors also have to understand and communicate the unique provisions of SBIR, which protects the technology for the small business forever, whereas many MDA agreements last only three to five years.
  • Insufficient Cases Demonstrating Return on Investment. Prime contractors cannot yet demonstrate enough successful transitions to Phase III. To do this, they need to integrate SBIR into the normal course of business and to continue their process improvement effort.

To complement this list of major issues, he summarized some of the recommendations that flowed from Raytheon’s experience with the SBIR program:

  • Ensure Variety in the SBIR Matchmaking Process. This can be done by sharing SBIR best practices across services, emulating the Navy’s TAP Forum for matchmaking and taking other steps described above.
  • Emphasize Program Manager Pull. This is key requirement for both existing and advanced programs, and should emphasize integration of the roadmap planning by government, prime contractors, and small businesses.
  • Focus on Program and Technology Roadmaps Gaps. Again, firms must incorporate the SBIR as a key element of technology roadmaps. Timing is critical, because the primary opportunities are created by beginning early—in “Phase Zero.”
  • Beware of Too-high Expectations of Small Businesses. An early start may create unrealistic expectations, which can be costly and demoralizing. All parties need to emphasize the three-way matchmaking process.
  • Begin Early to Plan for the Transition to Phase III. This requires setting aside adequate funding.

Mr. Waszczak summarized by restating Raytheon’s commitment to the SBIR program as an “important part of our technology development process” and a key element of supplier diversity. The program helped fill “gaps” in the company’s integrated roadmaps, which was the focus of current efforts. He was also working to fit SBIR into the company’s business development toolkit, and working with engineers throughout the company to engage their participation. He closed by saying that he welcomed additional opportunities to communicate this message to others and to expand the SBIR program throughout his company

Earle Rudolph


Mr. Rudolph, the vice-president for strategy and programs at ATK Mission Research, said that he would describe the SBIR from a different perspective. He said he had worked as a government program manager, where he interacted with small businesses; at a major prime contractor; and at the Draper Laboratory. As a result, he said, “I understand the transition and the retention of intellectual property, and how that strikes fear into a small company that’s trying to protect itself.” Now, he said, he was in “a company that’s in transition.”

ATK had originated as a spin-off from Honeywell, best known initially as Thiokol, manufacturer of solid rocket motors for the Space Shuttle. ATK’s core products also included conventional munitions, but the company was now in transition and had two sets of customers. The first was the DoD, and the second was the prime DoD contractors. “I have to understand where we’re going, where they’re going, and match my technology roadmap to both of them. Then we can use programs like SBIR to find niche markets to expand into.” Planned growth markets for the company included hypersonic air-breathing systems, thermal resistant materials, advanced propulsion systems, time critical strike weapons, advanced projectiles, Advanced Anti-Radiation Guided Missile (AARGM) derivatives and directed energy. The company had made 11 acquisitions in the past five years, and hired more than 200 new PhDs.

SBIR Brings Access to High-level Expertise

Mr. Rudolph said that his company valued the SBIR program for many reasons. A growing $3 billion company, ATK is able to gain access to high-level technical expertise that would normally be beyond its reach. The company had used its acquisition process to expand or increase its technical sophistication, allowing it to create partnerships with prime contractors and with government that it would not otherwise have. The SBIR program augmented its growth strat egy by enabling it to find and engage the kinds of entrepreneurs who have been “road warriors” or technical pioneers, often out of the industrial mainstream, who discover a technology and then look for a place where they can develop it further. This was often the “phantom works” or strategic group of an existing corporation. Having such people helps ATK nurture the new technologies needed by their customers at the DoD or the major prime contractors.

Strategies for Engaging Technologies

ATK has two strategies for engaging technologies. One is partnering. For Phase I, the company engages as a subcontractor in order to understand the technologies, assist in maturing the technology to a Phase II level, and establish trust and working relationships with the small firm. For Phase II, the company becomes a major sub (49 percent) during hardware implementation, testing, and maturation of the technology to a TRL of 5 or 6. For Phase III, ATK becomes the industry partner with the government as customer, employing discretionary resources for development.

The second engagement strategy is acquisition. ATK had made strategic acquisitions that were, for them, “fairly high-risk.” The business strategy is to identify potential candidates with the SBIR process, conduct technical and business due diligence, and make a decision to buy, with the key to the decision being the retention of intellectual property. Successful examples included the AARGM, which came out of an SBIR II contract and led to purchase of the company three years ago—at considerable financial risk for a company the size of ATK. The acquisition of IP rights involved much discussion and has since resulted in case law to support the process. ATK also purchased Mission Research Corp. (MRC) in a different type of acquisition, emphasizing multiple leading-edge technologies and bringing to ATK a fast, agile and entrepreneurial technical base. Successful SBIR programs at both companies convinced each side to do the acquisition.

Advantages of SBIR …

From the company’s perspective, the SBIR program has several advantages. It allows second- and third-tier firms like ATK to have a competitive advantage. These firms can leverage their discretionary funding with technologies already identified as relevant by the customer. Firms the size of ATK do not have a large engineering base, so the SBIR forums hosted by the services offer a valued alternative to engage with engineering expertise. He cited the recent Navy forum as providing a place where small firms, prime contractors, and government customers could engage in dialogue, exchange and even active negotiations. In addition, the program provides incentives for entrepreneurs to take risks and form new alliances in order to develop innovative solutions, essentially broadening the national R&D base.

… and Impediments to Execution

The SBIR program also has impediments, he said. First, the administrative processes are too slow to allow small business owners to move their technology forward quickly. This frustrates the small business owner and, from the point of view of the prime contractor or subsystem-level contractor, unduly slows the movement to market. From ATK’s perspective, one reason that transitions fail is that the SBIR program often focuses on technical solutions to the neglect of systematic planning. He cited AARGM as a “systems answer to a systems problem,” which was why it has done well. But if the firm and the customer do not decide what the system is and how the technology fits that system, even an excellent technology may not prevent a business failure.

He closed by reiterating the real concern of the small business for its intellectual property and the retention of IP rights. The protection of rights and positions is essential, he said, both for their confidence and for the relationship with a prime. If a prime is to work with a small firm as partner and help take that partner into production, the smaller partner must retain some level of control over the intellectual property. Only when the larger partner pays attention to the needs of the smaller firm will both participants realize the potential advantages of the partnership.


Trevor O. Jones


Trevor Jones thanked the speakers for their presentations, and said he would like to raise several issues he had not yet heard discussed. First, he asked whether any agencies had thought of taking an equity interest and/or options on small businesses, or given small business partners convertible equity loans to fill the funding gap. Second, he raised the possibility of encouraging industries to create their own equivalent of the SBIR program—as commercial ventures within companies, but ventures with a short timeframe. At present, he said, the gestation period from Phase I to Phase III is often too long to maintain the interest of a commercial entity. He asked for feedback on both these possibilities.

Mr. Waszczak said that Raytheon had several times experimented with total acquisition of small businesses. He was not sure whether it had done any partial equity transactions, but that they would certainly consider such an approach. Mr. Hendel estimated that Boeing had done three total acquisitions, but did not know of any partial equity arrangements.

Making Good Use of Roadmaps

Trevor Jones then offered several impressions. First, the program managers in the agencies sometimes served a valuable function as “match-makers” between prime contractors and small firms. At other times, the prime contractors with technology needs might be the matchmakers, finding a capable small business to take to the program managers.

Mr. Waszczak said that he has shared some very good exchanges about technology with program offices and Program Executive Office groups. They had then taken the further step of comparing technology roadmaps with that of their primary small businesses to make sure that all three of the organizations were in synch.

Mr. Hendel said that Boeing also used technology roadmaps to track the firm’s projects and needs and set priorities for the coming year. He said he knew from his experience with the Multi-Mission Maritime Aircraft Program that programs in his organization worked closely to identify technology needs and topics that could become SBIR projects.

Mr. Ramirez said that Lockheed and JSF integrated small business concerns into their overall roadmapping process, opening significant opportunities to SBIR awards.

Trevor Jones asked if a subcontractor to an SBIR award winner who has an idea and a product can ultimately become the contractor who sells that product to the agency. In some cases, their work will result in a production product—especially when that organization is the sole source for the procurement. Mr. Williams responded that the Navy had done so with one SBIR company. After the small firm completed Phase II work, the Navy formed a partnership with the firm, which then developed and sold the product on a sole-source contract. He said the Navy’s database had been reviewed and searched for companies to which the Navy had awarded contracts or some type of work. It was not easy to identify all firms in the database that had done SBIR-related work, but the number of such firms appeared to be large.

Trevor Jones also asked about first supporting development of a technology to the stage of commercialization, then issuing a request for proposals to learn whether other competitive technologies existed. Mr. Waszczak said that Raytheon, after working with a small business, usually would know that their technology was the best, most cost-effective solution. At the same time, the company would indeed continue to test the marketplace to be sure that this was true.


Mr. Kidalov then invited discussion from the panel members.

Incentives for Contracting with SBIR Firms

Mr. Kidalov said he had heard that even inside a large company SBIR firms needed a champion, a corporate strategy, and incentives for the company to continue using SBIR firms, even beyond the competitive advantages they provide. He asked whether or not the panelists saw value in a system that would allow for recognition of efforts to contract with SBIR firms, perhaps from Congress and the agencies.

Mr. Hendel said that when the agencies award contracts to prime contractors, incentives are built into the contracts. He said it should be possible to offer the prime contractors similar incentives for working with SBIR contractors or development projects.

Mr. Ramirez said that incentives are critical to technology transitions, and would stimulate additional competition and more SBIR-type technologies and companies.

Mr. Waszczak said that for Raytheon an important incentive would be to streamline and otherwise optimize the SBIR process, which would ensure the development of many technologies needed for the long term. A second incentive would be assurance that customers have realistic plans to support the transition from Phase II to Phase III. Third, companies all have requirements to work with small and disadvantaged businesses, and SBIR relationships would help meet those goals.

Mr. Rudolph pointed out that individual business units, like agency program managers, need to see value in what they do, and dislike the risk of new technologies or small companies without a track record. They need incentives and other encouragement to take these risks.

Mr. Waszczak repeated from his presentation that metrics are important in any aspect of the business, including measurements across the industry and across the SBIR process. Such metrics might be specific goals for industry, or a more general goal to take SBIR technologies into Phase III.

John Williams of the Navy SBIR program reminded participants of the importance of having and implementing incentive and risk-reduction strategies. The DoD, he said, has been promoting spiral development, technology insertion, and similar steps, but he found that funding for technology insertion work was often deleted from acquisition programs when overall program funding is constrained, since both prime contractors and DoD acquisition managers are risk adverse— and new technologies are inherently risky. He asked two sets of questions:

  • Should the review committee recommend that DoD acquisition programs set aside money to perform technology insertion work?
  • How can the DoD measure prime contractors’ Phase III subcontracting activity with SBIR firms, how should the DoD create incentives for this activity, how is technology assessment (“due diligence”) paid for, and how does the DoD ensure that SBIR insertion work is properly budgeted and what steps can be taken to protect those funds?

How to Finance Phase III

Mr. Waszczak addressed the question of how the government should provide funding to help SBIR firms make the transition from Phase II to III. He advised against tapping the fund of set-aside money, preferring to have program managers realize the value of SBIR activities. Steps to encourage acceptance include basic education about how small businesses can be technology engines for important technologies. Managers also need to realize that it can take three or four years to bring new value, unless a project is on a fast track, and that not all SBIR firms will make it into Phase III. Once managers do see the added value of the program, he suggested, the transition process would begin to take care of itself.

The Need to Educate Program Managers about SBIR

Mr. Rudolph agreed on the importance of articulating the value of SBIR to the program office and the Program Executive Office. A small company cannot be expected to do this, because it is focused on developing and explaining the technological aspect of its work. He had found it useful to sit down with the technical staff and show them how a technology would be used, which helps the staff to develop the right technology. This, in turn, leads to the buy-in of the program managers and the program executive officers.

Mr. Hendel agreed that education for program managers was needed, so that they see the need for the SBIR program and understand how it can improve performance and lower cost. Only then will they develop pools of money that could be utilized on a regular basis for Phase III awards from a prime. He called it “an education process by the government to us, and by us internally, and when we get to a certain point, the processes all fall into place and happen naturally.”

A Changing Role for Prime Contractors?

Dick Reyes, president of a small technology company, raised the question of changing the environment that had made it possible for the large prime contractors to dominate his market space. He recalled that in 2003, the top 100 DoD firms had 89.9 percent of the total federal R&D budget, with Boeing and Lockheed Martin together accounting for more than half. He asked the group whether they thought it would be desirable and possible to change the contractor environment, or whether this would be blocked by the large prime contractors in their desire to dominate the marketplace. Or, is it the responsibility of the DoD to bring about change? Why would the prime contractors change unless the government forced them to change?

Mr. Waszczak said the SBIR program was part of a larger cultural change affecting all three entities—the government, the prime contractors, and small businesses. He said that for most companies, the future would bring more horizontal versus vertical integration. The prime contractors were getting out of the business of building and designing everything. Two-thirds of their costs were now going out to suppliers, and because half of those suppliers were small businesses, the prime contractors were motivated to take advantage of that technology engine and work with them. “We don’t see you as competition 95 percent of the time,” he said. “We see you as enabling technology to allow us to bring the total system to the government.”

Mr. Rudolph added that five years ago, Lockheed, Boeing, Raytheon, ATK, and others would not have gathered as they had today to discuss how better to deal with SBIR and small business. Such a dialogue would not have occurred, or it would have occurred only at a governmental level. In addition, he said, having been a supplier to the larger prime contractors, “I can tell you they’re interested in diversifying their supplier base so that one single supplier does not become the single point of failure. I work mightily to get around that attitude, like you do.”



The Department of Defense IR&D Program is designed to promote communications between the DoD and industry to increase the effectiveness of independent research and development activities and to ensure effective use of IR&D accomplishments to meet defense needs.

A Cooperative Research and Development Agreement (CRADA) is a written agreement between a private company and a government agency to work together on a project. Created as a result of the Stevenson-Wydler Technology Innovation Act of 1980, as amended by the Federal Technology Transfer Act of 1986, a CRADA allows the Federal government and non-Federal partners to optimize their resources, share technical expertise in a protected environment, share intellectual property emerging from the effort, and speed the commercialization of federally developed technology.


The Small Business Administration defines a small business as a business employing fewer than 500 people.