FIMS projects are driven by business needs. Users’ input to the Business Board defines the new objectives and priorities.

Who are the users?

Everybody who benefits from the FIMS compatible products from a business point of view. Therefore, broadcasters, media producers, system integrators, and manufacturers are all potential users.


Capture --

The Capture Service Interface creates one or more related content items from video and audio sources. The service may involve a human operator to start and stop the operation. It builds on the Transform Service interface, but is constrained to support isochronous stream-based input, for example an HD-SDI stream.

In the case of audiovisual signals, the service can simply encode and wrap these into a file or can encode and wrap them with multiple formats into multiple files and put them in several places. The service could even perform an AV Process such as resize, burn-in, and LUT before encoding. In a sense, the Capture Service by nature includes elements of both a Transform Service and a Transfer Service within it.

The approved specification and reference files are located on the FIMS GitHub

Transfer --

The Transfer Service Interface copies one or more files to another place (or to several places). This document permits five different transfer protocols, HTTP, HTTPS, FTP, SFTP and FILE. A Transfer Service may implement one or more of these protocols, but a Transfer Service shall implement at least one protocol for an input and an output (although these do not need to match).

The approved specification and reference files are located on the FIMS GitHub

Transform --

The Transform Service Interface operates on media content to transform the content or a list of content elements from a source media format to a target or a list of target media formats. It builds on the Transfer Service interface, and adds some element of transformation to the input.

The approved specification and reference files are located on the FIMS GitHub

Content Repository --

The Content Repository Service Interface is for storing, retrieving and managing media assets within and across heterogeneous content storage systems. The scope of this service is tightly defined as dealing with persistence of a core set of asset types and a minimum set of associated metadata. Future projects will allow for additional asset types and extended metadata schemas. The service will be implemented in such a way as to allow for repositories of varying performance, scale and capability.

This project is in final review and approval phases.

Quality Analysis --

The Quality Analysis Service Interface will expose capabilities oriented around analysis and reporting of asset properties. Profiles will allow for specific analysis criteria and reporting thresholds to be pre-set within the system, and targeted towards specific jobs. Output of the service should extend the FIMS datamodel in such a way as to be persist-able in the Content Repository Service, and usable by higher level business logic and/or downstream FIMS services.

This project is currently in development.

Automatic Metadata Extraction --

The Automatic Metadata Extraction Service is important to the industry for several reasons. Richer and more accurate metadata makes search and retrieval easier, providing significant economies of scale to facilitate asset repurposing.

This project is currently being defined by the FIMS Business Board.


Test Harness

The Test Harness for FIMS is designed to help vendors test their implementation of a FIMS compliant service. Whether a vendor is implementing a FIMS service (transfer, transform, etc.) or orchestrating a workflow comprised of services that have implemented a FIMS compliant service, the ability to perform verification without having to actually integrate with a vendor is highly desirable. An independent test harness will allow vendors to easily test their FIMS implementations for interface conformance and behaviors in a repeatable manner for the purposes of development and regression testing.

For more information on the Test Harnesses for FIMS, see the FIMS wiki

REST Implementation

A new project has started within the FIMS Technical Board to provide a REST implementation of FIMS. The purpose of this project is to specify rules for the provision of FIMS services based on the normative FIMS XSDs that:

are RESTful and use HTTP directly rather than being tunnelled in SOAP messages through HTTP;
have both XML and JSON representations.

The use of REST and/or JSON is complementary to and in addition to the capabilities already specified and available in the published FIMS specification.

This project is in final review and approval phases.

AMWA website EBU website