Att A_Amend 003_changes identified__L1-STISSOW-0001_Ver0.2.pdf

SWFO STIS SOW 422-L1-STISSOW-0001

ii Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

SWFO – L1 STIS Statement of Work (SOW)

Signature/Approval Page

Prepared by:

Evan Goldstein Date

SWFO-L1 STIS Instrument Engineer

NASA/GSFC, Code 422

Reviewed by:

Gustave Comeyne Ronald J. Hooker Date

SWFO-L1 Deputy Project Instrument Systems Manager

Approved by:

Gene Martin Date

SWFO-L1 Project Manager iii Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

CM FOREWORD

This document is a SWFO-L1 (SWFO) Project Configuration Management (CM)-controlled document. Changes to this document require prior approval of the applicable Configuration

Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the

SWFO CM Office (CMO), along with supportive material justifying the proposed change.

Changes to this document will be made by complete revision.

Questions or comments concerning this document should be addressed to:

NASA/Goddard Space Flight Center

SWFO-L1 Project Office, Code 422

Attention: Configuration Management Office

Greenbelt, Maryland 20771 iv Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

Change History Log

REV

LEVEL

DESCRIPTION OF CHANGE APPROVED

BY

DATE

APPROVED

0.1 Initial Release GM 10/7/19

0.2

Updates as highlighted throughout document:

Blue are additions and Red are Deletions

Summary of Changes:

Section 1.0 Deletion of “High Fidelity” requirement for EDU and buildup of Assemblies.

Section 4.4 Deletion of Configuration Management requirement to place items on government portal and associated notifications. Knowledge capture program.

Section 4.5 Deletion of IBR requirement to review

Contractor financial and Schedule reporting system.

Removed listing of observatory reviews. Deletion of requirement for Test Data reviews of subassemblies and subcontracted items. Deletion of Notification requirement for TIMs at sub-contractor facilities. Removed listing of software reviews.

Section 5.5 Change to government led magnetic control program from contractor led.

Section 6.2 Deletion of requirement for providing

FPGA Data Design Package. Deletion of requirements related to Actel FPGA’s.

Section 6.3 Removed TBD from EIDP.

Section 6.5 Removed listing of spacecraft contractor led training activities.

GM 12/3/19

v Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

Table of Contents

1 Program Scope and Management

2 Documents

2.1 Applicable Documents

2.2 Reference Documents

3 Requirements Precedence

3.1 Terms and Definitions

4 Work Performed by the Contractor

4.1 Program Management Office

4.2 Resource Management

4.3 Visitor Badging

4.4 Configuration and Information Management

4.4.1 Documentation

4.5 Program Review Requirements

4.5.1 Kick-Off Meeting

4.5.2 Integrated Baseline Review (IBR)

4.5.3 Peer Reviews

4.5.4 Instrument Design Reviews

4.5.5 Observatory Level Reviews

4.5.6 Project Management Status Reviews

4.5.7 Test Data Reviews

4.5.8 Technical Meetings

4.5.9 Subcontract Subsystem and Instrument Reviews

4.6 Schedule Management

4.7 Risk Management

5 Systems Engineering

5.1 Systems Management and Engineering

5.2 Observatory Interface and Accommodation

5.3 System Analysis and Allocations

5.4 Contamination Control and Analysis

5.5 Magnetic Control Program

5.6 Special Engineering Analysis

6 Flight Model (FM)

6.1 Design and Analysis

6.1.1 Instrument Design

6.1.2 Flight and Ground Test Software Development and Maintenance

6.1.3 Ground Processing Algorithms (GPA)

6.2 Parts Procurement, Fabrication and Subassembly Testing

6.2.1 Field Programmable Gate Array (FPGA) Design and Development

6.3 Integration and Test

6.3.1 Integration

6.3.2 Performance Verification and Design Qualification

6.3.3 Calibration

6.4 Logistics

vi Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

6.4.1 Transportation and Handling

6.4.2 Storage

6.5 Post Delivery Support

6.5.1 Observatory Integration and Test Support

6.5.2 Launch Operations Support

6.5.3 Mission Operations Support

6.5.4 End-to-End (ETE) Test Support

6.5.5 Post-Launch Test (PLT) Support

7 Ground Support Equipment (GSE)

7.1 Electrical Ground Support Equipment

7.1.1 Electrical System Test Equipment (ESTE)

7.1.2 STIS Emulator (STISE)

7.1.3 Connectors

7.1.4 Other EGSE

7.2 Mechanical Ground Support Equipment

7.3 Ground Processing Development System (GPDS)

8 Mission Assurance

9 Acronym List

10 Definitions

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

1 Program Scope and Management

The SWFO-L1 Mission is a high priority joint undertaking by the National Aeronautics and

Space Administration (NASA) and the Department of the Commerce, National Oceanic and

Atmospheric Administration (NOAA). The SWFO-L1 Observatory will provide NOAA with the continuity of solar wind data and coronal mass ejection (CME) imagery, which is the National

