Who can see your viewing activity?
Are we recording?
who is AyanWorks represented by?
Hi Steve and everyone!
great direction for use cases - highly relevant today
i still haven't submitted yet but will over the weekend
https://www.covidcreds.com/ CCI's website for more information about the initiative
@Karl, can you post a link to this Google Slides presentation?
ONAP Meeting 2
To Dan’s query about whether there are gaps - I think we’d need to see a variety in use cases to arrive at the specifics of iterative improvement.
would add liabilities as is vs to be in the risk discussion
Nicky, that's a great one for healthcare too
Given we are in the context of an ecosystem, should there be a separate step/stage for the at least initial “Funding”? Seems we need a specific step to bridge from the non-economic to the economic. When the “ToIP Ecosystem” formed, this was a key step (member funding through the lean/agile JDF standup).
Funding should be part of Implement.
For sure @ Jim, really important for flows of liability, professional insurance etc
I think funding need not be an independent phase but be part of any
I think the we should schedule case review mtgs between WG mtgs b/c waiting 2wks is not productive.
@Will, interesting perspective setting up the ground rules for things like who is paying for what, who expects to make a profit etc. is very relevant to forming an ecosystem. Not sure how much detail falls into internal business model vs. ecosystem participation information
@scott i can see funding part of implement. thanks.
Can also see possibly under Create or separate/new as weel
@Will, Create would include the planning for funding, building the revenue model and that sort. It will also be part of Operate as ecosystem members join and leave the ecosystem.
@Steve Yes, very structured if ecosystem spawned as a new Series project non-profit legal entity under JDF (e.g. Steering, Associate, Contributor) but I think its part of this WG charter to help define a framework/template for consortia in for profit situations.
@scott - yes. agreed
@eric: it wld be helpful to you if u cld consider defining several use-cases becos I get a sense that your entire "value chain" comprises of several usecases
Doing case reviews between meetings is a good plan.
@Dan’s comment on frequency of use cases. +1
@Will, agree, I am just thinking out loud about where a framework ends and proprietary business information begins. For example a credit card ecosystem will publish access rates, but won't talk about their internal profit margins even though that (in a smaller context) might be relevant to the sustainability of an ecosystem
Yes, it does make sense.
@scott would love to discuss your use case before I submit mine :)
@Jim, sure. Let’s connect on Slack.
Thank you all. Solid set of conversations today!