Task 10-7 JPSS Program System Engineering.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: 5/7/21 Task Name: JPSS Program System Engineering Task No. / Mod: 10/7 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference: Enter the Function category and sub-section from the OMES-II Contract SOW that directly justifies the work of this task under the OMES-II contract. (A copy of the OMES-II SOW can be found in the TOMS Contract Library) EXAMPLE: Function 1(Technology Development Services), Sub Section B Instrument Systems Technology Services)

I. Scope

a. Background – This task is to provide engineering support services in accordance the

OMES SOW to the JPSS Program in the areas of mission systems engineering.

b. Summary of work – Contractor to provide system engineering support for JPSS Chief

Engineer and Program System Engineering team in performance of Engineering duties in order to meet NOAA level 1, 2 and 2.5 requirements for the end to end JPSS Mission, Flight and Ground Segment.

c. Required skills/knowledge – Senior level, detailed mission level, flight, and/or ground system engineering experience with NASA/NOAA Earth Science missions. Adherence to NASA System Engineering processes and reporting. Requirements management and DOORs support. Senior JPSS/NOAA science expertise in meeting NOAA’s operational mission utilizing JPSS mission data.

II. Period of Performance Task Mod Award – June 30, 2022

III. PSE Task Description For the cumulative description below a separate subtask for sub-charging to POR or PFO should be created. It is expected that most PSE engineers will be working across the overall POR/PFO timeframe and charging to both.

(OMES-II)

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

1. General -Support the JPSS Program Chief Systems Engineer to: review technical documentation; ensure software engineering processes conform to agency standards; review software metrics; perform requirements analysis; prepare programmatic and technical documents and briefs; convene and participate in special studies and review boards; lead evolution of JPSS and LEO system architecture and concept of operations to include advanced studies to identify, define and document alternative measurement and mission concepts to reduce the cost and risk associated with meeting mission objectives; provide subject matter expertise on operations, direct broadcast services, and frequency management.

2. General - Develop and track plans associated with Program Systems Engineering work on programmatic and technical documents and briefs; special and advanced studies.

3. General – Provide input and maintain the PSE risk; proved technical inputs to risk module with updates from each major PSE focus area (in bold). Support monthly PSE risk meeting.

4. Constellation Longevity – Support JPSS Flight Project and OSPO’s on-going responsibility to maximize the productivity and life of the constellation. A basic knowledge of Systems Engineering, particularly as it pertains to satellite and ground systems is required. While considerable expertise in many aspects of the S-NPP and NOAA-20 spacecraft and operations resides in the NOAA Office of Satellite and Product Operations (OSPO), the JPSS Flight Project, and the JPSS Ground Project, Program Systems Engineering requires a resident expert with ready access to the relevant technical information and subject matter experts. Specific areas of required support include:

a) Provide Program insight and support in anomaly resolution, management, and documentation.

b) Provide Program insight and support in Flight/Ground/OSPO coordination, preparation, and briefing of any operational changes to the satellites (flight software updates, orbital maneuvers, instrument calibrations, instrument operational changes, etc.).

c) Understand the potentially life-limiting components within the satellites (batteries, propulsion system, consumables, solar arrays, instrument scan motors and detectors, etc.), work with the Flight and Ground projects to identify possible ways to extend the life of the satellite, support background and decision briefings to NASA and NOAA management, and understand Flight/Ground/OSPO implementation of any life extension measures that are chosen for implementation.

5. Technical Review Leadership - Lead and manage the program/mission technical material for key JPSS satellite (milestones)

1) Provide technical insight into the integrated schedule and exchange planning between the JPSS Flight and Ground Segment Projects (i.e. giver/receiver) needed to support the JPSS managed and supported mission.

2) Provide technical input on appropriateness, completeness and linkage of Level 3 requirements verification activities needed to sell off Level 2 requirements.

3) Track Program-level technical metrics including system operational availability, data availability, and data latency.

6. Mission Orbit Analysis – Lead the mission analysis and planning support to the JPSS Program Systems Engineering and Flight Project via the Mission Orbit Analysis Working Group. The primary focus is on performing flight orbital dynamics modeling of space and ground assets to support requirements verification, operations, and technical studies for the JPSS constellation. Analysis activities include the following:

a) Hold MOAWG meeting consisting of PSE/Flight/Ground/OSPO/MOST coordination, preparation, and briefing:

1. Launch vehicle orbit insertion, orbit attainment, and mission orbit insertion analysis for JPSS-2.

2. Mission communications asset geometry analysis to optimize utilization of polar and space-based assets for JPSS mission constellation including NOAA partner missions.

3. Provide Launch and Early Orbit (L&EO) analysis for JPSS-2 orbit raising activities as needed to support the JPSS-2 Mission Operations and Support Team (MOST).

b) Provide NOAA Office of Satellite and Product Operations (OSPO) with SNPP and NOAA-20 analysis support in the areas of constellation management and maneuver planning to prepare for and enable safe insertion of the JPSS-2-JPSS-4 satellites into the JPSS constellation.

7. Concept of Operations – Lead the concept of operations (ConOps) development and planning efforts to support the JPSS Program via the ConOps Working Group. This forum includes OSPO, OSGS, JPSS Program, JPSS Ground and JPSS Flight Project participation.

1) Perform technical ConOps-related studies, analyses, and coordination supporting Program Office multi-mission planning and baseline requirements and ConOps evolution

2) Support various cross-team activities including MOAWG, Ground Project, Flight reviews, and JPS development

3) Support Advanced Studies and studies of planned JPSS system of system capabilities and abilities to satisfy operational availability, data availability, and data latency technical performance (TPM) requirements

