PACE-GNC-SOW-0064A_06-05-2018.pdf
PDF 1020 KB Posted
- Attached to
- Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) Star Sensor System Federal contract opportunity
- Solicitation number
- 80GSFC18R0045
About this file
Statement of Work
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Questions_and_Responses_Set_1.pdf | ||
| Amendment_01_to_80GSFC18R0045.pdf | ||
| PACE_STS_Solicitation_Final.pdf | ||
| STS_RFP_letter.pdf | ||
| PACE_STS_SpecComplianceMatrix-2018-06-15.pdf | ||
| SF26.pdf | ||
| Past_Performance_Questionnaire_-Star_Sensor_System.pdf | ||
| PACE-GNC-SPEC-0064B_06-18-2018.pdf | ||
| PACE_ST_DRAFT_SPEC_4-12-18).pdf | ||
| PACE-GNC-_DRAFT_SOW-0034-4-12-18.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PACE Star Sensor System SOW PACE-GNC-SOW-0034, Revision A
Effective Date: June 6, 2018 ii Check https://ipdtdms.gsfc nasa.gov to verify that this is the correct version prior to use
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) Mission Star
Sensor System Statement of Work
Signature/Approval Page
Prepared By:
Linh Nguyen
Reviewed By:
Gary Davis
Beth Weinstein
Nikesha Davis
George Bertholdt
Jaime Eitnier
Craig Stevens
Dave Sohl
Approved By:
Andre’ Dress
Electronic Signatures available online at: https://ipdtdms.gsfc.nasa.gov/ iii
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Preface
This document is under Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) Mission configuration control. Changes to this document require prior approval of the PACE
Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the PACE Configuration Management Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.
iv
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Change History Log
Revision Effective
Date
Description of Changes
(Reference the CCR & CCB/ERB Approval Date)
Revision - 5/01/2018 Baseline Release following the approval of PACE-CCR-0292
Revision A 6/01/2018 Updated following the approval of PACE-CCR-0363 v
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
Table of TBDs/TBRs/TBSs
Action Item
No.
Location Summary Individual/
Organization
Actionee vi
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
Table of Contents
1.0 Introduction
1.1 General Information
1.2 Scope
2.0 Applicable Documents
3.0 Management, Reporting, Reviews, and documentation
3.1 Program management
3.2 Reporting
3.3 Advanced Notifications
3.4 Reviews And Meetings
3.4.1 Kick-off Meeting
3.4.2 Design Conformance Review (DCR)
3.4.3 Pre-Environmental Review (PER)
3.4.4 Pre-Ship Review (PSR)
3.4.5 Technical Interchange Meetings (TIM)
3.5 Documentation
3.6 NA
3.7 Existing Components
3.7.1 Existing Documentation and Analysis
4.0 Design And Analysis
4.1 Interface Control Documentation
4.2 Drawing Package
4.3 Computer Models
4.3.1 CAD Model and Documentation
4.4 Structural Analysis Report
4.5 Structural Finite Element Model
4.6 Thermal Analysis Report
4.7 Thermal Model and Documentation
4.8 Worst Case Circuit Analysis Report
4.9 Parts Stress Analysis Report
4.10 Radiation Hardness Analysis Report
4.11 Reliability Analysis Report
4.12 Failure Modes And Effects Criticality Analysis Report
Table 4-1 FMEA Severity Categories
4.13 Error Analysis Report
4.14 Stray Light Analysis Report
4.15 User/Instruction Manuals
4.16 Night Sky test Report
5.0 Hardware Procurement/Manufacturing
5.1 General Requirements
5.2 STAR SENSOR System
5.3 Connector Savers
vii
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
5.4 Supporting Hardware
5.5 Ground Support Equipment
6.0 Performance Verification And Test
6.1 Verification Plan
6.2 Verification Test Procedures
6.3 Verification Test Reports
7.0 Quality Assurance
7.1 General Requirements
7.1.1 Quality Assurance Plan/Manual
7.1.2 Surveillance of the Contractor
7.1.3 Anomaly Reporting
7.1.4 Configuration Management
7.1.5 Ground Support Equipment Interfaces
7.2 System Safety Requirements
7.3 Reliability Requirements
7.3.1 Stability Trending
7.3.2 Limited-Life Items
7.3.3 Control of Sub-Contractors and Suppliers
7.4 Software Quality Requirements
7.4.1 General Requirements
7.4.2 Software Safety
7.4.3 Software Reliability
7.4.4 Software Management Reviews
7.4.5 Surveillance of Software Development, Maintenance, and Assurance Activities .. 26
7.4.6 Software Assurance Status Report Verification and Validation
7.5 Design Verification Requirements
7.5.1 Verification Requirements
7.5.2 Analysis, Trending, and Reporting of Test Data
7.5.3 Total and Failure-Free Operation hours
7.6 Workmanship Standards And Processes
7.6.1 General
7.6.2 New or Advanced Packaging Technologies
7.6.3 Workmanship: Use of Alternate Workmanship Standards
7.6.4 Electrostatic Discharge Control Requirements
7.6.5 Training and Certification of Contractor Personnel
7.6.6 Hardware Handling, Cleaning and Packaging
7.6.7 Splices, Circuit Board Trace Cuts, and Jumper Wires
7.6.8 Printed Circuit Board (PCB) Test Coupons
7.6.9 Use of Water Soluble Flux
7.6.10 Lead-Free and Tin Whisker Control Measures
7.7 EEE Parts Requirements
7.7.1 General
7.7.2 Plastic Encapsulated Microcircuits (PEMs)
7.7.3 Radiation Hardness
viii
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
7.7.4 Parts Age Control
7.7.5 GIDEP Alerts and Problem Advisories
7.7.6 Reuse of Parts and Materials
7.7.7 Part Notification of Failure
7.7.8 FPGA Programming Stations
7.8 Materials, Processes Requirements
7.8.1 Materials and Processes Control
7.8.2 Commercial-Off-The-Shelf (COTS), Vendor-Designed and Fabricated, and
Bilateral Agreement Furnished Hardware
7.8.3 M&P Usage Documentation
7.8.4 Materials Usage Agreements (MUAs)
7.8.5 Detailed Requirements
7.8.5.1 Flammability Control (NASA-STD-6016 Section 4.2.1.1)
7.8.5.2 Toxic Offgassing (NASA-STD-6016 Section 4.2.1.2)
7.8.5.3 Fluid Compatibility (NASA-STD-6016 Section 4.2.1.3)
7.8.5.4 Oxygen Compatibility (NASA-STD-6016 Section 4.2.1.4)
7.8.5.5 Electrical Wire Insulation Materials (NASA-STD-6016 Section 4.2.1.5)
7.8.5.6 Titanium (NASA-STD-6016 Section 4.2.2.3)
7.8.5.7 Tin (NASA-STD-6016 Section 4.2.2.11)
7.8.5.8 Polyvinylchloride (NASA-STD-6016 Section 4.2.3.2)
7.8.5.9 Composite Materials (NASA-STD-6016 Section 4.2.3.3)
7.8.5.10 Limited-Life Items (NASA-STD-6016 Section 4.2.3.5)
7.8.5.11 Thermal Vacuum Stability (NASA-STD-6016 Section 4.2.3.6)
7.8.5.12 External Environment Survivability (NASA-STD-6016 Section 4.2.3.7)
7.8.5.13 Glycols (NASA-STD-6016 Section 4.2.3.9)
7.8.5.14 Adhesive Bonding (NASA-STD-6016 Section 4.2.4.3)
7.8.5.15 Nondestructive Evaluation (NDE) Plan (NASA-STD-6016 Section 4.2.5.1)
7.8.5.16 Sandwich Assemblies (NASA-STD-6016 Section 4.2.6.2)
7.8.5.17 Fastener Installation (NASA-STD-6016 Section 4.2.6.5)
7.8.5.18 Contamination Control (NASA-STD-6016 Section 4.2.6.6)
7.8.5.19 Packaging (NASA-STD-6016 Section 4.2.6.7)
7.8.5.20 Shelf-Life Items
7.8.5.21 Printed Wiring Boards (PWBs)
7.8.5.22 Solder Flux
7.8.5.23 Fasteners with LL Longitudinal Locking Elements
7.8.5.24 Gold-Indium Intermetallic
7.8.6 Materials Procurement Requirements
7.9 Contamination Control Requirements
7.9.1 Contamination Control Plan
7.9.2 Surface Cleanliness
7.9.3 Material Outgassing
7.9.4 Thermal Vacuum Bakeouts
7.10 METROLOGY
7.10.1 Use of Calibrated and Non-calibrated Instruments
ix
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
8.0 Handling, Storage, Packaging, Preservation, and Delivery
Appendix A. Abbreviations and Acronyms Appendix B. GSFC PCB submittal and Material Selection Forms Appendix C. List of Applicable Documents
List of Tables
Table Page
Table 4-1 FMEA Severity Categories
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
1.0 INTRODUCTION
1.1 GENERAL INFORMATION
The Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) mission is a strategic climate continuity mission that was defined in the 2010 document Responding to the Challenge of Climate and
Environmental Change: NASA’s Plan for Climate-Centric Architecture for Earth Observations and Applications from Space (referred to as the “Climate Initiative”). The Climate Initiative complements NASA’s implementation of the National Research Council’s Decadal Survey of
Earth Science at NASA, NOAA, and USGS, entitled Earth Science and Applications from
Space: National Imperatives for the Next Decade and Beyond.
PACE will extend the high quality ocean ecological, ocean biogeochemical, cloud, and aerosol particle data records begun by NASA in the 1990s, building on the heritage of the Sea-Viewing
Wide Field-of-View Sensor (SeaWiFS), the Moderate Resolution Imaging Spectroradiometer
(MODIS), the Multi-angle Imaging SpectroRadiometer (MISR), and the Visible Infrared
Imaging Radiometer Suite (VIIRS). The mission will be capable of collecting radiometric and polarimetric measurements of the ocean and atmosphere, from which these biological, biogeochemical, and physical properties will be determined. PACE data products will not only add to existing critical climate and Earth system records, but also answer new and emerging advanced science questions related to Earth’s changing climate.
PACE is classified as a Category 2 mission, per the criteria in NASA Procedural Requirement
(NPR) 7120.5E, NASA Space Flight Program and Project Management Requirements. The mission classification is C according to NPR 8705.4B, Risk Classification for NASA Payloads.
The PACE observatory is comprised of three instruments, an Ocean Color Instrument (OCI) and two Polarimeters (HARP2 and SPEXOne). The OCI is the primary instrument on the observatory and is being developed at GSFC. The OCI is a hyper-spectral scanning (HSS) radiometer designed to measure spectral radiances from the ultraviolet to shortwave infrared
(SWIR) to enable advanced ocean color and heritage cloud and aerosol particle science. The
Polarimeters are second instruments on the PACE observatory, developed outside of GSFC.
Both Polarimeters are multi-band, multi-angle polarimeters planned to measure spectral polarized and unpolarized radiances to enable advanced cloud and aerosol particle science, as well as improved atmospheric correction for ocean color activities. This three-instrument PACE mission has the following multiple scientific goals:
Extending key systematic ocean biological, ecological, and biogeochemical climate data records and cloud and aerosol climate data records;
Making global measurements of ocean color data products that are essential for understanding the global carbon cycle and ocean ecosystem responses to a changing climate;
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Collecting global observations of aerosol and cloud properties, focusing on reducing the largest uncertainties in climate and radiative forcing models of the Earth system; and, Improving our understanding of how aerosols influence ocean ecosystems and biogeochemical cycles and how ocean biological and photochemical processes affect the atmosphere.
The PACE satellite is planned for a launch in 2022-2023. The PACE project office at the NASA
Goddard Space Flight Center (GSFC) is responsible for the satellite development, launch and operations. The mission is planned for launch into a Sun synchronous polar orbit at 676.5 km with an inclination of 98° and a 1 pm local ascending node crossing time. The spacecraft bus will host the OCI, HARP2, and SPEXOne instruments. The GSFC PACE Project office will oversee the mission and the development of the satellite, launch vehicle, mission operations control center, and operations. The Headquarters Program Science will separately fund the science data processing system and competed science teams, which will include field-based vicarious calibration and data product validation efforts to support the Project science team.
NASA Headquarters has directed the mission development to be guided by a Design-to-Cost
(DTC) process. All elements of the mission, other than the cost, are in the DTC trade space. At the heart of the DTC process are the mission studies, performed across all the mission elements.
The mission studies will be used to define appropriate approaches within and across elements while maximizing science capabilities at a high cost confidence. Mission baseline requirements development is also embedded within the DTC process, as these requirements were not established at the onset of the mission concept development. Baseline mission requirements will be a product of the mission studies and will be defined by the project office as part of the DTC process.
The PACE mission consists of four major segments: space segment (SS), ground segment (GS), science data segment (SDS), and the launch segment (LS).
The space segment consists of the spacecraft bus, the OCI, and the two polarimeters. The spacecraft and OCI are being developed and integrated at GSFC. The polarimeters are planned to be procured outside of GSFC. The spacecraft and instruments will be integrated as the PACE observatory at GSFC.
The GS and associated Mission Operations Center (MOC) will be developed, integrated, and operated at GSFC. The GS provides for the command and control and health and safety monitoring of the PACE observatory on-orbit, as well as ensuring the science data are accounted for and delivered to the SDS. The MOC will contain the flight operations team (FOT) and is being managed by the PACE project through observatory commissioning. After commissioning, the FOT will be managed by the GSFC Earth
Science Mission Operations (ESMO) office. The MOC performs all real time operations and off-line operations functions, including planning and scheduling, orbit and attitude
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
analysis, housekeeping telemetry data processing, monitoring/managing the spacecraft and instruments, first line health/safety for the instruments, and housekeeping archiving and analysis.
The SDS will be located at GSFC, but managed (separately from the project) by the
NASA Headquarters Earth Sciences Division. The SDS will ingest, apply calibration and science algorithms, and process the science data, provide science software development and algorithm integration, act as the science data interface to the science team, and deliver of all science data products to the NASA-assigned Distributed Active Archive
Center (DAAC).
The LS is planned for a launch vehicle to be selected and procured by the NASA Launch
Services Program at Kennedy Space Center (KSC).
In addition to utilizing GSFC institutional capabilities, the project will utilize the NASA/GSFC institutional capabilities such as the Flight Dynamics Facility (FDF), Near Earth Network
(NEN), Ocean Biology Processing Group (OBPG), Space Network (SN), and NASA Integrated
Services Network (NISN). PACE plans to generate 3.5 Terabits of science data daily. The data are downlinked from the observatory during 12-14 daily contacts via Ka-band communications to the NEN's ground stations. The observatory will also receive ground commands and transmit real-time housekeeping telemetry via a S-band 2-way link through the NEN during nominal operations. The observatory also has the capability of receiving ground commands and transmitting real-time housekeeping telemetry, via S-Band, through the SN during critical or contingency operations.
This document defines the work to be performed by the Contractor in the design, development, fabrication, and delivery of the PACE Star Sensor System, from here on referred to as the STS
System.
1.2 SCOPE
The contractor shall provide the facilities, personnel, services, tools, equipment, and materials necessary to design, analyze, manufacture, test, and deliver the hardware and data in accordance with the requirements of this SOW and the documents referenced herein.
This SOW defines the contractor tasks, deliverables, responsibilities, and schedule, either within this document or by reference. More details for the deliverables and the schedule can be found in the RFP Section B.2 Table. In this document, specific deliverables from that table are referenced with “(DIL #row_number).”
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
2.0 APPLICABLE DOCUMENTS
All applicable and reference documentation identified in this document shall apply in the situations where they are specifically referenced. In the event of a conflict between the SOW and the specification, the SOW shall take precedence. See Appendix C for applicable documents.
There are many applicable documents (standards, procedures, etc.) throughout this SOW. The expectation is suppliers will be compliant with the requirements within those documents.
However, we recognize often comparable documents may be used in lieu of those listed herein.
The alternative documents will be evaluated for compliance and approval is required prior to usage.
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
3.0 MANAGEMENT, REPORTING, REVIEWS, AND DOCUMENTATION
3.1 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 and cost constraints.
The contractor shall designate and identify by name a single individual who shall serve as a point of contact with the NASA/GSFC Contracting Officer’s Representative (COR) for all technical aspects of the STS System contract.
The contractor shall establish and apply a program control system for managing all resources, controlling schedules, managing all engineering, manufacturing and procurement activities, configuration management, Quality Assurance, documentation control, and distribution.
3.2 REPORTING
The contractor shall prepare and present to the NASA/GSFC COR monthly technical status reports via telecon and a written report. (DIL #2) The report shall be a summary presentation of the period's progress to include topics such as schedule overview, accomplishments, technical performance measures (e.g. mass and power), status of key milestones, risks, problem areas, challenges/issues and activities on-going and planned.
3.3 ADVANCED NOTIFICATIONS
The contractor shall notify the NASA/GSFC COR at least seven (7) calendar days in advance of all mandatory hardware inspections, test activities, TIM’s, and deliveries at either the contractor’s or a sub-contractor’s facility to allow timely participation by the NASA/GSFC
Quality Assurance representative. (DIL #4) Event specific notification requirements (such as failures, anomalies, etc.) are included in the appropriate sections.
3.4 REVIEWS AND MEETINGS
3.4.1 Kick-off Meeting
The Contractor shall organize and hold a Kick-off Meeting at the Contractor’s facility prior to any activity identified in this SOW. (DIL #5)
The Contractor shall provide to the NASA/GSFC COR a Kick-off Presentation Package and all other required deliverables. (DIL #6) The Kick-off Meeting shall address program management and quality assurance activities outlined in this SOW, as well as the performance and environmental requirements outlined in the STS System specification in sufficient detail to demonstrate understanding of contract requirements. At a minimum, the presentation package should cover the following areas:
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Program Management
Quality Assurance
Star Sensor System Design Description
Preliminary Interface Control Documents
Flight Heritage
Facilities
Qualification Verification Plan and Procedure
Mechanical Analysis with Boundary Conditions
3.4.2 Design Conformance Review (DCR)
The contractor shall organize and present a Design Conformance Review to a GSFC Review
Team at the contractor’s facility prior to the manufacturing program. (DIL #7) The contractor shall provide to the NASA/GSFC COR a Design Conformance Review Presentation Package and all other required deliverable data prior to the review. (DIL #8) The Design Conformance
Review shall address all program management, design, drawings, analysis, manufacturing, test, and quality assurance activities outlined in this SOW and the PACE Spacecraft Star Sensor
System Specification, PACE-GNC-SPEC-0064, in sufficient detail to ensure that the proposed design conforms to all requirements and is ready for fabrication to begin. At a minimum, the design package should cover the following areas:
Program Management
Quality Assurance
Electrical, Mechanical, and Environmental specifications
Parts, including stress analysis and radiation hardness assessment
Detailed architectural block diagrams for the different deliverable units
Fabrication, Assembly, and Inspection Flow plan
Facilities
Verification Test Plan (Including Performance Test Description)
Materials and Processes
Contamination Control (for items sensitive to contamination or with explicit surface cleanliness or outgassing requirements)
Mechanical/Structural analyses
Electrical Worst-Case analyses
Failure Modes Effects Criticality Analysis
Flight Heritage
Verification Matrix (per Section 7.5.1)
Review minutes shall be prepared and, as a minimum, shall include attendance, action items, action item accomplishment responsibility and agreements. All items shall be in sufficient detail to be self-explanatory. A Design Conformance Review Report shall be prepared following the review and, as a minimum, contain meeting notice, agenda, review meeting minutes described above and responses to all recommendations and action items. (DIL #9)
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
3.4.3 Pre-Environmental Review (PER)
The contractor shall organize and conduct a Pre-Environmental Review (PER) at the contractor’s facility before the environment test program begins. (DIL #10) This presentation shall demonstrate overall conformance of the requirements specified in the PACE Spacecraft Star
Sensor System Specification, PACE-GNC-SPEC-0064, and this Statement of Work for this phase of the procurement. This presentation shall cover programmatic, technical, test and verification, and quality assurance topics, and address any changes made to the Verification
Matrix since DCR. (DIL #11) This review shall also provide an opportunity to review test plans and procedures and all analyses required to approve the testing of the hardware.
3.4.4 Pre-Ship Review (PSR)
The contractor shall hold a Pre-Ship Review at the contractor's facility at the completion of verification tests and prior to the shipment of each hardware item to NASA/GSFC. (DIL #12)
This presentation shall demonstrate completion of all activities required for delivery of any hardware deliverable item to NASA/GSFC, and note any activities that are incomplete. In particular, the contractor shall present the completed verification matrix that shows verification of all requirements and presents actual data (results of tests or analyses) where applicable. (DIL
#13) Any requirements that are not met shall be identified in the Deviations/Waivers etc. list and discussed with NASA/GSFC during the review.
An End Item Data Package (EIDP) shall be made available for review during pre-ship reviews for each of the different hardware deliverables. (DIL #14) This package shall also be delivered with each end item with the level of detail required of that item. The package should be comprised of, but not limited to, the following data:
The deliverable item name, serial number, part number, and classification status (e.g., flight, non-flight, ground support).
Appropriate approval signatures (e.g., contractor’s quality representative, product design lead, government Representative)
Work orders for the final assembly and associated tests
As-Built vs. As Designed Parts List, (EEE parts, includes serialization/revisions)
As-Built Final Drawing Package (including rework instructions, if any)
Problem/anomaly reporting (complete copies of report)
Deviations/Waivers/shortages/open items/non-conformances and their dispositions, with supporting rationale
Status of all action items from previous reviews
Class I MRBs (complete copies of reports)
List of As-Built Materials and Processes used
Achieved surface cleanliness and outgassing rate data (when applicable)
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Log of total operating time and failure-free operation
List and status of all identified Life-Limited Items
Trended Critical Parameters Data (when applicable)
Verification matrix (including environmental), test data and reports
Photograph Documentation (Pre and Post conformal coating, Pre-Closure and Closed)
Certificate of Conformance, with management signature
End Item Inspection Report
As-Built Configuration List
Mate/Demate log
Printed circuit board coupon results
Storage and Transportation Plans and Requirements
3.4.5 Technical Interchange Meetings (TIM)
The contractor shall plan for and facilitate up to five (5) informal, face-to-face technical interchange meetings to be held at the contractor facilities. (DIL #15) 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.5 DOCUMENTATION
The contractor shall ensure the generation and delivery of all documentation as called for in the contract and listed in RFP Section B.2 table.
In addition to that documentation specifically called for in the contract, upon request by the
NASA/GSFC COR, the contractor shall make available a copy of any document or data generated during this contract performance for review by GSFC at either the contractor's facility or via the internet. This includes, but is not limited to, technical reports and memorandums, drawings, schematics, studies, analyses, parts and materials data, test data, alerts, etc.
3.6 NA
3.7 EXISTING COMPONENTS
3.7.1 Existing Documentation and Analysis
If analysis or documentation exists already for the flight unit that satisfies the requirements within the Star Sensor System Specification, PACE-GNC-SPEC-0064, then the analysis or documentation may not need to be redone, and the requirement can be satisfied by similarity and with the delivery of the previous analysis/documentation to the NASA/GSFC COR.
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
4.0 DESIGN AND ANALYSIS
The contractor shall perform analyses of the technical and environmental requirements specified in the PACE Spacecraft Star Sensor System Specification (PACE-GNC-SPEC-0064) to ensure compliance of the hardware fabrication and to assemble the documentation necessary to ensure its usability by NASA/GSFC users.
4.1 INTERFACE CONTROL DOCUMENTATION
The Contractor shall provide the following documents (DIL #16):
Mechanical Interface Control Document (MICD), including physical characteristics, mounting interface, outline drawing, thermal (electrical), thermal, coatings on surfaces
Electrical Interface Control Document (EICD), including connector identification, connector pinouts, detailed description of each signal, interface circuits, command description, command sequencing/timing, and data (telemetry) description (Data
Interface Control Document could be a part of this EICD or a standalone document)
4.2 DRAWING PACKAGE
The contractor shall provide a drawing package that includes, but is not limited to: (DIL #17)
ELECTRICAL: assembly and interface drawings (board level schematics available on request)
MECHANICAL: assembly and interface drawings
THERMAL: assembly and interface drawings
DATA: interface drawings including packet structure and formatting and data delivery timing information.
The contractor shall provide preliminary drawing packages at each review.
4.3 COMPUTER MODELS
The contractor shall deliver a Computer-Aided Design (CAD) file for the Star Sensor System:
(DIL #18)
4.3.1 CAD Model and Documentation
A computer aided design (CAD) model shall be delivered for the Star Sensor System components in Pro/E (*.asm, *.prt) or STEP (*.stp,*.step) and ACIS (*.sat) formats to the following specifications:
- Models delivered with information indicating the mass, moments of inertia, and products of inertia as defined in the Star Sensor System specification document (PACE-GNC-
SPEC-0064).
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
- Models include with the component outer frame, connectors and backshells, and payload mounting holes at a minimum.
The preferred format is Pro/E utilizing a version of wildfire equal to or later than version 3. Full assembly models are desired.
4.4 STRUCTURAL ANALYSIS REPORT
The purpose of the structural analyses is to demonstrate compliance with the mechanical/structural design and test requirements. Structural analyses verify the structural integrity of the flight hardware by assessing the size and location of applied loads, load paths, and critical failure modes. A Structural Analysis shall be provided for the Flight Unit structure to ensure the capability to withstand and survive launch and ascent loads. (DIL #19) The analysis shall also address loads on any lift points as well. For metallic elements whose strengths are to be qualified by analysis (rather than by test, subject to NASA/GSFC approval), margins of safety will be 2.0 on yield and 2.6 on ultimate. Beryllium and composite materials shall not be qualified by analysis alone. The effects of any thermal inputs shall be reflected in the analyses as appropriate. This analysis shall include a Venting analyses for applicable flight components (such as thermal blankets and contamination enclosures) susceptible to pressure loadings to verify that positive strength margins exist at loads equal to twice those induced by the maximum pressure differential during launch. The results of these analyses shall be summarized in a contractor format Structural Analyses Report that will be provided to the NASA/GSFC COR for review.
4.5 STRUCTURAL FINITE ELEMENT MODEL
Contractors required to submit finite element models (per PACE-GNC-SPEC-0064, Section 6.3, 11.5) to the spacecraft shall submit model documentation that describes the following: (DIL #20)
1. The version of the model, including date of creation
2. A list of element, node, property, and material identification (ID) numbers
3. A description of the nonstructural mass represented on each property card
4. A description of units
5. A description of the local reference coordinate system
6. The results of satisfying the following model validity checks
Equilibrium/grounding: Rigid body equilibrium/grounding checks using the
NASTRAN GROUNDCHECK case control statement to assess the presence of mechanisms, overconstraints, etc. for all six model degrees-of-freedom for the various constraint sets.
Free-free dynamics (showing rigid body modes): In the unconstrained condition, the deployed on-orbit model should have six rigid body modes with frequencies below 0.005 Hz, with a goal of 0.0005 Hz, and the ratio of the lowest elastic mode frequency and the highest rigid body mode frequency should be greater than 100, with a goal of 1000. In their unconstrained condition, the stowed dynamics and
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
thermal distortion models should have six rigid body modes with frequencies below 0.001 Hz, with a goal of 0.0001 Hz.
Unit gravity loading (each axis): With the model constrained at appropriate interfaces, and 1G inertial loadings applied separately in three orthogonal directions, the sum of constrained forces in the loading direction should be within
0.01% of the model weight. The magnitude of the sums orthogonal to the loading direction should be less than 1.0 N.
Enforced displacement/rotation (all 6 degrees-of-freedom): Grounding forces will be determined by applying unit rigid body displacements and rotations to a stiffness matrix of the unsupported model, and determining the resultant grid point forces. Full capability of NASTRAN GROUNDCHECK case control can be used to determine grounding forces and moments. Grounding forces should be less than 1.0 N, and moments less than 0.5 N-m.
Matrix Conditioning Checks: The maximum ratio of any diagonal term to its corresponding term of the triangular factor matrix should be less than 5.0E7. The evaluation should be performed in a static decomposition with restraints applied to remove rigid body modes. A negative value of NASTRAN Param, Bailout, and forcing program execution with near singularities will not be used.
In NASTRAN static analysis (for instance unit gravity and thermal load checks), epsilon is a measure of the error in the load predicted from the product of stiffness matrix and solution set displacement compared to the actual input load vector
. Epsilon should be less than 1.0E-8.
Unit increase temperature (if required): When thermal stress assessment are performed, model checks are needed to ensure proper results. Remove all rigid elements (if not assigning thermal expansion values), equate all material coefficients of thermal expansion and reference temperatures, assign a uniform temperature field and allow for expansion/contraction of the model in all 6 degree-of-freedom. Results should show minimal element force generation and uniform expansion/contraction.
7. Mass Properties (CG location, Inertias, and total model mass)
Contractors required to submit finite element models (per PACE-GNC-SPEC-0064, Section 6.3, 11.5) to the spacecraft shall adhere to the following:
1. Model submitted as a MacNeal Schwendler Corporation (MSC)/ NASA Structural
Analysis (NASTRAN) data deck
2. All model property and material cards have descriptive names
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
3. Models submission is "full" model with no symmetry assumptions made to reduce model size
4. Model includes no "Super Elements"
5. Model submission includes an explicit Single Point Constraint set
6. Until actual hardware mass properties are verified and final, the finite element model is adjusted to the maximum allocated mass for each subsystem and component
4.6 THERMAL ANALYSIS REPORT
The contractor shall provide a worst case thermal analysis that illustrates that the device and/or the electronic parts junction temperatures are within the Electrical, Electronic, and
Electromechanical (EEE) EEE-INST-002 (DIL #21) de-rated operational temperature limits when subjected to the boundary conditions specified in the Star Sensor System Specification
(PACE-GNC-SPEC-0064). This analysis shall be performed with the components operating at their maximum expected power dissipations. By analysis or by similarity to other flight qualified parts, the contractor shall also prove that start up at the minimum non-operational temperature will not cause damage to any parts. All analysis results shall be summarized in a thermal analyses report, to be provided for review as per the contract schedule. This report shall contain a comprehensive list of each component’s maximum expected power dissipation, maximum case temperature, theta JC, maximum junction temperature, and de-rated operational temperature limit. Additionally, this report shall contain a thorough description of the computer models (or reference to the documentation required from section 4.7 (Thermal Model and
Documentation) of this document) and the assumptions that were used to perform the analysis including boundary conditions, surface finish thermo-optical properties, interface conductances.
4.7 THERMAL MODEL AND DOCUMENTATION
The contractor shall provide reduced Thermal Math Models (TMMs) for the STS System with less than 50 nodes per box. (DIL #22) The TMMs shall be delivered in an agreed upon format.
If the contractor does not have the project-compatible software to create TMMs, then the contractor shall provide sufficient detailed information such that GSFC can create the TMMs.
Documentation shall be provided including detailed descriptions of all aspects of the model necessary for GSFC to run and/or recreate the TMMs.
4.8 WORST CASE CIRCUIT ANALYSIS REPORT
The contractor shall provide worst-case analyses (WCA) for newly designed or modified circuits. (DIL #23) This element has been identified as warranting a Worst Case Analysis, since it has performance critical or function critical components for which excessive operating variations could compromise mission performance. They include control loops that require adequate phase and gain margin to operate properly, sensitive analog circuitry, power supply or switching circuitry, Field Programmable Gate Arrays, and electro-mechanical elements that require torque margin to operate over life and environmental variations. The result is “reliability is designed into the hardware” for long term trouble-free field operation (i.e., removal of adverse operational circuit behavior due to unanticipated component stress drift).
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
WCA shall be performed during the design phase by the design engineer. The Worst Case
Analysis Report shall include the following:
- Address worst case conditions performed on each component.
- Discuss how each analysis includes the mission life.
- Discuss consideration of critical parameters at maximum and minimum limits.
- The effect of environmental stresses on the operational parameters being evaluated.
The results of these analyses shall be summarized in a Contractor format Worst Case Circuit
Analysis Report that will be provided to the NASA/GSFC COR for review.
4.9 PARTS STRESS ANALYSIS REPORT
The contractor shall provide parts stress analyses on Electrical, Electronic, and
Electromechanical (EEE) parts and devices as employed in the circuit designs of the Flight Item to certify conformance with the derating requirements of EEE parts. (DIL #24) The analyses shall be documented, and justification shall be included for all applications that do not meet the derating criteria. The Contractor shall use NASA document EEE-INST-002, Instructions for
EEE Parts Selection, Screening, Qualification, and Derating to establish criteria. Contractor derating guidelines may be considered in place of EEE-INST-002 guidelines but shall be submitted for approval. (DIL #25) The results of these analyses shall be summarized in a
Contractor format Parts Stress Analysis Report that shall be provided to the NASA/GSFC COR for review.
4.10 RADIATION HARDNESS ANALYSIS REPORT
The contractor shall provide a Radiation Hardness Analysis on the STS System design to determine the effects of Total Ionizing Dose (TID), Displacement Damage Dose (DDD) and
Single Event Effects (SEE) on performance. (DIL #26) The analysis shall address all the requirements contained in PACE-GNC-SPEC-0064. The results of these analyses shall be summarized in a Contractor format Radiation Hardness Analyses Report that will be provided to the NASA/GSFC COR for review.
4.11 RELIABILITY ANALYSIS REPORT
The contractor shall provide a numerical reliability assessment of the component, using reliability data from historical on-orbit performance, life-testing, or data books, such as MIL-
HDBK-217F. (DIL #27) The results of this analysis shall be summarized in a Contractor format
Reliability Analysis Report that will be provided to the NASA/GSFC COR for review.
4.12 FAILURE MODES AND EFFECTS CRITICALITY ANALYSIS REPORT
The contractor shall provide an FMECA (Failure Modes and Effects Criticality Analysis) to identify potential failures with severity categories 2, 3, and 4 per Table 4-1. (DIL #28) The STS
System is single-string for PACE.
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
The FMECA shall be updated throughout the development life cycle to address design changes that result in changes to failure modes, causes, effects, system impact. FMECA shall be performed at the interface and functional level of the component.
Table 4-1 FMEA Severity Categories
Category Severity Severity Description
1 Catastrophic Failure modes that could result in serious injury, loss of life (flight or ground personnel), or loss of launch vehicle.
1S Failure in a safety or hazard monitoring system that could cause the system to fail to detect a hazardous condition or fail to operate during such condition and lead to Category 1 consequences.
2 Critical Failure modes that could result in loss of one or more mission objectives as defined by the
NASA/GSFC COR.
3 Significant Failure modes that could cause degradation to mission objectives.
4 Minor Failure modes that could result in insignificant or no loss to mission objectives
We are considering the loss of a single string component to be a CATEGORY 2.
The results of these analyses shall be summarized in a Contractor format Failure Modes And
Effects Criticality Analysis Report that shall be provided to the NASA/GSFC COR for review.
4.13 ERROR ANALYSIS REPORT
An Error Analysis shall be provided on the Flight Unit STS System Design that shall identify all the factors that introduce error into the accuracy of the STS System, and shows that the system can meet its performance requirements in spite of the errors. Errors may include, but not be limited to: Alignment error, radiation effects, electronic noise, degradation of parts, thermal distortions, etc. An Error Tree shall be generated documenting ALL the sources of error, along with an Error Analyses Report and provided to NASA/GSFC COR for review. (DIL #29)
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
4.14 STRAY LIGHT ANALYSIS REPORT
A Stray Light Analysis shall be performed on the Flight Unit Sun Shade to ensure the capability to exclude interference from light sources such as the Sun, Moon, and Earth at the angles specified in the performance requirements in PACE-GNC-SPEC-0064. The effects of any stray light entering the Star Sensor System aperture shall be reflected in the analyses as appropriate.
The results of these analyses shall be summarized in a Contractor format Stray Light Analysis
Report that shall be provided to the NASA/GSFC COR for review. (DIL #30)
4.15 USER/INSTRUCTION MANUALS
The contractor shall deliver a user’s guide/instruction manual for the STS System. (DIL #31)
4.16 NIGHT SKY TEST REPORT
The contractor shall provide a report documenting the performance of the Star Sensor System subjected to night-sky testing. The test setup shall represent the geometric configuration to meet full performance under field of view requirements specified in sections 5.5 of the Star Sensor
System Specification (PACE-GNC-SPEC-0064) document. The results of this test shall be summarized in a report that shall be provided to the NASA/GSFC COR for review. (DIL #74)
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
5.0 HARDWARE PROCUREMENT/MANUFACTURING
5.1 GENERAL REQUIREMENTS
The contractor shall either procure or manufacture all components required to assemble, integrate, and test the STS System to support the delivery dates as called for in the contract and listed in RFP Section B.2 Table.
The contractor shall assemble the quantities of STS System hardware described below. The contractor shall provide a Fabrication, Assembly, and Inspection Flow plan at the DCR that describes the method of fabrication, assembly, and inspection from piece parts to the completely assembled STS System.
5.2 STAR SENSOR SYSTEM
a) The contractor shall provide the following hardware to meet the requirements of the
PACE Spacecraft Star Sensor System Specification (PACE-GNC-SPEC-0064):
One Star Sensor System Flight Unit, including associated electronics. (DIL #67)
b) The contractor shall provide the following hardware that is consistent with the requirements of the PACE Spacecraft Star Sensor System Specification (PACE-GNC-
SPEC-0064), and outline any differences between the flight unit and the ETU:
One loaner Star Sensor Engineering Test Unit (ETU) (for 2 months). (DIL #68)
5.3 CONNECTOR SAVERS
Flight Units shall be tested with connector savers to minimize mates and de-mates. Connector savers shall be delivered with each Flight Unit. (DIL #69)
5.4 SUPPORTING HARDWARE
The Contractor shall provide the following supporting hardware (DIL #70):
One set of the mating half of the external connectors for each delivered flight unit, plus two additional sets per contract delivery schedule
Electrostatic Discharge (ESD) flight protective caps, as applicable
Closeout caps for test connectors
Transport caps for each unit
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
5.5 GROUND SUPPORT EQUIPMENT
The Contractor shall provide Ground Support Equipment and any associated software to support
Integration and Test activities at the Observatory level. Ground Support Equipment includes:
Star Sensor Optical Stimulators capable of stimulating the Star Sensor optics for each sensor head, including thermal vacuum testing. (DIL #71)
Shipping Container (DIL #72)
Drill Template (DIL #73)
Mounting Interface and Alignment Hardware (DIL #75)
Non-Flight Baffle Covers (DIL #76)
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
6.0 PERFORMANCE VERIFICATION AND TEST
6.1 VERIFICATION PLAN
A Verification Plan shall be generated by the contractor to describe the details of how the analyses, inspections, and verification tests identified in the PACE Spacecraft Star Sensor
System Specification, PACE-GNC-SPEC-0064 will be performed. (DIL #33) 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/GSFC COR as part of the planning process for evaluation and a possible delta qualification test.
The plan shall state the purpose of each test, state acceptance criteria, describe in detail the test method, set up, instrumentation, data analysis methods (if applicable), and give the sequence of the tests. The plan shall include a verification matrix summarizing how all requirements are verified (analysis, inspection, test, per the definitions in the Spec.), and listing all tests that will be performed on the Star Sensor System.
This plan shall be a contractor controlled document and shall indicate all changes made after the initial approval by the NASA/GSFC COR. After Verification Plan approval, no changes shall be made without written NASA/GSFC COR approval.
If any individual test plans are created in addition to the master Verification Plan, such as for
Thermal Vacuum testing, those plans shall also be provided. (DIL #34)
6.2 VERIFICATION TEST PROCEDURES
The contractor shall generate Verification Test Procedures and provide them to the NASA/GSFC
COR. (DIL #35) The verification procedures shall be step-by-step instructions for performing tests outlined by the Verification Test Plan. The procedures shall define the environmental conditions for the tests, required equipment and facilities, test constraints, use of diagnostic or performance test software, operating conditions, tolerance on all input stimuli, data to be recorded and pass/fail limits.
Verification Test Procedures shall be contractor controlled documents and shall indicate all changes made after the initial release for review to NASA. The Thermal Vacuum Test
Procedure shall include the contents listed in Section 7.9.4 for the Chamber Configuration.
6.3 VERIFICATION TEST REPORTS
The contractor shall generate Verification Test Reports. (DIL #36) These reports shall document the results of each test that was performed, what test levels were achieved, what performance requirements were verified, what anomalies were seen, and how they were resolved. The
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
Thermal Vacuum Test Report may include the Bakeout results (see Section 7.9.4) if it can be delivered by the delivery date for Bakeout Test Results.
Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.
400-FORM-0002 (4/16/2014)
7.0 QUALITY ASSURANCE
7.1 GENERAL REQUIREMENTS
7.1.1 Quality Assurance Plan/Manual
The contractor shall have a Quality Management System that is compliant with the requirements of SAE AS9100 Quality Systems - Aerospace - Model for Quality Assurance in Design, Development, Production, Installation and Servicing or equivalent, as documented in a Quality
Assurance Plan. The Plan shall be delivered to the NASA/GSFC COR for approval, and GSFC shall be notified of any changes to the QA program. (DIL #37)
7.1.2 Surveillance of the Contractor
The work activities and operations of the contractor, subcontractors, and suppliers are subject to evaluation, review, survey, audit, and inspection by the NASA/GSFC representative.
The contractor shall provide the NASA/GSFC representative with documents, records, equipment, and a suitable work area within their…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.