• Replies 11 replies
  • Subscribers 414 subscribers
  • Views 58 views
  • Users 0 members are here
Related

Perf Code Format

Christopher Cuhel
$organization
Hey All, I'm trying to figure out a standardized perf code format for rentals in our spaces. The Smith Center is a new organization, however, I have been using Tessi for quite some time. Although, I've not been at a place with as much rental as we have....as well as having a jazz cabaret, black box studio, and park setting for outdoor performances. I've got a perf code setup that is pretty much the standard I have seen almost everywhere. My struggle is figuring out codes for rentals and those other spaces. I was thinking it would probably be best for those to just use a two letter code that is for each space and go from there. We also have meet & greets and such. We are in the initial stages of set up and want to have some "best practices" to bring to all involved so we have some options. Thanks all for any advice you have. Chris
Parents
  • $organization

    Chris,

    I feel your pain! As a large-ish consortium we've definitely needed to establish some standards around this, in particular where there are custom reports or elements depending on perf codes.

     

    Fully extended, ours might look like this:

    GTCS17BS01 = Granada Theatre Concert Series, Fiscal Year '17, Brian Setzer Orchestra, first performance.

    or

    RENT17AW03 = Rental, Fiscal Year '17, Ali Wong, third performance.

    Your idea of using two digits for identifying the space would work - but I'm curious why that needs to be encoded in the Perf Code? We've developed our code format primarily to avoid ever having duplicate performance codes, so if you're often producing the same event in multiple spaces, I can see the need to distinguish between the event in the park versus the event in the studio!

    Good luck with your standards-setting.

    --Stacey

Reply
  • $organization

    Chris,

    I feel your pain! As a large-ish consortium we've definitely needed to establish some standards around this, in particular where there are custom reports or elements depending on perf codes.

     

    Fully extended, ours might look like this:

    GTCS17BS01 = Granada Theatre Concert Series, Fiscal Year '17, Brian Setzer Orchestra, first performance.

    or

    RENT17AW03 = Rental, Fiscal Year '17, Ali Wong, third performance.

    Your idea of using two digits for identifying the space would work - but I'm curious why that needs to be encoded in the Perf Code? We've developed our code format primarily to avoid ever having duplicate performance codes, so if you're often producing the same event in multiple spaces, I can see the need to distinguish between the event in the park versus the event in the studio!

    Good luck with your standards-setting.

    --Stacey

Children
  • $organization in reply to Stacey Voigt
    Hey Stacey, We don't have to have the two letter code for the performance. That's a throw back to other organizations I've worked at that were previously Ticketmaster organizations. It seems they have always had a very uniform way of perf code entry in Ticketmaster Host. With that said....I'm amendable to any perf code setup as long as it makes sense for a venue with 4 performance spaces that can have multiple events in Tessitura on any given day. I just transitioned to The Smith Center and we are in onboarding phase of Tessi and I just want to ensure that we start using smartly from the beginning and have as best of data, that will stand the test of time, going into Tessi to start. Thanks for the insight Stacey. See you at TLCC? -Chris