BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to SunShot - Solar Land Solutions - Land Acquisition Wireframe Challenge. This challenge is focused on creating a wireframe for a responsive application that will allow solar developers to search through a list of properties/sites and find an appropriate site for development.

At the end of this challenge, we are looking to see intuitive and easy to use "wireframe concepts" that will help us design and build UI/UX in the next phase of this project!

This challenge is focused on "wireframe" output and results.
Be creative in your wireframes!

NOTE: We are awarding $100 for all best submissions at checkpoint!

Round 1

Submit your wireframe for checkpoint review..
1) Landing Page (not logged in)
2) Developer - Create Account

3) Login

4) Solar Developer Landing Page
5) Property/Site Details
6) Send Interest


Any comments about your wireframe, make sure all pages have correct flow!

Round 2

Final wireframe + any checkpoint feedback implemented!
1) Landing Page (not logged in)
2) Developer - Create Account
3) Login
4) Solar Developer Landing Page
5) Property/Site Details
6) Send Interest

7) Landowner - Create Account
8) List of Sites/Parcels
9) Add a New Site/Parcel


Any comments about your wireframe, make sure all pages have correct flow!


This project has two two types of users ‘Developers and Landowners’. For this challenge, we will be focusing more on the “Developers” - these user will have the ability to view list of possible properties/sites and be able to identify a site for development.

About Solar Land Solutions (SLS):
http://www.solarlandsolutions.com/
They provide contract land services for solar and wind energy projects and more. Experienced in energy development and land acquisition in 15 states and growing!

Wireframe Guidelines:
- Provide us with your interaction and click-path thoughts and suggestions
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when you create your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details below.
- Screen Sizes: We would like you to focus on Desktop and have the size as 1024px and height as required

Existing Problem:
- Land acquisition / site control is time consuming / costly
- Small Development Companies don’t have the time / manpower to look for find good sites and go through the land acquisition process.

Solution:
- Automate the current process and provide an easy way for developers to identify the site/properties for development.
- Looking for a zillow (http://www.zillow.com/ - Please DO NOT COPY, this is just for reference) like site that maps out opportunities for this type of development.

Required Pages:
Below are some of the features required in this application, but you are not limited to this, we are open to flows and suggestions on how things could work - so feel free to expand and suggest us what would be best for this application!!

A. Solar Developer Functionality:
1) Landing Page (not logged in):
- We need a simple landing page that explains the purpose of the site, what need to be included in this page?
- Looking forward to your thoughts on what information need to be put up on the page to make it useful, and to let the users have a better clarity on the purpose of the site. 
- This page should allow developers and landowners to create a new account with the site or if they are an existing user..we need to provide options for them to login to the site.

2) Developer - Create Account:
- The solar developer will first create an account on this web-site to access property lists of potential locations for solar developments.
- They will enter a unique login name and password, as well as details about the company.  
- At this time, it would also be optional for the developer to upload promotional material and lease documents for their account, so that when a site was selected, these were automatically sent to landowners.
- They will also agree to terms of service, which includes exclusivity when dealing with landowners listed on the site, as well as SLS’s (Solar Land Solutions) success fee for services. This should also have a disclaimer - SLS is not providing legal services, financial services, etc.

3) Login:
- Once the user has created an account with this site, they will be able to login.
- They need to enter the username and password
- What other elements/features are required in this page?
- On successfully signing in, they will see the “Solar Developer” landing page.

4) Solar Developer Landing Page:
- Once the user is logged in they see this page.
- This page shows list of properties and allows the to search through the list that matches the criteria entered (see below).
- Users will be able to search by these criterias:

  1. State

  2. Utility Area

  3. Size of Property - they can be represented as
    - Acreage (either in terms of mW capacity or acreage suitable for development - note: this may not equate to total acreage of property, as some acreage may be unusable due to wetlands, current buildings, etc).
    - mW capacity of the land (up to 40mW, etc)

  4. Size/quality of the interconnection (line-wise): Distribution level - 12kV to 22kV (or) Transmission level - 33 kV+

  5. Estimated cost of lease agreement (in MW/yr or in $/acre/yr)
    (should have a disclaimer stating that this is an estimate and actual final terms may be different)

