Styx - Gator Fire Management System UI Design Concepts Challenge - Part 2

Welcome to Styx - Gator Fire Management System UI Design Concepts Challenge - Part 2. In this challenge, styx is looking to create designs for a new fire enterprise management application that will run on device with touch screen - this will allow styx’s customers to manage fire management system.

We already had completed an initial challenge that defined the basic design direction for the screens and are looking for you to follow the design styles!

This application helps perform these below important functionalities:
- The UI provides a facility to assist in the installation, troubleshooting and maintenance of the system. For example, it provides a number of reports such status history (history of when events or operations occurred on the system), current status and diagnostics information.
- The UI also provides a mechanism for users to take control of the system. For example, silencing the bells or horns or selecting areas of the system for paging. This type of control typically will be used during emergency situation. However, there are times where the UI is used during non-emergency situations such as testing.
- The UI also provides a facility to assist in the testing of the system. For example, it provides a mechanism to disable portions of the system while testing is occurring (“to prevent the fire trucks from rolling”)
- Unlike other UI’s (i.e., cell phones), the fire system UI is NOT often used once the system is installed and only authorized users (that are trained on the system) are permitted to use the UI.

In this challenge, we are looking for DESIGN CONCEPTS on how this Application could work. What should the user see and experience when using the application!

Round 1

Submit your initial designs for Checkpoint Feedback

1) Creating Reports
2) Paging Application

Feel free to add any other additional screens which are necessary to explain your concept.
Notes.jpg: Please note any comments about your design for the Client
Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

Round 2

Your Final designs for all the required designs with all Checkpoint Feedback implemented.

1) Creating Reports
2) Paging Application
3) Telephone Application
4) Security Application
5) Update Storyboards

Feel free to add any other additional screens which are necessary to explain your concept.
Notes.jpg: Please note any comments about your design for the Client
Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

The application's UI primary usage is to display the status of the system for users such as first responders (i.e., firemen). For example, the UI provides information such as the number of alarms and their location within the system. 

For this challenge, we are looking for design community’s help in coming up with the initial design concepts based on the given wireframes that would lay the UI design strategy for this application. This is first challenge in the series of challenges that we have planned to run to define the overall designs for this application.

About the LCD Device:
For this challenge, you will be designing screens for this LCD touchable screen and understanding the configuration would really help in coming out with the best possible designs..
- 5.7" VGA with 18 bit color
- 86.4mm wide by 115.2mm tall
- The LCD shall be an 18-bit color touch-screen LCD with a 480x640 resolutions
- Resistive touch screen, Touch screen is capable of gesture recognition for 'swipe' based navigation:    

LED backlight, pwm brightness control
- Configurable brightness: 0%-100% duty cycle on pwm        
- Settings: idle %, user active %, unacknowledged queue entries by queue %, queue entries all acknowledged by queue %
- Delighter: transition backlight brightness at a fixed rate of 200% per second (i.e. from 0% to 100% over 0.5 seconds)

Languages:
- Arabic, Chinese (Traditional & Simplifier), Croatian, Czech, Danish, Dutch, English
- Finnish, Flemish, French, German, Greek, Hebrew, Hungarian, Italian, Korean
- Portuguese, Russian, Slovak, Spanish, Swedish, Turkish
- languages may have several locales resulting in separate translations by locale (i.e. individual English translations in North America, UK, Australia)

The UI will be implemented in QT in a Linux environment
- The creation of custom QT controls is to be minimized. Custom controls would be implemented only to provide required functionality, not for looks of flare.
- No video is played on the LCD. Limited graphic file display is envisioned with support for JPG, GIF, and PNG format

The display must be able to legibly display 2, 4, or 8 life safety events concurrently. The quantity of concurrent events is configurable display by display. The display must be configurable to legibly display 1 life safety event at all times, even when the user is navigating.
- This even is configurable as the earliest, or the most recent, event.
- This operation is configurable by display.
- This operation is selectable for all queues or a subset, at the project level
- The events will be organized into queues in order to present them to emergency responders in a prioritized view. There must be support for at least 10 priority queues.

Design Considerations:
- The interface will be easy and intuitive to navigate.
- Focus on the design being a great user experience, think simple but effective solutions!
- Give importance to the overall layout and think on how a user would interact with the content on the page.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application 
- What should the priority features be?
- How quickly could you find information?
- We would like you have the designs of size 480 x 640 resolutions (portrait).

Required Pages:
For this challenge, we are looking for the below pages to be designed/considered in your concepts (Make sure to follow the design styles from the attached designs)

