Challenge Summary
Welcome to "WellLog - LAS Simple Parsing Tool Wireframes Challenge". In this challenge, we need your help to create a wireframe that able to define and provide clear interaction flow for our new application that will be used to parsing LAS file and display it to the user.
We need to see an intuitive and easy to use "wireframe concepts" that will let us design and build the final user interfaces on the next stage of this project. Think about what are the best UI/UX practices when creating this wireframe. Ask any questions in the forum, and have fun!
2. Dashboard Screen
3. Upload LAS File Screen
4. LAS Details Screen
5. LAS Analytics and Report Screen
- Note: Submit as much application features as you can for early review.
- Your wireframes need to be clickable
1. Login Screen
2. Dashboard Screen
3. Upload LAS File Screen
4. LAS Details Screen
5. LAS Analytics and Report Screen
6. Settings Screen
7. Help Screen
- Note: please address Checkpoint Feedback for your Final Round Submission
- Your wireframes need to be clickable
Background Overview
Our existing system that usually being used to open the LAS file has been commissioned out and our user right now needs to use notepad or any text editor to open the file. This is not a good approach because data in the LAS files are huge, so viewing the data or searching data using text editor quite hard and not effective and efficient at all.
Through this challenge, we want to initiate and create a new system that able to open the LAS file for our user, giving our user an ability to parsing and choose what kind of information that they want to see from the files, able to edit and update the data in the file, and also saving and export the updated files either to the same format (LAS) or other formats (CSV, XML, XLSX, etc).
Challenge Goal
Create a wireframe that engaging and well thought out experience for our new simple LAS parsing tool that allows people to view, edit, saving, and export LAS files.
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=625549
Flow and UX Consideration
- Focus on general navigation between all required screens and functionalities
- Easy and intuitive use for tech and non-tech users.
- The target device for this application is Web.
- We are looking for your ideas here!
Wireframe Expectations
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information
LAS Files Definition and Purpose
- In this particular case, the LAS format is used for the log data. Generally meta-data on the top and the log curve in the remaining file. We are interested in the meta-data in this project.
- File created in the standard LAS format, which was developed by the American Society for Photogrammetry and Remote Sensing (ASPRS); stores Light Detection and Ranging (LIDAR) data that is collected by optical remote sensors; used to exchange LIDAR data between data providers and data consumers.
- The LAS file format was developed in response to the growing number of proprietary LIDAR file formats. It also was designed to overcome some of the complexities in existing LIDAR data. LAS files are stored in a binary format.
Screen/Features Required for the App
Below are some of the screens that we suggest based on the above concept, feel free to expand on your concepts:
1. Login Screen
- The user needs to log in to be able to use the app
- Ordinary login field (username/password)
- Needs error scenario added as part of a failed login attempt
- Feature for reset and forgot password
2. Dashboard Screen
- The user will be redirected to this screen after successful login
- The user can view the application latest activity
- Ability/Features to upload new LAS file
- Show list of available LAS file in the app
- Ability to do a quick preview of any LAS file
- Engaging Main navigation
- This screen needs to provide high-level information to the user, the dashboard needs to show a summary of the processed LAS files. It would be kind of a list of last files with status and file location link. Now for each LAS file, we need to show these details in a table, with a button on the right-hand side to view/edit, for example:
-- Available UWI/API
-- Well name
-- Service company
-- Operator and a file name
-- Link to the LAS file (dropbox file, google drive file, temporary link, etc)
- What kind of information that we can put on this screen? Personalize the dashboard for the user, show us your idea!
3. Upload LAS File Screen
- The user should be able to upload new LAS file to the app via this link
- Create this screen as a new screen? Or popup/modal window? Your call!
- Ability to upload single or multiple LAS file at one time
- Since the LAS file have quite a huge size, show a percentage of upload progress
- Fails and Success upload status
- Ability to cancel the upload process
- Ability to hide the upload progress so the user can continue and do any activity in The user
- User should be able to preview the LAS file content (read only/quick preview) once user finish uploading the LAS files to make sure it is the correct files.
4. LAS Details Screen
- In this screen, the user will be able to see the full content of LAS file.
- User can go to this screen via the dashboard, or after user finish uploading the LAS file.
- User will only able to open one LAS files at one time.
- Ability to manage and set which content that needs to be displayed (parsing feature) - what header field that needs to be selected and appear, set quantity of content/limitation per page, etc.
- There are a lot of information available in the LAS files, the app needs to parsing the content based on the category and heading from the LAS files and show the following informations (in some files, there might be some of the below informations not available):
-- Version Information
-- Well Information Block
-- Curve Information Block
-- Parameter Information Block
-- Other Information
-- Details Content (all data content)
- There is a spreadsheet that can help you to show what attributes needed that needs to be parsed. There are some high level rules associated to the parsing on that excel, for example (qe_log_classification_2.xlsx):
-- Keys to tie into TDM database
-- Detailed Screen for the file name
-- Each column from the attribute spreadsheet that we want to capture - predict operator that is missing, log type
-- Everything except for Column C
- User will be able to edit the data inside LAS file in this screen
- Ability to save the data
- Ability to export the LAS files into other formats (CSV, XLS, etc)
5. LAS Analytics and Report Screen
- In this screen, the user can analyze the LAS file and User activity.
- Trend of LAS files mined over a period of time
- Provide a simple set of reports so users can see what they done over the past week or month or an arbitrary time period
- Trend over time for files analyzed, may be the count of metadata extracted from each file. Number of parsing jobs and it's success/failure.
- Over a period of time we need Machine Learning, so we want to provide analytics to help that process.
- Let us know your other ideas for this screen/features!
6. Settings Screen
- Ability to set user profile and privileges
- Set LAS files configuration
- What else we can put in here? Show us your idea!
7. Help Screen
- Documentation
- FAQ
- Contact Support
Documentation
- LAS File example (Attached on the challenge attachment, check top right sidebar after register to the challenge!)
New to axure RP, get started right-away!!
- Here are some quick tutorials to help you get started http://www.axure.com/support
Screen Size
- Desktop: 1366px(w) & height up to your design
Target Audience
- Internal Employees
Judging Criteria
- User experience and information architecture
- Expanding upon and creating unique features for the provided concepts
- Visual-driven, clear, concise, and meaningful data display
- Capture all the required fields on every page
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- Wireframes should be clickable and can be opened in all major browser without issue.
- IMPORTANT! Make sure all the content is listed and the pages are linked together to show page flow.
- Keep your source files out from this submission folder.
Source Files
- All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file
- You can built the wireframes using Plain HTML/CSS/JS or you can generate from the Axure application. Other option is using Sketch with Black/White theme (needs to be clickable).
Final Fixes
As part of the final fixes phase, you may be asked to modify content or user click paths.
We need to see an intuitive and easy to use "wireframe concepts" that will let us design and build the final user interfaces on the next stage of this project. Think about what are the best UI/UX practices when creating this wireframe. Ask any questions in the forum, and have fun!
Round 1
Initial Wireframe for these following feature:2. Dashboard Screen
3. Upload LAS File Screen
4. LAS Details Screen
5. LAS Analytics and Report Screen
- Note: Submit as much application features as you can for early review.
- Your wireframes need to be clickable
Round 2
Final Wireframe for these following features:1. Login Screen
2. Dashboard Screen
3. Upload LAS File Screen
4. LAS Details Screen
5. LAS Analytics and Report Screen
6. Settings Screen
7. Help Screen
- Note: please address Checkpoint Feedback for your Final Round Submission
- Your wireframes need to be clickable
Background Overview
Our existing system that usually being used to open the LAS file has been commissioned out and our user right now needs to use notepad or any text editor to open the file. This is not a good approach because data in the LAS files are huge, so viewing the data or searching data using text editor quite hard and not effective and efficient at all.
Through this challenge, we want to initiate and create a new system that able to open the LAS file for our user, giving our user an ability to parsing and choose what kind of information that they want to see from the files, able to edit and update the data in the file, and also saving and export the updated files either to the same format (LAS) or other formats (CSV, XML, XLSX, etc).
Challenge Goal
Create a wireframe that engaging and well thought out experience for our new simple LAS parsing tool that allows people to view, edit, saving, and export LAS files.
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=625549
Flow and UX Consideration
- Focus on general navigation between all required screens and functionalities
- Easy and intuitive use for tech and non-tech users.
- The target device for this application is Web.
- We are looking for your ideas here!
Wireframe Expectations
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information
LAS Files Definition and Purpose
- In this particular case, the LAS format is used for the log data. Generally meta-data on the top and the log curve in the remaining file. We are interested in the meta-data in this project.
- File created in the standard LAS format, which was developed by the American Society for Photogrammetry and Remote Sensing (ASPRS); stores Light Detection and Ranging (LIDAR) data that is collected by optical remote sensors; used to exchange LIDAR data between data providers and data consumers.
- The LAS file format was developed in response to the growing number of proprietary LIDAR file formats. It also was designed to overcome some of the complexities in existing LIDAR data. LAS files are stored in a binary format.
Screen/Features Required for the App
Below are some of the screens that we suggest based on the above concept, feel free to expand on your concepts:
1. Login Screen
- The user needs to log in to be able to use the app
- Ordinary login field (username/password)
- Needs error scenario added as part of a failed login attempt
- Feature for reset and forgot password
2. Dashboard Screen
- The user will be redirected to this screen after successful login
- The user can view the application latest activity
- Ability/Features to upload new LAS file
- Show list of available LAS file in the app
- Ability to do a quick preview of any LAS file
- Engaging Main navigation
- This screen needs to provide high-level information to the user, the dashboard needs to show a summary of the processed LAS files. It would be kind of a list of last files with status and file location link. Now for each LAS file, we need to show these details in a table, with a button on the right-hand side to view/edit, for example:
-- Available UWI/API
-- Well name
-- Service company
-- Operator and a file name
-- Link to the LAS file (dropbox file, google drive file, temporary link, etc)
- What kind of information that we can put on this screen? Personalize the dashboard for the user, show us your idea!
3. Upload LAS File Screen
- The user should be able to upload new LAS file to the app via this link
- Create this screen as a new screen? Or popup/modal window? Your call!
- Ability to upload single or multiple LAS file at one time
- Since the LAS file have quite a huge size, show a percentage of upload progress
- Fails and Success upload status
- Ability to cancel the upload process
- Ability to hide the upload progress so the user can continue and do any activity in The user
- User should be able to preview the LAS file content (read only/quick preview) once user finish uploading the LAS files to make sure it is the correct files.
4. LAS Details Screen
- In this screen, the user will be able to see the full content of LAS file.
- User can go to this screen via the dashboard, or after user finish uploading the LAS file.
- User will only able to open one LAS files at one time.
- Ability to manage and set which content that needs to be displayed (parsing feature) - what header field that needs to be selected and appear, set quantity of content/limitation per page, etc.
- There are a lot of information available in the LAS files, the app needs to parsing the content based on the category and heading from the LAS files and show the following informations (in some files, there might be some of the below informations not available):
-- Version Information
-- Well Information Block
-- Curve Information Block
-- Parameter Information Block
-- Other Information
-- Details Content (all data content)
- There is a spreadsheet that can help you to show what attributes needed that needs to be parsed. There are some high level rules associated to the parsing on that excel, for example (qe_log_classification_2.xlsx):
-- Keys to tie into TDM database
-- Detailed Screen for the file name
-- Each column from the attribute spreadsheet that we want to capture - predict operator that is missing, log type
-- Everything except for Column C
- User will be able to edit the data inside LAS file in this screen
- Ability to save the data
- Ability to export the LAS files into other formats (CSV, XLS, etc)
5. LAS Analytics and Report Screen
- In this screen, the user can analyze the LAS file and User activity.
- Trend of LAS files mined over a period of time
- Provide a simple set of reports so users can see what they done over the past week or month or an arbitrary time period
- Trend over time for files analyzed, may be the count of metadata extracted from each file. Number of parsing jobs and it's success/failure.
- Over a period of time we need Machine Learning, so we want to provide analytics to help that process.
- Let us know your other ideas for this screen/features!
6. Settings Screen
- Ability to set user profile and privileges
- Set LAS files configuration
- What else we can put in here? Show us your idea!
7. Help Screen
- Documentation
- FAQ
- Contact Support
Documentation
- LAS File example (Attached on the challenge attachment, check top right sidebar after register to the challenge!)
New to axure RP, get started right-away!!
- Here are some quick tutorials to help you get started http://www.axure.com/support
Screen Size
- Desktop: 1366px(w) & height up to your design
Target Audience
- Internal Employees
Judging Criteria
- User experience and information architecture
- Expanding upon and creating unique features for the provided concepts
- Visual-driven, clear, concise, and meaningful data display
- Capture all the required fields on every page
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- Wireframes should be clickable and can be opened in all major browser without issue.
- IMPORTANT! Make sure all the content is listed and the pages are linked together to show page flow.
- Keep your source files out from this submission folder.
Source Files
- All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file
- You can built the wireframes using Plain HTML/CSS/JS or you can generate from the Axure application. Other option is using Sketch with Black/White theme (needs to be clickable).
Final Fixes
As part of the final fixes phase, you may be asked to modify content or user click paths.
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.