SOLAR-PCI-REQ-0047A_05-13-2026.pdf

DOORS EXPORT Effective Date: May 13, 2026 Effective Date: May 13, 2031

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

SOLAR-PCI-REQ-0047, Revision A Space Weather Next (SW Next) Program

Space weather Observations at L1 to Advance Readiness Project Code 493

SOLAR

Partner Contributed Instrument (PCI)

Hosted Payloads Requirements Document

(HPRD)

U.S. Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA) National Environmental Satellite, Data, and Information Service (NESDIS) National Aeronautics and Space Administration (NASA)

GSFC SOLAR Project CMO May 13, 2026

Released https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm

SOLAR PCI HPRD SOLAR-PCI-REQ-0047, Revision B Effective Date: May 13, 2026 ii Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

SOLAR Partner Contributed Instrument (PCI) Hosted Payloads Requirements Document (HPRD)

Signature/Approval Page

Prepared by:

Lindsay Zima

Reviewed by:

Alejandra Barfknetch Yaireska Collado Vega Charles (Hudson) DeLee

Approved by:

John Vollmer iii Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Preface

This document is under Space weather Observations at L1 to Advance Readiness (SOLAR) configuration management (CM)-controlled document. Changes to this document require prior approval and shall be submitted in the SOLAR project Technical Data Management System (TDMS) via a Configuration Control Request (CCR) or Signature Control Request (SCoRe), along with supportive material justifying the proposed change. Changes to this document will be made via complete revision.

All of the requirements within this document assume the use of the work “shall” unless otherwise stated.

Questions or comments concerning this document should be addressed to:

SOLAR Project Configuration Management Office Goddard Space Flight Center Code 493 Greenbelt, MD 20771 iv Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date Description of Changes (Reference the CCR & CCB/ERB Approval Date)

Revision - 05/28/2025 Baseline release following the approval of SOLAR-CCR-

Revision A 05/13/2026 Update following the approval of SOLAR-CCR-0212 v Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Deviations/Waivers Record

Section # / Rqmt.

Deviation / Waiver #

CCR # Date Approved

Description

None. None. None. None. None.

vi Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table of TBCs/TBDs/TBRs/TBSs

Item No. Identifier Section Summary

1 PCIHPRD-72 The PCI Provider shall plan for a two-day (TBR) review.

2 PCIHPRD-79

The PCI Provider shall support the following SOLAR Project Mission-level reviews: PDR, CDR, Pre-Environmental Review (PER), Pre-Ship Review (PSR), Flight Operations Review (FOR), Operations Readiness Review (ORR) (TBD), Post-Launch Assessment Review (PLAR) (TBD), and the Operations Handover Review (OHR) (TBD).

3 PCIHPRD-

The PCI Provider shall (TBR) support interface testing with an PCI emulator and the Spacecraft Instrument Interface Simulator (SIIS) at the Spacecraft provider’s facility.

4 PCIHPRD-

The PCI shall provide support at the MOC for all Mission Readiness Testing (end-to-end testing; three tests, three days each, TBD) and Simulations and Rehearsals that include the PCI (two simulations, two days each, TBD), with the SOLAR Project MOC and Science Data Segment (SDS) (TBD). This support is assumed to be on-site. The time estimates per test exclude travel days.

5 PCIHPRD-

The PCI Provider shall provide support at the MOC of PCI on-orbit activation and commissioning for an estimated period of 10 staff-days (TBD).

6 PCIHPRD-

The PCI Provider shall deliver a Computer-Aided Design (CAD) file for PCI three months (TBR) prior to the Spacecraft-level PDR and an update, by the PCI PSR or the Spacecraft-level CDR whichever occurs first.

7 PCIHPRD-

The PCI Provider shall provide the Structural Analysis three months (TBR) prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

8 PCIHPRD-

The PCI Provider shall provide the thermal analysis three months (TBR) prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

9 PCIHPRD-

The PCI Provider shall provide the TMM three months (TBR) prior to the Spacecraft-level PDR and an update by the PCI PSR, if needed.

10 PCIHPRD-

The PCI Provider shall provide interface FMEA results in a report for review by the SOLAR Project three months (TBR) prior to the Spacecraft-level PDR and an update by the PCI PSR, if needed.

vii Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

11 PCIHPRD-

The PCI Provider shall summarize the results of the parts stress analysis in a Parts Stress Analysis Report to be provided to the SOLAR Project for review three months (TBR) prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

12 PCIHPRD-

221 The spacecraft will provide the PCI a 30 degree half cone angle FOV (TBR) centered on the +X SRF axis.

13 PCIHPRD-

The spacecraft will provide the PCI’s +YSRF face a 2pi steradian FOV to space excepting a FOV blockage with less than 80 W/m^2 back loading in any single direction.

14 PCIHPRD-

227 The PCI Provider shall provide the nominal launch mass with tolerances before Spacecraft PDR (TBC).

15 PCIHPRD-

Instrument unit, spacecraft, and test fixture interfaces will (TBR) be drilled using templates to correctly establish the pattern of the mounting holes.

16 PCIHPRD-

237 7.4.5 The PCI drill template shall (TBR) include appropriate alignment, orientation and location reference information.

17 PCIHPRD-

2568 7.4.7 The PCI shall limit the maximum torque imparted on the spacecraft to no greater than (TBD) N-m.

18 PCIHPRD-

248 7.5.2 The PCI shall utilize no more than 4 (TBR) analog signals to monitor critical temperature points when PCI is powered off.

19 PCIHPRD-

317 7.9

