#SummitNow Digital Asset Management with Alfresco: Buongiorno case history November 5 th 2013 Silvio Cabiati

#SummitNow Agenda Buongiorno company profile About me Why Alfresco? Metrics Current DAM flow implementation CMS in 2014

#SummitNow Buongiorno Company Profile Buongiorno is a multinational leader in the worldwide mobile ecosystem for developing and managing paid apps and content that help consumers get greater enjoyment from mobile devices.

#SummitNow Buongiorno Company Profile After 2 major M&A deals in 2011 (acquisition of Dada.net and spin-off of Lumata), Buongiorno is a company: Specializing in mobile entertainment, focusing almost entirely on a B2C approach, based on strong product management, technology and direct marketing capabilities combined with a partnership attitude with mobile network operators With a team of approx. 700 professionals, based in 15 countries, conducting business in more than 20 countries around the world Generating 2012 revenues of ~€220 mn with an EBITDA of ~€27 mn Euro: 55% in Europe, 30% in the Americas and 15% in the rest of the world Running a blend of traditional, feature phone oriented, and of new, rapidly growing smart phone and tablet oriented, products With a sound balance sheet and a proven track record in delivering results, profits and cash flow

#SummitNow Buongiorno can reach more than 2 bln people through 100+ telecom operators Buongiorno Company Profile

#SummitNow About me Silvio Cabiati PT IT Project S.p.A.

#SummitNow Why Alfresco: Content storage: 2000 – 2010 B!3A Content Repository is an integrated, multi-channel media storehouse that provides an easy to use, object oriented content database system that stores rich media data in a flexible and hierarchical structure, much like the folders on ordinary personal computers. Both simple files, of any type, and structured content, in the form of predefined objects, can be stored in the repository. Known limits and issues were: Every country has his own content repository to be maintained and managed No Licensing control No Multilanguage Slow, unstable and not user-friendly user interface Limited Search functionalities Content Providers manual import (80%) No Automatic format transcoding No Content formats standardized among countries Tricky export functionalities Minimum user-profiles management No process control on production, import and publishing Proprietary Technical Environment

#SummitNow Content storage: New CMS aim: Managing contents, services and user agents in a brand new, efficient, user friendly, powerful and scalable platform based on Alfresco Main benefits: User-friendly (“Desktop-like”) user interface Unique content repository for all the countries (no duplication of contents) Multilanguage Advanced search functionalities Content Providers automatic import Automatic format transcoding An enhanced user agent management Simplified export functionalities Advanced user-profiles management Licensing integration (country/biz clearance control) Workflows (efficiency, process control) Why Alfresco: main benefits

#SummitNow Enhanced user interface Desktop like environment built in ext_js Multitasking

#SummitNow Content repository Licensing management and indicator Live previews Multilanguage Drag’n’drop

#SummitNow Advanced search functionalities Search in all metadata fields Multiple conditions Export results

#SummitNow User management permission by user, group, country, role, business line more than 70 different settings available

#SummitNow User agent management Dedicated tool Semi automatic UA creation Filtering by device specs

#SummitNow Workflows In order to manage contents four main workflows have been developed Ingestion workflow (manual, automatic) Format workflow Licence workflow Takedown workflow

#SummitNow Workflows

#SummitNow Catalogs multilanguage licensing definition adult level validation

#SummitNow Metrics Live services: 45, in 15 countries User agents available: approx 4200 Active users (platform GUI): 280

#SummitNow

DAM lifecycle We can identify 4 main steps ingestion process thru ingestion workflow catalog update publishing contents on front end side object delivery thru OTA delivery

#SummitNow DAM lifecycle Content providers thru ftp are in charge to load data (binaries and feeds) into their dedicated folder; an ingestion process starts and all the deliverables are created in repository. When deliverables are generated they can be added to an existing catalog both manually or automatically.

#SummitNow DAM lifecycle When a catalog is updated, at a given time some scheduled processes perform a set of REST calls in order to propagate changes on front end side in order to put at disposal new contents to final users for purchase purposes. When a download is requested, B! OTA calls are performed in order to complete the flow.

#SummitNow DAM: Ota Delivery – Ota Server Over the Air (OTA) is a standard for the transmission and reception of application-related information in a wireless communications system. ( Open Mobile Alliance, Download- OTA-v1_0. )Open Mobile Alliance B!3A manages OTA oriented services through different channels (WAP, Web, Pull/Push, Subscriptions, IVR, IVVR, etc.). The OTA Delivery Platform integrates two objects in the Content Repository, the OTA object and the User Agent object, with the OTA servers in order to prepare and deliver OTA objects to consumers’ handsets.

#SummitNow Android UA Content Repository (CMS OTA Server UA HTTP header mozilla/5.0 (linux; u; android 2.2; it-it; galaxy_tab build/master) applewebkit/533.1 (khtml, like gecko) version/4.0 mobile safari/533.1 HTTP request from the UA browser Identify Requested Object and return corresponding OTA User Agent Recognition (com.be3a.useragent) UA search Found? Yes No UA not found UA HTTP header Identify Android Family No Found? Getting default OTA object AN _Default AA _GTs5570 API Level Families apilv10,aplv9 Identify Android API Level from http header, using regular expression The table of corresponding versions are stored on jmailer_inter Founded? Yes AA _apilv10 No Founded? Yes AA _apilv9 No Yes Getting OTA object based on family Using major version of the corresponding API level DAM: Ota Delivery – Ota Server

#SummitNow Alfresco in 2014 In order to improve efficiency of the system in 2014 we’ll plan to Improve search results using a SolR external pool A better cache management thru an external pool; scouting in progress An enforced FTP process

#SummitNow DATABASE ALFRESCO IBATIS SOLR SSO GUIOTA SERVERREST API RMI API B! CUSTOMIZATIONS (Be3aAPIs,Workflows) CMS 2014 implementation

#SummitNow Thanks for your attention!

#SummitNow