Skip to content

Transport management (TMS)

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: API (the vendor’s response payloads) · type tms

What it is

A transport management system of record, read over REST. In the test estate it holds loads, with the planned route of each. The connector reference is Logistics systems of record.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typetms
Settingsbase_url, provider
Credentialsapi_key

The test connection

Transportation management

SettingTest value
base_urlhttps://tms.quillmere.invalid/api
providergeneric_rest

Credentials: api_key. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download tms.zip and unzip it. It holds paginated REST responses in a generic shape, and expected.json. These types are for a customer’s own systems of record, so no vendor is imitated.
  2. There is no system to stand up from this bundle. Load the records into the system of record you want to test against, or open them next to expected.json.
  3. Add the connection with the settings above, pointed at that system’s base URL.

What FACE finds

FACE fetches these records over its logistics REST connector, which pages through the system’s resource. It reads no catalogue, so the expected model is the record shape.

DatasetKindDomainPrimary keyRowsFields
loadsrest_resourceshipmentsload_id2415

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 5 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
carrierloads.carrier_idd365, document, files, guidewire, mysql, objectstore, postgres, redshift, sharepoint, yms
loadloads.load_idonly here
shipmentloads.shipment_refbigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, whs, yms
trailerloads.trailer_idcctv, databricks, document, excel, iot, kafka, mqtt, postgres, servicenow, yms
warehouseloads.origin.warehouse_idinventory, oms, postgres, redshift, whs, yms

Evidence it holds for the planted anomalies:

  • ANOM-5, A GPS route deviation. tms/api_loads.json in tms.zip, look for "shipment_ref": "SHP-50021" (planned route polyline).

See all connectors at once for the walkthrough across every source.

Download

  • tms.zip: 2 files, expected.json included.

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • tms/api_loads.json
  • tms/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.