New Product Introduction Team Site

NPI Team Site Get the Atlas drive module ready to build, together A shared working space for engineering, sourcing, production and quality as a design becomes a stable production process. Northstar Components is a fictional company and the Atlas drive module a fictional product, used throughout this site as the worked example. This site covers industrialization: handoffs, supply, trial builds and evidence. Customer-facing launch messaging lives elsewhere. Where is your work in the lifecycle? Each page answers one stage, with a worked Atlas example and the handoff to the next stage. Design handoffs Engineering passes the current design reference, change context and open questions to the receiving production role. Supply readiness Tie each build-critical part to a source, expected availability, receiving location and responsible role. Trial builds Agree the build scope, brief the participating roles and route observations to the people who can review them. Acceptance evidence Keep evidence traceable to a requirement, a revision and an owner, and show whether it has been reviewed. Launch support Route a production issue or open readiness item to the right function with product, location, shift and reference context. Section Divider Working across sites How teams hand work to each other The handoff pattern used on every page Plants, lines and shifts change; the four parts of a handoff do not. Name the receiving role Address the handoff to a role, such as the Atlas line production engineer for the receiving plant, not to whoever happens to be on shift. Write the role and the plant or line in the first sentence. Name a backup role for the next shift. Point to the work reference Give the drawing, BOM or work-instruction reference with its revision so everyone discusses the same version. Quote the revision letter, for example bracket B-214 Rev C. Link or cite the one governed copy rather than attaching a duplicate. Record open questions List what is not yet known, each with an owner role, so a question does not read as a decision. One question per line, phrased so it can be answered yes, no or with a number. Mark each as open, assigned or answered. Agree the next coordination point End with the next time or event when the two teams will look at the item together, such as the pre-build review or the next daily stand-up. Name the forum, not just a date. Say who sends the update if the answer changes. Sample readiness snapshot Illustrative Atlas figures, not live data. Source: sample NPI readiness review, as of week 14 of the sample program. Each value shows its denominator. build-critical parts with confirmed supplier delivery dates 18 of 24 design handoff questions answered by receiving roles 7 of 9 planned trial builds completed, with observations logged 2 of 3 evidence items reviewed by their owner role 11 of 20 Lifecycle pages The pages of this site, grouped by the kind of question they answer. Design-to-Production Handoffs Prepare, walk through and record a handoff, with a bracket revision example. Before the build Open page Supply Readiness A sample readiness register and the steps for reviewing supplier acknowledgements. Trial Builds Coordinate scope, briefing and observations for a trial build window. During the build Acceptance Evidence A sample evidence index and how to tell collected evidence from reviewed evidence. After the build Launch Support Who to route engineering, material, production and quality issues to, and what to include. Design-to-Production Handoffs A good handoff leaves nothing to guess After a handoff, the receiving team can say which design reference is current, what changed since they last looked, which questions are still open, and who owns the next step. If any of those four is unclear, the handoff is not finished. The owner of this page is Manufacturing Operations and Quality. If a step here does not match how your plant works, tell the owning team so the page can be corrected rather than working around it. Run a handoff in five steps Prepare the reference set Confirm the drawing, BOM and work-instruction revisions that apply, and note what changed since the last handoff. Name the receiving roles List the production, quality and sourcing roles at each receiving plant, plus a backup role for each shift. Walk through the changes Hold a short working session on the changed features only. Engineering explains the intent; receiving roles say what it means for their line. Record questions and owners Write each open question as its own line with an owner role and a status of open, assigned or answered. Agree the next coordination point Name the forum where the open items will be revisited, and who posts the update if an answer changes. Worked example: Atlas bracket B-214, Rev C Fictional example of a handoff record. It shows how a question is routed, not how it is resolved. What engineering explained Rev C moves two mounting-hole locations on the Atlas motor bracket to clear a redesigned heat sink. Engineering shared the revision letter and the changed dimensions with the receiving Plant 2 line. Reference: bracket B-214, Rev C, replacing Rev B. Change scope: two hole locations; material and finish unchanged. What production raised The Plant 2 production engineer asked whether the existing drilling fixture can still locate the part with the new hole positions. Question recorded as: does the current fixture locate Rev C parts without modification? Status: assigned to the Plant 2 tooling role. What happens next The tooling role reviews the fixture against the Rev C drawing and reports back. Nothing is approved by this record; it only makes the question visible and owned. Next coordination point: the pre-build review for trial build 2. If the answer needs a design change, engineering is looped in through a new handoff entry. When a handoff touches other work A part may not arrive in time Check availability and receiving location for the changed parts. The change affects an upcoming build Align build scope and briefing with the participating roles. Supply Readiness Every build-critical part needs a source, a date, a place and an owner Before a planned build, each build-critical part should connect to four things: where it comes from, when it is expected, where it will be received, and which role is responsible for chasing it. A gap in any of the four is a readiness question, not yet a problem. Sourcing owns supplier communication. Production and quality raise what they need; they do not agree dates with suppliers directly. Sample readiness register Fictional Atlas register for trial build 3. Dates refer to weeks of the sample program; unanswered items remain visible. Part Source and expected availability Receiving point Owner and next question Bracket B-214 Rev C Bracket supplier; provisional week 15 Tuesday Plant 2 receiving, Dock 4 Sourcing lead: confirm Rev C tooling at the pre-build review. Connector C-77 Connector supplier; revised week 15 Thursday, one week later Plant 2; receiving dock still to confirm Material planner: confirm dock and effect on build 3 at the supply call. Heat sink H-30 Heat-sink supplier; provisional week 15 Monday Design engineer: resolve compatibility with the Rev C bracket in the handoff session. Fastener kit F-12 Plant 2 standard stock; quantity check before build 3 Plant 2 stores, trial-build kit area Stores role: confirm quantity at the kit pull before build 3. Review supplier acknowledgements Compare the acknowledgement with the order Check part number, revision, quantity and delivery date line by line against what the build needs. Mark every mismatch Note differences in revision, quantity or date, and which build or line each one affects. Record the impact State in one sentence what is affected, for example: trial build 3 cannot start the connector step before the revised date. Hand the item to the owning role Pass unresolved mismatches to the sourcing lead or program role, with the register line and the next coordination point. The handoff does not promise a resolution. Related coordination Availability depends on a design change See how changes are handed to receiving teams. A build is approaching Check scope, briefing and dependencies for the trial build window. Trial Builds Plan the trial build as a team, then learn from it This page helps teams agree what a trial build is meant to show and how observations reach the people who can review them. It is a coordination guide; it does not authorize work or replace the approved operating and safety instructions for your line. What a trial build should leave behind When the build window ends, the team should have a shared scope that says what was built and why, the roles that took part, the design and material references in use, and a single place where observations were recorded. Observations are descriptions of what was seen. Whether one is acceptable is decided in review by the roles who own that decision. Coordinate the window in five steps Align scope and timing Agree the quantity, the configuration, the line and the shift or shifts, and what the team wants to learn. Check references and dependencies Confirm the design revisions in use and that the parts on the readiness register are expected before the start. Brief the participating roles Walk production, quality and engineering through the scope, the references and how to record an observation. Capture observations as they happen Record what was seen, on which unit or position, on which shift, and against which reference, in the shared log. Route follow-up Send each observation to the role that can review it and note it in the next coordination point. Worked example: Atlas trial build 2, shift 2 Fictional example. The record routes an observation for review; it does not rule on it. The observation On the second shift, an operator noted that the connector needed an extra reposition before seating on 4 of 20 units built. All four were at the same fixture position. Logged with unit positions, shift, and bracket B-214 Rev C as the reference. Written as what was seen, with no assumed cause. The routing The shift lead sent the entry to the design engineer and the quality engineer, since the pattern could relate to the fixture, the bracket or the connector. Both roles were named on the log line. Status: assigned, with the review point set for the next build debrief. What the team did not claim The record does not say the build passed or failed on this point. Engineering and quality decide what the pattern means and whether more units should be checked. The finding carries forward into the acceptance evidence index as an open review question. Adjacent coordination Check part readiness before the build Review the register of build-critical parts. Turn observations into evidence See how findings are indexed and reviewed. Acceptance Evidence Evidence is only useful if it can be traced Each piece of evidence should point back to the requirement or question it supports, say where it came from and at which revision, and show whether its owner has reviewed it. Having evidence collected does not mean it has been accepted. Collecting evidence is shared work; reviewing it belongs to the owner role named against each item. Sample evidence index Illustrative Atlas entries, not live data. Evidence topic Reference Owner role Review question Review state Connector seating observations Trial build 2 log, bracket B-214 Rev C Quality engineer Is the repositioning pattern linked to one fixture position? In review — next build debrief Fixture locating check Plant 2 fixture review, Rev C drawing Tooling role Does the fixture locate Rev C parts as drawn? Collected — review point to arrange Supplier delivery confirmation Readiness register, connector C-77 Sourcing lead Is the revised date consistent with build 3? In review — weekly supply call Build quantity and configuration Trial build 2 scope note Program role Did the build match the agreed scope? Reviewed — scope matched; conclusion in program review note Collected versus reviewed Show the state of each item Use three plain states in the index so a reader can tell at a glance what is waiting on whom. Collected: the evidence exists and is linked to its reference. In review: the owner role has it and a review point is set. Reviewed: the owner has recorded what they concluded and where. Route sensitive material to approved references Regulated, safety-critical or otherwise sensitive evidence follows the approved local procedure and is handled by trained roles. This index only points to it and records who owns the next review. Name the approved local reference instead of copying its content here. If you are unsure which procedure applies, ask quality before circulating the material. Where evidence comes from and goes Observations from a build See how trial-build learning is recorded and routed. Open items during launch Route unresolved evidence questions to the responsible function. Launch Support Route the issue to its function, with context If production meets an issue or an open readiness item during launch, send it to the function that can act on it and include four things: the product and revision, the plant and line, the shift, and the reference you were working to. Anything involving an immediate safety concern follows your site's approved escalation procedure first. This page covers coordination afterwards. Who picks up what Roles, not named people. Your site's help route lists who currently holds each role. Engineering change A drawing, tolerance or design-intent question. Goes to the design engineer for the product, with the revision and the feature affected. Material or supplier dependency A late, short or mismatched part. Goes to the sourcing lead or material planner with the part number and affected build. Production coordination A line, fixture or shift-handover question. Goes to the production engineer for the receiving line. Quality evidence A recurring observation or an evidence review question. Goes to the quality engineer with the log entry and reference. Write the request so it can be acted on Describe what you saw One or two sentences on the observation, without guessing the cause, for example: connector needs repositioning on 4 of 20 units at position 3. Link the reference Cite the drawing, log entry or register line with its revision. State the impact and the owner role Say what is blocked or at risk, and which role you are asking to take it. Agree how updates will be shared Name the forum or channel where the answer will be posted and who will post it. Authoritative pages for each topic Design handoffs Current references, changes and open questions. Supply readiness Parts, sources and receiving locations. Trial builds Build scope and observation routing. Acceptance evidence Evidence index and review state.