OWAL is a computer vision company that send alerts for specific events. We want to send these alerts as email to SureView (an video command center application) via their simple Generic stream integration. (API docs and Test harness will be shared upon job acceptance)
>> YOU WILL CREATE AND TEST AN SMTP MESSAGE FORMAT THAT SETS NOTIFICATIONS WITHIN IMMIX. there are extremely limited options , but this must be done in a windows environment)
"The Generic Stream integration was written to provide instant support for devices that can transmit
video using the RTSP protocol. We provide the integration as part of the API as it can be easily extended
to achieve more advanced functionality. You should use the Generic Stream integration whenever your
device/system transmits video over RTSP. The RTSP integration itself is built on top of the
[login to view URL] API. See the section “DevStreamGeneric Library Reference” for reference
documentation and usage"
(1) Submit alerts to a SureView Immix server with information comparable to what we post to Slack now — a camera, a description of the alert, time of the alert, and an image of the frame that triggered the alert, plus a URL link to open the OWAL viewer for the camera.
(2) Do so using either the “Generic” alert receiver that SureView provides, or a branded version of same, rather than any receiver with custom logic.
(3) Test against a Windows setup running SureView’s test harness software.
NOT planned for this phase of work:
(4) Initial configuration of OWAL cameras based on existing configurations in the Immix system. For now, the expectation is that sites will be manually added using OWAL’s configuration tools, along with the identifiers needed to properly associate the cameras between systems (possibly Immix’s ServerID and camera number, still working on clarifying this and evaluating options).
(5) Cross-referencing of footage. OWAL alerts will provide a timestamp in its alert submissions to Immix, which may be used by Immix for any activity that Immix normally provides for a timed alert. OWAL’s viewer, which would be accessed by a URL link from the alert, will display footage which OWAL has been engaged to retain, but will not be capable of presenting footage that may be stored in other systems.
Steps involved in implementing include:
a) receive and review specifications for SureView’s generic alert receiver
b) bringing up a Windows system with SureView’s test harness;
c) conduct manual tests to ensure understanding of the format
d) write code to compose an alert submission from typical OWAL alert data, as a simple executable (outside alert server)
e) test submission of that composed alert to the test harness, using SMTP protocol tools available from our Python environment;
OUT OF SCOPE:
f) integrate the alert composing and submission into a notification component that runs as part of OWAL’s alertmanager
g) making database changes needed to associate cameras between systems;
Potentially in scope as follow-on:
h) testing the full notification component against the test harness;
i) test against a live server and resolve any further problems;