# Presentation: 552834

## Experiment TitleNRA NumberLWSSET Contract Number

- PI
- Contact Information
- Date

## Summary of Presentation – Change as Needed

- Science Summary
- Experiment Top-level Information
- Status
- Operations
- Technical Disciplines - Electrical, Mechanical, Thermal, Software
- Parts, Quality Assurance,
- Schedule

## Science Information Summary

- What are you measuring, electrons, protons, GCR, single event/total dose, or shielding new devices, correlation with other missions, expected number of events, etc.
- Summary of Minimum Success Criteria, Radiation Exposure levels needed, data rate and volume, acceptable orbits, required environments

## Experiment Top-level Concept 

- Experiment architecture/implementation
- Places experiment in context of overall SET mission
- Is there a clear identification of all lower-level components that make up the experiment, as well as their function?
- Does the top-level concept mesh with the overall science requirements, design philosophy, and operational SET concept?

## Status and Changes Last Update

- Of Ongoing Development Work (I.e. breadboard manufacturing/testing)
- Status of testing and evaluation of breadboard prototypes, etc.  Results of tests and how they compare to requirement-driven performance expectations.
- Changes since last report (Management, Technical, or Cost)
- What was the catalyst/driver/impact for any changes? I.e. science, peer review of design, interface, software, power, data, mass, etc.
- Experiment peer reviews to date
- Summarize results of any internal experiment peer reviews, including significant issues addressed and status of Action Items
- Summary of major Action Items and any follow-up implementation changes that may have resulted

## Personnel Summary

- Brief Summary or Organization Chart of personnel (PI, Co-PIs, partners, sub-contractors, designers, QA, etc.) and their responsibilities

## Experiment Requirements Overview

- Demonstrate knowledge that you understand where your requirements are coming from
- Are all experiment requirements documented?
- Are higher level requirements that drive the experiment identified?
- Are requirements that flow down and drive lower-level experiment elements identified?
- Have all requirements been allocated to an owner?
- Do all requirements have an identified verification method?
- Are cross-cutting requirements that drive the experiment design (contamination, electrical, radiation, etc) clearly identified and addressed, as well as their impacts?

## Experiment Technical Resources and Budgets

- Are technical resource budgets (power, mass, data) identified, allocated, documented and controlled?
- Does the experiment meet allocated carrier interface budgets from the SEARS?
- Are the experiment performance budgets clearly identified and controlled?  Does the experiment meet identified budgets? Configuration Management?
- Is there adequate margin in all budgets for the level of maturity? 30% margin for DR level. Show mitigation strategy for margins below guidelines.

## Major trades/implementation decisions

- Identify all major implementation drivers (3U vs 6U cards, funding, interfaces, parts selection, etc.)
- Explanation of final implementation solution and process
- Are all major trades complete?  Briefly describe your completed trades with rationale.
- Describe any open major trades, when is completion planned, and description/rationale for various options.

## Experiment Operations Concept

- Number of data samples - per orbit, per day, data volume estimates
- Defined within context of overall experiment concept
- Does the experiment operations concept take into account and mesh with the planned mission operation concept to date?
- The following information is required from the PI during their design review to describe the operations concept of the experiment.  The presentation should be structured so as to provide an overview of experiment operations and a description of operations by phase.
- Generic:
- Specify any mounting or FOV constraints
- Specify requirements for simultaneous operation with any other investigation (if known)
- For each phase the presentation must provide information on:
- Required sequence of commands from the carrier, use of RESET, or experiment standby bi-levels
- Expected telemetry responses from the experiment
- Any timing restrictions (e.g. minimum/maximum time between steps), minimum powered off times, is science lost due to annealing?
- Any dependencies between command sequences
- Thermister, RadFET, or anlaog services required?
- It is strongly recommended that a timeline be included for each phase.

## Experiment Operations Concept

_**Operational Phases**_
- _First Activation_
- Specify the exact sequence of events required for the first activation of experiment.  Include information on the following:
- Power resources used and order they must be activated, and durinig powerdown
- Required command sequences for experiment checkout and expected telemetry responses
- Required state following activation
- _Normal Operations_
- Specify the normal or typical operations timeline following the first activation. Include details regarding frequency of “measurement” or “data takes” as applicable.  Specify data rates and frequency for each type of data take.  Specify trigger events or scheduling criteria for each type of data take.
- _Standby Operations_
- Specify the conditions for going into and coming out of standby if required.
- _Deactivation_
- Specify the conditions and commands to deactivate the experiment.
- _Reactivation_
- Specify any conditions/requirements/verification sequences required to reactivate if different from those of first activation

## Experiment Mission Completion /Expectations Operations

