Add text and link to use cases to homepage, some debugging on usecases page. (#12)

* create Use Cases page

* first use case, add to_top and sidebar

* add use case 2

* add use case 3

* edit use case 3

* add functional capabilities

* fix numbering in sidebar

* some corrections

* crossrefs

* update index to add use cases

* add quality check use case, debug use case navigation

Author: cwhanse

_includes/usecase_sidebar.html

@@ -23,13 +23,17 @@ <h2>Contents</h2>
           <li><a href="#uc3A">Disaggregate Sources of Performance Differences</a></li>
           <li><a href="#uc3B">Evaluate Sensors</a></li>
         </ol>
-      <li><a href="#portfolioanalysis">Perform portfolio analysis]</a></li>
+      <li><a href="#portfolioanalysis">Perform portfolio analysis</a></li>
     </ol>
   <br>
-  <li><a href="#capabilities">Functional capabilities</a></li>
+  <li><a href="#functionalcapabilities">Functional capabilities</a></li>
     <ol start="5">
       <li><a href="#performancemodels">Provide performance models</a></li>
-      <li><a href="#uploaddata">Upload data</a></li>
+      <li><a href="#uploaddata">Upload and check data</a></li>
+        <ol type="A">
+          <li><a href="#uc6A">Upload data</a></li>
+          <li><a href="#uc7B">Apply data quality checks</a></li>
+        </ol>
       <li><a href="#administer">Administer the platform</a></li>
         <ol type="A">
           <li><a href="#uc7A">Manage users and organizations</a></li>

index.md

