Tessa

digital asset management systems

Asset Management System

Tessa (‘asset’ backwards!) gives productions a pipeline that can track, automate, and organize movement of digital assets between artists. The artist is insulated from the complexity of the underlying data and processes – allowing them to focus on their creative tasks rather than worrying about where something is.

Tessa (‘asset’ backwards!) gives productions a pipeline that can track, automate, and organize movement of digital assets between artists. The artist is insulated from the complexity of the underlying data and processes – allowing them to focus on their creative tasks rather than worrying about where something is.

Tracks, automates and organizes

An asset produced in one site is often an input to the production of another asset in a different site. Tessa workflows help to ensure assets travel seamlessly between sites, departments and artists.

An asset produced in one site is often an input to the production of another asset in a different site. Tessa workflows help to ensure assets travel seamlessly between sites, departments and artists.

Supports multi-site Pipelines

A shot or asset often requires collaboration between artists creating components at different locations around the world. Tessa provides management of these assets, ensuring the right components are in the right location at the right time.

A shot or asset often requires collaboration between artists creating components at different locations around the world. Tessa provides management of these assets, ensuring the right components are in the right location at the right time.

DEFINES RELATIONSHIPS BETWEEN ASSETS

Tessa’s real power comes from having defined relationships between particular assets. We can use these relationships (in conjunction with a set of rules or criteria) to keep everything up to date and automate the creation of asset versions when required.

Tessa’s real power comes from having defined relationships between particular assets. We can use these relationships (in conjunction with a set of rules or criteria) to keep everything up to date and automate the creation of asset versions when required.

Automates the creation of assets

‘Streams’ define groups of assets that will eventually be packaged into a final product. Syncing of streams propagates the work done between isolated departments, maintaining the flow of assets across departments. An approval system acts as a gatekeeper between department streams, giving artists control over which assets will be made available to other departments.

‘Streams’ define groups of assets that will eventually be packaged into a final product. Syncing of streams propagates the work done between isolated departments, maintaining the flow of assets across departments. An approval system acts as a gatekeeper between department streams, giving artists control over which assets will be made available to other departments.

Front-end Python and C++ API

A C++ API featuring a 3D description library is supported by a versatile Python front end.

A C++ API featuring a 3D description library is supported by a versatile Python front end.

MULTIPLE BACK-END MICROSERVICES

Re-designed in 2013, a micro-services framework (AMANDA) forms the backbone of MPC’s pipeline. Modular, scalable components can be replaced independently – allowing the R&D team to keep artists at the forefront of new and better technologies.

Re-designed in 2013, a micro-services framework (AMANDA) forms the backbone of MPC’s pipeline. Modular, scalable components can be replaced independently – allowing the R&D team to keep artists at the forefront of new and better technologies.