Johnson Controls, Inc. and Human Computer Interface Ranjeeta Singh - - PowerPoint PPT Presentation

johnson controls inc and human computer interface
SMART_READER_LITE
LIVE PREVIEW

Johnson Controls, Inc. and Human Computer Interface Ranjeeta Singh - - PowerPoint PPT Presentation

Johnson Controls, Inc. and Human Computer Interface Johnson Controls, Inc. and Human Computer Interface Ranjeeta Singh User Experience Group Human Computer Interface (HCI) Definition


slide-1
SLIDE 1

Johnson Controls, Inc. and Human Computer Interface

Johnson Controls, Inc. and Human Computer Interface

Ranjeeta Singh User Experience Group

slide-2
SLIDE 2

Human Computer Interface (HCI) Definition

  • !

"#$ %# %&'$( )#% *&+ !,#

Human Computer Interface at Johnson Controls 2

!,# %%#- .& /% (%% !- !." %"-%%." &01

slide-3
SLIDE 3

Human Computer Interface (HCI) Definition Human Computer Interaction/Interface – A Combination of Science and Art

Science

(Objectivity)

Art

(Subjectivity) “Efficient Job Functions”

Human Computer Interface at Johnson Controls 3

(Objectivity) (Subjectivity)

Applies research findings from behavioral and Computer Sciences Leverages observation and testing Methodologies Incorporates data gathering and analysis techniques Aesthetics Users feelings and emotions

Stove Example

slide-4
SLIDE 4

Human Computer Interface (HCI) Definition Human Computer Interaction/Interface – A Combination of Science and Art

Similar Terminologies

HMI (Human Machine Interface)

Human Computer Interface at Johnson Controls 4

MMI (Man-Machine Interface) UCD (User Centered Design) Usability User-Friendly Human Factors

slide-5
SLIDE 5

Acronyms

UI User Interface UX User Experience JCI Johnson Controls, Inc BAS Building Automation System Project vs. Product

Human Computer Interface at Johnson Controls 5

slide-6
SLIDE 6

Johnson Controls, Building Efficiency Products

Johnson Controls Product References:

  • 1. Building Management Product(s)

Used to monitor and control the mechanical, lighting, security, and safety of a building (or more) and individuals within the building. Application running in a browser. Mouse driven.

  • 2. Chiller Management Product

Human Computer Interface at Johnson Controls 6

  • 2. Chiller Management Product
  • Used to monitor and control chillers.
  • Application running on a specific hardware.
  • Touch-screen driven.
slide-7
SLIDE 7

Building Management Product Pictures

Human Computer Interface at Johnson Controls 7

slide-8
SLIDE 8

Automotive Experience

Automotive Group shared with us their “Best Business Practice”. We tailored the process to best fit our needs.

Human Computer Interface at Johnson Controls 8

slide-9
SLIDE 9

JCI Requirements

Business Requirements System Requirements Notes: Requirements are written in a way so they can be traced back to a business requirement. Write requirements specific to its level, this reduces re-work and inspections.

Marketing / Program Management System Engineering

Human Computer Interface at Johnson Controls 9

Software Requirements Design Requirements

System Engineering, Engineering Owners Sub-system engineering

slide-10
SLIDE 10

Work closely with …

Legal Marketing Development Tools Organizational Need executive champion

Human Computer Interface at Johnson Controls 10

slide-11
SLIDE 11

Understand …

Before the HCI team starts on this study you should know a few things about the project:

Business and System requirements. Identify a group of people that represent the customer.

  • A set of individuals that may include actual customers and/or can clearly represent the customers.
  • Used to understand the existing product and how to make improvements.

Human Computer Interface at Johnson Controls 11

  • Not used to discuss details of the UI.
slide-12
SLIDE 12

Grasp …

Understand the high level goal of the project. Understand the customer(s). Understand the user(s).

Note: Customers are not the same as users.

Understand constraints.

Human Computer Interface at Johnson Controls 12

Define/Follow templates (for consistency and guidelines).

Is it a new project? Adding capabilities to an existing project?

slide-13
SLIDE 13

Gather Input Data

Understand existing products. Get familiar with existing product known issues. Gather competitive analysis. Get familiar with user(s). Is there one or more types of users. “Day In the Life”.

Human Computer Interface at Johnson Controls 13

slide-14
SLIDE 14

Build …

Personas

  • Represent a user type for a product.
  • Create a ‘complete’ persona for each user type.
  • Used in conjunction with use cases.

Human Computer Interface at Johnson Controls 14

Use Cases

  • Used to describe the system behavior from a user’s perspective.
  • Describe the most important usage of the product.
  • Why would the user interact with the system and what they expect?
  • Identify the “Today” vs. “Tomorrow/Future”
slide-15
SLIDE 15

Use Case Example

Situation: The monthly staff meeting at Liberty School was held, as usual, in the library from 4:00 PM until 5:00 PM. The schedule for the library includes exceptions to the lighting and HVAC schedules, to keep the area comfortable and well-lit for the meeting. At 4:02 PM, however, Maintenance Max receive an urgent page from Principal Polly - the lights in the library are off! Today: Max logs into Metasys. He selects the Lighting navigation tree and opens the Schedules folder. He drags the Library schedule into the display panel. The Schedule's value shows "1" (which he knows from experience means "Occupied") as expected, so the lights should be

  • n. Max goes back to the Lighting navigation tree and double-clicks the Lighting BOs folder to display its summary view in the display
  • panel. He scans the summary view looking for a point labeled LTG-LIB (he knows from experience that this is the binary output associated

with the Library lights). He sees the point, and also sees that it is controlled by an Operator Override. He opens the Commands for the point, and releases the operator override, thereby relinquishing control to the schedule. The summary view updates a few moments later to indicate that the lights are now On.

