Friday, March 2, 2007
API to Print
A concept that I have been thinking about as I work on my thesis is the use of an "Open" Application Programming Interface (API) to a print production system.
The API concept in itself is not a new method of ordering print. ColorCentric in Rochester, NY has built an API that allows their strategic partners to automatically submit print orders to their production system without the need for human-to-human interaction.
So when you order a copy of Frank Cost's Facing Myself X-Treme, the LuLu system interacts with the ColorCentric through a formalized document exchange and the order is queued up in ColorCentric production system, printed, and then shipped.
There were no phone calls, no proofs, or any of the traditional customer service activities associated with print production.
But to achieve this level of order automation and fulfillment you need be a ColorCentric partner. I can not build a web-based store front and just start pushing print ColorCentric.
But what if we take this production methodology one step further and create an Open API-based system that doesn't require strategic partnership or be an existing customer of the print service provider? What if there an API that would enable anyone with the desire to have content printed on-demand to plug-in to your production systems.
What does a system of this type require to work? What enabling technologies and production practices are required? And what are potential applications for this system?
Without a doubt, the technology exists: document exchange technology is prevalent, digital prepress is the norm, press systems for on-demand print production are abundant, and automated near-line and inline finishing systems are available for almost any finishing type.
Document Exchange Requirements
The Order and transaction system could leverage the abilities of document exchange standards:
- PDF/X for prepress data exchange
- Some type of an XML-based job ticket. This could be the combination of JDF for product specification and cXML for business transaction data.
When a transaction occurs, the print service provider would have all the necessary data to specify, produce, fulfill, and bill the job.
Embracing New Workflow Methodologies
Building this type of production system is departure from the traditional job shop mentality most printers have: I will produce any product you specify.
The Open API based content on-demand print production model relies on a catalog-based deterministic workflow methodology. This methodology is essentially what mass manufactures have been doing since Henry Ford, but with a touch of Dell Computer's product fulfillment methods: You can order a customized computer as long as it is within these constraints.
Applying this to a print production workflow dictates that only printed products with select attributes are offered by a print service provider. A companies internal processes and technology determine what colors, product sizes, and finishing options are available. For example, this might limit a company to only offer Monochrome or Full-color products that are 8.5 x 11, 6 x 9, or 5.5 x 8.5, and are finished either as flat sheets, saddle-stitched or perfect bound.
Constraining product variety provides the ability for the creation of production cells that have the potential for complete automation of production processes. In a manufacturing environment of one and twosies a high level of automation is required to remain profitable.
If We Build It, Will They Come
Of course there is no need for such a system if no applications exist to use it. One application I'm interested in is the Wiki-to-print system I wrote about a few weeks ago. But this could be an used on any web site that has rich content. Any current print on-denamd application would also be well suited for this system.
With wide spread adoption, each print service provider would become a node on network allowing a web storefront to start to using systems intelligence to determine where to send the job. It could make decisions based on price, geographic location or other productions metadata.
Posted in: Web-enabled Print
