Hello BI Group! As you probably saw in the January Tessitura Network newsletter, we’ve launched a Business Intelligence initiative. We’re currently in a “discovery” phase in which I’m soliciting feedback from licensees about the current state of Tessitura BI.
In these early conversations a few themes are emerging, one of which is the desire to perform “snapshot” or “as-of” analysis. For instance, "how many members did we have as-of July 1st, 2013?" I would appreciate your feedback, experiences or examples of “as-of reporting”. Have any of you attempted snapshot reporting? If so, how did you approach it? Were you successful?
Additionally, if any one would like to chat with me about BI individually, please email me directly at jjakovich@tessituranetwork.com.
Thank you!John
John, Just had another conversation with a BAM staff person asking a great diagnostic question that I cannot currently answer with the data I get out of T_Stats, RMA, or frankly the database currently. Here is the question: “Does the general availability of “good seats” (Price Zones 1 and 2 not in holds) at the on sale date have a correlation with BAM’s ability to “make goal for the performance” (Performance Sales $ (at curtain) >= performance budget $)? Here is what is missing. 1. I do not know how to do a true se Seat Inventory that describes how many seats we have not blacked out not in a hold codes at On Sale Date. (Frankly This question could and should be asked about any time along the sales cycle 10 days before curtain, 30 days before curtain… Or any set of availability conditions not just certain holds…) 2. In a Seat inventory we don’t know what zones seats were in at the time of On Sale or any other time other that as it is today. 3. Here at BAM we do not do a good job at recording an On-Sale Date in t_perf.def_onsale_dt. (Bad on us. We could fix this.) What do we already have to answer such a question. 1. The T-Stats data warehouse currently tracks Performance Sales data at the seat level as of today. However, one cannot determine the sales status “as of” say 30 days before performance 10 days…. We could use a sales transaction data set for data analysis.” 2. The T-Stats Data warehouse currently tracks budget numbers by performance. From: John Jakovich <bounce-johnjakovich8396@tessituranetwork.com> Sent: 2/19/2016 1:29:34 PM Hello BI Group! As you probably saw in the January Tessitura Network newsletter, we’ve launched a Business Intelligence initiative. We’re currently in a “discovery” phase in which I’m soliciting feedback from licensees about the current state of Tessitura BI. In these early conversations a few themes are emerging, one of which is the desire to perform “snapshot” or “as-of” analysis. For instance, "how many members did we have as-of July 1st, 2013?" I would appreciate your feedback, experiences or examples of “as-of reporting”. Have any of you attempted snapshot reporting? If so, how did you approach it? Were you successful? Additionally, if any one would like to chat with me about BI individually, please email me directly at jjakovich@tessituranetwork.com. Thank you! John
John,
Just had another conversation with a BAM staff person asking a great diagnostic question that I cannot currently answer with the data I get out of T_Stats, RMA, or frankly the database currently.
Here is the question:
“Does the general availability of “good seats” (Price Zones 1 and 2 not in holds) at the on sale date have a correlation with BAM’s ability to “make goal for the performance” (Performance Sales $ (at curtain) >= performance budget $)?
Here is what is missing.
1. I do not know how to do a true se Seat Inventory that describes how many seats we have not blacked out not in a hold codes at On Sale Date. (Frankly This question could and should be asked about any time along the sales cycle 10 days before curtain, 30 days before curtain… Or any set of availability conditions not just certain holds…)
2. In a Seat inventory we don’t know what zones seats were in at the time of On Sale or any other time other that as it is today.
3. Here at BAM we do not do a good job at recording an On-Sale Date in t_perf.def_onsale_dt. (Bad on us. We could fix this.)
What do we already have to answer such a question.
1. The T-Stats data warehouse currently tracks Performance Sales data at the seat level as of today. However, one cannot determine the sales status “as of” say 30 days before performance 10 days…. We could use a sales transaction data set for data analysis.”
2. The T-Stats Data warehouse currently tracks budget numbers by performance.
From: John Jakovich <bounce-johnjakovich8396@tessituranetwork.com> Sent: 2/19/2016 1:29:34 PM
Thank you! John