Blue Lucy
Profile Index
Vendor Details
Contact Name
Sales SupportCompany Profile
Blue Lucy is a software development leader in the field of media production and operations. The software capability is supported by business consulting and programme implementation to ensure the realisation of business benefits in all projects. We produce business orientated software tools for content asset management, workflow orchestration and video processing; enabling broadcasters and content owners / producers to confidently deploy software systems which meet the business drivers of today, and tomorrow.
The highly innovative software tools are enablers for broadcast operators and media companies to exploit and monetise content for multi-platform delivery. Our technology represents a fundamental shift in the provision of technology for video production and offers a step change in flexibility and cost model for content owners and media operators. We have a well-founded understanding of the business of production, broadcasting & content publishing as well as an appreciation that software systems support, not dictate, business and operations.
We take a business centric view and know that software provision without an operational business case, without rounded design and integration rarely realises the forecast benefits. We approach projects by first helping businesses understand the vision, then manage the entire realisation process from software build to transition to operational service. The Blue Lucy approach is a complete approach with demonstrable success in delivery.
The highly innovative software tools are enablers for broadcast operators and media companies to exploit and monetise content for multi-platform delivery. Our technology represents a fundamental shift in the provision of technology for video production and offers a step change in flexibility and cost model for content owners and media operators. We have a well-founded understanding of the business of production, broadcasting & content publishing as well as an appreciation that software systems support, not dictate, business and operations.
We take a business centric view and know that software provision without an operational business case, without rounded design and integration rarely realises the forecast benefits. We approach projects by first helping businesses understand the vision, then manage the entire realisation process from software build to transition to operational service. The Blue Lucy approach is a complete approach with demonstrable success in delivery.
Contact Telephone
020 8878 5313Contact Email
webcontact@bluelucy.comYears Trading
6Company Turnover
This is the actual turnover of the vendor in US Dollars.
10,000000Office Locations
- London
Product Name
BLAMLatest Version Number
V3.0Date Of Last Release
31/03/2015Documentation URL
http://bluelucy.com/downloadsCompany LinkedIn URL
https://www.linkedin.com/company/2599923?trk=vsrp_companies_cluster_name&trkInfo=VSRPsearchId%3A53618751432795187742%2CVSRPtargetId%3A2599923%2CVSRPcmpt%3Acompanies_clusterLicensing
Licensing Model
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.
- Proprietary
Licence Notes
Perpetual and lease licence models.
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.
- No open source components used
Hosting
Software Delivery Methods
- Hybrid
Technology
Client
Client refers to the type of hardware or software device that can be used to access or control the DAM system.
- Web client
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.
- Windows
Web Server
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.
- IIS
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.
- .NET
- C++
Database Technology
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.
- SQL Server
- MySQL
Search Technologies
This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).
- SQL Server
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.
- Yes
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.
- Metadata
- Storage
- Asset Media Processing
- User Authentication
- Workflow
Search
Search Features
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.
- Keyword
- Folders
- Filters
- Faceted Search
- Linked Asset Search
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.
- Yes
Metadata
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.
- XMP
- EXIF
Controlled Vocabularies
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.
- Yes
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.
- Yes
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
- Radio
- Checkbox
- Date
- File attachment
- Numbers
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.
- Yes
Audit Trail
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.
- Yes
Built-In Reports
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
- Most active users by uploads
- Most active users by downloads
- Average number of search results returned over a given period
- Asset search to download ratio
- Download activity over a given period
- Login activity over a given period
- Popular search terms
Asset Processing
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.
- Yes
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.
- Yes
Asset Manipulation
Image Manipulation
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
Video Manipulation
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
Linear (video tape) ingest.
Integration
API
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
- SOAP
Storage Integration
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.
- Amazon S3
- Amazon Glacier
- FTP
- Microsoft Azure Blob
- SFTP/SSH
Scripting & Plug-Ins
Scripting Capabilities
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.
- Yes
Plug-In Support
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.
- Yes
Authentication
Authentication Support
If you need to integrate with an existing corporate authentication service then this option will be important for you.
- Active Directory
- LDAP
Multi-Lingual Options
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.
- English
- Arabic
- Russian
- Polish
- French
- Spanish
- Italian
- German
- Dutch
- Norwegian
- Swedish
- Finnish
Multilingual Metadata Support
See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
- Yes
Version Control
File versioning
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.
- Yes
Metadata versioning
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.
- Yes
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.
- Yes
Profile Last Updated: 28/05/2015