Attachment A - MSRCCRS-VS-SOW.pdf

Effective Date: August 04, 2022 Expiration Date: August 04, 2027

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

400-FORM-0002 (4/16/2014)

National Aeronautics and Space Administration

Goddard Space Flight Center Greenbelt, Maryland

MSRCCRS-VS-SOW-0008, Revision -

Mars Sample Return - Capture, Containment and Return System (MSR - CCRS) Project

NASA/GSFC Code 435

CCRS Capture-Enclosure (CE) Camera

Statement of Work

MSR-CCRS CMO (NR)

August 04, 2022

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

CE Camera SOW MSRCCRS-VS-SOW-0008 Revision-ii

CCRS Capture-Side Camera Statement of Work

Signature/Approval Page

Prepared by:

Ron Shiri

Reviewers/Approvers:

R. Montgomery 7/27/2022 K. Cleveland 7/27/2022 B. Childs 7/27/2022 D. Wilson 7/27/2022 G. Casto 7/27/2022 C. Bacon 7/27/2022 K. Grello 7/26/2022 B. Yang 7/26/2022 B. Bos 7/26/2022 G. Cataldo 7/26/2022 K. Wrenn 7/20/2022 R. Ferrer 7/20/2022 B. Rizk 7/18/2022 W. Posey 7/15/2022 T. Feehan 7/11/2022 J. Capone 7/06/2022 D. Donovan 7/06/2022

Approved by:

Keith Walyus MSRCCRS CCB Chairman 7/27/2022

*** Electronic signatures are available on-line at: https://ipdtdms.gsfc.nasa.gov*** iii

Preface This document is a Mars Sample Return (MSR) Capture, Containment and Return System (CCRS) Project configuration control board (CCB) controlled document. Changes to this document require prior approval of the CCB Chairperson or designee. Proposed changes will be submitted in the Technical Data Management System (TDMS) via a configuration change request (CCR) along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.

All of the requirements in this document assume the use of the word "shall" unless otherwise stated.

Questions or comments concerning this document should be addressed to:

CCRS Configuration Management Office Mail Stop: 435 Goddard Space Flight Center Greenbelt, Maryland 20771 iv

Change History Log

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

Revision- 08/04/2022 Released per MSRCCRS-CCR-0116, July 27, 2022 v

Table of TBDs/TBRs/TBSs Action Item

No.

Location Summary Individual/

Organization Actionee vi

Table of Contents

1 INTRODUCTION

Purpose Scope Deliverables Hardware Deliverable Definitions Deliverable Schedule Related Documentation

2 GENERAL

Traceability Requirements Terminology and Verification Verification Methods

3 QUALITY ASSURANCE REQUIREMENTS

Quality Assurance Program Contractor Performance Customer Inspection and Acceptance Records Unverified Failure Processes Software Milestone Reviews

4 TRANSPORTATION, HANDLING, PACKING, PACKAGING AND SHIPPING

REQUIREMENTS

Transportation and Handling Shipping Containers Packing and Packaging Hand Carry Humidity Monitors Shock Monitors

5 TECHNICAL MANAGEMENT, TESTS AND PROCESSES

Performance Calibration Technical Considerations Electromagnetic Interface/Electromagnetic compatibility Vibration Thermal Thermal Vacuum Test Requirements Software Development Requirements Contamination Control Scheduled Communications and Reviews Post-Delivery Support

6 DATA DELIVERABLES

Documents Requiring Approval vii

Data Required Required SDRLs

NA TO CONTRACTOR (PROBABILISTIC RISK ASSESSMENT (PRA)

NA TO CONTRACTOR (FAULT TREE ANALYSIS)

List of Figures

Figure 1. Representative Thermal Vacuum Test Profile

List of Tables

Table 1. Random Vibration Test Specifications Table 2. Qualification Level Shock Response Spectrum (Q=10) Table 3. Required SDRLs

1 INTRODUCTION

Purpose The National Aeronautics and Space Administration (NASA) is developing the Capture, Containment and Return System (CCRS) as part of NASA’s Mars Sample Return campaign.

CCRS will be the primary payload of the European Space Agency’s Earth Return Orbiter which will launch into space on an Ariane 6 no earlier than 2026. The CCRS will capture an Orbiting Sample (OS) container in Mars orbit, process and prepare the OS for a return to Earth and deliver the Martian surface samples to the Utah Test and Training Range (UTTR) operated by the United States Air Force. The Capture Enclosure of CCRS provides the OS capture and OS processing functionality for the system.

To carry out the CCRS tasks, after the Orbiting Sample (OS) is captured and stationary, the Capture-Enclosure (CE) cameras will collect and transfer to the Avionics sub-system at least one image of the OS endcap to determine its orientation as described by 1) the OS Interface Control Document (ICD) and 2) Flight Subsystems to Vision System Interface Control Document (ICD).

The Capture Enclosure (CE) architecture requires two camera heads to acquire these data sets using vantage points inside the CE. The camera heads will be mounted to fixed position inside CE.

The illumination for the CE imaging will be provided by an array of LEDs illuminating the Orbiting Sample (OS) after CCRS capture with an illuminance and areal coverage to enable acquisition of an image by the Vision System camera to allow an observer to determine the correct end of OS facing the CCRS interior.

The purpose of this document is to describe and define the work required of the contractor by NASA for successful delivery of the Capture-Enclosure (CE) camera.

Scope The contractor will provide all labor, materials, facilities, service, equipment, analyses and management activities necessary to procure parts and materials, assemble and test, and deliver the CE camera described in the MSRCCRS-VS-SPEC-0036, CCRS Camera Specification and this document.

