Home

Company

Project

SMT Line-Up

Smart Production Line

Reflow Oven

SMT Stencil Printing Machine

Pick & Place Machine

DIP Machine

PCB Handling Machine

Vision Inspection Equipment

PCB Depaneling Machine

SMT Cleaning Machine

PCB Protector

I.C.T Curing Oven

Traceability Equipment

Benchtop Robot

SMT Peripheral Equipments

Consumables

SMT Software Solution

SMT Marketing

Applications

Services & Support

Contact Us

English
Bahasa indonesia
Сербия
Česky
Dansk
Deutsch
Español
Français
Hrvatski
Italiano
magyar
Nederlands
Polski
Português
Pусский
românesc
Slovenščina
Suomalainen
Türk dili
Tiếng Việt
العربية
فارسی
עִברִית
한국어
日本語
News & Events
As a global intelligent equipment provider, I.C.T has continued to provide intelligent electronic equipment for global customers since 2012. 
You are here: Home » Our Company » Industry Insights » Greenfield vs Brownfield PCBA Factory Projects: What Changes in Planning and Integration?

Greenfield vs Brownfield PCBA Factory Projects: What Changes in Planning and Integration?

Publish Time: 2026-11-17     Origin: Site

Project planning guide · Published by I.C.T · For process engineers, plant planners and equipment buyers

The two project types are usually described by age: a new building versus an old one. That description is misleading, because the difficulty does not come from the age of the walls. It comes from one question that changes every plan downstream — does production keep running while the project is built? When the answer is no, schedule is a resource you can spend. When the answer is yes, every activity has to be argued for a slice of a window that already belongs to someone else. A greenfield vs brownfield PCBA factory project comparison that stops at "new versus existing" tends to miss the part where the brownfield project costs 30 percent more planning effort for the same equipment, and where the greenfield project costs more commissioning time because nothing exists to borrow from.

This guide works through the seven areas where the two diverge in practice: utilities, shutdown windows, legacy equipment compatibility, MES and traceability, material flow, validation, and the ramp-up plan. In each one the difference has the same underlying shape — a greenfield project starts from zero and pays in time and in the risk of an unproven assumption, while a brownfield project starts from something that already works and pays in coordination and in the cost of touching a live system. The line itself is the fixed block in both cases; how it is packaged is covered under the line builds used as the fixed block in both cases. Every figure in the worked examples is an assumption with a stated basis, not a measurement from any project, and none of it should be pasted into a plan without your own numbers behind it.

What actually differs: whether production keeps running

Every practical difference between the two project types traces back to one property: whether the plant is producing while the work happens. In a greenfield project the building is empty, so access is unlimited, work can proceed in any sequence, and a delay costs money but not output. In a brownfield project the building is full, so every activity competes for space, for power, for the attention of the same maintenance team, and above all for time in which the existing lines are stopped. That single constraint propagates into all seven areas below: it forces utilities to be measured rather than designed, it turns the schedule into a set of windows, it makes compatibility a test rather than a specification, and it makes validation a question of what can be reused. The greenfield vs brownfield PCBA factory project decision is therefore less about construction and more about how much coordination your organisation can absorb at once. Which of the two you are building is downstream of the process route — the process route that stays the same in either setting — but the route does not change the planning method that follows.

Area

Greenfield: the constraint is absence

Brownfield: the constraint is presence

Utilities

Sized from nameplates plus margin, built once

Measured against a live system with unknown spare capacity

Schedule

Continuous, sequence is yours to choose

A series of shutdown windows owned by production

Legacy equipment

None, so no compatibility question

Existing machines set the conveyor height, the protocol and the takt

MES

No system, so the data model is a design decision

Existing system, so the data model is a negotiation

Material flow

Designed from the process outward

Fitted into corridors, doors and columns that already exist

Validation

Everything proven for the first time

Some evidence reusable, some invalidated by the change

Ramp-up

One curve, from zero

Two curves that interact: the old line's output while the new one climbs

Greenfield and brownfield are not age categories

