{ "context": { "schemaVersion": "hyperion-buyer-decision-asset.v1", "assetId": "intralogistics-procurement-evidence-checklist", "title": "Intralogistics procurement: evidence before a fleet commitment", "buyer": "Warehouse operations sponsor, procurement lead, systems integrator and accountable product owner", "decision": "Is there sufficient configuration-specific evidence and a complete operating commitment to justify a controlled fleet rollout?", "gate": "launch", "mandateId": "product-decision-review", "lenses": [ { "lensId": "customer-operator-value", "question": "Which accepted moves, human baseline and operator workload define useful work at this site?" }, { "lensId": "business-model-economics", "question": "Which ownership, integration, recovery, service and exit costs determine cost per successful move?" }, { "lensId": "ai-data-evaluation-hmi", "question": "Which task, sensing, planning and HMI behaviors are evaluated under representative conditions?" }, { "lensId": "system-architecture", "question": "Which robot/fleet-control/software/map/interface versions and site constraints form the purchase scope?" }, { "lensId": "safety-governance-oversight", "question": "Who owns hazard, threat, data-rights, authority and conformity decisions for the complete system?" }, { "lensId": "operations-ecosystem", "question": "Who commissions, trains, monitors, recovers, supports, updates and retires each part of the operation?" } ], "preparedAt": "2026-09-06T00:00:00Z", "publicationStatus": "not_published", "humanReviewStatus": "not_recorded", "customerEvidence": false, "canonicalPath": "/resources/intralogistics-procurement-evidence-checklist" }, "sourceNotes": [ { "id": "vda-version", "title": "VDA 5050 version and archive", "publisher": "VDA", "url": "https://www.vda.de/en/topics/automotive-industry/vda-5050", "publishedAt": null, "retrievedAt": "2026-09-06", "provenance": "primary_reference", "note": "The current-version page identifies VDA 5050 version 3.0.0, March 2026. An exact implementation version is needed when comparing suppliers." }, { "id": "vda-scope", "title": "VDA 5050 version 3 specification", "publisher": "VDA", "url": "https://www.vda.de/dam/jcr:09f03b91-13e2-4db3-bf30-4f221710071b/VDA5050_EN.pdf", "publishedAt": "2026-03", "retrievedAt": "2026-09-06", "provenance": "primary_reference", "note": "The interface specification excludes safety requirements, traffic-management logic, external-IT/peripheral interfaces, acceptance procedures, operating responsibilities and cybersecurity mechanisms. Interface support cannot establish complete system readiness." }, { "id": "iso-open-metadata", "title": "ISO Open Data: ISO 3691-4 deliverables metadata", "publisher": "ISO", "url": "https://www.iso.org/open-data.html#iso_deliverables_metadata", "publishedAt": null, "retrievedAt": "2026-09-06", "provenance": "primary_reference", "note": "ISO's open dataset records ISO 3691-4:2023 edition 2, publication date 12 June 2023, current stage 90.92 (to be revised), and a draft successor at stage 40.20 with no publication date. Metadata alone does not establish applicability or conformity.", "openData": { "datasetUrl": "https://isopublicstorageprod.blob.core.windows.net/opendata/_latest/iso_deliverables_metadata/json/iso_deliverables_metadata.jsonl", "datasetSha256": "845b6901d66310a767e06abdf03d48f460768b01c732b42d9f3f9d837aca71f0", "datasetBytes": 79375500, "licenseName": "ODC Attribution License (ODC-By) v1.0", "licenseUrl": "https://opendatacommons.org/licenses/by/1-0/", "attribution": "Contains information from ISO Open Data's iso_deliverables_metadata dataset, available under the ODC Attribution License (ODC-By) v1.0. Only selected metadata fields are retained; no normative standard text is reproduced.", "records": [ { "id": 83545, "reference": "ISO 3691-4:2023", "publicationDate": "2023-06-12", "edition": 2, "currentStage": 9092 }, { "id": 88615, "reference": "ISO/DIS 3691-4", "publicationDate": null, "edition": 3, "currentStage": 4020 } ] } } ], "requests": [ { "id": "workflow-value", "gate": "strategy", "lensId": "customer-operator-value", "ownerRole": "Operations sponsor", "request": "Workflow map, alternatives and value thesis, including work kept with people", "acceptanceQuestion": "Which accepted customer outcome improves, for whom, and compared with what?", "holdCondition": "The proposal measures robot activity without an accepted customer outcome.", "status": "not_assessed" }, { "id": "human-baseline", "gate": "discovery", "lensId": "customer-operator-value", "ownerRole": "Site operations and operator representative", "request": "Observed baseline for attempted/accepted moves, waiting, errors and person-minutes under declared shifts", "acceptanceQuestion": "Are population, window, task difficulty and exclusion rules comparable?", "holdCondition": "No measured baseline or an incompatible denominator.", "status": "not_assessed" }, { "id": "economic-boundary", "gate": "strategy", "lensId": "business-model-economics", "ownerRole": "Product and finance owners", "request": "Acquisition, integration, infrastructure, licenses, energy, operator/recovery work, service, spares and exit cost model", "acceptanceQuestion": "Are benefit, supplier revenue and total cost separated and assumptions sensitivity-tested?", "holdCondition": "Payback omits material lifecycle costs or assumes all released time becomes cash savings.", "status": "not_assessed" }, { "id": "configuration", "gate": "productization", "lensId": "system-architecture", "ownerRole": "System architect and integrator", "request": "Named robot, software, controller, map, payload, battery, charger and peripheral versions with compatibility evidence", "acceptanceQuestion": "Does every supplied test apply to the ordered configuration?", "holdCondition": "A component or version differs without impact review and revalidation.", "status": "not_assessed" }, { "id": "operating-envelope", "gate": "productization", "lensId": "system-architecture", "ownerRole": "Site and system owners", "request": "Site survey covering traffic, floors, slopes, loads, people, connectivity, charging and exceptional conditions", "acceptanceQuestion": "Are intended use, foreseeable misuse, exclusions and change triggers explicit?", "holdCondition": "The proposed site falls outside the evaluated operating envelope.", "status": "not_assessed" }, { "id": "protocol-version", "gate": "productization", "lensId": "system-architecture", "ownerRole": "Fleet-control and robot suppliers", "request": "Exact VDA 5050 version plus supported message/action/error/factsheet/zone matrix and cross-vendor tests", "acceptanceQuestion": "Which optional features and breaking-version migrations are supported by both sides?", "holdCondition": "The only evidence is an unqualified supports-VDA-5050 statement.", "status": "not_assessed" }, { "id": "external-interfaces", "gate": "productization", "lensId": "system-architecture", "ownerRole": "Integrator and enterprise IT", "request": "WMS/MES/ERP, door, conveyor, charger and infrastructure interface contracts with failure behavior", "acceptanceQuestion": "What happens on duplicate, delayed, lost or out-of-order work requests?", "holdCondition": "Responsibility for an external interface or inconsistent task state is missing.", "status": "not_assessed" }, { "id": "task-evaluation", "gate": "productization", "lensId": "ai-data-evaluation-hmi", "ownerRole": "Product evaluation owner", "request": "Representative successful, failed, aborted and difficult-task results with acceptance criteria and denominators", "acceptanceQuestion": "Do evaluation slices cover actual loads, obstructions, traffic and sensor degradation?", "holdCondition": "A demonstration or isolated easy task is treated as shift-level evidence.", "status": "not_assessed" }, { "id": "recovery-authority", "gate": "productization", "lensId": "ai-data-evaluation-hmi", "ownerRole": "Operations and control authority", "request": "Failure detection, bounded retries, replan, safe stop, handback and restored-state evidence", "acceptanceQuestion": "Who can intervene, with what latency and fallback when unavailable?", "holdCondition": "Recovery ownership, restored task state or the human intervention path is untested.", "status": "not_assessed" }, { "id": "safety-case", "gate": "launch", "lensId": "safety-governance-oversight", "ownerRole": "Competent safety/conformity owners", "request": "Applicable product/system/site scope, exact standards editions, hazard assessment and verification artifacts", "acceptanceQuestion": "Who determines obligations and accepts residual risk for the complete installation?", "holdCondition": "Interface compliance or a supplier statement is substituted for system conformity and site assessment.", "status": "not_assessed" }, { "id": "cyber-updates", "gate": "launch", "lensId": "safety-governance-oversight", "ownerRole": "OT cybersecurity and product owners", "request": "Broker/network boundaries, identities, access, update signing, vulnerability handling, incident response and recovery plan", "acceptanceQuestion": "Which supplier owns each control and what evidence covers loss of communications or compromised components?", "holdCondition": "The communication standard is treated as a cybersecurity assurance mechanism.", "status": "not_assessed" }, { "id": "data-rights", "gate": "launch", "lensId": "safety-governance-oversight", "ownerRole": "Data owner and legal/privacy specialists", "request": "Permitted telemetry, camera data, retention, access, training reuse, location and exit arrangements", "acceptanceQuestion": "Is each use necessary, permitted and separable from optional supplier model training?", "holdCondition": "Rights are unknown, bundled without scope, or incompatible with site obligations.", "status": "not_assessed" }, { "id": "commissioning", "gate": "launch", "lensId": "operations-ecosystem", "ownerRole": "Named launch owner and integrator", "request": "Site readiness, installation, training, acceptance trials, defects, rollback and phased release plan", "acceptanceQuestion": "Who signs each acceptance decision and can stop or reverse rollout?", "holdCondition": "Payment or deployment milestones outrun unresolved acceptance evidence.", "status": "not_assessed" }, { "id": "duty-and-service", "gate": "scale", "lensId": "operations-ecosystem", "ownerRole": "Service and operations owners", "request": "Shift-length availability by cause, intervention/recovery rates, person-minutes and longest continuous useful duty", "acceptanceQuestion": "Are support capacity, response times, parts and escalation adequate for the intended fleet and sites?", "holdCondition": "Mean uptime hides excluded downtime or recovery work that scales beyond capacity.", "status": "not_assessed" }, { "id": "success-cost", "gate": "scale", "lensId": "business-model-economics", "ownerRole": "Operations and finance owners", "request": "Total ownership/operating cost and accepted useful moves for the same population and accounting window", "acceptanceQuestion": "Are failed and aborted attempts retained, and is the denominator observed and nonzero?", "holdCondition": "Cost per move uses theoretical throughput, missing costs or an incompatible observation window.", "status": "not_assessed" }, { "id": "change-and-exit", "gate": "scale", "lensId": "operations-ecosystem", "ownerRole": "Product portfolio and procurement owners", "request": "Version-support terms, site replication evidence, configuration control, supplier exit and retirement responsibilities", "acceptanceQuestion": "What reopens the decision after map, fleet, authority, software, site or commercial changes?", "holdCondition": "Support lifetime, revalidation, rollback, data disposition or supplier exit is unspecified.", "status": "not_assessed" } ], "useInstructions": [ "Use this as a request for evidence and an ownership map. Every row starts not_assessed; the checklist does not score or approve a supplier.", "Record exact configuration, source, observation window, exposure, exclusions, evidence owner, review date and expiry for the response. Keep confidential replies in the buyer's governed private system.", "VDA identifies version 3.0.0 (March 2026) as current at the source retrieval date. Its interface scope excludes safety, cybersecurity, traffic logic, acceptance procedures and responsibility allocation; assess those separately.", "ISO Open Data records ISO 3691-4:2023 as published, at the to-be-revised stage, and its successor as an unpublished draft at the retrieval date. Confirm the applicable edition and product/system/site/jurisdiction with competent specialists; a draft is not a published standard.", "Use the existing Product System and Evidence Passport to connect claims, requirements, configuration, evidence gaps and the named human decision. Unresolved hold conditions remain visible; a filled checkbox cannot authorize operation." ], "sourceNotesHash": "a6ec4243a8656a8b91fd49496a56fd142041598043b345913dc4c90f061a37ba", "payloadHash": "d2176c47160e1dcfbd9fcde8c3a5edcb1d3d8ff52832ed83eeb434a453231a00" }