Weather Service’s highest priority for space weather observations. SWFO – L1 is planned to launch as a rideshare on the Interstellar Mapping and Acceleration Probe (IMAP) mission.

This Statement of Work (SOW) defines those tasks necessary to design, analyze, develop, fabricate, integrate, test, calibrate, evaluate and support launch and on-orbit check-out of the

Supra Thermal Ion Sensor (STIS) instrument, supply and maintain the instrument Ground

Support Equipment (GSE), and support the Mission Operations Center (MOC) through mission hand over to NOAA.

The period of contract coverage is from contract award through the life of the mission including successfully launched, post launch evaluation, calibration, data validation, and on-orbit anomaly investigations.

The STIS is part of the SWFO-L1 satellite which has a risk classification of C per NPR 8705.4, Risk Classification for NASA Payloads.

The Contractor shall provide the personnel, materials, facilities and other resources to design, develop, deliver and support under the basic contract:

a. One STIS Flight Model (FM)

b. One high fidelity Engineering Development Unit (EDU)

c. Spares and built up and tested sub-assemblies for one spare unit (TBR)

d. Two sets of the Electrical System Test Equipment (ESTE)

e. Three STIS Emulators (STISEs)

f. Two Flight Software Development Environment (FSDE)

g. One Ground Processing Development System (GPDS) (TBR)

h. All additional STIS Mechanical and Electrical Ground Support Equipment (MGSE and

EGSE) called out elsewhere in this document

i. All remaining items and documents specified in contract documents

2 Documents

2.1 Applicable Documents

The documents listed in this section apply directly to the performance of the STIS contract.

These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract.

STIS Requirements Specification, 422-L1-STISSPEC-0002

Instrument Mission Assurance Requirements Document (IMAR), 422-L1-IMAR-0004

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

STIS Contract Deliverables Requirements List (CDRL), 422-L1-STISCDRL-0003

NASA-STD-8719.13C NASA Software Safety Standard

NPD 8730.4 NASA Software Independent Verification and Validation Policy

NPR 8705.4, Risk Classification for NASA Payloads

2.2 Reference Documents

GOLD Rules, GSFC-STD-1000 (Rev G)

3 Requirements Precedence

In the event of a conflict in requirements between this SOW and other documentation, the order of precedence shall be: SOW, Contract Deliverables Requirements List (CDRL), STIS

Requirements Specification, Instrument Mission Assurance Requirements (IMAR), Spacecraft to

STIS Interface Control Documents (TBD), and any other Applicable Documents. The Contractor shall notify the Contracting Officer of any inconsistency in this SOW, including all attachments and applicable documents. Upon notification of an inconsistency, the Contracting Officer will clarify which requirement takes precedence, and may modify the contract as deemed appropriate.

3.1 Terms and Definitions

For the purposes of the SWFO-L1 STIS contract attachments, the following terms and definitions apply unless otherwise stated in a contract Attachment.

A requirement is identified by “shall”, a good practice by “should”, permission by “may” or

“can”, expected outcome or action by “will” and descriptive material by “is” or “are” (or other verb form of “to be”).

The term “TBS” (To Be Supplied) means that the Government will clarify or supply the missing information during the course of the contract. “TBR” (To Be Reviewed) means that the stated information will be reviewed for appropriateness by the Contractor and the Government and the value may be changed prior to final definition by the Government during the course of the contract. Until the value is changed or the “TBR” removed, the Contractor shall comply with the requirement as if the "TBR" notation did not exist. “TBD” (To Be Determined) indicates further research or analysis is needed to determine the information, during the course of the contract, with the final determination to be made by the Government. “TBP” (To Be Proposed) means the

Contractor proposes the information with the Offer submission for Government review and approval. All changes to resolve these “TBX” items will be done through a formal process of configuration change review, approval, and contract modification.

The terms “observatory” and “Observatory” refer to the spacecraft (or Spacecraft) bus fully or partially integrated with one or more flight instruments and is equivalent to the term

“observatory” used in the Rapid III Contract.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The term “Government” represents the appropriate NASA and/or NOAA SWFO-L1 management office or, where “the Government” is indicated as providing a function for or interface to the Spacecraft Contractor, the function or interface may be provided by

Government or Government SWFO-L1 or support service contractors.

The terms “SWFO-L1 Project Office”, “SWFO-L1 Project”, and “Project” refers to the

Government SWFO-L1 Project Office.

The terms “instrument team”, “instrument provider”, “instrument developer”, “instrument supplier”, and “instrument vendor” refer to the various instrument contractors and/or to

Government civil servant and Government support contractors interfacing with and or providing the instrument or data for the various instruments (to be revised based on instrument vendor selection).

4 Work Performed by the Contractor

4.1 Program Management Office

The Contractor shall establish a Program Management Office (PMO) responsible for the leadership and overall direction of all phases of the work specified in this SOW.

The Contractor shall establish effective communication with the Government Project Office through the Contracting Officer's Representative (COR) that includes, but is not limited to, e-mail and telephone contact as necessary, weekly telecons with the Government STIS team, and one-on-one contact between NASA and Contractor discipline engineers, to be coordinated by the

