Our country needs a standard for digital content sharing in order to ensure government content will be able to be archived and kept for generations to come. This is inline with the Malaysia Creative Content (MyCC) EPP1 Initiative.
Content sharing and archiving process can be simplified through the Content Ecology Services Framework, which provide facilities to control the content lifecycle and managing the distribution for later reference.
2. Welcome
Bienvenue
Sawadeekap
Selamat
Datang
Bine
Ai
Venit
Welkom
Chao
Mung
Valkomna
Maligayang
PagdaDng
Velkommen
Benvinguda
3. Proposal
Ra3onale
The
objecDve
of
the
project
is
to
create
a
standard
digital
content
sharing
pla6orm
between
government
agencies
and
to
control
the
content
distribu3on
through
a
secured
DRM
technology.
Our
country
needs
a
standard
for
digital
content
sharing
in
order
to
ensure
government
content
will
be
able
to
be
archived
and
kept
for
generaDons
to
come.
This
is
inline
with
the
Malaysia
CreaDve
Content
(MyCC)
EPP1
IniDaDve.
Content
sharing
and
archiving
process
can
be
simplified
through
the
Content
Ecology
Services
Framework,
which
provide
faciliDes
to
control
the
content
lifecycle
and
managing
the
distribuDon
for
later
reference.
4. Current
Scenario
Issues
to
Manage
No
DRM
implementaDon
to
control
the
content
distribuDon
Ownership
of
content
remains
at
the
respecDve
owners’
faciliDes.
Agencies
creaDng
content
management
silos
will
cause
content
duplicaDon.
Agencies
with
a
limited
budget
didn’t
implemented
content
management.
StandardizaDon
of
content
formats
and
naming
convenDon
No
IntegraDon
PlaRorm
that
will
allow
similar
access
to
mulDple
and
remote
repositories.
Expansion
of
proprietary
content
management
system
required
addiDonal
licenses
cost.
No
federated
retenDon
policy
management
system
for
archiving
process.
5. Current
Scenario
Content
Management
Implementa3on
Agency
Document
Management
System
Digital
Rights
management
DAM
/
MAM
Content
Management
Integra3on
Ecommerce
&
Online
Payment
6. Content
Lifecycle
Management
Content
Crea3on
Content
Management
Content
“End-‐of-‐Life”
Management
• Content
classifica3on
(ownership,
rights,
EOL
defini3on
and
etc)
• Standardiza3on
of
content
format
• Standardiza3on
of
content
naming
conven3on
• Cross
agencies
content
sharing
considera3on
• Deployment
of
DRM
to
manage
content
distribu3on
• Use
of
e-‐Commerce
pla6orm
manage
revenue
and
revenue
sharing,
if
applicable
• Elimina3on
of
independent
content
bunkers
that
are
isolated
but
stores
government
content.
Duplica3on
is
cost
to
Government.
• Storage
management
(actual
and
digital
format
content)
and
responsibility.
• Content
accessibility,
rights,
royalty
and
etc.
Other
Agencies
7. MAM
MAM
ECM
MAM
DMS
MAM
MAM
Best
Case
Scenario
DRM
DRM
MAM
DRM
ECM
Integra3on
Pla6orm
Users
Cloud
(WAN)
Internal
Agency
Users
Public
Users
8. Proposed
Solu3on
Key
Features
Diagram
Enterprise
Content
Manager
CLM–
Content
Lifecycle
Management
Digital
Asset
Management
Document
Management
System
Federated
Content
RetenDon
Policy
and
Management
DRM
–
Digital
Rights
Management
Federated
DRM
Management
Trading
&
Fulfillment
Management
Content
secure
Packaging
DRM
Content
Player
CC
M–
Content
CollaboraDon
Management
Ecommerce
Suite
Social
Media
AFS
–
ApplicaDon
Federated
Services
9. Proposed
Solu3on
System
Features
Content
Console
&
Management
(CCM)
Module
is
the
main
module
in
CES
system
server.
Its
provide
a
powerful
management
console
to
manage,
create
or
capture
content.
Ability
to
manage
mulDple
and
remote
repositories.
• Record
Reten3on
Policy
Management
• Content
Browsing
Module
• Content
Compliance
Module
• Content
Workflow
Module
• Document
Security
Module
• En3ty
Extrac3on
Module
• Data
&
Text
Mining
Engine
• Media
Streaming
Engine
• Content
Rendi3on
Engine
• Applica3on
Federa3on
Framework
• Asset
Management
Module
• Asset
Usage
Tracking
Module
• Asset
Capture
Module
• Content
Secure
Packaging
• Secured
Content
Repository
• Embedded
DRM
Content
Player
• Collabora3on
Portal
• E-‐Commerce
Suite
• Online
Payment
System
• Social
Media
10. Digital
Rights
Management
DRM
Rights
Model
An
effecDve
DRM
architecture
will
not
only
require
secure
rights
management
at
the
iniDal
content
use,
but
must
remain
persistent
with
the
content
as
it
is
edited
or
embedded,
in
the
future.
11. Proposed
Solu3on
System
Infrastructure
System
will
be
running
on
7
node
of
powerful
Cloud
Server
with
a
power
to
processed
98,875,800
file
per
hour
with
an
average
file
size
of
1Mb.
Delivery
of
300Mb
video
file
at
opDmum
internet
speed
will
be
less
than
10
minute.
12. Proposal
Objec3ve
Benefit
to
Government
Use
of
common
plaRorm
(ECM,
DRM,
e-‐
Commerce)
reduces
cost
of
ownership.
IP
rights
will
be
maintained
by
righRul
owners
regardless
the
locaDon
it
is
stored.
Each
agencies
can
manage
their
content
in-‐place
while
distribuDng
content
with
others.
Process
of
archiving
the
content
can
be
simplified
using
federated
retenDon
policy
management
Seamless
integraDon,
content
can
be
search
through
mulDple
repositories
using
single
interface.
Less
cost
and
Dmeframe
for
others
agencies
ECM
deployment.
13. Implementa3on
Plan
Task
Time
Qtr
1
Qtr
2
Qtr
3
Qtr
4
Qtr
5
Qtr
6
User
Requirement
Study
System
Design
&
Standard
System
Development
System
&
Infra
Deployment
Content
Migra3on
Training
&
Workshop
14. Moving
Forward
• Adopt
open
soluDon
and
open
technology
plaRorm
that
is
scalable
without
vendor
lock-‐in.
• Establish
standardizaDon
record
exchange
E.g.
metadata,
content
naming
convenDon,
format
and
etc.
• Consolidate
content
silos,
if
any
into
a
common
plaRorm
between
agencies
to
ensure
content
sharing
will
be
possible.
• Strategically
partner
with
local
soware
developer
to
customized
and
develop
Malaysia’s
own
Content
Ecology
Services
PlaRorm
17. Applica3on
Terminology
ECM
(Enterprise
Content
Management)
is
a
formalized
means
of
organizing
and
storing
an
organizaDon's
documents,
and
other
content,
that
relate
to
the
organizaDon's
processes.
The
term
encompasses
strategies,
methods,
and
tools
used
throughout
the
lifecycle
of
the
content.
19. Case
Study
Current
Content
Manager
Features
Category
ECM
ECM
MAM
MAM
Product
Name
OpenText
ECM
Suite
FileNet
P8
Interplay
DivaDirector
Digital
Right
Management
RMS
3rd
Party
None
DivaPublish
External
Integra3on
CMIS
CMIS
Web
API
DIVA
API
Trading
Pla6orm
3rd
Party
IBM
WebSphere
None
3rd
Party
Collabora3on
Opentext
Collab.
3rd
Party
Source
Code
Proprietary
Proprietary
Proprietary
Proprietary
20. Example
JSON
format
:
System
Flow
Architecture
Data
Model
Rela3on
Example
{
filename
:
myvideo.mpg
,
folder
:
/dokumentari/sejarah,
token
:
{
repository
:
G-‐REP1-‐FINAS-‐S7,
rights
:
G-‐DRM1-‐ANM-‐ID01FINASVID19810403A01
}
}
21. Project
Case
Study
State
Lands
Migrates
Historical
Documents
from
FileNet
Louisiana
Serves
Up
Historical
and
Tax
Documents
from
the
1800ʹ′s
How
do
you
grant
public
access
to
two
and
a
half
million
scanned
pages
of
a
state’s
historical
and
tax-‐related
documents?
“It
was
quite
easy
given
the
newer
technology
available,
a
lihle
research,
and
a
great
reputaDon.”
said
Calvin
Fabre,
Director
of
Client
EducaDon
at
Louisiana-‐based
Envoc.
“By
leveraging
Atalaso’s
DotImage
soluDon,
we
were
able
to
provide
a
secure,
scalable,
recoverable,
maintainable,
and
fast
soluDon
to
Louisiana
consDtuents.”
The
new
system
is
serving
up
almost
three
terabytes
of
images
through
a
completely
web-‐based
interface.
Prior
to
this
iteraDon
of
the
applicaDon,
the
system
was
running
on
an
IBM
FileNet
soluDon
with
a
web
front-‐end.
The
IBM
FileNet
system
demanded
heoy
yearly
licensing
fees
which
were
altogether
avoided.
AddiDonally,
the
server
hardware
being
used
by
FileNet
was
being
decommissioned
due
to
its
age.
Since
the
project
used
exisDng
virtualized
servers
and
SAN
space,
there
were
no
hardware
purchases
made
for
the
conversion.
The
new
file-‐system-‐
based
approach
to
document
storage
provides
an
added
benefit
of
a
faster
Recovery
Time
in
a
Disaster
Recovery
scenario.
1 management node
7 cloud node with 16 CPU core
64 x 3,600,000,000 = 230400000000 bit / second
230400000000 / 8 = 28800000000 byte / second
28800000000 /1024 = 28125000 Kbyte / second