- What are the successive steps of the demise of your experiment?
- What are the indicators (e.g. current change, bad data) that your experiment is nearing its mission end?
- Does your interest in the data increase or decrease as your experiment degrades? Or will you want your experiment turned off?

## System Block Diagram

- Include in diagram:
- Mechanical illustration - as applicable for box experiment
- Experiment Interface to Carrier
- Power Distribution
- Signal Interface
- Detector Elements

## Power and Signal Flow and Grounding Diagram

- Include in diagram:
- Voltages used
- Current used for each voltage, and current limiting implementation
- Grounding scheme
- Show isolation between power return and chassis
- RS-422 Differential or Single ended?
- Are you using a dosimeter? Or thermistor

## Detailed Design Implementation Specifics

- Experiment functionality and design implementation
- i.e. partitioning of functions within system (block diagrams, etc) as required to illustrate detailed design

## Major Interfaces

- Are all the major carrier to experiment interfaces clearly known?
- Describe the interface
- List any TBDs on the interface.

## Heritage

- What is the flight heritage of the experiment or it various components or concepts?

## Redundancy/Fault Tolerance Approach

- What is your redundancy philosophy & implementation plan and how does the design accomplish fault tolerance? Graceful degradation?
- Has preliminary reliability analysis been completed and documented?  What were the major recommendations and which are being adopted?

## Software Requirements and Implementation

- What processor is being used?
- What language is being used?
- Estimated Lines of Code
- Software or Firmware?
- Are you using an FPGA?

## Development Approach Analysis

- Identify all primary analysis required to demonstrate design meets allocated requirements.  If not yet completed, explain why and provide both schedule for completion and an assessment of risk to further development due to remaining outstanding work in these areas.
- Identify currently ongoing analysis required to develop design details, as well as plan and schedule for completion.  Provide schedule for completion and risk assessment of remaining analysis to ongoing design effort.

## Development Approach

- Design, Fabrication, Integration, and Test Procedures for breadboard, prototype, and/or flight unit
- Explain the end-to-end development plan of your experiment to getting to a final flight experiment.
- Is there a plan for experiment testing and verification throughout all phases of development, including I&T?
- Is there a list of GSE and an overview of the GSE design?  Is there a list and plan for development or procurement of all necessary GSE required to test and verify the system?
- Are any special facilities or test requirements identified and a plan for implementing these in place?
- Is there a plan for developing preliminary models, breadboards, prototypes, or qualified units and what these units will be used for after their completion?
- Describe Anomaly Tracking Process & System
- Will you be requesting a carrier simulator system from GSFC?

## Electrical System - Interface Circuits

- Schematic for each first circuit interface and  show what is not being used.

## Parts Information

