From concept to commercial release — with quality built in at every gate.

Decide whether and why to build, and frame the regulatory and quality strategy before any money is committed to design.

• Build the business case, capacity model, and target-market analysis
• Frame the regulatory strategy and applicable frameworks per market
• Set the make-vs-buy and technology/modality direction
• Define the high-level quality criteria the project will be judged against

• Executive sponsor and corporate development
• Regulatory affairs and the quality unit
• Technical operations and engineering leadership

• Regulatory-strategy input and the first quality criteria
• A veto on modality/market choices that cannot be qualified or inspected

• Feasibility of the technology and capacity concept
• Rough order-of-magnitude cost and schedule for the technical scope

• The demand, capacity, and reliability assumptions the case rests on
• Input on operability of the proposed modality

• Go/no-go on funding the next phase
• Target markets, modality, and make-vs-buy

• Business case & project charter
• Regulatory strategy memo
• Quality project plan (first issue)

• The approved business case and charter
• The regulatory strategy of record

• A modality or market chosen without regulatory input
• Optimistic capacity/demand assumptions never revisited

• An approved business case with a defined product, capacity, and target markets
• A first regulatory strategy naming the applicable frameworks and markets
• Quality represented in the decision, not consulted after it

• Regulatory strategy — deciding markets late forces redesign
• Quality involvement — its absence here is the costliest gap of all

The single highest-leverage phase: a modality or market choice made without quality in the room can make the whole asset expensive or impossible to qualify.

Greenfield frames a whole facility and site; brownfield frames a change to a licensed operation, so the case must weigh disruption to current supply.

Define the basis of design and the delivery model so design proceeds against agreed requirements rather than discovering them.

• Develop the basis of design from the business case — capacity, product mix, and the quality target the facility must meet
• Draft the first user-requirements outline and the regulatory expectations design must satisfy
• Set the contracting and delivery model (design-bid-build, EPCM, integrated, or modular) and the vendor-documentation requirements
• Produce a class-appropriate cost and schedule range with the quality and verification scope included, not bolted on

• Project sponsor, project director, and front-end/FEL engineering lead
• Quality unit and regulatory affairs shaping the requirements basis
• Procurement and contracts defining the delivery and vendor model

• The regulatory and quality requirements the basis of design is built to
• Confirmation that the contracting model keeps vendor documentation usable as verification evidence

• The basis of design and the technical assumptions behind the cost/schedule range
• Constructability and delivery-model feasibility for the technical scope

• Operability, maintainability, and capacity inputs to the basis of design
• The throughput and staffing assumptions the schedule rests on

• Approval of the basis of design and the funding class it supports
• The contracting and delivery model, and the risk allocation it carries

• Basis-of-design document
• User-requirements outline (first issue)
• Class cost estimate and project execution plan
• Contracting/procurement strategy

• The approved basis of design and execution plan
• The requirements outline of record and its regulatory basis

• A basis of design frozen before quality has shaped the requirements
• A low-bid contracting model that omits documentation, FAT, and access rights
• Cost and schedule ranges that quietly exclude the C&Q and validation scope

• A basis-of-design document and initial user-requirements outline
• A contracting/delivery model that keeps vendor documentation usable for verification
• A defensible cost and schedule range with the quality scope included

• Requirements definition — a requirement found in construction is the costliest change a project makes
• Documentation and FAT rights in the contract — impossible to add back once the deal is signed

Front-end loading is where cost and schedule certainty are bought cheaply; requirements found late are the most expensive change a project makes.

A greenfield basis of design starts from the process and market; a brownfield one starts from the constraints of the existing facility and must protect its validated state and supply while the project is delivered.

Choose a location that can be built, staffed, supplied, and inspected for the intended product and markets.

• Assess candidate sites against regulatory jurisdiction, utilities, infrastructure, workforce, and supply chain
• Determine which authority inspects the site and what its regime demands for the intended markets
• Evaluate environmental, zoning, hazardous-material, and expansion constraints
• Run the feasibility and due-diligence study that supports the site recommendation

• Project sponsor, site-selection lead, and real-estate/engineering advisors
• Regulatory affairs and quality assessing the jurisdiction and inspection regime
• Supply-chain, EHS, and HR assessing logistics, permitting, and workforce

• Judgement on whether the jurisdiction’s regulatory and inspection regime is acceptable for the target markets
• Whether the site can support the required cleanroom classifications and utility qualities

