Methodology Guide

A working guide to how aerospace manufacturing programs like the CWP-700 Composite Wing Panel Production Program are actually run — the discipline that AS9100, First Article Inspection, and the Material Review Board add on top of ordinary project management, illustrated with this program's real, reconciled numbers.

Aerospace manufacturing PM, at a glance

Most of what a program manager does on an aerospace production contract is recognizable from any other delivery methodology: a charter, a budget, a resource plan, a RAIDD log, a communications plan, a closeout report. What's different is the layer of quality discipline sitting on top of it, and the fact that this layer isn't optional — it's a condition of the contract itself. Meridian Aircraft Co. does not do business with a supplier that isn't AS9100 certified, and it does not accept production volume of a part until that part has passed First Article Inspection. Every nonconformance that surfaces after that point goes through a Material Review Board, not through whichever engineer happens to be closest to the problem. That combination — AS9100 as the umbrella, FAI as the gate, MRB as the ongoing control — is the spine of this suite, and it's what distinguishes an aerospace manufacturing program from a software or services program using the same underlying PM skeleton.

The CWP-700 Composite Wing Panel Production Program is a fixed-price production contract: Acme Aerostructures, a Tier 1 supplier, builds composite trailing-edge wing panels for Meridian Aircraft Co.'s Meridian M7 narrowbody. It runs 18 months in two phases — a 6-month Qualification & First Article phase, and a 12-month Production Ramp & Steady-State phase — and its $3,500,000 total budget, roster, and quality log are all real, reconciled artifacts in this suite, not placeholder numbers.

Phase 1 — Qualification & First Article (6 months)

Phase 1 exists to answer one question before a single production-rate part gets built: can this tooling, this process, and this supply chain actually produce a conforming part, repeatably? The team is weighted toward engineering and quality rather than production labor — a Program Manager, a Quality Engineering Lead who owns the AS9100 relationship for this program, a Manufacturing Engineer, a Materials/NDT Engineer, a Tooling Engineer dedicated to qualifying the production tooling, a Supplier Quality Engineer running PPAP on the raw-material supply chain, and a Program Coordinator. That's $755,000 of the program's $2,710,000 total labor spend, front-loaded into six months rather than spread evenly, because this is where the highest-risk unknowns get resolved.

The phase ends with First Article Inspection: a full dimensional layout, material certification check, special-process verification (the composite cure cycle and NDT ultrasonic scan), and an AS9102 Form 1/2/3 package, witnessed on-site by Meridian Aircraft Co.'s source inspection representative. On this program, the first tooling run did not pass clean — two of eight panel positions had an edge-trim dimension out of tolerance. That went to the Material Review Board (see below) as a rework-and-reinspect disposition rather than a failed FAI and a restart, which is exactly the difference a mature quality system is supposed to make: catching the defect doesn't have to mean losing the schedule, if the disposition path is already built into the plan. The reworked panel passed re-inspection, the customer source inspector witnessed and accepted it on-site, and Phase 2 production was released — three weeks later than the original target, fully inside the schedule buffer that had been built in for exactly this kind of event.

Phase 2 — Production Ramp & Steady-State (12 months)

Once FAI clears, the program shifts from "prove it can be built" to "build it at rate, and control it." The roster shifts too: the Tooling Engineer rolls off (the tooling is qualified and released), and a Material Review Board Chair joins — a role that doesn't exist in Phase 1 because there isn't yet enough production volume to generate a steady stream of nonconformances to disposition. That's $1,955,000 of labor across twelve months, still anchored by the same Program Manager, Quality Engineering Lead, and Manufacturing Engineer, with the Materials/NDT Engineer's allocation dropping from 80% to 50% (the qualification-heavy NDT development work is largely done) and the Supplier Quality Engineer's allocation rising to 100% (PPAP maintenance and incoming-lot verification becomes a continuous job, not a one-time qualification).

Production at rate surfaces problems that a low-volume qualification run doesn't: an NDT inspection queue backlog formed within the first weeks of ramp, adding roughly four days to the panel release cycle, simply because inspection capacity had been sized for FAI-level throughput rather than full production rate. The fix — a second, in-house NDT technician rather than outsourcing ultrasonic inspection — resolved the backlog within two weeks and kept full material traceability in-house. That specific miss (sizing NDT for the wrong phase's throughput) is one of the clearer lessons this program produced, and it's recorded, with a recommended fix, in the Lessons Learned register rather than just fixed quietly.

The Material Review Board, as a working control

Five nonconformances went through MRB disposition across the program's life: the FAI edge-trim finding (rework), a cosmetic surface porosity in a non-structural zone (use-as-is), an oversized fastener hole (rework, with an engineering-approved oversized fastener), a composite ply misalignment caught by NDT (scrap — no disposition short of scrap was defensible once the root cause was traced to layup fixture wear), and a raw material lot with a missing traceability code (return-to-supplier, before it ever touched production). Four different dispositions, out of the four the standard allows, on one program — a reasonable illustration that MRB isn't a rubber stamp for "rework it and move on." The board itself is intentionally cross-functional: a quality chair, an engineering representative, and a customer representative brought in specifically for major or structural dispositions, so that no single person can decide, alone, that a nonconforming part is good enough to fly.

