feature automation & asset management
Centralisation of
programming as well as content architectures, Snell’s Morpheus
ingest. automation serves as a proven
Morpheus can push content out to solution for efficient operations along
content distribution
any or all of the spoke sites at any the hub-and-spoke model. In doing
time, supplying up to three days so, the system enables users to
worth of what would normally be centralise media management and
Continued from Page 25.
centrally delivered programming. operational processes within a hub
Staff at the hub or at any of the Because each spoke site is site and, in turn, to achieve a
spoke sites can take operational configured with a complete, significant degree of resilience
control over content delivery, standalone automation and media through centralised playout and
broadcasting programmes of
The
management system including local archive support for local spoke sites.
particular interest to local and
distributed
ingest, Morpheus is able to offer a Centralisation of media storage at the
regional viewers. For example, higher level of resilience that hub also eliminates redundant tasks -
during mainstream programming
architecture
protects playout in the event of such as multiple QC checks at
hours, control of area news and of the hub- engineering or operational issues at different sites - while making it more
events can be handed off to various
and-spoke
the hub or if the network connection cost-effective to repurpose that
spoke sites, where minimal
model does
between the hub and one or more content across multiple regions and
operational support can oversee a
not increase
spoke sites should be lost. platforms.
local installation of Morpheus to The distributed architecture of the
handle creation and editing of
operational
Conclusion hub-and-spoke model does not
community-type programming and
costs in terms
increase operational costs in terms of
news schedules. These schedules are of duplication By properly implementing a hub- duplication of ingest processes and
also visible within the hub, and any
of ingest
and-spoke architecture for storage, nor does it increase a
new content requirements trigger a
processes &
multichannel playout, content facility’s personnel costs. Rather, the
transfer from the hub down to the
storage, nor
aggregation and distribution hub-and-spoke model offers
spoke(s). This workflow can also companies - whether broadcasters or flexibility that allows for tailoring of
include ingest of content directly
does it
other media companies - can balance playout operations to meet specific
within the spoke for commercials, increase the demands of ongoing capital functional or business needs. This
news, and programming specific to
personnel
investment in broadcast model of centralised multichannel
the viewing audience. Overnight or
costs.
infrastructure and operations with playout also provides a high level of
at less busy times each spoke can be the need to remain flexible within a end-to-end resilience without
operated totally ‘hands-free’ with continually evolving media-delivery requiring an increased investment at
control being handed back to the market. the spoke sites, thereby offering
hub site, which maintains control Already installed at the heart of maximum operational versatility and
and scheduling of all local large enterprise playout excellent value for money.
Next generation
Open standards
communications protocols. So the
developer of a particular part of a
One of the perceived disadvantages of
multi-vendor system could introduce a
news systems
putting together a system based on a
major upgrade with significant
number of products from specialist
changes to functionality, but as long
broadcast servers to consumer
as the web service API remains
software like Premiere or Final Cut Pro
constant there should be no impact on
Continued from Page 23.
is that developing and maintaining
the other sub-systems which
one to meet the time constraints of
the interfaces will be a nightmare. In
communicate with it.
the evening news programme, with
particular, as different suppliers
Development programmes on those
a fuller retelling for the website - is
upgrade their products, all the others
other sub-systems need not be
now a practical proposition.
The Curator
will need to be modified to keep
disturbed to respond to the upgrade
desktop in use.
communicating.
until they need to access the
The solution, as ever, lies in open
additional functionality. At that time,
standards like MXF, and in particular
because the communications API is
web service interfaces. Using
separate, stable and proven, adding
protocols like Soap (simple object
the new tools will be a simple and
access protocol) and Rest
secure matter.
(representational state transfer)
Already we are working with other
systems can exchange unstructured
vendors on complete systems which
and sophisticated data - control and
use web service interfaces. The IPV
command as well as complex
Curator asset management system
metadata - within a simple and
communicates with other equipment,
standardised framework. These
such as the newsroom and the online
protocols are relatively easy to
storage, to make a complete system
implement and permit easy exchange
which solves the critical issues of
between distributed devices in a
news: getting the story out fast, with
network using XML as the message
minimal resources wasted on non-
format.
productive tasks and maximum
The web service interface
investment in the quality of the
decouples the system from the
journalism.
26 l ibe l january/february 2010 l
www.ibeweb.com
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44