web integration

We've gone with a few local companies over the past 5 years - it has been somewhat of a struggle to be honest because there is such a steep learning curve. We are generally very happy with the company we are currently with, but we have really defined / refined the development process.

The way it works now is that we internally design and outline the backend processes and any hooks into the frontend and then send that to the development company who essentially codes it all.  First, this ensures that all stakeholders on our end understand the business process, rules, and how the product will actually be sold and how the customer will interact with it on the web. It also lets us work out all of the Tessitura 'kinks' like setting up or modifying new tables, create new local procedures if required, etc...

It also saves the development house a lot of time because they do not need to become Tessitura experts.

You can contact me directly and I can send you the latest example - I just sent a wireframe and 7 page document to the dev team for NFS packages online.

Hi there

We spoke to a few different vendors about the web integration work and got various responses. 

There are new people to Tessitura that are keen to get into this type of work but we decided we could not afford to provide the learning platform for them.

In addition we had feedback for other venues about the pitfalls they found because they used a developer new to Tessitura.

Your budget and available in house resource may well impact on you decision to.

Regards Ewan.

We use the recommended vendors, but have started to develop pages inhouse. We find this to be a healthy step in mantaining the pages that our vendors create. This way we don't have to go them every time we need a change. It also allows us to better communicate with the web vendors and provide better direction.

We found that there are 2 types of vendors- the ones that have a person that project manages and transaltes your needs to their developers. These type cost a lot. The second type are strictly developers and you need to spell it out for them. They are more cost effective.

If someone at the organization understand how the API works, I think that you will get all around better results whether you use a vendor or build the pages yourself. I was nervous to tackle the API, but I found it to be pretty straight forward and not too difficult.

Because of geography - mostly to do with the time differences between Australia and the US, we chose a local web development company.  It was painful at first whilst we (effectively) provided the resource for them to learn the web API they're pretty good at underastanding the calls and responses.   In hindsight it possibly cost us as much as using a US based company which, because of fluctuating exchange rates, can be pretty expensive!  The exchange rate issue also means for us that budgets can suddenly blow out - depending on how strong the AU$ is at the time of invoicing.  There is a reasonable amount of resource I need to supply to help them understand what's going on in Tessitura too.

Hi All,

Good day.

I have another idea about the web integration.

How about this?

You can develop a website selling tickets send out info do what ever you want to do totally separate.

You just pass certain numbers of tickets to web site, like pass them to TicketMaster.

So there is no Web API, no nothing.

What you need to do just load the sales data back to Tessitura.

It will cut your cost dramatically.

Have fun.

:-):-):-)