production-webproof-material-5.html
Whitepaper_LEAN_gb
6 / 10
6 / 9 white paper
webproof
.com access to the internal production
system
, which they could get through citrix, the supplier would have access to billing basis. this must not happen. so we decided which data fields in the booking system should display in webproof. this means only fields that are useful for ad manufacturers, not economic data. ad info is now automatically exchanged between atex and webproof using xml and is free-text-searchable. this is a big advantage for both internal sales and production employees who are always in webproof, and from where they simply can search on their name and only view their own ads. the external production location can, for example, now view the insertion date directly, which is important when it comes to priority. the implication is that users can only see what they have access to. some of the fields are editable, so you can add comments and other pertinent information. we exchange data between webproof and atex so webproof is the direct production management tool for external ad producers. we should not, through other channels, give the manufacturer the delivery date, the consultant?s name, whether the advertisement has to go through proof, etc. 7. workflow summary atex enterprise is a booking system that delivers ad data to webproof. webproof is the proofing and production management system. process status code changes on every single ad tell the user where in the process the ad is located. these status changes, either automatically via xml or manually - when a person is inside one of the processes, in both web- proof and atex enterprise. it could, for instance, automat- ically release a message to the respective sales people if the designer is missing some material. you can see an ad?s production location, the designer does not need to search for part materials, others can see that the designer is now working on the ad and, of course, you can see when it is approved. the ad may be in one of more than 100 different processes, but you never have doubts about where it is--an overview no other system can deliver and, as described here, has reduced manual manpower to a minimum as well as reduced production time, particularly waiting times, to almost zero. everything runs automatically to produce 10,000 to 20,000 ads per month, which has achieved major savings. 8. hardware overview all the manual processes that have been removed and put into automated workflows require a smaller system than you think. the only hardware used are a few servers. moreover, in- stead of using expensive cluster solutions, for production security, we have developed a solution so there are al- ways two servers, one as a hot standby for the other--i.e. all configurations files and ad data are being written down on both servers, so if one goes down, the other can just take over. it is a practical solution--keep it simple, stu- pid--it works. requiring no high it skills, this solution can be handled by a superuser with normal it background. cluster systems are very difficult to handle and require much more it expertise when something goes wrong. what once required 25 servers to handle preflight, etc. is today accomplished by one server, processing one- vision asura and webproof workflow. savings are piling up by dealing with one server rather than 25. this server handles preflight, collects all finished material, validates and manages the files so they follow the proof flow. a file server handles all part materials, packing/unpacking, shipping, etc. finally server handles xml file exchanges between atex enterprise and webproof, where webproof is a saas solution where the hardware and software is neither handled nor maintained by internal it. webproof is solely responsible ? again savings. 9. workflow overview to illustrate the extent of this automated ad production system, you will see just a small selection of the workflow involved--probably only 10% of all the processes. previ- ously, moving a file from one folder to another required a manual action. now everything happens automatically with a status code change, which eliminates the need to dig deeply in a file structure and copy files with the chance that they will be moved into the wrong folder, contain incorrect or old data, etc.
production-sales-webproof-7.html
