Challenge Summary
Welcome to Cardinal Health – Asset Management Module Design Challenge!
Cardinal Health is in the process of integrating the acquisition of Innovative Therapies Inc. (ITI). ITI is dedicated to providing innovations in the Negative Pressure Wound Therapy (NPWT) market, and is located in Pompano Beach, FL.
Good luck and we look forward to your design!
-- 01 Warehouse Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 07 Update Asset.
- If you have time - please provide us with a click map for your design.
- Readme.jpg : Provide notes about your submission.
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
-- 01 Warehouse Dashboard.
-- 02 Operations Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 05 Request Inventory Transfer.
-- 06 Approve Inventory Transfer.
-- 07 Update Asset.
-- 08 Add Asset.
-- 09 Style Tile.
- If you have time - please provide us with a click map for your design.
- Readme.jpg : Provide notes about your submission.
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Challenge Description:
The goal of this project is replace ITI Order, the company’s primary internal and customer facing application. The primary function of the application is to manage the rental of medical devices to customers in acute care and home care settings. This is expected to consist of an "asset management" module and a "rental management" model, with additional features & functionality as identified by the business.
The goal of this challenge is to design the Asset Management Screens according to our requirements below.
Notes:
- This is going to be a Web App.
- Desktop view: 1280px width and height as required.
- Make sure your design consider responsiveness and will look good on both tablet and mobiles.
- Make sure you create graphic in 'shape' format, so when we resize graphics will still look sharp!
- Feel free to suggest any tools/functions that can bring good User Experience for this tool.
- ITIorder was the legacy application name, but ITI is no longer the "go to market" brand for this company. A better description might be Cardinal Health NPWT Rentals.
Users:
1- Warehouse User:
- This user can access:
-- 01 Warehouse Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 07 Update Asset.
2- Operations User:
- This user can access:
-- 02 Operations Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 05 Request Inventory Transfer.
-- 06 Approve Inventory Transfer.
-- 07 Update Asset.
-- 08 Add Asset.
Required Screens:
01 Warehouse Dashboard:
- This should show key information for the warehouse role, primarily a listing of assets that are "in motion", including the following categories:
1) Inbound: assets that are in transit and expected to be received soon at the central warehouse.
2) Received: assets that have been received but no further action has been taken (clean, refurbish, repair, move to inventory).
3) In process: assets for which some action has been taken, but more work is needed before they will be restocked to active inventory.
4) Pending shipment: assets being picked/packed.
5) Outbound assets: assets that have been shipped but not yet received by the recipient territory rep but not yet received by the recipient territory rep.
02 Operations Dashboard:
- This should show key information for the operations role. This view should contain four key functions.
1) Open ATRs (adjust ticket requests). ATRs are a future system enhancement when rental tickets are added in Module 2, so the requirements are not well-documented yet. This portion of the dashboard should simply show open tickets that need to be reviewed/approved by the operations staff.
2) Customer search tool: find a customer and provide link to that customer's dashboard.
3) Field rep search tool: find a field rep and link to his/her dashboard to view all assets in that rep's territory.
4) Metrics dashboard: Will show metrics/graphs about overall asset utilization. You can leave this as blank or add one graph or two with dummy data.
03 Ship Asset:
- This action takes place when warehouse or operations personnel need to physically move an asset from one location to another.
- This can be from the central warehouse to a field rep, from a field rep back to the central warehouse, or between reps in the field.
- Should capture basic information about the transfer so users can determine physical movement of the asset.
- Possible attributes:
-- Serial number.
-- From territory.
-- To territory.
-- Shipped by.
-- Shipped time/date.
-- Shipment method.
-- Tracking number.
-- Comment.
04 Receive Asset:
- This is the counterpart to the "ship asset" action.
- It is triggered when the recipient receives the asset.
- It should update the database to show that the asset has changed territories and is no longer in transit.
- Possible attributes:
-- Transaction ID.
-- Serial number.
-- From territory.
-- To territory.
-- Shipment method.
-- Tracking number.
-- Received.
-- Received time/date.
-- Comment.
05 Request Inventory Transfer:
- This action takes place when a field rep needs to request additional inventory from the central warehouse.
- Once submitted, this will trigger a workflow requiring approval from operations to release the order for pick/pack/ship.
- Field reps are frequent travelers, and should be able to receive shipments at any address (including home addresses, hotels, etc).
- Possible attributes:
-- Rep ID.
-- Time/date.
-- Ship to name.
-- Ship to address.
-- Ship to address 2.
-- Ship to city
-- Ship to state.
-- Ship to zip.
-- Ship to country.
-- Phone.
-- E-mail.
-- Instructions.
-- Item.
-- Quantity.
-- Description.
-- Units.
06 Approve Inventory Transfer:
- This action is triggered when a field rep requests inventory from the central warehouse.
- Operations staff will review the request and approve if within expected constraints.
- This will trigger a pick/pack/ship action from the warehouse staff.
- Possible attributes:
-- Request ID.
-- Rep ID.
-- Ship to first name.
-- Ship to to last name.
-- Ship to address 1.
-- Ship to address 2.
-- Ship to city.
-- Ship to state.
-- Ship to zip.
-- Ship to country.
-- Phone.
-- E-mail.
-- Instructions.
-- Item.
-- Quantity.
-- Description.
-- Units.
-- Approve.
-- Approved by.
-- Approved time/date.
07 Update Asset:
- This is a general action that may be undertaken to update information about an asset.
- Examples may include: adjust an incorrect territory ID or location ID, adjust model number, update health status, update hours in service, or set asset to decommissioned.
- Possible attributes:
-- Model.
-- Date retired.
-- Hours.
-- Territory ID.
-- Location ID.
-- Transit status.
-- Health status.
-- Device type.
-- Customer ID.
-- On rent (flag).
-- Asset owner.
08 Add Asset:
- This action adds a new asset to the system.
- The input screen should capture basic information about the asset, including the items shown below.
- In most, if not all cases, the device will be added to inventory in the central warehouse, but may require the ability to select other locations or status codes.
- Possible attributes:
-- Serial number.
-- Model (dropdown).
-- Date in service Hours (default to 0).
-- Territory ID (dropdown).
-- Location ID (dropdown).
-- Device type (dropdown).
-- Health status (dropdown).
-- Asset owner (ITI or customer ID).
09 Style Tile:
- We would like you to create a style tile that will help developers.
- This Style Tile need to have the below at a minimum but feel free to add anything that would help developers
- Explore these references to learn more about style tiles: Reference 1, Reference 2
Links / Buttons Colors:
- Button colors (normal / hover states)
- Link colors (normal / hover states)
Typography:
We would like you to identify and define the list of fonts and the specific color, font size used:
- Headers
- Sub-headers.
- Paragraphs.
- etc.
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
Branding Guidelines:
- http://www.cardinalhealth.com/brand-guide.html
Target audience:
- Cardinal Health Staff:
-- Warehouse User.
-- Operations User.
Judging Criteria:
- How well you plan the user experience and capture your ideas visually.
- How well you implement the challenge requirements.
- Completeness and accuracy of the designs.
- Cleanliness of your graphics and design.
- Creativity and ease-of-use is key to the success as it must be engaging to users.
Stock Artwork:
- Stock Artwork policies: https://help.topcoder.com/hc/en-us/articles/217481408-Policy-for-Stock-Artwork-in-Design-Submissions
- Latest Design Policies: http://help.topcoder.com/hc/en-us/categories/202610437-DESIGN
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 for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.
Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
Cardinal Health is in the process of integrating the acquisition of Innovative Therapies Inc. (ITI). ITI is dedicated to providing innovations in the Negative Pressure Wound Therapy (NPWT) market, and is located in Pompano Beach, FL.
Good luck and we look forward to your design!
Round 1
Submit your initial design for a checkpoint feedback:-- 01 Warehouse Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 07 Update Asset.
- If you have time - please provide us with a click map for your design.
- Readme.jpg : Provide notes about your submission.
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Round 2
Final design plus checkpoint feedback:-- 01 Warehouse Dashboard.
-- 02 Operations Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 05 Request Inventory Transfer.
-- 06 Approve Inventory Transfer.
-- 07 Update Asset.
-- 08 Add Asset.
-- 09 Style Tile.
- If you have time - please provide us with a click map for your design.
- Readme.jpg : Provide notes about your submission.
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Challenge Description:
The goal of this project is replace ITI Order, the company’s primary internal and customer facing application. The primary function of the application is to manage the rental of medical devices to customers in acute care and home care settings. This is expected to consist of an "asset management" module and a "rental management" model, with additional features & functionality as identified by the business.
The goal of this challenge is to design the Asset Management Screens according to our requirements below.
Notes:
- This is going to be a Web App.
- Desktop view: 1280px width and height as required.
- Make sure your design consider responsiveness and will look good on both tablet and mobiles.
- Make sure you create graphic in 'shape' format, so when we resize graphics will still look sharp!
- Feel free to suggest any tools/functions that can bring good User Experience for this tool.
- ITIorder was the legacy application name, but ITI is no longer the "go to market" brand for this company. A better description might be Cardinal Health NPWT Rentals.
Users:
1- Warehouse User:
- This user can access:
-- 01 Warehouse Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 07 Update Asset.
2- Operations User:
- This user can access:
-- 02 Operations Dashboard.
-- 03 Ship Asset.
-- 04 Receive Asset.
-- 05 Request Inventory Transfer.
-- 06 Approve Inventory Transfer.
-- 07 Update Asset.
-- 08 Add Asset.
Required Screens:
01 Warehouse Dashboard:
- This should show key information for the warehouse role, primarily a listing of assets that are "in motion", including the following categories:
1) Inbound: assets that are in transit and expected to be received soon at the central warehouse.
2) Received: assets that have been received but no further action has been taken (clean, refurbish, repair, move to inventory).
3) In process: assets for which some action has been taken, but more work is needed before they will be restocked to active inventory.
4) Pending shipment: assets being picked/packed.
5) Outbound assets: assets that have been shipped but not yet received by the recipient territory rep but not yet received by the recipient territory rep.
02 Operations Dashboard:
- This should show key information for the operations role. This view should contain four key functions.
1) Open ATRs (adjust ticket requests). ATRs are a future system enhancement when rental tickets are added in Module 2, so the requirements are not well-documented yet. This portion of the dashboard should simply show open tickets that need to be reviewed/approved by the operations staff.
2) Customer search tool: find a customer and provide link to that customer's dashboard.
3) Field rep search tool: find a field rep and link to his/her dashboard to view all assets in that rep's territory.
4) Metrics dashboard: Will show metrics/graphs about overall asset utilization. You can leave this as blank or add one graph or two with dummy data.
03 Ship Asset:
- This action takes place when warehouse or operations personnel need to physically move an asset from one location to another.
- This can be from the central warehouse to a field rep, from a field rep back to the central warehouse, or between reps in the field.
- Should capture basic information about the transfer so users can determine physical movement of the asset.
- Possible attributes:
-- Serial number.
-- From territory.
-- To territory.
-- Shipped by.
-- Shipped time/date.
-- Shipment method.
-- Tracking number.
-- Comment.
04 Receive Asset:
- This is the counterpart to the "ship asset" action.
- It is triggered when the recipient receives the asset.
- It should update the database to show that the asset has changed territories and is no longer in transit.
- Possible attributes:
-- Transaction ID.
-- Serial number.
-- From territory.
-- To territory.
-- Shipment method.
-- Tracking number.
-- Received.
-- Received time/date.
-- Comment.
05 Request Inventory Transfer:
- This action takes place when a field rep needs to request additional inventory from the central warehouse.
- Once submitted, this will trigger a workflow requiring approval from operations to release the order for pick/pack/ship.
- Field reps are frequent travelers, and should be able to receive shipments at any address (including home addresses, hotels, etc).
- Possible attributes:
-- Rep ID.
-- Time/date.
-- Ship to name.
-- Ship to address.
-- Ship to address 2.
-- Ship to city
-- Ship to state.
-- Ship to zip.
-- Ship to country.
-- Phone.
-- E-mail.
-- Instructions.
-- Item.
-- Quantity.
-- Description.
-- Units.
06 Approve Inventory Transfer:
- This action is triggered when a field rep requests inventory from the central warehouse.
- Operations staff will review the request and approve if within expected constraints.
- This will trigger a pick/pack/ship action from the warehouse staff.
- Possible attributes:
-- Request ID.
-- Rep ID.
-- Ship to first name.
-- Ship to to last name.
-- Ship to address 1.
-- Ship to address 2.
-- Ship to city.
-- Ship to state.
-- Ship to zip.
-- Ship to country.
-- Phone.
-- E-mail.
-- Instructions.
-- Item.
-- Quantity.
-- Description.
-- Units.
-- Approve.
-- Approved by.
-- Approved time/date.
07 Update Asset:
- This is a general action that may be undertaken to update information about an asset.
- Examples may include: adjust an incorrect territory ID or location ID, adjust model number, update health status, update hours in service, or set asset to decommissioned.
- Possible attributes:
-- Model.
-- Date retired.
-- Hours.
-- Territory ID.
-- Location ID.
-- Transit status.
-- Health status.
-- Device type.
-- Customer ID.
-- On rent (flag).
-- Asset owner.
08 Add Asset:
- This action adds a new asset to the system.
- The input screen should capture basic information about the asset, including the items shown below.
- In most, if not all cases, the device will be added to inventory in the central warehouse, but may require the ability to select other locations or status codes.
- Possible attributes:
-- Serial number.
-- Model (dropdown).
-- Date in service Hours (default to 0).
-- Territory ID (dropdown).
-- Location ID (dropdown).
-- Device type (dropdown).
-- Health status (dropdown).
-- Asset owner (ITI or customer ID).
09 Style Tile:
- We would like you to create a style tile that will help developers.
- This Style Tile need to have the below at a minimum but feel free to add anything that would help developers
- Explore these references to learn more about style tiles: Reference 1, Reference 2
Links / Buttons Colors:
- Button colors (normal / hover states)
- Link colors (normal / hover states)
Typography:
We would like you to identify and define the list of fonts and the specific color, font size used:
- Headers
- Sub-headers.
- Paragraphs.
- etc.
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
Branding Guidelines:
- http://www.cardinalhealth.com/brand-guide.html
Target audience:
- Cardinal Health Staff:
-- Warehouse User.
-- Operations User.
Judging Criteria:
- How well you plan the user experience and capture your ideas visually.
- How well you implement the challenge requirements.
- Completeness and accuracy of the designs.
- Cleanliness of your graphics and design.
- Creativity and ease-of-use is key to the success as it must be engaging to users.
Stock Artwork:
- Stock Artwork policies: https://help.topcoder.com/hc/en-us/articles/217481408-Policy-for-Stock-Artwork-in-Design-Submissions
- Latest Design Policies: http://help.topcoder.com/hc/en-us/categories/202610437-DESIGN
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 for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.
Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
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.