Commanding of the PCI during Observatory I&T shall be executed by the instrument EGSE transmitting instrument commanding from instrument EGSE to the Spacecraft EGSE.

20 PCIHPRD-

350 MAC Values in Tabular Format (TBC)

21 PCIHPRD-

355 Acceptance Sine Vibration Environment (S/C to LV

Interface) (TBR)

22 PCIHPRD-

363 ELV Separation Shock Envelope (Acceptance Levels)

(TBR)

23 PCIHPRD-

371 Observatory Acceptance Acoustic Levels (TBR)

24 PCIHPRD-

377 Transportation Loads (TBR) viii Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

25 PCIHPRD-

The PCI Provider shall provide Ground Support Equipment (GSE) to support Integration and Test activities at the Observatory level. GSE includes:

a) Shipping container for the PCI

b) Mounting Interface and Alignment Hardware for the

PCI, (e.g., jigs, optical references, etc.)

c) Lifting fixture, (if applicable)

d) Electrical Ground Support Equipment (EGSE) necessary for Bench Acceptance Testing (BAT) at the delivery of the PCI instrument. The Spacecraft will perform instrument commanding during Observatory Integration and Test. Instrument command and telemetry monitoring will be made available via Spacecraft Vendor provided terminals. The PCI science data will be made available to the PCI Provider during Observatory Integration and Test.

e) Purge Interface (TBR)

26 PCIHPRD-

780 2.0-3.0-4 TBD

27 PCIHPRD-

1101 17.0-1.0-30 TBD

28 PCIHPRD-

1104 17.0-1.0-31 TBR

ix Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table of Contents

1 INTRODUCTION

1.1 Scope

1.2 Purpose

1.3 Requirements Approach

2 PCI PROVIDER APPLICABLE DOCUMENTS

3 MISSION OVERVIEW

4 MANAGEMENT, REPORTING, REVIEWS, AND DOCUMENTATION

4.1 Program Management

4.2 Reporting

4.3 Advance Notifications

4.4 Reviews and Meetings

4.4.1 Kick-off Meeting

4.4.2 Technical Interchange Meetings (TIM)

4.4.3 Spacecraft Level Reviews

4.4.4 Mission-Level Reviews

4.5 Documentation

4.6 Risk Management

5 MISSION PHASE SUPPORT

5.1 Pre-Delivery Support

5.2 Post Delivery Support

5.3 Observatory Integration and Test

5.3.1 Radioactive Sources

5.4 Launch Site Support

5.5 Launch Support

5.5.1 Pre-Launch Support

5.5.2 Post-Launch Support

6 DESIGN, ANALYSIS, AND TEST

6.1 Drawing Package

6.2 Computer Models

6.3 Structural Analysis Report

6.4 Structural Math Model

6.5 Thermal Analysis Report

6.6 Thermal Model and Documentation

6.7 Failure Modes and Effects Criticality Analysis Report

6.8 Parts Stress Analysis Report

6.9 Input to Orbital Debris Assessment Report and End of Mission Plan

6.10 Payload Safety Requirements

7 INSTRUMENT SOLAR PROJECT SPACECRAFT TO PCI INTERFACE

REQUIREMENTS

7.1 Instrument Operations

7.1.1 Instrument Power Off

7.1.2 Launch and Orbit Raising

x Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

7.1.3 On-Orbit Concept

7.2 Dimension Standard

7.3 Reference Frames

7.4 Mechanical Interface Requirements

7.4.1 PCI Envelope

7.4.2 PCI Field of View (FOV)

7.4.3 Mass Properties

7.4.4 Unit Stiffness

7.4.5 Mounting

7.4.6 Flight and Non-Flight Equipment

7.4.7 Exported Torque

7.5 Thermal Interface

7.5.1 Interface Temperature

7.5.2 Temperature Monitoring

7.5.3 On-Orbit Thermal Environment

7.6 Electrical Interface

7.6.1 Electrical Power Interfaces

7.6.2 Voltage Characteristics

7.6.3 Electrical Power Grounding

7.6.4 PCI Electrical Accommodations

7.7 Command and Data Handling

7.7.1 Data Transfer Between the Instrument and Spacecraft

7.7.2 Cable Design and Grounding

7.7.3 Parts Selection to Prevent Failure Propagation

7.7.4 Telemetry Source Packet Format

7.7.5 Command Source Packet Format

7.7.6 PCI Data Rate

7.7.7 Pulse Per Second (PPS)

7.8 Magnetics

7.9 Instrument GSE to Spacecraft I&T GSE Interface

7.10 Contamination Control

7.10.1 Particulate Generation

7.10.2 Molecular Contamination Generation

8 SOLAR PROJECT ENVIRONMENTAL CONDITIONS

8.1 Limit Loads

8.2 Sine Vibration

8.3 Random Vibration

8.4 Shock

8.5 Acoustics

8.6 Pressure Profile

8.7 Transportation Loads

8.8 On-Orbit Environment

8.9 Charged Particle Radiation

8.10 Charging Environment

8.11 Humidity

8.12 Conducted Susceptibility

xi Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

8.12.1 CS101 - Conducted Susceptibility, Power Leads

8.12.2 CS06 - Conducted Susceptibility, Transients, Power Leads

8.12.3 CS114 - Conducted Susceptibility, Common Mode, Interconnecting Power and

Signal Cables

8.12.4 CS114 - Conducted Susceptibility, Differential Mode, Power Leads

8.12.5 CS115 - Conducted Susceptibility, Bulk Cable Injection, Impulse Excitation, Interconnecting Cables

8.13 Radiated Susceptibility