A twenty-year-old building with an empty hall is a greenfield project in every way that matters, and a building finished last year with two lines running is a brownfield project regardless of its age. What defines the type is the state of the constraint, not the date on the deed. This distinction is worth making early because it changes who owns the plan. In a greenfield project the plan is owned by the project team, and production is a future customer. In a brownfield project the plan is co-owned by production, because production controls the windows and can veto any activity that threatens a shipment. Projects that misclassify themselves tend to fail in a specific way: a greenfield project treated as brownfield produces an over-elaborate coordination plan and slow decisions, while a brownfield project treated as greenfield produces a schedule that assumes access it will never get, and then blames the plant for not granting it. Classify honestly at the start, because the classification determines who has to be in the room for every subsequent decision.

What each type hides well

Greenfield hides the cost of assumption. With no existing system to test against, every design decision stands unverified until commissioning, and the errors only surface when several of them interact — a floor loading that was fine per machine but not per loaded pallet, a duct sized per unit but not per header, a network drop count that forgot the inspection stations. The comfort of an empty building is that nothing contradicts you, which is also the danger. Brownfield hides the cost of dependency. Existing systems absorb small changes without complaint, so the plan looks easier than it is, until a change touches something shared — a compressed air header used by three lines, an MES server at capacity, a maintenance team already committed to another project in the same month. Neither type is more difficult in absolute terms; they hide different risks, and the plan has to be written to expose the one your project carries. That is a design choice about the plan, not a personality trait of the project manager, and it can be made deliberately by allocating review time to the risks the project does not naturally surface.

The hybrid case that is harder than either

The most demanding arrangement is not greenfield or brownfield but the mix: a new building, or a new bay, that will be filled partly with new equipment and partly with lines relocated from the existing plant. It combines the absence risk of greenfield with the presence constraint of brownfield, and adds a third problem — the relocated equipment has to be proven again in a new location, while the old location is being decommissioned on a schedule that the new location's readiness controls. Two rules make this survivable. First, relocate the line that is least critical to current output, so a slip in the new site does not stop a shipment. Second, treat the relocation as a re-commissioning rather than a move: the machine arrives with a history, but its utilities, its conveyor heights and its neighbours are all new, and the acceptance test has to be repeated on site rather than inherited from the previous installation. Plan the relocation as a small project of its own, with its own window and its own first article, rather than as a line item inside the larger build.

Which type you actually have

Four questions settle the classification in under an hour. Does any current output depend on the space or the services the project will use? Is there an existing MES, ERP or traceability system that the new equipment must talk to? Will any existing machine remain in the same production flow as the new equipment? And is there a customer or regulatory commitment that constrains when the plant may stop? Two or more yes answers means the project carries brownfield constraints, whatever the building's age. The value of asking is not the label; it is that each yes answer names an owner outside the project team, and those owners have to be in the plan from the first week rather than at the commissioning meeting. Projects that skip this step discover their type at the worst possible moment, usually when a shutdown request is refused by someone who was never part of the planning conversation, which is also the moment they discover that half the project was planned without them.

Utilities: sizing from zero versus sizing into what exists

Utilities are where the two project types diverge most sharply in method, and where the brownfield method is consistently underestimated. A greenfield project sizes utilities from the equipment list: add the connected loads, add a diversity factor, add a margin, build it. A brownfield project has to do something harder, which is to find out what the existing system can actually deliver before deciding what to add. Those are different skills and they take different amounts of time, and the brownfield version is frequently attempted with greenfield habits — the new machine's nameplate is added to a spreadsheet, the total is compared against the building's service rating, and the answer comes back comfortable. It is comfortable because the spreadsheet does not know that the compressor is at the end of its life, that the header is undersized for its current load, or that two of the three exhaust fans have never been balanced.

Greenfield: add the nameplates, then add the margin