1) Creating Reports:
Please refer page 11-14 Reports-Mockup.pdf
The user can generate the below reports that can be viewed on the LCD and after ‘preview’ on the LCD can optionally be sent to the printer. There is no need for selection of printer from UI as it is preconfigured using configuration utility ( PC software).
- Status Report (for this challenge, you will be designing screen only for this report - please see page 11 - 14)
- Device maintenance
- History
- Revisions
- Modcom Compliance
- User Privileges

1.1 Status Report: (only this report need to be designed)
This creates a report of off normal points or status of points in  a security partition. The user can choose one of the below to generate the report.
- All Active Points
- Alarm points
- Supervisory points
- Trouble points
- Monitor points
- Test points
- Disabled points
- Output points
- Security points

After selecting one of the above options, user has to provide either three digit panel number or partition from the partition list. (A partition is a group of devices intended to secure a physical area)

2) Paging Application:
Please refer page 17 in Reports-Mockup.pdf
Paging application is to permit rapid selection and paging to the affected areas of the facility. In large facilities, the people affected by an emergency should be instructed to evacuate immediately and people who needs attention should receive alert message.

Selecting the paging application (options in shall display a page with below options to select:
- All Call: Directs the page to all areas of the facility.
- All Call Minus: Directs the page to the areas which are not receiving the pre-recorded EVAC and ALERT tones & messages.
- Page by Phone: Selects the telephone voice line as the paging source
- Page to Evac: Directs the page to the areas which are receiving the pre-recorded EVAC tones & messages.
- Page to Alert: Directs the page to the areas which are receiving the pre-recorded ALERT tones & messages.
- Stairwells: This is site specific areas configured by the user to page tones & messages

3) Telephone Application:
Please refer page 15, 16 in Reports-Mockup.pdf
The telephone application permits the user to talk with the other fire fighter telephone stations that are located throughout the facility. When the telephone application is selected, list of call-ins will be displayed on the LCD. User has to select the call-in to communicate and maximum of 5 simultaneous calls are allowed in the panel network.

The connected calls are always displayed on the top and user can scroll through the unconnected calls.
- Silence Call in: User can silence the buzzer beep due to new incoming new call-in
- Page by phone: This will allow the user taking on the telephone system to make announcements over paging system.

4) Security Application:
Please refer pages 5 - 14 in Security_Mockup.pdf for these screens
Under the security application the user can perform below operations and a valid user level password is needed.

Arming Security partition:            
- Partitions can be armed for “Stay” and "Away".
- Arming to "stay" causes the system to monitor only those devices on the perimeter of the protected area and leaving the user to move freely inside.
- Arming "Away" causes the system to monitor all devices both perimeter and interior.
- User has to select partition "away or stay" displayed at the top and select the partition from the partition list.

Disarming Security partition:
- When the partition is disarmed the system generates disarmed alarm events, except for 24Hr security devices which always generate armed alarm events

Bypass security Device:
- When device is bypassed, the system suppresses the alarm events from that device. The devices can only be bypassed only when the partition is disarmed.

Removing Device Bypass:
- When we remove a bypass from a security device, the system resumes the processing of alarm events.

Manage Users & Previleges:
A security administrator can add/delete users, changes the users password and can modify the access privileges of the user. 

5) Update Storyboards (Needs_update.zip):
- We have a few storyboards from the previous challenge that were not updated with the correct header (menu area), footer and scroll bar! (storyboards.zip has the correct header, footer and scroll bar).

Please see "Needs_update.zip" folder ..these are the images that need to be updates
- 08_Menu.png 
- 10_Controls.png
- 11_Virtual 1.png
- 12_Virtual 2.png
- 13_Virtual 3.png

- Above images need to be updated based on updated storyboards (storyboards.zip).
- Just need to change header (menu area), footer and scroll bar in these images.

Target Audience:
Below are the list of users who will use this application..

First Responder: 
- Either the firemen or someone trained to monitor and control the system during an emergency event.
Installer: The installer installs the system (based on engineering specification) and typically helps in the verification of the system. The installer may also be involved with any future modification of the system.  The installer may also use the system UI to help troubleshoot any installation issues (i.e., wiring problems).
Maintenance personnel: The maintenance personnel may use the system to diagnostics problems (i.e., dirty detector) or help with the testing of the system (drill).
Tester: The tester may use the UI to put the system into a test mode so that they can test various parts of the system to confirm that it is still operating according to spec. 

Judging Criteria:
- How well you plan the user experience and capture your ideas visually
- Cleanliness of your graphics and design
- Your design should possible to build and make sense as an application

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.