Skip to Main Content
Cabled observatories, such as MARS or the regional scale cabled observatory system planned for in the NSF Ocean Observatories Initiative (OOI), consist of many deployed instruments that communicate with human operators and shore-side data repositories. In addition, these deployed devices may actually communicate with one another, facilitating capabilities such as autonomous event response. These potentially complex interactions between multiple entities - human and machine - require that knowledge of the system configuration be available to participants. Users of instrument data require information - metadata - about the sensor that generated the data. Software that coordinates and controls instruments requires access to the software interfaces of those devices. "Manual configuration" has been used on small-scale systems, but in a network consisting of hundreds or thousands of instruments, the configuration challenge becomes critical. We propose to address the problem through automation of the configuration process; which will be achieved at several levels. Automated configuration will simplify the system operator's task of building and maintaining the observatory network. We describe a small, low-powered information storage device that we call a "instrument puck". When plugged into a suitable computer (lab workstation, deployed observing node), information can be written to or read from the puck. While an instrument is being prepared for initial integration into observatory, a technician "loads" a puck with information necessary to configure the instrument within the observatory, and then physically attaches the puck to its instrument. Thereafter the attached puck always travels with its instrument, no matter where it is being installed in the observing network. The information loaded into the puck encompasses whatever is necessary to enable automatic configuration and system integration of the instrument when it is plugged into the observatory network, and any other information required by observatory policies. This information may include structured descriptions of the instrument's sensor and data characteristics (metadata). The information can also include actual software code that is retrieved from the puck and executed by an observatory node w- hen the device is plugged in; this code could implement distributed instrument control and data retrieval interfaces, allowing network-wide access to the instrument functionality. We believe the puck concept to be a powerful one, a given instrument puck is configured just once; enabling automatic configuration of its instrument no matter it is installed on the network thereafter. We also describe mechanisms by which an instrument and its puck can be "discovered" by the observatory network when the devices are plugged in. Several approaches are explored, with varying degrees of automation. We evaluate these approaches with special consideration to electrical and safety aspects of the undersea environment. Information and results from our prototyping efforts are also presented.