Challenge Summary
In this challenge we want to see your ideas to create a user friendly website application for Quartz Energy to share frac schedule information and identify offset fracs to their wells. This is a concepts challenge, so want to see your unique design ideas and executions.
Please read the specification details below and let us know if you have questions
Round 1
Initial Quartz Energy - Offset Operator Frac Schedule Project Application for these following features on Web screen size1). Login page
2). Dashboard
3). Upload Data
4). Company page
5). Calendar
Note: Feel free to submit more screens for early feedback
Round 2
Final Quartz Energy - Offset Operator Frac Schedule Project Application for these following features on Web screen size combined with Checkpoint Feedback1). Login page
2). Dashboard
3). Upload Data
4). Company page
5). Calendar
Business Background
Offset Hydraulic Frac identification and well preparation is an ongoing problem that we are facing in the basin. As Quartz Energy acreage offsets many different operators (both at surface and underground), the ability to share schedules and information is a key role for not only maintaining a high level of safety, but to reduce economic waste. For example, if one operator is performing a hydraulic fracture at a well location near an existing well, there is a chance that the pumping operation will negatively impact the other operators producing well (this takes place deep underground). It’s important for all parties to know when and where the other parties are performing hydraulic fracturing in an area to ensure they take the necessary & timely precautions. The seamless sharing of operational timelines and locations is paramount to keeping all parties safe and secure.
The current process involves manually reviewing a frac schedule (both in house and from offset operators) and determining if there is any wells within our window of preparation (currently 2500’ ). Once a well is identified, we need to balance the safety concerns of having this well prepped in time for a somewhat uncertain frac schedule along with the loss of production and lease terms. If this prep timeline is missed, we could have a safety incident such as a a blowout, have a well water out, or even lose the lease.
The goal of this project is to create a web based tool for operators to share frac schedules and locations with other operators. Currently we have a consortium of 15 operators that share their schedules via email roughly once a week to monthly. The email list changes monthly with people being added or taken off, which makes it tough to manage if you are getting all the schedules you need. Not only does the email list change, but so does each individual company’s frac schedule. With so many moving parts, manually sharing emails and aggregating schedules is unsustainable. These emails contain API # (unique public well identifier), well name, Frac start, Frac end, Bottom Hole Lat/Long, Surf Hole Lat/Long, and sometimes the underground formation name. In the current state, we go into our internal mapping tool or the State website and manually measure out the distances between our well locations and the offset operators locations to see if we need to prepare our wells. From this frac schedule, it us up to the individual companies to check in to see if offset fracs are on time or delayed and if the operator will impact any of their assets. This methodology is cumbersome and time consuming. A tool should be easily accessible, be able to quickly upload operator information and provide a visual and user adjustable display of areas and times where frac operations may cause operational hazards due to “frac hits” http://www.eagleford.training/2015/08/what-are-frac-hits/
Design Page Requirements
For this challenge we need you to design a webpage that operators can easily log on to and share upcoming frac information.
Some features we are looking for:
1). Login page
- This will be a simple login page
- Username and password required
2). Dashboard
- Design Dashboard with a map feature that shows wells that are color coded on fracs coming up and possible prep radius report
- User interface permitting selection of map region, date ranges and Operator filters
- We have a vision for the dashboard that we can put together a design if this advances
- Map feature should have surface and bottom location information. Something similar to http://wwwgisp.rrc.texas.gov/GISViewer2/
- We would like to see an overlay with the frac schedule data that has a line connecting surface and bottom hole location with a color referring to the length of time it is away. We would also like to have some filtering options.
- Map need able to pull data like this following information https://docs.google.com/spreadsheets/d/1UIslDzG2kj3H9YIqLfXaHAZ6gm_F98weTM-_xHjBbZs/edit?usp=sharing
- Map filters would be a frac time frame (next 30 days or what not), formation, and company
- Ideally the user data would be a layer atop of an existing map like the TRCC one that shows wells and we would connect the surface and btm hole locations via a colored line for when the frac is scheduled based on current date
3). Upload Data
- Ease of upload of data with the ability to automate as much as possible via publically available data
- We can supply which columns that we need to require in an unloadable template
- Fields options are:
-- Company Name,
-- Well Name,
-- Frac Start Date,
-- Frac End Date,
-- Surface Lat,
-- Surface Long,
-- Bottomhole Lat,
-- Bottomhole Long,
-- Target formation or TVD
4). Company page
- Company page with updated contact list
- Would like these easily updated by the users, a way to email the whole group, and a way to email an individual with a click of a button
- Sample data for Company Page:
-- Date of Last Submissions (Or days since): 3/15/2018
-- Company name: Use placeholder (Need able to switch to another company)
- Display table list with these content:
-- Contact Order
-- Role
-- Phone Number
-- Location
5). Calendar
- Calendar that compiles activity for all operators and individual access to each operator’s schedules
- We no need the month view, maybe more like a compilation of all the schedules lumped into one list and sorted via frac date.
- You can use sample data from this document: https://docs.google.com/spreadsheets/d/1rFpOfncdEeLi-ynrvz3Tm4_PgFPH9oV5X4elKIzPsKk/edit?usp=sharing
Design Submission Formats:
a). Screen Sizes:
- Desktop Screen Size: 1280px(w) × Height up to your design
b). Design theme, colors, typography.
- Design Branding: Up to designer
- Fonts: Up to designer
- Color palette: Up to designer
c). Submission Design Presentation
- As part of your submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- You MUST create Hotspot click flow on your MarvelApp
- If you need an MarvelApp Project, send email OR via challenge forum to this following email address: lunarkid@copilots.topcoder.com
- Important! Make sure to include a URL/Link to your MarvelApp within your submission notes
Target User
- Quartz Energy - Offset Operators
Judging Criteria
- How well you create Initial Quartz Energy - Offset Operator Frac Schedule Project Application
- Cleanliness of your graphics and design.
- User Experience.
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
- Submit JPG/PNG image files based on Challenge submission requirements stated above.
- MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Sketch and saved as editable layer
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors.
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.