E2OPEN INC One of the typical integration challenges facing large businesses is figuring out how to simplify the way applications interact, especially when using different data formats.
In previous blogs, we introduced E2 Cloud Connectivity as the integration layer of the E2open Business Network platform. When this next generation integration product was being envisioned years ago, we knew it had to solve this integration challenge. Not only does E2open support data and process integration with our Supply Chain Network applications, we integrate with many Enterprise Applications and with the trading network via B2B standards. Deploying point solutions would create a significant proliferation of integrations.
In contrast, E2open's Cloud Connectivity Platform is built on a canonical messaging model. E2open has aligned to OAGIS standards as our message canonicals. OAGIS is a cross-industry XML standard developed by the Open Application Group (OAG) to support interoperability.
We look at it as democratizing the supply chain: brand owners can integrate with all of their supply chain partners, regardless of their data formats, processes or capabilities.
Founded in 1994, the OAGi is the only truly cross-industry business network integration standard committed to building open standards for mobile, cloud, B2B, application-to-application (A2A), and enterprise interoperability. Its members include some of the largest businesses in the world, among them Oracle, Microsoft, Boeing, Cisco, Emerson, and Land o'Lakes.
The current v10 OAG has 1,057 business object definitions under support and growing.
So what the heck is canonical messaging? A canonical data model is simply a design pattern used to communicate between different data formats. It is also an architecture decision that made good business sense for E2open, as did aligning with a cross-industry standard like OAGIS, with its strong adoption and message support across process domains and industries. This design approach allows E2open to "Productize Integration" through our network for business transactions, where the business process is orchestrated on our network.
In a nutshell, we normalize E2open applications, Enterprise Applications, and Trading Network data through the canonical messages and productized integration through the network. It is our "Universal language" for IT-related interfacing and data exchange.
The benefits of this design approach are many. At the OAG Plenary in November, one of the OAG members reviewed a significant business case tied to deployment of the OAG data model within their IT infrastructure, as part of their transformation and standardization initiatives within IT. At E2open, we've seen some of the following customer benefits vs. point solutions:
- Support of IT standardization and simplification initiatives
- Reduction in overall interface map assets under management
- Reduction in ongoing maintenance and support costs
- Reduced complexity by initiating changes in one vs. potentially many maps
- Partner network abstraction from our customer's back end application and system changes
- Out-of-the-box OAGIS Support for trading partner and/or back end systems support
I am interested in understanding how businesses have used canonical message models for their IT infrastructure and the benefits and business case drivers identified for this architectural approach. Please drop me a line to tell me your story.
|
distributed by
|
