About
Version 0.9
Thorpe Nexus is a web application for managing the daily operations of THORPE PARK RESORT.
Code and design © copyright Laurence Summers 2015-2018. All rights reserved.
Browser compatibility
Full compatibility
Near-full compatibility
Nexus will work with the following browsers with very minor layout and functional inconsistencies:
Partial compatibility
Nexus may work with the following browsers with frequent layout and functional errors:
Limited to no compatibility
Nexus is unlikely to work on the following browsers meaning they should not be used:
Time calcuations
For speed and efficiency Nexus calculates some times and durations client-side, meaning it uses the clock on the computer accessing it to calculate dates and times. For this reason it is important to ensure your computer's
clock is up to date to at least within a few seconds. All automaticly generated times (i.e. server time) are converted to British local time (either GMT or BST depending on the time of year), manually entered times (e.g. call time) are not converted.
Incidents
Incidents are events that may disrupt the normal operation of the park. There are three types of incident, each with its own colour:
- Ride incidents include any unexpected ride closures
- Security incidents include any incident that poses a substantial security concern
- Medical incidents include all situations where someone is hurt or ill and the first aid team are required to attend
Incident types
Ride incidents
Ride incidents are any incident involving the unplanned closure of a ride. They are grouped into three subtypes:
- STOP STOP STOPs are when a staff member has called for an emergency shutdown of a ride
- Shutdowns are when a ride has ceased operation unexpectedly
- Running closedowns are when a ride is being temporarily closed to perform an operational task
Security incidents
Security incidents are any incident posing a significant security risk or one requiring an urgent response from the security team. They are categorised by their codes.
Medical incidents
Medical incidents are any where someone is ill or injured and a response from the first aid team may be required; they are categorised by their triage (the potential severity of the illness/injury based on the information given by the caller):
- Prealert means the first aid team have been called for but the incident is not yet triaged
- Red1 means a possible immediate threat to life
- Red2 means a potential threat to life
- Amber means a minor emergency that should not be life-threatening
- Green means a very minor problem
After being triaged medical incidents are further separated into subcategories depending on the nature of the problem.
Incident fields
All incidents share the following fields, which are shown on various pages:
- Incident ID - the reference ID of the incident, which is simply the date and time (to the second) the incident was created (this is different from the call time and the database incident ID)
- State - whether the incident is currently ongoing (ACTIVE) or has been resolved (CLEAR)
- Location - where the incident is taking place (for ride incidents, this is the attraction that is closed)
- Status - the current stage of the incident, which varies depending on the inident type - see below
- Units - the short callsigns of units in attendance
- Update history - a list of every change to the incident saved
- Call time - the time control was notified and/or represents the start of incident
- Scene time - the time the first unit to arrive was at the scene of the incident
- Clear time - the time the incident was resolved
Ride fields
- Shutdown type - the type of ride/maze closure, see above
- Shutdown cause - the general cause of the incident
- Position - where applicable, the train/car/boat etc. position the ride stopped in
- Ride clear time - the time the ride was cleared of guests (sets to current time if "CLEAR" is entered in position field)
- Code/problem - the radio code applicable to the incident or a brief description of the problem
- Queueline evacuated (checkbox and times) - whether the queue was cleared of guests and the start/finish time
- Details - specific notes/comments for the incident
- DDM acknowledgement (checkbox and time) - whether a DDM has acknowledge the radio call at what time
Security fields
- Code - the radio code applicable to the incident
- Reported by - the individual or location that repoted the incident
- Information - specific notes/comments for the incident
- Bodycam activated - a unit's bodycam was turned on
- Physical intervention - a unit used physical force
- Handcuffs deployed - a unit used handcuffs
- Number detained/searched/offsite/arrested - the number of individuals whom the corresponding actions was taken against
- Police call time - the time the police were called (if applicable)
- Police scene time - the time the police were on scene (if applicable)
Medical fields
- Triage - the apparent potential severity of the incident - see above
- Condition category - the generic category of the patient's problem
- Age/sex - the age and sex of the patient, or approximate age if not known
- Presenting complaint - the signs and symptoms of the patient
- Responder notes - specific non-medical notes/comments for the incident
- Ambulance call time - the time an ambulance was called (if applicable)
- Ambulance scene time - the time the an ambulance was on scene (if applicable)
Incident summaries
Incidents are summarised using key fields depending on their type, this can be on one line or several short lines:
- Ride incidents: Shutdown type - shutdown cause
- Security incidents: Radio code
- Medical incidents: Triage - age/sex - condition category
Age/sex summaries are an abbreviation of the age and sex fields. If the age is known, it is represented as the age, age type (first letter of year/month/week/day) followed by 'old' ("O") and sex (first
letter of sex). For example, "25YOM" means "25 Year Old Male". If the age is not known, the approximate age and sex is shown, e.g. "Adult Male". If no details are known, simply "Unknown age/sex" is displayed.
Statuses
The status is the current stage of an incident, which varies depending on the type. An incident's state (ACTIVE or CLEAR) depends directly on its status. Statuses available for all incidents are:
- Waiting - no action has yet been taken (this is when the incident is either brand new or there are no available resources to respond with)
- En route - a unit is on the way to the incident but has not yet arrived
- On scene - a unit is on scene
Ride statuses
- Attendance not required - the incident can be resolved without a unit attending but the incident is still active (e.g. essential cleaning)
- Clear - the incident has been resolved
- Clear (no attendance) - the incident has been resolved without a unit attending and is now clear (e.g. essential cleaning)
Security statuses
- Returning to Code 8 - the parties invovled are being escorted to Code 8
- Returning to Code 8(2) - the parties invovled are being escorted to Code 8(2)
- In Code 8 - the parties invovled in Code 8
- In Code 8(2) - the parties invovled in Code 8(2)
- Escorting from park - the parties invovled are being escorted out of the park
- Police to scene - the police have been called to the scene of the incident
- Police to Code 8 - the police have been called to Code 8
- Police to Code 8(2) - the police have been called to Code 8(2)
- Police on scene - the police are at the scene
- Police at Code 8 - the police are at Code 8
- Police at Code 8(2) - the police are at Code 8(2)
- Leaving with police - the parties involved have been taken into custody and left park
- Left by police - the parties involved have been left on site by police
- Removed from park - the parties have been escorted from the park
- Stood down - the incident has self-resolved or security are no longer required
- Clear - the incident has been resolved
Medical statuses
- Discharged - the patient has been treated and discharged at the scene
- Returning with - the patient is being taken back to the First Aid Centre and is unlikely to require escalation
- Escorting to First Aid Centre - the patient is being taken back to the First Aid Centre but may require escalation (i.e. ambulance)
- Ambulance to scene - an ambulance has been called to the scene of the incident
- Ambulance to First Aid Centre - an ambulance has been called to the First Aid Centre
- Ambulance on scene - an ambulance is on scene
- Ambulance at First Aid Centre - an ambulance is at the First Aid Centre
- Leaving on ambulance - the patient has been taken to hospital on an ambulance
- Discharged by ambulance - the patient has been assessed by the ambulance service and not taken to hospital
- Hear and treat - the patient has been advised over the phone or instructed to make their own way to the First Aid Centre
- Stood down - the incident has self-resolved or first aid are no longer required
Map Colours and Icons
The live maps in Nexus use colour coding to help quickly identify types of incidents.
Bright red markers indicate a serious incident. They include Code Reds, STOP STOP STOPs, confirmed fires, Code 9s and Red1s.
Icon Symbols
Code red - catastrophic event
Code yellow - confirmed fire
Ride Icons
Routine ride incidents are dark orange. The code number denotes the type of incident, for those without a code S/D means shutdown, RCD means running close-down (generic ride incidents are marked with "RID").
Security Icons
Routine security incidents are navy blue. The code number denotes the type of incident (generic security incidents are marked with "SEC").
Medical Icons
Medical icon colours match the triage level of the call. The triage is determined by either Foxtrot 1 or the auto-triage based on the information provided by the caller - for safety the worst case scenario is always assumed until proven otherwise.
The call triage system is a guide only.
Red1 - possible threat to life, immediate response required.
Red2 - possible threat to life but less likely to be serious, immediate response required but can be stood down for a Red1.
Amber - minor emergency, may cause park disruption but unlikely to be life-threatening. Urgent response required but can be stood down for a Red1 or Red2.
Green - first aid only, very unlikely to cause park disruption. Response may be required but can be stood down for a Red1, Red2 or
Amber.
Prealert - a call has been made to this location but has not yet been triaged.
Displays
Displays are versions of the live information pages that are designed to be shown full screen.
The information pages display various current information about the park's operations.
Park status
The park status page provides a snapshot of the park's current state including ride uptimes.
Ride uptimes are calculated by diving the total time of all closures (including late-cardings) by the maximum possible uptime. A colour is then applied to the result percentage based on its value:
- 95% and above
- 90%-95%
- 85%-90%
- Below 85%
If a ride is currently having an unscheduled closure, its name will change colour to match the
incident type.
The gate figure information page shows the gate figures for today and plots them onto a graph.
Daily duty managers
The DDM page provides list of the department managers and special callsigns that are currently signed on. Each short callsign is listed with the corresponding department (or for special callsigns the description) underneath. The name of the manager
currently signed on, their callsign and when they signed on is below.
If no DDM for that callsign has signed on then "not signed on" will display in red. For managers that have signed off "signed off" in grey will show with their callsign and the time they signed off.
Logs
Logs are the event records for the day's normal operations and routine events. Information pages can also be edited from this section, e.g. duty manager sign-ons. The logs are intuative to use and largely self-explanatory.
Archives
Archives retrieve incidents, logs and information from previous dates. The incident archives allows for filtering of incidents by fields.
Advanced users only: setting the date to a day in the future allows entries to be added ahead of time, e.g. entering all the park opening hours for the season.
Archive search
The archives can be searched to retrieve incidents that match a given cretieria. Please note the time to fetch results will vary depending on the search parameters.
Advanced users only: certain fields are RegEx sensitive.
Data trends and analysis
Trends are a collection of pages that analyse incidents and other information:
- Incident times - organises data based on the time of day the incident commenced (the call time), i.e. when incidents are occuring
- Incident durations - organises data based on a chosen length of time:
- Response time - the time for a unit to arrive on scene
- On scene time - the time spent on scene until the incident was cleared
- Total duration - the total time for the incident
Trend options
There are various options for analysing trends data, most of which is self-explanatory.
For incident trends, data can be filtered by date and call time, however these fields are independent; i.e. a time range of 10:00-18:00 will only find incidents that occurred in the date range between
10:00 and 18:00. An incident occuring at 23:00 will not be shown in this example, even if it is between the dates given. To see all incidents, set the time from to the same as the time to, e.g. midnight to midnight.
System settings
Map settings
The map used by Nexus will require updating as the physical layout of the park changes with time. This has been made easy with the map settings page.
Uploading a map
To upload a map simply select a new image file, enter a name and any applicable notes and click "create". The upload will be complete when you are redirected to the map edit page.
Map file types
Any standard web image file can be used for the map image (list below). To keep load times low a maximum file size of 3mb is reccomended.
- *.png (reccomended)
- *.svg
- *.jpg
- *.bmp
Map edit
The edit map page will guid you through the process of calibrating a new map to best match the current locations. To toggle locations click the marker button in the top-right hand corner. The steps are:
- Initial width - default 1000px (this is not the width of the image file); if the new map covers a larger geographical area than the old one, the initial width will need altering
- Position offset - default 0/0; if the new map covers a larger geographical area than the old one, the new map will need an x/y offset to compensate
- Max zoom out - the maximum zoom out level
- Initial zoom - the zoom level when the map is first loaded
- Default centre - the custom centre of the map to focus on when the crosshair button is clicked
- Details - the name and comments of the file
Colours
Nexus uses several colours to convey various meanings (some colours are shared but do not conflict on individual pages):
Incident colours
- Dark orange relates to ride incidents
- Navy blue relates to security incidents
- Green relates to medical incidents
Incident state colours
- Bright red means active
- Green means clear
Data colours colours
- Bright red indicates a serious event or value
- Dark red indicates a moderate event or value
- Amber indicates a mild event or value
- Green indicates a nominal or non-serious event or value
Shortcuts
For ease of use the following keyboard shortcuts have been added:
- Insert the current time in blank time fields with the spacebar
- Submit a form with return (for security reasons this is not enabled in all fields)
Colour list
- Red1 (triage) #ff0000
- Stop stop stop #ff0000
- Severe security event #ff0000
- Serious value/statistic #ff0000
- Red 2 (triage) #cf000f
- Moderate security event #cf000f
- Moderate value/statistic #cf000f
- Amber (triage) #f1c40f
- Ride incident/related #e87e04
- Security incident/related #2980b9
- Medical incident/related #27ae60
- Green (triage) #27ae60
Libraries
Nexus utilses the following high-quality libraries for ease of function: