This document discusses a proposed content ecology service project for the ANM government. The project aims to create a standardized digital content sharing platform between government agencies and control content distribution through a secure DRM module. The key components of the project are a content console and management system, content DRM management, content collaboration, standards and compliance, and third party integration. Case studies of international ECM and DRM implementations in countries like the US, Australia, New Zealand, and Europe are also presented.

1. Content
Ecology
Service
Content
Management
Lifecycle
for
ANM

2. Welcome
Bienvenue
Sawadeekap
Selamat
Datang
Bine
Ai
Venit
Welkom
Chao
Mung
Valkomna
Maligayang
PagdaAng
Velkommen
Benvinguda

3. Project
Background
Project
Ra8onale
The
objecAve
of
the
project
is
to
create
a
standard
digital
content
sharing
plaForm
between
government
agencies
and
to
control
the
content
distribuAon
through
a
secured
DRM
module.
The
country
needs
a
standard
for
digital
content
sharing
in
order
to
ensure
government
content
will
be
able
to
be
archived
and
kept
for
generaAons
to
come.
Archiving
process
can
be
simplified
through
the
Content
Ecology
Services,
which
provide
faciliAes
to
control
the
content
lifecycle.

4. Project
Background
:
ANM
Government
Policies
Sama seperti rekod dalam bentuk kertas, rekod
elektronik adalah merupakan maklumat yang
dihasilkan atau diwujudkan, diterima atau
disimpan secara rasmi dengan menggunakan
kemudahan elektronik. Oleh yang demikian
rekod elektronik juga tertakluk kepada
penafsiran Rekod Awam dalam Akta Arkib
Negara Malaysia 2003. Rekod-rekod Elektronik
ini termasuklah surat menyurat atau dokumen
rasmi yang dihasilkan melalui penggunaan
Microsoft Office seperti pemprosesan perkataan,
lembaran kerja, grafik, persembahan, e-mel dan
maklumat dalam bentuk data-data dari
pangkalan data.
Rekod atau data elektronik yang masih aktif di mana
tindakan masih perlu diambil keatasnya, boleh disimpan di
Jabatan sehingga tindakan keatasnya selesai dan apabila
Jabatan tidak memerlukannya lagi, Jabatan dimestikan
menghantar rekod atau data yang tidak aktif dan
mempunyai nilai arkib (archival values) ke Arkib Negara
dalam format dan prosedur yang ditentukan oleh Arkib
Negara.
Arkib Negara perlu dirujuk terlebih dahulu sebelum
tindakan memusnahkan sebarang rekod atau data
elektronik.
[ref] : Dasar dan Garis Panduan Pengurusan Rekod Kerajaan

5. Project
Background
Project
Key
Component
Content
Standard
&
Compliance
Content
Console
&
Management
Content
DRM
Management
Content
Collabora8on
3rd
Party
Integra8on
This
project
is
proposed
based
on
the
5
main
components.
• Content
Console
&
Management
• Content
DRM
Management
• Content
CollaboraAon
• Standard
&
Compliance
• IntegraAon
and
centralizaAon.

6. Project
Case
Study
Interna8onal
ECM
&
DRM
Implementa8on
• USA
• E-­‐Government
Electronic
Record
Management
IniAaAve
based
on
DOD
5015.2-­‐STD
(SpecificaAon
by
Department
of
Defense)
• In-­‐house
developed
system
EDRMS(Electronic
Records
Management
SoYware
ApplicaAon)
–
NARA
ERA
(Electronic
Records
Archives)
• API
Level
on
record,
content
and
applicaAon
federaAon.
• No
DRM
implemented
based
on
OpenGoverment
iniAaAve,
content
are
accessible
to
all.
• Australia
• ICA/ADRI
-­‐
Australasian
Digital
Recordkeeping
IniAaAve
(Federal
NAA)
• VERS
-­‐
Victorian
Electronic
Records
Strategy
(State&
Territory
PROV)
• PROV
own
DRM
standard,
VEO
(VERS
Encapsulated
Objects)
using
XML
format.
• Mixed
of
EDRMS
used
by
state
under
PROV
(Highly
Interoperability)

