Tessitura Customisations Checklist

Hey folks,

We are shifting out SelfHosted Tessitura to Hosted Services (nee RAMP) and in the run up we really need to have a good look at the various, and many customisations that have been put in place over the last 10 years.

Does anyone have advice, tips and/or a customisation leger/doc that has helped them in the past?

H

Parents
  • Probably unneeded advice for a seasoned vet like yourself, but that is the perfect time (well, once you find them all, and Carol's queries there sound like the best place to start) to also evaluate all of your customizations and discuss things like which ones are still needed, which ones can be retired, which ones can be switched over to new/standard Tessitura functionality, and which ones need to be updated.

    And I do not have anything specific for this sort of thing, but I create build/to do checklists for just about everything I do.  Sure, you remember that you have already checked customization #2 the following week, but when you have been checking customizations for 2 full months, and just finished #48, you suddenly are reminded of #2, and ask yourself "Did I really look at this already?".  Looking at your log and being able to verify that you already signed off on it (or someone else did if their initials are there; plus a second column for proofing when needed), is definitely a way to lighten the mental load.

  • From everything weve talked about over the years, your cataloging set up is brilliant. I really would love to interview you about it sometime.

    To be honest a lot our customisations are some genius stuff solving a problem that you can mostly do in Tessitura anyway, or vastly over complicated business rules that gave marginal benefit. As a consequence we have a lot of stuff that has stopped us being able to upgrade, and we are newly on 15.0 and using t-stats. We'll clear it up though.

    A clever pal of mine gave me a bunch of tip including running through SSAgent. 

    I'm keen to get a library of the custom reports and their stored procedures, rdl, xml ready for reinstall. A lot will be rebuilt in  analytics.

    Thanks all. Hope to keep the chat going, maybe at a TLCC

  • To be called brilliant by is high praise.  I will take it, and I thank you truly.  TLCC is always a good option with me, and I am sure we can make something happen.

    Oh T-Stats.  I have not thought about you for years now.  Sounds like you do indeed have a fair bit of work ahead of you, and I wish you well on it.  I am also quite confident that you will get it handled.  And I am still working on moving a number of things to Analytics myself.  It is that data lover's wish for updated data that keeps getting me.  I know that precisely up to the minute data is not what all staff needs, and certainly when it comes to long term planning and for marketing and development strategies really, everything up to the end of the previous day really IS enough.  It just bugs me.  But I am getting there, slowly.

    Best of luck on this whole project!

    John A. Moskal II

Reply
  • To be called brilliant by is high praise.  I will take it, and I thank you truly.  TLCC is always a good option with me, and I am sure we can make something happen.

    Oh T-Stats.  I have not thought about you for years now.  Sounds like you do indeed have a fair bit of work ahead of you, and I wish you well on it.  I am also quite confident that you will get it handled.  And I am still working on moving a number of things to Analytics myself.  It is that data lover's wish for updated data that keeps getting me.  I know that precisely up to the minute data is not what all staff needs, and certainly when it comes to long term planning and for marketing and development strategies really, everything up to the end of the previous day really IS enough.  It just bugs me.  But I am getting there, slowly.

    Best of luck on this whole project!

    John A. Moskal II

Children
No Data