8.13.1 RS103 - Radiated Susceptibility, Electric Field, Launch

8.13.2 RS103 - Radiated Susceptibility, Electric Field, On-orbit

8.14 Launch Vehicle Environmental Control System Impingement Velocity

9 ENVIRONMENTAL VERIFICATION TESTS

9.1 Structural Test Factors and Durations

9.2 Test Tolerances

9.3 Structural Strength Test

9.3.1 Sine Burst Test

9.3.2 Static Load Pull Test

9.4 Sine Vibration Test

9.5 Random Vibration Test

9.6 Acoustics Test

9.7 Shock

9.8 Thermal Bake-out

9.9 Thermal Vacuum Test

9.10 Thermal Balance Test

9.11 Electromagnetic Compatibility Tests

9.11.1 CE101 - Differential Mode Conducted Emissions Limits

9.11.2 CE03 - Differential Mode Conducted Emissions Limits

9.11.3 CMBCE - Common Mode Bulk Conducted Emissions Limits

9.11.4 CETDT - Conducted Emissions, Time Domain, Transients Limits

9.11.5 RE102 - Radiated Emissions, Electric Field

10 HARDWARE PROCUREMENT/MANUFACTURING

10.1 Connectors

10.2 Supporting Hardware

10.3 Ground Support Equipment

10.3.1 Ground Support Equipment Interfaces

10.4 Instrument Emulators

11 REQUIREMENTS VERIFICATION AND TEST

11.1 Verification Matrix

11.2 Verification Test Procedures

11.3 Verification Artifacts

12 SAFETY AND MISSION ASSURANCE

12.1 Problem Reporting

12.2 Class I Changes

12.3 System Safety

12.4 Training and Certification of PCI Project Personnel

xii Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

12.5 Materials Identification and Usage List (MIUL)

12.6 Materials Usage Agreements (MUAs)

13 END ITEM ACCEPTANCE DATA PACKAGE (EIDP)

APPENDIX A SAMPLE OBSERVATORY-LEVEL TEST REPORT

APPENDIX B CHARGED PARTICLE RADIATION REQUIREMENTS

APPENDIX C TEST TOLERANCES

APPENDIX D ABBREVIATIONS AND ACRONYMS

APPENDIX E ROPS AND COPS TEMPLATE

xiii Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

List of Figures

Figure 1. SOLAR Spacecraft Reference System Figure 2. Telemetry Source Packet Definition Figure 3. Time Code Format Figure 4. Command Source Packet Definition Figure 5. Spacecraft Time Message Packet Figure 6. Acceptance Sine Vibration Environment (S/C to LV Interface) (TBR) Figure 7. ELV Separation Shock Envelope (Acceptance Levels) (TBR) Figure 8. Observatory Acceptance Acoustic Levels (TBR) Figure 9. Power Lead Conducted Susceptibility (CS101) Voltage Limit Figure 10. Conducted Susceptibility Power Limit (30 Hz to 150 kHz) Figure 11. CS06 Conducted Susceptibility Transient Waveform Figure 12. Common Mode Conducted Susceptibility, Bulk Cable Injection (CS114)

Calibrated Test Levels Figure 13. Conducted Susceptibility, Power Leads, 150 kHz to 50 MHz Limit Figure 14. Conducted Susceptibility, Power Leads, 150 kHz to 50 MHz Current Limits .. 42 Figure 15. CS115 Impulse Waveform Figure 16. CE101/CE1012 (CE03) Differential Mode Limits Figure 17. Common Mode Conducted Emissions Limit Figure 18. Inrush Current Transient Default Limit Figure 19. Radiated Emissions Electric Field Limits Figure 21. Total ionizing dose-depth curve for a 5-year mission at L1 Figure 22. DDD in Si Dose-Depth Curve Figure 23. Displacement Damage Dose in Gallium Arsenide Dose-Depth Curve Figure 24. LET Spectrum of GCR Background Figure 25. Solar LET Spectrum Background Figure 26. Solar Proton Background Spectra Figure 27. Peak Solar Particle Event Flux Figure 28. Peak Solar Proton Flux

List of Tables

Table 1. FMEA Severity Categories Table 2. Orbit Thermal Parameters Table 3. PCI Contamination Requirements Table 4. MAC Values in Tabular Format (TBC) Table 5. Random Vibration Levels for PCI Table 6. Candidate LV Shock Environment Table 7. Candidate LV Payload Acoustics Design Envelope Table 8. Transportation Loads (TBR) Table 9. RS103 - Radiated Susceptibility, Electric Field at Launch Table 10. RS103 - Radiated Susceptibility, Electric Field On-orbit Table 11. Structural Test Factors and Durations Table 12. Reserved xiv Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table 13. Total Ionizing Dose vs. Shielding Thickness Table 14. Displacement Damage Dose in Silicon vs. Shielding Thickness Table 15. Displacement Damage Dose in Gallium Arsenide vs. Shielding Thickness Table 16. Abbreviated LET Spectrum of GCR Background Table 17. Solar Background LET Spectrum Table 18. Solar Proton Background Flux Table 19. Peak Solar Particle Event Flux Table 20. Peak Solar Proton Flux

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1 INTRODUCTION

1.1 Scope

The Partner Contributed Instrument (PCI) is classified as a “partnered payload,” as defined in Requirements for Partner Payloads Hosted on GSFC Spacecraft, GSFC-STD-8008. Therefore, these are the nominal set of requirements imposed on partner payloads hosted on Goddard Space Flight Center (GSFC) spacecraft to protect the spacecraft. From the perspective of the SOLAR project, mission success for the partner payload is deferred to the partner’s own practices.

