Task 8-8 JPSS IDPS System Support.pdf

PDF 2 MB Posted

Attached to
NASA/GSFC Omnibus Multidiscipline Engineering Services (OMES) III, elibrary
Solicitation number
80GSFC21R0046-elibrary
Issued by

View the file

Other files

Show all 21

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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: November 10, 2021 Task Name: JPSS IDPS System Support Task No. / Mod: 8 / 8 Task Monitor (TM): Redacted Task Period of Performance: Task Award Date – 6/30/2022 Contract number: NNG17CR69C Contract SOW Reference: Function 3 (Implementation Phase Services), Sub Section B (Mission

Systems Engineering)

Mod Summary: Extended POP

I. Scope

a. Background – The Joint Polar Satellite System (JPSS) mission is to provide military and civilian agencies with environmental, meteorological, and climatological data and products. The Common Ground System (CGS) provides command and control of the National Polar-orbiting Operational Environmental Satellite System (NPOESS) Preparatory Project (NPP) and JPSS spacecraft and instruments. The CGS transports commands, telemetry, and mission data between the space, ground control, and processing facilities and the Customer locations, and enables mission planning, asset management, and delivery of the mission products. Interface Data Processing Segment (IDPS) is part of the Common Ground System (CGS). The IDPS is responsible for the receipt of raw mission data from the Command, Control, and Communications Segment (C3S) and for creating and delivering useable environmental products to Users. IDPS ingests Stored Mission Data (SMD) received from C3S – the artifacts from satellite on-board storage and ground communication routing are removed prior to arrival at the IDPS. The initial ingest processing provides raw data records (RDR; per sensor/channel raw bits) that are subsequently processed to create Sensor Data Records (SDR;

geolocated and calibrated samples), Temperature Data Records (TDR), deliverable Intermediate Products (IP), and Environmental Data Records (EDR; higher level products). The RDR, SDR, TDR, deliverable IP, and EDR products are made available to user systems, for use in application specific, weather related predictions.

b. Summary of work – The contractor shall provide the support services described in the Subtask Description section.

Subtask 1: The contractor shall provide systems engineering and sustainment support for IDPS, inter-segment coordination, and external interface negotiation and evaluation.

Subtask 2: The contractor shall provide systems engineering support for Polar Follow-On (PFO) for the JPSS IDPS team.

Required skills/knowledge –

The contractor shall have a strong technical base in the following areas:

- Spacecraft, instrument and satellite data and associated formats

- Earth Science ground data systems, processing and archiving.

At a minimum, all the personnel shall have the following skills:

- Earth observing mission system engineering skills

- Knowledge of system engineering and integration and data analysis tools

- Knowledge of system engineering standards

- Strong ability to independently lead and interact with distributed team members and different corporate cultures

Additional preferred skills include:

- Experience in system integration and mission data formats; test data generation and system propagation

- Direct, relevant experience and familiarization with NPP / JPSS system architecture and organizational structure

II. Period of Performance

The period during which the work for this task shall be performed is from task award through June 30, 2022.

III. Subtask Description

Subtask 1: The contractor shall provide systems engineering and software engineering support and technical oversight of the IDPS ground system segment.

The systems engineering objectives include:

o Change Control Requests (CCRs) and Engineering Change Requests (ECRs) evaluation o Configuration Modification Request (CMRs) evaluation o Ground Project Discrepancy Reports (DRs) evaluation o Algorithm Discrepancy Reports (ADRs) evaluation o Requirements evaluation/suggestion o Regression Test Procedure negotiation and evaluation o Inter-segment coordination and participation in external interface negotiation and evaluation (e.g. mission data issues, product calibration/validation and algorithm updates with appropriate science teams/groups, etc.)

o Manage Fast Track and out of cycle (OOC) table updates o Systems engineering support and technical oversight for JPSS

The software engineering objectives include:

o Evaluate code/design update and provide feedback in a timely manner to meet the program objectives o Evaluate IDPS Problem Change Requests (PCRs) provide feedback at weekly PCR Board meetings as well as coordinate PCR submission with the IDPS contract (Raytheon) o Support weekly Build Content Review (BCR) meetings o Participate in software and hardware evolution discussion o COTS/FOSS evaluation o Regression Test Procedure evaluation

Subtask 2: The contractor shall provide system engineering support and technical oversight for Polar Follow-On (PFO) that includes concept of operations, requirements

Systems and documents will be covered under the Project Configuration Management Plan.

c. Facilities

Subtask 1,2: Staff are planned to be housed on-site in Building 40. Appropriate IT devices to support the analyses, specification development, and report development are required and provided by GSFC.

d. Risk Management and Best Practices

The contractor shall manage schedule, cost, and technical risk through oversight, monitoring and reviewing 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 performance (completeness and accuracy) of the contractor that includes the following:

Evaluation of IDPS software and hardware evolution proposed by Raytheon

Evaluation and/or resolution of PCRs, CCRs, ECRs, DRs, ADRs, and IRDs/ICDs

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.

g. Quality Assurance Requirements (See Clause I.1 1852.216-80 TASK ORDERING PROCEDURE (d) (4) and QA plan)

VII. Work Location

Subtask 1-2: This work shall be performed primarily onsite at Government provided facilities.

VIII. Reporting Requirements

a. Monthly Progress Reports

The contractor shall provide monthly technical and schedule progress reporting to adequately describe the activities of the contractor team to the TM. The contractor shall provide monthly cost reporting in accordance with the WBS.

Monthly Subtask Report Spreadsheet

The contractor shall provide a break out of hours and costs by close of business on the 10th of each month to the Contract Officer, Contract Resource Analyst, and the Task Monitor. The report spreadsheet shall include current period hours, costs, cumulative-to-date hours and costs, and cumulative costs with a one-month cost plan. When needed, the contractor shall make adjustments to the distribution of costs, layout of the report and change reportable elements as specified by the Task Monitor and/or the Contract Resource Analyst.

IX. Security Requirements

The contractor shall comply with Information Technology Security procedures and requirements as defined by NPG 2810.1A in the performance of this task. In addition, the contractor shall comply with all applicable federal rules and regulations and agency directives. The contractor will not be required to handle classified data.

X. Safety

The OMES-II Safety/Mission Assurance Officer shall:

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

Ensure branch training requirements for contractor employees are implemented.

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

The contractor personnel shall:

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

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

XI. 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.”

XII. Applicable Documents

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 7150.2A NASA Software Engineering Requirements

2. NPR 7120.5D NASA Space Flight Program and Project Management Requirements

3. NPR 7123.1A NASA Systems Engineering Processes and Requirements

4. GPR 7120.5A System Engineering Requirement

5. GPR 7150 Goddard Software Engineering Requirements

6. JPSS Ground System Requirements Document

7. JPSS System Integration and Test Plan

8. Mission Level Interface Control Documents (ICDs)

9. JPSS Level 1 Requirements

XIII. References

File details come from the government source that posted it. Updated .