• Utility, infrastructure, and constructability assessment of each candidate site
• The technical feasibility of achieving the required classifications on the site

• Workforce availability, logistics, and supply-chain feasibility for routine operation
• Operating-cost and reliability assumptions tied to the location

• Selection of the site and the acceptance of its regulatory and infrastructure profile
• Property acquisition or lease commitment

• Site-selection assessment and recommendation
• Regulatory-jurisdiction and inspection-regime analysis
• Feasibility/due-diligence report

• The site-selection decision record and its basis
• The jurisdiction and inspection-regime analysis of record

• A site chosen for land or labour cost with an unassessed regulatory penalty
• Utilities or infrastructure that cannot reach the required qualities
• Workforce or supply-chain gaps that surface only after the commitment

• A site that supports the required classifications, utilities, and expansion
• The jurisdiction’s regulatory and inspection regime understood and acceptable
• Supply-chain and workforce feasibility confirmed

• Regulatory-jurisdiction assessment — it determines who inspects and how, and cannot be changed after acquisition
• Utility and infrastructure feasibility — a shortfall found later forces costly off-site solutions

A site chosen for cost alone can carry a regulatory or infrastructure penalty that outlasts the saving — the jurisdiction determines which authority inspects and how.

Site selection is a full phase for greenfield; on a brownfield project the site is a given, so the work becomes assessing whether the existing location and its licence can absorb the new scope.

Turn user requirements into a design concept whose critical aspects are identified by quality risk before detail locks in.

• Finalise the user-requirements specification (URS) as the design’s controlling document
• Develop process flows, room and pressure-cascade schemes, material and personnel flows, and major-equipment concepts
• Run the initial quality-risk assessment to identify critical aspects and critical quality attributes (ASTM E2500 / ICH Q9 thinking)
• Establish the contamination-control strategy concept and the classification scheme

• Process, facility, and automation design engineers
• Quality and the SMEs owning the critical-aspects risk assessment
• Operations providing flow, ergonomics, and operability input

• Approval of the URS and the risk-based identification of critical aspects
• The contamination-control strategy concept and the acceptability of the flow/segregation scheme

• The concept and basic design — process flows, layouts, and major-equipment selection
• Translation of the URS into a technically coherent design concept

• Operability, material and personnel flow, and maintainability review of the concept
• The staffing and throughput model the layout must serve

• Approval of the concept/basic design and the capital it commits
• Trade-offs between capital cost and the flexibility or compliance margin of the design

• Approved user-requirements specification
• Concept / basic design package (flows, layouts, classification scheme)
• Initial quality-risk assessment and critical-aspects register

• The approved URS and its revision history
• The critical-aspects risk assessment that scopes later verification

• Flow and segregation decisions that permanently cap contamination control
• Critical aspects not identified early, so verification is later mis-scoped
• A URS that is vague or unmaintained, breaking downstream traceability

• An approved user-requirements specification (URS)
• Concept/basic design with process, flow, and classification schemes
• Initial quality-risk assessment identifying critical aspects (ASTM E2500 thinking)

• Flow, segregation, and classification decisions — fixed at concept and unaffordable to reverse later
• Critical-aspects identification — its absence mis-scopes every downstream qualification

Concept decisions on flows and segregation set the contamination-control ceiling for the life of the facility; they cannot be cheaply undone later.

Greenfield concept design has full freedom over flows and classification; a brownfield concept must fit new flows into an existing shell and prove they do not compromise the segregation the facility already relies on.

Complete and verify the design against the URS so that what is built is what qualification will be able to accept.

• Produce functional specifications and detailed design (P&IDs, layouts, equipment/automation specifications)
• Hold formal design reviews and perform design qualification (DQ) confirming the design meets the URS
• Trace critical design elements back to the critical aspects identified at concept
• Freeze the design and place it under change control before construction commits

• Detailed-design engineering and specialist discipline engineers
• Quality performing/approving the design qualification and design reviews
• Operations and maintenance reviewing the detailed design for use

• The design-qualification decision — that the design satisfies the URS and its critical aspects
• Approval to freeze the design and the change control that governs it afterwards

• The complete, coordinated detailed design and its specifications
• Resolution of design-review comments and closure of the DQ actions

• Confirmation the detailed design is operable and maintainable as drawn
• Sign-off on ergonomics, access, and maintenance provisions