7. Project
Case
Study
cont’d
Interna8onal
ECM
&
DRM
Implementa8on
• New
Zealand
• ERKSS
–
Electronic
Record
Keeping
Standard
(NaAonal
Archive)
• NZ
E-­‐GIF
–
New
Zealand
Government
Interoperability
Framework
• 7
Service
layer;
network,
data
integraAon,
business
services,
access
&
presentaAon,
web
service,
security
&
best
pracAce.
• (Best
PracAce
Layer)
TC/DRM
–
Trusted
CompuAng
&
Digital
Rights
Management
• European
• MoReq2
–
European
Union
Model
Requirement
for
the
Management
of
Electronic
Record
• Mixed
implementaAon
of
EDRMS
applicaAons
(Highly
Interoperability).
• DRM
under
opAonal
module
based
on
Moreq2(2008)
spec.
10.9

8. Project
Case
Study
Current
Scenario
in
Malaysia
• Malaysia
CreaAve
Content
EPP
has
been
iniAated
to
foster
the
development
of
creaAve
industry.
• Ownership
of
the
content
are
being
held
by
many
parAes
with
their
respecAve
plans,
business
approaches
and
implementaAon
methods,
models
and
jusAficaAons.
• 6
Government
Agencies
(Arkib
Negara
Malaysia,
Bernama,
Filem
Negara
Malaysia,
Finas,
Jabatan
Penerangan
and
RTM)
are
the
main
owners
of
the
content,
several
key
issues
are
sAll
being
negoAated,
namely
• StandardizaAon
(naming
convenAon,
content
formats,
etc)
• ConsolidaAon
• Scope
of
responsibility
of
respecAve
agencies
• Business
focus

9. Project
Case
Study
Opportunity
and
threat
Current
Scenario
Crea8on
of
independent
silos
of
content
bunkers
by
respec8ve
agencies
if
standardiza8on
is
not
established
Content
sharing
will
not
be
able
to
be
set-­‐
up
Treats
that
will
hinder
consolida8on
Standardized
content
naming
conven8on
Specially
developed
and
customized
DRM
solu8on
for
ANM
Opportuni8es
that
need
to
be
considered

10. Project
Case
Study
Content
Type
Document
• Books
• Manuscript
• Magazine
• Newspaper
Video
• Short
clip
• Documentary,
etc
• Amateur
recording
Audio
Clips
• Press
conference
• Audio
Recording

11. Project
Case
Study
Content
Ownership
Matrix
Agency
Document
Video
Audio

12. Project
Case
Study
Indica8ve
Financial
Impact

13. Project
Case
Study
Moving
Forward
CES
implementaAon
next
steps
will
be
• Establish
standardizaAon
record
exchange
Eg;
metadata;
content
naming
convenAon,
format,
etc
• Consolidate
content
silos,
if
any
into
a
common
plaForm
between
agencies
to
ensure
content
sharing
will
be
possible
• Adopt
open
soluAon
and
open
technology
plaForm
that
is
scalable
• Strategically
partner
with
local
soYware
developer
to
customized
and
develop
Malaysia’s
own
Content
Ecology
Services
PlaForm.

14. Content
Ecology
Services
Proposal
Overview
The
objecAve
of
Content
Ecology
Service
(CES)
is
to
provide
a
complete
package
and
full
soluAon
of
Document
Lifecycle
Management
and
Content
Archiving
Standards
for
ANM
and
others
agencies/ministries
under
Malaysia
Government.
• To
establish
a
smart
and
efficient
content
sharing
protocol
amongst
agencies
and
ministries
in
the
government
using
standard
and
common
guidelines.
• ApplicaAon
Services
will
enable
smaller
agencies
to
use
a
complete
and
centralized
Content
Management
ApplicaAon
hosted
by
ANM
and
hence
reduces
Total
Cost
of
Ownership.
• Using
Digital
Rights
Management
(DRM)
to
control
the
distribuAon
and
protect
rights
of
the
content.
• DRM
also
increased
security
of
the
document
and
content
by
managing
and
tracking
the
usage
of
the
content.
• Content
Community
will
enable
all
users
to
provide
a
content
collaboraAon
portal
with
capabiliAes
of
E-­‐Commerce.

15. Content
Ecology
Services
Development
Concept
CES
will
be
developed
based
on
the
these
main
principles
to
ensure
the
deliverable
of
the
project
and
visible
impact
on
the
implementaAon.
Open
Standard
Technology
• Open-­‐source
library
and
framework
• InternaAonal
open
standard
• No
vendor
lock-­‐in
Palern
Base
Architecture
• All
object
and
component
can
be
reusable.
• Later
development
can
refer
to
complete
API
specificaAon.
• System
design
can
be
easily
extend
without
major
modificaAon.
MulAple
Tenant
&
Repository
• Fast
mulA
tenant
deployment
• Flexible
&
manageable
mulAple
remote
repository

