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-059
Multi-camera capture completeness
ProposedOperational assurance and capture integrity← EYZ-MV-058EYZ-MV-060 →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
Vision operations / safety reviewer
Job to be done
Ensure every required view belongs to the same triggered inspection.
Capture requirement
Capture group with required camera set, trigger ID, epoch and tolerance.
Required context
Station, trigger/capture group, recipe, permitted workspace, device clock and maintenance state
Responsibility and proof
EyeZ output
Complete/incomplete group and missing-view reasons.
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
Drop, delay, duplicate and reorder individual camera frames.
Guardrail
Do not issue PASS from a partial set unless an explicitly qualified partial method exists.
Candidate camera profiles (6)
| MV-CAM-001 | Basler pylon camera families | pylon SDK / pypylon | DETAIL |
| MV-CAM-002 | JAI GigE/USB3 and prism/line-scan camera profiles | eBUS SDK for JAI; approved GenTL/frame-grabber path for CXP/Camera Link | DETAIL |
| MV-CAM-020 | RealSense librealsense-supported depth devices | librealsense / RealSense SDK 2 | DETAIL |
| MV-CAM-026 | Prophesee Supported event-based sensors / EVKs | OpenEB / Metavision SDK modules | DETAIL |
| 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-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.
- MV-SW-014 Prophesee Metavision modules — Event-processing SDK; gate: Open-source acquisition is not blanket entitlement to commercial modules.
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.