Architecture for Digital Asset Management

The challenge

Customer: Large Swedish listed company.

Mission: Create better control over the business’ digital assets.

Information: The customer had several local  Digital Asset Management (DAM) systems for managing digital assets and rights. None of these systems were suitable to scale up and make central. Therefore, a new DAM was procured. The procurement covered the product itself, but also the implementation of it as well as its operation. In addition to the purely technical aspects, the introduction lead to a significant change in the business processes.

The journey

Architecture for Digital Asset Management

– From the beginning, our focus was on evaluating how the various candidates in the procurement could live up to the customer’s requirements. Had the system they requested have the required capabilities, or did we need to venture deeper into the problem? There was also the need to harmonise the business’ functional requirements with the IT requirements (for example, architectural, non-functional, etc)

– Tagore specified feasible non-functional requirements because it was not certain which parts of the business would ultimately use the system. This meant uncertainty about, among other things, amounts of data and the number of users that needed to be managed.

– In order to avoid a major implementation, Tagore made a roadmap with division in applications for the various systems that would be integrated with the DAM system.