80GSFC22R0007 VLBI - SOW.pdf

STATEMENT OF WORK

May 2021

I. Introduction This Statement of Work defines the general requirements for the contractor to support the NASA Space Geodesy Project (SGP) Very Long Baseline Interferometry (VLBI) operations. In particular, the contractor shall provide leadership and support for the International VLBI Service for Geodesy and Astrometry (IVS) Coordinating Center, CORE Operation Center, and the GSFC IVS Analysis Center. This effort also includes advanced VLBI related research and development.

The scope of this effort includes six specific task areas:

1. IVS Activities

2. VLBI Observation Coordination

3. VLBI Data Processing and Analysis

4. VLBI Research and Development

5. VLBI Software Development

The detailed requirements for each task will be provided in the contract Task Orders and through the NASA approved contractor plans listed in the deliverables section.

II. Description of Tasks and Technical Requirements

1. IVS Activities

The contractor shall support Goddard’s commitments to the IVS by supporting the responsibilit ies, duties, and functions of the IVS Coordinating Center and the IVS Analysis Coordinator, as described in the IVS Terms of Reference. The contractor shall work closely with all the IVS Coordinators and the IVS Chair as the leadership team of the IVS. The contractor duties may include:

a) The contractor employees who are members of the IVS Directing Board will attend the IVS Directing Board Meetings. Members of the IVS Directing Board currently include the IVS Coordinating Center Director and the IVS Analysis Coordinator.

b) The contractor shall provide the position of IVS Coordinating Center Director, including coordination of the daily activities of IVS, liaison with other services and external organizations, and ISC World Data Center meetings.

c) The contractor shall provide the position of Analysis Coordinator. The Analysis Coordinator is responsible for coordinating the analysis of the IVS and for stimulating VLBI product development and delivery. This includes the IVS contribution to the realizations of the International Terrestrial Reference Frame (ITRF). The contractor may utilize the IVSCC website to facilitate the coordination.

d) The contractor shall maintain the IVSCC website by posting new information and organizing operational information in support of IVS Coordination Center activities. The contractor shall ensure that IVSCC website is compliant with NASA policy and regulations. The contractor shall develop and maintain an IVSCC Website Future Release Document that outlines the plans for changes and upgrades to the website.

e) The contractor shall develop and maintain a contingency plan for essential IVS coordination functions in the event of the unavailability of the IVSCC website and other NASA IT resources.

f) The contractor shall support preparation of the IVS Biannual report and General Meeting proceedings.

g) The contractor shall solicit, edit, and prepare for publication the IVS Newsletter three times per year.

h) The contractor shall participate in the activities of the Global Geodetic Observing System (GGOS) representing the IVS and the VLBI technique. The contractor shall attend relevant meetings associated with GGOS.

i) For all IVS and related activities that require substantial resources and/or are highly visible, the contractor shall provide a briefing regarding the resources required to support the activity to NASA to obtain concurrence. The briefing shall include the resources required to support the activity, the schedule to support the activity and status. The contractor shall not commit any NASA resources, including NASA supported contractor resources, to other organizations without explicit approval of NASA.

2. VLBI Observation Coordination

The contractor shall coordinate all the VLBI observing sessions determined by the IVS to be included in the master schedule. This includes devising and maintaining the master schedule, generating detailed observing schedules, and coordinating operational resources (disk modules, observing time, and correlator time). The contractor shall:

2.1 Develop and Distribute Schedules

a) Devise a master schedule for ~150 VLBI sessions to be delivered in November for the following calendar year and update at least monthly throughout the year.

b) Perform the duties of the Goddard CORE Operation Center for the IVS by being responsible for scheduling and coordination of observing and correlation of the IVS-R1, RDV, R&D and special sessions. Distribute schedules to stations at least 6 days prior to use.

c) Coordinate and make observing schedules for special sessions such as fringe tests.

d) Coordinate scheduling and testing of VLBI Global Observing System (VGOS) stations.

e) Monitor the status of new VGOS stations as they are built and include them in the sessions when they are ready.

2.2 Coordinate VLBI Activities

