►
From YouTube: The "iDeAL" POC; a Wing-to-wing Proof of Concept for an Inter-company Distributed Acc... Gary Crisci
Description
The "iDeAL" POC; a Wing-to-wing Proof of Concept for an Inter-company Distributed Accounting Ledger - Gary Crisci, General Electric
As part of the effort to modernize GE's internal billing system, a proof-of-concept for a blockchain based decentralized ledger was built. The end result enables GE to transition its mission critical process from a legacy mainframe to a cloud-based instance of Hyperledger Fabric. In this session, Gary Crisci, Principal Architect at GE, will present the business requirements, and system architecture, that demonstrates how distributed ledger technology is an ideal solution for this use case. The presentation will highlight how data integration between multiple ERPs and Hyperledger Fabric is achieved through REST API endpoints, and how smart contracts codify the business rules that govern the entire process. There will also be a review of a chain-adjacent data warehouse solution that provides financial transaction provenance via rich data visualization dashboards.
To learn more about Hyperledger, the open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments. Which serves as a neutral home for various distributed ledger frameworks including Hyperledger Fabric, Sawtooth, Indy, as well as tools like Hyperledger Caliper and libraries like Hyperledger Ursa click here: https://www.hyperledger.org/
Session Details & Slides (if available)- https://sched.co/j3bX
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
Okay,
good
afternoon,
good
morning,
good
evening,
depending
on
where
you're
based
my
name
is
gary
chrissy,
I'm
going
to
be
presenting
today
on
what
we
call
the
ideal
proof
of
concept.
This
was
a
wing
to
wing
proof
of
concept
for
an
inter-company
distributed
accounting
ledger
again.
My
name
is
gary
christie,
I'm
an
enterprise
architect
at
general,
electric
at
ge,
corporate
and
financial
systems.
A
So
let
me
go
ahead
and
get
going
here,
probably
familiar
with
ge.
I
won't
spend
a
lot
of
time
talking
about
the
company,
but
significantly
large
global
manufacturing
in
various
different
areas:
healthcare,
power
generation,
renewables,
aviation
and
so
a
lot
of.
If
you
look
at
kind
of
that
grouping
of
companies
what
you
start
to
see,
because
one
of
the
first
questions
I
get
is
why
would
this
be
applicable
to
blockchain
if
you're
talking
about
intercompany
or
why
would
this?
Why
would
a
distributed
system
be
necessary?
A
But
I
think
one
of
the
things
you'll
see
is
that
right
off
the
bat,
an
enterprise,
a
conglomerate
is
a
built-in
consortium,
so
we
kind
of
went
kind
of
based
off
that
premise
to
say:
well
what
can
we
do
internally?
First
and
then
potentially
down
the
road
open
it
up
to
external
suppliers
and
and
customers
as
well,
but
today
we're
just
going
to
talk
about
what
we
could
do
within
the
walls
of
general
electric.
A
So
here's
the
agenda
I'll
run
through
the
problem
statement
in
our
overview
for
a
solution
talk
a
little
bit
about
blockchain
and
hyperledger
fabric.
I
won't
spend
as
much
time
on
that
with
this
group,
since,
if
you've
been
a
you
know
at
the
global
forum
for
the
last
two
and
a
half
days,
then
you
probably
have
a
pretty
good
idea.
At
this
point,
you
probably
came
to
the
table
with
a
decent
amount
of
knowledge.
So
we'll
talk
about
the
solution
architecture.
A
And
again
this
is
wing
to
wing
right,
and
I
say
that
because
I'm
not
just
focusing
on
the
blockchain
itself
right.
So
blockchain
is
a
storage
mechanism
at
its
most
fundamental.
You
know
premise
for
what
it
does,
but
there's
a
lot
of
things
that
have
to
happen
around
that
to
build
an
actual
application
that
that
does
something
for
functional
end
users.
A
Okay,
so
the
challenge
what
we
were
looking
to
do
is
we
had
a
internal
billing
system
ibs,
which
is
a
25
year
old
mainframe
that
was
processing
about
four
million
intercompany
invoices
each
year
very
high
total
cost
of
ownership.
If
you
think
about
the
cost
to
maintain
a
mainframe,
the
scale
of
this
work
was
not
necessarily
mainframe
worthy,
but
that's
where
it
had
been
built
over
25
years
ago.
So
you
have
a
significant
cost
in
maintaining
that
hardware,
that
software
and
the
people
skills
to
keep
that
running.
A
So
what
we
wanted
to
look
at
was
what
would
be
possible
for
intercompany
transformation
and
and
just
to
kind
of
take
a
step
back
for
a
second
for
those
of
you
who
may
not
be
familiar
with
that
term.
It.
You
know
it's
pretty
much
what
it
sounds
like,
and
so,
if
I
am
one
company
general
electric
and
I
have
two
divisions,
let's
say
aviation
and
power
and
they
want
to
sell,
buy
and
sell
goods
between
them.
A
I
can't
record
that
revenue
and
present
it
to
wall
street
as
revenue
that
came
into
the
company,
because
it
was
really
revenue
that
was
paid
from
one
part
of
the
company
to
another.
So
before
that
we
do
our
external
reporting,
those
numbers
have
to
be
backed
out.
So
all
of
that
inter-company
accounting
for
activity
that
happens
between
the
businesses
has
to
be
backed
out
and
there's
a
tremendous
amount
of
cash
settlement.
A
That's
involved
in
inter-company
because
one
when
one
company
buys
from
the
other,
you
have
to
move
that
cash
from
one
balance
sheet
to
the
other
and
that's
expensive.
So
you
want
to
optimize
your
cash
movement,
so
you
want
to
do
netting
and
and
settled
for
settlement,
so
the
concept
of
netting
is
you
know
this
idea
of.
If
I
owe
you
a
hundred
dollars-
and
you
owe
me
fifty
dollars
well,
we
don't
have
to
do
two
cash
transfers.
A
We
can
just
do
one
cash
transfer
of
fifty
dollars
and
call
it
even
so
all
the
accounting
that
goes
into
that
and
being
able
to
track.
All
of
this
activity
is
what
we
do
in
an
inter-company
billing
system,
okay,
and
so
what
we're
looking
at
is.
How
do
we
improve
upon
that
instead
of
having
a
centralized
mainframe?
What
would
a
distributed?
A
Ledger
look
like,
and
so
these
were
some
of
the
things
that
we
wanted
to
have
in
the
system,
beyond
just
the
ability
to
have
it
on
a
blockchain
it
had
to
integrate
with
the
financial
systems.
We
wanted
a
mobile
first,
you
know
modern
ui,
especially,
you
know
the
users
coming
from
an
old
mainframe.
We
wanted
to
give
them
something
that
was
very
modern
and
functional,
microservices
architecture,
very
modular,
being
able
to
swap
pieces
in
it
out
as
needed
a
dispute
management
system
and
analytics.
A
So
we're
going
to
run
through
all
of
this.
So
this
is
really
quick.
I'm
going
to
give
you
an
idea
what
an
intercompany
transaction
flow
looks
like,
and
you
could
see
that
the
way
we
structured
this
proof
of
concept
is
around.
We
took
three
different
businesses,
our
corporate
aviation
and
health
care,
and
we
took
a
subset
of
transactions
that
we
knew
were
relatively
easy
to
work
with.
A
So
the
solution
design
is
really
tied
to
a
business
capabilities
model.
So,
if
you're
not
familiar
with
this
term,
this
is
something
that
is
an
enterprise
architecture
concept,
and
I
encourage
you,
you
know
when
you
go
in.
One
of
the
things
that
we
learned
very
early
on
was
that
the
technology
was
going
to
be
the
easy
part,
getting
people
to
understand
how
this
technology
would
work
and
help
them
and
really
understanding
about
the
process.
A
Change
that
needed
to
take
place
for
this
to
work
was
really
important,
and
so
we
had
to
really
understand
and
know
what
the
business
needed.
What
did
they
expect?
So
we
went
through
this
exercise
of
building
out
a
functional
capabilities
model
we
identified
in
different
ways
what
activity
the
current
system
did,
what
activity
the
new
system
would
need
to
do
and
was
it
net
adding?
Was
it
crucial?
A
So
this
is
something
that
I
like
to
take
a
minute
to
discuss
and
I
think
it's
a
good
tool
to
use
as
you're
going
through
this
exercise
with
the
users
that
you're
going
to
be
developing
the
application,
for,
let
me
advance
next
side.
There
we
go.
So
this
is
the
design
overview
and
you
can
see
again
what
I
was
saying
before:
blockchain
smart
contract
is
just
one
of
the
building
blocks
right,
blockchain
with
smart
contracts.
It's
in
that
middle
layer
there.
A
That's
where
we're
going
to
do
the
invoicing
and
purchase
order,
validation,
we're
going
to
do
the
netting
in
the
settlement
and
and
basically
the
intercompany
agreements
are
those
smart
contracts
and
that's
kind
of
that
rule
that
says
you
know
you're
allowed
to
bill
me
up
to
a
certain
amount
each
month
for
certain
activity
and
as
long
as
it's
within
that
we're
going
to
let
it
go
through
or
or
not,
but
a
lot
of
other
processes
needed
right.
We
have.
We
have
the
source
systems
and
the
erps
where
we're
tracking
this
activity.
A
So
this
is
the
solution
architecture.
Again,
we
did
leverage
a
lot
of
the
oracle
tool
set
here,
but
there's
different
ways
to
to
build
this
and
structure
it
out,
but
you
can
see
that
we
kind
of
had
a
process
flow
here
that
went
from
the
erps
through
these
different.
What
we
were
calling
you
know
microservices
or
modules
you
can
see
in
the
integration
layer
we
talk
about
enrichment,
invalidation
and
that
that
was
really
kind
of
our
take
on
on
setting
up
oracle's
and
and
not
oracle
the
company
little
o
oracles.
A
You
know
the
idea
that
I
could
call
out
to
other
systems
to
get
information
that
I
need
for
the
transaction.
So
drm
is
is
a
master
data
system.
Eve
is
a
validation
engine
and
what
those
things
do
is
a
po
might
come
in
with
a
cost
center
or
a
legal
entity,
but
that's
limited
information,
and
there
may
be
things
that
there
are
rules
that
I
have,
for
instance,
let's
say
I'm
doing
business
with
a
restricted
country
if
I'm
moving
funds
through
a
restricted
country,
there's
certain
paperwork
that
has
to
be
filed.
A
So
we
have
to
hold
that
transaction
up
until
that
paperwork
is
received.
Well,
the
only
way
to
know
if
it's
a
if
it's
a
you
know
a
country
that
that
has
restrictions
on
it
would
be
to
look
up
what
country
that
particular
legal
entity
is
operating
out
of.
So
you
have
to
get
that
information
from
other
systems
and
then
we
go
and
we
move
it
through
the
process
flows.
A
A
This
right
here
is
really
just
to
kind
of
show
you
some
of
the
process
flows,
I'm
not
going
to
get
too
deep
into
this,
but
basically
the
way
it
was
structured-
and
this
is
a
simple
one.
This
is
a
successful
path.
Data
comes
in
from
the
erp,
it
goes
through
the
integration
layer.
It
gets
validated
against
those
other
supplemental
systems.
A
We
use
this.
We
use
the
smart
contract
to
assign
a
status
right,
so
it
evaluates
the
transaction.
Can
it
be?
Can
it
be
approved
and
validated
right
off
the
bat
does
it
need,
maybe
documentation
restriction?
Is
there
a
dispute,
etc?
So
everything
is
recorded
on
the
blockchain,
with
a
different
status
code
and
as
the
transaction
moves
through
its
lifetime,
those
status
codes
change
and
it's
all
recorded
on
the
blockchain.
A
Okay.
This
is
a
more
complicated
process
flow
again.
For
the
sake
of
time,
I
won't
jump
into
this.
These
these
slides
are
up
in
sched.
So
if
you
want
to
download
the
pdf
you
can
you
can
review
them
and
certainly
reach
out
to
me
if
you
wanted
to
discuss
this
is
dispute
management
dispute
management
was
very
important
because
today,
a
lot
of
that
was
being
handled
through
informal
communication
channels,
right,
maybe
email,
maybe
internal
text
messaging
and
sending
documents
and
communication
back
and
forth.
A
A
We
didn't
put
the
documents
on
chain,
but
we
were
able
to
hash
those
values
and
put
that
on
chain
so
that
we
know
that
the
underlying
documents
that
were
stored
in
the
document
retention
system
were
the
were
the
documents
that
were
there
when
the
transaction
got
processed.
So
we
were
able
to
do
some
interesting
things
there.
A
So
why
blockchain?
This
is
a
place
where
I
can
speed
up
a
little
bit,
certainly
preaching
to
the
choir
here.
I
would
assume,
if
you're
here,
you're
you're,
hopefully
a
believer,
but
one
of
the
things
that's
interesting.
That
I'll
call
out
here
is
trust,
because
trust
is
one
that
again
I'm
talking
about
ge
within
ge,
and
you
say
well,
why
do
you
need
trust
right?
Ge
aviation
is
not
going
to
try
to
defraud
ge
power
for
an
internal
transaction
and
you're.
Absolutely
right,
that's
not
the
problem.
A
That's
not
the
kind
of
trust
we're
talking
about,
but
trust
goes
beyond
bad
actors.
Okay,
trust
in
in
a
process
like
this
is
I
have
to
trust
you
to
do
it
the
right
way
and
you
may,
through
no
malicious
intent,
do
something
incorrectly.
Maybe
you
thought
it
was
correct.
Maybe
you
didn't
realize
it
was
incorrect.
A
perfect
example.
I
started
to
say
earlier:
you
know.
A
Maybe
we
have
an
intercompany
agreement
that
says
you
can
bill
me,
ten
thousand
dollars
a
month
for
certain
services
and
then
halfway
through
the
year,
we
decide
that
the
project
is
is
getting
smaller.
We're
gonna
cut
that
down
to
five
thousand
right,
so
in
june
is
the
last
time
you
could
do.
Ten
thousand
now
july
comes,
and
you
can
only
charge
me
five
thousand,
inevitably,
in
july,
there's
a
very
good
chance
that
that
billing
is
going
to
come
through
at
10
000..
Maybe
somebody
forgot
to
update
it.
Maybe
somebody
didn't
get
the
memo.
A
It
was
being
cut
down
in
the
today's
world
that
would
go
through
and
it
would
be
something
that
would
have
to
get
reconciled
and
corrected
later
in
a
blockchain
with
a
smart
contract
world.
If
that
smart
contract
intercompany
agreement
was
changed,
then
now
we
stop
that
transaction
right
at
inception
and
say
wait.
This
can't
go
any
further
because
it
exceeds
the
agreed-upon
amount.
A
So
those
are
the
kind
of
things
when
we
talk
about
trust
that
are
really
important
even
within
a
an
organization
that
is,
that
is
working
with
themselves
and
transparency
helps
obviously
be
able
to
give
everyone
the
understanding
of
what's
going
on
there,
no
intermediaries
right
today.
Corporate
is
the
intermediary.
A
If
healthcare
and
aviation
are
doing
business
with
each
other
or
power,
it
all
goes
through
corporate.
You
could
question:
why
does
corporate
need
to
be
in
the
middle
of
that
we're
not
really
governing
anything
that
they're
doing
if
anything,
we're
just
adding
extra
layers
of
complexity?
So
why
not?
Let
them
work
with
each
other
and
have
treasury
just
be
a
participating
node
on
that
network
and
when
they
see
it's
time
to
settle,
they
do
the
cash
movement.
A
So
there's
a
lot
of
really
really
strong
benefits
in
this
that
we
felt
that
the
blockchain
value
proposition
was
correct
for
what
we
were
trying
to
do
again.
You
know
I
won't
dig
into
this
at
all,
but
federated
enterprise
focus
around
hyperledger
fabric
right,
we're
not
interested
in
trying
to
do
this
on
an
open
permissionless.
You
know
kind
of
a
bitcoin
network
or
an
ethereum
network.
A
Potentially
you
could
do
it
in
a
closed
ethereum
network,
but
we
really
thought
that
hyperledger
fabric
was
the
correct
tool
for
for
what
we
were
trying
to
do
important
to
have
a
reality
check
on.
You
know
not
get
caught
up
in
your
own
hype
right.
If,
if
the
only
tool
you
have
is
a
hammer,
then
every
problem
starts
to
look
like
a
nail
right.
So
so
blockchain
is
not
the
solution
to
everything.
So
we
want
to
make
sure
that
we're
checking
ourselves
and
saying
you
know
what.
A
A
So
this
is
kind
of
the
proposal.
The
current
state
in
the
future
state
of
how
we
move
data
across
the
system
and
again
this
is
that
parallel
shared
ledger
that
you
have
that
operates
alongside
each
erp,
so
the
data
flows
or
it
goes
from
the
erp
onto
the
shared
ledger.
That
then
goes
into
the
counterparty's
erp,
and
this
is
all
animated
through
the
rest,
apis
and
integration
tools,
and
then
you
get
the
responding
that
you
know
part
of
that
transaction.
A
You
know
everybody
needs
to
know.
If
you
may
say
a
charge
is
coming,
but
you
can't
charge
me
until
you
get
receipt
of
the
product.
Well,
when
that
hits
the
erp
that
I've
received,
that
that
should
kick
off
a
integration
that
runs
a
smart
contract
that
says:
okay,
they've
received
it
now,
let's
build
them,
etc,
and
it
goes
through
that
whole
life
cycle,
so
blockchain
really
gives
us
the
ability
to
move
that
process
along
very
well
so
hyperledger
fabric.
A
A
We
are
not
doing
crypto
coins
in
this.
It's
something
that
we
discussed
as
part
of
our
brainstorming
session.
Maybe
in
the
future,
we
would
look
at
that.
You
could
see
a
use
case
for
tokenizing
these
assets
and
using
that
to
to
minimize
cash
settlement
in
the
form
of
an
internal
cryptocurrency,
but
that
was
way
beyond
the
scope
of
what
we
were
doing
here
so
for
this
no
crypto
just
leveraging
the
two,
the
abilities
and
the
features
of
hyperledger
fabric,
smart
contracts,
that's
how
we
get
the
algorithmic
trust
and
the
rules
that
I've
been
discussing.
A
A
Main
task
was
to
change
the
status
on
the
transaction,
so
there
was
a
po
submission
and
validation
invoices
matching
the
agreement
itself,
dispute
handling
the
netting
and
the
settlement.
All
that
logic
was
written
into
these
different
functions,
and
then
that
was
used
to
update
the
status
and
we
had
a
master
table
of
what
the
status
codes
meant
and,
depending
on
what
status
the
transaction
was
in
that
moved
it
through
its
life
cycle.
Until
ultimately,
it
got
resolved
or
potentially
rejected.
Nothing
ever
gets
deleted
right.
We
we
have
it
there.
A
A
Okay,
so
this
kind
of
talks
a
little
bit
about
what
we
did
with
oracle,
what
oracle
brought
to
the
table
for
us
and
why
we
decided
to
use
a
pass
service.
You
know
I
I
could
go
out
and
download
hyper
ledger
fabric
and
and
start
building
using
open
source
software
and
start
building
a
network
it
you
know
for
those
of
you,
who've
done
it.
A
A
So
this
is
what
the
architecture
looks
like.
You
could
see
kind
of
everything
from
going
from
right
to
left.
You
have
your
data
sources,
whether
it's
an
on-premise
erp
or
a
cloud
erp.
You
have
your
integration
components
which
leverage
the
rest
components
that
talk
to
the
blockchain
and
then
on
the
other
side.
What
oracle
brings
to
the
table-
and
you
can
do
this
in
your
own
environment,
but
it's
nice-
that
they
do
it
out
of
the
box.
A
Is
this
database
as
a
service
where
you
can
stream
your
blockchain
data
in
near
real
time
into
a
parallel
database
for
analytics
and
reporting,
and
that
was
really
powerful
for
us,
because
our
users
need
to
interact
with
this
data
and
we
didn't
want
to
be
in
a
situation
where
we
had
to
do
these
really
intensive
queries
against
the
blockchain?
That's
inefficient.
Blockchain
is
a
transactional
based
system,
the
same
way
in
my
sub
ledgers
and
my
erps.
I
also
have
limited
reporting
and
I
bring
data
into
a
data
warehouse
for
my
analytics.
A
This
gives
us
the
ability
to
run
that
off
chain
in
parallel
and
they
even
have
a
concept
in
their
database
of
blockchain
tables,
where
you
can
kind
of
maintain
the
integrity
so
that
you
ensure
that
what's
on
chain
and
what's
in
the
reporting
database,
are
that
you're
not
getting
anything
to
break
there
in
that
process,
and
then
we
developed,
of
course,
a
front-end
app
to
give
users
the
ability
that's
where
they
did.
They
could
check
on
what
the
status
of
their
transactions
were.
A
If
something
wasn't
reported
back
to
their
erp,
maybe
they
needed
to
file
a
dispute
or
they
needed
to
submit
supporting
documentation.
All
of
that
would
be
handled
through
the
front-end
gui.
It
was
relatively
low
code,
pretty
simple,
but
we
we,
you
know
we
got
that
up
and
running
as
well,
and
the
users
were
very
pleased
with
that.
A
I,
like
this
slide
this
kind
of
aligns
the
the
functional
kind
of
that
business
capability
and
and
what
we
built
as
a
solution
to
the
technology
itself,
and
this
is
one
of
those
cases
where
you
know
again.
Some
of
these
components
could
be
augmented
with
other
providers
and
things
could
be
swapped
out,
maybe
instead
of
oracle
analytics
cloud,
one
of
the
providers
prefers
tableau,
so
they
use
tableau
to
do
the
analytics,
maybe
instead
of
oracle
integration
cloud,
somebody
else
is
using
dell
boomi
or
they
want
to
just
write
it
themselves.
A
They
have
a
proprietary
integration
tool
that
they
use.
So
you
can,
you
can
kind
of
swap
things
out
and
that's
really
important
for
decentralization,
because
for
me
to
go
out
there
and
tell
the
businesses
or
then,
if
I
ever
extended
outside
the
business,
hey
come
use
my
blockchain
app,
it's
decentralized,
it's
distributed,
but
by
the
way
you
have
to
use
my
vendor
and
you
have
to
use
my
tools,
and
this
is
the
way
you
have
to
do
it-
it
kind
of
defeats
the
purpose.
It's
not
really.
A
That's,
not
that's,
not
a
good
way
to
do
consortium
building.
You
really
want
to
give
people
the
opportunity
to
build
on
this
in
the
way
that
they
need
to
themselves.
So
I
know
we
got
to
keep
moving.
These
are
really
just
screenshots,
we're
almost
at
the
end
here.
So
this
is
just
screenshots
of
the
different
tools,
the
identity
cloud
management.
This
is
where
you
create
the
users
and
you
set
up
your
remote
identity
providers.
A
This
is
again
just
how
you
would
do
authorization
and
authentication
getting
users
into
the
system,
data
integration.
These
are
the
workflows
that
would
take
the
data
out
of
the
erp.
They
would
basically
monitor
the
erp
for
messaging.
In
the
queue
and
then
they
would
run
a
workflow
that
would
bring
it
onto
the
blockchain,
execute
the
smart
contract,
etc.
A
A
This
is
a
this
is
again
through
the
console
view.
I
can
actually
look
at
the
ledger
and
I
can
see
the
actual
activity.
That's
on
the
ledger
itself.
So
as
a
transaction
gets
processed
on
a
smart
contract,
I
could
see
it
here
or
again.
I
could
go
to
that
external
database
and
see
it
there
or
through
any
kind
of
application
ui
that
I've
developed.
A
This
is
all
it
takes
to
set
up
this
rich
history
database.
You
just
come
in.
You
click
a
button,
and
you
say
you
know
here's
the
connection
string
to
my
database,
my
username
and
password,
and
it
automatically
starts
streaming
the
data
into
the
database.
It
creates
the
schema
for
you
and
then
it
loads.
A
The
data
there
in
a
json
format,
which
we
then
created,
views
to
parse
the
json
and
stage
the
data
in
in
a
more
kind
of
denormalized
manner,
and
then
we
built
executive
dashboards,
and
so
we
were
able
to
show
things
like
total
invoice
amount
for
a
particular
period.
The
total
number
of
invoices,
geographically,
where
the
activity
was
happening.
Interesting
side.
Note
about
the
text,
the
executive
summary
there.
That
text
was
not
written
by
a
a
person,
a
human
we
that
is
actually
in
the
oracle
analytics
tool.
A
So
earlier
I
talked
about
changing
the
tr,
the
status
codes
and
what
this
really
comes
down
to
is
what
I
refer
to
as
transactional
provenance,
and
so
we
hear
that
term
used
in
supply
chain.
But
for
an
accountant
us,
you
know
especially
some
kind
of
like
a
forensic
accountant
or
any
kind
of
analyst
understanding.
The
life
cycle
of
a
transaction
is
extremely
useful,
so
being
able
to
kind
of
show
that
at
any
point
in
time-
and
you
can
see
here-
the
different
you
know
timeline
views
of
all
these
different
activities.
A
This
is
the
overall
summary
integration,
blockchain
data
warehouse
analytics
everything.
I've
talked
about
enables
flexibility
and
business
agility,
and
that's
it
I'm
going
to
jump
over
to
q
a
I
apologize
for
rushing,
but
I
know
this
was
a
short
amount
of
time
to
discuss
a
lot
of
material.
I'm
certainly
happy
to
discuss
with
anyone.
If
you
want
to
reach
out
to
me,
one
of
the
first
questions
that
I'll
answer:
real,
quick
and
then
I'll
jump
into
the
qa
and
try
and
close
that
out
is
one
of
the
first
questions
I
get.
A
A
What
we
realized
from
this
was
that
the
technology
was
easy.
The
hard
part
was
changing
the
functional
process.
This
was
going
to
require
a
significant
amount
of
change
for
our
business
users
and
in
a
world
where
we
were
heading
into
covid
and
and
some
other
things
that
were
going
on,
we
decided
to
table
that
temporarily.
A
We
are
still
planning
on
doing
this.
I
mean
we're
using
the
foundation
of
what
we
learned
here
for
some
other
supply
chain,
proof
of
concepts
that
we're
working
on
actually,
pilots
that
we're
gonna
try
to
launch
to
go
into
production,
and
I
I
feel
strongly
that
we
will
get
there.
But
it's
definitely
the
lesson
learned
is
you
need
to
bring
the
functional
team
along
with
you
and
they
need
to
know
what
they're
getting
into
so?
A
A
A
So
those
are
all
things
that
we
would
consider
if
we
did
go
to
production.
But
yes,
you
definitely
are
not
locked
into
using
just
oracle
if
you
use
their
pass
so
yeah.
So
this.
I
think
this
is
a
related
question.
It
says
it
defeats
the
purpose
of
what
you
said,
avoid
vendor
lock
and
give
options
to
all
companies
in
a
consortium
but
yeah.
So
you
you
do
have
options
you're,
not
locked
into
just
using
oracle,
and
then
we
put
here,
you
mentioned
that
trust
in
data
is
also
about
reducing
human
ever
error.
A
A
We
did
not
want
to
bring
people
out
of
the
erp
and
into
the
intercompany
system
to
do
things
that
belonged
in
the
erp.
So
to
your
question
about
getting
the
errors
right,
there
are
other
programs
that
we
have.
I
don't
have
time
to
get
into
them
now,
but
there
are
other
things
that
we
do
at
the
erp
level
to
try
and
improve
data
entry
errors,
but
that
is
definitely
something
that
we
felt
needed
to
stay
at
the
point
of
entry,
which
was
in
the
erp
system.
A
So
I
think
that's
it
for
q,
a
I'm
two
minutes
over,
so
I'm
gonna
go
ahead
and
wrap.
Thank
you
so
much
for
spending
time,
and
you
know
here
hearing
about
what
we
did.
I
was
very
proud
of
it.
I
think
I
think
it
was
a
really
good
step
towards
towards
moving
us
into
using
getting
some
more
skin
in
the
game,
with
hyper
ledger
and
with
distributed
ledger
technology
and
again,
if
you
want
to
reach
out,
I
also
have
a
link
there
to
my
blog
post,
which
dives
in
deep
to
house.