Deliverables [VS-C-300] The deliverables of this procurement shall include:

1. Two (2) flight Capture-Enclosure (CE) Camera heads

2. One (1) flight-spare unit Capture-Enclosure (CE) Camera head

3. One (1) Engineering Model (EM) Capture-Enclosure Camera head

4. One (1) Electrical Ground Support Equipment (EGSE)

5. Software and algorithm tools required for converting raw image files into standard formats

6. Remove-before-flight camera covers for the flight and flight-spare Capture-Enclosure

Cameras heads

7. CE Camera Users Guide

8. CE Cameras Software Guide (may be combined with the CE Camera Users Guide if appropriate)

9. CE Camera Fault Management Plan (may be combined with the CE Camera Users Guide if appropriate).

10. CE Camera calibration report -- flight and flight-spare units only

11. CE Camera ICD

12. CE Camera Operations Manual

Hardware Deliverable Definitions

a. [VS-C-301] The flight-spare unit shall be identical to the flight models.

b.

c. [VS-C-302] The Engineering Model (EM) hardware shall match the flight versions but are not required to endure the full environmental or test program of the flight units.

Note: Specific exceptions for the EM hardware will be mutually developed between NASA and the contractor after selection in order to make the EM delivery schedule feasible.

Deliverable Schedule

[VS-C-303] The contractor shall deliver the following items to the NASA Goddard Space Flight Center, Greenbelt, Maryland in the stated timeframe after contract award

d. CE camera EM hardware within 15 months.

e. EGSE CE camera hardware and preliminary user guide within 15 months.

f. CE camera flight hardware within 21 months.

g. CE camera flight-spare hardware within 22 months.

h. CE camera items not already specified within 21 months (Update based on schedule --

- by acceptance review)

i. CE camera user guide within 21 months.

Related Documentation

The following documents, with versions current at the time of contract award, form a part of this SOW to the extent specified herein. This SOW will be considered the superseding requirement in case of conflict with any of the documents listed in this section. Other documents applicable to this SOW are delineated in the detailed MSRCCRS-VS-SPEC-0036, CCRS Camera Specification.

MSR-CCRS documentation will take precedence in the event of a conflict with any other documentation. The contractor will immediately report all such conflicts to NASA/GSFC for resolution.

j. Applicable Documents MSRCCRS-VS-SPEC-0036 CCRS Capture-Enclosure (CE) Camera Specification

ISO9001 Quality Management Systems – Requirements

MSR-CCRS-SMA-REQ-0003 MSR-CCRS Mission Assurance Requirements

MSR-CCRS-SYS-REQ-0002 CCRS Environmental Requirements Document

GSFC-STD-7000 General Environmental Standard (GEVS)

ASTM-E2900 Standard Practice for Spacecraft Hardware Thermal Vacuum

Bakeout, Method B

ANSI/ESD S20.20 ESD Association Standard for the Development of an ESD

Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment

ECSS-Q-ST-70-10 Qualification of Printed Circuit Boards.

MIL-PRF-55110 Performance Specification: Printed Wiring Board, Rigid, General Specification for

IPC-6012 Qualification and Performance Specification for Rigid Printed

Boards

MIL-STD-461 Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment

FAR Code 52 Federal Acquisition Regulation ECSS-E-ST-50-12 Spacewire – Links, Nodes, Routers, and Networks

540-PG-8700.2.1 Design of Dollies, Stands, and Spacecraft Shipping Containers

NASA-HDBK-7005 Dynamic Environmental Criteria

NASA-STD-7001 Payload Vibroacoustic Test Criteria

k. Reference Documents SAE AS9100 Quality Systems - Aerospace - Model for Quality Assurance in

Design, Development, Production, Installation and Servicing

2 GENERAL

[VS-C-304] The Contractor shall establish and maintain a configuration and data management system to assure control of the as-designed and as-built baselines of deliverable products (hardware, software, firmware) including the following:

a. Identification of all the design and product documentation that defines the deliverable product(s). Product will be uniquely marked in accordance with Section 4.2.

b. Control of all design, test procedure and product documentation, including control of changes to that documentation.

c. Controlling and reporting change implementation status of the deliverable products.

d. Correlation of the documented “as-designed” baseline with the product “as-built” baseline.

e. Develop interface control documentation with NASA/GSFC to document key interface information between the camera and the CCRS.

[VS-C-305] The contractor shall comply with NASA Procedural Requirements 7150.2, NASA Software Standard. Compliance shall be subject to oversite from the CCRS Software Systems Manager (SSM).

Traceability

[VS-C-306] The CE Camera is a serialization controlled item. Traceability shall be provided by assigning traceability identification to the CE Camera. Such identification provides the means of correlating the CE Camera to its historical records. Conversely, the records must be traceable to the CE Camera. Traceability is defined as the ability to know where a particular item part or type of material was installed during the course of assembly and to know where like items are located.

Consequently, when a component is determined to be questionable, the current location of all other members of its batch or lot can be easily determined.

Requirements Terminology and Verification Statements using “shall” are requirements. Each requirement in this document and MSRCCRS- VS-SPEC-0036, Capture-Enclosure Camera Specification will be verified by the Contractor.

[VS-C-307] At the preliminary design review (PDR), critical design review (CDR) and hardware acceptance review (HAR) the Contractor shall provide a verification matrix for all camera requirements that documents the verification type, state of compliance, performance values (when applicable) and references to supporting verification information. Note: At the PDR and CDR current best estimates (CBE) may be used in place of actual performance values for those items still in development. The final verification matrix is part of the EIDP.

