►
From YouTube: Blockchain and the use of RFID Chips in the supply chain
Description
A virtual meetup hosted by Hyperledger Atlanta featuring Matthew Russell from Auburn University as he presents what Auburn University's RFID Lab has been working on utilizing blockchain and RFIDs.
Matthew is a project manager at the Auburn University RFID Lab, overseeing all data initiatives. He currently leads the CHIP project, an initiative to capture and communicate serialized supply chain data over a Hyperledger Fabric blockchain. Matthew will detail the CHIP project and the learnings of the benefits, as well as what it takes to integrate serialized data, captured from sources like RFID, into a Hyperledger Fabric blockchain.
The RFID Lab is a research institution associated with Auburn University and focuses on the technical and business cases of identification technologies.
More about the event is at: https://www.meetup.com/Hyperledger-Atlanta/events/274619462/
----
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 #HyperledgerMeetups #Blockchain
A
A
A
So
today
we
do
have
arvind
university.
We
have
matthew
russell
from
army
university's,
rfid
lab,
we'll
be
speaking
today
for
our
first
groups
group
group
meeting
here
and
we'll
we'll
continue
this
and
hopefully
right
now,
we'll
do
this
on
thursdays
at
six.
We
start
at
6
30
today,
but
the
intent
is
to
be
at
six
going
forward
every
every
month.
You
still
got
to
decide
on
the
actual
date,
but
we
want
you
all,
as
you
did
with
the
survey,
to
give
your
input.
A
B
Okay,
well,
I'm
just
going
to
be
real
brief,
because
I
want
to
get
into
the
talk
with
matthew,
giving
him
opportunity,
but,
as
brian
mentioned,
I
am
the
cto
of
proven
and
we're
excited
about
getting
this
hyperledger
group
started
again
in
atlanta,
and
so
we
would
love
to
get
your
your
help
in
making
that
happen.
So
please
spread
the
word
after
this
event.
Let
everybody
know
how
good
it
was
and
that
you
know
get
them
to
sell
this
or
encourage
them
to
visit
us
next
month.
C
C
I
work
for
the
auburn
university,
rfid
lab,
and
I've
worked
there
for
about
two
and
a
half
years
at
this
point
and
what
we
focus
on
is
primarily
identification
technologies
and
how
we
can
use
those
from
a
technical
perspective,
but
also
what
the
business
value
is
for
using
those
in
the
retail
and
apparel
supply
chain.
But
then
we're
also
looking
at
other
spaces
too,
like
food
and
grocery,
as
well
as
aviation.
C
C
C
There's
been
a
lot
more
demand
and
and
kind
of
mandating
of
putting
an
rfid
tag
onto
a
clothing
item
at
source,
and
they
do
that
for
a
couple
of
reasons,
but
primarily
in
the
store
they
will
use
it
for
what's
called
cycle
counting.
So
if
I'm,
you
know
in
a
retail
store,
like
you
know,
I'll
give
walmart
as
an
example
and
I'm
in
the
apparel
section.
If
I
want
to
get
an
idea
of
what
I
actually
have
on
hand,
then
traditionally
I
would
go
through
and
scan
the
barcode
for
every
item.
C
That's
in
that
store,
and-
and
none
of
us
want
to
do-
that-
no
one
wants
to
do
that.
That
takes
a
long
time
and
they
they
only
do
that
a
couple
times
per
year.
If
that,
because
it
really
is
a
pretty
involved
process
and
so
rfid,
what
that
does
is
allows
them
to
not
only
assign
a
unique
identity
but
also
read
those
tags
in
a
much
easier
fashion.
C
So,
instead
of
establishing
line
of
sight
with
every
item,
then
they
can,
you
know,
put
out
a
radio
signal
with
either
a
handheld
device
or
a
fixed
infrastructure,
or
something
like
that
and
then
read
all
those
hundreds
of
tags
in
a
matter
of
seconds
rather
than
just
a
few
tags.
So
then
they
can
get
a
better
idea
of
specifically
what
they
have
on
hand
more
often
and
drive
up
their
inventory
accuracy
numbers.
C
So
that's
kind
of
how
rfid
began
in
the
apparel
space,
but
as
we
began
looking
farther
upstream,
we
realized.
Well,
you
know
we're
tagging
these
items
at
the
factory
and
they're
going
all
the
way
through
the
supply
chain
down
to
the
store
to
be
used.
But
why
can't
we
capture
this
data
at
every
point
along
the
way
in
the
supply
chain
and
then
leverage
that?
But
we
ran
into
a
problem
of
there's
not
really
a
great
way
to
share
this
data
or
exchange
this
data
in
in
sort
of
a
democratic
way.
C
When
we
begin
looking
at,
you
know
complex
trade
networks,
you
can't
just
say:
okay,
we're
going
to
use
this
one
platform
or
have
this
one
solution
provider.
So
we
needed
something:
that's
that's
sort
of
distributed
and
easier
for
individuals
to
tap
into.
So
all
that
goes
to
say
that
we
put
together
a
working
group
to
kind
of
work
through
some
of
these
problems
and
then
jumped
into
an
actual
proof
of
concept.
C
That
represents
the
traditional
flow
of
data
in
the
supply
chain
generally,
and
that's
really
point
to
point
so
a
manufacturer
would
say
to
a
supplier,
hey.
You
know.
Here's
the
advance
shipping
notice
for
what
I'm
supposed
to
be
sending
you
and
then
the
supplier
is
pretty
much
blind
until
the
products
actually
show
up
and
then
even
then,
it's
difficult
for
them
to
to
validate
and
double
check
everything
to
make
sure
it
matches
up.
So
they
really
just
trust
the
manufacturer
and
what
they
say.
C
They're
sending
and
the
same
goes
from
a
supplier
to
a
retailer
or
even
a
retailer
to
their
own
retail
store.
So
we
shifted
from
that's:
that's
called
g10
data.
That's
a
global
trade
identification
number
there's
a
lot
of
acronyms
on
the
screen,
so
you
know
bear
with
me
here,
but
all
that
is
just
like
a
barcode.
Again,
that's
a
quantity
level
basis,
so
the
manufacturer
would
say:
hey
I'm
sending
you
five
white
t-shirts
and
that's
the
only
you
know,
that's
as
granular
as
that
data
gets
so
like.
C
I
said
we
kind
of
shifted
towards
the
rfid
data
which
is
serialized.
So
then,
okay,
you
know
we
can
distinguish
each
item.
It
has
a
an
identity,
every
product-
I
guess,
but
even
if
we're
capturing
that
data
for
each
of
these
unique
items
at
every
point,
we're
still
not
sharing
it,
it's
being
siloed,
which
you
can
see
here
on
the
bottom
of
the
screen,
so
we're
not
leveraging
it
to
to
really
communicate
what's
going
back
and
forth.
C
So
they
upload
data
to
the
blockchain
network
and
the
manufacturer
can
say:
hey
here's,
the
individual
items
that
I'm
sending
you
the
supplier
and
supplier
can
see
that
before
they
even
receive
them,
and
it
is
so
much
easier
for
a
supplier
or
retailer
or
anyone
to
validate
and
say.
Okay,
let
me
make
sure
I
got
what
I
received
when
they
have
a
known
ledger
of
what
they're
already
expecting
and
because
then
they're
not
operating
blind.
So
that's
the
big
idea
and
there's
a
couple
of
different
business
values
or
reasons
that
you
know.
C
Individuals
in
the
supply
chain
might
want
to
do
this,
and
that
is
these
numbers
here.
So
this
is
from
the
retail
and
apparel
and
I
think
it
includes
grocery
as
well,
but
the
supply
chains
and
we're
looking
at
about
a
hundred
billion
dollars
of
counterfeiting
cost
each
year,
and
you
know
this
is
pretty
ambiguous.
A
lot
of
this
is
also
unknown.
C
Claims
is
estimated
to
be
around
35
billion
dollars
and
then
shrink
at
about
50
billion
dollars
yearly.
So
claims
is
when
a
supplier
would
send
a
retailer
or
any
manufacturer
supplier.
Any
two
partners
would
have
a
disagreement
on
what's
being
sent,
you
know,
so
a
retailer
would
say:
hey.
You
know
I
was
supposed
to
receive
10,
but
I
only
actually
received
nine
items.
C
I
think
the
idea
is
that
we
really
have
no
idea,
otherwise
it
would
be
classified
differently,
and
so
these
are
huge
problems
in
our
supply
chain
and
we
don't
have
great
visibility
into.
You
know
how
we
can
resolve
these
or
what's
actually
going
on,
and
that
would
definitely
ease
some
of
the
pains
and
that's
what
we
believe
and
what
we
feel
blockchain
can
help
us
work
towards.
C
So
again,
these
are
the
partners
that
helped
or
contributed
data
to
the
proof
of
concept.
We
split
them
up
into
three
different
data
streams
or
three
different
channels.
My
bad,
so
hyperledger
fabric
offers
the
channel
function
which
allows
us
to
kind
of
create
a
partitioned
off
space,
where
macy's,
for
example,
wouldn't
be
able
to
see
kohl's
data.
So
nike
was
vertical
going
from
encoding
data
at
the
manufacturing
level.
C
So
we
broke
it
down
into
three
different
steps,
the
first
being
to
identify
the
systems
and
the
stakeholders.
So
you
know
looking
at
the
supply
chains
of
each
of
the
partners.
Looking
at
who
controls
that
data
who
yeah
you
know
what
points
can
we
even
get
data?
Where
are
you
capturing
data
in
the
supply
chain
and
what
sort
of
system
systems
do
you
have
and
how
can
we
gain
access
to
that
and
once
we
identify
those
data
streams
of
you
know?
C
So
again,
this
is
a
focusing
on
epcis
here.
It
answers
the
questions.
What
when,
where
and
why?
So
what
item
is
going
from
point
to
point
at
what
time?
What's
the
location
of
that
and
then
why
what's
going
on,
is
this
item
being
shipped
or
is
it
being
received,
there's
a
whole
kind
of
vocabulary
that
gs1
has
defined,
and
I
know
that
standards
are
usually
boring
but
they're
pretty
necessary,
and
so
that's
definitely
something.
That's
that's
really
important.
C
When
we
begin
to
kind
of
move
towards
a
common
platform
like
this
and
then
finally,
we
integrated
it
into
the
blockchain.
So
this
is
kind
of
the
exciting
part.
The
new
part
I
mean
we
worked
with
the
ibm
blockchain
platform.
It's
relatively
easy
to
use.
We
didn't
have
to
code
a
lot
of
the
parameters
of
the
network,
but
we
did
have
to
put
together
client
applications
and
a
front-facing
web
application
to
actually
both
write
and
read
the
data
that
was
going
through.
C
Because,
right
now
they
don't
have
great
visibility
into
that
and
there's
a
lot
of
data
here.
I
can
send
out
this
deck
afterwards
to
everyone
that
was
on
the
call
or
not
a
lot
of
data,
but
a
lot
of
information,
because
I
think
it
might
be
helpful
if
you've
got
more
time
and
then.
Finally,
ultimately,
we
had
about
223
000,
rfid
tagged
items
that
were
accounted
for
from
source
to
store
and
that's
that's
kind
of
at
various
points.
C
Not
all
of
them
were
all
the
way
from
manufacturing
to
the
retail
store,
but
it
was
223.
000
items
that
we
saw
in
our
blockchain,
so
key
takeaways,
we
were
able
to
see
that
you
know
blockchain
actually
does
work.
We
can
use
it
to
exchange
data,
but
the
reality
is
that
the
transaction
speeds
are
pretty
low.
C
I
think
what
we
were
able
to
get
to
was
like
25
to
30
transactions
per
second,
which
you
know
I
know
now
with
fabric
there's
been
a
lot
of
testing
for
higher
transaction
speeds,
and
we
obviously
are
a
group
of
students
from
a
university,
but
we
did
work
with
the
ibm
team
and
some
other
individuals
on
this
and
compared
to
traditional
systems.
It
is
by
default
not
as
efficient.
C
So
I
think
it
does
need
to
be
proven
as
scalable
before
we
begin
actually
using
it
to
exchange
data,
because
that's
what
we
were
doing
was
taking
data
itself
and
exchanging
that
rather
than
using
it
as
like,
a
validation
of
some
sorts
and
only
storing
hashes,
or
something
like
that,
and
that's
what
I
know
a
lot.
A
lot
of
other
projects
are
doing,
and
so
that'll
probably
be
the
route
that
we
go
in
the
future.
But
that's
something
that
we're
still
kind
of
exploring,
but
then
beyond
that
epcis
is
key
or
really
any.
C
Standardization
is
key.
I
said
it
earlier,
but
I'll
say
it
again
that
a
common
platform
requires
a
common
language.
So,
regardless
of
of
what
sort
of
network
you
have
for
those
data
inputs,
you
want
to
make
sure
that
those
are
in
some
sort
of
standardized
format,
because
that
makes
things
a
whole
lot
easier
and
then,
finally,
data
quality
is
paramount
and
you
know,
as
they
say,
garbage
in
garbage
out
throughout
this
entire
proof
of
concept
that
we
ran.
We
didn't
focus
a
whole
lot
on
that
quality
of
the
data
that
was
actually
going
through.
C
C
C
Otherwise,
if
we're
sharing
something
that
can't
be
deleted
and
that
we
have
to
append
you
know,
we
don't
want
to
have
70
percent
of
our
only
70
percent
of
our
data
being
correct,
and
so
that's
what
kind
of
going
out
of
and
I've
got
the
launch.
The
chip
pilot
is
kind
of.
What's
next
going
into
the
chip
pilot,
we're
really
focusing
on
that
data
quality
piece,
because
that
that's
really
important
to
to
get
the
business
value
out
of
an
exchange
mechanism
like
blockchain,
and
you
can
see
here
on
the
right
side
of
the
screen.
C
If
you
say
hey,
you
know
you
have
to
give
all
your
data
over
or
you
have
to
control
or
be
controlled
by
this
one
organization
that
they
may
not
trust
and
that's
a
really
big
inhibitor
and
something
a
lot
of
people
have
brought
up
that
they're
concerned
about.
So
you
know
making
sure
that
we
really
do
have
a
neutral
environment
that
can
support
different
cloud
systems
or
different
cloud
deployments.
C
C
So
that's
that's
kind
of
where
we've
been
the
past
few
months
on
this
project
at
the
lab
and
that's
obviously
been
slowed
down
with
with
covet
and
everything,
so
we're
going
to
be
continuing
with
that
into
the
next
year
and
that
that's
really
adding
in
that
last
step.
Here
of
you,
know
identifying,
standardizing
and
integrating,
but
actually
analyzing
and
that's
the
end
goal.
Is
you
know
if
we're
using
blockchain
taking
things
like
smart
contracts
to
leverage
the
data
that's
on
that
chain
and
actually
analyze
it
to
derive
a
business
value?
C
For
what
does
this
mean?
How
does
this
help
us?
Because
that's
what's
going
to
get
a
lot
of
the
supply
chain,
stakeholders
on
board?
You
know,
that's
all
they're
looking
for
is
hey.
How
much
money
is
this
going
to
save
me
or
how
can
this
make
my
life
easier,
and
so
that's
the
part
that
we're
really
looking
into
and
focusing
on
now
and
here's
some
more
information
about
that
smart
contract
piece
and
how
that
would
actually
work.
C
This
is
pretty
complex,
but
essentially
you
know
taking
the
data
on
the
chain
and
verifying
it
with
you
know.
What's
supposed
to
be
sent
versus,
what's
actually
sent
and
then
creating
an
alert
for
if
those
don't
match
up,
but
again
I
can.
I
can
send
this
out
if
you
would
be
interested
to
kind
of
take
a
closer
look
at
it.
C
B
E
D
D
C
D
C
Yeah,
so
they
were
all
provided
by
ibm,
and
that
was
through
the
ibm
blockchain
platform,
and
then
it
was
supported
by
the
ibm
cloud.
So
that's
something
that
you
know
we
kind
of
got
a
little
bit
of
pushback
on
was
well.
Is
that
truly
blockchain?
If
it's
all,
you
know
kind
of
centralized
in
that
one
space,
and
so
that's
what
you
know
looking
at
in
the
future.
C
D
Yeah,
that's
kind
of
why
I
was
asking
the
question
you
know
because
sometimes
they
they
say
they're
giving
you
nodes,
but
they
put
you
in
one
particular
farm.
If
you
will
and
not
that
that's
necessarily
bad,
it's
just
that's
been
our
experience
that
would
might
make
provides
some
indication
of
you.
You
said
you
had
a
low
number
of
transactions
per
second,
so
you
know
it's
there's
a
lot
of
variables
there,
but
that's
what
I
was
asking
that
question
for
okay.
Thank
you.
D
B
C
Yeah,
so
we
that
is
something
that
we
did
build
from
kind
of
the
ground
up
independently,
and
I
wish
I
should
have
brought
some
of
our
technical
team
members
onto
here,
because
I
know
they'd
definitely
be
able
to
answer
some
of
these
in
a
lot
more
detail,
but
we
they
were
able
to
communicate.
So
we
would
upload
to
the
web
app
and
that
would
go
through
to
the
client
and
we
kind
of
tailor
each
client
to
feed
into
the
blockchain
itself
for
each
different
data
stream
that
we
were
getting.
C
So
that
would
be
like
each
individual
node
and
then
we'd
obviously
have
smart
contracts
to
upload
the
data
in
the
format
that
we
kind
of
predefined.
But
we
did.
We
did
build
the
the
web
app
and
the
client
independently,
and
I
don't,
I
believe
they
use
apis
to
communicate
with
each
other.
But
I'm
not
100
sure.
So,
if,
if
you
want,
I
can
get
with
them
and
get
a
little
more
detail.
E
Yeah
that'd
be
great
yeah
because,
like
my
from
my
experience
like
they
had
a
great
tool
there,
I
don't
know
if
you
ever
played
around
with
hyper
ledger
composer,
but
it
was
a
fantastic
tool.
I
mean
you
could
build
a
whole
blockchain
application.
I
mean
as
bare
bones
as
it
was.
I
mean
you
could
build
in
45
minutes
and
then
like
they
just
got
rid
of
it
and
it
kind
of
really
from
a
front-end
perspective
of
developing
a
web
app
like
there's
nothing
that
has
come
out
that
I
am
aware
of.
E
There's
nothing!
That's
come
out,
since
that
I
mean
I've
heard
of
mini
fabric,
which
is
like
I've
kind
of
heard.
They
kind
of
dabble
in
that.
But
it's
not
like
a
tool
that
is
dedicated
to
helping
you
develop
a
full
front,
end
web
app,
essentially
to
interact
with
your
blockchain
platform.
So
I
was
just
curious,
yeah.
C
Yeah
and
ours
was
ours
was
pretty
crude.
I
mean
it
was
nothing,
nothing
fancy,
but
it
was
essentially,
you
know,
click
here
to
upload
a
file
and
then
click
here
to
to
get
an
output
of
the
data.
That's
on
that,
but
the
their
ibm's
blockchain
platform
itself
is
in
a
way.
It
could
be
kind
of
the
front
end
because
it
allows
you
to
see
a
lot
of
the
stuff.
That's
actually
in
the
network,
but
yeah
we
haven't
looked
really
into
some
of
the
the
options
for
that
either.
E
So
your
interface
was
real
basic.
Like
you
said,
it
was
like,
like
an
upload,
a
pdf
for
an
example,
and
you
just
click
and
then
upload
it,
and
then
I
mean
there's
probably
a
little
more
to
that.
Obviously,
but
the
gist
of
it
was
like
kind
of
seeing
the
the
transactions
kind
of
what
the
history
of
the
distributed
ledger.
What
have
you
and
then
like
upload,
a
pdf
or
something
to
that
extent,
yeah.
C
Yeah
and
it
was
they,
the
partners
would
use
an
api
to
tie
into
that
in
some
cases
to
actually
kind
of
automate
that
process,
and
that's
that's
really.
What
pushed
us
to
to
have
that
web
app.
You
know
that
makes
that
process
a
lot
easier,
but
I
know
that
was
we.
We
ran
into
the
problem
of
like
querying
a
lot
of
different
items
at
once
and
ended
up
having
to.
C
C
D
E
B
C
F
F
F
But
let's
see
most
of
the
companies
they
are
using.
They
are
outsourcing
their
manufacturing
not
to
bring
up
any
specific
country
here,
but
it's
a
reality.
They
are
outsourcing,
so
they
are
outsourcing
partners.
Sometimes
it's
their
entity
in
that
country,
or
sometimes
it's
a
totally
different
country.
They
just
put
a
label,
and
they
just
done
so
how
how
to
make
sure
that
if
manufacturing
entities
are
outsourced,
what
the
data
they
are
providing
is
legitimate,
so
yeah
make
sure
this
blocks.
You.
C
Yeah
and
that's
that's
kind
of
a
difficult
question
that
we've
run
to
because
some
brands
may
be
using
hundreds
of
different
factories
to
actually
produce
their
items
and
it's
very
difficult
to
manage
the
data
that's
coming
out
of
those,
especially
when
it's
going
onto
a
chain,
because
you
know
you
can
say
well
once
that
data
is
on
the
chain.
Then
it's
secure
and
we
can
trust
it.
But
you
have
to
trust
the
quality
of
it
before
it
even
goes
in
in
the
first
place.
C
And
so
that's
that's
a
difficult
question
that
we're
working
through
right
now
and
then
we're
beginning
to
look
at.
Is
you
know
how
do
we
honestly?
You
need
to
have
some
sort
of
auditing
program
to
to
go
through
and
check
some
of
the
data
that
is
coming
out
of
these
locations
that
are
all
over
the
world
and
and
how
do
we
get
to
the
point
where
we
can
actually
trust
it?
C
And
you
know
that
kind
of
probably
varies
or
depends
based
on
what
sort
of
data
that
you've
got
coming
out
and
going
in
working
with
rfid
data,
we're
working
on
kind
of
a
general
process
or
a
a
way
that
you
would
go
about
actually
auditing
the
data
and
verifying
that
it
is.
You
know,
legitimate
and
is
accounting
for
everything,
but
you
know.
Needless
to
say,
that's.
It
is
really
important
to
think
about,
because
I
think
a
lot
of
people
harp
on
the
security
aspect
of
blockchain.
E
So
I
got
one
quick
question:
it's
kind
of
a
crazy
question,
but
I
figured
I'd:
ask
it
anyway,
so
why
did
you
pick
hyper
ledger
fabric
versus
something
like
hyperledger
grid,
because
grid
was
from
what
I
understand
was
designed
for
supply
chain
when
it
was
being
designed.
So
I
was
just
curious
why
fabric
versus,
like
the
other
platforms
or
frameworks.
C
E
C
D
There's
a
lot
of
you
know
when
you
look
at
the
the
gs1
standards
for
barcodes
there's
a
lot
of
there's
about
11.
I
think
primary
barcodes
that,
although
there's
plenty
there's
in
the
10
or
11,
that's
widely
used.
How
did
you
get
the
different
people
in
this
group
to
decide
on
a
common
barcode,
or
did
they
not
have
common
barcodes?
And
you
just
you
guys,
just
write
a
application
that
would
interpret
the
data.
You
know
basically,
a
filter
mechanism.
C
C
Half
and
half
of
some
of
them
chose
to
adopt
it
and
use
it
and
send
that
through,
but
the
other
half
we
just
ran
it
through
a
an
application
that
was
part
of
the
web
application
was.
It
would
actually
convert
that
data
into
the
proper
format
before
sending
it
through
to
the
client,
and
that
was
that
was
another
function
of
why
we
wanted
to
have
it,
go
through
a
web
app
in
the
first
place,
but
ideally
you
know
long
term,
they
would
produce
it
from
you
know.
The
output.
D
Yeah,
it
could
be
good
if
it
was
really
standardized,
but
I
figured
you
probably
wrote
some
kind
of
a
conversion
interpreter
or
something
like
that.
Now
I
mean
I
know
it's
the
university
that
did
that,
but
who
actually
paid
for
the
this
the
servers
and
stuff
ibm.
I
mean
they're,
not
they're,
not
cheap,
usually
after
they
get
you
out
of
the
sandbox,
I
mean.
Did
the
university
pay
for
that
or
did
they
have
a
contract
or,
and
then
how
much
do
you
know
how
much
it
may
have
cost.
C
C
I
would
have
to
reach
out
to
them
and
get
those
numbers,
that's
something
that
we
didn't
really
look
into,
but
you
know
I've.
I've
heard
from
people
that
some
of
the
prices
that
you
know
ibm
or
oracle
or
some
of
the
other
providers,
some
of
the
prices
for
these
these
services
are
are
kind
of
up
there,
and
you
know,
I
think,
that's
something
that
we
could
have
taken
into
account
when
looking
at.
How
does
this
compare
to
you
know
traditional
data,
storage
or
communication
methods,
but
yeah
I
don't.
C
E
I
think,
or
I
haven't
looked
very
recently
but
last
time
I
looked,
I
think
for
the
production
size
was
1500
a
month,
but
don't
hold
me
to
that
and
then
there
was
a
smaller
tier
that
I
think
was
500
a
month.
I
think
don't
hold
me
to
that,
but
that's
kind
of
the
ballpark
I'd
say
about
what
they're
charging
you
monthly
got.
C
It
yeah
and
that's
what
like
kind
of
moving
to
the
second
phase
of
once
we
kind
of
get
down
the
data
quality
part
and
begin
to
look
at
what
is
the
actual
business
value
here
like?
How
much
can
we
actually
reduce
these
costs
is
when
we
were
gonna
really
jump
into
okay?
Well,
you
know
how
worth
it
is
this
because
that's
the
big
question
that
we're
getting
from
all
the
end
users.
C
C
C
E
E
D
C
Yeah
so
that
was
was
students
on
our
team.
I
think
the
one
that
primarily
managed
that
actually
graduated
so
I'd
have
to
reach
back
out
to
him
specifically,
but
I
I
from
my
understanding
they
had
pretty
significant
database
management
experience
just
through
classes
and
other
projects
and
things
like
that,
but
also
a
lot
of
particularly
with
fabric.