SA R1C3 Wrap-up Presentation slide 1 Sensing and Acquisition Release 1 Construction 3 Wrap-up Presentation May 19, 2011 Alon Yaari, SA Team Lead

SA R1C3 Wrap-up Presentation slide 2 1. Release 1 Goals Support for end-to-end demonstration of instrument-sourced data. UC.R1.02 Hello Instrument:Connect it to the CI UC.R1.03 Hello Data Source:Register and connect a data source UC.R1.18 Command an Instrument:Send it commands UC.R1.19 Direct Instrument Access:Directly communicate with it (No Use Case)SIAM Integration proof-of-concept Pre-R1C3 Recap: Objectives met by IPAA team UC.R1.02,.03, and.18 were demonstrable by LCA/MBARI meeting in Jan 2011 Pre-R1C3 Challenges: Lack of formal SA team Fluid agent/driver definitions

SA R1C3 Wrap-up Presentation slide 3 2. R1C3 Iteration Goals Refined SA objectives to develop: Common (to each instrument) instrument agent Examples of customized instrument driver (SBE37, NMEA) Deployable instrument simulator (NMEA GPS) Initial SIAM adapter/driver Defer direct-access to later release cycle Concentrate on component interface definitions Concentrate = Action = developing, implementing, building, demonstrating Build on existing IPAA efforts Concentrate on specific R1 requirements: Instrument agent shall:Acquire data… publish to exchange Acquire metadata… publish to exchange Receive CI commands… command the instrument Manage instrument state… etc.

SA R1C3 Wrap-up Presentation slide 4 3. R1C3 Iteration Goals Status R1C3 Status: Areas in need of enhancement: SIAM set-params and execute-commands SIAM publishing to agent Duplex communications from NMEA driver Enhanced metadata capabilities (waiting on R2 design task) Direct instrument access (deferred to R2) FIPA standards (waiting on internal review)

SA R1C3 Wrap-up Presentation slide 5 4. Completing R1C3 Goals NMEA Driver How is this reflected in JIRA?As “work remains.” How serious is this?Required for IOC. Alternative is SBE37 against real instrument. What blocks completion?Developer’s time. When will it be complete?IOC-ready for morning of May 23, full-duplex communications by end of transition. Obstacles?None. SIAM Enhancement How is this reflected in JIRA?As “work remains.” How serious is this?Not very. Today we can demonstrate general SIAM integration without all the details. What blocks completion?Developer’s time. When will it be complete?End of transition period. Obstacles?Minor obstacle, how to implement a SIAM implementation for demonstrations and testing. Agent / Driver Enhancements How is this reflected in JIRA?As “work remains.” How serious is this?Not very. Agent and driver are usable without these enhancements. What blocks completion?Developer’s time; architectural review of FIPA integration plan. When will it be complete?By end of transition. Obstacles?Minor obstacle, how to implement a SIAM implementation for demonstrations and testing.

SA R1C3 Wrap-up Presentation slide 6 5. Transition Goals Improving Stability and Quality Code cleanup (agent, driver, SIAM adapter) Documentation cleanup (interfaces, high-level overviews) FIPA standards (waiting on internal review) GPB-ification of messages with COI Verification of SA Requirements As of May 18, 2011, all Release 1 SA requirements are met During transition, degree to which requirements are met will be improved, mainly wrt metadata Specific Transition Tasks General code and documentation cleanup Organize driver code into “driver frameworks” Metadata improvements (FIPA?) SIAM adapter: implement set-params, execute-commands, and redirect publish to agent SA Team All-hands transition objectives meeting to determine plan specifics for… NMEA Driver full-duplex enhancements PRR-specific objectives 6. Transition Plan

SA R1C3 Wrap-up Presentation slide 7 7. Obstacles to PRR Obstacles to completing Transition Activities: Access to demonstration SIAM platform Access to SBE37 instruments Consistency of standards and interfaces borne in other subsystems and architecture decisions (e.g., GPB) R2 design team decisions for implementing outside standards (e.g., PUCK, etc.) Issues with dependencies, delays, blockages: FIPA plan approval GPB-ification of messages with COI (has already shown to be a larger time investment than anticipated) 8. Risks