Verification Methods [VS-C-308] The Contractor shall execute verification procedures in order to demonstrate compliance with each requirement.

The methods specified below define how requirements are to be verified. The code letter in parentheses is assigned for use in the verification method matrix created by the Contractor.

l. Analysis (A) Verification by analysis includes systems engineering analysis, statistical and qualitative analysis, computer and hardware simulations, stress analysis and thermal analysis. Analysis may be used if rigorous and accurate analysis is possible, testing is not cost-effective, similarity is not applicable and inspection is not adequate.

m. Test (T) Performance testing consists of electrical or mechanical tests on hardware to establish that the hardware meets design specifications. Environmental testing assures that the flight hardware will perform satisfactorily in its flight environment. Examples are vibration, acoustics, thermal vacuum and EMI/EMC.

n. Qualify by Similarity (S) Qualification testing satisfactorily completed on identical (or almost identical) unit that was manufactures, assembled, and tested using the same type parts, materials, processes and procedures. No value added for acceptance-level testing of flight units.

o. Inspection (I) Inspection may be used instead of or in conjunction with testing to verify design features. The inspection process consists of the physical verification of compliance with drawings and specifications.

3 QUALITY ASSURANCE REQUIREMENTS

Quality Assurance Program

The Contractor will maintain a product assurance program and organization to ensure that the applicable quality requirements of the subcontract are satisfied during the design, development, manufacturing, testing, and delivery phases of the subcontracted item(s).

[VS-C-309] The Contractor shall develop a quality program and documentation in accordance with the current revision of ISO9001, Quality Management Systems Requirements or an equivalent Quality Management System (with AS9100 preferred) as approved by NASA/GSFC Quality Assurance.

Contractor Performance

p. Contractor Quality System and Special Processes

a. [VS-C-310] The Contractor and any subcontractors performing Special Processes

(example: soldering, cleaning, x-ray, welding, magnetic particle, penetrant inspection, brazing, heat treating, plating, etc.) shall have Special Processes reviewed and approved by NASA/GSFC if specified in the contract quality clauses.

b. [VS-C-311] The Contractor shall implement an ESD prevention and control program for ESD sensitive components in accordance with ANSI/ESD S20.20.

q. Workmanship Standards

[VS-C-312] The Contractor shall meet the workmanship standards as defined in the MSR- CCRS-SMA-REQ-0003, MSR-CCRS Mission Assurance Requirements. Alternate workmanship standards may only be used when approved by NASA/GSFC. The contractor will submit, for review and approval, the alternate standard and the differences between the alternate standard and the required standard.

r. Printed Wiring Boards [VS-C-313] The Contractor shall comply with one of the following standards for rigid printed circuit boards:

- IPC-6012 Qualification and Performance Specification for Rigid Printed Boards, (NOTE: Revisions B and later are acceptable (Class 3/A requirements are required for Revisions B and C; IPC-6012DS and IPC-6012ES addendum is required for Revisions D and E), with a preference for D or later. IPC-6012 Revs B and C should only be used to avoid changes to pre-existing drawings. Boards that show evidence of copper wrap are acceptable without meeting the copper wrap requirements in the applicable specifications.)

- MIL-PRF-55110H Performance Specification: Printed Wiring Board, Rigid, General Specification for

- ECSS-Q-ST-70-10 Qualification of Printed Circuit Boards.

[VS-C-314] The Contractor shall provide PWB test coupons to the GSFC Materials Engineering Branch (MEB) for evaluation per the appropriate procurement specification. The specific process for test coupon submittal and notification of test results is explained in Appendix A. Appendix B contains the coupon submittal form filename.

[VS-C-315] The Contractor shall obtain coupon acceptance prior to the population of flight PWBs.

s. Ground Support Equipment (GSE) that Interface with Space Flight Hardware [VS-C-316] The Contractor shall assemble and maintain the mechanical and electrical GSE and associated software that directly interfaces with flight deliverable to the same standards as the deliverable flight items, especially calibration and configuration control. Parts and materials selection and reporting requirements are exempted as long as the deliverable item is not compromised, including contamination.

[VS-C-317] The Contractor shall design and certify the GSE shipping container following the requirements outlined in 540-PG-8700.2.1.

t. Circuit Board Trace Cuts and Jumper “White” Wires

The use of jumper wires or cut PWB traces on any flight hardware is considered a repair and as such must be limited. While no documented requirement for the maximum number of jumpers is currently stated in the NASA Workmanship Courses and Certification, it’s the position of the Planetary Science Division that repairs comprise hardware reliability. That being the case, cut PWB traces or “white”/ jumper wires requires approval via MRB written by the Contractor and approved by NASA/GSFC prior to acceptance by the project.

u. Training and Certification

[VS-C-318] The Contractor shall train and certify the manufacturing, inspection, and test personnel working on the program. Certification of personnel for special processes and critical processes will be implemented formally and will include demonstration of proficiency. This activity includes the definition of responsibilities and establishing policies for training, certification, and recertification.

Customer Inspection and Acceptance

[VS-C-319] The Contractor shall notify NASA/GSFC at least 48 hours prior to reaching Customer Source Inspection Mandatory Inspection Points (MIP) which will be determined by NASA/GSFC QA before manufacturing of flight hardware.

Records [VS-C-320] In addition to records specified in End Item Data Packages (EIDP), the Contractor shall maintain records of all technical data and documentation (including ASIC and FPGAs at all tiers) developed and acquired for the design and manufacture of their product to support troubleshooting and repair for a period of ten years after completion of the effort specified in the contract. Design tools (including revision status) and the computing environment upon which the tools were used to develop the design will be recorded as a part of the design files.

Unverified Failure Processes

[VS-C-321] The Contractor shall have a written process for documenting and dispositioning hardware/software that has experienced an unverified failure (UVF).

Note: An UVF is any failure for which, at the conclusion of the investigation, a root cause has not been determined.

[VS-C-322] The Contractor shall coordinate the disposition of all UVFs with NASA/GSFC. In most cases, UVFs with significant mission impact require a Worst Case Change-Out (WCCO) performed on all suspect hardware and software to minimize mission risk. Exceptions to a WCCO for significant mission impacts require the consent of the UVF Review Team. UVFs with insignificant or no mission impact may be dispositioned with less than a complete WCCO accompanied by some repair, rework, or use-as-is dispositions.

Software

v. Software Development [VS-C-323] NASA/GSFC Quality Personnel and the Software Systems Manager (SSM) shall be involved in software related milestone reviews as defined by NPR 7150.2 and all FPGA reviews.

w. Ground Processing Algorithms and Tools [VS-C-324] The Contractor shall provide algorithms and/or tools for viewing image data which are developed in compliance of NPR 7150.2.

Milestone Reviews

[VS-C-325] NASA/GSFC Safety and Mission Assurance team shall be invited to all milestone reviews, such as: Manufacturing Readiness Review (MRR), Test Readiness Review (TRR), etc.

4 TRANSPORTATION, HANDLING, PACKING, PACKAGING AND

SHIPPING REQUIREMENTS

Transportation and Handling [VS-C-326] The Contractor shall emphasize protection during all critical hardware handling and transportation.

Shipping Containers

[VS-C-327] The Contractor shall make provisions to assure all shipping containers are capable of protecting the hardware during all phases of transportation and handling.

[VS-C-328] The Contractor’s shipping containers shall have all the required markings and labels and contain any provisions necessary for handling (e.g., forklift sleeves, lifting points, handles, ESD, etc).

[VS-C-329] The Contractor shall label each unit container and tag or mark to show the item name, part number, serial number, contract number, manufacturer’s cage code, and quantity.

Packing and Packaging

[VS-C-330] The Contractor shall be responsible for packing and packaging deliverable hardware such that performance life or cleanliness is not degraded.

[VS-C-331] The Contractor shall deliver each flight unit packaged in its NASA/GSFC approved shipping container.

[VS-C-332] The Contractor shall use electrical connector ESD dust caps and deliver them on all electrical connectors.

Hand Carry

Flight units may be hand carried by the NASA/GSFC representative.

[VS-C-333] Handling instructions shall be provided by the contractor and approved by NASA/GSFC prior to shipment.

[VS-C-334] The Contractor shall be responsible for packing deliverable hardware such that performance, life, or cleanliness is not degraded by the transportation process.

[VS-C-335] Shipping containers shall be provided by the Contractor and not returned to the Contractor unless specifically requested by the Contractor.

Humidity Monitors [VS-C-336] The Contractor shall include humidity monitors in the flight shipping containers at locations agreed upon with NASA.

Shock Monitors [VS-C-337] The Contractor shall include shock monitors with +5.0G sensitivity in all hardware deliverable shipping containers.

5 TECHNICAL MANAGEMENT, TESTS AND PROCESSES

Performance Calibration

x. [VS-C-338] The Contractor shall calibrate and characterize the flight and flight-spare cameras for:

y. Absolute response in photometric units, accurate to ±10%

z. System spectral bandpass

aa. Linearity and full-well

bb. Dark current at the minimum, maximum and typical operational temperatures

cc. Flat-field response with relative accuracy from pixel-to-pixel of 5% or better

dd. Geometric scene transformation including on-axis focal length and optical distortion, accurate to 1 pixel or better

ee. Stray light, consistent with the in-field and out-of-field stray light requirements specified in the MSRCCRS-VS-SPEC-00036, CCRS CE Camera Specification.

ff. Modulation Transfer Function (MTF)

gg. Geometric scene stability over temperature

hh. Gain and read noise

ii. Hot/dead pixel identification

jj. Camera boresight with respect to an external alignment reference

kk. [VS-C-339] The Contractor shall document the flight and flight-spare camera calibration and performance characterization results and relevant test uncertainties in a calibration report.

ll. [VS-C-340] The Contractor shall readout and save all flight and flight-spare camera calibration images such that they include all reference and dark pixel responses available on the detector array.

mm. [VS-C-341] The Contractor shall deliver all the flight and flight-spare camera calibration images to NASA/GSFC as part of the calibration report.

nn. [VS-C-342] The Contractor shall support a Spacewire interface test mutually coordinated with NASA/GSFC per ECSS-E-ST-50-12, Spacewire – Links, Nodes, Routers, and Networks.

Technical Considerations

oo. [VS-C-343] The Contractor shall provide any unique mechanical ground support equipment (GSE) required to operate or hold the CE camera prior to CE integration.

pp. [VS-C-344] The Contractor shall use metric units when interfacing with NASA/GSFC including any drawings, documents, models, except for the following cases:

- Heritage Component: Component that has been previously qualified, or of similar design heritage, may be specified in English units where use of metric equivalents would lead to additional cost to the program.

- Fasteners: Although bolt patterns will be defined using metric dimensioning, use of English fasteners (with hole dimensioning and tolerancing) is permitted.

- Angular Measurement: Angular measurement may be expressed in degree of arc or in an appropriate subdivision of degree of arc such as second of arc (arc-sec) when advantageous to application.

