Basically, there is an approach to solving a problem that is successful. Following the pattern creates a solution that works and is stable.

There has been “much ado” about this relatively new tool in software development, but its practical applications are result driven and show that this is a tool that is here to stay.  As integration Engineers we have a slightly different bent on software development, but we need to know how application developers think and more importantly, how they talk.

I recently came across a book on design patterns written by Steve Holzner.  Its called “Design Patterns – Simply” and can be found here.  His site is also pretty good and explaining the very basics of what design patterns are and what they mean.

Now, if we just had a design patterns for integration engineers.  Maybe a book called “Integration Patterns” or something…..

Manufacturer to Customer

Evan Schuman writing for CBS News relates a Christmas shopping scenario where a store could use RFID to not only tell if merchandise is in the store or in the stock room.  But can be used to tell if the item is lost on the wrong shelf, or in line waiting for checkout.  In the same way, this can give inventory control systems information on order fulfilment.  When an order comes in, is the item in stock?  It the answer is yes we will want to trigger a response to the orderer indication that we can fill their order.  But what if the inventory database has an item listed, that we can’t find.  Using RFID we are able to track where it went in the warehouse, or if it is on a cart, getting placed on another truck or has been pulled by mistake.

Having up to data data on where products are located is not just useful to the sales clerk at Best Buy, but is useful all the way up the supply chain to the manufacturer.  As RFID gains more acceptance and people find real ways to save money and time by implementing it, into their supply chain solutions.

And speaking of RFID acceptance, in a recent article in the RFID Journal they reported that the Air Transport Association is adding an enhancement to their Spec 2000 to include RFID data standards.  This standard from the ATA is not a mandate or an all encompassing specification, but it is a step in the right directions.  As more standards groups begin to include the use of RFID technology in their specifications, the easier it will be to implement cross dock utility, and more timely data will be available for BPM processes and audits.

Benefits of Data

In the end, the supply chain lives on data.  Data on what products are available, where those products are, and how long it will take to get them to the customer or point of purchase.  All of the data points impact the efficiency of the supply chain, and the efficiency impacts the cost.  The more and better data we have the better we can make the supply chain.

RFID is only one way that more data will be collected within a supply chain cycle.  It has the promise to fill in the gaps of missed data opportunities.  What are other ways to pull more data out of the cycle of the supply chain?

But in a quick recap of what you will find in this whitepaper, Nahid Jilovec talks about the historical progress of B2B and some of the triumphs, roadblocks, and challenges that B2B as faced over the years.  But then he goes farther and describes Supply Chain Synchronization as containing three phases; Connection, Communication, and Collaboration.

I admit that during the first few pages it was reviewing things that I learned first hand, but would be a good introduction to someone new to B2B integration.  But then he goes farther and describes some more advanced tactical and strategic ideas that are worth the read.

—-

Do you have some Supply Chain News or Product that should be shared?  Or do you use an integration tool or service that other should know about?  If so, please send me a note with a link or reference to news@theintegrationengineer.com and I will try to blog about it here.

And don’t forget to subscribe to my rss feed.

—-

But today I want to tell you about a company I heard about that has created new efficiencies through integration efforts of a part of business you may have thought was already integrated.  The company is  INTTRA.  And instead of coming up with an untried technology, INTTRA used a combination of existing technologies to do something new.

In and article published by Supply Chain Digest on March 27, 2009, the describes how INTTRA used existing EDI and XML interfaces of Retailers, Manufacturers and Ocean Shippers to bridge the gap and make a manual process automated.

And Harry Sangree, senior vice president of business development and corporate strategy at INTTRA, gave Supply Chain Digest a quote that I think we can all relate to; “What we set out to do is to take a very un-standardized process and make it standardized.”  Is this not at the heart of what we do as Integration Engineers?

They go on to describe another aspect of this business integration that I salute and hope that more companies adopt.  They leverage EDI, XML, email and one line web interfaces.  This approach lowers the bar of the technology needed to benefit from doing business with end through them.

That leads me to one of the other things I find myself ranting about.  Companies that decide that they will only do business with people that do X or Y but not Z.  And so they raise barriers that prevent customers from patronizing their businesses.  I am sure they feel they have good reasons to do this, but sooner or later, someone is going to go after that business, and the one the restrictive company is targeting.  When that happens the restrictive business will be at a financial and market share disadvantage.

So I salute INTTRA, and their efforts to bring the advantages of a more integrated supply chain to ocean shipping companies of all technology levels.

—-

Do you have some Supply Chain News or Product that should be shared?  Or do you use an integration tool or service that other should know about?  If so, please send me a note with a link or reference to news@theintegrationengineer.com and I will try to blog about it here.

And don’t forget to subscribe to my rss feed.

—-