Generator First-Article Approval: Production Control

An approved generator sample does not authorize later production or shipment. Before production, require one production-ready first article tied to the frozen build, with every difference, its evidence and disposition, and the exact units covered by production authorization. If the baseline, unit identity, or approval scope is unresolved, keep production on hold.

This guide controls the commercial and evidence handoff from sample to production for an OEM or private-label generator order. It is not US government-contract First Article Approval or aerospace AS9102 reporting. It is also not a generic FAT, routine quality control, legal advice, or a pre-shipment inspection. It sets no universal test method, sample size, tolerance, defect class, approval period, or release limit.

Name the sample object and the decision it can support

The word sample can describe several objects. If buyers treat them as equal, a narrow approval can become an uncontrolled production promise.

Write each object's role into the order record. The buyer may approve a prototype's appearance while leaving other fields open. Those may include the engine, alternator, controller, breaker, labels, manual, package, test evidence, or market variant. “Approved sample” must not erase those limits.

Keep the decisions separate. Inspection or testing creates evidence; approval accepts a named object and scope; production authorization permits a named revision within a stated range; shipment release closes the gate for the actual order. No decision implies the next one.

Freeze one approval identity and revision baseline

Freeze the baseline and identify the unit before comparing the first article. “Same as sample” is not a build key.

Start a controlled cover sheet with these fields:

• List the project, RFQ, quote, and purchase-order references when issued.
• State the exact build code, target market, and electrical variant.
• List the applicable BOM, drawing, wiring, software, data sheet, label, manual, accessory, and package revisions.
• Identify the approved sample, marked views, date, owner, scope, conditions, and open points.
• Identify the first article, build date, work order or lot, assembly site, and supplier entity.
• State the pack ID, issue date, preparer, reviewer, and revision.
• Set the proposed production lot, serial range, date range, or other traceable limit.
• List events that force a new review, such as a part, site, process, software, market, file, or rework change.

Use one revision index for the full pack. A chat photo, an email saying “OK,” and a BOM with no revision cannot govern the same object. The generator documents before order checklist gives the wider file-control method. The first-article pack should cite those controlled records, not copy loose files.

Private-label details belong in the same identity chain. A nameplate, mark, display, manual, carton, accessory, or language file may look right but carry an old revision. Use the generator OEM and private-label checklist to define the approved objects. Then bring their IDs into the baseline.

Do not fill a missing value with a nearby model or earlier order. Mark it OPEN, name the owner, and state which gate it blocks.

Require one evidence-return row per requirement

Sample feedback often arrives as marked photos, chat comments, sheets, and calls. Before review, put each relevant comment into a row that another person can follow without rebuilding the conversation.

Keep the states separate. A supplier statement may say what was installed. A marked part, controlled build record, or observation may offer stronger identity proof.

A test record may support one need within its method and build. None becomes technical, safety, market, or contract approval until the responsible party records that decision.

Do not invent a universal first-article test list. Derive the checks from the buyer's specification, approved drawings and BOM, agreed test plan, market duties, and open sample comments. Each row should show its source and the owner of any open pass rule.

Route every deviation to a named decision owner

A deviation is any recorded difference between the frozen baseline and the first article. That includes a change called harmless, improved, temporary, or equal. Logging a change does not reject it. It stops an unreviewed change from entering the production baseline.

Open a deviation for matters such as:

• Record a different engine, alternator, controller, breaker, AVR, battery, harness, sensor, outlet, fuel part, enclosure, or mount.
• Record a changed supplier, site, subcontractor, assembly route, process, software, or setting.
• Record hidden rework, hand finishing, temporary parts, or sample-only work.
• Record mixed revisions in drawings, BOM, manual, label, art, carton, accessories, or spares.
• Record a market or electrical variant that differs from the approved object.
• Record an unknown serial, lot, work-order, or BOM link.
• Record evidence from a nearby model instead of the first article.

Each deviation needs its own ID and baseline requirement. Record the observed state, affected objects, supplier explanation, containment, evidence request, owners, decision, conditions, and scope. Send any change that may affect interfaces, protection, use, safety, conformity, service parts, warranty, files, or packing to the qualified owner. The sourcing or inspection team should not declare it equal.

Use dispositions that describe what happens next:

Avoid “approved deviation” with no object or limit. A one-unit waiver must not become a permanent option. An approval for one market must not move to another. Visible rework must not change the routine work instruction in silence.

Make the supplier trace the first article into production

Trace the first article into the declared production route, because a carefully prepared sample may come from a different site, team, material set, or process. Surface appearance alone cannot demonstrate production transfer.

Link the identified unit to the production BOM and drawings. Then link it to received controlled parts, the work order, current instructions, software or settings, assembly and rework records, test records, labels, manuals, and packing state. Name the people or stations responsible for release. If another site does a step, record its entity, place, scope, control record, and approval owner.

One first article does not prove process ability or future output. It tests whether the proposed system can keep the approved identity and retrieve one clear production record. Capacity, supplier qualification, and routine quality need other evidence.

Challenge the weakest handoffs. Link the engine and alternator on the unit to the BOM. Match the controller to the released file.

Retrieve the current wiring drawing and manual. Link rework to the same unit. Match the market and private-label version. If the build used unusual conditions, record that limit and state what later evidence is needed.

Separate technical approval, production authorization, and shipment release

Use a separate decision block for evidence review, qualified approval, production authorization, and shipment release. One signature line marked “approved” hides which object, scope, and authority it covers.

Production authorization should say whether work may start, continue under containment, or remain on hold. It should also name what happens to material or units already built before a deviation was found. Silence is not authorization.

Shipment release comes later and applies to actual goods. The generator pre-shipment inspection checklist can compare presented units with the approved order baseline, but inspection does not rewrite that baseline or close an unapproved change. Payment milestones, shipping instructions, inspection completion, and technical acceptance should not be allowed to impersonate one another.

Consolidate the First-Article Deviation and Approval Pack

The pack is a compact index, not a replacement for the source evidence. Its job is to make identity, differences, decisions, and effective scope retrievable.

Build it with these sections:

1. document control, project identity, parties, responsibilities, and revision history;

2. approved-sample identity, configuration key, approval scope, conditions, and open items;

3. production-representative first-article identity, build route, order/lot/serial links, and declared site;

4. requirement-to-evidence matrix with sources, results, limitations, and evidence states;

5. controlled-component, software/settings, artwork, manual, accessory, and packaging returns;

6. deviation register with containment, impact review, disposition, closure evidence, and affected units;

7. technical or qualified approvals required for the exact issues raised;

8. production-authorization block and a separate shipment-release block;

9. distribution list, retained reference location, superseded records, and review triggers.

For every approval, record the object, configuration, sample or serial identity, revision, evidence basis, approver, date, scope, conditions, and expiry or review trigger where one is required by the agreement. Do not invent a default validity period. A review trigger is often more useful: a controlled-component change, site or subcontractor change, process change, software change, destination variant, prolonged interruption, documented failure, or other agreed event can reopen the relevant scope.

Store the approved pack where purchasing, supplier quality, inspection, document control, and the supplier are all using the same revision. Preserve superseded versions and the decision history. A spreadsheet that can be silently overwritten is not a reliable approval record unless version control and access are addressed.

Put supplier returns and stop rules into the RFQ and PO

First-article control is easier to enforce when the supplier sees the return format before quotation and sample work. Attach a schedule or quality appendix with these rows:

Have the supplier mark each row CONFIRMED, EXCEPTION, or OPEN. It must cite the returned file and revision, name the owner, and give a due date. A sales reply without production, quality, file, and technical owners is not a closed handoff.

Use RETURN when the supplier can provide a named field or record without changing the baseline. Use HOLD while a specialist decision or release authority remains open.

Use STOP if the unit cannot be linked to the baseline. Stop as well if a controlled change is hidden or has no decision, the production route cannot be traced, or the approval scope is unknown. Only the named owner may reopen the gate after new evidence is recorded. Schedule pressure and spoken promises do not create approval.

The generator supplier buyer checklist can frame the broader supplier decision, while the BEAR OEM/ODM page gives a starting point for a customized inquiry. Neither page approves an exact production build.

For a BEAR-specific return, send Miya the destination, use, proposed build, quantity, OEM scope, sample state, production period, and return schedule. BEAR must still confirm the build, duties, site and process scope, files, sample plan, timing, MOQ, capability, and approval path. Keep production and shipment on hold until the responsible parties close the gates in writing.