03 / Platform

A product identity. A connected next step.

CIRPAL is the digital layer being developed for circular pallet systems. Its intended role is to link a physical pallet to material records, lifecycle events and a defined return route.

Proposed architecture · Not a live software service

Discuss the MeSentia opportunity

The data model

Keep material and product information connected.

A pallet ID is useful when it connects to information people can act on.

The planned CIRPAL record begins with material and production data. It follows meaningful events during use and supports a decision when the pallet returns.

These records would support material traceability. Their reliability depends on accurate input data, recorded events and evidence supplied by the partners involved.

CIRPAL / Asset recordProposed model

Material: Qualified feedstock · batch reference · supporting records
Product: Unique identity · production reference · product version
Lifecycle: Handover · use · return · inspection decision
Responsibility: Current partner · next responsible party · agreed route
Next step: Reuse · repair assessment · qualified reprocessing

Conceptual fields only. No operational or sample fleet data.

From events to action

Every handover needs meaning.

A last recorded location is one event. A return decision also needs condition, responsibility and a destination.

01
Register at production
Link a unique product identity to the material batch and the production record.
02
Record the relevant event
Associate a scan or registered handover with a partner, a time and a lifecycle state.
03
Make return actionable
Identify the responsible partner and the intended receiving or inspection route.
04
Record the outcome
Capture whether the asset re-enters service or moves to an assessed material-recovery route.

Development scope

Build the useful core first.

The physical application should inform what the digital system actually needs.

Intended initial scope

Identity & return coordination

Material and product registration
Unique product identification
Partner roles and responsibility
Lifecycle states and event records
Defined return and next-step routes

Later possibilities · not available

Integration & automation

Connections to partner enterprise systems
Automated event capture
Operational reporting and evidence exports
Service and commercial workflows

Priorities depend on pilot learning and partner needs.

What a pilot needs to establish

Useful records.
Practical operations.

Can the identity survive actual use?

Evaluate identifier placement, readability and the effort required to register events.

Are the records trustworthy?

Define who supplies data, who can update it and how corrections and missing events are handled.

Does the next step happen?

Connect recorded decisions to receiving capacity, inspection and real return logistics.

For investors & strategic partners

Connect industrial technology with lifecycle intelligence.

The technology opportunity is centred on MeSentia. Explore the path from physical development to a repeatable industrial system.

The MeSentia investment case

In plain language

The platform, without assumptions.

Is the CIRPAL platform live?

CIRPAL is in development. The diagrams on this page describe the proposed architecture and initial scope. They do not show a live platform, registered customers or operating fleet data.

Will CIRPAL use QR codes or RFID?

The concept supports practical product identifiers such as QR codes or RFID. The final approach depends on durability, reading conditions, cost and partner requirements, and needs pilot validation.

Is CIRPAL continuous GPS tracking?

No. The proposed model is based on recorded lifecycle events and handovers. An event may identify a last registered location; it does not provide continuous GPS location. Continuous tracking would require separate hardware and an agreed use case.

Is CIRPAL a digital product passport?

The intended material and product records overlap with product-passport concepts, but CIRPAL also addresses lifecycle decisions and return coordination. No regulatory product-passport compliance or certification is claimed.

Can it connect to other logistics systems?

Connections to warehouse, enterprise, transport and pooling systems are potential later integrations. They are outside the initial core scope and are not presented as available features.