Attachment_C,_WFIRST-LIST-13054-.pdf
PDF 907 KB Posted
- Attached to
- Wide Field Infrared Survey Telescope (WFIRST) Launch Lock Vibration Isolation System (LLVIS) Federal contract opportunity
- Solicitation number
- Not on record
About this file
Attachment C, Deliverables
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Signed_Selection_letter.pdf | ||
| Final_Responses_to_Industry.pdf | ||
| Signed_RFP_letter.pdf | ||
| Electronically_Signed_RFP_Cover_Letter.pdf | ||
| Attachment_A,_WFIRST-SOW-13052--1.pdf | ||
| Final_RFP.pdf | ||
| Attachment_I,_QA_Plan.pdf | ||
| Attachment_F,_Small_Business_Subcontracting_Plan.pdf | ||
| Attachment_J,_Contractor_Proposed_Enhancements.pdf | ||
| SF_33.pdf | ||
| Attachment_B,_WFIRST-SPEC-12739-.pdf | ||
| Past_Performance_Questionnaire.pdf | ||
| Enclosure_1,_QASP_Cost-Type_Contract_Template.pdf | ||
| Enclosure_2,_IT_Security_Management_Plan_Template.pdf | ||
| Attachment_G,_IT_Security_Applicable_Documents_List.pdf | ||
| Attachment_H,_IT_Security_Management_plan.pdf | ||
| Attachment_D,_WFIRST-RQMT-05819_Released_Rev_A.pdf | ||
| Attachment_E,_533_Attach_Core_Completion.pdf |
Show all 18
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
Effective Date: March 8, 2019
Expiration Date: March 8, 2024
CHECK https://gddms.gsfc.nasa.gov/Windchill/app/
TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE.
National Aeronautics and Space Administration
Goddard Space Flight Center
Greenbelt, Maryland
WFIRST-LIST-13054, Revision -
Wide Field Infrared Survey Telescope (WFIRST), Code 448
Instrument Carrier (IC)
Launch Lock and Vibration Isolation System
(LLVIS)
Deliverable Items List and Schedule (DILS)
GSFC WFIRST CMO
March 13, 2019
Released https://gddms.gsfc.nasa.gov/Windchill/app/
LLVIS Deliverable Items List and Schedule WFIRST-LIST-13054, Revision -ii
Instrument Carrier (IC)
Launch Lock and Vibration Isolation System (LLVIS)
Deliverable Items List and Schedule (DILS)
Review/Signature/Approval Page
Prepared by:
Wes Alexander
Approved by:
David Content
Electronic Approval available on-line at: https://gddms.gsfc.nasa.gov/Windchill/app/ iii
Preface
This document is a Wide Field Infrared Survey Telescope (WFIRST)
Configuration Management (CM)-controlled document. Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee.
Proposed changes shall be submitted to the WFIRST CM Office (CMO), along with supportive material justifying the proposed change.
In this document, a requirement is identified by “shall,” a good practice by “should,” permission by “may” or “can,” expectation by “will,” and descriptive material by “is.”
Questions or comments concerning this document should be addressed to:
WFIRST Configuration Management Office
Mail Stop 448
Goddard Space Flight Center
Greenbelt, Maryland 20771 iv
Change History Log
Revision Effective Date Description of Changes
(Reference the CCR & CCB/ERB Approval Date) Revision - March 8, 2019 Initial release per WFIRST-CIR-09350 v
Table of Contents
1 INTRODUCTION
1.1 Purpose
1.2 Scope
1.3 Related Documentation
1.3.1 Applicable Documents
1.3.2 Reference Documents
1.4 Proprietary Data
2 DELIVERABLES
2.1 Definition of Maturity, Definition of Categories, and Delivery Instructions
2.2 LLVIS Contract Deliverables Requirement List (CDRL)
2.3 Government Furnished Property (GFP) Deliverables
3 DELIVERABLE ITEM DESCRIPTIONS
3.1 Hardware Deliverable Item Description
3.2 Data Deliverable Item Description
3.2.1 Verification matrix for Specification
3.2.2 Verification matrix for SOW
3.2.3 Verification Matrix for DILS
3.2.4 Work Breakdown Structure Diagram and Dictionary
3.2.5 Financial Management Reports
3.2.6 Integrated Master Schedule
3.2.7 Component and Subassembly Reports for All Subcontracted Items
3.2.8 Configuration Management Plan
3.2.9 Digital Image and Video Records
3.2.10 Kickoff Presentation
3.2.11 Preliminary Design Review (PDR)
3.2.12 Critical Design Review
3.2.13 Critical Design Review (CDR) In Support of IC CDR
3.2.14 Manufacturing Readiness Review (MMR)
3.2.15 Test Readiness Review (TRR)
3.2.16 Pre-Ship Review (PSR)
3.2.17 End Item Data Package
3.2.18 Monthly Status Reports
3.2.19 Drawing Tree
3.2.20 Document Tree
3.2.21 LLVIS Interface Control Documentation
3.2.22 Thermal Math Models and Reports
3.2.23 Mechanical CAD Model and Reports
3.2.24 Structural Math Model and Reports
3.2.25 Model Validation Plan
3.2.26 LLVIS Contamination Control Implementation Plan
3.2.27 Structural Analyses Reports
3.2.28 Correlated Structural FEM for Final IM and Reports
3.2.29 Spare Parts Plan and List
vi
3.2.30 Production Plan
3.2.31 Verification Plan
3.2.32 Individual Test Plans
3.2.33 Test Procedures
3.2.34 Test Reports
3.2.35 Transportation Handling Plan and Procedures
3.2.36 Instruction Manual for Refurbishment
3.2.37 Maintenance, Test and Operations Manual for Ground Support Equipment
APPENDIX A ABBREVIATIONS AND ACRONYMS
List of Tables
Table 1 Contractor Data Delivery and Schedule
1 INTRODUCTION
1.1 Purpose
This document is the Wide Field Infrared Survey Telescope (WFIRST) Instrument Carrier (IC)
Launch Lock and Vibration Isolation System (LLVIS) Deliverable Items List and Schedule
(DILS). This document provides specific information on the hardware and data deliverables for the LLVIS.
1.2 Scope
The Contractor shall provide the necessary personnel, facilities, services, materials, and equipment to design, analyze, develop, assemble, integrate, calibrate, test, and evaluate the
LLVIS. The Contractor shall participate in reviews, where the Government will review all documentation associated with the design, fabrication and testing of the LLVIS. The Contractor shall also supply the necessary resources to perform the subsequent LLVIS testing on site and post-delivery support for integration and testing. This work shall be performed in accordance with the deliverable requirements of this document and all application documents to the contract.
1.3 Related Documentation
The latest versions of all documents below should be used. WFIRST documents can be obtained from URL: https://gddms.gsfc.nasa.gov/Windchill/app/.
1.3.1 Applicable Documents
The following documents apply directly to the performance of the LLVIS contract. These documents establish detailed information necessary for the creation of the deliverables.
For traceability, each Applicable Document shall be traced down one level only: any applicable documents within the documents listed below are considered as applying directly to the performance of the LLVIS contract. For example, the WFIRST MAR (WFIRST-RQMT-05819) lists NASA Procedural Requirements (NPR) 7150.2 as an applicable document. Therefore, NPR
7150.2 is an applicable document with respect to this DILS. However, the documents listed in
Section P.4 of NPR 7150.2 are not considered Applicable Documents for the purposes of this
DILS.
The MAR is an Applicable Document; to the extent defined in Section 6 of the LLVIS SOW all deliverables associated with the specified requirements shall be delivered in accordance with the corresponding MAR DID’s.
Document Number Title
WFIRST-PLAN-06635 WFIRST Contamination Control Plan
WFIRST-RQMT-05819 WFIRST Mission Assurance Requirements
WFIRST-SPEC-12739 WFIRST Project LLVIS Specification Document
WFIRST-SOW-13052 WFIRST Project LLVIS Statement of Work
WFIRST-SPEC-05417 WFIRST Math Model Guidelines
1.3.2 Reference Documents
The following documents are referenced herein and amplify or clarify the information presented in this document. These documents are not binding on the content of this document.
Document Number Title
GPR-1410.2E GSFC Configuration Management
1.4 Proprietary Data
Some of the content of documents may be of a proprietary nature to the document preparing/sending Party. In the event data is deemed to be proprietary, and for which protection is to be maintained, the sending Party shall mark the document with a notice to indicate that the data therein is proprietary and shall be used and disclosed by the receiving Party and its related entities (e.g., contractors and subcontractors) only for the purposes of fulfilling the receiving
Party’s responsibilities under the WFIRST Project, and that the identified and marked technical data shall not be disclosed or retransferred to any other entity without prior written permission of the document preparer.
2 DELIVERABLES
2.1 Definition of Maturity, Definition of Categories, and Delivery Instructions
The following definitions apply to the "Maturity: Delivery Date”.
a) Maturity:
1) Preliminary. This refers to 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. This refers to a completed, thorough submission of an item for approval, review, or information. This does not preclude updating later. Any updates shall require the same
"approval/review" process as was required for the previous submissions.
b) NASA Action Required Code
A Approval: Items in this category require review and approval by GSFC or its designated representatives prior to use or implementation. GSFC shall approve/disapprove within 30 working days of receipt.
Requirements for resubmission shall be specified in letter(s) of disapproval.
R Review: Documents in this category are to be reviewed by the GSFC or its designated representatives in order to determine contractor effectiveness in meeting contract objectives. When Government review reveals inadequacies, the contractor may be requested to correct the inadequacies. GSFC shall review and comment within 20 working days of receipt.
I Information. Documents in this category are to be provided to GSFC or its designated representative for information purposes only. No
Government response is required.
c) Quantity: This provides the required number of copies for the deliverable.
2.2 LLVIS Contract Deliverables Requirement List (CDRL)
The Contractor Hardware Deliverable Items List is in the Contract.
The Contractor Data Delivery and Schedule is shown in Table 1.
The Contractor Hardware Deliverable Item Descriptions are in Section 3.1 of this document.
The Contractor Data Deliverable Item Descriptions are in Section 3.2 of this document.
Table 1 Contractor Data Delivery and Schedule
CDRL
No.
Title Reference Category Quant. Maturity: Delivery Date
PM-1 Verification Matrix for
SPEC
SOW 2.1-C R 1 Preliminary: with proposal
Baseline: at kickoff meeting
PM-2 Verification Matrix for
SOW
SOW 2.1-D R 1 Preliminary: with proposal
Baseline: at kickoff meeting
No.
Title Reference Category Quant. Maturity: Delivery Date
PM-3 Verification Matrix for
DILS
SOW 2.1-E R 1 Preliminary: with proposal
Baseline: at kickoff meeting
PM-4 LLVIS Work
Breakdown Structure
Diagram and Dictionary
SOW 2.1.1-F R 1 Preliminary: 15 Days ACA
Updates: as WBS changes occur
PM-5 Financial Management
Reports
SOW 2.1.2-C R 1 Preliminary:
- 533Q report within 30 working days ACA
- 533M reporting must begin no later than 30 days after incurrence of cost
Updates:
- 533Q: Due on the 15th of the month preceding the quarter being reported in columns 8a, 8b, and 8c.
- 533M: due no later than
(NLT) 10 working days after the close of Contractor’s monthly accounting period.
PM-6 Integrated Master
Schedule (IMS)
SOW 2.1.3-B A 1 Preliminary: 15 days ACA
Any changes to IMS shall be updated prior to the WFIRST
Monthly Review with updates by the end of 3rd week in the month.
PM-7 Component and
Subassembly Test
Reports for All
Subcontracted Items
SOW 2.1.4-C R 1 Preliminary: due 7 days after test completion
Final: due 20 days after test completion
PM-8 Configuration
Management Plan
SOW 2.1.5-F A 1 Preliminary: 30 days ACA
Final: 75 days ACA
PM-9 Digital Image and Video
Records Document
SOW 2.1.5-I R As needed
First: 30 days prior to the
LLVIS PDR
Preliminary: due 5 days after
Qualification unit and EDU
Final: due 10 days after
Qualification unit and EDU
Second: 30 days prior to the
IC CDR
All photo documentation will be provided along with the
EIDP delivery.
Title Reference Category Quant. Maturity: Delivery Date
PM-10 Kickoff Meeting
Presentation package
SOW 2.2.2-A R 2 Preliminary: 10 days before kickoff meeting
Final: day of kickoff meeting
PM-11 Preliminary Design
Review Package
SOW 2.2.4-A A 2 Preliminary: 7 calendar days before review
Final: 10 days after review
PM-12 Critical Design Review
Package
SOW 2.2.4-B A 1 Preliminary: 7 calendar days before Review
Final: 10 days after review
PM-13 Critical Design Review
(CDR) Package In
Support of IC CDR
SOW 2.2.4-C R 1 Preliminary: 7 calendar days before IC CDR
Final: 10 days after review
PM-14 Manufacturing
Readiness Review
(MRR) Presentation
Package
SOW 2.2.4-E A 1 Preliminary: 7 calendar days before review
Final: 10 days after review
PM-15 Test Readiness Reviews
Package
SOW 2.2.4-F A 1 for each review
Preliminary: 7 calendar days before both qualification and flight testing reviews
Final: 5 days after both qualification and flight testing reviews
PM-16 Pre Ship/Acceptance
Review Package
SOW 2.2.4-G A 1 for each review
Preliminary: 7 calendar days before both qualification and flight acceptance reviews
Final: Presented at each of the acceptance PSR for qualification and flight units
PM-17 End Item Acceptance
Data Package
SOW 2.2.4-H A 1 Preliminary: 7 calendar days before PSR’s for both the qualification and flight units
Final: at both qualification and flight PSR’s
PM-18 Monthly Status Report SOW 2.2.6-B R 1 Monthly Reports are due with updates by the end of 3rd week in the month.
SE-1 Drawing Tree SOW 4.2-B R 1 Preliminary: LLVIS PDR
Final: IC CDR
SE-2 Document Tree SOW 4.2-C R 1 Preliminary: LLVIS PDR
SE-3 LLVIS Interface Control
Documentation
SOW 4.3-A A 1 Preliminary: LLVIS PDR
Title Reference Category Quant. Maturity: Delivery Date
SE-4 Thermal Math Models and Reports
SOW 4.4-A R 1 Preliminary: 1 month prior to
LLVIS PDR
Update: 2 months prior to IC
CDR
Final: 15 days after IC CDR
SE-5 Mechanical CAD Model and Reports
SOW 4.4-A R 1 LLVIS top-level and component level CAD:
- Preliminary: 1 month prior to LLVIS PDR
- Update: 2 months prior to
IC CDR
- Final: 15 days after IC
CDR
Both models and reports
LLVIS:
- at any significant design update, or
- as requested to stay synchronized with the IC-level CAD development
Title Reference Category Quant. Maturity: Delivery Date
SE-6 Structural Math Model and Reports
SOW 4.4-A R 1 Stowed and Deployed load assessment:
- Preliminary: 1 month prior to LLVIS PDR
- Update: 2 months prior to IC CDR
- Final: correlated
Model Post
Transmissibility
Testing
Integrated Modeling (IM)
Models for on-orbit performance assessment:
- Preliminary: 1 month prior to LLVIS PDR
- Update: 2 months prior to IC CDR
- Final: correlated model post transmissibility testing
Note: If the deployed load assessment model can be used for IM purposes, only one deployed model needs to be provided.
Both models: updates after significant design changes
SE-7 Model Validation Plan SOW 4.4-C A 1 Preliminary: proposal
Update: LLVIS PDR
Final: IC CDR
SE-8 LLVIS Contamination
Control Implementation
Plan
SOW 4.5-B A 1 Preliminary: By LLVIS PDR
Final: By LLVIS MRR
SE-9 Structural Analyses
Reports
SOW 5.1-C R 1 Preliminary: 1 month prior to
LLVIS PDR
Update: 2 months prior to IC
CDR
Final: 15 days after IC CDR
Title Reference Category Quant. Maturity: Delivery Date
SE-10 Correlated Structural
FEM for Final IM and
Reports
SOW 5.1-E A 1 Stowed/Deployed Load
Assessment Models
- Final: 15 days after LLVIS qualification testing
IM Models
- Final: after transmissibility/ characteristic testing
SE-11 Spare Parts Plan and List SOW 5.2-B A 1 Plan: LLVIS PDR
List: LLVIS CDR
IT-1 Production Plan SOW 6.1-A R 1 Preliminary: 1 month prior to
LLVIS PDR
Final: 1 month prior to IC
CDR
IT-2 Verification Plan SOW 6.3-A A 1 60 days ACA
IT-3 Individual Test Plans SOW 6.3-B A 1 Final: 1 month prior to test start
IT-4 Test Procedures SOW 6.3-D A 1 Final: 10 days prior to test start
IT-5 Test Reports SOW 6.3-H R 1 per test
Preliminary: 5 days after test
20 days after test completion
IT-6 Transportation Handling
Plan and Procedures
SOW 6.4-B A 1 Preliminary: 1 month prior to
IC CDR
Final: 30 days before LLVIS
PSR
IT-7 Instruction Manual for
Refurbishment of the
LLVIS
SOW 6.5-B R 1 Preliminary: at LLVIS CDR
Final: 30 days before LLVIS
PSR
IT-8 Maintenance, Test and
Operations Manual for
GSE
SOW 8.0-E R 1 Preliminary: 1 month before testing begins
Final: LLVIS PSR
2.3 Government Furnished Property (GFP) Deliverables
NONE
3 DELIVERABLE ITEM DESCRIPTIONS
3.1 Hardware Deliverable Item Description
Title: Delivery of Engineering Design Units (EDU) Launch Lock CDRL No.: HW-1
SOW Paragraph 9.6
Description:
Contractor shall deliver one Launch lock EDU per WFIRST-SPEC 12739.
Applicable Documents: WFIRST-SPEC 12739
Reference Documents: WFIRST-SOW-13052
Title: Delivery of EDU of the Isolators CDRL No.: HW-2
SOW Paragraph 9.6
Description:
Contractor shall deliver one Isolator EDU per WFIRST-SPEC 12739.
Title: Delivery of Qualification Units CDRL No.: HW-3
Description:
Contractor shall deliver one Launch Lock Qualification Unit per WFIRST-SPEC 12739.
Title: Delivery of Qualification Units CDRL No.: HW-4
Description:
Contractor shall deliver one Isolator Qualification Unit per WFIRST-SPEC 12739.
Title: Flight Delivery of Launch Locks CDRL No.: HW-5
Description:
Contractor shall deliver six flight qualified Launch Locks per WFIRST-SPEC 12739.
Title: Flight Delivery of Isolators CDRL No.: HW-6
Description:
Contractor shall deliver six flight qualified Isolators per WFIRST-SPEC 12739.
Applicable Documents: WFIRST-SPEC 12739
Title: Flight Spare Delivery of Launch Lock CDRL No.: HW-7
Description:
Contractor shall deliver one spare flight qualified Launch Lock per WFIRST-SPEC 12739.
Title: Flight Spare delivery of Isolator CDRL No.: HW-8
Description:
Contractor shall deliver one spare flight qualified Isolator per WFIRST-SPEC 12739.
3.2 Data Deliverable Item Description
3.2.1 Verification matrix for Specification
Title: Verification Matrix for Specification CDRL No.: PM-1
SOW Paragraph: 2.1-C
Use:
Establish that all requirements will be met
Applicable Documents: None
Reference Documents: None
Maturity/Delivery Date:
Preliminary: with proposal
Baseline: kickoff meeting.
Preparation Information:
This matrix establishes that the contractor shall meet all the requirements in the document and will be used for tracking progress
3.2.2 Verification matrix for SOW
Title: Verification Matrix for SOW CDRL No.: PM-2
SOW Paragraph: 2.1-D
Use:
Establish that all requirements will be met
Applicable Documents: None
Reference Documents: None
Maturity/Delivery Date:
3.2.3 Verification Matrix for DILS
Title: Verification Matrix for DILS CDRL No.: PM-3
SOW Paragraph: 2.1-E
Use:
Establish that all requirements will be met
Applicable Documents: None
Reference Documents: None
Maturity/Delivery Date:
3.2.4 Work Breakdown Structure Diagram and Dictionary
Title: LLVIS Work Breakdown Structure Diagram and Dictionary CDRL No.: PM-4
SOW Paragraph: 2.1.1-F
Use:
The WBS establishes a product-oriented framework for reporting project cost, schedule, and technical performance and provides a basis for uniform planning, reporting status, project visibility, and assignment of responsibilities.
Additionally, the WBS provides a product-oriented logical subdivision of hardware, software, services, facilities, etc., that contribute to and/or make up the total project scope of effort and work.
The WBS Dictionary provides a narrative description of the work tasks and effort to be performed in each WBS element.
Applicable Documents: None
Maturity/Delivery Date:
Preliminary: 15 days ACA
Updates: as WBS changes occur.
The WBS and WBS Dictionary are two distinct project documents used for defining the approved project scope of work. The contents of each document are detailed in the following paragraphs:
a. WBS - A logical, hierarchical display of the subdivision of all project work to be completed. The WBS shall include the approved element title and element number.
b. WBS Dictionary - The WBS dictionary shall describe and document the work content of every WBS element and relevant efforts associated with each element (e.g., design, development, and manufacturing).
The WBS dictionary shall be arranged in the same order as the contract WBS.
3.2.5 Financial Management Reports
Title: Financial Management Reporting CDRL No.: PM-5
SOW Paragraph: 2.1.2-C
Use:
To provide data necessary for:
a) Projecting costs and hours to ensure that dollar and labor resources realistically support project and program schedules;
b) Evaluating the Contractors’ actual cost and fee data in relation to negotiated contract value, estimated costs, and budget forecast data;
c) Planning, monitoring, and controlling project and program resources; and
d) Accruing cost in NASA’s accounting system.
Applicable Documents: NPR 9501.2E NASA Contractor Financial Management Reporting
Maturity/Delivery Date:
Preliminary Submission:
The Contractor shall submit initial 533Q report within 30 working days ACA. The
533M reporting must begin no later than 30 days after incurrence of cost.
Further Submissions:
- 533Q: due on the 15th of the month preceding the quarter being reported in columns 8a, 8b, and 8c
- 533M: due No Later Than (NLT) 10 working days after the close of Contractor’s monthly accounting period.
Contents:
The 533M shall provide monthly data on actual and planned costs and labor hours, short-term projections, Estimate-to-Complete, and Contract Value, in accordance with
NPR 9501.2E.
The 533 shall provide monthly and quarterly contractual planned and actual expenditure data as defined by the Government including subcontractor data. It shall also include estimated cost to complete.
Financial reports shall be provided down to the WBS level 3.
The Financial Management Reports shall include reconciliation between the 533Q and the Integrated Program Management Report (IPMR). This reconciliation may be included within the required IPMR formats.
Format:
The NF 533 Financial Management Reports shall be prepared in accordance with
GSFC 52.242-90, Financial Management Reporting, and NASA FAR Supplement
(NFS) 1852.242-73, NASA Contractor Financial Management Reporting clauses.
3.2.6 Integrated Master Schedule
Title: Integrated Master Schedule CDRL No.: PM-6
SOW Paragraph: 2.1.3-B
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, including detailed subsystem schedules.
Maturity/Delivery Date:
Preliminary: 15 days ACA.
Change updates required at the end of the 3rd week of the month.
Detailed network diagrams shall be developed, delivered, and maintained for both the isolator and the launch lock schedule The Schedule shall reflect the significant activities in sufficient detail to permit adequate visibility into work progress. Schedules shall contain the approved baseline as well as current forecasted dates and shall be traceable to the approved Work
Breakdown Structure (WBS). All key milestones shall be clearly identified including: contract milestones, design reviews, readiness reviews, de-scope decision points and major receivables/deliverables among subsystems/organizations (including subcontractor effort).
Milestones shall be logically linked to related tasks. Clearly identified schedule margin tasks and dates needed for Government Furnished Property shall be included in the network. A log of changes to the schedule baseline shall be maintained and reported monthly. Critical paths, slack, and reserve shall be identified.
Scheduling Tool/Process: The Contractor shall use an application that is compatible to
Microsoft Project. The tool shall support data transfer and integration.
The following status and analysis reports shall be provided monthly:
Top-Level Contractor Summary Schedule: Top-level schedule (chart), in project compatible software, suitable for a formal presentation.
3.2.7 Component and Subassembly Reports for All Subcontracted Items
Title: Component and Subassembly Test Reports for All Subcontracted
Items
CDRL No: PM-7
SOW Paragraph: 2.1.4-C
Use:
Provides descriptions of analysis performed, drawings, inspections results, and test units, "as-run" procedures, test fixtures, test configuration, environment, test results, and any failures and corrective actions
Maturity/Delivery Date:
Preliminary: due 7 days after test completion
Final: due 20 after test completion
As a minimum, these reports shall identify the requirements, analysis performed, drawings, inspections results, and test units, "as-run" procedures, test fixtures, test configuration, environment, test results, and any failures and corrective actions.
3.2.8 Configuration Management Plan
Title: Configuration Management Plan CDRL No.: PM-8
SOW Paragraph: 2.1.5-F
Use:
To define the Contractor’s configuration management system and to provide a means of control for all changes affecting form, fit, or function and any impact on performance, cost or schedule.
Reference Documents: GPR-1410.2E GSFC Configuration Management
Maturity/Delivery Date:
Preliminary: 30 days ACA
Final: 75 days ACA
- The plan shall describe the Contractor’s configuration management organization and personnel responsibilities.
- The plan shall describe the Contractor's configuration identification system, including drawing and specification standards.
- The plan shall accommodate the requirements of the contract relative to technical direction and approvals.
- The plan shall describe the Contractor's change control system and shall include sample change documents and/or forms.
- The plan shall define the interfaces between the Contractor's change control system and
GSFC CM Office.
- The plan shall describe which types of changes will be submitted to GSFC for approval, and the process for their submittal.
- The plan shall define the Contractor's engineering data management activities
(including archiving process), documentation approvals, release procedures, and categories of release.
- The plan shall describe the Contractor's configuration status accounting system including samples of lists and reports used.
- The plan shall describe the Contractor's approach to verification and configuration audit to ensure that performance and functional requirements have been achieved by the design.
- The plan shall describe Contractor’s approach for using photographs as part of the
Configuration Management/documentation process.
3.2.9 Digital Image and Video Records
Title: Digital Image and Video Records Document CDRL No.: PM-9
SOW Paragraph: 2.1.5-I
Use:
Program status reviews; system, subsystem, and assembly packaging evaluations; and trouble shooting. Documentary electronic images of the LLVIS during key phases of fabrication and
Assembly, Integration, & Test (AI&T).
Maturity/Delivery Date:
30 days prior to LLVIS PDR.
Preliminary due 5 days after EDU and Qualification unit and EDU
Final due 10 days after EDU and Qualification unit and EDU
30 days prior to IC CDR
All photo documentation will be provided along with the End Item Data Package
(EIDP) delivery.
- Images shall be provided in digital format (JPEG, PNG, or TIFF)
- Images shall include pictures of the major subsystems, critical assemblies, the full-up system, and major GSE items.
- Images shall serve as a record of the build-up of a major subassemblies and assemblies;
e.g., a typical electronic card, mother board, electronic subsystem with cover off, etc.
- Each image shall be identified with a label containing the following information:
assembly number, serial number, description (e.g. name of the assembly), date of image, and the supplier's company name.
- Each image shall include a scale reference (e.g. rule, standard cube).
- The subject shall appropriately fill the digital frame to allow for effective magnification. Images shall include pictures of environmental test fixtures.
- Images shall be of sufficient resolution to clearly show component placement, part marking, or details that are covered or obscured at subsequent levels of assembly and/or any other operation that renders subsequent inspection impractical.
Images shall be of sufficient resolution to permit identification of components and verification of wire routings.
3.2.10 Kickoff Presentation
Title: Kickoff Meeting Presentation Package CDRL No: PM-10
SOW Paragraph: 2.2.2-A
Use:
To provide technical and programmatic information in the form of presentation slides, drawings, schematics, and schedules for distribution at kickoff meeting.
Maturity/Delivery Date:
- Preliminary: 10 days before kickoff meeting
- Final: day of the kickoff meeting
The template(s) will be mutually agreed to between the Project and the Contractor. As a minimum the presentation package should cover the following areas:
Program Management organization Chart
Review of flow-down documentation (SOW, MAR, Spec, DILS, applicable documents
Review of key baseline assumptions
Quality Assurance including non- conformance processing
Design Description review of technical approach, phasing of PDR/CDR
Preliminary Interface Control Documents
Flight Heritage including review of applicable Lessons Learned
Review of Critical Processes
Facilities
EDU and Qualification Verification Plan and Procedure
Mechanical Analysis with Boundary Conditions
Review of Potential Risks and risk mitigation plan
Review of key technical areas, confirmation of plans for TIMs
Schedule Review including critical path and margin
Review of Deliverable Items
3.2.11 Preliminary Design Review (PDR)
Title: Preliminary Design Review Presentation Package CDRL No: PM-11
SOW Paragraph: 2.2.4-A
Use:
To provide technical information on the hardware design in preparation for fabrication of
Qualification unit, and flight units.
Maturity/Delivery Date:
- Preliminary: 7 Calendar days before review
- Final: 10 days after review
Review packages shall provide the information to fully understand the design, analysis, fabrication, and testing of the LLVIS mechanism. The presentation shall 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
Preliminary Verification Plan
Flight Heritage
Schedule
Any risks
Issues and concerns
Plan forward
Conclusion
3.2.12 Critical Design Review
Title: Critical Design Review Presentation Package CDRL No: PM-12
SOW Paragraph: 2.2.4-B
Use:
To provide technical and programmatic information in the form of presentation slides, drawings, schematics, and schedules to verify that the contractor is ready to proceed to fabrication of parts and assemblies for the LLVIS.
Applicable Documents: None Reference Documents: None
Package shall provide all necessary documents, drawings and information for readiness to move to fabrication including as a minimum the following:
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
Preliminary Verification Plan
Flight Heritage
Results from completion of Life testing
Schedule
Any risks
Issues and concerns
Plan forward
Conclusion
3.2.13 Critical Design Review (CDR) In Support of IC CDR
Title: LLVIS Presentation Package In Support of IC CDR CDRL No: PM-13
SOW Paragraph: 2.2.4-C
Use:
To provide technical and programmatic information in the form of presentation slides, drawings, schematics, and schedules for IC element CDR.
Maturity/Delivery Date:
- Preliminary: 7 Calendar days before IC CDR
The Package shall identify final design, procedures, analysis, fabrication, and test of the
LLVIS system in support of the IC design
The template(s) will be mutually agreed to between the Project and the Contractor.
3.2.14 Manufacturing Readiness Review (MMR)
Title: Manufacturing Readiness Review Presentation Package CDRL No: PM-14
SOW Paragraph: 2.2.4-E
Use:
To provide technical information on the hardware design in preparation for fabrication of
Qualification unit, and flight units.
Maturity/Delivery Date:
Review packages shall provide the information to fully understand the design, analysis, fabrication, and testing of the LLVIS mechanism. The presentation shall cover the following areas. Fabrication, Assembly, and Inspection Flow plan
Key individuals that will be working the LLVIS and their training/qualifications
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)
Quality/Verification plan
GSE
Schedule
3.2.15 Test Readiness Review (TRR)
Title: Test Readiness Review Presentation Package CDRL No: PM-15
SOW Paragraph: 2.2.4-F
Use:
To provide technical information on the hardware design in preparation for testing of both the qualification unit and the flight units of each component such as the launch lock and the isolator.
- Preliminary: 7 calendar days before both qualification and flight testing reviews
(could be up to 4 reviews).
- Final: 5 days after both the qualification and the flight test reviews.
Preparation Information:
Review packages shall provide the information to fully understand the GSE, analysis, and testing of the launch lock and the isolator mechanisms. The presentation shall cover the following areas.
Quality Assurance
Electrical, Mechanical, and Environmental specifications
Detailed architectural block diagrams for the different deliverable units
Facilities
Verification Test Plan (Including Performance Test Description)
Materials and Processes
Mechanical/Structural analyses
Test plans and test procedures
Schedule
Any risks
Issues and concerns
3.2.16 Pre-Ship Review (PSR)
Title: Pre-Ship/Acceptance Review Presentations CDRL No: PM 16
SOW Paragraph: 2.2.4-G
Use:
The Pre-ship Review will demonstrate that the contractor has completed all contractual requirements identified in the Spec and SOW of this contract.
Maturity/Delivery Date:
Preliminary: 7 Calendar days before both the qualification and flight acceptance review
Final: presented at each of the qualification and flight acceptance reviews
Preliminary EIDP shall be presented along with any design changes
- Final Verification Matrix for items in the SPEC DILS SOW and MAR
- Preliminary EIDP
- Any tools and procedures required for operating the LLVIS units
- All GSE with descriptions and uses for GSFC later operations
3.2.17 End Item Data Package
Title: End Item Acceptance Data Package CDRL No: PM 17
SOW Paragraph: 2.2.4-H
Use:
The end Item data package documents the design fabrication, assembly, test, and integration of the hardware being delivered and is part of the end item delivery.
Maturity/Delivery Date:
Preliminary: 7 calendar days before PSR’s for both qualification and flight units
Final: at both qualification and flight PSR’s
The following items shall be included:
- The deliverable item name, serial number, part number, and classification status
(Flight, non-flight, GSE, LLVIS
- Appropriate approval signatures.
- As Built Serialization
- As built configuration
- In process Work Orders (available for review at contractors)
- Final assemblies and test work orders
- Major MRB actions
- Major anomaly reports with root cause and corrective action disposition
- Acceptance test procedures and reports, including environmental testing
- As built parts and materials list.
- Chronological History including total operating hours, mechanical cycles and remaining cycle life
- As built final assembly drawings
- Photo documentation with images per 3.2.9
- Waivers/Deviations
- Operations manual including setting and resetting the assemblies while in use
Certificate of compliance
3.2.18 Monthly Status Reports
Title: Monthly Status Reports CDRL No: PM 18
SOW Paragraph: 2.2.6-B
Use:
Provide monthly status to identify technical and schedule progress
Applicable Documents: None
Reference Documents: None
Maturity/Delivery Date:
Monthly Reports are due with updates by the end of 3rd week in the month
a. Description of work performed, including updated milestone plan
b. Status of open waiver requests.
c. Cumulative action item list showing open and closed action items with
ECD and assigned responsibility, as well as status of any open action items.
d. Description of significant problems and proposed solutions.
e. Risk and Opportunity management listing and status.
f. Status of Class I and Class II changes.
g. Material Review Board status.
h. Part and material status including subtier supplier status.
i. SDRL delivery status.
j. Other items as defined in applicable sections of the MAR.
3.2.19 Drawing Tree
Title: Drawing Tree CDRL No: SE-1
SOW Paragraph: 4.2-B
Use:
For ready reference list of all LLVIS flight, EDU, qualification units and LLVIS GSE drawings and documents.
Maturity/Delivery Date:
Preliminary: LLVIS PDR
- The drawing tree shall list all drawings for the LLVIS and separately for the GSE.
- The drawing trees shall be organized and identified to serve as a ready reference list.
- The drawing tree shall identify drawings by name and number.
- The drawing tree shall include a brief description of each drawing.
3.2.20 Document Tree
Title: Document Tree CDRL No: SE-2
SOW Paragraph: 4.2-C
Use:
For ready reference list of all LLVIS flight EDU, qualification units and LLVIS GSE documents.
Maturity/Delivery Date:
- The document tree shall list all documents for the LLVIS and separately for the GSE.
- The document trees shall be organized and identified to serve as a ready reference list.
- The document tree shall identify documents by name and number.
- The document tree shall include a brief description of each document.
3.2.21 LLVIS Interface Control Documentation
Title: LLVIS Interface Control Documentation CDRL No: SE-3
SOW Paragraph: 4.3-A
Use:
An Interface Control Document (ICD), developed by the Contractor, will be used to define the
LLVIS to external electrical, mechanical, and thermal interface requirements. Additionally, a
Mechanical Interface Control Drawing (MICD) will be used to define the LLVIS location relative to the IC and Spacecraft.
Maturity/Delivery Date:
The ICD shall capture all interface requirements from the LLVIS for both sides of the interfaces and shall define the necessary products and analysis required from the Contractor to support the integrated mission analyses to be performed by the WFIRST Project as the mission integrator. Typical mission analyses are integrated loads analysis, integrated thermal analyses, orbital debris analysis, etc.
The Contractor shall provide the following inputs, as appropriate, to the ICD:
Thermal Input to ICD
Thermal control coatings, blankets, heat flow and operating limits
Vent paths, grounding paths
Thermal Model Analysis Parameters
Temperature Monitoring and Thermal Control Hardware
Heaters o Resistance o Voltage range o Power range o Set Point o Heater control type
Electrical Input to ICD
Voltage Range
Current Range
Source Impedance
Interface Schematic
Termination Details
Filtering
Grounding Diagram
Interface Connector (if Applicable) o Pin (or wire if o connector) Assignment o Wire Type o Wire Gauge
Mechanical Input to ICD
Physical Requirements are;
- Mass properties
- Mass of interface fasteners
- Dimensions
- Static/dynamic volume clearance envelope
- Drill templates
- Alignment orientations
- Detailed interface definition including hole positions and tolerances, surface finishes, alignment provisions and tolerances, and other key features
- Access
- Lifting points
- Center of mass
- Moments of inertia
- Fastener size
- Surface finish
- Special surface finish
Special conditions shall be listed including but not limited to:
- Payload environments such as vibration, shock, acoustic, and purge needs.
- Safety-such as pyrotechnics, energy storage, trip-over, hazardous materials
- Ground Support Equipment- such as mechanical, test specific, targets, simulators.
- Contamination control-such as cleanliness levels, purge requirements, handling during transportation
3.2.22 Thermal Math Models and Reports
Title: Thermal Math Models and Reports CDRL No: SE-4
SOW Paragraph: 4.4-A
Use:
The LLVIS thermal math model is a mathematical representation of the heat transfer between the LLVIS, and the environment. It is integrated with the IC thermal model, and is used to evaluate the thermal performance of the instrument. This model shall accurately predict the heat flows and the resulting temperature changes for any alteration in the environment, internal power dissipation, or any other thermal model parameter.
Applicable Documents: WFIRST-SPEC-05417 Math Model Guidelines
Maturity/Delivery Date:
Preliminary: 1 month prior to LLVIS PDR
Update: 2 months prior to IC CDR
Final: 15 days after IC CDR
Thermal Model
The mathematical representation shall consist of a Thermal Model of the LLVIS The Thermal
Model shall include geometric math models (GMM), which calculate radiation couplings and environmental heat fluxes, and thermal math models (TMM), or nodal models which calculate the heat transfer and resultant temperatures. The models shall adhere to the Math Model
Guidelines (WFIRST-SPEC-05417). The model shall have sufficient detail of all critical interfaces to accurately predict temperatures. These models shall be verified and refined after comparison with thermal test data. The model shall match CBE mass to within +0 % to -5%.
A list of all nodes with nodal descriptions shall be provided. Sketches showing how nodes correspond to hardware components shall be included. Describe each node of the thermal model, its correspondence to a surface or surfaces of the GM, All models, simulations, and/or databases required by this deliverable shall be delivered on electronically compatible with the hardware platform on which it is to execute and include everything necessary to provide a fully functioning computer model in Thermal Desktop and SINDA.
Thermal Math Models shall support both steady-state and transient solutions. Thermal Math
Models shall represent all flight environments and mission modes from pre-launch through the entire mission life, as well as model the environments of the thermal balance and thermal vacuum tests.
The range of parameters used shall include allowance for natural variations, measurement uncertainties, manufacturing and assembly tolerances, degradation over the mission life, and contamination. Thermal Math Models shall include the files and description of any special analytical routines or techniques, e.g., for representing heater or other temperature control features. Any nodes or surfaces using adiabatic surfaces or arithmetic nodes (zero mass nodes) shall be noted. Thermal Math Models shall include figures showing at least the overall layout of the LLVIS with dimensions, and with significant features of the thermal control system identified (e.g., radiators, insulation,). Thermal Math Models shall include results of sample run (of the hot case, End of Life (EOL)).
Every temperature limited component, assembly or subassembly and every flight temperature sensor shall be represented by a node which predicts its temperature. Key features of the
GMM, such as geometry and coatings properties shall be traceable to the physical reality of the hardware.
Thermal Analysis Reports
Thermal analysis and design
Pre-environmental testing thermal analysis report
3.2.23 Mechanical CAD Model and Reports
Title: Mechanical CAD Model and Reports CDRL No: SE-5
SOW Paragraph: 4.4-A
Use:
The LLVIS mechanical Computer Aided Design (CAD) models are used to integrate with other models to create a complete model of the WFIRST Observatory.
Maturity/Delivery Date:
LLVIS top-level and component level CAD:
- Preliminary: 1 month prior to LLVIS PDR
- Update: 2 months prior to IC CDR
- Final: 15 days after IC CDR
- Both models and reports
- At any significant design update or as requested to stay synchronized with the IC level
CAD development
These models shall comply with the WFIRST Math Models Guidelines (WFIRST-SPEC-
05417). The parts list will be derived from the models.
A solid model is required for each project element. For each solid model two files will be created. One file will be the native software file format. If the native software produces multiple files (such as CREO version 3), then these files will be collected into one Zipped file.
The second file will be a STEP AP214 file format. There will be three files per solid configuration (native, STEP & documentation). All three files will be placed together and named after that solid configuration.
This applies to the LLVIS component/subassembly-level CAD and the LLVIS top-level CAD.
The LLVIS top-level CAD shall include all lower-level CAD.
3.2.24 Structural Math Model and Reports
Title: Structural Math Model and Reports CDRL No: SE-6
SOW Paragraph: 4.4-A
Use:
To provide instrument analysis results, interface information, and structural math models integrated into system level analysis; load derivation, operational performance, stowed dynamic, and deployment dynamic analysis.
Maturity/Delivery Date:
Stowed and Deployed load assessment:
- Preliminary: 1 month prior to LLVIS PDR
- Update: 2 months prior to IC CDR
- Final: correlated model post transmissibility testing
Integrated Modeling (IM) Models for on-orbit performance assessment:
- Preliminary: 1 month prior to LLVIS PDR
- Update: 2 months prior to IC CDR
- Final: correlated model post transmissibility testing
- Note: If the deployed load assessment model can be used for IM purposes, only one deployed model needs to be provided
Both models: Updates after significant design changes
All structural math models shall be compliant with the Math Model Guidelines (WFIRST-
SPEC-05417).
Interface degrees of freedom shall be compatible with corresponding attachment degrees of freedom to the payload.
Stowed Dynamics structural math models shall be developed to be included in system level launch configuration analysis.
Internal Finite Element Model (FEM) data recovery list for Coupled Loads Analysis (CLA) shall be provided for all GFP interfaces and LLVIS identified critical locations. Data recovery list shall include maximum allowable loads for assessment against CLA results.
The on orbit structural math model shall include time histories of forces and torques generated by LLVIS operations.
The final update of the structural model shall include any modifications required to correlate the model to the physical test results.
Documentation of the Finite Element Model shall be compliant with the MMG.
3.2.25 Model Validation Plan
Title: Model Validation Plan CDRL No: SE-7
SOW Paragraph: 4.4-C
Use:
To define the processes, encompassing testing, correlation criteria, and correlation procedures, that will be used to generate Thermal and Structural Math Models that are sufficiently accurate to predict thermal distortion, long-term material stability (moisture desorption, etc.), and jitter responses to meet WFIRST needs.
Maturity/Delivery Date:
Preliminary: Proposal
Update: LLVIS PDR
The Optical, Thermal, and Structural Math Models will be integrated into the system
Integrated Model by the WFIRST Project Integrated Modeling team and used to predict thermal distortion, jitter, and long-term material stability (moisture desorption, etc.)-induced optical responses. A subset of the error budget terms, specifically short duration stabilities, are too small to be verified by test and so will be verified analytically using the system integrated model at the IC level by the WFIRST and at the observatory level by the Project IM team. The thermal distortion, long-term material stability, and jitter analyses use multiplicative Model
Uncertainty Factors (MUFs) to bound the prediction error in the Thermal, Thermal Distortion, and Dynamics models, to which the prediction error in the IC is a contributor.
The Model Validation Plan shall define the tests, measurements, model correlation criteria, and procedures that will be used to correlate the Thermal and Structural Math Models, and validate that they are sufficiently accurate, with respect to thermal, thermal distortion, long-term material stability, and dynamics, to verify the short-term stability requirements.
Additionally, the Model Validation Plan shall define the process used to develop multiplicative
MUFs for thermal distortion, long-term material stability, and jitter that bound prediction error at the IC level that will be incorporated into the system level MUFs.
3.2.26 LLVIS Contamination Control Implementation Plan
Title: LLVIS Contamination Control Implementation Plan CDRL No: SE-8
SOW Paragraph: 4.5-B
Use:
To provide the details of how the contractor contamination control program will be implemented; this information will be reviewed to ensure consistency with the WFIRST contamination requirements.
Applicable Documents: WFIRST-PLAN-06635 WFIRST Contamination Control Plan
Maturity/Delivery Date:
Draft: by LLVIS PDR
Final: by LLVIS MRR
The CCIP shall be prepared in compliance with the WFIRST Contamination Control Plan
(WFIRST-PLAN-06635), and shall:
1. Identify the contamination sensitive hardware
2. Contain a contamination budget for all phases of the ground and flight operations conducted by the Contractor
3. Reference or include as an appendix the analyses that were used to derive the contamination budget
4. Provide methodology for achieving and maintaining the required cleanliness, including bake-out, purge, cleaning, and bagging
5. Specify which measurement and monitoring methods are used, and provide procedures or references where the methods differ from the practices specified in this document
6. Define the sequence of cleanliness activities, frequency of verification, and the capabilities of the facilities which will be occupied
7. Define the roles and responsibilities of the organizations and individuals which will implement the requirements
8. Provide descriptions of when and how the cleanliness activities are to be reviewed
9. Provide information on design features for contamination control and materials selection criteria
10. Provide information on how to train personnel and assess them
11. Define how to deal with situations that may result in cleanliness specifications not being achieved
12. Define single-point failure modes that can affect cleanliness, including equipment failures and human errors
13. Define the risk of cross-contamination between hardware elements
14. Provide references to procedures
3.2.27 Structural Analyses Reports
Title: Structural Analyses Reports CDRL No: SE-9
SOW Paragraph: 5.1-C
Use:
To aid in making judgments and decisions regarding numerous specific technical subjects relative to the LLVISs and GSE design. These analyses shall be reviewed periodically through the program both formally (design reviews), and informally (with GSFC Mechanical engineers).
Place/Time/Purpose of Delivery:
- Preliminary: 1 month…
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.