DRAFT_SOW_DRDs_Rev2.pdf

PART III – LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENT

SECTION J – LIST OF ATTACHMENTS

Section J J-1 LFS

ATTACHMENT J-X

Data Requirements List (DRL) and Data Requirements Descriptions (DRDs)

Lunar Freezer System

Section J J-2 LFS

INTRODUCTION

The following pages set out the documentation requirements of this contract, starting with a Data Requirements List (DRL), which is an index to the Data Requirements Descriptions (DRDs). Each DRD prescribes the required data product content, schedule, type, and other particulars for specific data submission requirements. NASA DRD forms are used to specify documentation requirements for this contract, and much of the Contractor-provided data is used to certify flight hardware.

Subject to the Clause 52.227-14, Rights in Data - General, this document sets forth the data requirements in each Data Requirements Description (DRD) and shall govern that data required for this contract. The contractor shall furnish data defined by the DRDs listed on the Data Requirements List (DRL) by category of data. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this document. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause, the regulation will take precedence over this document.

Documents included as applicable documents in the data requirements form a part of this document to the extent specified herein. References to documents other than applicable documents in the data requirements of this document may sometimes be utilized. These do not constitute a contractual obligation on the contractor. They are to be used only as a possible example or to provide related information to assist the contractor in developing a response to that particular data requirement.

DESCRIPTION

This document identifies and defines the requirements and data types for information and data required under this contract.

The Data Requirement Descriptions (DRDs), define, by an individual Data Requirement, the information and data required for each deliverable document.

The data types are used to identify the approval and control required for each DRD. The Data Requirements List (DRL) is an index of all the DRDs by category.

Documentation submitted pursuant to this clause may incorporate references to other current approved documentation, provided the references are adequate and include such identification elements as title, document number, and approval date (where applicable). However, if the pertinent information is of relatively minor size, the contractor shall incorporate the information itself, in lieu of using a reference. The contractor shall assure that any referenced information is readily available to appropriate users of the submitted document.

Section J J-7 LFS

12. DISTRIBUTION:

(1) 1 electronic copy to Contracting Officer

(2) 1 electronic copy to Contracting Officer’s Representative

13. REMARKS: N/A

Section J J-9 LFS

(b) Classification of property

3. Receipt of Government Property

(a) Receiving

(b) Identification

4. Records of Government Property

5. Physical Inventory

6. Subcontractor Control

(a) Flow down of property clauses to subcontractors

7. Reports

(a) Loss, Theft, Damage, Destruction reports

(b) Physical Inventory reports

(c) Audits and self-assessment reports

(d) Corrective Action reports

8. Relief of Stewardship Responsibility and Liability

(a) Loss, Theft, Damage, Destruction of property

(b) Consumed property

(c) Delivered property

(d) Contractor Inventory Disposal of property

i. In-house screening of excess

ii. Disclosure of excess

(e) Abandonment of Government property (if directed by the Government)

9. Utilizing Government Property

(a) Utilization

(b) Consumption

(c) Movement

(d) Storage

10. Maintenance

(a) Preventive maintenance

(b) Rehabilitation

(c) Calibration

11. Property Closeout

(a) Screening for further use

(b) Final physical inventory

(c) Transfers off the contract

(d) Final NASA Form 1018

12. Reconcile Contractor Records with NASA Financial Property Records. (NASA Form 1018 and the Contractor-Held Asset Tracking System (CHATS) if applicable.)

13. JSC-Unique Considerations (as they arise or known)

Management Qualifications/Experience:

1. The Offeror/Contractor shall specify the name and the qualifications of the proposed property manager.

a. List the Federal agencies or departments supported in managing Government property and the corresponding number of years of experience.

b. List completed personal property management training courses.

c. Specify the level of professional property management certification obtained by the proposed property manager.

d. List professional personal property management organizations in which the proposed property manager has an

Section J J-10 LFS active current membership.

2. This qualification data shall be a one-time submittal from the Offerors with their initial Property Management Plan (PMP) when the plan is requested by the Contracting Officer. Insert that data as a separate tab after that PMP. This qualification data shall be excluded from the final PMP from the awarded Contractor.

Remarks: N/A

Maintenance: Changes to the PMP shall be incorporated by change pages or complete reissue after coordination with the Government PA.

Section J J-12 LFS

Applicable Documents: NFS 1852.245-73

Scope: The NF 1018 report provides annual summary-level property management and financial data on Government-furnished and contractor-acquired NASA property.

Contents:

NF 1018 Reports

1. The NF 1018 report provides annual summary-level property management and financial data on Government-furnished and contractor-acquired NASA property.

2. The NF 1018 shall be completed in accordance with NFS Subpart 1845.7101, NFS 1852.245-73, and any supplemental guidance provided by NASA.

3. Contractors shall report all NASA-owned property in US dollars, regardless of location.

4. Negative or zero reports are required.

5. Adjustments to the NF 1018 shall be thoroughly explained in the NF 1018 “Comments” section and must be approved by the JSC Industrial Property Officer (IPO) prior to submittal of the report, after first being coordinated with the cognizant Government Property Administrator (GPA).

6. Entries in Type of Deletion 21 "h. OTHER" must be explained in detail in the “Comments” section.