Note, this HPRD only applies to the PCI and not the already established X-Ray Flux Monitor (XFM) instrument that is being contributed by ESA and which has its own separate HPRD.

1.2 Purpose

The purpose of this Hosted Payload Requirements Document (HPRD) is to define the PCI provider tasks, deliverables, responsibilities, and the requirements levied on the PCI.

This document provides the initial set of Spacecraft to PCI interface requirements. This set of requirements will serve as the starting point for the development of the Space weather Observations at L1 to Advance Readiness (SOLAR) Project Spacecraft to PCI Interface Control Document (ICD). The spacecraft provider will develop the SOLAR Project Spacecraft to PCI

ICD.

This document provides requirements and guidelines for the environmental verification program for the SOLAR Project PCI and describes methods for implementing those requirements. It contains a baseline for demonstrating by test or analysis the satisfactory performance of hardware in the expected mission environments, and that minimum workmanship standards have been met. It elaborates on those requirements, gives guidelines, and required test levels, provides guidance in the choice of test options, and describes acceptable test and analytical methods for implementing the requirements.

1.3 Requirements Approach

For requirements specified in this HPRD, the intent of a “shall” is to designate both a need for compliance and a need for verification of that compliance to preclude potential harm to the SOLAR project spacecraft, co-manifested instruments, and personnel or ground facilities/equipment.

In the above context, if a “shall” statement cannot be met, an effort to characterize the associated risk will occur, with one or more of the following likely results:

• Requirement would be deferred, at risk, to a higher level of assembly

• Requirement would be updated or modified

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

• Waiver or deviation would be written and granted

It is not the intent of the SOLAR project to dictate changes to the PCI design, except as needed to meet SOLAR spacecraft interface requirements. This is the case because changing an existing or well-understood design or departing from an organization’s established procedures introduces the potential for additional risk.

Unless a specific verification method is explicitly stated as part of a requirement, the PCI provider shall propose a verification method. European Cooperation for Space Standardization (ECSS) verification methods are acceptable if equivalency to the corresponding NASA standards can be established. Proposed or alternative verification methods, which pertain to the spacecraft interfaces or which may impact other SOLAR project instruments, require the approval of the SOLAR project.

Note: An instrument with requirement(s) that are not satisfactorily verified constitutes a potential threat to the primary mission objectives. Under such circumstances, that instrument ultimately may not be flown or may be flown with severely curtailed operations.

All other terms, including “will,” only designate statements of fact or intentions of SOLAR project and are not to be interpreted as provider requirements.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

2 PCI PROVIDER APPLICABLE DOCUMENTS

The following are the applicable documents from which this document has been derived. Any modification to an applicable document will be reviewed to identify the impact upon this document. In the event of conflict between an applicable document and the content of this document, the SOLAR project mission systems engineer has the final authority for conflict resolution.

Applicable Documents

Document Number Title SOLAR-SYS-REQ-0003 SOLAR Project Level 2 Requirements Document (L2RD) GSFC-STD-8008 Requirements for Partner Payloads Hosted on GSFC Spacecraft SOLAR-SC-REQ-0005 SOLAR Project Spacecraft Requirements Document (SRD) SOLAR-SYS-REQ-0030 SOLAR Project Observatory Technical Resource Allocation

Document (OTRAD) SOLAR-SYS-REQ-0016 SOLAR Project Radiation Hardness Assurance Requirements

Document (RHARD) EEE-INST-002 Instructions for EEE Parts Selection, Screening, Qualification, and

De-rating

NASA-STD-8719.24-A

and Annexes

NASA Payload Safety Requirements

NA-GSFC-2005-05 Latent Damage Reliability Issues Due to Single-Event Latchup and High-Current Error Modes

IEEE/ASTM SI-10 American National Standard for Metric Practice CCSDS 133-B-2 Consultative Committee for Space Data Systems (CCSDS) Space

Packet Protocol CCSDS 301.0-B-4 CCSDS Time Code Formats ECCS-E50-12A European Cooperation for Space Standardization (ECCS)

SpaceWire – Links, nodes, routers, and networks MIL-STD-461F Electromagnetic Interference Characteristic Requirements for

Equipment MIS-STD-462 Measurement of Electromagnetic Interference Characteristics ASTM E595-15 (2021) Standard Test Method for Total Mass Loss and Collected Volatile

Condensable Materials from Outgassing in a Vacuum Environment GSFC-STD-7000B General Environmental Verification Standard (GEVS) For GSFC

Flight Programs and Projects NIST Special Publication (SP) 800-53

National Institute of Standards and Technology Security and Privacy Controls for Information Systems and Organizations

NPR7150.2D NASA Software Engineering Requirements 540-PG-8700.2.1F Design and Certification of Dollies, Stands, and Shipping

Containers

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

3 MISSION OVERVIEW

The National Oceanic and Atmospheric Administration's (NOAA) space weather situational awareness and forecasting are critical services for the Nation. Timely and accurate forecasts of solar and geospace activity are needed to protect humans and technological systems in space and ensure continuity of services on Earth. To forecast space weather and provide accurate watches and warnings, imagery of coronal mass ejections (CMEs) from the Sun and in situ measurements of solar wind plasma are required. NOAA’s SOLAR project is the next generation space weather mission series designed to ensure the continuity of operational space weather observations required for space weather alerts beyond the current generation of missions consisting of the Space Weather Follow-On (SWFO)-L1, Deep Space Climate Observatory (DSCOVR), and Solar and Heliospheric Observatory (SOHO). The SOLAR project will be part of a robust space and ground architecture based on the NOAA National Environmental Satellite, Data, and Information Services’ (NESDIS) long-term planning. The SOLAR project will procure a minimum of (2) two Spacecrafts and instruments necessary to meet the requirements outlined in this document.