a) The contractor shall track and coordinate IVS shared resources to help ensure that there are sufficient media at the stations for observing and that there are sufficient correlator resources to process the data.

b) The contractor shall maintain an inventory of data disks at stations and correlators.

c) The contractor shall maintain session web pages and session status, station, correlator, and source monitoring statistics.

2.3 Station Support

a) The contractor shall support NASA VLBI stations as needed to troubleshoot, assess readiness, install software, provide training, test the system’s performance and integrity, and collect feedback and suggestions from the stations personnel. This should normally be performed remotely, but occasionally may involve travel to the stations.

b) The contractor shall assist non-NASA VLBI stations where NASA has a significant interest. This includes assistance with troubleshooting contractor developed software, guidance on experiment setup, etc. Assistance that requires a significant level of effort or changes to contractor developed software to support non-NASA systems must be pre-approved by NASA. All stations supported should be reported to NASA and assistance should be compliant with US export control laws and NASA policy.

3. VLBI Data Processing and Analysis The contractor shall support the IVS Analysis Center at GSFC to produce the core IVS products without interruption at a specified time lag to meet IVS requirements. The IVS core products, at a minimum, consist of Earth orientation parameters, station coordinates, and source coordinates. The contractor shall place the final results in IVS Data Centers for dissemination to researchers and other users. The contractor shall prepare VLBI data for correlation and analysis. This includes receiving and distributing field logs, preparing experiments for correlation, and tracking correlator usage. The contractor shall obtain all IVS and other NASA approved geodetic, astrometric, and specialized experiments from the responsible correlators and process the correlator output into calibrated data bases ready for initial analysis. This may include computing the VLBI observables, errors, and auxiliary data; creating the initial data base; inserting theoretical values, estimation quantities, and ancillary data; and inserting calibration and weather data. The contractor shall obtain VLBI data from other centers such as the U.S. Naval Observatory, the National Radio Astronomy Observatory, Max Planck Institute for Radio Astronomy, the Federal Agency for Cartography and Geodesy, the Jet Propulsion Laboratory, the Geospatial Information Authority, and the Institute for Applied Astronomy or from IVS Data Centers and prepare the data for analysis or reanalysis as needed. Specific tasks include:

a) The contractor shall import, process, and analyze all 24-hr geodetic/astrometric VLBI sessions performed by the IVS community. The contractor shall obtain VLBI data after their release by the correlators. The contractor shall parse log files and transform them to vgosDB format or other specified formats. The contractor shall perform calibration and data editing of VLBI datasets, flagging group delays, determining clock breaks, setting parametrization, and updating weight. The contractor shall maintain and update files of daily Earth Orientation Parameters (EOP), site coordinates, and source coordinates for use in computing the theoretical delays and rates.

b) After importing and preparing the 24-hr VLBI sessions, the contractor shall analyze, or re-analyze them in accordance with SGP requirements. The contractor shall compute an updated EOP series and submit it to the IVS Data Center after processing each new session.

Problems detected during analysis, not already reported by the correlators, will be reported to the particular station and to the IVS Network Coordinator. Statistical station performances and sensitivities (SEFD’s) will also be monitored by automated software.

Timeliness requirements will be monitored.

c) The contractor shall import and analyze all 1-hr Intensive (INT) sessions, using the procedures listed in a) and b) above in accordance with SGP requirements. A UT1 Intensive series will be updated with the results of each new session and submitted to the IVS Data Center, normally within 3 working hours of the data base arrival. Timeliness requirements will be monitored.

d) The contractor shall work in conjunction with NASA to process 6-12 VLBA geodesy sessions annually in accordance with SGP requirements within one month of data availability and submit results to the IVS Data Center.

e) The contractor shall work in conjunction with NASA to produce quarterly TRF solutions in accordance with SGP requirements. After NASA approval, the contractor shall submit the solutions in graphical and tabular form for posting to the SGP website.

