Attachment J-1 MAV IMU PWS 08 April 2021.pdf.pdf

MSFC Contract No. TBD Attachment J-1, PWS

J-1-1

Performance Work Statement

For

Mars Ascent Vehicle Inertial Measurement Unit

1 BACKGROUND AND SCOPE

This Performance Work Statement supports the development for the acquisition, testing, and manufacturing of an Inertial Measurement Unit (IMU) to support the Mars Ascent Vehicle (MAV).

The National Aeronautics and Space Administration (NASA) George C. Marshall Space Flight Center (MSFC) is pursuing procurement of an Inertial Measurement Unit (IMU) for a Mars Ascent Vehicle (MAV). As a part of the Mars Sample Return Campaign, the MAV will transport Mars regolith samples from the Martian surface into orbit for rendezvous with an awaiting spacecraft. Because the IMU will be used to propagate the launch vehicle attitude and support vehicle guidance during the ascent from Mars surface, the IMU will be considered a mission critical sensor assembly. Consequently, the IMU must provide uninterrupted measurement data (for a continuous period of up to eight hours) and offer high reliability and robustness against adverse space environments.

Additionally, the Mars Sample Return campaign will be classified as a NASA flagship mission, and therefore warrants critical sensor assemblies (such as the IMU) that are already space-qualified or can be space qualified through a judicious selection of high reliability and traceability of parts, qualified processes, and appropriate test campaigns in the desired timeframe.

The MAV is a two-stage vehicle and will require at least one IMU. Each IMU will be an integrated three-axis unit sensing both angular rates as well as linear accelerations about each axis. The IMU will be capable of meeting all the performance requirements after a minimum period of eight (8) years post-delivery. After a brief storage period and integration to the vehicle, the IMU would be required to tolerate environments of Earth launch, 2.5 years of deep space cruise, Entry, Descent, and Landing (EDL), and a storage period of up to two (2) years on the Martian surface. The IMU will be used for pre-flight gyrocompassing on the surface of Mars to obtain an accurate initial attitude solution. It can be assumed that there would be no external resources for in-flight or Martian surface recalibrations of the IMU. Note that the IMU will be in an unpowered state for a majority of the cruise except for short durations during health check-outs at survival temperature. The Contractor will be responsible for the design, development, manufacture, testing, qualification and delivery of a fully calibrated IMU assembly and subsequent flight, flight spare, and any flight test units as needed.

2 DOCUMENTS

2.1 Order of Precedence

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

J-1-3

3.2 Reviews

The Contractor shall conduct the following reviews. The Contractor shall provide the review package, including any presentations, to NASA/MSFC two weeks prior to each review, and provide presentation updates and review notes to NASA/MSFC within two week after each review.

Kick-Off Meeting

The Contractor shall conduct a kick-off meeting to review requirements, Contractor program and organization, design implementation, proposed milestones, and deliverables within three weeks of the contract award.

Preliminary Design Review

The Contractor shall conduct a preliminary design review (PDR) meeting sharing information ensuring both the Contractor and NASA/MSFC are in agreement on the baseline IMU design, configuration, specifications, modifications, etc.. This meeting will also cover Electrical, Electronic, and Electromechanical (EEE) parts and material usage. This meeting shall take place no later than three months after kickoff meeting.

Critical Design Review

The Contractor shall conduct a critical design review (CDR) meeting sharing information ensuring both the Contractor and NASA/MSFC are in agreement on the final IMU design, configuration, specifications, modifications, etc.., and share information on the end result of qualification testing. This meeting shall take place no later than one month after qualification testing is complete.

Manufacturing Readiness Review

The Contractor shall conduct a manufacturing readiness review (MRR) meeting sharing information ensuring both the Contractor and NASA/MSFC are in agreement regarding quality standards, parts, cleanliness, and personnel prior to IMU manufacturing. This meeting shall take place before manufacturing commences.

Test Readiness Review

The Contractor shall conduct a test readiness review (TRR) meeting sharing information ensuring both the Contractor and NASA/MSFC are in agreement regarding test plans, verification, and quality assurance topics prior to IMU testing.

Unit Delivery Review

The Contractor shall conduct a unit delivery review meeting sharing information on the end result of acceptance testing before delivery of the unit to NASA/MSFC. This meeting shall take place no later than one month before the hardware is delivered.

Other Reviews and Support

The Contractor shall plan to support the following reviews.

J-1-4

3.2.5.1 Technical Interchange Meeting (TIM)

At least three (3) informal, face-to-face technical interchange meetings to be held at the Contractor’s facilities if required. These TIMs shall support review and coordination of technical issues including, but not limited to, parts, test plans, test procedures, software changes, design modifications, and design analyses.

3.2.5.2 On Call Support

The Contractor shall provide engineering support on an as needed basis after hardware delivery and throughout the period of performance as defined in the PWS.

3.3 Management, Reporting, and Documentation

Program Management

The Contractor shall designate a single individual who will be given full responsibility and authority to manage and administer all phases of the work specified by the contract and ensure that all objectives are accomplished within schedule constraints. Additionally, the Contractor shall designate and identify by name a single individual to serve as a point of contact with the NASA/MSFC Contracting Officer (CO) and Contracting Officer’s Representative (COR) for all aspects of the IMU contract.

Reporting

3.3.2.1 Regular Status Meetings

