Task 5-6 JPSS Ground Project DPMS Support.pdf

Omnibus Multidiscipline Engineering Services II (OMES II) All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions

Task Order Statement of Work (SOW) Date: April 20, 2021 Task Name: JPSS Ground Project DPMS Support Task No. / Mod: 5/6 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference: Function 3 Implementation Phase [D. Software systems engineering, studies, analysis and support] and Function 4 Operational Pase [A. Data Systems Management Services]

This mod includes: Modifying the POP from Jun 5, 2021 to June 30, 2022 and updates to change AIT work on the on-premises G-ADA to the cloud system (DP-AE)

I. Scope

a. Background The Joint Polar Satellite System (JPSS) is the National Oceanic and Atmospheric Administration’s (NOAA) next-generation operational Earth observation Program that acquires and distributes global environmental data from multiple polar-orbiting satellites. The JPSS Program plays a critical role to NOAA’s mission to understand and predict changes in weather, climate, oceans, and coasts environments, which supports the nation’s economy and protects lives and property. The National Aeronautics and Space Administration (NASA) is acquiring and implementing the JPSS, comprised of flight and ground systems on behalf of NOAA. The JPSS satellites are planned to fly in afternoon orbit and will provide operational continuity of satellite-based observations and products for NOAA Polar-orbiting Operational Environmental Satellites (POES) and the Suomi National Polar-orbiting Partnership (SNPP) satellite.

NOAA is responsible for the JPSS program, while NASA is the program's procurement agent, and Goddard Space Flight Center (GSFC) is the lead for acquisition. The JPSS Ground Project, Goddard Code 474 under the Goddard JPSS Program Office is responsible for the design, development and deployment of the JPSS Common Ground System (CGS), a multi-mission command, control and communication and operational data production system. JPSS Ground Project primary customers are the weather Centrals Fleet Numerical Meteorology and Oceanography Center (FNMOC), Naval Oceanographic Office (NAVO), Air Force Weather Agency (AFWA) and the National Environmental Data and Information Service (NESDIS).

The ground system is organized into eight functional nodes. A node is collection of functions, computers, software, personnel, processes, and procedures to achieve

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions specific goals. The eight nodes are: the Space/Ground Communications Node, the Ground Network Node, and the Management and Operations Node, the Data Processing Node, the CGS Support Node, the Simulation Node, the Calibration/Validation (Cal/Val) Node, and the Field Terminal Support (FTS) Node.

The CGS is comprised of the Space/Ground Communications Node, the Ground Network Node, the Management and Operations Node, the CGS Support Node, and the Data Processing Node.

The Data Products Management and Services (DPMS) is responsible for the Cal/Val, FTS node and the Algorithm Management Project (AMP). All of the work within DPMS is accomplished via in-house support service contractors and not through the prime contractor Raytheon. The DPMS team has the following elements (1) Sustainment (Government Resource for Algorithm Verification Independent Test and Evaluation (GRAVITE),Data Quality Support Team (DQST), Field Terminal Support (FTS)),

(2) Systems Engineering Integration and Test (SEI&T), (3) Operations, (4) IT, (5) Transition of FTS to OSPO, (6) Algorithm Management Project (AMP) (now includes DP-AE and the Algorithm Integration Team (AIT)).

JPSS recently migrated parts of the Ground System to the cloud. The G-ADA, the system which the AIT accomplishes their work, is now referred to as the DP-AE and is part of the Core Ground System (CGS) under the prime contractor. In addition, the Ground Project may determine to move GRAVITE into the cloud. This work will be done as part of the usual sustainment activities associated with DPMS. FTS is expected to transition to OSPO in July 2021.

This Task Order (TO) is issued to support the JPSS Ground Project DPMS team for the acquisition to provide multidiscipline engineering and scientific support services for the study, design, systems engineering, development, integration, testing, verification, calibraton and validation, sustainment, maintenance, and operations of ground system hardware and software, DP- AE, and FTS transition activities. The contractor shall provide engineering and scientific subject matter expertise and project monitoring communication and coordination both within the larger JPSS Ground Project Segment, the CGS prime contractor and with external stakeholders in support of all DPMS activities.

b. Summary of Work

Sub-task I DPMS (formerly DPES)

Sub-task I: DPMS The contractor shall provide technical and engineering services and leadership to include but not limited to:

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions

Engineering Support to DPMS Operations

• Manage a team of contractors supporting operations

• Perform all tasks necessary to operate DPMS systems

• Create weekly and monthly reports for management

• Brief management on activities being performed, as necessary or requested

• Coordinate activities as necessary within DPMS and other stakeholders

• Develop, maintain and monitor DPMS Operational SOP, Schedules and Risks.

• Support various DPMS and JPSS meetings as necessary

• Manage relevant SCoRes, CCR’s, CMR’s, and Waivers and other necessary change management processes

• Monitor the operational and test systems, report breaks in Science dataflow or anomalies

• Develop improved monitoring tools for accurate reports and anomaly detection

• Test new versions of GRAVITE software prior to and if warranted during SEI&T testing

• Monitor system health and performance, trouble shoot and respond to anomalies and issues and report to DPMS lead, System Owner (SO) and ISSO

• Support DPMS related reviews (e.g. design reviews, code reviews, schedule reviews)

• Coordinate with management and obtain necessary approvals

• Communicate system status to management, operators, system administrators, SO, ISSO, users, DPMS staff and external mission partners as necessary

• GRAVITE account management and support

• Monitor DPMS engineering technical performance and provide/implement improvements

• Support FTS transition

• Support DPMS and JPSS Ground Segment Project Cloud; as needed

Direct Systems Support to DPMS

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions

• Coordinate and work with a team of contractors supporting IT

• Help develop, maintain and monitor DPMS IT Schedules and Risks.

• Support various DPMS and JPSS meetings as necessary

• Manage relevant SCoRes, CCR’s, CMR’s, and Waivers and other necessary change management processes

• Monitor the DPMS systems

• Assist with software/firmware updates and troubleshooting issues

• Support security audits

• Support DPMS and JPSS Ground Segment Project Cloud; as needed

DPMS Software Engineering and Data Quality Engineering Support

• Management of sustainment activities

• Work with the JPSS Program, the JPSS STAR Science Teams and the NOAA Office of Satellite Operation (OSPO) Data Operations Manager (DOM} and Product Area leads (PALs) to define process and procedures to assess and monitor operational data quality.

• Develop test plans, execute tests and troubleshoot data anomalies.

• Support the IDPS Data Quality Engineer (DQE) to resolve or characterize discrepancies found by the DQE and elevate to the DPMS management and JPSS STAR Science Teams as necessary.

• Maintain ASF PGEs and data quality tools and processes.

• Provide design, development, sustainment, maintenance, integration, testing, and deployment of software modules, and user training support

• Perform systems engineering tasks consistent with applicable NASA and/or NOAA (as applicable) systems engineering policies and practices, unless otherwise directed by the COR

• Participate in activities with external mission partners (e.g. technical interchange meetings, interface testing) as needed

• Support DPMS related reviews and trade studies (e.g. design reviews, code reviews, schedule reviews)

• Coordinate with operators, system administrators, users, DPMS staff, OSPS DQEs, JPSS team members and external mission partners to support DPMS activities.

• Communicate system status to management, operators, system administrators, users, DPMS staff and external mission partners as needed

• Analyze and prototype advance and enterprise technologies for the purpose of reducing life cycle and maintenance costs or as defined by management

• Coordinate and Participate in activities with DPMS, JPSS and external mission partners as needed in support of operations, maintenance, and other related activities

• Coordinate with other JPSS Ground Project organizations, including JPSS Ground Software Assurance, Mission Assurance, Security, and Ground Project SEIT, as needed, to assure DPMS systems are in accord with overall Ground Project objectives, plans and guidance

• Provide project management support including tracking schedules, identifying risks, and working with the stakeholders to mitigate or resolve issues or challenges, and assist in managing development, verification, implementation, and maintenance of the DPMS systems

• Provide support for the sustainment and transition of Field Terminal Support (FTS) to OSPO

• Develop and Maintain DPMS documents

• Provide project management support including tracking schedules, identifying risks, and working with the stakeholders to mitigate or resolve issues or challenges, and assist in managing development, verification, implementation, and maintenance of the DPMS systems

• Maintain and support algorithm segment of DPMS Integrated Master Schedule (IMS).

• Support JPSS DPMS and Ground Segment Project Cloud; as needed

DPMS Systems Engineering Integration and Test Support