16. Content
Ecology
Services
Architecture
Overview
Content
Ecology
Service
System
consist
of
3
main
modules.
By
designing
the
applicaAon
into
such
framework
architecture,
it
will
enable
these
main
modules
to
be
used
by
mulAple
agencies
without
any
extra
modificaAon.
• Content
Console
&
Management
• Content
DRM
Management
• Content
CollaboraAon

17. Content
Console
&
Management
System
Module
Overview
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
mulAple
and
remote
repositories.
• Applica8on
Federa8on
Framework
• Content
Browsing
Module
• Content
Compliance
Module
• Content
Workflow
Module
• Document
Security
Module
• En8ty
Extrac8on
Module
• Data
&
Text
Mining
Engine
• Media
Streaming
Engine
• Content
Rendi8on
Engine

18. Content
DRM
Management
System
Module
Overview
Content
DRM
&
Management
providing
out
of
box
digital
rights
of
management
for
the
content
in
repository
either
local
or
remote.
It
will
manage
and
track
distribuAon
of
the
content
through
mulAple
channels
using
proper
DRM
client
developed.
• Asset
Management
Module
• Asset
Usage
Tracking
Module
• Asset
Capture
Module

19. ANM
Content
Ecology
Services
Servers
Others
Agencies
MyCC
Repository
ANM
Repository
Content
Management
Interoperability
Service
MyCC
DAM
Portal
ANM
Online
Finding
Aids
-­‐
FINAS
-­‐
Filem
Negara
-­‐
RTM
-­‐
Jabatan
Penerangan
-­‐
Bernama
Users
Cloud
(WAN)
System
Architecture
Content
CollaboraAon
PlaForm

20. ANM
Secure
Repository
MyCC
DAM
Portal
IO
Exchange
IP
Asset
Management
IP
Asset
Usage
IP
Asset
Crea8on
COMPASS
AMS
MAMS
ANM
Content
Ecology
Services
Internal
CMIS
ApplicaAon
Workflow
System
Architecture

21. Content
Ecology
Services
Open
Standard
Integra8on
CMIS
CES
Core
Content
Collabora8on
Module
JAX-­‐WS
JAX-­‐RS
Java
API
(POJO)
WebDAV
CMIS
API
Request
Web
Service
/
Rest
/
DAV
API
CES
integraAon
will
be
uAlizing
the
most
used
enterprise
level
open
standard
available.
By
leveraging
open
standard
and
technology,
system
can
be
easily
scale
through
integraAon
protocol
in
the
future.
New
applicaAons
or
modules
can
be
developed
to
complement
the
CES
framework.

22. Content
Ecology
Services
Text
&
En8ty
Extrac8on
EnAty
ExtracAon
is
text
enAty
extracAon
engine
&
library
for
Malay,
English
and
other
major
language.
It
will
automaAc
extract
enAty
such
as
locaAon,
people,
organizaAon,
event
and
others.
The
extracted
enAty
can
be
used
as
metadata
for
the
document
or
content
for
later
advance
searching.
Bibliography
Document
Content
Content
Descriptor
Person
Organiza8on
Loca8on
Source
En8ty
Extrac8on
Informa8on
Index
Metadata
Mapping

23. Content
Ecology
Services
Applica8on
Federa8on
Services
Overview
CES
ApplicaAon
FederaAon
Services
provide
help
to
ANM
to
deal
with
3
main
issues;
IntegraAon,
StandardizaAon
and
ConsolidaAon.
An
integraAon
strategy
that
will
let
other
agencies’
user
to
manage
their
content
in-­‐place
by
federaAng
or
moving
content
into
CES
ApplicaAons
for
a
gradual
and
controlled
migraAon.
Below
are
the
key
features
of
the
services.
• CES
provide
mulA-­‐tenant
remote
hosted
CES
ApplicaAons
through
AFS
applicaAon.
• By
using
CES
ApplicaAon
proxy
in
local
environment,
access
speed
to
the
system
will
be
improved.
• Capable
of
using
local
repositories
for
content
storage.
• Less
TCO
and
iniAal
investment
for
government,
only
require
deployment
and
training
cost.
• Faster
content
management
applicaAon
deployment.
AFS
IntegraAon
Channel

24. Content
Ecology
Services
Applica8on
Federa8on
Services
Features
All
applicaAon
providing
a
set
of
common
feature.
• Virtual
Repository
for
mulAple
tenants.
• Look
and
feel
customizaAon.
• External
Repository
SynchronizaAon
• Centralized
user
authenAcaAon.
Content
Management
Module,
will
enable
users
to
create
and
manage
their
content
in-­‐
place.
E-­‐Commerce
Portal,
will
enable
users
to
sell
and
showcasing
their
content
online
with
capability
of
making
a
payment
online.
Digital
Rights
Management,
will
enable
users
to
protect
their
content
and
tracking
the
distribuAon
of
the
content.