The instrument set will include a solar coronagraph, a solar wind plasma instrument, a magnetometer, a solar X-ray irradiance sensor, and a suprathermal ion sensor. The Project will provide for accommodation of the Energetic Particle Spectrometer Instrument (EPSI) on the SOLAR-A Observatory, and accommodation of a Partner Contributed Instrument on the SOLAR-B Observatory. The instrument manifest may change over the course of the series as improved technologies and partner contributed instruments come available.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4 MANAGEMENT, REPORTING, REVIEWS, AND DOCUMENTATION

4.1 Program Management

The PCI Provider shall designate and identify by name a single individual who will serve as a point of contact with the SOLAR Project Representative for all technical aspects of the PCI development.

4.2 Reporting

The PCI Provider shall prepare and present to the SOLAR Project Representative a monthly technical status summary in written format.

The monthly technical status summary shall be a communication of the period's progress to include topics such as schedule overview, accomplishments, technical performance measures, status of key milestones, risks, problem areas, challenges or issues, and activities on-going and planned. This summary is intended to be easily produced and may be as simple as a bulletized list.

The PCI Provider shall immediately report in an email to the SOLAR Project Representative any delays in deliverables that may impact the Spacecraft development or integration and test schedule.

The PCI Provider shall generate and report progress in the monthly status report on a list of significant milestones that will enable the SOLAR Project Representative to evaluate progress over the course of the project.

The PCI Provider shall deliver a Mass and Power Report on a monthly basis.

The Mass Properties and Power Report shall provide the latest information on instrument mass, center of mass location, and moments of inertia.

The Mass Properties and Power Report shall provide power profiles indicating the elements that are individually controlled by command or automatic program, duty cycles, peaks such as turn-on transients, and average and peak power budget requirements during launch and operational modes.

The Mass Properties and Power Report shall separate the heater power from the operational power.

The Mass Properties and Power Report shall differentiate between calculated, estimated, or actual values for mass and power.

The Mass Properties and Power Report shall report values to at least the major assembly level of the subsystems, e.g., mechanism, power supplies, heaters, cabling, etc.

The Mass Properties and Power Report shall identify the accuracy of the values provided.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4.3 Advance Notifications

The PCI Provider shall notify the SOLAR Project Representative at least forty-five (45) days in advance of all environmental test activities and major PCI reviews, e.g., Preliminary Design Review (PDR) and Critical Design Review (CDR) to arrange travel by the SOLAR Project Representative or designee to witness and/or support the test or review. The actual date may change a few days one direction or the other, if necessary, after the initial notification.

The PCI Provider shall confirm the actual date of the environmental test activity and major PCI review one week in advance.

4.4 Reviews and Meetings

4.4.1 Kick-off Meeting

The PCI Provider shall organize and hold a Kick-off Meeting with the SOLAR Project at the PCI Provider’s facility or by teleconference/videoconference.

The PCI Provider shall provide to the SOLAR Project a Kick-off Presentation Package.

The Kick-off Meeting shall include a line-by-line review of this HPRD.

During the Kick-off Meeting the PCI Provider shall provide their interpretation of each line item (Items indicated by “Shall.”).

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

If the review is not complete in two days, the PCI Provider shall continue to conduct and support the review until the SOLAR Project deems the review complete.

4.4.2 Technical Interchange Meetings (TIM)

The PCI Provider shall participate in TIMs with the SOLAR Project. TIMs will be informal, usually conducted via teleconference, with infrequent meetings to be conducted at the PCI Provider designated facility. TIMs will support SOLAR Project programmatic planning and coordination of technical issues including, but not limited to: spacecraft interfaces, environmental test activities, materials usage, contamination requirements, launch site operations, mission operations planning, etc.

4.4.3 Spacecraft Level Reviews

The PCI Provider shall support in person the SOLAR Project Spacecraft-level PDR, CDR, and the System Integration Review (SIR) and provide the appropriate input and/or present relevant instrument interface information as needed.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4.4.4 Mission-Level Reviews

The PCI Provider shall support the following SOLAR Project Mission-level reviews: PDR, CDR, Pre-Environmental Review (PER), Pre-Ship Review (PSR), Flight Operations Review (FOR), Operations Readiness Review (ORR) (TBD), Post-Launch Assessment Review (PLAR) (TBD), and the Operations Handover Review (OHR) (TBD).

4.5 Documentation

In addition to the documentation specifically called for in this requirements document, upon request by the SOLAR Project Representative, the PCI Provider shall make available a copy of any document or data generated during this development effort that pertains to instrument-to-spacecraft interfaces for review by the SOLAR Project at either the PCI Provider's facility or via the internet. This includes, but is not limited to, technical reports and memorandums, drawings, schematics, studies, analyses, parts and materials data, test data, alerts, calibration coefficients, calibration algorithms, etc.

4.6 Risk Management

The PCI Provider shall track all risks associated with interfaces to the spacecraft or that may impact schedule on an ongoing basis, capture risk attributes and mitigation information by collecting data, establish performance metrics, and examine trends, deviations, and anomalies.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5 MISSION PHASE SUPPORT

5.1 Pre-Delivery Support

The PCI Provider shall deliver by the PCI Critical Design Review an Operations Handbook and another update by the PCI Pre-Ship Review.

