Skip to content
Blog

The project profile in plant engineering: what goes in it, with a template.

A project profile sums up on one page what everyone in the project needs to know: order, plant, deadlines, contacts and special points. What goes in it, where the details come from and how it stays current.

Yanik YeganehfarCo-Founder & COO5 min read
Quick answer

A project profile sums up on one page what everyone in the project needs to know. The order and customer, the key technical data of the plant, deadlines and milestones, contacts on both sides and the special points nobody should miss. Every entry should point to its source in the customer specification or order confirmation.

Contents
  1. What is a project profile?
  2. What goes into a project profile?
  3. What does a template look like?
  4. Where do the details come from?
  5. How does the profile stay current?
  6. How does KoAssist help with the project profile?

An electrical design engineer joins a project three weeks after the kick-off because a colleague has fallen ill. He is sent a link to the project folder. It holds 140 files, among them an 86-page customer specification in two revisions, the quotation, the order confirmation, minutes and a folder called "Customer incoming". In the end it is the project manager who tells him on the phone what protection rating the control cabinet needs. The specification says IP54, an email from the quotation phase says IP65.

A project profile would have saved him that half hour, as long as it said which value applies and where it comes from.

What is a project profile?

A project profile sums up on one or two pages what everyone in the project needs to know. It replaces neither the customer specification nor the functional specification. It is the entry point that tells you where to read further.

In machine and plant engineering it is usually written after the order comes in and presented at the kick-off. After that it serves three groups: people who are new to the project, departments that only deal with the project now and then, and the project manager, when switching between many projects.

How the customer specification and the functional specification relate to each other is explained in a separate article on the two documents.

What goes into a project profile?

Order. Customer, order number, date of the order confirmation, scope of supply in one sentence, contractual basis (customer specification with revision, quotation with date).

Plant. The key technical data that apply to everyone: output or cycle time, product variants, dimensions and installation site, interfaces to the existing plant, protection rating, controls, the standards and directives that are required.

Deadlines. Design release, FAT, delivery, installation, SAT, acceptance. Add the dates by which the customer has to supply something, such as the layout approval or sample parts.

Contacts. On the customer side and internally, each with their role. Who at the customer decides on changes?

Special points. What is different in this project from the usual. A penalty for late delivery, an unusual interface, a requirement from the customer's plant standard, a known risk from the quotation phase.

Open questions. Whatever has not been settled when the profile is written, with a reference to the open issues list.

What does a template look like?

Area Item Value Source
Order Customer Muster Antriebstechnik GmbH, Linz plant Order confirmation AB-2417
Order Scope of supply Assembly line for gearbox covers, 3 variants, incl. safety enclosure Quotation of 2 September, items 1–4
Plant Cycle time 18 s per part Customer specification rev. B, p. 12
Plant Control cabinet protection rating IP65 (specification says IP54, changed) Customer email, 14 September
Plant Controls Siemens S7-1500 to the customer's plant standard Customer specification rev. B, p. 31
Deadlines FAT CW 8 Order confirmation AB-2417
Deadlines Acceptance CW 12, on site Order confirmation AB-2417
Contacts Decides on changes Head of maintenance, customer Kick-off minutes
Special point Contract penalty 0.5% per week of delay, max. 5% Contract, § 7
Open Changeover time between variants not specified, asked of the customer Open issues list, no. 4

The source column is the part most templates leave out. Yet it is what makes the profile reliable. Anyone who doubts a detail can look it up instead of calling the project manager.

Where do the details come from?

Almost everything is already in the documents from the quotation and order phase: the customer specification, the quotation, the order confirmation, the contract and the emails from the clarification. The work lies in finding the details and spotting contradictions, like the protection rating in the example.

How to go through a customer specification systematically for this is described in the article on analysing customer specifications. For structuring the requirements themselves, a requirements list in design engineering helps.

How does the profile stay current?

A profile that is only correct at the kick-off is no longer read after four weeks. Three habits help.

Update changes straight away. When a customer change comes in, adjust the affected row and enter the new source. How to keep customer changes traceable across the whole project is covered in the article on customer changes in plant engineering.

Keep old values visible. "IP65 (specification says IP54, changed)" stops anyone from working to the specification later on.

One place, one link. The profile sits in a fixed place and is shared as a link, not sent around as an attachment.

How does KoAssist help with the project profile?

Project Memory, part of KoAssist, the AI agent for machine and plant builders, builds the profile from your documents. You upload the customer specification or connect the project folder from SharePoint, OneDrive or Google Drive. KoAssist fills in the details, each backed by a reference to the passage in the document. Whatever is missing or contradictory goes on a list of questions for the customer.

While the project runs, KoAssist reads new documents and relevant emails and proposes changes to the profile. A proposal only becomes valid once someone on the team accepts it. Project Memory is currently in pilot operation with existing customers.

If you would like to see what a profile built from your own customer specification looks like, you can book a demo.

Written by

Yanik Yeganehfar

Co-Founder & COO

On LinkedIn ↗

Frequently asked questions

Yanik Yeganehfar, co-founder of KoAssist

Find out with Yanik whether KoAssist fits your projects.

Request a demo