Technical Solution Proposal

Customer Name Sadhna

Project Name PTA and Production
Installation Date To be determined
XORMedia Sales Rep
SI Partner

This document is to be used to define the high-level project workflow, new hardware/software and
professional services required. It will also confirm with the client the acceptance criteria required.

Document Version Control

Version Name Date Notes
Number
1 VW 10.11.2013 Initial Draft
2 VW 10.16.2013 Update the SMG and diagram
3 VW 10.25.2013 Update the edit while ingest
4 VW 10.29.2013 Update the two solutions
5 VW 10.31.2013 Remove Option1 and keep Option2
6 RJT 11.04.2013 Repaginated and reformatted sections
Revised network diagram to include 3 DATA connection per
MCL
Included workflow diagram
Improved workflow discussion
7 VW 11.07.2013 Use 2 MCL8200 instead of 4 for the proposal
8 RJT 11.08.2013 Revised network and workflow diagrams
Revised network port requirements
9 RJT 11.11.2013 Included Vinayak Deos comments
Revised workflow diagram to show the actual number of
editors

Reviewers
Sales Susheel Koul
Engineering Roy Torrecampo /Vicky Wang
Professional Services James Oakes

Approvals
Sales Susheel Koul
Engineering Roy Torrecampo /Vicky Wang
Professional Services James Oakes
Client

Page |1
I. Project Background
A. Project Requirements for PTA

Ingest and Playout Requirements

Number of Input: 8 IN (4 main and 4 backup)

Number of Output: 8 OUT (4 main and 4 backup)

Ingest and Playout Controller

Etere automation will be used for controlling the decoder on two MCL8200s to
play out clips under Cache folder on PTA storage
Etere automation will also control the encoders for base band ingest on the
same MCL 8200s.

Video File Formats

SD: RawDV25
Computed at: 45 Mbps

Storage Requirements

Storage capacity: 16TB raw capacity for PTA storage

Automation

The automation is Etere automation.

B. Project Requirements for Production

Production Requirements

Total 15 FCPs will be used for editing. 3 layers will be loaded on each FCP.
All 15 FCPs will do the edit while ingest and edit in place will be performed.
Need to confirm the supported format for editing while ingest. Video format
and file wrapper (extension) .dv, .mxf, .mov supported by MCL and UML for
these features should be specified. Need to confirm with client for acceptance
of specified format.
Total of 1 x Adobe Premiere CS6.0 will be used for editing-while-ingest. Need to
find out how many layers will be edited and how many Adobe servers there are,
what OS is used.
Total of 2 x FlipFactory will be used for transcoding converting FTP ingest and
other file ingest in various formats to station format.

Page |2
 Total 2 x CarbonCoder will be used for transcoding converting all ingested
files, edited files and files to be archieved to low resolution file format for
viewing and browsing on all PCs.

Video File Formats

SD: RawDV25
Computed at: 30 Mbps

Storage Requirements

Storage capacity: 48TB raw capacity for production storage

II. Proposed Solution

A. Solution Overview

a. PTA SOLUTION

For the PTA requirements, XOR Media proposes the following:

Universal Media Library (UML-E 16TB) as storage

SMG Pro Ingest for monitoring hot folder on PTA UML to create PD/VIX for the
edited/transcoded clips and removing file extension and moving them with
metadata to Cache folder for playout
Two MCL8200 for playing clips from UML E via Samba. 4 SD encoders and 4 SD
decoders are run on each MCL but only the 4 SD decoders connect to PTA UML.

File Transfer Requirements

Automation/MAM will copy the edited/transcoded clips from production to PTA

UML for playout via FTP. Assume the concurrent sessions are 8 sessions.

b. PRODUCTION SOLUTION

For the Production requirements, XOR Media proposes the following:

Universal Media Library (UML-E 48TB) as storage

Two same MCL8200 with channel expansion for encoding clips into UML E via
Samba. 4 SD encoders and 4 SD decoders are run on each MCL but only the 4 SD
encoders connect to the production UML
15 FCPs connect to the UML E via Samba doing edit-in-place and edit-while-
ingest
1 x Adobe Premier CS 6.0s connect to UML E via Samba doing edit-in-place and
edit-while-ingest

Page |3
 3 ftp transferring to UML E from leased line
1 ftp transferring to UML E from P2/SXS
2 ftp transferring to UML E from SD cards

Ingest

Etere automation will be used for controlling the encoder on two MCL8200s to
encode clips into Cache folder on Production storage

File Transfer Requirements

Automation/MAM will copy the edited/transcoded clips back from production

to PTA UML for playout. Assume the concurrent sessions are 8 sessions.
3 x FTP sessions from Leased Line to production UML for file-ingest and editing
1 x FTP session from P2/SXS card to production UML for file-ingest and editing
2 x FTP sessions from SD cards to production UML for file-ingest and editing

Note: Encoder will not see these files from Leased line/P2/SXS card/SD cards as
they have no PD files so these clips wont be displayed in eXd inventory.

B. Solution Components

PTA SOLUTION SERVERS