- Has Parts List and Parts Plan been submitted to GSFC for review and approval?  Did you:
- Identify all non-QPL/QML parts
- specify screening criteria to up-grade devices, who will perform the screening and results, if known
- Identify which parts require PIND,  who will perform PIND and whether parts passed PIND
- Specify if each part's use in your design complies with derating requirements as specified in GSFC's EEE-INST-002 document
- See _[http://](http://nepp.nasa.gov/index_nasa.cfm/725/)__[nepp](http://nepp.nasa.gov/index_nasa.cfm/725/)__[.](http://nepp.nasa.gov/index_nasa.cfm/725/)__[nasa](http://nepp.nasa.gov/index_nasa.cfm/725/)__[.](http://nepp.nasa.gov/index_nasa.cfm/725/)__[gov](http://nepp.nasa.gov/index_nasa.cfm/725/)__[/index_](http://nepp.nasa.gov/index_nasa.cfm/725/)__[nasa](http://nepp.nasa.gov/index_nasa.cfm/725/)__[.](http://nepp.nasa.gov/index_nasa.cfm/725/)__[cfm](http://nepp.nasa.gov/index_nasa.cfm/725/)__[/725/](http://nepp.nasa.gov/index_nasa.cfm/725/)_ [click on link to EEE-INST-002, and log in]
- Specify whether radiation lot testing at the component level is required.
- Identified which part, which test (TID, SEU, SEL, etc.) and who will perform the testing.  Include results, if known.
- Identify parts that need additional screening and/or testing (and not included in above categories)
- Parts Issues:
- Include any selection, use, screening or testing issues?
- Have all parts received approval from GSFC's PCB (Parts Engineer, Radiation Engineer, SAM, and SET Experiment Manager)?
- Has a GIDEP Alert and NASA Advisory review been completed? (impact analysis and mitigation identified?)
- What is the status of any parts testing or screening?
- What parts(GFE and residual stock) are you getting/wanting from GSFC, how many and when do you need them? List out each.
- Discuss any other outstanding parts issues?

## Mechanical System

- Layout Drawings
- Weight, box, board, 3U, 6U, size
- Picture of experiment
- Torqued at certain level is that okay
- Ground plane, thermal contact
- Modeling

## Thermal System

- This should be information based on the components in your experiment don’t just list the temperatures as they are listed in the SEARS for the carrier, unless they happen to be the same.
- Power dissipation: max/min/nominal for each mode of operation (nominal, submodes, and standby)
- Thermal modeling (if any)
- Temperature predictions: max/min/nominal
- Thermal Testing Description/Status: completed or planned
- Conformal Coatings

## Software System

- Bubble chart, modes of operations
- Test Plans and Acceptance Testing Philosophy

## Modeling Results and Issues

- Thermal Margin, Mechanical
- If SET Project performs modeling, please provide information as soon as possible so we can perform it. The analysis needs to be complete prior to flight experiment build.
- Breadboard and Engineering Model Test Results

## Verification Approach

- If applicable, at BB or ETU level, covered more at PER level
- Experiment Verification Process
- Demonstrate how the experiment will be verified at the various levels and at final delivery.
- Requirements verification
- Show how requirements will be verified and when during development or integration level.
- Verify Completed Tasks
- Submit an up-to-date copy of SEARS Appendix A or the document you are using.

## Risk Management Chart

- Identify the major risks and status
- Clearly identify risks, consequences, decision points, and mitigation strategies.
- Are the mitigation plans realistic and do they result in serious impact to the mission (i.e degraded performance, limited life, descope, etc.)
- List at a minimum of three risks you have identified

## Risk Identification Chart

|  | Risk Description | Rate (High, Medium or Low | Mitigation and Comments |
| --- | --- | --- | --- |
| 1 |  |  |  |
| 2 |  |  |  |
| 3 |  |  |  |
| 4 |  |  |  |
| 5 |  |  |  |

## Quality Assurance Information

- What PWB Workmanship Standard is being used?
- What Printed Wiring Assembly (PWA) Workmanship Standards is being used?
- Are Assemblers using NASA-STD-8739.4 Wiring Workmanship Standards?
- Where is Flight Hardware fabrication being done?
- Where is Flight Hardware testing being done?
- Who will perform Flight PWA inspections?  Are they NASA trained or certified?
- Are Operators trained/certified to NASA-STD-8739.3 Solder Standards?
- Are Operators trained/certified to NASA-STD-8739.1 Staking/Conformal Coating Stds?
- Has _everyone_ who will touch Flight Hardware passed ESD training?
- Do work and storage areas have ESD and environmental controls in place?
- Are ESD, Temperature & Humidity monitor logs being maintained?
- Describe your Non-Conformance reporting system?
- Are there any Waiver Request? Have they been approved by GSFC?
- Have PWA test procedures been generated?  Included in Acceptance Data Package?
- Have Handling and Shipping Procedures for Flight Hardware been developed?
- Have you reviewed GIDEP and NASA Alerts for impact on parts?
- Does your design comply with PPL-21, Appendix B component derating requirements?
- Will your Flight EEE components meet your specified radiation levels?
- Have Parts Plan, Parts and Materials Lists been sent to GSFC for review?  Approved?
- Have you imposed MAR requirements on your contractors & subcontractors?
- Schedule/timeframe for flight build?  Have you allowed time for PWB coupon analysis?
- When can we schedule an initial visit to the fabrication and test facilities?

## Experiment Document Tree & Status

- Provide status and delivery dates of necessary documents
- Address all documents – SEARS Appendix A, B, and C, Specifications, Interface Control Documents, etc.

## Schedule

- Show major milestones and delivery dates

## Summary of Issues

## Acronyms – Change as Needed

- BB - Breadboard
- DR – Design Review
- EARD – Experiment Accommodations and Requests Document
- ETU – Engineering Test Unit
- FOV – Field of View
- GFE – Government Furnished Equipment
- GSE – Ground Support Equipment
- GSFC – Goddard Space Flight Center
- ICD - Interface Control Document
- I & T – Integration and Test
- Max – Maximum
- Min - Minimum
- PER – Pre-Environmental Test Review
- QA – Quality Assurance
- SEARS – SET Experiment Accommodations Requirements Specification
- SET – Space Environment Testbed
- TBD – To Be Determined
- VTL – Verification Tracking Log

## Submit Prior to Design Review Telecon

- Final Parts Plan – 1 month prior
- Initial Waivers
- Modeling and Analysis information if SET is performing your modeling
- Documented package of all major trades
- Schematics
- EARD - 1 month prior
- Verification Tracking Log (VTL) SEARS Appendix A
- Schedule