Greetings,
We are due to go live with TNEW in just over a month, and drop renewals for 15/16 at the same time.
Prior to the season build, we made a decision to subdivide our performances into separate seasons (Masterworks, Pops, etc), instead of our previous practice of building all concerts in one catch-all "Tickets" season per year. This decision was literally cheered for the improvements in reporting it would bring....
Then I began setting up a dummy 15/16 flex series for TNEW testing, and realized the corner into which I'd painted myself. Instead of one Performance Group per facility, and one flex Package for each package size (3 through 10 concerts), it seems I'd have to create the above times the number of Seasons per FY (which would be 4 or 5), and I don't even see how it would be possible to create package size and pricing restrictions across multiple Packages.
So it appears I'm stuck with an either/or choice: either forsake the reporting gains for manageable flex-package functionality (we sell a LOT of them), or proceed with multiple seasons and create a giant processing headache for the Box Office (not to mention quadrupling setup labor.)
Has anyone else found a good way around this, either from the setup or reporting end?
thanks, Herb
I'm not 100% sure if this is something that would even work, nor the level of reporting/T-Stats customization you'd need to implement to do so, but one thing I thought of would be possibly using genre. If you set everything to be in one big season, and then attached genre's onto each performance similar to how you have them broken out into each season. I read some forums on genres and saw some other people were using genres for T-Stats reporting, so you could potentially find some people to contact for help:
http://www.tessituranetwork.com/Community/groups/tstats/forum/t/6785.aspx
I'm not sure this is going to work for your case, but it's an avenue that you could try to give you the best of both worlds.