f) The contractor shall maintain and develop programs used for the operational data analysis system in coordination with NASA. The contractor shall develop new capabilities and features of the operational software according to the NASA approved Future Software Release Document. The contractor shall maintain operational and development versions of VLBI analysis software in accordance with SGP requirements. The development version will be used to test new models or analysis techniques. As appropriate, changes made in the development version will be merged into the operational version after validation and verification, and approval by NASA. Only the operational version shall be made publicly available. If problems or bugs are reported, an acknowledgement shall be provided within 3 business days and the contractor shall correct them as quickly as practical. The contractor shall update as necessary user manuals and other documentation and distribute these with the software package and submit into TDMS.

g) The contractor shall develop and maintain post-processing programs to analyze and report output from the VLBI analysis software in coordination with NASA. The contractor shall develop new capabilities and features of the post-processing software according to the NASA approved Future Software Release Document.

h) The contractor shall submit the analyzed database files to the IVS Data Center for all VLBI sessions for which GSFC has responsibility. This will normally occur within two-working days of the database arrival for routine sessions such as R1s and Intensives sessions.

Sessions which require more analysis, such as R&D sessions or RDVs, shall be submitted as soon as practical. The contractor shall also submit cable calibration, Tsys, weather files and other calibration information for the above sessions. The contractor shall generate and submit SINEX solution files for all 24-hr sessions analyzed.

4. VLBI Research and Development The contractor shall perform and support NASA in VLBI research and development. This includes performing original research, preparing materials for reports and presentations, collaborating in scientific papers, and supporting the documentation of research results and the subsequent activities associated with the presentation of results at scientific meetings and with publishing in refereed journal articles. The contractor shall participate in technical and programmatic meetings and support critiquing the research of others working in related fields. The contractor shall identify all planned areas of research and development with contractor participation in the Research and Development Plan and Future Software Release Document. The document shall be updated at least quarterly to reflect progress and any NASA approved changes to the plan. Once approved by NASA, the contractor shall follow the plan. Research and development activities include:

a) The contractor shall advance the VLBI technique in the areas of instrumentation, calibration, modeling, algorithms, analysis, optimization, simulation, comparisons, combinations, and ancillary data.

b) The contractor shall design and implement procedures for improving observing schedules, for upgrading the geodetic catalog in coordination with NASA. The contractor shall evaluate and modify procedures for routinely monitoring geodetic sources as well as observing sources not in the geodetic set. The contractor shall investigate improving the scheduling algorithms for VGOS systems.

c) The contractor shall advance VLBI analysis tools with expanded capabilities for processing VGOS data in coordination with NASA and according to the NASA approved Future Software Release Document. The contractor shall develop automation capabilities for all stages of data processing.

d) The contractor shall study and support the combination of space geodetic data from VLBI and other techniques as well as site tie and other geophysical information to generate the terrestrial reference frame, measurements of EOP, and crustal dynamic models.

e) The contractor shall support ad-hoc studies and simulations performed by SGP, such combination of space geodetic data and network design studies.

5. VLBI Software Development The contractor shall design, develop, test, implement, document and maintain software and data files for scheduling, data monitoring, data acquisition, data handling, calibration, modeling, simulation, analysis, report generation, visualization, archiving, data distribution, web site, and utility functions. The contractor shall maintain the associated documentation with contractor developed software. The contractor shall collaborate with NASA and NASA partners on the development and testing of VLBI software. The contractor shall identify future features for all contractor developed software that are planned to be released over the next 2 years in the Research and Development Plan and Future Software Release Document. The document shall be updated at least quarterly to reflect progress and any NASA approved changes to the plan. Once approved by NASA, the contractor shall follow the plan. The contractor software development includes:

a) The contractor shall support the development of VLBI analysis software.

b) The contractor shall maintain and enhance the programs used to schedule VLBI sessions and maintain the associated catalogs. Alternative scheduling programs and capabilities shall be evaluated and assessed for adoption by SGP.

c) The contractor shall maintain the legacy Field System and associated tools (such as drudg) used by NASA VLBI stations and provide bug fixes and updates necessary to comply with NASA IT security requirements. The contractor shall deliver documentation and installation instructions with each software release. The contractor shall provide Field System troubleshooting support for operational NASA VLBI stations.

d) The contractor shall provide technical consultation and design guidance for the contractor’s developed Monitoring and Archival System (MAS) to support NASA’s maintenance and operations activity.

