How do you Extend Tessitura today?

Hi Andrew

 

Apart from a general comment that virtually all our day-to-day sales/performance based reporting is customised, here’s a couple of more exotic examples:

 

1.     We needed to manage and report on GST (Tax) calculations in an environment where tax thresholds are set as an absolute value per production. Also needed to split out GST from prices at time of posting but without complex price mapping. This required three custom processes:

a. Define at a Zone Map level the absolute threshold above which GST applies;

b. Define every GL Code and whether or not it needs to be “split” at posting, and the rate at which the split is to be applied; and

c. A secondary split process that takes the ‘canned’ posting report and runs it through a secondary post to split out the GST-able amounts to a separate GL, based on the settings in item 2.

 

2.     We needed a process to manage performance settlements that captured multiple third party sales figures, and that was synched with our event management system (EBMS) where the final invoicing is managed. This comprised setup of a web-based data entry screen which updates two custom tables, one of which also defines the link between Tessitura performance IDs and EBMS equivalent codes, and an automated cross-platform checking process to ensure Tess and EBMS setups and settlement statuses are in synch. It also assists in end-of-month reconciliation between Finance system account balances and monies held on advance performances not yet ‘settled’ in EBMS, according to Tess GL posting dates.

 

3.     Our in-house producers needed a sales report that tracks revenue and ticket sales against per-production (not per-performance) targets; calculates number of days on sales and number of days to go and amount needed to sell per remaining day to achieve target. It needed to be able to exclude standby perfs in a production built but not on sale, and to be able to increase target values as new perfs are released for sale, and also ignore productions that ended more than a user-defined number of days prior to report run date.

 

 

peter nelson business analyst

information systems

pnelson@sydneyoperahouse.com

T+61 2 9250 7180  F+61 2 9251 7821 

 

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

 

 

Hi,

As we explore and refine the potential architecture approach for the Next Generation product, a key element is extensibility.  The current Tessitura software provides a variety of ways for organizations to extend the software today, and we have heard loud and clear that a high degree of customization/extensibility in the future product is a key requirement.  One way to help us understand future extensibility needs is to first understand how you customize today.  This is a purposefully open-ended question: 

 

Please provide us with examples of customizations or extensions you have made to Tessitura and the business case behind why you made the extension.

 

We aren’t looking for every customization, but one or two samples that are either most representative or most difficult to accomplish in current Tessitura.

 

 

A quartet of examples:

1.       We created a custom Box Office Statement in InfoMaker to match specific output field requirements of our promoter.  This allows us to settle with the promoter in an efficient and speedy fashion, without us having to run multiple reports and combine them after the fact.

2.       We adapted lp_customer_rank to automatically assign a constituency code of ‘Student’ if the constituent has purchased tickets to our Education season and has a customer type of Child.  This allows CSRs to quickly identify students when looking up an account, and makes list pulling easier.

3.       We created a custom constituent screen using InfoMaker to hold detailed information about our Press contacts.  This allows us to have information about all constituents in one place, and ensures we can track specific seating assignments and preferences based on the reviewer.

4.       We created a set of pages on our website to record individual member names on a family membership, tied to a custom table and custom membership card output so we can print individual member names on membership cards and link them back to a single membership in Tessitura.  This means that multiple members of a household can each have their own personalized membership card while retaining a single membership on the household itself.

 

 

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====

Hi Andrew

 

Apart from a general comment that virtually all our day-to-day sales/performance based reporting is customised, here’s a couple of more exotic examples:

 

1.     We needed to manage and report on GST (Tax) calculations in an environment where tax thresholds are set as an absolute value per production. Also needed to split out GST from prices at time of posting but without complex price mapping. This required three custom processes:

a. Define at a Zone Map level the absolute threshold above which GST applies;

b. Define every GL Code and whether or not it needs to be “split” at posting, and the rate at which the split is to be applied; and

c. A secondary split process that takes the ‘canned’ posting report and runs it through a secondary post to split out the GST-able amounts to a separate GL, based on the settings in item 2.

 

2.     We needed a process to manage performance settlements that captured multiple third party sales figures, and that was synched with our event management system (EBMS) where the final invoicing is managed. This comprised setup of a web-based data entry screen which updates two custom tables, one of which also defines the link between Tessitura performance IDs and EBMS equivalent codes, and an automated cross-platform checking process to ensure Tess and EBMS setups and settlement statuses are in synch. It also assists in end-of-month reconciliation between Finance system account balances and monies held on advance performances not yet ‘settled’ in EBMS, according to Tess GL posting dates.

 

3.     Our in-house producers needed a sales report that tracks revenue and ticket sales against per-production (not per-performance) targets; calculates number of days on sales and number of days to go and amount needed to sell per remaining day to achieve target. It needed to be able to exclude standby perfs in a production built but not on sale, and to be able to increase target values as new perfs are released for sale, and also ignore productions that ended more than a user-defined number of days prior to report run date.

 

 

peter nelson business analyst

information systems

pnelson@sydneyoperahouse.com

T+61 2 9250 7180  F+61 2 9251 7821 

 

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

 

 

Hi,

As we explore and refine the potential architecture approach for the Next Generation product, a key element is extensibility.  The current Tessitura software provides a variety of ways for organizations to extend the software today, and we have heard loud and clear that a high degree of customization/extensibility in the future product is a key requirement.  One way to help us understand future extensibility needs is to first understand how you customize today.  This is a purposefully open-ended question: 

 

Please provide us with examples of customizations or extensions you have made to Tessitura and the business case behind why you made the extension.

 

We aren’t looking for every customization, but one or two samples that are either most representative or most difficult to accomplish in current Tessitura.

 

 

A quartet of examples:

1.       We created a custom Box Office Statement in InfoMaker to match specific output field requirements of our promoter.  This allows us to settle with the promoter in an efficient and speedy fashion, without us having to run multiple reports and combine them after the fact.

2.       We adapted lp_customer_rank to automatically assign a constituency code of ‘Student’ if the constituent has purchased tickets to our Education season and has a customer type of Child.  This allows CSRs to quickly identify students when looking up an account, and makes list pulling easier.

3.       We created a custom constituent screen using InfoMaker to hold detailed information about our Press contacts.  This allows us to have information about all constituents in one place, and ensures we can track specific seating assignments and preferences based on the reviewer.

4.       We created a set of pages on our website to record individual member names on a family membership, tied to a custom table and custom membership card output so we can print individual member names on membership cards and link them back to a single membership in Tessitura.  This means that multiple members of a household can each have their own personalized membership card while retaining a single membership on the household itself.

 

 

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====