Thor PDU Mass Commissioning Concept Design Challenge

Round 1

• Submit as much screen as you can to get early feedback
• 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 correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

• 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 correct flow. Use the proper file numbers, (1, 2, 3, etc.)

• This will be built as desktop native application
• A PDU is identified either by its SN (Serial Number), MAC address or both
• The app is able to manage both GLOBAL configuration settings (that will be applied indifferently to all PDUs) and INDIVIDUAL settings (unique IP address, device name, etc… specific to a given PDU)
• The application can save/restore its status before exporting the configuration parameters

• User creates a CSV file from a provided template offline, and from outside of the application.
• User opens Mass Commissioning app and goes to the general settings page
• User clicks "upload configuration" button and selects the CSV file that was created outside of the app.
• User goes to general settings configuration.  There is a "GENERIC" option which selects firmware to be applied to any and all PDUs.  And there is a “SPECIFIC” option which allows the user to apply custom firmware to each individual PDU, from the CSV file created earlier.
• User goes to Network Infrastructure settings and inputs necessary configurations.  See the provided spreadsheet for the settings and configurations sample data.  The items highlighted in Blue are the  configurations for Basic mode and are always present. The other items in White are expert features and depending on the PDU type, some of these will be shown on the app.  So just pick a few when designing for Expert mode.
• User goes to Asset Management. A table displays all of the devices which were loaded from the CSV file in step 3. The user configures each device’s specific settings by clicking the device and configuring the settings on the additional section which comes up for that device.  See the spreadsheet for the sample data.  The items highlighted in Blue are the  configurations for Basic mode and are always present. The other items in White are expert features and dependant on the PDU type.  So just pick a few when designing for Expert mode.
• User goes to Export screen and confirms there are no validation issues. 
• User clicks the "Export" button and selects the USB drive they are exporting to
• Application saves all configuration elements to a CSV file in a local application folder
• Application converts the saved CSV file into the proper folder and file structure on the user's selected drive/folder
• Application prompts user when export is complete
• User unplugs the USB drive they exported to and plugs it into each of the PDUs that need to be configured

• When the user finishes with all of the PDU configurations, they plug the USB drive back into their computer, and opens the Mass Commissioning App.
• User goes to the Post-Configuration screen and clicks the "View Commissioning Logs" button which brings them to a folder selection on the USB drive
• The application loads a table of all the devices from the folder structure and analyzes  the log file. The table displays each of the Device Serial/MAC addresses and Commissioning Status, which shows Green/Yellow/Red icons for Success/Not Commissioned (no log)/Error Commissioning.
• User views a detailed log file displayed below the table, for the devices with errors to see error messages.

• This is a design concepts challenge, we need you to come up with a better application flow, layout and improvements on functionalities
• You’re encourage to suggest the best layout composition that will make the application more user friendly
• Current application screenshots are just the starting point, we expect you to not just redesign the application.
• Remember your submission design need address solutions that stated on Application high-level requirements above
• There are some additional features that need to be displayed on the app for the next version release
• Read each section carefully!
• Current application screenshots can be seen here:  https://drive.google.com/open?id=1Q_cY71aNppJLrPBjQkXiXAWxhlqnxgLV  
• This is app flow diagram to help you understand the app flow: https://www.lucidchart.com/publicSegments/view/b689c24e-caa8-440a-90ab-bac4dc32221d/image.jpeg 

• The welcome screen gives an introduction to the application and gives an overview of the app functionalities. 
• Includes Logo Placeholder + PDU related graphics
• Includes a short introduction to the application
• gives an overview of the app functionalities

• There will be 2 user modes:
  • BASIC: only a basic set of parameters is accessible (Light UI)
  • EXPERT: a more exhaustive list of parameters is accessible
• Refer to provided document of what need displayed for BASIC vs Expert: https://docs.google.com/spreadsheets/d/1g2ObOG0-D6dgyYBFB2NwlJQkOgv3IssPT7re9sbfCpc/edit?usp=sharing 
• User Profile choices always visible on screen: (BASIC vs. EXPERT) + language selection + ‘Help’ link 
• We are still waiting on the parameters for Basic and Expert mode, there should be a clear Basic/Expert mode.  