qq. [VS-C-345] The Contractor shall define the center of mass of each component of the Camera for the interface control documentation.

rr. [VS-C-346] The Contractor shall determine the center of mass of each camera to within ± 3.0 mm relative to an external reference.

ss. [VS-C-347] The Contractor shall calculate the final moments and products of inertia of the cameras to within 10%.

tt. [VS-C-348] The Contractor shall document the nominal CE camera fields of view for the interface control documentation.

uu. [VS-C-349] The Contractor shall measure the camera boresight to a fixed reference or feature on the camera body before and after environmental testing to document its stability.

vv. [VS-C-350] The Contractor shall design the CE camera to meet its performance requirements when subjected to the environments outlined in MSR-CCRS-SYS-REQ- 0002, CCRS Environmental Requirements Document.

Electromagnetic Interface/Electromagnetic compatibility

ww. [VS-C-351] The contractor shall execute an EMI test program including the following tests at a minimum: CE101, CE102, CS114, RE101, RE102, RS101, and RS102. The tests methods are defined in GSFC-STD-7000, General Environmental Standard (GEVS) and MIL-STD-461, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment. With the test levels tailored per the unit specification. In addition to the standard tests Common mode bulk emissions will be measured on both the power lines and signal lines for reference.

xx. [VS-C-352] The contractor shall submit a detailed EMI test plan for review.

yy. [VS-C-353] The contractor shall submit the EMI test procedure for review and approval 30 days prior to the EMI test.

Vibration

zz. [VS-C-354] Prior to any random vibration testing, the Contractor shall perform a survey of the test fixture/exciter combination to evaluate fixture dynamics and the proposed choice of control accelerometers.

aaa. [VS-C-355] The Contractor shall subject the camera to random vibration testing along three orthogonal axes as specified in the MSRCCRS-VS-SPEC-0036, CCRS CE Camera Specification.

bbb. [VS-C-356] When random vibration testing is conducted, the Contractor shall mount the test item to the test fixture as it would be mounted to CE. Note: this requirement includes the component harness.

ccc. [VS-C-357] The Contractor shall perform a functional test before the start of random vibration testing and after a test in each axis.

ddd. [VS-C-358] The Contractor shall perform random vibration testing of CE camera components for 1 minute per axis to Protoflight test levels as specified in Table 1 per GSFC-STD-7000, General Environmental Standard (GEVS) using limit levels provided in the MSRCCRS-VS-SPEC-0036, CCRS CE Camera Specification.

Table 1. Random Vibration Test Specifications eee. [VS-C-359] The Contractor shall provide random vibration analysis along with static loads analysis.

Note: See NASA-HDBK-7005, Dynamic Environmental Criteria and NASA-STD-7001, Payload Vibroacoustic Test Criteria for more information.

fff. [VS-C-360] If necessary, the Contractor shall reduce (notch) random vibration test input levels up to -12 dB of the original input and to a bandwidth of >100 Hz at critical frequencies to limit the random vibration loads and/or acceleration responses to 3 dB above design limit levels.

ggg. Note: Notching above these limits will require NASA/GSFC COR approval.

hhh. [VS-C-361] The Contractor shall complete a shock susceptibility and attenuation assessment on all CE components assuming Table 2 shock levels and GSFC provided attenuation assumptions.

Table 2. Qualification Level Shock Response Spectrum (Q=10)

Frequency (Hz) Acceptance Level (g) Protoflight/Qualification (g) 100 160 224 630 1000 1400

10000 1000 1400

Thermal

iii. [VS-C-362] The Contractor shall provide calibration information to convert camera internal temperature sensor signals into temperature units.

jjj. [VS-C-363] The Contractor shall test camera performance at proto-flight test levels ranging from -40° to +55° C.

Thermal Vacuum Test Requirements kkk. [VS-C-364] The Contractor shall vacuum bake the camera at the highest permissible temperature up to 50°C, until an outgassing stability of <1%/hour is achieved for an average of 6 hours when monitored with a quartz crystal microbalance (QCM) at -2040° C per ASTM-E2900, Standard Practice for Spacecraft Hardware Thermal Vacuum Bakeout, Method B.

lll. [VS-C-365] The Contractor shall thermal vacuum cycle test each flight and flight-spare CE camera component to proto-flight operational and survival temperatures a total of eight (8) times per Figure 1 while maintaining a chamber pressure less than 1.33x10-3 Pa (1x10-5 Torr).

Figure 1. Representative Thermal Vacuum Test Profile

NOTE: (1=Achieve survival temperature, stabilize for 1 hour, return to QUAL temperature, turn on unit under test, soak at test temperature for 4 hours, run functional test; 2=Soak at test temperature for 4 hours, run functional test at minimum operating voltage; 3=Soak at test temperature for 4 hours, run functional test at nominal operating voltage; 4=Soak at test temperature for 4 hours, run functional test at maximum operating voltage; 5 = Bake out phase) mmm. [VS-C-366] For the first two thermal vacuum test cycles the Contractor shall:

a. During the transition from cold to warm, switch component OFF, increase temperature to survival temperature for 1 hour, then return to qualification temperature, verify that component turns ON, and verify nominal performance once the component has reached the qualification temperature. Begin four hour hot soak.

b. During the transition from warm to cold, switch component OFF, decrease temperature to survival temp for 1 hour, then return to qualification temperature, verify that component turns ON, and verify nominal performance once the component has warmed to the qualification temperature. Begin four hour cold soak.

nnn. [VS-C-367] For thermal vacuum test cycles 3-8 the Contractor shall:

a. During the transition from cold to warm, switch the component OFF, increase temperature to the hot operational temperature, verify that component turns ON, stabilize temperature, then begin four-hour hot soak. At the completion of the soak, verify nominal performance of the component.

b. During the transition from warm to cold, switch the component OFF, decrease temperature to the cold operational temperature, verify that component turns ON, stabilize temperature, then begin four-hour cold soak. At the completion of the soak, verify nominal performance of the component.

Qual Limit

1 1 2 3 4 3 3 3 3

1 3 3 3 4 3 2 1

Qual Limit

Survival Limit

Survival Limit ooo.

ppp. [VS-C-368] The Contractor shall execute the thermal vacuum cycle test at temperature transition rates of 1° C/min or less to mitigate contamination risks.

Rationale: Transitions from cold to hot conditions increase contamination hazards because material that has accreted on the chamber walls may evaporate and deposit on the relatively cool test item. Minimizing the temperature transition rates reduces the likelihood of this occurring.

qqq. [VS-C-369] The Contractor shall begin and end the thermal vacuum test with a hot soak to minimize contamination risk.

rrr. [VS-C-370] Test chamber walls shall not exceed subsequent hot soak temperatures by more than 10° C.

sss. [VS-C-371] The Contractor shall verify component minimum, maximum and nominal voltages at the minimum and maximum temperatures.

ttt. [VS-C-372] The Contractor shall verify electrical system functionality at minimum, maximum and nominal voltages during temperature transitions.

Software Development Requirements uuu. [VS-C-373] If camera contains FPGA, the contractor shall provide review and data package and FPGA Development Requirements Prior to CDR, the Contractor shall hold an FPGA review.

vvv. [VS-C-374] The Contractor shall provide an FPGA data package.

[VS-C-375] All software delivered shall be in compliance of NPR 7150.2.

Contamination Control www. Cleanliness and Foreign Object Debris (FOD) [VS-C-376] The Contractor shall have a documented cleanliness and foreign object debris (FOD) control and monitoring program.

xxx. Shipping Contamination Control [VS-C-377] The Contractor shall package and ship the camera double-bagged in cleanroom compatible film such that the MSRCCRS-VS-SPEC-0036, CCRS CE Camera Specification particulate and molecular contamination requirements are met upon delivery.

yyy. Unacceptable Shipping Material [VS-C-378] The Contractor shall not package and ship the camera in clear pink polyethylene (pink poly) electrostatic discharge (ESD) material.

Scheduled Communications and Reviews zzz. [VS-C-379] Within 30 days of contract award, the Contractor shall hold a one-day

Project Kick-Off meeting with NASA/GSFC representatives.

aaaa. [VS-C-380] After the initial Project Kick-Off meeting, the Contractor shall hold one-hour, weekly status teleconferences with NASA/GSFC representatives as requested to report on project status, schedule and close open actions.

bbbb. [VS-C-381] The Contractor shall provide NASA with monthly schedule updates for key project milestones.

cccc. [VS-C-382] The Contractor shall hold a Preliminary Design Review (PDR) for NASA/GSFC representatives to review the CE camera preliminary design.

dddd. Note: If the design is suitably mature, a joint PDR/CDR review may be held in lieu of separate PDRs and CDRs.

[VS-C-383] If software is being delivered, then at or prior to the PDR, the Contractor shall hold a CE camera software review with NASA/GSFC representatives in compliance with

NPR 7150.2.

eeee.

ffff. [VS-C-384] The Contractor shall hold a Critical Design Review (CDR) for

NASA/GSFC representatives to review the CE camera final design gggg. Note: If the design is suitably mature, a joint PDR/CDR review may be held in lieu of separate PDRs and CDRs.

[VS-C-385] If software is being delivered, then at or prior to the CDR, the Contractor shall hold a CE camera software review with NASA/GSFC representatives in compliance with

NPR 7150.2.

hhhh.

iiii. [VS-C-386] The Contractor shall hold a Manufacturing Readiness Review (MRR) with

NASA/GSFC representatives prior to the start of final construction of the CE camera flight and flight-spare components.

jjjj. [VS-C-387] Prior to the flight and flight-spare CE camera component delivery the

Contractor shall hold a Pre-Ship or Hardware Acceptance Review with NASA/GSFC representatives.

[VS-C-388] If software is being delivered, then prior to the flight and flight-spare CE camera component delivery the Contractor shall hold a final CE camera software acceptance review with NASA/GSFC representatives in compliance with NPR 7150.2.

kkkk.

Post-Delivery Support llll. [VS-C-389] The Contractor shall support in-person checkouts of hardware deliveries to NASA/GSFC.

Note: These checkouts would last five 8-hour workday or less.

mmmm. [VS-C-390] The Contractor shall provide in-person support for the initial integration of the CE camera flight components into the CE hardware.

Note: This in-person support would last five 8-hour workday or less.

nnnn. [VS-C-391] The Contractor shall provide in-person support of CE delivery to the European Space Agency.

Note: This in-person support would last five 8-hour workdays or less.

oooo. [VS-C-392] The Contractor shall provide final pre-launch cleaning of the CE camera flight cameras.

6 DATA DELIVERABLES

[VS-C-393] The Contractor shall submit the following Subcontractor Data Requirements List (SDRL). The following table lists the SDRLs to be delivered during the period of performance of the contract. Additional data descriptions follow the table. The formats and drawing standards used will be those normally used by the Contractor unless specified otherwise.

All markings on data delivered must be in accordance with Federal Acquisition Regulation (FAR) 52.227-14 Rights In Data – General (MAY 2014)—Alternate II (DEC 2007) And Alternate III (DEC 2007) As Modified by NASA Far Supplement 1852.227-14 (APR 2015).