25. AFS
Remote
Hosted
With
Local
Proxy
AFS
Remote
Hosted
Content
Ecology
Services
Applica8on
Federa8on
Services
Deployment
Diagram
Agency
X
Agency
Y
ApplicaAon
FederaAon
Services

26. Integra8on
Strategy
What
Is
CMIS
?
Content
Management
Interoperability
Services
(CMIS)
is
a
specificaAon
for
improving
interoperability
between
Enterprise
Content
Management
systems.
OASIS,
a
web
standards
consorAum,
approved
CMIS
as
an
OASIS
SpecificaAon
on
May
1,
2010.
CMIS
provides
a
common
data
model
covering
typed
files,
folders
with
generic
properAes
that
can
be
set
or
read.
There
is
a
set
of
generic
services
for
modifying
and
querying
the
data
model,
and
several
protocol
bindings
for
these
services.
• Is
language-­‐agnosAc
(REST
and
SOAP
are
implemented
in
many
languages)
• Decouples
web
service
and
content.
So
CMIS
can
be
used
to
access
an
historic
document
repository.

27. Integra8on
Strategy
Major
CMIS
Implementers
The
iniAal
work
of
developing
the
momentum
and
use
cases
that
led
to
the
CMIS
proposal
was
conducted
by
the
iECM
IniAaAve
sponsored
by
AIIM1.
This
ongoing
project
to
foster
interoperability
among
ECM
systems
is
supported
by
the
collaboraAve
efforts
of
governmental,
commercial,
vendor,
and
consulAng
organizaAons.
[1]
AIIM
–
AssociaAon
for
InformaAon
and
Image
Management

28. Integra8on
Strategy
IBM
FileNet
Overview
FileNet
is
core
document
management
engine
For
IBM
content
manager
soYware.
Below
is
the
part
of
latest
key
feature
for
the
IBM
FileNet
• It
supports
a
wide
range
of
content
types
including
XML
documents,
Office
documents,
web
pages,
photos,
voice,
images,
and
process
definiAons
and
templates.
• Content
Management
Interoperability
Services
(CMIS)
standard
support
makes
it
easier
to
integrate
FileNet
Content
Manager
into
exisAng
installaAons
of
MicrosoY
SharePoint,
SAP,
and
other
parAcipaAng
vendors.
• DITA
support
speeds
and
simplifies
the
creaAon
of
technical
publicaAons.
• Content
FederaAon
Services
lets
customers
manage
content
in-­‐place
by
federaAng
or
moving
content
into
FileNet
Content
Manager
for
a
gradual
controlled
migraAon

29. CMIS
Channel
Integra8on
Strategy
IntegraAon
Channel
•
Agency
already
using
major
CMS/DAM
instance
and
local
repository.
•
Current
CMS/DAM
installaAon
is
CMIS
compliance.
AFS
Channel
• Agency
not
using
or
planning
to
used
a
CMS/DAM.
• Repository
can
be
hosted
local
or
in
CES
zone.
Under
CES
iniAaAve,
remote
agencies
have
been
provide
two
channels
to
leverage
the
power
and
usability
of
CES
System,
both
channels
provide
compliance,
integraAon
and
centralizaAon.
Deployment
of
any
channel
only
require
training
and
configuraAon
of
the
component
in
environment.

30. Integra8on
Strategy
Reduce
TCO
(Total
Cost
Ownership)
Master
Deployment
Deployment
1
Deployment
2
Deployment
3
Deployment
N
AYer
implementaAon
of
CES,
government
saving
million
of
IT
budget
on
any
future
content
manager
requirement.
ECM
Investment
CES
Expansion

31. Agency
Design
Development
Configura8on
Training
Integra8on
Strategy
AddiAonal
Deployment
Requirement

32. E-­‐Commerce
/
Trading
Plaaorm
Sobware
Step
1:
Consumer
will
browse
the
content
on
the
E-­‐Commerce
portal
or
any
trading
soYware
developed
using
Marlin
Client
SDK.
ANM
Content
Ecology
Service
IO
CES
Compa8ble
Repository
CES
DRM
Asset
Management
Module
How
DRM
Works
Gesng
the
content
CES
DRM
Asset
Usage
Module