Discipline comparison — how this differs from the other suites

The pattern across all four suites is the same: a predictive or hybrid PM skeleton (charter, budget, resource plan, RAIDD, governance, closeout) carries the program, and a domain-specific compliance layer sits on top of it that decides what "done" and "acceptable" actually mean. For Federal, that's ATO and Section 508. For Aerospace, it's AS9100, FAI, and MRB. The skeleton transfers; the compliance mechanics don't.

This program, by the numbers

Roles on this program

Questions people ask about this

Why does the Tooling Engineer roll off after Phase 1? Once tooling passes FAI and is released for production, there's no ongoing tooling-design work — only maintenance, which the standing production organization handles. Keeping a dedicated Tooling Engineer on the program budget past that point would be paying for capacity the program no longer needs.

Why does the MRB Chair only join in Phase 2? Phase 1's single nonconformance (the FAI edge-trim finding) was dispositioned with the Quality Engineering Lead chairing an ad hoc board — there wasn't yet enough volume to justify a dedicated chair. Production ramp changes that: a steady stream of nonconformances at rate needs a dedicated owner, not an ad hoc one.

What's the difference between use-as-is and rework? Use-as-is means the part is accepted exactly as it is — an engineering judgment that the nonconformance doesn't affect fit, form, or function. Rework means the part is modified (machined, re-drilled, patched) to bring it into conformance, then reinspected. Both require MRB sign-off; neither is a shortcut around inspection.

Why is a fixed-price production contract different from the Federal suite's Task Order? A Federal Task Order is a government contract governed by the FAR, with its own cost/pricing rules, security requirements (ATO), and accessibility requirements (Section 508). This is a commercial contract between two private companies — no FAR, no ATO, no ITAR (it's not a defense article) — so the compliance burden is entirely AS9100/aerospace-quality-driven rather than federal-acquisition-driven.

Did the program actually come in under budget, or is that just good luck? The $150,000 program management reserve went entirely undrawn — but two risks that were explicitly planned for (the NDT capacity risk and the tooling schedule risk) did materialize. The reserve wasn't undrawn because nothing went wrong; it was undrawn because the mitigations built into the base plan (the schedule buffer, the dual-NDT-source fallback) were sized correctly for the risks that were already identified going in.

What happens to the roles at closeout? They transfer to Acme Aerostructures's standing production quality organization rather than disappearing — the Quality Engineering Lead stays available through the transition window, and the MRB Chair's responsibilities move to the standing production Quality Review Board, since steady-state production continues indefinitely after this program's formal closeout.

How this compares to the other suites in this portfolio

If you've looked at the PM, Agile, or Federal suites in this portfolio, the shape of this one should already feel familiar: a charter, governance, a resource plan reconciled to a budget, a RAIDD log, status reporting, and a closeout tied back to lessons learned. What's new here is a physical-manufacturing quality system instead of a software-delivery or federal-compliance one — First Article Inspection instead of a go-live cutover or an ATO, and a Material Review Board instead of a change-control log or a defect backlog. The underlying PM discipline is portable across all four domains; the domain-specific compliance layer is what makes each suite worth building separately instead of just relabeling one template four times.

Risk management approach

Risk on this program is tracked in a single RAIDD log (Risks, Assumptions, Issues, Decisions, Dependencies) rather than a separate risk register and issue log — a deliberate choice to keep one traceable thread from an identified risk through to whatever it turns into. Four risks were identified at program kickoff: a single-source composite prepreg material with no fallback, NDT capacity that hadn't been validated against production-rate throughput, a tooling qualification schedule with limited slack, and uncertainty around the customer's source-inspection availability for the FAI gate. Two of the four (the material lead-time risk and the customer-availability risk) never materialized into an issue during the program; the other two both did, and both are traceable, line by line, from the original risk entry through the issue that resulted, the decision that resolved it, and the lesson that closed the loop. That traceability is the point — a risk log that only tracks risks that didn't happen isn't proving anything about how well the mitigations worked.

Assumptions get the same discipline. Two were logged at kickoff: that Meridian Aircraft Co.'s engineering source data was final and baselined at contract start, and that Acme Aerostructures's existing autoclave capacity was sufficient for the planned Phase 2 production rate without new capital investment. Both held for the life of the program — no engineering change requests came in from the customer, and no additional autoclave capacity was needed — but they were written down as assumptions rather than treated as certainties, precisely because an unstated assumption is the risk you don't find out you were carrying until it breaks.

Program timeline

Laid out this way, the program's two real disruptions — the FAI rework and the NDT backlog — both land early in their respective phases, which is exactly where a mature quality system wants problems to surface: while there's still enough schedule and budget cushion left to absorb them, rather than compressed against a delivery deadline with production already running at full rate.

