Challenge Summary
Welcome to the GE AWS Cloud Control Design Concepts Challenge
The GE AWS Cloud Control Portal is a self service portal that empowers GE’s clients to schedule, monitor, alter and configure their servers and environments on their own. The goal is to allow the server, application and environment owners to manage their servers based on their unique needs and schedules.
In this challenge we are looking for some initial design concepts on what the user should see and experience when controlling the AWS. We also want to focus on what items should have priority to the user. Read the design problem carefully let us know what you think via your design ideas.
Good luck and we look forward to your design concepts!
Round 1
Submit initial design concepts for client feedback
- "GE Cloud Control" pages for these screens:
1). Login
2). Dashboard
3). Application Detail
4). Environment Detail
Notes.jpg: Any comments about your design for the Client
Round 2
Final designs with checkpoint feedback included.
- "GE Cloud Control" pages for these screens:
1). Login
2). Dashboard
3). Application Detail
4). Environment Detail
- Any Checkpoint feedback from Round 1
Notes.jpg: Any comments about your design for the Client
The goal of GE Cloud Control is to create a web portal to control GE servers in Amazon Web Services. For this challenge you need address solutions for the problem we face.
Functionality and Design Requirements:
- GE has a large infrastructure of servers running in AWS, but they don't want to provide people direct access to all of AWS. AWS is quite complicated and there are many different things you can do. A user at GE might be in charge of a certain application with environments and numerous servers within that.
- Currently, users need to email GE support, who will log-in and reset the server for them. We want to empower the application owners to make these decisions and schedule items based on their unique needs and production schedules.
- Another critical piece of functionality is users want to be able to schedule time for servers to stop or to start automatically. This could be on an environment level (that affects numerous servers) or on an individual server level. The user MUST have that option.
- The schedule process needs to be extremely intuitive and maximize configurability to allow the user to make schedules effectively.
- GE wants the design to be extensible and flexible, meaning if they need to add more functionality, the design won't get too cluttered. For example, GE has created numerous automations for their customers to use to handle server configurations, maintenance and updates. The user should have the ability to add these items to their servers/ environments. There will also be additional widget/ modules that are needed in the future to View/take snapshots, schedule/ control upgrades, view logs, initiate/ schedule patches, view utilization, etc.
Screen Requirements:
1). Login
- The user needs to sign in to view GE Cloud Control page:
- Display these following fields in Login page
-- Username.
-- Password.
-- Login Button.
-- Remember Me Checkbox.
-- Forgot My Password Link.
- Research and design how Login page should created
- You might also need display the GE Logo and Application Name on this screen
2). Dashboard
- Dashboard page will serve as the first impression of GE Cloud Control for the users. The dashboard page is the most critical and requires the most creativity. We are open to any new ideas! Any design suggestions?
- Think about the best user flow for this and how the design will be able to handle viewing 900+ individual servers.
- Dashboard will display huge list of servers, think about the best way to view this information. Are their multiple “views”, list vs. grid, etc.
- Users view servers based on “Applications” with “Environments” inside of that.
- Applications = High level view of a group of servers
- Environments = Are within an application and are use for specific areas of an application. For example: DEV, QA or Production environments. There could be dozens of different servers within an environment
- Items to consider to help a user manage/ view the dashboard:
-- Grouped by “Applications”
-- Filters
-- Search
-- Favorites
- The user should be able to see the name of the Application, it’s general status (off, on, partial on/off), maybe a brief schedule or when it’s next status change is (server will be stopped in 5hrs, on Jan. 12, etc.)
- Think about what would be the most useful information to see on the dashboard WITHOUT making it overwhelming. The user needs to be able to find and see Applications/servers fast and efficiently.
- Once a user clicks on an Application name they are taken to the “Application Detail Screen”.
3) Application Detail Screen
- The Application detail screen should show:
-- Application Name
-- Environments within the Application (DEV, QA, Production, etc.) User will need the ability to click into these Environments
-- Number of servers within each Environment (This can be secondary/ smaller information)
4) Environment Detail Screen
- Once a user Clicks on an environment from the Application Detail screen they are taken to the environment detail screen, where they can make additional changes and schedules.
- Information that should be displayed on the Environment Detail screen:
-- Name of Environment
-- Names of servers within that Environment (ability to click into an individual server)
-- Actionable widgets/ modules
- Widgets or modules to include (All actions should have the ability to apply to one of more environments; or exclude an environment):
-- Start, Stop or Restart the entire Environment OR individual servers
-- Schedule downtime of the entire Environment OR individual servers. The entire environment schedule could be different than individual servers.
-- Build a schedule based on a typical week. Calendar view with ability to edit by day
-- Patch now or schedule patch
-- Disk Size - User sets new disk size and schedule
-- Downsize opt out - Opt out of this month’s automatic downsize
-- Upgrade opt out - Opt out of Gen upgrade
Submission Requirements:
1. Screen Size
- This application will be developed as Responsive application. Make sure your submission possible to expand with Responsive Design Theme.
- For this challenge, you only need to submit your submission on Desktop Standard size 1024px width and height up to your design
- Use shape based format on every graphic you created on your storyboard design to make sure everything remains sharp when resized!
2. Design Direction
Branding, fonts and design inspiration can be found on the Design Direction Site
Notes:
- Recommend to us how the colors should be used (combination) and we will provide feedback at the Checkpoint Review.
- Think about "Professional" theme when you are designing for this application.
- Keep it simple!
IMPORTANT
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.
Target User
- GE Internal Employees
- Managers of Applications and/or Development environments within GE
Judging Criteria
- How well you plan the user experience and capture your ideas visually.
- Cleanliness of your graphics and design.
- Mobile designs and experiences
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
All Requested challenge Submission Requirements stated above.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD.
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.