In 2022, our team began to think seriously about a gap between what technology made possible and what organizations could put to use. Data, automation, and increasingly capable software offered new ways to understand operations and solve difficult problems. But the existence of a tool did not mean an organization had the resources, expertise, or practical means to benefit from it.
We were particularly interested in the industries that communities depend on every day: the work of moving goods, providing energy, maintaining communications, and keeping essential infrastructure operating. In these settings, an idea has to survive contact with existing equipment, limited budgets, and the responsibilities of the people doing the work. A technically impressive solution can still be the wrong solution if an organization cannot adopt it, maintain it, or trust it.
That gap helped shape the purpose of Big Bear Associates. We wanted to create a place where ideas could receive sustained attention: where a difficult problem could be understood, a possible solution developed, and its usefulness tested before asking others to depend on it. We saw value in giving promising work room to mature, including work whose importance might be easier to recognize on a factory floor or in an operating facility than in a product demonstration.
We also wanted to help organizations make better use of what they already had. Progress should not always require more equipment, a larger budget, or another layer of software. It can come from reducing avoidable work, using capacity more effectively, and finding new value in existing infrastructure.
BBA exists to pursue this work as an independent technology incubator. Our mission is to modernize legacy infrastructure so essential services and industries can do more with the resources available to them and improve the quality of life of the communities they serve. We want to help organizations participate in an increasingly connected economy on terms they can sustain.
Capability that fits the work
We believe access to useful engineering capability should extend beyond organizations with the largest technology budgets. An organization should be able to explore a worthwhile idea without assuming that it must first replace its entire operation or assemble a large internal development team.
Affordability matters, but accessibility also depends on the effort required to adopt a solution and the responsibility of keeping it useful. A lower purchase price does little good if the result creates work that nobody has the time or expertise to manage. We want to develop capabilities whose requirements make sense for the people expected to use them.
The importance of adoption support remains visible today. In September 2026, NIST announced more than $30 million for 12 manufacturing-extension centers to help small and medium-sized manufacturers adopt advanced technologies, including AI, robotics, and automation.[1] BBA is not alone in recognizing the need. Our interest is in contributing through focused engineering and the development of ideas that deserve further work.
We are drawn to manufacturing and logistics, and to the networks behind energy, water, gas, and telecommunications. Their value is tangible: goods reach people, homes have running water and power, and businesses stay connected. Those consequences are why we want to work on their problems, even when the work attracts little attention outside the operation itself.
Understand before deciding what to build
Understanding begins with the operation as it is. We want to learn how work gets done, where information becomes difficult to use, and which decisions could improve with better support. The people responsible for the work have knowledge that a technical specification alone cannot provide.
Some constraints must be respected. Safety requirements, physical limits, and service obligations cannot be wished away. Other constraints may reflect a workaround that became routine or a decision made when different capabilities were available. Part of understanding is learning to distinguish between the two.
We want the problem to determine the solution. Sometimes that will mean extending what already works. Sometimes replacement will be justified. The choice should follow from the capability needed and the cost and risk of achieving it.
Give ideas room to mature
An incubator gives us a structure for pursuing that approach. We want to bring operational knowledge and engineering disciplines together, develop an idea far enough to test it, and revise it when the evidence challenges our assumptions.
A prototype can show that something is technically possible. Further development must establish whether it is useful, how it behaves when conditions change, and what it asks of the people maintaining it. We intend to judge promising ideas by those practical questions rather than by the polish of an early demonstration.
Recent Manufacturing Dive reporting from IMTS captures this distinction. Pinaxis's Sven Diedrich describes the continuing work of administering an application, investigating recurring exceptions, training employees, and improving a system after automation is introduced.[2] Those responsibilities belong in the design from the beginning.
Our ambition is to grow the strongest work into ventures of their own when the evidence supports it. Other ideas may be more useful as shared methods, tools, or lessons. An idea does not have to become a BBA product to make the effort worthwhile.
Steward what becomes useful
Stewardship means considering what happens after the first problem is solved. We want useful capabilities to remain understandable and supportable, and to improve as the people using them learn more. Carrying work forward also means recognizing when it needs to change, when its limits have been reached, or when it should be retired.
We also want to make better use of the investment already present in an operation. Equipment, infrastructure, and the knowledge of experienced people should not be discarded simply because a newer option exists. Where they remain useful, building on them can leave more capacity for the problems that genuinely require something new.
Doing more with less is a practical design aim. It might mean avoiding repeated work, reducing material losses, or helping an operation meet the same need with less energy. These are possibilities to test, not benefits to assume. A solution that improves one task but creates a larger maintenance burden elsewhere may leave the organization worse off.
We intend to judge improvement by what it delivers and what it asks of the operation in return. That includes the effort to keep it running, the resources it uses, and whether it leaves people better able to handle the next problem.
The work we choose
BBA is built around a conviction: difficult problems in essential industries deserve the attention needed to turn a promising idea into a useful capability. We choose work for its consequences in the operation and its value to the people who depend on it. That requires the discipline to understand a problem, challenge assumptions, and stay with an idea through testing and refinement.
Our ambition is to develop capabilities that organizations can put to work and build upon. We welcome focused collaborations with people who know their operations and are willing to question how they could work better. Through our Insights, we also want to share reasoning and ideas that others can take forward independently. The value of that work can extend beyond what BBA builds itself.
We created BBA to give this work a place to develop and mature. Its purpose is to connect engineering possibility with operational need, so the organizations doing essential work can make better decisions, use what they have more effectively, and pursue capabilities previously beyond their reach.
Sources
- NIST awards more than $30 million for MEP centers — NIST.
- Four pillars of automation — Manufacturing Dive.