MOOS Review Preview
Tue 8/3/04 0900-1100
raybould,oreilly, davis,gomes,chaffey,graybeal,kelley,edgington

Why this review?
Need to remind management team of what problems we are trying
to address with MOOS.

SIAM/ISI/SSDS: what are the big problems preventing mooring networks and self configuring networks? These were well defined in original ISI and SSDS proposals, and ISI workshop summary doc.

- solving metadata problem
- add quickly, efficient instruments to MOOS w/ minimal software work
- metadata

need to add controller to list

MTeam last year:
Isn't SIAM finished?
What does SSDS do for us?
>> let's evaluate w/ 2004 deployments

We want to express what we have accomplished at a high level

Pucks, too, at a high level (not to evaluate hardware)

Will NOT discuss transition to ops

Will NOT replace M1/2 with MOOS in 2005

Will replace CIMT (turn) and use either MTM2 or 2004M0

Start with original drivers and why they are important
MOOS system block diagram
CIMT specific design objectives (requirements for CIMT too detailed -- 
     need user level, top level requirements); lower level requirements that have to do with 
what worked, what didn't

Are the original questions the right ones to be asking? what new questions have surfaced (operational issues)

what decisions are being made based on information presented in this review?
 - affects 2005/2006
 - remind MTeam about importance of MOOS elements in larger programs

High level, simple: 
     when are things "done"? 
     what's taking so long if it's so simple?
- We need to communicate that we are solving big problems and we are at some point in a process
(bug/feature list...)
- we've reached ONE level of many in the MOOS roadmap

we need to plan in upgrades and development

>> Stress incremental development


what do I need to prepare?


Agenda Items

## 80%##
- Big problems trying to address (for each subsytem: SIAM(Tom)/SSDS(Kevin)/(Puck as enabler)/MMC (Mark))

- System Block Diagram (Mark)

- Subsystem requirements SIAM(Tom)/SSDS(Kevin)/MMC(Mark) 
  (ignore requirements not directly related to Big Problems (L1, L2/3 that are important to users)

- Design (multi-node system MOOS)(ID CIMT elements: it's done, it's being used,  Science data return)(Tom,Mark,Kevin)

- Results CIMT deployment (relate back to Big Problems, Original Requirements) (Kent)

- Extrapolation results -> OOI/IOOS results (Keith)
  
## 10% ##
- What's Next (near term)? (so MTeam knows why we are where we are, and why we're doing these things)
  - (multinode July/Aug '06) (Big Seafloor Experiment (2006 Shepards Meander))
  - event detection/response
  - dynamic metadata
  - tools for entering metadata
  - configuration management (hardware, metadata)
  - easier driver writing
  - interfaces to use metadata (query, search, merge, data/metadata)
  - instrument control GUI
  - isi/ssds/mmc buglists
  - transition to ops (packaging)(2006 M1/M2)
  - public interface to system info (top web page)
  - data QC

## 10% ##
- What's Next (Big Picture)(Keith)
  - OOI
  - IOOS
  - MARS

radio infrastructure, power mgmt: important, but not on this agenda

When detailed e2e engr system review?
     - MOOS hardware   
     - SSDS
     - SIAM (CDR done-ish)
     - before shepards meander; Q2/2005?

MOOS at what cost? 
     - covered under Design, Results (haven't turned a mooring around), link back to requirements
     - what is now more complex to do? what is cost relative to OASIS? What are benefits? 
     - Must keep Big Picture in view...


CIMT instruments -> MTM2 -> 2005CIMT

Dry Run? Wed afternoon , slides by Friday
I need something by Friday from Tom, Kevin, Mark to dovetail
Keith will do outline