What "quality" costs, and what it buys

It's easy to treat AS9100, FAI, and MRB as compliance overhead — paperwork layered on top of the "real" engineering and manufacturing work. The numbers on this program argue the other way. The direct quality investment — tooling and fixtures NRE, the FAI lab/metrology/NDT testing budget, and the dedicated quality-engineering labor across both phases — comes to roughly $320,000 against a $3,500,000 total program budget, a little over 12% of program cost. The Program CBA page frames what that buys against a single avoided failure mode: a nonconformance that makes it past FAI and into a delivered part, discovered only after the aircraft is in the field. An Aircraft-on-Ground event, the root-cause investigation, the supplier corrective-action cycle, and any rework or return that follows are conservatively estimated at several times the entire quality investment for this program — which is the argument for why the investment is proportionate to the risk it's managing, not proof that any specific failure was avoided. The program's actual MRB history — five real nonconformances, four different dispositions, zero that made it to the customer undetected — is the more concrete evidence that the system did the job it was built to do.

Further questions people ask

Could this program have skipped FAI and gone straight to production, to save the six months? No — not and still hold AS9100 certification or sell to Meridian Aircraft Co.. FAI isn't a project-management best practice that a program can choose to skip under schedule pressure; it's a contractual and certification requirement. The six months in Phase 1 is the cost of proving the tooling and process work before committing to a production rate, not a buffer that a more aggressive PM could negotiate away.

Why track cosmetic nonconformances (like MRB-002's surface porosity) through the same formal MRB process as a structural one? Because the disposition — not the severity — is what determines the process. A cosmetic nonconformance still needs an engineering judgment call and a documented record of who made it and why, even though the outcome (use-as-is, in this case) is less consequential than a structural rework or scrap decision. Treating minor findings informally is exactly the kind of shortcut that erodes traceability over time.

Is a Tier 1 supplier's program team this small in practice? Roles here represent dedicated program-level ownership; each role also draws on Acme Aerostructures's broader corporate functions — the AS9100-certified quality management system, corporate supply-chain management, and standing production operations — that aren't billed to this individual program's budget. The program team is deliberately lean because it leans on infrastructure that already exists at the company level.

Reading this suite alongside the others

Anyone comparing this suite to the PM, Agile, or Federal suites in the same portfolio will notice the underlying documents track closely — same charter structure, same RAIDD approach, same resource-plan-to-budget reconciliation discipline, same closeout format tying back to lessons learned. That's intentional: it's the same PM skeleton demonstrated four times, once per domain, so the domain-specific compliance layer — AS9100/FAI/MRB here, ATO/Section 508 in Federal, sprint cadence in Agile — is what's actually being tested each time, not whether a new template can be invented from scratch.

Supplier quality (PPAP), explained

The Production Part Approval Process was originally an automotive standard, but it's widely borrowed across aerospace supply chains because it answers a question AS9100 doesn't fully address on its own: not "does the part conform," but "can this specific supplier reliably keep producing conforming parts, lot after lot." On this program, PPAP sits underneath the composite prepreg and fastener-hardware supply chain, owned by the Supplier Quality Engineer. A supplier passes PPAP by submitting evidence — material certifications, process capability data, sample inspection results — that ties a specific production process to a specific expected output, not just a one-time sample that happened to measure in tolerance. The one real PPAP-adjacent finding on this program, a raw-material lot with a missing batch traceability code, was caught at incoming inspection and returned to the supplier before it ever reached production — a control that exists specifically because AS9100's traceability requirement doesn't stop at the supplier's front gate; it has to reach back into the raw material itself.

Certification and audit cadence

AS9100 certification isn't something a program earns; it's something the company holds, audited on a recurring cycle (typically a three-year certification cycle with annual surveillance audits) by an accredited third-party registrar. What a program like this one does is generate the evidence — First Article records, MRB dispositions, supplier PPAP files, lessons learned — that an internal or external auditor would sample against during that surveillance audit. None of this suite's artifacts are themselves the certification; they're the operating record a certified company is expected to be able to produce on request. That distinction matters for anyone reading this suite as a stand-in for "how does a company get AS9100 certified" — it doesn't answer that question, because certification is a corporate quality-system audit, not a program deliverable. What this suite shows is what a single program's slice of that operating record looks like day to day.

Where this suite's numbers come from

Every dollar figure on this page is drawn directly from the Program Budget and Program Resource Plan pages in this suite, not invented separately for narrative purposes — the $755,000 Phase 1 labor total and $1,955,000 Phase 2 labor total sum to the $2,710,000 labor line in the budget, which combines with $640,000 of non-labor and an undrawn $150,000 reserve to the program's $3,500,000 total. The MRB case count (five), the Lessons Learned entry count (ten), and the CBA's return-on-investment figure are pulled the same way, from the MRB log, Lessons Learned register, and Program CBA pages respectively — so a reader who wants to verify any number here can trace it back to its source artifact rather than taking this guide's word for it.