• Perform systems engineering activities maintained and/or managed by DPMS consistent with applicable NASA and/or NOAA (as applicable) systems engineering policies and practices, unless otherwise directed by the COR

• Coordinate with other JPSS Ground Project organizations, including JPSS Ground Software Assurance, Mission Assurance, Security, and Ground Project SEIT, as needed, to assure that DPMS -managed activities and systems are in accord with overall Ground Project objectives, plans and guidance

• Identify, plan, develop and maintain schedule for successful internal and external DPMS milestones

• Implement a technical assessment process to monitor progress of the GRAVITE and FTS effort throughout the life cycle

• Support system-level coordination with the MSE and stakeholders on SEI&T, Requirements, interfaces, and performance issues

• Monitor and assess management of hardware and software resources

• Ensure that requirements are traced correctly to test events and documented in the RTM and other locations as appropriate

• Support the various test reviews (Test Readiness Reviews (TRR), Operational Readiness Reviews (ORR), etc).

• Prepare, review, maintain and execute test plans, cases, procedures and reports

• Provide expert guidance regarding schedule, software test events, tools, and other activities

• Provide technical guidance related to JPSS Ground and Project SEI&T activities

• Provide technical information to Safety/Mission Assurance

• Develop and maintain DPMS documentation and ensure that all DPMS related documents are updated as required. This includes both “System Level” documents and lower level documents

• Maintain the Document Management List (DML) (as per the DPMS CM Plan)

• Serve as primary POC for system level interfaces in order to track, monitor, and compare implementation of interfaces against the baselined documents

• Prepare and maintain hardware design documentation and coordinate with appropriate stakeholders as necessary for hardware related issues

• Develop short/mid/long term/tech refresh hardware designs, plans, trades, parts lists, cost estimates, and spending profiles for DPMS

• Manage procurement and tracking of hardware, software, software license renewals, and other items

• Perform and assist in hardware and other audits as necessary and maintain a permanent record of all results and resolve any issues

• Coordinate with hardware vendors to address hardware related problems and their resolution

• Provide quality of service metrics, security summary spreadsheets, and hardware/software maintenance agreement tracking reports as needed

• Documentation and design of System Level Architecture

• Support and evaluation of DPMS system design proposals

• Creation of system architecture and design related white papers, recommendations and other communications

• Track government-procured hardware and software in support of DPMS

• Maintain SOPs related to account management and procurement/tracking

• Assist in various DPMS audits

• Maintain and support algorithm segment of DPMS Integrated Master Schedule (IMS).

DPMS AIT Support

• Provide necessary support for the DP-AE environment including working as necessary with IDPS to install and test new IDPS SW releases onto the DP-AE.

• Provide necessary development of custom software and training to DPMS and/or Cal/Val team members in the use of the DP-AE, as requested.

• Assist the algorithm teams with preparation and submission of Algorithm Change Packages (ACPs), Algorithm Discrepancy Reports (ADRs), Configuration Change Requests (CCRs) and associated and supporting documents.

• Receive, integrate, run, test the ACPs or other computations in the DP-AE as requested

• Support DPMS in the evolution of the operations, requirements, design, sustainment etc. for the DP-AE

• Serve as DPMS’s technical liaison for Algorithm Development Library (ADL) to CGS contractor and Users as necessary.

• Install and maintain an ADL user environment within the GRAVITE (Government Resource for Algorithm Validation, Independent Test and Evaluation) system and provide DPMS with general technical advice and assistance concerning ADL.

• Provide technical and management administration of the government-side JDRS , including enrolling and training users; providing user information to the CGS contractor so that user accounts may be created and maintained. Provide DPMS with general assistance and advice concerning the DPMS use of JDRS.

• Coordinate activities with external “givers” and “receivers” as necessary to identify, track, and mitigate issues.

• Maintain and support algorithm segment of DPMS Integrated Master Schedule (IMS).

• Support IDPS Build-to-Build (BtB) activities to include coordination of proposed code changes and requests for Factory Benchmark Test (FBT) and Integration, Test, and Check-Out (ITCO) data.

• Serve as Common Configuration Management (CM) lead and assist in the coordination of the ADL updates between the DPMS -AIT, STAR-AIT and Raytheon.

• Interact with DPMS testing group to test weekly and monthly look-up tables (LUTs).