@@ -8,19 +8,42 @@ The Solar Performance Insight is an open source tool to enable evaluations of so
 
 [Sign up](https://solarperformanceinsight.github.io/emaillist/) to recieve project updates by email.
 
-Members of the solar community are invited to join the [Stakeholder Committee](/stakeholdercommittee) to provide guidance on project development. 
+Members of the solar community are invited to join the [Stakeholder Committee](/stakeholdercommittee) to
+ provide guidance on project development.
 
 # Project Goals
 
-A common task in PV Operations and Maintenance (O&M) is to compare expected system performance with actual performance
-over a period of time. Currently, O&M service engineers must adapt their workflows to the available modeling tools which
-are primarily designed to predict future performance, rather than model past performance.
+Our project will build a performance modeling and analytics platform based on open-source, extensible,
+community-maintained code. The project will benefit to the solar community through two primary outcomes:
+-  Extending [pvlib-python](https://github.com/pvlib/pvlib-python) to easily model PV systems with greater detail.
+-  Deliver modeling capabilities through a web-based dashboard and an API.
+We work directly with industry stakeholders to validate user stories, derive use cases and analytic requirements,
+and test the platform.
 
-Our project will build a performance modeling and analytics platform based on open-source, extensible, community-maintained code. The project will benefit to the solar community through two primary outcomes:
--	Extending [pvlib-python](https://github.com/pvlib/pvlib-python) to easily model PV systems with greater detail.
--	Deliver modeling capabilities through a web-based dashboard and an API.
-We work directly with industry stakeholders to validate user stories, derive use cases and analytic requirements, and test the platform.
+# Project Background and Motivation
+
+A common task in PV Operations and Maintenance (O&M) is to compare actual performance over a period of time
+with modeled performance. Available asset management platforms that provide performance analytics are often
+far larger in scope than many O&M contractors need or can be tied to proprietary data acquisition systems.
+These platforms can be unaffordable for O&M providers with smaller portfolios or impractical for portfolios
+with diverse data systems. Consequently, O&M service engineers typically adapt their workflows to the available
+modeling tools which are primarily designed to predict future performance, rather than model past performance.
+
+# Project News
+
+We have published use cases to guide project development. The [use cases](/usecases) were compiled from input from O&M
+providers, asset owners and managers, and other PV professionals during a special session of SAMNA North America
+(online, April 6-7, 2020) and from members of the [Amicus Solar Cooperative](https://www.amicussolar.com/). Priority
+use cases include:
+-  Calculate performance from actual weather with user-selected performance models.
+-  Compare actual and modeled performance using performance ratios.
+-  Account for snow and soiling in performance models.
+
+In the coming months, the project team will build out capabilities in the [pvlib-python](https://github.com/pvlib/pvlib-python.git)
+modeling library that support the use cases. The project team will also draft a business plan to ensure that the
+modeling services are available to the industry after the project period has ended.
 
 # Funding
-See the [funding page](/funding) for more information on the project's funding from the U.S. Department of Energy's Solar Energy Technology Office.
+See the [funding page](/funding) for more information on the project's funding from the U.S. Department of Energy's
+ Solar Energy Technology Office.
 

usecases.md

@@ -32,6 +32,7 @@ Platform functional capabilities include:
 7. [Administer the platform](#administer).
 
 ## Definitions
+{: .anchor}
 
 **Predicted performance** refers to PV system energy output using the same modeling assumptions
  and weather data as were used in pre-operational performance projections.
@@ -49,8 +50,8 @@ user supplied modeling assumptions and actual weather data.
 #### 1.A. Calculate predicted performance {#uc1A}
 {: .anchor}
 
-**Use case narrative**: Using an SPI Performance Model [capability 5]](#uc5) with user-provided modeling assumptions,
-user input system metadata, and user supplied weather data [capability 6](#uc6), calculate system output.
+**Use case narrative**: Using an [SPI Performance Model] (#performancemodels) with user-provided modeling assumptions,
+user input system metadata, and [user-supplied weather data] (#uc6a), calculate system output.
 
 **Requirements**:
 
@@ -63,8 +64,8 @@ user input system metadata, and user supplied weather data [capability 6](#uc6),
 #### 1.B. Calculate expected performance {#uc1B}
 {: .anchor}
 
-**Use case narrative**: Using an SPI Performance Model [capability 5]](#uc5) with user-provided modeling assumptions,
-user input system metadata, user-uploaded actual weather data [capability 6](#uc6), and user-selected data quality checks (X.0),
+**Use case narrative**: Using an [SPI Performance Model](#performancemodels) with user-provided modeling assumptions,
+user input system metadata, [user-uploaded actual weather data] (#uc6a), and user-selected [data quality checks](#uc6b),
 calculate system output.
 
 **Requirements**:
@@ -190,7 +191,7 @@ can indicate sensor health and accuracy.
 - Platform provides metric values and visuals of comparison.
 - Platform provides a report for download.
 
-### 4. Perform portfolio analysis (stretch) {#uc4}
+### 4. Perform portfolio analysis (stretch) {#portfolioanalysis}
 {: .anchor}
 
 **Use case narrative**: In order for asset owners/managers and O&M providers to efficiently evaluate portfolios,
@@ -222,7 +223,9 @@ The SAM/CEC performance model will be a stretch goal.
 - The platform supplies functions to execute model chains.
 - Platform houses public databases of equipment and model parameters.
 
-### 6. Upload data {#uploaddata}
+## Upload and check data {#uploaddata}
+
+### 6.A Upload data {#uc6A}
 {: .anchor}
 
 **Narrative**: Users must be able to upload or otherwise specify system metadata, modeling assumptions,
@@ -240,7 +243,23 @@ model parameters and weather data.
 - Users can provide parameters for process models. Where available, the platform provides default values
   for process models.
 - The platform provides available, public databases of module and inverter model parameters.
-- Users can upload weather data.
+- Users can upload weather and power data.
+
+### 6.B Apply data quality checks (stretch) {#uc6B}
+{: .anchor}
+
+**Narrative**: The platform automatically checks user-uploaded weather and power data for quality issues,
+e.g., non-physical values, missing or incorrect timezone, and misaligned sensors, and provides a report
+to the user.
+
+**Requirements**:
+- Users can specify system metadata to include:
+  - location and orientation (tilt, azimuth, tracking)
+  - equipment type and number (inverters, modules)
+  - System layout (number of sub-arrays, string length, strings per inverter)
+- Users can select data quality checks to apply, and specify limits for data values.
+- Users can upload weather and power data.
+- The platform provides a report to the user on data quality issues.
 
 ### 7. Administer the platform {#administer}
 {: .anchor}