Swiss Post - Platane Resource Planning Tool Design Challenge

Welcome to the Swiss Post – Platane Resource Planning Tool Design Challenge! In this challenge we are looking to design a web-based resource-planning tool called Platane, a resource here means an employee with his work capacity.

In Platane an employee can be reserved for a particular project, also Platane collects from Outlook the absences of the employees and collects from Jira the assigned tasks for the employees. With an optimizing-algorithm, Platane calculates the optimal work-order of the tasks and the workload of the employees.

Round 1

Submit your design for a Checkpoint feedback:

0. Navigation.
1. Login.
2. View Employee.
3. View Team.
4. View Project.
5. Make Project Reservation.
6. Add Resources.
- 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:
0. Navigation.
1. Login.
2. View Employee.
3. View Team.
4. View Project.
5. Make Project Reservation.
6. Add Resources.
7. Create Manual Task.
8. Maintain Public Holidays.
9. View Outlook Absence.
10. View Jira Task.
- 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:
In this challenge we need to design the new pages for Platane the web based resource planning tool, The tool will allow team leader (Administrator) to assign employees (Resource) onto projects, and employee (Resource) to find out what projects they are on.
This tool will have 2 main users:
1- Employee (Resource):
- Watches his personal workload and the order of the task he has to work on.
2- Team leader (Administrator)���:
- Watches the workload of the unit, team and employees. Makes reservations of an employee for a particular project.

We are looking for the [topcoder] design Community to help us with planning our new "user experience" (UX).

Branding Guidelines:
For the sake of the best visualization there are no branding requirements.

Design Considerations:
- Consistency across the pages is Very Important.
- Need a very clean look, professional and slick.
- The final application is using the Bootstrap 3 Framework!
- This does not mean you need to understand everything about how Bootstrap 3 works, but just being aware of how good design goes with the framework.

General Guidelines:
There are many aspects of the web page for which we are looking for YOU to exercise your creativity.  These include:
- Exact layout of the elements.
- Look and feel of the different elements.
- Consistent use of colors to act as visual cues.

Screen Sizes:
- Desktop: 1440px width and height as required.

Supporting Documents:
- You can use Swiss Post logo (Swiss Post Logo.zip).
- Platane Requirements (Platane-business-requirements_V01.01.pdf), several screenshots / GUI-mockups are displayed in this document. This should help to understand what the application should do and which information should be displayed. The real implementation can slightly differ from this GUI-mockups and we are appreciate better solutions. We say very little about the user-navigation so you are free to implement a modern and user-friendly navigation.

Required Screens:
0. Navigation:
- How does the user navigate this app?
- Include navigation that you think fits with this app.
- Focus on the priority items and how things should be sized.

1. Login:
- User logs in to the application using his username and password.
- Please show validation error message.

2. View Employee:
- Please refer Platane Requirements Document Section 3.1.1
- The User shall execute a planning activity of his project works.
- Scenarios:
-- View task of user.
-- Add new task for user.
-- Update task for user.
-- Delete task from system.
- Please refer to 3.1.1.1 section for Graphical User Interface.
- Please refer to 3.1.1.2 section for Requirements.

3. View Team:
- Please refer Platane Requirements Document Section 3.1.2
- The User may get the planning view of a team.
- Scenarios:
-- View user of a team.
- Please refer to 3.1.2.1 section for Graphical User Interface.
- Please refer to 3.1.2.2 section for Requirements.

4. View Project:
- Please refer Platane Requirements Document Section 3.1.3
- The User may get the planning view of projects.
- Scenarios:
-- View user of a project.
- Please refer to 3.1.3.1 section for Graphical User Interface.
- Please refer to 3.1.3.2 section for Requirements.

5. Make Project Reservation:
- Please refer Platane Requirements Document Section 3.1.4
- The user shall create, update or delete a “Reservation”.���
- A Reservation is always assigned to one Employee and one Project. See 3.2.
- The Employee can be reserved for a given project during a given time-period for a given load.
-- Example: Employee brownt works on project Platane for 70% from 1.5.2015 to 31.8.2015.
- As additional information a Reservation has this attributes:
-- Name: some short display-name.
-- Description: some optional longer description.
-- Priority: [high, normal, low].
-- Reliability: [sure, probable, maybe].
- Please refer to 3.1.4.1 section for Requirements.

