Key Points

1. Wipro presentation on Paramount services
   
   1. our company
   2. our resources
   3. our experience
   4. our strategy
   5. our value add
      1. blockchain, data services, analytics, other ( was, mq, web services, ibm i, ecms, web dev ), integrations, clouds, iot ( nodered ), automation
      2. our investments > hlf certs, k8s, app connect, ibm i toolkits – > Fabric Certified Solutions Provider in progress
      3. 2 way marketing leads?
   6. our customer approach - metagility, sdp, boa, pox
   7. our partnerships
   8. next steps
2. Wipro keys for implementation software partner
   
   1. marketing and implementation partner —   cbtp - lsp - isa - vcrs - factur3.io
      1. write articles - case studies - tutorials
   2.  team interested in how we can help - opportunity to be major solution / services partner for them
   3. key focus areas for Wipro:
      1. DT roadmap = VCN maturity cycle ( connected > integrated > coordinated > automated > smart )
      2. Cloud migrations
      3. Cloud Paks
      4. Watson family - Studio and more
      5. Data Solutions
         1. Cognos - analytics - BI
         2. MDM - master data mgt
         3. SPSS - statistical analysis tool sets
         4. Informix - SQL, NoSQL, spatial, time series ( like MySQL, MariaDB )
      6. Messaging - IIB
      7. Security Services
      8. Blockchain Services
      9. Integration Services
      10. AppConnect
      11. Nodered
      12. StrongLoop
      13. OpenWhisk ? event services
      14. Grails
      15. What about Identity, Key management services, Session Tokens, RBAC?
      16. more
   4. more
3. more

References

Wipro solution areas

Partners deliver Marketing and Technical resources to sell, implement, service Wipro services and solutions stack

Our Transformation Strategies ...

EDT >>

HCA - Hybrid Cloud Architecture

CSA - Cloud Services Architecture

VCN - Value Chain Network

Blockchain Services

Kubernetes

IoT automation

Smarts

Compliance services

Other Priorities

other data svcs, cloud
data arch, svcs, pipelines, streams - sql, nosql, procs, views
java and nodejs
bi tools - oss, gds, obi,
was, iib, ace, camel, nodered,
guardium

other systems, iot, automation,

Key Concepts

Wipro potential strategies

1. Company introduction --- 2 minutes
   1. alignment with Government, Industry sectors, Technologies, IBM Portfolio
      
      
2. Paramount Blockchain Practice
   
   
3. Opportunities to work with IBM
   
   
   1. Existing challenges, opportunities and goals from RFP
   2. Goals and Opportunities
   3. Next Steps
      
      
4. Hi level requirements summary
   1. Assumptions list from PSS to validate on our concepts
   2. Key Issues to Address
   3. Solution strategy to selected scenarios conceptually
   4. POC / POV for key design decisions and validation
      
      
5. Our Solution Strategy & Technical Solution Concepts ---- 15 minutes
   Responses that addresses the requirements set forth in the IPB such as:
   1. solution strategy - follow RFP process, build foundations, then address key use cases in priority order
   2. why enterprise blockchain adds value
   3. why fabric ?? --- diagram from Forbes 50 ...
   4. Privacy and Security
   5. Document sharing amongst stakeholders and auditability
   6. Integration capabilities with IT systems and blockchain interoperability
   7. Scalability of the solution
   8. Governance model of blockchain network
   9. Build concepts
   10. Operate and govern concepts
   11. Grow concepts 
       
       
6. Relevant Paramount enterprise blockchain solutions – 5 minutes ???
   Past or current projects that may demonstrate the firms experience (optional)
   1. Farm to Plate - tracking example on web console
   2. Social Good POC - Mobile interface, custom tokens for incentives
   3. NSF - secure, decentralized energy marketplace for Solar
   4. Sextant Solutions - TVA - identity management solutions
      
      
7. Address how your firm would approach the PoC. - 5 minutes
   1. Dr David Bishop - Metagility - project management methods
      
      
8. Summary on next steps and Questions – 10 minutes

The ISX client reporting series

Service

ISA

ISP

ISR

IST

ISD

ISM

ISI

ISS

SOA - Solution Opportunity Assessment

Assessments on

Blockchain, Services, IoT, Data services, Analytics

Proof of Concept (POC) Goals - POT > POC > POV

The  Statement of Work (SoW) defines requirements for the proof of concept using blockchain and distributed ledger technologies ( DLT ).

Functional:  Address disbursement traceability challenges in the World Bank funded projects

Key non-functional features: a production-ready pilot that addresses: security, privacy and scalability

Define the risks and challenges of operational DLT for loan disbursement

Learnings from this prototype could be used for consideration of a potential pilot phase in the future

Challenges for a DLT Solution Strategy

Performance will continue to scale from current levels significantly over the next few years

As DLT evolves, timely testing and migrating to new versions is important

It's not clear how privacy, security and other regulations will evolve from different entities

How will new features, solutions and technologies be integrated?

Where will the solution run?

How will appropriate users participate in the solution?

What are the implementation, roll out challenges moving to the solution?

How will VCRS ( Value - Costs - Risks - Support ) be managed across the Value Chain Network ( VCN )?

Solution Scope

loan disbursements to network participants for defined disbursement scenarios

Candidate Solution Requirements 

integrated identity management - options for DID or existing IDs

integrate to existing grants, loans system

Section 3 - Solution Strategy deliverables

• Architecture of the end-to-end systems required to achieve the solution(s).

slides on Fabric solution software stack

logical vs physical network model 

supports all actors, disbursement scenarios 

• Suggested approach for what data should be captured and stored on chain vs. off chain (e.g. via a database or other solution).