7. Entries should not be placed in Type of Deletion 21 "d" or "e" since they should be reflected in "c”.

8. The NF 1018 report consists of two pages; a Summary first page and a Deletions second page. Both must be accurately completed for submittal.

Monthly Property Financial Reports

1. The Contractor shall request that the JSC Contractor Held Property Accountant in LF/Property, Cost, and Reporting Branch add contracts meeting the requirement for monthly property financial reporting to the CHATS. The contractor shall also request access to the CHATS via the NASA Account Management System (NAMS).

2. Monthly Property Financial Reports are required with item level supporting data. This data shall be submitted for all items with an acquisition cost of $500,000 or more, in the contractor's and its subcontractors' possession, in the following classifications: real property, equipment, special test equipment, special tooling, and agency peculiar property (if applicable). Monthly reporting is not required for property in the above classifications with an acquisition cost under $500,000. Monthly data shall also be submitted for items of any acquisition cost in the classifications of materials and contract work-in-process (WIP). Itemized monthly data is required for material line items of $500,000 and over. Itemized monthly line item data is required for WIP. Summary monthly data is required for material items under $500,000. Other software (not integrated into a piece of Government property that is necessary to operate that item) shall be considered an individual reporting item if the acquisition cost is $1,000,000 or more an expected to have a useful life of 2 years or more.

3. Acquisition costs shall be developed using actual costs to the greatest extent possible, especially costs directly related to fabrication such as labor and materials. Supporting documentation shall be maintained and available for all amounts reported, including any amounts developed using estimating techniques.

All Adjustments shall be thoroughly explained and directly related to a specific fiscal year. If the fiscal year cannot be determined, the default shall be the previous fiscal year. Adjustments to the monthly report must be coordinated with JSC Finance.

Section J J-13 LFS

Remarks:

The Monthly Property Financial Reports shall be completed in accordance with the CHATS user manual (https://epss.nasa.gov/gm/folder-1.11.1123762?mode=EU&primaryCSH=chats) and any supplemental guidance provided by NASA.

Maintenance:

Revisions to the NF 1018 data shall be coordinated with the cognizant Government PA. Revisions to the Monthly Property Financial Reports shall be coordinated with the JSC Contractor Held Property Accountant in LF/Property, Cost, and Reporting Branch.

Section J J-15 LFS disadvantaged communities?

2. What actions has the organization taken to implement affirmative equity-enhancing policies, regulations, guidance, and approaches to emphasizing equity in policy- and rule-making processes?

3. Describe how the organization’s commitment will be communicated internally and externally from leadership to employees and stakeholders.

Diverse Talent – Demonstrate a pursuit of a high performing diverse workforce from underserved communities.

1. Discuss the specific diversity metrics utilized by the organization to measure performance in achieving a diverse workforce and provide the corresponding metrics for the current or most recent organizational reporting period

2. What barriers or opportunities exist to engage subject matter experts from underserved communities in industry and academia? How does the organization plan to overcome those barriers?

3. How will underserved communities be leveraged?

4. Describe recruiting activities, objectives, and outcomes (e.g., number of participants, number interviewed and hired from underserved communities).

Culture & Sustainability – Demonstrate how an inclusive and fair work environment will be cultivated and maintained.

1. Based on the data, what structures and strategies will be used to manage diversity, measure results, refine approaches, and institutionalize a culture of inclusion?

2. Identify actionable opportunities to improve data collection, use, and sharing that would allow for disaggregation, the ability to deliver services more equitably, and better understanding of how programmatic and policy decisions impact underserved communities.

3. Describe other corporate activities that seek to increase support of diversity, equity, and inclusion.

Remarks: N/A

Maintenance: Changes shall be incorporated by change page or complete reissue.

Section J J-17 LFS system(s) in accordance with the definitions set forth in NPR2810.1(series). The IT security plan shall be kept up to date as changes to the baseline configuration of the system occur and shall be documented in the IT Security Plan. Note: An IT Security Plan is specific to a system or group of systems, while an IT Security Management Plan is defined as the elements a contractor has outlined to meet the IT Security requirements for interfacing with other contractors and NASA, training requirements and meeting the requirements in NPR 2810.1(series).

IT Security Awareness Training:

Employees subject to this contract shall complete the NASA approved IT Security Awareness Training annually. The contractor shall provide evidence that periodic IT security awareness training has been met for all employees subject on this contract. The contractor shall submit periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1st through September 30th.

IT Security Role Based Training:

Employees subject to this contract shall complete NASA approved IT Security Training annually related to the following Role Based functions:

• IT Security Manager

• Information System Owner (ISO)

• Information Systems Security Officer (ISSO)

• Organizational Computer Security Official – Representative (OCSO-R)

The Contractor shall provide evidence that periodic IT security training has been met for all employees subject on this contract. Contractor provided IT security awareness training may be substituted but must be approved annually by the Government (via the JSC Center IT Security Officer [CISO]) as an acceptable substitute. The Contractor shall submit periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1st through September 30th.

Information on Employees in Sensitive Positions/Assignments Report:

The Information on Employees is Sensitive. ITS Positions/Assignments Report shall provide information annually for personnel screening as required by NPR 2810.1(series), and NPR 1600.1 on position risk.

IT Point of Contact:

The contractor shall identify a point of contact that NASA may reach in its attempt to address IT and IT Security issues.

The point of contact shall have the authority to ensure appropriate actions occur.

A list of all lead system administrators shall be updated by September 30 of each year. This list will be used to ensure the Contractor has met the system administrator certification requirements.

SUBMISSION

IT Security Management Plan Initial: 30 days prior to contract start Approval: upon contract start Frequency: Annually by September 30 IT Security Plan(s) Initial: assume maintenance of existing plans (for Government-owned and Contractor-managed systems) at Contract start; IT Security Plan(s) for contractor-owned systems due 30 days prior to contract start

Section J J-18 LFS

Approval: upon contract start Frequency: shall be kept up-to-date as changes to the baseline configuration of the system(s) occur Others as stated in this DRD.

C. FORMAT:

Unless otherwise directed, the data requested in this DRD shall be delivered to the Government in soft-copy via an electronic transfer mechanism (e.g., electronic mail, flash drive, or file transfer protocol) in a format readable by a Government device utilizing the standards in NASA-STD-2804, Minimum Interoperability Software Suite.

D. MAINTENANCE:

E. DISTRIBUTION:

Initial approval: Contract COR, CO, Contracting Organization’s OCSO, and JSC CISO Annual approval: Contract COR, CO, and Contracting Organization’s OCSO

F. APPLICABLE DOCUMENTS:

Section J J-21 LFS

Contents: All Contractors shall submit their Fiscal Year spending plans for review and approval to the cognizant Center Chief Information Officer (CIO), or designee, prior to the beginning of the Fiscal Year (October).

Changes to spending plans during the Fiscal Year shall be approved by the CIO, or designee, before implementation. Formats and reporting processes and procedures will be provided annually based upon Center and Agency requirements.

Examples of documentation, formats, processes, procedures, and structures will be provided annually in support of the data call. The attached Excel Spreadsheet, entitled “CPIC DRD Template for IT Portfolio PPM Data Collection,” is a sample template for Year 1 of the Contract. This is a dynamic process, and formats, processes, procedures, and structures are subject to change. The reporting requirement is defined by OMB annually. Each year, OMB may request varying levels of reporting across varying levels of technologies and labor, depending on their focus.

Remarks: None

Maintenance: Updated with Annual Submission

Section J J-24 LFS each RC (column 7a on NF533) Contract prior month planned cost (7b) Planned cost for prior month for each RC

(column 7b on NF533) HR/WYE contract prior month planned hours (7b)

Prior month planned HR/WYE for each RC (column 7b on NF533)

Contract ITD Cost Actual (7c) Contract ITD cost for each RC (column 7c on NF533)

Contract planned ITD (7d) Contract planned ITD cost for each RC (column 7d on NF533)

Current Gov’t FY Cum to Date Actual (7c1)

Actual cumulative cost and hours incurred for the current Government Fiscal Year through the prior month for each RC (column 7c1 on NF533)

Current Gov’t FY Cum to Date Planned (7d1)

Planned cumulative cost and hours for the current Government Fiscal Year through prior month for each RC (column 7d1 on

NF533)

Current month estimated cost (8a) Cost estimate (not Plan) for the current month for each RC (column 8a on NF533)

Current month estimated HR/WYE (8a)

HR/WYE estimate (not plan) for the current month for each RC (column 8a on

NF533)

Next month estimated cost (8b) Estimated cost for next month for each RC (column 8b on NF533)

Balance of Contract (8c) Balance of contract for the remaining estimate to complete for each RC (column 8c on NF533)

Government Fiscal Year EAC (8d) Actual cumulative cost and hours incurred plus remaining estimated cost and hours for the current Government Fiscal Year (column 8d on NF533)

Contractor Estimate (9a) Contractor estimate for the total estimate to complete entire scope of contract for each RC (column 9a on NF533). The EAC is the most likely outcome of all authorized work based on the most current and reliable information available at the time of submittal

Contract Value (9b) Contract value based upon contract modifications for each RC (column 9b on

NF533)

Unfilled orders outstanding (10) Unfilled orders outstanding at the end of the reporting period for each applicable RC (column 10 on NF533)

Reporting Category level Used by NASA’s accounting system to determine the RC level

Reporting Category Identifier Identifies if the RC is an actual Reporting Category or a Sub-Reporting Category

The Contractor is required to coordinate with the NASA Resource Analyst assigned to the contract in order to establish and maintain the Reporting Categories the contractor shall use to comply with this data requirement.

A Reporting Category (RC) correlates to a task order, delivery order, or Work Breakdown Structure (WBS) and is the level at which cost is reported. Each RC can have Sub-Reporting Category line items (detailed cost elements) that add up to a RC.

Column 7b (planned cost incurred/hours worked for the month) and 7d (cumulative planned cost incurred/hours worked) of the NF533M represent the negotiated baseline plan for the contract. There may not be a relationship between the estimates provided in columns 8 of the NF533M to columns 7b and 7d. Columns 7b and 7d represent the legally binding

Section J J-26 LFS to enter an accurate monthly cost accrual in the accounting system. All due dates are firm and changes will only be considered for declared holidays and or the center closures due to extenuating circumstances, all deviations to the due dates need to be coordinated and approved by the OCFO and contracting officer.

The due dates reflect the date the NF533 reports are received by personnel on the distribution list, not the date the reports are generated or mailed by the contractor. It is critical that the NF533 reports are submitted in a timely manner to ensure adequate time for NASA to analyze and record the cost into the NASA accounting system.

An initial Baseline report is required (in the NF533Q format) to be used as a baseline for the life of the contract. The initial baseline report shall be submitted by the contractor within 30 working days after contract award. The initial report shall reflect the original contract value detailed by negotiated reporting categories and shall be the original contract baseline plan. Any contractual changes to the initial baseline report should be worked with and must be accepted by the contracting officer. Contractual changes are defined as scope changes; i.e. extended period of performance, content de-scope, scope increase, etc. which should not be retroactive to the start of the contract. All changes made to the initial baseline report should be reconciled by a trace from the original and documented.

NF 533 M reporting shall begin no later than 10 days following the close of the contractor’s accounting period after initial incurrence of cost, including phase-in cost.

NF533 Final Submission Upon Contract Completion

Monthly NF533 reporting is no longer required once the contract is physically complete, provided the final cost report includes actual cost only (no estimates or forecasts). The contractor must continue to submit monthly NF533 reports as long as estimates for the following period are included. The final NF533 M should be clearly identified as such and shall only contain actual cost. If the final cost of a contract changes after the submission of the "final" contractor cost report, the contractor must submit a revised NF533 report in the month the cost change is recognized.

However, a significant amount of time may pass between completion of work on a contract and final closeout, due to final reporting, payment and acceptance requirements, property disposal considerations, and other administrative matters. If no significant additional costs are being incurred or are anticipated, then one of the following alternatives may be directed by the NASA contracting officer, with concurrence of the NASA Center Chief Financial Officer and cognizant Project Manager:

a. Summary NF 533 M reporting only, on a quarterly basis.

b. Reporting only when changes in actual cost occur.

c. Suspension of NF 533 reporting altogether.

Electronic NF533 Flat File Requirement

An electronic NF533 flat file is required from the contractor to NASA by the same due date. The data shall be submitted via email using the Government prescribed flat file format (see Appendix D for an example of the Agency Defined File Format layout details).

NF533 Report Distribution

See Appendix C JSC DATA REQUIREMENTS LIST (DRL) based on JSC-STD-123. NASA policy requires Sensitive but Unclassified (SBU) data file types be encrypted prior to being uploaded/ sent to NASA. Any Sensitive but Unclassified (SBU) data requires the documentation clearly labeled as “Sensitive but Unclassified” and emails containing SBU data be encrypted.

NF533 Supplemental Reporting

Supplemental reporting requirements will be submitted during the course of the contract in accordance with direction in Appendix B.

Section J J-27 LFS

APPENDIX A. NF533 Format

Analyst will provide a sample NF533M for this contract that conforms to the required NF533M format in a separate attachment.

Section J J-28 LFS https://nodis3.gsfc nasa.gov/displayDir.cfm?Internal ID=N PR 9501 002E &page name=AppendixB

Section J J-30 LFS

1. What was the on-board total headcount for this contract as of September 30th? (Please include in-directs and an estimate for your major subcontractors.)

2. For the total workforce indicated in #1 above, approximately how many worked in the local [City, State] area?

3. What was the approximate dollar value of goods and services (including labor) purchased in [City] and the rest of

[State] under this contract during the prior Government Fiscal Year?

4. What was the approximate dollar value of goods and services (including labor) purchased in [City] and within the

State of [State]?

Section J J-37 LFS

Current Month Estimate Cost (8a)

Estimated costs for first upcoming month for given category.

Line item field— submitted with

CONTRACT

OR

data

Required. CUR_MONTH_EC 89 101 13 CURRENCY (2)

HR/WYE

Curren t Month

Estimated hours for first upcoming month for given category. Will only be needed if labor hours are required to be

Line item field— submitted with

CONTRACT

OR

Optional unless Required by contract for

WYE

HRWYE_CUR_MONT

H_EST

102 111 10 NUMERIC

(1)

Section J J-40 LFS

c. Engineering release and correlation of manufactured products.

d. Identification of design responsibility (use of CAGE code).

e. Assignment and application of configuration identifiers including document numbers, nomenclature, serial numbers, and part numbers to hardware, lot codes, software, and firmware identifiers.

f. Part marking, including marking to identify discrepant items and marking to identify flight like items that are not qualified for flight use.

3.0 Configuration Control - this section shall describe the sequence of events and milestones for implementation of CM/DM/RM during the contract phase in with major milestones and events including as a minimum:

a. Release and submittal of configuration documentation in relation to program events (e.g. technical reviews).

b. Establishment of internal configuration and contractual baselines.

c. Implementation of internal and NASA configuration control.

d. Establishment of configuration control boards and processes.

e. Identification of processes to document changes.

4.0 Configuration Status Accounting (CSA) - this section shall describe the Contractor’s processes for CSA:

a. Hardware and Software CSA processes and provisions for reports and/or access to CSA data.

b. Methods for collecting, recording, processing, and maintaining data necessary to provide contractual status accounting information via reports and/or data base access.

c. Description and methods of processes and tools to provide:

i. Identification of current approved configuration documentation and configuration identifiers associated with each CI.

ii. Status of proposed engineering changes from initiation to implementation.

iii. Waiver/deviation status and processing.

iv. Results of configuration audits; status and disposition of discrepancies.

v. Traceability of changes from baselined documentation.

vi. Effectivity and installation status of configuration changes to all CIs.

vii. Limited Life Items List.

d. Methods of access to information in status accounting information systems and/or frequency of reporting and distribution.

5.0 Configuration Verification/Audits - this section shall describe the contractor’s processes for

Section J J-41 LFS

Configuration Verification:

a. Processes, plans, documentation, and schedules for internal CM audits.

b. Format for reporting results of in-process configuration audits.

c. Methods used by the contractor to ensure its subcontractor(s) compliance with Configuration Management requirements.

6.0 Data Management - this section shall describe the Contractor’s part-centric product life- cycle management methods for meeting the Configuration Management technical data requirements:

a. Development, approval, release and submittal of configuration data/documentation (including drawings) in relation to program and contractual events (DRD's, Technical Reviews, FCA/PCA, Acceptance Reviews, COFR, etc.).

b. Plan for subcontractor data management deliveries/control access.

c. Establishment and operation of Engineering Release Unit and CM receipt desk.

d. Process for Documentation control (i.e., DCNs).

e. Retention of historical data.

f. Systems and tools.

The Flight Products Configuration Management Plan shall describe the process to be used for performing electronic configuration management of native files/models and data for each discipline and for subcontractors performing engineering, manufacturing, inspection, testing, procurement, and maintenance. The Configuration Management shall encompass the entire life cycle of the product.

Examples of disciplines and native files include but are not limited to the following:

a. Mechanical Design:

i. CAD Model (Pro/E Creo, Unigraphics, etc.)

b. Structural Analysis:

i. Pre & Post-process Finite Element Model (Patran, Ideas, etc.)

ii. Numerical Analysis input (NASTRAN, FEMAP, ANSYS, etc.)

iii. Manual Analysis (Excel, MathCAD, MATLAB, etc.)

c. Thermal Analysis:

i. Pre & Post-process (TSS, Thermal Desktop, Sinda/Fluint, etc.)

ii. Manual Analysis (Excel, MathCAD, MATLAB, etc.)

d. Power:

e. Electrical Design:

i. Circuit Board design (Altium, etc.)

f. Aerodynamic:

g. Aero thermal:

h. Validation, Verification, and Certification Testing:

The plan shall also describe the Configuration Management organization activities, processes, and systems to be employed to support the NASA change evaluation and control process for the approval. In addition, the plan shall describe the process for levying requirements on subcontractors and the monitoring of those

Section J J-42 LFS subcontractors. Also, the plan shall describe the contractor process for compiling, reviewing, and maintaining the Acceptance Data Package (ADP) in accordance with Acceptance Data Package Requirements Specification .DRD

TD-04.

Format: The Contractor’s format shall be within the environment associated with this data in the JSC Engineering Design Information Infrastructure (JEDII) (or equivalent). The Flight Products Configuration Management Plan shall be delivered in native format, and format and shall be compatible with the JSC standard software loads.

Submission: - Type 1

Initial - 10 days prior to contract start

Updates – review annually , update as required by review or directed by COR

Distribution: Default

Applicable Documents:

JPD 7123.1 JSC Configuration Management Policy JPR 8500.4: JSC Engineering Drawing System Manual

Section J J-45 LFS

10. Describe your responsibilities and requirements for planning and conducting audits (internal and external), and for reporting results and maintaining records.

11. Explain how you will be involved in waivers and deviations when quality assurance is affected.

12. Explain your methods for measuring the achievement of your quality objectives.

13. Explain the processes you will implement to report problems, corrective actions, and resolution verification to the designated NASA Quality Organization.

14. Explain your process for determining appropriate quality indices and measurements and reporting those to designated Quality organization in a timely fashion.

Format:

Contractor’s format in native format and compatible with standard JSC office software loads. (E.g. Microsoft Word or pdf)

Maintenance:

The plan shall be reviewed by the contractor annually and updated as needed or as directed by the contracting officer. All changes and updates to the Quality Plan shall be approved by NASA.

Submission and Distribution:

Distribution:

a. Initial – As specified in Proposal Instructions

b. Final - BH2/Contracting Officer; NT2/ Quality Assurance Branch; Contracting Officer’s Representative (COR)

c. Update - BH2/Contracting Officer; NT2/ Quality Assurance Branch; Contracting Officer’s Representative (COR)

Submission:

a. Initial: Due with Proposal

b. Frequency: Update as needed or as directed by the Contracting Officer

Ship to:

NASA Lyndon B Johnson Space Center 2101 NASA Pkwy Houston, TX 77058

Section J J-47 LFS

Deliverable Frequency Format

2. Mishap reporting and investigation involves mishap notification and response, reporting, investigating, and correcting negative findings that are discovered in its investigations. See NPR 8621.1 and JPR 1700.1. Report the following mishaps

a. Damage to hardware manufactured or handled on the contract

b. Type A, B, or C injuries to personnel on the contract that could affect hardware delivery.

Immediate notification within 24 hours of a mishap and follow-up with interim updates and final investigation results, to include causes and corrective actions. Identify which parts of the report are proprietary for business reasons or otherwise controlled for reasons of security

JSC Form (JF) 1627 to the Safety and Test Operations Division, the Contracting Officer, and the COR

3. Lessons Learned Report. Lessons learned are intended to prevent recurrence of undesirable events and involve uncommon insight arising from any event or observation that will benefit from sharing with a larger community of interested parties. Follow JPR 2310.1, JSC Organizational Learning Program.

Enter data into the JSC LLDB or NASA LLIS:

a. Within 30 days of a triggering event;

b. Within 30 days of a program milestone, mishap investigation, or hazard or other engineering analysis / evaluation is completed;

or

c. 30 days before end of contract evaluation period or 45 days before end of contract, whichever is applicable.

Database entry with 1 electronic copy to the Contracting Officer’s Representative (COR).

When onsite at a NASA Center, contractor personnel must follow the safety and health requirements of that Center.

Section J J-50 LFS

10) Verification that the prescribed disposition was acceptably completed; and

11) When applicable, a cross-reference to an associated PAR report.

FORMAT: The contractor's format for the record is acceptable. The product shall be in a Microsoft Office compatible format. For Payload Anomaly Reporting, record in IFI/PART database:

https://part.iss nasa.gov.

MAINTENANCE: Update as required. All dispositions other than rework will require NASA project approval. All records shall be available upon request.

Nonconformance reports, waivers, and deviations shall be reviewed quarterly with the NASA Procurement and Technical Teams. This may be included as part of the Project Management Review (PMR) topics or as standalone meetings.

SUBMISSION: As required per non-conformance

DISTRIBUTION: Each time a document is initiated, notification e-mails should be sent to the following distribution list:

• CO

• COR

• Technical Monitor

• Government Quality Assurance Representative

Section J J-52 LFS

4. Design Configuration Acceptability and Control: The plan shall address how the selected parts for a design are reviewed for application and environment suitability, how the parts quality and reliability will meet the operational performance requirements, and if the parts are being used within the specific device ratings (including the NASA derating policy). The selection process, technical acceptability of devices, and application documentation and review results shall be available to NASA to support hardware design reviews, certification, acceptance reviews, problem resolutions, and ground and flight operations. Key elements are as-designed-parts lists, application stress analyses (including radiation effects), and nonstandard parts acceptability assessments.

5. Parts Procurement: The plan shall address how the contractor will select, qualify, control, and monitor parts manufacturers. The plan shall address the contractor's source inspections, receiving inspection (including destructive physical analysis), and stocking and handling procedures prior to and during assembly. These procedures shall address how the contractor will mitigate the procurement and any subsequent installation of parts or "lots" of parts subject to conditions identified in GIDEP and NASA ALERT's. This section of the plan shall ensure that the selection and use of the parts will not have an "obsolescence" issue to the greatest extent possible.

