MediaCentre RFP
Where we are, Where we are going
Agenda
•
•
•
•
•
•
•
•
Where we are now
Where we have been
RFP Overview
What’s not in the RFP
Selection Process
Team Discussion
Report Back
Wrap-up
Where we are now…
Many details will be settled during detailed design after Greenlight.
However, we need to wrap up some lose ends before greenlight
MediaCentre
Requirements
(within RFP scope)
Question for this Session:
Do we have everything we need
to move forward with the
vendors to do a final selection
and final cost?
Project Greenlight
Final Vendor Scope
(RFP) & Selection
and
Refine Overall Project
Scope
Business Systems
Requirements
(outside RFP scope)
Launch Project &
Detail Design
How the MediaCentre RFP relates
[Insert Eric’s diagram of overall program
and how MC is a project within it]
The RFP Story… So Far…
Final Decision
Process
Jan – Mar 2013
Analysis
Mar 2012
RFP Release
Jun 2012
Final Selection
Apr 2013
 March 2012 – TSL consultant provides Workflow and Content Process
analysis, content flow numbers, and recommendations.
 June 2012 – RFP written and distributed
 January 2013 – Involve Procurement, Legal, Risk Management, InfoSec
 January 2013 – Validation & Review of Functional Design
 Jan-Mar 2013 – Decision Process to select vendor
