Birth of Chimera

I The Problem — Why Chimera Exists

The Mission

MIE's mission: get advanced capabilities into the field in hours, not years.

The central obstacle to that mission is the monolithic coupling between hardware and software in the embedded multicomputer platforms that implement defense and intelligence capabilities. When a mission requirement changes, the traditional answer has been to acquire a new system or contract with a system vendor to change the hardware — triggering a new program, new integration cycle, new qualification, new deployment. That path takes years.

The solution is to field defense systems on embedded multicomputer platforms that are modular and extensible, and to include software infrastructure to accept hardware and software updates that add new capabilities without changing the core platform design. This requires open standards defining hardware, network, and software interfaces — but standards are not sufficient. The gap has been a market of modular hardware components with pre-integrated software implementing the platform infrastructure for integrating new capabilities nearer the deployment space.

Build the right platform once. Update it as the mission evolves.

The Role of MOSA

The Modular Open Systems Approach (MOSA) is the Department of Defense framework for achieving this goal. It defines open interfaces, modularity standards, and interoperability frameworks that — if implemented — would allow components from different vendors, different programs, and different generations to work together in a modular, updateable platform. The relevant standards and frameworks include:

• SOSA®Sensor Open Systems Architecture
• CHILCommon Hardware Integration Layer — network management
• CMOSSC5ISR/EW Modular Open Suite of Standards
• MORAModular Open RF Architecture
• VICTORYVehicular Integration for C4ISR/EW Interoperability
• FACE®Future Airborne Capabilities Environment
• AMS-GRAAirborne Mission Systems Ground Reference Architecture
• VITA 65Open VPX — form factor, backplane, connector standards
• VITA 46.11Hardware management standards for VITA 65
• VITA 100Next-generation form factor, backplane, connector standards
• VITA 100.20Next-generation system management for embedded multicomputers

The Gap

MOSA is a promise, not a solution. It is a framework for organizing acquisition programs to leverage a collection of standards for engineering and procuring modular systems. It does not implement the hardware and software products that realize modular components with open interfaces. It does not provide tools to operate, monitor, and manage a MOSA platform in the field. It does not provide the methods or tools necessary to verify that a component not only conforms, but is usable in real systems. And it does not universally provide formal models to help engineers reason about how standards fit together.

The gap between “MOSA is the approach” and “MOSA is running in the field” is wide. Programs need to see modular components on the market, ready to operate in the real world, before committing to adoption — while providers need to see a return on investment before developing real products. That is where realization of MOSA stalls: programs perceive risk without proven and fielded products, and products aren't developed and proven without investment. Systems continue to be deployed with narrow capabilities and limited extensibility. Time remains the barrier.

Chimera is the delivery mechanism for MOSA — closing the gap between the MOSA approach and MOSA realization, reducing years to hours.

II The Mythology — Why Chimera?

The Origin of the Name

In Greek mythology, the Chimera was a fire-breathing creature composed of parts from three separate animals — the head of a lion, the body of a goat, the tail of a serpent. It was not weakened by its mixed heritage. It was more powerful because of it. Each part contributed a capability the others lacked: the lion's force, the goat's endurance, the serpent's reach.

The Chimera platform takes its name from exactly this principle. MOSA standards come from different communities, different domains, different services, different DNA: SOSA from the sensor world, CHIL from naval airborne mission computers, MORA from Army RF domains, VICTORY from ground vehicles, FACE from avionics software, AMS-GRA from Air Force airborne platforms. Each framework addresses part of the modularity problem. None of them, alone, delivers an integrated solution.

Chimera allows them to be fused to form system solutions. Likewise, MIE's own capabilities in embedded software, user interfaces, test, modeling, and software-hardware integration are combined to form Chimera — a single organism that is stronger than any of its parts.

The Five Parts of the Organism

The chimera / Naming Convention

Each sub-product carries the chimera /prefix — rendered in lowercase monospace before its own name. This convention signals family membership while preserving each product's distinct identity. Just as the mythological Chimera's parts retained their own nature while serving the whole, each Chimera product retains its own character, color, and focus within the unified platform.

• chimera / VULCAN
• chimera / MOSAIC
• chimera / MTAi
• chimera / ROSETTA
• chimera / MOSA Dev Kit

III The Products — Five Capabilities, One Platform

Chimera provides the capabilities that make MOSA real: resilient embedded software, enlightening user interfaces tailored for key use cases, models for defining and analyzing systems before building, tests to prove the suitability of components and systems, and a physical toolkit that hosts the software and tools to deliver MOSA solutions.