MDM IMPLEMENTATION TO REPLACE GPMS TITLE MANAGEMENT October
MDM IMPLEMENTATION TO REPLACE GPMS TITLE MANAGEMENT October 28, 2013
Legacy GPMS – Title Master Data and Rights Mgt. Area of Focus Title Master Data Management • Titles/Products • Descriptive Metadata • Release Dates Rights Management • Rights In/Rights Out (Data Mart) • Contract Management • Payments, Delivery GPMS Program has evolved to serve two functions: MDM and Rights Management. In order to meet the evolving business and technical needs/challenges, we propose to separate and replace the existing legacy functionality 2
Title Master Data Management GPMS Current Situation/Challenges Rights Management Situation: • GPMS integrates with over 60+ SPE systems as the enterprise Title Master system that provides reliable Title, rights, and associated metadata. • 250+ key SPE stakeholders are consulted about GPMS development to support 1500+ individuals and major workflows throughout SPE. Challenges: • GPMS is currently not capable of supporting increased automation and localized metadata for workflows across the business, including the expansion into International Productions and International Networks. • GPMS is between 7 -12 years old and is on old technology that presents vulnerabilities. • By not improving our system and functionality we are increasing inefficiencies and redundancies by driving groups to develop their own solutions. 3
Proposed Solution and Selected Software Solution Software Selection Implement a new MDM solution with greater flexibility, functionality, and efficiency to replace the existing custom legacy system and lower support cost. Down selected Riversand Orchestra Networks from a group of six recommended MDM vendors First Filter Vendor Shortlist 6 Vendors Second Filter Vendor Demos 4 Vendors ƒ Third Filter Vendor Proposals 2 Vendors SAP IBM SAP Orchestra Networks Teradata Riversand TBD Orchestra Networks Riversand IBM Rights Management Title Master Data Management 1 Vendor Riversand Orchestra Networks LOB Systems Additional Enterprise Benefit: MDM can be expanded out to support other data domains such as Customer, Talent, and Employee (Party) or can be integrated with the selected solutions of these respective areas 4 Contract Web methods ‚
Financial Summary Year One Project Costs Five-Year Summary and Payback Software: $600, 000 Five-Year Total Cost: $3, 267, 636 Hardware: $155, 520 Five-Year Total Benefit: $5, 784, 336 Internal Labor: $47, 880 Five-Year Net Benefit: $2, 516, 700 External Labor $300, 386 Misc. /Other: $0 TOTAL $1, 103, 786 FY 1 Project Benefits Hard $ Benefits $1, 304, 160 (cost reduction, cost avoidance, and operational efficiencies) TOTAL $1, 304, 160 Internal Rate of Return: 89% Net Present Value at 10%: $1, 418, 646 Payback in Months: 19. 32 Funding by Fiscal Year FY 14 $1, 109, 786 FY 15 $1, 617, 850 TOTAL $2, 727, 636 Depreciation: Ongoing Costs: $122, 744 ** Five-Year Benefit is a total of the Quantifiable Business and IT Benefits explained in the slides to follow 5
Business Benefits 6
Additional Qualitative Business Benefits Key business workflows supported: SPT Distribution: Sales planning & forecasting, competitive title benchmarking, expansion of worldwide digital clients (e. g. , Netflix), fulfillment, & business intelligence & analytics (BI &A) SPT Networks: Digital asset management in the Media Center, programming & scheduling, contract & rights management in GNET, fulfillment, & business intelligence & analytics (BI &A) SPHE Distribution: Sales planning & forecasting, worldwide HE JVs, expansion of worldwide digital clients (e. g. , i. Tunes, Amazon), development of new business models (e. g. , 2 nd screen, Ultra. Violet) fulfillment, & business intelligence & analytics (BI &A) Fulfillment & DBB: End-to-end order processing and fulfillment automation (including asset management, metadata transformation, & delivery), compliance with regulatory requirements (e. g. , UK product placement), etc. Corporate: Legal, Finance, Participations & Residuals New GPMS platform & functionality would enable: • Title deduplication and record creation • Mass metadata creation & update • Acquisition of 3 rd party metadata to augment existing GPMS titles and data • Exchange and sharing of LOB-created metadata with other stakeholders • Localized title, Alpha, & talent metadata • Expansion of Alpha model to include VAM and trailers • Audit of GPMS metadata to ensure business rule compliance • Creation of flexible data model to meet new business requirements (e. g. , multiple season & episode numbers) 7
IT Benefits 8
Competitive Analysis • What are other studios/corporations doing to address this issue? • Riversand or Orchestra Networks SPE • SPE Library, SPT Networks, 3 rd party competitive titles, and Alphas • ~370 K titles and ~160 K alphas currently; 50 K-75 K titles added annually • Integrated with 60+ systems • $2. 5 M • Orchestra Networks Paramount • Paramount Library – Active titles only (~8 K titles) • Integrated with <6 systems • ~$2 -3 M • SAP IPM and SAP Netweaver Warner Bros. Fox • IPM for MPM Set-up and Netweaver for Version management • Integrated with <6 systems • ~$55 -65 M • Informatica • Used for data aggregation from LOBs (not a title master) 9
Proposed Project Timeline 10
- Slides: 10