COR.

The Contractor shall prepare, lead and provide minutes for weekly teleconferences with the

Government to discuss status, risks, issues, schedule and other business-related activities.

Once instrument integration and test (I&T) begins, the Contractor shall include the Government team in the Contractor’s regularly scheduled I&T meetings.

The Contractor shall establish a Subcontract Management and Control System to provide technical direction and effective sub-contract management utilizing schedule milestone controls.

The Contractor shall develop and maintain a Master Action Item Data Base (MAID), or spreadsheet, listing all Request for Actions (RFA) or Action Items from formal reviews, Government status reviews, internal technical reviews, peer reviews, all other reviews required by the contract, technical meetings, telecons, etc., listing author and origin (PDR, telecon, etc.) of the RFA, person responsible for closure, wording of the RFA, response, persons(s) authorizing final closure, due date, date closed, and a column for Government concurrence and comment.

The Contractor shall not delete closed action items from the MAID.

The Contractor shall retain all documents and test data for the life of the contract.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

4.2 Resource Management

The Contractor shall establish, implement and maintain a comprehensive Resources

Management System (RMS) for planning, authorizing, and controlling the total resource effort for each Work Breakdown Structure (WBS) element, by instrument, and for providing timely and adequate visibility into manpower, materials, cost, schedule, travel, and subcontract performance.

The RMS shall be consistent with the contract WBS and provide timely and traceable incorporation of contract changes, and document the effect on the resource management baseline.

The contractor shall maintain and provide the WBS to the government once it is baselined and after any significant changes due to project changes or contract modifications.

The Contractor shall use Microsoft Project (latest version) as the scheduling tool for the generation and reporting of project schedules.

The Contractor shall define and implement a parts program for all flight and GSE parts that minimizes the risk of a schedule delay, in the event of a part or component failure, inadvertent damage, contamination, or by other plausible events or conditions and based on the Contractor’s historical experience, current practices, and lessons learned from similar Class C missions.

The Contractor shall provide private office space with a locking door, furniture, copier(s), facsimile machine(s), phones and high-speed internet access in the vicinity of the PMO for one

Government resident and one visiting representative. (TBD)

The Contractor shall provide property management of NASA Government Furnished Equipment

(GFE) and GSE.

The Contractor shall deliver a Safety and Health Report.

Any major Sub-contractor that may be providing one or more of the STIS Subassemblies shall provide private office space, furniture, copier(s), facsimile machine(s), phones and high-speed internet access in the vicinity of the project office for one government representative. (TBD)

4.3 Visitor Badging

The Contractor shall accommodate facility access and badging for SWFO-L1 Project representatives throughout the life of the contract. This shall include short term visitor badging for all Contractor-hosted meetings, Technical Interchange Meetings (TIMs), Working Groups

(WGs), and reviews, as well as long-term, unescorted badging for up to 6 Project representatives in order to accommodate long-duration visits (e.g. during integration and test [I&T]) and resident personnel. If the Contractor requires training for entry into any facilities, the Contractor shall provide the necessary training to Project representatives. This training shall be provided in a timely manner.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

4.4 Configuration and Information Management

The Contractor shall oversee and manage the generation, configuration control and distribution of all documents required by the contract.

The Contractor shall establish, implement, and maintain a government approved Configuration

Management System that provides Configuration Management control of configured items including all flight hardware and software, all GSE hardware and software, and all documentation developed under this contract, including drawings, procedures, plans, CDRLs, and program review materials.

The Contractor shall provide all documents called out in the CDRL plus all updates and revisions in accordance with the CDRL. The Contractor shall produce, control and maintain contract documentation in accordance with the CDRL. The Government will establish and maintain a secure website, called the SWFO-L1 Portal. The Government will maintain a folder on the portal for STIS only, accessible by the Contractor and selected government personnel, for document delivery and the exchange of information only.

The Contractor shall place on the SWFO L1 Portal, as generated or changed, all technical and programmatic documentation generated on the contract that includes but is not limited to, CDRLs, MAID, schedules, meeting minutes, systems engineering reports, design memos, internal technical memoranda, schematics, design specifications and test procedures. The

Government will post on the website Government deliverables and technical documentation generated in support of the STIS mission.

The Contractor shall notify the selected Government personnel by e mail that a document has been posted on the website. The Government will provide similar notification to the Contractor.

The Contractor shall develop, implement and maintain a document and drawing tree.

The Contractor shall develop, implement and maintain a Software Configuration Management

System that provides baseline management and control of software requirements, design, source code, data and documentation.

The Contractor shall employ a source code version control tool to check in/check out current or previous versions of a source file.

The Contractor shall establish a Configuration Control Board(s) to review and approve changes to the flight design documentation models, software, GSE and all controlled documents.

The Contractor shall submit Class I changes to the Government for approval before implementation of the change. (Class I changes affect an item’s fit, form or function.)

