Delivering content through the Cloud: A review of WVPT s operational needs as a baseline for a group distribution services offering

Transcription

1 Delivering content through the Cloud: A review of WVPT s operational needs as a baseline for a group distribution services offering Sony Electronics Professional Solutions Group September 17, 2013 Rev B

2 I. Introduction Casting through the cloud: Produce once edit/brand/deliver many! This brief will act as a catalyst in confirming the requirements for the WVPT, Harrisonburg, VA, a PBS broadcasting group member. This brief will also outline the unique elements and strengths Sony can bring to a cloud-based group distribution model: MBEMS, cloud storage: Ci, optical storage: ODA; a history of content creation and distribution; and the Sony brand. The first part of the brief which outlines the scope of services needed to successfully deploy a broadcast paradigm for WVPT, is intended to be confirmed by WVPT before cost modeling is undertaken. The second part of this brief outlines the operational elements and some commercial considerations in the provisioning of group distribution services for WVPT, other regional Virginia stations aligned with the same out-sourcing objectives as WVPT, and act as a basis for the myriad of other PBS stations through the US that are not currently aligned with any other group distribution services model. The following outsourced services requirements for WVPT are the offshoot of discussions held at WVPT in July with David Mullins, GM; Tony Mancari, COO; John Harper, Engineering Manager; and George Lilly, Creative Services Manager. From a broader sense, these requirements can be seen as generic to PBS stations overall with some regional exceptions, i.e.: live news, greater storage archive, etc. The intent of any commercial services model undertaken by Sony would be to build an infrastructure that can be expanded and scaled cost effectively while at the same time be agile to respond to a rapidly changing broadcaster environment. Additionally, the final model needs to provide value to the WVPT in a way only Sony can with its broad range of product offerings indigenous to current broadcaster demands, i.e.: Media Backbone Enterprise Management Systems, Ci cloud offering, System Watch monitoring systems, Professional Solutions and a rich catalog of supporting hardware and software. An overall high-level pictorial description of the proposed model is included as Appendix A. The overriding theme of this services model would be to capitalize on the elegance of a file based distribution model via casting through the cloud: Produce once, edit/brand/deliver many! II. Outsources Services Requirements for WVPT The following services requirements have been identified through discussions with WVPT as critical to their operational business model and can be seen in a broad sense to cover a typical PBS station s operational needs in general: A. Content Acquisition 1. In bound PBS satellite delivered content (HD Legacy, Create, V-me and World streams) is via AMC 21 Ku-band transponders: PBS RT (real-time) is Mpeg 4 six HD, and seven SD feeds converted back to baseband; PBS NRT (non-real time pre-prepped MOC files) feed is Mpeg 2 MXF (35 Mb HD LONG GOP, SD 8 Mb LONG GOP). AMC 1 PBS C-band clear feed is utilized to back up weather related events for AMC 21. 2

3 2. HD01, 02, and 03 are all 24 hour feeds, HD02 is a time zone delay so same programming schedule repeated 3 hours later with same media. As PBS begins migrating more and more to NRT rather than RT delivery except for live news feeds and last minute timely specials, probably would see more and more NRT handling the delivery. 3. A future 100 Mbit PBS statewide fiber network delivered via a Tier 1 Virginia based provider is being contemplate as a managed service GigE ring interconnect between Virginia PBS stations in Roanoke, Richmond and WVPT. Future plans call for PBS content delivered via 100 Mbit PBS terrestrial network with v-sat backup subsequent to State wide analog microwave system in place; needs to continue operations. 5. Ad-hoc Beta SP tapes from external sources, thumb/hard drives, and content delivered to the station FTP site in various formats requiring transcoding to a common format. 6. NRT PBS delivered underwriting interstitials/promos. 7. Minimal live programming though the capability for live-to-tape when warranted. 8. Future capabilities for state and public cloud content acquisition. B. Content Management and Operations 1. The station will run a seven (7) day advanced window of program automation and content storage on redundant cache servers located at the station. These servers will be populated with content from the AMC satellites via the NOC to the cloud (Ci) along with other Ci contained content. See Table One. 2. Integration of legacy content presently stored on Sea Change servers, ~52 Tb. 3. AVID/FCP edit systems to utilize cloud-based storage (possibly Adobe addition). 4. Automated transcoding, quantity of real-time channels TBD user selected profiles. 5. Traffic system (Protrack legacy). 6. MAM system (Myers legacy). 7. Automation system (TBD). 8. Automated QC of managed content (manual where appropriate). 9. Nine to Ten (9-10) Managed satellite receivers (Ericsson RX8200 family) at the NOC and locally at the station node. 3

