Sphere Digital Media Asset Management system is connected to MBT’s IP Data platform, Vertex. Vertex is the core system of MBT’s software.
The Vertex Data Platform manages data and the metadata of the media and integrates services to manage the automatic identification of the media on the storage units.
Based on a SOA architecture, the Vertex Data Platform allows all systems to manage information and content from every location where the media are stored.
The Vertex Data platform is based on an IP data bus, developed by MBT, which is a software architecture model where a shared communication channel facilitates connections and communication between soft-ware modules.
This makes software buses conceptually similar to the bus term used in computer hardware for interconnecting pathways
This technology allows therefore for all
the benefits of an open collaborative system.
Data and data flows are managed by the Vertex Digital Objects (DOM) server. This server uses MS-SQL Server as database for data archiving. This architecture allows to build a scalable solution around the customer’s operational and functional areas.
Vertex disposes of its own API that manages the communication between the Core System and external systems. The API server allows external software to access to the data bus. It has several features that can be used to manage all data. XML commands are sent in a TCP socket. It is possible to add, update or delete all Vertex data.
The structure uses inheritance and delegation concepts to define the data and to optimize the access and the scalability. Each “Media” has his own list of object elements that is related to physical files. These media can be put into assets. The cataloguing and classification of assets allows to navigate easily between media, for example using a tree view.
The Vertex Data Platform is composed of several object servers (big data oriented) in order to organize and manage a wide range of services so digital objects can be accessed in real time even if millions of media are stored, using a big data full search engine (elastic search).
The Workflow engine can be seen as a backbone connected to functional clients that are designed to work with media. This backbone has incoming resources on the input side. On the output side, it delivers the media that are ready to be published or to be broadcasted.