Subcontract Plans and Documentation

Exhibit III to Subcontract No. TBD October 29, 2004 Mars Telecommunications Orbiter Subcontract Plans and Documentation Subcontract Data Requirements List (SDRL) and Data Requirements Descriptions (DRDs) Exhibit III Jet Propulsion Laboratory California Institute of Technology Exhibit III to Subcontract No. TBD October 29, 2004 Subcontract Plans and Documentation The documentation deliverable under the referenced Subcontract is summarized in the following Subcontract Data Requirements List (SDRL), which identifies the items to be delivered and when delivery is required. The Data Requirement Description (DRD) forms referenced in the SDRL describe the specific requirements for the item(s) to be delivered, reference documents, and other instructions as to content, format, and preparation. Non-Design Documentation Identification The Subcontractor shall display on the cover of the title page of all deliverable non-design documentation (all documents except drawings and specifications) the following minimum information: (1) Document Title (2) Subcontractor’s Name (3) Subcontract Number (4) Document Number (JPL or Subcontractor assigned) (5) DRD number and SDRL item number (6) System, Subsystem or Support Equipment Name (7) Approval Signatures (8) Project Identification, viz., ―MTO‖ (9) Date of Issue or Publication (10) Revision or Change Identification Approval Requirements Documents requiring JPL approval are identified in the column titled, ―APPROVAL CODE,‖ of the SDRL. The following codes are used to denote approval requirements: A – JPL approval is required X – JPL approval is not required JPL will review documents submitted by the Subcontractor for JPL approval and approve or provide comments within twenty (20) working days of receipt at JPL, except as otherwise provided for in this Exhibit and the Statement of Work. In the event JPL does not make a formal disposition of a given document within the required response time, or does not negotiate an extension in time, the document is approved as submitted. If the document is approved by JPL, the JPL Subcontract Manager will send an electronic approval notice to the Subcontractor. If the document requires modification before JPL approval will be granted, the following steps will be taken: 1. The modifications required by JPL will be transmitted or discussed between the cognizant parties. 2. The Subcontractor shall submit an updated version, containing the required modifications within ten (10) working days (or as otherwise specified) after the modifications have been identified. 3. If the updated version is approved by JPL, the JPL Subcontract Manager will send an electronic approval notice to the Subcontractor. Documents conditionally approved shall be resubmitted as final documents if all conditions of approval can be met exactly. If it is not possible to exactly meet the conditions of approval, the Subcontractor shall resubmit the document with all possible corrections completed and a letter explaining why the remaining corrections could not be made. Unless otherwise specified, re-submittal of data for approval shall be so identified and delivered ten (10) working days after receipt of JPL’s comments. Note: Revisions or updates to any data requirements set forth herein shall be resubmitted to JPL. The requirements and approvals for data item revisions shall be the same as applied to the original data item submittal unless specified otherwise in the SDRL or DRD. Date Due Unless otherwise specified, all periods identified in the SDRL are in working days. 1 Exhibit III to Subcontract No. TBD October 29, 2004 The following Data Requirement Descriptions (DRDs) are included in this Exhibit: DRD List Configuration Management (CM) CM-001 Flight System Configuration Management Plan CM-002 Software Configuration Management Plan CM-003 Engineering Documents CM-004 Interface Control Documents CM-005 Hardware End Item Data Packages, including HRCRs CM-006 Support Equipment End Item Data Packages, including SECRs CM-007 Software End-Item Data Packages, including SRCRs Environmental Requirements (ER) ER-001 Environmental Requirements Document ER-002 Electromagnetic Compatibility Control Plan ER-003 Assembly/Subsystem Environmental Verification Record Ground System (GS) GS-001 Flight System Dictionaries GS-002 Flight System Operations Handbook GS-003 Flight Rules GS-004 Flight System Idiosyncrasies GS-005 Flight System Team Analysis and Operations Plan GS-006 Flight System Analysis Software Implementation Plan and Interface Specifications GS-007 Flight System Operations Team Requirements Launch Vehicle (LV) LV-001 Launch Vehicle Documentation LV-002 Inputs to Missile System Prelaunch Safety Package (MSPSP) Mission Assurance (MA) MA-001 Safety and Mission Assurance Plan MA-002 Contamination Control Plan and Analyses MA-003 Materials and Processes Data MA-004 Electronic Parts Data MA-005 Reliability Data MA-006 Problem/Failure Reports (P/FR) MA-007 Material Review Board (MRB) Items MA-008 Quality Assurance Data and Documentation MA-009 Safety Data MA-010 Safety and Health Plan and Incident Reports Management System (MS) MS-001 Earned Value Management Plan MS-002 Work Breakdown Structure and Dictionary MS-003 Subcontract Budget Baseline (CBB) and Funding Profile MS-004 Integrated Master Schedule (IMS) MS-005 NASA Financial Management Report MS-006 Cost/Schedule Performance Report 2 Exhibit III to Subcontract No. TBD October 29, 2004 Program Management and Reports (PM) PM-001 Knowledge Transfer Plan PM-002 Risk Management Plan PM-003 Contractual Reports PM-004 Phase Implementation Plans PM-005 Spares and Property Management Plans PM-006 Long Lead-Time Items List Reviews (RE) RE-001 Review Plan and Data RE-002 Review Data Packages and Reports RE-003 Monthly Management Reviews System Engineering (SE) SE-001 Spacecraft and Flight System Requirements SE-002 Subsystem Specifications SE-003 Flight System Fault Protection Design SE-004 Inputs to Planetary Protection Documentation Software (SW) SW-001 Software Development Plan SW-002 Software Requirements Document SW-003 Software Design Document SW-004 Software Integration and Test Plans SW-005 Software User’s Manual Technical Document (TD) TD-001 Flight System Technical Resources Management Plan TD-002 Spacecraft Parameters Document TD-003 Flight System Telemetry and Command Simulator Users Document TD-004 Digital Images TD-005 Inputs to Flight System – Ground System Interface Control Document TD-006 Miscellaneous Analyses TD-007 Flight System Testbed, Simulators and Support Equipment Implementation Plan Integration, Test and Verification (TE) TE-001 Spacecraft and Flight System Verification Plan TE-002 Spacecraft and Flight System Integration and Test and Launch Operations Plan TE-003 Subsystem Test Plans TE-004 Inputs to Launch Site Support Plan TE-005 DSN, Ground System and MSL Compatibility Test Plans and Reports TE-006 Test and Verification Reports 3 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS CM 001 001A 001B CM 002 001A 001B CM 003 Configuration Management (CM) Flight System Configuration Management Plan Preliminary Final Software Configuration Management Plan Preliminary Final Engineering Document(s) System Preliminary Final Subsystem and Assembly Preliminary Final Engineering Change Requests (ECR) Waivers Interface Control Documents Engineering Subsystems Preliminary Final Payload Preliminary Final X = JPL Approval Not Required X A Once Once PMSR PDR – 3 mo. X X X A Once Once PMSR PDR – 3 mo. SR X X Provide JPL access to all Engineering Documents. Deliver to JPL as requested. X X X X X X X X X Per CM-001 001A 001B 002A 002B 003 X A X A A Once Once Once Once As Generated As Required PDR CDR – 3 mo. PDR – 1 mo. CDR – 1 mo. 10 days ARJC 004 CM 004 A 10 days ARJC X X X X X Per CM-001 Includes Hardware, Software, and Ground Support Equipment. 001A 001B 002A 002B X A X A Once Once Once Once PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. DA = Working Days After X X X X Project PDR Project CDR Project PDR Project CDR ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks A = JPL Approval Required DB = Working Days Before NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 4 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 003A 003B 004A 004B CM 005 001 Ground System Preliminary Final Ground Support Equipment Preliminary Final Hardware End-Item Data Packages including HRCRs Support Equipment End-Item Data Packages including SECRs Software End-Item Data Packages including SRCRs Environmental Requirements (ER) Environmental Requirements Doc Preliminary Final Electromagnetic Compatibility Control Plan Preliminary Final Assembly/Subsystem Flowdown Environmental Verification Record Preliminary Final Assembly/Subsystem Environmental Test Verification Record X A X A A Once Once Once Once Once PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. Each Delivery X X X X X X Project PDR Project CDR Project PDR Project CDR Retain documents at Subcontractor’s facility unless requested by JPL Retain documents at Subcontractor’s facility unless requested by JPL Retain documents at Subcontractor’s facility unless requested by JPL CM 006 001 A Once Each Delivery X X CM 007 001 A Once Each Delivery X X X ER-001 001A 001B ER-002 001A 001B ER-003 001A 001B 002 X A Once Once PMSR – 1 mo. PDR – 1 mo. X X X A Once Once PMSR – 1 mo. PDR – 1 mo. X X X A X Once Once Once As Generated As Generated Within 2 weeks of last environ. test DA = Working Days After X X X X For each item listed on the ERD Environmental Test/Analysis Matrix Updates to a previously submitted flowdown test specification For each item listed on the ERD Environmental Test/Analysis Matrix A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 5 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS GS 001 001A 001B 001C 002A 002B 002C 003A 003B 003C Ground System (GS) Flight System Dictionaries Command Dictionary Preliminary Final Updates Telemetry Dictionary Preliminary Final Updates Block Dictionary Preliminary Final Updates X A A X A A X A A Once Once As Required Once Once As Required Once Once As Required CDR – 7 mo. ARR – 3 mo. SR CDR – 7 mo. ARR – 3 mo. SR CDR – 7 mo. ARR – 3 mo. As Generated X X X X X X X X X Test Bed Delivery – 3 mo. X X With each Flight Software Delivery Test Bed Delivery – 3 mo. X X With each Flight Software Delivery Test Bed Delivery – 3 mo. X Update based on Test bed and ATLO results GS 002 001A 001B GS 003 001A 001B Flight System Operations Handbook Preliminary Final Flight Rules Preliminary Final Updates Flight System Idiosyncrasies Preliminary Final Updates Flight System Team Analysis and X = JPL Approval Not Required X A Once Once CDR – 1 mo. Launch – 6 mo X X Project CDR X A A Once Once As Required ATLO Start Launch – 1 yr As Generated X X X X GS 004 001A 001B X A A Once Once As Required Launch – 1 yr PSR As Generated X X X X GS 005 A = JPL Approval Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 6 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 001A 001B GS 006 Operations Plan Preliminary Final Flight System Analysis Software Implementation Plan and Interface Specification Preliminary Final Flight System Operations Team Requirements Preliminary Final Launch Vehicle (LV) Launch Vehicle Documentation Launch Site Procedures—Final Input to Integrated Launch Vehicle Test Procedures—Final Inputs to Launch Vehicle Interface Requirements Document (IRD)— Final Flight System Mathematical Model for Dynamic Analysis Preliminary Input Final Input Verification Flight System Thermal Model Flight System Dynamics Test Plan Flight System Dynamics Test Results Summary X = JPL Approval Not Required X A Once Once PDR – 1 mo. CDR – 1 mo. X X Ground System PDR Ground System CDR 001A 001B GS 007 001A 001B X A PDR – 1 mo. CDR – 1 mo. X X Project PDR Ground System CDR X A Once Once PDR – 3 mo. CDR – 6 mo. X X Ground System PDR Ground System CDR LV 001 001 002 003 A A A Once Once Once L – 5 mo. L – 6 mo. As Required X X X 004A 004B 004C 005 006 007 X X X X X X Once Once Once Once Once Once PDR + 3 mo. CDR + 3 mo. L – 10 mo. L – 10 mo. 3 mo. prior to test 3 wk. after test X X X X X X A = JPL Approval Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 7 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 008 009A 009B 010 011A 011B 011C 011D 012 013 014 Electrical Wiring Requirements for Flight Umbilical and Launch Complex EGSE Flight System Configuration Drawings Preliminary Final Flight System Launch Site Test Plan Flight System Mass Properties Report Draft Preliminary Final Update Inputs for Launch/Hold Criteria— Final Flight System Ventable/NonVentable Volumes—Final Inputs to Launch Vehicle Interface Control Document (ICD) Inputs to Missile System Pre-launch Safety Package (MSPSP) Draft Preliminary Final Mission Assurance (MA) Safety and Mission Assurance Plan Preliminary Final Update for mission operations X = JPL Approval Not Required X Once L – 19 mo. X X X X X Once Once Once Once L – 26 mo. L – 20 mo. L – 9 mo. X X X X X X X X A A X Once Once Once Once Once Once As Required L – 2 yr L – 16 mo. L – 10 mo. L – 8 wk L – 8 wk L – 7 mo. As Required X X X X X X X X LV 002 001A 001B 001C X X A Once Once Once PDR + 3 mo. CDR + 3 mo. PSR – 2 mo. X X X MA 001 001A 001B 001C X A A Once Once Once PDR – 6 mo. PDR – 1 mo. ORR – 1 mo. DA = Working Days After X X X Project PDR Project PDR A = JPL Approval Required DB = Working Days Before ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 8 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS phase MA 002 Contamination Control Plan and Analyses Contamination Control Plan Preliminary Final Contamination Source & Effects Analyses Preliminary Final Materials and Processes Data Materials Identification and Usage Lists (MIULs) Preliminary Final Qualification Plans Failure Analysis Reports Materials Usage Agreements (MUAs) Subcontractor Applicable Documents Subcontractor Limited Shelf-Life Materials Control Plan Fastener Selection List Preliminary Design List As-Designed List Updates As-Built List Electronic Parts Data Parts Lists X = JPL Approval Not Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks 001A 001B X A Once Once PDR – 6 mo. PDR – 1 mo. X X Project PDR Project PDR 002A 002B MA 003 X A Once Once PDR – 1 mo. CDR – 1 mo. X X 001A 001B 002 003 004 005 006 X A A X A A A Once Once As Required As Required As Required As Required As Required PDR – 1 mo. CDR – 1 mo. As Generated As Generated As Generated As Generated As Generated X X X X X X X X X X X X X X X X X X Project PDR Project CDR 007A 007B 007C 007D MA 004 X A X X Once Once As Required Once PDR – 1 mo. CDR – 1 mo. As Generated With EIDP X X X X X X See CM-005 (EIDP) A = JPL Approval Required NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 9 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 001A 001B 001C 001D 001E 002 003 004 005 006 007 008 009 MA 005 001A 001B 002A 002B 003A 003B 004A 004B Preliminary Design List As-Designed List As-Designed Parts List Review Results Updates As-Built List NSPARs/Associated Documentation Failure Analysis Reports Parts Specifications DPA and RGA Reports GIDEP Alert Review and Status Report Test Plans Test Reports NCMR Action Report Reliability Data Fault Tree Analysis Preliminary Final Electronic Parts Stress Analyses Preliminary Final Thermal Stress Analyses Preliminary Final Structural Stress Analysis Preliminary Final X = JPL Approval Not Required X A X X X A X X X X A X A Once Once Once Monthly Once As Required As Required As Required As Required Monthly As Required As Required Monthly PDR – 1 mo. CDR – 1 mo. CDR – 1 mo. Monthly SR As Generated As Generated As Generated As Generated Monthly Test – 6 wks Test + 1 mo. Monthly X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Project PDR Project CDR Project CDR Per RE-003 Include in EIDP, and provide direct submittal. Approval or conditional approval required prior to parts procurement. Failure Notice to JPL 3 days after occurrence. Per RE-003 X A X A X A X A Once Once Once Once Once Once Once Once PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. DA = Working Days After X X X X X X X X Project PDR Project CDR Project PDR Project CDR Project PDR Project CDR Project PDR Project CDR ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks A = JPL Approval Required DB = Working Days Before NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 10 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 005A 005B 006A 006B 007A 007B 008A 008B Worst Case Circuit Analyses Preliminary Final Worst Case Parameter Database Preliminary Final Mechanical Worst-Case Analyses Preliminary Final Single Event Effects (SEE) Analyses Preliminary Final Functional Failure Modes, Effects and Criticality Analyses (FMECA) Preliminary Final Failure Modes, Effects Analyses (FMEA) Preliminary Final Problem/Failure Reports (P/FR) X A X A X A X XA X X A Once Once Once Once Once Once Once Once PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. PDR – 1 mo. CDR – 1 mo. X X X X X X X X Project PDR Project CDR Project PDR Project CDR Project PDR Project CDR Project PDR Project CDR 009A 009B Once Once PDR – 1 mo. CDR – 1 mo. X X Project PDR Project CDR 010A 010B MA 006 001 X A A Once Once As Generated As Required As Required PDR – 1 mo. CDR – 1 mo. 2 days after Occurrence As Generated As Generated PDR SR X X X X X X Project PDR Project CDR MA 007 MA 008 001 Material Review Board (MRB) Items Quality Assurance Data and Documentation QA Documents for JPL Approval QA Documents for JPL Review A X X X 001 002 A X Once Once X X X X Provide copies or make available for review at Subcontractor’s facility within 5 DA JPL request ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before DA = Working Days After NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 11 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS MA 009 001 002 003 MA 010 001A 001B 002 Safety Data Safety Surveys Crane and Handling Equipment Inspection and Proof Test Verification Mishap Reports Safety and Health Plan and Incident Reports Preliminary Final Illness, Incident, and Injury Experience Reports Management System (MS) Earned Value Management Plan Preliminary Final Work Breakdown Structure and Dictionary Phase A/B/C/D/E Update Phase C/D Update Phase E Contract Budget Baseline (CBB) Profile and Funding Profile Phase A/B/C/D/E Update Phase C/D Update Phase E A A As Required As Required As Generated As Generated X X X X X X X X As Required As Generated X X X X X X A X Once Once Per occurrence 2 mo. ADOC 1 mo. ARJC 24 hours after occurrence X X X X X X X MS 001 001A 001B MS 002 001 002 003 MS 003 001 002 003 X A Once Once 2 mo. ADOC 1 mo. ARJC X X X X X Once Once Once 2 mo. ADOC With PM-004 With PM-004 X X X X X X Once Once Once 2 mo. ADOC With PM-004 With PM-004 X X X A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 12 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS MS 004 001 002 003 004 MS 005 001 002 MS 006 001 Integrated Master Schedule (IMS) Phase A/B/C/D/E Update Phase C/D Update Phase E Updates for all Phases NASA Financial Management Report NASA 533 M NASA 533Q Cost/Schedule Performance Report Program Management (PM) Provide in native and PDF format. X X X X Once Once Once Monthly 2 mo. ADOC With PM-004 With PM-004 MMR X X X X X X X X X X X Monthly— SR Quarterly— SR Monthly SR See Remarks SR X X X X X X X X X X X X X X X First two months of quarter, 10 DA reporting period Third month of quarter, 10 DA reporting period 10 DA close of accounting month. PM 001 001A 001B PM 002 001A 001B PM 003 001 002 003 004A Knowledge Transfer Plan Preliminary Final Risk Management Plan Preliminary Final Contractual Reports Subcontracting Report for Individual Contracts (Standard Form 294) Summary Subcontract Report (Standard Form 295) Internal Audit Reports New Technology Reports Interim Reports X A Once Once 2 mo. ADOC 1 mo. ARJC X X X A Once Once PMSR PDR – 3 mo. X X X X X X Quarterly Yearly As Required Yearly - SR SR SR As Generated SR X X X X X X X X X X X X X X X X X X X Submit quarterly for first two periods and semiannually thereafter 1 mo. after reporting period Submit at the end of each Government Fiscal Year 1 mo. after reporting period Initial report due 1 year ADOC; subsequent reports yearly thereafter SR = See Remarks A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 13 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 004B 005 006A 006B 006C Final Report DOD Industrial Plant Equipment Requisition (JPL Form 1419) NASA Property in the Custody of Contractors (NASA Form 1018) Monthly Submission Annual Submission Annual Verification of GovernmentOwned, Subcontractor-Held Property X X Once As Required SR SR X X X X X X X X Within 3 months of work completion 30 days prior to need for acquiring or fabrication of item X X X Monthly Yearly Yearly 3 DA Reporting Period SR SR X X X X X X X X X X X X X For controlled assets > $100K and for all Work in Process (WIP) and material 15 DA close of Government Fiscal Year; For all controlled assets, WIP, and material 30 DA receipt of list of controlled assets from JPL PM 004 001A 001B 002A 002B 003A 003B PM 005 001 A 001 B 002 A 002 Phase Implementation Plans Phase A/B Implementation Plan Preliminary Final Phase C/D Implementation Plan Preliminary Final Phase E Implementation Preliminary Final Spares and Property Management Plans X A X A X A Once Once Once Once Once Once 2 mo. ADOC 1 mo. ARJC PDR – 3 mos. 1 mo. ARJC Launch – 3 mos. 1 mo. ARJC X X X X X X Project PDR Spares Plan Preliminary Final Property Management Plan Preliminary Final X = JPL Approval Not Required X A Once Once PMSR – 1 mo. PDR – 1 mo. X X Project PDR X A Once Once 2 mo. ADOC PDR – 1 mo. X X ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks A = JPL Approval Required DB = Working Days Before DA = Working Days After NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 14 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS PM 006 B 001 Long Lead-Time Items List Reviews (RE) Review Plan Preliminary Final Review Data Packages and Reports Agenda Review Data Packages—Electronic Presentation Materials Review Report Action Items Monthly Management Review Review Package—Electronic Review Package—Hardcopy X As Required As Generated X RE 001 001A 001B RE 002 001 002A 002B 003 004 RE 003 001 A 001 B X A Once Once PMSR PDR – 3 mo. X X X X X X X As Required As Required As Required As Required As Required 6 wk. before reviews 5 DB Review At Review 5 DA Review Assigned Date X X X X X X X X X X X X X X X X X X X X X X X X X X X Monthly Monthly 1 DB MMR At MMR X X X X X X X X X X SE 001 001A 001B 001C SE-002 001A 001B System Engineering (SE) Spacecraft and Flight System Requirements Draft Preliminary Final Subsystem Specifications Preliminary Final X = JPL Approval Not Required X X A Once Once Once PDR – 6 mos. PDR – 2 mos. CDR – 1 mo. X X X Project PDR Project PDR Project CDR X A Once Once PDR – 2 mos. CDR DA = Working Days After X X Subsystem PDR Subsystem CDR ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks A = JPL Approval Required DB = Working Days Before NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 15 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS SE 003 001A 001B 001C SE 004 Flight System Fault Protection Design Description Preliminary Final Updates Inputs to Planetary Protection Documentation Planetary Protection Control Plan Inputs Preliminary Final Prelaunch Protection Analysis Report Inputs Post Launch Protection Analysis Report Inputs Software (SW) Software Development Plan (SDP) Preliminary Final Software Requirements Document (SRD) Preliminary Final Software Design Document (SDD) Preliminary Architectural Design Preliminary Detailed Design and Final Architectural Design Final Detailed Design X = JPL Approval Not Required X A X Once Once As Required PDR – 2 mo. CDR – 2 mo. As Generated X X X X Fault Protection PDR Fault Protection CDR 001A 001B 002 003 X A X X Once Once Once Once PDR – 6 mo. PDR – 1 mo. Launch – 6 mo. Launch + 2 mo. X X X X Project PDR Project PDR SW 001 001A 001B SW 002 001A 001B SW 003 001A 001B 001C X A Once Once PMSR PDR – 1 mo. X X Project PDR X A Once Once PDR – 2 mo. PDR X X Project PDR Project PDR X X A Once Once Once PMSR – 1 mo. PDR – 1 mo. CDR – 1 mo. X X X Project PDR Project CDR ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks A = JPL Approval Required DB = Working Days Before DA = Working Days After NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 16 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS 001D SW 004 001A 001B 001C 001D SW 005 001A 001B 001C Updated Detailed Design Software Integration and Test Plans (STP) Concept Draft Preliminary Final Software User’s Manual Draft Preliminary Final Technical Documents (TD) Flight System Technical Resources Management Plan Preliminary Final Updates Spacecraft Parameters Document Preliminary Final Updates Spacecraft Telemetry and Command Simulator User’s Document X As Required As Generated X With each software version delivered. X X X A Once Once Once Once PMSR – 1 mo. PDR – 1 mo. CDR – 1 mo. ARR – 1 mo. X X X X Project PDR Project CDR X X A Once Once Once CDR – 1 mo. ARR – 2 mo. PSR – 2 mo. X X X Project CDR TD 001 001A 001B 001C TD 002 001A 001B 001C TD 003 X A A Once Once As Required PMSR PDR – 1 mo. As Generated X X X X X X X X X Once Once As Required ARR – 1 mo. FPR – 1 mo. As Generated X X X X ARR = ATLO Readiness Review FPR = Flight Parameters Review 001A 001B Preliminary Final X A Once Once PDR – 1 mo. CDR – 1 mo. X X Project PDR Project CDR A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 17 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS TD 004 001 A 001 B Digital Images As-Built Images X X As Required As Required As Generated EIDP X X X X X TD-005 001A 001B 001C 001D TD-006 001 A 001 B TD-007 Inputs to Flight System – Ground System Interface Control Document Draft Preliminary Final Update Miscellaneous Analyses Preliminary Final X X X X Once Once Once As Required PMSR + 1 mo. PDR – 3 mo. CDR – 1 mo. As Generated X X X X X Project PDR Project CDR X X As Required As Required As Generated As Generated X X X X X X X X 001A 001B 001C Flight System Testbeds, Simulators and Support Equipment Implementation Plan Concept Preliminary Final Integration, Test and Verification (TE) Spacecraft and Flight System Verification Plan Preliminary Final X X A Once Once Once PMSR – 1 mo. PDR – 1 mo. CDR – 1 mo. X X X Project PDR Project CDR TE 001 001A 001B X A Once Once PDR – 1 mo. CDR X X Project PDR Project CDR A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 18 1. Exhibit III Subcontract Data Requirements List 3. DRD NO. 4. ITEM NO. 5. TITLE OR DESCRIPTION OF DATA 6. APPR CODE 7. FREQUENCY OF ISSUE 8. DATE DUE TO JPL 2. MTO Project Update #3 9. PROJECT PHASES B C A D E October 29, 2004 10. REMARKS TE 002 001A 001B 001C 001D TE 003 001 002 TE 004 001 002 TE 005 Spacecraft and Flight System Integration and Test and Launch Operations Plan Draft Preliminary Final Update Subsystem Test Plans Preliminary Final Inputs to Launch Site Support Plan Preliminary Final DSN, Ground System and MSL Compatibility Test Plans and Reports Preliminary Plans Final Plans Reports Test and Verification Reports Flight System Test Reports Flight System Verification and Validation Reports Testbed Test Reports Verification and Validation Reports for Testbeds X X A X Once Once Once Once PDR – 1 mo. CDR – 2 mo. ARR – 3 mo. PSR – 1 mo. X X X X X X Once Once CDR TRR X X X Subsystem CDR Subsystem TRR X A Once Once Launch – 14 mo. Launch – 7 mo. X X 001A 001B 001C TE 006 001 002 003 004 X A A Once Once Each test CDR + 2 mo. 30 DB Test 10 DA Test X X X Project CDR X X X X X X X X 30 DA Test 10 DB PSR 30 DA Test Prior to FS tests X X X X Once for each test performed After Performance and Environmental Test A = JPL Approval Required X = JPL Approval Not Required DB = Working Days Before DA = Working Days After ARJC = After Receipt of JPL Comments ADOC = After Date of Contract SR = See Remarks NOTE: Updates of all documents shall be provided As Required and As Generated. (Approval Code for Updates is the same as for the Original Version.) 19 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Configuration Management Plan USE: The Plan describes the methods and procedures used to manage the functional and physical characteristics of configuration items, and their interfaces and identification documents, during design, fabrication, assembly, and testing. DRD INTERRELATIONSHIP: CM-002, CM-003, CM-004 CM-001 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Information, Information Technology and Configuration Management Plan, D-29298 PREPARATION INFORMATION: 1. The Subcontractor’s Flight System CM Plan shall describe how the Subcontractor will manage the configuration in accordance with D-29298. 2. The Subcontractor Flight System CM Plan shall also address the following: a. The plan shall describe the Subcontractor’s configuration management organization and personnel responsibilities for meeting the MTO Project’s CM requirements. b. The plan shall describe the Subcontractor’s configuration identification system, including model, drawing and specification standards. c. The plan shall accommodate the requirements of the Subcontract relative to JPL technical direction and approvals. d. The plan shall describe the Subcontractor’s change control system and shall include sample change documents. As a minimum, the plan shall require a change description for each revision letter of every document changed. e. The plan shall define the interfaces between the Subcontractor’s change control system and JPL’s System. f. The plan shall define the Subcontractor’s expected time required for processing changes. g. The plan shall define the Subcontractor’s engineering data management activities (including archiving process), CM process workflows, documentation approvals, release procedures, and categories of release. h. All web-based reporting from the CM system shall report through JPL’s Teamcenter Product Data Management System (PDMS) system. i. The plan shall describe the Subcontractor’s approach to verification and configuration audit to ensure that performance and functional requirements have been achieved by the design. 20 Subcontract No. __________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Configuration Management Plan USE: The Plan describes the methods and procedures used to manage all software configuration items, and their interfaces and identification documents, during architectural and detailed design, implementation, unit testing, integration and system test. DRD INTERRELATIONSHIP: CM-001, MA-001 SW-001 PREPARATION INFORMATION: CM-002 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan JPL D-28353 1. The Subcontractor’s Software (SW) CM Plan shall describe how the Subcontractor will manage the complete software configuration in accordance with the Subcontractor’s CM Plan CM-001 and the MTO Software Management Plan JPL D-28353. 2. The Subcontractor’s SW CM Plan shall also address the following: a. The plan shall describe the Subcontractor’s configuration management organization and personnel responsibilities for meeting the MTO Project’s SW CM requirements. b. The plan shall describe the Subcontractor’s software configuration identification system, including system, component and module specification standards and its compliance with JPL CM policy and procedures (see above reference docs). c. The plan shall accommodate the requirements of the Subcontract relative to JPL technical direction, CM technical management and approvals. d. The plan shall describe the Subcontractor’s software change control system, its compatibility with the JPL institutional systems, and shall include sample change documents. As a minimum, the plan shall require a change description for each revision of every design, model, document, component and module changed. e. The plan shall define the interfaces between the Subcontractor’s change control system and JPL’s System. All web-based reporting from the software CM system shall report through JPL’s Teamcenter Product Data Management System (PDMS) system. f. The plan shall define the Subcontractor’s expected time required for processing changes. g. The plan shall define the Subcontractor’s engineering data management activities (including archiving process), CM process workflows, design, implementation and documentation approvals, release procedures, and categories of release and software build measurements. h. The plan shall describe the Subcontractor’s plan to provide JPL with access to in-process and completed software designs, implementations, test procedures and data, documentation and other items related to software development activities. i. The plan shall describe the Subcontractor’s approach to verification and configuration audit to ensure that performance and functional requirements have been achieved by the design. 21 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Configuration Management Plan (Cont.) USE: DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Cont.) CM-002 PROJECT: MTO APPLICABLE DOCUMENTS: 2. The Subcontractor’s SW CM Plan shall also address the following: (Cont.) j. The plan shall describe how the following items are to be configuration managed: i. Change requests ii. Problem, failure, and anomaly reports, including how these are tracked to closure iii. Requirements iv. Design v. Code vi. Associated data files vii. Documentation viii. Subcontractor and Second-Tier Subcontractor CM systems ix. Compilers, operating systems, and other tools used in the development environment x. Testbed environment and reporting: including test harness, test cases, test results, baseline, and releases. xi. Operating system, target processors/systems, and other COTS components incorporated into the final product. xii. Access authority for change control and measurement reporting xiii. Change control process xiii. Build process and procedures xiv. The details of the interface between project CM and lower-level CM system The plan shall describe the metrics to be collected and reported to JPL, including schedule, effort, size and defect data. k. 22 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Engineering Documents USE: To describe Flight System configuration data developed for MTO. DRD INTERRELATIONSHIP: CM-001, PM-001 PREPARATION INFORMATION: CM-003 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Information, Information Technology and Configuration Management Plan, D-29298 1. Provide Documents, Drawings, Schematics, and Associated Lists in accordance with MTO Configuration Management Plan, D-29298 in electronic format. 2. Prepare engineering drawings, block diagrams, schematics, and associated lists describing each deliverable and if applicable, firmware control drawings. Documentation shall be sufficient to specify procurement, manufacture, inspect, test and integrate the deliverable items. 3. Maintain all documents per PM-001. Provide copies to JPL as requested. 4. Prepare and update engineering documentation identified below: (a). (b). (c). (d). A Data List delineating each deliverable Configured item. An Indentured Drawing List for each deliverable item showing an indenture to each major assembly and subassembly. An Engineering Parts List for each deliverable item assembly drawing which may be integral to its parent drawing or provided as a separate engineering drawing. Drawings, Schematics, Data and Associated Lists identified in the data list, except JPL controlled drawings, and all subsequent changes to the documentation, including change authorization and implementation paper. Drawings and Models All drawings shall be submitted as Portable Document Format (PDF) files and Computer-Aided Design (CAD) files. The CAD files for drawings and models shall be delivered in ISO 10303 Standard for the Exchange of Product Model Data (STEP) format and also in native format. It is desired that the delivery be directly into the JPL Institutional Product Data Management System to integrate with the master model and that this take place throughout the design phase. Document Tree and Drawing Tree Summary trees that document Subcontractor-developed documentation. Waivers to specified requirements shall be generated in accordance with JPL-approved Configuration Management Plan Engineering Change Requests (ECRs) shall be processed for changes to the established baseline after deliverable hardware and software (if applicable) are placed under configuration management (e). (f). (g). (h). 23 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Interface Control Documents USE: Describe and control the complete interface between the spacecraft and (1) the engineering subsystems and assemblies, (2) the payload assemblies, (3) the ground system and (4) the ground support equipment. DRD INTERRELATIONSHIP: CM-001, SE-001 PREPARATION INFORMATION: CM-004 PROJECT: MTO APPLICABLE DOCUMENTS: These documents describe the requirements and detailed implementation of all interfaces between the spacecraft and the engineering subsystems and assemblies, the payload assemblies, the ground system and the ground support equipment (including test-beds, simulators, etc.) to a level of detail sufficient to fabricate compatible hardware and software. These documents include both flight hardware and software and ground test interfaces and integrate all information to fully describe both sides of all interfaces. These documents will include a description of the following interfaces [where applicable] connectors, power, data, software, mechanical mounting, thermal, environmental, flight operations, ground operations, test, handling, installation, ground support equipment, services, documentation and interface verification. Separate detail implementation documents such as electrical and mechanical interface control documents/drawings, software interface specifications and operational agreements shall be created as required to describe and control the interfaces. 24 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Hardware End-Item Data Packages including HRCRs USE: Hardware Review & Certification Record (HRCR) DRD INTERRELATIONSHIP: CM-003, CM-004, MA-006, MA-007 TD-004, TD-006, TE-002, TE-007 CM-005 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan D26471 PREPARATION INFORMATION: An end item data package shall be prepared for each ATLO deliverable assembly. The Subcontractor shall determine the form of the package. The contents of the package shall include, but not be limited to, the following information: (1) As-Built data: ―As-Built‖ hardware documentation is a compilation of items describing exactly the configuration of a fabricated serialized assembly including: a. Part number and revision letter of each item b. Part description (title) of each item c. Electronic part reference designation d. Manufacturer e. Procurement specification or Source Control Drawing (SCD) number and SCD revision letter. f. Parts and material lists with mass estimates, and material samples (when applicable) g. Actual part marking h. Traceability number (as assigned) i. Lot date code (when applicable) j. Test/screening lot numbers (when applicable) k. Wafer and wafer lot number (when applicable) l. Serial number (for serialized parts) (2) A complete manufacturing and quality history of the deliverables, including all manufacturing travelers or manufacturing and test logs, and descriptions of manufacturing environments. Documentation of any contamination bake-out/dry-heat microbial-reduction processes performed (when applicable) (3) A complete shortage list which itemizes discrepancies between the subject hardware and the requirements of the detail specification. The list shall also itemize the documentation shortages. (4) Operating time data on all major electronic assemblies and time sensitive items. (5) A complete list of the tests performed including a compilation of test data and test results for each test. (6) A copy of all action items generated against the equipment, including open or closed status (7) A copy of all problem/failure reports generated against the equipment, including open or closed status. (8) A copy of all QA discrepancy reports generated against the equipment, including open or closed status. (9) A summary of all deviations and waivers applicable to the deliverable items. a. A copy of all MRBs including open or closed status. b. A summary list of all ECRs generated against the equipment, including open and closed status (12) Evidence of acceptance by Subcontractor QA. (13) Environmental test report(s) applicable to the deliverable item, including thermal vacuum bake-out. (14) Vendor parts and material certification forms (as applicable). (15) Handling and operating constraints, including unique, specific instructions for safety, handling, packaging, storage and shipping, as applicable. (16) Precap photographs for each assembly. (17) A one time delivery, with updates as required: a. A copy of all Environmental Analysis. b. A copy of the Packaging Qualification Verification Report. c. A complete and up-to-date top assembly drawing of each type of delivery. d. A complete and up-to-date mechanical and electrical ICDs for each delivery. e. For electronic assemblies, a complete set of circuit schematics and circuit data sheets. (18) Completed Hardware Review and Certification Record (HRCR) form or JPL-approved equivalent. 25 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Support Equipment End-Item Data Packages including SECRs USE: To document the design, fabrication, assembly, integration, and test history of the Support Equipment deliverables. DRD INTERRELATIONSHIP: TD-004 PREPARATION INFORMATION: CM-006 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan D26471 Support Equipment (SE) End Item Data Packages An end item data package prepared for each deliverable assembly shall include the following: 1. The following documents shall be provided with each type of Support Equipment: a. A complete and up-to-date top assembly drawing b. A complete and up-to-date set of schematics for custom designs c. A complete and up-to-date set of mechanical drawings d. A complete and up-to-date set of Circuit Data Sheets e. A complete and up-to-date set of software design documentation, if software is part of the SE f. Cabling/Connector interconnect diagrams g. A complete and up-to-date FMECA h. A complete and up-to-date test procedure i. Photographs of the hardware assemblies j. SE User’s Guide with operating and emergency procedures 2. The following data shall be provided each deliverable assembly. The contents shall include, but not be limited to the following information: a. As-built materials list for all items used in the fabrication of the assembly. b. Shortage list itemizing discrepancies between the subject hardware and the requirements. c. A copy of all material MRB actions and discrepancy reports generated against the equipment. d. A copy of all action items generated against the equipment, including open and closed status. e. A copy of all problem/failure reports generated against the equipment, including open and closed status. f. A summary of all deviations and waivers applicable to the deliverable items. g. If mechanical ground support equipment, copies of proof-test records and certification. h. Evidence of acceptance by the Subcontractor QA i. As-run test procedure with test results. j. COTS Description and Manufacturers’ documentation including, as a minimum, the following: a. Calibration and maintenance procedures and instruction manuals. b. Manufacturers’ software. 3. Completed Support Equipment Certification Record (SECR) form or JPL-approved equivalent. 26 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software End Item Data Package including SRCRs USE: Software Review & Certification Record (SRCR) DRD INTERRELATIONSHIP: CM-002, MA-001 CM-007 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan D26471; MTO Project Software Management Plan, D-28353 PREPARATION INFORMATION: A software end item data package or software release/delivery package shall be prepared for each software and firmware delivery. The Subcontractor shall determine the form of the package. The contents of the package shall include, but not be limited to, the following information: (1) As-built product identification, including: a. Identification of software release by program ID, phase, version, date, and build. b. Operating system name and version. c. Programming language name, compiler name, and version. d. Supporting development environment name and version (if any). A Release Description Document (RDD) or equivalent which contains: a. Functional Requirements/Capabilities of the build. b. Instructions or user manual to install and configure the software application, including special test equipment software which are required to support the primary software application (if any). c. Lists of all software deliverables in this build, including special test equipment software (if any), test data, hardware configurations used for test, etc. List of dates and versions of all required documents (under Configuration Management control). A list of all open/closed anomalies or liens against this delivery. All red-flag anomalies should be closed prior to this delivery review. Verification test procedures/results. For Class A/B software, Acceptance Test Plan/Procedures/ Report shall be provided. Test Verification Traceability Matrix against software requirements. Completed Software Review and Certification Record (SRCR) or JPL-approved equivalent. Executable code and source code. (2) (3) (4) (5) (6) (7) (8) 27 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Environmental Requirements Document USE: To document environmental design and test requirements for the Spacecraft and Payloads. DRD INTERRELATIONSHIP: ER-002, SE-003 ER-001 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan D-26471 MTO Preliminary ERD: JPL D-26405 PREPARATION INFORMATION: The MTO Preliminary Environmental Requirements Document D-26405 may be used as the basis for the ER-001 submittal, either in whole or in part, with the appropriate Subcontractor-derived environments and environmental test and analysis matrix, or it may be used as a guide for preparing a separate document. In either case, the ER-001 submittal shall be consistent with the intent of the MTO preliminary Environmental Requirements Document and shall be subject to JPL approval. Environmental Requirements Document (ERD) shall define the overall environmental program policy and requirements and the environmental verification program. It shall define the environmental design and test requirements and program for the Spacecraft and assemblies/subsystems and payloads. It shall provide an environmental test and analysis matrix comprised of all Spacecraft and Payload assemblies to the lowest environmentally tested unit and designate what environmental tests and analyses are to be performed. Designations will state what level of test is to be performed (i.e., Qualification, Protoflight, or Flight Acceptance). It will state whether each item is: 1. heritage/spare from another program; 2. heritage design from another program; or 3. a new design or configuration for MTO. Dynamics (acoustics, random vibration, pyro shock) design/test levels and durations, thermal vacuum or atmosphere design/test levels and durations, charged particle radiation environments and design levels, micrometeoroids, and other expected environments shall be designated. The number of thermal and mechanical test cycles shall be designated, when applicable. The document shall include requirements for all assembly/subsystem and system environmental tests. It addresses instrumentation requirements, test configuration and installation requirements, and equipment operating states during the environmental test activities. It also includes all environments (levels, durations, tolerances, and control parameters) that are to be verified by tests at the assembly/subsystem and system levels. This document may be subdivided into design and test specification sections. Payloads shall be considered as Flight System subsystems and interface environments shall be called out. Electromagnetic Compatibility shall be described in a separate Electromagnetic Compatibility Control Plan (ER-002). 28 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Electromagnetic Compatibility Control Plan USE: To define the policy, process, and methodology used to attain compatibility with the electromagnetic environment and requirements associated with the mission. DRD INTERRELATIONSHIP: ER-001, SE-002 ER-002 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan JPL D-26471 PREPARATION INFORMATION: This plan describes the electromagnetic compatibility (EMC) environments, test methods and requirements, and the organizational structure with the responsibility for compliance with EMC requirements. This plan provides both an overview of the EMC test program as well as its specific applicability to each assembly/subsystem and for the Flight System. Subcontractors’ responsibilities for EMC control are also included. The EMC Control Plan shall address the following topics, as a minimum 1. EMC constraints on the Flight System 2. EMC requirements to be fulfilled 3. EMC design requirements 4. EMC test/analysis program for each assembly/payload and system 5. How compliance to the EMC requirements is to be verified 29 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Assembly/Subsystem Environmental Verification Record USE: To document the flowdown of details for verifying compliance to the environmental test/analysis matrix in the MTO Environmental Requirements Document (ERD) DRD INTERRELATIONSHIP: ER-001, ER-002 ER-003 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan JPL D-26471 PREPARATION INFORMATION: 1. The Subcontractor shall provide the specifications flowed down to both vendors and in-house organizations containing the environmental test requirements for each assembly/subsystem and unit listed in the ERD environmental test and analysis matrix, other than GFE units. 2. The Subcontractor shall subsequently provide a test verification record for each assembly/subsystem listed in the ERD environmental test and analysis matrix, other than GFE units. The record shall contain, as a minimum: any test deviations from the flowdown specifications; the test results (pass/fail); and details of anomalies during the test and their resolution; any requirement verified ―by similarity‖ or ―by heritage‖ and not by environmental test shall be so designated. 30 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Dictionaries USE: Command and Telemetry Dictionaries provide information regarding the structure, formatting, and meaning of Flight System commands and telemetry. Block Dictionary defines a set of Flight System commands that perform specific functions. DRD INTERRELATIONSHIP: GS-001 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit IV - Mission Operations Requirements PREPARATION INFORMATION: 1. Command Dictionary: The command dictionary will be specified through both a document and an electronic database. This document will describe the general on board commanding process and detailed spacecraft and payload commands including the following attributes: These attributes will also be specified in a database. a. Command name b. Command op code c. Command parameters d. Applicable subsystems e. Telemetry effects including confirming telemetry for command verification f. Whether this command is a restricted command or not (Restricted commands are commands which if executed improperly could result in permanent damage to the spacecraft, or other undesirable operational impacts) g. Whether this command can be sent as immediate command h. Whether this command can be used in block/sequence i. Whether this command can be treated as non-interactive command, i.e., executing this command will not change the state of the spacecraft, e.g. payload commands which only change internal payload status. 2. Telemetry Dictionary: The telemetry dictionary will be specified through both a document and an electronic database. This document will describe the general on board telemetry process and detailed spacecraft and payload telemetry including the following attributes: These attributes will also be specified in a database. a. Telemetry identifier b. Subsystems to which the measurement belongs c. Description d. Length in bits e. Type of telemetry (analog, discrete) f. Type of data when it is downlinked or derived on the ground (floating point, signed integer) g. Engineering unit h. Sample rate i. Sample type: type of data when the data is sampled (double precision, floating point) j. Polynomial coefficients used in converting the measurement to engineering unit. 3. Block Dictionary: A ―block‖ is a series of time tagged commands stored on board that perform specific functions over a preset time period. The Block Dictionary will contain a general description of the block construction philosophy and for each block, the following characteristics; including, but not limited to: a. Block description: (1) Block Title, (2) ID, (3) Description b. Command listing of events required to achieve the block goal along with relative timing, constraints, and expected telemetry c. Ancillary information such as the time of initiation, required configuration, inputs, constraints and conditions that the blocks can be performed 31 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Operations Handbook GS-002 USE: PROJECT: To provide descriptive material of the flight system to support MTO development of flight sequences and to provide information needed for calibration and maintenance of the flight system. DRD INTERRELATIONSHIP: APPLICABLE DOCUMENTS: GS-001, GS-003, GS-004, GS-005, TD-002 Exhibit IV PREPARATION INFORMATION: This document will describe the detailed Flight System design attributes and the calibration and maintenance requirements with the day-to-day needs of the Mission Operations team in mind. As a minimum, the handbook shall contain the following information: a. Flight System Design Overview: This section comprises the bulk of the handbook. Descriptive material containing attributes of the Flight System at a sufficient level to design and implement unplanned flight sequences during all phases of the mission, from pre-launch countdown through orbital operations. b. Flight System Calibration and Maintenance Requirements. 1. Calibration and alignment activities required in flight in order to enable the Flight System to meet its performance requirements. Frequency and mode of these activities should be described, but detailed procedures are to be documented per GS-005. 2. Maintenance activities required in flight to ensure proper operation and lifetime of hardware. Frequency and mode of these activities should be described, but detailed procedures are to be documented per GS-005. c. Flight System Operational Modes Definitions 1. Flight System states - These states and the allowable transitions among them are defined from the system-level down to the subsystem level that are planned to be used during mission operations and allowable transitions among them. Examples are power loads, flight software configuration, hardware configuration, attitude control mode, and telemetry mode. The system power configuration during each spacecraft state shall explicitly detail what loads are active. 2. Flight System operational modes - An operational mode is a defined set of the above states and modes that together represent a Flight System configuration to be used in mission operations. Operational mode definitions may also include resource (e.g., power, data rate) envelopes and a limited set of transitions allowed within the operational mode that do not violate these resource envelopes. 32 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight Rules USE: Define in-flight operational limitations imposed by Flight System hardware and software. DRD INTERRELATIONSHIP: GS-002, GS-003, GS-005 PREPARATION INFORMATION: GS-003 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit IV The Flight Rules document consists of a detailed, categorized list of all the in-flight operational limitations imposed by spacecraft and payload hardware and software. 1. A Flight Rule is defined as any operational limitation imposed by the Flight System design, hardware, or software, the violation of which would possibly result in Flight System damage, loss of consumables, loss of mission objectives, including loss or degradation of relay data, or operational hardship. 2. Flight Rules are categorized by impact if violated: a. Category A: Substantial or total loss of mission return b. Category B: Substantial degradation or threat of degradation of mission c. Category C: Significant impact on operations workload d. Category D: Temporary loss of instrument or engineering subsystem performance having no Criticality-A, -B, or -C effects 3. Each Flight Rule shall include the following information: a. Statement of the rule b. Mission phase applicability c. Level of management authority required to approve the execution of a Flight System activity that would violate the rule d. Impact if rule is violated e. List of commands associated with the rule f. Allocation of the rule checking to operations team and procedure or allocation to Ground System software program 33 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Idiosyncrasies USE: To define the unpredicted features or behaviors of the Flight System DRD INTERRELATIONSHIP: GS-002, GS-003 PREPARATION INFORMATION: GS-004 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit IV This document will describe the idiosyncrasies, i.e. the unpredicted features or behaviors, of the Flight System identified during development and testing. Note: If a feature or behavior contains constraints that need to be checked during operations, then that item needs to be included in GS-003, Flight System Rules. 34 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: Flight System Team Analysis and Operations Plan USE: This document is the plan for the analysis and operations support, including post-launch Flight System checkout and associated activities. DRD INTERRELATIONSHIP: GS-002, GS-007 PREPARATION INFORMATION: NUMBER: GS-005 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit IV This document is the Subcontractor operating and analysis plan. The following shall be addressed: (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) Organization, structure, and staffing profile Operating policies, guidelines, and constraints Milestone schedule Operational process and interfaces with other elements of Ground System and the required external interfaces of the Spacecraft algorithms Nominal and Contingency Operational procedures Operational interface agreements Operational team requirements (e.g., response time for analyzing spacecraft health, supporting spacecraft sequence generation, etc.) Training and certification procedures System and subsystem Spacecraft performance analysis processes. Identify specific analysis to be performed, telemetry measurements used, algorithms used, etc. Description of activities to support post-launch Flight System checkout. 35 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Analysis Software Implementation Plan and Interface Specifications USE: To define the mission operations spacecraft analysis software implementation plan, schedule, process and resources and the software interface specifications. DRD INTERRELATIONSHIP: SW-001 through SW-005, GS-007 PREPARATION INFORMATION: 1. GS-006 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan D-28353, Exhibit IV Flight System Analysis Software Implementation Plan This document will describe the mission operations detailed spacecraft analysis software implementation plan following the requirements of SW-001 through SW-005. The plan shall call out: a. b. c. d. e. Schedule and resources Documentation plan including as built design documentation Review plan Users guide Delivery process 2. Flight System/GS Software Interface Specifications Software interface specifications shall be prepared for interfaces between Flight System analysis software and other software in the GS. 36 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: Flight System Operations Team Requirements USE: To define the functional and performance requirements on the Flight System operations team. These serve as inputs to various Ground System (GS) documents. DRD INTERRELATIONSHIP: GS-005,. GS-006 PREPARATION INFORMATION: NUMBER: GS-007 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit IV This document defines the requirements on the Subcontractor Flight System operations team and on its interfaces with other GS teams. The following shall be addressed: 1. Functional requirements on the team activities (e.g., determine Flight System health, assess Flight System performance). Overall performance requirements on the team activities (e.g., response time for analyzing Flight System health). Functional and performance requirements on the Flight System operations team hardware/software required to support the team’s functional and performance requirements. 2. 3. 37 Subcontract No. __________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Launch Vehicle Documentation USE: To provide documentation associated with launch system. DRD INTERRELATIONSHIP: LV-001 PROJECT: MTO APPLICABLE DOCUMENTS: Definition of MTO Project Launch Vehicle Integration Deliverables PREPARATION INFORMATION: 1. 2. Launch Site Procedures: All hazardous and Non-hazardous procedures are to be submitted for approval prior to first use. Inputs to Integrated Launch Vehicle Test Procedures: Provide handling constraints, environmental constraints, personnel requirements, equipment requirements and other necessary data for incorporation into the Launch Vehicle Subcontractor (LVC) launch site procedures involving spacecraft resources. Inputs to Launch Vehicle Interface Requirements Document (IRD): This document contains all spacecraft requirements / mission requirements that are levied on the launch system. These inputs are to include facilities, interfaces, and support requirements. The format for these inputs will be provided by JPL. Flight System Mathematical Model for Dynamic Analysis: A finite element structural model for use in dynamic coupled loads analysis to be performed by the LVC. Specific format requirements for the model will be provided by JPL/NASA-KSC. Flight System Thermal Model: Geometric and thermal math models to be used in Integrated Thermal Analysis that is performed by the LVC. Specific formats will be provided by JPL/NASA-KSC. Flight System Dynamics Test Plan: The test plan defines the general philosophy and an overview of the system-level environmental testing to be performed to demonstrate the adequacy of the Flight System for flight (e.g., static loads, vibration, acoustics, shock). Flight System Dynamics Test Results Summary: The test summary, documents the results of the system-level dynamics test program. This deliverable is to document to NASA/KSC the structural adequacy of the MTO Flight System to endure the launch dynamic environment. Electrical Wiring Requirements for Flight Umbilical and Launch Complex Electrical Ground Support Equipment EGSE: This item is the final definition of the MTO SC-to-LV and SC blockhouse support equipment electrical interface requirements. The information in this deliverable will be used by the LVC to design the wiring at the launch complex and on the launch vehicle. Flight System Configuration Drawings: Drawings showing the details of the Flight System configuration are to be provided periodically with the final input to be used by the LVC to generate the Launch Vehicle Compatibility Drawing. The drawings shall show nominal and worst-case (maximum tolerance) dimensions, clearance analysis, fairing compatibility, and other interface details. Specific drawing format requirements will be provided by JPL. 3. 4. 5. 6. 7. 8. 9. 10. Flight System Launch Site Test Plan: Provides all agencies with a detailed understanding of the launch site activities and operations planned for a particular mission. The plan is intended to describe all aspects of the program while at the launch site. The format of this item is defined in the Definition of MTO Project Launch Vehicle Integration Deliverables. 38 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Launch Vehicle Documentation (Cont.) USE: DRD INTERRELATIONSHIP: PREPARATION INFORMATION (Continued) 11. LV-001 PROJECT: MTO APPLICABLE DOCUMENTS: Flight System Mass Properties Report The data from the Flight System mass properties report is used in orbit error, control, performance, and separation analyses. It represents the best current estimate of final spacecraft mass properties. The data should include any changes in mass properties while the Flight System is attached to the launch vehicle. Values should include nominal and 3-sigma uncertainties for mass, centers of gravity, moments of inertia, products of inertia, and principal axis misalignment and launch vehicle upper stage mass properties provided in the MTO Launch Vehicle Interface Requirements Document. Inputs for Launch/Hold Criteria: Provide inputs for the development of the MTO launch criteria and launch hold criteria. Flight System Ventable/Non-ventable Volumes Provide analysis and results that defines the total volume of air vented (ventable) during launch ascent and the volume of components (non-ventable) that are enclosed inside the MTO Flight System. Inputs to Launch Vehicle Interface Control Document (ICD) Provide inputs as needed to this Launch System/MTO mission interface document. This document defines the mission- and ground-operations interface between the MTO Project and the launch system: 12 13. 14 o o o o o Mechanical interface between LV & Spacecraft Electrical interface between the launch vehicle and spacecraft Defined ground and flight environments (RF, Temp, Shock/Vibration, Cleanliness, etc.) Spacecraft operational constraints/handling Launch Pad operations/services 39 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Inputs to Missile System Prelaunch Safety Package (MSPSP) USE: To define and describe the Flight System/Subsystems in detail and provide hazards analysis for each. DRD INTERRELATIONSHIP: MA-001 LV-002 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan JPL D-26471; AFSC Man 91-701 PREPARATION INFORMATION: The Subcontractor shall comply with the requirements of AFSC Man 91-701 Eastern and Western Range Safety Requirements. The MSPSP shall include the following information: 1. 2. 3. 4. 5. 6. 7. Format: Subcontractor’s format is acceptable provided the information described below is provided. Table of Contents and Glossary. Introduction: The Introduction shall address the scope and purpose of the MSPSP. General Descriptions: Provide an overview of the launch vehicle or payload as a prologue to the subsystem descriptions. The following information shall be included in this section: a. Physical dimensions and weight b. Nomenclature of major subsystems c. Types of motors and propellants to be used d. Sketches and/or photographs of the launch vehicle or payload e. Synopsis of each hazardous and safety critical system Flight Hardware Subsystem descriptions: At a minimum, the Flight Hardware Subsystems Section shall include the following information: a. Subsystem overview b. Nomenclature of major subsystems c. Function of the subsystem d. Types of motors and propellants to be used e. Location of the subsystem f. Operation of the subsystem g. Subsystem design parameters and test requirements h. Subsystem operating parameters i. Summaries of any Range Safety required hazard analyses conducted Ground Support Equipment including the following information: a. Subsystem overview b. Nomenclature of major subsystems including function of the subsystem and location c. Subsystem design parameters and test requirements d. Subsystem operating parameters e. Summaries of Range Safety required hazard analyses conducted Compliance Checklist: A compliance checklist of all applicable design, test, analysis, and data submittal requirements as specified in AFSC Man 91-701. The checklist shall indicate for each requirement if the proposed design is compliant, non-compliant but meets intent, non-compliant (waiver required) or nonapplicable. The following items shall be included in this section: a. Criteria/requirement b. System c. Compliance, non compliance, not applicable d. Resolution e. Reference f. Copies of all Range Safety approved non-compliances including deviations, waivers and ―formal‖ meetsintent certifications. 40 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Safety and Mission Assurance Plan USE: To define the requirements of a Mission Assurance Plan. DRD INTERRELATIONSHIP: All MA and ER DRDs MA-001 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan -JPL D-26471 MTO Envir. Rqm’ts Doc, JPL D-26405 Electrostatic Discharge Plan, JPL D-1348 Workmanship Standards/Handbook, JPL D8208 PREPARATION INFORMATION The MTO Safety and Mission Assurance Plan, D-26471, serves as the master Mission Assurance planning and control document. As a minimum, the Subcontractor’s plan shall address the following topics: (1) System Safety (2) Safety and Health (3) Reliability Assurance (4) Problem/Failure Tracking and Reporting (5) Environmental Assurance (per JPL D-26405) (6) Hardware Quality Assurance (7) Software Quality Assurance (8) Electrostatic Discharge (per JPL D-1348 or JPL-approved equivalent) (9) Workmanship Standards/Handbook (per JPL D-8208 or JPL-approved equivalent) (10) Electronics Parts Program (11) Materials and Processes (12) Mission Operations Assurance At the Subcontractor’s discretion they may generate either a single Mission Assurance Plan that addresses all of the DRD requirements or individual plans that address the DRD topics separately. 41 Subcontract No. __________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Contamination Control Plan and Analyses USE: Describes the requirements, documentation, analyses, evaluation and testing of the contamination control methods used for flight hardware. Documents analyses to assess the induced contamination environment and its affect on system and subsystem performance DRD INTERRELATIONSHIP: MA-001 PREPARATION OF INFORMATION: A. Contamination Control Plan MA-002 PROJECT: MTO APPLICABLE DOCUMENTS: Safety and Mission Assurance Plan JPL D-26471 1. The Contamination Control Plan shall satisfy the requirements of JPL D-26471 and describe the Subcontractor’s contamination control methods including references to Subcontractor’s applicable institutional policies, procedures, specifications, and instructions. The plans shall also include the following: a. Document Change Log, Table of Contents, purpose, scope, and applicability of plan, list of applicable documents. b. A description of requirements, sources of requirements, and methodologies selected for implementing them. c. A description of the Subcontractor Contamination Engineer’s authority and responsibility with respect to meeting the Contamination Control Requirements delineated in JPL D-26471. d. A description of fabrication, testing, storage, and shipment environments to be encountered by the deliverable hardware. e. A description of techniques and activities necessary for accomplishing Contamination Control Requirements. f. A schedule describing reviews, fabrication, maintenance, testing, certification, acceptance, and shipment of hardware. g. A description of the time allocation for contamination control activities. h. A description of how the Subcontractor will impose all requirements by appropriate documents on all Subcontractors and suppliers including the assignment of responsibilities. 2. The contamination control plan shall also describe how the Subcontractor intends to address contamination control at system integration including: a. Identify contamination-sensitive space system surfaces. b. Describe Valid End Of Life cleanliness values for contamination-sensitive surfaces: Detail how these were derived. c. Detail how the cleanliness of the flight system will be preserved during ground processing: System level integration through LV integration—beginning with payload fairing encapsulation, ending with flight system separation from the Launch Vehicle — and mission operations. d. Detail compliance with outgassing requirements. e. Describe implementation and verification with facilities requirements. f. Describe cleaning requirements. 42 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Contamination Control Plan and Analyses (Cont.) USE: MA-002 PROJECT: MTO DRD INTERRELATIONSHIP: APPLICABLE DOCUMENTS: PREPARATION OF INFORMATION: (Cont.) B. Contamination Source and Effects Analyses The Subcontractor shall document the analyses that demonstrates the following: a. Flight System contamination sources (outgassing, thruster plumes direct impingement, backflow and particulate) do not adversely impact payload instrument or contamination-sensitive spacecraft subsystems performance. Placement of payload instruments does not result in cross contamination of other payloads or contamination-sensitive spacecraft subsystems. Launch system environments—ground processing and flight—do not adversely affect the performance of the MTO Flight System, i.e., the Flight System shall be designed to survive the predicted LV-induced contamination environment (defined as beginning at LV/payload integration through separation of the Flight System from the LV). Confirm that the Flight System can perform the MTO mission in the predicted contamination environment, i.e., ground processing, launch, flight operations. b. c. d. 43 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Materials and Processes Data USE: Lists and provides data, plans, and reports pertaining to the materials and processes that are to be used in the design and fabrication of flight hardware. DRD INTERRELATIONSHIP: MA-001 PREPARATION INFORMATION: Prepare and submit data in accordance with the following: 1. MA-003 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan, JPL D-26471 Materials Identification and Usage Lists (MIULs) for all mechanical parts, including fixtures, electronic parts, materials and processes and related compatibility data that are to be used in the design and fabrication of flight hardware. Information that shall be provided in the MIULs is described in JPL D-26471. The Subcontractor shall prepare the MIUL using the JPL form in JPL D-26471 or the JPL-approved Subcontractor’s equivalent document. Qualification Plans for nonstandard Materials and Processes (M&P) design items. The plans shall describe the qualification procedures and explain how these procedures will be used to satisfy the requirements of JPL D26471. Failure Analysis Reports must document the analysis approach, the determined failure mode and mechanism responsible for the failure and the corrective actions required to prevent recurrence of the failure. Digital Images and other supporting data and information are also required. Material Usage Agreements: The Subcontractor shall prepare Material Usage Agreement (MUA) forms for application of all materials and processes that do not meet the requirements specified in JPL D-26471, using the applicable form in JPL D-26471. Subcontractor Applicable Documents as referenced in plans, procedures, procurement specifications, and screening specifications. Subcontractor Limited Shelf-Life Materials Control Plan must describe how the Subcontractor plans to control materials (such as polymeric ―O‖ rings, tapes, thermal control coatings, and other polymerics) that have a limited shelf life. The plan shall include the methodology used to extend the expiration dates. Fastener Selection List: a listing of all fasteners used including those used in hardware procured from Subcontractors and venders, but excluding government-furnished equipment (GFE): a. Preliminary Design Lists: Preliminary design lists include (1) Manufacture part number (2) Generic part number (3) Proposed manufacture (4) Procurement specification (5) Screening/demonstration/upgrade specification (6) Quantities used (7) Government-Industry Data Exchange Program (GIDEP) Alert status b. As-Designed Lists: same information as preliminary design lists c. Updates: Part changes are annotated as changes are approved. d. As-Built Lists: same as the as-designed list with the following additional information: (1) Actual part number and revision letter of each item (2) Reference designation where each part is used (3) Serial number of part (if serialized) (4) Screening/demonstration/upgrade lot number, as applicable (5) Manufacture lot date code (6) Traceability number as applicable (7) Serial number and part number of the next assembly into which the part is installed 2. 3. 4. 5. 6. 7. 44 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Electronic Parts Data USE: To provide data on electronic parts for the proposed design. MA-004 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety & Mission Assurance Plan JPL D26471 DRD INTERRELATIONSHIP: MA-001 PREPARATION INFORMATION: Submit technical data as defined by JPL D-26471 and the JPL-approved Subcontractor’s Parts Program Plan, developed in accordance with DRD MA-001, which covers part selection, evaluation and test, application status, and problems/concerns during selection, procurement, design/development, fabrication and testing. These data shall consist of the following: 1. Parts lists: Lists of all EEE parts used, including those used in hardware procured from Subcontractors and vendors excluding GFE, shall be submitted electronically in Microsoft Excel platform. The parts list shall contain the following information: a. Preliminary Design Lists (Includes manufacturer part number, generic part number, proposed manufacturer, procurement specification, screening/demonstration/upgrade specification, applicable Non-standard Part Approval Requests [NSPARs]/waivers with revision letter and status, quantities used and GIDEP Alert status). b. As-Designed Lists: (Submit the complete parts list with updates annotated.) c. As Designed Parts List Review Results: For each part on the As-Designed Parts Lists, submit the Subcontractor parts list review information which addresses the acceptability of the part for both reliability and radiation requirements. d. Updates: (Part changes annotated as changes are approved) e. As-Built Lists (Same as as-designed list with the following additional information): 1) 2) 3) 4) 5) 6) 7) 8) 2. Actual part number and revision letter of each item. Reference designation where each part is used. Serial number of part (if serialized). Screening/demonstration/upgrade lot number, as applicable. Manufacture lot date code. Traceability number as applicable. Serial number and part number of the next assembly into which the part is installed. As-built data for hybrids. Non-Standard Part Approval Requests (NSPARs) and all associated procurement and screening and/or demonstration (test) documentation. The provided JPL form or Project-approved equivalent shall be used. Failure Analysis Reports: The reports must document the analysis approach, the determined failure mode and mechanism responsible for the failure and the corrective actions required to prevent recurrence of the failure. Digital images and other supporting data and information are also required. Parts Specifications: Provide copies of Supplier- and Subcontractor-developed parts specifications to include part parameter specifications and applicable test, screening and qualification specifications. Destructive Parts Analysis (DPA) and Residual Gas Analysis (RGA) Reports: to include all supporting data including the disposition of acceptability of the lot. GIDEP Alert Review and Status Report: summary report of the impact of any GIDEP and NASA Alert Advisories and disposition status. Test Plans: all electronic parts test plans describing the proposed test setup, test procedures, and test conditions. The report shall also include all supporting diagrams and drawings. Test Reports: All electronic parts test reports describing the test set up, test conditions, test procedures and data. The report shall also include all supporting diagrams and drawings and an overall assessment and analysis of the results. Nonconformance Material Review (NCMR) Action Report describing the NCMR actions and status with supporting documentation. 3. 4. 5. 6. 7. 8. 9. 45 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE NUMBER Reliability Data USE: To provide data for review and evaluation of design status and progress. DRD INTERRELATIONSHIP: MA-001 PREPARATION INFORMATION: MA-005 PROJECT: MTO APPLICABLE DOCUMENTS: Safety & Mission Assurance Plan JPL D-26471, JPL D-5703, JPL D-8545 Reliability analyses of the hardware design shall be performed to ensure proper designed-in reliability and consistency with mission requirements and objectives. All of the analyses shall be conducted and documented as required in the Safety and Mission Assurance Plan. 1. Fault Tree Analysis (FTA): A FTA shall be performed at the flight system level. An FTA shall also be performed on all mechanisms and address failure modes capable of occurring down to the lowest-level assembly. 2. Electronic Parts Stress Analysis (EPSA): An EPSA shall be performed and documented to verify the applied stress on each piece part does not exceed the derating values established in JPL D-8545, or JPL approved equivalent. 3. Thermal Stress Analysis: The Thermal Stress Analysis shall be performed and documented for all assemblies to address the effect of the thermal environment, including worst-case estimates, for all anticipated environmental conditions. 4. Structural Stress Analysis: The Structural Stress Analysis shall be performed and documented to address the effect of the dynamic environment including effects on electrical, mechanical and electro/mechanical assemblies. 5. Worst-Case Circuit Analysis (WCA): A WCA shall be performed and documented for all circuit designs to demonstrate that sufficient operating margins exist for all operating conditions and performance requirements. 6. Worst Case Parameter Database (WCDB): A WCDB shall use a systematic approach to determine the parameter variability of all parts used in any given electrical design. The variables are those resulting from initial tolerances, aging, operating temperature and radiation. 7. Mechanical Worst-Case Analysis (Mechanical WCA): A Mechanical WCA shall be performed to ensure that worst-case mechanical tolerances and thermal environments cannot adversely affect the performance of mechanical and/or optical assemblies. 8. Single Event Effects Analysis (SEEA): A SEEA shall be performed and documented for all circuit designs containing parts susceptible to radiation-induced Single Event Effects. 9. Failure Modes Effects and Criticality Analysis (FMECA): A FMECA shall be performed on the flight hardware design interfaces to analyze postulated failures and identify the potential resultant effects. Subsystem interface circuits shall be analyzed to determine whether there are sneak paths between powered and unpowered circuits. If there are such sneak paths, the Subcontractor must ensure the paths will not affect the function of the circuits involved nor cause overstress to any parts. 10. Failure Modes Effects Analysis (FMEA): A FMEA shall be performed on all test equipment to flight hardware interfaces to assure no failure modes in the test equipment can propagate and damage flight hardware. 46 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Problem/Failure Reports USE: To provide JPL with timely notice of anomalies, problems or failures with the Subcontractor’s software or hardware. Also, to provide JPL with the data necessary to assess the adequacy of the analysis and corrective action, so as to prevent recurrence of anomalies, problem/failures and to assess the residual risk following corrective action. MA-006 PROJECT: MTO DRD INTERRELATIONSHIP: MA-001 APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan JPL D-26471 Anomaly Resolution—JPL D-8091 Problem Reporting System (PRS) User’s Manual PREPARATION INFORMATION: Each report shall be submitted in accordance with the JPL-approved Plan, and shall be responsive to the requirements of JPL D-26471. JPL shall be notified via email within 48 hours of occurrence. P/FRs shall be entered into the JPL Problem Reporting System (PRS), per the PRS User’s Manual. Each report shall include, but not be limited to, the following: A. B. C. D. E. F. G. H. I. J. K. L. M. N. O. Complete identification of the hardware and software; Date the problem/failure/anomaly occurred; Estimated accrued operating hours and/or cycles at the time the problem/failure/anomaly occurred; Location of the hardware when the problem/failure/anomaly occurred; Hardware environmental conditions when the problem/failure/anomaly occurred; Test/operation being performed and reference to associated test data; A description of the problem/failure/anomaly incident and the potential impact on the subsystem functional performance; A description of the problem/failure/anomaly analysis, including impact on hardware; Cause of the problem/failure/anomaly; A description of the corrective action taken; A description of the method used to verify that the corrective action was effective; Failure effects and cause ratings; Safety rating; Supporting material shall be provided to allow JPL to perform the mission risk assessment; and Appropriate closeout signatures per the Safety and Mission Assurance Plan, D-26471. JPL intends to approve P/FR closures as an acting member of the Failure Review Board. 47 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Material Review Board (MRB) Items USE: To define what interaction is expected involving MRB items. DRD INTERRELATIONSHIP: MA-001 MA-007 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan, JPL D-26471 MTO Project Information, Information Technology, and Configuration Management Plan, JPL D-29288 PREPARATION INFORMATION: This is to document the MRB requirements and minimum communicated items to JPL. A. Nonconformances that affect fit, form, function, safety, reliability, or interchangeability shall be submitted per waiver in accordance with the project configuration management plan. Nonconformances that do not affect fit, form, function, safety, reliability, or interchangeability do not require JPL approval; however, for each nonconformance, the Subcontractor shall submit the following information to JPL: a. Part number b. Serial number c. Nomenclature of part or assembly d. MRB initiated date e. Reason for MRB action (discrepancies should include ―is‖ and ―should be‖ condition) f. Final disposition(s) g. MRB record number MRBs not requiring JPL approval are those with dispositions of ―Repair‖ per a JPL approved Standard Repair Procedure (SRP), Return to Vendor and low cost scrap. JPL QA will be an acting member of the MRB. JPL will initially respond within three (3) working days. JPL will provide a technical reason for not concurring with a final disposition. B. C. D. 48 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Quality Assurance Data and Documentation USE: To provide the data and documentation that defines the details of the Subcontractor’s Quality Assurance activities. DRD INTERRELATIONSHIP: MA 001 PREPARATION INFORMATION: MA-008 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan JPL D-26471 Provide Quality Assurance Data and provide or make available Quality Assurance Supporting Documentation for JPL’s review and approval in accordance with the JPL-approved Subcontractor’s Mission Assurance Plan, MA-001 as follows: A. Quality Assurance Data 1. Product Inspection, Assembly and Test Flow Chart showing the fabrication and test flow of the Flight System hardware including the JPL mandatory inspection points. B. Quality Assurance Supporting Documentation Submit documents or make available for JPL’s review at Subcontractor’s facility. 1. Flight Workmanship Standards 2. Critical Process Instructions 3. ESD Procedures 4. Storage, handling and shipping procedures 5. Standard rework/repair procedures C. Procurement Quality Assurance Documentation 1. A list of approved suppliers for MTO. The list shall include: a) Company Name; b) Cage Code; c) Address; d) Hardware and/or Software Product(s) to be delivered to MTO. 2. A list of major and/or critical suppliers that will require source inspection. 3. Supplier audit plan. 49 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Safety Data USE: MA-009 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Safety and Mission Assurance Plan JPL D-26471; MTO Project Policies, JPL D-29220 NPR 8621.1; JPL Form 0554-S JPL Standard for Systems Safety, D-560 To describe the Subcontractor’s System Safety Data requirements DRD INTERRELATIONSHIP: MA-001, MA-010 PREPARATION INFORMATION: The required safety data includes the following: 1. Safety Surveys Provide copies of documented Safety Surveys including: a. Facility and Operations Safety Surveys —This survey addresses the safety features within the facility that protect personnel and hardware from harm. The survey shall also address the safety features of specific test facilities and/or test activities, including test equipment. Transportation Safety Surveys (TSSs)— This survey addresses safety features for all significant movements of flight hardware. (See Project Policies, D-29220, Item #10.) b. 2. Crane and Handling Equipment Inspection and Proof Test Verification These certificates document the proof loading and inspection results on all cranes and handling equipment used on flight-critical hardware at all locations. Certification can be by test or analysis, or a combination of both, or can be waived on submittal of appropriate information. Mishap Reports In accordance with NPR 8621.1, NASA Procedure Requirement for Mishap Reporting, Investigations and Record Keeping, all Subcontractor employees are responsible for reporting mishaps immediately. In event that a mishap is serious, the Subcontractor shall immediately notify JPL project management. All mishaps shall be documented on a Mishap report (JPL Form 0554-S or JPL-approved equivalent. If personnel are injured, see reporting requirements for MA-010.) 3. 50 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Safety and Health Plan and Incident Reports USE: To define and describe the Subcontractor’s Personnel Safety Policy and Reporting requirements DRD INTERRELATIONSHIP: MA-009 PREPARATION INFORMATION: MA-010 PROJECT: MTO APPLICABLE DOCUMENTS: Additional General Provision, Safety and Health The Subcontractor shall comply with the requirements of the Safety and Health Additional General Provision (AGP) of this Subcontract. 1. Safety and Health Plan: Prepare and submit for JPL approval, a Safety and Health Plan in accordance with paragraph (d) of the AGP. The Safety and Health Plan shall describe the means to be employed by the Subcontractor to monitor and enforce the safety and health requirements in the AGP. The plan shall also include the Subcontractor’s standards and criteria for imposing safety and health standards upon its Subcontractors of any tier and its plans and procedures for monitoring compliance with such standards. The Subcontractor’s currently published Safety and Health Plan or a previously published plan for similar work performed by the Subcontractor on a federal contract may be submitted for JPL review and approval under this Subcontract. 2. Illness, Incident, and Injury Experience Reports: The Subcontractor shall immediately notify and promptly report to JPL any accident, incident or exposure resulting in fatality, lost-time occupational injury or occupational disease, contamination of property or property loss of $25,000 or more arising out of work performed under this Subcontract in accordance with paragraph (e) of the AGP. The Subcontractor shall submit such additional reports of illness, incident and injury experience reports as required by paragraph (f) of the AGP. If the incident or injury is applicable also as a mishap, see reporting requirements for MA-009. 51 Subcontract No. __________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Earned Value Management Plan USE: Provides an overview of the management processes for work organization and for cost/schedule planning and control; provides the documentation required to demonstrate compliance with NASA’s Earned Value Management (EVM) requirements. DRD INTERRELATIONSHIP: All MS DRDs PREPARATION INFORMATION: (1) MS-001 PROJECT: MTO APPLICABLE DOCUMENTS: NPD 9501.3A, NASA EVM Requirements The responsibilities and methods needed to meet NASA EVM requirements (NPD 9501.3A), plus any additional procedures the Subcontractor deems necessary to adequately manage its Resources, shall be documented in either an Earned Value Management (EVM) Plan or a validated EVM System Description. The Subcontractor shall describe the management system to be used to: a. Organize, clearly describe, and authorize the work to be performed to meet the Contractual requirements; b. Schedule, authorize, and budget the work; c. Establish metrics and performance measurement baseline; and d. Monitor and control cost performance and schedule progress during the Subcontract. Specifically, the Subcontractor’s EVM Plan shall include, but not be limited to: a. A narrative description of the following processes: i) Work Definition, Organization, and Integration with project organization structure ii) Scheduling iii) Baseline Budgeting and Baseline Change Control iv) Work Authorization v) Actual Cost Collection vi) Indirect Cost Management vii) Monthly Earned Value measurement and assessment viii) Reporting of monthly EVM data to internal management and JPL ix) Second-Tier Subcontract management and material cost control and accountability As appropriate provide graphic examples, i.e., flow charts, diagrams, report formats, etc., of the processes described above. b. Specific discussion of Item (3)(a)(i) above to include: i) The process used to assign organizational responsibility/integrate the Organization structure with the Work Breakdown Structure c. Specific discussion of Item (3)(a)(iii) above to include: i) The lowest applicable level (i.e., Control Account/work package) at which cost and schedule integration occurs in the Subcontractor’s EVM system; ii) The process used to integrate the Project Schedule (milestones and activities) with the Baseline Budget; iii) The process and controls used to establish the Performance Measurement Baseline (PMB); (2) (3) 52 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Earned Value Management Plan (Cont.) USE: MS-001 PROJECT: MTO DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) The process and controls used to revise the PMB with internally authorized changes The establishment and use of a Budget Transaction Log and MR Log Management (MR) The processes and controls used to establish and distribute Undistributed Budget and/or Management Reserve; vii) The processes and controls used to implement authorized Subcontract changes into the PMB. d. Specific discussion of Item (3)(a)(vii) above to include: i) The methods for computing earned value at the Work Package level, and the criteria for their usage; ii) The policy which requires establishment of discrete means of earned value measurement for all appropriate tasks, and which limits the level-of-effort method of earned value measurement to only those tasks which cannot be measured discretely; iii) The methods and report formats for control account variance analysis as determined by the thresholds established to identify ―significant‖ variances at the control account level. iv) The methods used to identify and implement corrective actions in response to variances generated during the reporting period; v) The methods used to project the Subcontract cost Estimate-At-Completion (EAC) for both direct and indirect costs. e. Specific discussion of Item (3)(a)(viii) above to include: i) The method used to summarize or rollup EV control account data by the WBS and the Organization structure. f. Specific discussion of Item (3)(a)(ix) above to include: i) The method used for scheduling second-tier subcontract and material procurements; ii) The method used for second-tier subcontract and material cost budgeting; iii) The method used for second-tier subcontract and material earned value measurement; iv) The method used to recognize second-tier subcontract and material actual costs; v) The procedure for analyzing material price and usage variances; and vi) The procedure for analyzing second-tier subcontract cost and schedule variances. g. Identification of personnel (either by name or by functional title) who are responsible for planning the work and reporting work progress. Also identify individuals responsible for reviewing reported accomplishments, monitoring the EVM activities, and verifying earned value calculations. iv) v) vi) APPLICABLE DOCUMENTS: (4) After initial JPL approval, the Earned Value Management Plan shall be modified only with the prior consent of JPL. 53 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Work Breakdown Structure and Dictionary USE: The Work Breakdown Structure (WBS) and WBS Dictionary establish the basic framework within which all effort necessary to meet the requirements of the Subcontract is identified and defined. It provides the logical product-oriented structure for cost planning, performance assessment, and cost control. DRD INTERRELATIONSHIP: All MS DRDs PREPARATION INFORMATION: 1. MS-002 PROJECT: MTO APPLICABLE DOCUMENTS: NPD 9501.3A, NASA EVM Requirements The purpose of the WBS is to provide a logical, product-oriented framework that organizes the Project work, schedules, and budgets. It shall be presented in both tabular and graphic form and shall be an expansion of the summary WBS provided by JPL. a. WBS Index (Tabular form): An index will be submitted to include: i. Line item number ii. WBS element/task listed by title and indentured to reflect level iii. Responsible organization (see 3 below) iv. Statement of Work (SOW) paragraph associated with the WBS element v. The number of the specification that covers the WBS element (if applicable) vi. Subcontract end item (deliverable) number (if applicable) b. Graphical form: Subcontractor format is acceptable A WBS Dictionary statement shall be prepared to define each element of the WBS. These definitions shall describe the scope of work to be performed and the major receivables(s) and deliverable(s) involved (as applicable). The dictionary will include: i. WBS element title, number and task description (technical and cost content) ii. SOW paragraph number and narrative iii. Specification associated with the element (if applicable) iv. Date, revision number and approved changes v. Subcontract end item/data item number (if applicable) 2. 3. The Subcontractor shall establish a Project organization structure wherein individual organizations are assigned responsibility for implementing the control accounts within the WBS. 4. The lowest level of the WBS shall be agreed upon during Subcontract negotiations. It will be consistent with NASA criteria (NPD 9501.3A) for organizing and planning a project. Control account plans will be required for each control account within the lowest element of the WBS. The WBS shall be coded to establish the relationship among all of its levels in accordance with the numbering of the summary WBS provided by JPL. The WBS coding shall be used to identify each particular WBS Item on all Project budgets, schedules and financial reports. After initial JPL approval, the WBS and WBS Dictionary shall be modified only with the prior consent of JPL. All changes to the WBS and WBS Dictionary required by negotiated changes to the scope of the Subcontract, or by authorized but not negotiated Subcontract changes, shall be incorporated as directed by JPL’s Acquisition Division. 5. 54 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Contract Budget Baseline (CBB) Profile and Funding Profile USE: The Contract Budget Baseline (CBB) is a time-phased cost plan for the entire length of the Subcontract performance. It is the key element for financial planning and management of the Subcontract and is used as the basis for performance measurement. The funding profile provides a projection of cost obligations for incremental funding of the Subcontract. DRD INTERRELATIONSHIP: MS-002, MS-005, MS-006 PREPARATION INFORMATION: 1. MS-003 PROJECT: MTO APPLICABLE DOCUMENTS: NPD 9501.3A, NASA EVM Requirements Contract Budget Baseline (CBB) Profile a. The Subcontractor shall prepare Baseline Budgets at the control account/work package level in accordance with NASA EV criteria (NPD 9501.3A). Budgets will be summarized at successively higher levels of the WBS to the Total Subcontract performance measurement baseline (PMB). A time-phased baseline budget (for entire period of performance) shall be submitted for each WBS item reported on the Cost/Schedule Performance Report (see MS 005). b. Each baseline budget shall be broken out by element of cost (e.g., direct labor hours, Full Time Equivalents (FTEs), direct labor cost, material cost, second tier subcontract costs, other direct costs, overhead costs, and G&A cost) and summarized through total cost. It shall also be time-phased by month and subtotaled by fiscal year, and then totaled for the Budget At Completion (BAC). c. Each WBS element’s baseline budget shall be accompanied by a workforce profile (in planned hours, monthly conversion factor, and the resulting FTEs) which shall also be time-phased by month and subtotaled by fiscal year, and then totaled at completion. d. The initial Performance Measurement Baseline (PMB) for the total project shall equal the original negotiated Subcontract Total Cost (fee excluded), less any Management Reserve. The PMB profile shall be accompanied by a Management Reserve expenditure plan, which projects the potential use of Management Reserve. e. After initial JPL approval, the PMB shall be modified in accordance with NASA EV criteria. Changes to the PMB as a result of regular baseline maintenance (i.e. rolling wave planning, externally driven scope change, etc.) will be reported monthly via the Cost/Schedule Performance Report (MS-006). Modifications to the PMB that are not part of regular baseline maintenance, such as consuming all management reserve in a given year or a project re-baseline will require the prior consent of JPL. All negotiated changes to the scope of the Subcontract shall be incorporated into the PMB as directed by JPL. On occasion, JPL may require the Subcontractor to incorporate authorized but not negotiated changes to the Subcontract into the PMB. 2. Funding Profile A time-phased plan shall be provided for open commitments, for fee and for termination liability. This data shall be summarized with the CBB profile to provide a baseline funding profile. The profile shall be updated quarterly, or more frequently if needed, based on the actual costs to date plus revisions in the estimate to complete or revisions in the commitments, or the termination liability profile. The summary profile shall provide a projection of the incremental funding needed for the Subcontract. 55 Subcontract No. __________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Integrated Master Schedule (IMS) USE: To provide a time-phased project plan consistent with Subcontract requirements. To display project activities and milestones with their expected performance duration’s in their planned sequence of events. To provide Management with the capability for schedule analysis and a clear picture of overall project schedule status. DRD INTERRELATIONSHIP: MS-002, MS-003, MS-006, SW-001 PREPARATION INFORMATION: 1. MS-004 PROJECT: MTO APPLICABLE DOCUMENTS: NPD 9501.3A, NASA EVM Requirements The Subcontractor shall prepare a scheduling system that contains a master schedule and related subordinate schedules, which will provide a logical sequence from detail to the summary level. This Integrated Master Schedule must represent the plan for accomplishing all of the authorized activities necessary to meet the requirements of the Statement of Work within the time constraints imposed by the Performance and Delivery Schedule of the Subcontract. During initial development of the Schedules, the Subcontractor shall integrate all schedule levels by establishing common activities or milestones among the various levels. All schedule items shall be traceable to the WBS. The IMS should be constructed using critical path method scheduling techniques. The IMS enables preservation of a performance measurement baseline and a coexisting representation of schedule progress, and estimates of future schedule. The IMS enables the creation of intermediate and top level schedules, tied to and traceable to the data maintained at the lowest level. The IMS baseline is the foundation for time-phased resource planning. Schedule progress and future estimates are the foundation for Estimate To Complete/Estimate At Complete exercises. The software used for schedule creation and maintenance shall be compatible with, or translatable to, the current JPL schedule system. Deviations from the requirement must be negotiated and shall only be used with JPL concurrence. The schedules shall include all receivables and deliverables, the detailed activities of second-tier subcontractors, the primary and supporting reviews, and all SDRL documentation deliveries and information on each software build per SW-001. The responsible Cost Account Manager (CAM) for schedule tasks and the names of second-tier subcontractors shall be identified on the schedule or with a supplemental data sheet. The baseline schedule shall include the following schedule margins for the hardware and software deliveries: (1) One month/year from start of implementation to delivery to ATLO, (2) Two months/year from start of ATLO to ship to launch site, and (3) One week/month from delivery to the launch site to launch. After approval of the Initial Schedules by JPL, the start and completion dates on the Initial Schedules shall become the baseline start and completion dates reflected on all monthly updates to the Schedules. The Subcontractor shall not revise these baseline start and completion dates without prior consent from JPL. Monthly updates shall reflect any progress the Subcontractor has made toward accomplishing scheduled activities, and any projected (i.e., forecasted/estimated) start and completion dates of scheduled activities. 2. 3. 4. 5. 56 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Integrated Master Schedule (IMS) – (Cont.) USE: . DRD INTERRELATIONSHIP: PREPARATION INFORMATION (Continued) 6. MS-004 PROJECT: MTO APPLICABLE DOCUMENTS: The Subcontractor shall prepare the following types of schedules: (a) Detailed Network Schedule -- The detailed Schedule shall portray the following information for each of the Subcontractor’s lowest level activities: i) ii) iii) iv) v) vi) vii) viii) ix) x) xi) Activity Description WBS Number (for Reference/Cross-Reference) Schedule Start Date Schedule Completion Date Forecast/Estimated Start Date Forecast/Estimated Completion Date Actual Start Date Actual Completion Date Predecessor-Successor task relationships Receivables or Deliverables from external sources such as GFP providers Schedule Margin, if applicable The Subcontractor shall be responsible for establishing the schedule interdependencies among these lowest level activities and for identifying the critical path that runs through them. (b) Intermediate Schedules – The Subcontractor shall provide a separate Intermediate Schedule for each major subsystem or component of their deliverable product to JPL. Each Intermediate Schedule shall portray the information in Items (6) (a) i) through (6) (a) xi) of this DRD for each of the Subcontractor’s activities required to produce the subject subsystem or component. The Subcontractor shall be responsible for establishing the schedule interdependencies among these activities and for identifying the critical path that runs through them. Summary Schedule- – The Subcontractor shall provide a Summary Schedule. The schedule shall portray the information in Items (6) (a) i) through (6) (a) xi) of this DRD for each of the Subcontractor’s major activities and milestones. In addition, the Summary Schedule shall portray the sequential relationship and interdependence among each of the Subcontractor’s major activities and milestones. A distinctive marking shall identify each activity on the Summary Schedule that falls on the ―critical path.‖ (c) 57 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: NASA Financial Management Report USE: Provides monthly cost and commitment information for financial management of the Subcontract DRD INTERRELATIONSHIP: MS-003 & MS-006 PREPARATION INFORMATION: 1. MS-005 PROJECT: MTO APPLICABLE DOCUMENTS: NPG 9501.2D, Contractor Financial Management Reporting A NASA Form 533M report shall be completed in accordance with the instructions on the reverse side of the form. A 533M shall be prepared for the total project and for each Level used for earned value reporting per MS-006, as mutually agreed upon during negotiations. Reporting categories on each 533M shall be the elements of cost (e.g. labor hours, labor dollars, overhead costs, material, second tier subcontracts, other direct costs, G&A) and profit or fee. A NASA Form 533Q shall be completed in accordance with instructions on the reverse side of the form. Reporting levels and categories shall be the same as those required for the 533M. An overhead report shall provide a listing of the latest bidding, billing and actual overheads, fringe and G&A rates by cost centers. The accounting calendar shall also be included. A reconciliation report shall be prepared in accordance with instructions on the reverse side of the 533 forms and those included in Contractor Financial Management Reporting NPG 9501.2D. The potential termination liability shall be identified as a projection by month for the current and subsequent fiscal years. 2. 3. 4. 5. 58 Subcontract No. ________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Cost/Schedule Performance Report USE: To provide a monthly update of the status of Schedule, Earned Value, and Cost performance on the Subcontract effort. DRD INTERRELATIONSHIP: All MS DRDs, RE-003 PREPARATION INFORMATION: The Report shall include the following: 1. MS-006 PROJECT: MTO APPLICABLE DOCUMENTS: NPD 9501.3A, NASA EVM Requirements Schedule: a. A detailed update to the Integrated Master Schedule (IMS) comprising tasks and milestones that depict all work activities and procurements under this Subcontract. i) Identified schedule margins (slack). ii) Including tasks, which are identified as ―receivables‖ or ―deliverables‖ from external sources such as GFP providers. b. Level 1 or 2 rollup schedules. 2. Schedule metrics: a. Milestone trend charts. b. Slack tables. c. Critical-path tables. d. Schedule margin: plan vs. consumption. 3. Significant schedule changes in: a. Schedule slack. b. Critical path. 4. Schedule recovery plans. 5. Cost/schedule Performance Data: a. Contractor Performance Report (CPR) Format 1, minimum WBS level 3 (Subsystem) or below as mutually agreed upon during negotiations. b. Provide reporting to the level necessary for specific WBS elements with a high or medium risk, as defined by the Subcontractor or as mutually agreed with JPL, in order to understand the WBS element’s risk status. c. Provide a list of control accounts with Significant Variances (both cost and schedule) per negotiated thresholds. d. Provide Variance Analysis Report (VAR), in CPR Format 5, that describes impact of significant variances (including impact of other subsystems) and the corrective actions planned to rectify these variances. e. JPL-approved changes to the Subcontractor’s Performance Measurement Baseline will be discussed. f. Supplemental Data that supports the reported cost information will be retained at the Subcontractor’s facility and made available for JPL review. g. EAC: The EAC will be updated by a comprehensive review and re-estimate of the scope of work remaining at least once a year. This does not preclude regular updates of the EAC for known performance issues, scope changes, etc. 6. Workforce Status - Plan vs. Actual Full-Time Equivalents (FTEs). 59 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Cost/Schedule Performance Report (Cont.) USE: DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) 7. MS-006 PROJECT: MTO APPLICABLE DOCUMENTS: Cost management status of major second tier sub contracts and long lead-time procurements: a. Supplier name b. Negotiation status c. Proposed price vs. negotiated price d. Assigned WBS element e. Estimated/Actual definitization dates f. Plan vs. Projected/Actual delivery dates Management Reserve: a. Cost/schedule reserves remaining vs. estimated cost-to-go b. Project Lien List: List cost impacts to the PMB/EAC Status of Significant Risk List a. List known or perceived programmatic and technical risk items b. Include a ROM cost for each item, should it occur c. Include a ROM probability of its occurrence (very low, low, moderate, high or very high). d. Identify any item to which reserves were applied e. Identify the definitized, time-phased allocated cost of the item 8. 9. 60 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Knowledge Transfer Plan USE: To provide the plans for communication, data, and information exchange between JPL and the Subcontractor and for records storage. DRD INTERRELATIONSHIP: TD-004 PREPARATION INFORMATION: PM-001 PROJECT: MTO REFERENCE: MTO Information, Information Technology, and Configuration Management Plan, D-29298 The plan shall describe the Subcontractor’s implementation for communicating and exchanging data and information with the MTO Project and for storage of the MTO records. The Subcontractor plan shall address at a minimum: 1. Method for providing to a JPL electronic Library all Subcontractor generated MTO deliverable documents, data, schedules and reports in Exhibit III. Describe the processes for (1) transferring documents to JPL, (2) notifying JPL when documents are stored, (3) documentation control of the data, and (4) marking and identifying user access to Subcontractor proprietary data. Method for providing access, by the Internet to authorized MTO Project personnel, for in-process and supplementary documents and files, which are developed for the MTO Project. Examples include: (1) Documents that are in review (2) Documents that are used to support working group meetings and peer reviews or help resolve technical or management issues (3) Software code, test files, and directories (4) Informal documents that are pertinent to the work being done such as engineering designs and analyses, reliability analyses, and technical memos (5) Documents that are to be retained at the Subcontractor’s facility such as test data (6) Digital photographs per TD-004 Describe the processes for: (1) storing and making the data available (JPL or Subcontractor electronic database systems, or combination of both can be used) (2) configuration control of the data, if applicable (3) maintaining access-protection for the system and data files, including an access control list for all authorized MTO Project personnel, if a Subcontractor database is used (4) backup and recovery of Subcontractor systems and data files (5) identifying and providing JPL access to Subcontractor proprietary data 3. Method for assuring compatibility of software versions between the Subcontractor and JPL, or use of nonnative formats to ensure effective transfer of data and communication with JPL. Capabilities and use of video and high-fidelity telephone conferencing with JPL for communications and information exchange. Specific formats, e.g. Netmeeting, Meeting Place or similar software, to be negotiated with JPL. Process for interfacing with the JPL web based collaborative systems requiring the Subcontractor to report, track, and sign-off PFRs, Action Items, Risk Management Items, etc. 2. 4. 5. 61 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Risk Management Plan USE: This document describes the approach to managing risk. DRD INTERRELATIONSHIP: PREPARATION INFORMATION: PM-002 PROJECT: MTO REFERENCE: MTO Risk Management Plan, D-29208 This plan shall contain a description of the Subcontractor’s approach to manage risk on a recurrent basis throughout the Subcontract life for all work elements of the Subcontract in accordance with the MTO Risk Management Plan, D29208. The plan shall include the tasks, functions, and activities necessary to accomplish effective risk management. This plan will describe the process through which the risks will be identified, evaluated, quantified for cost and schedule impacts, prioritized and mitigated. Specifically the plan will include: 1. Purpose, scope, assumptions, constraints, and policies pertaining to risk management. 2. Overview of the process and a description of how risk management is integrated into MTO management processes. 3. Organization, roles and responsibilities for risk management. 4. Methods and tools to be used. 5. Schedule and milestones for risk management activities, including preparation of risk list, updating list and reporting status. 6. Address how risks are identified, evaluated, quantified for cost and schedule impacts, documented, reported, maintained, mitigated, and dispositioned. Identify how mitigation plans will be validated. 7. Descope strategies, related to MTO objectives. 62 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Contractual Reports USE: Provides data on the implementation of the Subcontractor’s Small Business/Small Disadvantaged Business Subcontracting Plan. Reports corrective or preventive action taken to eliminate the causes of actual or potential non-conformance to Subcontract requirements, and New Technology Reports. PM-003 PROJECT: MTO DRD INTERRELATIONSHIP: PM-005 PREPARATION INFORMATION: Provide the following reports: APPLICABLE DOCUMENTS: 1. Subcontracting Report for Individual Contract, Form SF 294, prepared in accordance with the instructions on the reverse side of the Form. 2. Summary Subcontract Report, Standard Form 295, in accordance with the instructions on the reverse side of the form 3. Internal Audit Findings, risk items or deviations that have been determined to potentially affect mission success. The report shall include, but not be limited to, the following: a. b. c. d. e. The effective disposition of concerns and reports of product non-conformance. Investigation of cause of non-conformance related to products and processes. Determination of corrective action needed to eliminate the cause of the non-conformance. Application of controls to ensure that corrective action is taken and that it is effective. Appropriate close-out signatures, including the Cog Engineer and the Subcontractor’s Project Manager. 4. New Technology Reports in accordance with the Subcontract Article entitled, ―New Technology.‖ 5. DOD Industrial Plant Equipment Requisition, JPL Form 1419 for off-the-shelf equipment with a cost greater than $1,000. 6. NASA Property in the Custody of Contractors, NASA Form 1018 a. Monthly report for controlled assets greater than $100,000 in value and for all Work in Process (WIP) and material. b. Annual report for all controlled assets, WIP and material c. Annual verification of all controlled assets per list provided by JPL. 63 Subcontract No. __________ Date: October 29, 2004, Page 1 of 4 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Phase Implementation Plans USE: Provides the description of the Subcontractor’s plan to perform in the specified Phase. DRD INTERRELATIONSHIP: CM-003, MS-002, MS-003, MS-004 and PM DRDs PM-004 PROJECT: MTO APPLICABLE DOCUMENTS: JPL Design Principles, JPL D-17868; MTO Project Policies, JPL D-29220 Article 1, paragraphs 1.9 and 2.12 of the Subcontract PREPARATION INFORMATION: Phase A/B Implementation Plan The Subcontractor Phase A/B Implementation Plan describes the Subcontractor’s approach to completing the MTO Spacecraft preliminary design and analyses, and integrating the science and engineering payload. The implementation plan shall be correlated to the WBS (MS-002) and shall identify cost and schedule plans. The Plan shall include as a minimum the following: 1. Technical and programmatic challenges that will impact Phase A/B cost and schedule (identify each challenge and its impact on cost and schedule). 2. Flight System summary description, including key or driving requirements. 3. Key open issues and risks with a plan for mitigation and resolution, including Payload accommodation. 4. Plan for performing design and analyses activities concurrently with JPL mission and payload design. 5. Plan for performing preliminary reliability analyses including schedule, staffing, and phasing with design and implementation activities. 6. Electronics parts or electro-mechanical procurement and screening plan, and phasing with implementation activities. In particular, long lead or high-risk parts should be identified and include a discussion of how schedule and technical risk will be managed. 7. Implementation approach for flight hardware (subsystems and assemblies) and flight software including: a. b. c. d. 7. 8. 9. Key requirements. Make or buy approach, including Subcontractor division and facility or Subcontractor at which assemblies will be manufactured. Surveillance provisions, including meetings and reviews, to insure that technical, mission assurance and program requirements and constraints are met, including surveillance of Subcontractors. Use of simulators, testbeds and the flight system for test and verification Phase A/B organization and staffing plan. Implementation approach to technology transition, system engineering, radiation control, if applicable, and export control, etc. Plan for compliance with the JPL Design, Verification/Validation and Operations Principles (D-17868) and the MTO Project Policies, JPL D-29220, including compliance matrices. Provide rationale for non-compliance and waiver plans, except in those areas specifically excluded by the MTO Project Policies, JPL D-29220. 64 Subcontract No. __________ Date: October 29, 2004, Page 2 of 4 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Phase Implementation Plans (Cont.) USE: PM-004 PROJECT: MTO DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) Phase C/D Implementation Plan The Subcontractor shall prepare a Phase C/D Implementation Plan that describes the Subcontractor’s approach to completing spacecraft design, fabricating and verifying the spacecraft, integrating the engineering and science payload, and completing flight system acceptance testing and subsequent launch operations and post-launch checkout. The implementation plan shall be correlated to the WBS (MS-002) and include a detailed schedule and cost proposal for Phase C/D. In addition, provide a recommended JPL budget reserve amount, time-phased by GFY, for each JPL-supplied WBS element that was bid, based upon the Subcontractor’s assessment of that element’s development risk and cost estimate uncertainty risk. The Plan can be an updated version of the Phase A/B plan expanded to include the phase C/D activities. It shall include as a minimum the following: 1. Technical and programmatic changes in Phase A/B that impact Phase C/D cost and schedule (identify each change and its impact on cost and schedule). Updated spacecraft and flight system summary description, including key or driving requirements. Key open issues and risks with a plan for mitigation and resolution, including payload accommodation. List top program issues and risk items that have been closed to date. Plan for managing the design and analyses activities that are done concurrently with JPL mission and payload design. Plan for completing reliability analyses including schedule, staffing, and phasing with design and implementation activities. Electronic parts or electro-mechanical procurement and screening plan, and phasing with implementation activities. In particular, long lead or high-risk parts should be identified and include a discussion of how schedule and technical risk will be managed. APPLICABLE DOCUMENTS: 2. 3. 4. 5. 6. 65 Subcontract No. __________ Date: October 29, 2004, Page 3 of 4 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Phase Implementation Plans (Cont.) USE: PM-004 PROJECT: MTO DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) Phase C/D Implementation Plan (Continued) 7. Updated implementation approach for flight hardware (subsystems and assemblies) and flight software including: a. Key requirements. b. Make or buy approach, including Subcontractor division and facility or second-tier Subcontractor at which assemblies will be manufactured. c. Surveillance provisions, including meetings and reviews, to insure that technical, mission assurance and program requirements and constraints are met, including the surveillance of second-tier subcontractors. d. Use of simulators, test beds, and the flight system for test and verification. e. Summary manufacturing, integration, and test and verification plans, including IV&V plans. f. Summary delivery and end item data package requirements. Plan for verifying spacecraft and flight system interfaces using test beds and/or simulators. ATLO flow plan and description, schedule, facility requirements (including Subcontractor-provided facilities for spacecraft and all payload processing), support equipment development & verification approach. REFERENCE: 8. 9. 10. Ground System development and support plan, including Ground System and DSN compatibility testing, and end-to-end test. 11. Plan for initial in-flight checkout of Flight System. 12. Phase C/D organization and staffing plan. 13. Transition plan from Phase A/B into Phase C/D. 14. Implementation approach to technology transition, system engineering, radiation control, if applicable, and export control etc. 15. Plan for compliance with the JPL Design, Verification/Validation and Operations Principles (D-17868) and the MTO Project Policies, JPL D-29220, including compliance matrices. Provide rationale for non-compliance and waiver plans, except in those areas specifically excluded by the MTO Project Policies, JPL D-29220. 66 Subcontract No. __________ Date: October 29, 2004, Page 4 of 4 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Phase Implementation Plans (Cont.) USE: Provides the description of the Subcontractor’s plan to perform in the specified Phase. DRD INTERRELATIONSHIP: MS-003, MS-004, MS-007 PREPARATION INFORMATION: (Continued) Phase E Implementation Plan PM-004 PROJECT: MTO REFERENCE: The Subcontractor shall prepare a Phase E Implementation Plan that describes the Subcontractor’s approach to providing post-launch mission operations support. The implementation plan shall be correlated to a JPL-provided WBS for Phase E, and shall include a detailed schedule and cost proposal for Phase E. The Plan shall include as a minimum the following: 1. Technical and programmatic changes that impact Phase E cost (identify each change and its impact on cost and schedule). 2. Baseline Ground System support description, including key or driving requirements. 3. Plan for maintaining testbeds at JPL and Subcontractor’s facilities. 4. Plan and approach for monitoring routine in-flight telemetry and assessing Flight system health. 5. Key open issues and plan for resolution. 6. Plan for initial in-flight checkout of flight system. 7. Phase E organization and staffing plan. 8. Risk items and mitigation measures. 9. Transition plan from Phase C/D into Phase E. 67 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Spares and Property Management Plans USE: Describe the Subcontractor’s approach to spares planning and property management. DRD INTERRELATIONSHIP: MA-001, PM-003, TD-007S PREPARATION INFORMATION: PM-005 PROJECT: MTO APPLICABLE DOCUMENTS: The Spares and Property Management Plans shall include the following: 1. Spares Plan The Spares Plan shall describe the process for planning, acquiring, maintaining, and delivering spares. Adequate flight hardware spares shall be identified in the plan and maintained to mitigate schedule risk and carry out a robust integration, verification, and validation program. Hardware levels applicable to flight spares include the following: a. Part/component b. Subassembly c. Assembly d. Subsystem 2. Property Management Plan The Property Management Plan shall describe the approach for parts inventory, stores management and residual parts/hardware disposition 68 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Long-Lead-Time Items List USE: Describe the Subcontractor’s approach for long-lead-time parts planning. DRD INTERRELATIONSHIP: PREPARATION INFORMATION: PM-006 PROJECT: MTO APPLICABLE DOCUMENTS: The Long-Lead-Time Items List identifies for planning purposes the long-lead-time items to be considered for acquisition prior to Phase C/D. The list shall include the following: 1. 2. 3. 4. Identification of the proposed long-lead-time items Rationale for the selection of long-lead-time items. The acquisition schedule for each identified long-lead-time item. The funding profile associated with each long-lead-time acquisition. 69 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Review Plan USE: Provides the Subcontractor’s implementation of the MTO Review Plan requirements. DRD INTERRELATIONSHIP: RE-002 PREPARATION INFORMATION: RE-001 PROJECT: MTO REFERENCE: MTO Review Plan D-29289 A review plan shall be prepared identifying the Subcontractor and the Subcontractor reviews in accordance with the MTO Review Plan, D-29289. The approach shall address both Subcontractor-developed and subcontracteddelivered items. The plan shall describe reviews such as, but not limited to: a. b. c. d. e. f. g. h. i. j. k. l. Peer Reviews of designs, documents, processes, software, and fault protection at the assembly, subsystem and system levels. Design reviews of complex parts such as ASICs, FPGAs, and Hybrids. Subsystem Preliminary Design Review (PDRs) and Critical Design Reviews (CDRs), Hardware and Software Inheritance Reviews (NOTE: these may be held in combination with PDRs or peer reviews). Spacecraft PDR and CDR. Informal subsystem/assembly Test Readiness Reviews (TRR) for environmental testing. Informal subsystem/assembly software and support equipment pre-delivery reviews. Assembly, Test and Launch Operations (ATLO) Readiness Review (ARR). ATLO Environmental Test Readiness Review (ETRR). Pre-ship Reviews prior to shipment of the Flight System to the Environmental Test Facility (as required), and to shipment to KSC Flight Parameters Review (FPR). Project Reviews, NASA Reviews and Launch Site Reviews which require Subcontractor support per the MTO Review Plan, D-29289. The plan shall provide review purpose, scope, convening authority, data contents, and data package delivery schedules. Also the plan shall describe the process for creating and closing out action items. 70 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Review Data Packages and Reports USE: Provide review materials and associated data packages. DRD INTERRELATIONSHIP: RE-001 PREPARATION INFORMATION: A. Agenda RE-002 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Review Plan D-29289 If applicable, provide draft agenda in accordance with RE-001 prior to the reviews, for concurrence with the JPL CTM. B. Review Package Data Submittals For each review, prepare and submit a review package of the presentation material and the support data necessary for the complete understanding and assessment of the review. C. Review Report The report for each review, for which the Subcontractor is the chair, shall include the following: 1. List of attendees 2. Updated material as needed 3. Findings or minutes as requested by JPL 4. Copy of Requests for Action (RFAs) D. Action Items Action items assigned during project-required reviews and meetings shall be closed out and the status maintained. Action item status shall be reported as follows (1) Action Item Responses—Each action item close-out report shall include, as a minimum: a. Restatement of the action item. b. Summary recommendation and conclusion. c. Detail descriptive narrative, analysis, calculations or other data as necessary to respond to the action items including rationale for recommendations and conclusions. (2) Action Item Summary a. Summary List of action items, including person(s) responsible for closure, due date, status, closure date and closure summary, and reference to closure documentation. b. Monthly status update for MMRs 71 Subcontract No. _________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Monthly Management Reviews USE: RE-003 PROJECT: Provides monthly status briefing and materials to identify and resolve technical, business and management issues. DRD INTERRELATIONSHIP: MTO APPLICABLE DOCUMENTS: MS-003, MS-004, MS-005, MS-006, PM-002, & RE-001 JPL D-29208, MTO Risk Mgmt. Plan PREPARATION INFORMATION: The MMR Package shall include, but not be limited to, the following: 1. Program Status Overview 2. Programmatic Status a. Summary Earned Value Status in CPR format as described in MS-006 (Cost Status for Phase E) b. Workforce Status—Summary and detail at same level as EV reporting c. Schedule—Schedules and status as described in MS-004 d. Receivable/Deliverable and SDRL status e. Procurements Status—Subcontracts, Parts & Materials f. Risk Management Activities and Status (per PM-002) g. Issues/Concerns and Mitigation Plans h. Liens/Threats List i. Contractual Issues 3. System Engineering Status a. Summary Technical Progress b. Technical Resources Metrics Status c. Requirements o Definition o Traceability o Verification and validation o Interfaces d. Systems Status per common format in item #6 4. Mission Assurance Status—See Page 2 for detail reporting requirements a. QA Status – Hardware & Software c. Parts Status b. Reliability Status –Analyses & PFRs d. Materials and Processes Status 5. Configuration Management Status a. Documents – Release/Approval Status and Metrics b. Drawings – Release/Approval Status and Metrics c. ECRs, Waivers, etc. – Release/Approval Status and Metrics 6. Subsystem and Technical Status including Software and Fault Protection System a. Accomplishments – Met & missed e Issues and Concerns b. Deliverables/Receivables Status f Action Plan to Address Problems c. Earned Value Status g Plans for Next Month d. Schedules h. See page 2 for detail software reporting rqm’ts 7. Action Items – Status for MMRs and prior Flight System Reviews, and New Items 72 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Monthly Management Reviews (Cont.) USE: DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) Mission Assurance Detail-Reporting Requirements (A) RE-003 PROJECT: MTO APPLICABLE DOCUMENTS: Reliability Analyses Status Matrix of all reliability analyses vs. assemblies/subsystems/system to which they apply, responsible authority/engineer, schedule for completion. Problem/Failure Report Summary Status 1) Part 1, which lists P/FRs by component and includes for each P/FR: a) The P/FR identifying number, b) The date the problem/failure/anomaly occurred, c) The location of the hardware when the problem/failure/anomaly occurred, d) A short summary description of the problem/failure/anomaly, e) Status of P/FR (open or closed), f) Preliminary failure effect and risk rating for P/FRs open longer than 60 days, and g) The failure effect rating and risk rating for closed P/FRs (with Red-Flag P/FRs identified). Rating shall apply to P/FR which affect flight hardware. 2) Part 2, which lists for each assembly as a whole: Total number of P/FRs: (1) initiated, (2) closed, (3) Red-Flag, (4) open longer than 60 days, and (5) closed since last report (B) (C) Parts Status Periodic status reports for all electronic parts program activities, including parts list submittals/reviews, NSPAR/waiver processing, part procurement status, issues/resolutions, failure analyses results, response to GIDEP alerts, and all test results [screening, demonstration, upgrade, Total Ionizing Dose (TID) & Singe Event Effect (SEE)]. (D) Materials and Processes Status Status reports for all M&P activities including MIUL submittals/reviews, nonstandard design items/qualification plans, waiver processing, materials and processes issues/resolutions, failure analysis results, response to Government Industry Data Exchange Program (GIDEP) alerts. (E) Software Detail Reporting Requirements 1) Defect density per unit size. 2) Percent test coverage of delivered code. 3) Software Problem/Failure Reports summary and status 73 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Spacecraft and Flight System Requirements USE: Document the spacecraft and flight-system design and interface requirements, including fault protection. DRD INTERRELATIONSHIP: CM-003, SE-002, SE-003, TD-001, TD-005, ER-001 PREPARATION INFORMATION: SE-001 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit I This document shall contain the system functional, performance, and general design requirements, and it will define subsystem-to-subsystem interface requirements. Functional requirements will be allocated to subsystems. (Subsystem functional, performance, and detailed interface requirements will be contained in SE-002.) The document will define the interface requirements between the spacecraft and the launch vehicle and between the spacecraft and the Ground System. Spacecraft requirements for accommodating payloads and supporting their operations will be included. This document shall include: (1) (2) (3) (4) (5) (6) (7) (8) (9) Design criteria, design constraints and a definition of the general philosophy to be used System level derived requirements and constraints affecting subsystem design Allocation of requirements and functions to the subsystems Subsystem boundaries and interfaces in sufficient detail so that identification with cognizant design groups can be made and interface control maintained System alignment and pointing budgets and tolerances within which subsystems must perform. Allocation of system resources such as mass, inertial properties, power, pointing, memory, I/O. System functional block diagram. The grounding policy and design requirements. A high-level Flight System mechanical configuration drawing illustrating subsystem, major assemblies, and payload locations, fields of view, booms and appendages. Flight system configuration for launch, cruise and on orbit will also be shown. System power requirements including power bus regulation, transients, overload protection, inrush current, power-on reset, impedances, etc., plus power mode definitions for flight operations. System level fault protection requirements and allocation to subsystems System level requirements on the telemetry and command structures plus data bus design. System level thermal design requirements and criteria (10) (11) (12) (13) 74 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Subsystem Specifications USE: Define detail requirements for the spacecraft subsystems. DRD INTERRELATIONSHIP: ER-001, ER-002, SE-001 PREPARATION INFORMATION: SE-002 PROJECT: MTO APPLICABLE DOCUMENTS: Contains all the requirements that are to be satisfied by the MTO Spacecraft subsystems excluding the hardware being provided by JPL. Should be responsive to the Spacecraft & Flight System Requirements Document, SE-001. Include the following topics, as a minimum: 1. Subsystem Description and Characteristics 2. Subsystem Block Diagram(s) 3. Performance Requirements 4. Power allocations and related requirements 5. Performance Budget sub-allocations with respect to system budgets 6. Operational Requirements 7. Command and Telemetry Requirements 8. Interfaces to other subsystems 9. Umbilical interfaces 10. System Test Interfaces 11. Subsystem modes 12. Fault Detection and Correction Considerations/Requirements 13. Redundancy description 14. Mass allocation 15. Summary of Software Requirements and Interfaces 16. Power-on reset state 17. Contamination Control requirements 18. Magnetic Control requirements (if any) 19. Special Accommodations 20. Personnel safety requirements 21. System safety requirements 75 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Fault Protection Design Description USE: Document the Flight System Fault Protection Design and Usage. DRD INTERRELATIONSHIP: PREPARATION INFORMATION: SE-003 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit I This document describes the fault protection (FP) system implementation and the system and subsystem level requirements that drove its design. The implementation will include the details of the fault protection detection and correction algorithms. This document will also include a description of its operation and maintenance in flight, particularly with regard to parameter modifications for non-nominal, post-anomaly conditions. The content shall include as a minimum: 1. 2. 3. FP system coverage and implementation requirements. Description of redundancy and cross-strapping, as it pertains to the FP implementation. Description of fault protection settings/configuration for mission critical events, e.g., Launch, MOI, etc. 4. Description of the fault protection design philosophy, architecture and implementation approach. 5. Detailed description of all fault protection algorithms, including graphical representations (e.g. flow diagrams, state charts, or other similar representations). 6. Listing and description and settings/values (by mission phase, as appropriate) of all fault protection parameters. 7. Description of Operational Considerations and Constraints, including the following: a. b. c. Boot States Fault Protection Command and Telemetry Anomaly Resolution Guidelines 8. Description of Safe mode configuration(s). 9. Procedure for returning to nominal operations from Safe mode. 76 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Inputs to Planetary Protection Documentation USE: To provide materials that assist in demonstrating compliance with the NASA planetary protection requirements. DRD INTERRELATIONSHIP: SE-004 PROJECT: MTO APPLICABLE DOCUMENTS: NPR 8020.12.B MTO Planetary Protection Plan _________ PREPARATION INFORMATION: These inputs describe the actions taken to meet the MTO Project planetary protection requirements IAW NPR (formerly NPG) 8020.12B. The project has chosen to use the orbital lifetime approach to meet PP requirements rather than through the use of the microbial burden approach. The Subcontractor provides inputs to those plans/reports that pertain to their effort in this area. Three specific inputs are required in a format provided by JPL: 1. Planetary Protection Control Plan Inputs. These describe the Subcontractor’s planned approach to their element of achieving compliance with PP implementation requirements as set forth in NPR 8020.12B. Information required from the Subcontractor includes, but is not limited to: a. Organic Materials Inventory b. System parameters needed for completion of the orbital lifetime analysis c. System parameters for Reliability Analysis as required for Accidental Impact Analysis d. Any additional microbiological monitoring which may be required by the NASA Planetary Protection Officer (PPO) Prelaunch Planetary Protection Analysis Report Inputs This document is used by the project to provide verification to the PPO that PP requirements have been met. Information required from the Subcontractor includes, but is not limited to: a. System parameters needed for completion of the orbital lifetime analysis b. System parameters for the spacecraft reliability analysis as required for the Accidental Impact Analysis c. Spacecraft reliability analysis d. List of any deviations from the requirements as set forth in 8020.1 Post Launch Planetary Protection Analysis Report Inputs.. This document is a brief summary based on the Pre-Launch report described in 2., but updated to include the effects of launch and early post-launch activities. Information required from the Subcontractor includes, but is not limited to: a. Report any anomalies during the time since the PP Pre-Launch Report, relevant to PP requirements b. System parameters, based on launch and Trajectory Correction Maneuver TCM-1, needed to update the probability of accidental impact by the launch vehicle and orbiter 2. 3. 77 Subcontract No. __________ Date: October 29, 2004, Page 1 of 3 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Development Plan USE: The plan establishes and governs the software development processes and products for the MTO software. DRD INTERRELATIONSHIP: All SW DRDs, CM-002, MS-004, RE-001 TD-001, GS-006 SW-001 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan, D-28353; JPL Software Development, D-23713; JPL Design Principles, D-17868 PREPARATION INFORMATION: 1. A Software Development Plan (SDP) shall be prepared that describes the Subcontractor’s plans for conducting the software development effort for MTO. The term ―software development‖ is meant to include new development, modification, reuse, reengineering, maintenance, and all other activities resulting in a software product. The term ―software‖ includes the software portion of firmware. The SDP shall satisfy the requirements specified in MTO PSMP D-28353, JPL documents D-23713 and D-17868. Elements of this plan may be published as separate documents providing that the same delivery and approval requirements apply to those documents. e.g., Software Configuration Management Plan, Software Operation and Maintenance Plan. For the software, the SDP shall include, but not be limited to the following: a. b. c. System overview including identification of the Software Components, their functions, size and characteristics. Referenced documents (compliance documents and other related documents). Software Project Organization i. Description of all software team members, their roles and responsibilities relative to the software components defined in Section 4.a. ii. Description of the internal software organizational structure. iii. Description of the project software team structure. iv. Description of the relationship of the software project organization to the organizational structure of the rest of the project, including customer interfaces. d. Software Development Process Model i. Description of the software development life cycle model(s) to be used, including identifying the software development activity phases and their sequencing. ii. Description of the planned builds, the objectives of each build, and the software development activities to be performed in each build. iii. Identification of system and software reviews and participants to be conducted and where they occur in the software development life cycle model(s). (RE-001) iv. Plans for regression testing of subsequent builds (after the first). v. Identification of key software deliveries and where they occur in the software development life cycle model(s), including internal deliveries to other organizations within the Subcontractor team and external deliveries to the customer. vi. Description of software process audits by independent auditors or software quality assurance organizations, the frequency of such audits, and the plan for sharing findings and recommendations. 2. 3. 4. vii. Description of software IV&V activities and interfaces with the NASA IV&V facility 78 Subcontract No. __________ Date: October 29, 2004, Page 2 of 3 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Development Plan (Cont.) USE: DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) e. SW-001 PROJECT: MTO APPLICABLE DOCUMENTS: General Plans for Software Development i. Software Methods, Standards, Procedures and Tools ii. Software Classification according to the JPL Software Development Requirements, D-23713. iii. Management of Software Reuse iv. Management of Commercial Off-the-Shelf (COTS) Software v. Handling of Critical Requirements -- Description of the approach (plans, processes, methods, procedures, tools, roles and responsibilities) to be used. vi. Target Computer Hardware Resource Utilization -- Description of the approach (plans, processes, methods, procedures, tools, roles and responsibilities) to be used. vii. The integration of the software system with other flight and ground software elements, with interdependencies, shared products and resources, and long lead software activities identified. Plans for Specific Software Development Product-Oriented Activities—Description of the approach (plans, processes, methods, procedures, tools, roles and responsibilities) to be used for the following activities. i. Software participation in System Requirements Definition ii. Software participation in System Design iii. Software Requirements Definition iv. Software Interface requirements Description v. Software Architecture Definition vi. Software Detailed Design vii. Software Interface Specifications viii. Software Unit Implementation and Testing ix. Integration and Testing of Software Units x. Hardware/Software Integration Testing xi. Software Qualification Testing (i.e., verification of software requirements) xii. Software Validation (Acceptance) Testing xiii. Software participation in System Qualification Testing xiv. Software Transition to Operations and Maintenance xv. Post-Delivery Software Maintenance Plans for Specific Software Development Integral Activities—Description of the approach (plans, processes, methods, procedures, tools, roles and responsibilities) to be used for the following activities. i. Software Project Planning and Oversight ii. Software Metrics iii. Software Risk Management iv. Peer Reviews and Other Technical Product Evaluations v. Joint Technical and Management Reviews vi. Software Corrective Action Process vii. Software Quality Assurance viii. Software Configuration Management ix. Software Process Improvement x. Software Reliability Analyses, e.g. Fault Tree Analysis and Failure Modes Effects and Criticality Analysis f. g. 79 Subcontract No. __________ Date: October 29, 2004, Page 3 of 3 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Development Plan (Cont.) USE: SW-001 PROJECT: MTO DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Continued) h. i. Plans for Software Development Environment, and for Verification and Testing Environment. Schedules and Activity Networks (Include following detail in the Integrated Master Schedule (MS-004)) i. Schedules, showing each build, activities in each build, draft and final products and deliverables, and other milestones ii. Activity networks, showing sequential relationships, dependencies and critical path(s) iii. Schedules shall include at least the following items: 1) Requirements Development activities 2) Architectural Design activities 3) Detailed Design activities 4) Design Reviews 5) Implementation activities 6) Code Reviews 7) Documentation activities 8) Documentation Reviews 9) Unit Test activities 10) Integration activities 11) Test Planning 12) Test Results Reviews 13) All receivables and deliverables, internal and external 14) Schedule slack (margins) in accordance with the Design Principles 15) Any other significant activities, milestones, events or products Resources i. Software Management, Engineering, and Test Environment(s) ii. Personnel – including staffing plan and training plan iii. Other Resources Compliance matrices for Design Principles, D-17868, SDRs (Software Development Requirements D-23713), JPL MTO PSMP (Project Software Management Plan) D-28353 Margins. Plans for management of margins as required by the Design Principles, D-17868 and methods for estimating and measuring the margins. (TD-001) APPLICABLE DOCUMENTS: j. k. l. 5. All deliverables called out in the SDP, such as documents, metrics and reports shall be made part of the Subcontractor software development schedule and shall be delivered to JPL at the frequency specified. 80 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Requirements Document USE: Definition of software requirements in sufficient detail to execute and verify software design effort. DRD INTERRELATIONSHIP: SW-001, SW-003, SW-004, SW-005, SE-001, SE-002, GS-006 PREPARATION INFORMATION: SW-002 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan, D28353 The Software Requirements Document shall contain requirements allocated to the software as well as internally derived requirements. Any element of this document may be published as a separate document providing that the same delivery and approval requirements apply to this document. Topics to be addressed in the SRD shall include but not be limited to the following: 1. 2. 3. 4. 5. 6. 7. 8. 9. Software components description, and/or interface description, and diagrams. Functional requirements, including nominal, fault protection/response, and ―fault mode‖ operations requirements. Interface requirements, including content, format, data source/sink, protocols, and data rates. Performance requirements. (For flight software components) commanding and command validation requirements. (For flight software components) telemetry requirements. Reliability, maintainability, and related requirements. Delivery, installation, and environmental requirements. Design and implementation constraints. 10. Traceability matrix showing a two-way trace of software or software interface requirements to and from higher level requirements, interface control documents, or design decisions from which the requirements in this document are derived. 81 Subcontract No. __________ Date: October 29, 2004, Page 1 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Design Document USE: To provide insight into the software architecture, components and interface design as the foundation for detailed software design and development. DRD INTERRELATIONSHIP: CM-003, SW-001, SW-002, SW-004, SW-005, GS-006 PREPARATION INFORMATION: SW-003 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan, D28353 The Software Design Document shall contain a detailed description of the software architecture, with a collection of components and well-defined interface and service semantics that operate over an underlying infrastructure. Design document(s) shall be developed for the system architecture, each of its components, and all lower-level modules, to and including the individual classes, procedures, and functions. For all software interfaces, Interface Control Documents shall be generated as separate documents, as part of the ICDs as specified in CM-003. Elements of this plan may be published as separate documents providing that the delivery and approval requirements for those documents are contained in an approved Software Development Plan (SW-001). The design document shall include: 1. Overview and Scope 2. Reference Documents 3. Architecture Description a. b. c. d. e. f. g. h. i. j. j. k. l. m. A description of how the software interacts with users and other systems/subsystems. A logical representation of the architecture that models architectural components and supports the representation of both abstract interfaces and interface implementations. Diagrams that show the component interactions/collaborations. Identification and description of the processes and a mapping of processes to system components. Description of software organization from a development viewpoint. Diagrams that show the computer system hardware architecture, with a mapping of the software architectural components to the physical hardware. A bi-directional mapping of the software and interface requirements to software architectural components and operational scenarios. Identification of COTS software products that are expected to be used to implement part or all of specific software architectural components. Identification of legacy software components that are expected to be used to implement part or all of specific software architectural components.. Descriptions and definitions of the behavior and functionality of all components (use of standardized methods such as UML is highly desired) Complete definitions of all external and key internal component interfaces Complete descriptions of all data types, valid ranges, and exception handling mechanisms Descriptions of software architecture-wide key mechanisms and design decisions that are not covered by the above items. Identification and analysis of failure modes 82 Subcontract No. __________ Date: October 29, 2004, Page 2 of 2 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Design Document (Cont.) USE: DRD INTERRELATIONSHIP: PREPARATION INFORMATION: (Cont.) 4. Design Specifications a. b. c. d. e. SW-003 PROJECT: MTO APPLICABLE DOCUMENTS: A bi-directional mapping of each software module and interface to software architectural components and operational scenarios. A complete trace of software requirements to and from each software module Descriptions and definitions of the behavior and functionality of all modules (use of standardized tools such as UML is highly desired) Complete definitions of all module interfaces Complete descriptions of all classes, objects, data types, procedures and functions, including behavior, parameters, constraints, exceptions, side-effects, pre-conditions, post-conditions, coupling and cohesion Identification and analysis of failure modes Allocation and descriptions of fault protection and correction implementations in each module Allocations and estimates of margins as specified in the Design Principles JPL D-17868 and the MTO SMP D-28353 f. g. h. 5. Reliability Analyses a. b. Software Fault Tree Analyses (FTA) Software Failure Modes Effects and Criticality Analysis (FMECA) Note: Electronic versions of the models themselves (e.g., UML) are also to be delivered in addition to the diagrams and descriptions provided in this document. The Subcontractor shall coordinate with JPL to ensure the models are in a format usable by JPL for architecture analysis and evaluation. 83 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software Integration and Test Plans USE: Provides the overall philosophy and plans for integrating and testing the Spacecraft Module software components and Flight System software components. DRD INTERRELATIONSHIP: SW-001, SW-002, SW-003, SW-005, GS-006 PREPARATION INFORMATION: SW-004 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan, D28353 This plan describe the integration (demonstrate that the finished software meets the software requirements, generally prior to h/w integration) and acceptance testing (demonstrate that the software in the containing system meet the goals of the operational and failure mode scenarios) of the software components. Elements of this plan may be published as separate documents, providing that the delivery and approval requirements for those documents are contained in an approved Software Development Plan (SW-001). Topics to be addressed in the Software Integration and Test Plan shall include the following: a. Overall software integration and test process, b. Policy determining which verification process(es) are to be used (i.e., inspection, analysis, test, audit), c. Mechanism for tracing tests back to SRD and other controlling documents, d. Testing policies determining which test types are to be used (e.g., stress, thread, regression), e. Test policies covering test execution (e.g., starting, stopping, re-testing), f. Integration and acceptance test priorities and order, g. Test environment definition and, if needed, test environment development plans, h. Coordination with other testing and test-bed activities, i. j. Test tracking and progress reporting approach, including metrics reporting, Software problem reporting (SPR) and tracking approach, including coordination with system-level problem/failure reporting (P/FR) system, k. Integration test requirements and procedures development plans, l. Integration test execution and report documentation plans, m. Acceptance test requirements and procedures development plans, n. Acceptance test execution and report documentation plans. o. IVV plans 84 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Software User’s Manual USE: To provide instructions for how to use and/or operate with the software. DRD INTERRELATIONSHIP: SW-001, SW-002, SW-003, SW-004, GS-001, GS-006 PREPARATION INFORMATION: SW-005 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan, D28353 The User’s Manual shall include information sufficient for Mission Operations personnel to control, command, and understand the output of the MTO flight software. This document shall serve as the primary source of instrument operations information for the software. The telemetry, command, and block dictionaries shall serve as reference manuals in support of this document. The User’s Manual shall include: a. b. c. d. e. f. g. h. i. j. k. l. m. n. Software Overview, software application (Brief description of the intended uses of the software). Software execution, including major software states and operational transitions between states, startup, restart and reset conditions and responses, during test and flight. Program data, including constants tables, operational data tables, and memory map. Command descriptions and usages, command limitation, suggested sequences for various operational scenarios. Telemetry descriptions and interpretations, expected telemetry sequences for nominal and offnominal situations. Memory readout maps and interpretations. Table uploading procedures and cautions for each table. Program patching and uploading directions, procedures, and cautions. Fault protection conditions and recovery. Operational sequences such as startup, shutdown, switching modes, and instrument parameter adjustments. Software inventory (Identification of all software files, including databases and data files, that must be installed for the software to operate). Software environment (Identification of the hardware, other software and other resources (e.g., equipment, manual forms, etc.) needed to operate the software). Software organization and overview of operation (Brief description of the organization and operation of the software from the user’s point of view). Contingencies and alternate states and modes of operation (Explanation of differences in what the user will be able to do with the software under contingency). 85 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Technical Resources Management Plan USE: Document Technical Budgets DRD INTERRELATIONSHIP: SE-001 PREPARATION INFORMATION: 1. TD-001 PROJECT: MTO APPLICABLE DOCUMENTS: JPL D-17868 Describe the plan for managing technical resources, including establishing margins, defining margin usage strategy (where appropriate), suballocating technical resources among subsystems, tracking status, and applying corrective action when necessary. Document the major technical resources, including performance budgets, for the MTO Flight System. This includes, but is not limited to: a. b. Technical Resources: mass, power, processor utilization, memory utilization, data bus bandwidth, power and pyro switch count, and propellant. Performance Budgets: RF Communications links, attitude control and pointing accuracy, attitude knowledge. 2. 3. 4. Resource allocations shall be shown at the subsystem and assembly levels as appropriate. A subset of the technical resources will be reported on at the MMR. 86 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Spacecraft Parameters Document USE: Documents all of the spacecraft parameters DRD INTERRELATIONSHIP: PREPARATION INFORMATION: TD-002 PROJECT: MTO APPLICABLE DOCUMENTS: Project Policies, JPL D-29220 This document shall contain descriptions of all the parameters in the spacecraft. A parameter is any persistently stored, ground-command, modifiable data value. Both hardware and software parameters shall be described, including at least the following details: 1. Name 2. Level of criticality 3. Value, including any variations that are planned to or that may occur during flight 4. Type of value 5. Minimum acceptable value, if applicable 6. Maximum acceptable value, if applicable 7. Constraints/dependencies upon other parameters’ values, if applicable 8. Method used to determine value 9. Cognizant individual and approval authority for selected value 10. Review frequency (e.g., weekly, monthly, event-based) 11. Commands (e.g., change, view, save) 12. Telemetry 87 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: User’s Guides and References for Test Bed and Simulators USE: Operational user’s guides and references for the FlightSystem Test Bed; and the C&DH Flight-Software Simulator; and for the Spacecraft Interface Simulator, which will be used to support the development and testing of the payload and RAN. DRD INTERRELATIONSHIP: TD-007 PREPARATION INFORMATION: The operational user’s guides and references shall include: 1. Functional Description 2. Physical Description 3. Command Interface 4. Telemetry Interface 5. Operation and Control: States/Modes 6. Power interface circuitry 7. Signal interface circuitry 8. Timing, signal levels, polarity, bit ordering, and data format 9. Test Points 10. Task-oriented user’s guide TD-003 PROJECT: MTO APPLICABLE DOCUMENTS: 88 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Digital Images USE: Provides a photographic record of hardware, test configurations, and facilities. DRD INTERRELATIONSHIP: CM-004, CM-005, PM-001 PREPARATION INFORMATION: 1. TD-004 PROJECT: MTO APPLICABLE DOCUMENTS: Digital images shall be Tagged Image File Format (TIFF), or other common image format, encoded images with a resolution, sufficient to render appropriate detail. Digital image records shall include all Flight System hardware and the support equipment. Digital images shall also be taken of special test equipment, special tooling, test areas, test configurations, and facilities as appropriate The records shall include the following views: a. Two or more views of each subassembly. b. Internal components prior to sealing. c. All sides of each assembly. d. All sides of the system. The hardware digital images shall show the placement of parts, routing of wires and cables, and the relationship of parts. When it is possible, the items shall be arranged so component serial numbers show. A size reference (e.g. ruler) shall be included in each digital image as well as top orientation. A master digital image list shall include the following information, which shall also be supplied with each image: a. A concise title, accurately describing the subject matter imaged. b. If applicable, part number, reference designator, and serial number. c. Subcontractor’s internal file designation for image retrieval. d. Date image taken. e. Where image was taken. 2. 3. 4. 5. Photographic record before and after repairs and rework, and before enclosure and close-out. 89 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Inputs to Flight System–Ground System Interface Control Document USE: This is an input to the Flight System–Ground System Interface Control Document (ICD). It describes the Subcontractor interfaces between the MTO Flight System and the MTO Ground System. DRD INTERRELATIONSHIP: CM-003, SE-001 PREPARATION INFORMATION: Input to Flight System–Ground System ICD TD-005 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit I, Exhibit IV This input shall contain detailed descriptions of the functional, protocol, and physical interfaces between the Flight System and Ground System. This will define the protocol data units that are used between Flight and ground protocols, and over the virtual connections between Flight and ground applications. The inputs will include: a. Documentation of each functional (virtual) interface between Flight and ground based software applications. b. Documentation of each protocol used between the Flight and ground. c. Implementation use matrix for each standard (CCSDS and other) that is implemented between Flight and ground. d. Description of the physical interface between the Flight and ground systems. e. Description of the protocol data units and application data units transported over the Flight  ground virtual interfaces. 90 Subcontract No. ___________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Technical Analyses USE: To document key design and requirements analyses at the Flight System through subsystem level that are not addressed by other DRDs. DRD INTERRELATIONSHIP: MA-005, SE-001, SE-002, TE-001, TE-006 PREPARATION INFORMATION: TD-006 PROJECT: MTO APPLICABLE DOCUMENTS: For each analysis performed by the Subcontractor, document the following, as applicable: 1. 2. Description of the requirement the analysis is addressing. The report shall bear the report title, number, date of issue, and the name of the analyst. Each page shall contain the page number and revision letter or number as applicable. The report shall include a description of the articles analyzed and other pertinent data as necessary to fully describe the analysis environment. The reports shall contain all calculations necessary to verify analytically that the design satisfies the requirements defined in the referenced Equipment Specification. Tables of data from computer program outputs shall bear complete identification of all input parameters used and sufficient explanation to render the output data entirely understandable. Adequate sketches shall be provided throughout the analysis, to eliminate the need for referring to any drawings of the article analyzed. The report shall include copies of all technical reports used in the analyses. References used in the report shall be defined in a table of references. Any assumptions that must be made to facilitate the analysis must be clearly stated and adequately justified. The operating limits for which the analysis is valid shall be included in the report. 3. 4. 5. 6. 7. 8. 9. 10. A description of the computer programs that are used in the analysis shall be included in the report where necessary to interpret the report. 11. The report shall include a table of contents, an abstract, and conclusions and recommendations. 91 Subcontract No. __________ Date October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Flight System Testbeds, Simulators and Support Equipment Implementation Plan USE: Describes the Subcontractor’s plan for the flight system testbeds, simulators, and support equipment to be used for flight system development and mission operations DRD INTERRELATIONSHIP: CM-003, SE-001, TD-003 PREPARATION INFORMATION: TD-007 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Project Software Management Plan JPL D-28353 The Subcontractor shall prepare a plan for the development, verification, validation, utilization and delivery of test beds and simulators necessary for software development and to assemble, integrate, and test the Flight System, spacecraft, and subsystems and to support mission operations. The plan shall include the following: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. Quantity, types, and intended use of the test beds and simulators Utilization of models (breadboard, engineering model, flight, spares) and simulators Description of how payloads are incorporated in the various test beds and simulators Test bed schedules (design, fabrication, and utilization) Functional requirements for test beds to adequately represent the flight spacecraft Design requirements for test bed hardware and software for each test bed Requirements for data interchange between the ground support equipment and spacecraft Differences between test beds/simulators and flight equipment that it is intended to emulate Validation and validation plan to demonstrate and document the capabilities and characteristics of each test bed Approach to integration of test beds and simulators with ground system elements List of ICDs (CM-003) List of user’s guides and related information to be provided with each test bed and simulator Requirements and plans to allow JPL remote access to the test beds Additional ground support equipment (mechanical, electrical) and software needed to verify that the flight system meets all technical requirements Unique tooling, special test equipment, special handling equipment, or Government Furnished Property needed for flight system fabrication, assembly, test, and launch operations Spares plan and parts inventory and stores approach for maintenance of test beds, support equipment, and simulators Facilities to be used Grounding system for test beds, simulators, and support equipment that is compatible with the flight system grounding (SE-001) 92 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Spacecraft and Flight System Verification Plan USE: Describes the Subcontractor’s approach for Spacecraft and Flight System Verification and Test DRD INTERRELATIONSHIP: ER-004, SE-001, SE-003, TE-005 PREPARATION INFORMATION: TE-001 PROJECT: MTO APPLICABLE DOCUMENTS: Exhibit I; Project V&V Plan, D-TBD Prepare and submit a plan that defines the approach and methods the Subcontractor will implement to verify that the Spacecraft and Flight System meets the requirements in Exhibit I and the Project V&V Plan, D-TBD. The plan must describe how functional, performance, environmental and reliability requirements will be verified at all levels (flight system, spacecraft, subsystem, assembly, etc.) as well as a function of design and implementation maturity (breadboards, testbeds, engineering models, flight hardware and system/spacecraft integration & test, and post launch). The plan shall address verification of spacecraft and flight system interfaces and functions with external mission interfaces, including science and engineering payloads, launch vehicle, Ground System (GS), Deep Space Network (DSN) and the Mars Science Laboratory (MSL). Where verification and test information required herein are provided in separate and prior delivered SDRL(s), the applicable sections shall be referenced and supplemented herein as appropriate. The plan requires the following as a minimum: 1. Verification matrix of MTO Project and Subcontractor-generated requirements with traceability from Exhibit I to all Subcontract specifications (partitioned from system-level to subsystems, assemblies, payload interfaces, etc) identifying verification methods for each requirement. 2. Detailed flow chart(s) of all planned test verification activities from subsytem/assembly to Spacecraft and Flight System-level, and including test interrelationships, functional verification, dynamic and environmental test, inspections, analyses, and other activities planned by the Subcontractor and Subcontractors to verify compliance with all requirements. 3. For requirements that will not be verified by test or calibration on the Flight System (such as fault protection, margin testing, etc), describe why not and describe the methods by which these requirements will be verified. Where testbeds, analyses or engineering model hardware will be utilized, provide a description of what will be done to certify that such approaches provide a suitable representation of the flight system as the work evolves over the prelaunch life of the Subcontract. JPL must concur with all exceptions and methods for verification deviations. 4. The plan requires descriptions of the following: a. Description of all hardware and configurations during verification activities b. Test levels and durations (as applicable) (See ER-004) c. Approach for allocation of the verification activities, i.e. when and how it will be done and at what level (flight system, spacecraft, subsystem, assembly, etc.). d. Pass/Fail criteria for all verification activities e. Method of testing, facilities (including location), instrumentation and controls used. f. System and subsystem test data, trending and analysis methodology. g. Plans and approach for addressing measurement uncertainties for verification test (as applicable). h. Subcontractor’s plans for Test Readiness Reviews and post-test result reviews i. Safety issues and concerns j. Summary schedule of verification activities. k. Subsystem verification and validation l. Functional & scenario tests m. Flight Software Verification and Validation 93 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Spacecraft and Flight System Integration and Test and Launch Operations Plan USE: Also known as the assembly, test, and launch operations (ATLO) plan, this plan describes the work to be performed at the system level to integrate, test, and launch the Flight System. DRD INTERRELATIONSHIP: ER-001, TE-001, TE-007 PREPARATION INFORMATION: TE-002 PROJECT: MTO APPLICABLE DOCUMENTS: MTO Preliminary Environmental Requirements Document, JPL D-26405 The Subcontractor shall prepare a plan containing but not limited to the following: (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) Test Program requirements and objectives Description of the individual tests to be performed, their configuration, test objectives, special equipment, and requirements addressed by the test Organization of the test team including description of each team function, roles and relationships between functions, and required personnel qualification Description of the plan for safe conduct of operations (flight hardware and personnel). Flight hardware contamination and environmental control requirements and implementation Flight hardware security requirements and implementation Requirements for handling deviations, exceptions, omissions, typographical corrections, and discrepancies during tests Listing of additional plans and procedures to be written in support of this plan including name, nomenclature, hazard level, and approval levels Transportation plan for all flight moves. Plan for support equipment certification, including FMEA, acceptance, checkout, installation, and configuration management Plan for control of Flight System configuration during ATLO Plan for development of test procedures, including hazardous procedures Use of quality assurance Control and archive of controlled records (including as-run test procedures and data) Network schedule with appropriate margin (baseline schedule) Receivables and deliverables for all flight hardware, flight software, flight sequences, ground support equipment, and documentation (baseline) Integration, Test, and Handling constraints Facility requirements and floor plans for all facilities used during testing including Kennedy Space Center (KSC) and Cape Canaveral Air Station (CCAS) Plan for real-time, as-run flight system operations log. Environmental Test Plans and test levels per the MTO Environmental Requirements Document. (ER001) 94 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Subsystem Test Plans USE: Document subsystem functional, performance and environmental test plans. DRD INTERRELATIONSHIP: ER-004, SE-003, TE-001, TE-002 PREPARATION INFORMATION: TE-003 PROJECT: MTO APPLICABLE DOCUMENTS: Prepare documents that define testing required at the subsystem level and summarize testing done at the component/assembly level to verify subsystem functional, performance and environmental requirements. These documents may also be used to define subsystem testing to be done at a higher level, or on an alternate test platform. They should summarize the test plans and scope of tests to be conducted using special simulation setups, test beds, or any unique test set-up required for verification. Suggested Outline: 1.0 Introduction 1.1 Scope 1.2 Acronyms 2.0 Reference Documents 3.0 Test Objective 4.0 Test Requirements 5.0 Test Plans 6.0 Configuration 6.0 Unique Test Equipment 7.0 Special Considerations These documents are also intended to provide subsystem unique test requirements to ATLO personnel to aid in planning system level testing and may be superceded by future system test plans and detailed procedures. 95 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: Inputs to Launch Site Support Plan USE: To define the launch site support requirements DRD INTERRELATIONSHIP: LV-001, TE-002 PREPARATION INFORMATION: TE-004 PROJECT: MTO APPLICABLE DOCUMENTS: Prepare a document to define the launch site support requirements that includes, but is not limited to: 1. Facility characteristics and requirements for flight system processing, test and launch, including government-provided supplies and services. Government supplied transportation and handling support such as forklifts, trucks, transporters, storage space. Government-supplied operational interfaces support such as power, communications lines including voice, data, and control, cranes, purges, spin tables, etc. Government-supplied propellants, gases, etc. 2. 3. 4. 96 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: NUMBER: DSN, Ground System and MSL Compatibility Test Plans and Reports USE: To define the tests required to verify the compatibility of the telecommunications subsystem with the Deep Space Network (DSN), and to verify the spacecraft compatibility with the Ground System (GS) and the Mars Science Laboratory (MSL). DRD INTERRELATIONSHIP: TE-001 TE-005 PROJECT: MTO APPLICABLE DOCUMENTS: PREPARATION INFORMATION: All test data and reports shall be maintained and made available for inspection at the Subcontractor’s facility. Copies of test data shall be submitted to JPL as requested. 1. DSN Compatibility Test Plan This MTO spacecraft plan establishes the tests and documentation required to demonstrate the compatibility between the telecommunications subsystem and the DSN. The plan includes descriptions for all receiver, transmitter, command, telemetry and radiometric tests and test configurations. Test facilities and dates shall be described. 2. DSN Compatibility Test Report The Subcontractor shall complete a report that fully documents the results of the testing. 3. GS Compatibility Test Plan The GS Compatibility plan establishes the tests and documentation required to demonstrate the compatibility between the spacecraft and the GS. The plan includes descriptions of all command sequences and telemetry tests. 4. GS Compatibility Test Report The Subcontractor shall complete a report that fully documents the results of the testing. 5. MSL Compatibility Test Plan The MSL Compatibility plan establishes the tests and documentation required to demonstrate the compatibility between the MTO spacecraft and the JPL provided MSL spacecraft or simulator. 6. MSL Compatibility Test Report The Subcontractor shall complete a report that fully documents the results of the testing. 97 Subcontract No. __________ Date: October 29, 2004, Page 1 of 1 DATA REQUIREMENT DESCRIPTION TITLE: Test and Verification Reports USE: To provide a test report and a verification report to ensure verification of all MTO requirements. NUMBER: TE-006 PROJECT: MTO APPLICABLE DOCUMENTS: DRD INTERRELATIONSHIP: ER-004, TD-001, TD-007, TE-001, TE-007 PREPARATION INFORMATION: All test data and reports shall be maintained and made available for inspection at the Subcontractor’s facility. Copies of test data shall be submitted to JPL as requested. 1. Flight System Test Report Final package that is a compilation of the results of the flight system level environmental and performance testing. As a minimum, the reports contained in the compilation requires the following information: A. Description of the test configuration and instrumentation, and test sequence. B. Compilation of the test data and results. C. A list and description of specific deviations/changes from the approved test plan or test procedures. D. Copies of all non-conformance reports, PFRs, MRB actions or other documents that define problems/changes/deviations from the approved test plans or test procedures. E. Copy of logs with mate/demates on all flight-interface connectors and flight flanges. F. Environmental test report documentation. (See ER-004) G. Trend data and results Flight System Verification Report A summary report recording the actual verification method, when and where it was done, at what level (flight system, spacecraft, subsystem, assembly, etc.), and the results for each flight system requirement, per the verification methods identified in TE-001. Include the traceability of flight system verifications to lower-level verifications. Provide references to the test reports or analyses where the details are documented. Testbed Test Reports: Reports containing a compilation of the results of testing performed using test beds. As a minimum, the reports require the following information: a. Description of the test bed: flight and ground hardware and software configuration, instrumentation, and test sequence. b. Compilation of the test data and results. c. A list and description of specific deviations/changes from the approved test plan or test procedures. d. Copies of all nonconformance reports, P/FRs, MRB actions, or other documents, which define problems/changes/deviations from the approved test plans or test procedures. e. Copy of logs with mate/de-mates on all test bed flight-interface connectors and flight flanges. Verification and Validation Reports for Testbeds A summary report recording the actual verification and validation methods, when and where it was done, at what testbed hardware and software configuration, and the results for each test bed requirement, per the verification and validation methods identified in TD-007, item 8. Include the traceability of test bed verifications to lower-level verifications. Provide references to applicable test reports and/or analyses where the details are documented. 2. 3. 4. 98