AXIS D4100-E can be used standalone. The product basically requires a trigger to activate a profile. In a standalone context, it can be activated by the I/O port on the device, or by setting up a scheduled trigger inside the rule engine. The user just needs to configure the events on the device using the web GUI.
Manual trigger from the operator:
In your integration, you probably want the operator to be able to manually activate/deactivate AXIS D4100-E. This can be done in many ways depending on your way of integration, but you need to add ability to turn the pre-configured profile(s) on and off based on user input.
AXIS D4100-E is mainly designed for event triggers, such as motion detection from a camera, if a panic or alarm button is pushed, a door is forced, or a storage disk is full. AXIS D4100-E can be triggered to act depending on the end user's requirements. This can be done in many ways depending on your way of integration.
The AXIS D4100-E is also producing an event stream, for example, when an I/O port on the device is activated or when a profile is activated. Your system can subscribe to the event stream and trigger different actions depending on which event that is triggered in the strobe siren. You can use the AXIS Metadata Monitor to see which events you can subscribe to.