• Serve as Systems Requirements Specification Parameter File (SRSPF) and Algorithm Change Management Plan (ACMP) “book boss” and provide inputs for the DPMS Risk Boards.

• Support the Algorithm Discrepancy Report Action Team (DRAT) in coordination and tracking of Discrepancy Reports (DRs), compilation of meeting minutes and facilitation of comments and concurrence by stakeholders.

• Coordinate the weekly DRAT, assist in the organization of the AERB, Raytheon Tier 1 meetings, participate and contribute to the Weekly Schedule Meetings, and participate in the Project Monthly Reviews (PMR) Algorithm Splinter meetings as needed.

• Provide DPMS management with advice and improvements related to algorithm software engineering and DPMS’s support of algorithm Cal/Val, maintenance, integration, tools, data product quality monitoring, etc.

Sub-task V: DRL The contractor shall provide developers from the Direct Readout Laboratory (DRL) to support the FTS Node and the Commercial Ground Service Demo. The DRL is developing custom software technologies to work with S-NPP and JPSS science algorithms.

The DRL will concentrate on the following areas of development:

• Develop software (RT-STPS) that produces RDRs that are consistent with IDPS and therefore compatible with the ADL unpacker (CDRL8)

• Report HRD anomalies to OSPO per the OSPO Anomaly Reporting Procedure (01-57)

• Support the JPSS Ground Project in the commercial ground services demo

a. Augment the direct readout lab software (RT-STPS / CSPP) to accept stored mission data (SMD) / channel access data units (CADUs) for processing raw data records (RDRs) and downstream senor data records / environmental records (SDR/EDR) processing in a ground demo cloud environment; participate in cloud demo environment establishment, including data routing protocols / account set up

b. Augment the software to accommodate simultaneous current incoming SMD streams

c. Support the demo configuration definition, setup and checkout

d. Participate in the demo execution, analysis, and troubleshooting

e. Identify recommendations and lesson learned

Sub-task VI: AMP Sensor and Environmental Data Record Science The contractor shall provide technical services to include but not limited to:

• Serve as liaison between, interface between, and coordinate among the JPSS Program, JPSS Flight project, JPSS Ground Segment, JPSS Program Science, the JPSS STAR Science Team Leads, OSPO DOM and PALs, and external groups on matters related to algorithm and data product performance and requirements, system interface definition, interface compliance, requirements verification and validation, data flows and test events, and overall system and user requirements satisfaction and make recommendations to improve customer satisfaction.

• Serve as a liaison between Flight and Ground to assess impact of sensor performance waivers on data product performance, provide results of anomalous performance in sensor data products for JPSS Flight Project assessment and appropriate action on sensor characteristics and design, develop and review sensor and environmental data products requirements and performance, and provide guidance to Flight Project on adequacy of flight sensor test program and calibration and characterization sources used in the fight sensor test program.

• Lead the implementation and support the algorithm change process, including facilitating Algorithm Engineering Review Board (AERB) and its subsidiary working groups such as the Discrepancy Report Action Team (DRAT), writing Algorithm Discrepancy Reports (ADRs) and Configuration Change requests (CCRs), and providing technical and engineering expertise on algorithm discrepancies and changes.

• Provide presentations and publications on sensor and environment data products, performance matters at scientific meetings, conferences and research journals, and provide, as needed, expertise in the Physical Sciences including Atmospheric and Space Physics, Meteorological and Oceanographic Forecasting, Communications and Networking, Computers and Software, Systems Engineering.

• Provide technical expertise in data product formats (e.g, NetCDF, HDF, BUFR, GRIB2, GeoTiff, etc), common software languages, Open Geospatial Consortium (OGC), Cloud computing, and other common software practices and standards, system interfaces, and satellite data generation and distribution

• Review the algorithms and calibration and validation documents as necessary to ensure that the documents meet the programs’ standard.

• Attend the product lifecycle reviews and validation reviews for JPSS SDRs and EDRs, to ensure the data products’ development and validation are executed as planned, and the product performance meets the specs

• Recommend or contribute to JPSS Algorithm Project policy and strategy and assist in the documenting algorithms and technical reports.

• Provide project management support including tracking schedules, reporting on the status of the planned deliverables, milestones, identifying risks, and working with the stakeholders to mitigate or resolve issues or challenges, and assist in managing development, verification, implementation, calibration, validation, and maintenance of the JPSS Program's science algorithms and associated data products.

