Key Points

1. Blockchains deliver the most value integrating networks
2. Blockchains can add value in centralized and internal applications as well for data compliance services over traditional database

In my experience, blockchain technology is a lot like tennis

it's not the technology that is the key driver to business success

John McEnroe and I used the same tennis racket with very different results

References

Key Concepts

Blockchain Engineering Lessons Learned

------------------
chris g

6 wk poc time frames
automated devops

oil and gas use cases -
> frictions
no net
legacy erp - no edi ???
old biz processes

> bpr opportunity w automated integration
move from sap to sap ?? or ??
O>> sap bc svc
form 1 co w few suppliers for consortium w governance, pricing

baker hughes field svc, mid east ...
looking at bc

HL talking to Oman
looking at bc accelerator for Omani state oil co
convert to bpm

HL can deploy on any cloud platform, uses K8s

SAP issues
old ECC version from Oracle vs Hanna
db migration project to Hanna
synch reqmt to link ERP, bc via API
piecemeal approach to bc solutions

oil field GNA costs are high
add RPA to SAP to lower costs

1> bc with RPA links
2> bc to ERP via api
3> bc links via db

legal compliance opportunity

Working models with HL
HL can be a subcontractor, co-brand or host on HL
Paramount owns client, HL is delivery sub contractor

Next steps
Chris G email on working options
NDA before collaboration
Define project, POC

Keys
client participation in use case definition, value opp
current pain points now to focus value on
what's manual?
what requires costly, long edits, reconciliations?
are there counter parties in the process?
client defines pass / fail criteria for POC use case
POV approach to validate value delivered in bc solution
POV is 6 weeks to measurement of value

bc marketing, engineering challenges
what has paramount done on bc in this sector in production?
can add incentives to get suppliers to deliver, pay faster
rethink opportunity to define better value from all roles
all oil companies running same SAP system as EOL

if contracts renegotiatied, there's a winner and loser
with bc re-engineering for the network allows all to cut overhead

fabric v2x is duct tape - works anyway you need

producer > midstream channel
get agreements on contracts, rules, data visibility
data privacy with authorized visibility
separate contract to midstream providers

producer > refiners channel
get agreements on contracts, rules, data visibility
data privacy with authorized visibility
separate contract to refiners

refiners > retail channel
get agreements on contracts, rules, data visibility
data privacy with authorized visibility
separate contract to retailers

bc project decision flow gates ...
poc?
feedback?
pilot?
feedback?
production
feedback?

POV constraints
6 week POC
limit to 2 suppliers to work with
pre-defined contracts, rules, pricing
requires clean master data
support push notifications where person approvals needed

POV results
share POV results across the network

data quality metrics
deterministic data inputs - avoid human custom input
master data dependencies
actors are secured by certificate identities
known entities on the network good candidates for the bc

bc is like my experience with tennis
it's not the technology that is the key driver to business success
John McEnroe and I used the same tennis racket with very different results

Potential Value Opportunities

Potential Challenges

Candidate Blockchain Engineering Solutions

-------------------------------
#bc.concepts

checkpoint chains can eliminate fraud attacks

checkpoint chains can ensure integrity of a base chain and provide recovery points

keeping source data after checkpoint allows rebuilding a base chain to the curerent state

merkle forest = decentralized bc segments directory service

dac ( decentralized audit chains ) vs pbft
dac = dependent proof checkpoint chains

hierarchical directory for chains

bc segments are doubly linked lists to set of chained blocks

the blocks in the segment are chained following traditional hashes

the segment knows the block ids it contains

the blocks know their segment ids

a query for blocks run through the segment trees by block id

client access controls to chains

gatekeeper routers validate clients
reverse execution token granted to track X?

token history
wallet has tokens but token history?

wallets only need tokens if they need to be transferred to other account wallets

dirving requirements with BDD with Groovy DSLs

dsl = expando2

DB reverse engineering for Groovy Domain classes

read tables in list using jdbc metadata

generate groovy class files with default foreign key relations

db.rev.gen2 w ddl annontations on relation types ( belongs vs has etc)

Candidate Solutions

Step-by-step guide for Example

sample code block

Recommended Next Steps

Related articles