Plant Performance Monitor

Goal Define an interaction model that depicts the basic framework for how App will behave. Define its high level information architecture.

Task illustrated Working hypotheses for App design App information architecture definition Interaction model Demonstrating cross section of the interaction model with task flows

Working hypotheses for App design

App adapts to usersJob title does not define role, so let users configure their setup to meet their needs.

Configuration, not customizationApp should be easy to set up, and provide limited but sufficient configuration options.

Provide a continuous experienceThe system adapts to users, enabling them to pick up where they left off. Applications within the App suite acknowledge each other.

Make the important obviousHighlight important information to help users prioritize information and aid decision-making.

Information Architecture Definitions

ModuleGrouping of applications related to a particular set of goals and needs. Included as primary navigation element for users.

ApplicationA self-contained toolset—grouped by particular user activities—that users access within a module and provides them with specific features and content.

FeatureSpecific component within an application that allows users to fulfill a task or view desired content.

Interaction Model

Screen Components (working hypotheses)

Global Navigation

Global navigation exists across all screens in App, enabling quick access to any application from anywhere in the suite. Rolling over a module reveals a drop-down containing all of the applications within the module.

Reflects the need to nimbly respond to changes by enabling quick navigation to appropriate App features.

Global Navigation

App LogoApp Logo

Dashboard

The Dashboard contains quick summaries of specific features and components selected by the user to provide a unique overview of App. Users add items to the Dashboard by pinning individual features within an application, or by choosing from a set of dashboard components.

Reflects the need to see the whole picture from the user’s perspective.

Dashboard

App LogoApp Logo

Alerts Panel

The Alerts panel exists in a minimized state at the bottom of all App screens, and contain both alarms and alerts sequenced by time.

Clicking on an alert switches the main view to reflect a relevant application or feature within App. Helps the user be more proactive.

Alerts Panel

App LogoApp Logo

Saved States

Saved States are snapshots of the application state that enable users to quickly reconfigure App to a preferred configuration.

Tear off components

Tear off components retain a parent-child relationship with the main screen and do not display global navigational elements.

Saved States

App LogoApp Logo

Filter Panel

The filter panel exists in the top-right of App screens. Settings chosen in the filter panel affect all applications and features. Users can choose to lock specific features so they are decoupled from the filter settings, making it easy to compare different assets or data types.

Reflects the need for short learning curves and ease of use. Filters behave in a consistent and predictable manner across all of App, while enabling custom configurations for detailed investigation as needed.

Filter Panel

App LogoApp Logo

Demonstrating interaction model using task flows

Flow 1

Signing in & Configuring the Dashboard

Flow 2

Drilling Down into the Benchmarking Tool

Asset Manager

Tasks

Responsible for lifecycle costs,has a need for total visibility. Seeks availability, reliability, & performance.

Mantras:Focus on Future CostsSee the Whole PictureMake Long-Term ProjectionsBalance Cost vs. Risk

Flow 1

Signing in & Configuring the Dashboard

John the Asset Manager is new to the App and is logging in for the first time. He locates the Log In button on the external Login page.

1

2

Flow 1.0 – App Login (external)

Login PageLogin Page

John enters his credentials in the Single Sign On page.

John acknowledges the legal agreement and continues on to App.

Flow 1.2 – Legal Agreement

Because this is the first time John has logged in, he is presented with the First Visit Welcome screen. He scans the various call-outs and decides to follow the call to action to set up his dashboard.

One challenge that users currently face is applications that require involved configuration and steep learning curves before users can derive value from them. The first visit welcome screen points out major functionality and provides a call to action, ensuring that new users are able to quickly ramp up and get immediate value out of the box.

Flow 1.3 – First Visit Welcome Screen

App LogoApp Logo

John enters the dashboard configuration screen, and browses through the selection of dashboard components. He sees a few that seem interesting, and adds them to his dashboard. When he’s finished adding components, he clicks Done.

Because job titles do not define roles, each user will come to the App with unique needs that App cannot come preconfigured to address. Configuring the dashboard as a first step quickly surfaces the breadth of offerings, making it more likely that users will find App offerings which are relevant to them.

Flow 1.4 – Configuring the Dashboard

App LogoApp Logo

John returns to the dashboard, which is now populated with the components he selected. The configurable dashboard provides a familiar and relevant landing page, ensuring users see exactly what they need upon entering.

Flow 1.5 – Configured Dashboard

App LogoApp Logo

Flow 2

Drilling Down into the Benchmarking Tool

John the Asset Manager begins his day by opening the App and landing on the Dashboard, which he has configured to provide him with an overview of key fleet metrics.

Flow 2.0 – Viewing the Dashboard

App LogoApp Logo

John is interested in reviewing the latest statistics about his fleets’ starts, so he decides to launch the Starts Analysis application.

John clicks on Operational Excellence in the Global Navigation to navigate to the Starts Analysis application.

Flow 2.1 – Navigating to Starts Analysis Application

App LogoApp LogoApp LogoApp Logo

The initial view of the Starts Analysis application provides John with an overview of key benchmarks. John wants to investigate his fleet’s startup reliability in further detail, so he clicks into the visualization to drill down to the Site Startup Reliability feature.

Clicking on a visualization within an application drills down into the associated feature. The visualization at the application level is meant to provide more detail than what’s provided at the dashboard level, but still present information for consumption rather than manipulation. To manipulate the visualization, users must click into the feature.

Flow 2.2 – View Starts Analysis Application

App LogoApp Logo

John’s first view in the Startup Reliability feature is of the same visualization plus additional controls enabling him to manipulate the data viewed to aid his investigations.

When viewing a feature, breadcrumbs at the top of the screen provide navigation back to the application layer. Global navigation provides the means to quickly navigate to other applications. The panel on the side of the visualization enables John to tear off the component into another window, pin the component to the dashboard, use the lock to control whether the component is affected by global filters, print, save, or mail the data, and access help.

Flow 2.3 – View Startup Reliability Feature

App LogoApp Logo

GE Confidential

Thank you.