Many companies are hard pressed to keep their B2B integration infrastructure current in today’s fast paced, constantly changing business environment. New demands from customers, limitations of the legacy IT environment, and extended implementation associated with bringing on new partners are but a few of the challenges that must be overcome.
Integration expert, Barry Sponsler, breaks down how your company can respond to these demands quickly and easily, while reducing risk and keeping costs under control.
See the recorded presentation at: http://www.extol.com/videos/webinar-drivers-and-outcomes-to-modernizing-your-integration.html
3. Constant
Change
The
ability
of
the
enterprise
to
react
quickly
to
changes
in
the
B2B
ecommerce
environment
will
directly
affect:
• Execu&on
of
growth
ini&a&ves
• Length
of
order
to
cash
cycle
• Internal
processing
costs
• Customer
sa&sfac&on
4. Constant
Change
How
can
the
enterprise:
• Embrace
changes
quickly
and
easily
• Reduce
risk
• Keep
costs
under
control
5. Common
B2B
ecommerce
change
drivers
• Outdated,
Legacy
EDI
/
Integra.on
PlaJorms
• New
Integra.on
Requirements
from
Trading
Partners
• Enterprise
Applica.on
Adop.on
/
Elimina.on
• Extended
.meframes
to
deploy
new
Trading
Partners
and
/
or
Projects
6. Legacy
EDI
/
Integra7on
PlaBorms
• Lost
revenue
due
to
missing
capabili.es
or
poor
scorecard
ra.ngs
• High
error
rates
in
order
processing,
excep.on
handling,
and
shipping
• Slow,
expensive,
and
labor-‐intensive
partner
onboarding
and
ongoing
changes
• Moun.ng
costs
of
licensing,
maintenance
and
training
7. New
Integra7on
Requirements
• Non-‐EDI
(XML
/
Flat
File
/
Spreadsheet)
data
exchange
• Web
/
Portal
based
data
sources
&
targets
• New
communica.ons
protocols
• Service
Level
Agreement
(SLA)
compliance
9. New
Partner
/
Project
Deployment
• Expansion
into
new
markets
/
geographic
areas
• New
customer
/
vendor
rela.onships
• Applica.on-‐to-‐Applica.on
integra.on
• Merger
/
Acquisi.on
10. What
now?
• Is
your
enterprise
experiencing
one
(or
more!)
B2B
ecommerce
change
drivers?
• If
yes
–
what
is
a
viable
op.on?
• Embrace
“Modern”
EDI
11. “Modern”
EDI
Classic
EDI
Modern
EDI
Document
Types
Standard
EDI
document
syntax
and
seman.cs
Standard
EDI
plus
XML,
spreadsheet,
and
flat
file
documents
Endpoint
Connec.ons
Limited
to
connec.ons
between
external
partners
and
internal
resources
“Any-‐to-‐any”
integra.on
between
partners,
applica.ons,
data,
and
cloud
services
Process
Flexibility
Simple
inbound
and
outbound
processes
End-‐to-‐end
combina.ons
of
partner-‐facing
and
internal
business
processes
Resource
Integra.on
Coded
integra.on
with
applica.ons
and
data
Rapid
integra.on
with
internal
and
external
endpoints,
without
coding
Visibility
IT-‐dependent,
“forensic”
management
and
repor.ng
Management
by
excep.on
via
alerts,
dashboards,
and
self-‐serve
repor.ng
12. Before:
Silos
of
Integra7on
Warehouse/3PL
Trading
Partners
Cloud/SaaS
ERP/TMS/WMS
Databases
Business
Intelligence/Repor@ng
14. “Modern”
EDI
plaBorm
characteris7cs
• Ease
of
use
(simple
UI,
drag
and
drop)
• Any-‐to-‐any
integra.on
(A2A,
B2B,
database
integra.on,
document
syntaxes,
communica.ons
protocols,
cloud
data)
• Model-‐driven
approach
(object
reusability,
widgets,
connectors)
• Automated
object
genera.on
(generate
objects
from
data
&
heuris.cs,
automated
mapping
assistant)
15. “Modern”
EDI
plaBorm
characteris7cs
• Expandability
&
scalability
(modular,
extensible,
and
scalable)
• Process
automa.on
&
event
management
• Business
ac.vity
monitoring
(tracking,
compliance)
• Support
for
real
.me
&
asynchronous
integra.on
16. Summary
• Change
is
coming
(or
has
already
arrived!)
to
your
B2B
ecommerce
integra.on
environment
• B2B
ecommerce
“Darwinism”
-‐
Adapt
or
die
17. Summary
• Is
the
enterprise
experiencing
any
of
the
change
drivers?
• If
yes,
must
embrace
“Modern”
EDI
• Select
an
B2B
integra.on
vendor
whose
plaJorm
supports
“Modern”
EDI
features
&
func.onality