Skip to content

Main content

Biosecurity Incident Report Clock Offset Tool

Normalize supplied benign incident-record timestamps to an explicit common clock reference.

Loading tool…

Description

Return incident/report times on a reference clock and their lag.

Biosecurity administration records training assertions, custody, access purposes, inventories and document handling. Local counts, time checks and permission predicates describe supplied metadata; they do not authenticate people or items, enforce access or establish actual protective conditions.

Return incident/report times on a reference clock and their lag.

When to use this tool

Use Biosecurity Incident Report Clock Offset when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter eventTime, reportTime, eventOffset, reportOffset. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read eventReference, reportReference, lag. Use the output convention below.

Return incident/report times on a reference clock and their lag. eventReference = eventTime-eventOffset, reportReference = reportTime-reportOffset, lag = reportReference-eventReference.1

Input fieldMeaning and unitsAccepted input
eventTimeEvent TimeRequired. Finite number.
reportTimeReport TimeRequired. Finite number.
eventOffsetEvent OffsetRequired. Finite number.
reportOffsetReport OffsetRequired. Finite number.
Output fieldInterpretationReturned shape
eventReferenceEvent ReferenceRequired. Finite number.
reportReferenceReport ReferenceRequired. Finite number.
lagLagRequired. Finite number.
json
{
  "input": {
    "eventTime": 100,
    "reportTime": 110,
    "eventOffset": 2,
    "reportOffset": -1
  },
  "output": {
    "eventReference": 98,
    "reportReference": 111,
    "lag": 13
  }
}

Limitations and assumptions

  • Signed lag is retained; no actual incident, synchronized clock, timely reporting duty or response adequacy is verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Verify actual records, permissions and conditions through the responsible organization's procedures; use qualified risk assessment and appropriate professional oversight for practical decisions.

References

  1. Calculation and input contract: biosecurity/biosecurity-incident-report-clock-offset — tool.io

Similar or alternative tools