The Contractor shall prepare and present to NASA/MSFC ~30-minute biweekly technical status reports via telecon which shall include a quad chart. The purpose of the status meetings is to inform NASA/MSFC of progress on topics such as schedule, accomplishments, technical performance measures, status of key milestones, risks, problem areas, challenges/issues, quality assurance issues/statuses, and activities on-going and planned. The Contractor can add additional slides if required. The contractor shall provide the quad chart and any additional slides as a deliverable 24 hours prior to the telecon.

3.3.2.2 Issue Reporting

The Contractor shall maintain communication with the NASA/MSFC CO and COR. The Contractor shall notify the NASA/MSFC CO and COR immediately of any problems that would prevent meeting established milestones.

3.3.2.3 Financial Management Report

The Contractor shall provide a Financial Management Report deliverable in accordance with Appendix F. An initial report in the 533Q format is required within 30 working days after contract award. Initial 533M reporting shall begin no later than 10 days following the close of the contractor’s accounting period after initial incurrence of cost.

Documentation

3.3.3.1 Performance Specification

The Contractor shall provide a performance specification deliverable that includes expected IMU errors to support construction of a NASA/MSFC computer model of the IMU. Initial deliverable shall be submitted with proposal, if not already covered by addressing requirements. Baseline deliverable shall be no later than three weeks before PDR, and updates as required.

J-1-5

3.3.3.2 Mechanical Interface Control Document

The Contractor shall provide a Mechanical Interface Control Document (MICD) deliverable, including physical characteristics, mounting interface, and outline drawing in accordance with Appendix B. Initial delivery shall be no later than three weeks before PDR.

3.3.3.3 Electrical Interface Control Document

The Contractor shall provide an Electrical Interface Control Document (EICD) deliverable, including connector identification, connector pinouts, detailed description of each signal, interface circuits, command description, command sequencing/timing, and data description in accordance with Appendix B. Initial delivery shall be no later than three weeks before PDR.

3.3.3.4 Data Interface Control Document

The Contractor shall provide a Data Interface Control Document (DICD) deliverable, including sequencing/timing and data (telemetry) description in accordance with Appendix B. Initial delivery shall be no later than three weeks before PDR. This delivery may be a part of the EICD or a standalone document.

3.3.3.5 Computer Models

The Contractor shall provide a mechanical computer-aided design (CAD) deliverable in STEP-file format including accurate representation of all mechanical assembly interfaces, mass properties, and dimensions in adherence to Appendix B. Initial delivery shall be no later than three weeks before PDR. This does not need to include detailed models of hardware internal to the IMU.

3.3.3.6 User Instruction / Manuals

The Contractor shall deliver procedures that describe the operation of the unit and any operational constraints to the unit as a deliverable. Initial delivery shall be no later than three weeks before PDR, and the Contractor shall update at major reviews and as needed. This delivery may be a part of the EICD or a standalone document.

Contractor format is acceptable.

3.3.3.7 Verification Data

Verification tests shall demonstrate the item meets all of the specified performance requirements over the specified range of environments, measure performance parameters and reveal inadequacies in manufacturing and assembly such as workmanship or material problems. Any requirement that exceeds previous qualification test data shall be presented to the NASA/MSFC COR as part of the planning process for evaluation and a possible delta qualification test.

Verification data shall include the following:

• Verification compliance assessment deliverable shall be in accordance with Appendix I.

• Verification procedures deliverable shall be in accordance with Appendix I.

• Verification reports data deliverable shall be in accordance with Appendix I.

• Verification requirements data deliverable shall be in accordance with Appendix I.

• Verification success criteria data deliverable shall be in accordance with Appendix I.

J-1-6

3.3.3.8 Qualification Data

The Contractor shall provide a Qualification Data Package deliverable no later than two weeks prior to CDR.

This data package shall include the information as specified in Appendix A along with verification data of all requirements associated with qualification.

3.3.3.9 Acceptance Data

The Contractor shall provide an Acceptance Data Package (ADP) deliverable as specified in Appendix A no later than two weeks prior to Delivery Review.

3.3.3.10 Material Identification and Usage List

The Contractor shall provide evidence of compliance of the MAV IMU with the intent of the applicable technical requirements of NASA-STD-6016, the MAV Materials and Processes Selection, Control, and Implementation Plan, or the Contractor Materials Control Documentation. Verification/Evidence shall consist of the following as a minimum:

a) NASA review and approval of the Contractor’s documentation used to control materials and processes.

b) Contractor Materials & Processes (M&P) signature on engineering drawings, and/or Contractor procedures/evaluation ensuring that all vendor-designed, Commercial-Off-The-Shelf (COTS), and supplier-furnished items comply with M&P requirements, including safety of flight concerns such as flammability and vacuum off-gassing.

c) NASA approval of Material Usage Agreements (MUAs) deliverable as specified in Appendix E. Initial submission shall be no later than two weeks prior to PDR.

d) NASA approval of a Material Identification and Usage List (MIUL) deliverable as specified in Appendix G. Initial submission shall be no later than two weeks prior to PDR.

e) Contractor compliance with the MAV Planetary Protection Implementation, Contamination Control, Electrostatic Discharge Control, and Foreign Object Debris (FOD) Prevention Plan (MAV-011).

3.3.3.11 EEE Parts Lists

3.3.3.11.1 As Designed

The Contractor shall provide an as-designed EEE parts list deliverable as specified in Appendix D. Initial submission shall be no later than two weeks prior to PDR

3.3.3.11.2 As Built

