►
Description
Saudi Aramco, Procure to Pay Eco-System - Ali Safri, Avanza Innovations & Abdullah M Askari, Saudi Aramco
As the largest Oil & Gas and the most profitable company in the world, Saudi Aramco has complex procurement & payment processes. Contracting, delivery & payment processes with hundreds of suppliers across thousands of services & orders is tedious and entangled with heaps of documentary proofs, verification reports, third party evaluations & a barrage of internal checks & controls. Despite investing in some of the best ERP technologies, Saudi Aramco & it’s suppliers face a multitude of challenges, delays & even disputes in procurement & payment cycles. Avanza helped Aramco address these age-old challenges, discrepancies & in-efficiencies by developing a HLF Based Procure to Pay platform. Deployed on IBM’s IBP, the Platform helps streamline & automate entire delivery related documentation & verifications in real time, thereby bringing huge efficiencies to the overall invoice verification & payment processes. Tightly coupled with complex contract terms, platform is a self-regulating network that enables Aramco’s suppliers & internal departments to agree on all aspects of services, goods delivered & associated payments. Platform was launched in Aug 21 & is rolled out to 13 suppliers.
Sessions Details & Slides (if available): https://sched.co/14H4Z
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
Discord: https://discord.gg/rVCn4j7UFd
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
License
Creative Commons Attribution license (reuse allowed)
A
Hello,
everyone
thank
you
for
attending
the
session.
Today
we
will
specify
the
use
case
that
is
being
done
for
Saudi
aramco,
so
that
the
supplier
ecosystem
that
it
has
for
very,
very
complex
contracts,
how
that
could
be
utilized.
We
can
utilize
a
hyperledger
fabric
to
automate
all
that
particular
process.
What
were
the
problems
that
are
associated
with
it
and
how
we
delivered
this
particular
solution
to
them?
So
first
we'd
like
to
introduce
ourselves
Abdullah,
he
is
from
aramco,
so
he
is
my
co-speaker,
so
he'll
specify
things
about
ramco.
Yes,.
B
Thank
you
for
attending
good
afternoon.
My
name
is
Abdul
alaskar
I
work
for
Saudi
aramco,
for
with
experience
of
15
years
I
started,
supporting
the
hydrocarbon
hydrocarbon
systems
and
then
shifted
to
the
blockchain
solution
at
the
end
of
2019.
Saudi
aramco
is
the
one
of
the
largest
energy
integrated
energy
and
chemicals
group
of
companies.
Okay,
with
the
goal
of
assist
providing
a
sustainable
and
reliable
energy
to
the
world.
Let's
say
back
to
you:
Mr
Ali,.
A
And
like
if
you
can
Google
across,
if
people
don't
know
about
ramco,
if
you
see
around
1.42
trillion
numbers,
so
that
is
what
the
ramco
is.
It's
a
huge
huge
organization.
So
now
myself,
I
am
Alisa.
Free
I
am
the
chief
technology
officer
at
avanta
Innovations,
and
we
had
been
Partners
to
deliver
this
particular
purchase
to
pay
an
invoice
verification
use
case.
Avanza
is
a
certified
hypervisor
solution,
provider
and
one
this
is
one
of
the
projects
we
have
delivered
many
other
consortia
in
the
Middle
East
region.
B
I
will
start
by
comparing
the
goods
or
material
procurement
with
the
service
procurement.
Honestly,
you
know
we
can.
We
can
say
that
there
is
no
real
complexity
on
the
goods
or
material
procurement,
because
verification
of
such
thing
is
based
on
quantities
or
quality
of
these
delivered
Goods,
no
defects,
everything
is
okay,
then
invoice
can
be
issued
and
paid.
Normally,
the
problem
and
the
complicity
complexity
comes
when
we
procure
Services,
especially
with
long-term
contracts
that
can
also
span
a
period
of
10
years
or
more,
with
with
big
service
providers
dealing
with
Saudi
aramco.
B
The
problems
come,
the
problem
comes
when
we
try
to
cross-check
the
delivered
services
with
the
terms
and
conditions
in
the
contract,
and
we
need
to
go
back
not
only
to
the
contract
also
to
the
purchase
order
level.
So
when
we
receive
the
invoice
and
the
invoice
package
from
our
vendor,
we
need
to
verify
that
all
these
Services
delivered
or
the
claims
in
the
invoice
are
really
delivered
and,
according
to
the
terms
and
conditions
of
the
contract,
Here
Comes
The
Challenge,
and
we
will
elaborate
more
on
the
complexity
and
challenges
back
to
you.
Mr
Ali.
A
So
some
of
the
contracts
are
Manpower
based
contracts
and
the
Manpower
based
contract.
What
will
happen
so
still?
The
work
is
not
started.
You
are
onboarding
a
contractor.
You
will
say
these
are
the
technical
skills
that
I
need
across,
and
this
for
this
particular
skill.
I
am
willing
to
pay
you
this
amount
of
rate
of
straight
time
and
this
amount
of
rate
of
overtime,
and
these
things
gets
complex.
Sometimes
they
say,
okay
for
this
average
salary
between
this
particular
bracket
would
be
allowed
along
with
it.
A
If
you
have
spouses
or
children's,
these
would
be
additional
benefits
that
you
will
get
across.
Now
people
will
travel
also
so
based
on
travel,
there
would
be
per
diems.
There
are
constructions
because
there
are
big
constructions
that
happen
in
oil
and
gas
as
well.
So
there
are
certain
office
spaces
that
are
created
across
so
for
that
there
are
rules,
there
are
technical
drawings
that
are
building
delivered
for
them.
There
are
certain
billing
rules,
so
a
lot
of
rates
are
there
and
like
a
hundred
pager
contract
is
created
across
with
a
lot
of
terms
and
conditions.
A
Now
this
is
on
paper
now.
Secondly,
what
happens
is
when
they
have
a
requirement.
They
issue
some
kind
of
a
service
request,
and
again
this
is
running
across
one
or
two
years,
so
that
service
request
is
there
now
how
the
supplier
will
prove
that
this
particular
Manpower
or
services
that
I
utilized
across
there's
much
I
need
to
charge.
So
what
happens
they?
A
These
guys
go
normally
to
those
particular
construction
sites
or
the
other
sites
of
oil
and
gas
related
sites,
and
there
is
some
field
engineer
or
field
staff
from
aramco
that
creates
a
kind
of
a
timesheet
and
now
see
what
is
happening
over
here.
That
contractor
is
using
their
own
system
to
put
the
timesheet
data.
They
are
taking
the
printouts.
They
are
getting
that
verified
from
this
particular
field
staff
or
field
manager.
That
is
there
on
site
and
keeping
the
copy.
Now
this
works
for
the
whole
month.
A
At
the
end
of
the
month,
invoice
has
submitted
across
along
with
all
the
paper
trail
right.
So
there
is
a
obvious
opportunity.
There
is
data
within
a
ramco.
There
is
data
between
for
this
particular
supplier,
but
it's
not
a
shared
leather.
It's
not
a
distributed
ledger.
So
first
application
of
the
DLT
comes
over
here.
Now
second
thing
is:
somebody
has
to
verify:
are
the
contractual
terms
and
conditions
which
are
a
number
of
contractual
terms
and
conditions
and
I'll
come
on
to
the
next
slide
for
this
as
well?
How
do
we
govern
so?
A
The
current
the
previous
structure
was
that
somebody
was
manually
looking
across
multiple
tiers,
verifying
that
whatever
invoice
amount
that
is
finally
calculated
across
and
whatever
are
the
supporting
documents
they
match
or
not
match
now
change
it
put
everything
onto
the
blockchain
and
make
the
blockchain
enforce
those
smart
contract
conditions,
so
the
resultant
activity
was
that
whatever
was
taking
two
months
to
reconcile.
It
is
like
very,
very
quick
right,
so
these
are
the
things
which
are
there
so
now
I
will
tell
about
the
different
kind
of
contracts.
A
One
is
a
Manpower
based
where
you
talk
about
the
skill
sets
how
what
are
the
rates
for
those
particular
skill
sets?
Other
is
Services.
Let's
say
you
need
tiling
to
be
done.
You
need
other
kind
of
activities
to
do
to
be
done,
so
there
are
rates
involved
and
that
would
be
under
certain
circumstances.
Those
trades
would
be
applicable
across.
So
that's
a
service
based
rates.
A
There
would
be
many
variety
of
equipment
and
vehicles
that
would
be
required
because
in
order
to
construct
or
in
order
to
do
the
complex
things
you
have
those
complex
equipment
as
well,
so
those
equipments
also
have
as
rates
under
very
specific
terms
and
conditions.
Those
rates
could
be
different
as
well.
So
that's
another
thing
and
there
are
a
variety
of
contracts
in
which
all
of
the
above
are
applicable
across.
A
So
taking
those
contractual
things
on
one
side,
then
you
need
to
verify
those
terms
and
conditions,
and
then
another
area
is
there
that
if
the
contract
is
there,
it
would
be
canceled,
it
would
be
revised,
it
would
be
extended.
So
these
add
to
more
complexities
on
those
particular
areas
so
with
distributed
Ledger
that
shared
view
to
all
the
parties
at
all
times
comes
using
the
hyper,
larger
Fabric
and
with
the
smart
contracts,
all
the
contractual
terms
and
conditions
becomes
enforceable.
A
A
Now
authorization
is
important
as
well
that
before
this
person
is
deployed
across
some
certain
person
authorizer
as
well,
so
there
is
a
structure
called
prior
authorization
forms
that
were
previously
used
and
sent
across
the
emails.
So
this
was
one
another
area.
There
are
social
benefits
that
are
given
across
because
of
the
bonuses
and
other
perks.
So
that's
another
area,
so
they
agree
with
that
particular
contractor
other
personal
cost
and
also
like
the
person
is
for
the
first
year
or
for
the
second
year,
that's
complexity.
There
are
different
kind
of
a
rates
for
that.
A
There
are
many
indirect
costs
for
that
particular
company,
for
example,
for
providing
the
insurance
or
paying
the
management
salary
all
those
things
with
another
terms
and
conditions,
and
depending
on
how
many
hours
you
work,
there
are
different
rates
right.
So
how
you
come
up
with
the
rates
there
are
formulas
and
formulas,
there
are
a
lot
of
formulas.
A
A
There
are
certain
Consultants
sometimes
comes,
they
have
certain
different
rates
based
on
which
things
would
be
done
across,
and
there
is
a
fee
structure
which
is
a
kind
of
a
very
transparent
margin
that
the
contractor
will
make
on
all
the
this
particular
contract.
So
all
of
these
things
are
pre-agreed
across
then
there
would
be
certain
conditions
as
well
that
if
there
is
a
subcontractor,
they
cannot
charge
more
than
30
percent
more
than
the
overall
amount,
and
there
are
different
heads
in
which
the
costing
is
happening
across.
A
A
So
if
we
see
this
particular
life
cycle
processing,
so
from
the
Contracting
stage,
a
smart
contract
is
set
up,
then
all
the
service
deliveries
that
happens
all
that
data
stamped
onto
the
blockchain
and
finally,
what
is
going
to
happen
system
will
generate
all
the
documents,
all
the
invoices
and
come
up
with
the
final
amount
now
and
for
this
verification
cycle
will
be
very
very
less
previously.
Everybody
has
to
reconcile
things.
So
what
another
thing
that
needs
to
be
considered,
that
the
scope
that
was
taken
across
was
not
how
you
reach
the
Contracting.
A
Those
Contracting
team
will
decide
what
is
the
Contracting?
What
is
there
is
that
they
are
providing
support,
that
they
can
translate
those
terms
and
conditions
into
a
smart
contract.
So
that's
one
thing
and
secondly,
once
the
invoice
is
verified,
the
payment
is
going
to
happen
where
the
traditional
means
that
payment
is
not
part
of
that
particular
blockchain
initiative.
So
it
is
when
the
contract
is
signed,
all
the
service
request
or
the
service
delivery.
The
invoice
generation
invoice
verification
that
happens
between
ramco
and
its
Partners
onto
the
blockchain.
A
B
Now
we
will
dig
into
the,
as
is
the
process.
As
you
can
see.
The
manual
process
includes
sharing
Excel
files,
sharing
scan
documents,
emails
between
different
Saudi,
aramco
employees,
from
different
departments,
these
timesheets
or
pre-approval
forms
service
requests
and
the
signatures
or
the
sign
of
of
the
delivery
service
are
all
manual
all
communicated
in
a
synchronous
and
offline
manner.
B
A
After
the
solution,
all
all
the
things
that
we
talked
about,
if
we
see
the
life
cycle,
the
first
is
a
Contracting
stage.
The
second
is
a
service
request
is
created
for
procuring
those
particular
Services
based
on
pointing
on
to
that
particular
contract,
then,
which
resources
would
be
conducted?
What
would
be
the
travel
budget?
All
these
things
would
require
certain
pre-approvals,
so
those
particular
data.
Yes,
please.
A
A
So
initially
we
started
to
Port
those
particular
contracts
and
put
it
into
the
smart
contract,
because
every
different
requirement
was
having
a
different
kind
of
a
smart
contract.
So
as
part
of
the
process,
there
was
some
standardization
that
was
done
as
well.
Right
after
the
activity
we
created
a
kind
of
a
contract
Builder
as
well,
so
to
the
contract
Builder.
There
would
be
a
wizard
interface
whereby
you
specify
that
these
would
be
the
type
of
conditions,
so
it
would
automatically
deploy
that
particular
smart
contract.
A
A
Filing
different
kind
of
so
how?
How
did
you
do
it
at
what
level
so
first
like
this
would
be
one
of
the
challenges
that
happened
across
that
you
had
to
look
at
those
pile
of
contracts,
and
then
you
have
to
standardize
something
from
a
perspective
that
on
ground
those
contract,
those
10
don't
change,
but
technically
that
needs
to
be
delivered.
So
there
is
a
variety
of
contracts
that
we
had
to
read
across
and
then
we
have
to
generalize
certain
things
and
certain
things
remain
special,
so
certain
smart
contractor
very
specifically
written.
A
B
These
are
vendors,
okay,
we
don't.
We
don't
deal
with
individuals,
because
individuals
are
part
of
the
contract,
for
example
Manpower.
If
you
remember,
when
Mr
Alex
explained
the
different
types
of
contracts,
some
of
them
might
be
solely
only
Manpower
providing
manpower
to
Saudi
aramco.
Some
of
them
is
a
mix
of
all
or
or
a
combination
of
all
Manpower,
plus
other
things
like
equipments
or
Services
being
delivered
like
drawings
or
other
Engineering
Services.
B
So
we
deal
with
the
contractor
with
a
company
big
and,
as
I
told
you,
maybe
very
complex
and
long-term
contracts,
with
billions
of
dollars
an
amount.
So
we
have
this
contract
in
a
vendor
level
and
later
we
we
have.
Every
vendor
has
a
node.
Okay,
everyone
there
has
a
node
and
we
keep.
We
keep
sharing
our
the
shared
Ledger
is
among
all
the
the
participants.
A
We
will
come
to
the
architecture
as
well.
Let's
go
through
the
story,
so
first
was
a
Contracting
phase.
It
convert
it
into
a
kind
of
a
smart
contract.
Second
thing
is
the
service
request.
It
would
be
recurring
Whenever
there
would
be
a
requirement.
A
service
request
would
be
raised
across.
Then
there
is
a
service
execution
whereby
approvals
are
taken,
timesheets
are
periodically
given
and
now
what
is
the
architecture?
A
One
of
the
things
that
we
have
seen
across
in
a
blockchain?
If
you
tell
people
that
okay,
there
was
an
old
system,
now
use
a
new
system,
so
they
would
be
kind
of
confused
that
why
they
are
asking
to
hop
across
the
system.
Saudi
aramco
the
people
are
using
the
same
sap
system,
so
there
are
uis
created
rather
than
going
into
this
app
it
Taps
into
the
blockchain
data.
Similarly,
the
contractor
has
a
node
so
contractor
whatever
they
upload.
A
A
A
That
visibility
is
there
with
the
contractor
as
well,
and
they
know
every
week
that
whenever
they
submit
their
timesheet,
it
is
getting
approved,
or
there
is
a
dispute
compared
to
the
previous
case,
where,
after
the
month
they
will
submit-
and
they
will
take
two
to
three
weeks
and
then
raise
a
dispute
there's
no.
This
was
not
correct,
so
overall
agreements
and
disputes
Cycles
are
reduced
across
and
finally,
once
the
service
is
completed
because
over
here
there
are
different
mechanisms
as
well.
Some
contracts
says:
when
you
deliver
the
complete
service,
then
you
will
be
paid.
A
Other
contract
says
no.
We
will
pay
you
every
month
on
whatever
services
that
are
being
provided
to
you.
So,
depending
on
how
you
set
up
the
contract,
these
things
would
be
available,
but
the
Crux
of
the
thing
is
neither
a
ramco,
neither
the
supplier
or
the
contractor,
they
are
not
generating
the
invoice.
It
is
not
manual
system
will
tell
that.
Based
on
these
formulas
see,
this
is
the
final
invoice.
This
is
the
associated
documentation
with
respect
to
it.
A
So
this
is
how
things
would
be
generated
across
as
part
of
a
invoice,
and
this
is
a
digital
invoice.
Now
there
are
other
advantages
to
it
as
well:
a
mandate
for
e-invoicing
Kingdom
across
in
Saudi.
So
what
happens?
They
implemented
this
thing
so
now
the
supplier
doesn't
have
to
do
separately
right
because
from
the
system
it
would
be
based
on
the
Mandate
that
it
would
be
directly
generated
across.
So
these
are
some
of
the
advantages
now.
Another
thing
is
that
we
we
could
think
about
that.
A
Okay,
any
organization
in
order
to
pay
its
supplier,
the
longer
it
takes.
It
is
good
for
them
right
why
you
want
to
pay,
but
for
the
aramco,
the
biggest
one
of
the
challenges
was
that
they
have
kind
of
SLA
that
if
everything
is
verified,
we
will
pay
you
in
one
or
two
days
now,
because
of
this
complexity,
that
you
don't
know,
the
funds
would
be
required
in
the
next
one
month
next,
one
week
or
next,
two
months
or
next
three
months,
they
have
to
log
the
funds.
A
So
they
cannot
do
anything
about
those
particular
points
with
this.
The
cash
flows
improves.
So
there
is
a
Advantage
for
the
ramco
as
well,
and
another
thing
is:
supplier
also
has
a
great
Advantage,
because
if
they
come
on
this
particular
solution,
they
would
be
paid
faster,
so
I
think
you
can
discuss
the
other
advantages.
B
You
know
I
will
reiterate
the
challenges
like
the
frequent
disputes,
lengthy
processing
time,
as
you
could
tell
from
the
previous
discussion
and
the
maybe
it's
prone
to
overpayments
error
also,
and
the
enablers
to
solve
these
challenges
are
the
smart
contract,
the
share
Ledger
and
the
digital
signature
that
we
introduced
using
the
blockchain
solution,
and
these
are
the
benefits
that
we
got
from
the
solution.
That
processing
time
is
really
optimized
around
90
percent
enhancement
for
that
processing
time.
B
A
One
other
thing
I'd
like
to
highlight
in
the
last
slide
that
we
can
see
across
about
overpayment
errors,
consider
the
situation
when
everything
is
paper
based.
So
what
can
happen
is
that
a
rogue
supplier
can
book
one
person
with
certain
hours
in
one
time
sheet,
because
it's
all
manual
right
and
book,
the
same
person
and
some
other
project
and
some
other
timesheet.
There
is
no
control
right,
but
now
the
smart
contract
is
seeing
that
this
is
one
person.
A
How
can
it
go
at
the
same
time
on
the
same
day
with
the
same
amount
of
hours,
so
a
kind
of
governance
which
was
previously
not
available?
A
lot
of
those
particular
conditions
came
into
the
highlight
and
when
we
showed
this
particular
solution,
those
guys
were
really
excited
that,
yes,
whatever
is
written
in
those
particular
IAP
books
as
conditions,
they
could
be
actually
automated
and
cached
across
and
not
allowed
in
the
first
place.
A
Second
thing
is
about
digital
signatures:
I'd
like
to
identify
that
as
well
that
in
a
blockchain
and
a
hyperledger
fabric
implementation,
it
is
the
organization
identification,
but
in
real
world
what
happens.
It
is
the
people
that
are
signing
those
particular
document,
so
you
need
people
digital
signatures,
since
such
a
feature
is
outbound
not
available
in
hyperledger
fabric.
A
So
what
happens
is
all
the
organization
users
that
are
also
onboarded
their
digital
signatures
or
public
private
keypads
are
also
recorded
and
every
signature
they
do
like
a
timesheet
that
they
approve
so
on
a
blockchain,
a
transaction
as
a
digital
record,
for
that
particular
signing
is
there
which
is
verifiable
as
well.
So
this
is
one
another
thing
which
is
different
than
the
paper
based
approach
that
was
happening
previously.
B
Always
summarize
the
value
again
that
is
provided
by
the
blockchain
solution
when
we
compare
the
the
as
solution
with
the
2B
or
the
current
solution
with
the
blockchain,
you
know
all
contracts
were
paper
based
more
than
100
Pages.
Now
we
have
Smart
contrast
summarizing
all
the
terms
and
conditions
contributing
to
the
amount
of
the
invoice.
At
the
end,
all
the
manual
work
for
the
service
delivery
is
gone.
B
Now
we
are
dependent
on
some
automation,
all
transactions
for
the
service
delivery,
tracking
are
and
the
shared
Ledger
between
the
two
different
parties,
Saudi
aramco
and
the
vendor.
The
system
of
recourse
was
distributed
and
scattered
everywhere,
emails,
Microsoft,
Office
files
like
word
excel,
and
maybe
some
an
official
communication
even
using
phone.
Now,
it's
all
share.
B
Ledger
and
voices
were
scanned
in
an
invoice
package
with
all
supporting
documents
and
being
submitted
with
hundreds
of
pages
at
the
end
of
the
month
or
at
the
end
of
the
service,
and
then
the
starting
of
the
verification
or
the
verification
starts
only
then
scanned
supporting
documents,
but
now
system,
generating
support
and
supporting
documents.
For
example,
demand
hours
can
be
summarized
okay
through
the
system
no
need
to
submit
like
scanned
copies
about
the
timesheets
for
the
individuals.
No
time
sheets
can
be
calculated
and
provided
as
generated
by
the
system.
A
Okay,
so
these
are
some
of
the
application
components
as
I
specified
across
that
a
blockchain
is
not
only
a
hyperledger
fabric.
There
is
a
complete
ecosystem
around
it.
There
would
be
off
chain
components
that
would
complement
it.
There
would
be
user
interfaces
with
which
organization
will
work
across
there
would
be
API
integration
with
the
traditional
system.
A
That
is
going
to
happen,
and
in
this
case
it
is
both
the
Saudi
aramco
systems,
as
well
as
the
contractor
systems
that
could
be
connected
across
and
the
user
interfaces
to
be
provided
to
those
particular
partners
that
are
currently
working
totally
in
Excel
or
without
any
automation.
So
one
is
the
contact
definition
module
whereby
you
can
Define
what
are
the
contract?
What
are
the
contractual
terms?
What
are
the
parameters
within
those
particular
contract?
So
that's
one
part.
A
Then
there
would
be
different
kind
of
service
requests
that
are
available
and
there
is
a
variety
of
different
kind
of
a
request.
It
is
also
not
standardized,
so
there
is
a
standardized
version
as
well,
but
there
are
different
versions
of
well
sometime.
It
is
called
a
service
order.
Sometimes
it's
a
master
service
order.
There
is
a
work
order.
There
is
a
work
element
release,
so
a
lot
of
combinations
are
available
for
just
defining
the
service
request,
timesheets
and
approval
forms.
They
are
kind
of
common
across
what
they
capture
is
different.
Things
like
as
I
specified.
A
Sometimes
it
is
a
very
straight
time
that
is
provided,
but
in
other
cases
it
is
the
benefits,
other
direct
costs,
all
of
them,
combined
together
to
create
a
straight
time.
So
there
is
some
kind
of
a
complexity,
Auto
invoice
generation,
module
that
takes
the
blockchain
data
and
outputs
all
the
PDFs.
So
this
is
that
particular
module.
So
this
is
with
the
business
area,
which
is
there,
but
other
components
are,
for
example,
the
apis
that
are
being
created
and
provided
to
the
systems.
In
certain
cases,
interfaces
are
provided
by
the
blockchain
application.
A
This
is
particularly
true
for
the
contractor,
because
some
of
the
contractors
did
not
have
any
systems,
so
they
have
to
do
the
data
entry
itself,
events
coming
from
the
blockchain,
so
there
are
event
handling
components
that
are
created
across
and
at
the
bottom
authentication
and
authorization
notification,
because
it
is
required
right,
a
timesheet
is
submitted.
Then
somebody
in
America
needs
to
know
using
a
notification,
so
amount
of
module
for
that
signature.
Verification
as
I
specified
the
all
the
users
that
are
onboarded
across
the
organization.
A
A
There
are
workflows,
so
what
happens
is
that
when
the
supplier
or
the
contractor,
is
submitting
a
timesheet,
maybe
his
boss
wants
to
review
it
before
it
is
submitted
to
a
ramco.
So,
inter
organization
workflows
are
available
as
part
of
this
particular
solution.
So
it's
not
only
the
Contracting
smart
contracts
for
the
workflow
signature
verification.
There
are
different
kind
of
smart
contracts
that
are
running
there,
replication
of
the
data
for
the
reporting
purposes.
So
these
are
some
of
the
other
areas
and
the
application
components
that
we
have
available
here
now.
A
One
other
thing
that
needs
to
be
seen
across.
When
we
talk
about
blockchain,
we
say
everybody
has
a
node
right
and
the
nodes
could
be
corrected
across.
What
we
have
seen
is
that
how
consortiums
have
evolved
is
that
there
is
a
champion
entity
because
it
has
to
prove
a
concept.
Other
party
says
no.
We
are
not
ready
to
invest
in
this
particular
thing.
A
So
initially,
the
owner
of
the
Consortium
says
okay,
I'll
host
all
the
nodes,
so
this
is
one
element
of
it
that,
with
ramco
and
with
its
different
supplier,
they
are
hosted
with
an
ibp
itself
within
a
ramco.
So
that's
one
thing.
Second
thing
is
contractor,
saying
across
that:
okay
I'll
host,
my
note,
so
that's
a
very
traditional
architecture
with
which
you
can
connect.
A
Third,
is
there
are
smaller
partners
right
now
you
create
a
totally
separate
node.
That
would
be
expensive
right
because
from
a
business
sense
the
contribution
is
not
that
much.
The
business
benefit
is
not
that
much.
So
what
you
can
do
is
you
can
create
a
shared
node
with
the
shared
node.
What
will
happen?
It
will
have
technically
the
same
MSP,
but
the
data
is
recorded
on
different
channels.
So
this
is
one
another
concept
that
we
normally
utilize
in
the
deployments
that
we
do
either
the
Consortium
owner
hosts
the
notes.
A
Node
is
outside
or
it's
a
shared
load
so
that
everybody
could
be
onboarded
very
much
easily
and
everybody
gets
the
benefit
of
the
blockchain.
So
this
is
about
the
deployment
architecture,
and
you
can
see
that
the
contractors
they
can
have
system
to
system
or
a
user
to
system
interaction
and
on
the
other
side,
Saudi
aramco
guys
they
don't
feel
at
all
the
blockchain,
because,
whatever
uis
they
were
seeing
across,
they
see
the
same
UI.
They
see
press
the
same
button.
They
work
in
the
same
manner
that
they
were
previously
doing
across.
A
So
I
will
go
about
the
implementation
challenges.
One
of
the
first
implementation
challenge
that
comes
is
about
the
security
and
organizations
like
anamco.
They
have
a
number
of
teams
which
are
separate
infrastructure.
Security
is
separate.
Network
security
is
separate.
There
is
a
governance
and
risk
that's
separate.
So
a
lot
of
different,
like
sub
organizations
with
with
ram
course
are
there.
All
of
them
have
certain
conditions
that
you
need
to
comply.
A
So
this
is
one
of
the
part
that
takes
time
in
order
to
actually
create
this
particular
architecture,
and
since
we
were
the
first
one
for
the
others,
implementation
that
will
happen,
they
had
some
relaxation
because
we
protect
all
these
things
and
to
Ram
with
how
things
will
happen
from
a
security
perspective.
This
took
us
a
certain
amount
of
time,
and
even
there
are
other
challenges
as
well
like
you
cannot
just
deploy
the
components,
because
at
the
back
there
are
certain
node
modules,
for
example
that
could
be
utilized
right.
A
A
Other
thing
is
about
engaging
the
people.
There
are
separate
departments
for
each
of
the
Contracting
governance.
There
are
separate
Department
who
are
taking
for
the
business
like
awarding
those
particular
jobs.
There
are
separate
departments
that
are
saying
for
the
day-to-day
operations
and
there
are
separate
people
who
actually
verify
certify
the
things
across.
So
lot
of
stakeholders
need
to
be
engaged
across.
You
have
to
take
everyone
together.
Otherwise
nobody
is
excited
about
technology.
They
want
business
right
at
the
end
of
the
day,
so
everybody
has
to
be
taken
across.
A
So
this
is
one
another
important
challenge
that
we
had
and
last
thing
is
think
about
a
case
because
it
is
all
paper
right.
I
am
creating
invoice
in
my
format.
I
am
like
putting
the
data
in
my
format
and
submitting
across
somebody
else
is
doing
something
else.
Somebody
has
some
systems,
somebody
do
not
have
a
system
now
it
is
all
standardized
if
a
new
supplier
comes,
he
comes
with
a
node.
All
these
processes
are
already
available,
they
have
to
just
log
in
and
it
becomes
easier
for
the
supplier
as
well.
A
So
this
means
you
have
to
take
all
the
contractors
and
all
their
people
as
well
into
confidence,
and
this
could
happen
right.
I
can
go
with
one
of
the
contractors
and
then
find
out,
but
that
would
not
be
the
true
situation
on
ground,
so
we
had
to
engage
initially
multiple
contractors,
listen
to
them,
what
are
their
problems
and
take
their
buying
as
well,
so
this
stakeholders,
both
at
aramco
as
well
as
all
those
contractors.
B
Finally,
I
will
give
some
statistics
some
numbers
about
the
system.
Now,
as
a
current
state,
we
have
imported
11
vendors
till
now
the
submission
to
payment
cycle
reduced
by
90
I,
as
I
mentioned
in
the
benefits
from
the
system
we
processed
up
to
now,
more
than
28
invoices
using
the
system
and
zero
disputes
till
now
and
one
to
three
months.
Verification
period
is
now
reduced
to
around
two
to
eight
days
or
maximum.
We
can
say
two
weeks,
which
is
really
a
great
benefit,
and
this
is
an
incentive
really
for
our
vendors.
A
A
To
kind
of
convince
them
from
the
value
perspective,
or
did
you
say
hey?
This
is
blockchain
you're
going
to
use
this?
How
do
you
kind
of
approach
that
okay
I'll
answer
in
this
particular
manner?
Let's
see
when
you
need
to
engage
at
different
levels,
you
engage
in
a
different
manner,
so
the
higher
management
that
is
there
in
that
particular
organization.
You
take
it
from
a
perspective
of
business
benefit.
You
were
getting
the
invoice
in
two
to
three
months.
You
will
get
the
money
in
two
days.
Are
you
interested?
A
Yes,
I
am
interested,
so
it
users,
business
users,
operational
users,
operational
users.
If
you
see
their
challenges,
will
I
do
more
work
than
I
do
was
doing
previously.
You
have
to
convince
him
that
no,
you
have
to
do
less
work
now,
so
he
is
on
board.
So
this
requires
certain
soft
skills
as
well
to
actually
onboard
them.
It's
not
about
technology
and
what
we
have
seen
is
you
tell
anyone.
There
is
a
blockchain,
nobody
will
come
and
actually
on
board
over
there.
Blockchain
has
to
be
at
the
background.
A
It
provides
all
those
particular
things
which
are
very,
very
much
required,
but
people
see
what
is
visible
right.
Business
C
business
benefits,
users
see
how
they
are
working
or
interacting
with
the
system
make
that
thing
right
and
you
can
have
this
particular
blockchain
implemented
easily.
So
it
involves
those
particular
soft
skills.
A
B
Will
repeat
the
question?
Maybe
because
it
was
not
hearable
to
the
audience
in
the
virtual
session,
that
is
the
invoice
generated
outside
this
AP
and
if
the
invoice
is
being
moved
to
sap
and
updated
there
right.
Is
this
your
question?
Yes,
the
invoice
is
generated
by
the
blockchain
system
and
fed
to
the
sap
system
and
later
on,
the
payment
will
be
carried
out
in
the
sap
system.
B
The
payment
status
will
be
updated,
then,
in
the
blockchain
only
the
payment
status,
so
the
payment
process
itself
will
be
all
carried
out,
as
is
now
in
the
Erp
system
and
this
AP,
but
the
status
update
will
happen
also
on
the
blockchain,
so
the
full
end-to-end
cycle
can
can
be
visible
to
all
parties
that
okay.
This
invoice
has
been
generated
by
the
system
submitted
by
the
by
the
vendor
and
paid
by
Saudi
aramco.
A
A
Technically,
somebody
can
go
and
modify
that
thing
in
the
middle.
That
could
happen
so
how
controls
are
put
across
that
the
document
that
is
created
it
hash
is
also
recorded.
Hash
of
that
particular
record
is
also
recorded
onto
the
blockchain,
and
that
document
is
verifiable,
because
when
you
will
put
that
document
across
you
can
compare
that
hash.
So
even
those
particular
documents
are
kind
of
tamper
proof.
A
So,
even
if
you
try
to
go
into
the
middle
and
try
to
put
certain
documents,
which
is
a
different
one,
maybe
a
system
administrator
has
access
or
do
something
so
that
will
not
work
out.
It
would
be
flagged
across
as
well,
so
blockchain
is
being
used
and
from
a
security
and
threat
cases
perspective.
These
things
are
seen
through
that
such
technical
things
are
also
not
violated.
B
A
B
A
See
there
is
always
a
hybrid
approach.
There
are
certain
mature
organization
who
have
the
system
organization
that
has
a
timesheet
system.
They
are
already
recording
that
particular
data
right,
so
system
to
system
integration
is
the
way
so
the
user
Works
in
their
own
system.
At
the
back.
You
take
those
particular
record
and
put
it
onto
the
blockchain
because
it
has
to
be
passed
to
the
other
organization.
A
That's
the
thing,
but
there
would
be
other
organizations
that
they
might
not
have
the
system,
so
you
create
a
dab,
distributed
this
particular
user
interface
and
that
connects
with
their
node
and
show
that
particular
data
beautifully
like
they
can
see.
What
is
the
status
of
the
timesheets
that
they
have
uploaded?
What
stage
of
workflow
they
are
there.
So
this
is
on
the
contractor
side.
They
are
working
totally
on
their
node.
On
the
aramco
side,
we
have
not
created
any
additional
user
interface
because
they
have
already
sap
system
which
is
available.
A
A
B
B
However,
yes,
if
we
overcome
these
security
barriers
now
which
are
almost
following
the
traditional
software
verification
cycle,
we
can
Import
in
one
day
as
you
said,
but
you
know
yeah
technically,
okay,
but
what
would
it
take
for
a
new
vendor
to
like
do
the
change
management
or
to
train
their
users?
It
will
take
longer
for
sure,
but
technically
yeah
I
can
import
them
and
configure
and
operate
their
node
in
in
one.
A
Day
so
if
we
see
a
crossy,
you
know
any
onboarding
activity,
because
we
have
been
working
with
multiple
Consortium
in
which
new
participants
are
always
added.
There
are
certain
steps,
one
as
a
technical
step.
You
need
to
spend
the
node.
You
need
to
put
all
those
off
chain
components
you
need
to
create
those
particular
users.
You
need
to
have
the
authentication
and
everything
right.
So
this
is
something
now
technology
is
there
like,
for
example,
you
have
form
with
which
you
can
automate
it,
so
everything
node
would
be
spent
in
a
matter
of
minutes.
A
That's
not
a
problem.
All
the
hyperluster
command
to
make
the
channel
join
the
channel.
Everything
can
happen.
So
that's
not
the
part.
The
second
thing
is
how
that
organization
will
connect.
This
would
require
certain
things
because
no
Enterprise
was
going
to
allow
and
open
the
port.
Quite
much
easily
security
teams
will
once
again
come
and
assess
that
everything
is
fine
on
both
the
sides.
This
activity
typically
takes
time
and
it's
nobody
in
control
right
because
it
is
up
to
the
security
teams.
The
third
thing
is
those
system
with
people
who
have
to
use
the
system.
A
They
need
to
be
trained
as
well,
so
you
should
keep
something
around
of
one
week
or
two
weeks
training
period,
and
what
they
have
done
is
that
they
have
invited
complete
organizations
into
I,
think
big
holes
and
done
multiple
trainings
with
them.
This
is
very,
very
much
important
as
I
was
saying.
All
the
stakeholders
need
to
be
actually
made
aware
system
should
be
easy
for
them.
It
is
not
like
the
technical
people
have
delivered
and
nobody
can
use
it.
So
that's
that's
a
very
important
element
to
it.