System architecture

XProtect Incident Manager is installed on the same computer as the Management Server service.

The following diagram illustrates the system communication and data flows between the different components in XProtect Incident Manager and the XProtect VMS.

Flow	Actions and components
1	An operator of XProtect Smart Client starts, saves, edits, or deletes an incident project. Information about the incident project and its data is saved in the extension’s own SQL Server database Surveillance_IM. The activities related to incident projects are - depending on the activity - logged in the extension’s own SQL Server database Surveillance_IM, in the Log Server service’s SQL Server database SurveillanceLogServerV2, or in both.
2	A Management Client administrator creates, edits, or deletes an incident property. The incident property definition is saved in the extension’s own SQL Server database Surveillance_IM. The user activity is logged in the Log Server service’s SQL Server database SurveillanceLogServerV2.

Flow

Actions and components

An operator of XProtect Smart Client starts, saves, edits, or deletes an incident project. Information about the incident project and its data is saved in the extension’s own SQL Server database Surveillance_IM. The activities related to incident projects are - depending on the activity - logged in the extension’s own SQL Server database Surveillance_IM, in the Log Server service’s SQL Server database SurveillanceLogServerV2, or in both.

A Management Client administrator creates, edits, or deletes an incident property. The incident property definition is saved in the extension’s own SQL Server database Surveillance_IM. The user activity is logged in the Log Server service’s SQL Server database SurveillanceLogServerV2.