The Contractor shall provide an as-built EEE parts list deliverable as specified in Appendix C . Initial submission shall be no later than two weeks prior to Delivery Review.

3.3.3.12 Quality Plan

The Contractor shall submit a quality plan deliverable in accordance with Appendix H. An overview shall be submitted with proposal; baseline at contract award.

J-1-7

3.4 Units Required

Flight Unit

The Contractor shall provide one flight unit that meets the requirement of the specifications, has successfully completed acceptance testing, and is quality-controlled as specified in this PWS.

Flight Spare Unit

The Contractor shall provide one unit to be used as a flight spare that is identical to the flight unit, meets the requirement of the specifications, has successfully completed acceptance testing, and is quality-controlled as specified in this PWS.

Qualification and Engineering Unit

The Contractor shall provide one unit to be used as a qualification and engineering unit that is identical to the flight unit, meets the requirement of the specifications, has successfully completed acceptance testing, and is quality-controlled as specified in this PWS. This unit shall be used for any qualification testing that is needed.

Flight Test Units

The Contractor shall be capable of providing up to three flight test units if NASA/MSFC deems necessary. These flight test units shall be identical to the flight units in form, fit, and function, meet the requirement of the specifications, has successfully completed acceptance testing, and is quality-controlled as specified in this PWS.

3.5 Hardware Need by Dates

The Contractor shall deliver the two flight units no later than November 1st, 2023. Also, the Contractor shall be capable of providing up to three additional units before October 1st, 2023 to support a flight test, if NASA/MSFC deems necessary upon contract award. The one qualification/engineering unit, which is equivalent in form, fit, and function to the flight units, shall be provided by September 1st, 2023. The Contractor shall supply adequate information to support meeting the delivery timeline, including the associated impacts of model design options, configurations, and/or modifications to support meeting the specification requirements.

4 MILESTONES

The Contractor shall include in their proposal a list of suggested milestones which NASA/MSFC will use to ascertain progress of the procurement. Initial deliverable shall be with proposal, with updates no later than 30 days after contract award.

J-1-8

Appendix A: Acceptance Data Package

SCOPE:

The Acceptance Data Package (ADP) contains the elements of documentation required to establish the acceptability of equipment and software.

CONTENTS:

An Acceptance Data Package (ADP) for configuration items shall include:

a. Running/operating time and cycle for each time and cycle critical items of the Configuration Item (CI).

These logs shall identify the item(s) by nomenclature, part number, and serial number and shall state the total authorized life and the life expended.

b. Test history log, including post manufacturing checkout and final verification tests of the CI, with the following data:

1. Actual measurements identified to specified tests. Reference to applicable test reports are satisfactory provided that copies of the reports are provided.

2. Brief test summary.

3. List of unaccomplished tasks and estimated man-hours to complete.

4. List of actual and recommended retest.

5. Special test instructions, investigations, warnings, and problems encountered during test.

6. Failure and corrective actions data for all failures during all testing.

c. Inspection records for all inspections.

d. Transfer records providing a history of all CI and critical component movements.

e. Alignment data for all CIs and critical items.

f. Component log books, including Government furnished items.

g. Weight and balance logs covering total weight and horizontal, vertical, and lateral center(s) of gravity.

h. Configuration Records:

1. Parts and drawing list identifying all parts and incorporated or pending changes to each.

2. Software configuration records defining the verified and validated software, version description documents, software certification, and the validated software program.

3. List of approved and pending deviations and waivers.

4. Complete list of hardware and software/firmware items shipped loose or separately.

5. Copy of proposed DD Form 250.

MAINTENCNE:

The ADP shall be maintained current. Changes and/or updating shall be in accordance with the provider/contractor’s approved change control system.

SUBMISSION FREQUENCY:

Baseline following delivery of each Configuration Item (CI)

J-1-9

Appendix B: Engineering Drawings and Associated Lists

SCOPE:

Engineering drawings disclose (directly or by reference) the physical and functional requirements of an item by means of graphics or textual presentation or combinations of both, as supplemented by 3D models.

Drawing Trees depict the hardware and software configuration item drawing in graphic, top down, hierarchical structures.

APPLICABLE DOCUMENTS/CLAUSES:

ASME Y14.100 Engineering Drawing Practices ASME Y14.41 Digital Product Definition Data Practices ASME Y14.5 Dimensioning and Tolerancing MIL-STD-130 Department of Defense Standard Practices, Identification Marking of U.S. Military Property

CONTENTS:

Requirements:

a) Part I - Engineering drawings and associated lists shall meet the requirements of ASME Y14.100.

Geometric Dimensioning and Tolerancing shall be implemented in accordance with ASME Y14.5. Supplemental 2D/3D CAD shall meet the requirements of ASME Y14.41. Engineering drawings and associated lists of end items, elements and/or all components and assemblies shall be provided to define the details necessary for the manufacture, test, inspection, operations and logistic support of the system. This definition shall:

1) Reflect the end-product at its current level of design maturity.

2) Provide the engineering data for logistics support products.

3) Provide the necessary data to permit manufacture and/or acquisition of items identical to the original item(s).

4) Document directly or by reference the following:

i) Details of unique processes (i.e., not published or generally available to industry) when essential to design and manufacture.

ii) Performance ratings.

iii) Dimensional and tolerance data (Geometric Dimensioning and Tolerancing (GDT) shall be required between all external and major internal interfaces).

iv) Critical manufacturing processes and assembly sequences, and rigging procedures.