The Contractor shall submit Class II changes to the Government for concurrence with the classification. (Class II changes are changes to correct documentation or changes to hardware not otherwise defined as a Class I change.)

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

If GSFC determines that a Class II classification is incorrect the Contractor shall resubmit the change as a Class I change.

The Contractor shall implement a knowledge capture program. so that the knowledge base developed during design and development of the Engineering Model (EM) and Flight Models

(FMs) will be available to the engineering staff that will be called upon to maintain the program through the life of the mission. (TBD)

4.4.1 Documentation

The Contractor shall develop, produce, deliver, and maintain all documentation required by and in accordance with the SWFO-L1 STIS Contract Deliverables Requirements List (CDRL)

The Contractor shall comply with applicable export control protocols: Export Administration

Regulation (EAR) or International Traffic in Arms Regulation (ITAR), as determined by the

NASA GSFC Export Control Office. The Contractor will appropriately mark information provided to the SWFO-L1 Project that is subject to export control restrictions and will leave information unmarked that is not.

All efforts, including the performance of tests and analyses not otherwise explicitly stated in other parts of the SOW, but determined jointly by the Contractor and the Government to be mission critical, shall be performed and documented by the Contractor. All documentation, data, and analyses generated for or applicable to the contract effort, whether formal or informal, deliverable or non-deliverable shall be made available to the Government and Government support Contractor’s upon request. This information shall be provided electronically through a

Contractor provided web portal that provides Government document download capability.

4.5 Program Review Requirements

The Contractor shall provide the technical and administrative support for all program reviews and meetings. including, but not limited to, Instrument Design Reviews, Project Status Reviews, Technical Meetings, Data Reviews, Design Modification/Upgrade Reviews, and Subcontract

Reviews.

The Contractor shall provide technical support to observatory system-level reviews, observatory integration and test reviews and mission operations reviews.

Unless otherwise stipulated, all reviews and meetings will be held at the Contractor's facility.

4.5.1 Kick-Off Meeting

Approximately one month after award the Contractor shall prepare and conduct a Kick-Off

Meeting covering a line-by-line review of the contract schedule and clauses, SOW, STIS

Requirements Specification, IMAR, and CDRLs.

The Contractor shall provide their interpretation of each line item (“Shall.”)

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The Contractor shall plan for a two-day (TBR) review.

If the review is not complete in two days, the Contractor shall continue to conduct and support the review until the Government deems the review complete.

4.5.2 Integrated Baseline Review (IBR)

Approximately 3 months after contract award, the Contractor shall conduct an Integrated

Baseline Review (IBR)

The IBR shall include a review of the Contractor's financial reporting system. (TBD)

The Contractor shall review, in detail, the financial reporting system and schedule baseline established for the STIS program. (TBD)

4.5.3 Peer Reviews

The Contractor shall work with the Government to implement a program of periodic tabletop engineering and risk mitigation reviews (peer reviews) throughout the life cycle to identify and resolve concerns as they arise, and prior to formal, system level reviews.

Peer review teams shall be comprised of technical experts from the Contractor and the

Government with significant practical experience relevant to the technology and requirements to be reviewed.

The Contractor shall provide three days prior notification so that government representatives can prepare and be present.

4.5.4 Instrument Design Reviews

The Contractor shall prepare and conduct Instrument Design Reviews for the Independent

Integrated Review Team that will be chaired by the Government. The reviews will cover all aspects of flight and ground hardware, software and operations for which the Contractor has responsibility.

The Contractor shall conduct a dry-run chart flip-through via a telecon and/or WebEx for each design review, with the government STIS team, 2 weeks (TBR) prior to the review.

After each formal review, the Contractor shall document all RFA's with planned closure date in the MAID within 1 week of receipt.

Each dry-run and design review, (PDR, CDR, etc.) is not considered complete until approved by the Government. If the Government determines that a delta review is necessary, the Contractor shall conduct such review at a time to be mutually agreed-upon with the Government.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

4.5.4.1 System Definition Review (SDR) /Systems Requirements Review (SRR)

The Contractor shall prepare and conduct an SDR/SRR after all requirements have been allocated to the subsystem level.

The Contractor shall plan for a two-day (TBR) review, not including resolution of RFAs.

4.5.4.2 Preliminary Design Review (PDR)

The Contractor shall prepare and conduct a PDR at the conclusion of the preliminary design efforts and after testing the breadboard or brass board models of critical subassemblies/assemblies.

The Contractor shall plan for a two-day (TBR) review, not including resolution of RFAs.

4.5.4.3 Critical Design Review (CDR)

The Contractor shall prepare and conduct a CDR prior to the start of manufacture of the FM hardware unless the Contractor requests and the Government concurs with an earlier start.

The Contractor shall plan for a two-day (TBR) review, not including resolution of RFAs.

4.5.4.4 Pre-Environmental Review (PER)

The Contractor shall prepare and conduct a PER prior to the start of environmental testing of the

FM to establish the readiness of the system and to evaluate the environmental test plans and procedures.

The Contractor shall plan for a two-day (TBR) review, not including resolution of RFAs.