For the PTA Solution2 requirements, XORMedia proposes

Two (2) x MCL8200 configured as follows:

- 4 x SD IN (configured to ingest contents to production UML-e)

- 4 x SD OUT (configured to playout from PTA UML-e)
- These two servers work as main and backup.

One (1) x UML-E 16 TB configured as follows:

- 2 x HA Linux server Heads

- 16 x 1TB SAS Drives
- RAID 6 protection
- Aggregate Raw Capacity: 1 x 16 = 16TB
- Aggregate Usable Capacity around: 12TB

One(1) x SMG Pro Ingest

Page |4
 PRODUCTION SOLUTION SERVERS

One (1) x UML-E 48 TB configured as follows:

- 2 x HA Linux server Heads

- 16 x 3TB SAS Drives
- RAID 6 protection
- Aggregate Raw Capacity: 3 x 16 = 48TB
- Aggregate Usable Capacity around: 36TB

C. Estimated bandwidth requirement

a. PTA SOLUTION UML E Bandwidth Table

The tables below show the estimated bandwidth requirements for the PTA UML-E based
on the video format provided.

Page |5
 b. Production Solution UML E Bandwidth Table

The table below shows the estimated bandwidth requirements based on the Production
UML-E based on the video format provided.

III. Workflow Description

A. Production Workflow

The suggested Production workflow for the solution is described below:

Baseband ingests Baseband ingest sources include SDI outputs from any of the
following:
o Backpack receivers which accept feeds from backpack
transmitters over 3G Mobile
o DSNG Receivers
o Leased-line receivers
o Studio Recordings (PCR)
o Ingest VTRs
o Satellite feeds and other baseband sources

Automation shall be responsible for controlling these baseband

sources and feeding them to the encoder ports of the MCL8200s

Page |6
 Video files will be ingested by two MCL8200s into the Cache folder
of the Production UML-e in Raw DV25 format via Samba.
Each of the two MCL8200s shall have 4 encoders; i.e., 4 on Main and
4 on Backup. However, the backup encoders will also be used for
normal ingest operations every day. So a total of 8 encoders will be
used simultaneously. In case of failure or any of the MCL8200s, the
number of ingest channels will be reduced.
Automation Automation shall control encoding operation of the two MCL8200s.
File-based ingests File-based ingest sources include the following:
o 3 ftp transferring to UML E from leased line
o 1 ftp transferring to UML E from P2/SXS
o 2 ftp transferring to UML E from SD cards
FCP ingests clip into UML directly via Samba
Edit-in-place/ FCP Editors connect to the Production UML-e via Samba and edit
Edit-while-Ingest contents in-place
FCP editors can also edit contents on the Production UML-e while
still being ingested.
Needs to be confirmed as FCP only supports
edit-while-ingest of content is MXF-wrapped??
One (1) editor using Adobe Premiere CS 6 also connects to the UML-
e via Samba and will edit contents while still being ingested.
Editors will only edit on the Production UML but shall have the
option of saving edited contents on the PTA UML-e. No editing shall
take place on the PTA UML-e.
File Transfers Automation accesses watch folders on FTP servers, registers files in
database, and moves them to Production UML-e.
Automation shall transfer the edited files from Production UML to
PTA on UML for playout

B. PTA Workflow

The suggested PTA workflow for the solution is described below:

File-based ingests Automation will transfer the edited clips from Production UML-e to
PTA UML-e
Editors also have the option of manually saving contents on the PTA
UML-e instead of the Production UML-e in time-critical situations or
on both UMLs
SMG Pro Ingest monitors a hot folder on the PTA UML-e for
incoming edited clips to create the necessary PD/VIX files and
moves those files to the CACHE folder so that they can be playable
by MCL8200s.

Note that an SMG PRO Ingest is not necessary in the Production

UML-e since files ingested there are mainly for editing and therefore
do not require VIX/PD files anyway.

Page |7
 Playout The same two MCL8200s connected to the PTA UML-e via Samba
play out the contents from the CACHE folder.
Each of the two MCL8200s has 4 decoders; i.e., 4 on the Main
MCL8200 and 4 on the Backup MCL8200.
Automation Etere automation shall control decode operations of the two
MCL8200s for PTA.

Page |8
Page |9
Baseband Ingest

Edit-in-place

Edit-while-ingest

Figure 1. Workflow Diagram

MAIN A/V ROUTER

IV. XOR-Media Professional Services
A. High-level description of tasks required

 Site inspection and preparation

 Rack-mounting, installation, and commissioning of two (2) UML-Es
 Installation and configuration of two (2) MCL8200 with CEK
 Installation and configuration of SMG Pro Ingest
 Commissioning and Workflow simulation
B. Expected Duration

Task Man Days

Site Inspection and preparation 1
UML-E setup and configuration, and network provisioning 6
Installation and configuration of MCL8200 1
Installation and configuration of SMG Pro Ingest 1
Workflow simulation and commissioning 1
On-site system overview & basic introduction 1
Total 11 days

C. XORMedia Professional Services Breakdown