4 10. Automated workflow including content creation, QC, storage, archive, system wide monitoring and distribution including client approvals (i.e. for underwriting, etc.) 11. Local cache server with a capacity of seven (7) days advanced storage. 12. Portal for external, third party produced content with transcode capabilities. 13. System architecture to provide for four discrete (4) channels of content creation, management and distribution (i.e. WVPT-HD, Create, World and V-me) throughout the programming and delivery chain. 14. Agreed upon legacy content from the current 52 Tb WVPT archive will be scavenged to either Ci or NOC based ODA. 15. Graphics files created locally utilizing cloud based applications including legacy formats with Photoshop elements. 16. Web enabled local user dashboard for human interaction and control. 17. Ability to QC, prep and ingest content at the local station/node when necessary. 18. Content channels to be encoded locally, branded and integrated with EAS systems for transmission. 19. Develop a common archive for ~ 50 stations in the cloud so only one copy of the show is needed plus backup, rather than 50 copies. Table One: Current Content Management Content Element Size Time Frame Format Storage WVPT :30 Media Promo 130 Mb 3:14 between each 35 Mbps Near-line Cache hour long segment MXF Single PBS HD NRT file 32 Gb - 35 Mbps Near-line Cache Single PBS SD NRT file 8 Gb - 35 Mbps Near-line Cache Typical PBS play-to-air TB Play-to-air 35 Mbps Near-line Cache server Typical PBS station near line TB Near-line 35 Mbps Disc/LTO/Tape WVPT SD archive 44 TB - 8 Mbps Spinning Disc MXF WVPT HD archive 60 TB - 35 Mbps Spinning Disc MXF WVPT Future cache storage TB 7 days of programming 35 Mbps MXF Near-line Cache 4

5 C. Transmission and Distribution 1. The local station will be considered as a node on the Sony delivery network and will have secure web based user portals for the following cloud based applications: Graphics (vendor TBD), Edit (Avid and FCP interfaced to MBS and possibly Adobe). Automation and Traffic applications will run concurrently from the NOC (or possibly virtualized in Ci) and mirrored at the station node. 2. The system will be capable of controlling and delivering four (4) separate content streams throughout the signal chain starting at the Sony NOC through to WVPT transmitters and translators. Web/mobile based streams will be discrete formats specific to the medium, post node switcher. 3. Content delivery from the cloud to station rack cache will be via redundant and diverse Tier 1 fiber circuits (100 Mbps/GigE GigE pending further data analysis) from a local Virginia based provider. Local cache near-line servers will be redundant and mirrored. 4. Demark of the provided services for SLA purposes will be at the node MC switcher within the station rack. The local cache capacity will be borne out via the final system design. 5. Content format delivered to the station node will be detailed in the final system design. 6. Content will be converted to baseband at the station rack and integrated into a automation controlled master control switching system (such as the Snell ICE product) integrating on-line server, RT network feed, and local branding. Post switcher feeds will pass through the EAS system controlled at the station. (The Sony NOC would be able to control these functions when required.) 7. Multiple flavors of the station s final programming are fabricated for Internet delivery, delivery to the ATSC encoder for OTA transmission, and other mobile platforms and encoding schemes. 8. Cable handoff for the Comcast local POP will be at the station node and aggregation for DirecTV and DishNet will be via bonded T1 s to a remote aggregation point external to the Station, all post EAS encoding. 9. There are two means of DR for the station/node: the local dish at the station (or future direct 100 mbps NGIS feeds) will provide a hard back-up RT feed to the local switcher in the event of Sony NOC failure; and/or the local cache servers, which will have seven (7) days play- to-air capacity. 10. Transmitter and off-air monitoring will be available at the station as well as the NOC (and on other web enabled platforms) via a System Watch portal on MBEMS. 11. Stations to be served via the outbound main program stream are: 5

