Keep current on things as they happen at Onpoint

Passive Integrations with Customer Systems

Jack Perry  January 20 2011 07:45:08 AM
Jack Perry
We've been seeing more requests for passive integrations lately. Passive is my term. Let me define what I mean. Rather than connect systems at the application layer through web services, 'passive' integrations use an intermediary utility such as an FTP folder. Two or more systems communicate by passing XML or ASCII type files to secure folders. Here's a likely scenario.

An order file is submitted to FTP folder by a customer-side system such as a marketing automation platform. A printer workflow system polls the FTP folder for new files to be retrieved then parses the order data in any new file found. Within seconds a reconciliation file is sent back to the FTP folder which is then retrieved and parsed by the customer application. "WE'VE RECEIVED YOUR ORDER".

Throughout the production, finishing and shipping process more communications are sent from the printer system to the customer system. "ORDER PRINTED". "ORDER FINISHED". "ORDER SHIPPED".

These passive integrations can provide significant savings in time and cost for both customer and printer. Passive integration is also an affordable way to integration and demonstrate to customers that you are willing to apply best practices to create print programs that are affordable and sustainable. Passive integrations also lead to long-term contracts and in-depth partnerships rather than customer/vendor relationships.