Task 11-9 JPSS Systems 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:

Task Name:

Task No. / Mod:

Task Monitor (TM):

Contract number:

Contract SOW Reference:

4/1/2021 JPSS Systems Engineering 11 / 9 Redacted

NNG17CR69C

Function 4: Operational Phase Services

I. Purpose of Modification

a. To extend the period of performance of the task.

II. 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 primarily from multiple polar-orbiting satellites. The program plays a critical role to NOAA’s mission to understand and predict changes in weather, climate, oceans and coasts, and the space environment, which support the Nation’s economy and protect lives and property. For information regarding the JPSS Program, missions, instruments, and partners, see the JPSS website at https://www.jpss.noaa.gov/.

The JPSS Ground Segment supports the heterogeneous constellation of the before-mentioned polar-orbiting satellites both within and outside the JPSS program through a comprehensive set of services as defined in the Catalog of JPSS Ground Segment Services, 474-01575.

b. Summary of work – The contractor shall provide support as identified in the following sub-tasks. Contractor shall perform Systems Engineering, Systems Integration and Test Planning support to the JPSS Ground Project and execution of specific tasks included, but not limited to the following:

o Develop, maintain and ensure implementation the concept of operations for the JPSS

Ground System o Develop, maintain and ensure implementation of the architecture model and description document for the JPSS Ground System o Develop and maintain the JPSS Ground Project requirements. Establish the baseline in

DOORS, traceability to the JPSS mission level requirements and down to the Ground Segment specifications and contractor lower element requirements

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions o Develop and maintain the DOORS database and perform administrative functions on the system o Develop verification descriptions and provide traceability to requirements o Generate and support the development of JPSS Ground Project interface requirements and interface control documentation o Lead and oversee specific Block development for JPSS Ground System as designated, act as the key representative for each Block o Provide system engineer for each major mission (JPSS-x, S-NPP, GCOM) providing a single point of contact for the program and flight project for management of the specific mission technical baseline, reviews, giver/receivers, interface and mission unique ground system capabilities.

o Support CGS Change order process and documentation o Develop and review flight/ground giver receiver list and documentation o Support working groups and Technical Interchange Meetings (TIMs) with the JPSS

Flight Project and Flight Project vendors and JPSS Ground System data users and external interfaces.

o Provide the JPSS Ground Project risk management and support the JPSS Program risk management process o Develop and maintain required JPSS Ground System KPPs and TPMs as identified in the Concept of Operations (ConOps) o Perform system modeling and analysis to support system development and performance requirements o Review, evaluate, and provide input to JPSS Ground segment/element designs, development and planning activities o Support JPSS Ground Project review preparations o Contribute and/or review JPSS mission level and Ground Project plans, designs, specifications, requirements, and other documents as required.

o Review, evaluate, and provide input to the JPSS mission readiness test planning o Review, evaluate, and provide input to the Level 4 and Level 5 requirements, verification descriptions, OpsCons and the associated designs.

o Perform mission system integration and test planning and execution o Develop system verification plans/status and the development of detailed test plan, procedures, and timeline, periodic system analysis.

o Provide test director(s) for each defined mission test, including the flight / ground JPSS

Compatibility Tests (JCTs) and other mission level test events, including interface and performance tests.

o Support roles of Project System Integration and Test Manager.

o Support mission level Discrepancy Review Board (DRB) and related activities.

o Support mission level reviews and meetings with various agencies (NASA, NOAA), agency partners, agency contractors, and customers.

o Develop, plan, and execute verification of the Ground Segment Security requirements

c. Required skills/knowledge -

a. Candidates are required to have experience in the design, development and operations preparations of NASA ground systems.

b. DOORS personnel are required to have experience with the DOORS requirements database tool.

c. Risk Manager is required to have experience in NASA risk management processes and procedures.

d. NDA agreements with vendors may be required: Expected number of NDAs is based on number of subcontractors