6 WVPT Staunton/Harrisonburg, Virginia WVPT Charlottesville, Virginia (translator) WVPT Monterey, Virginia (translator) WVPY Front Royal, Virginia WVPY Fulks Run, Virginia (translator) WVPY Luray, Virginia (translator) WVPY Ruckersville, Virginia (translator) III. Sony services model elements The three specific areas of Sony strength in building this services model are commercial with respect to the above needs of WVPT (possibly four with the application of ODA at the NOC for historic archive): Overall system wide management MBEMS; Cloud based storage Ci; Network Operations Ingest, QC, Monitoring, Distribution and Application Management. A. Overall Architecture Review (Appendix A) The Sony distribution model would leverage existing Sony products capabilities, which were primarily Capex funded by client s in the past into an aggregated Opex services model (shaded in green in Appendix A) scalable to a client s needs and with a commercial commitment by the client commensurate to the Sony business model. In Appendix A for the WVPT example noted, PBS Real Time (RT) and Non-real time (NRT) content is distributed for the present (through 2016) via the PBS satellite system on AMC 21 and 1 transponders. This content will be received at the Sony Network Command and Control Center (NOC) via MBEMS user controlled Ericsson 8200 receivers, QC d through MBEMS control, populated into the Sony Ci cloud with metadata generated through MBEMS (stripped off the PBS file) and the user, and tagged for play to air using a NOC/Node based mirrored automation system, the play-to-air list built and uploaded to the platform by the user. Additionally, the RT feed can be taken to air at the station/node directly utilizing the station located dishes minimizing the RT traffic and bandwidth on the Sony NOC interconnect and possibly providing a better price point to the client. This process allows not only WVPT to utilize PBS delivered content elements but also allows other PBS stations on the Sony network to access PBS content at any time, anywhere. For editing promos, interstitials, features and other content, files will be delivered to the Avid or FCP workstation from the local near-line cache server which has been populated via Ci. PBS and third party portal loaded elements are fed through the Sony NOC to Ci for use at the station cache. Finished files are stored back to Ci for when they are needed by the automation system for delivery to the local station s near-line cache before they are pulled into the Snell ICE station-in-a-box product on-line storage cache (for example) for final branding and play to air. Graphics using Photoshop elements and Adobe Graphics Suite from the client, are uploaded by the client into the cloud based Graphics system. Individual station brandings and sponsorships are tagged through metadata through the automation system, in essence formulating a just-intime manufacturing process for producing content to air from the raw materials (content) supplied by PBS and other user supplied programming which is uploaded into the MBEMS Ci portal and local near-line cache. 6

7 Play-to-air is based on a client generated play list uploaded to automation with an advance of seven (7) days playtime. At a high-level, the traffic system pulls the content it needs into the near-line storage cache servers from Ci (noted as Deep Storage on Appendix A). For a single program stream such as PBS HD01, the automation system pulls the content from the near-line cache servers into the on-line server contained within the Snell ICE product at the station node. Automation running at the station node fully controls the ICE master control switcher with control mirrored at the main automation server at the NOC. The ICE master control switcher allows the capability of local breakaway in the event of a catastrophic failure of the Sony network. Station branding is added locally through ICE with EAS added post ICE. Four baseband feeds from four ICE switching matrices (WVPT-HD, World, V-me, Create) then feed the ATSC encoder located at the station and subsequently fed to the over-the-air transmitters, translators via microwave STL s. B. The Sony NOC The role and purpose of the Sony Network Operations Command and Control Center (NOC) is to have a central point of control of inbound PBS network generated content, content prep, a point of across-the-board quality control and intervention capabilities, real time system wide monitoring with alerts and integrated help desk, Ci control, as well as management of the cloud based applications of graphics, and edit systems, and the main automation and traffic systems servers. Additionally, the NOC manages day-to-day the commercial relationship with the client and is the central monetization portal for Sony of the service offering. The general requirements of the NOC at this time are the ability to receive PBS s Ku satellite programming on AMC-21 and C band satellite programming contained on AMC 1. Additional satellite feeds may arrive at the facility on an ad-hoc basis as would inbound cloud content and, anticipated post 2016, PBS 100 Mbps terrestrial services. It is anticipated that the NOC would apply automated QC techniques to the inbound content, strip off metadata where possible, add additional metadata at a control console where necessary, register it into MBEMS and push the content to the cloud service Ci for use by WVPT. The NOC will act as the entry point into Ci for third party generated content through a secure user portal with transcoding into the agreed base format for WVPT with automated QC. The NOC will also act as Sony s management portal for the applications, which will run in Ci such as Graphics and Editorial; it is envisioned at some point that the master traffic and automation servers initially located at the NOC will be virtualized in Ci as well. At the management portal, overall monitoring of the performance of the applications can be seen and adjusted and upgraded as necessary. A critical function of the NOC will be to monitor across the entire WVPT chain, utilizing Sony s System Watch product, content input, storage, manipulation and delivery of all necessary parameters to insure the service is being delivered as noted in the agreed to SLA, i.e. programming logs, QoS, bandwidth used, off-air signal performance of transmitters and translators, QC results, error and issue logs, etc. 7

