How can standardization of blockchain-based protocols in Automation projects be achieved?

Blockchain protocol standardisation, interoperability, IIoT, industrial data models and security

The image treats standardisation as a conversion problem: different inputs arrive in incompatible forms, are normalised into a common structure, and only records that satisfy the agreed rules move forward. That is a useful industrial model. Blockchain standardisation does not mean forcing every manufacturer onto the same ledger. It means allowing different systems to exchange records without losing their meaning, identity or verification history.

What Exactly Needs to Be Standardised?

A real plant may contain PLCs from several manufacturers, an independent SCADA package, MES and ERP systems, energy meters, IIoT gateways, cloud services and maintenance software owned by outside contractors.

Replacing all of those systems with one blockchain platform would be neither realistic nor particularly useful.

The real question is:

Can one system understand a record created by another system, identify where it came from, verify who was authorised to create it and preserve the same meaning throughout the exchange?

That makes standardisation much broader than a communication protocol. It includes data models, asset identity, timestamps, signatures, access rights, smart-contract behaviour, APIs, error handling, privacy, lifecycle management and governance.

For that reason, industrial blockchain sits naturally between industrial standards, industrial communication and modern distributed data architecture.

The First Standard Is a Common Meaning

Two devices may exchange packets perfectly and still fail to understand each other.

One maintenance system may create an event called maintenance_completed, while another records only service=1. Both can be transmitted successfully, but several questions remain unanswered:

Which asset was serviced?
Who performed the work?
When did it happen?
Was the work approved?
Which procedure or specification applied?
Which version of the record format was used?

A useful industrial blockchain record therefore needs a predictable structure.

Asset identity: Which machine, component or product?
Event type: Failure, maintenance, calibration, inspection or shipment?
Time: When did the event occur?
Source: Which device or organisation produced the information?
Authority: Was the source permitted to create this record?
Verification: Which signature, hash or approval mechanism was used?
Version: Which data model or business rule applied?

Without that common semantic layer, blockchain-based industrial data sharing can simply create another collection of incompatible data islands.

Blockchain Standardisation Is No Longer an Empty Standards Discussion

International standardisation work now covers blockchain and distributed ledger technology directly. ISO/TC 307 is dedicated to blockchain and DLT and has produced work covering terminology, reference architecture, privacy, identity, smart contracts and interoperability.

ISO 23257:2022 provides a reference architecture for blockchain and distributed ledger systems. A new edition is currently under development, which is important because the surrounding technology and deployment models continue to evolve.

More directly relevant to automation integration, ISO/TS 23516:2026 defines an interoperability framework covering communication between DLT systems and between DLT and systems outside the ledger environment.

That second case is especially important in industry. A blockchain installation rarely operates alone; it has to exchange information with PLCs, SCADA, MES, ERP, historians, data loggers, gateways and cloud platforms.

Interoperability Does Not Mean Using the Same Blockchain

A common mistake is to assume that interoperability requires every participant to migrate to the same ledger technology.

One manufacturer may use a permissioned DLT network. A supplier may use another blockchain platform. The plant itself may keep most operational data in SQL databases and historians.

Standardisation should allow these systems to exchange meaningful information without forcing them into a single vendor's architecture.

That means both DLT-to-DLT and DLT-to-non-DLT interoperability matter.

For existing factories, DLT-to-non-DLT integration may be the more important problem, because almost the entire installed automation base was built without blockchain.

IEEE Work Shows the Same Interoperability Problem from Another Angle

IEEE 3205-2023 addresses blockchain interoperability data authentication and communication protocols. Its focus is cross-chain communication between homogeneous and heterogeneous blockchain systems.

For the industrial side, the ongoing IEEE P3849 project is particularly interesting because it addresses trusted data circulation for Industrial IoT (IIoT) using blockchain, trusted hardware, edge computing, smart contracts and industrial identification mechanisms.

P3849 is still a standards-development project rather than a published standard, but the scope itself is revealing: industrial blockchain is increasingly being treated as part of a wider data lifecycle and trust architecture, not simply as a ledger.

IIoT Makes Common Data Rules Essential

An IIoT architecture may contain hundreds or thousands of devices. Allowing every device vendor to invent its own blockchain record format is not sustainable.

A vibration monitor, power meter, robot controller, servo drive and quality station all generate different information, but a higher-level system should still be able to understand the basic framework around that information:

Who produced it?
Which asset does it describe?
When was it created?
Can the source be authenticated?
Who is allowed to use it?
Has the registered record changed?

That is one of the reasons why blockchain data exchange between IIoT devices needs more than a blockchain node and an internet connection.

Device Identity Has to Survive the Life of the Machine

A blockchain can make historical manipulation easier to detect, but the value of that history depends heavily on the identity that created it.

What happens when an industrial gateway is replaced?
Can the replacement inherit the old device identity?
What happens when a certificate expires?
Can a removed service contractor still sign new records?
How are records created with an old credential treated?

These questions show why the identity of blockchain participants has to be part of the architecture from the beginning.

Smart-Contract Standardisation Is Not About Choosing a Programming Language

For industrial smart contracts, standardisation has much more to do with behaviour than syntax.

What event triggers the contract?
How is the source of that event authenticated?
What happens when several approvals are required?
Which contract version applies to an old transaction?
How is a faulty contract stopped?
How does the application report a failed execution?

This makes industrial smart-contract standardisation a problem of state, behaviour, authority and lifecycle, not simply code compatibility.

Time Is Part of the Data Model

Timing matters in automation.

If an alarm occurred at 14:31:05, maintenance approval at 14:31:07 and an operator intervention at 14:31:10, the sequence itself may be important evidence.

If the participating systems do not share a reliable time base, the blockchain may preserve transaction order while the actual physical event sequence remains uncertain.

That means time source, timestamp format, clock synchronisation and expected accuracy also belong in the wider standardisation discussion—particularly when blockchain is connected to real-time industrial monitoring.

Cryptography Needs a Lifecycle Too

Industrial equipment can remain in service for twenty years or more. It is dangerous to assume that today's cryptographic choices will remain appropriate for the full life of the plant.

A robust standard therefore needs to think beyond which algorithm is used today.

It should also consider how keys are renewed, how certificates expire, how algorithms are replaced and how historical records remain verifiable after a migration.

These lifecycle issues are directly connected to the broader question “Is blockchain secure?” Security is not a one-time configuration.

Blockchain Standards Cannot Live Apart from Industrial Cybersecurity

A perfectly standardised ledger can still receive false information from a compromised gateway.

That is why blockchain integration must sit alongside industrial cybersecurity: authentication, network segmentation, secure remote access, role-based permissions and endpoint hardening still matter.

The contribution described in blockchain protection against industrial cyber threats is therefore one layer of the defence architecture, not the complete security architecture.

Privacy Also Needs Standard Rules

Making every participant see the same data is not interoperability. In many industrial projects it is a privacy failure.

The architecture needs rules describing which data belongs on-chain, which data remains off-chain and which participants may access each part.

A production recipe, for example, can remain inside the plant while its version number, approval status and cryptographic hash are registered on the blockchain.

That model fits much better with industrial data privacy than distributing the actual recipe across several nodes.

Edge Gateways Can Become the Translation Layer

It is unrealistic to expect every legacy sensor or drive to understand a blockchain protocol.

An edge computing gateway can translate several field protocols into a common higher-level record model.

A Modbus energy meter, PLC production counter and vibration monitoring system can keep their existing interfaces. The gateway can normalise their relevant records into a common structure before anything reaches the blockchain:

asset + event + timestamp + source + verification.

That is probably the closest real-world equivalent to the converter shown in the page image.

Legacy Automation Makes API Standardisation Essential

The success of industrial blockchain may depend less on new blockchain-ready machines than on how easily existing plants can connect to it.

A ten-year-old PLC does not need to become a blockchain node. A SCADA, MES or gateway can expose the selected event through a defined API and pass it to the ledger layer.

This allows the existing control system to remain intact while blockchain is added only where it has a clear role.

Without this approach, standardisation risks creating an entire second automation architecture alongside the first one—and that can quickly destroy the cost-effectiveness of industrial blockchain.

