Scope Coordination metadata only · never CAD, geometries, or program-name technical data · controlled records referenced by identifier only · ITAR + EAR boundaries respected end to end.

One program in focus. ?family= scopes this view to another program · Customer B (automation cell, Phase C) or Customer C (launch tooling, Phase H). Defaulting to Customer A.

Program lifecycle · where this program stands

Supplier gate sequence, A through H. The current phase is the only attention point; build & qualify resolves at the factory acceptance runoff.

A · Capture
Opportunity
B · RFI
Capability fit
C · Bid
Price + lead time
D · Contract
Kickoff
E · Design
PDR → CDR
F · Current
Build & qualify · FAT
H · Later
Lifecycle support

Timeline · coordination touches

Threaded from your tools · status only
Today · 9:02 AM Teams
"Who's briefing the CEO before Thursday's runoff?" raised in the cross-plant channel · reply drafted for your read
Today · 8:40 AM Calendar
Thursday west-coast factory visit confirmed on your calendar · 9:00 AM runoff window held
Yesterday · 4:18 PM Travel
OEM program manager's witness travel refreshed · arrives Wednesday evening · confirmation forwarded, no action needed
Yesterday · 11:05 AM Outlook
Visit-agenda thread reopened by the program office · two carry-over punch-list items from the last runoff attached
2 days ago · 3:30 PM Teams
Manufacturing Readiness Review wrapped · one open action assigned to the integration lead · due before Thursday
4 days ago Outlook
ECN-A-0142 status note · the OEM program manager's sign-off still outstanding · waiting on one site to acknowledge the current revision REF · NO CONTENT
1 week ago Teams
FAI plan owner confirmed · first-article inspection due-date set ahead of the runoff · pass/fail status pending, report stays in PLM REF · NO CONTENT
3 weeks ago Calendar
CDR signed off · detailed design frozen, manufacturing authorized · program moved from Phase E to Phase F

Open coordination · what's still moving

Aging + status · never record content
5 days ECN-A-0142 · awaiting OEM program-manager sign-off · one site yet to acknowledge the rev AGING
2 days MRR action · integration lead · due before Thursday's runoff OPEN
today FAI plan · pass/fail status to confirm before FAT DUE
×2 Punch-list carry-over from last runoff attempt · both reopened on the agenda thread
Today's next action
Confirm Thursday's site visit and reply to the CEO-brief question · the readout pulls the MRR open action, the two punch-list carry-overs, and the witness travel window into one note. Drafted in your voice, awaiting your send.
Drafted at 9:06 AM · you always send · we never do

The OEM program manager

Role Counterpart on Customer A · owns the gate sign-offs
Cadence Weekly sync · last touch yesterday 11:05 AM
Style Wants the punch-list and approval status up front; brief on logistics
History Witnessed the PDR and CDR runoffs · flies in for FAT
Outstanding ECN-A-0142 sign-off · 5 days · surfaced for the Thursday agenda

AIP reporting touchpoints

Cadence Monthly roll-up → quarterly narrative
This program feeds Milestone health · gate outcomes · open-change count · FAT/SAT dates
Next roll-up Friday draft · in operational-KPI language, from coordination atoms only
Where it lands The brief · the owner reads a woven narrative, not a dashboard

Recurrence watch

Same finding, separate records 2 open follow-ups tagged to the same process step across this program COUNT
Validation gap 1 design revision with no first-article re-do opened yet
Reading Counts and linkage only · the record content stays in PLM, never threaded here
Pattern · proactive
Every Customer A gate review in your book has slipped at least once on an outstanding approval, never on the build. The approval clock is the thing to watch, so it's surfaced first.

Related industry events

Aerospace automation forum Next month · the OEM program manager is attending · a quiet chance to clear the ECN sign-off in person
Composites + tooling expo Q3 · relevant to the Customer B bid · prep folded into that thread, not this one
Note Event prep is coordination only · no program technical data travels to an event