Task 4-12 JPSS Flight Software Systems Eng Sup.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: 25-Jan-2021 Task Name: JPSS Flight Software Systems Engineering Support Task No. / Mod: 4/12 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference: Function 3 (Implementation Phase Services), Subsection D (Software Systems Engineering, Studies, Analysis, and Support)

Summary of changes in Task 4 MOD 10: Extend POP 12 months to 01-Apr-2022.

I. Scope

a. Background

The Joint Polar Satellite System (JPSS) Flight Project (FP) Flight Software (FSW) Systems Engineering (SE) Group performs acquisition management, technical oversight, monitoring of software engineering processes and standards, and full lifecycle support for the flight software elements on all JPSS missions (S-NPP, NOAA-20, and JPSS-2/3/4) on behalf of the JPSS Flight Project. JPSS Flight Software Systems Engineering Support specified within this task provides technical engineering support to the JPSS Flight Project FSW SE Group Lead (a.k.a. the JPSS Flight Software Acquisition Manager) across all of these elements.

b. Summary of work Provide technical insight/oversight support for flight software development and maintenance, including software engineering processes and standards, for the instruments and spacecraft busses during the full lifecycle of the S-NPP, NOAA-20, and JPSS-2/3/4 missions, as directed by the JPSS Flight Software Acquisition Manager. This effort entails insight over vendors supplying software to the JPSS Flight Project via site visits, established communication with provider Flight Software teams, and review of numerous documentation/deliverables/artifacts. Specific support areas include but are not limited to:

1. requirements definition and trace

2. preliminary and detailed/critical design

3. implementation/coding

4. unit-level and integration-level software testing

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

5. system integration, test, and troubleshooting

6. support of launch and early spacecraft operations through deployment and commissioning

7. post-launch support for anomaly resolution and continuing development

Related duties shall include, but are not limited to:

1. review and assessment of delivered documentation

2. preparation for and participation in associated peer reviews and technical meetings

3. adherence to and assessment of products against applicable software processes and standards (e.g. NPR 7150.2A/B/C)

4. adherence to and assessment of products against applicable contractual documentation (e.g. vendor Statements of Work [SOWs], Contract Data Requirements Lists [CDRLs], Satellite Requirements Documents [SRDs], etc.)

5. support of development of products for spacecraft operations

6. support of development of simulators, software test benches, and software for ground/integration support equipment

7. evaluation of artifacts for requirements verification and sell-off

8. coordination and resolution of technical issues with other JPSS personnel representing assorted technical disciplines (e.g. electrical, mechanical, thermal, etc.)

and interests (e.g. operations, ground system, simulators, etc.)

9. participation in reviews and disposition of analyses generated by NASA Independent Verification and Validation (IV&V) Facility

10. monitoring compliance with requirements for software engineering processes and standards for the spacecraft and instruments

Perform other technical activities at the direction of the JPSS Flight Software Acquisition Manager.

c. Required skills/knowledge The contractor shall have an appropriate four-year engineering degree and a minimum of eight years of experience implementing flight software systems for NASA spacecraft.

The contractor shall have functional knowledge of the elements and subsystems composing contemporary civilian scientific spacecraft, and the considerations regarding their development, operation, and maintenance.

The contractor shall have a strong technical base of experience in the development and application of embedded real time software control systems as applied to civilian scientific spacecraft. This includes the development, implementation, integration, test, operation, maintenance, and troubleshooting of flight software - for spacecraft control (e.g. power, communication, attitude control, etc.), payload control (i.e. scientific instruments), and command and data handling.

The contractor shall have practical experience working with rigid software development processes and standards.

At a minimum, the contractor shall also have the following skills:

1. Hands-on experience with development of onboard flight software systems for meteorological or scientific satellites

2. Knowledge of NASA software engineering standards, processes, and best practices (e.g. NPR 7150.2A/B/C, GOLD Rules, etc.)

3. Experience in coordinating stakeholder teams to define engineering interfaces and technical processes

4. Experience with mission readiness preparation and post-launch operations

5. Experience in collaborating with spacecraft and instrument supplier technical personnel to investigate and resolve issues

6. Experience using high-fidelity simulators to verify and troubleshoot flight software systems

7. Knowledge of systems engineering and integration tools

8. Knowledge of flight systems engineering information management

9. Experience documenting and reporting discrepancies

10. Experience documenting and reporting risks

11. Experience with the definition, implementation, verification, and troubleshooting of the SpaceWire communications protocol for instrument communications within JPSS-class spacecraft

12. Experience with the definition, implementation, verification, and troubleshooting of the 1553 communications protocol for instrument communications within scientific spacecraft

13. Experience with the VxWorks real time operating system

14. Experience with the definition, implementation, verification, on-orbit installation, and post-installation verification of instrument flight software version updates for S- NPP/JPSS-class (or other civilian scientific) spacecraft

15. Experience in collaborating with NASA IV&V personnel and Government contractors to evaluate and resolve findings from IV&V analyses relating to S- NPP/JPSS-class (or other civilian scientific) spacecraft

16. Outstanding communication and interpersonal skills for communicating technical information to personnel of assorted technical backgrounds

17. Knowledge of configuration management principles and experience with using related tools

II. Period of Performance

(Tasks will be issued with no more than 12 month periods of performance unless otherwise justified and approved)

The period during which the work for this task shall be performed is from initial start of task on July 01, 2017 thru April 01, 2022.

III. Subtask Description There are no subtasks.

Monthly Deliverable Report The contractor shall provide no later than the 10th working day following the close of the contractor’s monthly accounting period a 533M for each individual subtask and a summary 533M at the total task level. If it is not possible to provide the individual 533M at the subtask level, the contractor shall provide on the 10th working day following the close of the contractor’s monthly accounting period a break out of hours and costs by subtasks to the Contract Resource Analyst, Contracting Officer, and the Task Monitor. The report shall include current period hours and 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.

IV. Deliverables/Schedules/Milestones (See Contract sections B.1 and C.3)

At a minimum, the contractor shall deliver the items specified below:

VII. Work Location

This work shall be performed primarily at the Goddard Space Flight Center (GSFC), Greenbelt, MD.

VIII. Reporting Requirements

a. Weekly or Bi-weekly Status Report

Each member of the task shall generate a status report every week for the TM. The report shall be posted electronically by close-of-business every Friday to a folder on JPSS eRooms designated by the TM. The report shall include, as a minimum, a summary of the week's highlights/accomplishments/problems encountered, milestones/schedule/deliverables, risks and customer meetings. The report shall also include a forecast of planned out-of-office time for work travel, vacation, etc.

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 support the TM in the preparation of status reviews as needed. 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 does not involve any 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:

a. NPR 7150.2A/B/C NASA Software Engineering Requirements

b. GPR/GPD 7150 Goddard Software Engineering Requirements

c. GSFC STD-1000 Goddard Space Flight Center Rules for the Design, Development, and Operation of Flight Systems (GOLD Rules)

d. NASA-STD-8739.8 NASA Software Assurance Standard

XIII. References

a. JPSS Flight Project Software Acquisition Management Plan (SAMP), 472-00585

b. JPSS-2 Spacecraft Mission Assurance Requirements (MAR), 472-00266 (also applies to JPSS-3/4)

c. JPSS-2 Instrument Mission Assurance Requirements (IMAR), 472-00253 (also applies to JPSS-3/4)