A Standard Must Define Failure, Not Only Normal Operation

Real plants fail in untidy ways.

What happens if a blockchain node is offline?
What if the same event is submitted twice?
What if the timestamp is invalid?
What if the signing certificate has expired?
What if two systems report conflicting states?
What if communication fails halfway through a smart-contract workflow?

Interoperability rules need predictable behaviour for these cases as well. Otherwise two systems may work perfectly during a demonstration and become incompatible during the first network fault.

Conformance Testing Matters More Than a Logo

A product claiming support for the same standard does not automatically mean it will work correctly with another implementation.

Useful testing should answer practical questions:

Can gateways from different vendors create the same event structure?
Can each implementation validate the other's signatures?
Do both reject malformed records consistently?
Do they interpret the same asset identity in the same way?
Do they recover from communication failure predictably?

Formal certification can provide a baseline, but project-level interoperability still needs to be tested under actual plant conditions.

A Pilot Should Test the Architecture, Not Prove That Blockchain Exists

Two computers creating blocks in a laboratory proves very little about industrial interoperability.

A useful pilot asks harder questions:

Can equipment from different vendors exchange the same event?
Does the machine identity survive the entire data path?
What happens after 100,000 events?
What happens during a network outage?
Can a service company's permission be revoked cleanly?
Can the record still be verified years later?

Testing at this level also reveals the real performance impact of blockchain on industrial automation.

Governance Is Part of the Standard, Even When It Is Not a Protocol Field

Once several companies share a blockchain network, somebody has to define how that network is governed.

Who may add a new node?
Who issues identities or certificates?
Who approves a smart-contract update?
How is an incorrect record handled?
What happens when one partner leaves?
Who decides when the data model changes?

A common packet format does not answer any of these questions.

This is why the technical challenges of industrial blockchain quickly become organisational challenges as well.

The practical meaning of standardisation: it is not “every factory must run the same blockchain.” It is “whatever platform is used, all parties can determine which asset a record belongs to, who created it, when it was created, which rule validated it and how another system should interpret it.”

What Should a Useful Industrial Blockchain Standard Cover?

1. Terminology: common definitions for assets, nodes, events, transactions and smart contracts.
2. Reference architecture: clear boundaries between field, control, edge, cloud and ledger layers.
3. Data models: common representation of assets and industrial events.
4. Identity: authentication of devices, users and organisations.
5. Security: key, signature, certificate and permission management.
6. Privacy: rules for on-chain and off-chain information.
7. Interoperability: both blockchain-to-blockchain and blockchain-to-conventional-system exchange.
8. Smart-contract behaviour: triggering, approval, failure and version handling.
9. Performance: expected latency, throughput and scaling behaviour.
10. Governance: membership, updates and responsibility.
11. Testing: conformance and interoperability criteria.
12. Lifecycle: migration of devices, credentials, algorithms and standards.

These subjects do not have to live inside one document. But if one of them is ignored, a supposedly standard industrial blockchain can still fail to interoperate in practice.

Standardisation Does Not Make Blockchain Necessary

A good standard can make blockchain easier to integrate. It cannot make blockchain the right answer to every project.

A single company managing its own machine records may still be better served by an ordinary database.

The real benefit of standardisation appears when blockchain already has a valid technical or commercial reason to exist and the project needs to avoid vendor lock-in, incompatible data structures and custom interfaces at every boundary.

Standardisation therefore does not replace the need to assess scalability, cost, privacy and performance.

The objective is not: “Everyone must use the same blockchain.” The better objective is: “Whatever system they use, the industrial record must keep the same meaning and remain verifiable.”

Related Blockchain Topics

Blockchain for IIoT data exchange
Blockchain scalability and flexibility
Industrial data integrity
Industrial data privacy
Technical challenges of industrial blockchain
Smart contracts in industrial automation

Related Automation Topics

Industrial Standards  |  Industrial Communication  |  Industrial IoT  |  Industry 4.0

Edge Computing  |  Industrial Cybersecurity  |  Cloud Computing  |  Data Logger

← Blockchain FAQ and Industrial Blockchain Topics