EU regulatory deadlines create binding evidence obligations for this platform category. EXOS-LINK adds runtime integrity monitoring and tamper-evident compliance evidence — zero hardware changes required.
ON REQUEST
COMMERCIAL TERMS
MACHINERY REG ANNEX III
PRIMARY REGULATION
DEPLOYABLE TODAY
6 DEPLOYABLE MODULES
▸ REGULATORY CONTEXT — WHY THIS MATTERS NOW
⚠
REGULATORY DEADLINE
Dual exposure: Machinery Regulation Jan 2027 · Annex III 1.2.1(f) (AI-specific requirements via the Aug 2028 delegated act). One EXOS-LINK integration supports evidence outputs for both frameworks.
Your platform already leads on safety — EXOS-LINK adds the runtime evidence layer above it, without touching your safety architecture.
▸ LIVE DEMO — BUILT FOR YOUR PLATFORM
▶ 6-Axis Cobot — Integrity Demo
SCENARIO BUILT FOR INDUSTRIAL COBOT
Full encoder fault cycle with tamper-evident audit log. Evidence pack supports Machinery Reg Annex III, MR Annex III §1.1.9/§1.2.1(f), and the 2028 delegated act technical documentation — one integration.
BODY MODEL INTEGRITYREGULATORY EVIDENCE GENERATORSIGNAL INTEGRITY LAYERTRUST-STATE GOVERNORDISTRIBUTED TIMING INTEGRITYNOISE SUPPRESSION
▸ REGULATORY COVERAGE — WHAT THIS ADDRESSES
Machinery Reg Annex III
SUPPORTS EVIDENCE
Supports evidence and record-keeping obligations for Machinery Reg Annex III. Final conformity assessment depends on system classification, intended use, and integrator. Tamper-evident audit log generated on each integration run.
AI Act — via 2028 delegated act
SUPPORTS EVIDENCE
After the Digital Omnibus (July 2026), machinery moved to Annex I Part B: AI Act requirements reach machinery through a delegated act under the Machinery Regulation, due 2 August 2028. EXOS-LINK already produces the runtime record those obligations will rest on. Tamper-evident audit log generated on each integration run.
MR Annex III §1.1.9 / §1.2.1(f)
SUPPORTS EVIDENCE
Supports evidence outputs for MR Annex III §1.1.9 / §1.2.1(f). Tamper-evident audit log generated on each integration run.
Ready to discuss a pilot?
Pilot scope and timeline available on request.
REST / ROS2 / file tail — same schema. Output: signed compliance evidence on each integration run.
Licence terms available on request.
All company names, product names, and trademarks referenced on this page are the property of their respective owners. Olikonste Systems is not affiliated with, endorsed by, or in partnership with any of the companies named. This page is an independent technical overview prepared for informational purposes only. Nothing on this page constitutes legal advice or a conformity assessment. Final regulatory classification, conformity assessment, and compliance determination depend on system classification, intended use, and the responsible integrator or manufacturer.