Industrial parks and enterprises · Hybrid

Industrial parks and enterprises

One park, N enterprises: multi-organisation books, shift limits and cross-tenant canteen

Multi-enterprise split booksShift spend limitsContractor visitor passes
Back to the zero-carbon smart card solution
Scene position

The hard part of a park card is “books must land on the enterprise”

Canteens and facilities are provided by the park operator; users belong to different enterprises. Multi-organisation books are the scene’s standing point.

Principals
Park operators, factories, tenant enterprises
Account shape
Hybrid (spend + membership entitlements)
Delivery layer
Tier 1 full delivery
Core capability
Multi-organisation membership and split books
Industrial parks and enterprises
People and roles

Park and enterprise are two buyers

The park operator buys utilisation and leasing attractiveness; the enterprise buys staff welfare and management efficiency.

Park operatorFacility utilisation, merchant settlement, ancillary services they can pitch to tenants
Tenant HRStaff roster and welfare issuance; this enterprise’s spend reports
Enterprise staffCanteen, coffee, gym, parking and charging on one card
Factory front-lineMeals by shift; night shift not blocked by day windows
ContractorsTemporary access and meals; auto-expire when the project ends
Core capabilities

What park delivery must include

Multi-organisation and shifts are the two must-have park capabilities; the rest reuses platform commons.

Multi-organisation membership and split

One park, N enterprises; spend collected by enterprise; reports by enterprise

Cross-tenant canteen

Shared canteen; group-meal cost monthly by enterprise (in planning)

Shift spend limits

Meal windows and limits for three-shift; night shift has its own policy

Contractor visitor pass

Contractors and visitors issued by project cycle; auto-expire

Staff welfare issuance

Enterprises issue welfare quotas to their own staff, with usable-scope limits

Charging and parking link

Staff vehicle charging and parking entitlements, connected to the existing car-park system

Scene hard parts

Three practical park-project problems

These tend to explode late in implementation. Draw the responsibility boundary at proposal stage.

Who maintains the enterprise roster

The park cannot get staff lists; enterprises do not want frequent sync

Enterprises self-maintain their roster; the park manages organisation and authorisation

Who the bill goes to

Staff spend may be personal, enterprise-paid or park-subsidised

Personal + enterprise quota + park subsidy can combine and split

Enterprises move in and out

Tenant lifecycle is short

Organisation-level start/stop and archive; history reports stay intact

Carbon value

Park carbon data must split organisation-level and personal

An enterprise’s own abatement belongs in organisation accounting. Putting it in staff personal carbon accounts is double counting.

Green commute and shuttles

Access and vehicle ID

Shuttle-vs-drive abatement is counted on the enterprise side

Canteen clean-plate

Weigh stations

Personal incentive; participation rate is the key metric

Electric forklift and equipment charging

Chargers

Enterprise organisation-level accounting; not into personal accounts

Delivery boundary

What we do, and what we do not

Park scenes are easily expected to become a “park management platform”. Spell out the card’s range.

Delivered in this solution

  • Multi-organisation accounts and split
  • Shift limits and contractor visitor passes
  • Welfare issuance and merchant settlement
  • Staff-side carbon-act collection

Out of scope

  • No enterprise ERP or production management
  • No park leasing and lease contracts
  • No safety production or environmental monitoring
  • No substitute for the enterprise’s own HR

Want to see how this scene is actually delivered?

A demo walks the account, spend or entitlement write-off and the carbon board for this scene. You can also return to the solution overview to see platform capabilities.