Skip to end of metadata
Go to start of metadata

Home page for detailing User Experience development plans and tasks.


Release 1 User Experience design and development efforts are divided into three categories:

Key Deliverables

Deliverable Description
Production UI Graphical user interface provided to end users to support their use of the system to accomplish their work.
Provisional UIs Screens provided to allow direct access to key system functionality during the development phase.
[Cognitive workflows] Theoretical models of science inquiry and related cognitive tasks as understood by psychology and cognitive science, elaborated for ocean science and used to inform design and user research.
[Design-a-thon] campaign Series of events bringing together small groups of users and designers to generate ideas and solutions for particular design questions, used to collect examples of how the framework might be used.
[User Engagement Platform] Web-based support for community interaction for the express purposes of collecting design ideas and insights and for gathering feedback on proposed designs.

Provisional vs. Production UI

Release 1 of the OOI Ocean Observatory will offer users a single web-based graphical user interface (GUI), but some users will see two distinct types of design: Production UIs and Provisional UIs. These will look similar and be implemented within the same presentation framework, but represent significantly different levels of sophistication of usability design. Production UIs are intensely designed with regards to supporting users' ways of thinking and working, and are intended to make users productive in their work. Provisional UIs are minimally designed with respect to users' workflows and rather aim to meet pragmatic needs for testing and experimenting with specific functionality. Provisional UIs are intended to provide early access to functionality that has not yet been released for general use.

A key difference between the two is in how functionality is decomposed and exposed: In Production UIs, access to a particular feature might be distributed in bits and pieces across the design so that the user has the right tool in the right place at the right time, while, in a Development UI, all access to that feature would be gathered in one place. It's like controlling the electricity in your house: you (the user) need switches in each room, while your electrician (the engineer) wants a single panel that controls the electricity throughout the house. And, note, in all likelihood, most Provisional UIs will be exactly that: control panels.

At the moment, the intent is that Provisional UIs are temporary, that is, they will be removed as the design matures and features are integrated into Production UIs. Ultimately, we expect that there will be no Provisional UIs in the system. However, being designers, we reserve the right to realize that they serve long-term practical purposes and retain the concept in the final system.

Subsystem Objectives

Release 2 Objectives

(see also R2 UX Construction Plan)

  • Support the core R2 target user audience (non-end user, non-scientist, instrument operators, marine engineers, instrument driver developers, data process developers) with appropriate APIs and user interfaces.
  • A sufficient and necessary set of screens that meet the core needs of RSN and CGSN in a simple and elegant fashion, where the core needs are defined in the R2 Themes and Features (extended version) document.
  • A refined and enhanced interaction framework, visual framework and toolset for finding, understanding and analyzing data of interest to meet the core needs of OOI project scientists and designated early adopters, where specific refinements and enhancements are defined by R2 Themes and Features and by user response to R1 implementation and designs.
  • A plan for providing access to OOI functionality via mobile platforms that is based on user studies using exploratory prototypes.
  • An interactive prototype of the proposed system that serves as an unambiguous tool for discussion and communication internally as well as externally.
  • Active involvement by the OOI project scientists and operational engineers in defining and verifying user interface requirements and designs.


We produced a CI Technical Elements Overview for General Audiences, which may be useful to appreciate the overall context of this system.


Release 2

The finalized iteration task plan (13 May) for User Experience is here. The evolving list of tasks is on this google docs spreadsheet.

Architecture and Design

Development and Implementation

There is a separate page capturing the following efforts:



Workshop Proposals

Release 2

Click to add new UX workshop proposal

PageWorkshop TopicTotal DaysCoordinator Name Key External AttendeesPoster
Workshop Proposal for EPE Team Liaison1Debi Kilb, John GraybealAnnette deCharon, Carla CompanionJohn Graybeal
Workshop Proposal on Scientific collaboratory integrationScientific collaboratory integration1.75Susanne Jul Judy Olson, UC Irvine; Gary Olson, UC Irvine; David McDonald, U Washington; (someone from colwiz - Matt Baker?)John Graybeal


r2-subsystem-objectives r2-subsystem-objectives Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.