• Approval of the frozen design and release for construction/procurement
• Any value-engineering changes and the re-verification they trigger

• Functional and detailed design specifications
• Design-review records and the design-qualification report
• Design traceability from URS → critical aspects → design elements

• The approved design-qualification record
• The design-basis documents and the traceability that supports qualification

• A design frozen without design qualification, exporting gaps downstream
• Critical design elements not traced to critical aspects, so verification misses them
• Uncontrolled late design changes that break the as-designed baseline

• Functional and detailed design specifications complete
• Design review and design qualification records against the URS
• Critical design elements traced to the critical aspects from concept

• Design qualification — a gap left in the design surfaces in C&Q at an order-of-magnitude cost
• Design freeze and change control — without them, construction chases a moving target

A design frozen without design qualification exports its gaps into construction and C&Q, where they cost an order of magnitude more to fix.

Brownfield detailed design adds tie-in design and shutdown planning against live systems, and every design element is assessed for its impact on the existing validated state — a constraint greenfield does not carry.

Procure and fabricate equipment to specification, capturing the vendor evidence C&Q will reuse instead of repeating.

• Issue purchase specifications traced to the detailed design and URS
• Qualify suppliers and embed quality, documentation, and FAT requirements in the contract
• Oversee fabrication and witness factory acceptance testing (FAT) of major equipment and systems
• Assemble the vendor turnover documentation package that commissioning and qualification will leverage

• Procurement, contracts, and vendor-management engineering
• Supplier-quality and the SMEs witnessing FAT
• Automation/CSV engineers for computerised and control systems (GAMP 5)

• Supplier qualification and the quality/documentation requirements in the purchase order
• Acceptance of the FAT evidence as leverageable for qualification

• Purchase specifications, FAT protocols, and fabrication oversight
• The technical acceptance of the fabricated equipment against specification

• Input on operability and maintainability of the specified equipment
• Spare-parts and maintenance-documentation requirements

• Vendor and equipment award decisions
• Acceptance of long-lead commitments and their schedule risk

• Purchase specifications and qualified-supplier records
• Executed FAT protocols and reports
• Vendor documentation / turnover packages

• FAT protocols and results used to support qualification
• Supplier qualification and material/build documentation

• A low equipment bid that omits documentation and FAT rights, forcing re-test in C&Q
• FAT run informally, so its evidence cannot be leveraged
• Vendor computerised systems delivered without GAMP-appropriate documentation

• Purchase specifications traced to the design and URS
• Supplier quality qualified and quality/documentation requirements in the contract
• Factory acceptance tests (FAT) executed with usable, complete documentation

• Documentation and FAT rights in the contract — unrecoverable once the order is placed
• Supplier qualification — an unqualified supplier surfaces as rework and inspection risk later

A contract that omits documentation and FAT rights forces C&Q to re-test from scratch — the classic hidden cost of a low equipment bid.

Greenfield procures a whole plant at once; brownfield procurement is smaller but must ensure new equipment is compatible with existing utilities and can be tied in without disrupting live production.

Build and install to the design under GEP, generating the installation record installation qualification will rely on.

• Construct the facility, utilities, and equipment to the approved design under Good Engineering Practice
• Capture installation, weld, material, and passivation documentation contemporaneously
• Manage field changes through construction change control and reflect them in as-built records
• Perform GEP inspections and progressively build the installation-verification evidence

• Construction management, contractors, and site engineering
• Quality/CQV oversight of GEP and documentation practices
• Commissioning team beginning system walkdowns and punch listing

• Confirmation that field changes are controlled and the as-built record stays trustworthy
• The standard the installation documentation must meet to support installation qualification

• Construction to the design under Good Engineering Practice
• The completeness and accuracy of installation, weld, and material records

• Early familiarisation and input on installed access and maintainability
• Identification of operability issues while they are still cheap to fix

• Approval of field changes and their impact on cost, schedule, and design intent
• Acceptance of construction progress against the completion plan

• As-built drawings and installation records
• Weld/material/passivation and GEP documentation
• Construction change-control log

• The as-built record and installation documentation supporting IQ
• Weld and material certifications for product-contact and utility systems

• Undocumented field changes that break the as-built record
• Installation documentation captured too late or incompletely to leverage
• GEP not applied, so systems must be re-worked before they can be qualified

