To view this page ensure that Adobe Flash Player version 11.1.0 or greater is installed.
TECHNOLOGY CLASS FIMS: A Plug-and-Play Solution by Bruce Devlin FIMS, the Framework for Interoperable Services. N o two broadcasters are alike. Meaning, that just about every broadcaster in the world uses its own, customized workflow comprised of any number of proprietary tools and solutions, specially designed to work together. With so many systems with proprietary interfaces in existence, IT-based media projects require a great deal of integrations. As the industry evolves and new technology becomes available, this makes solutions very complex and costly to deploy and maintain. Enter: FIMS, the Framework for Interoperable Services. This framework simplifi es integrations through better and stronger standards – meaning, no need for custom integrations. However, to achieve this, we must develop applications with a standard interface. In addition to standard interfaces, FIMS employs a data model – a common representation for media assets – which incorporates standard metadata (such as EBUCore) that have been developed separately. 44 | KITPLUS - THE TV-BAY MAGAZINE: ISSUE 106 OCTOBER 2015 The idea behind the set of standard interfaces and data model is to develop a Service-Oriented Architecture (SOA). By exposing media applications as services and allowing for a fl exible, “plug-and-play” architecture, we can leverage standard IT technologies and enable customers to build best-of-breed workfl ows. As a result, we create an ecosystem of standard interfaces that simplify the design, build and deployment of systems, as well as the maintenance of said systems over time. Thus, integrating new tools through a FIMS interface does not require a complete architectural change. For vendors, this means more elaborate integrations can be built at a much lower cost. And because we reduce the number of custom interfaces, the cost to upgrade any given system is also reduced. What’s more, vendors can offer customers more benefi t through improved core applications, as – ideally – the time and money saved by not developing custom integrations can be reallocated towards developing media specifi c applications.