The Operations Handbook shall provide all the information needed for operating the PCI, interpreting all housekeeping data, and taking corrective action as necessary.

As a minimum, the Operations Handbook shall include the following:

a) Operational Constraints

b) Initial On-orbit Turn-on and Checkout - include details such as the contents of operational control tables, start-up command sequences, etc.

c) Heater usage during on-orbit mode

d) Initial on-orbit outgassing requirements. (i.e. minimum time post-launch before instrument or instrument functions can be started.

e) Instrument diagnostic procedures

f) Periodic Operations e.g., on-board memory tests and corrective upload procedures

g) Standby Mode Configuration and Operation

h) Eclipse procedures and off-point procedures

i) Recovery procedures from safe mode

j) Corrective actions required for error conditions

k) Software operating, diagnostics, and patching procedures

l) Itemized identification of all telemetry signals from and commands to the instruments.

m) A description of the data format, including packet size, headers, addresses and data location.

n) Red and Yellow limit tables for all housekeeping telemetry for ground testing and all on-orbit operational modes

o) A complete list of instrument commands for all instrument modes of operation and sequence testing with a description of their effects. The Command List includes the command number, title of command, description, telemetry verifier (if any), and subsystem commanded. It identifies any critical commands which may damage the instrument in certain situations.

p) The operations handbook will provide Recommended (standard) and Contingency

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Operating Procedures (ROPs and COPs) for the instrument that will provide the following details:

1. Operational Constraints / Flight Rules for Instrument

2. Operations description: Include “Day in the life” for each mission phase (eg, activation, cruise, orbit raising, normal ops, maneuver cadence/station-keeping, calibrations, other special activities/maintenance, etc.)

3. Configurations for each Instrument state and mode of operation

4. Recommended Operating Procedures:

a. For each Instrument: Activation, Nominal Ops, Special Activity, De-orbit, (calibration, test/checkout, etc), and Contingency/Recovery / Fault Management

b. For each procedure, provide:

i. Short description of the procedure, including any state or mode changes induced by the procedure

ii. Whether the command is designated a SAFETY or HAZARDOUS command

iii. Planned use (phase/mode/configuration as applicable) [Include SC configuration/mode if applicable]

iv. Applicable Constraints/Flight Rules

v. Initial Conditions or other dependencies

vi. Command sequence, timing, and TLM validation

c. For each command sequence provide:

i. Step by step operation (including references to other imbedded procedures if applicable)

ii. Timing (if applicable)

iii. State change (if applicable)

iv. CMD mnemonics including parameters/options

v. TLM response for each command

d. When applicable, provide drawings to illustrate state/mode changes (eg, changes to comm command/housekeeping/mission data path selections)

The ROPs and COPS will use the template shown in Appendix E.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The PCI Provider shall deliver by PCI Pre-Environmental Review a Command and Telemetry Database in a format and schema negotiated with the spacecraft contractor and approved by the SOLAR Project.

The Telemetry and Command Database shall include all parameters necessary to operate the instrument during ground test and all phases of on orbit operations.

The PCI Provider shall support the development of and review the integrated command and telemetry database and the script-based test procedures written by the spacecraft integration team for use in integration and testing of the PCI on the observatory.

The PCI Provider shall deliver by PCI Pre-Environmental Review a Flight Telemetry and Command Handbook.

The Flight Telemetry and Command Handbook shall provide an itemized identification of all telemetry and commands to and from the instrument.

The Flight Telemetry and Command Handbook shall contain a Data Format Control section defining the contents of all telemetry packets, including sensor data, metadata, calibration data, ancillary data, engineering data, health and safety data, and commands.

All command and telemetry Source Packet content definitions shall list all Application Process Identifications (APIDs), secondary header flags, packet length including headers, and data zone contents.

The command description shall contain a complete list of instrument commands for all instrument modes of operation and sequence testing with a description of their effects.

The Command List shall include the command number, title of command, description, telemetry verifier (if any), and subsystem commanded.

The Command List shall identify any critical commands that may damage the instrument in certain situations.

The Telemetry Listing shall contain the telemetry position in the source packet, telemetry point size in bytes, description of the telemetry point, indication whether analog or digital, range of parameter, accuracy of telemetry point, and default sample rate.

The Telemetry Listing shall contain a complete list of housekeeping telemetry data coming from the instrument, including telemetry calibrations and levels that require alerts or immediate actions, for each instrument.

The PCI Provider shall deliver PCI packetized data for input for observatory and NOAA ground system testing and debugging ingest and analysis capabilities by PCI Pre-Environmental Review.

The PCI PER packetized data shall include all PCI data from government specified tests.

The packetized data shall be delivered on digital media.

The PCI Provider shall (TBR) support interface testing with an PCI emulator and the Spacecraft Instrument Interface Simulator (SIIS) at the Spacecraft provider’s facility.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The PCI Provider shall deliver a Maintenance, Test, and Operations Manual concurrent with the delivery of the PCI emulators.

The Maintenance, Test and Operations Manual shall include detailed vendor and custom equipment description, including a list of parts/devices.

The Maintenance, Test and Operations Manual shall include configuration of the final design including a set of reduced electrical schematics and top assembly mechanical drawings supporting the design and function description.

The Maintenance, Test and Operations Manual shall include installation procedures.

The Maintenance, Test and Operations Manual shall include hardware maintenance resources.

The Maintenance, Test and Operations Manual shall include operations and test procedures.

The Maintenance, Test and Operations Manual shall include corrective maintenance procedures.