Current Goal: Decision by April 1st
Importance of the Worklows
The value of the workflows to the effort cannot be
understated.
The entire RFP and wider effort is based on these.
Huge thanks to the entire team for their time,
knowledge, and effort to make these
comprehensive touchstones.
Who was given the RFP
RFP distributed
Went out to 5 vendors
(Sony Professional Services, TSL, Globecomm, BCE, & IBM)
Initial responses returned
Some vendors excluded due to high costs and poor technical solution
Initial Downselection
Sony Professional Services and TSL both are capable of doing the project
successfully
RFP Overview - 5 Major Areas in the RFP
Technical
Buildout
Content &
Workflow
Management
System
(Workflows)
Regional
Requirements
Project
Management
Requirements
Supporting
Information
A compilation of specific technical
requirements, workflow diagrams,
functional specifications, scenario
descriptions, planning assumptions,
and project guidelines.
Technical Buildout – Central Technical Area
“Things that bolt into racks and have LED lights”
Technical
Buildout
Reference &
Test Signals
Status & Alarm
Monitoring
Signal Monitoring
& Measurement
Automated
QC
Signal
Routing
Comms/
Talkback
External
Feeds
Disk &
Datatape
Storage
With HSM
Transcoding
Technical Buildout – Key Items
Technical
Buildout
New Traffic Area for 8 people
6 New QC/Version Edit Rooms
New Playout Area for 3 people
Technical Buildout – Key Items
Technical
Buildout
New Storage Infrastructure
180 terabytes of spinning disk storage
2.1 petabytes of datatape storage
New data network
Approx 1 TB inbound data per day
Transfer of 1.25TB of new content to playout per day
365 GB of content to non-linear platforms per day
Extensive Transcoding Capabilities
Approx 1 TB of transcoded data created per day
Technical Buildout – Key Items
Technical
Buildout
The CWM system
will connect and
help manage the
existing post
production areas
to improve the
process workflow.
Post areas will
remain connected
to their own
dedicated shared
storage.
Existing OAP Edit Suites/Seats
Existing Graphic/Audio/VO Rooms
Content & Workflow Management System
“Getting the raw content ready for air”
Content and Workflow Management System
Ingest
Voiceover
QC
Localisation
Compliance
On-Air
Graphics
Promo
Production
Playout
Distribution
CWM helps
manage all
aspects of
preparing
content for air.
Content &
Workflow
Management
System
(Workflows)
Content & Workflow Management System
CWM
Key features and benefits
Automates transcoding
to needed formats
Content &
Workflow
Management
System
(Workflows)
Automation of file movement
Central tracking of all assets
Manages ingest of all files
from the variety of sources
Push to playout systems
Common system for
all content preparation
Coordination of the QC process
Direct integration with
Vision/BMS/Landmark
Regional Requirements
“What happens in Budapest & Madrid”
Standardized workflows
in place at channel
offices managed by the
CWM
Regional
Requirements
Opportunity to share
content and resources
across the region
Content preparation for
linear & digital would occur
at the MediaCentre, as
requested by channel office
personnel using the CWM
Project Management Requirements
“Best Practices and doing it the Sony Way”
Project
Management
Requirements
Program and Management Requirements
Standards, Formats, & Specifications
Consulting/Design Requirements
Installation Requirements
Supporting Information
“Large amounts of complicated workflows and spreadsheets”
Volumetric information on Program,
Commercial, and Promo elements
Supporting
Information
Tweaks to plan not reflected in the RFP
Not In
RFP
Majority of MediaCentre equipment & racks to be
hosted at a datacenter location
Removed playout monitoring/DR playout suite
Playout centres will remain in London
The Singapore transition is delayed
Various changes to routing, videotape equipment,
multiviewer, and talkback capability modifications
What’s not in the RFP
Not In
RFP
Business Systems / SPE Enterprise Systems
Detail
GPMS
EAGL/DMR
CineShare
MediaCentre
(within the RFP)
Digital Backbone
Vision
Broadcast Master
Landmark
Content Workflow
Management
Technical Buildout
Crackle
Over The Top
MediaCentre is part of the larger effort toward improvement.
Multiple interfaces with existing systems are required but this effort is
intentionally not in the RFP.
Implementation Partner Selection
Approach
Utilize RFP response
evaluation tools and
methods (see next
page)
Involve other key
Sony resources such
as: Procurement,
Legal, Risk
Management,
Information Security
Provide a
Transparent,
objective, fact
driven approach
Current
Decision
Date:
April 1st
DRAFT: Selection Process Going Forward
Finalize
scope
changes
Document RFP
amendments
Involve
Procurement,
Legal, Risk
Management,
Information
Security
Develop
scenario & use
test cases
Develop
evaluation
requirements
Contact
vendors
• Present
amendments
• Solution
Demos
Review
Responses
Utilize
Scorecard
Tool
Scorecard Tool
Identifies
requirements to
be evaluated
Team members
complete
scorecard
Rates requirements
on a 0-4 scale
Some experts on
specific areas may not
complete entire
scorecard
3.0 Good
4.0 Excellent / Exceeds
Expectations
2.0 Average / Meets Expectations
1.0 Fair
0.0 Poor / Does Not Meet
Expectations
Generates a more consensus driven evaluation
Helps identify show-stopper issues
Avoids Bias
Scores
averaged and
weighted
EXAMPLE: Scorecard Method – A Tale of
Two Toasters
Toaster #1
Category
Weight Comments
Toaster #2
Rating
Score
Category
Weight Comments
Rating
Score
1 Size of toaster
20.0
Average
2.0
10.0
1 Size of toaster
20.0
Small
3.0
15.0
2 Controls
20.0
Good
3.0
15.0
2 Controls
20.0
Good
3.0
15.0
3 Speed of toasting
20.0
Rapid
3.0
15.0
3 Speed of toasting
20.0
Average
2.0
10.0
4 Browning
20.0
Uneven
1.0
5.0
4 Browning
20.0
Superb
4.0
20.0
5 Price of toaster
20.0
Average
2.0
10.0
5 Price of toaster
20.0
High
1.0
5.0
Total (Actual)
Total (Possible)
Percentage/Weighted Score
100.0
55.0
100.0
55.0%
Total (Actual)
Total (Possible)
Percentage/Weighted Score
100.0
65.0
100.0
65.0%
Team Discussion
• What was addressed well in the RFP?
• What areas of the RFP would benefit from additional clarification? (to
allow us to accurately scope the project for Greenlight and to write accurate SOWs
with the selected Vendor?)
– What sections would you want to make sure address in more detail this
week?
– What assumptions were made that you think we should revisit or were
not addressed
– What critical information or workflow process are we missing? What do
we risk if we don’t get this additional detail
• What other Sony groups can benefit from the MediaCentre project
and need to be included?
– How do you see them being benefited?
• What are your key points about how to best move the selection
process is conducted going forward?
– What do you want to make sure happens?
– What do you believe will be the key differentiating selection criteria?
Report Back
• What was addressed well in the RFP?
• What areas of the RFP would benefit from
additional clarification? (to allow us to accurately
scope the project for Greenlight and to write accurate
SOWs with the selected Vendor?)
• What other Sony groups can benefit from the
MediaCentre project and need to be
included?
• What are your key points about how to best
move the selection process forward?
Wrap-up and Review
• What do we need to address in the RFP
• What of these additional questions are can
be addressed by the