1
Existing cameras
Current RTSP or on-site feeds already in the warehouse.
First-site rollout
How one bounded first site goes live.
Use this page when you want the rollout sequence behind Start with One Site, from readiness and workflow setup through live use and final review.
One site, one bounded deployment path, and one clear review point before expansion.
Operating flow
The one-site operating flow
Existing cameras feed the edge runtime for local processing. Operators use cloud review and control to move reviewed incidents into Odoo workflow continuation today, while broader downstream actions are scoped case by case.
2
Edge
Local processing, durable queues, and incident creation on the box.
3
Cloud control plane
Review, diagnostics, deployment control, and governed fleet state.
4
Customer systems
Odoo workflow continuation exists today; broader ticket, WMS, or ERP handoff is scoped case by case.
Detection & Policy
Incident Review
Site Health & Diagnostics
Governance & Expansion
Cameras -> Edge runtime -> Cloud -> Apps, with policies, releases, and deployment changes flowing back to the edge.
Rollout boundary
What keeps the first site focused
The first deployment works best when the site boundary, camera set, workflow, and owner are clear before live operation begins.
One site with a clear operational boundary
Two to six cameras connected to the rollout
Two to three policy types that are easy to review
One named owner for operational feedback and final review
One visible final review point before expansion or refinement
A milestone view of the first site: controlled scope, visible stages, and a clear final review point.
Site stages
The first-site sequence
The goal is to move one site through visible stages and end with a clear review and rollout decision.
Readiness
Connect the site, confirm camera inputs, and make sure the first deployment starts from a usable baseline.
Workflow setup
Define zones and policies so the first workflow is narrow enough to review properly.
Go-live
Run preflight, go live in a bounded way, and keep rollout state visible.
Incident review
Review incidents with evidence, ownership, and clear follow-through.
Diagnostics and recovery
Use diagnostics and recovery tools when camera, device, or rollout conditions drift.
Final review
Close the loop with readiness, incident evidence, and a clear next-step decision.
Readiness -> Workflow setup -> Go-live -> Incident review -> Diagnostics -> Final review.
By final review
What should be true before the next decision
By the end of the rollout, the site should be live, understandable, and ready for a clear next-step decision.
Site is live
The deployment is active and visible.
Incidents are easy to review
Operators can review what happened with retained evidence.
Readiness is visible
The site and camera state are clear at the point of review.
Next decision is clear
The rollout ends with enough context to refine, expand, or stop deliberately.
Final review
What the rollout review looks at
The review should be based on visible materials: incident summaries, incident evidence, readiness checks, and the context around the rollout.
Incident summary for what the site actually detected
Incident evidence for the material used in final review
Final review summary for the site outcome
Readiness summary for site and camera state
Audit context for what changed during the rollout
Final review view showing what is ready to review, what evidence supports the site outcome, and what the next-step decision depends on.
Site journey
From bring-up to final review
The first site moves through visible stages from readiness to final review.
Related pages