Representative Cameras
Choose views that match the operating environment, including the conditions that challenge the intended use case. Record camera position and image quality.
From Pilot to a Production IREX Deployment
A deployment starts with the camera estate and the decision you need to make. This guide shows what your team, IREX, and an implementation partner must agree before a pilot becomes a production program.
Start with the Estate
What to Bring to the First Review
Bring a camera inventory with locations, stream details, and intended use cases. Identify the network owner, the existing video systems, any databases or devices that must exchange events, and the security and data-residency constraints. A site survey then checks power, cooling, rack space, network topology, and physical security before architecture or hardware is committed.
Each camera must be assessed against the connection baseline and the requirements of the analytics intended for that view. A camera that connects is not automatically suitable for every detection task. Network remediation, additional optics, and edge hardware belong in the design and budget, not in a surprise after kickoff.
Measure the Pilot
Agree What Success Means Before Testing
Detection and Review
Define what counts as a true detection, a missed event, and a false alert. Record alert volume and the human verification workflow against the agreed test set.
Written Acceptance
Name the measured criteria, reviewer, pass/fail evidence, and production-sizing decision in the Pilot Acceptance Report. IREX does not substitute a universal accuracy claim for testing on your feeds.
Stage Gates
Seven Decisions from Discovery to Handover
- 01
Discovery and Demo
Agree the use cases, stakeholders, sovereignty posture, budget range, and decision timeline. The output is an opportunity brief.
- 02
Analysis and Requirements
Record functional, security, compliance, integration, and operational requirements. Confirm feasibility and maintain a risk and dependency log.
- 03
Pilot and Acceptance
Run a typical 6–12-week pilot against real camera feeds at one site. Agree three to five use cases and two or three measurable success criteria in writing before it starts. Close with a Pilot Acceptance Report and a recommendation for production sizing.
- 04
System Design and Commercials
Complete the site survey and target architecture, capacity model, hardware and software bill of materials, support scope, and three-year cost view. Sign the statement of work and the required design, service, and data-processing documents.
- 05
Procurement and Mobilization
Use the procurement route your rules allow. Confirm purchase orders, delivery dates, and the joint delivery team before ordering hardware.
- 06
Build, Integrate, and Test
Stand up the infrastructure, connect cameras, configure analytics and integrations, and complete security hardening before user acceptance testing. Record the acceptance result.
- 07
Go-Live, Hypercare, and Run
Cut over with a rollback window, train operators, record go-live acceptance, and transition from hypercare to steady-state support under the agreed SLA.
Responsibility
Who Does What
- Customer
- Provides access to the estate and decision-makers, owns the lawful use and budget decisions, and signs pilot, design, and service acceptance.
- IREX
- Owns the platform demo, target architecture and capacity model, platform deployment and analytics tuning, and ongoing platform maintenance.
- Implementation Partner
- Leads site studies, field installation, camera and stream provisioning, procurement coordination, user onboarding, and first-line local support where a partner is engaged.
FAQ
Is the 6–12-week pilot the full implementation?
No. It is the typical pilot period. A full IREX platform deployment typically takes 6–12 months from first qualified conversation to steady-state operations, with procurement and site readiness as major variables.
Can the pilot run without sending video to a US-hosted instance?
Yes. An on-premises pilot can be scoped where video must remain on your network. Hosting, connectivity, security review, and cost are agreed for the specific pilot before it starts.
Start with Your Use Cases and Camera List
We can identify the first site, the conditions to test, and the evidence your decision-makers will need.