VI. Management Approach

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions

a. Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.

b. Configuration Management

Ensure DPMS follows the necessary NPR 7150.2B NASA Software Engineering Requirement & NPR 7123 System Engineering Standards.

c. Facilities Appropriate IT devices to support the analyses, specification development, and report development are required. It shall be the contractor’s responsibility to provide and set up local workstations and network connections at the contractor’s off-site facilities as required, and to install any required tools and utilities on the contractor’s equipment.

d. Risk Management and Best Practices The contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the compliance of the TM.

e. Performance Metrics The work performed for this task will be evaluated by the TM based on the technical merit. The TM shall develop detailed performance metrics that shall reflect the contractor’s performance in meeting research analysis, specific mission requirements, deliverables and delivery schedule, and the contractor’s cost. Technical evaluation of the task performance is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.

Specific performance metrics include:

1. Percent completion of subtask

2. Planned versus actual

3. Delivery dates

4. Delivered lines of code (LOC)

5. Reporting

f. Government Furnished Facilities, Equipment, Software and Other Resources The Government will provide account and passwords to government-furnished workstations where existing versions of various relevant software packages shall be maintained. It shall be the contractor’s responsibility to complete any GSFC required security-related training courses.

NASA shall provide office space within NASA/GSFC facilities for on-site personnel. Infrastructure, including computers, cell phones, blackberries, etc. shall also be provided where necessary. The place of performance will be on site at the GSFC JPSS facility (Building L40). Any conflicts discovered by the Contractor between the requirements in this SOW and any referenced specification herein shall be brought to the attention of the Task Monitor, or his representative, for resolution.

g. Quality Assurance Requirements

(See Clause I.1 1852.216-80 TASK ORDERING PROCEDURE (d) (4) and QA plan) The contractor shall comply with the JPSS Project’s Quality Assurance Plan. The contractor providing technical services shall comply with all CMMI Level 2 processes established for the Project and deliverable products. Applicable requirements include, but not limited to:

1. NPR 7120.5D NASA Program and Project Management Requirements

2. NPR 7123.1A NASA Systems Engineering Processes and Requirements

3. GPR 7120.1C Project Management

4. GPR 7120.5A Systems Engineering

VII ODC (Travel and Procurement)

(See I.1 1852.216-80 TASK ORDERING PROCEDURE d (6), please provide a BOE for all proposed ODC’s to determine the reasonableness) The contractor shall receive prior authorization from the Task Monitor and Contracting Officer, or her/his representative, for all travel associated with the conduct of this SOW. Travel may be proposed for Technical Interchange Meetings (TIMs), workshops, conferences, special training needs and other engineering support task activities as directed by the task monitor. Travel will be to meet with the ground system development contractor and observatory providers at contractor facilities (Aurora, El Segundo, XI. Safety

The OMES-II Safety/Mission Assurance Officer shall:

a. Ensure all contractor personnel understand their safety responsibilities and follow safe practices for all lab and office operations.

b. Ensure branch training requirements for contractor employees are implemented.

c. Attend safety related training applicable to the operations under their area of responsibility.

The contractor personnel shall:

a. Follow safety requirements when performing any task, keeping their workplace in a safe manner.

b. Attend all required training, set forth by the OMES-II Safety/Mission Assurance Officer, ensuring certifications are current.

XII. Data Rights

This SOW shall adhere to the following Data Rights clause, as stated in this contract: “the default Data Rights clause under this contract is FAR 52.227-14 RIGHTS IN DATA-GENERAL as modified by NASA FAR Supplement 1852.227-14-Alternate II and Alternate III and GSFC 52.227-90. Any exceptions to this clause will be covered by FAR 52.227-17 RIGHTS IN DATA- SPECIAL WORKS as modified by NASA FAR Supplement 1852.227-17, and, if applicable, GSFC 52-227.93”

XIII. Applicable Documents

In the performance of this task, the contractor shall comply with the following documents:

a. NPR 7150.2A NASA Software Engineering Requirements

b. GPR 7150 Goddard Software Engineering Requirements

c. NPR 7123 NASA System Engineering standards

XIV. References

JPSS documents available and baselined in the MIS.

XV. NASA Task Monitor Redacted