33. CES
DRM
Asset
Usage
Module
E-­‐Commerce
/
Trading
Plaaorm
Sobware
Step
2:
Web
store
(E-­‐Commerce
Portal)
will
communicate
with
back-­‐office
to
acquire
the
business
token,
Later
will
generate
acAon
token
(instrucAon
set)
to
pass
to
client
soYware.
ANM
Content
Ecology
Service
IO
CES
Compa8ble
Repository
CES
DRM
Asset
Management
Module
How
DRM
Works
GeneraAng
AcAon
and
Business
Token
[A]
Token

34. CES
DRM
Asset
Usage
Module
E-­‐Commerce
/
Trading
Plaaorm
Sobware
Step
3:
AcAon
token
pass
to
content
manager
for
processing
and
prepare
the
content
for
delivery.
Business
in
AcAon
Token
will
be
verified
and
process
for
content
packaging.
ANM
Content
Ecology
Service
IO
CES
Compa8ble
Repository
CES
DRM
Asset
Management
Module
How
DRM
Works
Processing
A
Token
[A]
Token

35. CES
DRM
Asset
Usage
Module
E-­‐Commerce
/
Trading
Plaaorm
Sobware
Step
4:
License
or
cerAficate
in
AcAon
token
will
be
passed
to
client
soYware,
content
will
be
decode
by
Marlin
Client
SDK.
ANM
Content
Ecology
Service
IO
CES
Compa8ble
Repository
CES
DRM
Asset
Management
Module
How
DRM
Works
Content
Delivery
[A]
Token

36. CES
DRM
Asset
Usage
Module
E-­‐Commerce
/
Trading
Plaaorm
Sobware
Step
5:
Customer
will
receive
and
view
the
content
with
the
proper
rights
assign
by
the
Content
Ecology
Service
DRM
ANM
Content
Ecology
Service
IO
CES
Compa8ble
Repository
CES
DRM
Asset
Management
Module
How
DRM
Works
Receiving
The
Content

37. CES
Content
Collabora8on
CES
Content
Collabora8on
Embeddable
Java
Applet
Web
Client
All
CMIS
Compa8ble
ECM
Applica8on
iGPaper
:
Portable
Electronic
Paper
Device
CES
Content
Access
Client
Content
Access
Channel
Content
under
CES
can
be
accessed
through
two
(2)
main
channels;
Marlin
DRM
Client
and
CMIS
compaAble
client.
Each
channel
provide
a
variety
of
soYware
client
and
devices
that
can
be
extend
easily.

38. CES
Content
Access
CMIS
CompaAble
ECM
ApplicaAon
CMIS
standard
and
protocol
have
been
supported
by
various
ECM,
CMS
and
Blog
System
developer.
To
include
CMIS
compaAble
content
only
require
minimal
programming
or
configuraAon.
CES
Compa8ble
Repository
CES
Content
Collabora8on

39. CES
Content
Access
Java
Applet
Web
Client
Access
Marlin
(Sushi
Marlin
Client
SDK)
Java
Applet
is
a
embeddable
plug-­‐in
or
applet
that
can
be
use
in
any
web
page
with
a
minimal
configuraAon.
All
communicaAon
with
CES
DRM
server
will
be
done
automaAcally
using
secure
protocol
to
display
selected
content.
CES
DRM
Asset
Usage
Module
CES
Compa8ble
Repository

40. CES
Content
Access
iGPaper
:
Portable
Electronic
Paper
Devices
iGPaper
is
a
prototype
of
portable
electronic
paper
device
that
will
enable
to
access
content
in
CES.
• Reading
a
DRM
protected
content
or
document
from
CES
server.
• Embedded
fingerprint
will
enable
document
signing
and
enhanced
content
access
control.
• Eco
friendly
and
less
energy
display
usage
with
60%
saving
compare
to
others
device
and
technology.

41. CES
Content
Access
iGPaper
Prototyping
58mm
17mm
UPEK
TCESC4K
TouchStrip
Fingerprint
•
TCD50
Digital
ID
Hardware
Engine
Overo
GumS8x
Computer
on
Module
with
•
600mhz
ARM
Processor
•
512Mb
flash
memory
•
Bluetooth
&
wireless
module
processor
Monochrome
E-­‐INK
Pearl
Imaging
Film
•
Black,
white,
grayscale
•
Bit
Depth
:
4bit
gay
16
level
•
Viewing
angle
:
180
degrees
•
ResoluAon
:
200
DPI
iGPaper
prototype
will
be
using
latest
embedded
hardware
and
module.
Listed
is
the
basic
building
block
to
develop
a
iGPaper
prototype
devices.

42. Q&A
azri@nema8x.com