Elevator Traffic Handling Calculator

Observed elevator fleet service equivalents over caller peak interval, fractional equivalents not actual boarded people or lift code capacity. Caller independently establishes units, regime, calibration and applicability; this does not establish design-code compliance, authenticity, operational safety, treatment efficacy or a validated forecast.

Description

Elevator handling estimates combine usable car loading, available cars and round-trip time.

Elevator handling estimates combine usable car loading, available cars and round-trip time.1

Passenger-equivalent throughput is a continuous scenario estimate rather than an integer dispatch simulation. Use Elevator Traffic Handling Calculator to evaluate the supplied inputs under the specific model below.

When to use Elevator Traffic Handling Calculator

Use Elevator Traffic Handling Calculator to evaluate the supplied inputs under the specific model below. Establish the units, measurement scope and applicable model or recipe assumptions before entering values.

How to use Elevator Traffic Handling Calculator and understand its results

  1. Establish the units, measurement scope and applicable model or recipe assumptions before entering values.
  2. Enter Caller observed round trip seconds, Caller usable car passengers, Caller available cars, Caller peak interval seconds using the field table and validation rules below, then run the tool.
  3. Read Interval handling passenger equivalent and interpret units, signs, ordering and placeholders as explained below.
  4. If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
Input fieldMeaningValue typeRequirement
callerObservedRoundTripSecondsCaller observed round trip secondsnumberRequired; constraints below
callerUsableCarPassengersCaller usable car passengersnumberRequired; constraints below
callerAvailableCarsCaller available carsnumberRequired; constraints below
callerPeakIntervalSecondsCaller peak interval secondsnumberRequired; constraints below

Enter a strictly positive observed round-trip time in seconds and nonnegative usable passenger load, available car count and interval duration in seconds. Multiply load by car count and interval, then divide by round-trip time. These inputs can be fractional, including the car count; the output is passenger-equivalent throughput rather than an integer passenger dispatch schedule.

handlingEquivalent = usableLoad×availableCars×intervalSeconds/roundTripSeconds

Field order, units and branch conditions follow the implementation explanation above.

Output fieldMeaningValue type
intervalHandlingPassengerEquivalentInterval handling passenger equivalentnumber
json
{
  "input": {
    "callerObservedRoundTripSeconds": 120,
    "callerUsableCarPassengers": 10,
    "callerAvailableCars": 3,
    "callerPeakIntervalSeconds": 300
  },
  "output": {
    "intervalHandlingPassengerEquivalent": 75
  }
}

Limitations and assumptions

Passenger-equivalent throughput is a continuous scenario estimate rather than an integer dispatch simulation. Apply the exact scope and assumptions described above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.

Alternative or Complementary methods

Use Evacuation Time Calculator for a related task: An evacuation scenario combines detection, premovement, travel and exit-service times.

Use Elevator Round-Trip Time Calculator for a related task: A round trip includes travel and stop service as well as terminal activity.

References

  1. Elevator Traffic Handling Calculator — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies