Wed Aug 12, 2004

[chaffey - requirements]

non moos (e.g. earthquake) triggering MOOS response?
cost of achieving requirements, cost-benefit importance
what were greatest cost drivers 
	(depth, survivability, maintenance interval, etc.)
non moos data big cost driver?
accoustic comms, auv ops
commercial, community standards - what is state of the art  (SSDS presentation)

[chaffey - moos block diagram]

MMC fanout of 12:
operational cost of using multiple controllers
sideARM processor lifetime and MMC roadmap -- can upgrade MMC
are radio links shared among multiple nodes -- can configure it either way
power consupmtion (defer to CIMT presentation)

[oreilly]
cost-benefit, scalability, application space for moos...

pucks, cost, benefits

what about managing device ids (for use across MOOS observatories)
is network secure? security tbd...not designed against malice
issue for NEPTUNE?

what about virtual pucks...defeats plug n work and opens up to operational mistakes, but it's an option -- need to review puck concept

[gomes]
high level control is small part of effort
dropping high level participation required -- ease of entry
authoring metadata is hard part?

[headley]
what are big cost drivers for the system?

[discussion]
what's next
mtm3 2004 (NSF funded)
moos array 2005 
shepard's meander 2006
	oem, benthic vp, benthic nodes,
	siam, ssds,mms, medusa, 
	event detection/response

uwc benthic profiler oct 2004

more and more mooring deployments...auv/docking deployments falling off table
what is most effective way to move forward on docking
moos is capped, but not entitled to, 50% of resources...can use less
mooring efforts
whoi (small, accoustic comms, batteries), scripps(large, diesel)
is moos robust enough for ORION

what are cost/benefits of replacing m1/m2 with moos moorings

[extras]
power budget (not shown)