The logic is that NPrinting will ultimately make it so you need fewer people and qlikview licenses.
The value of it depends on how many standard recurring reports you have to send out and how complex those reports are. For instance, we used to have a couple of analysts who'd spend about 80 hours per month navigating qlikview dashboards and populating this super-fancy pdf they made that had mtd/qtd/ytd numbers and percents and graphs and tables about numerous kinds of activities for a few dozen corporate clients. Then they left our company simultaneously a week after we got nprinting and I was still figuring out one end from the other of nprinting. Their pdfs had color schemes and graph styles and layouts that a Qlikview rocket scientist might've been able to match 80% of, so I didn't hurt myself reconstructing that. Instead I just made a little 1-2 cell chart object with a super formula to compute each of the numbers the analysts had been looking up. (Actually a hidden =1 to force the chart to exist even if the main formula results in 0, then the actual formula in the second cell.) Then I set NPrinting to get all those mini charts and dump them on a plain excel worksheet. Then I linked all the cells of the fancy excel template to my raw nprinting exports. We went from 80 hours of work looking up all those numbers and transcribing to the fancy report templates, to pushing 'run' and spending about 1 hour opening and resaving as pdf. That was the weirdest case. I have numerous other daily and weekly reports I made from scratch where people were happy with any kind of decent looking graph or table or screenshot Qlikview could make and I don't have to touch those at all.
I've analyzed how much time those things took to assemble and send before and after NPrinting. They saved us about 7000 man-hours in year 1, about 15000 in year two (conservatively), and so on. And that was just me on SBE Qlikview server, my named license, NPrinting 16 server, and 2 nprinting desktop licenses. The license paid for itself, Qlikview, and my annual salary in under a year that first year. (We have 5 np designer licenses, 90 qv document licenses, 20 qv named licenses, and people doing interesting things around the place. I'm just the qv/np sme here.) I have an honors degree in finance, many years of analyst experience, and still hurt my brain on the formulas and process design though, so you do need to know what you're about to achieve that. (Also thanks to Gysbert Wasserstein and other legendary QV people and videos and nprinting community helping me learn how to operate the stuff when it was new to me. My degree helped me with data modeling and analytics, but not how to operate the applications :))
So, if it's just you making monthly reports to yourself and friends about your movie collection it's probably not worth it. If you have dozens or hundreds of recurring reports going to many people, it's certainly worth it. Also I think our nprinting price was something grandfathered and they were doing something to make it cost more if you have more recipients... but you all can assess the value by how much time it saves to have nprinting pull and send reports to everyone before the humans show up to work. Customer service and health coach teams still need to go navigate Qlikview dashboards to look up individual information on the fly whenever random customers called with random questions. And we have analysts data mining things and doing ad hoc reports and research too. If anyone has a repetitive task they're doing though, they ask me to automate it with nprinting for them.
Edit: fixed a couple of incorrect words and indented a bit. 🙂
