Documentation and Reporting Flashcards
7 cards from real CRE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Documentation and Reporting flashcards as text
Which document formally captures the agreed-upon reliability requirements between a customer and supplier at the start of a program?
Answer: Reliability Requirements Specification
A Reliability Requirements Specification documents the mutually agreed reliability goals, constraints, and metrics before program execution begins.
In a Failure Mode, Effects, and Criticality Analysis (FMECA) report, the 'criticality number' for each failure mode is calculated using which two parameters?
Answer: Failure rate and failure mode ratio
MIL-STD-1629A defines criticality number Cm as the product of failure rate, failure mode ratio, and mission time for quantitative FMECA.
A reliability engineer needs to communicate a sudden field failure spike to executive leadership. Which reporting format is MOST appropriate?
Answer: Executive dashboard with trend charts and key metrics
Executive dashboards condense complex reliability data into visual trends and key metrics suited for senior leadership decision-making.
What is the primary purpose of a 'lessons learned' document in a reliability engineering program?
Answer: To transfer knowledge from completed programs to future ones
Lessons learned capture insights from both successes and failures so future programs can avoid repeating mistakes and replicate successes.
Which section of a Reliability Test Report typically documents the statistical confidence level and sample size justification?
Answer: Test Plan Rationale and Statistical Basis
The test plan rationale section documents the statistical methodology, confidence levels, and sample size calculations that underpin the test design.
An 8D corrective action report requires 'D4: Root Cause Identification.' Which tool is MOST commonly documented in this step?
Answer: Is/Is Not analysis combined with fishbone diagram
The 8D D4 step uses Is/Is Not analysis to bound the problem and fishbone (Ishikawa) diagrams to identify the verified root cause.
When documenting reliability predictions per MIL-HDBK-217, which information is mandatory to report for each part?
Answer: Part failure rate, quality level, and operating stress factors
MIL-HDBK-217 predictions require documenting each part's base failure rate, quality level, and applied stress derating factors to justify the calculated failure rate.