1 / 27

B2B Messaging with Suppliers and Customers Using EDI and Portals

B2B Messaging with Suppliers and Customers Using EDI and Portals. Ann Holwey, QAD. Agenda. B2B Messaging B2B Messaging Components B2B Gateway Application Gateway Supplier EDI and Portals Supply Visualization Global Variations Deployment Options Best Practices. B2B Messaging.

max
Download Presentation

B2B Messaging with Suppliers and Customers Using EDI and Portals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. B2B Messaging with Suppliers and Customers Using EDI and Portals Ann Holwey, QAD

  2. Agenda • B2B Messaging • B2B Messaging Components • B2B Gateway • Application Gateway • Supplier EDI and Portals • Supply Visualization • Global Variations • Deployment Options • Best Practices

  3. B2B Messaging B2B Integration Trends: Message Formats Alternatives Grow, EDI Standards Still Leading B2B Messaging Option “Enterprise architects should strive to create a B2B support infrastructure that is designed to take advantage of both old and new technology, as each can provide unique value in meeting the full range of external integration needs.” EDI messages estimated to be 85 – 90% B2B transaction volume Ken Vollmer, Forrester Research, Inc - July 6th 2007

  4. B2B Messaging Components • B2B Gateway • Data Delivery • Data Mapping • Examples – Gentran Integration Suite & Seeburger BIS • Application Gateway • Data Integration • Examples – EDI eCommerce • B2B Development/Support Team

  5. B2B Messaging Process Flow Application Gateway B2B Gateway AS2 B2B Message Application File(SNF) Data Integration Data Mapping QAD Apps Data Delivery Web Service OFTP

  6. B2B Gateway - Definition Business-to-Business (B2B) Gateways integrate data from back-end systems enabling information exchange across trading partners. B2B Gateways also provide a centralized point for transformation of multiple data sources through interoperability standards such as XML (Extensible Markup Language), cXML(Commerce XML) and EDI (electronic data interchange). Wikipedia - June 2008

  7. B2B Gateway – Data Delivery • Communications and Security • Legacy communication protocols (eg 3780, OFTP V1, X.400) • Internet-based communications protocols • Security certificate management • Perimeter services • Business Process Management • Event-based processes • Scheduled processes • Content-based routing • Trading Partner Management

  8. B2B Gateway – Data Mapping • Reformats B2B message to/from Application file • B2B message is flat file, EDI message or XML message • Application file could be fixed/variable flat file or XML file • Mapping requirements depend on Application Gateway • Business application data access is minimized • Very few, if any, business rules should be applied here

  9. Application Gateway (Supplier or Customer EDI) • Bridge between trading partner and internal business processes • Business rules ideally executed here • Inbound Process • Restructures trading partner messages to application document(s) • Data cross referencing • Data augmentation • Message transformation • Stores turnaround data for subsequent use in business process • Outbound Process • Restructures application document(s) to trading partner message(s) • Data cross referencing • Data augmentation • Message transformation • Retrieves turnaround data required by trading partner

  10. Supplier EDI and Portals • Traditional B2B Messaging • B2B Gateway • Application Gateway • Portal • i.e. QAD’s Supplier Visualization

  11. Supply Visualization Provide asingle unified visibility toolenablingtrading partnersto share supply chain information so they can deliver goods and services atincreased levels of serviceand atlower costs.

  12. Value of SV • Exchange accurate information between trading partners to optimize production, capacity and minimize cost • Provide real time visibility into inventory / schedule changes/shipments • Improve production and transportation utilization – Fewer expedites • Provide critical information on shipment events as they occur • Manage by Exception – Use technology to Alert to unplanned or out-of-tolerance events. • Anticipate and manage potential breakdowns in plans and schedules. • Free up valuable resources, people, cash, & capacity

  13. Global Variations – Communications • North America • Automotive • Value Added Network (VAN) • FTP over ANX • OEM Hubs (eg Honda using FTP/S) • AS2 (Aftermarket and Korean OEMs) • CPG and other verticals • VAN • AS2

  14. Global Variations – Communications • Latin America • Automotive • VAN (eg Embratel) • X.400 • Hosted B2B Gateways (Sawluz, Sintel)

  15. Global Variations – Communications • EMEA • Western Europe • Automotive • OFTP V1 via X.25 or ISDN • OFTP V1 via TCP/IP over ENX • OFTP V2 over ENX or Internet • VAN (eg GXS in France and Spain) • CPG and other verticals • AS2 • VAN

  16. Global Variations – Communications • EMEA • Eastern Europe • Automotive • OFTP V1 via X.25 or ISDN • Regional VAN and Hosted B2B Gateways • CPG and other verticals • AS2 • Regional VAN and Hosted B2B Gateways

  17. Global Variations – Communications • Asia Pacific • Australia • CPG and other verticals • AS2 • VAN • China • Automotive • AS2 • VAN and Hosted B2B Gateways (Covisint)

  18. Global Variations – B2B Messages

  19. Global Variations – Business Processes • Nota Fiscal (Brazil) • Self Billing (EMEA)

  20. Deployment Options • B2B Gateway • Global or regional instances • Clustering for resilience • Communications • Internet-based at global or regional centers • Telephony-based protocols (OFTP V1, X.400) • Regional or country specific controllers • Let VAN or Hosted B2B Gateway handle • Remote locations in emerging markets may require special consideration

  21. Deployment Options • Application Gateway • Dependent on Application deployment • Independent of B2B Gateway deployment • Global B2B Gateway/Global Application Gateway • Global B2B Gateway/Regional Application Gateways • Regional B2B Gateway/Global Application Gateway • Regional B2B Gateways/Regional Application Gateways

  22. Deployment Options • B2B Development/Support Team • Global or regional internal teams • Can be remote from B2B Gateway • Supplement with regional Hosted B2B Gateway support team • Supplement with Application Managed Services from QAD

  23. Deployment Options – Considerations • B2B Gateway • Extent of regional autonomy • System support coverage for global instance • Shift operation • Out of hours coverage • Scheduled down time • System support skills • Regional communications protocols (eg OFTP)

  24. Deployment Options – Considerations • B2B Development/Support Team • Culture • Language • Regional B2B message knowledge • Regional business process knowledge • Cost effective to maintain internal expertise ?

  25. Best Practices • B2B Gateway • Global B2B Gateway (with high availability infrastructure) • Supplement with regional Hosted B2B Gateway(s) • Application Gateway • Mirrors Application Deployment • B2B Development/Support Team • Regional Development/Support Team • Supplement (where appropriate) with • Regional Hosted B2B Gateway Support Team • Application Managed Services from QAD

  26. Questions?

  27. Thank you!

More Related