4.5.4.5 Pre-Storage/Pre-Shipment Review

The Contractor shall prepare and conduct a pre-storage review prior to placement of the FM into storage at the Contractor's facilities.

The Contractor shall plan for a two-day (TBR) pre-storage review, not including resolution of

RFAs.

The Contractor shall prepare and conduct a pre-ship review prior to the shipment of instrument.

The Contractor shall plan for a two-day (TBR) pre-ship review, not including resolution of

RFAs.

4.5.5 Observatory Level Reviews

The Contractor shall provide technical support to all Observatory level and Mission reviews.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The Contractor shall support the Observatory level reviews by presentations and/or documentation; for example, an instrument overview or design summary, test and data evaluation summaries, etc.

The Contractor shall attend all Observatory Reviews (TBR) including but not necessarily limited to:

a) Observatory System Definition Review/Systems Requirements Review (3 days)

b) Observatory Concept Review (3 days)

c) Observatory Preliminary Design Review (3 days)

d) Observatory Critical Design Review (3 days)

e) Mission Operations Review (1 day)

f) Observatory Pre environmental Review (1 day)

g) Flight Operations Review (1 day)

h) Observatory Pre storage/Pre ship Review (2 days)

i) Flight Readiness Review (1 day)

j) Launch Readiness Review (1 day)

k) Post Launch Test Readiness Review (1 day)

4.5.6 Project Management Status Reviews

The Contractor shall prepare and hold once every two months Project Management Status

Reviews (PMSR). for the purpose of reviewing the status of the instrument and GSE development, and the overall status of the project.

The status reviews shall be held at the Contractor's facility through successful completion of the

CDR, then alternate between a government designated facility and the Contractor's facility.

Specific agenda items may be required by the Government.

4.5.7 Test Data Reviews

The Contractor shall prepare and conduct table-top test data reviews with government personnel on the overall instrument status and performance.

Test data reviews shall include instrument sub-assemblies and subcontracted subassemblies as well as instrument level test data.

The Contractor shall conduct data reviews prior to the shipment of deliverable GSE.

The Contractor shall prepare and conduct reviews of the interim data following any instrument or system level performance verification or calibration test prior to the breakdown of any test setup to ensure collection of good data, and prior to the Pre Storage and Pre-Shipment Reviews to determine readiness.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

4.5.8 Technical Meetings

The Contractor shall provide technical meetings and reviews as deemed necessary by the

Government for the purpose of discussing and/or resolving problems or items of interest.

The Contractor shall conduct Technical Interchange Meetings with subcontractors. for instruments, critical assemblies and subassemblies and provide the Government 7 days advanced notice so that government representatives can attend.

4.5.9 Subcontract Subsystem and Instrument Reviews

The Contractor shall plan a series of subsystem reviews and document that plan as part of the

Program Management Plan.

The Contractor shall conduct PDR and CDR reviews of all major sub-systems whether these subsystems are provided by the Contractor or by a subcontractor.

Whether internal or external, sub-system reviews shall be chaired by the Contractor and conducted by personnel not directly responsible for design or procurement of the hardware under review. The Government reserves the right to attend these reviews and requires 10 business days of advance notification.

The Contractor shall document the minutes and action items that result from these reviews and make them available on the government website.

The Contractor shall conduct internal software reviews. as follows: (TBR)

a) Software Requirements Review

b) Software Preliminary Design Review

c) Software Critical Design Review

d) Software Test Readiness Review

e) Software Acceptance Review

The Contractor shall conduct tabletop code walkthroughs (TBR); the Government reserves the right to attend and requires three business days advance notice.

4.6 Schedule Management

The Contractor shall establish, implement, and maintain an STIS Instrument Schedule

(STISIS). The Contractor shall present schedule status at the Program Management Status

Reviews.

The Contractor shall obtain Government approval for STISIS changes that impact Deliverable

Items or GFE delivery dates as defined in contract.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

4.7 Risk Management

The Contractor shall implement and maintain a Risk Management Program addressing all programmatic, performance and reliability risks.

The Contractor shall evaluate, classify, and prioritize all identified performance, reliability and quality risks and assess their potential impact on cost and schedule.

The Contractor shall develop and implement risk management strategies, actions (mitigate, watch or research), and assign tasks and appropriate resources to manage and control the risks.

The Contractor shall track all risks being mitigated on an ongoing basis; capture risk attributes and mitigation information by collecting data; establish performance metrics; examine trends, deviations and anomalies; and writing risk mitigation plans as necessary.

5 Systems Engineering

The Contractor shall establish and maintain a Systems Engineering Program for directing, specifying and overseeing the design and technical development of the STIS instrument, GSE, and ground algorithms.

The STIS System Specification shall include derived requirements from the STIS Requirements

Specification, the SWFO-L1 IMAR, and the STIS SOW.

The Contractor shall use a requirements traceability tool to demonstrate that the STIS design meets all requirements.

5.1 Systems Management and Engineering

