PEPPOL IBM Full Pres (Animated YouTube Version at the end)
•Als PPTX, PDF herunterladen•
3 gefällt mir•1,116 views
See also: The PEPPOL Tipping Point #NotJustPublic http://bit.ly/PEPPOL_NotJustPublic Take the handcuffs off your EDI with PEPPOL http://bit.ly/PEPPOL_EDI My IBM homepage: http://ibm.co/GerClancy
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Empfohlen
Empfohlen (20)
PEPPOL IBM Full Pres (Animated YouTube Version at the end)
- 1. © 2014 IBM Corporation From EDI to B2B Integration with PEPPOL (#NotJustPublic) Ger Clancy IBM Inside Sales Why businesses should get on board now
- 2. © 2014 IBM Corporation Agenda How PEPPOL can transform “traditional” EDI into B2B integration International eCommerce via PEPPOL PEPPOL standard documents Why PEPPOL? Contact me, Further information
- 3. © 2014 IBM Corporation Existing Infrastructure Sphere LARGE COMPANIES SME SP 3 SP 4SP 1 PEPPOL Infrastructure SP = eCommerce Service Providers Before: Trading “Silos” dictated by larger companies, with only accidental synergies Accidental Synergy SP 5 SP 2
- 4. © 2014 IBM Corporation Existing Infrastructure Sphere LARGE COMPANIES SME PEPPOL Access Points PEPPOL Infrastructure SP = eCommerce Service Providers Before: Trading “Silos” dictated by larger companies, with only accidental synergies After: All PEPPOL-enabled entities can trade with all enabled entities on PEPPOL network ANY PEPPOL Provider SP 5 NO MORE SILOS SP 1 SP 2 SP 3 SP 4 Connect Once, Communicate Everywhere! SP
- 5. © 2014 IBM Corporation Existing Infrastructure Sphere LARGE COMPANIES SME PEPPOL Access Points PEPPOL Infrastructure SP = eCommerce Service Providers Before: Trading “Silos” dictated by larger companies, with only accidental synergies After: All PEPPOL-enabled entities can trade with all enabled entities on PEPPOL network ANY PEPPOL Provider SP 5 NO MORE SILOS SP 1 SP 2 SP 3 SP 4 Connect Once, Communicate Everywhere! SP GOVT?? What if a new client appears that’s not yet PEPPOL enabled? “Legacy” EDI routings still possible while PEPPOL being set up SP 6
- 6. © 2014 IBM Corporation Existing Infrastructure Sphere LARGE COMPANIES SME PEPPOL Access Points PEPPOL Infrastructure SP = eCommerce Service Providers Before: Trading “Silos” dictated by larger companies, with only accidental synergies After: All PEPPOL-enabled entities can trade with all enabled entities on PEPPOL network ANY PEPPOL Provider SP 5 NO MORE SILOS SP 1 SP 2 SP 3 SP 4 Connect Once, Communicate Everywhere! SP GOVT What if a new client appears that’s not yet PEPPOL enabled? “Legacy” EDI routings still possible while PEPPOL being set up
- 7. © 2014 IBM Corporation Country A SP 1 LARGE COMPANY SME Existing Infrastructure SP = eCommerce Service Providers
- 8. © 2014 IBM Corporation Country A LARGE COMPANY SME SP 1 Existing Infrastructure SP 3 SP 2 SP 4 LARGE COMPANY Country B SP = eCommerce Service Providers “Closed” Online Trading Platform OR
- 9. © 2014 IBM Corporation Country A LARGE COMPANY SME PEPPOL Infrastructure LARGE COMPANY Country B SP = eCommerce Service Providers SP 5 SP 6 SP 3 PEPPOL Infrastructure ANY PEPPOL Provider Country C & D
- 10. © 2014 IBM Corporation Delivery note PEPPOL Documents Invoice Order Confirmation Purchase Order Catalogue Buyer Seller Message Level Response AS2 Security
- 11. © 2014 IBM Corporation Who to Contact? http://ibm.co/GerClancy Detailed Use Cases on why to adopt PEPPOL The PEPPOL Tipping Point #NotJustPublic YouTube PEPPOL B2B Channel: http://bit.ly/IBM_PEPPOL_Youtube Find out more:
Hinweis der Redaktion
- Hello and welcome to my presentation about why businesses should adopt the European Interoperable EDI standard named PEPPOL (Pan European Public Procurement Online) without necessarily waiting for individual country public sector to catch up. Hence my #NotJustPublic Hashtag.
- Slide 2: Our Agenda covers the steps from traditional EDI towards B2B integration as enabled by the PEPPOL standard. I also look at how PEPPOL finally turns International electronic trade into an easy concept for any business, and at the standardised electronic documents which form the basis for PEPPOL. On the final page you have the link to my IBM homepage with my contact details as well as my PEPPOL blogs which provide much deeper information than I’ll cover in this presentation
- Slide 3: This is a general view of traditional electronic and EDI trade relationships. Note the vertical silos created over time by individual large enterprises following strategic e-procurement initiatives, and effectively forcing their downstream trade partners to either adopt their chosen format, platform or technology, or risk losing the business. Any synergies from the point of view of the smaller trader are accidental, and the thing that they will fear most is another large trading partner deciding to use yet another standalone method for electronic trade. From the point of view of an individual large company shown here, they have simplified their trade and reduced costs. What they don’t necessarily take into account is that they’ve transferred their cost and complexity onto the smaller traders. All of those different trade formats terminate in the purchasing department of the smaller business who has to manage several supplier-specific solutions, login details etc in best case and in worst case individual hard-coded 1:1 connections that require careful maintenance and expensive recoding if a change is made at either end. The cloud icons represent the different kinds of eCommerce and EDI service providers, trade platforms and Value Added Networks, all of which give access electronic trade of one type or another, but which are generally relationships governed by individually negotiated contracts, with only the trading platforms offering wider trading scope. The trade-off for this is all parties involved having to join a (generally) closed trading network. Till now, a business at the end of this chain finds itself circled by spears, all pointing in, with little hope of pushing back. It is time to turn that on it’s head. As we overlay the PEPPOL network, and the smaller business becomes PEPPOL compliant, we see the blue PEPPOL Gateways or Access Points are controlled by Service Providers as in the previous view, however note the difference as the animation progresses where the all of the companies have the freedom to choose which Service Provider gives them PEPPOL access. Some retain the existing relationships, others can change if they find better service elsewhere. The vertical silos have now gone, and all of the PEPPOL connected businesses here can now trade with each other via the PEPPOL network so long as they have the Endpoint address of their new trading partner. What now if you want to trade with a new government body, or business, or they want to trade with you? They simply need to become PEPPOL compliant via an Access Point provider of their choosing. And if you want to add a new electronic trading partner NOT yet on PEPPOL, it may be that they are accessible via the legacy EDI or VANS networks, while PEPPOL is being set up. Once PEPPOL is available, the need for that Peer-to-Peer connection diminishes as we saw with the other large companies earlier.
- Slide 3: This is a general view of traditional electronic and EDI trade relationships. Note the vertical silos created over time by individual large enterprises following strategic e-procurement initiatives, and effectively forcing their downstream trade partners to either adopt their chosen format, platform or technology, or risk losing the business. Any synergies from the point of view of the smaller trader are accidental, and the thing that they will fear most is another large trading partner deciding to use yet another standalone method for electronic trade. From the point of view of an individual large company shown here, they have simplified their trade and reduced costs. What they don’t necessarily take into account is that they’ve transferred their cost and complexity onto the smaller traders. All of those different trade formats terminate in the purchasing department of the smaller business who has to manage several supplier-specific solutions, login details etc in best case and in worst case individual hard-coded 1:1 connections that require careful maintenance and expensive recoding if a change is made at either end. The cloud icons represent the different kinds of eCommerce and EDI service providers, trade platforms and Value Added Networks, all of which give access electronic trade of one type or another, but which are generally relationships governed by individually negotiated contracts, with only the trading platforms offering wider trading scope. The trade-off for this is all parties involved having to join a (generally) closed trading network. Till now, a business at the end of this chain finds itself circled by spears, all pointing in, with little hope of pushing back. It is time to turn that on it’s head. As we overlay the PEPPOL network, and the smaller business becomes PEPPOL compliant, we see the blue PEPPOL Gateways or Access Points are controlled by Service Providers as in the previous view, however note the difference as the animation progresses where the all of the companies have the freedom to choose which Service Provider gives them PEPPOL access. Some retain the existing relationships, others can change if they find better service elsewhere. The vertical silos have now gone, and all of the PEPPOL connected businesses here can now trade with each other via the PEPPOL network so long as they have the Endpoint address of their new trading partner. What now if you want to trade with a new government body, or business, or they want to trade with you? They simply need to become PEPPOL compliant via an Access Point provider of their choosing. And if you want to add a new electronic trading partner NOT yet on PEPPOL, it may be that they are accessible via the legacy EDI or VANS networks, while PEPPOL is being set up. Once PEPPOL is available, the need for that Peer-to-Peer connection diminishes as we saw with the other large companies earlier.
- Slide 3: This is a general view of traditional electronic and EDI trade relationships. Note the vertical silos created over time by individual large enterprises following strategic e-procurement initiatives, and effectively forcing their downstream trade partners to either adopt their chosen format, platform or technology, or risk losing the business. Any synergies from the point of view of the smaller trader are accidental, and the thing that they will fear most is another large trading partner deciding to use yet another standalone method for electronic trade. From the point of view of an individual large company shown here, they have simplified their trade and reduced costs. What they don’t necessarily take into account is that they’ve transferred their cost and complexity onto the smaller traders. All of those different trade formats terminate in the purchasing department of the smaller business who has to manage several supplier-specific solutions, login details etc in best case and in worst case individual hard-coded 1:1 connections that require careful maintenance and expensive recoding if a change is made at either end. The cloud icons represent the different kinds of eCommerce and EDI service providers, trade platforms and Value Added Networks, all of which give access electronic trade of one type or another, but which are generally relationships governed by individually negotiated contracts, with only the trading platforms offering wider trading scope. The trade-off for this is all parties involved having to join a (generally) closed trading network. Till now, a business at the end of this chain finds itself circled by spears, all pointing in, with little hope of pushing back. It is time to turn that on it’s head. As we overlay the PEPPOL network, and the smaller business becomes PEPPOL compliant, we see the blue PEPPOL Gateways or Access Points are controlled by Service Providers as in the previous view, however note the difference as the animation progresses where the all of the companies have the freedom to choose which Service Provider gives them PEPPOL access. Some retain the existing relationships, others can change if they find better service elsewhere. The vertical silos have now gone, and all of the PEPPOL connected businesses here can now trade with each other via the PEPPOL network so long as they have the Endpoint address of their new trading partner. What now if you want to trade with a new government body, or business, or they want to trade with you? They simply need to become PEPPOL compliant via an Access Point provider of their choosing. And if you want to add a new electronic trading partner NOT yet on PEPPOL, it may be that they are accessible via the legacy EDI or VANS networks, while PEPPOL is being set up. Once PEPPOL is available, the need for that Peer-to-Peer connection diminishes as we saw with the other large companies earlier.
- Slide 3: This is a general view of traditional electronic and EDI trade relationships. Note the vertical silos created over time by individual large enterprises following strategic e-procurement initiatives, and effectively forcing their downstream trade partners to either adopt their chosen format, platform or technology, or risk losing the business. Any synergies from the point of view of the smaller trader are accidental, and the thing that they will fear most is another large trading partner deciding to use yet another standalone method for electronic trade. From the point of view of an individual large company shown here, they have simplified their trade and reduced costs. What they don’t necessarily take into account is that they’ve transferred their cost and complexity onto the smaller traders. All of those different trade formats terminate in the purchasing department of the smaller business who has to manage several supplier-specific solutions, login details etc in best case and in worst case individual hard-coded 1:1 connections that require careful maintenance and expensive recoding if a change is made at either end. The cloud icons represent the different kinds of eCommerce and EDI service providers, trade platforms and Value Added Networks, all of which give access electronic trade of one type or another, but which are generally relationships governed by individually negotiated contracts, with only the trading platforms offering wider trading scope. The trade-off for this is all parties involved having to join a (generally) closed trading network. Till now, a business at the end of this chain finds itself circled by spears, all pointing in, with little hope of pushing back. It is time to turn that on it’s head. As we overlay the PEPPOL network, and the smaller business becomes PEPPOL compliant, we see the blue PEPPOL Gateways or Access Points are controlled by Service Providers as in the previous view, however note the difference as the animation progresses where the all of the companies have the freedom to choose which Service Provider gives them PEPPOL access. Some retain the existing relationships, others can change if they find better service elsewhere. The vertical silos have now gone, and all of the PEPPOL connected businesses here can now trade with each other via the PEPPOL network so long as they have the Endpoint address of their new trading partner. What now if you want to trade with a new government body, or business, or they want to trade with you? They simply need to become PEPPOL compliant via an Access Point provider of their choosing. And if you want to add a new electronic trading partner NOT yet on PEPPOL, it may be that they are accessible via the legacy EDI or VANS networks, while PEPPOL is being set up. Once PEPPOL is available, the need for that Peer-to-Peer connection diminishes as we saw with the other large companies earlier.
- Slide 4: Moving to the next slide, we see a common 1-1 B2B trade relationship, but what happens if you want to expand your trade internationally? Traditionally you would have had to either navigate a Daisy-Chain of Value-Added-Network providers to hopefully get your message to its destination. This was was fraught with complexity, cost and the risk of the messages not getting through. Alternatively you could sign up to a trading platform that operates across multiple countries, and offer such cross-border flexibility, but at the tradeoff of needing a closed trading network to achieve it. Only if everyone concerned has already got an individual contract with THAT trading platform can they exchange messages. PEPPOL enables wide geographical reach without dependency on an individual Service Provider. The important thing is that the trading partners at both ends gain PEPPOL access and compliance via a Service Provider of their choice. This could be via a single Access Point provider operating internationally, or via separate local providers. It just doesn’t matter. PEPPOL is about the trade, NOT about the Service Providers. But what about adding Public Sector trade in that other country? Or adding additional countries, commercial and / or public sector? It is the responsibility of the individual entity to get access to the PEPPOL Network, and after that the borders are removed. The final element on this chart loops back to the initial trade relationship in Country A. The Large Enterprise joined PEPPOL and expanded their trade across both public and private sector and in multiple countries, while still continuing to trade with their initial trading partner via the legacy system. Now that trading partner joins PEPPOL and gains access to all of the same trading partners and more. Peer to Peer is no longer needed.
- Slide 4: Moving to the next slide, we see a common 1-1 B2B trade relationship, but what happens if you want to expand your trade internationally? Traditionally you would have had to either navigate a Daisy-Chain of Value-Added-Network providers to hopefully get your message to its destination. This was was fraught with complexity, cost and the risk of the messages not getting through. Alternatively you could sign up to a trading platform that operates across multiple countries, and offer such cross-border flexibility, but at the tradeoff of needing a closed trading network to achieve it. Only if everyone concerned has already got an individual contract with THAT trading platform can they exchange messages. PEPPOL enables wide geographical reach without dependency on an individual Service Provider. The important thing is that the trading partners at both ends gain PEPPOL access and compliance via a Service Provider of their choice. This could be via a single Access Point provider operating internationally, or via separate local providers. It just doesn’t matter. PEPPOL is about the trade, NOT about the Service Providers. But what about adding Public Sector trade in that other country? Or adding additional countries, commercial and / or public sector? It is the responsibility of the individual entity to get access to the PEPPOL Network, and after that the borders are removed. The final element on this chart loops back to the initial trade relationship in Country A. The Large Enterprise joined PEPPOL and expanded their trade across both public and private sector and in multiple countries, while still continuing to trade with their initial trading partner via the legacy system. Now that trading partner joins PEPPOL and gains access to all of the same trading partners and more. Peer to Peer is no longer needed.
- Slide 4: Moving to the next slide, we see a common 1-1 B2B trade relationship, but what happens if you want to expand your trade internationally? Traditionally you would have had to either navigate a Daisy-Chain of Value-Added-Network providers to hopefully get your message to its destination. This was was fraught with complexity, cost and the risk of the messages not getting through. Alternatively you could sign up to a trading platform that operates across multiple countries, and offer such cross-border flexibility, but at the tradeoff of needing a closed trading network to achieve it. Only if everyone concerned has already got an individual contract with THAT trading platform can they exchange messages. PEPPOL enables wide geographical reach without dependency on an individual Service Provider. The important thing is that the trading partners at both ends gain PEPPOL access and compliance via a Service Provider of their choice. This could be via a single Access Point provider operating internationally, or via separate local providers. It just doesn’t matter. PEPPOL is about the trade, NOT about the Service Providers. But what about adding Public Sector trade in that other country? Or adding additional countries, commercial and / or public sector? It is the responsibility of the individual entity to get access to the PEPPOL Network, and after that the borders are removed. The final element on this chart loops back to the initial trade relationship in Country A. The Large Enterprise joined PEPPOL and expanded their trade across both public and private sector and in multiple countries, while still continuing to trade with their initial trading partner via the legacy system. Now that trading partner joins PEPPOL and gains access to all of the same trading partners and more. Peer to Peer is no longer needed.
- Slide 5: Here you can see the types of electronic message that are facilitated by PEPPOL, as well as their routings. Sellers can provide electronic catalogues of goods and services at pre-agreed terms, from which Buyers can then select their choices and use this to generate Purchase Orders. Order Confirmations can be sent back, and as the order fulfillment progresses, the Shipment Notification and Invoice can also be exchanged electronically. A key feature of PEPPOL is the Message Level Response that can act as a “read receipt” and audit trail that all sent messages have been received. AS2 Security underlies the whole series of transactions Depending on the size of organisation and their desired level of Integration, the exchange of messages portrayed here can take place flexibly between either Email Inbox, or Web Portal or ERP Integrated (eg SAP) interfaces. The degree of integration required will influence the overall cost, however the deeper the integration the more flexibility and automation possible.
- Slide 6: We’ve reached the end of the presentation. I hope you’ve found value in the topics covered and I’d be happy to provide further information and background as desired. The best way to reach me is via my IBM homepage ibm.co/GerClancy, where you can see all my contact details and if I’m online, you can Instant Message me directly from there. Thanks for your attention. I look forward to hearing from you