►
From YouTube: EV Battery Parts Traceability Pilot at MOBI
Description
Rajat Rajbhandari, PhD give the community some insights on the pilot through for tracking EV batteries parts that is being developed by MOBI Mobility Open Blockchain Initiative.
----
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 #Blockchain
C
B
C
Okay,
beautiful
well
welcome
everybody
to
thursday
was
it
march,
24th
2022
the
supply
chain
and
trade
finance
special
interest
group
session
today.
We'll
have
rajat
joining
us
here
by
representing
moby
today,
we'll
give
him
a
second
here,
because
he
has
a
day
job
we'll.
Let
him
talk
about
it.
Dex
freight
a
little
bit
here
on
his
day
job,
but
he's
also
a
big
part
of
moby
he's
been
involved
with
it
for
a
while.
I
contacted
him
when
I
saw
some
stuff
about
dex
freight
and
thought
that
he
might.
C
It
might
be
an
interesting
to
hear
about
that
and
it
turns
out
the
dextrade
isn't
using
hyper
ledger,
but
moby
is,
and
so
that's
why
rajad
is
going
to
share
with
us
this
eve
battery
pack,
traceability
pilot
at
moby,
so
we're
recording
this
session
here,
as
is
normal
with
the
case
with
hyper
ledger.
Events
all
are
welcome
and
any
any
trust
thoughts.
We
don't
have
those
part
of
the
charts,
but
you
know
this
is
an
open
session
here.
C
A
A
B
B
B
Great,
I
do
have
to
sign
off
like
five
minutes
prior
because
I
need
to
have.
I
need
to
go
to
another
talk
if
that's
okay
with
y'all,
absolutely
all
right,
then
well!
Thank
you,
tom
and
and
andrea
and
the
and
the
sig
for
the
opportunity
to
come
and
talk
to
you
come
and
talk
to
y'all,
and
forgive
me
for
for
not
having
pretty
good-looking
slide
decks.
B
So
they're
pretty
boring
at
this
point,
but
I'll
try
my
best
to
to
to
make
a
good
point
of
of
what
we're
trying
to
do
and
and
hopefully
we'll
learn
something
out
of
out
of
the
of
the
work
we're
doing
so.
I'm
gonna
talk
about
the
av
battery
pack,
traceability
pilot
that
moby
is
doing
and
hold
on
so
okay.
There
you
go
so
so
today's
agenda
is,
is
I'm
going
to
talk
about
the
pilot
objectives
and
scope?
B
B
B
A
global
consortium
of
mobility
companies
started
in
2018,
so
we
have
members
about
100
or
plus
members,
including
top
top
10
oems,
for
gm
honda,
toyota
industries,
bmw,
we
have
tier
one
suppliers
like
denzo,
hitachi,
tochu
and
service
providers
like
censure
infrastructure,
provides
like
aws
and
and
a
lot
of
good
folks
that
are
in
mobility,
space,
contributing
to
moby's
core
core
objective
of
creating
various
standards
with
regards
to
using
blockchain
and
associated
technologies
and
mobility.
Verticals.
B
The
objective
of
the
group
is:
is
develop,
data
specifications
and
reference
architectures
and
other
standards
that
will
prescribe
interfaces,
data
structures,
on-chain,
blockchain
storage,
those
primitives,
as
well
as
some
governance
regarding
the
use
of
blockchain
in
various
supply
chain,
use
cases
and
and
supply
chain.
As
you
all
know,
it's
quite
complex
and
before
I
was
part
of
the
working
group
I
had,
I
had
no
knowledge
of
the
nuances
of
automotive
supply
chain
which,
which
turned
out
to
be
very,
very
complex.
B
The
the
first
task
is
is
to
develop
standards,
data,
schemas
reference,
implementations
and
then
the
second
phase
is
to
then
sort
of
battle
test
those
standards
because
we
want
we
want
to
learn.
You
know.
What's
you
know
if
the
standards
are
good
enough
for
for
field
work
and
actual
implementation,
so
the
pilots
we
found
that
pilots
are
a
good
way
to
sort
of
battle
test
those
standards.
B
Tracking
trace-
and
the
first
thing
we
decided
was:
why
do
we
need
parse
disability
or
why
do
the
the
stakeholders
need
power,
stressability
and,
and
it
kind
that
need
has
sort
of
evolved
over
time?
That's
what
I
felt
part
of
being
the
working
group.
Initially
it
was
more
about.
You
know
how
to
reduce
the
recall
cost
of
those
high
value
parts.
A
lot
of
those
high
value
parts
are
also
called
safety
parts,
because
those
parts
are
the
one
that
they're.
A
B
Scrutinized
under
if
there's
a
massive
recall
and
regulatory
bodies
like
it's
a
nstsa
and
and
other
european
regulatory
bodies,
you
know
those
look
closely
on
on
those
safety
parts
and
then
for
the
last
I
would
say
five
years
the
big
oems
have
all
started
talking
about
their
sustainability
goals.
You
know
they
want
to
be
carbon
neutral
by
10
years
and
reduce
carbon
emissions
by
x
percent.
So
they've
all
made
those
made
those
announcements
so
that
now
that
I
guess
they
have
to
live
with
it.
B
B
C
B
So
that's
the
third
point.
The
fourth
point
is
reducing
losses
due
to
counterfeit
parts.
This
is
this
is
known.
This
is
a
this
could
be
a
big
problem.
This
has
been
a
big
problem
for
oems,
especially
now
that
that
the
onions
are
slowly
moving
into
3d,
3d,
printing
and
they've,
seen
their
their
their
3d
printing
plans
and
files
being
you
know,
stolen
and
all
that
stuff.
C
B
It's
mostly
the
the
first
market,
not
not
so
much
an
aftermarket,
but
they
do
recognize.
The
the
the
whole
counterfeit
part
has
the
potential
where
the
the
aftermarket
devices
may
not
follow
the
spec
of
of
the
original
design
and
they
could
be
added
to
the
to
the
vehicles
and
they
have
issue
of
now.
You
know
what
do
we
do
with
the
warranties
right,
so
it
was
discussed,
but
it's
mostly
that
the
whole,
the
counterfeit
part
scope
is.
I
think
it
includes
the
aftermarket
power
system.
Okay,
good.
Thank
you.
B
So
as
we
as
we
thought
about
the
the
whole,
you
know
parts
track
and
trace.
So
we,
the
first
thing
we
we
did
was
we
defined
the
scope,
and
then
we
spend
about
a
couple
of
months
working
on
the
workflow,
the
actual
workflow,
of
how
parts
move
upstream
and
downstream
from
you
know,
tier
tier
one
suppliers
all
the
way
to
the
oem
to
the
dealers
and
all
the
way
to
the
end
user
and
at
the
same
time
we're
also
thinking
about
okay.
B
A
B
And
trace
the
the
physical
custody
of
of
parts
as
they
move
upstream
and
downstream.
So
so
we
we
say
we
call
this
a
multi-layer
construct.
Is
you
know?
First,
let's
do
the
foundation,
which
is
the
the
physical
custody
of
parts
and
then
and
then
we
can
start
adding
other
applications
on
top
the
the
the
complexity
comes
from
from
you
know,
one
of
these
kind
of
realities
of
the
automotive
supply
chain,
which
is
there
are
several
tier,
a
tier
one,
can
provide
parts
to
several
oems.
B
A
tier
n
can
provide
materials,
and
you
know
basic
parts
to
several
tier
ones,
but
as
you
go
down
like
from
ou
to
the
oem
level,
you
know
so
they
get,
they
obviously
receive.
You
know
different
kinds
of
parts
based
on
their
specs,
maybe
from
the
same
tier
same
interior,
same
company,
because
the
because
their
relationship,
even
though
the
relationship
is
one-on-one,
they're,
they're,
getting
materials
and
some
you
know
core
parts
from
from
different
parts,
different
different
tier
and
suppliers.
C
B
You
know
common
documentations,
like
delivery
notes,
delivery
notes,
advanced
shipment
notifications,
bill
of
ladings
those
kind
of
things,
and
one
of
the
things
that
they
mentioned
was
like
a
lot
of
times.
The
identity
identity,
that's
assigned
by
a
tier
tier
one,
may
not
be
recognizable
by
oem
and
so
on
and
so
forth.
B
So
our
challenge
was
to
okay.
You
can
create
a
new
identity
structure,
but
it
still
needs
to
be.
It
still
needs
to
encapsulate
the
existing
identity
structures
that's
assigned
by
which
are
mostly
serial
numbers.
That's
assigned
by
you
know,
manufacturers
right.
So
that
was
a
challenge
and
then,
if
you
want
to
do
you
know
the
the
provenance
of
parts
through
blockchain
or
dlt,
or
what
have
you
then
those
identity
structure
has
to
be
has
to
be,
has
to
be
the
same.
B
B
B
B
Typically
in
an
av
like
tesla,
you
have
16
modules
per
pack
and,
and
one
pack
has
other
components
like
battery
management
systems
and
circuits
and
all
that,
but
usually
they
have
like
16
modules
and
each
module
has
a
bunch
of
cells.
I
think
there's
like
36
48
cells
or
something
like
that.
So
then
the
question
was
okay.
You
know
you
want
to
track
pac
and
you
want
to
track
modules.
B
So
we
have
we've
categorized
the
pilot
in
two
objectives,
the
business
objectives
and
the
technical
objectives,
the
business
objectives
for
from
from
you
know
the
moby
member
point
of
view.
Is
you
know
we
wanna?
They
want.
You
know
they
wanna,
be
they
wanna
be
prided
with?
What's
what
are
the
lessons
learned?
What
are
the
challenges?
What
are
the
solutions?
What
are
the
related
to
to
scaling
this
type
of
physical
tracking
trace
they?
Obviously,
we
also
want
to
be
able
to
show
you
know
how
what
happens
when
somebody
wants
to
query.
B
You
know
who
has
the
battery
pack,
who
has
the
battery
module
for
first
life?
Second,
life
use
cases
at
any
given
time
right.
An
example
of
that
is
that
makes
the
recalls
a
lot
easier,
be
able
to
estimate
time
resources
required
to
move
battery
packs,
and
so
this
is
with
regards
to
estimating
greenhouse
gas
emissions
during
the
transportation
process.
As
you
all
know,
transportation
also
creates
a
significant
greenhouse
gas
emissions
and
and
also
carbon
footprint.
B
B
We
also
the
pilot,
obviously
has
to
maintain
the
current
workflow
right
that
the
poems
and
suppliers
typically
use
and
in
terms
of
technical
objectives.
We
wanted
to
test
how
various
dlt
blockchain
primitives
work,
including
verified,
credential,
did's,
zero
knowledge,
proofs
and
and
also
kind
of
battle
test,
mobi
and
other
standards
that's
available
out
there,
including
movies,
vid
and
vc's,
and
that's
our
w3c
standards.
There's
new
one.
That's
coming
up
replication,
2020.,
so
yeah.
We,
we
kind
of
outlined
these
two
major
objectives
of
the
pilot.
C
B
C
B
Okay,
so
just
to
continue
on
the
current
scope,
dv
battery
module
physical
track
and
trace
upstream
and
downstream,
we
wanted
to
limit
the
suppliers
to
tier
one.
Obviously,
there's
multiple
tiers,
we
call
it
tier
end
suppliers
just
to
keep
things
simple
so
in
in
the
process
of
physical
movement
of
those
parts
or
packs
the
the
logistics
process
is.
Is
we
want
to
simplify
it?
So
we
just
assume:
there's
one
logistics
provider,
that's
picking
up
parts
from
let's
say
a
supplier
and
and
from
the
supplier
and
delivering
it
to
an
oem.
B
If
you're
sending
a
part
you
know
cross-border
or
international,
then
you
have
multiple
logistics
providers
and
multiple
modes
involved,
but
we
wanted
to
for
the
for
the
sake
of
the
pilot,
given
the
time
and
time
and
time
and
resource,
we
want
to
keep
it
simple,
so
we
assume
there's
one
logistics
provider,
who's,
taking
care
of
all
the
information,
we're
not
doing
any
integrations
with
any
legacy
systems.
At
this
point,
that
would
be
a
significant
cost.
B
Cost
to
the
pilot
we're
also
not
working
on
any
governance
with
regards
to
the
the
layer,
zero
operation,
I'll
talk
about
the
layer,
zero
in
just
a
moment,
for
example,
you
know
who
can
be
part
of
the
part
of
the
track
and
trace.
You
know
who
runs
the
notes
and
those
kind
of
things,
so
we're
not
taking
care
we're
not
dealing
with
that.
B
It
includes
it's
based
on
the
the
verifier
credential
schema
that
birth
certificate
is
then
transferred
to
the
oem,
obviously
tier
one
supplier,
hires,
a
logistics
provider
and
then
the
logistics
provider.
You
know
picks
up
the
shipment,
you
know,
delivers
to
the
oem
and
there's
a
trip
start
and
and
and
certificates.
B
That's
you
know
provided
to
provided
to
the
logistics
provider
which,
which
says
which
provides
credentials
as
to
you
know.
When
did
they?
When
did
they
start
a
trip,
and
when
did
they
end
the
trip
and
if
they
were
able,
they
have
all
the
documentations
necessary
to
verify
if
the
right
right
pack
was
delivered
or
not,
based
on
the
communication
between
the
tier
1
and
oem?
B
So
it
basically
follows:
follows
that
ways
up
to
downstream
all
the
way
to
the
owner,
and
then
we
also
doing
sort
of
an
up
kind
of
reverse
flow.
Where
an
example
is
the
owner
reports
that
the
battery
pack
battery
pack
has
some
issues
takes
it
to
the
dealer,
and
the
dealer
looks
at
the
pack
and
dealer
says
I
think
you
know
five
out
of
the
16
modules
are
not
working,
and
in
that
case
the
dealer
sends
the
pack
back
to
the
oem
and
the
oem.
B
C
B
Of
trash
it
so
that
they
would
send
it
to
some
other
companies
too,
for
that
matter,
so
all
these
certificates
are
essentially
verified
credentials
using
w3c
standards
there.
So
one
thing
we've
done
is:
we've:
we've
created
all
these
structures
in
as
json
files
and
github.
So
any
member
who
wants
to
run
their
own,
you
know
pilot.
They
can,
just
you
know,
borrow
all
the
certificates
and
the
schemas
associated
with
that.
C
B
So
what
we're
working
on
is
a
battery
identification
number
which,
which
would
look
very
similar
to
the
vehicle
identification
number
that
we're
all
familiar
with.
That's
the
17
digit
code
that
you
see
on
the
windshield
and
the
door,
so
we're
working
on
that,
so
that
that
anybody
can
look
at
it
and
kind
of
decode.
Some
basic
information
about
the
pi
about
the
battery
there's
another
initiative
that
global
battery
alliances
is
working
on
in
response
to
eu
directive
is
to
create
a
battery
passport,
and
that
includes
rfid
or
qr
code.
B
All
right,
so
the
major
components
in
the
pilot,
the
obviously
we
need
to
take
care
of
the
the
ids
right,
the
vehicle
id
the
battery
id
and
the
battery
pack
id
that's
associated
with
the
vehicle
id
and
and
all
of
that,
so
we're
we're
we're
using
w3c.
For
that
there's
a
there's,
a
infrastructure
that
moby
is
is
is
building
it's
been
tested
right
now
with
with
our
oem
members,
it's
called
integrated
trust
network.
It's
essentially
basically
a
federated
network
of
us.
B
B
B
We
call
it
integrated
trust
network,
because
mobi
is
using
that
network
for
other
use
cases
as
well.
The
pilots
that
we're
doing
and
there's
a
bunch
of
our
members
are
already
running
the
nodes
and
some
are
in
the
face
somewhere
in
the
states
of
testing
those
nodes,
but
there's
a
middle
layer
which
is
sort
of
an
orchestration
layer
that
issues
the
verifiable
credentials.
B
So
we're
providing
some
basic
functionality
to
those
nodes
that
basic
functionality
is
the
you
know,
creating
your
dates
and
and
registering
those
dates
to
the
to
the
to
the
to
the
layer,
zero
and
depending
on
the
use.
Then,
then,
those
stakeholders
can,
you
know,
add
multiple
functionalities
to
the
to
the
to
the
node.
B
B
All
right
so
the
digital
twin,
the
node,
the
the
one
that
highlighted
in
red.
So
if
you,
if
we
kind
of
zoom
in
into
that
it
has
several
components,
I
I'm
not
good
at
explaining
all
these
components.
So
the
digital
twin
existentially
note
that
individual
members
run
have
a
bunch
of
components.
In
there
encrypted
data
evolved
universal
wallet,
they
are
sharing.
C
C
B
A
A
B
B
The
working
group
is
now
discussing
the
next
steps
in
the
pilot,
so
once
you
have
so
the
current
scope,
whether
we
expand
the
scope
horizontally,
include
more
suppliers
upstream
or
where
whether
we
add
depth
to
the
current
workflow.
So
that
means
adding
you
know,
warehousing
translating
modal
changes
and
other
tier
and
suppliers
right.
So
we're
working
the
committee's
actually
discussing
that
as
we
speak,
so
the
scaling
challenges
that
we've
already
kind
of
identified
is
you
know
we're
gradually
understanding
the
scaling
challenges
when.
C
B
It
may
not
be
a
significant
challenge,
but
it's
it
still
could
be
a
challenge.
If,
if
you
know
we're
talking
about
tier
and
suppliers
or
a
lot
of
them
are
small
businesses-
and
you
know
we-
obviously
we
still
need
to
work
on
the
governance
of
those
nodes,
because
the
federated
network
there's
also
possibility
of
sub
network
being
formed
different
depending
on
the
use
cases,
and
at
this
point
we
don't.
B
A
B
B
C
Beautiful
rajat,
thank
you
very
much
appreciate
it
here.
I
see
one
question
in
the
chat
box
here:
all
the
nodes
spin
up
over
cloud
or
native
hardware
nodes.
I
think
you
mentioned
aws,
so
maybe
that's
the
answer
to
the
question
but
I'll.
Let
you
answer
that
and
folks,
please
get
your
questions
up
whether
you
want
to
raise
your
hand
or
we'll
just
open
it
up
here
and
right
after
rajon
finishes.
You
can
ask
your
next
question
right
now.
C
And
but
sounds
like
some
of
those
might
be
their
own
dedicated
hardware,
nodes,
okay,
got
it
okay,
good!
I
I
have
one
question
and
then
we'll
go
to
the
floor
here.
How
much
time
did
you
spend
thinking
about
tokenizing
any
of
this
information
at
all,
or
it
was
like
not
not
even
worthwhile
at
this
point
in
time
to
have
that
discussion.
B
C
B
You
know
tokens
where
the
mobi's
position
is
not
to
talk
about
tokens
because
they're,
you
know
the
their
members
are
all
publicly
credited
companies
and
they
want
to
be
careful
not
to
get
associated
with
with
a
non-profit
like
mobi
issuing
tokens.
So
that's
one
with
regards
to
nfts
we're
we're
just
exploring
nfts
for
some
other
use
cases,
but
but
not
on
this
one.
So
this
one
we
feel
at
up
to
this
point.
C
A
A
C
C
All
the
identity
work,
which
is
itself
right,
yeah
exactly
it-
is
a
bit
challenging
all
the
things
so
for
the
folks
who
asked
rashad.
If
you
well
we'll
be
able
to
share
your
presentation
on
our
wiki
and
then
this
this
presentation
will
go
up
on
youtube,
so
people
can
watch
it
and
we'll
put
something
out
there
so
that
there's
a
link
and
then
we'll
get
that
to
you
also
rashad.