• Construction to the approved design under Good Engineering Practice
• Installation, weld, and material documentation captured contemporaneously
• Field changes controlled and reflected in as-built records

• Contemporaneous installation documentation — impossible to reconstruct faithfully once trades leave
• Field-change control — undocumented changes become qualification and inspection findings

Undocumented field changes break the as-built record and surface as qualification findings and inspection risk long after the trades have left.

Brownfield construction happens inside a live, licensed facility: tie-ins, shutdowns, and contamination controls must protect adjacent production, and every change is assessed against the existing validated state — greenfield builds on an empty site.

Formally hand systems from construction to commissioning with a complete, verified turnover package.

• Confirm mechanical completion of each system against the design and P&IDs
• Assemble and verify system turnover packages (drawings, records, certifications)
• Walk down systems, raise and categorise punch-list items, and manage them to closure
• Formally transfer care, custody, and control from construction to commissioning

• Construction and commissioning leads executing the handover
• Quality/CQV confirming documentation completeness for later verification
• System owners accepting custody for commissioning

• Confirmation that the documentation trail is intact across the handover
• The completeness standard a turnover package must meet before commissioning starts

• Verification of mechanical completion against the design
• Assembly and technical acceptance of the turnover packages

• Early acceptance walkdowns and input on punch-list priorities
• Readiness to receive systems for operation downstream

• Acceptance of mechanical completion and authorisation to begin commissioning
• Disposition of open punch items and their impact on the commissioning start

• Mechanical-completion certificates
• System turnover packages
• Punch lists and their disposition records

• Accepted turnover packages and mechanical-completion records
• The punch-list closure trail

• A sloppy turnover that breaks the documentation trail
• Incomplete packages that force commissioning to reconstruct evidence
• Punch items deferred into commissioning and then lost

• Mechanical completion confirmed against the design
• Turnover packages complete and accepted, with punch lists managed
• Documentation trail intact through the construction→commissioning handover

• Turnover-package completeness — reconstructing it later burns the commissioning schedule
• Punch-list discipline — deferred items resurface as qualification findings

A sloppy turnover is where the documentation trail breaks; commissioning then spends its float reconstructing evidence instead of testing systems.

On brownfield work the turnover also has to confirm that tie-ins to existing systems are complete and that adjacent live operations were not disturbed — a handover dimension greenfield does not face.

Bring systems into working order and demonstrate they meet engineering requirements, producing leverageable evidence.

• Set to work, adjust, and functionally test systems against engineering requirements
• Confirm each system’s impact classification (direct / indirect / no impact) to scope qualification
• Document commissioning results to a standard qualification can leverage under ASTM E2500
• Resolve commissioning deficiencies and hand direct-impact systems forward to qualification

• Commissioning engineers and system SMEs
• Automation/CSV engineers for computerised systems (GAMP 5)
• Quality providing oversight and confirming the leverage approach

• Agreement that commissioning evidence is generated to a leverageable standard
• Confirmation of system impact classification that scopes formal qualification

• Execution of commissioning and the functional performance of each system
• The commissioning documentation that becomes verification evidence

• Early operation of systems and feedback on real operability
• Operator familiarisation ahead of qualification and start-up

• Acceptance of commissioning completion and readiness to qualify
• Resourcing of deficiency closure against the schedule

• Commissioning plan and executed test records
• System impact-classification register
• Commissioning deficiency/punch list and closure

• Commissioning records leveraged into qualification
• The impact-classification rationale that scoped qualification

• Informal commissioning whose evidence cannot be leveraged, forcing re-test
• Impact classification done loosely, so qualification is mis-scoped
• Deficiencies carried unclosed into qualification

• Systems commissioned and functioning to engineering requirements
• Commissioning evidence documented to a standard qualification can leverage
• System classification (direct/indirect impact) confirmed for qualification scoping

• Leverageable commissioning documentation — informal evidence is repeated under qualification rigor
• Impact classification — getting it wrong either over-qualifies or leaves a gap an inspector finds

Commissioning done to a leverageable standard shrinks qualification; done informally, it is repeated under qualification rigor at far higher cost.

Brownfield commissioning must protect adjacent live systems while setting new ones to work, and shared-utility tie-ins are commissioned without disturbing the running operation — greenfield commissions an empty plant.

Verify and document that direct-impact systems are fit for their intended GMP use, and release them for use.

