Task 1-10 JPSS Requirements 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 15, 2021 Task Name: JPSS Requirements Support Task No. / Mod: 1/10 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference: Function 3 - Implementation Phase Services/Sub Section B Mission

Systems Engineering/ Item 3 Requirements Analysis, Identification, and Managements

MOD SUMMARY

This mod extends the POP date and keeps all other requirements as-is

I. Scope

a. Background – The JPSS Flight Project, Code 472, is responsible for the management of the Suomi National Polar Project (S-NPP) technical support, and post launch support. JPSS Flight Project management responsibilities include the design, development, manufacturing, integration and test, verification and documentation of the JPSS flight systems. The Project monitors the launch vehicle acquisition by KSC and provides payload launch integration support. KSC provides software, launch site facilities, and launch site support services required to successfully integrate the observatory to the LV, verify their integration, and conduct pre-launch and launch operations.

b. Summary of work – Provide Requirements Management and Verification Systems Engineering Support:

1. Support in the planning, organizing, scheduling, managing and directing of efforts associated establishing, maintaining, and verifying the requirements baseline for the JPSS Flight Project -particularly in areas of DOORs Relational Database Operations and Development.

2. Participate in program status meetings, telecons, peer reviews, and major project reviews for spacecraft, instruments, launch vehicle, mission operations system, and science data system.

3. Support with requirements definition, flow-down, validation and verification;

4. Prepare/Review project documentation and submit comments and recommendations

5. Prepare and present technical information for technical meetings / reviews / briefings;

6. Analyze configuration, design, and procedural changes submitted to the Project change control boards;

c. Required skills/knowledge - The contractor should have experience with the Dynamic Object Oriented Requirements System (DOORS) software tool.

II. Period of Performance

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

b. Configuration Management Systems and documents will be covered under the JPSS Program Configuration Management

Procedure (470-00012).

c. Facilities

VI. See Work Location and Security Requirements below.

a. 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.

b. 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 could be:

1. Percent completion of subtask

2. Planned versus actual

c. 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.

Execution of this task may require access to other contractor proprietary information. Company-to-company non-disclosures agreements (NDAs) may be required.

d. 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

VII. ODC (Travel and Procurement)

Periodic Travel is required in support of activity approximately 1 trip per Quarter. Travel is to be Pre-Approved by Project. Travel Locations shall include, but not be limited to, following locations: 1. Quarterly trips to Satellite Provider (Phoenix, AZ) (3 days) 2. Quarterly trips to Instrument Provider (assume Asuza, CA for costing) (3 days). Trip Reports in Contractor Format required within seven (7) days of completion of trip.

VIII. Work Location This work shall be performed primarily on-site at the Goddard Space Flight Center and/or via telework from employee location, but the contractor may be required to perform some work at the contractor’s facility.

IX. Reporting Requirements

a. Monthly status report Each member of the task shall generate a status report monthly for the TM. The report shall be posted electronically by close-of-business at the end of the month to a folder on JPSS eRooms designated by the TM. The report shall include, as a minimum, a summary of the month’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.

X. 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.

There will not be any handling of classified data.

XI. Safety

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.

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

1. NPR 7120.5E, “NASA Space Flight Program and Project Management Requirements”

2. NASA SP-2007-6105 Rev1, NASA Systems Engineering Handbook December 2007

XIV. References