The Maintenance, Test and Operations Manual shall include preventive maintenance procedures.

The Maintenance, Test and Operations Manual shall include troubleshooting guide and error message descriptions.

The Maintenance, Test and Operations Manual shall include a detailed test and certification procedure for certifying PCI emulator performance.

The PCI Provider shall provide inputs to SOLAR Project to support the Mission Operations Concept documentation generation.

5.2 Post Delivery Support

The PCI Provider shall perform the following post-delivery support activities at the Spacecraft provider’s facility: Incoming inspection, bench test check-out, and safe-to-mate.

The PCI Provider shall present the bench test check-out and safe-to-mate results to the SOLAR Project and the Spacecraft provider for review and approval.

5.3 Observatory Integration and Test

The PCI Provider shall assist and support the following activities: instrument inputs to support integration-related reviews, instrument-to-spacecraft integration, a post-integration interface test, Observatory environmental testing, Observatory performance testing, and final inspections before shipment to the Launch Site.

The PCI Provider support during observatory integration and test shall include on-site technical personnel familiar with the instrument’s design, construction, and operation.

The PCI Provider shall provide Observatory-level Test Reports that provide a summary of all instrument performance during observatory level testing from first power ON through final testing.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The PCI Provider shall deliver their Observatory-level Test Reports upon completion of each Observatory-level test, which can be in the form of a simple checklist (Refer to Appendix A for a template). The same general format template can be modified for Comprehensive Performance Tests (CPTs)’ or other integrated testing as required.

5.3.1 Radioactive Source

The Spacecraft provider will provide any radioactive source(s) needed for PCI performance validation during the instrument bench check-out upon delivery and during Observatory-level CPTs.

The PCI Provider shall provide the information necessary, e.g., type of source, strength, size, etc., for the Spacecraft provider to provide a radiation source, if needed, for PCI performance validation during bench check-out upon delivery and during Observatory-level CPTs.

5.4 Launch Site Support

The PCI Provider shall assist and support the following activities at the Launch Site: post-ship Observatory functional and any applicable performance testing, final flight preps/close-outs, and inspections.

5.5 Launch Support

The main goal of this task is to facilitate support to the SOLAR Project Flight Operations Team (FOT) and mission manager for on orbit mission activities and/or troubleshooting. Mission operations support is divided between pre-launch support and post-launch support.

5.5.1 Pre-Launch Support

The PCI Provider shall provide technical inputs to develop, verify, and validate the Mission Operations Center (MOC) Instrument Standard Operating Procedures, Contingency Operating Procedures (COPs), instrument activation sequences, instrument stand-by modes, Instrument Telemetry & Command database, and Telemetry Displays, Constraints, and Restrictions, and Trending reports.

The PCI shall provide support at the MOC for all Mission Readiness Testing (end-to-end testing;

three tests, three days each, TBD) and Simulations and Rehearsals that include the PCI (two simulations, two days each, TBD), with the SOLAR Project MOC and Science Data Segment (SDS) (TBD). This support is assumed to be on-site. The time estimates per test exclude travel days.

The PCI Provider shall provide instrument configurable items stored and used in the instrument (e.g., tables, files, parameters, software patches) necessary to operate the instrument during pre-launch testing, Mission Rehearsal, and on-orbit phases in a format compatible with SOLAR Project ground system for command input to be received by the instrument.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5.5.2 Post-Launch Support

The PCI Provider shall provide support at the MOC of PCI on-orbit activation and commissioning for an estimated period of 10 staff-days (TBD).

The PCI (operations) specialist(s) shall provide consultation, troubleshooting, anomaly resolution, and general on-call support to the SOLAR Project team during the duration of the on-orbit portion of the mission as it is related to the propagation of damage or a fault at the interface to the Spacecraft.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

6 DESIGN, ANALYSIS, AND TEST

The PCI Provider will demonstrate compliance with the requirements for design, analysis, and test detailed in this section to demonstrate that no portion of the PCI design, PCI operation, or an PCI fault can cause harm to the Spacecraft or the other instruments.

6.1 Drawing Package

The PCI Provider shall provide a drawing package that includes, but is not limited to:

ELECTRICAL: Top-level assembly drawings (board level schematics available on request).

MECHANICAL: Top-level assembly drawings.

6.2 Computer Models

The PCI Provider shall deliver a Computer-Aided Design (CAD) file for PCI three months (TBR) prior to the Spacecraft-level PDR and an update, by the PCI PSR or the Spacecraft-level CDR whichever occurs first.

6.3 Structural Analysis Report

The purpose of the structural analyses is to demonstrate compliance with the mechanical/structural design and test requirements at the spacecraft to PCI interface. Structural analyses verify the structural integrity of the flight hardware by assessing the size and location of applied loads, load paths, and critical failure modes.

The PCI Provider shall provide a Structural Analysis for the Flight Unit interface and primary structure to ensure the capability to withstand and survive launch and ascent loads.

The PCI Provider shall provide the Structural Analysis three months (TBR) prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

The Structural Analysis shall use factors of safety of 2.0 on yield and 2.6 on ultimate when strength qualified by analysis (rather than by test, subject to NASA/GSFC approval).

The PCI Provider shall qualify by test Beryllium and composite materials.

The structural analysis shall include the effects of any thermal inputs.

The PCI venting shall be directed away from any instrument or spacecraft contamination-sensitive surfaces.

