Choose the integration boundary
An existing field system can retain camera acquisition and edge analytics while sending agreed events, clips and metadata to a central operating layer. A split design can assign additional scenarios to ViewLogic processing where compute and connectivity permit. Treat these as integration patterns to be scoped and validated for the specific partner system.
Agree the event contract
Document site and source identifiers, event type, event time, related observations, evidence references and delivery status. Align authentication, acknowledgement, retry and duplicate-handling behaviour with the receiving interface. Use the API and transport supported by the agreed delivery; this guide does not define a vendor-specific endpoint.
Separate customer and site access
Define which customers, operators and service teams can access each site, event and media item. Include the administrative actions that must be audited and how customer boundaries are tested.
Configure the operating workflow
Agree zones, time conditions, accumulation rules and notification ownership. Define how model and scenario versions are tested, approved, replicated and rolled back. Optional multimodal modules and positioning require their own inputs and acceptance criteria.
Run a joint pilot
Choose a limited set of priority scenarios, test them on representative site data and evaluate both event quality and the complete operator workflow. Verify outage recovery, evidence access and the responsibility for diagnosing each failure.
Prepare a repeatable service
Document installation, customer configuration, training, updates and first-line versus specialist support. White-label presentation, service commitments and commercial terms are agreed separately for the engagement.