• Author and approve qualification protocols (IQ/OQ/PQ) with pre-defined acceptance criteria
• Execute installation, operational, and performance qualification against those criteria
• Investigate and resolve deviations, then compile qualification summary reports
• Make the acceptance-and-release decision for GMP use (EU GMP Annex 15)

• Qualification/validation engineers and system SMEs
• Quality Assurance approving protocols, deviations, and release
• Automation/CSV for computerised-system qualification (GAMP 5)

• Approval of qualification protocols, deviations, and acceptance criteria
• The system release / acceptance-and-release decision that permits GMP use

• Execution of IQ/OQ/PQ and generation of the qualification evidence
• Technical resolution of qualification deviations

• Participation in performance qualification under representative conditions
• Confirmation that the qualified system is operable for routine use

• Acceptance of qualification completion and residual risk
• Prioritisation of deviation closure against the start-up date

• Approved IQ/OQ/PQ protocols and reports
• Deviation records and their resolution
• System release / qualification summary

• Executed qualification protocols and summary reports
• The release decision and its supporting acceptance-criteria results

• Acceptance criteria set after results are seen, undermining the qualification
• Deviations closed without genuine resolution
• Leverage of commissioning evidence not justified, weakening the qualification

• Approved qualification protocols with pre-defined acceptance criteria
• IQ/OQ/PQ executed, deviations resolved, results meet criteria
• System release / acceptance-and-release decision by quality

• Pre-defined acceptance criteria — criteria written to fit results are an inspection finding
• Deviation resolution — an unresolved qualification deviation blocks release and slips start-up

The gate that permits GMP use; a weak qualification is the finding an inspector pulls first and the reason a start-up date slips.

Brownfield qualification is scoped by change impact against the existing validated state — often a focused requalification — whereas greenfield qualifies every direct-impact system from scratch.

Demonstrate the manufacturing process is reproducible and in a state of control on the qualified asset.

• Carry Stage 1 process design knowledge into a Stage 2 process validation plan
• Execute process performance qualification (PPQ) batches against pre-defined criteria
• Validate computerised systems (GAMP 5) and establish cleaning and environmental-monitoring baselines
• Compile the PPQ report and confirm the process is in a state of control

• Process/validation engineers and manufacturing science (MSAT)
• Quality Assurance approving the plan, batches, and PPQ report
• QC laboratory, CSV, and cleaning-validation SMEs

• Approval of the process validation plan, PPQ protocol, and acceptance criteria
• The disposition of PPQ batches and the state-of-control conclusion

• Equipment and utility performance supporting the validated process
• Support to resolve process/equipment issues arising in PPQ

• Execution of the PPQ batches under routine, representative conditions
• The trained operators and procedures the validated process depends on

• Commitment of API/material and schedule to the PPQ campaign
• Acceptance of PPQ outcomes and authorisation toward commercial supply

• Process validation plan and PPQ protocol
• Executed PPQ batch records and the PPQ summary report
• CSV, cleaning-validation, and monitoring baseline records

• The approved PPQ protocol and summary report
• Cleaning-validation and monitoring baselines that anchor Stage 3

• PPQ run before Stage 1 knowledge is adequate, risking a failed campaign
• Cleaning or monitoring baselines set too thin to support routine limits
• CSV not complete, so data supporting PPQ is not trustworthy

• A process validation plan carrying Stage 1 knowledge into Stage 2
• PPQ batches executed and meeting pre-defined criteria
• CSV, cleaning validation, and monitoring baselines established

• Stage 1 process understanding — thin design knowledge shows up as a failed, costly PPQ campaign
• Cleaning and monitoring baselines — retrofitting them delays commercial release

PPQ is the gate to commercial supply; a process not shown to be in control cannot lawfully ship, and a failed PPQ campaign is a direct schedule and cost hit.

A technology transfer or brownfield line may run a confirmatory PPQ leveraging the sending site’s knowledge; a greenfield process is validated from first principles on a brand-new asset.

Make the organisation ready to operate the asset in a state of control from the first commercial batch.

• Author and approve the SOPs the asset runs on and train/qualify personnel to them
• Bring the deviation, CAPA, and change-control systems live on the new asset
• Confirm materials, supply chain, warehousing, and maintenance/calibration readiness
• Run an operational readiness review against a defined checklist before start-up

