MV-VIEW-01 CatalogueVIEW-02 Station commissioningVIEW-03 SDK & driver compatibilityVIEW-04 Capture & evidenceVIEW-05 Trigger & capture groupsVIEW-06 CalibrationVIEW-07 Source contract & mappingVIEW-08 Inspection & provenanceVIEW-09 Vision / WMS / LocateLinkVIEW-10 Fault & recovery labVIEW-11 Qualification & coverageVIEW-12 Release & rollbackEyeZ job catalogue (60)Software & standards (16)Primary sources (54)Import checks
Acting asAuthorization is evaluated by effect, not by screen. Demonstration only.0 session operations
EYZ-MV-033
Transit and package-damage evidence
ProposedWarehouse, logistics and product journey← EYZ-MV-032EYZ-MV-034 →Synthetic vision workspace. No camera, frame grabber or vision controller has been contacted; camera SDKs run only in engineering-managed edge workers, never in a browser. No real image exists here — every frame is a described placeholder. Nothing is live or qualified, and no inspection result releases product or causes any robot, reject, dispatch or stock effect.
The job
Actor
Warehouse/traceability supervisor
Job to be done
Capture visible carton/pallet damage at custody boundaries.
Capture requirement
Time-stamped multi-view evidence with handling-unit and checkpoint identity.
Required context
WMS owner, HU/LPN, order, dock, lane, event-time tag assignment and inventory authority
Responsibility and proof
EyeZ output
Damage regions and before/after comparison.
CoreSync responsibility
Acquire the native observations and evidence references; preserve source identity, capture time/epoch, quality, recipe/calibration versions and delivery evidence. Bind through approved canonical semantics; do not infer control authority.
Acceptance evidence
Evaluate damage classes and compare only equivalent views/coverage.
Guardrail
Appearance alone does not establish which party caused damage.
Candidate camera profiles (7)
| MV-CAM-001 | Basler pylon camera families | pylon SDK / pypylon | DETAIL |
| MV-CAM-016 | Zivid Zivid 3D cameras | Zivid SDK | DETAIL |
| MV-CAM-020 | RealSense librealsense-supported depth devices | librealsense / RealSense SDK 2 | DETAIL |
| MV-CAM-021 | Orbbec SDK-supported depth camera families | Orbbec SDK v2; legacy packages separately | DETAIL |
| MV-CAM-027 | Cognex In-Sight smart-camera families | In-Sight SDK / Web SDK by generation | SURFACE |
| MV-CAM-031 | Axis VAPIX-compatible network cameras | VAPIX; ACAP only as separately qualified application option | DETAIL |
| MV-CAM-032 | ifm O3R vision platform | ifm3d | DETAIL |
A candidate is a design reference from a reviewed technical source. It is not an implemented capability, not coverage and not a qualified adapter.
Candidate software and standards (5)
- MV-SW-005 MVTec HALCON / MERLIC interfaces — Vision-processing and acquisition integration; gate: Tool licensing and exact acquisition-interface revision required; not every camera is qualified.
- MV-SW-009 OpenCV — Image-processing library; gate: Audit package and third-party dependencies; OpenCV 4.5+ license differs from older releases.
- MV-SW-010 OpenVINO — Inference runtime; gate: CPU model/operator/precision coverage and latency must be benchmarked; accelerators optional.
- MV-SW-011 ONNX Runtime — Inference runtime; gate: Operator set, preprocessing, numerical equivalence and provider fallback are qualification items.
- MV-SW-012 Ultralytics YOLO — Model tooling and runtime integration; gate: AGPL/Enterprise licensing and model/export rights require an approved review before proprietary embedding.
Synthetic results attributed to this job (0)
No synthetic assertion is attributed to this job yet. Run a scenario in the fault and recovery laboratory.