I am finding a need to justify to our HR department the need for a full time Tessitura Specialist/Administrator/Manager position. I have completed a job description and a justification for the position here but HR has informed me that they believe such a position is not a long term fulltime position. I would like to give them a number for the number of Tessitura users that have such a position. We are a museum and we went live only 9 months ago. Our project manager for the implementation was/is our collections management system administrator and two systems is one too many for one person to oversee.
Any help you can provide me to justify that administering Tessitura is a long term full time position will be greatly appreaciated.
We only have one official Tessitura Administrator (me), but we also have a Development Research Manager who acts as the Development's first line of defense for similar requests. But as others have said below, any level of minor customizations, new report requests, website issues and questions, not to mention weird one-time data requests. Then there is application user access and management, not to mention someone whose job it is to look out for data integrity and be the go to person to train and tell people "this is how you do this" or "you cannot do that without also affecting all of this" is highly useful. If the position is there, it WILL get used.
"weird one-time data requests" - this. And the ability to judge when you need to custom report it. And the ability to custom report it.
If I can also stress that centralising the role will bring your data integrity together. I've spent a lot of time tidying a number of disparate Constituencies, Attributes (GL codes even). Without a Tessitura Admin it can become a wild west in there