Challenge Summary
Welcome to "Rollout Management Tool Design Challenge". In this challenge, we are looking for your help to create the best possible design for our Rollout Management Tool which will be used by System Engineer to track desktop migration activities at the customer end. This application needs to be simple, easy to use, offer a great visualization, and at the same time it needs to look professional.
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
02) Onboard Screens (Upload and Validate Raw Data)
03) Dashboard Screen
04) Data Detail Screens
05) Self Service Screen
06) App Readiness Screen
- As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
01) Login Screen
02) Onboard Screens (Upload and Validate Raw Data)
03) Dashboard Screen
04) Data Detail Screens
05) Self Service Screen
06) App Readiness Screen
07) Report Screen
08) Capacity Planning Screen
- As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Project Description
We are in need to build a Tool to help track desktop migration activities at the customer end. The tool will help in quick view of user and asset (desktop data including OS, applications and hardware, user, departments), rationalize and report asset categories, validate user information and help in scheduling migration activities through automated emails. The tool will help in scaling and optimizing desktop migration activities through less effort and time.
The client is a company that offers a service for migration related to computer, system app, and data for the customer. Client System Engineers will visit the customer location for enterprise migration-related activities (ex: migrate desktops of ABC corporation from windows-7 to windows-10 and ABC corporation has around 100 employees along with 3rd party app like chat tools (skype or slack), administrative tools (office365, etc), or their internal apps)
Challenge Goal
Build a great design look and feel for our Deployment Management Tool to track the migration activities of an enterprise
Design Consideration
- Simple, Clean, Professional, Corporate/Enterprise look and feel
- Simplicity to find and add necessary information
- Needs to offer a great focus to the user
- Best Practice for Web-Based App (Desktop)
- Easy to understand flow from page to page
- Intuitive for the user; should never be left asking "what do I do next?"
- Easy viewing for pages that may be over overcrowded with information (eg. when hovering over an item will enlarge for easy viewing or similar)
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=667076
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
01) Login Screen
- System Engineer will visit the customer location onsite and install the Rollout application into customer infrastructure so they can access it via customer network (installed in customer server/cloud)
- Once it gets installed, System Engineer will be able to open the app via any customer computer and log in to the tool using their credential
- Provide ordinary login form (username and password)
- No need for registration or forgot password feature
- Still need to have error login related scenario for the app
02) Onboard Screens (Upload and Validate Raw Data)
- This action only need to do one time and counted as a setup before the migration process started (onboarding process)
- Needs two main interactions in this screen, uploading the CSV file and validate the data:
Upload Data
- Data can be imported directly from the below tools: SCCM, AD, HR Database
- Option to be provided to do offline data upload via CSV
- The CSV file will contain data related to customers specific information (users, department, application, and type of computer that will be migrated in the customer company)
- System engineer can upload the CSV file into the Rollout tool (see https://sn4wst.axshare.com/#g=1&p=csv_import)
- It's up to you to define the interaction for uploading process, whether you want to upload each data (users, application, department, and computers) as a single CSV separated by tab, or each one has their own CSV file, or bulk upload, etc.
- Following data needs to be imported to the tool:
-- User Data-Name, Email, Manager Name
-- HR Data- Department, Business Unit, Country, City, Floor, Address
-- Hardware Data- Computer Name, MAC Address, IP Address, Domain, Memory, Disk Size, Process, Serial Number, Hardware Type, Model Number, Asset Number
-- Software Data- Application Name, Version, Manufacturer, Build No, Rationalization Status, Packaging Status
-- User Vs Computer Vs Software Mapping
-- See our "Data Fields 2602.xlsx" for the fields needed
Validate Data
- Once the data is uploaded successfully, System engineer will continue and validate the raw data (see https://sn4wst.axshare.com/#g=1&p=onboard_data)
- To validate the data, System Engineer will need to browse/search the available raw data which has been uploaded to the tool earlier
- System engineer can choose which data they want to see (users/application/computers/department)
- System engineer will be able to set some filter to make the data search results become more specific, some filter can be based on: User Name, Full Name (display name - e.g. Joanne Gall), Computer Name, Application Package Name, Group Name, IP Address, MAC Address, etc
- Once the filter ready and user click browse, the data will appear in the screen
- In each data, the user can select the rows (via checkbox)
- If the migration will be done in several phases, the user can create a 'project', for example: company have 100 users, project 1 will be 20 users migration, project 2 will be 30 users migration, and so on
- Once the user finish selected all valid data for the migration, they can click 'publish' button to store the data into the database, these data will be used as the target for the migration
03) Dashboard Screen
- Once the onboarding process finish or whenever the System Engineer open the application, they will be redirected to the dashboard screen (see https://sn4wst.axshare.com/#g=1&p=dashboards)
- Needs to have main navigation where System Engineers can navigate to other features of the app
- In this screen, we need your creativity to create a great dashboard design that efficient and effective for the system engineer when doing the migration process
- We need to provide table of information here, started with a list/table of application/users/computer/department related to the migration
- Each content on the list/table will be clickable and can bring the System engineer to "Data Detail Screens" that will show information depends on which data they clicked on
- It also can show the status of migration progress to completeness, migration appointment/schedule status with the self-service users, etc (feel free to be creative here!)
04) Data Detail Screens
- Depends on what System Engineer click in the dashboard, the Data Detail Screens will show different information:
-- If System Engineer click on Application table/list from the dashboard, it will show details of the application information (see Data Fields 2602.xlsx for the fields), along with details of what user and computer that use the application (see https://sn4wst.axshare.com/app_details.html)
-- If System Engineer click on User table/list from the dashboard, it will show details of the User information (see Data Fields 2602.xlsx for the fields), along with details of all applications and computer that the user currently use (see https://sn4wst.axshare.com/user_details.html)
-- If System Engineer click on Department table/list from the dashboard, it will show details of the department information (department name, how many employees, office location, etc), along with all the employees in that department, computer, and applications
-- If System Engineer click on Computer table/list from the dashboard, it will show details of the computer information (see Data Fields 2602.xlsx for the fields), along with details of the user and what application that should be available in this computer (https://sn4wst.axshare.com/computer_details.html), there will be a button here too where System Engineer can update the 'Migration Status' for the computer.
- If System Engineer clicks the 'Migration Status', it will open a form where they can and enters details regarding the daily progress/activities performed and relevant details. This data is also used in reporting:
-- Two types of migration: Replace and Refresh
---- If Replace, both column at the bottom (current H/W model and New H/W model needs to appear)
---- If Refresh, only column Current H/W model needs to be appear
-- Ability to Set the migration status
-- Set the migration actual date
-- Replacement device
-- Migration Data and the size
-- Column information about the current H/W model and it's specific data
-- Column information about the new H/W model and it's specific data
05) Self Service Screen
- Company User/Self Service User will get an email from the RollOut app that informs them about the migration. There will be a link provided in the email, upon click by recipient a web page will open on the browser and they will be redirected to this screen (no login required, see https://sn4wst.axshare.com/#g=1&p=selfservice)
- Self Service Users will need to fill the form and upon submit, data is saved to the DB
- The Migration Date is an appointment date that the user can select, there will be an empty slot in the calendar date that user can select, also some full schedule date that user no longer able to select (System Engineer work is full on that date)
- By doing this, the Self Service Users actually doing an appointment with the System Engineer about when the migration should be done for them and if they have some specific request about the migration (for ex: they cannot leave the computer, they need a specific tweak on the computer, etc)
06) App Readiness Screen
- In this screen, System Engineer or Administrator can update/modify the application if it turns out the application has some incompatibility issue with the computer, OS, user, etc. (https://sn4wst.axshare.com/#g=1&p=app_readiness)
- This needs manual categorization of various applications from management interface then applying the same categorization to rationalize the complete record of user asset
- The application list will be taken from the database (data that being imported/uploaded in the onboard process), so no new application can be added to the app (read-only)
- If the application is somehow not compatible anymore, System Engineer can provide some information about what action needs to be done (whether to update the app to a higher version, change it completely, etc)
- For each current status, the RAG light will have different colors:
-- Production Ready - Green
-- In UAT - Amber
-- In QA - Amber
-- In Packaging - Red
-- On Hold - Red
-- Manual - Brown
-- Not Started - Red
-- Not Compatible - Red (Dark)
-- Uncategorized - Purple
07) Report Screen
- System Engineer can fetch various reports on pages
- Example of reports:
-- Number of migrations done on a particular day
-- Total migrations progress summary
-- Etc
- There will be a max of 3 reports
- See 'Rollout Management Tool Requirements 2602.pptx' page 19, 20, 21 for example of reports
- Ability to export the report to CSV, PDF, etc
08) Capacity Planning Screen
- Check "Rollout Management Tool Requirements 2602.pptx" page 22
- Usually, a team of System Engineers visits the customer place onsite for this activity
- Team size can vary (ex: 1 to 10 people) and in this scenario, each engineer can certain bandwidth to work on the migration (ex: 1 system engineer can do 5 desktop migrations a day and this should be configurable, with this a team of 5 people can do 25 migrations in a day)
- Before Self Service User fill the form (check requirement "05) Self Service Screen"), System Engineers needs to choose a convenient time slot by clicking on day (calendar popup) calendar popup shows dates with highlighted in green (for available slots)
- Provide option to set the day-wise capacity to manage the resourcing for a rollout Group
- Should be an option to select different numbers for different dates
- Also, look at the possibility of setting up capacity for a timeslot in a day in the next version
Important:
- Keep things consistent. This means all graphics styles should work together
- All of the graphics should have a similar feel and general aesthetic appearance
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to fajar.mln@gmail.com (Challenge Copilot)
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comments this link while you upload).
Branding Guidelines
- Think of professional, clean branding for the application
- Open to designers
Documentation (Available in Challenge Forum)
- Rollout Management Tool Requirements 2602.pptx
- Very Basic Wireframes available online - https://sn4wst.axshare.com/#g=1&p=login
- Data Fields 2602.xlsx
Target Devices
- Web-Based Application
- Desktop: minimum 1366px Width with Height adjusted accordingly
Target Audiences
- System Engineer
- Administrator
- Self Service Users
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into solving the problem
- The overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
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 Adobe Photoshop, XD or 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.
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
Round 1
Submit your initial design for a Checkpoint Feedback02) Onboard Screens (Upload and Validate Raw Data)
03) Dashboard Screen
04) Data Detail Screens
05) Self Service Screen
06) App Readiness Screen
- As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Round 2
Submit your Final Design plus Checkpoint Updates01) Login Screen
02) Onboard Screens (Upload and Validate Raw Data)
03) Dashboard Screen
04) Data Detail Screens
05) Self Service Screen
06) App Readiness Screen
07) Report Screen
08) Capacity Planning Screen
- As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Project Description
We are in need to build a Tool to help track desktop migration activities at the customer end. The tool will help in quick view of user and asset (desktop data including OS, applications and hardware, user, departments), rationalize and report asset categories, validate user information and help in scheduling migration activities through automated emails. The tool will help in scaling and optimizing desktop migration activities through less effort and time.
The client is a company that offers a service for migration related to computer, system app, and data for the customer. Client System Engineers will visit the customer location for enterprise migration-related activities (ex: migrate desktops of ABC corporation from windows-7 to windows-10 and ABC corporation has around 100 employees along with 3rd party app like chat tools (skype or slack), administrative tools (office365, etc), or their internal apps)
Challenge Goal
Build a great design look and feel for our Deployment Management Tool to track the migration activities of an enterprise
Design Consideration
- Simple, Clean, Professional, Corporate/Enterprise look and feel
- Simplicity to find and add necessary information
- Needs to offer a great focus to the user
- Best Practice for Web-Based App (Desktop)
- Easy to understand flow from page to page
- Intuitive for the user; should never be left asking "what do I do next?"
- Easy viewing for pages that may be over overcrowded with information (eg. when hovering over an item will enlarge for easy viewing or similar)
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=667076
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
01) Login Screen
- System Engineer will visit the customer location onsite and install the Rollout application into customer infrastructure so they can access it via customer network (installed in customer server/cloud)
- Once it gets installed, System Engineer will be able to open the app via any customer computer and log in to the tool using their credential
- Provide ordinary login form (username and password)
- No need for registration or forgot password feature
- Still need to have error login related scenario for the app
02) Onboard Screens (Upload and Validate Raw Data)
- This action only need to do one time and counted as a setup before the migration process started (onboarding process)
- Needs two main interactions in this screen, uploading the CSV file and validate the data:
Upload Data
- Data can be imported directly from the below tools: SCCM, AD, HR Database
- Option to be provided to do offline data upload via CSV
- The CSV file will contain data related to customers specific information (users, department, application, and type of computer that will be migrated in the customer company)
- System engineer can upload the CSV file into the Rollout tool (see https://sn4wst.axshare.com/#g=1&p=csv_import)
- It's up to you to define the interaction for uploading process, whether you want to upload each data (users, application, department, and computers) as a single CSV separated by tab, or each one has their own CSV file, or bulk upload, etc.
- Following data needs to be imported to the tool:
-- User Data-Name, Email, Manager Name
-- HR Data- Department, Business Unit, Country, City, Floor, Address
-- Hardware Data- Computer Name, MAC Address, IP Address, Domain, Memory, Disk Size, Process, Serial Number, Hardware Type, Model Number, Asset Number
-- Software Data- Application Name, Version, Manufacturer, Build No, Rationalization Status, Packaging Status
-- User Vs Computer Vs Software Mapping
-- See our "Data Fields 2602.xlsx" for the fields needed
Validate Data
- Once the data is uploaded successfully, System engineer will continue and validate the raw data (see https://sn4wst.axshare.com/#g=1&p=onboard_data)
- To validate the data, System Engineer will need to browse/search the available raw data which has been uploaded to the tool earlier
- System engineer can choose which data they want to see (users/application/computers/department)
- System engineer will be able to set some filter to make the data search results become more specific, some filter can be based on: User Name, Full Name (display name - e.g. Joanne Gall), Computer Name, Application Package Name, Group Name, IP Address, MAC Address, etc
- Once the filter ready and user click browse, the data will appear in the screen
- In each data, the user can select the rows (via checkbox)
- If the migration will be done in several phases, the user can create a 'project', for example: company have 100 users, project 1 will be 20 users migration, project 2 will be 30 users migration, and so on
- Once the user finish selected all valid data for the migration, they can click 'publish' button to store the data into the database, these data will be used as the target for the migration
03) Dashboard Screen
- Once the onboarding process finish or whenever the System Engineer open the application, they will be redirected to the dashboard screen (see https://sn4wst.axshare.com/#g=1&p=dashboards)
- Needs to have main navigation where System Engineers can navigate to other features of the app
- In this screen, we need your creativity to create a great dashboard design that efficient and effective for the system engineer when doing the migration process
- We need to provide table of information here, started with a list/table of application/users/computer/department related to the migration
- Each content on the list/table will be clickable and can bring the System engineer to "Data Detail Screens" that will show information depends on which data they clicked on
- It also can show the status of migration progress to completeness, migration appointment/schedule status with the self-service users, etc (feel free to be creative here!)
04) Data Detail Screens
- Depends on what System Engineer click in the dashboard, the Data Detail Screens will show different information:
-- If System Engineer click on Application table/list from the dashboard, it will show details of the application information (see Data Fields 2602.xlsx for the fields), along with details of what user and computer that use the application (see https://sn4wst.axshare.com/app_details.html)
-- If System Engineer click on User table/list from the dashboard, it will show details of the User information (see Data Fields 2602.xlsx for the fields), along with details of all applications and computer that the user currently use (see https://sn4wst.axshare.com/user_details.html)
-- If System Engineer click on Department table/list from the dashboard, it will show details of the department information (department name, how many employees, office location, etc), along with all the employees in that department, computer, and applications
-- If System Engineer click on Computer table/list from the dashboard, it will show details of the computer information (see Data Fields 2602.xlsx for the fields), along with details of the user and what application that should be available in this computer (https://sn4wst.axshare.com/computer_details.html), there will be a button here too where System Engineer can update the 'Migration Status' for the computer.
- If System Engineer clicks the 'Migration Status', it will open a form where they can and enters details regarding the daily progress/activities performed and relevant details. This data is also used in reporting:
-- Two types of migration: Replace and Refresh
---- If Replace, both column at the bottom (current H/W model and New H/W model needs to appear)
---- If Refresh, only column Current H/W model needs to be appear
-- Ability to Set the migration status
-- Set the migration actual date
-- Replacement device
-- Migration Data and the size
-- Column information about the current H/W model and it's specific data
-- Column information about the new H/W model and it's specific data
05) Self Service Screen
- Company User/Self Service User will get an email from the RollOut app that informs them about the migration. There will be a link provided in the email, upon click by recipient a web page will open on the browser and they will be redirected to this screen (no login required, see https://sn4wst.axshare.com/#g=1&p=selfservice)
- Self Service Users will need to fill the form and upon submit, data is saved to the DB
- The Migration Date is an appointment date that the user can select, there will be an empty slot in the calendar date that user can select, also some full schedule date that user no longer able to select (System Engineer work is full on that date)
- By doing this, the Self Service Users actually doing an appointment with the System Engineer about when the migration should be done for them and if they have some specific request about the migration (for ex: they cannot leave the computer, they need a specific tweak on the computer, etc)
06) App Readiness Screen
- In this screen, System Engineer or Administrator can update/modify the application if it turns out the application has some incompatibility issue with the computer, OS, user, etc. (https://sn4wst.axshare.com/#g=1&p=app_readiness)
- This needs manual categorization of various applications from management interface then applying the same categorization to rationalize the complete record of user asset
- The application list will be taken from the database (data that being imported/uploaded in the onboard process), so no new application can be added to the app (read-only)
- If the application is somehow not compatible anymore, System Engineer can provide some information about what action needs to be done (whether to update the app to a higher version, change it completely, etc)
- For each current status, the RAG light will have different colors:
-- Production Ready - Green
-- In UAT - Amber
-- In QA - Amber
-- In Packaging - Red
-- On Hold - Red
-- Manual - Brown
-- Not Started - Red
-- Not Compatible - Red (Dark)
-- Uncategorized - Purple
07) Report Screen
- System Engineer can fetch various reports on pages
- Example of reports:
-- Number of migrations done on a particular day
-- Total migrations progress summary
-- Etc
- There will be a max of 3 reports
- See 'Rollout Management Tool Requirements 2602.pptx' page 19, 20, 21 for example of reports
- Ability to export the report to CSV, PDF, etc
08) Capacity Planning Screen
- Check "Rollout Management Tool Requirements 2602.pptx" page 22
- Usually, a team of System Engineers visits the customer place onsite for this activity
- Team size can vary (ex: 1 to 10 people) and in this scenario, each engineer can certain bandwidth to work on the migration (ex: 1 system engineer can do 5 desktop migrations a day and this should be configurable, with this a team of 5 people can do 25 migrations in a day)
- Before Self Service User fill the form (check requirement "05) Self Service Screen"), System Engineers needs to choose a convenient time slot by clicking on day (calendar popup) calendar popup shows dates with highlighted in green (for available slots)
- Provide option to set the day-wise capacity to manage the resourcing for a rollout Group
- Should be an option to select different numbers for different dates
- Also, look at the possibility of setting up capacity for a timeslot in a day in the next version
Important:
- Keep things consistent. This means all graphics styles should work together
- All of the graphics should have a similar feel and general aesthetic appearance
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to fajar.mln@gmail.com (Challenge Copilot)
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comments this link while you upload).
Branding Guidelines
- Think of professional, clean branding for the application
- Open to designers
Documentation (Available in Challenge Forum)
- Rollout Management Tool Requirements 2602.pptx
- Very Basic Wireframes available online - https://sn4wst.axshare.com/#g=1&p=login
- Data Fields 2602.xlsx
Target Devices
- Web-Based Application
- Desktop: minimum 1366px Width with Height adjusted accordingly
Target Audiences
- System Engineer
- Administrator
- Self Service Users
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into solving the problem
- The overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
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 Adobe Photoshop, XD or 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.