BVMS 10.0 CC Events and Alarms

Bosch Video Management Systems
Your path to superior video recording management and performance
BVMS 10.0 Configuration Client (CC):

Events and Alarms
BVMS Certification Training: Expert Level

BVMS – CC Events and Alarms
Scope and purpose of this slide set
 This presentation is for presence based training purpose only.
 The slides are not self learning material, it is intended that a Bosch professional
trainer explains and gives additional information while going through the topics
step by step.
 The included hands on exercises and live demo scenarios require a test system
based on the specific Bosch Video Management System version as covered in the
training.
 All information and screenshots may be subject of change.
 The slides describe important topics from learning point of view but do not reflect all features and functions of the
Bosch Video Management System. The slides are not part of the product catalog and do not replace the
individual manuals (e.g. Configuration or Operation manuals) which can be found on: www.boschsecurity.com
 select “Product Catalog”  select your country  “Products”  “Video”  “Video Software”  “Video Management Systems”
2 Building Technologies | BT-SC/MKK2 | September 2019

© Robert Bosch GmbH 2018. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.
Objectives
Learn how to configure events and alarms in Configuration Client
 Defining events
 Alarm configuration
 Alarm options
 Exercise
 Bonus: Scripting
 Backup: Detailed event and alarm Settings & additional exercises

Events: Introduction
 A circumstance or state of the system that can be used to trigger an alarm and/or an action.
 Events can:
• Arise from many sources such as cameras, encoders, directories, digital inputs, etc.
• Include start-recording states, loss of signal states, disk full messages, user logons, digital input
triggers, etc.
• Be use to trigger an alarm
• Be logged to logbook
• Trigger the execution of command scripts:
• BVMS Server “scriptlet” (depends on event type)
• The right place to begin your scripting journey
• Can be combined to form a compound trigger for an alarm
• Specify different event state priority

Events: Concept

Events: Concept
Trigger Alarm (Schedule):

Depending on the event the value is set to “Never” or “Always”
An Alarm message in Operator Client will appear when “Always” is configured.
Never means => No Alarm message will be generated in OP-Client
Can you remember to the purpose of a Task schedule?

Here you can use it and assign a task schedule to an event.
Basic Events: Cameras
 Encoders/Decoders (Bosch IP devices)
• Some important camera states
• Connection state
• Motion detection
• Recording mode
• Storage state
• Video Analysis 1 to 16

Basic Events: Recap on Video Content Analytics
Video Content Analytics (VCA)
 is the capability of automatically analyzing video to detect real-world
circumstances that are of interest to the system.
Bosch IP 1000 to Bosch IP 3000 to Bosch IP 7000 to

Video Content Analytics
2000 series * 6000 series* 9000 series *
Motion+ ✓ ✓ ✓
Tamper detection ✓ ✓ ✓
Essential Video Analytics  ✓ ✓
✓
Intelligent Video Analytics  
Intelligent Video Analytics ✓

 
flow
* some camera models vary on VCA features, just refer to the individual data sheet of each model

Basic Events: Video Content Analytics
What is the
difference
between
Essentials
VA and
Intelligent
VA?
 Let’s
watch this
video

Basic Events: VCA Events on Configuration Client
 VCA events can generate actions into a BVMS system
 Motion+ is described as “Motion Detection”
 IVA, IVA flow, Essential VA is described in BVMS as “Video Analysis”
 BVMS supports to receive individual events from VCA cameras
 Video Analysis 01 represents the first IVA task configured in the camera.
Video Analysis 02 represents the second task, and so on.
Video Analysis 01
Video Analysis 02
Video Analysis 03
Bosch IVA Cameras
Video Analysis 04 supports up to 8
tasks simultaneously

Basic Events: Camera
Important event for detecting recording issues due to
e.g. Unstable Network
 Storage State -> Storage State Failure
Description:
Primary recording of camera failed to write to the iSCSI storage, e.g. due to network
problems or unavailability of the iSCSI storage
By default this event triggers an alarm message with Priority 20
Possible Impact:
Recording gaps may be caused when the camera buffer for recordings reaches the
limit due to network outages.

Basic Events: VRM
 VRM Devices
• VRM Server Connection State
• VRM Server Failover State
• VRM Server License State
• VRM Server Type
• LUN Formatting State
• iSCSI Device Connection State
• Streaming Gateway Device Connection State

Events: Default Debounce Time for all devices
 Events happens during the predefined period will be ignored
Event generate by device for example relay closed:
500 msec
Event report by BVMS
Captured by BVMS Server Captured by BVMS Server

Events: Debounce time
Once an Event has been defined, a Default
Debounce time can be configured (500 msec)
• Different Event State Priorities needed ? Use

the “Edit Priorities” button. Priority can be edited
on a state-by-state basis. Standard Priority for
all event states is = 5
Deviating Debounce time needed on Device

Level?
• Multiple devices can be configured by using the

“Add Setting” button

Events: Compound Event
 Combine different events to a combination.

 Uses Boolean expressions : AND and OR
 Applicable to state change only.
 Supports up to 1000 compound events
 Each compound event can contain up to

10 devices
 Compound name cannot be duplicate.

Hands On: Configure Alarm Trigger & Logging 1
Configure alarm trigger & logbook logging for relay state
1. Select Events page
2. Expand the Events and Alarms  Encoders/Decoders Encoder Relay  Relay State
3. Click on the Relay Opened
4. Specified the Trigger Alarm schedule to Always
4 5
5. Configure the Log Schedule to Always

6. Click on Save icon
2 7. Click on the Activate icon
3

Optional (Bonus) Hands On: Configure Debounce 1
Configure debounce time of 3000 msec for Relay State
2. Expand the Events and Alarms  Encoders/Decoders Encoder Relay  Relay State
3. Change the Debounce Time to 3000 msec
4. Click on Save icon
5. Click on the Activate icon

3
You can test this change after you have

configured the alarm for Relay State later 2
by toggling the relay on Operator Client

Alarms: Introduction
 An Event can trigger an alarm
 An event can be configured as an alarm for example triggered by :
• Motion
• Contact Alarms
• Relays
 Alarm is displayed in the Operator Client
 Alarm must be accepted/cleared by an operator (besides Autoclear is configured)
 A series of action can be achieved:
• Display Live video, Instant Playback video
• Start Alarm-Recoding, Sent SMS/E-mail
• Execute Preset, Customise audio playback, Workflows, Web pages, Maps
Alarms: Concept

Events: Best practice for testing: Use the “Event Button Pressed”
“Operator Client Event Assign “Always” and configure the Alarm options for
Button” can be used to exercising with the alarm functionalities of BVMS
manually trigger events

Alarms: Alarm list in the Operator Client
What is the purpose of the buttons Accept, Workflow, Clear and Un-Accept? Example:
1. Operator A (Operator B and C are working in parallel) will “Accept” the Alarm (take over responsibility).
 After that the Alarm will disappear in the Alarm list of Operator B and C.
2. Operator A (optional if configured): A workflow has to be processed before “Clear” is possible
3. Operator A (optional): Before clearing the Alarm, it can be “Un-Accepted”, so it will appear again in the
Alarm lists of the Operator A, B and C.
4. Operator A: Alarm can be “Cleared” only by the operator who “Accepted” the Alarm.

Alarms: Configurations
Alarm Identity
 Title: Description display
on Operator Client Alarm
 Priority
• 100 is lowest priority; 1 is highest priority; Default is 20
• Priority behavior depends on user settings and can be configured on User group level:
• Assign Priority lower than 10 => Alarm will interrupt your work
immediately on Op-Client with an Alarm Pop-Up Window
(+ listed in Alarm Window). Work means e.g. watching live view
or doing some research via replaying recordings.
• Assign Priority higher than 10 => Alarm will be shown in Alarm

Window of the Op-Client and Alarm Pop-Up will be shown
only after manual acceptance of the operator
 Color:
The alarm color display
on the operator Client
Alarm Image Panes

 Maximum 5 panes display
 Applicable to cameras added to the Logical Tree in Maps and Structure
 Display Live or Instant playback video or Start Alarm-Recording
 Audio file format per alarm supported: mp3 and wav
