PERICLES partner Johannes Biermann (University of Göttingen) introduces the concepts of digital ecosystem and modelling in the context of change management and LTDP.

1. GRANT AGREEMENT: 601138 | SCHEME FP7 ICT 2011.4.3
Promoting and Enhancing Reuse of Information throughout the Content Lifecycle taking account of Evolving Semantics [Digital
Preservation]
Digital Ecosystem model
Johannes Biermann UGOE

2. Overview
1. Definition
2. Purpose
3. Model components
a. Communities
b. Technical Infrastructure
c. Policy Management
d. Quality Assurance
e. Change Management
f. Dependencies and Appraisal
g. Model Instantiation

3. The "Digital Ecosystem" is a concept with the
purpose for analysing and modelling the ability
of infrastructure to maintain the usefulness of
digital objects. A digital ecosystem consists of
all the entities and relations influencing or
necessary for a successful use at a later point
in time.
What is the Digital Ecosystem?

4. to capture the current state of a system in order to
◦ capture processes that humans perform
◦ carry out experiments on change related questions
◦ simulate change & management of complex digital
ecosystems
◦ ranking and weighting of actions and components
◦ identify and resolve possible problems
◦ detection of policy violations
◦ trace the history of a changing ecosystem
◦ sheer curation approach
Why model a Digital Ecosystem?

5. another enterprise modelling technique like ARIS,
TOGAF, ArchiMate, ...
(which is divided into functional, data, business process
and system architecture models)
in depth modelling of entities
dictating a system architecture
a lifecycle model
What is the Digital Ecosystem not?

6. Digital Ecosystem & PERICLES context
Registration / Model update
Knowledge base
Metadata
extraction
PeriCAT
PET2LRM
Domain
ontologies
Model repository / Entity
registry
User interface
Model
builder
Test scenarios
User model
entry
Ontology
and entity
template
references
Content
Entities,
dependencies,
metadata
Validation
results
LRM
PET
Metadata for
embedding
Topic
maps
(Space)
Digital
Ecosystem
3rd party
Ontologies
stored/registered on

7. Main entities
Process
PolicyDigital
Object
Technical Service Community
User uses TS to get access to Processes and
Digital Objects
manage
executes
rulebase, constraints, validation
procedure, rulebase, constraints, validation
procedure, rulebase,
constraints, validation
rulebase,
constraints,

8. LRM provides a set of concepts, abstract notions and functions
Digital Ecosystem and LRM
Resources Dependencies Agents Events Versioning ...
Policy
Process
hard
rule
...
Software
Agent
Ecosystem
Agent
Policy
changed
Process
added
Digital Ecosystem extends LRM with a set of resources to model digital ecosystems

10. Ecosystem Communities

11. Technical Ecosystem Infrastructure

12. Ecosystem Policy Management - Part 1

13. Ecosystem Policy Management - Part 2

14. Ecosystem Quality Assurance

15. Ecosystem Change Management

16. Types of dependencies
print medium
strong dependency (hard): a dependency that must exist
clock time server
weak dependency (soft): an optional dependency, depends on the use case
rule based dependency: a complex dependency with criterias
video stream network
throughput >= 10 MBit/s
latency < 40ms

17. Ecosystem Appraisal
not significant
dependent
significant
(custom value)

18. The model provides templates of entities and relations
which need to be instantiated to get a model of a real
digital ecosystem.
Instances can be created via a Java interface with the
EcoBuilder
The EcoBuilder provides high level methods for well
defined modelling and creates an ontology file of the model
instance.
Therefore it is not necessary to be able to write ontology
files for creating an ontology of a digital ecosystem.
Ecosystem Model Instantiation