e. Contractor shall comply with NASA’s identity and credential issuance requirements.

Staff may not begin working under this Task Order until a validated NASA identity with favorable background investigation adjudication is complete.

f. The Contractor may be required to travel during the period of the Task Order.

g. Contractor will use computing resources supplied by NASA (e.g., networks, servers).

h. Candidates are required to comply with NASA’s training requirements including but not limited to security, environmental awareness, and safety.

i. Candidates may be required to comply with NOAA’s training requirements including but not limited to security, environmental awareness, and safety.

j. DOORS System Administration skills will be required.

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

i. Knowledge of system engineering and integration tools

ii. Strong ability to lead and interact with distributed team members and different corporate cultures

iii. Earth observing mission system engineering skills

iv. Data format analysis and test data generation

v. Earth Science data processing and archiving

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

IV. Subtask Description

a. Subtask 1: The task will focus on support needed for missions associated with the JPSS Program of Record (POR) to include Suomi National Polar-orbiting Partnership (S-NPP), JPSS-1, JPSS-2, Defense Meteorological Satellite Program (DMSP), European Organization for the Exploitation of Meteorological Satellites (EUMETSAT)’s Metop satellites, Coriolis/WindSat, Global Change Observation Mission (GCOM) - Water (W) 1 (GCOM-W1), NASA Space Communication and Navigation (SCaN), National Science Foundation (NSF). (This consolidates the previous subtasks 1, 2, 3, and 4.)

b. Subtask 5: The task will focus on support needed for missions associated with the JPSS Polar Follow-on (PFO) to include JPSS-3, JPSS-4, and EUMETSAT Polar System (EPS)- Second Generation (SG). Note: this Subtask remains Subtask 5 rather than becoming Subtask 2 to keep the cost in alignment for historical cost purposes.

Work elements are the same for both tasks:

1. Requirements management and documentation in support of the Ground Project. The contractor shall coordinate, generate and manage the following for the JPSS Requirements objectives:

a. Reviewing Level 1 and 2 requirements

b. Generating, managing and/or reviewing Level 3 and Level 3.5 requirements

c. Conducting requirements traceability

d. Documenting specified and lower level derived requirements to demonstrate that performance requirements are met (Level 4 and 5)

e. Reviewing/performing independent design and development requirements analyses, and submitting comments and recommendations

f. Reviewing technical specifications, and submitting comments and recommendations

g. Providing specification of Requirements for Design, non-flight fabrication, and checkout of ground support equipment

h. Reviewing contamination control requirements

i. Reviewing operating plans and procedures for cryogenics, fuels, and other hazardous materials

j. Coordinate working groups to properly communicate requirement changes and management

k. Managing requirements via DOORS

2. Systems engineering in support of the Ground Project. The contractor shall coordinate, generate and manage the following for the Systems Engineering objectives:

a. Defining the architecture of the ground systems

b. Defining systems and conducting trade-off studies/design studies for spacecraft, suborbital craft, instruments, space segments and ground segments

c. Reviewing software development and software system test activities

d. Generating and maintaining and/or reviewing system block diagrams

e. Serving as representative for facility-related activities for JPSS hardware installations at

GreenTec, NSOF, and CBU.

f. Generating, maintaining and/or reviewing Interfaces and Interface Control Documents

(ICDs):

i. Reviewing and analyzing design interfaces

ii. Identifying interface control requirements for engineering and design of components for launch, on orbit servicing, or retrieval of flight hardware

iii. Preparing, reviewing, and analyzing interface documentation for mission systems

iv. Preparing interface control documents and verifying proper implementation for flight and ground subsystems and systems

v. Controlling external interface documentation and requirements

g. Supporting Risk Analysis, Reduction, and Management

i. Identifying high risk elements and developing/executing contingency plans for controlling the high risk elements

ii. Reviewing contractor risk management plans and commenting on alternate approaches

3. Test and verification in support of the Ground Project. The contractor shall coordinate, generate and manage the following for the Test and Verification objectives:

