OT-Cyber.de
Free sample case · CRA and Machinery Regulation

Networked wood chip heating: nine steps to CE marking under the CRA and the Machinery Regulation

A free, fully worked example for heating and machine builders. Whoever combines several machines into a networked plant and hands it over is the manufacturer under the Machinery Regulation (EU) 2023/1230 and the Cyber Resilience Act (EU) 2024/2847. The example shows a company with two people and six partner firms, with 30 documents as blank templates and as filled examples.

Regulation (EU) 2024/2847Regulation (EU) 2023/1230IEC 62443EN ISO 13849
The plant

The plant and its protective functions

Wood chip boiler NWT HACKTHERM 60 connect (18 to 60 kW) with room discharge system, rotary valve and a safety controller. Orange: safety functions according to EN ISO 13849. Blue: zones according to IEC 62443.

SF4Store room door

Door open: agitator and discharge stop immediately, restart blocked. Coded safety switch, PL d.

SF1Burn-back protection

The rotary valve separates combustion chamber and fuel store. On overtemperature it closes; the extinguishing device works thermally without power.

SF2Overtemperature

Safety temperature limiter at 105 °C, hard-wired, plus monitoring by the safety controller.

SF3Emergency stop

Emergency stop at the boiler and the heating emergency switch outside the boiler room stop all drives.

SF9Ash box

Lid open or box removed: ash augers stop. No remote start.

Z3Gateway

The only route into the network. Outgoing encrypted connections only, secure boot, signed updates. No write access to safety data.

Z4Portal and app

Remote maintenance only after approval by the operator, with MFA, time limit and log. Blocked: anything that causes movement.

The most important principle: temperature limiter, thermal discharge safety device, safety valve and extinguishing work without software and without the network. An attack over the internet cannot switch them off.

The company

Two people, six partners, one manufacturer

Nordwald Wärmetechnik GmbH (fictitious) places the boiler on the market under its own brand and is therefore the manufacturer, even though partners build and program parts of it.

Michael Berger

Master heating engineer, managing director, CE coordination, signs the declaration.

Jonas Weiß

Mechatronics technician: engineering, safety functions, product security, reporting.

Partner (fictitious)Contribution
Kesselbau Alpenrand GmbHBoiler body, room discharge, rotary valve
Schaltanlagen Hofer GmbHControl cabinet, routine test
Datenwerk Embedded GmbHGateway, portal, app, SBOM, updates
Ingenieurbüro LechnerSafety functions, validation
Sichtwerk Security GmbHPenetration test, on-call duty for reports
Prüfinstitut Feuerungstechnik SüdType test EN 303-5, EMC

Partners deliver services. The obligations under the Machinery Regulation and the CRA stay with the manufacturer. That is why an obligations annex sets reporting routes in hours, 15 years of updates, retention and source code escrow (D02, F03).

Deadlines

Which dates apply?

What counts is the day on which each individual plant is placed on the market.

  • 11 Sep 2026: Reporting obligation under Article 14 CRA applies already, also for networked plants that have been delivered before.
  • until 19 Jan 2027: Machinery Directive 2006/42/EC with EC declaration of conformity.
  • from 20 Jan 2027: Machinery Regulation (EU) 2023/1230, without a sell-off period.
  • from 11 Dec 2027: CRA applies in full, CE marking also under the CRA.
Procedure

Nine steps from classification to support in the field

For every step the documents are available as a blank, fillable template and as a filled example of Nordwald Wärmetechnik.

Step 1

Classify

Do the Machinery Regulation and the CRA apply, and are we the manufacturer?

Who: Berger (managing director), checked by Weiß · In the example: Nov 2026

  1. We are affected because we create an assembly of machinery: several machines arranged and controlled so that they work together as one plant. The boiler with its motor-driven augers alone is already a machine. This makes us the manufacturer under the Machinery Regulation. When we hand the plant over to the customer, we place this assembly on the market. Because it is networked, it is a product with digital elements and also falls under the CRA.
  2. Fix the legal acts and dates: Machinery Regulation from 20 January 2027, CRA in full from 11 December 2027, reporting obligation since 11 September 2026.
  3. Determine the CRA class: core function heat generation, no category in Annex III or IV, so a default product.
  4. Choose the conformity assessment procedure: internal control under both legal acts, no notified body.

Which role do we have? Three cases

  • Case A: own name or own brand. The plant goes to the customer under our name or brand, even if partners make parts of it. Machinery Regulation: full manufacturer obligations. CRA: full manufacturer obligations.
  • Case B: assembly of machinery, without an own product brand. We combine boiler, room discharge system, rotary valve and controller from different suppliers into one plant and hand it over in working order at the customer site. For us this is the decisive reason; our own brand comes on top. Machinery Regulation: manufacturer of the assembly, own name on the rating plate, own declaration. CRA: manufacturer of the whole plant if it is networked; for controller and gateway we rely on the suppliers' declarations, SBOMs and updates.
  • Case C: installing finished devices without modification. We install a finished, CE-marked device according to the manufacturer's instructions, without combining it with other machines into one plant and without changing software or security settings. No manufacturer obligations, only distributor and installation duties. Anyone who switches off safety functions, sets up remote access on their own or changes software has to check again: this can be a substantial modification.

It does not matter whether the plant is assembled in our workshop or at the customer site. A plant used only in your own company does not fall under the CRA, but it does fall under the Machinery Regulation. How authorities view assembly at the customer site in an individual case has not been finally settled; agree the manufacturer role in writing with the customer and the suppliers.

Result: Matrix of legal acts, list of standards and assessment procedure are fixed.

Documents: D01 Classification, legal framework and assessment procedure (template, example)

Step 2

Set up the company

How do two people cover all manufacturer obligations?

Who: Berger, Weiß, partner companies · In the example: Nov 2026

  1. Allocate roles with deputies: management and CE with Berger; engineering, safety and product security with Weiß.
  2. Bind partners by contract: reporting routes, 15-year support commitment, retention, source code escrow.
  3. Become able to report: access to the ENISA single reporting platform, on-call duty, emergency card, reporting drill.
  4. Plan and record training.

Result: The organisation is in place; the company can report vulnerabilities and incidents on time.

Documents: D02 Roles, subcontractors and allocation of obligations (template, example); D16 Emergency card: reporting under Article 14 CRA (template, example); F03 Subcontracting agreement: CRA and MR annex (template, example); F06 Reporting record under Article 14 CRA (template, example); F12 Training record (template, example)

Step 3

Describe the plant

What exactly do we place on the market, and for what purpose?

Who: Weiß, approval by Berger · In the example: Dec 2026

  1. Record product data, assemblies and interfaces.
  2. Describe intended use and reasonably foreseeable misuse, including remote access.
  3. Define limits and life phases, including updates and decommissioning.
  4. Enter requirements with their source in the requirements list.

Result: Plant description and requirements list as the basis for all further steps.

Documents: D03 Plant description (template, example); F01 Requirements list (template, example)

Step 4

Design for safety and security

How does the heating system stay safe, even under attack?

Who: Weiß with engineering office and software partner · In the example: Dec 2026

  1. Select a safety controller certified to IEC 62443-4-2.
  2. Define safety functions SF1 to SF10 with their required performance level (PLr).
  3. Principle: safety temperature limiter, thermal discharge safety device, safety valve and extinguishing work without software and without the network.
  4. Plan zones and conduits according to IEC 62443, remote maintenance only after approval, signed updates.

Result: Control and safety concept and network architecture.

Documents: D04 Control and safety concept (template, example); D05 Network and system architecture (template, example)

Step 5

Assess the risks

Which hazards remain, and are they acceptable?

Who: Weiß, Berger, engineering office, security partner · In the example: Jan 2027

  1. Assess hazards according to EN ISO 12100 for all life phases and reduce them with the three-step method.
  2. Assess cyber threats according to IEC 62443-3-2 and map them to CRA Annex I.
  3. Show that an attack cannot defeat a safety function (MR Annex III, sections 1.1.9 and 1.2.1).
  4. Record residual risks for the instructions.

Result: Two risk assessments with a joint cyber safety argument.

Documents: D06 Risk assessment, machinery safety (template, example); D07 Cybersecurity risk assessment (template, example)

Step 6

Introduce processes

What has to run permanently in the company?

Who: Weiß (PSO), Berger, software partner · In the example: Dec 2026 to Mar 2027

  1. Introduce 20 processes according to the process manual: development, SBOM, vulnerabilities, updates, changes, market surveillance.
  2. Assess suppliers and components.
  3. Publish the coordinated vulnerability disclosure policy and security.txt.
  4. Ship every release with an SBOM and a security approval.

Result: Processes that are actually lived, with evidence for the technical documentation.

Documents: D08 Process manual (template, example); D14 Coordinated vulnerability disclosure policy (template, example); F02 Supplier and component assessment (template, example); F04 SBOM release (template, example); F14 Security release approval (template, example)

Step 7

Test and validate

Does everything work as planned?

Who: Weiß, engineering office, test laboratory, partners · In the example: Jan to Mar 2027

  1. Type test to EN 303-5 and EMC at an accredited laboratory.
  2. Validate every safety function with fault injection.
  3. Penetration test and communication failure test.
  4. Introduce a routine test for every serial number.

Result: Test reports, validation records, routine test record.

Documents: F09 Validation record, safety function (template, example); F10 Routine test record (template, example)

Step 8

Document and declare

What is needed for the CE marking?

Who: Berger (signature), Weiß · In the example: Mar 2027

  1. Compile the complete technical documentation.
  2. Publish the user information, with the simplified EU declaration of conformity under Annex VI and the end of the support period for each unit (15 years from handover).
  3. Work through the checklist, then sign the joint EU declaration of conformity: with the statement that fulfilment of Annex I has been demonstrated, valid from 11 December 2027, and standards with their edition.
  4. Attach the rating plate, CE marking and end-of-support label.

Result: Signed declaration, CE marking, release for placing on the market.

Documents: D09 Technical documentation: table of contents (template, example); D10 Checklist before placing on the market (template, example); D11 EU declaration of conformity (template, example); D12 Rating plate and marking (template, example); D13 User information under CRA Annex II (template, example); D15 Support period statement (template, example)

Step 9

Deliver and support

What applies after the sale, over the whole support period?

Who: Weiß (service, PSO), Berger · In the example: from Mar 2027

  1. Commissioning with a secure initial configuration.
  2. Handle vulnerabilities, inform users, provide updates free of charge.
  3. Check changes for substantial modification.
  4. Implement corrective actions and inform authorities where required.

Result: Conformity and safety over the entire support period.

Documents: F05 Vulnerability ticket (template, example); F07 Security advisory to users (template, example); F08 Change request (template, example); F11 Commissioning record (template, example); F13 Corrective action and contact with authorities (template, example)

Product

What the product must be able to do

The requirements of Annex I, Part I, point (2) CRA in plain words. How the example implements them: D04 Control and safety concept (template, example); D05 Network and system architecture (template, example); D07 Cybersecurity risk assessment (template, example).

  • (a) No known exploitable vulnerabilities on delivery.
  • (b) Secure by default configuration, with the option to reset the product to that state.
  • (c) Security updates can be installed, automatically by default, with an option to switch this off.
  • (d) Protection against unauthorised access: login, roles, no shared default passwords.
  • (e) Confidentiality of stored and transmitted data, for example by encryption.
  • (f) Integrity of data, commands, programs and configuration protected against manipulation.
  • (g) Process only the data needed for the purpose.
  • (h) Essential functions remain available, also during attacks or when the connection is disturbed.
  • (i) The device does not disturb other devices and networks.
  • (j) As few attack surfaces as possible: only the interfaces and services that are needed are open.
  • (k) Limit the impact of an incident.
  • (l) Record and monitor security-relevant events, with an opt-out for the user.
  • (m) Users can delete all data and settings securely and permanently.

For machinery there is more: remote access and connected devices must not lead to a hazardous situation, and control systems must withstand malicious attempts (MR Annex III, sections 1.1.9 and 1.2.1).

Documentation

What goes where

User information and instructions

CRA Annex II, MR Annex III, section 1.7.4

Manufacturer and contact point for vulnerabilities, purpose and security properties, known risks, support period, secure commissioning, updates, switching off automatic updates, secure decommissioning. Plus the machine instructions with installation, operation, maintenance and residual risks. In the example: D13 User information under CRA Annex II (template, example).

Technical documentation

CRA Annex VII, MR Annex IV Part A, one single set under Article 31(3) CRA

Description, design, both risk assessments, processes, justification of the support period, standards, test reports, SBOM, declaration of conformity. Keep for at least ten years, longer if the support period is longer. In the example: D09 Technical documentation: table of contents (template, example); D10 Checklist before placing on the market (template, example).

EU declaration of conformity

CRA Article 28 and Annex V, MR Article 21 and Annex V

One single declaration for all legal acts that apply to the product, with product, manufacturer, legal acts, standards with edition and signature. Required under Article 28(1) CRA is the statement that fulfilment of the requirements in Annex I has been demonstrated. It applies to units placed on the market from 11 December 2027. The product comes with the declaration or the simplified version under Annex VI. In the example: D11 EU declaration of conformity (template, example).

Rating plate and CE marking

CRA Article 30, MR Annex III, section 1.7.3

Manufacturer, type, serial number, CE marking; plus a note where to find the declaration and the user information. In the example: D12 Rating plate and marking (template, example).

On your website

CRA Annex I, Part II, points (5) and (6), Article 13(19)

Contact point and coordinated vulnerability disclosure policy (ideally as security.txt), the end of the support period, the full declaration of conformity and the security advisories with severity and affected versions. In the example: D14 Coordinated vulnerability disclosure policy (template, example); D15 Support period statement (template, example).

Internal, as evidence

Articles 13 and 14, Annex I Part II CRA

Reporting records, vulnerability tickets, SBOM and release approvals, change requests, training, commissioning. In the example: F04 SBOM release (template, example); F05 Vulnerability ticket (template, example); F06 Reporting record under Article 14 CRA (template, example); F08 Change request (template, example); F12 Training record (template, example); F14 Security release approval (template, example).

Relief for small companies

  • Microenterprises and small enterprises are not fined for missing the 24-hour early warning deadline. The reporting obligation itself still applies (Article 64(10)(a) CRA).
  • For the technical documentation the CRA provides a simplified form for microenterprises and small enterprises, to be established by the Commission (Article 33(5) CRA). Anyone using it still has to provide all content of Annex VII.
  • Member States are to support small companies with information, training and help desks (Article 33(1) CRA).

Common mistakes

  • "The CRA only applies from 2027": the reporting obligation applies since 11 September 2026, also for devices already at customer sites.
  • Forgetting the app and cloud portal: whatever controls the device remotely or processes its data belongs in the assessment.
  • "The partner delivers, so the partner is responsible": the obligations stay with the manufacturer. Contracts and reporting routes have to cover this.
  • No support period defined, or not published.
  • Two separate declarations of conformity instead of one joint declaration.
  • A declaration without the statement on Annex I (Article 28(1) CRA), or with a CRA reference also for units placed on the market before 11 December 2027.
  • One fixed end of support for all units: a late buyer gets less than five years. Better a period counted from the handover of each unit.
  • Not assessing every point of Annex I Part I individually: Article 13(3) requires for points (a) to (m) whether it applies and how it is implemented.
  • Safety functions that depend on software or the network. In the example, temperature limiter and thermal discharge safety device work without either.
Downloads

All 30 documents

D = document, F = form. Every document comes with document control, revision history and a glossary.

No.DocumentStepDownload
D01Classification, legal framework and assessment procedure1template, example
D02Roles, subcontractors and allocation of obligations2template, example
D03Plant description3template, example
D04Control and safety concept4template, example
D05Network and system architecture4template, example
D06Risk assessment, machinery safety5template, example
D07Cybersecurity risk assessment5template, example
D08Process manual6template, example
D09Technical documentation: table of contents8template, example
D10Checklist before placing on the market8template, example
D11EU declaration of conformity8template, example
D12Rating plate and marking8template, example
D13User information under CRA Annex II8template, example
D14Coordinated vulnerability disclosure policy6template, example
D15Support period statement8template, example
D16Emergency card: reporting under Article 14 CRA2template, example
F01Requirements list3template, example
F02Supplier and component assessment6template, example
F03Subcontracting agreement: CRA and MR annex2template, example
F04SBOM release6template, example
F05Vulnerability ticket9template, example
F06Reporting record under Article 14 CRA2template, example
F07Security advisory to users9template, example
F08Change request9template, example
F09Validation record, safety function7template, example
F10Routine test record7template, example
F11Commissioning record9template, example
F12Training record2template, example
F13Corrective action and contact with authorities9template, example
F14Security release approval6template, example

Check before signing a declaration

  • Adoption of the national CRA implementation act and the competent market surveillance authority in your country
  • Harmonised standards for the CRA and for MR Annex III, section 1.1.9, once cited in the Official Journal (until then, use specifications such as IEC 62443 and justify the solutions)
  • Numbering in MR Annexes IV and V against the Official Journal

Frequently asked questions

Does the CRA apply to a machine builder who assembles a heating plant from supplier parts?

Usually yes, if the plant is networked. Whoever combines several machines into one plant and hands it over is the manufacturer under the Machinery Regulation; if the plant has a network connection (gateway, app, portal), it is a product with digital elements under the CRA as well.

Do we need a notified body?

Not for a default product such as this heating system. Its core function is heat generation and it is not listed in Annex III or IV CRA, so internal control is enough under both legal acts.

What does the maintenance team have to do when a vulnerability is actively exploited?

Report it: early warning within 24 hours of becoming aware, notification within 72 hours, final report later, via the ENISA single reporting platform. The emergency card (D16) hangs at the workstation, the reporting record (F06) shows a filled example.

Can we use these documents for our own product?

Yes, the blank templates are free to use. Every manufacturer assesses its own product; the risk figures, performance levels, deadlines and support period in the example are justified sample values, not legal advice.

Sources

Free sample by OT-Cyber, not legal advice. All companies, people and data in the example are fictitious. Status 22 Nov 2026. German version: Muster vernetzte Hackschnitzelheizung.

Help with implementation: CRA as a Service

Last updated: 22.11.2026

Share: LinkedInXINGFacebookXWhatsAppE-Mail