Inpute’s Customised Music Returns Solution Delivers Major Resource Savings for RTÉ
Each week, RTÉ broadcasts hundreds of different programmes, from news and current affairs to children’s programming and sport. Music forms a part – frequently an integral part – of almost all of this material and RTÉ provides details of its music usage to the relevant copyright organisations.
It’s the job of the Music Returns department to manage this process in RTÉ. The department collates details of the music RTÉ plays and sends these along with the transmission log to the relevant rights body. Eamon Cassidy of RTÉ explains that prior to the installation of the Inpute system, this was a very cumbersome process.
“It was a big paper-based exercise; nightmarish really, if you think of all the music that’s played out every day.”
That music returns process begins when the broadcast co-ordinator fills out a form detailing each piece of music used on the programme, how it was used, its duration and so forth. When the old, paper based system was in place, these were then sent to the Music Returns Department where they were collated, batched and sent out to the rights organisations. These returns were sometimes emailed in as MS Word or MS Excel attachments, though more often than not, they came in as paper.
“Prior to getting Inpute’s system,” says Cassidy, “we were managing a torrent of paper and electronic documents in multiple formats, all manually”
The Music Returns department employed between three and four people simply to co-ordinate all of this paperwork.
“You have mountains of paper piling up. The scale of it doesn’t come home until you consider, say, one of the old style cartoons: Bugs Bunny or Roadrunner, for example. There’s non-stop music in each of those. The music return could actually run to several sheets of paper, for an item that was only ten minutes long.”
The digitisation process began by getting all of the stakeholders in a room with Inpute and mapping out the process, mocking up screens and imagining how an electronic version of the workflow might look.
The team explored a wide variety of ‘what-if’ scenarios – suppose a form comes in and it’s unreadable? What if a return comes in late? What if it gets indexed incorrectly? Some returns can run to twenty pages. What if one comes in with a page missing? Will it be possible to insert it post-indexation?
One by one, each of these scenarios was discussed and debated, and a solution designed to deal with it. That process was so thorough, says Eamon Cassidy, that when the system was implemented, there were almost no teething issues.
“Between ourselves and Inpute, we did an excellent job of identifying all the possible nuances of what could go wrong with it, with the result that we got something that was fit for purpose, and ultimately required practically no tweaking.”