a. Ground and overall JPSS mission verification including satellite, ground, and mission level requirements and interfaces

b. JPSS Compatibility Test (JCTs) support and planning

c. Develop ground systems level tests required to verify readiness of the Ground to meet specific Block or sustainment releases.

d. Generate and/or reviewing Verification Plans

e. Preparing and/or reviewing hardware and software integration plans and procedures, and witnessing execution

f. Preparing and/or reviewing detailed functional and environmental test plans and procedures, and witnessing test execution

g. Documentation and/or review of system qualification requirements

h. Reviewing/refining regression tests to enhance with evidence collection and requirements mapping to ensure leveraging test events

i. Monitoring test and sustainment activities in preparation for mission level testing.

1 Weekly Status reports Description of accomplishments, issues/concerns for the previous week and plans for the following month

Weekly

2 Monthly Technical progress reports Description of accomplishments, issues/concerns for the previous month and plans for the following month

Monthly

3 Financial Report 533 financial report along with the variance report detailing reasons for hour and cost variances

Monthly, submitted with OMES II report

4 Analytical Products Documents a position, an issue, a proposal, trade study, risk analysis, strategic alignment, test analysis, test data characterization, etc., and is the primary ongoing deliverable mechanism for the task

As required, tracked in weekly and monthly reports

5 Requirements Data Requirements updates to DOORS or extracts from DOORS into other MS Office products

As required, tracked in weekly and monthly reports

6 Communications Materials Artifacts as required to support outreach and communications (e.g., presentations, handouts, blog/wiki/web updates, announcements)

As required, tracked in weekly and monthly reports

7 Meeting Minutes Within one week of completion of meeting

8 End of Task status Description of objectives, accomplishments, issues/concerns, and closure path and acceptance.

End of task

9 Test Plans and Procedures Test plans and detailed procedures for each planned test; Regression test updates to include requirement mapping and evidentiary collection

As required, tracked in weekly and monthly reports

10 Engineering management document updates Update to overall test planning documents; schedule status for requirement verification and upcoming planning;

As required, tracked in weekly and monthly reports

11 Trip Report for International Travel Summary of discussion or results from any international travel conducted in support of this task

Within one week of completion of meeting

12 Tools Generation of tools in support of evaluation of the system performance, data analysis, issues/concerns

As required, tracked in weekly and monthly reports

NOTE: Deliverables should include source code, executable and all related documents, if applicable.

VI. Management Approach

a. Staff Allocation, Expertise, and Skill Mix

The contractor shall staff these work items with the appropriate skill mix and staffing level for the work. Staff will be a mix of technical task lead with work breakdown structure (WBS) & scheduling experience, senior and junior system engineers, programmers, testers, software engineers, data analysts, and requirements engineers.

b. Configuration Management

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

c. Facilities

Staff are housed onsite in Building 40 or at the Raytheon facility in Colorado. 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 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 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.

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

VII. ODC (Travel and Procurement)

(See I.1 1852.216-80 TASK ORDERING PROCEDURE d(6), please provide a BOE for all proposed ODCs to determine the reasonableness)

Travel during this period of performance is significantly reduced from previous years due to COVID-19 impacts and increased remote support of events previously requiring travel.

Travel may be proposed for special meetings and other engineering support task activities as directed by the Project.

In the past, travel in support of technical meetings was required in support of Program Management Reviews (PMRs) and TIMs for interfaces, user interfaces, and ground system requirements. Travel was also needed to meet with the ground system development contractor, observatory providers, instrument providers, at contractor facilities, JPSS program facilities, and at the mission partners.

The following events will entirely be supported remotely and not require travel:

o Monthly PMR – this used to alternate between GT4 and Raytheon/CO. Ground Project Management has told us to assume all future PMRs will be at GT4.

o Test witnessing – all SEIT test witnessing will be performed remotely.

