4. @LiaisonTech
The “Trap”
• Multiple products and processes; some overlap, some
are siloed
• Tools are complex and cannot fit more than one task
• Knowledge gaps
• Over time, companies can become rigid and brittle.
• Data synchronization headaches
• ROI goes…..
5. @LiaisonTech
Integration Solution Offerings –
ECS and Delta
• Delta is an any-to-any mapping and data translation
tool.
• ECS is a communication server supporting a wide
variety of data transfer protocols and standards.
• Delta and ECS combined provide an enterprise
application integration (EAI) solution capable of
coordinating the many diverse applications, databases
and e-commerce formats found across the enterprise.
• Delta and ECS combined provide a business to
business (B2B) solution capable of coordinating all
trading partner requirements as an extension of the
enterprise.
8. @LiaisonTech
Value Proposition
• Scalable
– The platform is powerful as a standalone server or may be
scaled out across multiple servers for load balancing and
failover.
• Sophisticated
– Delta & ECS together create a flexible integration platform to
meet typical B2B requirements and complex Enterprise
Application Integration needs.
• Simplistic
– Originally built for the SMB market, the configuration interface
and development environment is intuitive and does not require
engineer level expertise for development and support.
(read: no programming required)
9. @LiaisonTech
Translates to…
• Maximizing ROI by:
– Reducing the number of software tools needed
– Allowing common tools to be used for uncommon
implementations
– Lowering the “IQ” required to succeed where:
• IQ = Implementation Quotient
10. @LiaisonTech
Common Midsize Supplier Solution
• Typical need
‒ Onsite software for integration with mid to high level ERP
package
‒ Technical components may be developed and maintained by
Liaison, channel partner community or client
• Most customers can be served by a single server
solution
‒ Delta Engine, Delta Studio, and ECS Standard
‒ Additional servers can be added for disaster recovery or
test/development systems
11. @LiaisonTech
High Volume, Complex Clients
• Typical need
‒ Need load balancing for high volume of transactions
‒ Looking for live fail-over server capabilities
‒ Looking for segmented dev/test/production environments
‒ Need to support multiple map developers with version control,
map check-in/out and roll forward/back
• Complex client needs can be served by multi-server
systems
‒ Delta Engines, Delta Enterprise Studio(s)
‒ ECS Enterprise provides for hot-hot support
12. @LiaisonTech
Differentiation by Versatility and Flexibility
• Can be used to solve common B2B, EAI, A2A needs
• Migration projects
• Eliminate the cost of maintaining many disparate
applications, overcoming silos
• Data translation and integration in unexpected places
• When you empower the tools, they can empower you,
save time, money, errors.
• Liaison examples:
– JIRA migration
– Athena
– Company-wide reporting...
13. @LiaisonTech
JIRA Migration
• JIRA provides issue tracking and project tracking for
software development teams to improve code quality
and the speed of development
• Some of Liaison development teams using homegrown
defect tracking system. Inherited by way of acquisition
• Delta used to migrate from homegrown system to JIRA
in less than 30 days
• Project was completed by an intern with no prior Delta
mapping experience.
• Solution involved mapping from SQL Server database
to a JIRA supported XML-based scripting language
called “Jelly”
16. @LiaisonTech
• Leading generic prescription pharmaceutical distributor based in
Cincinnati, Ohio.
• Celebrating our 15th year anniversary in 2011
• Providing value and customer satisfaction, KMI has achieved the
Inc. 500 and Inc 5000 list for the past three years.
• VAWD (Verified-Accredited Wholesale Distributors)
16
About Keysource Medical
17. @LiaisonTech
Liaison ECS and Delta at Keysource Medical
• Typical install to start – Delta Studio, Delta Engine,
ECS
• 80+ “standard” EDI partners
• Vendor facing and customer facing
• Added 2nd ECS node in late 2010 for disaster recovery
and load balancing
• 1K-2K batches of data per day
• Primary integration with MAS 200 SQL
• SWK’s MAPADOC is used as “middleware” for creating
sales orders in ERP system
• EDI duties take 5-10% of weekly workload of one
person
• AS2, VAN and FTP traffic handled by ECS
18. @LiaisonTech
•Our customers were asking for EDI, but we also recognized a
need for other functionality and integrations. We wanted one
central platform to handle all scenarios.
•After implementing the first customer, we found that we could
create mappings very rapidly that provided the same type of
logging and reporting as EDI and found other unique uses for the
tools. Using the Studio, we were able to create integrations rapidly,
with no code to support and enjoy all the exception reporting of the
“standard” integrations.
18
Keysource Medical – General Problem Statement
19. @LiaisonTech
Warehouse temperature management - how can we monitor our
warehouse temperature/humidity, log the results, keep history and
notify management of a potential issue?
We have a process that queries 4 temperature sensors in our
warehouse, checking for both temperature and humidity. A file is
written to the network for each data value.
19
Pain Point/Solution #1 – Warehouse Management
20. @LiaisonTech
• ECS picks up that data file on a fixed schedule (every 2 minutes)
and logs the file.
• Delta translates the data and writes the value, filename, reading
type and time to a SQL Server database
• If the reading is outside our set parameters an exception is fired
off and management is notified via email.
• History is kept for 6 months in that table.
20
Pain Point/Solution #1 – Warehouse Management
21. @LiaisonTech
How can we improve our interaction with our parcel carriers and
“rate shop” effectively? We have all these disparate systems for
each carrier!
• Can we design something inside the ERP system where order
entry takes place?
• Can we save any time?
• Can it be done “yesterday”?
21
Pain Point/Solution #2 – Shipping Rates
22. @LiaisonTech
• Send sales order number and ship via code to ECS via HTTP.
• ECS invokes a “process map” that takes Ship Via and Sales
Order Number as input and based on code (UPS, FEDEX) calls a
web service map. This map queries the carrier and returns a dollar
figure. The dollar figure is then sent back to the originating request
(synchronously).
• Uses powerful WebServiceRequest function in Delta to make the
Web Service to the carrier
22
Pain Point/Solution #2 – Shipping Rates
24. @LiaisonTech
• We have to monitor our customers to make sure they are licensed
by the DEA to buy controlled substances. The DEA keeps a list of
1.3 million licensed dispensers, which we download weekly.
• How can we validate our customer records against our DEA
database “on the fly”? How can we automatically maintain our
database as well?
24
Pain Point/Solution #3 – Customer Compliance
25. @LiaisonTech
When a customer record is changed, a web service call is made to
ECS, where the customer data is checked against that database.
If the customer is not in the database, or has an expired license, it
will not let the customer record be changed. That customer will not
be allowed to order controlled substances from us.
25
Pain Point/Solution #3 – Customer Compliance
26. @LiaisonTech
Maps were created to run on a schedule to maintain the customer
master in the ERP system.
Each customer gets checked daily for:
• Valid DEA Registration #
• DEA License Expiration
• DEA “Schedule”
26
Pain Point/Solution #3 – Customer Compliance
27. @LiaisonTech
Depending on the results of the validation the maps do the following:
• Send a text report via email to the compliance department.
• Updates the customer record to make them compliant with our
ordering system
• Turns off that customers ability to order certain product from us.
27
Pain Point/Solution #3 – Customer Compliance
28. @LiaisonTech
Our sales people don’t really understand EDI. How can we make it
user-friendly for them and give them visibility to their EDI orders,
without giving them unnecessary tools? How can we show the
details of their order easily?
Orders go through a series of checks before we accept any items.
These include: minimum order amount, daily item limits, monthly
item limits, out of stock check, refrigerated items, etc.
28
Pain Point/Solution #4 - Ordering
29. @LiaisonTech
HTML to the rescue!
During order process, a control map is used to fire off different
maps and process - all of the logic necessary to validate an order.
Since HTML allows better control over the presentation layer, we
use it to show the information to the rep in an automated, user-
friendly method.
This is done via EDI -> text mapping, where HTML is the target.
29
Pain Point/Solution #4 - Ordering
31. @LiaisonTech
Why Delta / ECS for these projects?
• Standardized data – simple to model
• Maps are stored in Solution Manager for version control
• RAD – rapid application development
• “No code” solutions
• Automated logging / audit trail / exception reporting
31
In Summary
32. @LiaisonTech
Solutions
• Data Integration
• Data Management
• Data Security
Multinational
• Global headquarters in Atlanta
• European offices in Finland,
Netherlands, Sweden, UK
• More than 7000 customers
worldwide in over 46 countries
Visit KeySource
Medical here
For more
presentations:
Liaison Webinars
ABOUTLIAISON
32
Additional Resources
Editor's Notes
Discuss the need for flexibility and versatility in the enterprise.
B2B functions
EAI functions
Other A2A functions
Migration projects
Cost of maintaining many disparate applications, overcoming silos
Data translation and integration in unexpected places
When you empower the tools, they can empower you, save time, money, errors, etc
Give examples – (JIRA), reports,
Discuss the need for flexibility and versatility in the enterprise.
B2B functions
EAI functions
Other A2A functions
Migration projects
Cost of maintaining many disparate applications, overcoming silos
Data translation and integration in unexpected places
When you empower the tools, they can empower you, save time, money, errors, etc
Give examples – (JIRA), reports,
Discuss the need for flexibility and versatility in the enterprise.
B2B functions
EAI functions
Other A2A functions
Migration projects
Cost of maintaining many disparate applications, overcoming silos
Data translation and integration in unexpected places
When you empower the tools, they can empower you, save time, money, errors, etc
Give examples – (JIRA), reports,
Joined KMI in 3/15/2010
Delta / ECS has been an important part of the growth we’ve experienced
Cornerstone of our integration processes
ECS Enterprise (orchestration) and Delta (translation)
Does both vendor facing and customer facing
2nd node is primarily for failover, but some processes are dedicated solely to that node
No formal EDI “team” (yet).
Rapid development makes for quick on-ramping
SWK – top flight integration solution for MAS 200. More desirable than other methods of entering data into the ERP
EDI -> Flat File, EDI -> Database
Any to any mapping comes in play.
Powerful database connections, query writing
DB -> DB
4 temperature sensors mounted in optimal location
Need both temperature and humidity readings
If Temperature < 68 or > 78, we need to know about it ASAP
If Humidity > 75%, notify.
Separate readings
Query the sensors via HTTP.
4 temperature sensors mounted in optimal location
Need both temperature and humidity readings
If Temperature < 68 or > 78, we need to know about it ASAP
If Humidity > 75%, notify.
Separate readings
Query the sensors via HTTP.
Solution must be fast, flexible
Keep end users in order entry screens
Get rid of 3rd party websites, proprietary applications
A web service within a web service!
WebServiceRequest function calls the parcel XML maps
The dollar amount is written to the freight field of the Sales Order
Less than 3 seconds on average for total process
Rapid development
Very little code in the ERP to support
Saves end user minutes per order, eliminates various websites and applications for rate checking
Resources:
HTTP input channel
Three maps: process, UPS XML, FedEx XML
Sync port response
Two HTTP output channels (one for each carrier)
Sync port response
CSV file downloaded manually (behind a login page)
1.3 million records
½ GB of Data (load takes about 2 hours)
Very similar solution to the Rate Shopping
Easier in the sense that it doesn’t do a second web service call
HTTP request -> Delta map -> Sync response with validation criteria
Quick to production (about a ½ day).
Some ERP application programming that needs to be supported
Very similar solution to the Rate Shopping
Easier in the sense that it doesn’t do a second web service call
HTTP request -> Delta map -> Sync response with validation criteria
Quick to production (about a ½ day).
Some ERP application programming that needs to be supported
Updates Expiration Date
Sets flags as to whether they can order controls
Updates DEA “Schedule”
Unique part of our integration process
While we are talking about our order process, we do the same thing for inbound invoices and inbound Advance Ship Notices
Limits the # of ECS clients we have in our organization
Adds the extra benefit of actually showing the end user the different permutations / status of line items
End user doesn’t need to see raw EDI
This is an example of what a sales rep might see when the order goes through the process.
An email for each order gets emailed.
As long as total order is greater than the min amount, the order will get integrated (flat file is on network)
We have programming resources in house. .Net, ProvideX, VB, scripting languages, web development, Flash, etc
Modeling data using Delta is simple
For some of the most complex processes only use 150 map
rules. Coding that same solution in .Net would be at least triple the lines of code (and would require compilation, source storage / version control, source maintaining)
Some of these maps took less than a half day.
Batches are all logged in a central repository – regardless of solution.
Errors are trapped consistently in the same framework