The Contractor shall perform all system studies, trades, risk assessments, and fault management strategy necessary to develop an instrument system design that meets the system performance specifications.

The Contractor shall flow-down the STIS performance requirements into engineering functional requirements, detailed equipment and end item design requirements.

The Contractor shall ensure that all subsystems, both individually and in combination, meet the intended design and performance specifications and that the design specifications are sufficient to meet the mission life requirements.

The Contractor shall establish and maintain a System Performance and Environmental

Verification Program that demonstrates that the FM meets all mandated and derived performance requirements, and that the GSE meets all design and interface requirements and is safe to use with the flight hardware.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

5.2 Observatory Interface and Accommodation

The Contractor shall coordinate with the observatory implementation contractor and support technical interchange meetings to define the instrument accommodations and interfaces between instrument and observatory as well as instrument GSE to observatory GSE interfaces, and instrument GSE to NOAA GSE interfaces.

The Contractor shall assist in the development of the STIS to Spacecraft (S/C) Interface Control

Documents (ICDs) specified in the STIS specification.

The Contractor shall support the observatory implementation contractor in design and test of all instrument to observatory interfaces: mechanical, including the location of the STIS instruments on the observatory, electrical, and thermal.

The Contractor shall support at their facility pre-delivery data and electrical power interface testing in coordination with the spacecraft vendor using a spacecraft vendor provided interface simulator.

5.3 System Analysis and Allocations

The Contractor shall conduct complete analyses of the technical requirements that fully establish and define budget allocations for all required performance and design parameters, including but not limited to, mass, power and volume allocations, alignment, magnetic cleanliness, contamination control, thermal, radiation, on-board processing resources, and data timeliness.

The Contractor shall maintain and control budgets (i.e. allocations and margins) for all instrument resources.

The Contractor shall conduct the analyses required to confirm the integrity of the instrument design, and to ensure that instrument performance will be compliant with specifications over the operational design life.

The Contractor shall conduct analyses and simulations required to assure the combined subsystems function properly as an integrated unit.

The Contractor shall conduct data analysis and trending and maintain a trend database during instrument level testing, observatory level testing, post-launch operations, and mission operations in order to ensure stability of instrument performance.

The Contractor shall conduct end-to-end analyses of the instruments to demonstrate the designs will meet all performance requirements.

The Contractor shall develop and maintain over the duration of the contract, a computer simulation(s) and models for these end-to-end STIS system analyses.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The Contractor shall use a requirements management tool that interfaces with Dynamic Object-

Oriented Requirements Management System Next Generation (DOORS- NG) requirements management tool for the import/export of requirements and traceability linkages.

5.4 Contamination Control and Analysis

The Contractor shall establish a Contamination Control Program and provide the resources necessary to assure that appropriate contamination control is exercised through all phases of instrument manufacture, build-up/assembly, integration and test, and observatory integration and test, launch site processing, and on-orbit operation. This includes assuring that STIS will not produce contamination that degrades companion instruments and spacecraft subsystem performance

Supplemental CCP documents shall be developed for cleanroom operations, contamination protocols, cleaning procedures, monitoring plans, vacuum bake out plans, I&T plans, launch site processing, and any contamination-related plans for the on-orbit phase.

The Contractor shall establish and document contamination allowances and budgets for performance degradation of sensitive surfaces, components, and thermal contamination-sensitive hardware such that, even when degraded by contamination within the stated allowance, the hardware will meet its end-of-life mission objectives.

The Contractor shall provide a mass transport analysis and a particle generation and redistribution analysis for the instrument.

The Contractor shall perform all cleaning that is required to maintain contamination at defined levels.

The Contractor shall report the status of all contamination control activities at Instrument Design

Reviews, technical meetings and PMSRs.

5.5 Magnetic Control Program

The Contractor shall implement a magnetic control and verification program to track, manage/report and test (TBR) to ensure that the instrument-generated magnetic fields do not exceed the field limits during instrument operation.

The Contractor shall participate in the Government observatory contractor lead magnetics control program.

5.6 Special Engineering Analysis

The Contractor shall conduct special engineering tasks and/or analyses relating to the development, implementation, and operation of the STIS instruments, and ground systems as required and authorized by the appropriate contract clauses.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

6 Flight Model (FM)

The Contractor shall develop a STIS Proto-flight Model (PFM), designated as FM to qualify the designs and procedures and to fly on the SWFO-L1.

The effort shall include fabrication, assembly, test, calibration, maintenance, storage (including calibration verification after a TBD timeframe), delivery and post-delivery support through the handover of the SWFO – L1 mission plus one (1) year.

The FM shall be functionally tested and environmentally tested to proto-flight qualification levels and durations as defined in the STIS Requirements Specification.

6.1 Design and Analysis

6.1.1 Instrument Design

The Contractor shall design the instrument to meet the performance and interface requirements.

of all contract documents.

To support and gain confidence in the design of critical and high-risk systems the Contractor shall perform subassembly/assembly level design and testing to verify expected performance prior to the start of FM instrument fabrication.