o Segment Integration Working Group (this is typically face-to-face (location TBD (likely

Fairmont, WV), 1 trip, 3 persons per trip, approximate 3 work day duration), but will be virtual and supported remotely

• Anticipated number of trips during the task:

o Facility trips to CBU – monthly, 1 person per trip, approximate 5 work day duration o Trip to NASA facility for badging – 1 person, 1 trip, approximate 2 day duration; travel from Denver, CO area to either NASA/GSFC or White Sands Test Facility; included the more expensive trip to Greenbelt, MD in cost estimate o Local travel to NSOF, Suitland, MD as needed.

• Trips to Aurora (or nearby), CO (CGS provider); Boulder, CO (BATC – J1 S/C provider);

CBU facility at Fairmont, WV (other than facility trips); Phoenix, AZ (Northrop Grumman – J2/3/4 S/C provider) are not to be priced at this time, but may be added as the need arises.

• Trips to JPSS Ground Stations (i.e., Fairbanks, Svalbard, WSC, Troll, and McMurdo, Antarctica) are not to be priced at this time, but may be added as the need arises.

• International trips to support JPSS mission partners (e.g., EUMETSAT/Germany, JAXA/Japan) are not to be priced at this time, but may be added as the need arises.

VIII. Work Location

This work shall be performed primarily on-site at the Goddard Space Flight Center, but the contractor may be required to perform some work at the contractor’s facility in Colorado.

IX. Reporting Requirements

a. Weekly status report

The contractor shall provide input to Performance Reports that are generated every week by the integrated badgeless contractor team and given 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 also support the TM in the preparation of status reviews for internal funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports

c. Monthly Deliverable 533M 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.

d. 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 will not be required to handle classified data.

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

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:

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 System Integration and Test Plan

7. Mission Level Interface Control Documents (ICDs)

8. JPSS Level 1 Requirements

9. JPSS Ground System Schedule and Technical Baseline

10. JPSS Multi-Mission System Specification (MMSS)

11. JPSS Ground System Requirements Document

12. JPSS Environmental Satellite Processing Center (ESPC) Requirements Document

(JERD)

13. JPSS Common Ground System Requirements Document

14. JPSS Ground Segment Data Product Specification (GSegDPS)

15. JPSS Ground System Concept of Operations Document

16. Various JPSS Ground System Interface Requirement Documents

17. JPSS Ground System Verification and Validation Strategy Documents

18. JPSS Program System Engineering Management Plan

19. Applicable NPGs and GPGs

XIV. References

None

XV. Proprietary Information This work may require access to other contractor proprietary information. Company-to-company non-disclosures agreements will be required.

Task members directly involved with test activities at secure facilities may require security clearances. The contractor will coordinate and obtain concurrence from the task monitor (TM) for individuals requiring clearances. Additionally, the contractor will be compliant with the NASA security requirements and guidelines.

Interchanges with the Norwegian Space Centre (NSC) and their contractor, Kongsberg Satellite Services (KSAT) will be required. Appropriate agreements and arrangements will be required, and information exchange will be assessed via the GSFC Export Control Office through the JPSS Ground.

This SOW identifies the OMES contractor’s responsibilities to the broader engineering roles and responsibilities to NASA. The JPSS Ground Segment is a distributed system that serves the weather prediction and climate research needs of NASA and NOAA. Interactions with foreign persons, specifically members of the Norwegian Space Centre (NSC) / Kongsberg Satellite Services (KSAT) is limited to planning, scheduling ground station assets for test events, execution of tests and troubleshooting of test issues. The scope of this interaction is limited to ensuring that all the system resources required for end-to-end mission system testing are available and ready to operate in an orchestrated fashion. More to the point, interaction is limited to ensuring that U.S. government property that is operated by KSAT under contract to both NASA and the ground system development contractor is available at specific dates and times as requested in order to support activities performed in CONUS.

Any technical issue arising from these requests falls under the responsibility of a separate and distinct U.S. Government contract.