OMG makes the rules that let rivals work together

Consider a satellite ground station. Before scheduling software can arrange a contact, it needs to know where an antenna is, when it is available and what radio frequencies it supports. In its April 2026 announcement of a proposed standard called SCARS, the Object Management Group described a surprisingly ordinary obstacle: much of that information still gets entered by hand. Space has a typing problem.

This is the territory OMG occupies. Between two systems sits an unfinished agreement. A field has a different meaning. A model cannot travel cleanly. An interface needs another adapter. OMG brings organizations together to write the shared specifications that make these boundaries less troublesome.

01A committee with something to ship

Founded in April 1989 by eleven companies, OMG began as a nonprofit consortium. Christopher Stone, identified as its founder, chairman and CEO in a contemporary Novell announcement, helped establish an organization whose output would be rules other companies could implement. CORBA arrived in 1991, addressing communication between distributed software objects. UML followed in 1997, giving software designers a common modeling language.

The distinction matters when placing OMG in the enterprise technology market. It develops specifications; vendors build tools and services around them. A toolmaker can support an OMG language and compete fiercely on usability, performance or support. Customers gain a shared basis for evaluating products, even when the products themselves remain quite different.

The catalog now stretches from business processes to real-time data. BPMN supplies a notation for business workflows. SysML describes complex systems. DDS addresses data distribution in distributed applications. UAF connects enterprise architecture and systems engineering. These are different jobs, held together by the same concern: how to make work intelligible beyond the tool in which it began.

02The diagrams needed a second language

For a systems engineer, a model can connect requirements, structure, behavior and verification. It lets a team examine relationships that would otherwise be scattered across documents and spreadsheets. The appeal is practical: a change to one part of a system should be traceable through the decisions that depend on it.

But sharing a modeling language did not settle every question of precision or tool interoperability. OMG’s June 2026 certification announcement explicitly describes those limitations in SysML’s predecessor. The revealing failure was at the boundary: common diagrams alone were insufficient for the model exchange engineers wanted. That is a design problem a prettier diagram cannot solve.

In July 2025, OMG announced final adoption of SysML v2, alongside its KerML foundation and a standard API and services specification. Textual and graphical representations describe the underlying model; software can query, navigate and update it through the API. The change puts machine access beside human readability.

Bill Hoffman, OMG’s chairman and CEO at the announcement, called it “the cumulative work of many OMG members.” The release credited seven years of effort. The Systems Modeling Community also described work on a reference implementation and conformance tests. Agreement had to become something implementers could exercise, inspect and check.

03Who pays for agreement?

OMG’s immediate constituency includes tool vendors, industrial users, government and academia. Its stated footprint covers 27 countries and more than 230 member organizations, although counts on its own pages vary. The users downstream include engineers designing systems, analysts describing workflows and developers connecting applications. They need implementations as well as specifications.

The business model makes participation explicit. OMG publishes specifications online and charges for organizational membership, certification and events. Its posted annual schedule lists university membership at $550, trial membership at $2,150 and contributing membership from $11,000 to $75,000, depending on revenue. Rights vary by membership level. Those prices buy a form of participation, rather than a finished engineering system.

A SysML v2 certification exam has a separate published price of $400 before applicable discounts. Tool licenses, staff training, migration and integration belong in an adopter’s budget too. A standards document cannot price those choices for every organization. Reading a specification and changing how a department works are very different purchases.

04The rivals are also in the room

OMG’s expertise combines language design, distributed computing, domain knowledge and the mechanics of consensus. Task forces develop proposals; architecture and technology committees review them; finalization and maintenance continue after adoption. Its one-organization, one-vote policy gives eligible organizations a defined voice, while membership classes determine where they can vote.

This produces some useful double roles. In 2023, Dassault Systèmes agreed to provide modeling and collaboration applications for OMG standards teams, with promotional activity from OMG in return. In March 2025, PDES, Inc. signed an agreement with OMG covering semantic interoperability, data exchange and long-term archiving. INCOSE collaborates with the Systems Modeling Community on engineering practices.

There is no single like-for-like competitor across that portfolio. Other standards bodies serve overlapping needs; proprietary interfaces, internal conventions and alternative modeling approaches also compete for adoption. OMG’s position is the shared specification around which multiple suppliers can build. The buyer still needs to check what each supplier actually implements.

The buyer still needs to check what each supplier actually implements.

05Copy the test, then scale it

A practical lesson follows from this history: choose one troublesome handoff and make it testable. For a systems team, that might mean taking a small representative model, accessing it through the standard API and checking whether another tool preserves the relationships that matter. This is an adoption tactic suggested by the evidence, rather than a promise from OMG.

It also establishes a boundary. If partners do not implement the required features, if migration loses important information, or if a small project has little need for model exchange, the investment may bring little return. Start with a measurable integration problem. Add modeling ceremony only when it helps answer that problem.

OMG itself changed context in 2025. EDM Association completed an acquisition of its assets in October, bringing the standards organization and associated communities alongside data-management programs. In June 2026, OMG launched SysML v2 certification and requested proposals for mapping IDL4 to Rust. The work keeps returning to the same task: defining the connection carefully enough that someone else can use it.