Skip to content

Main content

Biosafety Equipment Service Date

Preserve an explicit equipment service-date record without specifying maintenance procedures or deciding readiness.

Loading tool…

Description

Preserve an explicit equipment service-date record.

Biosafety records distinguish required training, recorded completion, service labels, incidents and document versions. A false outstanding-training flag can mean training was not required, rather than competence being demonstrated. Supplied service-date text or permission assertions do not verify equipment readiness or authorize work.

Preserve an explicit equipment service-date record.

When to use this tool

Use Biosafety Equipment Service Date when you already have equipmentId, recordedServiceDate, serviceRecordId and need to preserve an explicit equipment service-date record.

How to use the tool and how it works

  1. Enter equipmentId, recordedServiceDate, serviceRecordId. 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 token. Use the output convention below.

Enter equipmentId, recordedServiceDate, serviceRecordId using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
equipmentIdEquipment IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
recordedServiceDateUnparsed literal date text in a record, not calendar-validated or checked for service readiness.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
serviceRecordIdService Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "equipmentId": "EQ17",
    "recordedServiceDate": "2026-11-01",
    "serviceRecordId": "SR2"
  },
  "output": {
    "token": "[\"EQ17\",\"2026-11-01\",\"SR2\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without specifying maintenance procedures or deciding readiness. Sources and asserted relationships are not independently authenticated.
  • 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.

Alternative or Complementary methods

Check controlled training, equipment, incident and authorization records through the established safety process. Use appropriate professional assessment for actual work; local status logic and record formatting do not validate containment, competence or operating conditions.

References

  1. Calculation and input contract: biosafety/biosafety-equipment-service-date — tool.io

Similar or alternative tools