6. Radiation Effects: The Parts Control Plan shall include the following requirements:

a. It shall be shown by test or analysis that Single Event Upset (SEU) and/or total dose radiation effects will not cause Electrical, Electronic, or Electromechanical (EEE) parts to fail or malfunction in such a manner as to cause a safety hazard or loss of a mission.

b. EEE parts that are used to control a hazard, or subsystems that control a hazard, shall be immune to the SEU and total dose radiation environment to which they will be exposed.

7. Commercial Off-The-Shelf (COTS) hardware: The plan shall address the use of COTS hardware for which insufficient parts information is available. In these cases, parts used in COTS hardware may be qualified by environmental and accelerated life testing of a complete COTS assembly.

8. Documentation: The plan shall define the contractor's electronic (preferred) or paper documentation system, data supporting milestone and design reviews, and NASA's access to the parts electronic data base and files.

FORMAT: Native format and compatible with standard JSC office software loads.

MAINTENANCE: As required.

Section J J-53 LFS

1. DRD Title 2. Date of current version

3. DRL

Line Item No.

RFP/Contract No.

(Procurement completes)

Flight Hardware Failure Analysis Report SQ-06

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one) To provide and document the detailed data generated during the testing and analysis of defective hardware.

Technical Administrative

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

8. Preparation Information (Include complete instructions for document preparation)