Human Computer Interface at Johnson Controls 15

indicate that the lights are now On. Future: Max logs into Metasys. He clicks on the Schedules icon and is presented with a list of schedules and the building areas they affect (floor plan?). He clicks on Library. The UI displays a scheduling view for the library. The view indicates that the Library is currently Occupied, and that the lights are scheduled to be On. The view also indicates that the current state of the lights (Off) does not match the expected state (On), and that the lights are currently controlled by an Operator Override. Max clicks to expand the details for the Lighting BO, and sees it was overridden at 2:30 PM by the Librarian, who left early that day. He right-clicks on the point and selects the Release Operator Override

  • ption, thereby relinquishing control to the schedule. The scheduling view updates to reflect that the current state of the lights now matches

the expected state of On.

If time allows, build a workflow in block diagrams

slide-16
SLIDE 16

Usability Goals

Identify the Usability Goals for your user(s):

1. Intuitive

Users require no or little explanation to understand what is presented in the screens. Either because of previous product knowledge or by the design of the product’s user interface.

2. Effectiveness

Users require little training to successfully accomplish their tasks.

3. Usefulness

Human Computer Interface at Johnson Controls 16

3. Usefulness

Users accomplish all of their tasks as product contains a complete set of features and capabilities.

4. Learnability

Users are effective with the product even when used infrequently, and with limited training.

5. Appeal

Users enjoy using the product as screens are visually pleasing and graphics are professionally designed.

slide-17
SLIDE 17

Usability Goals Examples

(

  • (

2 % ! %2 + (2

  • +

3 4 4 4 5 5 5 + 4 3 6 5 6 6 6 & 7 7 7 7 7 7 7 8 5 6 5 6 4 4 4

Human Computer Interface at Johnson Controls 17

!%% 6 5 3 3 3 3 3

slide-18
SLIDE 18

User Interface Design Starts …

User Interface design follows the following process:

  • 1. Navigation:
  • Most important when designing a UI. It is the foundation.
  • A bad navigation product creates frustration.
  • Defines the Information Architecture. Broad and Shallow vs. Narrow and Deep.
  • 2. Presentation
  • Layout
  • Color

Human Computer Interface at Johnson Controls 18

  • Graphics
  • Text
  • 3. Content
  • Clear Writing.
  • Include methods to improve scanning.
  • Persuasion, emotion, and Trust (PET).
  • 4. Interaction
  • User interface controls (widgets).
  • Error handling and feedback.
slide-19
SLIDE 19

Navigation

Common Navigation Models

Hierarchal, Drill Down

Single Level Multi Level Not common

Sequential

Forms Wizard, tutorial, or training.

Enhance with:

  • Global
  • Breadcrumbs
  • Rollovers and

cascading menus

  • Secondary windows
  • Quick Links

Human Computer Interface at Johnson Controls 19

Wizard, tutorial, or training.

Persistent

Button menu Notebook menu

Menus

List menus

Search Engine

Query Results

slide-20
SLIDE 20

Presentation

Higher color contrasts attracts user attention quickly. Use of colors and saturation can guide users into a path. Brain fills in the gap of graphics and creates its own image. Text size and case makes you process at different speeds.

Human Computer Interface at Johnson Controls 20

slide-21
SLIDE 21

Presentation

Font Size (9 Font Size

x / x x / x

Do all text below use the same font size?

Human Computer Interface at Johnson Controls 21

Font Size

  • x
  • x
slide-22
SLIDE 22

Interaction Factors that influence interaction design.

Effective visual hinting shows available options. Invite without requiring a mouse over action. For example, enabled/disabled, selected/unselected, linkable/static.

Human Computer Interface at Johnson Controls 22

Graphic states: normal, disabled, depressed. Simple mouse interactions vs. complex pointing device interactions. For complex there is no universal standard to provide visual indication. OK for certain users. Does page have sufficient cues? Is interaction intuitive? Is it easy to perform? Do all interactions work elegantly together? Are UI controls appropriate? Are feedback meaningful and useful?

slide-23
SLIDE 23

Other Software Design Steps

Document the Design Implement the Design Test & Verify the Design and Implementation Note: Some re-design may be required.

Human Computer Interface at Johnson Controls 23

Work independently but share key information at intervals between engineering groups!

slide-24
SLIDE 24

Accessibility and Internationalization

Directly relate to software design

Accessibility Requirements Internationalization Requirements Unicode / UTF Fonts

Human Computer Interface at Johnson Controls 24

Bold Italic

slide-25
SLIDE 25

HCI Methods

Methods used during an HCI Study:

  • Heuristic Reviews
  • “Day in the Life”
  • Types of prototypes (pros and cons)
  • Usability Study

Human Computer Interface at Johnson Controls 25

  • Usability Study
  • Satisfaction Surveys
slide-26
SLIDE 26

Prototypes

There are different goals/outputs for the two used prototypes

Paper Prototype

  • Used to verify layout, presentation, and labels.
  • People won’t get hung-up on size, colors, fonts, etc.

Human Computer Interface at Johnson Controls 26

Electronic Prototype

  • Used for behavior.
  • Be careful with colors/fonts.
  • Have accurate data.
slide-27
SLIDE 27

Prototypes Prototype Fidelity

Low Fidelity:

Identifies show stoppers Navigation scheme Labeling Good time to critique by customers and developers.

Human Computer Interface at Johnson Controls 27

Good time to critique by customers and developers.

High Fidelity:

Include more depth and breadth of features and is interactive. Validates mental models, navigation, detailed design issues, interactions, graphics, etc.

slide-28
SLIDE 28

The End

Q & A

Human Computer Interface at Johnson Controls 28

Q & A