Process engineering

From process basis to an integrated production line

A controlled engineering workflow that connects requirements, process design, equipment duties, interfaces, acceptance evidence and plant integration.

01Start with the design basis02Own every interface03Write acceptance before procurement
Integrated commercial production line connecting multiple unit operations
Illustrative process system, not a customer installation or project design.
Direct answer

An integrated production line is not created by placing individually suitable machines in sequence. It is created by converting the product and process objectives into a controlled design basis, defining every unit-operation duty, assigning every interface, and carrying those requirements through FAT, site integration and performance acceptance.

7controlled engineering gatesFrom requirements to site acceptance
1live interface registerMechanical, process, utility, control and safety ownership
20 Jan 2027EU Machinery Regulation appliesCompliance planning belongs in the design basis
01

Build a deliverable ladder, not a stack of disconnected documents

Each engineering document should answer a different question and pass controlled information to the next decision.

ISO 10628 provides internationally recognised principles for diagrams used in chemical and petrochemical process industries. The value of a BFD or PFD is not aesthetic: it establishes a common process model from which duties, interfaces and test evidence can be traced.

  1. 01 · Requirements

    Product, feed, capacity, quality, operating mode and site constraints

  2. 02 · Design basis

    Assumptions, balances, utilities, control philosophy and acceptance boundaries

  3. 03 · Process route

    BFD / PFD, recycle logic, emissions and critical unit operations

  4. 04 · Equipment duties

    Function, material properties, turndown, containment and cleanability

  5. 05 · Integration

    Layout, piping, utilities, controls, access, maintenance and safety interfaces

  6. 06 · FAT

    Document, fabrication, functional and agreed material-trial evidence

  7. 07 · SAT & performance

    Installed functionality, product performance and controlled close-out

Sources: S1

02

Control the interfaces that no equipment data sheet owns

Many line-level failures occur between technically acceptable packages.

Minimum interface register
InterfaceQuestions to closeAcceptance evidence
Material transferFlow regime, segregation, bridging, dust, temperature and hold-upTransfer trial, inspection and clean-out evidence
UtilitiesLoad, quality, pressure, diversity, peaks and failure behaviorConsumption schedule and functional test
ControlsSignals, permissives, interlocks, alarm ownership and recipe handoverI/O test and cause-and-effect record
MechanicalLoads, nozzles, access, lifting, maintenance and thermal movementInterface drawing and installation check
Quality & cleaningResidue limits, cross-contamination, drainage and inspection accessCleaning protocol and verification method
SafetyHazards, zones, isolation, guarding, pressure relief and emergency stateRisk assessment and safety-function test
03

Integrate compliance while the line is still changeable

Compliance is a design input, not a document package added after fabrication.

Regulation (EU) 2023/1230 on machinery applies from 20 January 2027. For equipment intended for potentially explosive atmospheres, the ATEX framework may also govern equipment and protective systems. Applicability depends on the machine, material, atmosphere, installation and destination market.

Risk architecture

Define machine boundaries, intended use, foreseeable misuse and interfaces between assemblies.

Material hazards

Assess dust explosibility, chemical compatibility, thermal decomposition and occupational exposure.

Documentation

Keep declarations, manuals, safety functions and technical evidence aligned with the delivered configuration.

Change control

Reassess compliance when throughput, product, layout, controls or package boundaries change.

Sources: S2 · S3

04

Keep one requirements-and-deviation thread through every phase

A production line changes during design; uncontrolled change is what breaks traceability.

The design basis should identify assumptions that still require confirmation. When a supplier proposes a different material, nozzle arrangement, utility condition or control sequence, the change needs an owner, technical disposition and impact review across process performance, safety, schedule, cost and acceptance.

The same register should survive package award. Closing a comment in a drawing is not enough if the affected requirement, interface, test or operating document remains unchanged.

Controlled change record
FieldRequired contentDownstream control
OriginRequirement, design review, supplier deviation, site discovery or test resultPreserves why the change exists
Technical impactProcess, mechanical, electrical, control, safety, quality and maintenance effectsPrevents local optimisation from moving risk elsewhere
Commercial impactPrice, schedule, warranty, performance and scope boundaryAvoids silent transfer of responsibility
DocumentsDrawings, calculations, lists, manuals and test protocols affectedKeeps the delivered baseline coherent
ClosureApprover, evidence, date and residual actionCreates an auditable handover
05

Write the acceptance logic before issuing purchase orders

A test is useful only when feed, duration, method, tolerance and consequence are defined.

Evidence chain
GateTypical evidenceDecision
Design reviewApproved basis, calculations, drawings and deviation registerAuthorized manufacturing release within the agreed scope; remaining holds recorded
Fabrication reviewMaterial certificates, weld / finish records and inspectionConforms to approved design
FATFunctional sequence, instruments, interlocks and agreed duty simulationAgreed factory tests passed; shipment still requires release of relevant holds
SATInstallation, utilities, I/O and site-function evidenceAgreed site tests passed; commissioning requires separate readiness authorization
Performance runDefined feed, steady state, sampling, analysis and balanceMeets contracted process outcome
06

Follow one requirement from the process basis to test evidence

A document list is not a closed engineering requirement. The requirement needs an owner, a testable criterion and an accepted result.

Consider an illustrative transfer interlock: the upstream feed must stop when the downstream receiver is unavailable. The process owner defines the intended response and relevant operating states; the package suppliers agree signal ownership, fail state and reset authority; the controls design implements the sequence; FAT checks the agreed simulated conditions; SAT checks the actual installed interface. This example is not a completed safety function or a customer-approved design.

EQM requirement-to-evidence chain
FieldMinimum recordClosure check
RequirementUnique ID, controlled source revision and testable acceptance criterionThe parties are testing the same requirement
ImplementationDrawing / logic revision, package boundary and responsible designerThe installed configuration matches the reviewed implementation
VerificationProtocol, prerequisites, actual result, deviations and evidence locationA reviewer can reproduce the conclusion from the evidence
ReleaseAuthorized approver, scope of acceptance, remaining holds and retest triggersThe record states exactly what may happen next
07

Make open holds usable at handover

A punch list should tell the receiving team what is blocked and how to unblock it—not merely how many items remain.

Identify the consequence

Link each hold to the affected equipment, requirement and next activity. Separate a documentation correction from an unresolved functional or safety issue.

Name the closure evidence

Record the responsible party, due date or dependency, required evidence and reviewer. A supplier acknowledgement alone does not close a failed test.

Authorize the next stage

Record the exact release scope and remaining restrictions. Where the design or installation changes, assess which previous tests must be repeated.

Where production performance still depends on scale-up evidence, use the pilot-to-design decision gate.

Evidence and sources

  1. S1
    ISO 10628-1: Diagrams for the chemical and petrochemical industry ↗

    International Organization for Standardization · 2014

  2. S2
  3. S3

Numerical values are presented with their regulatory or study context. Study conditions are not represented as universal commercial setpoints. EQM engineering frameworks are identified separately from cited external facts.

Frequently asked questions

Can EQM integrate equipment from different suppliers?

Yes, provided package boundaries, duties, interfaces, control ownership, documentation and acceptance evidence are explicitly managed.

Is FAT the final proof of process performance?

Usually not. FAT verifies agreed factory-level scope. Full process performance may require defined material, site utilities and sustained operation, which belong in a separate performance protocol.

Does a successful FAT mean the complete line is accepted?

No. FAT addresses the agreed factory test scope. Shipment release, site installation checks, commissioning readiness and contractual performance acceptance require their own evidence and authorized decisions. Record any remaining holds explicitly.