SCOPE:

The report documents the test and analyses conducted during an investigation of defective hardware to determine the root cause of the failure. It also records the Contractor's recommended corrective action required to prevent another occurrence of the same failure. Contractor analysis will be required for each failure resulting in a JSC PRACA (see DRD SQ-16).

CONTENT:

The report shall contain the following information as a minimum;

1. Description of when, where, and how the hardware failed, along with supporting evidence.

2. Documentation on how the hardware was transported to the vendor.

3. Documentation of how the hardware was received and processed by the vendor.

4. Documentation of tests performed and test results obtained to assess the failure.

5. Documentation of the analysis performed and results obtained to assess the failure.

6. Documentation on verification of the original certification data and any discrepancies found.

7. Method used to arrive at root cause of the failure.

8. Rationale used to arrive at recommended corrective action.

9. Plan for implementation and estimated cost of corrective action for the Contractor.

FORMAT:

The Contractor's format shall be used. The software used shall be compatible with Microsoft Word.

MAINTENANCE:

The report is updated as required.

Section J J-54 LFS

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

(Procurement completes)

Reliability and Maintenance plan (R&M) Plan SQ-07

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category:

(check one)

Establishes reliability and maintainability tasks and activities to implement qualitative and quantitative requirements associated with space flight hardware or software and related operations.

