The DAM Playbook
This vendor does not appear in the in the DAM Playbook.
DAM 10 Core Accreditation
This vendor is not 10 Core accredited.
Contact NameDavid Clemenceau
More than 15 years of expertise to serve your image banks projects
Opsomai is a leading provider of Media Asset Management platforms, and the French leader of video banks, thanks to its Web 2.0 software Opsis Media, that helps video archive holders, production companies and large organizations to leverage the value of their audio, image and video assets, through online sale of archives, news sites, VOD services, corporate communication, Web TV… Integrated into the client’s technical infrastructure or run on Opsomai’s cloud platform, Opsis Media offers a standard package for digitalization, indexation, archiving, streaming and publishing, that meets the needs of both audiovisual professionals and medium-sized or large companies.
Thanks to its team of experts and to a strong network of partners, Opsomai can handle any project of multimedia catalog development, from tapes and pictures digitalization, to online programs sale, through derushing and indexing. When you choose Opsomai, you first choose a partner that will support you in a fast evolving technical domain, whether it has to do with video formats or diffusion modes on the Internet. You also choose a software, Opsis Media, which integrates these evolutions, thanks to the support of all the video, image and sound formats, and to software interfaces with all the broadcasting channels: video sharing websites, social networks, mobile applications, connected televisions…
Major actors have chosen Opsomai’s solutions to safeguard and distribute their assets: Gaumont Pathé Archives, INA, Bouygues Construction, COLAS, ENGIE, RATP, SNCF, CNRS, French Economy and Finance Ministries, French Federation of Football, Paris Museum of Natural History… Based in Paris, Opsomai started its international development 5 years ago, with already several installations abroad, including Asian and African countries.
Company Turnover Category
The turnover of the vendor can give an indication of their size. US Dollars is used as common currency to allow comparisons. Note that turnover is not necessarily any indicator of financial stability but as part of any procurement due diligence you are obliged to carry out by your organisation, any vendors who have not agreed to show their turnover here might be required to do so if subsequently appointed.
This is the actual turnover of the vendor in US Dollars.
Percentage of Revenue From DAM Software
A vendor might have a large turnover and many employees, but their DAM software division is a very small element of what they offer. If a large proportion of their revenue comes from DAM solutions (licenses, support, hosting, consulting etc) then this may mean they are more specialised, but also there are risks to their overall financial stability if there is a downturn in the DAM software market.
Number of Full-Time Employees
Along with turnover, the number of full-time employees gives an indication of the size of the vendor. Note that although a firm might have many employees, not all of them might be dedicated to developing DAM solutions, so this cannot be relied on in isolation.
Product NameOpsis Media
Latest Version Number3.1
Date Of Last Release01/07/2017
Online trial linkhttp://demo.opsismedia.com
Company LinkedIn URLhttps://www.linkedin.com/company/105767/
Company Facebook URLhttps://www.facebook.com/OPSOMAI
Clients & Customers
- Bouygues Construction
- CAMSTL (Timor Leste video archives)
- CNES (French Space Agency)
- CNRS (French Center for Scientific Research)
- COLAS (construction)
- Eiffage (construction)
- ENGIE (gaz distributor)
- French Economy and Finance Ministries
- French Federation of Football
- Gaumont Pathe Archives
- INA (French TV and Radio archives)
- National Rugby League
- Paris Museum of Natural History
- RATP (Paris metro)
- Regional Council of Ile-de-France
- RTC (Cap Verde's Radio and Television)
- SNCF (National railways)
If the vendor operates through a sales channel they may use intermediaries who have regional focus or additional specialisms in a given vertical market.
This refers to the type of licence the DAM system software is supplied under. Proprietary means that the developer restricts access to the source code (the instructions used to generate the software). Open source means that the developer provides full access to the code so you can modify it yourself. Split model is hybrid and means they may offer both options with some restrictions removed (or added) depending on the model chosen. If split is selected, it is advisable to verify the differences with the vendor.
Source code is provided to clients for internal use.
Use of Open Source Components
Many DAM systems use freely available open source components to deliver key functionality. The products themselves may not be open source, however. This question will help to identify to what extent they are open source.
- Some open source components used, but core product is not open source
Open Source Component Usage Notes
Open Source database (PostgreSQL), search engine (Solr), and media processing tools (ffmpeg, ffmbc, ImageMagick…).
Software Delivery Methods
- Installed (On-Premise)
Client refers to the type of hardware or software device that can be used to access or control the DAM system.
All recent browsers are supported, without plug-in installation if HTML-5 video is supported.
Responsive design user interface designed for iOS and Android devices.
Server Operating Systems supported
This only applies for installed or hybrid DAM systems and refers to what types of OS they can be run on. This question is less relevant for DAM systems where a third party will be hosting it for you.
Server Operating System Notes
Linux CentOS or Red Hat recommended
The type of web server software that the DAM system can operate with. Not all DAM systems use a web server and for pure SaaS products the question is irrelevant. If you either want SaaS or non-web DAM systems, do not choose an option.
Software Development Technologies Used
This means the programming language or development technology used to implement the DAM system. This question is more important for open source software or if you have IT policy restrictions that require you to use (or not use) some technologies. It may not be relevant if you require a hosted DAM and never intend to host the system in-house.
Server Technology Notes
The Database that the DAM system uses. All DAM systems require some kind of storage for asset metadata and they are usually based on an existing technology - but that may not always be a conventional database. If the DAM will be hosted by someone else (e.g. SaaS/Cloud) this question may not be relevant.
Legacy MySQL support
This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).
Search Technologies Notes
Biggest managed database: 35m assets (INA)
Service Oriented Architecture
Service Oriented Architecture (SOA) means the vendor's product uses a modular architecture where each core DAM function is delivered as a service which can be separated out independently from other functions. It is important for large-scale Digital Asset Management implementations or more complex integration requirements.
Service Oriented Architecture Definition
Some vendors have widely differing opinions of what Service Oriented Architecture means. Their response to this question allows you to understand if their definition concurs with your own. If you are not contemplating a large scale DAM implementation or one with many complex integration requirements, SOA may not be relevant to your needs.
Basically, we provide SOAP Web Services in order to search and retrieve documents and their associated media assets, and to ask for media processing tasks, as transcoding and splitting.
Unique SOA Services
If the vendor uses a Service Oriented Architecture, they should be able to identify a number of unique services that are isolated from each other. Note there is overlap between with question and the one about scalable asset processing. Some vendors do not have an SOA but do offer large scale asset processing capabilities.
- Asset Media Processing
This describes the search strategies that can be used to find assets. If you do not understand any of them, leave the options de-selected. Most DAM systems should support at least keyword search at a minimum.
- Faceted Search
- Linked Asset Search
Query extensions based on thesauri
Index/Search Text Content Of Documents
Some DAM systems can search the text content of document assets and that might be important for your DAM solution.
Document Text Indexing Notes
Text documents (Office, PDF…) are processed with an OCR tool for indexation.
Audio and Video assets can be automatically processed by our partner Authôt (http://www.authot.com
) for sound track transcription.
Embedded metadata support (reading)
Embedded metadata refers to information stored within asset files which can be searched from the DAM system. There are different standards for this type of metadata. Some image cataloguing software like Adobe Lightroom will write this data to asset files and a device like a camera may capture details also such as GPRS coordinates where an photo was shot. XMP metadata is often used with other types of files such as InDesign or PDF. If you are unsure whether this applied to you, do not check any options.
Embedded metadata support (writing)
See the reading question above for more details on what embedded metadata is. This question refers to whether embedded metadata can be written back to files if edited within the DAM system.
Embedded metadata support notes
ID3 tags, Quicktime and MXF embedded metadata support.
Controlled Vocabularies are predefined lists of search terms. They can be realised in many different ways but the common factor is the user picks from a restricted selection rather than enters a keyword. Most DAM systems will usually support both controlled vocabularies and keywords.
Controlled Vocabulary Notes
Controlled Vocabulary can be either hierarchical or flat. In standard, we propose: concepts (hierarchical), places (hierarchical) and persons (synonyms only), but CV can be added for specific needs: subsidiaries, building materials, locomotives…
User Defined Metadata Fields
The ability to configure metadata your own metadata fields is important for DAM systems so you can assign a dedicated field for certain items of information rather than using a generic classification method or one of the vendor's own standard fields.
Cataloguing Interface Options
When cataloguing assets with custom fields, some metadata will be controlled selections, others will be free text. There are further choices like date fields, file attachments etc.
- Text field
- Text area (narrative)
- Drop down menu
- Combo-box (multi-item selection)
- File attachment
Cataloguing Interface Notes
Verify how the vendor has implemented a given cataloguing interface control. It is preferable if they can demonstrate with examples of how they have implemented interface options for cataloguing and metadata entry.
Cataloguing interfaces are usually associated to fields types, like calendar pop-in for dates, but specific cataloguing interfaced can be designed.
Thesauri based cataloguing can use hierarchical browsing tool.
Business Intelligence & Reporting
Asset Usage Records
To enable reports to be generated, DAM solutions must retain records of asset usage, including searching, download and editing of records. The reporting should include the user who carried out the activity and the date/time it occurred.
Asset Usage Notes
Every user action is logged along with the user ID and his geographical localization.
Statistics can be displayed for connections, queries, views, downloads… Statistics are displayed online through graphics, but the corresponding raw data table can also be exported for external processing.
A detailed audit trail that logs every user action in a central record is useful to gain insight into user behaviour. Comprehensive audit trails allow DAM system users to produce reports that address their unique needs.
Audit Trail Notes
Actions can be filtered by users. So, it is possible to get all the actions of a given user.
A range of built-in reports that you can quickly generate is useful to answer common questions such as the "what is our most popular asset?".
- Most popular assets by download
- Download activity over a given period
- Login activity over a given period
- Popular search terms
Media viewing statistics also available.
Dedicated/Scalable Proxy or Derivative Asset Generation
Nearly all DAM systems will generate thumbnails and previews of media, including more dynamic types like video or audio. Some products use a separate server to do this which usually makes them more suitable for large scale asset ingestion and processing.
Dedicated/Scalable Proxy or Derivative Asset Generation Notes
The included proxy and derivative asset rendering server is controlled by Opsis Media, through its Workflow Manager. It can be physically installed on the same server as the main system, or on a dedicated server or servers cluster, remotely controlled by our Workflow Manager.
Multi-Page Document Asset Previews
If you deal with document oriented assets, having a solution which can generate multi-page previews (and also zoom in on them) can save the hassle of downloading a file only to discover it is not the one you need. For assets with very similar content, this can be a useful feature.
Multi-Page Document Asset Preview Notes
Multi-page documents can be previewed and searched, even scanned PDFs.
Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.
- Image re-sizing
- Image cropping
- Format conversion
- Flip images
- Rotate image
- Batch manipulate groups of assets
Image Manipulation Notes
Some DAM systems may allow video assets to be converted or modified. If that is a potential requirement for you, specify those features which are likely to be needed. EDL = Edit Decision List and refers to providing in/out points when editing video footage.
- Format conversion
- EDLs and editing features
- Timeline metadata
- Batch operations on multiple video assets
Video Manipulation Notes
Audio transcription (with our partner Authôt), Subtitling, sequences extraction without transcoding, storyboard generation with scene changes detection, DVD-Video ISO image generation, video generation from still images…
Importing metadata is an important feature if you have either legacy assets or metadata is generated using some other tools (for example a spreadsheet). Not all systems offer this, but usually if the feature is not available, the vendor will be able to carry out batch importing for you via professional services (note: this will usually incur a cost, unlike a built-in capability).
Metadata Import Formats
This question only applies if the vendor has features to import metadata. There are common formats like CSV, XML and Excel which DAM solutions may support. If this is a requirement you are likely to make frequent use of, it is essential to verify whether the product supports the formats you typically work with.
- CSV (or any delimited file)
Metadata Import Notes
A standard metadata import model is proposed. It can be customized to meet specific clients' needs.
As well as importing metadata, sometimes it is important to be able to export sections of it to conduct further analysis in third party applications. Not all products support this, but usually it will be possible to request the vendor provides an export via professional services (although a fee may be charged).
Metadata Export Formats
This question only applies if the vendor has features to export metadata. There are common formats like CSV, XML and Excel which DAM solutions may support. If this is a requirement you are likely to make frequent use of, it is essential to verify whether the product supports the formats you typically work with.
- CSV (or other delimited file)
Metadata Export Notes
User customizable exports, with fields selection and ordering.
API means Application Programming Interface and allows third party software to control a DAM system. If you intend to integrate your DAM with another existing solution then you need to choose the API protocol that is compatible with that.
REST AND SOAP APIs are available for searching and retrieving documents and their associated media assets, and for asking for media processing tasks, as transcoding and splitting.
Hooks are related to APIs but are initiated by the application rather than by an external application making the request. Hooks allow other actions to be initiated based on events, for example if a user downloads an asset, an action can be commenced to notify another application that this has taken place (along with the ID number of the asset, date/time etc).
Hooks Targets Supported
In most DAM applications that support them, hooks are initiated as web requests, so the system will call a given external URL and provide some parameters. Some solutions also support initiating scripts or applications which can run on the server where the system is hosted.
- Web hooks
- Scripts (using an existing scripting feature, if it exists)
If the vendor claims support for hooks, check how they define them and see if their interpretation concurs with your own. A reasonably detailed explanation along with citations/links should be given here.
FTP watch folders, external feeds recordings and post-processing, Unix Shell scripts…
Many DAM solutions will now allow assets to be stored on the server of Cloud storage providers. This allows asset files to be distributed and/or integrated with other solutions. Some third party services use generic protocols like FTP, others are proprietary.
Storage Integration Notes
Media can be stored on any external storage that can be accessed through standard protocols as FTP, SFTP, SCP…
Scripting & Plug-Ins
Some advanced DAM solutions have a scripting capability that allows users or third parties to add functionality which the vendor did not originally envisage. Usually programming skills will be required to use this, but some tools have visual interfaces also.
In addition to scripting (or sometimes instead of), some DAM solutions will have a plug-in architecture that allows third party developers to extend the core platform.
If you need to integrate with an existing corporate authentication service then this option will be important for you.
Use of SSO authentication for several clients and of Shibboleth (SAML V2) for some universities and research centers.
Multilingual Application Interface Support
The interface means the controls to use the DAM system. This is different from the metadata support which is usually entered by end users when cataloguing assets.
Multilingual Metadata Support
See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
Multilingual Support Notes
Khmer (Cambodia), Vietnamese and Portuguese also supported.
Controlled Vocabularies can be translated in order to generate automatically a partial translation of any imported asset metadata.
File versioning refers to the digital media associated with an asset record. This is usually the minimum requirement for a DAM system to claim support for versioning assets. See also responses to the related question about metadata versioning below.
Metadata versioning is separate from the files associated with assets. Many DAM solutions will track updated digital assets but only retain a single current version of the metadata. Since metadata is likely to be edited many more times than assets get replaced, this can be an important point to check.
Independent Metadata And File Versioning
This questions assesses whether the solution allows versions of either the file or metadata to be reverted independently or if both are linked to a single shared version instance.
Version Control Notes
Files versions are automatically categorized: original, intermediate version N, master version, browsing version…