OAGIS isn’t a human-communication language, like French. It is a language for business communications. The toughest challenge in integration is semantics. Understanding each system’s vocabulary is a major obstacle. When all systems being integrated can “speak” OAGIS, integration becomes a breeze.

Hundreds of companies use our standards. Some software companies use OAGIS as their internal solution data format. OAGi’s website serves visitors worldwide. OAGIS as the world's premier enterprise canonical standard increases each day.

Here are some examples of organizations who have implemented OAGIS:

The typical approach is to select a few business processes to address first. Document the processes and in doing so, identify where data is exchanged between systems or parties. Select the OAGIS messages that meet the requirements of the data flows identified in the process documentation. Profile the OAGIS messages to meet the requirements specific to the data flow. During this process, OAGi staff and its member organizations are available to offer best practice, helpful tips, and training.

Not at all. Big companies use OAGIS not just in specific projects, but across the enterprise. Small companies use OAGIS - especially now with our improved tooling.

Governance and documentation are critical to effective enterprise-wide interoperability. OAGIS does not eliminate these requirements but makes it easier. OAGi provides governance best practices and documentation to help your company get off to a great start that is sustainable.

OAGIS does have a steep learning curve relative to other options and your company’s first integrations will take longer, however, the payoff comes after the first few integrations where the work from prior integrations can be leveraged extensively. The benefits of using OAGIS compound the more integrations your company has. Additionally, OAGIS reduces the overall risk and makes long-term project estimating more realistic, reducing time and cost.

Some people think of sophisticated as meaning complicated. OAGi thinks of sophisticated as meaning powerful and flexible. The OAGIS standard has come a long way over its 25-year history, and we’ve kept strict discipline to ensure that OAGIS has remained relatively simple and easy to use. Especially considering our incredible new tooling like Score. Sure, there’s a small learning curve at first while you learn the verbs and nouns, etc. But you’ll see a recurring pattern throughout OAGIS that is straight forward and easy to understand. OAGi also has a fantastic online resource library to help you get acquainted in record time.

Absolutely. OAGIS provides an “application area” in every message, which supports these requirements. Additionally, OAGIS has a special message with rich support for confirmation and exception information.

Not at all. Using Score, you can profile an OAGIS message which results in XML or JSON schema that is an exact fit for your shared interoperability requirements - potentially very small. OAGIS is well documented and is commonly used in B2B scenarios.

The main thing your company would learn would be patterns and best practices around enterprise integration.

Not at all. Big companies use OAGIS not just in specific projects, but across the enterprise. Small companies use OAGIS - especially now with our improved tooling.

Governance and documentation are critical to effective enterprise-wide interoperability. OAGIS does not eliminate these requirements but makes it easier. OAGi provides governance best practices and documentation to help your company get off to a great start that is sustainable.

OAGIS does have a steep learning curve relative to other options and your company’s first integrations will take longer, however, the payoff comes after the first few integrations where the work from prior integrations can be leveraged extensively. The benefits of using OAGIS compound the more integrations your company has. Additionally, OAGIS reduces the overall risk and makes long-term project estimating more realistic, reducing time and cost.

Some people think of sophisticated as meaning complicated. OAGi thinks of sophisticated as meaning powerful and flexible. The OAGIS standard has come a long way over its 25-year history, and we’ve kept strict discipline to ensure that OAGIS has remained relatively simple and easy to use. Especially considering our incredible new tooling like Score. Sure, there’s a small learning curve at first while you learn the verbs and nouns, etc. But you’ll see a recurring pattern throughout OAGIS that is straight forward and easy to understand. OAGi also has a fantastic online resource library to help you get acquainted in record time.

OAGi upgrades OAGIS according to the requirements of its members, which is a couple of minor releases per year. OAGi takes backward compatibility very seriously. Everything in minor releases is backward compatible with previous versions. It has been years since the latest major version, 10, was released. Presently there are no requirements being considered that would lead to a release that breaks backward compatibility.