e) The contractor shall develop automation capabilities for VLBI standard “day in the life” procedural steps that currently require human (manual) interactions.

f) The contractor shall support VLBI hardware and software interface standardization activities.

g) The contractor shall update all relevant contractor developed software to support the latest version of VEX.

h) The contractor shall continue to support and maintain the vgosDB and vgosDA software and associated documentation.

i) The contractor shall support the development and utilization of the Space Geodesy Network Operations Center, including the development of a VLBI Dashboard.

j) The contractor shall develop and document procedures for the installation and utilizat ion of contractor developed software, including use cases such as the checkout of equipment, antenna pointing, and measuring system performance.

k) The contractor shall support training in the use of contractor developed software and procedures.

III. Space Geodesy Project Policy Compliance

1. Reporting

a) The contractor shall deliver weekly highlights according to the regular SGP schedule.

b) The contractor shall deliver detailed weekly status reports that include the previous week’s accomplishments and plan for the upcoming week. The weekly report may be in spreadsheet form (or other form as agreed to with NASA).

c) The contractor shall provide material on the group's activities, achievements, and products for posting on the SGP website.

2. System Administration and Information Technology (IT) Security

a) The contractor shall coordinate with the NASA IT Security and Systems Administration resources for hardware and software (system administration) support.

b) The contractor shall implement, enforce and monitor compliance with IT security policy and procedures in accordance with NPR 2810.1 for all contractor activities that utilize NASA IT resources.

c) The contractor shall ensure that hardware and software being delivered to stations are checked for vulnerabilities by IT security personnel and are compliant with NASA IT security requirements.

d) The contractor shall designate a single point of contact who will interface with the NASA Information System Officer (ISO) and the NASA Information Security Officer (ISSO) and be responsible for ensuring that all contractor developed software and systems are compliant with NASA IT security requirements.

e) Given the reliance of the VLBI technique on the contributions from international partners and required compatibility of scheduling tools, station hardware and software, correlators, and analysis tools it is important that the contractor maintain expertise in not only the technical aspects of the NASA systems, but also in the international partner systems as well. When the required expertise is not available within the domestic team, the contractor may provide the expertise through consulting or other relationships with the foreign experts. This expertise may be provided remotely from the expert’s permanent location outside the USA in a manner consistent with NASA and Space Geodesy Project IT security requirements.

3. Configuration Management Process

a) The contractor software development and maintenance processes shall be compliant with the Space Geodesy Project Information and Configuration Management Procedure, SGP-

MGMT-PROC-002.

b) The contractor shall establish a process to manage and control changes to the software and utilization of software version control and bug problem reporting tools approved by SGP such as Gitlab.

c) The contractor shall submit documentation/deliverables to the SGP Configuration Management Officer (CMO) for approval and archiving in the Technical Documentation Management System (TDMS).

IV. Travel

The contractor shall travel domestically and internationally to support activities consistent with this SOW.

V. Deliverables

1. Weekly Status Reports and Weekly Highlights

2. Monthly Progress Report: 15th of every month.

3. IVS Newsletter: three times per year.

4. IVS Master Schedule: each November and updated monthly.

5. Quarterly Solutions: every quarter.

6. Research and Development Plan and Future Software Release Document: updated quarterly.

7. IVSCC Website Future Release Document: updated quarterly.

8. IVS coordination contingency plan, updated annually.

9. New and updated versions of contractor developed software, within 1 day of release.

10. Monthly Software Status meeting to address the following:

a) Monthly progress

b) Plans for upcoming month

c) Government feedback on plans and activities

d) Gitlab reports on

e) Submissions

f) Issues

g) Issues resolution

11. Software Version Description document with each GitLab software submission to include:

a) Summary of changes and rationale

b) Associated GitLab Issue

c) Software Design Document on new development to include:

d) Purpose and function summary

e) Overall logic flow

f) Test strategy

g) Test results

12. Software release meeting prior to new software releases to discuss

a) Gitlab artifacts

b) Development

c) Testing strategy

d) Testing results

e) Readiness for release