- Would it be a good idea to provide a map based search, looking forward to your thoughts!
- Based on the chosen criteria, results are shown and user selects the potential site to view more details.
- We are looking for your thoughts on what else need to be shown in this page.


5) Property/Site Details:
- This page has the details about the site.
- The site is graded for suitability on a numeric (range-bound) scale, with sub-categories (also graded) detailed below.

Site details would include the below:
- ID (MN-XCEL-01) is an example of an ID. 
- Map of property with potential project area/lease area highlighted (other details can be obscured i.e. we need to blur road names and any identifying features to keep the location “secret”). 

- Details about MW potential or acreage available
- Type of Interconnection (estimated size of line and distance of line to project area)
- Utility territory
- Proximity to substation
- Zoning of property
- Tax assessment value of property
- Environmental details:

  1. Wetlands (shown on map - FWS .kmz)

  2. Floodplains (Y/N)

  3. Slope/Topography (%, qualification - rolling, flat, etc.)

  4. Endangered Species (Y/N)

  5. Historical/Archeological sites (Y/N)

  6. Superfund/former industrial locations (Y/N)

  7. Wooded vs. cleared (%)

Additional details:
- Oil and Gas leases/Mineral ownership
- Other existing easements (shown on map if possible)
- Conservation easements/other restrictions
- Potential shading issues (cell towers, radio towers)

Call to Action:
- If the solar developer feels that the site is suitable for development, then we need a way (perhaps a button?) in the page that allows solar developers to send their interest to the landowner.

6) Send Interest:
- Once the developer had reviewed and selected a site, they would then have the option in the property/site details page to upload her company’s lease form or letter of interest for review and execution by the landowner.
- As well as a note detailing the company’s plans for the property and any other info on the company, and automatic notification would also be sent to SLS and the landowner.

B. Landowner Functionality:
7) Landowner - Create Account:
- Landowners would create an account before they lease out their parcels to developers. 
- They will enter a unique login name and password and agree to have SLS promote these parcels to solar developers on their behalf, with a limited term of exclusivity (1-2 years). 

8) List of Sites/Parcels:
- Landowner will be able to view list of sites/parcels that they already entered.
- What details you think need to be shown here? 
- Probably they should be able to see list of interests that were received for a particular land? Do you think - we need to show some kind of notification?

9) Add a New Site/Parcel:
- We need below details to be entered in-order to create a new site
- Landowner inputs would include:

  1. Landowner name, address, phone #, email

  2. Information about utility servicing property and power lines in proximity to property

  3. Parcel address

  4. Tax ID #

  5. Zoning information

  6. Size of parcel and available land for development

  7. Desired lease rates for property (range bound – would be given options)

  8. Additional questions about suitability for development:

    1. Wetlands (shown on map - FWS .kmz)

    2. Floodplains (Y/N)

    3. Slope/Topography (%, qualification - rolling, flat, etc.)

    4. Endangered Species (Y/N)

    5. Historical/Archeological sites (Y/N)

    6. Superfund/former industrial locations (Y/N)

    7. Wooded vs. cleared (%)

    8. Mineral ownership (Y/N)

    9. Encumbrances on property (drop-down):

      1. Other

      2. Easements

      3. Mortgages

      4. Other leases

- Critical examining on the part of SLS (solar land solutions) will be required before the sites are available for review by solar developer.
- Once they finish entering all values, we see them under the list of sites/parcels with their status on whether they are approved or need any action to be taken will be indicated!

10) Additional Pages:
- If you feel there are any other pages that can be added to show the flow, please feel free to do so!

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Target Audience:
- Developers and Landowners

Judging Criteria:
Your submission will be judged on the following criteria:
- User Experience.
- Completeness and accuracy of the wireframe.
- How well your wireframes provide a consistent user flow.
- Any suggestions, interactions and user flow you recommend (provide any notes or comments for the client).

Submission & Source Files:
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2016 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30051609