THRON

https://www.thron.com

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.

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.

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.

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.

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.

Client refers to the type of hardware or software device that can be used to access or control the DAM system.

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.

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.

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.

This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).

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.

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.

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.

Microservices are similar in nature to Service Oriented Architecture (SOA) with the key difference being that they can be deployed entirely independently of the platform that uses them. Microservices are usually prevalent in Digital Asset Supply Chain projects.

As with Service Oriented Architecture (SOA) some vendors have different opinions of what microservices are. Their response to this question allows you to understand if their definition concurs with your own. If you are not contemplating a Digital Asset Supply Chain project, large scale DAM implementation or one with many complex integration requirements, microservices may not be relevant to your needs.

If the vendor uses microservices, 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 microservices but do offer large scale asset processing capabilities via an alternative method.

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.

Some DAM systems can search the text content of document assets and that might be important for your DAM solution.

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.

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.

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.

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.

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.

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.

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.

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.

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?".

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.

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.

Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.

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.

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).

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.

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).

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.

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.

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).

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.

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.

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.

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.

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.

See previous question. Most DAM systems with multi-lingual support will provide it for 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.

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.