# SICK TiM5xx at Waldkirch: deployment

Canonical ID: `77ea6051-648f-4ac9-8e6d-2cb67fc3b0a8`

Aggregate deployment of SICK TiM5xx across factory automation and mobile robots.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-07_

- **Slug:** sick-tim5xx-hq-aggregate
- **Status:** operational
- **Model:** [SICK TiM5xx](/models/sick-tim5xx.md) (id: `80083928-12b0-4dc6-b2b6-6c0d8080f266`)
- **Company:** [SICK](/companies/sick.md) (id: `0a5344d3-7994-4a51-b2e2-ce123a22d2b3`)
- **Location:** [Waldkirch](/locations/waldkirch-germany.md) (id: `7d72f73c-cc94-4420-a265-12bd4af2b4dd`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.sick.com/

## Common questions

### What is the SICK TiM5xx deployment at Waldkirch?

SICK TiM5xx, built by SICK, is recorded as a deployment at Waldkirch on the DEPLOY registry. SICK operates the deployment directly.

### Who operates SICK TiM5xx at Waldkirch?

SICK, the manufacturer of SICK TiM5xx, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the SICK TiM5xx deployment at Waldkirch?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/77ea6051-648f-4ac9-8e6d-2cb67fc3b0a8 · feeds: GET /v1/feeds?deploymentId=77ea6051-648f-4ac9-8e6d-2cb67fc3b0a8 · canonical URL: /deployments/sick-tim5xx-hq-aggregate_