J-1_Statement_of_Work.docx
DOCX document 39 KB Posted
- Solicitation number
- NNM16593644Q1
About this file
J-1 Statement of Work
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NEA_Scout_SRD_Change_List.docx | DOCX document | |
| System_Requirements_Document.docx | DOCX document | |
| SolicitationTerms_and_Conditions_NNM16593644Q1.docx | DOCX document | |
| J-2_Data_Procurement_Document.doc | DOC document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF WORK (SOW)
For
REACTION CONTROL SYSTEM (RCS) HARDWARE
FOR THE NEAR EARTH ASTEROID (NEA) SCOUT CUBESAT PAYLOADS
1.0 Background and Scope:
This Statement of Work supports the development for the acquisition, engineering research, design, modeling, testing, and manufacturing of a Reaction Control System (RCS) to support the Near Earth Asteroid (NEA) Scout cubesat secondary payloads for launch on Space Launch System (SLS) Exploration Mission (EM) – 1.
The NEA Scout cubesat will be deployed as a secondary payload on the SLS EM-1 flight. The NEA Scout RCS provides the thrust for the post-deployment correction maneuver and reaction control in the first weeks of the mission. Contractor shall comply and meet the NEA Scout RCS technical requirements for performance to achieve the required total impulse, volume, mass and delta-V required for mission success. Contractor shall provide detailed cost data related to materials, labor categories, hours, and tests required for the NEA Scout (Protoflight Unit cold gas RCS systems.
Design, modeling, testing, and manufacturing of an R236fa Reaction Control System (RCS) are needed to support the NEA Scout cubesat mission. In order to achieve the science mission of surveying a Near Earth Asteroid, NEA Scout requires an RCS that provides attitude control for initial de-spin and momentum management of reaction wheels as well as a propulsive maneuver capability to target a lunar flyby shortly after the spacecraft is deployed.
2.0 Requirements
2.1 Technical Requirements:
Below is a high level summary of technical requirements. Detailed technical requirements are in Attachment A “Systems Requirements Document for the NEA Scout Reaction Control System”. For any conflict between the summary below and Attachment A, Attachment A supersedes.
| - | The RCS must achieve a total impulse >= 500 Newton-seconds. The total impulse must be able to support a minimum 15 meters/sec delta-V thrusting in the direction of the spacecraft + Z axis. The RCS system attitude control must have a specific impulse ≥ 40 seconds. |
| - | The mass of the cubesat is limited to 14 kg based on the limit imposed by SLS and the cubesat dispenser provider. 2.5 kg of the 14 kg total mass is allocated to the RCS. |
| - | The volume is also constrained by the SLS to fit within a 6U cubesat deployer volume envelope. All hardware shall be compatible with the deep space environment and have an expected in-space life of 2.5 years. |
The Contractor shall provide the following in accordance with Attachment A:
1. Electronic control (“flat sat”) Engineering Development Unit (EDU).
2. Cold gas RCS protoflight unit.
3. Technical advisory support, on an as-needed basis to Jet Propulsion Laboratory (JPL) and Marshall Space Flight Center (MSFC) during integration of the propulsion system to the spacecraft, spacecraft-level environmental/functional testing, Phase 3 Safety Review, through delivery of the spacecraft to Kennedy Space Center (KSC). Not to exceed 250 hours.
2.2 Documentation Requirements
The Contractor shall provide the following in accordance with Appendices A, B, and C and Attachment J-2 as applicable:
1. Engineering drawings and associated list shall be delivered per Appendix B.
2. Verification reporting shall include all test data requested by NASA, test procedures, descriptions of instrumentation used for testing, test reports, reports of inspections and analysis reports. Verification reporting content appears in Appendix C.
3. Acceptance reporting shall include all test data requested by NASA, test procedures, descriptions of instrumentation used for testing, test reports, reports of inspections and analysis reports. Acceptance reporting content appears in Appendix A.
4. The Contractor shall report and document this work and fulfill the requirements of associated Data Requirements Description (DRD) as outlined in Data Procurement Document (DPD) 1593 (Attachment J-2). The contractor shall determine the data restriction that applies to each data deliverable and mark or transmit the data restriction in accordance with section 2.3.3 of the Data Procurement Document.
2.3 Reviews
The Contractor shall provide the following reviews:
1. Kick-Off Meeting The Contractor shall conduct a kick-off meeting to review requirements, design implementation, and proposed verifications within 3 weeks of award at the Contractor site.
2. RCS Long Lead Item Review The Contractor shall conduct a Long Lead Item Procurement Review for any item that requires initiation of procurements or manufacturing prior to the RCS Design Review (DR). Long lead item reviews are planned for electronics, thrusters, and any others and reference the schedule. This review shall be conducted via teleconference unless otherwise directed. If there are no long lead items, that information shall be communicated to NASA at the Kick-Off meeting.
3. RCS Design Review The contractor shall conduct a Design Review within 6 weeks of ATP. The RCS DR will ensure that the RCS design has met all of its requirements before hardware manufacturing commences. The DR review shall be held at the Contractor’s location.
4. NEA Scout Design Review The Contractor shall support the spacecraft-level NEA Scout Design Review to be conducted by MSFC. The Contractor shall provide the RCS design review package and provide input and updates as requested by NASA. If ATP occurs after the DR the contractor shall provide a Delta DR.
5. Launch Vehicle Safety Reviews The Contractor shall provide data inputs required to support the development by NASA/MSFC of the integrated NEA Scout safety package.
6. ProtofFlight Unit Pre-Ship Review The Contractor shall conduct a Pre-Ship Review to assure the design meets all validation requirements for environmental qualification and acceptance test prior to shipping for the hot-fire acceptance test. The Acceptance Review shall be held at the Contractor facility.
7. EEE Parts Selection The contractor shall provide an Electrical, Electronic and Electromechanical (EEE) parts list. MSFC will conduct assessments and provide radiation suitability recommendations based on the initial EEE parts list review. This list shall be due on or before the date of the Kick-Off Meeting.
2.4 Reporting
1. The Contractor shall provide NASA with weekly status reporting via ~ 30 minute telecons which shall include a written summary on a single quad chart, format to be provided by the Government. Additional charts and presentations may be included at the discretion of the Contractor.
2. The Contractor shall be responsible for maintaining communication with NASA Technical Representatives and alerting the Contracting Officer (CO) immediately of any problems that would prevent meeting established milestones.
3. The contractor shall provide technical information concerning any invention, discovery, improvement, or innovation made by the contractor in the performance of work under this contract. Technology Reports shall be prepared in accordance with DRD 1593CD-001.
4. The contractor shall prepare and submit the Environmental Compliance Reports that complies with Executive Order 13693 in accordance with DRD 1593EE-001.
5. The contractor shall report mishaps and safety statistics to the MSFC Industrial Safety Branch in accordance with DRD 1593SA-001. The contractor shall submit directly into the NASA Mishap Information System (NMIS) or shall use the forms listed in section 15.4 of DRD 1593SA-001or electronic equivalent to report mishaps and related information required to produce the safety metrics.
3.0 Partial Payment Schedule
Schedule invoicing shall be based on the following from date of award. Upon meeting milestones, invoicing terms due 30 days of a proper invoice is submitted to NSSC for payment.
1. Milestone: Deliver project schedule including dates of delivery of electronic control EDU, qualification unit and flight unit. Expected completion date is one week after Authority to Proceed (ATP).
2. Milestone: Deliver Design Review package and conduct Design Review. The scheduled lead-time is 6 weeks after ATP.
3. Milestone: Deliver electronics control EDU and associated documentation. The scheduled lead time is 2 months after ATP.
4. Milestone: Deliver qualification verification items other than protoflight qualification test data. The scheduled lead-time is 6 months after ATP.
5. Milestone: Deliver protoflight unit all protoflight qualification test data and all acceptance verification items. The lead-time is on or before May 31, 2017.
4.0 Period of Performance
The POP for this effort is ATP through August 10, 2021.
Appendix A: Content of Acceptance Data Package An Acceptance Data Package (ADP) for hardware contract configuration items shall contain the current log book that includes:
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.
6. As-Built Parts List
7. As-Designed Parts List
i. Verification compliance matrix and Verification/Validation Reports. Verification/Validation Reports shall contain the following:
1. Conclusions and recommendations relative to success of the verification/validation activity.
2. Concurrence by the appropriate discipline (e.g. safety, thermal, structures, etc.).
3. Description of deviations from nominal results, failures, approved corrective actions and procedures, and retest.
4. Traceability back to the requirement and/or verification/validation success criteria.
5. Traceability back to the requirement and/or verification/validation success criteria.
6. Identification of test configuration and any differences from the flight configuration.
7. Specific results of each procedure including automated test segments, each analysis, or other verification/ validation activity.
8. Performance data, telemetry files, plots, and pictures (as appropriate).
9. Models used in analysis.
j. The Limited Life Items List shall contain the following for those items identified as time, cycle, or age sensitive:
1. Name of item.
2. Lot number and Part number.
3. Allowable time and/or cycles and age permitted.
4. Accumulated time and/or cycles at time of shipment.
5. Required time and/or cycles and age that must be remaining prior to conducting each major milestone test and launch.
6. Action required at end of life (e.g., remove and replace, calibrate, inspect, etc.).
Appendix B: Engineering Drawings and Associated List
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:
| ASME Y14.100 | Engineering Drawing Practices |
| ASME Y14.41 | Digital Product Definition Data Practices |
| ASME Y14.5M | Dimensioning and Tolerancing |
| MIL-STD-130M | Department of Defense Standard Practices, Identification Marking of U.S. Military Property |
| NASA-STD-6002 | Applying Data Matrix Identification Symbols on Aerospace Parts |
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.5M. 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: |
| (a) | Details of unique processes (i.e., not published or generally available to industry) when essential to design and manufacture. |
| (b) | Performance ratings. |
| (c) | Dimensional and tolerance data (Geometric Dimensioning and Tolerancing (GDT) shall be required between all external and major internal interfaces). |
| (d) | Critical manufacturing processes and assembly sequences, and rigging procedures. |
| (e) | Diagrams. |
| (f) | Mechanical and electrical connections. |
| (g) | Physical characteristics, including form and finish. |
| (h) | Details of material identification, including heat treatment and protective coatings. |
| (i) | Inspection, test, and evaluation criteria. |
| (j) | Equipment calibration requirements. |
| (k) | Quality assurance requirements. |
| (l) | Hardware marking requirements. |
| (m) | 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 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. |
| 5. | The Fluid system schematic shall illustrate and describe all components with symbols and flow designators such that the fluid system may be traced from component to component (such as pumps, valves, meters, regulators, and filters). The schematics shall document the range requirements (flow, temperature, and pressure) for all component external interfaces and line sizes. The placement and arrangement of these components shall follow a logical sequence of presentation to provide a clear description of the flow of fluids in the system. The schematics shall reference engineering drawings and associated lists for configuration details. |
c. Engineering drawing shall specify marking criteria and methods for identification of parts produced or procured. Markings shall meet criteria of NASA-STD-6002. Final Assembly 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. However, the Data Matrix Symbol format shall be used for Machine Readable Identification on paper labels and tagging.
| 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. |
| e. | 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 file format. The corresponding 2D and 3D CAD models shall be submitted in SolidWorks (native format) or STEP file format. Originator format is acceptable for drawing trees. Alternate formats may be acceptable upon negotiation. All documentation/data shall include the contractor's CAGE code and document numbers.
Appendix C: Verification Planning
Verification Planning: The contractor shall develop, document, and implement a verification and validation program that confirms the deliverable product is in compliance with requirements and is ready for a particular use, function, or mission. The following six tasks shall be performed as part of a comprehensive and thorough verification and validation program:
a. The identified product’s set of requirements or specifications shall be the basis of the verification and validation program. Each requirement shall have a corresponding verification/validation requirement(s) that identifies how the requirement will be met. The verification/validation requirements shall be developed and documented in using SE-VVREQ as a guideline.
b. Verification/Validation planning shall be developed that provides more details and discussions of the identified verification/validation activities and provides an overview approach of the overall verification/validation program. The verification/validation planning shall be developed and documented using SE-VVPLAN as a guideline.
c. Each of the planned verification/validation activities shall have success criteria developed to determine if the activity was successful. The verification/validation success criteria shall be developed and documented using SE-VVSC as a guideline.
d. Verification/Validation procedures shall be developed to define the detail instructions for conducting those verification/validation activities pertaining to tests, inspections, and demonstrations. The verification/ validation procedures shall be developed and documented using SE-VVPROC as a guideline.
e. The verification/validation reports shall report the results of the planned activities with respect to the identified success criteria. The verification/validation reports shall be developed and documented using SE-VVREP as a guideline.
f. Determining the product’s ability to meet the set of requirements and readiness for a particular use, function, or mission shall be based on the assessment of the verification/ validation report(s). The verification/validation compliance assessment which identifies and correlates the submitted reports against the products’ set of requirements shall use SE-VVC as a guideline.
Verification/Validation Requirements (VVREQ):
SCOPE: The Verification/Validation Requirements (VVREQ) information identifies the method(s) (e.g., test, analysis, inspection, etc.), level(s) (e.g., component, subsystem, system), and phase(s) (e.g., qualification, acceptance) of the verification/validation to be performed to satisfy each of the requirements (e.g., SRD, CEI, IRD, EIS, etc.).
APPLICABLE DOCUMENTS: None
CONTENTS: The Verification/Validation Requirements (VVREQ) information shall include the following:
| a. | Identification of the method(s) (e.g., test, analysis, inspection, etc.) in which the verification/ validation is performed to satisfy each of the requirements. |
| b. | Identification of the level(s) (e.g., component, subsystem, system) at which the verification/ validation is performed to satisfy each of the requirements. |
| c. | Identification of the phase(s) (e.g., qualification, acceptance) during which the verification/ validation is performed to satisfy each of the requirements. |
Verification/Validation Planning (VVPLAN)
SCOPE: The Verification/Validation Planning (VVPLAN) information provides a detail description of the project’s verification/validation approach and structure for implementing the verification/ validation program, as well as detail descriptions for the planned verification/ validation requirements. The Verification/Validation Plan will address both hardware and software efforts. Software verification/validation planning requirements are contained in NPR 7150.2.
APPLICABLE DOCUMENTS:
NPR 7150.2 NASA Software Engineering Requirements
CONTENTS: The Verification/Validation Planning (VVPLAN) information shall include the following:
| a. | Overview of the project’s verification/validation program (i.e., qualification/acceptance vs. proto-flight, verification/validation of spares, refurbishment/re-verification/ revalidation plans). |
| b. | Description of the project’s organizational structure for implementing the verification/ validation program (i.e., organization’s involved in component vs. system tests, review and signoff authority for compliance data). |
| c. | Detail preliminary descriptions of all verification/validation activities (i.e., tests, analyses, inspections, etc.) to be performed based on the identified verification/validation requirements. Identify any prerequisites, constraints, and objectives for all the verification/ validation activities. |
| d. | Detail time correlated sequence of verification/validation activities. |
| e. | Description and planned usage of the support equipment, software, facilities, and tooling necessary to execute the verification/validation activities. |
Verification/Validation Success Criteria (VVSC)
SCOPE: The Verification/Validation Success Criteria (VVSC) information establishes the detail success criteria for each of the activities identified in the verification/validation planning.
APPLICABLE DOCUMENTS: None
CONTENTS: The Verification/Validation Success Criteria (VVSC) information shall establish:
| a. | Detail success criteria (i.e. test limits, tolerances, specifications, margins) used in determining acceptability of the results of each verification/validation activity. |
| b. | Detail constraint criteria associated with performing the verification/validation activity or on the results of each verification/validation activity. |
Verification/Validation Procedures (VVPROC)
SCOPE: The Verification/Validation Procedures (VVPROC) define the detail instructions to be followed in conducting the identified verification/validation activities (test, inspection, or demonstrations).
APPLICABLE DOCUMENTS: None
CONTENTS: Each Verification/Validation Procedure (VVPROC) shall contain the following:
| a. | Identification of item/article being subjected to test, inspection, or demonstrations. |
| b. | Identification of objectives established for the particular test, inspection, or demonstrations. |
| c. | Characteristics and criteria to be verified, including values, with tolerances, for acceptance or rejection and traceability back to the applicable verification success criteria. |
| d. | Description of steps and operations, in sequence, to be taken. |
| e. | Identification of measuring and recording equipment to be used, specifying range, accuracy, and type and any special instructions for operating such equipment. |
| f. | Confirmation that required support equipment has been calibrated and certification of the calibration is still valid. |
| g. | Identification that any support equipment has been verified prior to use with flight hardware. |
| h. | Layouts, schematics, or diagrams showing identification, location, and interconnection of item/article, support equipment, and measuring equipment. |
| i. | Identification of hazardous situations or operations. |
| j. | Precautions and safety instructions to ensure safety of personnel and prevent degradation of verification article and supporting equipment. |
| k. | Environmental and/or other conditions to be maintained with tolerances. |
| l. | Constraints on test, inspection, or demonstration. |
| m. | Instructions for handling non-conformances and anomalous occurrences during activity. |
Verification/Validation Reports (VVREP)
SCOPE: The Verification/Validation Reports (VVREP) (e.g., as-run procedure, memo, assessment, test report, inspection report, analysis, etc.) identifies the data that documents the results of each individual verification/ validation activity.
APPLICABLE DOCUMENTS: None
CONTENTS: The Verification/Validation Reports shall contain the following:
| a. | Conclusions and recommendations relative to success of the verification/validation activity. |
| b. | Concurrence by the appropriate discipline (e.g. safety, thermal, structures, etc.). |
| c. | Description of deviations from nominal results, failures, approved corrective actions and procedures, and retest. |
| d. | Traceability back to the requirement and/or verification/validation success criteria. |
| e. | Copy of as-run procedure (as appropriate). |
| f. | Identification of test configuration and any differences from the flight configuration. |
| g. | Specific results of each procedure including automated test segments, each analysis, or other verification/ validation activity. |
| h. | Performance data, plots, and pictures (as appropriate). |
| i. | Models used in analysis. |
Verification/Validation Compliance (VVC) Assessment (VVC)
SCOPE: The Verification/Validation Compliance (VVC) Assessment identifies and assesses the submitted verification/validation reports associated with satisfying each requirement.
APPLICABLE DOCUMENTS: None
CONTENTS: The Verification/Validation Compliance (VVC) Assessment shall contain the following:
| a. | Identification of the requirement(s) to be satisfied. |
| b. | Identification of the verification/validation requirements associated with each of the requirements. |
| c. | Identification and traceability of the verification/validation reports to each of the requirements. |
| d. | Assessment of the verification/validation reports to determine compliance/non-compliance. |
| e. | Identification of any non-conformances (e.g. waivers, deviations, discrepancy reports) against each of the requirements. |
NASA MSFC Technical POCs:
EV42: Andy Heaton, NEA Scout Guidance and Control Lead Guidance, Navigation & Mission Analysis Branch (EV42) andrew.f.heaton@nasa.gov Office: (256) 544-3839
FP30: Leslie McNutt, NEA Scout Program Manager Exploration & Space (FP30) Transportation Development Office Leslie.mcnutt@nasa.gov Office: (256) 544-1611 Cell: 256-412-7574
J-1-2
File details come from the government source that posted it. Updated .