Staff Constituency Code for ticket discounts

Hello Grant,

Here at The 5th we do enter all staff into Tessitura. This is done by our IT network team as they set up all credentials for a new staff member. We do add a staff constituency so we know they are staff (more for staff parking then anything). We recently upgraded to 12.5 and haven't started using pricing rules much yet. But, I would imagine you could set up pricing rules to work with this constituency. The hardest part of all this is upkeep. Often current staff members aren't transitioned out of the staff constituency.

You are on the right track and all you are looking to do is totally doable and done at many organizations.

Best,

Christopher Cuhel, The 5th Avenue Theatre

PS (Split Rock Lighthouse was always one of my favorite North Shore excursions to take. That and Gooseberry Falls. I'm originally from Superior, WI) 

Thanks for your reply and North Shore endorsement!

How many employees do you have?  We have more than 700 during the summer. 

Tessitura using employees....we have probably 20-25. As for total staff, our numbers can go over 300 depending on the time of year.

However it doesn't have to be too difficult for you. There is a utility called Manage Constituency. You could create a list for each year/season that is all of your seasonal staff and one for you permanent staff. You could then run this Manage constituency report to add, update and even deactivate the constituency. The only thing you can't do in the out of the box utility is set a start date. The start date will be whatever day you run the utility. I'm sure with a little custom work though, you could augment the utility to also allow you to set a start date.

I could even see segmenting your lists for different start dates and departments or historical sites throughout Minnesota. The possibilities are endless.  :)

Unknown said:

We are relatively new to Tessitura and are trying to think of ideas for adding staff members as constituents.  Then assigning them a constituency that can be used for discounts to programs online and in person.

How are others managing this?  

Most staff here have always had constituent records, for comp sales. In recent years we've slowly become more systematic about this, and this year, with the move to a new payroll system, I've begun work on what will hopefully be a completely automated, daily update of active staff, actors, contractors, etc., that are eligible for comps. 

Different constituencies have different criteria for determining Active status, e.g. for regular staff ("STF" constituents), they are present in payroll data as such; for Actors ("ACT") and other creatives ("CRE")), they are associated with a current or upcoming production, etc. (All of our constituencies, related to ticketing or not, are activated/inactivated via a daily SQL update; none are applied manually) As the related constituency becomes active, they are also populated with a Rank that enables a MOS-switch on TNEW, revealing comps on selected dates. When the triggering data disappears or (more usually) goes inactive, the constituency goes inactive, and access to the comps goes with it.

There are a lot of moving parts, but it's working out well so far. The download of payroll data isn't automated yet, but that will come. Contractors and other non-payroll people need end-dated Affiliation records, which are manually created, and in some cases that may never be completely automated.

Hi Chris,

Amazing, I've been wanting to do this at the Public for about a year now.  Which payroll system do you use?

I'm interested in which parts are automated and which parts are handled by a human --

When you say "triggering data", I'm assuming you mean the payroll data - where does it live? Is it in a folder that SSMS refers to?

How do the constituencies first get applied?

Do you use LP_CUSTOMER_RANK for the ranking based on the constituency?

Thanks,

Frannie

Hi, Frannie-

Unknown said:

Which payroll system do you use?

As of around 4/1 this year, UltiPro, from ultimatesoftware.com. Previously we used Ceridian, and before that ADP, and thankfully we've carried a unique ID along from system to system, which of course lives in Tessitura as a "payroll_no" attribute.

Unknown said:

I'm interested in which parts are automated and which parts are handled by a human --

When you say "triggering data", I'm assuming you mean the payroll data - where does it live? Is it in a folder that SSMS refers to?

In the case of regular STF that are in the Ulti data, they must have a payroll_no attribute and an active affiliation with the Guthrie. The daily-ish refresh of payroll data is supplied for the moment by a Cognos report that I created in Ulti's online GUI, which is generated for me each day via a schedule. (Ulti has an API, which I hope to make use of at some point to grab this automatically, but that's not baked yet.) I get name, title, status, etc. from that data, and will eventually create new constituents from it as needed.

Unknown said:

How do the constituencies first get applied?

I have a nightly SQL Agent Job that among other things runs a custom sproc that maintains all of our 50+ constituencies. In the case of STF constituencies, if the active Employment affiliation mentioned above exits, they get a STF. When the Affil reaches an end date (or that payroll_no no longer exists in the payroll data), the STF inactivates.

Unknown said:

Do you use LP_CUSTOMER_RANK for the ranking based on the constituency?

No, I've always hesitated to use that sproc since it executes so often, and thus might slow down client performance. I update our ranks via, you guessed it, another scheduled SA job + sproc. :-)

all very interesting! thank you

Chris, this is very cool.  Thanks for posting!  

I might be reaching out to you as we move forward with implementing this.