• The user is able to change configurations by: 
  • Uploading an existing configuration file (CSV file).  By default, the firmware loaded by the user is a general configuration setting that can be applied to all PDUs.
  • The user can also select an option to load custom firmware for each specific device.  When this option is selected, a warning notice appears saying, “Each FW needs to be in the originating folder” (Feel free to use your own wording)
  • Additional General Settings
    • Provide Administrator credentials (Admin Account & Admin Password) to be later exported to the USB and uploaded to the PDUs
    •  Unit Identification Criteria: should be 2 fields (MAC Address and SN).  The user should be able to manually enter the data into either of those fields or use a barcode scanner to enter the necessary data
    • The PDU device types: MI/IL, MO, SW, MA
• Firmware upgrade scenario option : (NONE / GENERIC /SPECIFIC), allows the option to upgrade the firmware on an already commissioned PDU

• We need way to simplify Network settings and Internet settings below to make them to be more user friendly. 
• Does all of this information really need to be provided and/or seen by the user?
• There are 3 tabs on Network page: 
  • Interface: allows the user to choose between Wireless and Wired Ethernet connections
  • Service 
  • Traps Management - allows monitoring of PDU devices on the network
• Need allows the user to configure all the generic network related parameters IPv4, IPv6 (IP address range Start-end), DHCP, DNS, NTP, etc
• On Network, user can change configuration for: 
  • IPv4
  • IPv6

• This screen is mainly a table of the devices being configured.
• Allow the ability to Import .csv files, 
• The data from the .csv file populates a table with the devices being commissioned
• Remove the Wizard tab from your design
• In the table view, we need to allow the user to manually add, edit and remove the devices
• The user can select one or more devices and adjust the configuration of device specific settings
• We also need you to create another view to check each devices threshold. There will be low, medium and high threshold.

• PDU ID (MAC and/or SN), PDU type, asset location, naming, contact, feed names, host name or Static IP, etc

• SNMP&Traps, SMTP, TFTP, FTPS, SSH, Telnet, etc

• Threshold values, outlet naming, etc

• This will be the area to export the configuration files based on what the user filled out in the previous steps
• When the user plugs in a USB drive, there should be some type of indication showing that that either the USB is ok or an error message showing that it is not properly formatted 
• Shows a list of the PDUs being configured and commissioned
• Gives feedback on the validation checks (if parameters are missing or if any validation is not passing)
• Before exporting the files, the app performs some basic consistency checks to detect potential errors.  Below are some example errors:  
• The same PDU SN and/or MAC address cannot have different configuration settings, but the same IP can be used on different PDUs in case of separated networks (however, the same IP configured on different PDUs should rise some warning)
• The app is able to detect any error in the field format or type (check whether the IPv4 or IPv6 field is correct, a MAC address should be XX:XX:XX:XX:XX where X is a character, etc…)
• Check whether the MAC address has the right MAC prefix
• Gives feedback on the validation checks (if parameters are missing or if any validation is not passing)
• Gives feedback on the USB drive status
• Shows a list of the PDUs being configured and commissioned with 2 different levels of granularity:
  • Overview
  • Detailed Log per PDU
• Able to parse the restoration points available on the flash drive (under /OLD folder) and select one to be restored based on its time stamp

• Post Configuration Screen
• After the user has commissioned the PDUs, they can plug the USB back into their desktop and view the commissioning status.  The status would be either “Successful” or “Unsuccessful”
• Should also have the ability see further details about the commissioning status
• Once the user has analyzed the statuses, they can choose to restore the old configuration on the PDUs that failed.  The application copies the previous files that worked, back onto the USB into the appropriate folders.  The user ejects the USB and makes another attempt at configuring the PDUs that failed.

• Overall idea and execution of concepts
• How well does your design align with the objectives of the challenge
• Execution and thoughtfulness put into the solving the problem
• Overall design and user experience
• Cleanliness of screen design and user flow
• Ease of use

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback