IEC 61406
Unique, machine-readable ID marking
Provided twice: as a QR code on the nameplate and as an RFID/NFC tag.
For suppliers to the process industry
IEC 61406, VDI 2770, AASX: your customer is asking for the digital twin.
We deliver it.
For suppliers and component manufacturers in the process industry that have received a digital twin requirements letter from a major customer – without having to start an IT project of their own.
IDTA member since 2021 Member of the Digital Data Chain Consortium (DDCC) >10 years of experience in the process industry
Sound familiar?
Four points that appear in almost every one of these letters.
If you recognise this, you are in the right place. We have met exactly these requirements several times.
VDI 2770
Structured manufacturer documentation
Handover Documentation in the structure the operator requires.
AASX
Digital twin as an Asset Administration Shell (AAS)
For types and instances, accessible via the AAS API.
IDTA 02006 · 02003 · 02004
Specific submodels
Digital Nameplate, Technical Data, Handover Documentation – that is the stable basis. We add further submodels where they make sense, for example Product Carbon Footprint.
Not sure whether you already meet this? Email us the letter and have it reviewed →
Why now
Two deadlines are running in parallel.
Your major customer
Deadlines set by your customer
Every plant operator sets its own date from which it expects the data – it is stated in your letter. Anyone unable to deliver by then risks losing the order, regardless of EU regulation.
EU regulation
Mandatory from February 2027
Start now and you secure implementation free of charge within the promotional period (order by 31 Dec 2026) and stay one step ahead of the regulation.
The solution
From an Excel file to a compliant digital twin.
The DPP platform meets all four requirements in your customer’s letter – from the data you already have today. You supply a file or give us access to your systems; the platform does the rest.
What you supply
- Excel or other file formats
- ERP SAP, Navision, others
- MES / database CSV, XML, SQL
- PDF documents manuals, certificates
The platform
Codewerk DPP Platform
Turns your data into the Asset Administration Shell, holds the documents and provides the ID link – as a portal your customer opens directly, under your own brand. Operated by Codewerk, with no installation at your end.
-
IEC 61406
ID link as a QR code and RFID/NFC tag.
-
VDI 2770
Manufacturer documentation in the required structure.
-
AASX
Asset Administration Shell for type and instance, accessible via the AAS API.
-
IDTA submodels
Digital Nameplate, Technical Data, Handover Documentation.
Free test account, no installation. Operated and maintained by Codewerk.
Your systems stay as they are
No replacement, no rebuild of your IT, no prior AAS knowledge required. You choose how much we take on: tools & support, integration by Codewerk or DPP as a Service.
Example · valve manufacturer
One simple, human-readable exchange file per order is enough, and it can cover several valves. The manufacturer drops the file and documents in place, the platform detects them automatically and generates the Asset Administration Shell from them – with no development of its own.
How it works
Three phases – tailored to the answer you give your customer.
Phase 1
Concept phase
Workshop, clarification of the requirements in your customer’s letter, AAS structure design, sample Asset Administration Shell.
Duration approx. 3–6 weeks
Phase 2
Implementation
Integration of your data sources, automated AAS generation, portal configuration.
Duration approx. 2 months
Phase 3
Test & go-live
Functional test, integration of existing devices, import test at the customer.
Total duration 3–5 months from start to go-live
The offer
Fixed scope, fixed price.
Every phase has a fixed scope and a fixed cost envelope. You decide after each phase whether to continue.
01 · Concept phase
Fixed price, clear deliverable
Requirements clarification, workshop, AAS modelling, technical blueprint.
02 · Implementation
No implementation cost
within the promotional period
Implementation, integration, go-live; up to 2 systems (CSV/XML/SQL).
Promotional period: order by 31 Dec 2026
03 · Hosting
Monthly operation from go-live
Operation including maintenance and updates, with a fixed minimum term.
We give you the figures for all three phases in conversation. Request a quote
Common objections
What suppliers tell us in these conversations.
Answer · DPP platform
One file is enough. Any format, for example per instance or per batch – the DPP platform builds the Asset Administration Shell from it.
Answer · DPP platform
Templates take that off your hands. Pre-filled for exactly the submodels your customer requires: 02006, 02003, 02004.
Answer · DPP platform
A finished submodel isn’t required. We advise on how your data can be represented in a compliant way.
Answer · DPP platform
You don’t have to. Thanks to the template approach, adapting to new standards or submodels is quick and straightforward.
References & trust
Two suppliers that already have this behind them.
Live · publicly accessible
Michael Koch GmbH
Digital nameplate for energy management devices. On-premise pre-processing: unibeam pulls the data straight from the production database.
DPP as a Service
Manufacturer of special valves
A single simple exchange file per order is enough – the Asset Administration Shell is generated automatically in the DPP platform and made available directly.
Why Codewerk
We know the supplier side
More than 10 years of experience in the process industry. We know what a requirements letter means day to day.
We help write the standards
IDTA member since 2021, active in the Digital Data Chain Consortium and at Factory-X – where we contribute to the MX-Port concept.
FAQ Digital Data Chain
Frequently asked questions
The Digital Product Passport becomes binding per product group through delegated acts, roughly 18 months after each one is adopted. The first deadline is 18 February 2027 for batteries. For process industry components, the date set by your major customer normally comes first – it is stated in your requirements letter.
The Asset Administration Shell is the data structure, the passport is the use case. The Asset Administration Shell (AAS, standardised in IEC 63278-1) describes a product in machine-readable form. The DPP is the regulatory requirement built on top of that structure. If you have a compliant AAS, you have the basis for the passport – and your customer’s requirements are met as well.
A globally unique, machine-readable identity per device. Provided as a QR code on the nameplate and as an RFID or NFC tag. In the Asset Administration Shell this belongs to the Identification submodel. The code becomes an ID link through which your customer retrieves the device data.
Your existing manufacturer documentation, just structured. The guideline defines structure, scope and data format: manuals, certificates, test reports and drawings in the arrangement the operator expects. In the Asset Administration Shell this is the Handover Documentation submodel. You do not have to produce new content for it.
The unbroken, machine-readable data chain from manufacturer to plant operator. Today it breaks at every handover: datasheets as PDFs by e-mail, spreadsheets, documents in a customer portal. Unbroken means product data and documents are passed on in one consistent format – as an Asset Administration Shell, addressable through an ID-Link on the device. Your customer then ingests them automatically instead of retyping them.
A process industry consortium that standardises data exchange. Plant operators, manufacturers and service providers jointly define how objects are uniquely identified and how their information is exchanged. Codewerk is a member of the DDCC and has been an IDTA member since 2021 – the standards your customer is asking about are created in exactly these bodies.
Whoever places the product on the market, which is you. Responsibility for the presence, structure and accuracy of the data stays with the manufacturer, even when a service provider generates it. That is why our data comes out of your systems rather than being recreated: the platform reflects what you already maintain.
Not immediately, but they can be included. New devices run through the platform from go-live. Existing devices follow in phase 3, as far as the data is available. Whether a retrofit is needed depends on what your customer requires for the installed base – we clarify that in the gap check.
No. You need product knowledge and a contact for technical questions, not prior AAS knowledge. Modelling the Asset Administration Shell, connecting your systems and running the platform is on Codewerk. No development team on your side, no installation in your IT.
Gap check
Send us your customer’s requirements letter – we will tell you how we can meet the requirements.
We analyse the letter and create a solution for the requirements.
- What your customer requires, set against what you can deliver today
- An assessment of whether your customer’s deadline is realistic
How to submit
Send us the requirements letter by email.
sales@codewerk.deAs a PDF, DOCX or photo. Please include in the email:
- Company and contact person
- Your customer’s deadline, if known
- Which systems hold your product data today
Your letter is used solely for this assessment and is not passed on.