Industry & ProjectEngineering

Home / Engineering partners

Defined engineering packages within your project team

Bring IPE into your project for a defined engineering package, a discipline scope or an agreed team extension. We work within the model environment, standards and document-control requirements agreed with your lead team, with clear interfaces and review milestones.

Engagement models

Three ways to engage IPE

Whichever model you choose, the proposal fixes the scope, the deliverables list, the issue milestones and how changes and acceptance are handled.

Work package

A defined deliverable with a fixed scope and issue dates – for example piping layout and isometrics, pipe stress analysis, steel structures, electrical and control design, or a laser scan and as-built model.

Discipline scope

One discipline for a whole project, from basic to detail design, coordinated with your lead engineer and your other contributors through agreed interfaces.

Agreed team extension

Engineers working in your project environment for an agreed period and scope, for peaks in your workload. Names, roles and the period are set out in the proposal.

Inputs, outputs and interfaces

Your standards, model environment and drawing templates

We deliver to your project's conventions. The table shows what we need from your lead team and what we return at each step.

StepFrom your lead teamFrom IPE
ScopeScope and battery limits, schedule, available design documentsWritten proposal: deliverables list, exclusions, issue milestones, assumptions
Set-upModel environment (for example an AVEVA E3D or PDMS project with your catalogues and specifications), standards, numbering, drawing templates and title blocksSet-up check and a deliverables register in your numbering
DesignDesign inputs from your lead disciplines, vendor data, answers to technical queriesDesign within the agreed interfaces; a list of open interface items kept up to date
Review and issueReview comments at the agreed milestonesInternal check by a second engineer before each issue; controlled revisions under your revision rules
ChangesChange requestsThe effect on scope and dates stated and agreed with you before change work starts
HandoverAcceptance criteria agreed in the proposalFinal issue, native model and drawing files and the document register, as agreed

Local standards such as GOST, SNiP or DSTU are applied where your client specifies them. Drawings made under a partner's title block remain the partner's documents and are not published as IPE's work. Confidentiality, intellectual property, design rights and end-client contact are defined in each proposal.

Tools

Software we work in

DisciplineSoftware
ProcessAspen Plus simulation; piping and instrumentation diagrams (P&IDs)
Plant layout and pipingAVEVA E3D and PDMS, CADWorx
Pipe stressCAESAR II
Civil and steel structuresRevit, Advance Steel, SCIA
Electrical and controlELCAD
Existing plantsPoint clouds from 3D laser scans, Navisworks model review

Quality and handover

  • EN ISO 9001:2015 quality management, SGS, certificate SK07/0134
  • Every document checked by a second engineer before issue
  • Engineers authorised by the Slovak Chamber of Civil Engineers, with authorisation also from the Czech chamber
  • Documents in English, Slovak, Czech and Russian; project meetings in English
  • Office in Michalovce, Slovakia, on Central European Time; site visits and designer's supervision where agreed

Partner examples

Packages delivered within other engineering teams

Contracting party, plant location and IPE's package are shown separately.

Contracting partyEnd client and plant locationYearsIPE packageWorking environment
Contiplus Limited, Malta; Xylo Engineering CZ, Czech RepublicResin and glue plants, Kaluga and Ufa, Russia2021–2022P&IDs, mechanical detail design, civil design; 45 P&IDs, 1,312 pipelines, 2,853 valves, 199 equipment itemsBilingual English–Russian documents; civil drawings to GOST
TechniCAD Engineering, SwitzerlandNestlé, Konolfingen, Switzerland: extension of the fermentation unit2020–2021Detail design and 3D model; 188 pipelines, 458 valves, 4 equipment itemsDelivered in TechniCAD's title blocks; TechniCAD was the contracting route to the end client
JPS, SlovakiaU. S. Steel Košice: coke-oven gas desulphurisation – dephlegmator and coal-water stripper2018–2019Laser scan, 3D model of the existing plant, detail design, pipe stress analysis (CAESAR II)3D model built on the laser scan
TechniCAD Engineering, SwitzerlandPEG2MAL pharmaceutical project, Belgium2012–2013Piping and HVAC designPDMS
Energyco, SlovakiaCORUS, IJmuiden, the Netherlands: continuous galvanising line DVL32007–2008Detail design and PDMS model; 1,005 pipelines, 298 valves, 237 equipment itemsPDMS model delivered to Energyco
Grontmij | Carl Bro, DenmarkWintergas LPG carrier (2007) and cooling-station modules for a multigas LNG/LPG carrier (2008), Denmark2007–2008Detail design of steel structures and pipingPDMS model
Koch-Glitsch Italia, ItalyKuibyshevazot, Togliatti, Russia: revamp of a cyclohexanone rectification unit2012–2013Basic designPDMS model
PDMS model of green and white process piping, tanks and platforms of a galvanising line
IPE's PDMS model of piping on galvanising line DVL3, CORUS IJmuiden, prepared for Energyco, 2007–2008.
PDMS model of a compressor-house module of a gas carrier, with coloured suction and process lines on its roof
IPE's PDMS model of the compressor-house module of the Multigas carrier, for Grontmij | Carl Bro, Denmark, 2008: steel structure and piping.

Other engineering firms and licensors we have delivered packages for include ABB Lummus Global, KG Process Innovations, Biochemtex, OT Industries, Technip, and JPS, ProIng and AMT Servis for U. S. Steel Košice. Full reference list

Bar chart of ten engineering packages from IPE's reference list, with separate bars for pipelines, valves and equipment items, each on its own scale; the resin and glue plants package shows 1,312 pipelines and 2,853 valves
Examples of engineering package scale: pipelines, valves and equipment items in ten packages from IPE's reference list. Each count uses its own scale; a dash means the value was not recorded, not zero. The figures describe past packages, not current capacity.

Discuss an engineering package

What we need to scope a package

The discipline and scope; your model and tool environment; the standards and interfaces; the issue dates; your confidentiality requirements.