Further, if the data delivered was first developed under this contract, then no marking shall be placed on the delivered item.

Documents Requiring Approval [VS-C-394] NASA/GSFC’s approval is required on SDRL items as indicated in the following table of this statement of work. NASA/GSFC shall have thirty (30) working days to review, comment, and provide approval. Approval/disapproval and comments will be contractually communicated through the NASA/GSFC Contract Administrator. Necessary updates are to be incorporated into the updated deliverable and re-submitted to NASA/GSFC within thirty (30) working days of receipt of comments. It is recommended that SDRLs be pre-coordinated with NASA/GSFC prior to formal submittal to minimize any iterations. Lack of a response to SDRL’s from NASA/GSFC does not constitute approval.

Data Required [VS-C-395] The Contractor shall submit all data deliverables to NASA/GSFC by placing the applicable documentation into the designated large file transfer site. NASA/GSFC’s disposition of all SDRLs submitted will be communicated via a consolidated tracking worksheet managed by the NASA/GSFC Contract Administrator.

Required SDRLs The SDRLs and their delivery dates are summarized below in Table 1. All software delivered by the vendor will be developed in accordance to a Software Development Plan (SW01) which provides details on NPR 7150.2 compliance and shall be concurred with by the CCRS SSM prior to Camera PDR.

Once the build plan is defined, then SDRL table will be expanded to provide details on all required deliverables for each build.

Deliver dates are tied the following program milestones:

Contractor Milestones PDR – Preliminary Design Review CDR – Critical Design Review MRR – Manufacturing Readiness Review HAR – Hardware Acceptance Review EIDP – End Item Data Package

Table 3. Required SDRLs

SDRL # SDRL Title

Delivery Date

(PDR/CDR references pertain to the Contractor’s PDR/CDR)

NASA/GSFC

Approval

Required (Yes/No)

E01 Engineering Drawings Draft 2 months after contract start, update as required, final in EIDP

Yes

E02 Interface Control Document (ICD) Draft 2 months after contract start, update as required, final - MRR

Yes

E19a Structural Model (FEM) & Description Document (if < 100 Hz)

Draft 2 months after contract start; Final due 30 days prior to CDR. Updates within 30 days of changes.

Yes

E19b CAD/Solid Model Draft 2 months after contract start; Final due 30 days prior to CDR. Updates within 30 days of changes.

Yes

H01 Preliminary Design Review (PDR) Data Package

2 weeks prior to PDR. Results of PDR and any RFAs to be provided to NASA/GSFC within 2 weeks following PDR.

Yes

H01a FPGA Peer Review Data Package Due at least one week prior to FPGA Peer Review

Yes

H02 Critical Design Review (CDR) Data Package

2 weeks prior to CDR. Results of CDR and any RFAs to be provided to NASA/GSFC within 2 weeks following CDR.

Yes

H03 Hardware End Item Acceptance Data Package (EIDP)

2 weeks prior to Hardware Acceptance Review (HAR)

Yes

H04a Materials Usage Agreement

(MUA)

2 months after contract start. Revised MUAs within 30 days of identification.

Yes

H05a Materials Identification and Usage List (MIUL)

Prelim. 2 months after contract start Final 30 days prior to CDR Updates 30 days after identification.

Yes

H05b Electronic Parts List

Preliminary Design List within 1 month of ATP, As Designed List – Monthly updates until MRR minus 1 Month, As Built List prior to hardware delivery and included in EIDP.

Yes

H05c Printed Wiring Board Test Coupons

As soon as practicable for analysis of the printed wiring boards for approval. Approval required prior to population of flight PWBs.

Yes

H08a Failure Modes & Effects Analysis

(FMEA)

Initial 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

SDRL # SDRL Title

Delivery Date

(PDR/CDR references pertain to the Contractor’s PDR/CDR)

NASA/GSFC

Approval

Required (Yes/No)

H08b Worst Case Analysis Initial 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

H08c Structural Analysis Draft 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

H08d Thermal Analysis Draft 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

TH01 Thermal Model Draft 2 months after contract start; Final due 30 days prior to CDR Updates within 30 days of changes.

Yes

RVM01 Requirement Verification Matrix Preliminary status at PDR, CDR, and HAR Final with EIDP

Yes

EM01 EMI/EMC Test Plan Draft at PDR, Final at CDR Yes EM02 EMI/EMC Test Procedure 30 days prior to EMI/EMC test Yes EM03 EMI/EMC Test Report Final at HAR Yes TH02 TVAC Test Report Final at HAR Yes VIB01 Vibration Test Report Final at HAR Yes

H10a EEE Parts Stress Analysis Initial 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

H10b Reliability Assessment and Predictions

Initial 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

H10c Limited-Life Item List Initial 2 months after contract start; Final due 30 days prior to CDR, Updates within 30 days of changes.

Yes

Appendix A Applicable MAR

MAR

paragraph

DID Brief Statement on Tailoring of MAR

1.1 DID 1-1 Mission Assurance Compliance Matrix (per the applicable requirements in this table)

1.2 Provide Org chart

1.3 Applicable to contractor (Requirement Flowdown)

1.4 Applicable to contractor (Suspension of Work Activities)

1.5 Applicable to contractor (Quality Assurance Surveillance)

1.6 Applicable to contractor (GMIPS)

1.7 DID 1-2 Applicable to contractor (ASL)

1.8 DID 1-3 NA if contractor does not use Inherited Products/Items, otherwise, applicable.

2.1 Applicable to contractor (QMS, General)