8 It is envisioned that to reduce circuiting costs to WVPT, which would presumably be based on bandwidth, the RT PBS feed would be taken to air in its default mode at the station/node rather than through the NOC/Ci. Output of NOC content to Ci will be dual and diverse GigE fiber circuit paths routed from a Tier 1 service provider. Overall loading of these circuits will have to be commensurate with the envisioned throughput to not only WVPT but other station groups who may be drawing content at the same time. Circuits back to WVPT, which are also dual and diverse could possibly be 100 mbps, as this content would be used for populating the near-line cache servers. Through recent internal discussions, consideration has been given to have the dual and diverse circuit from Ci back to WVPT be the responsibility of WVPT. Further modeling of this element needs to be undertaken. Through a formal workflow design actual 24/7/365 head-count can be ascertained for the operation of the NOC. It is expected that the NOC would be contained within a hardened facility with the usual redundant power, HVAC and security systems in place. Room for expansion to scale the operation would also be necessary. Some of the proposed bundled services offered at the Sony NOC are listed in Table Two with proposed providers in Table Three. Optional Services (not part of the base offering) follows in Table Four. Table Two: Bundled Services Offered NOC Services Element System Process Destination PBS Network content MBEMS Automated w/manual Cloud ingest management intervention Contribution stations MBEMS Automated w/manual Cloud content ingest management intervention Content prep MBEMS Automated w/manual Cloud intervention QC Cerify/Baton/Amberfin Automated Cloud Transcode TBD Automated Cloud Closed Captioning TBD Automated Cloud Metadata tagging MBEMS Automated w/manual Cloud intervention Third party content MBEMS Automated w/manual Cloud portal intervention System wide MBEMS Automated Cloud monitoring: content, control & OTA Satellite dish control TBD Automated w/manual N/A intervention Managed circuits Tier 1 TBD Manual Cloud services Traffic list supervision MBEMS Manual NOC/node Automation supervision MBEMS Manual NOC/node 8

9 C. Media Backbone Enterprise Management System (MBEMS) MBEMS forms the backbone of the Sony network services offering and is a unique competitive edge that Sony brings to the market in this regard. It is envisioned that MBEMS would act as the orchestrator of the network wide systems with user interfaces into traffic, automation, edit and other control systems. To leverage start-up costs, serious consideration should be given to adapter/services interfaces that currently exist for automation, traffic and edit systems as a basis for the choice of traffic and automation systems where possible. While MBPS can be used for the production of live or live-to-tape content locally at the station, MBEMS is the overarching set of applications that monitor workflow within the station, to and from Ci and to and from the Sony NOC. It is responsible for all content management (MAMS) and acts as the supervisory layer for the client as well as Sony personnel and management through its analytics and dashboard interfaces. A key function of MBEMS will be the monitoring of inbound and outbound content, as well as all stages of the content s life cycle for the client that Sony has under its control and SLA agreements. MBEMS will be at the start of the programming chain monitoring PBS network content as it arrives at the Sony NOC and through the QC process into Ci, play-to-air content from the station to the transmitter (pre and post ATSC encoding), and to other transcoding devices for mobile, web, in their discreet layers and local over the air decoding of the final signal off the transmitter and/or translator. A final key MBEMS contribution will be to utilize the intelligence gathered from over-the-air System Watch monitoring functions to serve as an early warning mechanism to trigger Disaster Recovery (DR) plans in the event the final program signal does not reach the transmitter and/or other outlets. As the proposed station design includes an ICE master control switching system(s), routines need to be developed within MBEMS to identify where the fault lies, cause the trigger for DR, and utilize a pre-determined work-around to compensate for the fault. For example, if there is no longer an off-the-air signal being received back at the Sony NOC, in-place decision trees are enabled to see if it is a Sony related delivery issue back to the Station, in which case the master control switcher reverts to auto play out of the seven (7) day stored content on the local cache server. If it is a server issue, RT content from the PBS feed received locally is switched to air until the event is resolved. Processes for local control of the station master control switcher need to be in place as well for station control of content play out locally. D. Sony Cloud Ci Another key competitive edge that Sony enjoys with the new service offering is Ci, AWS ISO27001 and MPAA certified cloud-based storage. The Ci element within this new services offering from Sony acts as the Asset Management environment and Storage Platform for all content from and to PBS and from and to the station(s). Integrating Ci with MBEMS is an elegant scalable solution for the network services model and by integrating these two systems, draws a clear distinction between Sony and its competitors. And, it allows common PBS content needed by a group of PBS stations to be securely deployed, readily available and accessible anywhere, 9