• Operations, quality, and the site training function
• Supply chain, warehousing, and maintenance/engineering
• Quality systems owners (deviation/CAPA/change control)

• Approval of SOPs and confirmation personnel are trained and qualified
• That the quality system (deviation/CAPA/change control) is live on the asset

• Maintenance, calibration, and spare-parts readiness for the asset
• Handover of engineering documentation into the maintenance system

• Staffing, shift structure, and operator qualification for routine running
• Material flow, warehousing, and the day-one production plan

• The operational readiness go/no-go for start-up
• Resourcing of any readiness gaps before the first commercial batch

• Approved SOPs and completed training/qualification records
• Operational readiness review and gap register
• Live quality-system configuration for the asset

• Training and personnel-qualification records
• The operational readiness review and its go/no-go decision

• A qualified asset with SOPs or trained staff not ready, stalling start-up
• Quality system not truly live, so early deviations are mishandled
• Supply-chain or maintenance gaps that surface in the first weeks

• SOPs approved and personnel trained and qualified for their tasks
• Deviation, CAPA, and change control live on the new asset
• Materials, supply chain, and maintenance readiness confirmed

• Training and SOP readiness — gaps become first-batch deviations and lost start-up time
• A live quality system — mishandled early deviations are a shaky first-inspection signal

A qualified asset with an unready organisation stalls at start-up; readiness gaps show up as early deviations and a shaky first inspection.

Greenfield stands up a whole new organisation and quality system; brownfield extends the existing site’s trained workforce and live quality system onto the new asset, so readiness is incremental rather than wholesale.

Assemble the regulatory evidence and prepare the site so the market authorisation and inspection succeed.

• Draw submission-supporting documentation from the project’s qualification and validation deliverables
• Run an inspection-readiness assessment and a mock inspection, closing gaps via CAPA
• Confirm the data integrity (ALCOA+) of every record an inspector could pull
• Prepare front-room/back-room logistics and brief the teams for a pre-approval/pre-license inspection

• Regulatory affairs and the site quality unit
• Project, validation, and QC SMEs supporting the evidence
• Site leadership and the inspection host/back-room teams

• Confirmation of data integrity across every inspectable record
• Ownership of the inspection-readiness assessment and CAPA closure

• Retrieval and completeness of qualification and engineering records for inspection
• Facility and utility documentation an inspector may request

• Readiness of the floor, operators, and batch records for observation
• Execution discipline that survives real-time inspection scrutiny

• Declaration of inspection readiness and submission timing
• Resourcing of remediation for readiness findings before the inspection

• Submission-supporting documentation set
• Inspection-readiness assessment and mock-inspection report
• Data-integrity assurance record for inspectable systems

• The inspection-readiness assessment and its CAPA closure
• The data-integrity assurance evidence for the site’s records

• A record an inspector pulls that cannot be produced or is not attributable
• Mock-inspection findings closed on paper but not in reality
• Submission claims not fully supported by retained project evidence

• Submission-supporting documentation drawn from project deliverables
• Inspection-readiness assessment and mock inspection completed
• Data integrity of every record an inspector could pull confirmed

• Data-integrity assurance — a broken record found in inspection delays launch and revenue
• Inspection-readiness remediation — findings surfacing live are far costlier than in a mock

The gate to market entry; an inspection finding here delays launch and revenue and can trigger costly re-work of records already produced.

A greenfield site faces its first-ever inspection with no track record; a brownfield site is already licensed, so readiness focuses on the new scope and its impact on the existing inspection standing.

Bring the asset into routine commercial production and reach target rate, yield, and reliability.

• Produce and release commercial batches while ramping toward target rate
• Trend early-production deviations and drive them down through CAPA
• Stabilise yield, reliability, and cycle time as volume rises
• Watch the process closely and feed learnings into continued verification

• Operations and manufacturing leadership running the ramp
• Quality releasing batches and governing early deviations
• MSAT/process engineering supporting stabilisation

• Batch disposition and release during the ramp
• Governance of the early-production deviation and CAPA load

• Equipment reliability and the maintenance response as volume climbs
• Resolution of equipment-driven yield and downtime issues

• Achieving target rate, yield, and reliability against plan
• Working down the early-production deviation backlog on the floor

• Ramp rate versus stability trade-offs
• When to declare the asset at steady-state routine operation

• Released commercial batches and their records
• Early-production trend and deviation-closure data
• Ramp performance vs plan (rate, yield, reliability)

