A flexible passport model separates stable identity, product data, documents and lifecycle events.
This guide is written for practical use: it focuses on information that should remain understandable after installation, handover, maintenance or staff changes. The objective is not to collect the maximum possible data, but to keep the right data structured, traceable and easy to use at the physical object.
Begin with persistent identity
The product needs a durable identifier that remains stable as documents and lifecycle information change.
Separate structured data from documents
Core attributes should be queryable fields where appropriate, while certificates, manuals and declarations can remain versioned documents linked to the same identity.
Model lifecycle events
Manufacture, inspection, repair, ownership or status changes can be represented as dated events instead of repeatedly overwriting one current-state record.
Expect requirements to evolve
Different sectors and regulations require different information. A composable schema is safer than baking every possible field into one universal table.
Practical focus
Model identity, structured product attributes, documents and lifecycle events as related but distinct concepts. This keeps the record extensible as sector requirements change and avoids a brittle universal table with hundreds of optional fields.
Separate identity from changing data
The identifier on the physical object should remain stable while descriptions, ownership, documents and lifecycle information evolve. This reduces relabelling and preserves continuity across years of use.
- Use one durable object identifier.
- Keep mutable information in the digital record.
- Retain a human-readable ID even when QR or NFC is present.
Control what different audiences can see
A person standing next to the object may need a simple public page, while staff need internal notes, evidence and history. Public and private information should be deliberate rather than an accidental consequence of where a file was uploaded.
- Review public fields as if an unknown person scanned the tag.
- Keep sensitive documents behind authenticated access.
- Use explicit visibility for attachments and lifecycle events.
Preserve lifecycle context
A current status is useful, but it does not explain how the object reached that state. Dated events for inspections, maintenance, replacements and important changes make the record far more useful for future decisions.
How to choose between the options
Use the simplest approach that still preserves stable identity, traceability and the level of access your workflow needs. Avoid choosing technology only because it is newer; consider cost, environment, expected lifetime and who will actually use the record.
- Prefer durable identifiers over temporary labels.
- Separate physical carrier choice from the underlying digital identity.
- Plan how the record will be maintained after the initial rollout.
A practical decision rule
If the information changes often, keep it in the digital record. If it must remain visible without a device or network connection, keep a concise human-readable version on the physical label as well.
A practical implementation workflow
Treat the first version as an operational baseline rather than a one-off document. Start with a small representative sample, check that another person can understand the identifiers and fields without verbal explanation, then apply the same structure consistently. The workflow should be simple enough to repeat during installation, handover and later maintenance, because a technically perfect record that nobody keeps updated quickly loses value.
- Pilot the structure on a few real objects before rolling it out in bulk.
- Define which fields are mandatory and which are optional before importing or printing labels.
- Test links, QR codes and exported files on the actual devices and materials used in the field.
- Record who owns the data quality and who is expected to update the record after a change.
Review the record as part of the lifecycle
Good documentation is not finished when the first record is created. Review it whenever the physical object changes, when responsibility is handed over, or when an inspection or maintenance event reveals new information. A short periodic review is usually more reliable than trying to reconstruct several years of undocumented changes later. The aim is to keep the current view accurate while preserving enough history to understand important decisions.
- Update the current state after material changes instead of adding contradictory notes.
- Keep dated evidence for changes that may matter during troubleshooting, audit or handover.
- Retire obsolete information deliberately rather than leaving several competing versions in circulation.
Common mistakes to avoid
Avoid using sequential public URLs, treating a QR code as the permanent identity, exposing internal notes by default or creating a new object record every time a label is replaced.
A sensible next step
Choose one real object, assign a stable human-readable ID, create its digital identity and decide which fields, attachments and lifecycle events should be public or private.