The greenfield calculation is arithmetic plus judgement. Sum the connected electrical load, apply a diversity factor for machines that do not all draw maximum simultaneously, and add margin for the equipment you will buy in year three. Do the same for compressed air, where the figure to sum is consumption rather than pressure, and for exhaust, where the figure to sum is flow at each connection rather than the fan rating. The judgement part is the margin, and it should be stated as a policy rather than invented per project: a plant that adds 20 percent to air and 25 percent to exhaust has a rule it can defend, while a plant that adds "a bit" has a number it cannot explain. The published layout requirements for the equipment give the floor for each service — compressed air above 7 kg/cm², single-phase 220 V and three-phase 380 V within plus or minus 10 percent, exhaust at 500 cubic feet per minute or about 14.15 cubic meters per minute per connection, 800 to 1200 lux at the working plane, and 23 degrees plus or minus 3 at 45 to 70 percent humidity — and each of those is a minimum at the machine, not a sizing basis for the building.

Brownfield: measure, do not trust the nameplate

The brownfield method starts with measurement, and the measurement has to be taken under load at the point of use rather than read from a drawing. Three measurements matter most. Air pressure at the furthest existing drop while the plant is running, because a system that reads 7 kg/cm² at the receiver can read well below that at the end of the line. Available electrical capacity at the distribution board, which requires knowing what is actually connected and what is actually drawing, not what the panel schedule says. Exhaust flow at the nearest existing connection, measured at the flange, because duct runs accumulate losses that the fan curve does not show. Each measurement takes an hour and each one can change the project's scope by an order of magnitude — discovering that the header needs replacing is a different project from adding a branch to it. Do the measurement before the RFQ, not after the equipment order, and record who took each reading and with what instrument, so that the number can be defended when it becomes a purchase.

The margin question when the system is already loaded

In a greenfield project margin is a design choice; in a brownfield it is a negotiation with reality, because the existing system is already carrying a load you did not create. The useful way to frame it is headroom per service rather than margin per project. For each utility, record three numbers: the present load, the capacity, and the headroom as a percentage. Then decide, service by service, whether the new equipment fits in existing headroom, requires an upgrade, or requires a separate system. A separate exhaust run for a new through-hole section, for example, is often cheaper than upgrading a shared header, because it avoids rebalancing the whole network and avoids the argument about who pays for the upgrade. This is the kind of choice that has to be made on the drawing rather than on site, and it is why a through-hole section that has to fit an existing conveyor height is a different engineering problem from the same section installed in an empty hall, even though the equipment list is identical.

The shutdown window is the only schedule unit that matters

In a greenfield project the schedule is measured in weeks and the question is sequence. In a brownfield project the schedule is measured in windows and the question is whether the work fits. A window is a period when production has agreed to stop, and it is owned by whoever has to fill the orders — which means it is finite, negotiable only once, and expensive to extend. Windows come in three shapes: a weekend or holiday closure, a planned production gap created by a customer's own shutdown, and a genuine line stop negotiated against a finished-goods buffer. The planning error in most brownfield projects is not underestimating the work; it is estimating the work correctly and then failing to divide it into "must happen inside the window" and "can happen before or after". A window that is 100 percent full of required work is a window with no recovery allowance, and recovery allowances are what separate a project that finishes Sunday night from one that explains itself on Monday morning.

Activity inside the window

Assumed duration

Can it move outside?

Decommission and remove the old line

8 hours

No, but removal can start the evening before

Floor preparation, drilling and cable penetrations

12 hours

Partly, if the area is already isolated

Position, level and anchor the new machines

10 hours

No

Electrical, air and network connection

16 hours

Pre-built leads and pre-labelled cables cut this by hours

Single-machine commissioning and recipe load

20 hours

Yes, if the machines are commissioned off-line first

Line linking, first article and trial run

12 hours

No

Total as a naive plan

78 hours

Against a 72-hour weekend window, 6 hours over

Where the window comes from, and what it really costs

Windows are produced by three things: the production calendar, the customer base, and the finished-goods buffer. The production calendar gives you the predictable ones — weekends, public holidays, the week between Christmas and New Year in many markets. The customer base gives you the ones you can negotiate, usually by aligning the change with a customer's own maintenance shutdown, which turns your window into a shared benefit rather than a request. The buffer gives you the ones you can buy: if the plant holds enough finished goods to cover demand for five working days, a weekend window can extend into the following week without a shipment being missed, at the cost of carrying that stock. That cost is real and should be calculated before the window is requested, because it is the number that decides whether a longer window is worth buying. A plant that has never calculated it usually negotiates the shortest possible window and then pays for it in recovery work at double time.

What fits inside it, counted in hours

The table above is an assumption set for a single-line replacement, and its purpose is to show the shape of the arithmetic rather than the numbers themselves. The naive total is 78 hours against a 72-hour window, which is a six-hour overrun before anything goes wrong. That overrun is not a scheduling detail; it is the difference between a Monday restart and a Monday explanation, because the last two activities — line linking and first article — are the ones that cannot be compressed and the ones whose duration is most uncertain. Two moves fix it. First, move single-machine commissioning outside the window by commissioning the machines in an isolated area of the hall before the shutdown, which is possible for any machine that can be powered and fed independently. Second, pre-build and pre-label every cable and air drop so that connection time becomes terminating rather than fabricating, which typically removes several hours from the sixteen assumed. Both moves cost preparation time, and preparation time is available in a brownfield project in a way that window time is not.

Moving work outside the window

The discipline is to classify every activity three ways: inside the window, before the window, and after the window. Inside goes anything that physically requires the space or the connection. Before goes fabrication, pre-assembly, cable making, program creation, recipe development and single-machine commissioning in an isolated area. After goes optimization, documentation updates, training refreshers and the second product's recipe. A project that classifies honestly usually finds that the window can be reduced by a third without touching the critical activities. Part of the preparation is choosing equipment that supports this pattern, which is one reason a staged installation is easier with a semi-automatic SMD line that can be staged before the window: machines that can be run and proven standing alone reduce the number of activities that depend on the shutdown, and every activity removed from the window is risk removed from the restart. The same table then becomes the agenda for the pre-shutdown review, with each row owned by a named person and each before-window item closed before the plant stops.

The window that closes badly

Plan the exit as carefully as the entry, because the last hours of a window are where projects lose their gains. Three items belong in the exit plan. A rollback position: the state to which the area can be returned if the new line cannot produce a first article by the deadline, including where the old line's output would come from. A first-article definition agreed before the shutdown, so that "it runs" is not the acceptance criterion at two in the morning. And a named decision-maker with the authority to extend the window or to accept a staged restart, available by phone for the whole period. Projects without these three tend to make their worst decisions at the point of maximum fatigue, and the decisions they make are usually to keep going rather than to stop, which is how a six-hour overrun becomes a three-day outage, and how a project that was technically finished on Sunday is remembered as the one that missed the quarter.

Legacy equipment: compatibility is a data problem first

The compatibility question in a brownfield project is usually framed as engineering — will the new machine's conveyor match the old one's height, will the SMEMA handshake work, will the old oven accept the new recipe. Those are real questions, and they are the easy ones, because they can be answered from drawings. The harder compatibility problem is data: what the existing machines know, what they can report, and what the new equipment expects to receive. A line that runs perfectly well as a physical flow can be impossible to integrate as a data flow, and that gap is discovered late because nobody owns it. The practical approach is to treat every existing machine as a black box with three properties to establish before the project is scoped: its mechanical interface, its electrical and control interface, and its data interface.

Three kinds of compatibility, in order of discovery

Mechanical compatibility is the first and the most visible: conveyor height and width, board edge clearance, the direction of flow, the position of the load and unload stations, and whether a machine can be moved without dismantling the corridor. Electrical and control compatibility comes second: voltage and phase, the handshake protocol between machines, whether the existing line uses a central control or independent controllers, and how the safety circuit is wired between units. Data compatibility comes third and is the one most often left out of the scope: which parameters each machine can export, in what format and over what protocol, and whether a machine built before networked reporting existed can be queried at all. Answer the three in that order but budget for them in reverse, because the data layer is where the surprises are and where a workaround costs the most, usually as an unplanned purchase of a gateway, a licence or a small integration project nobody budgeted for.

Line balancing when the old machine is slower

The most common brownfield arithmetic is a new machine that is faster than everything around it. Assume, as an illustration, an existing line whose placement stage runs at 12,000 components per hour and a new placement platform rated at 28,000 under the same conditions. Placing the new machine in the same flow does not raise the line's output to 28,000; it raises it to whatever the constraint allows, which is the old stage at 12,000 before any efficiency loss. If the new machine's effective rate after utilization losses is around 24,000, the line runs at the old rate and the new capacity is absorbed as idle time. The fix is rarely a new machine — it is a change of role: let the new platform carry the high-count product and the old one carry the low-count or low-volume work, so each runs near its own constraint instead of sharing one. That decision is a product-allocation decision, not an equipment decision, and it should be made before the order rather than after the installation.

Spares, software and the lifecycle question

Mixing old and new equipment creates a lifecycle problem that a greenfield project never faces. Three aspects matter. Spares: an existing machine's spare parts may already be at end of life, so the new project should record, for every retained machine, which parts are still available and which would require a retrofit if they failed. Software: an existing controller may run a firmware version that the new equipment cannot communicate with, and upgrading it may break something else on the line. Support: the retained machines may be out of the original supplier's support window, which means the new project inherits a maintenance risk it did not create and cannot resolve by buying anything. The practical output of this section is a one-page table listing every retained machine with three columns — parts availability, software version, support status — and a decision for each: retain as is, retain with a planned retrofit, or replace. That table is also the honest basis for choosing a semi-automatic SMT line commissioned off-line then moved in, since a line that can be proven independently is easier to slot beside ageing equipment whose behaviour is not fully documented.

MES and traceability: extending versus starting

MES and traceability are the area where the two project types are least alike and most often planned as if they were the same. A greenfield project has no system, which sounds like freedom but is actually a demand: you must decide what to record, at what granularity, retained for how long, before any data exists. A brownfield project has a system, which sounds like a head start but is actually a constraint: every new machine has to be expressed in terms the existing system already understands, and the terms it understands may have been decided years ago by someone who has left. Both projects fail in the same place, which is the interface between the machine and the system, and both fail for the same reason — the interface is specified as hardware ("MES-ready", "Ethernet port") rather than as a data deliverable ("this parameter, in this unit, visible in this screen").

The greenfield trap: system before data model

The greenfield error is to buy or configure a system and then ask what it should collect. That order produces a database with fields that nobody uses and a shop floor that reports what is easy rather than what matters. The correct order is the reverse: define the decisions the data must support, then the measurements those decisions need, then the retention and the granularity, and only then the system. Three decisions drive almost all of it. Are you tracing units or panels, because that sets the identifier granularity and the marking requirement. Are you tracing process parameters or only pass and fail, because that sets the data volume by an order of magnitude. And how long must records be retained, because that decides whether the system needs archival rather than only storage. A greenfield project that answers those three before selecting software spends less and gets a system people use; one that selects first spends more and gets a system people work around.

The brownfield trap: two data dictionaries

The brownfield error is assuming that "integrate with the existing MES" is a single task. It is at least three: mapping the new machine's parameters to the existing system's dictionary, reconciling units and naming where the two do not match, and deciding what to do where the existing system has no field at all. The second and third are where projects stall. An existing system built around panels may have no concept of a unit-level identifier, so a new machine capable of unit traceability has nowhere to put its data. A naming convention that grew by accretion may call the same measurement two different things on two lines, so a report that spans both lines is wrong before it is written. The practical move is to produce a mapping table before the equipment order: one row per parameter, with the source, the target field, the unit, the frequency and a status of mapped, needs new field, or not required. That table is the deliverable, and it is cheap compared with discovering the gaps during commissioning.

The identifier nobody owns

Traceability depends on an identifier, and the identifier is usually the least-owned element in the project. Four decisions sit behind it: what is marked (panel, unit or both), where on the board it goes, what symbology or format is used, and who defines it — the plant, the customer or a regulatory scheme. In a greenfield project all four are open, which invites a decision by default: the marking machine's easiest format. In a brownfield project the format already exists, which invites a different default: whatever the old line does. Both defaults are wrong when the plant serves several customers with different requirements, because the identifier has to survive the customer's own systems and their own audits. Write the four decisions into the project before the marking equipment is specified, and check them against the customers who actually audit you, not against the ones who do not, and revisit the decision when a new customer's audit finds a format your line cannot produce.

Writing an acceptance test that means something

The acceptance test for this area is not "the interface works". It is a small number of observable facts, each verified in the consuming system rather than at the machine. Four are usually enough: a specified parameter appears in the system within a stated interval of the event; a traceability query on a known identifier returns the correct route and timestamps; a deliberately induced failure produces the expected alarm record; and a report that spans the new and the existing equipment returns consistent totals. Each of those is testable in an hour, and each one fails in a way that a port check would have passed. Write them into the scope with the same weight as a mechanical acceptance criterion, because a line that produces but cannot be traced is not a finished line in a plant that has customers with quality agreements. Repeat the same four tests after any later change to the line, since an interface proven once is only proven for that configuration.

Logistics and material flow in a building you did not design

Material flow is the area where a greenfield project has an unearned advantage, and where brownfield projects most often accept a permanent compromise. When the building is empty you design the flow from the process outward: receiving, storage, kitting, line side, finished goods, dispatch, in that order, with the corridors placed to serve them. When the building already has walls, columns, a loading dock in the wrong place and a corridor that doubles as a walkway, the flow has to be fitted into constraints that were decided for a different product mix. The cost of fitting badly is not dramatic; it is a permanent tax of a few minutes per movement, multiplied by every movement, every shift, for the life of the plant. That is why the flow deserves a drawing before the equipment layout is fixed, even when the equipment has already been ordered.

Travel distance and work-in-process

Two numbers make the flow argument objective. The first is travel distance per shift: the sum of all movements of material, calculated from the layout rather than estimated from memory. A plant with a receiving dock at one end and a line at the other pays for that distance on every reel, every stencil and every finished pallet. The second is work-in-process, and it can be calculated rather than felt. Assume a changeover of 30 minutes at a takt of 60 seconds: the buffer needed to keep the line running through the changeover is 30 boards, and if the buffer position is three corridors away, those boards also cost travel. The useful discipline is to draw the flow for the worst product rather than the average one, because the worst product is what the layout has to survive, and to mark on the drawing every point where two flows cross — material and people, or new material and returned material. Crossings are where congestion and errors live.

Receiving, storage and the feeder wall

Brownfield projects inherit storage, and storage is usually the first thing to be squeezed when space is short. The consequence appears at the line rather than in the store: feeders stored far away lengthen changeover, reels stored without a location system cause line stops, and stencils stored flat in a corridor get damaged. A feeder wall near the line, indexed and counted, is worth more than an equivalent area of general shelving, and it is the single cheapest flow improvement in most existing plants. The same logic applies to receiving: a dock that cannot accept a full pallet forces double handling on every delivery, which is invisible in a capacity calculation and obvious on the floor. Both items belong in the requirement package both project types still need, because a supplier cannot design a layout around a store whose contents and movement nobody has written down. A store that has never been counted cannot be planned around, and the count is a half-day task that pays for itself during the first changeover.

People, pallets and the one-way rule

The last flow question is the one that gets least attention until an audit: how people and material share the same floor. A single rule covers most of it — where possible, people and material move in one direction and do not share a corridor. In a greenfield project this is a drawing decision; in a brownfield project it is often impossible to achieve fully, and the compromise has to be managed rather than ignored. Mark the crossings, define who has priority, and put a physical barrier where a barrier is possible. The safety consequence is obvious, but the productivity consequence matters too: a corridor shared between a forklift route and a walking route slows both, and the slowdown is never booked against anything. Existing plants that measure this usually find the largest single improvement available is not a machine but a redrawn route with one crossing removed. That improvement costs a morning of tape on the floor and one conversation with the shift supervisor, and it appears in no capital request.

Validation and ramp-up: what you reuse and what you re-prove

Validation is where the brownfield project has a genuine advantage, and it is the advantage most often thrown away. An existing plant has evidence: process capability studies on similar products, first-article approvals, calibration history, operator qualifications, audit results. Some of that evidence survives a change and some does not, and the difference is not the equipment — it is whether the variable that the evidence depended on has changed. A capability study taken on the same machine, same product, same materials and same people in a new building is not automatically valid, because the building changed. A study taken on a different machine in the same building is also not valid, because the machine changed. The useful question is therefore not "greenfield or brownfield" but "which variable moved", and that question makes the reuse decision specific instead of optimistic.

Evidence

Reusable in a brownfield extension?

Reusable in a greenfield build?

Equipment acceptance records

Yes, for retained machines; no for new ones

No, all new

Process capability on an unchanged product

Only if machine, materials, people and environment are unchanged

No, nothing to inherit

Programs and recipes

Yes as a starting point, re-verified on the new position

Built from the product definition

Operator qualification

Partly: familiarity carries, certification does not

No, trained from zero

Calibration and MSA records

Yes for retained instruments, re-done for new ones

No

Customer approvals

Frequently void after a process or site change

Required before first shipment

Audit history and certifications

Carries, but the scope of the certificate may need extending

New certification cycle

Evidence you can carry over

Three categories of evidence usually survive a brownfield change. Documentation of retained equipment survives as a starting point: manuals, schematics, calibration records and the original acceptance data remain useful even if the machine has moved, because they describe the asset. Product and process knowledge survives in the form of programs, recipes and the people who wrote them, provided those people are still there and provided the programs are re-verified at the new position. And the quality system survives: procedures, work instructions, control plans and audit history belong to the plant rather than to the line, and they do not restart because a machine arrived. The discipline is to list what you intend to carry over, name who confirmed it is still valid, and record the confirmation. Evidence carried over without confirmation is not evidence; it is an assumption wearing a document's clothes. The confirmation itself is cheap: a signature, a date and one sentence saying that nothing on the list has changed since the evidence was produced.

What has to be proven again

Four things almost always have to be proven again, and each one has a reason. Capability on a changed process: any change to machine, material, method, measurement or environment invalidates the previous study, and in a brownfield extension at least one of those has usually changed. Safety: a new machine beside an old one creates a new hazard boundary, and the safety validation covers the combined system rather than the new unit. Traceability: the identifier and the data path have to be proven end to end in the new configuration, because the pieces are individually proven and the chain is not. And customer approval, where the customer's own rules require notification of a process or site change — which many do, and which is frequently discovered after the first shipment rather than before it. Plan these four as a sequence with dates, not as a list of activities to be done "during commissioning", and write them into the scope boundary that has to name the shutdown clause before the contract is signed, because a validation plan that exists only as a project schedule tends not to survive the first commercial negotiation.

A ramp-up curve with assumptions

Ramp-up is where the greenfield and brownfield curves differ most visibly. A greenfield plant starts from zero output and a team that has never run the line, so the curve is steep at the beginning and slow at the end. A brownfield extension starts with an experienced team and an existing product, so the new line can often reach a higher share of nominal output sooner — but it also has to share people, maintenance and quality resources with the running plant, which is why the curve can plateau in an unexpected place. Take an illustrative case, all figures assumed: a new line reaching 40 percent of nominal in week one, 60 in week two, 75 in three and 85 by week four, with the remaining gap closed over the following two months. Against a plan that assumes 85 percent from week one, the shortfall over four weeks is roughly 120 percent of one week's nominal output — a number worth knowing before the sales commitments are made. The curve should be written into the project plan with the assumption behind each point, and with the trigger that moves the plan if a point is missed twice.

Decide which type you are before you decide the schedule

