J_1(a)2_-_CDRL_List_072216_final.pdf
PDF 884 KB Posted
- Attached to
- SOFIA Science and Mission Operations Federal contract opportunity
- Solicitation number
- NNA16579196R
About this file
Contract Deliverable Requirements List (CDRL)
View the file
Other files for this federal contract opportunity
Show all 46
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
NNA16579196R ATTACHMENT J.1(a)2
CONTRACT DATA REQUIREMENTS LIST (CDRL)
SOFIA SCIENCE AND MISSION OPERATIONS SUPPORT CONTRACT
For purposes of this document, "time" is defined as follows: Time—if stated as a number of days—is calculated using business days, unless otherwise specified. It excludes Saturdays, Sundays, and legal federal holidays.
Unless otherwise specified, reports may be submitted electronically to each of the identified recipients.
Unless otherwise specified, the Authority to Proceed (ATP) date for the Initial Submission refers to the start of the contract Phase-In period.
Acronyms: [See acronym list for the SOW]
*** IDIQ CDRL – Invoked for new hardware or software developments.
Contract Deliverable Requirements List (CDRL) Index
CDRL #: CDRL Title SOW Rqmt #
General
200001 Annual Staffing Plan 2.1.1
200002 Personnel Certification Status Report 2.1.2
200003 Contractor foreign travel requests 2.2.2
200004 Contractor GFP Management Process 2.4.6
200005 Purchase requests 2.5.1
200006 Export Control Records, including ECCNs, for all international destination shipments.
2.6.3
WBS 1.01 Program Management
310100 Management Plan 3.1.1.2
310101 Contractor inputs to the IMS 3.1.2.1
310102 PMR Report on the technical, schedule, operations status and risks
3.1.3.1
310103 Assigned performance metrics 3.1.3.2
310104 Financial Monthly Report 3.1.4.1
310105 PCFR Financial Monthly Report Presentation 3.1.4.2
310106 5-year budget recommended updates 3.1.4.3
310107 Documentation and presentations of requested cost, schedule, and technical information
3.1.5.1
310108 PMB Presentation on unplanned support in agreements, MOUs, and commitments
3.1.6.4
310109 Public Engagement Program Plan 3.1.7.1
310110 SCWG minutes 3.1.7.3
310111 SOFIA Program webserver and website 3.1.7.5
310112 Published articles, web features, and press releases 3.1.7.6
WBS 1.02 Systems Engineering & Integration
310201 New system and software requirements *** 3.2.2.2
310202 Documentation for Technical Reviews 3.2.1.5
WBS 1.03 Safety & Mission Assurance
310301 Contractor Safety and Mission Assurance Plan (PM21) 3.3.1.1
310302 System Safety Hazard Analyses (PA10) Report *** 3.3.2.1
310303 Failure More Effect Analyses (PA06) Report 3.3.2.2
310304 Contractor Environmental Safety and Health (ES&H) Plan (PM22) 3.3.3.1
310305 Contractor Quality Assurance Plan 3.3.4.1
310306 Nonconformance Reports 3.3.4.2
310307 Reports of GIDEP Alerts 3.3.4.4
310308 Hardware Acceptance Data Package (ADP) (PA14) *** 3.3.4.5
310309 Recommendations for improvements in program processes and procedures
3.3.4.6
310310 Software Acceptance Data Package (ADP) (PA15) *** 3.3.5.1
CDRL #: CDRL Title SOW Rqmt #
WBS 1.04 Science & Technology
310401 SOFIA Science Operations Plan (SSOP) 3.4.1.3
310402 Science Community Engagement Implementation Plan 3.4.1.5
310403 Articles, web features, science papers, and presentations delivered to the web site
3.4.1.6
310404 PMR Monthly science engagement efforts and effectiveness report
3.4.1.8
310405 Grant Funding Distribution Plan 3.4.2.2
310406 Annual call for US cycle observation proposals (CfP) 3.4.3.1
310407 Agreements, commitments, and MOUs 3.4.3.4
310408 Observer’s handbook 3.4.3.6
310409 List of peer review panel members and statement for each that there is no conflict of interest
3.4.3.9
310410 Report and Presentation on the results of the peer review 3.4.3.11
310411 Director’s Discretionary Time (DDT) Allocation Report 3.4.3.12
310412 Draft science optimized cycle observation schedule and presentation
3.4.4.1
310413 SOFIA User Feedback Survey 3.4.5.2
310414 SOFIA User Group Survey Report and Presentation 3.4.5.3
310415 Processed L1, L2, L3 SOFIA data 3.4.6.1
310416 Correlated and archived water vapor monitor data 3.4.6.3
310417 Data Processing Cookbook 3.4.6.4
310418 SOFIA raw and processed data stored in the SOFIA Data Archive 3.4.6.5
310419 SOFIA Data Management Plan 3.4.6.6
310420 Monthly Report on timeliness and quality of the data processed and distributed
3.4.6.10
310421 Science Paper Development and Published Report 3.4.7.1
WBS 1.05 Science Instruments
WBS 1.06 Aircraft/Observatory Systems
310601 Flight display software (Workstation GUI) deliverables defined in the SOFIA Configuration Management Plan and SOFIA Software Management Plan
3.6.1
310602 Flight Management Infrastructure (FMI) software deliverables defined in the SOFIA Configuration Management Plan and SOFIA Software Management Plan
3.6.2
310603 Facility-class Science Instrument (FSI) software deliverables defined in the SOFIA Configuration Management Plan and SOFIA Software Management Plan
3.6.3
WBS 1.07 Science Mission Operations
310701 SOFIA Mission Operations Plan 3.7.1.1
310702 Draft and Final Cycle Operations Management Plan (OMP) 3.7.2.2, 3.7.2.3
310703 Science Observation Plan 3.7.2.4
310704 Science Fight Plan 3.7.2.6
310705 SOFIA Observatory Readiness Review (SObRR) presentation 3.7.2.11
CDRL #: CDRL Title SOW Rqmt #
310706 Updated FSI configuration drawings, Interface Control Documents (ICD's), and operation and maintenance manuals
3.7.3.4
310707 Provide Certified Mission Director 3.7.4.2
310708 Provide Certified Telescope Operator 3.7.4.3
310709 Post flight report 3.7.4.14
WBS 1.08 Reserved
WBS 1.09 Ground Systems
310901 IT System Security Plan for the SOFIA Science Network System 3.9.1.2
310902 Not Used
310903 Deliverables associated with the SOFIA Science Network System operation and maintenance listed in the controls implementation of the SSP package
3.9.1.3
310904 Deliverables associated with the SOFIA Platform Systems operation and maintenance listed in the controls implementation of the SSP package
3.9.1.4
310905 IT Security Continuous Monitoring Plan (SCMP) 3.9.1.5
310906 Deliverables listed in SCMP that are reviewed and tested per the schedule in SCMP
3.9.1.6
310907 Deliverables associated with sustainment of application software defined in the SOFIA Configuration Management Plan and SOFIA Software Management Plan
3.9.2.1 3.9.2.2
3.9.2.3 3.9.2.4
3.9.2.5 3.9.2.6
3.9.2.7 3.9.2.8
3.9.2.9
WBS 1.10 Integration & Test
311001 ICDs for products being updated or developed 3.10.1.2
311002 Integration, Test, Verification & Validation (ITV&V) Plan 3.10.1.3, 3.10.1.4
311003 Verification reports as defined in the ITV&V Plan 3.10.2.2
311004 Validation reports as defined in the ITV&V Plan 3.10.2.3
311005 System Test Verification & Validation Report 3.10.2.4
General
1. CDRL #: 200001 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #: 2.1.1 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Annual Staffing Plan
8. DESCRIPTION/USE: The Contractor shall provide and maintain a Staffing Plan
9. DISTRIBUTION:
CO COR SOFIA PM [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx]
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: Contractor Staffing Plan;
15: Scope/Contents:
The staffing plan shall describes the approach to staffing which satisfies the requirements of the SOW . The Staffing Plan shall include:
(i) A description of how the staffing approach meets the requirements of the SOW. If it includes other than full time personnel or cross-utilizations of skills, identify and explain.
(ii) A description of how the staffing approach acquires and retains required skills, accommodates personnel departures, staff training and certification, fatigue management, prolonged deployments, and planned and unplanned personnel absences without impacting
SOFIA operations.
(iii) A Labor Distribution and Qualification Mapping between the Staffing Plan, and the SOW
(WBS).
(iv) A description of staff special training and/or independent research allocation required to provide and maintain a skilled workforce, and a list of the job classifications to which these apply.
16. Remarks:
1. CDRL #: 200002 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #: 2.1.2 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Personnel Certification Status Report
8. DESCRIPTION/USE: The Contractor shall train and annually certify mission operations personnel supporting both ground and flight operations per the SOFIA Mission Operations Training Plan SCI-US- PLA-PM19_200E provided by NASA. As part of this task, the Contractor shall provide to NASA an annual Personnel Certifidation Status Report.
9. DISTRIBUTION:
CO COR SOFIA PM SOFIA Operations Director [xxxxxxx] [xxxxxxx] [xxxxxxx]
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: SOFIA Mission Operations Training Plan SCI-US-PLA-PM19_200E
15: Scope/Contents: During the period of performance of the contract, Contractor mission operations personnel need to be certified annually to help ensure safe and efficient flight operations. These mission essential employees also will require periodic training to enhance skills or increase knowledge in order to continue to perform the tasks defined in the contract, or to meet new mission requirements.
The Contracting Officer Representative will make the determination of whether training is mission essential.
For personnel involved in flight operations, the contractor shall establish and maintain a training and certification program and ensure that the required qualified and certified workforce can properly support flight operations.
The Personnel Certification Status Report shall list all mission operations personnel supporting both ground and flight operations; the dates of their training; date of last cerfification; and whether or not the cerification is current.
1. CDRL #: 200003 2. Issue:
3. Date:
06/15/2016
4. SOW Req #: 2.2.2 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Contractor foreign travel requests
8. DESCRIPTION/USE: The Contractor shall submit requests for foreign travel to the Contracting Officer Representative (COR) for approval
CO COR SOFIA PM [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx]
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☐ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance:
14. Applicable documents: N/A
15: Scope/Contents: The COR needs to approve all requests for foreign travel by Contractor employees.
The format and contents of the requests will be per an mutually agreed-to format by the COR and Contractor.
1. CDRL #: 200004 2. Issue:
3. Date:
06/15/2016
4. SOW Req #: 2.4.6 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Contractor GFP Management Process
8. DESCRIPTION/USE: The Contractor shall establish and maintain a Government Furnished Property (GFP) management process and deliver that process to the Government within 90 days of contract award.
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: N/A
15: Scope/Contents: This process is needed to help ensure all GFP is used appropriately and from which the Government can accurately determine the location of every item.
1. CDRL #: 200005 2. Issue:
3. Date:
06/15/2016
4. SOW Req #: 2.5.1 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Purchase requests
8. DESCRIPTION/USE: The Contractor shall submit purchase requests to the Government for approval prior to the purchase of equipment or services over $100,000 value
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: N/A
15: Scope/Contents: It is expected the Contractor will need to make purchases of goods and services on the behalf of the Government in carrying out the required tasks as defined by the requirements in this SOW. This includes mission-essential tools, equipment, or software needed to conduct the tasks in this SOW not already being supplied by the Government. This requirement provides for government input and oversight on large item purchases and enable collaboration to manage and control program costs.
NASA will determine whether items can be provided by NASA at lower cost or the Contractor will be authorized to purchase the items for NASA. The objective is to minimize cost by investigating lower cost options that NASA may have available to it such as equipment already purchased by NASA and available. The determination of whether the requested property is mission-essential will be solely at the discretion of the Contracting Officer Representative. As part of their contract oversight function, the Contracting Officer or COR may request copies of the cost estimates and/or quotations for any purchase or subcontract made on the contract regardless of value.
The format and contents of the Purchase Requests will be per a mutually agreed-to format by the COR and Contractor.
1. CDRL #: 200006 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #: 2.6.3 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Export Control Records, including ECCNs, for all international destination shipments.
8. DESCRIPTION/USE: The contractor shall provide export control records for all international destination shipments per the SOFIA Program Export Control Plan (SOF-AR-PLA-PM91-2020) and
NPR 2190
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☐ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: SOFIA Program Export Control Plan (SOF-AR-PLA-PM91-2020) and NPR
15: Scope/Contents: The SOFIA program operations involve southern hemisphere deployments that include export classification of foreign destination shipments. The contractor needs to document, provide, and maintain export control records for all international destination shipments per the SOFIA Program Export Control Plan (SOF-AR-PLA-PM91-2020) and NPR 2190.
The format and contents of the export control records will be per a mutually agreed-to format by the COR and Contractor consistent with SOFIA Program Export Control Plan (SOF-AR-PLA-PM91-2020) and NPR 2190.
WBS 1.01 Program Management
1. CDRL #: 310100 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.1.2
5. Page: 1/1
6. DATA TYPE:
☒ Scheduled Submittal ☐ Submitted Upon Request Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: Management Plan
8. DESCRIPTION/USE:The contractor develops and submits a Management Plan
9. DISTRIBUTION:
CO COR SOFIA PM ☒ Responsible Org. Dir. ☐ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the Org. Dir. being supported
10. Format: ☒ Electronic ☐ Hardcopy ☐ Contractor Format ☐ Powerpoint ☐ Word ☐ Excel ☐ .pdf
11. Initial Submission: ☐ 10 ☐ 15 ☒ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: As needed ☐ As directed by NASA ☒ Monthly Annually
13. Maintenance: N/A
14. Applicable documents:
15: Scope/Contents:.
The contractor Management Plan (MP) shall include at a minimum a discussion of management policies and procedures including any metrics/performance standards the Contractor will use to ensure;
a) high quality performance for each SOW element.
b) cost and schedule control The contractor MP shall include an organization chart(s) identifying roles of all organizational elements and reporting relationships, including job titles, clearly identifying internal and external lines of authority and relationships between the Offeror’s organization, Subcontractors, the NASA SOFIA Program organization, and SOFIA International partners.
1. CDRL #: 310101 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.2.1
5. Page: 1/1
6. DATA TYPE:
☒ Scheduled Submittal ☐ Submitted Upon Request ☐ Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: Contractor inputs to the IMS
8. DESCRIPTION/USE:The contractor submits its summary schedule and status information to the program that is integrated into the Integrate Milestone Schedule (IMS). The SOFIA PP&C office provides all monthly reporting schedules based on the schedule status supplied.
9. DISTRIBUTION:
☐ CO ☐ COR ☐ SOFIA PM ☒ Responsible Org. Dir. ☐ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the Org. Dir. being supported
10. Format: ☒ Electronic ☐ Hardcopy ☐ Contractor Format ☐ Powerpoint ☐ Word ☐ Excel ☐ .pdf
☒ Microsoft Project
11. Initial Submission: ☐ 10 ☐ 15 ☒ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☐ As needed ☐ As directed by NASA ☒ Monthly ☐ Annually
13. Maintenance: N/A
14. Applicable documents: N/A
15: Scope/Contents: The contractor is expected to have detailed internal schedules to manage the work it performs. The contractor must submit to the SOFIA PP&C office a summary schedule that has the summary tasks, major milestones, and linkages of all contractor work. The detail of the summary schedule must be such that in general the average time between major milestones do not exceed several months so that progress can be measured through completed milestones. Linkages between the contractor task/milestones must be provided. Required linkages to non-contractor SOFIA task/milestones or program controlled milestones should be included. An example is a schedule for development of a flight plan would be linked to the flight date which is controlled by the Program. The Program uses Microsoft Project for the IMS. The contractor is allowed to use any scheduling software but the input to the IMS must be in the format of microsoft Project input format. This can be in spread sheets, etc. but must include for each task/milestone, at a minimum, task/milestone id, name of task/milestone, length of task, baseline start date of task/milestone, baseline end date of task/milestone, linkages to other task/milestone, and % complete. Current date of task/milestones and current end date of task/milestones should be included if different than the baseline dates. One week prior to the SOFIA Program Monthly Review (PMR) the contractor delivers to the PP&C office, in electronic form, updates to the contractor schedules. The format of the updates is the same as the format of the initial schedule input provided, typically updating the % complete and changes to current start/end dates. Alternate IMS update formats can be established with PP&C if more streamlined approaches are possible. If the updated schedule causes a change to a program controlled milestone or negative task durration occurs, the contractor shall identify the issues as soon as they are known. One working day before the PMR, PP&C will provide to the PMR presenters requested schedules to include in the monthly reports.
Request for schedules are to be made one week prior to the PMR. It is expected that the same schedule charts will be presented each month, schedules requested to be provided every PMR need only be requested once. Only schedules from the IMS are to be used in the monthly reports. If disconnects are found with updated schedules, such as a program controlled milestone is moved, the disconnect will be identified in the schedule chart provided for the PMR.
1. CDRL #: 310102 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.3.1
5. Page: 1/1
6. DATA TYPE:
☒ Scheduled Submittal ☐ Submitted Upon Request ☐ Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: PMR Report and presentation on the technical, schedule, operations status and risks
8. DESCRIPTION/USE: The SOFIA program conducts monthly reviews of all program activities. The reports are organized by program function and delivered orally and powerpoint presentation to the SOFIA program manager, (PP&C, Operations, Science Mission Operations, Observatory Systems, Safety and Mission Assurance, Integration Office, etc). The Science Missions Operations monthly report and the Public Outreach monthly report are provided by the contractor to the program monthly review. For all other contractor task areas the contractor provides monthly report inputs to the program function the contract task area it is supporting. For example, monthly reports on task areas supporting Operations are provided to the Program Operations Director, reports on tasks supporting Observatory Systems are provided to the Program Observatory Systems Director, etc. The Directors integrate the contractor input into the monthly report and provide an integrated report to the Program Monthly Review (PMR).
9. DISTRIBUTION: Delivered to the responsible Org. Dir. , email or web site provided by the Org. Dir.
☐ CO ☐ COR ☐ SOFIA PM ☒ Responsible Org. Dir. ☐ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the Org. Dir. being supported
10. Format: ☒ Electronic ☐ Hardcopy ☐ Contractor Format ☒ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Powerpoint presentations in the format provided by the responsible Org. Dir.
11. Initial Submission: ☐ 10 ☐ 15 ☒ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☐ As needed ☐ As directed by NASA ☒ Monthly ☐ Annually
13. Maintenance: N/A
14. Applicable documents: N/A
15: Scope/Contents: The content of the reviews are the recient accomplishments, current technical, schedule, and operations status, metrics associated with the tasks being reported, and any issues and concerns. Metrics, schedules, and risks that are included in the report are to be aquired from the SOFIA program data bases. Contractor input to metrics, schedules, risks and financial reporting are covered separately in requirements 3.1.3.2, 3.1.2.1, 3.1.6.3, and 3.1.4.1. SOFIA data bases will be identified by the COR.
1. CDRL #: 310103 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.3.2
5. Page: 1/1
6. DATA TYPE:
☒ Scheduled Submittal ☐ Submitted Upon Request ☐ Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: Assigned performance metrics
8. DESCRIPTION/USE:The contractor is respnsible for providing statistical data and metrics related to the tasks performed by the contractor. The statistics and metrics are collected by the Program and made available in a single location. Only metrics from the Program are to be used in PMR charts to insure consistancy.
9. DISTRIBUTION:
☐ CO ☐ COR ☐ SOFIA PM ☒ Responsible Org. Dir. ☐ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the COR
10. Format: ☒ Electronic ☐ Hardcopy ☐ Contractor Format ☒ Powerpoint ☐ Word ☐ Excel ☐ .pdf
11. Initial Submission: ☐ 10 ☐ 15 ☒ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☐ As needed ☐ As directed by NASA ☒ Monthly ☐ Annually
13. Maintenance: N/A
14. Applicable documents: SOF-AR-PLA-PM17-2079
15: Scope/Contents: The statistical data and metrics provided by the contractor and delivered to the SOFIA confluence web site, “https://dfvmconfluence.ndc.nasa.gov:8443/display/Metrics/SOFIA+Metrics”, are identified in the SOFIA document SOF-AR-PLA-PM17-2079. The required statistical data and metrics are as follows;
1) Planned Research hours reported prior to each science flight series at the SObRR
2) Planned Research hours reported prior to each observing cycle at the time observing cycle schedule is baselined
3) Actual research hours identified in flight by the mission directors setting a MD status flag in the house keeping data log.
4) Science Flight Hours identified in flight by the Telescope Operator setting a TO status flag in the house keeping data log.
5) Data Collection time identified in flight by the Facility Science Instrument operator setting a SI status flag in the house keeping data log
6) Number of US & German observing proposals awarded, number of US & German hours awarded at selection of proposals.
7) Number of US and German proposals executed and number of observation hours executed updated monthly
8) Number of GIs flown updated monthly
9) Oversubscription ratio for hours and proposals, both Us and German, and the % of proposers that are new reported at the time of proposal selection
10) Observer feedback survey average score, help desk inquiry number and response times updated monthly
11) Science data archive usage statistics updated monthly
12) Number of accepted science papers with identification of related proposal, instrument used, and citations of the paper updated monthly
13) Time to provide Level 3 science data to investigators from the end of a flight series identified by flight series, instrument, and effected proposer updated monthly
14) Time to release Level 3 science data to the public from the end of a flight series identified by flight series, instrument, and effected proposer updated monthly
15) Number of public outreach flight representatives and science outreach flight participants flown updated monthly https://dfvmconfluence.ndc.nasa.gov:8443/display/Metrics/SOFIA+Metrics
16) Estimate of number of public and scientist reached through outreach activitiesupdated monthly
17) Number of media interactions updated monthly
1. CDRL #: 310104 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #:
3.1.4.1
5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Financial Monthly Report (FMR)
8. DESCRIPTION/USE: The Contractor shall deliver a Financial Monthly Report (FMR) to the SOFIA Program
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: N/A
15: Scope/Contents: This contract represents a major portion of the total program budget and requires periodic reporting to the SOFIA Program. The budget informatin shall be organized by WBS.
The format and contents of the Financial Monthly Report will be per a mutually agreed-to format by the COR and Contractor consistent with SOFIA Program financial reporting and tracking system.
1. CDRL #: 310105 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #:
3.1.4.2
5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Program Contract Financial Review (PCFR) Financial Monthly Report (FMR) presentation
8. DESCRIPTION/USE: The Contractor shall present a summary of the FMR at the Program Contract Financial Review (PCFR)
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☐ Excel
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: N/A
15: Scope/Contents: This presentation is a summary of the FMR. The presentation helps to ensure the Contractor financial status is clearly communicated to the SOFIA Program Office in a forum restricted to only Contractor and NASA.
1. CDRL #: 310106 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #:
3.1.4.3
5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Annual update to the SOFIA Program 5-year budget plan
8. DESCRIPTION/USE: The Contractor shall provide an annual update to the SOFIA Program 5-year budget plan.
9. DISTRIBUTION:
CO COR SOFIA PM [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx]
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually (draft and final within 5 business days from the submittal of the draft.)
Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: N/A
15: Scope/Contents: This update is needed to support NASA’s annual budget formulation cycle (PPBE).
The update needs to include budget and workforce estimates by FY and WBS.
The update shall consist of a minimum of 2 deliveries: a draft update to the SOFIA 5-year budget plan delivered on a date consistent with the program budget cycle schedule and a final update within 5 business days of the draft submittal integrating any program guidance concerning the information in the draft.
The format and contents of the Annual update to the SOFIA Program 5-year budget plan will be per a mutually agreed-to format by the COR and Contractor consistent with SOFIA Program financial reporting and tracking system.
1. CDRL #: 310107 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #:
3.1.5.1
5. Page: 1/1
6. DATA TYPE:
☐ Scheduled Submittal ☒ Submitted Upon Request ☐ Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: Documentation and presentations of requested cost, schedule, and technical information
8. DESCRIPTION/USE: SOFIA is a Congressionally reported program in the Science Mission Directorate (SMD) Portfolio, and as such is generally subject to independent reviews from internal SMD or external (GAO/IG) sources; the Contractor will need to support these reviews for content in the scope of this SOW. Included in these reviews are NASA Senior Reviews that may start in 2018 and may reoccur every two years.
9. DISTRIBUTION: SOFIA Program Manager and/or Program Scientist depending on the review being supported
☐ CO ☐ COR ☒ SOFIA PM ☐ Responsible Org. Dir. ☒ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email will be provided by the COR
10. Format: ☒ Electronic ☐ Hardcopy ☐ Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Word compatible format.
11. Initial Submission: ☐ 10 ☐ 15 ☐ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☐ As needed ☒ As directed by NASA ☐ Monthly ☐ Annually
13. Maintenance: N/A
14. Applicable documents: N/A
15: Scope/Contents: Historically SOFIA undergoes several reviews each year. The reviews typically are from GAO/IG and NASA SMD science committees. Although SOFIA has not yet participated in a NASA Senior Review it is expected that it will with a highest frequency of once every two years. These reviews require support by the contractor in the form of answering questions related to questions asked by the reviewers, developing presentation material, developing science optimization strategies, developing observatory improvement options, developing cost estimates for program change options, and assessing the science impact of proposed strategies and changes. The contractor may be asked to present to the review committees. The contractor may also be asked to provide external expertise in support of answering questions or assessing proposed concepts.
1. CDRL #: 310108 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.6.4
5. Page: 1/1
6. DATA TYPE:
☐ Scheduled Submittal ☐ Submitted Upon Request ☐ Submitted Upon Update ☒ Gov’t Approval
Required
7. TITLE: PMB Presentation on unplanned support in agreements, MOUs, and commitments
8. DESCRIPTION/USE: SOFIA is a highly integrated program with multiple centers, international partners, multiple contractors, and multiple universities participating. The work distribution between these entities must be controlled by the program. The contractor will be interfacing directly with all participants of SOFIA and needed tasks may be included in contractor agreements, MOUs, and commitments that are not in the contractors budgeted plan. The contractor is reponsible for identifying these unplanned tasks within the agreements, MOUs, and commitments prior to the commitments be finalized and presenting them to the PMB for a decision to proceed with a budget plan modification or to modify the agreement to exclude the unplanned tasks. The decision to proceed may involve negociations and modifications to other NASA agreements, MOUs, and commitments.
9. DISTRIBUTION:
☒ CO ☒ COR ☒ SOFIA PM ☐ Responsible Org. Dir. ☐ SOFIA Project Scientist ☒ SOFIA CCM
(primary) Note: Email will be provided by the COR
10. Format: ☒ Electronic ☐ Hardcopy ☒ Contractor Format ☒ Powerpoint ☐ Word ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Word compatible format
11. Initial Submission: ☐ 10 ☐ 15 ☐ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☒ As needed ☐ As directed by NASA ☐ Monthly ☐ Annually
13. Maintenance: N/A
14. Applicable documents: none
15: Scope/Contents: The Contractor presentation to the PMB shall:
identify unplanned tasks included in the agreement, MOU, or commitment, the cost impact of the activity, any impacts to other contract work or schedule, and the schedule of activities, if applicable.
identify who was responsible for the tasks prior to the proposed agreement, if any.
identify any impacts to SOFIA if the identified unplanned tasks are not completed.
1. CDRL #: 310109 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.7.1
5. Page: 1/1
6. DATA TYPE:
☒ Scheduled Submittal ☐ Submitted Upon Request ☒ Submitted Upon Update ☒ Gov’t Approval
Required
7. TITLE: Public Engagement Program Plan
8. DESCRIPTION/USE: The Program Public Engagement Plan describes how the contractor will communicate the unique and inspirational attributes of airborne astronomy and the SOFIA Program capabilities and accomplishments to the public.
9. DISTRIBUTION: SOFIA Configurtion Control Manager (Primary)
☒ CO ☐ COR ☒ SOFIA PM ☐ Responsible Org. Dir. ☐ SOFIA Project Scientist ☒ SOFIA CCM
Note: Email will be provided by the COR
10. Format: ☒ Electronic ☐ Hardcopy ☒ Contractor Format ☐ Powerpoint ☒ Word ☐ Excel ☒ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Word compatible format.
11. Initial Submission: ☐ 10 ☐ 15 ☐ 30 ☐ 45 ☐ 60 ☒ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☐ As needed ☐ As directed by NASA ☐ Monthly ☒ Annually
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue. The updated plan is due each year prior to the PPBE process, date to be provided by the COR.
14. Applicable documents: SOF-DF-FOR-PM93-2004 Rev G
15: Scope/Contents: The Program Public Engagement Plan shall include:
1) General content of NASA guidelines located at http://communications.nasa.gov/content/nasa-comm-guidelines
2) General content of “Communications Plan Template” from http://communications.nasa.gov/content/nasa-comm-guidelines
3) Metrics to be measured addressing the performance of the plan to meet objectives
4) Reporting of prior year metrics, analysis of the metrics, and plan changes resulting from prior year metrics
5) Events to be attended
6) Displays to be maintained or developed
7) Web Site format, content, and maintenance
8) Press, social media, and other forms of public communication interaction
9) Writing and publication of SOFIA articles and web features (both SOFIA web site and NASA web site)
10) Planning and escorting of flight participants related to public outreach
11) Coordination with NASA ARC, AFRC, HQ, and international partner Public Affairs Offices (PAO)
12) Center displays (eg. ARC entry sign)
13) Apon approval this plan becomes a SOFIA Program controlled document and must include a configuration change request cover page SOF-DF-FOR-PM93-2004 Rev G.
http://communications.nasa.gov/content/nasa-comm-guidelines
1. CDRL #:
310110
2. Issue:
basic
3. Date: 06/15/2016 4. SOW Req #:
3.1.7.3
5. Page: 1/1
6. DATA TYPE:
☐ Scheduled Submittal ☐ Submitted Upon Request ☐ Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: SOFIA Communications Working Group minutes
8. DESCRIPTION/USE: Minutes of the SCWG meetings are to be provided by the contractor to the participants of the SCWG and the SOFIA Project Scientist
☐ CO ☐ COR ☐ SOFIA PM ☐ Responsible Org. Dir. ☒ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the COR
10. Format: ☒ Electronic ☐ Hardcopy ☐ Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Word compatible format.
11. Initial Submission: ☐ 10 ☐ 15 ☐ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☒ As needed ☐ As directed by NASA ☐ Monthly ☐ Annually
Meetings are typically every other week. The minutes are to be delivered NLT 3 working days after the meeting
13. Maintenance: N/A
14. Applicable documents: N/A
15: Scope/Contents: The content of the minutes are to be the participants of the meeting, key topics discussed, decisions made, actions assigned, and the date and time of the next meeting.
1. CDRL #: 310111 2. Issue:
3. Date:
01/26/2016
4. SOW Req #:
3.1.7.5
5. Page: 1/1
6. DATA TYPE:
☐ Scheduled Submittal ☐ Submitted Upon Request ☒ Submitted Upon Update ☐ Gov’t Approval
Required
7. TITLE: SOFIA Program webserver and website
8. DESCRIPTION/USE: The SOFIA Program Web site must be maintained and kept current.
9. DISTRIBUTION: Web site operational is delivery
☐ CO ☐ COR ☐ SOFIA PM ☐ Responsible Org. Dir. ☐ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the COR
10. Format: ☒ Electronic ☐ Hardcopy ☒ Contractor Format ☐ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Word compatible format. Content for the website shall be that required for the website.
11. Initial Submission: ☐ 10 ☐ 15 ☒ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☒ As needed ☐ As directed by NASA ☐ Monthly ☐ Annually
13. Maintenance: As required to maintain operational and keep information on the website current
14. Applicable documents: NASA standards identified in http://communications.nasa.gov/content/nasa-comm-guidelines, and ARC PAO Policy “NASAInfoReleasePolicy-2015MAR. NIST standard identified in http://www.hq.nasa.gov/office/procurement/regs/NIST special publication 500-267.pdf.
15: Scope/Contents: The web site shall include the following;
1) Public information on the SOFIA mission such as the aircraft, telescope, mission, operations, etc.
2) Public articles on the SOFIA mission and SOFIA science results
3) Information on SOFIA science such as science calls for proposals, science papers, SOFIA science capabilities, SOFIA recient discoveries, SOFIA science conferences, etc.
4) Web features and articles on SOFIA operations and science papers
5) Directions to related NASA web sites, help desk for proposals and data analysis, data archives, dates for public release of data
6) SOFIA history, media resources such as pictures and articles, and current flight status
7) Links to social media
8) Links SOFIA partnership opportunities
1. CDRL #: 310112 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.1.7.6
5. Page: 1/1
6. DATA TYPE:
☐ Scheduled Submittal ☐ Submitted Upon Request ☒ Submitted Upon Update ☒ Gov’t Approval
Required
7. TITLE: Published articles, web features, and press releases
8. DESCRIPTION/USE: The contractor shall create and, after receiving approval from the SOFIA Project Scientist, publish articles, web features, and press releases to inform the public of SOFIA activities, accomplishments, and SOFIA's mission.
☐ CO ☐ COR ☐ SOFIA PM ☐ Responsible Org. Dir. ☒ SOFIA Project Scientist ☐ SOFIA CCM
Note: Email addresses will be provided by the COR.
10. Format: ☒ Electronic ☐ Hardcopy ☒ Contractor Format ☒ Powerpoint ☐ Word ☒ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Word compatible format.
11. Initial Submission: ☐ 10 ☐ 15 ☐ 30 ☐ 45 ☐ 60 ☐ 90 calendar days of contract authority to proceed
(ATP)
12. Submission Freqency: ☒ As needed ☒ As directed by NASA ☐ Monthly ☐ Annually
13. Maintenance: N/A
14. Applicable documents: NASA standards identified in http://communications.nasa.gov/content/nasa-comm-guidelines, and ARC PAO Policy “NASAInfoReleasePolicy-2015MAR
15: Scope/Contents: Articles, web features, press releases, social media content, etc. are developed in support of the SOFIA public outreach objectives. The outreach materials are delivered to the SOFIA project scientist and PAO offices for review. The contractor shall also coordinate with SOFIA partner PAO offices to insure that NASA and partner publications are consistant and coordinated. The content must be approved by the SOFIA Project Scientist prior to publication. Additional review may be required by the ARC, AFRC, and HQ PAO offices. The contractor shall incorporate all content change requests from the PAO offices and deliver the updated materials to the Program Scientist for consideration and approval.
WBS 1.02 Systems Engineering & Integration
1. CDRL #: 310201 2. Issue:
3. Date:
06/15/2016
4. SOW Req #:
3.2.2.2
5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: New System and software requirements (IDIQ)
8. DESCRIPTION/USE: The Contractor shall develop and deliver to NASA (for approval and baseline) all requirements generated and derived, as part of a system or software development upgrade, or modification task. (IDIQ)
CO COR SOFIA PM Responsbile OPR [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx]
Note: Email will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☐ Powerpoint ☐ Word ☐ Excel ☐ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format. If requirements are maintained in a requirement management tool, the requirements shall be submitted to the Government in an MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP) on the related IDIQ task
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: NPR 7123.1B and NPR 7150.2B.
15: Scope/Contents: NASA is the approving authority for all system and software developed as part of this contract. As such, they need to approve for baseline all requirements prior to the system being built or the software being coded. Currently, there are no SOW requirements for the contractor to develop any new systems or software. This requirement applies to the development of any new hardware or software, or upgrades or modification to existing hardware or software as directed by NASA per a separate task order (IDIQ).
The format and contents of the requirement document shall be per a mutually agreed-to format by the COR, OPR, and Contractor.
1. CDRL #:
310202
2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #: 3.2.1.5 5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Documentation for Technical Reviews
8. DESCRIPTION/USE: The Contractor shall demonstrate compliance with entrance and success criteria, as determined by NASA, for each technical review (SRR, PDR, CDR, and
TRR) prior to scheduling the review and proceeding to the next technical review.
9. DISTRIBUTION:
CO COR SOFIA PM OPR [xxxxxxx] [xxxxxxx] [xxxxxxx] [xxxxxxx]
Note: Email addresses will be provided by the COR
10. Format: Electronic Hardcopy Contractor Format ☒ Powerpoint ☒ Word ☒ Excel ☒ .pdf
Electronic copies shall be in .pdf and native format. Native format for docments, spreadsheets, and presentation shall be in MS Office compatible format.
11. Initial Submission: 10 15 30 45 60 90 business days of contract authority to proceed
(ATP)
12. Submission Freqency: Weekly Monthly As needed As directed by NASA Annually, unless waived by OPR. Within 5 10 15 business days after the addition/deletion of major content to applicable documents
13. Maintenance: Changes shall be incorporated as required by change page or complete reissue.
14. Applicable documents: NPR 7123.1B
15: Scope/Contents: The Contractor shall develop and deliver documentation that satisfy the entrance criteria and exit/success criteria for various technical reviews, including but is not limited to a Systems Requirements Reviews (SRR), Preliminary Design Reviews (PDR), Critical Design Reviews (CDR), and Test Readiness Reviews (TRR). Such documentation include review agenda, presentation charts, and design documentation. Design documentation can include technical drawings, block diagrams, schematics; system descriptions, architectural descriptions, and ICDs; test plans and procedures;
reports, analyses, and studies; failure modes and effects analysis; system manuals and/or user’s guides, spares plan, etc. Entrance and exit/success criteria for the review include documented Requests for Information and Requests for Actions that stem from the review and the Contractor’s responses to those requests.
WBS 1.03 Safety & Mission Assurance
1. CDRL #: 310301 2. Issue:
basic
3. Date:
06/15/2016
4. SOW Req #:
3.3.1.1
5. Page: 1/1
6. DATA TYPE:
Scheduled Submittal Submitted Upon Request Submitted Upon Update Gov’t Approval
Required
7. TITLE: Contractor Safety and Mission Assurance Plan (PM21)
8. DESCRIPTION/USE: The Contractor shall develop and deliver to NASA for approval a S&MA Plan (PM21) per CDRL 310301 that documents how the Contractor will comply with the safety, quality, and software assurance requirements defined in:
SOF-DA-PLA-PM21-1086, SOFIA Program Safety and Mission Assurance Plan
SOF-NASA-PLA-PM21-2089, SOFIA Safety Plan (SSP)
SOF-NASA-PLA-PM21-2090, SOFIA Quality Plan (SQP)
SOF-NASA-PLA…
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 .