S&MA

Applicable documents on contract for this DRD are as follow:

ANSI/ESD S20.20-1999,Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices) EA-WI-023, Project Management of GFE Flight Projects EA-WI-025, GFE Flight Project Software and Firmware Development IPC 2221, Generic Standard on Printed Board Design IPC 2222, Sectional Design Standard for Rigid Organic Printed Boards IPC 6011, Generic performance Standards for Printed Boards IPC 6012, Qualification and Performance Specification for Rigid Printed Boards JSC 23642, JSC Fastener Integrity Program JSC 28035, Program Problem Reporting and Corrective Action (PRACA) Requirements for Johnson Space Center (JSC) Government Furnished Equipment (GFE) JSC 28484, Program Requirements Document for Johnson Space Center Non-Critical Government Furnished Equipment JSC 61360, Engineering Directorate Certified Parts Approval Process MF0004-400, Electrical, Electronic and Electromechanical Orbiter Project Parts Requirements JSC 49879, Johnson Space Center (JSC) Wire and Cable Integrity Compliance Program (Draft) NASA-STD-2201.93, Software Assurance Standard, (See Reference Documents) NASA-STD-8739.1, Workmanship Standard for Staking and Conformal Coating of Printed Wiring Boards and Electronic Assemblies NASA-STD-8739.3, Soldered Electrical ConnectionNASA-STD-8739.4, Crimping, Interconnecting Cables, Harnesses, and Wiring NASA-STD-8739.5, Fiber Optic Terminations, Cable Assemblies, and Installation NSTS 22206, Requirements for Preparation and Approval of Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL)

Reference Documents:

NPR 8705.4, Risk Classification for NASA Payloads NASA-STD-8739.8, Software Assurance Standard, 07/04 (superseded NASA-STD-2201.3)

SCOPE: This DRD establishes the requirements for content, format, and maintenance of the Reliability and Maintainability Program Plan (RMPP), which is used for controlling risk and enhancing reliability flight and critical ground support equipment.

CONTENTS: The RMPP shall be developed for the contract to plan, establish, document, and implement:

(1) System R&M design and operational performance requirements (qualitative and quantitative).

(2) System maintenance concepts.

(3) Requirements and tasks for R&M engineering, analysis, and testing (including hardware, software, firmware, and human elements).

(4) Timely and continuous assessment of the progress toward achieving the R&M requirements, including identification of areas for improvement.

(5) Integration of R&M processes and analytical activities with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance.

Section J J-55 LFS

1.0 General. The RMPP shall be documented in narrative format and shall:

1.1 Describe the scope of the R&M engineering activity for the contract.

1.2 Describe any interrelationships to other contract requirements, tasks and functional elements including appropriate cross references to minimize duplication.

1.3 List the contractor and NASA documents which will be applied either as directives or as guidance in the conduct of the RMPP.

2.0 Reliability and Maintainability Engineering Organization. The RMPP shall describe:

2.1 The R&M organization or function within the organization of the contract including charts to show the organizational and functional relationships and lines of communication.

2.2 The responsibility, authority, and accountability of R&M personnel and other contractor organizational elements (including subcontractors) involved in the R&M effort. Identify the authority in regard to resolution of all identified nonconformances. Include the title, address, and telephone number of the R&M Program Manager.

2.3 The procedures by which the contractor will integrate and coordinate the R&M efforts. Include methods of dissemination of R&M requirements to action organizations and subcontractors; coordination of subcontractors' R&M programs; reporting requirements; and the identities and charters of any R&M groups.

2.4 The interfaces between the R&M organization and all other applicable disciplines such as Engineering, Occupational Safety and Health, and Quality Assurance.

3.0 Reliability and Maintainability Requirements. The RMPP shall describe:

3.1 The methods that will be used to identify and apply R&M requirements and criteria for the design and operation of flight equipment and software and facilities specifically required to support flight missions (e.g., SAIL).

3.2 The qualitative or quantitative measures of R&M required by the contract.

3.3 The management controls used to ensure compliance with requirements or justify waivers and deviations of flight hardware or software of critical ground support equipment.

4.0 Reliability and Maintainability Analyses. The RMPP shall describe the analysis techniques and format to be used in qualitative and quantitative analysis.

5.0 Reliability and Maintainability Data. The RMPP shall:

5.1 Describe the approach for researching, disseminating, and analyzing pertinent R&M data.

5.2 Identify deliverable R&M data and the level of approval required for customer acceptance.

6.0 Verification & Validation and Audits. The RMPP shall describe:

6.1 The verification & validation and audit requirements and procedures for ensuring that the objectives and requirements of the R&M program have been adequately demonstrated and implemented.

6.2 The procedures for ensuring feedback of information for management and engineering review.

7.0 Training. The RMPP shall describe techniques and procedures to ensure that the objectives and requirements of the R&M program are implemented in training for contractor personnel.