2.2 (2.2.1;

2.2.2; 2.2.3;

2.2.4)

DID 2-1;

DID 2-2

Applicable to contractor (Supplemental Quality Management System Requirements)

2.3 DID 2-3 NA to contractor (Orbital Debris Assessment Report (ODAR) and End of Mission Plan (EOMP)

3 Header

3.1 General (Not applicable to contractor)

3.2 NA to contractor (Mission Related Safety Requirements

Documentation)

3.3 Header

3.3.1 DID 3-1 NA to contractor (System Safety Program Plan)

3.3.2 DID 3-2 NA to contractor (Safety Requirements Compliance

Checklist)

3.3.3 HA Header

3.3.3.1 PHA AR via

FSW

request

NA to contractor (Preliminary Hazard Analysis)

3.3.3.2 OHA DID 3-3 NA to contractor (Operations Hazard Analysis (OHA) and Hazard Verification Tracking Log (HVTL))

3.3.3.3 LDE AR NA to contractor (Lifting Device Safety Requirements) 3.3.3.4

O&SHA

Not used

3.3.4 ISAR DID 3-4 NA to contractor

3.3.5 ISAR-

VTL

Not used

3.3.6 Haz Procs DID 3-5 NA to contractor

3.3.7 Waivers AR NA to contractor

3.3.8 Mishap AR NA to contractor

3.3.9 ELV

Forms

Not used

4.1 DID 4-1 Applicable to contractor (Reliability Requirements)

4.2 NA to contractor (Reliability Program Plan, RPP)

4.3 DID 4-2 NA to contractor (Probabilistic Risk Assessment (PRA)

4.4 DID 4-3 Applicable to contractor (FMEA, Critical Item List, CIL)

4.5 NA to contractor (Fault Tree Analysis)

4.6 DID 4-5 Applicable to contractor (Parts Stress Analysis)

4.7 DID 4-6 Applicable to contractor (Worst Case Analysis)

4.8 DID 4-7 Applicable to contractor (Reliability Assessment and

Predictions)

4.9 DID 12-1 Applicable to contractor (Trend Analysis)

4.10 Applicable to contractor (Analysis of Test Results)

4.11 DID 4-8 Applicable to contractor (Limited Life Items)

4.12 Applicable to contractor (Single Point Failures)

5 (Software Assurance)

This SOW overwrites the software assurance requirement in the MAR.

(Workmanship)

DID 6-1,

DID 6-2,

DID 6-3,

DID 6-4,

DID 6-6,

DID 6-7

All applicable to the contractor.

7 (EEE parts) DID 7-1, DID 7-2

All applicable to the contractor.

8 Header 8.1, General (M&P)

Vendor to provide a list of material being used to GSFC Material Engineer for review. GSFC material engineer will help provide feedback if the selected material meets this requirement.

8.2 DID 8-2 Applicable to contractor (MUA)

8.3 DID 8-3 Applicable to contractor (MIUL)

8.4 DID 8-4 Applicable to contractor (Life Test Plan, Lubricated

Mechanism) 9 Header

9.1 DID 9-1 Applicable to contractor (Contamination Control Plan) 9.1.A Not Applicable to the vendor (Planetary Protection)

9.2 DID 8-3 Applicable to contractor (Outgassing)

9.3 DID 9-2 Applicable to the vendor (Foreign Object Debris Program) 10 (All sections)

Metrology, All sections applicable to contractor

11 GIDEP, all sections applicable to contractor

12 DID 12-1 Applicable to the vendor (accepting vendor format as long as all contents are included).

Appendix B Abbreviations and Acronyms

ATLO Assembly, Test and Launch Operations ATP Authorization to Proceed C&DH Command & Data Handling CDR Critical Design Review CE Capture Enclosure CMN Common Mode Noise CCRS Capture, Containment and Return System CSUS Conducted Susceptibility DDD Displacement Damage Dose DPC Discrete Power Controller ECC Error Correction Code EDAC Error Detection and Correction EEE Electrical, Electronic and Electromechanical EGSE Electrical Ground Support Equipment EIDP End Item Data Package ELDRS Enhanced Low Dose Rate Sensitivity EM Engineering Model EMI/EMC Electromagnetic Interface/Electromagnetic compatibility FAR Federal Acquisition Regulation FOV Field of View FPGA Field Programable Gate Array FSW Flight Software GSFC Goddard Space Flight Center GSE Ground Support Equipment HAR Hardware Acceptance Review ICD Interface Control Document IDP Instrument Dependent protocol IP Internet Protocol ITAR International Trade in Arms Regulation LET Linear Energy Transfer MORR Mission Operations Readiness Review MPP Manufacturing Process Plans MRR Manufacturing Readiness Review NASA National Aeronautical and Space Administration NPR NASA Procedural Requirements NSPAR Non-Standard Part Approval Request OS Orbiting Sample PDR Preliminary Design Review PF Protoflight PS Pyrotechnic Shock RDM Radiation design Margin RE Radiated Emissions RF Radio Frequency

RS Radiated Susceptibility RV Random Vibration SBU Sensitive But Unclassified SEU Single Event Upsets SIR Software Integration Review SMRF Structural Mechanical Reference Frame SOW Statement of Work SP Science Protocol SwCDR Software Critical Design Review SwPDR Software Preliminary Design Review SwRR Software Requirements Review MORR Mission Operations Readiness Review TBD To Be Determined TBS To Be Scheduled TID Total Ionizing Dose TVAC Thermal Vacuum UDP User Datagram Protocol WCCO Worst Case Change-Out

Milestone Reviews