Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add these "purpose" sections back to the README #1

Open
thclark opened this issue Jun 15, 2023 · 0 comments
Open

Add these "purpose" sections back to the README #1

thclark opened this issue Jun 15, 2023 · 0 comments
Labels
decision needed A decision is required (e.g. on UX or company policy) documentation Improvements or additions to documentation

Comments

@thclark
Copy link
Contributor

thclark commented Jun 15, 2023

Feature request

The "purpose" section of the README has a high level set of bullet points on the benefits.

Before adding these high-level points, I wrote a longer section which was a bit more elaborate (but a bit less impactful!). We could consider re-introducing that text which is as follows:


This system has its drawbacks. As far as turbine manufacturers (_Data Providers_) are concerned:

- **Long Sales Cycle** - The sales cycle is much longer than necessary because detailed Site Design (SD) and Energy Yield Assessment (EYA) and processes are slowed down substantially.

- **Loss of Control** - Distribution of a PDF loses control of exactly who has visibility of information, when, and for what purpose (eg as opposed to distribution over a permission controlled API with time-scoped access tokens)

- **Reputational risk** - Manual processes lead to human errors, with potential to be using incorrect or outdated information. This affects EYA processes, with potential ramifications for bankability

- **Inability to update** - When updating control systems with new features, issuing site-specific curves, adding other performance modes, or making other updates, new power curves must be issued. It's difficult to demonstrate the direct benefits of these new features to customers, because each reissue results in many weeks of work for downstream _Data Consumers_ in order to be relected in any EYA. Being able to immediately show the effect of a new control system on the customer's EYA is a powerful sales tool.

As far as _Data Consumers_ (such as site developers and third party consultants) are concerned:

- **High overheads** - Transcription of power curve data into whatever format is used by internal tools
@thclark thclark added the documentation Improvements or additions to documentation label Jun 15, 2023
@thclark thclark changed the title Consider longer-form description Consider longer-form README Jul 6, 2023
@thclark thclark changed the title Consider longer-form README Add these "purpose" sections back to the README Jan 16, 2024
@thclark thclark added the decision needed A decision is required (e.g. on UX or company policy) label Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision needed A decision is required (e.g. on UX or company policy) documentation Improvements or additions to documentation
Projects
Status: Post first draft
Development

No branches or pull requests

1 participant