Open Applications Group

Open Applications Group
Name	Open Applications Group
Abbreviation	OAG
Formation	1997
Type	Consortium
Headquarters	United States
Region served	Global
Focus	Application integration, interoperability, data standards

Open Applications Group is a consortium founded to develop interoperability standards for enterprise application integration and electronic business processes. It produced specifications and models intended to enable compatibility among SAP SE, Oracle Corporation, Microsoft, IBM, and other enterprise software vendors, aiming to reduce integration costs for enterprises such as General Electric, Procter & Gamble, Caterpillar Inc., and Siemens. The consortium operates within a landscape that includes standards bodies like OASIS, ISO, W3C, and industry forums such as RosettaNet, UN/CEFACT, and GS1.

History

The organization was established in the late 1990s amid a surge of interest in application interoperability alongside initiatives from CommerceNet, XML.org, BEA Systems, and Ariba. Early contributions came from technology firms including Baan Company, JD Edwards, PeopleSoft, Intentia, and SSA Global Technologies. OAG’s milestones paralleled the evolution of XML, the rise of Web services, and the development of SOAP, UDDI, and XML Schema. Throughout the 2000s the consortium engaged with projects and events involving Gartner, Forrester Research, and major systems integrators like Accenture and Deloitte. The group’s timeline intersects with regulatory and industry shifts led by entities such as HIPAA, Sarbanes-Oxley Act, and procurement platforms used by Walmart and Target Corporation.

Purpose and Scope

The consortium’s stated mission emphasized creating reusable business message standards to facilitate integration among enterprise resource planning, customer relationship management, and supply chain management solutions from vendors like Infor, Sage Group, Salesforce, and Epicor Software Corporation. By defining canonical business objects and process interfaces, it sought to complement initiatives from EBXML, AS2, and EDI networks used by companies including Amazon (company), FedEx, and UPS. Its scope covered domains such as manufacturing, logistics, finance, procurement, and human resources as practiced in corporations like Toyota Motor Corporation, Ford Motor Company, and Johnson & Johnson.

Architecture and Standards

The consortium produced specifications grounded in XML Schema and message modeling techniques compatible with SOAP and later RESTful APIs. Its framework described canonical data models, interface definitions, and mapping methodologies similar to approaches from PROV, UBL, and RosettaNet Implementation Framework. Interoperability guidance referenced patterns recognized by TOGAF practitioners and integration platforms from TIBCO Software, MuleSoft, and Dell Boomi. Technical artifacts included business object libraries, transaction patterns, event models, and message payload definitions intended to interoperate with middleware such as IBM WebSphere, Oracle Fusion Middleware, and Microsoft BizTalk Server.

Implementations and Software

Implementations of the consortium’s specifications appeared in adapters, connectors, and middleware offered by vendors like SAP SE (connectors for SAP ERP), Oracle Corporation (integration adapters), and independent integrators including Red Hat and Software AG. Systems integrators and managed service providers such as Capgemini, Cognizant, and Wipro incorporated the models into project artifacts for clients including Boeing and Lockheed Martin. Open-source projects and toolkits from communities around Apache Software Foundation projects and Eclipse Foundation tooling sometimes provided supporting parsers, mapping tools, and code generation utilities aligned with the consortium’s schemas.

Adoption and Industry Impact

Adoption varied across sectors; manufacturing and retail supply chains saw practical benefits when harmonizing interfaces among ERP and WMS solutions from vendors like Manhattan Associates and JDA Software. The consortium’s work influenced procurement automation efforts at multinational buyers such as Unilever and Nestlé, and informed integration strategies for telecommunications carriers like AT&T and Verizon Communications. Analysts at firms like Gartner and IDC referenced the consortium in studies on application integration, while standards overlaps and consolidation with organizations such as OASIS and ISO/IEC JTC 1 shaped its long-term footprint.

Governance and Organization

The consortium’s governance model combined member-driven working groups, technical committees, and liaison relationships with standards organizations including OASIS and UN/CEFACT. Membership comprised vendors, end-user companies, system integrators, and consulting firms such as Ernst & Young and KPMG. Decision-making followed patterns similar to consortia like W3C and IETF with chartered committees focusing on domain-specific message sets, maintenance, and outreach to stakeholders such as chambers of commerce and procurement consortia for corporations including IKEA and Carrefour.

Category:Consortia Category:Data interchange standards Category:Interoperability