INSTRUCTIONS

We are looking to develop a detailed understanding of what information about an Platform needs to be displayed somewhere in the user interface, and how prominently it needs to appear. You can help by telling us how you use and think about this information. We will combine your view with that of others to develop something that works for most people.

You can work by yourself, with someone of your choice, or talk it through with us. Please email us if you prefer the last or if you have any questions.TH

E G

OAL

• Always work in the Normal view• It’s best to work zoomed out (“Fit” or ~33%) when moving blocks of things around, and zoomed in (100%) when editing

the text within a block• Please enter your name(s) and email addresses here, so that we can get back to you if we have any questions:

PRAC

TICA

L TI

PS

• On the next slide, we have selected some information and proposed an organization of it. We would like you to add, remove, rename and reorganize it to look the way you would want it. Remember that you’re the expert, we’re just making educated guesses.

• We are looking for a marine Operator’s perspective at this time, so put yourself in the frame of mind of a operator who is new to the system or has been away on an extended vacation, and is sitting down to catch up on a particular Instrument.

• When you are done, please email your edited file to us at UX@oceanobservatories.org

WH

AT T

O D

O

The information is organized in several ways. 1. Information is grouped into related pieces that are shown as blocks. Feel free to rename add and remove blocks2. Within a block, information is organized by “click-priority.” This reflects how directly available this information should be if

anything is displayed on the screen. Think “If I can only have a little bit, what do I want?” (0-click). Then, “if I can have a little more, what would I want?” (1-click)

3. Blocks are then organized according to their overall relative importance. Information that absolutely has to be available quickly (Critical), is needed (Importantt) or good to have (Useful)

ORG

ANIZ

ATIO

N

Contact InformationName Email Address

UX@oceanobservatories.orgSusanne Jul, User Experience

Lead sjul@acm.org+1 650-455-8228

CON

TACT

IDENTIFYING INFORMATIONClk Label Example Data

0 NameType

IDModelManufacturer

OOI Test Mooring #3Bottom-tethered, suspended, no surface expressionION-1234567CustomWHOI

1 Serial #Manufacturer’s Contact InfoSupplierSupplier’s Contact InfoPictures

WHOI-39887

2

OPERATIONAL STATEClk Label Example Data

0 Lifecycle/operational stateSummary indicator •Warnings•Alerts•Open trouble tickets•Connection Indicator•UptimeIn direct access mode

Active[Stoplight indicator][Red] 0[Yellow] 5[Active trouble ticket] 2[Direct access on] Operator ID

1 Last Trouble TicketLast Archived FileLast communicationLast data reportedNext communication expectedNext data expected

2 Activity•Data volume•Power duty cycle•Frequency of ION interactionTelemetry•Telemetry age trend•Sampling error rate trend•Error message historyEngineering data over time•Sensor-produced flags•Computed health statusLogs•Data Logs•Command Logs•Communications/protocol events•AnnotationsMessages•Latest messages•Debug messages

IMPO

RTAN

TU

SEFU

LPlatform

CRIT

ICAL

PROVENANCEClk Label Example Data

0 Principal Investigator•Email•Phone•FaxOwner•Email•Phone•Fax

1

2

LOCATIONClk Label Example Data

0 Site Region[Map]LatitudeLongitudeDepth (m)Drift Tolerance

Hydrate RidgeOffshore Oregon

1.5 mile radius

1 At Location Since

2

SETTINGSClk Label Example Data

0 Lifecycle state•Planned•Developed•Commissioned•Active•DecommissionedEffective DateData Rate <would this be by instrument or by sensor?>IP AddressPort Settings• Port Label• Port Code• Port Direction• Power• VoltageProtocol

1

2

DATAClk Label Example Data

0 Quick Plot•one per sensorSummary Plot - all sensorsSample valuesAccess to download

[platform-specific data, not data from instruments deployed on platform]

1 OrientationHeadingTiltRoll

2

SENSORS (Table)Clk Label Example Data

0 StatusSensor NameSensor Type

[platform-specific sensors, not the sensors of the instruments deployed on platform][Stop light indicator]

1 Unit of MeasureSampling rateLast sample data

2 Calibration

POLICYClk Label Example Data

0 [Usage][Control authority]

1

2

DOCUMENTATIONClk Label Example Data

0 Manufacturer•Images•ManualsOOI•Logs

[Link][Link]

[Attachments]

1

2

COMMAND STATUSClk Label Example Data

0 Under active direct command control by someone

1 Last CommandedCommanded ByCommandsAccess to Command Interface

2

ELECTRICALClk Label Example Data

0 Breaker NumberSwitch Port NumberNominal Voltage (V)Nominal Current (A)Peak Voltage (V)Peak Current (A)Power (W)

1

2

TROUBLE TICKETSClk Label Example Data

0 Active tickets

1 History

2

EVENT HISTORY (Table)Clk Label Example Data

0 DateTypeEventInitiated ByDescriptionNotes

1

2

DEPLOYMENTClk Label Example Data

0 NameStart date (planned or actual)End date (planned or actual)

Glider Test2012-01-012012-02-01

1 CruiseShip

2

DEPLOYED INSTRUMENTS (Table)Clk Label Example Data

0 StatusPositionNameTypeOwnerLast Data Received DateLast Event DateLast Event

[Stop light indicator]20 meters

1

2

DESCRIPTIONClk Label Example Data

0 Description [Narrative description]

1

2

COMPONENTS (Table)Clk Label Example Data

0 Parts Diagram/PicturesReferenceCategory• Sensors• Communications• Controllers• Connectors• Software• OtherNamePositionTypeIDModel#/Part#ManufacturerDescription

[keyed to diagram]

1

2