6. Add Resource:
- Please refer Platane Requirements Document Section 3.1.5
- The User may execute the allocation of resources within the System.
- Scenarios:
-- New resource into the system.
-- Delete resource from system.
- Please refer to 3.1.5.1 section for Graphical User Interface.
- Please refer to 3.1.5.2 section for Requirements.

7. Create Manual Task:
- Please refer Platane Requirements Document Section 3.1.6
- The User may execute the allocation of a project and tasks.
- Scenarios:
-- New project/task for a user/team.
-- Update project/task for a user/team.
-- Delete project/task from system.
- Please refer to 3.1.6.1 section for Graphical User Interface.
- Please refer to 3.1.6.2 section for Requirements.

8. Maintain Public Holidays:
- Please refer Platane Requirements Document Section 3.1.7
- The Administrator shall setup the public holiday for resources considering their locations.
- This use case includes the scenarios:
-- Add new public holiday.
-- Update / delete public holiday.
-- If not existing, add new location.
- Please refer to 3.1.7.1 section for Graphical User Interface.

9. View Outlook Absence:
- Please refer Platane Requirements Document Section 3.1.8
- The User may get a list of Outlook (task) absences.
- Scenarios:
-- View (task) absences of a user.
- Please refer to 3.1.8.1 section for Graphical User Interface.
- Please refer to 3.1.8.2 section for Requirements.

10. View Jira Task:
- Please refer Platane Requirements Document Section 3.1.9
- The User may get a list of Jira tasks.
- Scenarios:
-- View jira task of a user.
-- View jira all task of all user.
- Please refer to 3.1.9.1 section for Graphical User Interface.
- Please refer to 3.1.9.2 section for Requirements.

General Design Requirment:
- The user will use CRUD dialogs (CRUD stands for create, read, update and delete) to maintain:
-- Unit.
-- Team.
-- Resources (Employees).
-- Working Place.
-- Public holidays (a special case of absence) and adding new locations.
-- Reservation.
-- Manual Projects.
-- ManualTasks.
- We need a button or link to trigger the sync between Jira and Exchange server.
- The business-organization is structured in a tree. Parent is a recursive unit-structure. A unit can have several teams. The team can have several employees.
- A unit can contain other units and/or team(s).
- Please refer Platane Requirements Document Section 3.2
- An employee has a pensum. The pensum is a float [0 – 1]. 1 means the employee works 100% (full-time- job). This is from Monday – Friday, 8 hours per day. 0.8 means the employee would work 80% (four days per week). The default is 1. The pensum is in fact the load of the capacity.
- An employee can have several constraints. This can be an absence, a capacity and a reservation:
-- The absence can be attached directly to the employee, e.g. his holidays.
--- This absences are imported from the Exchange-Server.
-- The absence can also be a public holiday for the given working-place of the employee:
--- E.g. 25.12 – 26.12 is public holiday in the city of Berne.
--- Public holidays are maintained in Platane (and not imported from Exchange-Server).
-- A reservation belongs to a project:
--- E. g. Employee brownt works from 1.3.2015 – 30.4.2015 for project Proj-X for 50% (load of reservation is 0.5, which means that the employee works 2.5 days per week for this project). For the other 50% brownt works for project Proj-Y���.
--- Even for the same project an employee can have more than one reservation.
---- E. g. brownt works from 1.5.2015 – 31.8.2015 for 100% (load 1) for project Proj-X.
- A task is some kind of work, which have to be executed by an employee. A task can either be imported from Jira or can be manually created in Platane.
-- Usually a task belongs to a project. However, it’s possible to have tasks, which are not linked to a project.
-- A Jira-Task belongs to a Jira-Project:
--- E. g. The task PLAT-104 belongs to the Jira-Project PLAT.
-- More than one Jira-Project can belong to a project:
--- E. g. Jira-Projects FOO and BAR belongs to the project Proj-Z.

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.

Target User:
- Project Team Leaders and Resources working on projects.

Judging Criteria:
- How well you plan the user experience and capture your ideas visually.
- Cleanliness of your graphics and design.
- Creativity and ease-of-use is key to the success as it must be engaging to users.

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.