Identity

all participants ( users, organizations ) need an identity on the network

POC can use MSP, CA but production should consider DID

https://medium.com/uport/the-basics-of-decentralized-identity-d1ff01f15df1

• Detailed information about the blockchain/DLT technology, including:

• a) the consensus mechanism that will be used and ability to configure the parties participating in that mechanism; and

• b) baseline performance metrics (e.g. transaction throughput),

• c) scalability of the solution,

• d) future proofing the solution by exploring the viability of implementing smart contracts, tokens,

• e) potential to interoperability of the solution(s) offered.

Recommended Fabric Consensus Model

recommend RAFT consensus model at this point for a version 2x production solution

Fabric provides very flexible endorsement policies that can match specific network roles

Performance monitoring

Caliper provides operational metrics on blockchain performance

compare 3rd party tools like BlocWatch 

create performance aggregates for throughput and response outliers by period for trend, exception analysis

RAS - Reliability, Availability and Service

Blockchain networks have some built-in advantages as decentralized systems

Fabric version 2x further decentralizes the system with decentralized ordering services 

Organizations and nodes that go offline can catch up automatically on reconnect with the ledger

Smart Contract Life Cycle Support in v2x

Transactions are digitally signed, executed, endorsed and tracked on the immutable ledger

Smart contract versions are also signed and tracked on deployment providing complete audit trail

Smart contracts have decentralized governance for deployment with policy-driven endorsements for deployments

Smart contract ( chaincode ) packages can be inspected, deployed multiple times

Smart contracts can be extended to provide custom validations on transactions for example

Private Data Enhancements 

https://hyperledger-fabric.readthedocs.io/en/latest/whatsnew.html

Instead of sharing private data within a collection of multiple members, you may want to share private data across collections, where each collection may include a single organization, or perhaps a single organization along with a regulator

Private data can be shared with members not a member of a private data collection

Member receiving shared data can verify the transaction is valid by matching the on-chain hashes

Private data allows custom, optional endorsement policies that override smart contract endorsement policies

For example, 2 orgs with private data may have to endorse the transaction as well

For direct, per-organization private data sharing, private data collections do not need to be defined first

Token Support 

Design process can determine the need for different token types in the disbursement solution

Token Taxonomy Initiative defines a Token Taxonomy Framework 

https://github.com/token-taxonomy-initiative/TokenTaxonomyFramework

http://tokentaxonomy.org/wp-content/uploads/2019/11/TTF-Overview.pdf

Examples of tokens defined in version 1 specification 

• Provide a governance model including processes, structure, etc. for the blockchain/DLT network.

• Recommendations for additional complementary technologies to support the objectives. Recommendations for a successful implementation and integration with other systems and to capture data automatically without human intervention.

automation via IoT devices and sensors for data capture and validation where feasible

automated monitoring on data quality at data capture ( entry - edit - post )

automated monitoring of project disbursement limits by actor and role

external systems integration - real-time editing on data capture 

event driven and batch control posting of blockchain transactions to auxilliary systems

• Recommendations for end beneficiary interaction with the blockchain/DLT system and the processes surrounding onboarding (KYC/AML), offboarding, data collection, data privacy/sharing of end beneficiaries.

Assumptions and Considerations for end beneficiaries

All beneficiaries ideally have a compatible mobile device to access the network BUT this can't be assumed as a requirement

When on-boarded, all beneficiaries need to provide an proof-of-identity ( via online registration or another method )

All beneficiaries need to be assigned an identity from the World Bank and stored in the network for remote access

All beneficiaries need to consent o the terms and conditions of operating on the World Bank network and are subject to application local regulations

Beneficiaries accessing the network need to use an approved multi-factor authentication method ( MFA ) on the device

Auditors and regulators have defined access rights to authorized data subject to any applicable legal limitations

Where feasible and within regulations, personal data is not shared with others on the network without consent

If self-sovereign identities ( SSI ) are used, then zero-knowledge proofs can be used as identity and claim proofs for verification

Decision on which languages and localization will be supported 

• Security, access control, permissions, data privacy and scalability are essential and must be described as part of the response. Also, from the data privacy perspective, provide information on potentially applicable local laws that may need to be considered to ensure that sensitive data of data subjects can be processed in the manner contemplated, examples include, banking or financial sector regulatory restrictions, or data localization issues and etcetera.

• A project plan for this proof of concept.

Proposed POC Project Plan

The production project plan will be set during the POC based on requirements and results

The POC project prerequisites address several areas:

Establishment of POC project governance and success criteria

Loan disbursement process requirements

Requirements for actors by role to participate in the network and processes

Solution surveys validating needs analysis and usability of selected participants

Analysis of existing systems gaps, performance

Conceptual design of the production system

Conceptual design of the production infrastructure 

Using the recommended Agile process, the POC project plan covers several areas:

POC Design of selected processes, actor roles, transactions and validations

POC infrastructure build out including POC security 

POC integration interfaces 

POC identity management enrollments and authorizations for participants

POC development of required artifacts

POC applications, systems integration and load testing

POC operations automation and testing 

Evaluation and feedback from POC participants

Review of POC systems results 

Section 3 - Solution Strategy updates

architecture models ...

.. see ibm docs 

view the logical software stack 

the logical network

the privacy & confidentiality 

the identity 

the security

update Logical slide with diagram

update Identity and Security slide 

add Identity Integration Options 

IDEMIX

add IDEMIX option ???

Indy ??

add slide

Candidate Solution Components

Indy, Explorer, Caliper, Cello and more

show Indy integration example – see verified.me and ??

Related articles