Verifying maintenance with smart contracts
Sector: Tertiary sector · Industry: Facility services · Organisation: SPIE Deutschland & Zentraleuropa · Maturity level: Pilot
SPIE piloted a blockchain-based maintenance process for technical assets. QR or NFC scans established the asset reference, mobile records documented execution, and smart contracts checked agreed criteria before the invoice proceeded for processing.
Documentation status
- Project status: Unknown (as of 30 January 2023) — In 2019, SPIE documented a prototype, later two customer pilots, and on 30 January 2023 the technical pilot architecture. Continued productive operation thereafter is not evidenced in the evaluated primary sources.
- Evidence: Evidence high
- Editorial review: SapientBlock Redaktion, 17 September 2026
Description
Maintenance of many technical systems generates numerous inspection reports. The client must assign them to the agreed services, deadlines, and a consolidated invoice. SPIE tested a seamless process linking equipment identification, on-site verification, maintenance report, and invoice verification via a permissioned blockchain.
In 2019, SPIE developed a prototype for blockchain-based maintenance processes at ARENA2036 and later described two customer pilots. In the initial process, SPIE carries out maintenance and inspections on fixed technical equipment. The customer then receives individual inspection reports and a consolidated invoice and must manually reconcile the documents. In the pilot, a maintenance request was assigned to a smart contract and submitted as an event to Hyperledger Fabric. On site, employees identified the equipment via QR code or NFC tag; a mobile application added date and time and led to the appropriate report. Documents were stored outside the blockchain in IPFS, while references and process events were kept in the permissioned blockchain. APIs and Robotic Process Automation connected email, mobile capture, application server, and ledger. The smart contract checked agreed criteria such as deadlines, reports, and evidence. If fulfilled, the user interface signalled further invoice processing. SPIE documented one pilot for performance-based invoice verification and a second in the GMP environment. Public primary sources confirm prototype and pilot, but neither quantified savings nor current productive operation.
Benefits
General
- Traceable maintenance events
- Uniform inspection criteria
B2B — organisations
- Shared status for service and evidence
- Less document reconciliation required
- Integration of existing systems via APIs
Employees
- Direct access to equipment-related report
- Structured mobile documentation
Technology foundation
Permissioned Hyperledger Fabric network on virtual Linux systems in Microsoft Azure; IPFS for external document storage; web interface, mobile applications, APIs, and RPA for process integration.
Implementation examples
SPIE Deutschland & Zentraleuropa
Equipment-related maintenance evidence and rule-based invoice verification
Not quantified by SPIE
Labour-intensive reconciliation of maintenance reports, service evidence, and consolidated invoices