Conservation Treatment Backlog Aging Days Calculator

Retain closed service time versus right-censored open backlog age with explicit status, rather than age every completed object to today; zero maximum means no open records.

Description

Completed treatment records have a closed service duration.

Completed treatment records have a closed service duration. Open records instead have an age observed through an as-of date.

Retain closed service time versus right-censored open backlog age with explicit status, rather than age every completed object to today; zero maximum means no open records.

When to use Conservation Treatment Backlog Aging Days Calculator

Use this tool to retain closed service time versus right-censored open backlog age with explicit status, rather than age every completed object to today; zero maximum means no open records.

Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.

How to use Conservation Treatment Backlog Aging Days Calculator and understand its results

  1. Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
  2. Enter enqueuedDayOrdinals, completedFlags, completionDayOrdinals, asOfDayOrdinal using the field table and calculation rules, then run the tool.
  3. Read observedBacklogAgesDays, openBacklogCount, maximumOpenBacklogAgeDays. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
Input fieldMeaningValue type; see rules belowRequirement
enqueuedDayOrdinalsEnqueued day ordinalslist of numberRequired
completedFlagsCompleted flagslist of numberRequired
completionDayOrdinalsCompletion day ordinalslist of numberRequired
asOfDayOrdinalAs of day ordinalintegerRequired

Align nonnegative integer day ordinals and binary completion flags. Require enqueue no later than as-of and completed dates between enqueue and as-of. Return ages, open count and maximum open age; zero maximum means no open records.1

Paired lists must be nonempty and have equal lengths.

age = (completion if closed, otherwise as-of) − enqueue ordinal

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output fieldMeaningValue type
observedBacklogAgesDaysObserved backlog ages dayslist of number
openBacklogCountOpen backlog countnumber
maximumOpenBacklogAgeDaysMaximum open backlog age daysnumber
json
{
  "input": {
    "enqueuedDayOrdinals": [
      10,
      20
    ],
    "completedFlags": [
      0,
      1
    ],
    "completionDayOrdinals": [
      0,
      25
    ],
    "asOfDayOrdinal": 30
  },
  "output": {
    "observedBacklogAgesDays": [
      20,
      5
    ],
    "openBacklogCount": 1,
    "maximumOpenBacklogAgeDays": 20
  }
}

Limitations and assumptions

Open ages are right-censored and are not completed service times.

Numbers and computed results must be finite; overflow produces an error. Numeric lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Conservation Lab Annual Throughput Objects Estimate Calculator: Budget expected complete lab objects using caller productive hours and explicit complexity mix, not universal conservator-hour multipliers or a guaranteed integer mix allocation. For a complementary task, use Integrated Pest Monitoring Inspection Interval Scheduler: Schedule caller IPM inspection cadence from actual last events on continuous day ordinals, retaining overdue sign; no recommended monitoring interval or pest-free guarantee.

References

  1. Conservation Treatment Backlog Aging Days Calculator — tool.io

Similar or alternative tools

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