Toms,

I have a tentative schedule and service arrangement with SIO MPL to use the R/V New Horizon for the upcoming SAN2 sea test in December. The deployment dates are 6-7 December and the recovery dates are 20-21 December, with mobilization and demobilization dates on both sides of these periods. Capt. Althouse, the Marine Superintendent, is willing to accommodate our special needs by allowing us to start after midnight on the first day in order to accomplish the fathometer survey before we enter normal daytime operations on 6 December. A similar schedule would be desirable on 20 December so that we could perform surface target runs with the ship prior to recovery. Because of the University National Observatory Laboratory Ship (UNOLS) rules under which this and the larger ships operate, and to minimize ship's crew fatigue, it is highly desirable, and perhaps necessary, for our scientific party to embark on the evening of the day before we sail, and to remain on board until the cruise is completed. This is somewhat different than we would have done with the R/V Sproul, had it been available for this schedule. The Horizon has sufficient berthing for this, whereas the Sproul does not.

Elizabeth Brenner and Rose Dufour, the ship schedulers, contacted John Freitag at ONR to see if we could use his funding arrangement to support us; however, he can accept only 6.1 funds, so we will need to make other arrangements. We should ask ONR for advice and direction on how to proceed here. Do we need to get competitive bids? Who should do the contracting? Should SSC-SD proceed on its own, or should LWAD become involved now and include the PBD in the negotiations? I'm sure Jim Curtis could do this much better than I, but then we need to know what Dana and Dave want us to do.

Regarding the node laydown for SAN2: We plan to deploy four nodes in a straight line with the most shallow node in 75 meters. The remaining nodes will be deployed to the west with even spacing, and the deepest node in 100 meters. The total distance is 2 nmi, giving a spacing of about 1235 meters between the nodes. An alternative laydown would have a shorter spacing, but no nodes beyond 82 meters depth.

We have a workable solution to securing recovery loops to the array strength member, as suggested by Bob Wilson. We would need to have the arrays here a week in advance of deployment in order to install the loops. An option is to have USSI install the loops, which may require 15 minutes each plus some stitching. We have ordered the necessary material, and will begin installing loops on the practice array in 2-3 weeks when the order comes in.

I recommend that the R/V New Horizon or other ship be scheduled as soon as possible for the PBD, since our schedule flexibility will be virtually nil. A "final" request to SIO MPL still does not commit the Navy to anything, but would reserve the time slot. Because we can operate from shore in San Diego, we do not need such a large ship as we were planning in our original location. Also, we should not need the ship continuously between deployment and recovery. I will be happy to work with LWAD to come up with a revised plan for ship usage.

Regards,
Ken

---------------------------------------------------------------------------------------------------------------------

SCHEDULE
The summary schedule of activities can be found below. Adjustments may be necessary to accommodate weather and other contingencies.

MON 28 Nov All nodes received from USSI; commence node checkout & crypto load
TUE 20 Nov
WED 30 Nov
THU 1 Dec All deployment/recovery equipment ready
FRI 2 Dec Load ship, stage equipment; dockside practice; pre-sail conference
SAT 3 Dec All personnel board ship; conduct fathometer survey beginning at midnight
SUN 4 Dec Practice normal deployment/recovery procedures; deploy racom buoy, repeaters, and up to 4 ADM nodes; check out communications
MON 5 Dec Complete deployment; conduct telesonar & release surveys at night; turn on one node; turn off three nodes; return to port; commence data collection and surface surveillance; one node operation with targets of opportunity, with short-term settling time
TUE 6 Dec Unload ship
WED 7 Dec Deployment backup day
THU 8 Dec Deployment backup day
FRI 9 Dec Node stabilization
SAT 10 Dec Node stabilization
SUN 11 Dec Node stabilization
MON 12 Dec Turn on three nodes; turn off one node
TUE 13 Dec Node operation with targets of opportunity, with long-term settling time
WED 14 Dec Node operation with targets of opportunity
THU 15 Dec Node operation with targets of opportunity
FRI 16 Dec Node operation with targets of opportunity
SAT 17 Dec Node operation with targets of opportunity
SUN 18 Dec Node operation with targets of opportunity
MON 19 Dec Load ship for recovery; all recovery personnel board ship; commence target runs after midnight
TUE 20 Dec Recover all equipment
WED 21 Dec Backup recovery day
THU 22 Dec Demobilize
FRI 23 Dec Backup day: Last day to recover and demobilize

---------------------------------------------------------------------------------------------------------------------

TEST OBJECTIVES

Objectives for this test are to ensure that the ADM hardware and software are functioning in a manner to support the DADS PBD. Specifically, this includes
• Verify all sensor node functions.
• Verify the quality of recorded data, including use of encryption algorithms.
• Verify that magnetometer movement does not contribute excessive noise to the magnetic data.
• Refine new deployment hardware and procedures.
• Measure the settling time required to stabilize magnetometers on the sea floor.
• Test automated array element localization software.
• Test acoustic surface ship classification software.
• Demonstrate automated contact reporting.