Skip to content

Main content

Historical Unit Echelon Source Code

Qualify an explicit historical unit-echelon code by source without mapping current organization or operations.

Loading tool…

Description

Qualify an explicit historical unit-echelon code by source.

Historical and noncombat logistics records connect source conventions, museum dimensions, relief supplies and recorded service dates. A stock residual or nominal portion count is bookkeeping, while a scale factor describes supplied exhibit geometry. These limited quantities do not verify historical identity, suitable shelter capacity or protective performance.

Qualify an explicit historical unit-echelon code by source.

When to use this tool

Use Historical Unit Echelon Source Code when you already have recordId, suppliedEchelonCode, historicalSource and need to qualify an explicit historical unit-echelon code by source.

How to use the tool and how it works

  1. Enter recordId, suppliedEchelonCode, historicalSource. 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 recordId, suppliedEchelonCode, historicalSource 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
recordIdRecord IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedEchelonCodeSupplied Echelon CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
historicalSourceHistorical SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordId": "R17",
    "suppliedEchelonCode": "EC2",
    "historicalSource": "Archive A"
  },
  "output": {
    "token": "[\"R17\",\"EC2\",\"Archive A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without mapping current organization or operations. 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

Reconcile original historical records and physical inventories, and inspect dimensioned museum or shelter plans when relevant. Use complete logistics and site requirements for an actual allocation; local counts and margins are individual record components.

References

  1. Calculation and input contract: military-science/historical-unit-echelon-source-code — tool.io

Similar or alternative tools