Edi seminar - case unifeedertke

CASE: Unifeeder

EDI med BizTalk

December 2013

Thomas Berg

About Unifeeder

about me and long term relationships

About Unifeeder

25 countries

Legacy systemModern system

CustomersPorts and terminals

Customs and authorities

the solution

solution / architecture / loose coupling

Legacy system Modern system

Customers

Ports and terminals

Customs and authorities

BizTalk Server

BizTalk to the rescue

solution / architecture / loose coupling

hard coupling

Legacy system Modern system

Customers

Ports and terminals

Customs and authorities

solution / architecture / loose coupling

loose coupling

Legacy system Modern system

Customers

Ports and terminals

Customs and authorities

solution / architecture / loose coupling

Basics in inhouse architecture (canonical)

6Booking

5

Booking

Legacy systemModern system

Customer 2

IBooking

Booking Booking

Booking

Customer 3

Booking

Customer 1

Booking

Customer 4

why?

when?

how?

solution / architecture / loose coupling

Why?

Dependencies

Less work (less complexity)

Better development performance

Understand and make better analysis

solution / architecture / loose coupling

When?

support a good business proces

iformat corresponds directly to a ‘business document’

scalability is important

solution / architecture / loose coupling

How?

Describe data in a meaningful way

The iformat corresponds to your business

Do not!!

Copy a standard document to be your inhouse format

Define the format based on ” it’s easier to map”

Version 1 vs Version 3

Use XSLT mappings

• when dealing with complex mappings• when mappings are done by someome with

developer skills• The right choice for large EDI-solutions

6Booking

5

Booking

Legacy systemModern system

Customer 2

IBooking

Booking Booking

Booking

Customer 3

Booking

Customer 1

Booking

Customer 4

solution / architecture / loose coupling

Control data with conversion

Conversions

BAMDataware-

house

Cache

Conversion service

solution / architecture / loose coupling

Downsides

If you don’t get it right

Deployment

about integration projects

Integration projects

De gode EDI-projekter

Forankret i forretningen

Modenhed

Attention

Integration projects

EDI – at analysere i test?!!

Analyse Development TestGo live

Analyse Development TestGo live

Integration projects

Migreringsprojekt - ikke øje tørt

41 unikke trading partners

Estimat på 55 timer pr. trading partner

Aktuelt 30 timer pr. trading partner. 10 timer pr. dokument.

10 timer for at sætte en integration op fra første første

Integration projects

Nyt iformat

Genbrug af entiteter

Forståelsen er på plads

certifikater, obskure formater og XML uden namespaces.

det er ikke teknikken, der gør forskellen på et godt eller dårligt projekt.

-

fokus på resultatet

spørgsmål?

EDI med Microsoft BizTalk Server 2013

Tak for nu…

Thomas Berg

Mail : tbe@vertica.dk

Web : www.vertica.dk

Blog : blog.vertica.dk

: @verticadk

Workshop

Gratis EDI-workshop

Jeres virksomhed og forretning

Forretningen, organisationen, kunder og leverandører

It-setup og systemer

Eventuelle erfaringer med EDI

Jeres EDI-behov

Processer til implementering (ordrer, fakturaer mv.)

Hvilke dokumenter skal udveksles, og hvordan er flowet?

Hvordan håndteres integration til/fra backend?

Ønsker/muligheder for jeres egen involvering

EDI med BizTalk og mulige løsninger

Verticas bud på hvordan I kommer videre med BizTalk

Om Vertica-BizTalk.dk

EDI med Microsoft BizTalk Server 2013

Kort fortalt: Vi er Danmarks største leverandør af BizTalk-

løsninger med mange langvarige kunderalationer.

Ydelser: BizTalk, Azure og EDI-løsninger

Kompetencer: Rådgivning, analyse og implementering samt

drift, service og undervisning.