Zephyr - eMOC App Desktop Wireframe Challenge

Welcome to the Zephyr - eMOC App Desktop Wireframe Challenge!

Zephyr is a fortune 500 industrial gas company that operates chemical manufacturing facilities throughout the world.  From time to time we need to make changes to the different aspects of the manufacturing processes at these facilities.  As you can imagine it is very important that these changes be managed through a very disciplined approach and enforce certain business rules because mistakes in the Management of Change process could have catastrophic effects.   These changes could be as simple as updating a site specific operating procedure to a adding addition equipment such as compressors, pumps or electrical components.  The more complex the change, (Level 1 change is the highest) the greater amount of additional actions and contributor’s (people) that will be involved in the change process.  We currently are working with a paper process and are looking to change to a web based application that will allow us to enforce business rules and eventually conduct some data mining to understand how we can make this process better.

In this challenge, we are looking for wireframe (Axure) solutions based on requirements below. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

It’s critical to think about a clean user experience for desktop view.

Round 1

Submit the following for Checkpoint feedback:
0. Feedback Tab.
1. Landing page.
3. Create MOC Screen.
Notes.jpg: Any comments about your design for the Client.

Round 2

Final wireframe plus any Checkpoint feedback:
0. Feedback Tab.
1. Landing page.
2. My MOC’s Page.
3. Create MOC Screen.
Notes.jpg: Any comments about your design for the Client.

Challenge Details:
Proposed Concept:  We like the look and feel of the Turbo Tax Program.  Our vision is that when the MOC Initiator clicks the “Create New MOC” Link it will start a Turbo Tax like process where information is collected from the initiator in subsequent screens.  We propose that it starts with basic information which is detailed below and move through the other screens.  All of the this information will eventually be used to determine the ultimate workflow for the MOC records.  We will use built in editable business rules to determine the MOC Level and which “Technical Reviewer Roles” will be required for an MOC.  A more detailed explanation follows later on in this document.

What is a MOC?
Please read this link to understand what is a MOC: http://www.gatewaygroup.com/management-of-change/

Also please read Additional MOC Information document to have a basic understanding of what we are trying to build here.

Note: Please understand that although we are presenting a concept to you we would like you to feel free to use your creativity and experience to recommend different approaches / ideas to our project.

Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in required new sections below, if any requirement is missing in final submission the client will not take a look at it, so make a checklist for the required
screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

Supporting Documents:
- Client mockups (Screenshots.zip).
- MOC Additional Information (Additional MOC Information.doc)
- Create MOC Process (Create MOC Process)
- eMOC Flow Diagram (eMOC Flow Diagram.pdf).

Screen Size:
- Desktop: size of 1024px width and height as required.

Design Requirements:
0. Feedback Tab:
Please refer to feedback_expanded.png & feedback.png screenshots
- Available from every page on left side (feedback.png).
- When users click on this tab, a small page appears with the following information: (feedback_expanded.png)
Fields:
- Name - automatically populated based on single sign on.���
- Business - Drop down selection - 3 choices USIG, US Hydrogen, Praxair Canada.
- Feedback - Comments field.
- ���Submit and Cancel buttons at bottom.
When users hit submit 2 emails will automatically be generated:
1) Email to person giving feedback thanking them for their feedback and letting them know that feedback is important if we are going to improve the process and their experience.
2) Emails to all users listed as administrators for that business informing them that someone has left feedback.

1. Landing page:
- Splash page will be the first page that everyone comes to when trying to access the Zephyr eMOC site.
- Left hand side will be a navigation bar that will be editable by administrators (Very similar to share Point sites).
- Pre-populated navigation Links:
-- Request Access to eMOC site.
-- My MOC's - When clicked will take user to "My MOC Page".
-- All MOC's - Take users to a list of all MOC's for all three businesses.
-- Create MOC - When clicked will open up "Create MOC Screen.
-- Reports - Need to understand what reports we will want pre-populated.
- Ability to add announcements to the screen as things change with the program or updates are made to inform our users.

2. My MOC’s Page
Please refer to tracking_example.png screenshot
- We envision a page that displays the information that is important to the current user.  We think that it would be important for a list of all of the MOC’s that the current users has a role in that are still open.  We would also like a feature like Facebook uses that would allow a user to add an MOC to their My MOC view even if they do not have a defined role because sometimes an employee might want to keep track of a particular MOC for some reason.  We would also like to have the ability for our users to track all of their open action items.  In the attached screenshot (tracking_example.png) a user can keep track of all of their action item and also see if any are past due.  We would also like the ability to be able to click on the numbers bars below to generate a list of those action items.
- We are open to your suggestions here.

3. Create MOC Screen
- Please refer to Create MOC Process document.

Target Users:
There are 8 roles associated with this project.  They are defined as:
1- MOC Initiator – Person initiating the process. The initiator may be the person who enters all information prior to technical review and comment or, the MOC may be more fully developed by the “MOC Lead” prior to distribution for technical review and approval.

2-���MOC Lead – The individual who takes the lead in defining the detailed scope, enters required information in the eMOC tool, and pulls together all of the supporting documentation.���This person can be the MOC Initiator someone else who is selected by the Approving Manager in the MOC Initiation Phase.���

3- Approving Manager – This is typically the manager of the facility where the change is taking place.

4- Technical Reviewer – These are the subject matter experts (SME’s) who we assign to technically review the MOC Record (Multiple persons), for their respective discipline. We will populate a list on this site (or within the eMOC framework) that can be edited only by the administrator and we will use in the program to only allow our users to pick the people assigned the roles in the list. A limit to list type option. We will explain this concept in more detail in the Create New MOC section of this document.

5- Area Director – Only required for an “Emergency Change” Type. Area Directors are responsible for approving subject matter experts to serve as technical reviewers. Therefore, they have permission to edit the technical reviewers list/table.���

6- Additional Editor – These are people listed in the Praxair address book who may not be a required part of the process, but we want them to have the ability to edit the content of an MOC record.

7- Administrator – This is the person who will make changes to the workflows for their business.

8- Management Representative - This is a required role for the Pre-Startup Safety Review MOC Phase and is selected by the MOC Lead when he picks his technical reviewers.

Judging Criteria:
- How well you translate the requirements into an attractive and usable design.
- Cleanliness of your graphics and design.
- Design and User Experience.

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
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.