10 anytime. By Sony QC ing and prep ing the content on the inbound side of the NOC and pushing it to Ci, multiple stations can utilize those files through their MBEMS workflows following the produce once, edit/brand/deliver many! mandate. The Ci function within this model needs to be scalable to the amount of content envisioned to be used by a single station and beyond. For reasonable data-throughput from the Sony NOC to Ci, a redundant and diverse 1 GigE Tier 1 interconnect is envisioned. The interconnect to and from the NOC to Ci will be Sony s responsibility. The interconnect between Ci and the station is envisioned to be the station s responsibility. Ci s inherent collaborative working features will allow efficient utilization of content throughout the station workflow process. And because it is collaborative, bringing in other PBS stations into the mix to utilized the PBS stored content on Ci enhances the service offering. By integrating MBEMS with Ci, the client is empowered to take charge of their content directly, un-like a traditional heavy metal hub and spoke central cast model where control of the content is at the hub. In the Sony model, the client pushes their own edited content to Ci, collaborates with others in the content production process, gains approvals where necessary, uploads their own traffic lists and graphic elements taking charge of the look of the station using web based tools from their own station location or remote desk top. Or, as the case may warrant, the client could push a part of these required services as additionally supplied services from the Sony NOC. In any case, MBEMS integrated with Ci offers the client the greatest amount of flexibility and the supply of Sony services in this regard is only limited by the client s vision and financial capabilities. E. Commercial Considerations 1. Level of Services Offered The level of services offered in the proposed set of models to be developed in detail will be commensurate with the client s needs and the third party applications and services needed to satisfy those needs. There will be a basic level of services, which will include the NOC, Ci, MBEMS and third party applications/hardware. The pricing model will need to address these four specific scalable systems/services costs: In terms of the NOC, how much intervention by personnel is needed to operate the service? Also, physical plant costs and transport costs, and services costs are key cost model elements. For Ci, what is the total capacity of storage needed, envisioned uploads and downloads, and number of users on the system? For MBEMS, what is the number of users, interfaces and adapters needed or needed to be developed, cache storage, i.e. adapter costs for transmitter monitoring, etc.? And, there will be a number of third party specific applications to be offered as well including a NOC/node based traffic system specific to the needs of this offering (possibly ProTrac in use now by PBS stations), cloud NOC/node automation and graphics systems (possibly Vizrt). See Table Three. In terms of specific hardware, cache servers and local master control switching systems (i,e, ICE) at the station level will also need to be integrated into the cost model. It is envisioned that the level of services beyond a basic level needed to run the station at a level of confidence that the station currently enjoys with its own personnel, will increase based on specific needs of the station/client. Various other pricing models can be arranged based on needed level of services. 10

