You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When project developers and/or other policy users follow the workflow submitting data in forms etc they currently have no way to foresee what effect the data they input would have or results they'd produce. I.e. there is no way for them to 'trial-run' individual steps or the entire policy with project data and to see, for example, the resulting calculations of estimated ERRs.
Requirements
We are in the process of creating a few approaches to this ticket from the business use case perspective. One is essentially an “estimator” with a simplified workflow that can be used to estimate emission reductions, token issuance, etc. upfront to help the user better anticipate issuances and the impacts of various project activities and methodological choices. The other is more of a “summary preview” of the actual calculation results, that can be implemented just before validation (or anytime thereafter) to see summary KPIs based on the actual inputs and methodological choices made by the user, and they can then interact with the data like the Nerd Wallet retirement calculator to see how changes to the project activities could impact issuances. To be discussed further with the team.
Definition of done
Create a Business Use case approaches for Pre Calculator.
Creating a detailed document and video to explain the use cases to the community.
Acceptance criteria
What are the criteria by which we determine if the issue has been resolved?
The text was updated successfully, but these errors were encountered:
Problem description
When project developers and/or other policy users follow the workflow submitting data in forms etc they currently have no way to foresee what effect the data they input would have or results they'd produce. I.e. there is no way for them to 'trial-run' individual steps or the entire policy with project data and to see, for example, the resulting calculations of estimated ERRs.
Requirements
We are in the process of creating a few approaches to this ticket from the business use case perspective. One is essentially an “estimator” with a simplified workflow that can be used to estimate emission reductions, token issuance, etc. upfront to help the user better anticipate issuances and the impacts of various project activities and methodological choices. The other is more of a “summary preview” of the actual calculation results, that can be implemented just before validation (or anytime thereafter) to see summary KPIs based on the actual inputs and methodological choices made by the user, and they can then interact with the data like the Nerd Wallet retirement calculator to see how changes to the project activities could impact issuances. To be discussed further with the team.
Definition of done
Acceptance criteria
What are the criteria by which we determine if the issue has been resolved?
The text was updated successfully, but these errors were encountered: