EMC CCE iPAD Application

EMC CCE iPAD Application

When skeuomorphism (prior to Apple’s iOS 7 flat design HIG) was still the trend I was consulting to EMC on a great, fun project . The Connected Customer Experience (CCE) 2.0 iPAD project is a new business sponsored initiative to provide data center managers, responsible for EMC equipment, with configuration and capacity intelligence about their products via an iPad Application. The CCE data is used to summarize capacity and configuration information for Symmetrix, Data Domain, and VPLEX systems for capacity planning, tech refresh, and renewal purposes.
ProcessAudienceFeaturesEcoSystemViewsProcess Experience


There are two different users that the application is targeting:

  • Data Center Managers/Directors at existing EMC customers
  • EMC Global Sales Organization (Note: The intent of the branding is toward the end customer, not the EMC organization.)


The EMC CCE App main goal is to quickly answer questions about the EMC systems in the user’s data center:

  1. System Identification: What systems I have, of which EMC product families and how many of each? Where are they?
  2. Storage Capacity: How much total capacity I have on these systems? How much I have left and of what type? When will I run out?
  3. Hardware Configuration: What hardware options, disk drives types and sizes, and other hardware features I have on each system?
  4. Licensing and Service Contracts:  What software am I using from EMC? Am I properly licensed? When will my service contract expire?
The CCE ecosystem that enables the iPad App to display this information consists of four main components:

  1. A collection process that runs on the user’s systems gathers data from the user’s data center and sends it to a central EMC data warehouse.
  2. A backend server, that integrates all the collections, manages the data warehouse and prepares data for the iPad client on a weekly basis.
  3. An administration Web portal, that enables the definition and configuration of CCE users and filtering of the data for each user.
  4. The iPad App that fetches a weekly payload from the backend server and displays the information to the user.
The information is shown to the user in several ways:

  1. A Dashboard View, consisting of a collection of KPIs (Key Performance Indicators) that enable the user to see at a glance the most important or actionable information in the above categories. The information shown in the dashboard is scoped to the systems selected by the user.
  2. A Chart View, focusing on one KPI or several related KPIs for the selected systems, shown in a table, graph or map view. This enables the user to explore the KPI in detail, see its trend and forecast, and compare this KPI across several systems. There can be many such chart views. The user will be able to use the items displayed in Dashboard View to navigate to the related Chart Views
  3. A Systems View, showing all the systems the user has selected in one scrollable view. For each system, key information will be shown in a concise manner.
  4. A Detail System View, showing detailed information about a single system. The user will be able to use the items in the Systems View to navigate to a single System View.

Set of linked wireframes created in balsamiq, a wireframing tool to get initial input from users, stakeholders and colleagues on the user-interface, interactions, functionality and plans for iPad, with functionality, mobile, code and performance optimization in mind, with changes and interactions annotated with notes, arrows and callouts explaining how sections/areas elements work on mobile and what they do. The mobile interactions were demonstrated in the functional HTML prototypes that were created early on during development and the same was transitioned to the final production app in an Agile development mode.

Date: July 15, 2013
Tags: , , , ,