CI Integrated Build/Verify/Test

1. CI Integrated Build/Verify/Test

2. Integration Team Focus on End to End Performance • Members represent all parts of the system and development team • OL – System Engineering and CI • Rutgers – Host CI, Integration, science/engineering V&V, transition to O&M • Raytheon Omaha – CI uFrame Software • Applied Science Associates (ASA)  - User Interface • Marine IOs - science/engineering V&V • Each Software delivery is integrated and exercised at Rutgers using data from at-sea instruments • Issues are detailed, resolved and/or documented with Redmine tickets • Daily morning team calls – reviews status, issues and priorities • Entire team is linked by the CI network with access to the CI Servers • On-site team integration events for each build • Parallel Integration efforts balance the core system integration with early visibility to the science community • Integration of Software builds • Conditional Acceptance • Community Outreach

3. CI Integrated Build/Verify/Test Flow Integration Unit Test & Integration V & V • Dev/integ Servers • Rutgers • Full strings • Weekly builds • Production Server • Rutgers • Full string • Delivered builds • Development Servers • Omaha and ASA • Task focused config • Daily builds Status/Process Servers are on line at Rutgers 3 servers uFrame/UI L1/L2 products >> GUI >> being evaluated Performance approaching expected speed Stability is good except under high load Experiencing overload induced system gridlock UI tools are in place but are sensitive to unexpected conditions and slow response from uFrame Data First of class platforms for Group 1A/B, 2A/B, 3, and 4 are all available These are sets required for conditional acceptance Cabled Calibration and data ready for all instruments Test Procedures Test Procedures written for Builds 1-4 Infrastructure Data threads Algorithms Asset management System management Instrument Drivers Parsers Port Agents User Interface (UI) Infrastructure (uFrame) Full integrated system Capabilities added when stable Focus on debug, stability, and performance Full integrated system Focus on complete system capability Focus on system test and sell-off UI Capabilities Instrument data

4. Data Stream Summary

5. Functioning Capabilities Are Exercised in Integration • Cabled instrument command and control (C2) • Initial bench tests with C2 UI have been completed • These tests must be performed with additional instrument to verify full function • All cabled instrument testing has been performed on a dedicated string; we need to integrate this testing into the common development strings and perform load testing • Final configuration networks and VPNs need to be in place to be sure all is working • End-to-end tests will wait for all other tests to be completed to ensure stability

6. Conditional Acceptance Allows the Program to Accept the Deployment with Conditions Prior to Commissioning • Conditional Acceptance verifies the Marine Implementing Organization (MIO) deployed Infrastructure and data path from at-sea sensor through the in-process CI • Conditional Acceptance is detailed in an ECR and Report • The planned Conditional Acceptances Include: • Pioneer/endurance Coastal Glider and wire following profiler moorings • Pioneer Surface Mooring • Station papa /global moorings & Gliders • Cabled Array – new • Pioneer/Endurance Coastal surface piercing profiler • Commissioning will occur when the marine platforms in the array are deployed and operational, and when the full OOI Cyberinfrastructure (CI) and related User Interfaces (UI) are complete and verified. • Prerequisites required are detailed in the SEMP Final and punch-list needed for Conditional Acceptance and Commissioning are tracked using Redmine.

7. Conditional Acceptance and Final Commissioning Conditional Acceptance • A complete As-Built Technical Data Package (TDP) has been provided • The IO has verified all of its L3 and L4 requirements • All action items from prior Technical Reviews have been closed • Operational Status of the Deployment or Software has been provided to the PMO • Validation Testing has been completed • The shore-side management component of the array (OMC or Shore Station) is operational and its design and operational procedures are documented. • All L0 and L1 Science and Engineering Data Products associated with the deployment are available through the CI through a rudimentary web-based CI search and download capability • Conditional Acceptance Report, including a recommendation to Conditionally Accept Final Commissioning • All the above plus the completion of the Commissioning Checklist • Acknowledgement of readiness to operate the platform or array • Set of proposed Operational Metrics and Government Performance Metrics • Commissioning Report, including a recommendation to Commission

8. Data Sets For All OOI Are Being Ingested Into uFrame Uncabled • Associated calibration/asset information ingestion is ongoing • First of class platforms for Group 1A/B, 2A/B, 3, and 4 are all available • Most are already ingested • These are sets required for conditional acceptance • All 1A platforms are ingested • Required ingest and cal info for all 2A platforms is about half done • Other full sets will follow Cabled • Calibration and data ready for all instruments

9. CI Validation Follows Formal Procedures • Once initial testing by the integration team is complete, each driver and algorithm in the group is then tested by subject matter experts • Validation Test Procedures document the results   • For dataset agent drivers and data product algorithms, science subject matter experts (SMEs)test the L0, L1, and L2 products produced and validate the correctness of output science data, checking for correct variable names and units, correct and complete metadata, and for reasonableness of the variable values.   • For instrument and platform drivers, marine operations subject matter experts test the command and control functionality of the driver.  • CI UI functionality is increasingly utilized as builds are integrated. • SME testers use the UI to access and visualize products produced by the drivers • Regression testing of previously-integrated user interface functionality is conducted as each new batch is integrated. • Final Commissioning is performed with released CI/UI