Project Engineer
Project Engineer Perspective
Tracks decomposition progress, ARB readiness, JAMA submission timelines, and the cross-team commitments that keep Product Support requirements moving.
- Track decomposition commitments and ARB milestones
- Coordinate SME availability and reviews
- Surface blockers before they slip the schedule
Primary responsibilities
- Maintain the decomposition schedule across CBM+, Integrity, PSE, O-Level, Personnel, and Configuration topics.
- Track SME engagements (Mohammed and Feras for Reliability; Product Support for sustainment).
- Coordinate ARB submissions and confirm architecture is ready prior to JAMA entry.
- Monitor the readiness gate: when a requirement is ready for JAMA review.
Day-to-day work activities
- Stand-up review: status of each parent (assigned, drafted, in SME review, in ARB, in JAMA, baselined).1
- Confirm SME availability for the week (Mohammed, Feras, Product Support reps).2
- Drive ARB submission cadence and track open ARB action items to closure.3
- Run the JAMA readiness gate; reject items missing rationale, allocation, or SME sign-off.4
- Maintain risk and blocker log; escalate aging items.5
- Brief leadership on decomposition burn-down and government review readiness.6
Status views maintained
| View | Audience | Cadence |
|---|---|---|
| Decomposition burn-down | Leadership | Weekly |
| SME engagement schedule | Author + SMEs | Weekly |
| ARB submission log | Architect + PM | Per ARB cycle |
| JAMA readiness dashboard | Author + Owner | Continuous |
| Risk / blocker register | Leadership | Weekly |
Government approvals coordinated
- ARB scheduling, agenda, and submission-package coordination.
- Customer/program review prep (SRR, PDR, CDR milestones).
- Audit support for requirement traceability and ownership.
- Disposition of customer comments back into JAMA actions.
Deliverables
- Status dashboard of decomposed vs. outstanding parent requirements.
- ARB submission packages and decisions log.
- JAMA submission readiness summary per topic area.
- Risk and blocker register with mitigation owners.
Dependencies
Needs from others
- Draft requirements and open-question lists from Systems Engineers.
- Allocation confirmation from the Architect.
- SME availability commitments.
Provides to others
- Clear deadlines and ARB submission windows.
- Visibility into upstream/downstream blockers.
- Escalation paths for unresolved SME questions.
Decision rights
- Sequencing and prioritization of decomposition work.
- Calling a requirement "Ready for JAMA Review" once quality gates pass.
- Escalating SME or architecture blockers.
Tracking checklist
- Every parent requirement has a named decomposition owner.
- Open SME questions have target resolution dates.
- ARB-approved naming/behavior updates are reflected in pending requirements.
- JAMA submission status is current for each topic.
- Risks and blockers are visible to leadership.