Challenge Summary
Welcome to the "RUX Vulcan - Collaboration Tool Design Refinement Challenge". This RUX is a follow-up challenge to the recently completed challenge to create a “Collaboration Tool” for the Vulcan company. In this RUX challenge, we are looking for your help to refine, completing missing screens/features/interactions, combine and clean up the different design elements based on the provided winning designs, and the latest client requirements for the application. This challenge is focused on creating one solid application design that provides well-organized information architecture and clean navigation for the user to have a seamless experience.
Let us know if you have any questions!
What is a RUX Challenge?
The RUX (Rapid User Experience) challenge uses the same format as our famous LUX Challenge except it is not "Live" at an event. The RUX Challenge Series provides you with an opportunity to show digital leaders from some of the largest companies in the world just how good your concept and user experience (UI/UX) design skills are.
RUX (Rapid User Experience) challenges are fast, fun, and have more chances for you to capture prize money!
Note: You do not need to have RUX challenge experience to join this challenge - Just jump in and give it a try! Make sure to follow the challenge details, the challenge forum and ask questions.
Project Description
Vulcan is a company that is implementing new technologies and digital transformation within their factories and plants. To execute these plans, Vulcan is preparing 2 strategic initiatives, which are:
1. Create a "collaboration tool" between Vulcan Technicians and Experts which was recently started via This RUX challenge
2. Create a "Nerve Center" or command center room in their headquarters, that will monitor, react and predict all things related to IIOT connected devices (assets) within Vulcan factories and plants which was recently run via This RUX challenge (in Review Phase)
In this challenge, we want to continue to refine, update and improve the "collaboration story" and design the screens and interactions between Technician and Experts. We are looking to:
1. Complete the flow (include any missing features)
2. Continue refining the UI
RUX Challenge Timeline and Rolling Checkpoint
- Submission Start: Tuesday, 18th December 2018 at 23:00 PM EST
- Rolling Checkpoint Start: Thursday, 20th December 2018 at 11:00 AM EST
- Submission End: Friday, 21st December 2018 at 23:00 PM EST
Note: Important Rolling Checkpoint Details
- High-Def and adroc will answer questions and provide Rolling Feedback as fast as possible
- You must watch the Forum for your feedback!
- All initial qualifying checkpoint submissions will win $50 (Only 8 potential submissions)
Challenge Goal
Continue to refine the UI and completing screen interactions between Technician and Expert in the "collaboration tool", in order to facilitate access communication between those two roles and speed up the process of fixing machine issues
Challenge Forum
Please ask in challenge forum for any doubts/questions regarding challenge requirements:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=651018&mc=4
User Personas
1. Factory Maintenance Technician
- Machine "fixers" who need their hands free to perform their jobs. They wear an AR headset (we will use the Realwear glasses product) which acts as a HUD (heads up display) that provides necessary information and data on the machinery. They need their hands free to operate and fix the machines. The Factory Technician will be reaching out and asking for assistance from the expert network as part of this collaboration tool.
- AR realwear Headset (https://www.realwear.com/) is a hands-free tool based on an Android OS for industrial workers. It is head-mounted to improve the efficiency and productivity of mobile workers in hazardous environments. See this link for the glasses detail information.
2. Machine/Technical Experts
- Our company experts, who work globally and remotely away from the factories that they monitor. They are there to support the Technicians with any machine issues. The devices they use is primarily tablets (as they will be mobile).
- This collaboration tool will look to "assign the best talent and available talent" to the situation. They can be anywhere in the world so the collaboration tool will also provide a real-time voice translation. The experts might use different language from the Technician but the collaboration tools should have the capability to translate the language in real time for both of them. See this video to get more ideas/information about the real-time voice translation.
IMPORTANT NOTE: Vulcan has upwards of 150 factories around the world, a Technician who receives help today can be an expert that is helping someone else tomorrow. This is an important contextual element and key to "collaboration". It is important because an expert has their own routine and work within the factory they support.
~
Screen Requirements and Refinements
For this challenge, we are looking for the provided "user story" to be captured as we will want to demo this experience (between the Technician and the Expert) in the future. The screen functionality listed is suggested functionality for consideration. As we are continuing to refine the story please continue to look for design efficiencies in the experience. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
Glasses
01) Technician Assignment
1. The Technician will log into the system using the AR glasses (by scanning his ID card or via Voice authentication). They are aware they need to check an asset or see about available Work Orders (WO) planned for Technician’s undertaking.
2. The Technician will need to prompt/use the voice command to call their dashboard (“Show me Dashboard”, “Show me Work Orders”) - it needs to be arranged to have a good fit for the AR Glasses (more visibility and less visual blocks than the current design(s), Technician). The Technician by default will error on the side of visibility in their glasses.
*Design Note: Many of the designs in the first challenge covered a lot of the main focus/viewing area… work to improve this and look to see what "actions" or interactions can be called by voice.
3. The Technician can see if there are any immediate Work Orders (WO) for himself so they can go to that asset and start work. Usually, WOs have a schedule. If they grab a WO it will provide them the Asset information, location, issue etc. The Technician is able to start to diagnose the issue as they are on their way to check on it.
*Design Note: Work Order items are listed based on impact. The Technician will walk to the asset and deal with the situation. A WO might go for a few days. More than one technician can be doing the work in their respective shifts for long WOs, like a relay race.
WO Status
- In Progress
- Completed
- Assigned
- Status of parts and impact on status of WO.
4. Need to see a factory view that shows items that have work orders. also allows the tech to ask for directions to the machine that needs fixing.
5. Voice Search: In a typical plant/factory, there might be 400 assets available there, so voice search is needed, for example: Voice command: "Milling", then continue with another Voice command: "status vulnerable" (it would filter milling machines of which status is 'vulnerable') - Voice commands should be displayed back to the glasses user, this will ensure they are captured properly.
Samples:
Voice command - up / down, or search: 'current'
Voice command - 'Last 50 hours' – shows the time series for only the last 50 hours
Voice command - 'anomalies only'. – filters sensor series with anomalies in the last 50 hours
Voice command – 'correlation' - calculates whether some sensor readings have strong correlation and activates the ones with strong correlation
Voice command – 'only strongly correlated' - filters everything else
Voice command - 'anomalies more than 1 standard deviations'
6. Recording: Recording Features - Ability to start/stop recording and documenting issue when start fixing the Asset
7. A Technician can also scan an Asset in the factory to see current status, any Work Orders and subscribe to it take the immediate WO.
8. If there is problem that happens when a Technician is on duty and there is no assignment created yet, the Technician can create the Work Order by themselves.
02) Analyzing Assets
An asset here can be a Machine, Robot, Workstation, etc.
1. The Technician will need to connect to the Asset first by scanning barcode OR selecting the asset from collaboration tool database (choose/search from Asset list). Then technician sees the Asset Hierarchy for the selected asset. Asset Hierarchy refers to the components/sub-components/sub-components… is organized for an Asset.
*Design Note: We will mention the Asset Hierarchy a lot here. This is a missing interaction(s) that we want to capture. "Asset Insights". This view may be captured in a couple of locations. The Technician can see all Assets or they will see how the Asset they are checking on fits in that hierarchy. We currently see this being designed in a tree structure. (see Complex-Assets.png)
Asset Hierarchy View
- Important to capture Assets (their hierarchy) and time series data. This view is insightful if it can show a link among 2-3 abnormal sensor readings.
Scenario
- Current (amp) spiked like 50%
- 3 seconds later the oil temperature starts to increase steadily for 120 seconds
- In this 120 seconds 'wear metal particles' sensor reading increases rapidly (this actually means some mechanical problem with the gears)
- At the end machine gave an error and shut down.
If the UI can connect these 3 events, the Technician asks 'select gearbox', they see the gearbox 3D CAD and associated sensor data (hours since last maintenance etc.)
2. The Technician is able to see all of the Asset details, Asset hierarchy, work orders, previous history, drill into the asset details.
- Asset Details
- Asset History
- Parameters
- Diagnostics
- Status: Vulnerable, Critical, Stable
Thinking this might be 4 Tabs: Asset, Asset History, Parameters, Diagnostics
*Design Note: What is a good interaction of calling up a lot of information? We need to maximize the Technicians cognitive effectiveness, especially working memory. So, going back and forth between screens/tabs might not be the best solution. Also, we need technicians glass view as open as possible, due to safety concerns.
3. The Technician is able to see a thermal imaging view of the Asset (see attachments)
03) Asset Detail and Drill-in
After the Technician has checked on on the asset they will want to see additional information and drill into the Asset details to figure out what is wrong/how to fix the issue. Essentially they will be doing a much "self-help" if possible.
1. To open the asset details, the Technician needs to use Voice command like "Open CAD" or "Open Blueprint".
2. The Asset Hierarchy would be visible to the Technician.
3. Technician see's the documentation dashboard and listed blueprint/CAD documents
4. Some of the most frequent failure types can be shown with the CAD drawing. Because we are narrowing the culprits. Showing "common issues"
5. Technician is able to drill into the documents, zoom into the CAD/Blueprint files to find the item they are looking for. Voice command is critical here.
*Design Note: Focus on the user - "Safety First" on how they will be viewing/using this feature while in the factory.
04) Request Help
The Technician is unable to find or solve the problem OR they need immediate help "SOS"
1. The Technician asks for help - voice command
2. Provide an ability to ask for help - it can be done via two ways:
Find Expert
- Find the expert directly is available in the system via the collaboration tool database.
- Show the list of Experts and see their profile before connecting to them
- Find Experts algorithm should be based on (Skill + Location + Availability + Rating + Cost Per Hour + Experience with the Asset or similar problem classes).
- No need to show Experts who are not available (no use for that).
- A Technician might select a different expert if they know that expert will be available in an hour (so reasonable availability).
- Most important is, the Experts should have status 'has worked on this machine before'
- The Technician, with the help of Nerve Center or Choose the Expert directly, will be able to setup a 'collaboration session' with the selected Expert to get the problem fixed
SOS Alert
- Send SOS to the Nerve Center so they can analyze the problem and find a solution from the Nerve Center base knowledge or put in a request to an Expert.
05) Technician & Experts Collaboration
- We want to capture the flow of how the Technician and Experts are collaborating.
*Design Note: Keep the names, assets, expert consistent throughout your screens
- In the 'collaboration session' provide a feature that if the recording has not started yet (Technician does not activate the features when he starts doing the assignment), the Tool will record the call automatically to create an archive/transcript that will be saved and sent to the Nerve Center for future improvements.
Technician (Glasses)
1. Technician (no need to see the Experts face) - has to see what the Experts is seeing on the screen - However, if necessary, Technician should also able to call "show me expert" to pull up the video of the expert, maybe the expert needs to show a part
2. Show conversation features between Technician and Alex - Real Time Voice Translation (show audio and text translation)
3. Show the collaboration tool "AR" where they are working together to view a 3D diagram of the machine.
4. Show the collaboration tool where the Expert is drawing and pointing on the screen, Expert is coding/making updates to the Asset, sharing documents.
5. Show the issues being resolved where Technician provides verbal feedback/notes on the issues and what was solved. (These notes and video show up later in the support areas)
Experts (Tablet)
*Challenge Note: the priority in this challenge is Technician flow (and interactions with the Expert). Look to refine the Glasses view as much as possible.
1. The Experts will be able to login and see his dashboard via tablet device
- The Experts should be able to see missed calls and ability to called back
2. Experts should be able to perform this Asset Maintenance/Fixing Attempts from his tablet (and Technician can see it):
- Get pictures/video of the asset - Need to see more than 1 side of an asset at the same time.
- See Blueprints, CAD, 3D images
- The ability to upload the Asset schematic and then the Technician can see it (blueprint, image of a part, instruction manual, etc)
- Show Asset Details Information (See sensor readings, filter, sort - See asset hierarchy - See 3D CAD models of the components of the asset hierarchy)
- Ability to Remote Connect to the Machines - Remote access to machine CLI or Remote access to a laptop with access to machine CLI
- Show Suggestions (from the Nerve Center)
- Read the Asset manual document
- Follow the available module to fix issue (based on log history or from maintenance work instructions)
- Drawing on the screen by the Expert - including Drag and drop to the Technician video/screen
- Upload video
- Show previous incident reports (See maintenance/repair history)
- Capture WO wrap up questions: Captured verbally by both the Technician and the Expert
Multiple Experts Scenario, needs to provide collaboration session to be elaborated with screen sharing, 2 Experts + 1 Technician, remote access to machine CLI - If for some reason, the current Experts can't solve the Asset problem (less knowledge, called disconnected, etc), Technician can request another Experts to join the call and collaborate to fix the Asset problems (so the other experts can learn too)
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/comment this link while you upload).
Video References
- Real Time Voice Translation: https://www.youtube.com/watch?v=oQVQVt5H2QM
- How Voice Control Works in glasses: https://www.youtube.com/watch?v=T5ddPN7a9fk
- Sample video of Collaboration between Technician and Expert: https://www.youtube.com/watch?v=Mvjf8VOKZy4
- RealWear Glasses demo:
-- https://www.realwear.com/rw/hmt-1-featured-in-honeywell-video/
-- https://www.youtube.com/watch?v=kGBgBFkQuFE
-- https://iqagent.com/realwear/
-- https://www.youtube.com/watch?v=RNW842zldlo
Previous RUX Design
- We are providing the screen designs from the previous RUX
- Use them as inspiration for where we want to continue to evolve the UI
- Color is very important! Clarity of data is very important!
Branding Guidelines
- We would like you to continue to evolve the UI leveraging the previous 1st place design and also the designs from the Nerve Center RUX. This is an evolution.
- The designs do need to work in an "enterprise setting" so do not go too crazy with the star trek/futuristic fonts! See more details in the Forum.
- Think about target users and type of devices that they will be wearing (glasses and tablet)
- Avoid contrasts that are too hard and too light
- Modern UI's are okay and now we are refining the "look" even more! This is conceptual..so color, icons, the voice services (control and translation) is critical to helping the user quickly get answers.
Documentation
Download all documentation from the challenge forum!
- Design Direction and Wireframe (RUX51-Reference-Files)
- Complex-Assets.png
- Branding Guidelines Document
- Previous RUX Winners as Reference (RUX Collaboration Tool Source Files)
- Plant and Machine Images References (Use these as images for the plant and machines in your design)
Target Devices
AR Glasses and Tablet - 1024px width and 600px height:
- Factory Maintenance Technician: Horizontal/Landscape using voice/sound interaction (Glasses)
- Machine/Technical experts: Landscape or Portrait - Open to any suggestion (tablet)
- Use grid systems for your layout
Target Audiences
- Factory Maintenance Technician
- Machine/Technical experts
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 the 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, Illustrator, XD or Sketch and saved as editable layer
Final Fixes
This RUX might have final fixes
Let us know if you have any questions!
What is a RUX Challenge?
The RUX (Rapid User Experience) challenge uses the same format as our famous LUX Challenge except it is not "Live" at an event. The RUX Challenge Series provides you with an opportunity to show digital leaders from some of the largest companies in the world just how good your concept and user experience (UI/UX) design skills are.
RUX (Rapid User Experience) challenges are fast, fun, and have more chances for you to capture prize money!
Note: You do not need to have RUX challenge experience to join this challenge - Just jump in and give it a try! Make sure to follow the challenge details, the challenge forum and ask questions.
Project Description
Vulcan is a company that is implementing new technologies and digital transformation within their factories and plants. To execute these plans, Vulcan is preparing 2 strategic initiatives, which are:
1. Create a "collaboration tool" between Vulcan Technicians and Experts which was recently started via This RUX challenge
2. Create a "Nerve Center" or command center room in their headquarters, that will monitor, react and predict all things related to IIOT connected devices (assets) within Vulcan factories and plants which was recently run via This RUX challenge (in Review Phase)
In this challenge, we want to continue to refine, update and improve the "collaboration story" and design the screens and interactions between Technician and Experts. We are looking to:
1. Complete the flow (include any missing features)
2. Continue refining the UI
RUX Challenge Timeline and Rolling Checkpoint
- Submission Start: Tuesday, 18th December 2018 at 23:00 PM EST
- Rolling Checkpoint Start: Thursday, 20th December 2018 at 11:00 AM EST
- Submission End: Friday, 21st December 2018 at 23:00 PM EST
Note: Important Rolling Checkpoint Details
- High-Def and adroc will answer questions and provide Rolling Feedback as fast as possible
- You must watch the Forum for your feedback!
- All initial qualifying checkpoint submissions will win $50 (Only 8 potential submissions)
Challenge Goal
Continue to refine the UI and completing screen interactions between Technician and Expert in the "collaboration tool", in order to facilitate access communication between those two roles and speed up the process of fixing machine issues
Challenge Forum
Please ask in challenge forum for any doubts/questions regarding challenge requirements:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=651018&mc=4
User Personas
1. Factory Maintenance Technician
- Machine "fixers" who need their hands free to perform their jobs. They wear an AR headset (we will use the Realwear glasses product) which acts as a HUD (heads up display) that provides necessary information and data on the machinery. They need their hands free to operate and fix the machines. The Factory Technician will be reaching out and asking for assistance from the expert network as part of this collaboration tool.
- AR realwear Headset (https://www.realwear.com/) is a hands-free tool based on an Android OS for industrial workers. It is head-mounted to improve the efficiency and productivity of mobile workers in hazardous environments. See this link for the glasses detail information.
2. Machine/Technical Experts
- Our company experts, who work globally and remotely away from the factories that they monitor. They are there to support the Technicians with any machine issues. The devices they use is primarily tablets (as they will be mobile).
- This collaboration tool will look to "assign the best talent and available talent" to the situation. They can be anywhere in the world so the collaboration tool will also provide a real-time voice translation. The experts might use different language from the Technician but the collaboration tools should have the capability to translate the language in real time for both of them. See this video to get more ideas/information about the real-time voice translation.
IMPORTANT NOTE: Vulcan has upwards of 150 factories around the world, a Technician who receives help today can be an expert that is helping someone else tomorrow. This is an important contextual element and key to "collaboration". It is important because an expert has their own routine and work within the factory they support.
~
Screen Requirements and Refinements
For this challenge, we are looking for the provided "user story" to be captured as we will want to demo this experience (between the Technician and the Expert) in the future. The screen functionality listed is suggested functionality for consideration. As we are continuing to refine the story please continue to look for design efficiencies in the experience. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
Glasses
01) Technician Assignment
1. The Technician will log into the system using the AR glasses (by scanning his ID card or via Voice authentication). They are aware they need to check an asset or see about available Work Orders (WO) planned for Technician’s undertaking.
2. The Technician will need to prompt/use the voice command to call their dashboard (“Show me Dashboard”, “Show me Work Orders”) - it needs to be arranged to have a good fit for the AR Glasses (more visibility and less visual blocks than the current design(s), Technician). The Technician by default will error on the side of visibility in their glasses.
*Design Note: Many of the designs in the first challenge covered a lot of the main focus/viewing area… work to improve this and look to see what "actions" or interactions can be called by voice.
3. The Technician can see if there are any immediate Work Orders (WO) for himself so they can go to that asset and start work. Usually, WOs have a schedule. If they grab a WO it will provide them the Asset information, location, issue etc. The Technician is able to start to diagnose the issue as they are on their way to check on it.
*Design Note: Work Order items are listed based on impact. The Technician will walk to the asset and deal with the situation. A WO might go for a few days. More than one technician can be doing the work in their respective shifts for long WOs, like a relay race.
WO Status
- In Progress
- Completed
- Assigned
- Status of parts and impact on status of WO.
4. Need to see a factory view that shows items that have work orders. also allows the tech to ask for directions to the machine that needs fixing.
5. Voice Search: In a typical plant/factory, there might be 400 assets available there, so voice search is needed, for example: Voice command: "Milling", then continue with another Voice command: "status vulnerable" (it would filter milling machines of which status is 'vulnerable') - Voice commands should be displayed back to the glasses user, this will ensure they are captured properly.
Samples:
Voice command - up / down, or search: 'current'
Voice command - 'Last 50 hours' – shows the time series for only the last 50 hours
Voice command - 'anomalies only'. – filters sensor series with anomalies in the last 50 hours
Voice command – 'correlation' - calculates whether some sensor readings have strong correlation and activates the ones with strong correlation
Voice command – 'only strongly correlated' - filters everything else
Voice command - 'anomalies more than 1 standard deviations'
6. Recording: Recording Features - Ability to start/stop recording and documenting issue when start fixing the Asset
7. A Technician can also scan an Asset in the factory to see current status, any Work Orders and subscribe to it take the immediate WO.
8. If there is problem that happens when a Technician is on duty and there is no assignment created yet, the Technician can create the Work Order by themselves.
02) Analyzing Assets
An asset here can be a Machine, Robot, Workstation, etc.
1. The Technician will need to connect to the Asset first by scanning barcode OR selecting the asset from collaboration tool database (choose/search from Asset list). Then technician sees the Asset Hierarchy for the selected asset. Asset Hierarchy refers to the components/sub-components/sub-components… is organized for an Asset.
*Design Note: We will mention the Asset Hierarchy a lot here. This is a missing interaction(s) that we want to capture. "Asset Insights". This view may be captured in a couple of locations. The Technician can see all Assets or they will see how the Asset they are checking on fits in that hierarchy. We currently see this being designed in a tree structure. (see Complex-Assets.png)
Asset Hierarchy View
- Important to capture Assets (their hierarchy) and time series data. This view is insightful if it can show a link among 2-3 abnormal sensor readings.
Scenario
- Current (amp) spiked like 50%
- 3 seconds later the oil temperature starts to increase steadily for 120 seconds
- In this 120 seconds 'wear metal particles' sensor reading increases rapidly (this actually means some mechanical problem with the gears)
- At the end machine gave an error and shut down.
If the UI can connect these 3 events, the Technician asks 'select gearbox', they see the gearbox 3D CAD and associated sensor data (hours since last maintenance etc.)
2. The Technician is able to see all of the Asset details, Asset hierarchy, work orders, previous history, drill into the asset details.
- Asset Details
- Asset History
- Parameters
- Diagnostics
- Status: Vulnerable, Critical, Stable
Thinking this might be 4 Tabs: Asset, Asset History, Parameters, Diagnostics
*Design Note: What is a good interaction of calling up a lot of information? We need to maximize the Technicians cognitive effectiveness, especially working memory. So, going back and forth between screens/tabs might not be the best solution. Also, we need technicians glass view as open as possible, due to safety concerns.
3. The Technician is able to see a thermal imaging view of the Asset (see attachments)
03) Asset Detail and Drill-in
After the Technician has checked on on the asset they will want to see additional information and drill into the Asset details to figure out what is wrong/how to fix the issue. Essentially they will be doing a much "self-help" if possible.
1. To open the asset details, the Technician needs to use Voice command like "Open CAD" or "Open Blueprint".
2. The Asset Hierarchy would be visible to the Technician.
3. Technician see's the documentation dashboard and listed blueprint/CAD documents
4. Some of the most frequent failure types can be shown with the CAD drawing. Because we are narrowing the culprits. Showing "common issues"
5. Technician is able to drill into the documents, zoom into the CAD/Blueprint files to find the item they are looking for. Voice command is critical here.
*Design Note: Focus on the user - "Safety First" on how they will be viewing/using this feature while in the factory.
04) Request Help
The Technician is unable to find or solve the problem OR they need immediate help "SOS"
1. The Technician asks for help - voice command
2. Provide an ability to ask for help - it can be done via two ways:
Find Expert
- Find the expert directly is available in the system via the collaboration tool database.
- Show the list of Experts and see their profile before connecting to them
- Find Experts algorithm should be based on (Skill + Location + Availability + Rating + Cost Per Hour + Experience with the Asset or similar problem classes).
- No need to show Experts who are not available (no use for that).
- A Technician might select a different expert if they know that expert will be available in an hour (so reasonable availability).
- Most important is, the Experts should have status 'has worked on this machine before'
- The Technician, with the help of Nerve Center or Choose the Expert directly, will be able to setup a 'collaboration session' with the selected Expert to get the problem fixed
SOS Alert
- Send SOS to the Nerve Center so they can analyze the problem and find a solution from the Nerve Center base knowledge or put in a request to an Expert.
05) Technician & Experts Collaboration
- We want to capture the flow of how the Technician and Experts are collaborating.
*Design Note: Keep the names, assets, expert consistent throughout your screens
- In the 'collaboration session' provide a feature that if the recording has not started yet (Technician does not activate the features when he starts doing the assignment), the Tool will record the call automatically to create an archive/transcript that will be saved and sent to the Nerve Center for future improvements.
Technician (Glasses)
1. Technician (no need to see the Experts face) - has to see what the Experts is seeing on the screen - However, if necessary, Technician should also able to call "show me expert" to pull up the video of the expert, maybe the expert needs to show a part
2. Show conversation features between Technician and Alex - Real Time Voice Translation (show audio and text translation)
3. Show the collaboration tool "AR" where they are working together to view a 3D diagram of the machine.
4. Show the collaboration tool where the Expert is drawing and pointing on the screen, Expert is coding/making updates to the Asset, sharing documents.
5. Show the issues being resolved where Technician provides verbal feedback/notes on the issues and what was solved. (These notes and video show up later in the support areas)
Experts (Tablet)
*Challenge Note: the priority in this challenge is Technician flow (and interactions with the Expert). Look to refine the Glasses view as much as possible.
1. The Experts will be able to login and see his dashboard via tablet device
- The Experts should be able to see missed calls and ability to called back
2. Experts should be able to perform this Asset Maintenance/Fixing Attempts from his tablet (and Technician can see it):
- Get pictures/video of the asset - Need to see more than 1 side of an asset at the same time.
- See Blueprints, CAD, 3D images
- The ability to upload the Asset schematic and then the Technician can see it (blueprint, image of a part, instruction manual, etc)
- Show Asset Details Information (See sensor readings, filter, sort - See asset hierarchy - See 3D CAD models of the components of the asset hierarchy)
- Ability to Remote Connect to the Machines - Remote access to machine CLI or Remote access to a laptop with access to machine CLI
- Show Suggestions (from the Nerve Center)
- Read the Asset manual document
- Follow the available module to fix issue (based on log history or from maintenance work instructions)
- Drawing on the screen by the Expert - including Drag and drop to the Technician video/screen
- Upload video
- Show previous incident reports (See maintenance/repair history)
- Capture WO wrap up questions: Captured verbally by both the Technician and the Expert
Multiple Experts Scenario, needs to provide collaboration session to be elaborated with screen sharing, 2 Experts + 1 Technician, remote access to machine CLI - If for some reason, the current Experts can't solve the Asset problem (less knowledge, called disconnected, etc), Technician can request another Experts to join the call and collaborate to fix the Asset problems (so the other experts can learn too)
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/comment this link while you upload).
Video References
- Real Time Voice Translation: https://www.youtube.com/watch?v=oQVQVt5H2QM
- How Voice Control Works in glasses: https://www.youtube.com/watch?v=T5ddPN7a9fk
- Sample video of Collaboration between Technician and Expert: https://www.youtube.com/watch?v=Mvjf8VOKZy4
- RealWear Glasses demo:
-- https://www.realwear.com/rw/hmt-1-featured-in-honeywell-video/
-- https://www.youtube.com/watch?v=kGBgBFkQuFE
-- https://iqagent.com/realwear/
-- https://www.youtube.com/watch?v=RNW842zldlo
Previous RUX Design
- We are providing the screen designs from the previous RUX
- Use them as inspiration for where we want to continue to evolve the UI
- Color is very important! Clarity of data is very important!
Branding Guidelines
- We would like you to continue to evolve the UI leveraging the previous 1st place design and also the designs from the Nerve Center RUX. This is an evolution.
- The designs do need to work in an "enterprise setting" so do not go too crazy with the star trek/futuristic fonts! See more details in the Forum.
- Think about target users and type of devices that they will be wearing (glasses and tablet)
- Avoid contrasts that are too hard and too light
- Modern UI's are okay and now we are refining the "look" even more! This is conceptual..so color, icons, the voice services (control and translation) is critical to helping the user quickly get answers.
Documentation
Download all documentation from the challenge forum!
- Design Direction and Wireframe (RUX51-Reference-Files)
- Complex-Assets.png
- Branding Guidelines Document
- Previous RUX Winners as Reference (RUX Collaboration Tool Source Files)
- Plant and Machine Images References (Use these as images for the plant and machines in your design)
Target Devices
AR Glasses and Tablet - 1024px width and 600px height:
- Factory Maintenance Technician: Horizontal/Landscape using voice/sound interaction (Glasses)
- Machine/Technical experts: Landscape or Portrait - Open to any suggestion (tablet)
- Use grid systems for your layout
Target Audiences
- Factory Maintenance Technician
- Machine/Technical experts
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 the 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, Illustrator, XD or Sketch and saved as editable layer
Final Fixes
This RUX might have final fixes
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.