Logistics, Warehousing & Yards

An internal delivery target is often more specific than a building or loading dock. Text labels, rack/bay naming schemes, or human-specific instructions.

The delivery order can include the receiving footprint instead of stopping at a site address. A driver, operator, or compatible automated system can recover the same destination. A point identifies a simple position, a rectangle adds extent and orientation, and a height-aware point distinguishes vertically separated targets. The spatial reference complements the delivery order and the local operating instructions.

Scenarios and variations

• Receiving footprints beyond the building or dock.
• Internal delivery and pickup destinations.
• Oriented handoff areas shared with logistics partners.

Many industrial targets are regular floor or pad footprints, not arbitrary polygons. CAD layers, warehouse drawings, or point markers with surrounding metadata.

A storage assignment can carry the bounded floor area allocated to the goods. Regular footprints are represented by rectangles or squares; a polygon can describe a less regular yard section. The same geometry can travel between a warehouse plan, an operator instruction, and a partner message. Later volume references can extend the handoff when stacking height becomes part of the target.

Scenarios and variations

• Regular floor-storage footprints.
• Temporary material-staging pads.
• Container-aligned yard blocks and irregular yard sections.

Containers, cargo positions, and storage pads are often regular footprints with orientation, not arbitrary polygons or informal labels. Point markers, CAD overlays, and metadata strings that leave the footprint implicit.

A footprint reference can state the orientation and occupied surface of a cargo position. This makes a handoff more explicit than a center point accompanied by dimensions in free text. Operators can attach it to loading instructions or a yard allocation. A later volume geometry can also carry height, while the cargo identifier, load properties, and handling requirements remain separate business information.

At a container terminal, the horizontal slot alone does not distinguish containers stacked above one another. A 3D point can identify a reference position in a container on the fifth tier using its actual vertical position. The tier label can accompany the SRL in the terminal's own numbering convention. A later 3D volume could also describe the container's full extent and orientation; the container number remains the asset identifier.

Scenarios and variations

• Oriented container and cargo footprints.
• Swap-body, trailer, truck, and bus placement areas.
• Loading positions and container-stack abstractions.
• A container in the fifth tier of a stack at a container terminal.

A port crew or logistics partner needs the exact vehicle slot, row section, or handoff footprint within an export yard, rather than the port's general address. Yard-local slot labels, screenshots, phone calls, and instructions that must be interpreted inside a separate local yard system.

A compact reference can travel with the shipment order from the vehicle sender to the port crew and onward logistics partner. A point identifies the intended position, a rectangle adds the handoff footprint, and a polygon identifies a larger yard section. Recipients can recover the geometry even when they do not use the same yard-local slot labels or internal map.

Scenarios and variations

• An individual vehicle slot in an export yard.
• An oriented handoff footprint with an entry edge where applicable.
• A row section or larger yard area.

The real target may be the stored product or product pack inside a container or storage position, which demands true local 3D addressability. Shelf metadata, bin identifiers, scanner workflows, or human interpretation of the surrounding storage system.

The complete target is the product or product package inside a storage container, with that container located in a high-bay warehouse. A useful reference must therefore resolve the local position within the container as well as the position in the storage environment. The planned precision path adds explicit dimensions and oriented 3D placement. Full spatial orientation is a further extension beyond the first rotation-around-vertical approach.

Scenarios and variations

• An individual product or product package inside a container or box.
• The container at a position within a high-rack warehouse.
• Rack, shelf, pallet, and storage-bin references.
• Precise local product position, dimensions, and 3D orientation.

Precise package-volume addressing and full 3D orientation are in development. Current height-aware points and footprints provide related references, but do not already deliver centimeter-class product placement.

The operational target is often the precise line-adjacent handoff point, not simply a room or building reference. Station names, line codes, and local conventions that do not travel across software systems.

A material instruction can specify the actual line-side handoff position, with a footprint or height reference when needed. This helps the destination remain meaningful when it moves between production planning, logistics, and external service providers. The SRL accompanies the part number and work order; it identifies where the material is needed, while process and sequencing information stay in the production system.

Scenarios and variations

• Conveyor and production-line handoff positions.
• Material-flow destinations.
• Final consumption-point references for parts and consumables.

Industrial RTLS/RFID, MES/ERP, edge analytics, and AI workflows need a portable way to attach spatial context to assets, orders, geofence events, inference results, alerts, and audit logs. Vendor-local object IDs, factory-layout coordinates, geofence definitions, event payloads, CAD/GIS references, or application-specific metadata that do not travel cleanly between systems.

Existing positioning and identification systems can supply observations that an integration represents as SRLs. A compact location or geometry token can then accompany an order, event, or analysis result across software boundaries. The receiving system gains spatial context without requiring the originating vendor's local identifier or full factory-layout model. The asset and event retain their own identities.

Scenarios and variations

• Spatial context from RTLS, UWB, RFID, or machine vision.
• Portable references for assets, materials, tools, and replacement parts.
• Locations attached to orders, geofence events, AI results, and alerts.
• Shared context between production, warehouse, edge, and analytics systems.

This is an integration pattern, not a delivered connection to a particular RTLS, RFID, or industrial software product.

A construction-site address can remain the same while the actual unloading destination changes as work progresses. Drivers receive updated screenshots, phone directions, and site-specific descriptions.

The site team selects the intended unloading area and attaches its SRL to the delivery instruction. A separate route reference can describe the approved approach supplied by the operator. The driver and site contact then discuss the same spatial target. The instruction must still state when it applies; a fixed geometry reference does not automatically update as the construction schedule changes.

Scenarios and variations

• Changing construction unloading areas.
• Temporary material-staging footprints.
• Supplier access paths and delivery handoff positions.

A charging-site address may not identify the intended bay, vehicle orientation, or connector position for a commercial vehicle. Drivers and dispatch rely on site diagrams and local bay labels.

A logistics instruction can identify the bay footprint and the relevant connection point as separate spatial references. The footprint provides the intended orientation and occupied surface; the point identifies the physical connection location. Charging availability, connector compatibility, reservations, and electrical operation remain the responsibility of the charging system and site operator.

Scenarios and variations

• Truck and bus charging placement footprints.
• A separate physical connector or connection point.
• Orientation-sensitive access to a designated charging position.