8. Technical Baseline Management - Maintain and evolve the Level 1/2/2.5 Technical Baseline for JPSS to support the design of the J2-J4 missions in order to fulfill Level 1 requirements. Develop, maintain and evolve new baseline(s) as necessary.

1) Complete NOAA-20 and GSUP Block 2.x Level 1/2 V&V.

2) Multimission baseline which includes the MMSS, FSRD, Multi-Mission ConOps, and all external interface document. Manage updates for NOAA for L1RD changes.

3) Maintain the JPSS Program Verification and Validation Plan. Provide updates for each JPSS managed (J2-J4) mission at major milestone review to reflect the planned V&V events as defined for each individual mission.

4) Maintain the JPSS Program SEMP. Provide updates for each JPSS managed (J2-J4) mission at major milestone review to reflect the planned systems engineering activities.

9. Requirements and Verification Management - Perform requirements management for JPSS level1-2.5 baseline including change management, DOORS entry, tracing, and verification. Populate and manage the content of the DOORs Database for all Program/Mission Level Requirements.

1) Maintain the eRooms / DOORs requirements sell-off tracking tool for level 1 to 2.5.

Collect and link verification artifacts with DOORs requirements. Maintain metrics on requirements sell-off.

10. Technical insight into JPSS satellite and Ground System

1) Provide technical insight into Flight and Ground Projects system designs, attend key

MSRs, PMRs, and peer reviews a well as major milestone reviews and dry runs.

2) Attend and participate in any Flight or Ground ART or ARM’s

3) Lead Program ARM as needed (ie, SNPP Scan Drive issue)

11. JPSS Science Integrations - Support the calibration, validation, and monitoring of the Suomi NPP, NOAA-20, and JPSS-2 missions, including sensors and ground algorithms affecting mission system science performance.

12. JPSS ETE Science Verification and Validation Management- the verification and validation activities and sell off of Level 2 science performance requirements.

1) Complete the traces from Level 2 specifications to the Level 3 specifications for requirements and verification attributes. Ensure requirements flow of Level 1 requirements to Level 2. Coordinate changes with key NASA and NOAA Stakeholders.

2) Review JPSS sensor characterization testing plans, and test data interfaces to ensure completeness and data sufficient for supporting the production of compliant sensor data records.

3) Track the artifacts and Verification Decision Authority sign-off of Level 2/Level 3 science performance requirements.

4) Participate in the Level 3 science performance verification and validation test activities in support of the Program.

13. System V&V – Management – lead the verification and validation activities and sell off of Level 1 – 2.5 end to end system functional and performance requirements.

1) Complete the traces from Level 2 specifications to the Level 3 specifications for requirements and verification attributes. Ensure requirements flow of Level 1 requirements to Level 2. Coordinate changes with key NASA and NOAA Stakeholders.

2) Ensure the verification activities as described by the L2/L3 verification attributes, namely Verification descriptions, events, methods are sufficient to sell-off Level 2 requirements. Identify additional tests for areas that are not.

3) Track the artifacts and Verification Decision Authority sign-off of Level 2/Level 3 functional requirements and system performance.

4) Participate in the Level 3 Functional Verification and Validation test activities in support of the Program/mission requirement selloff.

5) Run necessary Mission Systems Working Group(s), as in Mission Orbit Analysis Working Group, ConOps Working Group, etc.

6) Run the Integration Issue Resolution Tiger Team Meetings.

7) Track and manage Flight/Ground and ESPDS/Ground Giver Receiver items

1 Monthly Status Reports Monthly Weekly/Biweekly

2 Monthly Variance Report Spreadsheet Performance Reports

Monthly

3 Monthly Deliverable Report (533M) Monthly

4 End-of-task Report End of task

Key Milestone Reviews requiring major PSE support and deliverables per NPR 7123.A

11/2021– JPS IVV Key

5/2022 – JPSS-3 dMOR

Point Review Other Key deliverables

- Major Milestone review briefing packages

V. Management Approach

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

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

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. Risks should be input thru the monthly PSE risk reporting process

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.

NOTE: Each Task Order should have specific performance metrics and should be detailed in the SOW. Examples of performance metrics are:

1. Percent completion of subtask

2. Planned versus actual

3. Delivery dates

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)

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 Space Flight 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

VI. 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)

Travel: TM shall pre-approve all travel.

1. Estimate 30 12 round trips (4 day duration) to Gilbert, Arizona in support of JPSS-2 satellite meetings in the timeframe during this POP

2. Estimated 13 round trips from Goodview, VA to Greenbelt, MD to support Program engineer team face to face meetings. (mileage only)

3. Estimated 2 round trips (4 days duration) from Baltimore, MD to Darmstadt, Germany to support JPS meeting during this POP

VII. Work Location

This work shall be performed primarily on-site at the Goddard Space Flight Center and via telework, but the contractor may be required to perform some work at the contractor’s facility or remote locations.

VIII. Reporting Requirements

a. Weekly or Bi-weekly status report The contractor shall generate Performance Reports every week to the TM. The report shall include, as a minimum, a summary of the week’s highlights/accomplishments, milestones/schedule/deliverables, risks and customer meetings.

b. 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. The contractor, including subcontractors, shall be available to attend monthly status meetings.

The contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports.

Monthly Subtask Report Spreadsheet

The contractor shall provide a break out of hours and costs by close of business on the 15th 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 NPR 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 shall adhere to project requirements regarding ITAR related information, as controlled by the ITAR, 22 CFR 120-130, by the U.S. Department of State. Any transfer of controlled information to a foreign person or entity requires an export license issued by the U.S.

Department of State or an ITAR exemption to the license requirement prior to the export or transfer.

This task shall not require handling of 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

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

1. NPR 7150.2A NASA Software Engineering Requirements

2. GPR 7150 Goddard Software Engineering Requirements

XIII. References - NA