►
From YouTube: Does Industrial Asset Management Provide Good Use Cases for Verifia... - Oliver Pfaff & Andreas Kind
Description
Does Industrial Asset Management Provide Good Use Cases for Verifiable Credentials and Distributed Ledgers? - Oliver Pfaff & Andreas Kind, Siemens AG
This presentation investigates how decentralized trust technologies can help to automate the asset management in industrial automation. Industrial automation is concerned with the automation of production processes in manufacturing, utilities, and supply/service processes. Asset management is important: actors need to understand which equipment is used, where it is deployed, in which setup it is operated. This demands automation to improve asset information availability and quality. Ironically, automation for the asset management of industrial automation equipment is not yet championed by the industrial automation industry. Current practices use manual steps, media breaks, shortcuts. Improving the asset management for industrial automation requires advanced means to assign information to industrial automation equipment, to exchange and to process this information in a secure way.
Session Details & Slides (if available)- https://sched.co/j3fM
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerGlobalForum2021 #Blockchain
A
A
We
get
started
so
welcome
to
another
interesting
hyperledger
global
forum
session.
The
title
is:
does
industrial
asset
management
provide
good
use
cases
for
verifiable
credentials
and
distributed
ledgers?
It's
a
provocative
question.
In
a
way
my
name
is
andreas
kint.
I
am
in
charge
of
cyber
security
technology
here
in
siemens.
A
It's
a
global
team
that
covers
cyber
security
technologies
on
all
levels
of
the
siemens
enterprise,
the
siemens
production
and
siemens
products
and
solutions.
It's
a
quite
an
interesting
field.
What
brings
us
here
to
hyperledger
global
forum
is
a
really
very
concrete
problems
in
industrial
production,
around
machine
identities
around
extending
trust
into
production,
environment,
physical
context,
things
like
energy.
A
B
B
Andreas
and
me
both
are
cms
employees,
and
siemens
is
a
global
champion
in
industrial
automation,
start
off
with
a
few
slides
about
industrial
automation,
what
it
is
and
to
establish
a
common
ground
for
the
discussion
on
what
it
could
have
to
do
with
verifiable
credentials,
distributed
ledgers
and
so
on.
First
of
all,
what
you
see
here
is
a
distinguished
individual
in
the
industrial
automation
component.
B
Since
the
dimension
is
not
quite
clear,
I
think
it
would
be
something
like
10
centimeters
by
10
centimeters
by
10
centimeters,
so
not
too
big,
and
this
actually
is
a
piece
one
piece
of
an
industrial
automation
component,
and
this
is
used
as
a
part
of
machine.
A
machine
could
be
something
like
an
industrial
robot
and
that
becomes
part
of
things
which
are
production,
cells
or
sites,
and
these
components,
machines,
production
cells
sites
are
used
all
over
manufacturing
all
over
utilities
process.
B
Industries
and
so
on
and
so
forth,
so
that's
kind
of
a
common
component
which
is
kind
of
ubiquitously
used,
nor
it
has
some
properties.
So,
first
of
all,
there
are
components
which
are
called
actuators
and
sensors,
which
actually
interact
with
the
physical
world,
and
this
is
one
class
of
industrial
automation
component
and
there
are
other
classes
of
components
which
control
such
activators
and
sensors.
So
these
are
the
most
important
classes
of
components.
B
B
It
has,
of
course
identification
and
the
identification
comes
in
two
flavors.
You
can
identify
such
a
product
as
a
part
of
a
cohort
of
a
class
of
components,
so
there's
like
a
product
type
and
order
id
specific
information
by
which
you
identify
a
whole
class
of
components
and
there's
also
identification
on
an
individual
instance
level.
B
Such
a
component
of
course,
has
a
life
cycle
and,
on
the
left
hand
side
you
see
top
down
a
a
rough
chart
of
its
life
cycle.
It
starts
with
the
manufacturing
phase
where,
by
the
manufacturer
of
such
components,
the
actual
instance
is
manufactured.
Then
it's
kind
of
shipped
it's.
The
shipping
is
not
shown
here.
It
arrives
at
the
customer
side
and
then
it's
kind
of
bootstrapped,
so
it
must
be
installed,
it
must
be
commissioned.
B
B
Of
course,
it's
not
not
so
easy
to
read
here
from
from
a
kind
of
a
space
perspective,
the
interest
of
the
customers,
of
course,
to
maximize
the
operational
phase.
So
the
idea
is,
of
course,
this
component
should
run
24
hours
a
day,
seven
days
a
week
and
52
weeks,
and
when
this
is
happening,
some
data
is
produced.
So
next
thing
we
look
at
the
data
objects
and
here
it's
important
to
understand
that
we
have
different
classes
of
data
which
are
associated
cycle.
B
So
when
the
component
is
being
manufactured,
then
data
objects
are
being
generated,
which
we
call
product
master
master
data
and
think
of
things
like
items
would
be
the
serial
number
for
the
product
instance
or
things
like
the
mac
address,
which
is
bound
to
the
component
and
also
information
like
who's
the
manufacturer.
What
type
of
component
was
manufactured?
What
was
the
order
idea
which
hardware
software
version?
Do
we
have?
B
B
During
the
operational
phase,
we
have
operational
data
that
is
being
created
and
that
kind
of
reports
on
the
performance
of
the
component,
as
well
as
the
health
of
the
component
and
kind
of
the
maintenance
phase
and
the
off-boiling
phases
they
kind
of,
can
touch
certain
sets
of
information.
But
we
already
talked
about
the
most
important
ones.
B
B
We
have
a
couple
of
other
roles
which
can
be
the
consumers,
so
we
see
another
actor
in
such
an
industrial
automation
system
could
be
a
distributor
or
the
machine
builder.
The
system
integrator,
who
kind
of
builds
the
production
seller
or
plant
on
behalf
of
the
owner
and
the
owner
operator.
So
we
have
different
roles
along
the
value
chain
in
industrial
automation,
and
here
you
can
see
that
the
production
and
consumption
changes
with
respect
to
where
we
are.
B
The
short
summary
is:
there
is
no
single
entity
which
can
give
and
provide
all
information
that
is
relevant
for
an
industrial
automation
component
along
its
life
cycle,
and
we
will
see
that
that's
an
important
aspect
to
to
the
challenge
and
to
its
solution
that
we
discuss
in
a
moment
right.
So
next
question
is
the
customers,
so
the
the
the
owners
and
operators
of
industrial
automation
equipment.
B
Here
we
we
provided
some
information
from
a
recent
rfi
request
for
information
by
a
major
car
manufacturer,
one
of
the
top
five
car
manufacturers
and
that's
what
they
are
asking
for
and
let's
take
a
minute
to
understand.
So,
first
of
all-
and
I
hope
you
can
see
my
cursor-
I
go
to
the
sub
bullets-
they
give
a
list
of
information
items
they're
mostly
interested
in,
and
we
can
see
by
roughly
checking
it
that's
kind
of
a
union
between
the
production,
master
data
and
the
deployment
master
data,
so
they
won't
have
both.
B
B
They
want
to
have
it
for
each
and
every
component
and
the
number
of
such
components
can
be
quite
high,
so
it
it's.
You
easily
have
a
five
digit
number
of
industrial
automation
components
within
a
single
factory.
If
you
look
at
a
user
owner
like
a
car
manufacturer
and
the
production
of
some
cars,
there
are
also
smaller
deployments.
There
are
also
deployments
with
four
digit
numbers,
and
here
maybe
an
example
could
be
even
vessel
equipment
or
ship
equipment
is
one
of
a
major
market,
and
I
guess
the
numbers.
B
B
B
Well,
that's
what
the
customer
asked
for
and
again
the
information
was
it's
a
reasoned
requirement.
Now,
let's
double
check
where
we
are
so
the
question
is:
are
these
customer
demands
fulfilled
already?
And
here
we
look
at
three
dimensions.
First,
dimensions
is
the
third
thing.
So
can
we
get
the
information
at
all
and
it's
structured
according
to
the
ideas
the
customer
has,
they
suggest
something
like
a
profinet
identification
and
maintenance
data
record
profinet
is
one
of
the
important
field
buses
which
are
used
to
to
control
actuators
and
sensors.
B
Snmp
is
an
ivf
standard
for
network
management.
Opc
ui
is
an
industry
domain
standard
for
industrial
components,
and
here
you
can
see
the
overall
assessment
would
be.
We
have
a
partial
coverage
of
the
sourcing,
looks
like
the
profinet
e
m
data
is
best
in
providing
coverage,
but
they
only
cover
the
profinet
specific
data.
As
soon
as
you
have
an
industrial
component
which
runs
profinet
plus
x,
you
have
coverage
for
profinet,
but
you
don't
have
coverage
for
the
plus
x,
so
overall,
it's
powerful
next,
if
we
so
andreas
and
me.
B
So
if
we
look
at
the
level
of
protection
of
information
or
of
proving
that
information
question
is,
are
we
covered
here
and
the
answer
is
not
yet
typically.
For
instance,
profinet
e
m
data
is
self-asserted
information
without
any
protection
at
all,
so
it's
actually
pretty
simple
to
create
for
to
to
kind
of
create
fake
equipment
claiming
or
pretending
to
be
siemens
equipment,
because
there
is
no
safeguard
for
for
this.
I
m
data
as
f
as
of
today,
and
that
belongs
to
the
class
of
self-asserted
information.
B
B
B
B
We
have
two
candidates
here
which
look
appealing
to
us.
There
is
the
w3c
verifiable
credentials.
Here's
a
bit
of
generic
information
on
that
slide
about
verify
credentials.
I
guess
for
most
of
you,
there
is
not
much
too
much
news
on
that
slide.
So
maybe,
let's
quickly
concentrate
on
that
chart
here.
So
if
we
translate
that
to
industrial
automation,
the
component,
which
is
called
holder
here,
would
become
the
industrial
automation
component.
B
B
The
next
thing
is
based
on
what
we
talked
already.
They
need
production
data
production
data
is
understood
by
the
manufacturer.
They
need
deployment
data
deployment.
Data
is
understood
by
the
machine
builder
or
by
by
others.
So
we
will
have
multiple
issuers.
So
in
our
understanding
we
have
one
component,
which
is
the
holder.
Probably
we
have
one
verifier.
I
hope
you
can
see
my
mouse
cursor.
B
I
move
it
a
little
bit,
but
we
have
multiple
issuers
making
statements
about
that
component
and
the
verifier
asking
questions
about
that,
and
here
you
can
already
see
with
a
classical
model
here.
The
verifier
probably
would
have
to
ask
multiple
questions
to
understand
deployment
data,
as
well
as
production
master
data.
B
It
also
allows
to
kind
of
do
further
transformation
operations,
so
this
proposal
for
industrial
automation,
along
with
the
verifiable
credentials,
we
have
the
decentralized
identifiers-
and
here
it's
important
to
understand.
As
of
now,
they
provide
an
identification
fabric
which
is
used
in
the
context
of
variable
verifiable
credentials,
so
they
are
used
for
in
order
to
refer
to
verifiable
credentials,
schema
objects
or
to
actual
concrete
objects.
B
B
Two
steps,
so
things
start
with
an
issue
and
step
which
means
the
issuer
issues
credentials
to
the
industrial
automation
component.
The
indus,
the
androsco
automation
component
is
the
over
here
and
we
equip
them
with
rfid
credentials
again
here.
This
is
a
recurring
thing,
because
we
have
multiple
actors
able
to
say
something
about
the
industrial
automation
component.
While
the
owner
operator
is
asking
for
all
we
have
multiple
or
we
believe
there
will
be
multiple
in
the
issuance
steps.
There
will
be
multiple
issuers
providing
objects,
verified
the
credential
objects
to
a
single
industrial
automation
component.
B
This
is
addressed
already
in
the
w3c
verifiable
credential
data
model.
Next
step
would
be
the
presentation
step.
So
I'm
interested
I'm
curious
to
understand
something
about
my
industrial
automation
component
and
in
order
to
do
that,
I
interact
with
the
component
and
I
challenge
it
to
present
either
credential
or
verified
presentation,
and
I
do
this
in
the
role
of
an
owner
operator.
For
instance,
that's
also
addressed
in
the
w3c
verifiable
credential
data
model.
B
Then
there's
the
verification
step.
Once
I
obtained
my
verifiable
presentation,
I
need
to
check
it,
of
course,
with
respect
to
its
authenticity
with
respect
to
its
timeliness.
Things
like
that
that's
already
covered
in
the
w3c
data
model,
then,
after
checking
the
actual
information
that
I
got,
I
not
the
overall
context
that
I
operate
like
was
now.
I
understand
that
this
component
has
this
and
that
serial
number,
but
is
it
supposed
to
be
operated
within
my
production,
solar
site?
B
That
would
be
next
question
the
validation
step,
and
here
the
w3c
verification,
verifiable
data
model
intentionally
abstains
from
elaborating
that,
so
they
formulate
the
talk
about
the
validation
step,
which
is
a
good
idea,
and
but
they
abstain
from
detailing
it,
because
that
becomes
industry.
Specific.
B
B
And
here
the
answer
to
this
question
is
yes,
we
believe
some
lifting
is
needed,
and
this
concerns
both
actors,
or
especially
the
the
technology
and
solution
providers.
We
talk
about
in
a
minute
about
the
users
of
this
of
the
solutions,
but
actually
it's
not
a
rocket
science
that
has
to
be
done
and
the
following
items
from
the
work
items
that
have
to
be
addressed
in
doing
this.
B
Lifting
and
again
the
lifting
here
or
the
assumption
is
the
lifting
starts
with
the
artifacts
that
we
get
from
the
w3c,
such
as
decentralized
identifiers
and
verifiable
credentials,
and
for
the
verified
credentials.
The
the
the
proposal
is
for
the
assumption
is
we
need
to
have
specific
schemas
for
the
industrial
automation
domains.
B
B
We
talked
about
the
validation
procedure,
so
the
things
that
have
to
happen
or
should
happen
after
the
actual
verification,
technical
verification,
so
the
overall
context,
validation,
that's
something
like
I
said
before.
That's
d
scoped
for
a
good
reason
from
the
w3c
standards
that
would
have
to
be
filled.
B
There
also
needs
to
be
a
clear
understanding
on
what
the
verifier
role
is.
So
is
this
like
a
like
a
automated
component,
which
runs
continuously
in
in
a
production
cell,
or
is
it
more
kind
of
an
operator
tool
thing
that
is
being
used,
so
things
like
that
would
have
to
be
specified
and
and
identified,
and
also
it
looks
like
that.
B
As
I
told
you
before,
identification
information
already
is
there
and
there
is
not
really
an
interest
to
kind
of
to
go
back
to
zero
here
and
restart
the
whole
thing
with
an
empty
page.
So
the
decentralized
identifier
models
probably
have
to
take
into
account
that
they
are
already
there's.
There
are
identification
schemes
which
carry
a
value
both
for
the
manufacturer
organizations
as
well
as
for
the
owner
organizations.
B
The
quotation
here
gives
you
a
short
definition
of
our
understanding
of
asset
management
which
which
was
taken
from
wikipedia,
so
I
think
that
should
be
pretty
clear.
I
guess
to
everybody
and
the
the
importance
next
thing
that
isn't
relevant
here.
The
importance
of
asset
management
kind
of
is
self-evident.
B
In
industrial
automation,
we
look
at
the
owner
operator,
which
typically
are
legal
organizations.
This
is
not
you
and
me
at
home,
which
are
interested
in
a
smart
home
solution,
so
these
are
legal
entities
which
manufacture
some
goods
or
or
produce
some
some
utilities,
and
usually
they
are
pop
and
the
industrial
automation
components
provide
capital
goods
for
them
and
with
respect
to
that,
they
need,
of
course,
to
understand
what
they
have
and
in
which
kind
of
state
and
shape
that
is,
and
this
is
an
old
requirement.
B
It
is
solved,
but
actually
it's
kind
of
old
school
solved
like
spreadsheets
papers,
people
walking
around
the
the
asset
management
solutions
that
we
are
aware
of
are
actually
like,
digi,
the
digitization
right
now
and
when
we
would
use
the
emerging
technologies.
Trust
technologies
especially
verify
the
credentials
and
dispute
ledgers
in
a
smart
way.
B
Then
we
could
fill
the
gap,
so
asset
management
is
important,
and
here
we
try
to
to
establish
the
slogan.
Yes,
it's
there,
it's
kind
of
analog.
It's
done.
It's
happening,
it's
analog,
it's
not
net
digitized,
it
probably
has
to
be
digitized
and
the
technologies
we
were
discussing
can
fill
and
can
provide
an
important
or
can
play
an
important
role
in
doing
that.
B
So
expectation
management
is
also
important
when
we
think
about
how
we
could
exploit
this
potential.
When,
for
those
who
are
acting
or
working
for
technology
and
solution
providers,
the
message
would
be,
or
the
expectation
management
would
be.
What
we
see
that
we
can
get
from
from
organizations
like
w3c
is
something
I
would
term
raw
material
for
solving
industrial
automation,
use
cases
and
that's
not
yet
the
turnkey
solution,
and
that
was
the
slide
about
the
lifting
and
whether
it's
heavy
or
not.
So
something
has
to
be
done
in
on
top.
B
Yes,
some
lifting,
but
I
guess-
or
we
believe
it's
it's
not
really.
Having
lifting
for
those
who
are
on
the
side
of
technology
or
solution
providers,
then
there
will
be
some
procedural
changes
so
how
asset
management
is
happening
and
being
done
can
and
will
change
if
this
kind
of
process
takes
place,
but
there
is
no
fundamental
change
with
respect
to
whether
or
not
I
have
to
take
care
about
that
and
that,
where
the
slides
that
we
wanted
to
present
to
you.
A
Yeah
exactly
please
post
your
questions
into
the
chat.
I
know
we
have
only
a
couple
of
seconds.
Let's
just
reminded
us,
so
one
quick
question
from
somebody
otherwise
feel
free
to
reach
out
to
oliver
me.
We
would
be
quite
interested
in
exchange
on
machine
identities.
There's
a
question
from
simon:
how
do
you
verify
that
the
information
about
the
industrial
automation
component
is
maintained
correctly.