The Contractor shall develop and maintain Assembly and Integration Procedures and Drawings.

The Contractor shall develop an high fidelity Engineering Development Unit (EDU) to reduce, mitigate or retire critical subassembly or assembly risk.

The Contractor shall conduct life tests of all mechanisms and other critical assemblies as specified in the STIS Requirements Specification.

The Contractor shall verify the expected performance of any design change before proceeding with fabrication of the changed article.

The Contractor shall ensure that all STIS technologies achieve a Test Readiness Level (TRL) 6 by PDR.

The Contractor shall provide a list of any STIS technologies that are below TRL 6 at the time of award.

6.1.2 Flight and Ground Test Software Development and Maintenance

The Contractor shall update and maintain all flight software, ground test software, processes, procedures and software tools required for support of the FM integration, test and verification program, and on-orbit operations in accordance with the Software Maintenance Plan.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The Contractor shall establish and maintain a Software Management Program to plan and document software development processes and procedures, software tools, reviews, resources, schedules and deliverables.

The contractor shall document and maintain under configuration control all software requirements in the STIS Requirements Specification.

The contractor shall identify the person responsible for directing and managing the software assurance program and interfacing with government assurance personnel.

The contractor shall identify safety critical software per Appendix A of NASA-STD-8719.13

Software Safety Standard, or equivalent, with NASA/GSFC COR approval.

The Contractor shall provide technical support for NASA Independent Verification and

Validation (IV&V) efforts in accordance with the IMAR and NASA Software Independent

Verification and Validation Policy, NPD 8730.4 (TBR).

The Contractor shall design, develop, test and implement flight software and GSE ground test software for the FM.

The Contractor shall specify, design, review, develop, configuration control, and test the software component of firmware, consisting of computer programs and data loaded into a class of memory not dynamically modifiable by the computer during processing (e.g., Programmable

Read Only Memories, Programmable Logic Arrays, Digital Signal Processors, Field

Programmable Gate Arrays, etc.), in the same rigorous manner as the flight software (TBR).

The Contractor shall provide and maintain one Flight Software Development Environment

(FSDE), including hardware, software, procedures and associated documentation, to be used for the life cycle management, development and verification of the flight software at the Contractor's facility.

The Contractor shall provide and maintain one FSDE, including hardware, software, procedures and associated documentation for delivery to the Government for development, test and verification of software patches that may be required throughout the operational phase of the

STIS mission.

The Contractor shall provide and maintain a GSE Ground Test Software Development System to be used for the life cycle management of the ground test software at the Contractor's facility.

(TBR)

The Contractor shall classify each Computer Software Configuration Item (CSCI) in accordance with the software classifications definitions for Class A, B, C, D, E, F, G and H in Appendix B of NPR 7150.2B.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The Contractor shall maintain a Government approved tailoring compliance matrix against NPR

7150.2B requirements, including those accomplished by subcontracts, for each software classification/CSCI.

The Contractor shall implement the safety requirements of NASA-STD-8719.13C when a system or subsystem is determined to have safety critical software.

The Contractor shall provide Government insight into software design, development and test activities including monitoring integration and verification adequacy, trade study data, auditing the software design and development process, and participation in all software peer reviews and technical interchange meetings.

The contractor shall perform an analysis of unnecessary and/or unreachable code, as defined per

GSFC-STD-1000 (Rev G) Table 3.02-1, on the intended flight load for launch. The analysis shall identify all instances (areas) of unnecessary/unreachable code, the general functionality associated with the code, the reason each is intended to be left within the flight load, and the justification (e.g., mitigating action) that explains why the included code does not provide a risk to the mission.

The contractor shall ensure that SW functional/requirements and comprehensive performance verification/validation testing is performed by qualified testers that are independent of the SW designers and developers.

6.1.3 Ground Processing Algorithms (GPA)

The Contractor shall provide Ground Processing Algorithms (GPAs) to produce data to be compliant with the requirements specified in the STIS Requirements Specification. The algorithms will be documented in a Ground Processing Algorithms Document (GPAD).

The Contractor shall develop, maintain and update GPAs for the MOC, National Centers for

Environmental Information (NCEI), and NOAA’s Space Weather Prediction Center (SWPC) for processing from Level 0 to Level 1a and Level 1b. It is recommended that the source code should be in a language on NOAA’s operational baseline (e.g. Python is preferred by NCEI).

The Contractor shall conduct a comprehensive test and validation program of the GPAs and demonstrate that the algorithms can produce data that meets the requirements of the STIS

Requirements Specification, all within the required data latency period.

The Contractor shall provide a copy of the GPA source code "as-run", and as-updated, for validation.

The Contractor shall participate in Technical Interchange Meetings with SWPC to define algorithm format, testing and other required support.

The Contractor shall support the implementation and testing of the GPA by SWPC.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The Contractor shall identify all discrepancies in the GPA acceptance test results.

The Contractor shall certify the implementation of the GPA once the SWPC has successfully demonstrated acceptable performance.

6.2 Parts Procurement, Fabrication and Subassembly Testing