If you are planning a PCBA factory project, the first useful step is not a quotation but a classification, because the classification decides what the plan has to contain. Answer the four questions in the first section — does current output depend on the space, is there an existing system, will an existing machine share the flow, and is there a commitment that limits stopping — and the project type follows. If two or more answers are yes, the plan needs windows, owners from outside the project team, a measured utility survey and a reuse table for validation evidence. If all are no, the plan needs a data model, a margin policy and a commissioning sequence with more time than you think. Send us the classification, the window you can realistically obtain and the list of machines that will remain in the flow, and we will tell you which of the seven areas is likely to become your critical path, where the interface between old and new equipment needs a test rather than a drawing, and what has to be finished before the first shutdown rather than during it. A greenfield vs brownfield PCBA factory project differs least in the equipment and most in the plan, and the plan is what we would rather argue about on paper than on the Monday morning after a window closes.

Frequently asked questions

Is a brownfield project always more expensive than a greenfield one?

Not in capital terms, and often the reverse — a brownfield extension reuses the building, the utilities, the people and part of the equipment, so the capital number is usually smaller for the same capacity. It is more expensive in planning effort and in coordination cost, because the work has to fit around production and every activity needs an owner outside the project team. The honest comparison puts the two numbers side by side: lower capital and higher coordination for brownfield, higher capital and higher commissioning risk for greenfield. Projects that compare only capital tend to choose brownfield for the wrong reason and then under-resource the planning.

How long a shutdown window should we ask for?

Ask for the window that fits the activities that genuinely cannot happen outside it, plus a recovery allowance, and no more. Build a table of every activity with an assumed duration and classify each as inside, before or after the window. In most single-line replacements the honest number is between 60 and 80 percent of the naive total, because commissioning, program loading and cable fabrication can usually move outside. Then buy the recovery allowance deliberately — with stock, with overtime, or with a longer window — rather than discovering it at two in the morning on the last night.

Can we keep the old line running next to the new one during commissioning?

Often yes, and it is the single best way to avoid a large shutdown, provided three conditions hold: the new line can be powered and fed independently, the two lines do not share a utility header that would be disturbed, and the building has the physical space to keep both in operation without blocking access. Running both in parallel converts a hard stop into a soft one, because the old line keeps shipping while the new one is proven. The cost is floor space and time, and the risk is that the parallel period gets extended indefinitely because nobody sets the date on which the old line stops.

What is the first thing to check on legacy equipment?

The data interface, before the mechanical one. Mechanical questions can be answered from drawings and corrected with an adapter; data questions often cannot be answered at all until someone connects to the machine, and the answer may be that it exports nothing useful. Establish, for each retained machine, which parameters can be read, in what format and over what protocol. If a machine can only report pass or fail, no amount of MES configuration will produce process data from it, and that constraint has to be known before the traceability scope is written rather than after.

Do we need to re-qualify the product if we move an existing line into a new building?

Treat it as yes until a documented analysis says otherwise. Moving a line changes at least the environment and often the utilities and the people, and any of those can invalidate a capability study even when the machine, the product and the materials are identical. The efficient path is not to redo everything but to identify which variable moved and re-prove only that: a capability study on the moved line for the highest-risk product, a first-article approval, and a traceability check end to end. Where the customer requires notification of a site change, that notification is a schedule item rather than a formality, because approval can take longer than the move.

How do we stop the ramp-up from being an argument?

Write the curve into the plan before the first board runs, with an assumption stated for each point and a defined action if a point is missed twice. A curve that says 40, 60, 75 and 85 percent over four weeks is a commitment that can be checked weekly; a plan that says "full production after commissioning" is an argument waiting to happen. Include the trigger for each action — additional training, a second shift, a supplier visit — and agree who decides. The curve also protects the sales side, because it makes the output available in month one an explicit number rather than an optimistic one.

What single document should a brownfield project produce first?

A one-page classification and constraint sheet: the four classification questions with their answers, the list of retained machines with their parts, software and support status, the shutdown windows that are realistically available with the basis for each, and the measured utility headroom per service. That page is enough to tell a supplier, a contractor and an internal steering committee what kind of project they are looking at, and it prevents the most expensive brownfield error — planning a live-plant project as if the plant were empty. It takes about a week to produce honestly and it changes almost every later decision.

Get a Quick Quote

Copyright © Dongguan ICT  Technology Co.,Ltd.