Table of Contents

Key Points

BICARSA
dependencies on identities ( organizations, individuals ), accounts, accounting systems
payments
credit payments
bank payments
settlements
orders
invoicing
receivables
sales analysis

References

Reference_description_with_linked_URLs_______________________	Notes______________________________________________________________

	F2F Product document folder
Deck for InComm - Sep 23 v2 .pptx
https://www.finastra.com/solutions/transaction-banking/trade- supply-chain-finance	Finastra trade finance software supports SWIFT
payments and tokens service product concepts

F2P setup info


"mongodb+srv://f2puser:FarmToPlate@f2pdb.qunan.mongodb.net/F2Pdb?retryWrites=true&w=majority	url for Mongo DB for F2P TNT

Payments Task List

task___________________________________________________________________________	status_______________	Notes________________________________________
get bluenumber project access: JIRA, Confluence, Github, Postman, DB
get TNT project access: JIRA, Confluence, Github, Postman, DB
define process, inputs, prereqs for invoicing
define payment services for invoicing	Thomas poc	file system wallet
review onboarding model for growers, processors, shippers
check use of Indy IDs, wallets for Fabric MSP services
define any known integration requirements
create product roadmap

Key Product Solution Questions

What are the payment scenarios in F2P Finance?
what are the challenges, opportunities for each stage and role in the payment chain?
who can pay for the solution in the payment chain? ( NOT the growers )
what's the F2P story we share? ( challenges & opportunities, F2P FBRs, case studies )

Product Delivery Concepts

_Item__________________	notes______
https://dataports-project.eu/deliverables/ dataports-project.eu-Deliverables DataPorts.pdf	a>> well defined work packages for a product w good research tasks **

Key Payment Services Concepts

DPS - Digital Payment Services Feature Concepts

--------------
#DPS - digital payment services - DPS
--------------

...

DPS fees
- different use cases may have different fees
- fee structures should allow multiple servicers
- fee structures should support discount methods applied by account, account type ( eg a flat fee for all trans in period)
- fee visibility restricted by role
- should include coverage of all related costs to run, maintain, manage DPS
- should support usage credits, tokens based on defined rules

Thomas POC features tested

buy tokens with credit card

add payment method for account
buy tokens on credit card
show token purchase
explorer - view new account balance minus fees
stripe login
stripe payment with credit card shown

cash payout using xwise

xwise summary screen
xwise login - MFA
add new bank account
create cash payout
confirm the payout request w transfer shown
Stellar explorer shows payout transaction on xwise
> consider login to view the JSON details
xwise shows the payout to Paramount and the $1.05 fee

send money feature

F2P Solution Concepts

F2P Modules ( needs review )

IAMS - Identity, Access and Memberships Services

SCM - Supply Chain Management

FMS - Financial Management Services

Invoicing

Invoice reconciliation

...

ethical sourcing

fresher food

F2P Incomm presentation deck

Deck for InComm - Sep 23 v2 .pptx

see the ps deck model ...

https://en.wikipedia.org/wiki/GS1

...

related stds - ssi, did, toip, pki, ...
swt id bc pptx

Potential Value Opportunities

Food Supply Chain

Distribution models ??

free 30 day trials hosted

limited function, capacity open-source version

enterprise version

Potential Differentiators ??

pluggable interfaces for: identities, RBAC, data models, logic scripts, workflows, events

...

partners on sub-systems - eg payments, inventory

Research list

Normal ERP logistics apps in cloud

When we started there were no reference solutions to review and we went with our gut feeling but now the market is getting mature and we do have some references from different aspects covering the end to end provenance and tracking for the Food Supply Chain.
Please review the shared links and let me know your thoughts.

...

We have to use specific features from the above to guarantee a competitive end to end provenance and tracking solution for enterprise clients.

Potential Challenges

Legal Terms and Documents

I have shared the legal artifacts on Blockchain and would appreciate your views.This will help our attorney draft the contents precisely matching our expectations.

1 - Page numbered 2 and 3 section client responsibility

...

Will we be accountable for the Cloud infrastructure or how is it going to be managed and if a third party is responsible how does the accountability is reflected in the document.The IBM Cloud in document 3 shares about the T&C and we can customize from that.

My Onboarding support concepts

good customer service

easy, effective, low-cost Paramount support options

...

No-charge Account planning meetings to define
- goals, expected usage, gather requirements, plan any custom services, standard onboarding, training, connections, support and more
use youtube videos, docs as an option here
use knowledge base with youtube video links as first stop for help normally
provide direct email, live chat and phone support options for registered account contacts
use custom Zoom support meetings as needed to resolve issues
use online Grails app to record and manage work requests ( problems, questions, feature requests )
use online BIRT or equivalent Web report tool to show system usage and manage work request status
customer portal provides account information and billing status

Customer responsibilities for implementation and support

Customer Resources committed to meet planned onboarding and support requirements
Customer designates specific support contacts who go through on-boarding training courses
Customer is responsible for integrations to existing systems unless Paramount hired on a custom SOW under an MDA to provide services integrations
Customer documents planned usage of services using JEPL ( Java Event Processing Language ) to define a planned usage model for workflows, event notifications, automation
Paramount provides support on usage documentation with JEPL via knowledge base and support staff
Customer provides a test environment to test and validate planned usage and identity support problems separate from Production systems
Customer uses Paramount online support templates to record any support incidents ( problems, questions, feature requests ) and submit to Paramount online ( see work request template as a Grails app )

Candidate Solutions

F2P solution

MVP Plan

https://drive.google.com/file/d/1fmNi3Nptr335LZyp-40l8sM7kntZLzFh/view?usp=sharing

OKR - Objectives Key Results

Problem Statements

https://paramountsoft.atlassian.net/wiki/spaces/FAR/pages/264077353/Problem+Statements

Meetings

Restructure F2P product plan - 210504

Pramod,Yuva and I had a deep discussion yesterday and as an outcome of that we are going to sandwich the modules and reduce the timeline.

...

The next activity will be Invoice Management (within the Trade module) and Jim will take care of that.We are already hiring a Product manager to help Jim on that.
Remaining sub topics within each module will be considered later as and when the scope arises.

Expand

Step-by-step guide for Example

Info

sample code block

Code Block

language	text
title	sample code block
linenumbers	true
collapse	true

Page Comparison

Versions Compared

Old Version 4

New Version Current

Key