The Contractor shall procure all parts required for the one EDU (TBR), one FM, and all GSE.

If it is necessary to procure parts due to long lead times or potential parts obsolescence prior to the CDR, the Contractor shall obtain the Government's consent prior to doing so.

The Contractor shall procure, build-up, test and maintain a supply of spare parts and tested subassemblies, to minimize cost, mitigate schedule and performance risks caused by the launch schedule, part and sub-assemblies damage or shortages, for one spare flight instrument.

The Contractor shall provide and maintain assembled and tested spares of sub-assemblies to mitigate against and minimize schedule delays.

The Contractor shall procure and deliver to the observatory contractor, mating flight connectors for all electrical interfaces to the observatory for the FM.

The Contractor shall perform fabrication and assembly/subassembly testing of all flight hardware, life test items and needed spares.

The Contractor shall provide all harnesses between instrument units.

The Contractor shall provide all instrument mounting hardware (i.e., all kinematic mounts and any vibration isolation hardware) and thermal isolation hardware, if required.

The Contractor shall provide one flight and flight spare set of thermal blankets.

The Contractor shall document and tag all non-flight items to be removed prior to flight with a red tag stating “STIS Remove before flight.”

The Contractor shall document and tag all flight items to be installed prior to flight with a green tag stating “STIS Install before flight.”

The Contractor shall provide and install the passive temperature sensors.

The Contractor shall perform safe-to-mate and signal characterization tests on all instruments and GSE prior to electrical mating.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

6.2.1 Field Programmable Gate Array (FPGA) Design and Development

The Contractor shall provide Government insight into Field Programmable Gate Array (FPGA) design, development and test activities including: monitoring verification adequacy, trade study data, auditing the FPGA design and development process, and participation in all FPGA peer reviews and technical interchange meetings.

The contractor shall provide a FPGA Design Data Package for each flight candidate FPGA design (both those inherited and those developed for SWFO L1) prior to committing the flight design, to accommodate government review and contractor response to any findings. Typically, this should occur after Place and Route, Timing Analysis and Signal Integrity Analysis have been completed for that FPGA and concurrent with board level testing.

The Contractor shall assist the Government's FPGA Independent Assessments, assess all review findings and recommendations, and implement corrective actions to address such findings and recommendations. Detailed justification and rationale shall be provided for any instances where the Contractor decided not to take corrective action on specific FPGA design findings and recommendations.

If Actel RTAX S series FPGAs are utilized in the instrument design, the contractor’s procurement of this part shall meet the requirements of one of the following options: (TBR)

Option 1: Procure parts to Actel E level flow. Procure parts sufficient to support a 6 piece life test per lot. Procure data package, which will include read and record data from screening, qualification, and Enhanced Lot Acceptance (ELA) testing. (TBD)

Option 2: Procure parts to Actel EV level flow. Procure the data package, which will include read and record data from screening, qualification, and Enhanced Lot Acceptance (ELA) testing.

The life test shall be included in the EV flow. (TBD)

6.3 Integration and Test

The Contractor shall integrate the instrument and perform a testing, calibration and data analysis regimen to qualify the instrument design, verify that instrument performance meets all requirements, proof test fixturing and debug all test and calibration procedures.

The Contractor shall perform a safe-to-mate and signal characterization on all instrument hardware and GSE prior to electrical mating.

The Contractor shall develop and deliver an End Item Data Package, contents and sections

(TBD).

The contractor shall use metric units when interfacing with the spacecraft including any drawings, documents, models, except for the cases called out in the STIS Spec.

Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.

The mounting interface shall be defined in the Mechanical Interface Control Drawing (MICD), which will be developed between the Instrument contractor and the SWFO spacecraft vendor.

The electrical interface shall be defined in the Electrical Interface Control Document (EICD), which will be developed between the Instrument contractor and the SWFO spacecraft vendor.

The Contractor shall provide digital imagery and video documentation of all instrument assemblies and subassemblies during the manufacturing process, environmental tests, critical activities, pre and post transportation, and final assembly.

6.3.1 Integration

During integration the Contractor shall perform any tests, alignments, etc. that cannot be performed at the subassembly level nor at the fully assembled level.

The Contractor shall integrate the FM and certify that the instrument is ready for the application of power.

The Contractor shall perform initial tests to demonstrate that the instrument is performing as designed and is ready to proceed with Functional Testing.

During the course of FM testing the Contractor shall debug and correct test procedures, GSE and fixtures as use indicates.

6.3.2 Performance Verification and Design Qualification

The Contractor shall develop and maintain all verification test procedures.

The Contractor shall perform data reduction and provide analysis of test results at the subassembly, assembly, unit and instrument level, and verification of observatory interfaces.

The Contractor shall prepare and provide Test Reports following completion of instrument functional and performance testing, life testing, environmental testing, and calibration testing commencing at the sub-assembly level.

6.3.2.1 Functional and Performance Testing

The Contractor shall conduct Functional and Performance Tests that includes Electrical Interface

Test…