• Batch and release records from the ramp
• Deviation trends demonstrating the process settling into control

• A slow, deviation-heavy ramp that defers revenue and strains supply
• Chronic yield or reliability shortfalls not root-caused
• Ramp pressure eroding the discipline the qualification established

• Commercial batches produced and released
• Early-production deviations trended and worked down
• Yield, reliability, and rate approaching plan

• Deviation root-causing during ramp — unresolved early issues become chronic losses
• Reliability stabilisation — a shaky ramp strains the supply commitments the project promised

Where the investment finally earns; a slow, deviation-heavy ramp defers revenue and can strain the supply commitments the project was justified on.

A greenfield ramp starts from zero on an unproven organisation; a brownfield ramp adds volume to an operation already running, so the risk is disruption to existing supply rather than first-time start-up.

Transition from project oversight to routine continued process verification and lifecycle management.

• Stand up the Stage 3 continued process verification (CPV) plan and its monitoring
• Trend CQAs and CPPs statistically and respond to out-of-trend signals
• Establish periodic product review and requalification/maintenance cycles
• Hand ongoing lifecycle management from the project to the site organisation

• Site quality, MSAT, and manufacturing owning the running process
• QC and data-analytics resources running the trending
• Engineering owning periodic requalification and calibration

• The CPV plan, its signals, and the response to out-of-trend results
• Periodic review governance that keeps the state of control demonstrable

• Periodic requalification, calibration, and preventive-maintenance cycles
• Reliability and drift management of equipment and utilities

• Routine execution feeding the monitoring data
• Acting on trend signals before they become deviations

• Formal handover of the asset from project to operations
• Resourcing of ongoing monitoring, review, and improvement

• Continued process verification (Stage 3) plan and data
• Periodic review and trending records
• Lifecycle-management handover record

• CPV data demonstrating the sustained state of control
• Periodic review conclusions and any resulting actions

• Monitoring allowed to lapse after project close, so drift goes unseen
• Trend signals recorded but not acted on
• No clear owner once the project team disbands

• Continued process verification (Stage 3) plan live and generating data
• Periodic review and trending established
• Ongoing monitoring detects drift before it becomes deviation

• A live CPV plan — a monitoring gap is how a well-built asset drifts toward recall or shortage
• Clear operational ownership — an ownerless asset loses its state of control quietly

Sustains the state of control the project delivered; letting monitoring lapse is how a well-built asset drifts into the shortage or recall statistics.

CPV is largely archetype-independent — greenfield and brownfield assets alike settle into the same Stage 3 lifecycle, differing mainly in how much prior process history informs the trending limits.

Formally close the project, confirm benefits, archive the record, and capture lessons for the next project.

• Close all remaining project quality actions and punch-list items
• Archive project documentation so it is indexed and retrievable for the asset’s life
• Assess benefits realised against the business case and record variances
• Capture lessons learned and transfer residual risks and actions to operations

• Project director and project management office
• Quality confirming action closure and records archival
• Operations receiving the asset, its risks, and its records

• Confirmation that all project quality actions and punch items are closed
• That the documentation is archived, retrievable, and complete for its retention period

• Handover of as-built and engineering records into the site systems
• Closure of engineering punch items and open technical actions

• Acceptance of the asset, its residual risks, and its open actions
• Ownership of anything carried forward from the project into routine running

• Formal project close-out and benefits sign-off
• Disposition of any unrealised benefits or carried-forward risks

• Project close-out report
• Documentation archival and retrievability record
• Lessons-learned register and benefits-realisation summary

• The signed close-out report and benefits assessment
• The archival index proving records remain retrievable

• A project never formally closed, leaving open quality actions adrift
• Records archived but not retrievable when an inspection later needs them
• Lessons never captured, so the next project repeats the cost

• All project quality actions and punch items closed
• Documentation archived, indexed, and retrievable for the asset’s life
• Benefits realised against the business case and lessons captured

• Records archival and retrievability — an unretrievable record is a future inspection gap
• Lessons capture — an un-mined lesson is a cost the next project pays to relearn

Closes the loop: a project never formally closed leaves open quality actions and an un-mined lesson that the next project pays to relearn.

A greenfield close-out hands over a whole new asset and organisation; a brownfield close-out folds the change back into the existing operation and updates its validated-state and licence records accordingly.