The Kepler Sensor Platform consists of a flexible set of components that may be partially or entirely adopted to help you manage sensor site deployments. A typical scenario has components installed in three areas:
1) Field Components: A low-power PC running the Sensor Processing and Acquisition Network (SPAN) for datalogger or sensor communication, and a DataTurbine as on-site ring buffer.
2) Server Components: A server running a DataTurbine as buffer and data provider, Scheduler and Kepler Run Engine web services for periodic, remote workflow executions, and a Metacat repository for archiving sensor data and workflow run results.
3) Desktop Components: Desktop computers interacting with the Kepler Sensor Platform through the Sensor View 0.9 add-on suite for Kepler 2.3.

This beta release of the Kepler Sensor platform represents a technology preview that illustrates new functionality for sensor data management within Kepler. We encourage others to contribute further to its development and testing so that it might become a fully supported release within Kepler. Please contact barseghian [at] nceas.ucsb.edu (Derik Barseghian) and/or jones [at] nceas.ucsb.edu (Matt Jones) for details on how to contribute or on future plans for the Kepler Sensor Platform.

The Kepler Sensor Platform was developed under a grant from the National Science Foundation (CEO-P #0619060) to the National Center for Ecological Analysis and Synthesis (NCEAS) at UC Santa Barbara, with collaborating partners at UC San Diego, UC Davis, OPeNDAP Inc., and University of Minnesota.