Main Page

From AMWA-EBU

Jump to: navigation, search

Welcome to the EBU-AMWA FIMS (Framework for Interoperable Media Service) Task Force Wiki

This is not the AMWA wiki, which discusses AMWA-only efforts. This wiki is for the AMWA-EBU joint task force.


FIMS Phase 2 - procedures

Contents

FIMS 1.0 - FINAL OUTPUT DOCUMENTS FOR FINAL REVIEW

FIMS 1.0 is composed of the following parts:

  • FIMS 1.0 Part 1
  • FIMS 1.0 Part 2 (specification)
  • FIMS 1.0 XSDs and stubs


These documents can be downloaded from here (specification directory): [[1]]

FIMS Phase 2 - REPORT ON SUBMISSIONS RECEIVED

The FIMS Phase 2 RfT is now closed.

For reference the RfT for phase 2 is available at : File:FIMS Phase2 RfT.pdf.

The RfT is a success with 30 Use cases from 10 individual companies and a European project consortium.

The main domains covered by the use cases can be summarised as follows:

  • resource estimation for reservation - BBC
  • IP stream capture - BBC
  • Quality Check / Quality Control(QC) / conformance check - BBC, IRT, NBCU, TBS, RAI
  • forensic marking - NBCU
  • repository service - RedBee Media, Bloomberg, TBS (proxy browse)
  • AV process service - Sony
  • advanced transform service - Sony
  • media asset registration service - Sony
  • media asset retrieval service - Sony
  • media asset update service - Sony
  • media asset query / search / discovery - Sony, NBCU, TOSCA consortium, Wells Fargo (and other associated metadata management considerations)
  • status logging service - Sony
  • status retrieval service - Sony
  • media logging - TBS
  • proxy browse - TBS (see also repository)
  • VoD fulfilment / broadcast preparation - TBS, RAI, CBC
  • preparation for edit - RAI
  • automated metadata extraction benchmarking, query and search - TOSCA consortium
  • automated metadata extraction services in production - TOSCA consortium
  • customised FIMS services based on tools defined in the specification - Hessische Rundfunk

NOTE: the above is a preliminary rough classification of the submission and these will be reviewed in more details by the FIMS Business Board (FIMS_BB) in charge of assessing the responses, evaluating they purposefully address the project goals, seeking clarification, identifying resources to work on a solution and setting priorities for the Technical Board (FIMS_DEV).

The following file contains all the forms submitted within the deadline: File:FIMS RFT Phase2 Submissions.zip

NOTE: The contribution from Wells Fargo came with substantial supporting documentation that will be made available in due course (already available to the fims_adm members and can be provided on request).

FIMS Phase 1 - All other documentation about phase 1

FIMS COMMUNICATION AND PARTICIPATION IN INTERNATIONAL EVENTS (NAB, IBC)

Webinars

Webinar, November 30th, 2011: File:FIMS Webinar Phase2 20111130 Version Final.pdf

Exhibitions and demonstrations

Publications in English

Al Kovalick, Avid

Publications in Japanese

Yoshiaki Shibata, metaFrontier, "FIMS comes after FileBase", monthly magazine "NEW MEDIA"

  • Part 1 - "Media SOA and the FIMS Eve" (Vol. 29, No.341, p,95-97, Aug.1, 2011)

http://metafrontier.jp/drupal/sites/default/files/papers/intro2Fims4NewMediaSep.pdf

  • Part 2 - "Web Service and SOA System" (Vol. 29, No.342, p,82-84, Sep.1,2011)

http://metafrontier.jp/drupal/sites/default/files/papers/intro2Fims4NewMediaOct.pdf

  • Part 3 - "FIMS Features and Implementations" (Vol. 29, No.343, p,59-61, Oct.1, 2011)

http://metafrontier.jp/drupal/sites/default/files/papers/intro2Fims4NewMediaNov.pdf

Publications in Russian

Igor Petrov, Cinegy, "FIMS - но вый стандарт взаимодействия медиасервисов", Russian periodical ‘625’

File:FIMS Russian 625 7 2011 74.pdf

Why did EBU and AMWA initiate this joint task force?

While the market is moving away from traditional videocentric technologies in favour of IT based ones, the design and management of enterprise level production systems is still a challenge for most broadcasters. A main obstacle has been identified in the lack of standard interfaces between components and systems that forces system integrators to devote consistent resources in the development of custom adapters to integrate components from different vendors. This in turn generates scalability and maintenance problems as the substitution or upgrade of one component can require further adaptation expenses.

The EBU, through the P/NP group, is evaluating the use of Service Oriented Architecture (SOA), a system design pattern that is ,believed to offer the potential for greatly improved interoperability over the current system design practices based on proprietary interfaces.

AMWA has set up a Media Services Architecture Group (MSAG) with a similar mandate.

Therefore, as both EBU and AMWA have similar activities and intents, the two organizations have agreed to engage in joint efforts in order to gather a broader consensus between users and manufacturers and to join knowledge and resources to better fulfil the assignments.

What are the expected benefits?

The introduction of IT based production models is considered a strategic move to fulfil the market demand for new integrated content distribution services. Interoperability of systems and components is deeply needed to guarantee the required flexibility in the design, configuration and upgrade of the production infrastructure and to keep its associated TCO as low as possible.

The joint Task Force is made up of both manufacturers and users. Manufacturer members are interested in reducing their costs and risks associated with integration. User members are interested in faster time of integration, with lower cost and risk. The adoption of standard interfaces at the business level, as SOA promotes, would allow for these goals to be achieved.

What are the risks if the activity is not done?

The risks are that market solutions are not converging spontaneously towards interoperable models. This could lead to higher costs and low efficiency in the deployment of the new IT technologies in the broadcast environment. It could also lead to a loss of competitive advantage as users are unable to implement more flexible workflow designs which are required to meet the requirements of an ever-changing business environment.

Co-chairs:

  • John Footen, NTC, on behalf of AMWA assisted by Brad Gilmer, AMWA
  • Giorgio Dimino, RAI, on behalf of EBU assisted by Jean-Pierre Evain, EBU.

Who can join and contribute?

What are the tasks?

How will it work?

Use case analysis

Request for Technologies

Personal tools
contacts
news!