OAGIS is a standard with a very broad scope. It covers most of the business message types associated with enterprise processes. That said, occasionally new processes emerge for which there is not complete OAGIS support. In those situations, OAGi is prepared to rapidly develop messages to support the requirements. Furthermore, OAGIS architecture includes a rich extensibility mechanism to address any immediate needs.

No. OAGIS serves to meet integration-requirement needs. There is nothing about OAGIS that requires more data than is necessary to meet the requirements your company identifies.

Not at all. Using Score, you can profile an OAGIS message which results in XML or JSON schema that is an exact fit for your shared interoperability requirements - potentially very small. OAGIS is well documented and is commonly used in B2B scenarios.

There is nothing about OAGIS that forces you to rework existing integrations. You can keep existing integrations in place, and introduce OAGIS at your own pace. Most organizations start using OAGIS with new integration projects and rework older ones at a later time as justified by reduced maintenance costs. You don’t have to “boil the ocean” with OAGIS. Incorporate OAGIS message types at a speed that works best for your team and your organization.

While the OAGIS standard requires commitment and discipline to use effectively, and it requires more resources to start, it requires fewer resources in the long run as your organization integrates more and more systems. Bottom line: If your company has resources to integrate systems, your company has the resources to integrate those systems using OAGIS.

OAGIS does have a steep learning curve relative to other options and your company’s first integrations will take longer, however, the payoff comes after the first few integrations where the work from prior integrations can be leveraged extensively. The benefits of using OAGIS compound the more integrations your company has. Additionally, OAGIS reduces the overall risk and makes long-term project estimating more realistic, reducing time and cost.

OAGi upgrades OAGIS according to the requirements of its members, which is a couple of minor releases per year. OAGi takes backward compatibility very seriously. Everything in minor releases is backward compatible with previous versions. It has been years since the latest major version, 10, was released. Presently there are no requirements being considered that would lead to a release that breaks backward compatibility.

OAGIS is a standard with a very broad scope. It covers most of the business message types associated with enterprise processes. That said, occasionally new processes emerge for which there is not complete OAGIS support. In those situations, OAGi is prepared to rapidly develop messages to support the requirements. Furthermore, OAGIS architecture includes a rich extensibility mechanism to address any immediate needs.

OAGi recommends using OAGIS for B2B communications, but it is certainly not a requirement. OAGi has a tool that can produce API specifications for B2B communications.

Absolutely. OAGIS provides an “application area” in every message, which supports these requirements. Additionally, OAGIS has a special message with rich support for confirmation and exception information.

OAGi upgrades OAGIS according to the requirements of its members, which is a couple of minor releases per year. OAGi takes backward compatibility very seriously. Everything in minor releases is backward compatible with previous versions. It has been years since the latest major version, 10, was released. Presently there are no requirements being considered that would lead to a release that breaks backward compatibility.

OAGIS is a standard with a very broad scope. It covers most of the business message types associated with enterprise processes. That said, occasionally new processes emerge for which there is not complete OAGIS support. In those situations, OAGi is prepared to rapidly develop messages to support the requirements. Furthermore, OAGIS architecture includes a rich extensibility mechanism to address any immediate needs.

No. OAGIS serves to meet integration-requirement needs. There is nothing about OAGIS that requires more data than is necessary to meet the requirements your company identifies.

Not at all. Using Score, you can profile an OAGIS message which results in XML or JSON schema that is an exact fit for your shared interoperability requirements - potentially very small. OAGIS is well documented and is commonly used in B2B scenarios.

There is nothing about OAGIS that forces you to rework existing integrations. You can keep existing integrations in place, and introduce OAGIS at your own pace. Most organizations start using OAGIS with new integration projects and rework older ones at a later time as justified by reduced maintenance costs. You don’t have to “boil the ocean” with OAGIS. Incorporate OAGIS message types at a speed that works best for your team and your organization.