Seven scenes delivered in full; eight scenes land light
Not every scene deserves a full system. Layer delivery by demand density so budget and pace match the scene’s real value.
Seven scenes with a coherent need
These seven have a named customer and a coherent need: full solution plus scene-specific capability. Open a card for roles, capabilities, hard parts and the delivery boundary.
Eight light scenes — configuration, not new development
The scene is real but thin, or highly isomorphic with Tier 1. Deliver by config, scene codes and report templates — no new system or account type.
Zero-carbon MICE
Entitlement + carbon- Scene increment
- Events last only days; bulk card open and bulk expire are required; green travel to the venue can be accounted
- Carbon acts
- Green-travel arrival, e-badge vs paper, catering clean-plate, meeting carbon-neutrality quantification
After the event, one click produces an emissions and offset note — the part MICE customers most readily pay for
Scenic and cultural tourism
Hybrid- Scene increment
- Annual, visit and time-window ticket rules; visitors are often not real-name — ticket number or mobile as the key
- Carbon acts
- Green-travel arrival, on-site shuttle vs driving, paperless ticketing
Connect to the existing ticketing system rather than replace it; the card is identity and entitlements only
Construction sites
Funds type- Scene increment
- Real-name and attendance are hard regulatory requirements; people turn over fast, with large daily in/out change
- Carbon acts
- Site-canteen clean-plate, electric plant charging, commute shuttle vs driving
Positioned as reporting into the housing-construction real-name platform — not a substitute for the supervisory system
Logistics and warehousing
Hybrid- Scene increment
- The vehicle is the principal, not the person; plate is the key identifier; 24-hour ops with no fixed shifts
- Carbon acts
- NEV truck charging, electric forklift charging, driver rest-area energy
Driver life services (rest, shower, laundry) on the card are the differentiator
Research institutes
Funds + carbon- Scene increment
- Highly isomorphic with universities; extra need for lab safety access and shared large-instrument timing
- Carbon acts
- High-power lab equipment standby, canteen clean-plate, green commute
If the customer strongly needs instrument billing and hazardous-chemical control, that should be a separate module — not stuffed into the card
University science parks
Hybrid- Scene increment
- Enterprises move in and out often; shared-resource quotas (meeting rooms, pitch halls, desks) matter more than spend
- Carbon acts
- Shared space vs private offices, green commute, shared equipment
Entitlement quotas first — unlike industrial parks, where funds spend is the centre of gravity
Asset sharing and reuse
Identity + entitlements only- Scene increment
- The object is a physical asset, not a service; return and status flow required; tightly coupled to the asset ledger
- Carbon acts
- Reuse vs new purchase, lifecycle method; per-item abatement is material
The light scene with the strongest carbon story: one reused device avoids a full-lifecycle new-purchase emission
Malls and complexes
Hybrid- Scene increment
- Customer side already has a mature membership system; the card only overlays carbon. Staff side is the funds scene
- Carbon acts
- Green travel to store, paperless receipts, bring-your-own cups, reuse / recycling campaigns
Do not sell “a smart card”. Sell a “mall carbon-benefit membership layer”, and connect the local official carbon-benefit platform
Scenes that do not need an independent card form
These only need carbon-event reporting or identity recognition on top of an existing system — no card issuance or account stack.
Ingest travel-type carbon events
Existing charging systems report carbon events
Third-party platform data connect
Merchant-end redemption code; no card issuance
Temporary access codes only
When a scene should upgrade to full delivery
If any one holds, upgrade to Tier 1 and deliver as a dedicated pack:
Needs new database tables or a new backend service
Needs a new account type (beyond funds, entitlements, carbon)
Has hard industry regulation that needs dedicated compliance design
Has a signed customer whose demand density exceeds a light template
Needs an independent front-end app
Which layer is your scene?
Tell us the scene and population scale. We will propose a delivery layer, a pace and the first carbon handle.