1. 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. THE GOAL 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: PRACTICAL TIPS 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.orgUX@oceanobservatories.org WHAT TO DO 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 blocks 2.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) ORGANIZATION Contact Information NameEmail Address UX@oceanobservatories.org Susanne Jul, User Experience Lead sjul@acm.orgsjul@acm.org +1 650-455-8228 CONTACT

2. IDENTIFYING INFORMATION Clk Label Example Data 0Name Type ID Model Manufacturer OOI Test Mooring #3 Bottom-tethered, suspended, no surface expression ION-1234567 Custom WHOI 1Serial # Manufacturer’s Contact Info Supplier Supplier’s Contact Info Pictures WHOI-39887 2 OPERATIONAL STATE Clk Label Example Data 0Lifecycle/operational state Summary indicator Warnings Alerts Open trouble tickets Connection Indicator Uptime In direct access mode Active [Stoplight indicator] [Red] 0 [Yellow] 5 [Active trouble ticket] 2 [Direct access on] Operator ID 1Last Trouble Ticket Last Archived File Last communication Last data reported Next communication expected Next data expected 2Activity Data volume Power duty cycle Frequency of ION interaction Telemetry Telemetry age trend Sampling error rate trend Error message history Engineering data over time Sensor-produced flags Computed health status Logs Data Logs Command Logs Communications/protocol events Annotations Messages Latest messages Debug messages IMPORTANT USEFUL Platform CRITICAL PROVENANCE Clk Label Example Data 0Principal Investigator Email Phone Fax Owner Email Phone Fax 1 2 LOCATION Clk Label Example Data 0Site Region [Map] Latitude Longitude Depth (m) Drift Tolerance Hydrate Ridge Offshore Oregon 1.5 mile radius 1At Location Since 2 SETTINGS Clk Label Example Data 0Lifecycle state Planned Developed Commissioned Active Decommissioned Effective Date Data Rate IP Address Port Settings Port Label Port Code Port Direction Power Voltage Protocol 1 2 DATA Clk Label Example Data 0Quick Plot one per sensor Summary Plot - all sensors Sample values Access to download [platform-specific data, not data from instruments deployed on platform] 1Orientation Heading Tilt Roll 2 SENSORS (Table) Clk Label Example Data 0Status Sensor Name Sensor Type [platform-specific sensors, not the sensors of the instruments deployed on platform] [Stop light indicator] 1Unit of Measure Sampling rate Last sample data 2Calibration POLICY Clk Label Example Data 0[Usage] [Control authority] 1 2 DOCUMENTATION Clk Label Example Data 0Manufacturer Images Manuals OOI Logs [Link] [Attachments] 1 2 COMMAND STATUS Clk Label Example Data 0Under active direct command control by someone 1Last Commanded Commanded By Commands Access to Command Interface 2 ELECTRICAL Clk Label Example Data 0Breaker Number Switch Port Number Nominal Voltage (V) Nominal Current (A) Peak Voltage (V) Peak Current (A) Power (W) 1 2 TROUBLE TICKETS Clk Label Example Data 0Active tickets 1History 2 EVENT HISTORY (Table) Clk Label Example Data 0Date Type Event Initiated By Description Notes 1 2 DEPLOYMENT Clk Label Example Data 0Name Start date (planned or actual) End date (planned or actual) Glider Test 2012-01-01 2012-02-01 1Cruise Ship 2 DEPLOYED INSTRUMENTS (Table) Clk Label Example Data 0Status Position Name Type Owner Last Data Received Date Last Event Date Last Event [Stop light indicator] 20 meters 1 2 DESCRIPTION Clk Label Example Data 0Description[Narrative description] 1 2 COMPONENTS (Table) Clk Label Example Data 0Parts Diagram/Pictures Reference Category Sensors Communications Controllers Connectors Software Other Name Position Type ID Model#/Part# Manufacturer Description [keyed to diagram] 1 2