AVGS Activity Models
Role-Based Perspectives
Reliability Engineer

Reliability Engineer Perspective

Supports decomposition of reliability, maintainability, and Integrity-related Product Support requirements alongside named SMEs (Mohammed, Feras).

  • Review reliability and Integrity decomposition
  • Align with named SMEs on mission reliability content
  • Confirm metrics and assumptions in rationale

Primary responsibilities

  • Participate in decomposition of reliability and Integrity Program requirements.
  • Coordinate with Mohammed and Feras as the Reliability SMEs supporting this work.
  • Confirm reliability metrics, assumptions, and data sources are documented in rationale.
  • Ensure mission reliability requirements are technically scoped and not restatements of higher-level intent.

Day-to-day work activities

  1. Review reliability-tagged Product Support parents and propose a decomposition strategy with SMEs.1
  2. Validate mission reliability, service life, and fleet flight hour assumptions referenced in rationale.2
  3. Confirm data sources required to assess reliability are within Ground Systems scope or sourced from a known owner.3
  4. Support Integrity Program generalization in the ARB package.4
  5. Sign off on reliability rationale before JAMA submission.5

Reliability content map

TopicWhat to confirmSource
Mission reliabilityDefinition + applicable assumptionsReliability SME
Service life / 30-yearApplicability to requirementProgram standard
Fleet flight hoursBasis for the number usedReliability SME
Integrity Program scopePreserved under generalized namingARB record + SME

Government approvals touched

  • ARB review of Integrity / reliability-related architecture updates.
  • Customer reliability and Integrity Program review inputs.
  • Audit support for reliability rationale and data source provenance.

Reliability review checklist

  • Reliability assumptions and definitions are captured in rationale.
  • Integrity Program scope is preserved through generalized naming.
  • Mission reliability content is reviewed with named SMEs.
  • Data sources required for reliability assessment are identified.
  • Requirement is technically scoped, not a parent restatement.