v) Diagrams.

vi) Mechanical and electrical connections.

vii) Physical characteristics, including form and finish.

viii) Details of material identification, including heat treatment and protective coatings.

ix) Inspection, test, and evaluation criteria.

x) Equipment calibration requirements.

xi) Quality assurance requirements.

xii) Hardware marking requirements.

xiii) Requirements for reliability, maintainability, environmental conditions, shock, and vibration testing and other operational or functional tests.

5) Limited rights-in-data items - Engineering drawings for items which the Government does not have unlimited rights in data shall specify the form, fit, and function requirements of the item and conform

J-1-10 to the requirements for a control drawing as defined in ASME Y14.100 or a specification prepared in accordance with project requirements.

b) Part II - Cable interconnect diagrams (CID's), electrical system schematics, and wiring lists. Cable interconnect diagrams, electrical system schematics, wiring lists, and fluid system schematics shall be prepared in accordance with ASME Y14.100. Part I drawings shall be utilized to the maximum extent possible in providing the design definition. The drawings shall include the following:

1) Cable interconnect diagrams shall show graphically the arrangement of external electrical cabling which interconnects electrical assemblies and/or equipment. The CID shall show all cable runs and terminations; each cable shall be identified by reference designation number. The connector short sign shall be identified.

2) Electrical system schematics shall illustrate and describe circuit items with symbols placed such that a circuit may be traced from item to item in the sequence of its function. The placement and arrangement of these circuits shall follow a logical sequence of presentation to provide a clear description of the distribution.

3) Component Level Documentation - Schematics and/or wiring lists for components, including interconnecting cable harnesses, shall be provided.

4) Overall Grounding Documentation - The grounding schematic shall show the details of all grounds and power returns from source to loads. All connections shall be shown. It shall also show details of all Electrical Ground Support Equipment interconnections to facility and safety grounds.

c) Engineering drawing shall specify marking criteria and methods for identification of parts produced or procured. All parts shall be physically marked. When physical marking or tagging causes a deleterious effect, labels, tags, and nameplates may be considered. MIL-STD-130 shall be used for paper labels, tagging, and nameplates.

d) A drawing tree shall be submitted for each configuration item that graphically depicts the hierarchical structure of drawings-parts from the configuration item down to assemblies, subassemblies, and components.

FORMAT:

Format of engineering drawings shall be in accordance with ASME Y14.100. Drawings shall be delivered in PDF format. 2D/3D CAD shall be in accordance with ASME Y14.41, in the current version of native developed CAD, fully parametric and associative. Originator format is acceptable for drawing trees. All documentation/data shall include the contractor's Commercial and Government Entity (CAGE) code and document numbers.

For all binary deliveries the contractor shall include a listing of the creating environment to include:

a. CAD product name/version/patches.

b. Subordinate (plug-in) software/version/patches.

c. Description of hardware.

d. Operating system/version/patches.

MAINTENANCE:

All documents produced under this DRD must be maintained current. Changes to and/or updating of engineering drawings, associated lists, and drawing trees shall be in accordance with the contractor's approved drawing system and the provisions herein. Changes to engineering drawings under the Government's Class I change control shall be submitted by Engineering Change Proposal. The contractor shall maintain the capability to restore and modify any engineering data used in the design through the project lifecycle.

J-1-11

Three weeks prior to each major review, as part of an Acceptance Data Package (ADP), and as requested. In addition, 3D CAD Models shall be submitted between milestones as requested by the procuring activity, and updated Drawing Trees shall be submitted for the related configuration items Physical Configuration Audit

(PCA).

J-1-12

Appendix C: As-Built EEE Parts List

SCOPE:

The As-Built EEE Parts List provides required information for all EEE parts actually used in the assembly of contractor, subcontractor, supplier, and in-house equipment.

APPLICABLE DOCUMENTS/CLAUSES:

MSFC-STD-3012 Electrical, Electronic and Electromechanical (EEE) Parts Management and Control

Requirements for MSFC Space Flight Hardware

CONTENTS:

The As-Built EEE Parts List shall comply with requirements stated in MSFC-STD-3012:

a) Delivered end item or equipment identification (part number and serial number).

b) EEE part’s next higher assembly identification (part number and serial number).

c) EEE part type.

d) EEE part number.

e) Generic EEE part number.

f) Grade of EEE part as defined in MSFC-STD-3012.

g) Identification of additional testing performed for parts that do not meet Grade 1 or Grade 2 requirements.

h) EEE part’s circuit locating reference designation.

i) EEE part manufacturer’s identification [Name and Commercial and Government Entity (CAGE) code or equivalent].

j) EEE part’s lot identification (Lot Date Code or equivalent).

k) EEE part’s serial number, if applicable.

l) Identification that an item has been changed from a previous submission.

FORMAT:

MSFC approved contractor format is acceptable. Data shall be submitted by editable electronic media (e.g. Excel or Access format).

MAINTENANCE:

Changes shall be incorporated by complete reissue.

Subsequent changes in configuration

J-1-13

Appendix D: As-Designed EEE Parts List

SCOPE:

The As-Designed EEE Parts List identifies the EEE parts approved for use in contractor, subcontractor, supplier, and in-house equipment designs.

APPLICABLE DOCUMENTS/CLAUSES:

MSFC-STD-3012 Electrical, Electronic and Electromechanical (EEE) Parts Management and Control

Requirements for MSFC Space Flight Hardware.