11 Table Three: Proposed Services Element Provider Services Element Vendor Location User Automation Pebble Beach NOC/node Station & NOC /Crispin? Traffic Myers ProTrack NOC/node/Cloud Station & NOC Graphics Adobe Cloud Station Edit Avid/FCP/(Adobe?) Cloud Station MBEMS Sony Cloud Station & NOC MBPS Sony Cloud Station MAMS MBEMS/Myers Cloud Station & NOC System Watch Sony Cloud Station & NOC monitoring GigE circuits Tier 1 TBD To/from Cloud Station & NOC Table Four: Optional Services Services Element Vendor Location User Live Captioning Sail Labs speech to NOC/Cloud Station text engine (?) Closed Captioning EEG CC Encoders NOC/Cloud Station Virtualized Graphics Vizrt? Cloud Station Mobile /CDN streaming TBD Cloud Station distribution platforms VOD Sony DADC Cloud Station Blu-ray Disc Sony DADC Cloud Station V-sat Backhaul to transmitter site Sony NOC/Cloud Station 2. Opex vs. Capex Traditional broadcast sales have been based on a Capex model. The objective of this model wiuld be to provide value to WVPT on the heels of diminished publically available funding by offering to the WVPT a monthly cost services model, based on a several year agreement, provided the offering is affordable and offers value beyond the competition. The Sony offering would be cloud based as described previously, sold on a monthly fee basis, predicated on probably a 3, 5, 7 and/or 10-year service agreement. F. Other Commercial issues 1. Partnerships and PBS funding considering the elements needed to effectively launch a group distribution services offering in a timely manner for WVPT including a rigorous proof-of-concept partnerships are key to an timely launch of these services, considering the time and expense it would take to launch the service from scratch. 11

12 In discussions with PBS and CPB in Washington this past July, there was interest shown on the part of these organizations to possibly underwrite a portion of or contribute to, the start-up costs of this services offering akin to the financial contribution that was made to other groups in Jacksonville and Syracuse for hub and spoke launches. Further discussions with WVPT to explore the possibilities of partnership need to be considered as there is a short fuse for a potential launch such as the exploration of grants to the stations from PBS/CPB to adopt a cloud based group distribution model. 2. Duration of station services agreements It is envisioned that the duration of the agreement should be no shorter than three (3) years with a potential of up to ten (10) years. As there would probably be a technology cost refresh at five (5) years, longer models would need to consider this renewed capex funding in the model. 3. SLA s It is envisioned that the level of service offered in this business model would need to be equal to or better than the client s current level of service and captured as such in subsequent SLA s. 4. Critical mass of stations - While this model has been based on discussions and needs of WVPT in particular, it will be an important part of the cost modeling effort to ascertain how many stations within Virginia would be candidates for participation in this new service. And in a larger picture, how many PBS stations throughout the region and country that are looking for an alternative broadcast model where this service can apply. Additionally, as soon as a more detailed presentation can be developed post the September 10 th to WVPT, PBS stations WBRA in Roanoke and WCVE in Richmond who have been a part of WVPT thinking s on this subject should be made. G. Next steps The following next steps are necessary to develop this model further: 1. Develop a detailed system architecture A detailed system/services architecture is needed to develop the equipment list and systemization to complete the services offering model based on an affirmation of technical and operational elements of this brief. This detailed architecture will form the basis of the model. It is envisioned that after the architecture is developed that it will be shared under NDA with WVPT, WCVE and WBRA to get critical buy-in. 2. Identify Partnerships - Partnership opportunities identified. Areas include: WVPT PBS/CPB Tier 1 lines provider Applications providers (i.e., Vizrt, Pebble Beach, Crispin, Myers, etc.) Storage/server providers (i.e. NetApp, Omneon,etc.) 3. Build a working financial model Develop order of magnitude costs for each element of the program to get a sense of capex needed to fund and funding offsets through partnerships. 4. Build a proof-of-concept model - Integrate identified partners into the proof-of-concept program including architecture contributions as well as core competencies through which would 12

13 help insure the success of the program. 5. Build a detailed financial model With knowledge gained from steps 1-4, build a detailed financial model, which includes the following elements. 6. Presentation and subsequent buy-in from WVPT and other Virginia based PBS stations, i.e. WVPE and WBRA. 13

14 Appendix A Sony High-Level WVPT PBS Distribution Model Sony Media Backbone Conductor and System Watch Monitoring Layer Sony Ci Local PBS Station/Node Ci)Applications) PBS AMC Feeds Sony Network Deep Storage Graphics) State/Ad-Hoc Feeds Command And Control Center NOC Content)Files) Content)Files) Editorial) Public Cloud PBS 100Mbit Feeds Traffic) Server) AutoB mation) Server) Application) Data)and)Control) Traffic) Server) AutoB mation) Server) NOC/Node)Application) Servers) Live) Production/) News) Transmission / Distribution Circuits & Platforms ODA) Stations Content)Files) Cache) Cache) Servers) Server) Near%line) Storage) PBS)RT)Feed) On%line)) ) storage ) ) ICE)MC) Switcher) ) Rich Bisignano Rev G 14