Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page outlines the Operations Engineers' responsibilities on ARIA HySDS. Questions regarding these specific points may be directed towards to Andrew Zhang [andrew.m.zhang@jpl.nasa.gov].

  • Product Generation

    • Ensuring the expected products are being generated generated.

    • Supporting product generation for monitoring and urgent response campaigns.

  • Data Accountability

    • Ensuring expected jobs are being submitted for both on-demand job submission and trigger - rule job submission.Supporting product generation for monitoring and urgent response campaigns

    • Ensuring jobs complete successfully.

  • Product Delivery

    • Ensuring products belonging to completed tracks are delivered to the DAAC and published to ARIA Products regularly.

  • DAAC Communication

    • Responsible for communication with DAAC regarding the delivery pipeline, including, but not limited to, expected outages, changes in the delivered products, and/or changes in the interface between JPL and the DAAC.

  • Customer Communication

    • Responsible for communicating to the customer the processing status.

    • Advocating for the customer when system changes are made to ensure expectations are understood and met.

  • Monitoring Slack Alerts

    • Responsible for monitoring and investigating slack alerts indicating the ARIA HySDS system has detected anomalous behavior.

  • Monitoring Ancillary Data Ingest

    • Make sure latest acquisitions, orbits, and ipf’s are ingested. If they failed to ingest, investigate cause of failure and notify team members of problem and whether additional assistance is required to resolve the failures.

  • Ticket Tracking

    • Responsible for creating and updating operations Jira tickets.