CONTENTS:

The As-Designed EEE Parts List shall comply with requirements stated in MSFC-STD-3012:

a) Deliverable end item or equipment identification (part number).

b) EEE part type.

c) EEE part number.

d) Generic EEE part number.

e) Grade of EEE part as defined in MSFC-STD-3012.

f) EEE part specification.

g) EEE part qualification method and status.

h) Identification of additional testing performed for parts that do not meet Grade 1 or Grade 2 requirements.

i) Nonstandard EEE part approval identification and status.

j) Identification of EEE part manufacturer [QML, QPL, or name and CAGE code].

k) Quantity of EEE part used in equipment (estimated).

l) Indication that item is a change from the previous submission.

FORMAT:

MSFC approved contractor format is acceptable. Data shall be submitted by editable electronic media (e.g. Excel or Access format).

MAINTENANCE:

Changes shall be incorporated by complete reissue.

Update quarterly to document the current design and 30 days prior to the CDR; update as required to document the current design.

J-1-14

Appendix E: Material Usage Agreement (MUA)

SCOPE:

Material Usage Agreements (MUAs) describe the material or processes application with sufficient technical rationale to justify usage in accordance with the guidelines of MSFC-PROC-1301.

a. Category I MUAs – Category I MUAs are those that involve material or process usage that could affect the safety of the mission, crew, vehicle, or affect the mission success, but must be utilized for functional reasons. Approval by the responsible NASA Materials and Processes organization and the NASA Program/Project office is required.

b. Category II MUAs – Category II MUAs are those that involve material or process usage that fails a screening of Materials and Processes requirements and is not considered a hazard in its use application but for which no Category III rationale code exists. Approval by the responsible NASA Materials and Processes organization is required.

c. Category III MUAs – Category III MUAs are those that involve materials or processes that have not been shown to meet minimum requirements but have an approved rationale code listed in NASA-STD-6016, Appendix C, or NASA approved Contractor equivalent. They are evaluated and determined to be acceptable at the configuration/part level. Category III MUAs shall be reported in the Materials Identification and Usage List (MIUL) system or electronic data system utilizing the approved rationale codes in appendix C. A key may be provided to correlate contractor Category III MUA database codes to the codes in appendix C.

APPLICABLE DOCUMENTS/CLAUSES:

NASA-STD-6001 Flammability, Offgassing and Compatibility Requirements and Test Procedures NASA-STD-6012 Corrosion Protection for Space Flight Hardware NASA-STD-6016 Standard Materials and Processes Requirements for Spacecraft MSFC-STD-3029 Guidelines for the Selection of Metallic Materials for Stress Corrosion Cracking

Resistance in Sodium Chloride Environments MSFC-STD-506 Standard Materials and Processes Control MAPTIS database http://maptis.nasa.gov/ Electronic Materials Selection List for Space Hardware Systems JSC-SP-R-0022A General Specification: Vacuum Stability Requirements of Polymeric Materials for

Spacecraft Application MSFC-PROC-1301 Guidelines for the Implementation of Required Materials Control Procedures

CONTENTS:

The MUA shall contain the information required per NASA-STD-6001, NASA-STD-6012, NASA-STD-6016, MSFC-STD-3029, JSC-SP-R-0022A, and MSFC Form 551 (latest revision) and shall be categorized as Categories I, II, or III. MUAs shall be submitted as component level, i.e. valve, transducer, motor, where possible according to MSFC-PROC-1301 guidelines. Category I and II MUAs shall be required for materials, processes, certifications, and specifications, which require NASA approval prior to qualification and incorporation into design. Category I and II MUAs shall be submitted formally to the Materials Application Evaluation Board (MAEB) at Marshall Space Flight Center (MSFC), Mail Code EM04. Category III MUAs shall be retained by the hardware developer and subject to NASA review. Category I and II MUAs shall be submitted to NASA for review and approval for all M&P usages that do not comply with the contractual specification requirements. MUAs are classified as Category I or II if one or more of the following is in effect:

a) Flammability - size greater than 1 square foot total (one or more materials and do not create propagation path).

J-1-15

b) Toxicity - the total amount of material intended for use exceeds the maximum limit weight for the total Toxic Hazard Index (T) value of 0.5 or the total T value for the total number of assembled articles intended for use exceeds 0.5.

c) Stress Corrosion - usage could effect safety of vehicle or major operational, cost or schedule problem; or complete environment history, including all storage, assembly and service environments are not defined.

d) Fluid System - materials do not meet requirement of NASA-STD-6001 for liquid or gaseous oxygen.

e) Corrosion - usage where corrosion can affect structural integrity, or complete environment history, including all storage, assembly and service environments are not defined.

f) Thermal Vacuum Stability - line of sight, critical surfaces.

g) Other - any other requirement, e.g., space environmental effects, propellant compatibility (hydrogen, hydrazine, etc.), age life capability, material design properties or temperature capability, processing, Nondestructive Evaluation (NDE), etc., that could affect the safety of vehicle or major operational, cost, or schedule problem.

h) Other materials that do not meet screening requirements, but are acceptable at the configuration/part level, shall be designated as Category III. These MUAs shall be approved by the Chief of the hardware developer's Materials Organization, and retained at hardware developer's plant, subject to NASA's review upon request. A Rationale Evaluation Code shall be added in the MUA field of MIUL after the Category III MUA number specifying rationale for approval. Rationale codes from NASA-STD-6016 are as follows:

Flammability Codes:

101 Approved Materials Usage Agreement (MUA) category I.

102 Approved Material Usage Agreement (MUA) category II.

103 Passed requirements when tested in configuration.

104 Unexposed, overcoated, or sandwiched between non-flammable materials with only edge exposure and no ignition source or propagation path.

105 Minor usage (less than 0.1 lb. and 2 sq.-in. surface area); no propagation path or ignition source.

106 Materials used in hermetically sealed container.

107 Passes Test No. 10 of NASA-STD-6001, Flammability Test for Materials in Vented or Sealed

Containers by test or analysis.

108 Off the shelf equipment, having material acceptable in configuration; no ignition source or propagation path.

109 Material not exposed; totally immersed in fluid; evaluated for fluid compatibility only.

110 Material is acceptable when used on a metal substrate that provides a sufficient heat sink. Material considered noncombustible in this configuration by test or analysis.

111 Material is flammable but is sandwiched between nonflammable materials with edges only exposed and is more than 5cm from an ignition source or more than 30cm (12 in) from other flammable materials.

112 Material is flammable but is unexposed or is overcoated with a nonflammable material.

113 Material is flammable but has a thickness less than 0.25mm (0.010 in) and is sprayed or bonded to a metallic surface greater than 1.6mm (0.062 in) thick.

114 Material is flammable but is used in small amounts and is more than 5cm (2 in) from an ignition source or more than 30.5cm (12 in) from other flammable materials. Small amounts for flammability may be quantified as follows: total weight less than 45g (0.1lb) and less than 13cm2 (2.0in2) surface area.

Toxicity Codes:

201 Approved Material Usage Agreement (MUA) Category I.

202 Meets TOX requirements with performed cure.

203 T value for material/component in usage weight is <0.5 for manned flight compartment volume.

204 Materials used in hermetically sealed container.

J-1-16

Fluid System Compatibility Codes:

301 Approved Material Usage Agreement (MUA) Category I.

302 Passes requirements when tested in configuration.

303 Material is B rated in MAPTIS (batch/lot testing required) but batch/lot used in hardware passed test.

304 Approved Material Usage Agreement (MUA) Category II.

Thermal Vacuum Stability Codes:

401 Approved Material Usage Agreement (MUA) Category I.

401 Approved Material Usage Agreement (MUA) Category II.

403 VCM between 0.1 and 1.0 percent; exposed area is less than 13cm2 (2in2) and not near a critical surface.

404 VCM >1.0 percent; exposed area is less than 1.6cm2 (0.25in2) 405 Unexposed/overcoated, or encapsulated with approved material.

406 Material is B rated in MAPTIS (batch/lot testing required) but batch/lot used in hardware cured to meet requirements.

407 Meets thermal vacuum stability requirements in configuration.

408 Materials used in hermetically sealed container.

409 Material has VCM > 0.1 percent, but is enclosed in a sealed container (maximum leak rate less than 1 x

10-4cm3/sec)

Stress Corrosion Cracking Codes:

501 Approved Material Usage Agreement (MUA) Category I 502 Approved Material Usage Agreement (MUA) Category II.

503 Maximum tensile stress <50 percent of yield strength for part on electrical/electronic assemblies.

504 Martensitic or PH stainless steels used in ball bearing, race, or similar applications where the primary loading is compressive.

505 Metal not listed in table 1 of MSFC-STD-3029 for stress corrosion cracking is not exposed to a corrosive after final assembly trough end-item use.

506 Carbon and low alloy high strength steels greater than 1240 MPa (180KSI) used in ball bearings, springs, or similar applications where primary loading is compressive, low tensile stresses, or history of satisfactory performance.

Corrosion Codes:

601 Approved Material Usage Agreement (MUA) Category I 602 Approved Material Usage Agreement (MUA) Category II.

603 Adequately finished for corrosion protection.

604 Acceptable in use environment.

606 Electrical grounding required, cladding plus conversion coating adequate.

607 Thermal conductance and electrical bonding requirements preclude painting and chemical conversion coating is adequate (for aluminum only).

608 Finished on a higher assembly.

609 Laminated shim - minimum exposure of corrosion resistant material.

610 Material does not meet the requirements of NASA-STD-6012, Class II, but is treated or coated in a manner which meets or exceeds the requirements of NASA-STD-6012. Actual surface treatment shall be listed.

611 Material does not meet the requirements of NASA-STD-6012, Class II, but is not exposed to a corrosive environment after final assembly through end-item use.

J-1-17

612 Welding of titanium alloy-to-alloy or commercially pure alloy-to-alloy using commercially pure filler metal in mixed alloy welds where hydrogen embrittlement is not predicted in service.

FORMAT:

MSFC Form 551 (latest revision) and MSFC-STD-3029, Section 5.4, “Assessment of the Potential for a Stress Corrosion Failure” are acceptable formats for MUA data. MUAs shall be submitted in an electronic or hardcopy format compatible with Materials and Processes Technical Information System (MAPTIS) database at:

http://maptis.nasa.gov/.

Category 1 and II - as identified in design and one month prior to milestone reviews; Category III - upon request

J-1-18

Appendix F: Financial Management Report (533M and 533Q)

SCOPE:

The Financial Management Report (533M and 533Q) provides data on accumulated costs and funding projections for management of the contract.

APPLICABLE DOCUMENTS/CLAUSES:

NPR 9501.2E NASA Contractor Financial Management Reporting NPR 9060.1A Accrual Accounting - Revenues, Expenses, and Program Costs

CONTENTS:

The elements of cost for financial reporting shall be mutually agreed by the contractor and NASA project office.

The Financial Management Reports (533M and 533Q) shall be prepared in accordance with the detailed instructions provided on the reverse side of the NASA Forms 533M and 533Q and the supplementary instructions set forth in NPR 9501.2E, Chapter 3.

a. 533Q Quarterly Report shall include actual cost and cost projections at the total contract level.

The initial 533Q report shall reflect the original contract value detailed by negotiated reporting categories and serve as the original baseline plan.

b. 533M Monthly Report shall include actual cost and cost projections at the total contract level.

When Earned Value Management System (EVMS) or other performance measurement system (PMS) and NF 533 reports are required under the contract, they shall reflect information that is consistent and generated from the same management information systems.

FORMAT:

Contractor internal automated printout reports may be substituted for 533M/533Q forms (with NASA Contracting Officer’s approval) provided that the contractor report contains all of the data elements required by NASA Forms 533M and 533Q. NASA strongly encourages the use of electronic contractor cost reporting, as long as the requirements of NPR 9501.2E are met and NASA obtains the information it needs to manage its contracts. The data contained in the reports shall be auditable using Generally Accepted Accounting Principles.

Contractors should submit the reports earlier than the required due dates whenever possible.

SUBMISSION FREQUENCY:

533Q: Quarterly; no later than the 15th day of the month preceding the quarter being reported in columns 8a, 8b, and 8c. 533M: Monthly; no later than 10 working days following the close of the contractor’s accounting month.

NF533 SUPPLEMENTAL REPORTING REQUIREMENTS:

Supplemental reporting requirements will be submitted during the course of the contract in accordance with direction in Appendix A per NPR 9060.1A.

REQUIRED SUPPLEMENTAL REPORTING REQUIREMENTS:

ANNUAL ACCOUNTING CALENDAR:

Contractors' accounting periods commonly differ from the calendar month basis used for NASA accounting.

Monthly cost accruals, however, need not include an estimate for the cost to be incurred during the period from the end of the contractor's accounting period to the end of the month. This estimate should be performed

J-1-19 quarterly. The contractor’s accounting calendar for the contract period of performance shall be provided in electronic format to the Contracting Officer and RS20 Cost Accountant within 10 business days after contract award. Updates to the accounting calendar shall be provided in electronic format to the Contracting Officer and RS20 Cost Accountant before the delivery of the subsequent NF533.

CONTRACTOR VARIANCE REPORT:

The contractor shall submit variance reports along with the NF533M when NF533M variances meet or exceed +/- 10% for each Reporting Category for the following items:

1. Column 7A current month (actuals) to 8A previous month (estimate)

2. Column 7A current month (actuals) to 7B current month (plan)

J-1-20

Appendix G: Material Identification and Usage List (MIUL)

SCOPE:

Materials Identification and Usage List (MIUL) identifies all M&P usages contained in the end item and shall be documented in an electronic searchable parts list or separate electronic searchable MIUL. The procedures and formats for documentation of materials and processes usage will depend upon specific hardware but shall cover the final design. The system used shall be an integral part of the engineering configuration control/release system.

A copy of the stored data shall be provided to National Aeronautics and Space Administration (NASA) in a form compatible with the Materials and Processes Technical Information System (MAPTIS) database at:

http://maptis.nasa.gov/.

APPLICABLE DOCUMENTS/CLAUSES:

NASA-STD-6001 Flammability, Offgassing and Compatibility Requirements and Test Procedures NASA-STD-6012 Corrosion Protection for Space Flight Hardware NASA-STD-6016 Standard Materials and Processes Requirements for Spacecraft MAPTIS-II database http://maptis.nasa.gov/ Electronic Materials Selection List for MSFC Space Hardware

Systems.

MSFC-STD-3029 Guidelines for the Selection of Metallic Materials for Stress Corrosion Cracking Resistance in Sodium Chloride Environments JSC-SP-R-0022A General Specification: Vacuum Stability Requirements of Polymeric Materials for

Spacecraft Application MSFC-PROC-1301 Guidelines for Implementation of Required Materials Control Procedures

CONTENTS:

As a minimum, the MIUL shall document and identify the following:

a) Detail drawing number, title (nomenclature), and dash number.

b) Next assembly number, title (nomenclature), and dash number.

c) Change letter designation.

d) Drawing source (contractor or vendor).

e) Material and process specification with title, revision, and author identified.

f) Cure number from the Materials and Processes Technical Information System (MAPTIS) (shall define cure conditions for nonmetals only).

g) Environmental data (complete environment history including all storage, assembly and service environments, media, pressure, temperature, etc.).

h) Quantitative information shall include weight, thickness and surface area (for nonmetals only).

i) Materials Usage Agreement (MUA) number/status (if applicable).

j) NASA material code (from MAPTIS-II database shall identify material/alloy designation, form, strength or condition for metals; and material designation, trade name, use type, composition and manufacturer for nonmetals).

k) Standard part number (NAS, MS, AN, etc.).

l) Material rating/usage evaluation (shall evaluate usage based on applicable criteria of NASA-STD-6001, NASA-STD-6012, NASA-STD-6016, MSFC-STD-3029 and JSC-SP-R-0022A, utilizing MAPTIS-II database as a data source).

