Currently in the media industry, users are implementing service-based systems using proprietary systems with bespoke software ‘glue’ holding it all together. They are doing this without an open, agreed framework and without standardized interfaces. While several organizations have identified a number of common processes such as capture which are performed essentially the same way throughout the industry, users are implementing these processes as services in different ways. At the same time, technology vendors are responding to demand for services-based products, but interoperability between different implementations is non-existent. This is because there is a lack of an agreed framework and publically developed service definitions in the media industry.
The AMWA-EBU FIMS (Framework for Interoperable Media Services) Task Force was established in December 2009. FIMS is a framework of service definitions for implementing media related operations using a Service-Oriented Architecture (SOA) approach. Media companies deploying this framework can expect that doing so will promote interoperability and reusability of services. FIMS defines service models with associated management, error handling, communication, and time awareness.
To properly exploit this technology the Task Force has developed a common framework which will help ensure integration interoperability, interchangeability and reusability of services. This will drastically reduce integration costs, allow users to more freely choose the most appropriate products on the market at any given time, improve maintainability, and aid in the adoption of new technologies.
FIMS also has begun the process of defining open services that are loosely coupled thereby enabling multivendor services to be integrated and creating “best-in-class” media systems. The services can span a wide domain of operations and permit integration of FIMS into business and management systems. The bottom line is that implementing FIMS will move facilities to an agile environment that is more easily configured, modified, managed and governed compared to non SOA systems.
Read the full whitepaper here : http://wiki.amwa.tv/ebu/images/1/12/FIMS_WhitePaper_Version_1.0.1.pdf
Via Nicolas Weil