NSF06-505 Discussion
1	Strategies
1.1	don't get involved with big architectural things with other guys (Jim B)
1.1.1	carve out many small projects
1.1.1.1	Eye in the Sea
1.1.1.2	docking
1.1.1.3	event detection
1.1.2	concrete in the water thing
1.1.3	few talk about how you're going to manage system
1.2	key ingredients
1.2.1	data system
1.2.2	acquisition system
1.2.3	AI?
1.3	we could connect engineering to science
1.4	too big for any one group to take on
1.4.1	architectural proposal and prototype of it
1.4.2	need more than oceanography
2	Concepts
2.1	focused on end results from existing data
2.1.1	don't select a toy problem
2.1.2	must be demonstrable
2.2	why not throw AOSN thing at this?
2.2.1	has all elements except our AUV
2.2.2	very good narrative
2.2.3	conflict of monies?
2.2.4	idea of AOSN is real-time control
2.2.5	integrated use of data
2.3	interaction between assets (moorings and AUVs)
2.3.1	like Luiji
2.3.2	web interfaces to allow components to interact from remote control
2.3.3	C Scholin needs event response
2.4	MARS project is a big asset
2.5	combine data assets from multiple organizations
2.5.1	e.g., CeNCOOS partners
2.5.2	show cross-institutional interoperability
3	Partners
3.1	Need SIO
3.1.1	Tony Fountain a good ally?
3.2	Larry Smarr may be someone we can talk to
3.2.1	pre-disposed to work with SIO
3.2.2	guy who wants to deliver
3.3	substantial number of people at Ames for Grid computing
3.3.1	subtle issue with NSF not funding Ames
3.3.2	good for cross-discipline (not just oceanography)
3.4	Lawrence Livermore
3.5	lots of other people, but control is nice
3.6	Deborah Estrin's group at UCLA: NEON
3.7	industrial partners
3.7.1	Agilent
3.7.2	NetBeams
3.8	may want to embrace LOOKING effort in some way
3.8.1	disappointment with LOOKING products
3.8.1.1	confusion at PI meeting: what are we going to do?
3.8.1.2	showboating video
3.8.1.3	Smarr: need to get something out the door
3.8.2	Arrott interest unclear (mixed signals)
3.9	CeNCOOS and its regional partners