The structural analysis shall include a venting analysis for applicable flight components, such as enclosed volumes, thermal blankets, and contamination enclosures, susceptible to pressure loadings. The purpose of this analysis is to verify that positive strength margins exist at loads equal to twice those induced by the maximum pressure differential during launch or that the design provides adequate venting areas and filters to prevent pressure build up during ascent.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The PCI Provider shall summarize the results of the structural analysis in a report that will be provided to the SOLAR Project for review. This report may be in slide format.

6.4 Structural Math Model

The structural math model shall include a full order structural math model.

The full order structural math model shall be NASTRAN compatible.

The structural math models shall provide models of the instrument in launch configuration.

The Structural Math Model Reports shall document the math models with the following information:

a) Configuration version

b) Identification of the documents and drawings used to generate the model

c) Model mass properties

d) Boundary conditions

e) Figures showing the components modeled

f) References used for mechanical properties

g) A summary of output results including modal frequencies, deflections and critical stresses

h) Undeformed and deformed plots of the FEM

6.5 Thermal Analysis Report

The PCI shall meet thermal requirements assuming the spacecraft heat rejection capability as already identified in the SOLAR Project Spacecraft Requirements Document (SRD).

The PCI Provider shall provide a thermal analysis that demonstrates compliance with the thermal design and test requirements at the Spacecraft to PCI interface.

The PCI Provider shall provide the thermal analysis three months (TBR) prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

The PCI Provider shall perform the thermal analysis with the components operating at their maximum expected power dissipations.

The PCI Provider shall summarize the thermal analysis in a thermal analysis report to be provided for review by the SOLAR Project. This report may be in slide format.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

6.6 Thermal Model and Documentation

The PCI Provider shall provide reduced Thermal Math Models (TMMs) for the PCI with between 10 and 50 nodes per box.

The PCI Provider shall deliver the TMMs in an agreed upon format.

If the PCI Provider does not have the project-compatible software to create TMMs, then the PCI Provider shall provide sufficient detailed information such that the Spacecraft provider can create the TMMs.

The PCI Provider shall provide documentation of the TMM, including detailed descriptions of all aspects of the model necessary for the Spacecraft provider to run and/or recreate the TMMs.

The PCI Provider shall provide the TMM three months (TBR) prior to the Spacecraft-level PDR and an update by the PCI PSR, if needed.

6.7 Failure Modes and Effects Criticality Analysis Report

The PCI Provider shall perform an FMEA (Failure Modes and Effects Analysis) of the PCI interface to the Spacecraft to identify potential failures with severity categories 1, 1R, 1S, 2, 2R, and 3 per Table 1.

Table 1. FMEA Severity Categories

Category Severity Severity Description 1 Catastrophic Failure modes that could result in serious injury, loss of life (flight or ground personnel), or total loss of mission.

1R Failure modes of identical or equivalent redundant hardware items that could result in Category 1 effects if all failed.

1S Failure in a safety or hazard monitoring system that could cause the system to fail to detect a hazardous condition or fail to operate during such condition and lead to Category 1 consequences.

2 Critical Failure modes that could result in loss of one or more mission objectives as defined by the GSFC project office.

For PCI, this would be damage to the spacecraft or other instruments.

2R Failure modes of identical or equivalent redundant hardware items that could result in Category 2 effects if all failed.

3 Significant Failure modes that could cause degradation to mission objectives as defined by the GSFC project office.

The PCI Provider shall update the FMEA throughout the development life cycle to address design changes that result in changes to failure modes, causes, effects, system impact, or to mitigation status and corresponding retention rationale.

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The PCI Provider shall provide interface FMEA results in a report for review by the SOLAR Project three months (TBR) prior to the Spacecraft-level PDR and an update by the PCI PSR, if needed.

6.8 Parts Stress Analysis Report

For circuits identified as posing an interface risk in the interface FMEA, the PCI Provider shall perform a parts stress analysis on Electrical, Electronic, and Electromechanical (EEE) parts and devices as employed in the circuit designs of the Flight Item to certify conformance with the derating requirements of EEE parts.

The PCI Provider shall provide justification for all applications that do not meet the derating criteria.

For Spacecraft to PCI interface components, the PCI Provider shall use NASA document EEE- INST-002, Instructions for EEE Parts Selection, Screening, Qualification, and Derating to establish criteria.

The PCI Provider shall summarize the results of the parts stress analysis in a Parts Stress Analysis Report to be provided to the SOLAR Project for review three months (TBR) prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

6.9 Input to Orbital Debris Assessment Report and End of Mission Plan The PCI Provider shall provide input to the Orbital Debris Assessment Report (ODAR) and End of Mission Plan (EOMPL) 30 days prior to the Spacecraft-level PDR and an update, if needed, by the PCI PSR.

6.10 Payload Safety Requirements

PCIHPRD-576: All flight hardware being developed shall meet the applicable standards of NASA-STD-8719.24 and Annexes.

Rationale: Flow down of SSRD for LV Safety Requirements

PCIHPRD-577: All GSE that is being delivered for use at the Launch Site shall meet the applicable standards of NASA-STD-8719.24 and Annexes.

Rationale: Flow down of SSRD for LV Safety Requirements

The SOLAR Project will support determination of applicability as described below. Sections of the NASA STD 8719.24 Annexes that are relevant to the hardware and GSE being developed are included in Volume 3 and Volume 6. Volume 3 contains system/design requirements and Volume 6 contains operational requirements.

a) Mechanical Systems and GSE: Volume 3 Chapter 6 and Volume 6 Chapter 6

b) Hazardous Materials: Volume 3 Chapter 10 and Volume 6 Chapter 10

Check https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

c) Electronics (including Battery requirements): Volume 3…