m) Remarks (shall provide additional rationale to justify acceptance of M&P application using MSFC-PROC- 1301 for guidance).

J-1-21

The hardware developer shall designate on the MIUL which process specifications are critical* to the fabrication, control and inspection of the contract end items on the MIUL. These processes shall be submitted for the review and approval of NASA.

*Critical Processes: A materials process (i.e., a process that changes the chemical/physical properties of a material). A critical process is an operation, treatment or procedure used as a step in manufacturing or inspection that, if improperly or inadequately performed, can have a significant performance effect on any of the following:

a) Hardware identified on the Critical Items List (CIL).

b) Hardware designated for fracture control.

c) Ordnance hardware.

d) Hardware where design conformance is not assured by inspection or test.

e) Hardware that has a high technical risk, i.e., stringent technical performance requirements in its intended application relative to state-of-the-art techniques for the item.

FORMAT:

Contractor format is acceptable and shall be consistent with contents section of this DRD. Contractor format for electronic submittal of MIUL data shall be compatible with MAPTIS.

MAINTENANCE:

Changes shall be incorporated by complete reissue.

As-designed MIUL – at Delivery Review; As-built MIUL updates as needed

J-1-22

Appendix H: Quality Plan

SCOPE:

The Quality Plan will identify, as applicable, the specific quality activities (implementation) related to the design and development, procurement of materials/subcomponents, fabrication, test, shipping, flight operations, refurbishment, and reuse to assure the quality of the items delivered. The plan shall reference the contractor’s quality manual and procedures as necessary to fully describe the contractor’s quality system.

APPLICABLE DOCUMENTS/CLAUSES:

ANSI/ISO/ASQ Q9001-2015 Quality Management Systems Requirements Standard ISO/IEC 17025 General Requirements for the Competence of Testing and Calibration Laboratories SAE AS9100D Quality Management Systems - Aerospace – Requirements SAE AS9003 Inspection and Test Quality System NPD 8730.5 NASA Quality Assurance Program Policy

CONTENTS:

Each quality element of SAE AS9100D in conjunction with either ANSI/ISO/ASQ Q9001-2015 or SAE AS9003 and/or as applicable ISO/IEC 17025 shall be addressed to describe the philosophy and approach for implementation. This can be satisfied by contractor’s existing quality manual and procedures. The only exceptions allowed will be processes noted in Section 7 of SAE AS9100D and/or ANSI/ISO/ASQ 9001- 2015 as applicable in the contract Performance Work Statement (PWS). A copy of the Quality System Manual and 1st tier procedures shall be submitted with any required quality plan.

As a minimum, the subparagraphs below shall be addressed by the present documented quality management system or subsequent submittal of a quality plan to include details of responsibilities and controls to adequately describe the specific quality assurance activities related to hardware being procured by MSFC:

a) Customer quality requirements – include hardware specific quality requirements imposed by contract or component/equipment specification (i.e., traceability requirements, specific inspection points, specific quality activities including Government surveillance and inspection processing) including Government surveillance and inspection processing, also known as Government Mandatory Inspection Points (GMIP).

b) Responsibilities – describe which contractor organizations will be responsible to perform the applicable quality management system activities.

c) Article, Material, and Service Controls - describe the level of article, material, and service control including traceability requirements invoked by the contractor for the articles, materials, and/or services used in or performed as part of the hardware design and maintenance criteria, including how quality is assured for each material, part, assembly, and/or service performed.

d) Procurement – include the procurement quality requirements for all materials/parts/components the contractor purchases and the level of control exercised over the suppliers including how suppliers are approved, monitored, and maintained with controls for supplier nonconformances processing.

e) Milestone Reviews – describe how the contractor’s quality system will support milestone reviews.

f) Configuration Assurance – describe how the configuration of the hardware build is compared and verified to the approved design baseline drawings and specifications. Describe how the configuration of Government Furnished Property/Equipment is maintained.

J-1-23

g) Special Process Controls – describe special process controls implemented for in-house processes and, if applicable, for sub-tier supplier processes.

h) Inspection and Test (describe who will be responsible to perform inspections to include any restrictions)

– include: how the quality of purchased items is validated at receiving inspection or at sub-tier suppliers facilities, specific in-process (manufacturing) inspections performed, details of final inspection, functional and environmental test monitoring details, and pre-ship inspections. When applicable, provisions shall be included for development of site quality plans for major end item test and flight test.

i) Nonconforming Product (Material Review Board Process) - describe the process of convening a nonconforming product material review board (MRB) to disposition nonconforming product using a defined board of qualified personnel including contractor quality assurance personnel and customer representatives. MRB limitations within the Performance Work Statement (PWS) PWS and membership qualification shall be defined.

An MRB membership listing shall be submitted within the quality plan or by contract letter.

j) Flight Operations, Refurbishment, and Reuse – when applicable, describe how the contractor’s quality assurance system is implemented for flight operations, refurbishment and reuse.

k) Record retention – for those records not delivered to MSFC, specify which records are required to be kept, who keeps them, for how long, and how they are to be dispositioned at the end of the retention period, and/or as specified in the contract.

FORMAT:

Contractor format is acceptable.

MAINTENANCE:

Changes shall be incorporated by complete reissue.

Update as design matures and risks and their quality related mitigating factors are better defined.

J-1-24

Appendix I: Verification/Validation Data

Verification/Validation Compliance Assessment (VVC)

SCOPE: The Verification/Validation Compliance (VVC) Assessment…