Item Unit
UML E SERIES on site basic installation 1
(1 day of setup & configuration, 1 day of commissioning and 1 day
of on-site system overview & basic introduction, excl. T&E)
Additional UML E series installation (2nd UML) 1
MCL 8000 on site initial installation (max 4 MCL, 1 day, excl. T&E) 1
SMG Pro installation & configuration(1day, excl. T&E) 1

D. Exclusions

 Integration with customers Active Directory for user authentication

 LDAP configuration for user authentication
 Folder based quota
 Network configuration and fine tuning
 Specialized UML storage partitioning

P a g e | 10
V. Equipment List
A. New Equipment to be supplied by XOR-Media

Storage (Production)

Product Description QTY

UML 1600 48TB 10GbE 1
(2x Active-Active High Availability Controllers, 16 x 3TB SAS Drives =
48TB Raw, 4x10GigE Ports & Cables, Hot-swappable drives, fans, and
power supplies, BlueWhale FileSystem, RAID-6 data protection, Includes
Warranty Support for Year 1)

Storage (PTA)

Product Description QTY

UML 1600 16TB 10GbE 1
(2x Active-Active High Availability Controllers, 16 x 1TB SAS Drives =
16TB Raw, 4x10GigE Ports & Cables, Hot-swappable drives, fans, and
power supplies, BlueWhale FileSystem, RAID-6 data protection, Includes
Warranty Support for Year 1)

Ingest/Playout Servers

Product Description QTY

MCL 8200 with channel expansion kit combo 2
(3RU, 12 channel MediaClient inclusive channel expansion kit for
4 SD/HD-SDI inputs and 8 SDI/HDI outputs, redundant power
supply, SSD service disk, up to 12 SD or 8 HD codec license pack
support depending on format refer to channel guidelines)

P a g e | 11
 B. Software and Licenses

Product Description QTY

SD Encoder pack (add 1 SD in) 8
SD Decoder pack (add 1 SD out) 8
MediaGateway PRO INGEST v3.2 LICENSE 1
Media Kit V3.0 and license keys for MediaGateway Pro Ingest v3.2 License (4
streams simultaneously per License, including Transfer utility)

C. MEDIA Gateway Machine

XORMedia will only provide the Media Gateway Software. The client shall be
responsible for providing the machine on which to install the software. The following
are the recommended hardware specs for Media Gateway:

Quad core CPU

Microsoft Windows XP Professional, Service Pack 3, or Windows 2008 64-bit
Service Pack1, or Windows 7 32-bit/64-bit Service Pack1, or Windows 2008 R2
64-bit
4GB RAM with FB DIMM 667 SPEED or higher
250GB or higher for service OS disk

D. Remote Access Machine (if there is NO Boss Machine)

XOR-Media strongly recommends the client to provide remote access machine / facility
to allow remote diagnosis and troubleshooting of our proposed systems. Customer will
provide this machine where any remote access application (such as TeamViewer) can be
installed. This remote access machine needs to be connected to the service network
and as well to the internet or to a Virtual Private Network.

P a g e | 12
 E. Network Requirements

The UML and Media Clients require a data and service network as shown in the network
diagram. The customer shall procure the switches required for this project as per
following specifications.

Data network

For the data network switch, the following features are required:

Combination of 10Gbps and 1Gbps ports

The 10Gbps ports should have SFP+ transceivers using LC connectors

Please note that the necessary and appropriate SFP+ modules and transceivers are
normally ordered separately with the switches.

Service Network

This network is typically used by the UML for remote administration and maintenance
purposes only. This network may reside on the house network where the UML heads
may be accessed from a designated remote management workstation equipped with
system administration utilities (such as Putty).

Number of Ethernet Ports Required

In summary, the number of 10Gbps and 1Gbps ports required by the UML and its clients
is shown in the table below.

Table 1. Ethernet Port Requirements

Data Service
Machine 10 Gbps 1 Gbps 1 Gbps
UML-E (PTA) 2 2
UML-E (Production) 2 2
2 x MCL8200 6 2
SMG Pro Ingest 1 1
Total 4 7 7

P a g e | 13
 Figure 2. Network Diagram

P a g e | 14
VI. Responsibility Matrix

Node / Product / Hardware Software Supply HW Support & SW Support &

Services Supply & & installation Maintenance Maintenance
Installation
Project Management
Prime Integration
UML-E XOR-Media XOR-Media XOR-Media XOR-Media
MCL8200 XOR-Media XOR-Media XOR-Media XOR-Media
SMG Pro Ingest Customer XOR-Media Customer XOR-Media

Remote Access Machine Customer Customer Customer Customer

Network Switches Customer Customer Customer Customer

VII. Acceptance Criteria

The system is deemed accepted after completion of the following:

1. Successful installation and commissioning of MCL8200. Clips are ingested into or played
from UML E
2. Successful demonstration of SMG creating PD/VIX for the edited clip on PTA UML E
3. Successful transfer of files from PTA UML E to Production UML E using FTP or vice versa
4. Successful demonstration of the whole system workflow

P a g e | 15