indd-materials-webproof-4.html
Whitepaper_LEAN_gb
5 / 10
5 / 9 white paper
webproof
.com the right folders. in principle, we should not worry about the extraction at the supplier, as this was included in the agreed millimeters price, but many errors at this process revealed that we had to automate this process as well. in this way, we eliminated all the manpower required to pack and unpack and material
s went back realtime. 1. we set up a function which collected all materials together, including previous indesign ads, images, fonts, and renamed files so when the material is returned. this function automatically moves and archives folders and moves ads to respective news- papers, etc. 2. after collection of all material into a folder, it will be zipped and uploaded to webproof, where it waits for a status that tells which production
location shall produce the ad. when this status is applied, the zip package will automatically be moved to the produc- tion site. the ad is visible in webproof for only this particular production location, and they can start immediately. 3. the proofing traditionally runs between the pro- duction location and the advertiser or sales con- sultant. when the ad is approved by the customer, all materials will again automatically be collected and packed, including indesign files, high-reso- lution pdfs, and part materials, and sent back to be unpacked automatically and moved to the right folders. the production location handles the proofing directly with the customer. eliminating manpower means no designers have to unpack when the ad is returned from the production location. all material is ready when we receive an order for a new ad from the same client. only one designer is involved, when all material must be prepared for auto packing. the structure of part materials and pdfs, both going and coming, is most important. it now becomes meaningful to outsource production. prior to implementation, it could take up to one month before ads and part material came back from other pro- duction locations. problems could result if the ad had to be produced again. this now happens in realtime. today we are never missing material. 5. process flow to external production locations we would like to go even further and remove the resourc- es we used to prepare the materials for ad production: part materials, previous ad copies, old logos to be recy- cled, old material copies, etc. at the same time we would like to ensure that suppliers do not have external access to our file system, a general it security requirement for all external suppliers. we used the webproof solution, which has some great facilities to auto-empty email boxes and structures, i.e., xml tag content for further use. when there is an order for a new ad, you simply send an email, with the ad number in the subject line, to a given emailbox. this email also contains, for example, the mes- sage that the ad should look like the last produced ad, but it must be changed. webproof picks up all sub mate- rials in different folders, zips and places the package on a ftp server, and creates an ad page in webproof with the status ?ready for production.? by placing status ?ex- ternal? in webproof, the zip package is automatically moved to the current supplier and passes a message that the supplier can now start to produce the ad. the supplier places the status ?external production,? which tells everyone that they are now in progress. at any time in webproof you can determine a given ad?s location in the process and sort these process statistics and dis- play visually, in real time, how many ads are waiting to get started, how many are in progress, in proofreading, etc. when a new supplier starts up, we initially add an extra control bow, to eliminate obvious errors until the sup- plier runs flawlessly. this check is also performed during production, as a quality control. 6. xml integration between booking and webproof (mirroring) there was still some manual handling we wanted to re- move from the process. here we saw the xml integration as a solution. we could also exchange more information between webproof and the booking system--here, atex enterprise (mactive). users sometimes registered incor- rect file names, which meant that we sometimes had to spend quite a time on troubleshooting, material search, etc. a prerequisite was that suppliers must not have access to the internal production systems. if you gave
webproof-production-system-6.html