Att C_Amend 003_changes identified_L1-STISCDRL-0003_Ver0.2 .pdf
PDF 1 MB Posted
- Attached to
- Supra Thermal Ion Sensor (STIS) Instrument Federal contract opportunity
- Solicitation number
- 80GSFC19R0033
About this file
This document outlines a forthcoming federal contract solicitation for a Supra Thermal Ion Sensor instrument. NASA Goddard Space Flight Center plans to issue a Request for Proposal for the development of a Supra Thermal Ion Sensor and associated Engineering Development Unit to be part of the Space Weather Follow On satellite mission, a joint undertaking with NOAA. The contract scope includes design, development, fabrication, integration, testing, calibration, evaluation and launch support for the instrument. It also covers Ground Support Equipment, mission operations center support, and delivery of flight spares. The anticipated contract type is cost-plus-incentive-fee. Small business subcontracting goals include 6% total, with targets for small disadvantaged, women-owned, HUBZone, veteran-owned, and service-disabled veteran-owned small businesses. The North American Industry Classification Code is 336414 and size standard is 1,250 employees. The RFP is expected in fall 2019 with proposals due 45 days thereafter.
View the file
Other files for this federal contract opportunity
Show all 32
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
SWFO STIS CDRL 422-L1-STISCDRL-0003
ii
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
SWFO – L1 STIS Contract Deliverables Requirements List (CDRL)
Signature/Approval Page
Prepared by:
Debbie Henretty Date
SWFO-L1 STIS Instrument Engineer
NASA/GSFC, Code 422
Reviewed by:
Gus Comeyne Date
SWFO-L1 Deputy Project Manager
Approved by:
Gene Martin Date
SWFO-L1 Project Manager iii
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
CM FOREWORD
This document is Space Weather Follow On - Lagrange 1 (SWFO-L1) Project Configuration
Management (CM)-controlled document. Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes will be submitted to the SWFO CM Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.
Questions or comments concerning this document should be addressed to:
NASA/Goddard Space Flight Center
SWFO-L1 Project Office, Code 422
Attention: Configuration Management Office
Greenbelt, Maryland 20771 iv
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Change History Log
REV
LEVEL
DESCRIPTION OF CHANGE APPROVED
BY
DATE
APPROVED
0.0 Sept 5, 2019
0.1
Updated CDRL 74 to match the wording in the
SWFO-L1 IMAR
Removed CDRL 005 Small Disadvantaged
Business
Updated CDRL 013
Updated CDRL 042 – changed contract clause from
H.13 to H.8
Oct 3, 2019
0.2
Deleted the following CDRLs: 7, 8, 12, 21, 25, 26, 27, 28, 32, 43, 48, 49, 51, 58, 70, 72, 73, 79, 80, 90, 92, 95, 103, 104, 106
Updated the following CDRLs: 1, 2, 6, 14, 17, 18, 22, 24, 29, 30, 31, 40, 46, 57, 88, 89
Added new Section 4 to include hardware deliverables and their delivery dates
Dec 3, 2019 v
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Table of Contents
1 INTRODUCTION
1.1 Definition of Due Dates/Maturity, Definition of Categories, and Delivery Instructions 1
2 STIS CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)
3 DATA ITEM DESCRIPTIONS
3.1 Program Management Plan
3.2 Weekly Status Reports and Telecon Minutes
3.3 Monthly and Quarterly Financial Report
3.4 NASA Property in the Custody of the Contractors
3.5 Reserved
3.6 Contractor’s Work Breakdown Structure Diagram and Dictionary
3.7 Reserved
3.8 Reserved
3.9 Detailed Schedules
3.10 Configuration Management Plan
3.11 Configuration Change Requests (CCR) Class I
3.12 Reserved
3.13 Safety and Health Reports
3.14 Integrated Baseline (IBR) Review Data Package
3.15 Responses to Requests for Action
3.16 System Definition Review (SDR) Data Package
3.17 Preliminary Design Review (PDR) Data Package
3.18 Critical Design Review (CDR) Data Package
3.19 Pre-Environmental Review (PER) Data Package
3.20 Pre-Storage/Pre-Ship Review Data Package
3.21 Reserved
3.22 Program Management Status Review Data Package
3.23 Subsystem Review Minutes and Action Items
3.24 Subcontract and Subsystem Review Data Packages
3.25 Reserved
3.26 Reserved
3.27 Reserved
3.28 Reserved
3.29 Risk Management Plan
vi
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
3.30 Systems Engineering Management Plan
3.31 Engineering Analyses Reports
3.32 Reserved
3.33 Document Tree
3.34 Instrument Description Document (IDD)
3.35 Flight Telemetry and Command Database
3.36 Flight Telemetry and Command Handbook
3.37 STIS System Specification
3.38 Contamination Control Plan
3.39 Solid Math Model
3.40 Thermal Math Models and Reports
3.41 Structural Math Model and Reports
3.42 Contractor Task Plan
3.43 Reserved
3.44 Instrument Block Diagrams and Approved or Controlled Drawings
3.45 Detailed Design Specifications
3.46 Software Management Plan
3.47 Software Delivery Packages
3.48 Reserved
3.49 Reserved
3.50 Digital Imagery and Video Records
3.51 Reserved
3.52 System Performance Verification Plan
3.53 Individual Test Plans
3.54 Performance Verification Procedures
3.55 Environmental Verification Specification
3.56 Radiation Shielding and Dose Analysis Report
3.57 Single Event Effects Control Plan
3.58 Reserved
3.59 Magnetic Control Plan
3.60 Verification Reports
3.61 Component and Subassembly Verification Reports for All Subcontracted Items
3.62 EMC/EMI Compatibility Plan
3.63 Mass Properties and Power Report
vii
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
3.64 Calibration Program Plan
3.65 Calibration Data Books
3.66 Ground Processing Algorithm Document
3.67 Ground Processing Algorithms Test and Validation Plan
3.68 Ground Software Acceptance Plan Input
3.69 STIS Packetized Data
3.70 Reserved
3.71 Maintenance, Test, and Operations Manual for the STIS Emulator
3.72 Reserved
3.73 Reserved
3.74 Request for Use of Inherited, Build-to-Print, or Modified Heritage Items
3.75 Software Assurance Plan
3.76 Non-Conformance Reports
3.77 System Safety Program Plan (SSPP)
3.78 Safety Assessment Report
3.79 Reserved
3.80 Reserved
3.81 Operations Hazard Analysis and Hazard Verification Tracking Log
3.82 Pre-Mishap Plan
3.83 Failure Mode, Effects, and Criticality Analysis (FMECA) and Critical Items List (CIL)
3.84 Worst-Case Analyses
3.85 Reliability Predictions
3.86 Trend Analysis Plan and Data Reports
3.87 Limited Life Items List
3.88 EEE Parts Control Plan
3.89 Master EEE Parts List
3.90 Reserved
3.91 Materials Usage Agreement and/or Stress Corrosion Evaluation Form
3.92 Reserved
3.93 GIDEP Alert/NASA Advisory Dispositions
3.94 Transportation Handling Plan and Procedures
3.95 Reserved
3.96 On-Site Data Analysis Reports
3.97 Observatory Level Test Procedures
viii
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
3.98 Observatory Level Test Report
3.99 Operations Handbook
3.100 Post-Launch Test Reports
3.101 Major Anomaly Report
3.102 System Performance Verification Report
3.103 Reserved
3.104 Reserved
3.105 Field Programmable Gate Array (FPGA) Development Plan
3.106 Reserved
3.107 End Item Acceptance Data Package
3.108 Mission Assurance Requirements Compliance Matrix
3.109 Supplier List
3.110 Reporting of Material Review Board Actions
3.111 Input to Orbital Debris Assessment Report and End of Mission Plan
3.112 Safety Requirements Compliance Checklist
3.113 Safety Data Package
3.114 Hazardous Procedures for Payload I&T and Prelaunch Processing
3.115 Parts Stress Analysis
3.116 Alternate Printed Circuit Board Standard Report
3.117 Printed Circuit Board Procurement Plan
3.118 Lot Acceptance and Quality Conformance Test Results for Printed Circuit Boards .. 131
3.119 Materials and Processes Selection, Control, and Implementation Plan
3.120 Materials Identification and Usage List
3.121 Foreign Object Debris Prevention and Control Plan
3.122 Instrument Operations Configurable Items
3.123 Initiating GIDEP Alerts
4 STIS HARDWARE DELIVERABLE ITEMS
5 ACRONYMS
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
1 INTRODUCTION
This Contract Deliverables Requirements List (CDRL) document defines the requirements for data items to be provided by the SWFO-L1 Supra Thermal Ion Sensor (STIS) contractor.
Section 1.1 includes definitions and instructions for distribution. Section 2 presents the CDRL item by item with due dates. Section 3.0 provides the Data Item Description (DID), a description of each item and describes use, and preparation information.
1.1 DEFINITION OF DUE DATES/MATURITY, DEFINITION OF
CATEGORIES, AND DELIVERY INSTRUCTIONS
The following definitions apply to the "DUE DATE, MATURITY" column in the STIS Contract
Deliverables Requirements List.
a) DUE DATE:
1. Proposal: Items that are provided with the proposal.
2. CDR, PER, etc.: Critical Design Review, Pre-Environmental Review, Pre-Ship
Review, etc.
3. As Generated: After each initial edition, revision, addition, etc.
4. Monthly: Monthly by the 15th of each month or as required or as modified by CO
5 Weekly: Weekly status reports by Tuesday close of business or as modified by
Contracting Officer (CO)
6. L: Launch Date
7. DACA: Days after contract award
8. MACA: Months after contract award
Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.
b) MATURITY:
1. Preliminary: The initial submission of an item. To be completed with available information as of the time of preparation for the due date.
2. Update: The best up-to-date information available at the time.
3. Final: The complete thorough submission of an item for approval, review, or information. This does not preclude updating later.
c) NASA Acceptance Code
A Approval: Documents in this category require approval by the GSFC Contracting
Officer’s Representative (COR) prior to use by the contractor.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
R Review: Documents in this category require delivery to the Government prior to use and within the time period specified in the "Due Date" column of this document. They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives.
I Information: Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the STIS Contract Deliverables
Requirements List for the purpose of determining current program status, progress, and future planning requirements.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
2 STIS CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)
Items with an “As Generated” due date that are critical to schedule, performance, or interface shall be transmitted to GSFC by within 48 hours of generation.
Any updates to items of “Final” maturity shall require the same "approval/review" process as was required for the previous submissions.
Receipt of “Approval”, “Review”, and “Information” coded items by the Government shall occur within the time specified in the "Due Date" column of the STIS Contract Deliverables
Requirements List of this document.
Requirements for re-submission of “Approval” coded items shall be as specified in the letters of disapproval. For most cases, the contractor will be required to resubmit the document within 30 days of receiving comments from the Government.
If the contractor has not received response from GSFC within 60 days of delivery of an
“Approval” coded CDRL item (15 days for test procedures), the contractor may proceed as if the document has been approved.
When Government evaluations of “Review” coded items reveal inadequacies, the Contractor shall correct the documents within 30 days of receiving comments or provide a plan approved by the Government for closing deficiencies.
All Data items shall be delivered in electronic format to a GSFC SWFO-L1 specified web portal unless otherwise noted in the STIS Contract Deliverables Requirements List.
Individual CDRL items may be combined with other CDRL items to increase documentation efficiency if the content and requirements of the CDRL items are satisfied.
Electronic deliverables shall be delivered in the following formats unless otherwise approved by the government:
1 Text Documents: PDF (searchable) or MSWord
2 Presentations: PDF (searchable) or PowerPoint
3 Spreadsheets: Microsoft Excel
4 Database: Delimited ASCII files accompanied with database schema document defining tables and entries.
5 Schedules: MS Project
6 Schematics and Drawings: PDF
7 Photographs: JPEG or current industry standard.
8 Video: Any readily available open standard (e.g., AVI, MPEG)
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
STIS Contract Deliverables Requirements List (CDRL)
ID
No.
Document Title Due Date, Maturity
NASA
Accept.
001 Program Management Plan Preliminary: 30 DACA
Final: TBD R
Weekly Status Reports and
Telecon Minutes Weekly R
Monthly Financial Report
Quarterly Financial Report Per Contract Clause TBD R
NASA Property in the
Custody of the
Contractors3
Per Contract Clause TBD R
005 Reserved
Contractor’s WBS
Diagram and Dictionary
Final: 15 DACA
Updates: As generated A
007 Reserved
008 Reserved
009 Detailed Schedules Preliminary: 15 DACA
Monthly Updates R
Configuration Management
Plan
Preliminary: 15 DACA
Final: TBD A
Configuration Change
Requests (CCR) Class I As generated A
012 Reserved
013 Safety and Health Report Per the contractual requirements A
Integrated Baseline Review
Data Package
Preliminary: IBR – 14 days
Final: IBR R
Responses to Request for
Actions
Preliminary: 30 days after assigned
Updates: As agreed A
System Definition Review
Data Package30
Preliminary: SDR – 14 days
Update: SDR – 7 days
Final: SDR
R
Preliminary Design Review
Data Package30
Preliminary: PDR Dry Run – 7 days
Final: PDR R
Critical Design Review
Data Package30
Preliminary: CDR Dry Run – 7 days
Final: CDR R
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
Pre-Environmental Review
Data Package30
Preliminary: PER Dry Run of each
Model – 7 days
Final: PER of each Model
R
Pre-Storage/Pre-Ship
Review Data Package30
Preliminary: PSR Dry Run of each
Model – 7 days
Final: PSR of each Model
R
021 Reserved
Program Management
Status Review Data
Package
Bi-Monthly R
Subsystem Review
Minutes and Action Items
Preliminary: 2 days after review
Final: 14 days after review
R
R
Subcontract and Subsystem
Review Data Packages5 Final: Review R
025 Reserved
026 Reserved
027 Reserved
028 Reserved
029 Risk Management Plan Preliminary: 30 DACA
Final: TBD R
Systems Engineering
Management Plan
Preliminary: 30 DACA
Final: TBD R
Engineering Analyses
Reports As generated R
032 Reserved
033 Document Tree Preliminary: PDR
Final: CDR R
Instrument Description
Document (IDD)
Preliminary: PDR
Final: CDR A
Flight Telemetry and
Command Database
Preliminary: PER of FM1
Updates: As generated R
Flight Telemetry and
Command Handbook
Preliminary: PDR
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
STIS System
Specification
Preliminary: SDR – 14 days
Final: SDR A
Contamination Control
Plan
Preliminary: 30 days before
PDR
Final: 30 days before CDR
R
A
039 Solid Math Model
Preliminary: PDR
Update: CDR, FM1 PER, FM1 PSR, and as generated
R
Thermal Math Model and
Reports
Preliminary: PDR
Update: CDR, FM1 PER, FM1 PSR, and as generated
R
Structural Math Model and
Reports
Preliminary: PDR
Update: CDR, PER, PSR, and as generated
R
042 Contractor Task Plan Per Contract R
043 Reserved
Instrument Block
Diagrams, and
Approved or Controlled
Drawings
Preliminary: PDR
Update: CDR
Final: PSR
R
Detailed Design
Specifications
Preliminary: Applicable subsystem
PDR
Final: Applicable subsystem CDR
R
Software Management
Plan
Preliminary: 30 DACA
Update: SWPDR, SWCDR, SWTRR
Final: SWAR
A
Software Delivery
Packages As generated R
048 Reserved
049 Reserved
Digital Image and Video
Records As generated I
051 Reserved
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
System Performance
Verification Plan
Preliminary: With Proposal
Update: SDR
Final: PDR
A
053 Individual Test Plans Preliminary: CDR
Final: 90 days before Test A
Performance Verification
Procedures 30 Days prior to use A
Environmental Verification
Specification
Preliminary: PDR
Final: CDR A
Radiation Shielding and
Dose Analysis Report
Preliminary: PDR
Final: CDR R
Single Event Effects
Control Plan
Preliminary: PDR
Final: CDR R
058 Reserved
059 Magnetic Control Plan Preliminary: PDR
Final: CDR R
060 Verification Reports Preliminary: 1 day after test
Final: 30 days after Test R
Component and
Subassembly Test Reports for all Subcontracted Items
As generated.
Maintained on site I
EMC/EMI Compatibility
Plan
Preliminary: PDR
Final: CDR R
Mass Properties and Power
Report Monthly R
064 Calibration Program Plan
Preliminary: SDR
Update: PDR
Final: CDR
A
065 Calibration Data Books Final: PSR of each Model R
Ground Processing
Algorithm Document
Preliminary: PDR
Update: CDR
Final: PSR months
A
Ground Processing
Algorithms Test and
Validation Plan
Preliminary: PDR
Update: CDR
Final: PSR - 3 months
A
Ground Software
Acceptance Plan Input
Preliminary: CDR
Final: PSR - 6 months
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
069 STIS Packetized Data As generated I
070 Reserved
Maintenance, Test, and
Operations Manual for the
STISE
Final: With Delivery of STISE R
072 Reserved
073 Reserved
Request for Use of Multi-
Mission or Previously
Designed, Fabricated, or
Flown Hardware
Preliminary: 60 DACA
Final: SDR + 60 days R
075 Software Assurance Plan
Preliminary: 30 days prior to SDR
Final: 15 days prior to PDR
Updates: 15 days prior to implementation
I
I
I
076 Non-Conformance Report
Notify In-plant Resident Office by the next business day.
Written Notification: < 1 week
Update: Completion of analysis, Assignment of Corrective Action
Final: Closure
A
077 System Safety Program Plan Preliminary: SDR
Final: 30 days prior to PDR R
078 Safety Assessment Report
Preliminary: PDR + 30 days
Update: CDR – 30 days
Final: PSR -30 days
A
079 Reserved
080 Reserved
081 Operations Hazard Analysis Preliminary: CDR
Final: 45 days prior to PER
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
082 Pre-Mishap Plan 45 days prior to PDR A
Failure Mode, Effects, and
Criticality Analysis and
Criticality Items List
Preliminary: 30 days prior to PDR
Final: 30 days prior to CDR
R
A
084 Worst-case Analyses 30 days prior to CDR
Revisions within 30 days R
085 Reliability Predictions Preliminary: PDR
Final: CDR R
Trend Analysis Plan
Trend Analysis Data
Reports
Preliminary: PDR
As Generated
087 Limited Life Items List
Preliminary: 30 days prior to
PDR
Updates: Revisions within 30 days
R
088 EEE Parts Control Plan Preliminary: 30 DACA
Final: PDR I
089 Master EEE Parts List
Preliminary: PDR
Final: CDR
Updates: As generated
A
090 Reserved
Materials Usage
Agreement and/or Stress
Corrosion Evaluation Form
New MUAs: 30 days prior to CDR
Updated MUAs: as generated A
092 Reserved
093 GIDEP Alerts
Disposition of existing Alerts within
30 days of identification
Disposition of new Alerts within 30 days of Alert release
Transportation, Handling
Plan and Procedures
Preliminary: PDR
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
095 Reserved
On-site Data Analysis
Reports As generated R
Observatory Level Test
Procedures
Preliminary: PER
Final: PSR R
Observatory Level Test
Report Observatory PSR R
099 Operations Handbook Preliminary: PER
Final: PSR A
100 Post Launch Test Reports3 Preliminary: 2 weeks after test
Final: 2 months after test R
101 Major Anomaly Report
Preliminary: Electronic submission within 24 hours of occurrence
Updates: Electronic notification of a change in status within 24 hours of occurrence
Final: Proposal prior to closure
I
System Performance
Verification Report Final: PSR of each Model R
103 Reserved
104 Reserved
105 FPGA Development Plan
Preliminary: TBD
Update: PDR
Final: CDR
A
106 Reserved
End Item Acceptance Data
Package
Preliminary: PSR – 14 days
Final: 30 days prior to delivery
Mission Assurance
Requirements Compliance
Matrix
Preliminary: 60 DACA
Update: 30 days prior to implementation
I
109 Supplier List
Preliminary: 60 DACA
Update: semi-annually after contract award
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
110 Reporting of MRB Actions
Major MRB actions: within 5 working days of MRB action
Minor MRB actions: within 5 working days of MRB action
Input to Orbital Debris
Assessment Report
Preliminary: 15 days prior to mission
PDR
Updates: 60 days prior to mission CDR
Final: 90 days prior to PSR
I
Safety Requirements
Compliance Checklist
Preliminary: 45 days prior to SDR
Final: 45 days prior to PDR
Updates: 45 days prior to CDR
A
113 Safety Data Package
Preliminary: 30 days prior to SFWO
PDR
Updates: 30 days prior to SWFO CDR
Final: 120 days prior to shipment
Hazardous Procedures for
Payload I&T and Prelaunch
Processing
Payload I&T Hazardous Procedures:
7 days prior to first use
Launch Range Hazardous
Procedures: 60 days prior to first use
R
115 Parts Stress Analysis Final: 45 days prior to CDR
Revisions: NLT 30 after identification
R
R
Alternate Printed Circuit
Board Standard Report 30 days prior to use R
Printed Circuit Board
(PCB) Procurement Plan
Preliminary: 30 days prior to PDR or
30 days before procurement, whichever comes first
Updates: 14 days prior to circuit board manufacturing
Lot Acceptance and Quality
Conformance Test Results for PCBs
As generated A
Materials & Processes
Selection, Control, and
Implementation Plan
60 DACA I
Materials Identification and
Usage List
30 days prior to PDR
30 days prior to CDR
Updates within 30 days of identification
R
Foreign Object Debris
Prevention and Control 30 days prior to PDR R
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Document Title Due Date, Maturity
NASA
Accept.
Instrument Operations
Configurable Items
Preliminary: 30 days prior to launch
Updates: As needed
123 Initiating GIDEP Alerts Within 30 days of identification R
Notes:
1. Single hardcopy only delivered to Contracting Officer or per the Contract.
2. Two hardcopies delivered to the Contracting Officer with electronic delivery.
3. Three hardcopies delivered to the Contracting Officer with electronic delivery.
5. Five hardcopies and CDs of the final version delivered at the review along with electronic delivery to the Web Portal. Preliminary versions delivered to
Web Portal.
10. Ten hard copies of the final version of the presentation package, and five CDs of the final version of the entire data package (including all documentation) delivered at the review along with electronic delivery to the Web Portal.
Preliminary versions delivered to Web Portal.
30. Thirty hardcopies and CDs of the final version delivered at the review along with electronic delivery to the Web Portal. Preliminary versions delivered to
Web Portal.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
3 DATA ITEM DESCRIPTIONS
3.1 PROGRAM MANAGEMENT PLAN
DESCRIPTION OF REQUIRED DATA
1. CDRL No.: 001
2. Title: PROGRAM MANAGEMENT PLAN
3. Use: Describes how the program is organized and managed. It provides the management structure, its system of operation, responsible lines of communications, and key personnel assignments.
4. Preparation Information:
The Program Management Plan shall address the overall organization, management approach, and structure of the STIS Program plus its interrelationships with the parent company and the subcontractors, and relationship with the Government.
The Program Management Plan shall describe how and where the program will operate during all phases of the contract.
The Program Management Plan shall delineate how the requirements of the Statement of Work
(SOW) will be achieved and include a description of planned activities for identifiable SOW requirements.
The Program Management Plan shall describe the concept of the nature of the tasks and related potential problems. Discuss the approach to problem avoidance and/or solution. Address the degree to which proposed personnel and procedures are proven through similar experience.
The Program Management Plan shall address interfaces with the Government and with any
Government Furnished Equipment (GFE) suppliers.
The Program Management Plan shall indicate critical paths, long-lead items and significant milestones down to at least the lowest level of the WBS.
The Program Management Plan shall indicate the need for additional definition of spacecraft and mission information, and when this information is required to avoid schedule slippage.
The Program Management Plan shall include graphical displays such as flow diagrams, WBS, logic networks, etc., to reduce verbal descriptive material.
The Program Management Plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the program showing inter- relationships of technical management, business management, and subcontract
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
management, from lower level through intermediate management to top-level management with detailed explanation of:
a) The authority of the STIS Program Manager relative to other ongoing programs and applicable support organizations within the company structure. Discuss the program manager’s control over essential resources and functions necessary to accomplish the work.
b) How and by whom interdepartmental work will be monitored and the authority of the program manager over interdepartmental work.
c) Process to be followed by the program manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources and functions not under the program manager’s direct control such as personnel, finances, and facilities.
d) The lead program team members with names, functions, and qualifications.
The Program Management Plan shall provide contractual procedures proposed for the program to effect administrative and engineering changes, describing any differences from existing procedures.
The Program Management Plan shall describe management techniques to be employed in minimizing program costs and schedule impacts, including controls to be exercised over subcontractors and suppliers.
The Program Management Plan shall describe how issues will be surfaced in a timely manner and at the proper levels.
The Program Management Plan shall discuss and illustrate the proposed STIS Mission
Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.
The Program Management Plan shall discuss whether the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours) are presently on payroll and immediately available for this work.
The Program Management Plan shall state the number and kind of persons who would have to be hired, and plans to obtain them.
The Program Management Plan shall state the independence of the system safety/quality assurance functions.
The Program Management Plan shall explain/describe the schedule administration/control.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The Program Management Plan shall describe how the schedules are developed, maintained and updated.
The Program Management Plan shall explain the internal review cycle of the scheduling process.
The Program Management Plan shall explain how internal audits/reviews ensure that scheduling data reported to the Government accurately reflects the work status.
The Program Management Plan shall describe how subcontracts will be managed and reviewed, and describe the performance milestones of each.
The Program Management Plan shall address the design review process.
The Program Management Plan shall list and describe the planned subsystem reviews.
The Program Management Plan shall address the Contractor's approach to performance verification.
3.2 WEEKLY STATUS REPORTS AND TELECON MINUTES
1. CDRL No.: 002
2. Title: WEEKLY STATUS REPORTS AND TELECON MINUTES
3. Use: Contract status evaluation.
The Weekly Status Report shall indicate the status of the contract as of close of business the preceding Friday, including a summary of progress made.
The Weekly Status Report shall address the work completed during the week against the work planned for the week, and address recovery plans if necessary.
The Weekly Status Report shall include technical progress, including significant accomplishments and milestones reached.
The Weekly Status Report shall include problems encountered and proposed corrective action.
The Weekly Status Report shall indicate any actual or anticipated slip in schedule.
The Weekly Status Report shall include identification of any Class I or Class II changes.
The Weekly Status Report shall detail the work planned for the next week and summarize the work planned for the next month.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The Weekly Status Report shall contain telecon minutes for the previous week's weekly telecom.
The Weekly Status Report shall contain Action Item Status for any overdue action items and any action items due in the next two weeks.
The Weekly Status Report shall contain status of any open Non-Conformance Reports.
The Weekly Status Report shall contain status on any open contract actions, including Special
Engineering Analyses.
The Weekly Status Report shall contain status on any red risk item.
Note: This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.
3.3 MONTHLY AND QUARTERLY FINANCIAL REPORT
1. CDRL No.: 003
2. Title: MONTHLY AND QUARTERLY FINANCIAL REPORT
3. Use: For budget and cost control
The Monthly Financial Report shall be prepared in accordance with NFS 1852.242-73 and NPR
9501.2D, NASA Contractor Financial Management Reporting on NASA Form 533M.
The Monthly Financial Report shall be submitted within 15 days of the end of the reporting period.
The Quarterly Financial Report shall be prepared in accordance with NFS 1852.242-73 and NPR
9501.D, NASA Contractor Financial Management Reporting on NASA Form 533Q. The report is due 2 weeks prior to the period being reported.
At a minimum, the reporting structure shall be in accordance with and to Level 1 of the WBS as set forth in Attachment J.
The reporting categories shall include as a minimum:
a) Direct labor by labor category
b) Overhead
c) Fringe Benefits
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
d) Materials
e) Material Overhead
f) Subcontracts
g) Travel
h) Other Direct Costs
i) Facilities Capital Cost of Money
j) Fee
k) Total Cost Plus Fee
3.4 NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS
1. CDRL No.: 004
2. Title: NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS
3. Use: For budget, cost, and property control
The NASA Property in the Custody of the Contractors report shall consist of NASA Form 1018 in accordance with NFS 1845.505-14, the instructions on the form, subpart 1845.71, and any supplemental instructions for the current reporting period issued by NASA.
3.5 RESERVED
3.6 CONTRACTOR’S WORK BREAKDOWN STRUCTURE DIAGRAM AND
DICTIONARY
1. CDRL No.: 006
2. Title: CONTRACTOR’S WORK BREAKDOWN STRUCTURE DIAGRAM AND
DICTIONARY
3. Use: To facilitate program planning and control and for financial and technical reporting.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The Contractor's Work Breakdown Structure (WBS) Diagram shall document Government accepted changes to the Government WBS with an updated WBS diagram and description of task elements.
The Contractor's WBS Diagram shall define all work included in the STIS development life cycle.
The Contractor's WBS Diagram shall hierarchically relate all work, products, and end items.
The Contractor's WBS Diagram shall provide a framework for program work definition to a level of detail consistent with cost, schedule, technical, and risk oversight as desired by contractor's management.
The Contractor's WBS Diagram shall contain a companion WBS dictionary that narratively describes the overall structure and content of each individual element of the WBS.
3.7 RESERVED
1. CDRL No.: 007
2. Title: SPARE PARTS LIST
3. Use: To review contractor’s spares list.
The Spare Parts List shall define and justify the contractor's position for the spares proposed for the STIS program.
The Spare Parts List shall also present the schedule and method for obtaining the spares.
3.8 RESERVED
1. CDRL No.: 008
2. Title: MANPOWER AND COST REPORT
3. Use: To provide assurance the Contractor’s internal cost and schedule performance are consistent and controlled effectively.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The Manpower and Cost report shall list by name all individuals who charged to a STIS WBS and the hours charged by each individual.
3.9 DETAILED SCHEDULES
1. CDRL No.: 009
2. Title: DETAILED SCHEDULES
3. Use: For understanding and mapping out in detail the most efficient way of melding together all elements necessary for providing the program deliverables by their required delivery times.
The schedule shall encompass all phases of the program indicating critical path and schedule slack and reserve.
Phase 1 schedules shall include the instrument and GSE design, the Program Reviews, fabrication and test of the Engineering Development Unit (EDU) and GSE.
Phase 2 schedules shall include the fabrication, test, calibration, and delivery of the Proto-Flight
Model (PFM) instruments and their integration to the SWFO-L1 spacecraft.
Design schedules shall be detailed by task with expected start and completion dates.
Procurement schedules shall be detailed by major items, assembly, or definable subassembly.
Procurement schedules shall be subdivided into standard electrical parts, integrated circuits, etc.
Fabrication schedules shall be detailed to the mechanical subassembly level and to the electronic board level, and show the expected start and completion dates, as well as substantive in-process milestones.
Detailed schedules shall indicate critical paths.
Detailed schedules shall indicate slack and reserve.
For the build-up of an instrument, an assembly/test flow diagram shall show sequences of fabrication, assembly, integration, and test for assemblies, subsystems and system, and includes quality assurance test points and associated inspection level requirements.
The Detailed Schedules shall include views in Microsoft Project that, as a minimum, summarize the following information:
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
a) Level 1 Program Schedule - This schedule should include the programmatic milestone/events for the STIS Program reflecting the development of all of the models.
b) Level 2 Model Schedules - These schedules should include programmatic milestones/events for the individual Model from design, manufacturing, integration and test through launch including data on major procurements.
c) Intermediate Logic Networks - These networks should be established for each subsystem or subassembly to the electronic board level. Upon request for the Government, the
Contractor will supply the Government with more information from the detail schedules, which the Contractor maintains.
d) 180-Day Window Report - This report should reflect all the events which are expected to start/complete within 180 days after the current reporting cycle.
e) End Item Float Report - A monthly report should be submitted for each deliverable subsystem or subassembly comparing the current month float to the float of the previous month and explain any changes.
A monthly analysis shall be submitted that will contain a brief description of the current status of each subsystem or subassembly along with descriptions of any existing or potential problems areas.
3.10 CONFIGURATION MANAGEMENT PLAN
1. CDRL No.: 010
2. Title: CONFIGURATION MANAGEMENT PLAN
3. Use: To define the contractor’s configuration management system and provide a means of control for all changes affecting form, fit, or function and any impact on performance, cost or schedule.
The Configuration Management Plan shall describe the scope, approach, methods, and procedures of the system used to control changes of requirements and design.
The Configuration Management Plan shall describe the organization of the configuration management program and how it relates to the rest of the STIS program.
The Configuration Management Plan shall list all tools used for configuration management.
The Configuration Management Plan shall use the following product change classifications:
a) A change or request for Deviation/Waiver is classified as Class I when it affects one or more of the following factors:
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
1) Program baseline documentation
2) Technical requirements contained in the product configuration identification, including the following:
i) Form, fit, or function
ii) Performance
iii) Power
iv) Reliability outside stated requirements
v) Weight, balance, moment of inertia
vi) Interface characteristics
vii) Hardware and process qualifications
3) Non-technical contractual provisions
i) Fee
ii) Incentives
iii) Cost
iv) Schedule
v) Guarantees or deliveries
4) Other factors
i) Government-furnished property (GFP)
ii) Safety
iii) Electromagnetic characteristics
iv) Deliverable operational, test, or maintenance computer programs
v) Compatibility with support equipment
b) A change is classified as Class II when it does not fall within the definition of a Class I change.
3.11 CONFIGURATION CHANGE REQUESTS (CCR) CLASS I
1. CDRL No.: 011
2. Title: CONFIGURATION CHANGE REQUESTS (CCR) CLASS I
3. Use: Class I changes are to be used as a vehicle for orderly processing of change requests to appropriate level of approval authority for disposition.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Class I Configuration Change Requests shall document proposed changes impacting form, fit, function, cost, schedules or performance per the Configuration Management Plan or per the
Software Configuration Management Plan section of the Software Management Plan.
3.12 RESERVED
1. CDRL No.: 012
2. Title: CONFIGURATION CHANGE REQUESTS (CCR) CLASS II
3. Use: Class II changes are to be used as a vehicle for processing of all change requests not classified as Class I to appropriate levels for concurrence.
Class II Change Requests shall document all change requests that are not Level I changes and are not detrimental to the government.
3.13 SAFETY AND HEALTH REPORTS
1. CDRL No.: 013
2. Title: SAFETY AND HEALTH REPORTS
3. Use: To document any accident, incident, or exposure resulting in fatality, lost-time occupational injury, occupational disease, contamination of property beyond any stated acceptable limits.
The Safety and Health Report shall be per the contractual requirements.
3.14 INTEGRATED BASELINE (IBR) REVIEW DATA PACKAGE
1. CDRL No.: 014
2. Title: INTEGRATED BASELINE (IBR) REVIEW DATA PACKAGE
3. Use: To evaluate whether the contracted work is properly linked with its cost, schedule, and risk and that the management processes are in place to conduct performance measurement. The IBR will evaluate the performance baseline to ensure it
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
captures the entire technical scope of work, is consistent with schedule requirements, has adequate resources assigned, and has sound management processes.
The IBR Review Data package shall identify the internal organization elements and the major subcontractors responsible for accomplishing the authorized work.
The IBR Review Data package shall describe the relationship and level of integration of all management control systems (e.g., Planning and Scheduling, Budgeting, Estimating, Work
Authorization, Cost Accumulation).
The IBR Review Data package shall identify the managerial positions responsible for controlling overhead.
The IBR Review Data package shall identify physical products, milestones, technical performance goals to be used to measure output.
The IBR Review Data package shall describe the method of maintaining time phased baseline.
The IBR Review Data package shall explain the cost to schedule correlation at the work/planning package level.
The IBR Review Data package shall identify management reserve and undistributed budget.
The IBR Review Data package shall identify the authority process for allocating management reserve and undistributed budget.
The IBR Review Data package shall identify bases for allocating the cost of apportioned effort.
The IBR Review Data package shall describe the procedures for measuring performance.
The IBR Review Data package shall describe the procedures for incorporating authorized changes.
The IBR Review Data package shall provide details on the baseline through CDR.
3.15 RESPONSES TO REQUESTS FOR ACTION
1. CDRL No.: 015
2. Title: RESPONSES TO REQUESTS FOR ACTION
3. Use: To evaluate replies to issues raised during Instrument Reviews.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
Preliminary Responses to Requests for Action (RFAs) may be in any form, such as fax or telecon, to promote coordination with the Project.
Final Responses to RFAs shall include any supportive material, such as:
a) Engineering reports
b) Sketches
c) Drawing changes
d) Documentation narrative changes
e) Test reports, graphs, etc.
3.16 SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE
1. CDRL No.: 016
2. Title: SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE
3. Use: To evaluate the requirements, requirements flow-down, and the operational concepts and to validate the realism of the functional and performance requirements and their congruence with the system configuration selected to conduct the mission.
The SDR Data Package shall discuss contractor system level requirements, rationale, and flow-down plans to lower level requirements.
The SDR Data Package shall cover the STIS System Specification and the traceability matrix to applicable government requirements documents.
The SDR Data Package shall cover requirements for the STIS instrument, Ground Support
Equipment, flight software, ground test software, and processing algorithm.
The SDR Data Package shall show how the current concept meets all government specified requirements including interface requirements.
The SDR Data Package shall identify any STIS technologies that are below Test Readiness
Level (TRL) 6.
3.17 PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
1. CDRL No.: 017
2. Title: PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE
3. Use: To demonstrate the Flight Equipment and GSE designs meet the documented requirements.
The PDR data package shall include Science/Technical Objectives, Requirements, and General
Specification.
The PDR data package shall include responses to action items from previous reviews, including subsystem PDRs.
The PDR data package shall include changes since the last review.
The PDR data package shall address performance requirements.
The PDR data package shall address system performance budgets and margins.
The PDR data package shall include processor resource utilization estimates.
The PDR data package shall address error budget and error budget allocation.
The PDR data package shall address mass, power, data rate, commands, Electromagnetic
Compatibility (EMC) / Electromagnetic Interference (EMI).
The PDR data package shall address interface requirements.
The PDR data package shall address mechanical/structural design, analyses, and life tests.
The PDR data package shall address electrical, thermal, and sensor design and analyses.
The PDR data package shall address software requirements, design, and development environment.
The PDR data package shall address Ground Support Equipment design and work flow, and describe how each item will be fabricated, tested and certified when needed.
The PDR data package shall address design verification, test flow and calibration/test plans.
The PDR data package shall address instrument operations.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The PDR data package shall address parts selection, and qualification.
The PDR data package shall address preliminary Failure Modes Effects Analysis
(FMEA)/Failure Modes, Effects, and Criticality Analysis (FMECA); Fault Tree Analysis; and reliability analysis and results.
The PDR data package shall address parts stress analysis.
The PDR data package shall address redundancy and redundancy management.
The PDR data package shall address single point failures.
The PDR Data Package shall address the list of long lead items, and of items that may become obsolete prior to completion of all flight instruments, identify those items that must be procured prior to CDR, and provide a plan for procuring these items and all parts.
The PDR data package shall address contamination requirements and control plan.
The PDR data package shall address safety hazards identified for flight, range, ground hardware and operations.
The PDR data package shall delineate the status of each document required at PDR as to its acceptability for use as is.
The PDR data package shall address open interface items and the status of the Instrument
Description Document (IDD).
The PDR Data Package shall present all program risks and address their mitigation.
The PDR Data Package shall provide the status of all subcontracts and discuss the preliminary design status of critical assemblies and sub-assemblies.
The PDR Data Package shall present a summary of all breadboard and brassboard testing and present the test results.
The PDR Data Package shall present the development status of sub-assembly engineering units, and available test data.
The PDR Data Package shall address the producibility of the design solution.
The PDR Data Package shall address mission assurance to be imposed including parts and materials usage as well and workmanship standards imposed.
The PDR Data Package shall address software assurance process.
The PDR data package shall contain information to cover the STIS ground algorithm design.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The PDR Data Package shall demonstrate that all STIS technologies have achieved a TRL 6 or higher.
3.18 CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE
1. CDRL No.: 018
2. Title: CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE
3. Use: To present the Flight Equipment and GSE design and operation and S/C interface aspects, to demonstrate that all related manufacturing documentation, processes and fixtures are in place before hardware manufacture begins, and to demonstrate that the design meets all performance requirements.
The CDR data package shall include responses to action items from previous reviews, including subsystem CDRs.
The CDR data package shall include changes since the last design review.
The CDR Data Package shall address the procurement status of long lead items and Electrical, Electronic, and Electromechanical (EEE) parts.
The CDR Data Package shall address manufacturing flow, and the status of manufacturing and assembly drawings, bill of materials, etc.
The CDR Data Package shall address manufacturing procedures.
The CDR Data Package shall address mission assurance product checkpoints and evaluation criteria.
The CDR data package shall address the STIS ground algorithm design and development.
The CDR Data Package shall address standard applicable in-house processes.
The CDR Data Package shall address special/unique tooling and fixtures.
The CDR Data Package shall address facilities required for manufacturing.
The CDR Data Package shall address personnel resources (time phased).
The CDR Data Package shall address the delivery schedules for flight instruments and GSE.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The CDR Data Package shall provide status of:
a) Performance specification (subsystems and GSE)
b) Block diagram and description of operation (instrument and GSE)
c) Schematic and logic diagrams (including waveforms, and timing)
d) Mechanical configuration drawings
e) Test procedures
f) Calibration procedures
g) GSE development
The CDR data package shall address detailed analysis from FMEA/FMECA, fault tree analysis, and reliability analysis.
The CDR data package shall address parts stress analysis.
The CDR Data Package shall address worst-case analyses of:
a) Electrical circuits
b) Tolerance and tolerance sensitivity analysis (including thermal and mechanical considerations)
The CDR Data Package shall address stress analyses using NASTRAN, or compatible tool, with hand stress analysis verification.
The CDR Data Package shall address the structural frequency and other dynamic analyses
(including shock, sine sweep, and random, at a minimum).
The CDR Data Package shall address the thermal analysis.
The CDR Data Package shall address end-to-end system performance and margins.
The CDR Data Package shall address mass, power, data rate, commands, EMI/EMC.
The CDR data package shall include processor resource utilization estimates.
The CDR Data Package shall address test plans (including all environmental and calibration tests).
The CDR Data Package shall address manufacturing considerations.
The CDR Data Package shall address maintainability considerations.
The CDR Data Package shall address materials and processes lists.
Check the SWFO-L1 Portal at (UPDATE) https://goessp.ndc.nasa.gov to verify correct version prior to use.
The CDR Data Package shall provide a summary of deviations/waivers.
The CDR Data Package shall address contamination control and monitoring considerations.
The CDR Data Package shall address spares program.
The CDR Data Package shall address system safety hazards analyses.
a) Hazards identification matrix
b) Single point failure summaries
c) Risk assessment rationale
The CDR data package shall address open interface items and the status of the IDD.
The CDR Data Package shall present any additional test results from breadboard and brassboard testing.
The CDR Data Package shall present the test data from any engineering model.
The CDR Data Package shall address the status of all program risks and their mitigation.
The CDR Data Package shall…
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. Updated .