These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Theme Park Management
- Data model and import order
The tables behind Theme Park Management
Theme Park Management ships with 11 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 11
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Events and capacity:
Events, Venues. Operating events with venue and capacity.
Ride readiness:
Ride readiness. Ride sessions checked and released per event.
Admissions and gates:
Admissions. Tickets reserved and admitted per event.
Payments and refunds:
Payment evidence. Provider payment events per event.
Review and evidence:
Review decisions, record attachments. Decisions and inspection files.
Operations and people:
Operation receipts, Organizations, team members, Users.
Every table, by feature
- Events and capacity3
- Ride readiness4
- Admissions and gates3
- Payments and refunds3
- Review and evidence4
- Operations control2
- Shared and settings1
- Events
Park operating events with capacity, lifecycle and revision control.
Linked to Team members, Venues, Organizations - Venues
Park venues and operating sites eligible for events.
Linked to Organizations - Organizations
Park operating organizations with time zone and currency scope.
- Ride readiness
Ride operating session readiness records supporting reviewed release.
Linked to Events, Organizations - Record attachments
Inspection and operating evidence files attached to an event.
Linked to Events, Team members - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Events, Team members - Events
Park operating events with capacity, lifecycle and revision control.
Linked to Team members, Venues, Organizations
- Admissions
Guest admission lines reserved and admitted against an event.
Linked to Events - Events
Park operating events with capacity, lifecycle and revision control.
Linked to Team members, Venues, Organizations - Payment evidence
Provider payment events reconciled against event admissions.
Linked to Events
- Payment evidence
Provider payment events reconciled against event admissions.
Linked to Events - Events
Park operating events with capacity, lifecycle and revision control.
Linked to Team members, Venues, Organizations - Admissions
Guest admission lines reserved and admitted against an event.
Linked to Events
- Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Events, Team members - Record attachments
Inspection and operating evidence files attached to an event.
Linked to Events, Team members - Events
Park operating events with capacity, lifecycle and revision control.
Linked to Team members, Venues, Organizations - Team members
Park staff with organization membership and platform identity.
Linked to Organizations, Users
- Operation receipts
Durable receipts for guarded operations with stable operation keys.
Linked to Events - Events
Park operating events with capacity, lifecycle and revision control.
Linked to Team members, Venues, Organizations
Keys and references
Readiness records, admissions, payment events, decisions, attachments and operation receipts reference their event. Events reference venue, owner and organization. Team members link to user accounts. Keep event record numbers, venue codes and provider event identifiers stable and import by them.
Migration order
- Load Organizations, Users and team members.
- Load Venues with codes, contacts and notes.
- Load upcoming Events with capacities.
- Load sold Admissions for those events and verified payment evidence.
- Reconcile sold tickets with your ticketing system and test permissions before go-live.
Set up Theme Park Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.