Product Support Team (Product Development)
Product Support & SME Perspective
Validates that decomposed Ground Systems requirements reflect the real sustainment, Integrity, and CBM+ intent — and supplies the definitions, standards, and context engineers need.
- Review for intent and operational realism
- Provide definitions, standards, and historical context
- Confirm Reliability and Integrity scope with named SMEs
Primary responsibilities
- Review draft Ground Systems requirements for alignment with Product Support intent and sustainment realities.
- Provide subject-matter context: CBM+ definitions, Integrity expectations, Reliability assumptions, O-Level practices, PSE behavior.
- Confirm whether a requirement belongs to Ground Systems, Air Vehicle, or another team.
- Support Reliability decomposition with Mohammed and Feras as named SMEs.
Day-to-day work activities
- Triage incoming SME questions from Systems Engineers and route to the right SME.1
- Hold focused review sessions on draft requirements; answer in writing so authors can paste into rationale.2
- Confirm scope: Ground Systems vs. Air Vehicle vs. another product team.3
- Provide source references — AFIs, technical orders, sustainment plans, historical CBM+/Integrity decisions.4
- Sign off on requirements that reflect intent; reject and redirect those that do not.5
- Support ARB by confirming Product Support intent behind naming/behavior generalizations.6
SME coverage map
| Topic area | Primary SME(s) | Typical question type |
|---|---|---|
| Reliability / Mission Reliability | Mohammed, Feras | Metrics, assumptions, service life |
| Integrity Programs | Product Support lead | Scope, generalized naming |
| CBM+ / Program Health Monitoring | Product Support lead | Data needs vs. analytics ownership |
| O-Level / PSE / Cradle | Sustainment SME | Maintenance procedures and boundaries |
| Configuration preservation | Matt Joseph / Config SME | Definition and applicability |
Government approvals supported
- Provide Product Support input to ARB on naming/behavior generalizations.
- Support customer reviews by confirming sustainment intent of each requirement.
- Validate that the requirement set supports CBM+, Integrity Programs, and broader Product Support needs.
Deliverables
- Documented SME answers to open questions.
- References to applicable standards, definitions, and historical decisions.
- Sign-off that a decomposed requirement captures the intended sustainment behavior.
- Topic-area readiness statement for ARB and customer reviews.
Dependencies
Needs from others
- Specific, written questions from Systems Engineers.
- Architectural context from the Architect.
- Adequate review time scheduled by the Project Engineer.
Provides to others
- Authoritative intent and definitions.
- Validation of scope boundaries.
- Reliability and Integrity Program guidance.
Decision rights
- Whether a requirement reflects the correct Product Support intent.
- Acceptance of Reliability-related decomposition in coordination with named SMEs.
- Confirmation that historical CBM+/Integrity context has been honored.
SME review checklist
- Requirement matches the operational intent it is meant to support.
- Terminology aligns with Product Support and Integrity conventions.
- Reliability content has been reviewed with Mohammed or Feras when applicable.
- All SME questions are answered in writing and captured in rationale.
- No requirement claims Air Vehicle ownership or out-of-scope analytics.