Recommendation:
When defining a high priority to an Alarm e.g. 5 it is very useful
to assign as well minimum one Alarm Image pane (e.g. Camera in Live view, Map or HTML-Document

More Alarm Options:
 Cameras
• Activate recording (Re)
• Protect recording (Prot)
 make up your mind about the impact of this setting enabled, what is the risk?
• Execute PTZ Aux commands
(Bosch Protocol only)
• Execute PTZ Predefine position

 Notifications
• Alarm Notification Services:
• SMTP (email) Recipients
• SMS Recipients
Note: SMTP or SMS Server has to be

configured beforehand in “Device” tab

 Workflow
• Record only alarm: The alarm will not
come up in the Operator Client Alarm list
(but still visible in logbook)
• Auto-clear alarm (two options):
• After configured time (global Alarm settings)
• When the states goes back to normal

• Hiding of important alarms can be avoided
by not allowing the operator to clear an
alarm as long as its triggering event is still
active

 Workflow
• Prevent alarm clearing details:

• If the option is enabled:
• No auto-clear after configured time is possible for
the same alarm
• The alarm which has a still active trigger event cannot
be cleared
• The user is informed with the self closing message box about
the active event state when trying to clear the protected alarm
• The “Prevent alarm” option is not available for peak alarms
also called “fire and forget” alarms. For example “virtual input
data” or “Operator client event button pressed”.
For these specific alarm the option is blocked:

 Workflow
• In order to prevent the operator being
flooded with alarms, the new triggered
alarms can be suppressed if the same
alarm is already available in the system
• If the option is enabled:
• No further alarms are created as long as the
same alarm exists in alarm pane in active,
workflow or accepted state
• The duplicated events are still logged in the
log book and event de-bouncing is still active
• The duplicated events will not trigger another
alarm action like SMS, recording,
prepositions, etc. (actions are not retriggered)
• Same behavior for SDK notifications
 Workflow
• Display action plan
• HTML
• Text File
• Display a comment box
• Force the operator to complete process

workflow
 Execute Client Script when the alarm is
accepted.

 Monitor Group
• Display up to 10 cameras on each Monitor Group
• Display Onscreen Display (OSD) on monitor

Operator Client: Multi/Single-row alarm image window
 For better alarm overview the user is able to maximize a single alarm in the alarm image window
 This can be done by clicking on the button or double-clicking the alarm image pane
Multi-row mode (like before BVMS 9.0 but new UI) Single-row mode (new in BVMS >=9.0)
Use this …….OR double-click on

button…… any alarm image pane….
…..to change from multi-row to single-row view mode

 New action buttons on the right side in both modes
New buttons on the right

side of the alarm image
pane:
• Accept
• Process workflow
• Un-Accept
• Clear

Go to  From single row mode the
next following actions are possible:
alarm
 Go to the next/previous alarm
Cameras: drag Maps: drag  Maximize different camera image
& drop in order from title bar to pane windows per drag & drop
to maximize to title bar in order  Maximize a map: Drag the map
the other image to maximize the window on the title bar and drop it
pane map to the title bar of the new window
 Go back to the multi row mode
by button
 Go back to the multi row mode
by double-click on any image/map
Back to Single-row  Accept, unaccepted, process
multi-row
mode
mode workflow, clear the alarm
 Maximized alarm is automatically minimized if a higher priority alarm was received

 If the maximized alarm is cleared, alarm image window goes back to multi-row mode
Global Alarm Settings
 Alarm Settings
• Define the number of Image Pane per alarm.
Maximum number is 5
• Only for Auto-clear alarms: Define how long an
alarm will be cleared after triggered
• System can be configured to have only single-
row alarm display or both single and multi row
display (valid for entire system)
Selected box: Multi- and single-row display available in

Operator Client (default for upgraded systems)
Cleared box: Only single-row display available in Operator
Client (default for complete new installations in BVMS 9.0)

Alarm configuration: Stop alarm recording after defined time
 In order to save storage in cases where only the first minutes of an alarm are important, alarm recording can be stopped after a
defined amount of time before the event state is back to normal (e.g. gate is opened and forgotten to be closed again).
 This can be configured globally for all recordings in BVMS Configuration Client / Settings / Alarm Settings / Set the duration limit
for state-triggered alarm recordings:
 If the feature is enabled a state controlled alarm recording shall be stopped after a given time. If the trigger state of the event
delivering device changes back to normal before the given time, alarm recording is stopped after the configured post alarm.

Alarm configuration: Stop alarm recording after defined time
Example A :
 The feature is disabled by default.
+ Pre-alarm configured: 30 min
 The time limit can be changed in the range of 1 to 1440 minutes.
+ Alarm time (door open): 1h
 15 minutes is the default value.
+ Post alarm configured: 1h
 If the alarm is retriggered, the timer is restarted with its initial value. + Duration limit Recording disabled
 The feature affects also local and ANR recording.  Recording will be 2,5 h
Pre-Alarm Alarm Post Alarm

Example B:
Example A + Pre-alarm configured: 30 min
no limit:
+ Alarm time (door open): 1h
+ Post alarm configured: 1h
+ Duration limit Recording configured: 30 min
 Recording will be only 1 h as the limit
Example B kicks in 30 minutes after the alarm time to
with limit: avoid too much alarm recording fills up the
Duration storage.
limit
Global Alarm Settings
 Analog Monitor Groups
• Determine how video display on MG is handled

in case of same alarm priority
• Determine what to display when monitor is not

configured to display video

Alarms with high priority: Example and Recommendation
When defining a high priority to an Alarm e.g. 5 it is very useful to assign as well minimum one Alarm Image
pane. It can be a Camera in Live view, a Map or a HTML-Document (whatever is part of the logical tree in
Operator Client). What is the expected behaviour in Operator Client when this Event is triggered?
Priority 5 and Image Pane 1 configuration

results into a immediate alarm pop-up
window in Operator Client no matter what
is currently shown (live view or replay).
Without defining an Alarm Image Pane the

Alarm will come up as part of the Alarm list
but the whole Alarm List comes up
immediately to the front of the screen
Hands On 1: Configure an Alarm for Relay Closed Event
Be sure that you have enable the Trigger Alarm condition to Always in
Event Tab before you proceed with this exercise
1. Select Alarms page

2. Expand the Events and Alarms  Encoders/Decoders  Encoder Relay 
Relay State  Relay Closed
3. Change the Priority value to 10
4. Change the Title description to “Light On”
5. Change the Color to Blue
6. Click on the Alarm Image Pane 1, select any camera to show Live
7. Click on the Save icon 2
8. Click on the Activate icon
3 4 5 6

Hands On 2: Advanced scope
 Configure motion based recording & Live view camera pop up
 Use one Camera (1st ) and enable Motion+ or IVA triggers. Select only a small area (window) of the total filed
of view of the camera where no movement happens. Alternatively use trip wire IVA as trigger.
Make sure the trigger is not coming too often (somebody moves permanently inside the detection area)
 Motion based recording with 5 seconds pre and post alarm time.
 Trigger a second camera (2nd) to record as well based on the trigger from first camera
(Watch out: not based on the trigger coming form the 2nd camera! Motion detection on the 2nd camera: off )
 Verify recordings of both cameras after motion has been detected
 Bonus: Switch off management server and verify whether both cameras continue their recording behavior as
before

QUESTIONS?
Additional Information for self reading

- not relevant for the Expert Level Exams -

Events: Advanced state display on maps
 Recap, before BVMS 9.0: The already existing icon coloring/blinking on the map feature (introduced in BVMS
6.0) provides an operator a quick device state (online, motion detected, etc.) overview on the map.
The feature is based on device events only i.e. device icon coloring fades only if its state has changed.
Operator has less control over the icon highlighting.
 This feature remains in BVMS9.0 unchanged
Result

Alarms: Advanced state display on maps
 NEW in >=BVMS 9.0: Icon blinking on the map based on Alarms. It provides an operator a quick device
alarm overview on the map. It shows which devices have not solved alarms.
The feature is based on device alarms i.e. the blinking persists as long as alarm is not deleted from alarm
pane (no matter in which state device is).
Operator has more control over the icon highlighting.
Blinking red
Result on
the map in
the Op-client

 How to configure:
1. Open Configuration Client
2. Go to “Settings” / “Options”:
3. Enable hotspot coloring in maps depending on alarms:
Default
Based on states (Events) only
New in 9.0 based on Alarms only

4. Choose “Blink hotspot” in alarm configuration
Blinking red
Result on
the map in
the Op-client
This column is visible only after
enabling the alarm based feature
in step 3.

 System can run either in state (event) or alarm dependent mode, but not both in parallel
 Device icon is blinking in alarm color:
Blinking red
 Compound alarms are supported. In case of alarm the icons of all compound event components on the map will
blink (valid for OR and AND condition).
 Compound alarms are supported also with the components that have no icons on the map e. g. schedules.
In this case only those components which are present on the map will blink.
 In general: When does a icon stop blinking on the map? Example with 2 operator clients active:
 First operator: Has accepted the alarm (optional: workflow state when configured)  Blinking still on for the first operator
 Second operator: Icon stops blinking as first operator has already accepted the alarm
 First operator: Clears the alarm  Blinking stops also for the first operator

 If the alarm is re-added to the alarm list (the other operator has un-accepted alarm), the icon on the map starts
blinking again.
 If there are multiple alarms existing for the same device, the icon on the map blinks with the color of alarm with
the higher priority (lower priority value).
 If all existing alarms for the device are of the same priority, the icon on the map blinks with the color of the
most recent alarm.

Alarms: Text Data in Alarm image window
 If Alarm is associated with text data, it is now automatically shown next to alarm in the alarm image pane.
 Text data is available in the multi- and

single-row view.

Bonus: Scripting
BVMS Supports Scripting in both C# and VB.NET
• Select the “Script Editor” button
• Select a Script Language
(selection cannot be changed once scripts have been created)
• Select OK
Note:
• Scripting is a very powerful feature
• Advanced Programming skills are recommended
• Take advantage of the Scripting Training offerings in your region

Bonus: Scripting
Once the Command Script Editor is open you
can write and parse your own scripts.
Server Scripts
• Are executed on the Management Server
• Only Server scripts can be assigned to
events
Client Scripts
• Are executed on the Workstation (OP-Client)
• Client scripts can be placed in the logical tree
and on maps

Bonus Scripting: Exercise
 Create 2x server script, one to close and one to open an relay contact of
an selected camera
 Use the script examples provided by the Trainer
 Add the relay to the logical tree to see the status (open/close)
 Add the script to an motion triggered event (use the event from the previous exercise)
 When motion is detected, the script shall close the relay. No motion => open the relay

Other Basic Events
 BRS/DiBos Devices
• Input state
• Relay state
• Server state
• Connection State
• Disk Failed
• Server Reset
• Video Camera
• Motion Detection
• Recording Mode
• Reference Image Check
• Video loss
• Video signal too bright
• Video signal too dark
• Video signal too noisy

Other Basic Events
 DVR Devices (DVR 400/600/700)
• Input state
• Relay state
• Server state
• Disk Failed
• Disk Full
• Fan Failed
• Software Incompatibility
• System Alarm
• Temperature Above Limit
• Video Camera
• Video Loss

Other Basic Events
 ONVIF Encoders
• ONVIF Encoder Connection State
• ONVIF Camera
• Recording Mode
• Storage State
• …..
• ONVIF Encoder Relay
• Relay State
• ONVIF Encoder Input
• Input State
Other Basic Events
 RTSP/JPEG Devices
• RTSP/JPEG Camera
• Recording Mode
• Storage State
 Encoders/Decoders (Bosch IP devices)

• Decoder connection state
• Decoder input state
• Decoder relay state
• Encoder connection state
• Encoder input state
• Encoder relay state

Other Basic Events
 VRM Devices
• VRM Server Connection State
• VRM Server Failover State
• VRM Server License State
• VRM Server Type
• LUN Formatting State
• iSCSI Device Connection State
• Streaming Gateway Device Connection State
• Allegiant Devices
• Connection state
• Input state
• Camera video loss

Other Basic Events
 ATM/POS Devices
• POS Bridge connection state
• POS Bridge Input data input
• DTP Device connection state
• ATM Device connection state
• ATM Input data input
 Network Devices
 SNMP Receiver trap received
 ADAM Device connection status
 ADAM Input connection state
 ADAM Input state
 ADAM Relay connection state
 ADAM Relay state
Other VRM Events
 Failover State
• Active: Triggered when Failover VRM takes over
• Passive: Primary VRM is active
 VRM Types:
• Wrong Type is fired if configured VRM role does not match
the installed role
• E.g. Secondary VRM is configured, but Primary VRM is
installed

Events: Debounce time – some examples
Debounce Time = 1 sec
Input Open Input, priority high Input Open, priority low

Input Closed Input Close, priority Input Close, Priority high
low
Both same priority
Event
Alarm
0s 1s 2s 3s 4s
By default all the priorities are equal.
Within debounce time interval:

• first high priority - then low priority event => only the high priority event is triggered
• first low priority - then high priority event => both are triggered

BVMS – CC Events and Alarms 1
Hands On: Create a Compound Event
2
2. Click on the Create Compound Event icon
3. In the Create Compound Event window, expand the Events and Alarms tree 
Encoders/Decoders  Encoder Relay 
Relay State  Relay Opened 5
4. Ticked the check-boxes for the compounded

4
relay objects.
3
5. Rename the Event name to
“Compound Relay Event 1”
6. Click on the OK button.
6
BVMS – CC Events and Alarms 1
Hands On: Edit a Compound Event
2. Expand the Events and

Alarms tree  System
4
Devices  Compound
Events  Compound
Event State  Compound
3
Event is True / False
3. Select a Compound Event
4. Click on the Edit 2

Compound Event icon

Hands On: Edit a Compound Event
5. In the Create Compound Event window, amend the compound event to your requirements
6. Click on the OK button
Optional topic
for Expert
Level
5 Trainings
- not relevant
for the Expert
Level Exams -
6

BVMS 10.0 CC Events and Alarms

Uploaded by

Copyright:

Available Formats

BVMS 10.0 CC Events and Alarms

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BVMS 10.0 CC Events and Alarms

Uploaded by

Copyright:

Available Formats

Bosch Video Management Systems

Your path to superior video recording management and performance

BVMS 10.0 Configuration Client (CC):

BVMS Certification Training: Expert Level

 All information and screenshots may be subject of change.

2 Building Technologies | BT-SC/MKK2 | September 2019

 Backup: Detailed event and alarm Settings & additional exercises

4 Building Technologies | BT-SC/MKK2 | September 2019

5 Building Technologies | BT-SC/MKK2 | September 2019

6 Building Technologies | BT-SC/MKK2 | September 2019

Trigger Alarm (Schedule):

Can you remember to the purpose of a Task schedule?

8 Building Technologies | BT-SC/MKK2 | September 2019

Bosch IP 1000 to Bosch IP 3000 to Bosch IP 7000 to

Intelligent Video Analytics ✓

9 Building Technologies | BT-SC/MKK2 | September 2019

10 Building Technologies | BT-SC/MKK2 | September 2019

11 Building Technologies | BT-SC/MKK2 | September 2019

12 Building Technologies | BT-SC/MKK2 | September 2019

• VRM Server Failover State

• VRM Server License State

• VRM Server Type

• LUN Formatting State

• iSCSI Device Connection State

• Streaming Gateway Device Connection State

13 Building Technologies | BT-SC/MKK2 | September 2019

Event generate by device for example relay closed:

Event report by BVMS

Captured by BVMS Server Captured by BVMS Server

14 Building Technologies | BT-SC/MKK2 | September 2019

• Different Event State Priorities needed ? Use

Deviating Debounce time needed on Device

• Multiple devices can be configured by using the

15 Building Technologies | BT-SC/MKK2 | September 2019

 Combine different events to a combination.

 Each compound event can contain up to

 Compound name cannot be duplicate.

16 Building Technologies | BT-SC/MKK2 | September 2019

5. Configure the Log Schedule to Always

17 Building Technologies | BT-SC/MKK2 | September 2019

1. Select Events page

3. Change the Debounce Time to 3000 msec

4. Click on Save icon

5. Click on the Activate icon

You can test this change after you have

by toggling the relay on Operator Client

18 Building Technologies | BT-SC/MKK2 | September 2019

20 Building Technologies | BT-SC/MKK2 | September 2019

21 Building Technologies | BT-SC/MKK2 | September 2019

22 Building Technologies | BT-SC/MKK2 | September 2019

• Assign Priority higher than 10 => Alarm will be shown in Alarm

Alarm Image Panes

24 Building Technologies | BT-SC/MKK2 | September 2019

25 Building Technologies | BT-SC/MKK2 | September 2019

• Alarm Notification Services:

• SMTP (email) Recipients

Note: SMTP or SMS Server has to be

26 Building Technologies | BT-SC/MKK2 | September 2019

• When the states goes back to normal

27 Building Technologies | BT-SC/MKK2 | September 2019