E2OPEN INC In my last blog post, I discussed the benefits of canonical messaging in terms of how it enables applications to "talk" to one another, particularly when using different data formats. Overcoming this communicability challenge among applications is a milestone, but it's not the only challenge to consider when looking at B2B integration.
When thinking about B2B integration, it's safe to say that most typically have a good understanding of the nitty-gritty components of the technical solution that's required, such as data transformation, protocol mediation, transaction visibility, and partner configuration UI.
But while there's a general agreement on the "what," the "how" of B2B integration can vary widely. In many cases, when deploying a platform on premise, companies leverage their existing IT staff to deploy the IT infrastructure and then license the integration software that supports the desired integration patterns with available resources, who may also be the resources who onboard the community on to the platform. However, deploying, operating, and supporting the integration infrastructure internally in this manner can be time-consuming and expensive, as the solutions are typically point solutions with tightly-coupled integration between source and target systems.
But in the SaaS world, it's a different ballgame entirely, as integration can be delivered as a service, and businesses can benefit from the provider's services expertise and scale to support onboarding programs. When evaluating the overall total cost of ownership, it's important to remember that:
- The software is just a small part of the cost of the overall solution, and
- Maintaining the trading network connections over time can be a costly endeavor, as the graphic below illustrates.
Instead, an integration solution should be focused on collecting and delivering timely operational and transactional data to run the business. Additionally, the integration solution should enable an agile enterprise, as opposed to handcuffing the business because of lack of resources or capability. All too often, I have seen the misalignment between business and IT in business programs where collaboration is required, but the people and processes to onboard are not available.
This is precisely where solutions like E2open's can help, through the deployment of technology, such as E2 Cloud Connectivity, and reuse of network content required for multi-enterprise process integration. So, when considering an integration solution, what should be on your wish list?
To start, look for a multi-tenant SaaS platform focused on near real-time integration with industry-leading SLAs. The E2open Business Network is architected in this exact fashion and allows businesses to leverage a cloud-based integration infrastructure available as a service. Because the E2open integration platform is pure SaaS, and we deploy agile development methods within our R&D team, businesses can consume new features much more frequently in comparison to the costly, sporadic upgrades that are tied to traditional solutions. As a further benefit, businesses can gain additional value by leveraging supply chain-based canonical messages and productized maps.
To illustrate these points, consider the real-world scenario below with E2open. A buy-side purchase order object initiated from SAP (Integration A) can be mapped through E2open to a widely accepted X12 850 4010 version (Integration B). The purchase order data can also be natively consumed into the E2 Process Management layer for further collaboration, reporting, and event management (Integration C). This productized approach enables time to value for customers, as the already-developed map assets can be used within the business process choreography out-of-the-box. If customization is required, then the map assets can be drawn from the library to create map deviations to support desired data requirements.
This is just a small sampling of the processes orchestrated on the E2open Business Network. The purchase order is one transaction within a broader buy-side procurement process. Most (if not all) of the discrete transactions within that collaborative process have modeling and map assets on the network. When a new map asset is created by the E2open product team, that asset is made immediately available to the network.
Some of the many business processes modeled on the E2open Business Network with message and map assets include:
- Order to cash
- Procure to pay
- Inventory management
- Shipping/logistics
- Forecast collaboration
- Planning and response
- Manufacturing work in process (WIP)
Additionally, if a trading partner is already connected on the E2open Business Network, that connection has the ability to be a reusable one, thus eliminating the need to set up a new connection and removing the worry about connectivity interoperability and secure data exchange.
So what does all of this mean for your business? At E2open, we strongly believe that when undertaking a multi-enterprise business process integration with your trading network, the leveraging and reuse of integration assets on the network can deliver the time to business value more rapidly than traditional methods can.
In other words, it's time to stop worrying about the complexities of integration and put your technology investment to work. I'm always eager to hear about how other companies have navigated the waters of B2B integration and achieved the much sought-after rapid time to value - please share your thoughts in the comments below.
|
distributed by
|