FORMAT:

The plan shall be delivered in the contractor’s format. The plan shall be delivered to DDMS in native format, compatible with Microsoft Word.

MAINTENANCE:

Update as required. This plan shall be maintained in the DDMS.

Section J J-58 LFS

1. DRD Title 2. Current Version Date

3. DRL Line Item No.

RFP/Contract No.

(Procurement completes)

Reliability and Maintainability Predictions Report

SQ-11

4. Use (Define need for, intended use of, and/or anticipated results of data)

To document the reliability and maintainability data and analysis that will be used to meet the applicable Systems Requirements Document in support of design analysis, reliability, testing, availability, maintainability, and supportability analysis using quantitative analyses.

5. DRD Category: (check one)

Administrative X S&MA

FMEA;CIL

8. Preparation Information (Include complete instructions for document preparation)

SCOPE:

Report shall consist of the Reliability and Maintainability predictions for flight hardware.

CONTENT:

The report shall consist of three volumes, as follows. Each volume may be submitted and approved independently.

The volumes may be further subdivided according to subsystem architecture and/or end items, as appropriate.

Volume I

1) General and programmatic information

2) Top-level ground rules and assumptions used in performing the R&M analyses.

Volume II

1) R&M source data in accordance with Table B1.

2) Failure Detection Isolation and Recovery Assessment Information (see Table B2).

3) Perform Preventative Maintenance Assessment per decision matrix (see Figure B1).

Volume III FMEA/CIL summary information GP 10025, including summary tables (index), list of critical items, and identification of incomplete design areas.

FORMAT:

See R&M Source Data field definitions in Table B1. R&M Source Data shall be submitted in an electronic table (see Table B3).

NEED DATE or MILESTONE REQUIRING R&M PREDICTIONS REPORTS SUPPORT:

The R&M Predictions Report data requirements applies to all flight hardware shall be delivered at the System Acceptance Review (SAR)

Section J J-60 LFS

B. Drawing/Part Number - R&M attributes shall be referenced to the Drawing/Part number in the VMDB.

R&M is not responsible to develop the Drawing/Part number but shall use it as a reference for reporting R&M parameters.

F. Reliability Class - Reliability classification. The six reliability class codes are as follows:

CODE DESCRIPTION

1 Electronic - equipment which primarily contains digital or low power analog electronics. Moving parts are high power electrical equipment normally constitute less than 5% of the item failure rate in the classification. Electronic type will typically have a fairly high level of Built-In-Testing (BIT).

2 Electrical - equipment which performs electrical power distribution, power storage, signal distribution, and/or radio frequency radiation functions. Moving parts or low power electronics normally constitute less than 5% of the item failure rate in this classification. Electrical types will typically have a low level of BIT.

3 Electro-Mechanical - equipment which contains electrical/electronic and mechanical parts, including devices which use electrical power to produce mechanical motion, and devices which use mechanical motion to produce electrical power or signals. Electro - Mechanical items should contain more than 5% electrical/electronic and more than 5% mechanical parts by failure rate contribution in this classification.

4 Mechanical - equipment which primarily consists of moving parts, fluid handling equipment(including thermal systems), and or seals. High power electrical equipment or low power electronics normally constitute less than 5% of the failure rate in this classification.

5 Structural with Crew Contact - equipment which is primarily structural but encounters planned crew contact or provides equipment protection. This type specifically includes doors, covers, panels, hatches, micro meteoroid/debris shields, and thermal blankets.

6 Structural with no crew Contact - equipment which is load bearing. Moving parts, electronics, and electrical equipment normally constitute less than 5% of the failure rate in this classification. Structural items should not normally encounter planned crew contact.

IVA/EVA/Robotics Code - The code which describes the level of robotic compatibility of the equipment. The codes are as follows:

CODE DESCRIPTION

0 Equipment located in pressurized area.

1 Equipment can be maintained only by EVA crew member. No robotic support is required or intended.

2 Equipment can be maintained using SPDM without EVA. Equipment is SPDM compatible.

Compatibility consists of Equipment to SPDM interface. EVA can provide maintenance support in a backup role.

3 Equipment can be maintained using SSRMS without EVA. Equipment is SSRMS compatible.

Compatibility consists of Equipment to SSRMS interface. Equipment must be equipped with SSRMS grapple fixture. EVA can provide maintenance support in a backup role.

4 Equipment requires combined SPDM/EVA operations for maintenance.

5 Equipment requires EVA crew member to be positioned on SSRMS for access to the worksite.

Equipment requires no robotic compatibility.

Section J J-61 LFS

6 Equipment requires the Mobile Servicing System/SSRMS for transportation to the EVA worksite.

Dimensions or mass of equipment to be replaced are not compatible with EVA/CETA translation.

Equipment must be equipped with SSRMS grapple fixture.

J MTBF - Mean Time Between Failures (“Hot” or “operating” MTBF). The estimated average time in hours between failures due to random effects under nominal operating conditions at the maintainable equipment level. Redundancy within the maintainable equipment item which is not necessary to meet failure tolerance requirements (e.g., component redundancy used for reducing maintenance demand) shall be modeled so as to improve the reported MTBF. Worst case estimates shall not be used.