Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This section covers the configuration of the Gallagher SMB system, including:
Create a Site or Demo Site
Default configuration overview
Enable Guarding
Assign a Controller to a site
Configure inputs and outputs
Configure readers
Configure monitoring
Configure areas
Configure Entry Delay
Configure Exit Delay
Configure Doors
Door status, history, and overrides
Site Actions
Publish configuration to Controller
Activation
Gallagher SMB has partnered with First Security (New Zealand) and Wilson Security (Australia) to provide an integrated guarding solution as an alternative to self-monitoring or third-party monitoring. Guarding is not currently available outside of New Zealand and Australia.
With the Guarding service enabled, customers can request a guard directly from the Gallagher SMB app or enable automated guarding where the system will automatically request a guard in an alarm incident.
The guarding provider will respond to the alarm, assess the site, call the police if needed, and provide a full report within the SMB app. Customers will receive regular update notifications indicating the guard has arrived on site and departed, followed by updates on their actions on-site and a final report.
To be eligible for Guarding, a site must:
be in New Zealand or Australia
be activated
not be a demo site
A guard call-out can be initiated either manually or automatically.
Manual guard call-out
With Guarding enabled, the customer can choose to manually request a security guard when an incident occurs. When reviewing an incident, the site Manager can take the Action to “Request Security Guard”. A warning will appear to ensure they want to proceed and are aware the call-out could result in a call-out fee. Once agreed to proceed, the customer would need to call the guarding company to cancel, and fees may still apply.
Auto-Guard call-out
The customer can enable Auto-Guard call-outs, where the request for a guard is automatically sent. Customers can configure a guard to be automatically requested if an incident is not responded to within the selected timeframe. This does not need to be set at the time of activation; the customer can enable auto-guarding within the SMB app.
Guarding has a monthly ongoing subscription associated with it. Billing will commence once the 'Setting up Guarding' section (below) is complete for a site and the site is activated. When a guard call-out is made either manually or via Auto-Guarding, the customer incurs a call-out fee additional to the monthly billing.
To cancel charging, contact Gallagher (order@security.gallagher.com) and the Guarding company.
Getting the Client Code
To enable Guarding for a customer, a Client Code is required from the Guarding provider.
Note: Guarding is only available for activated, real (not demo) New Zealand and Australia sites.
Complete the Guarding Form.
This is available from within the SMB Installer Portal, under 'Support' tab > 'Administration' > Guarding Form.
Provide Site Details, Site Name, Site Address, Site Contact & After-Hours Contact.
Click Send form to send the Guarding Form to the guarding provider (First Security NZ or Wilson Security AUS).
The guarding provider will organise a site visit with the customer and create a proforma.
Once the site visit is completed, the Site Plan is sent to the customer.
The guarding provider advises the Technician of the Client Code, which should start with 'GAL'.
Once the Technician has the Client Code, Guarding can be enabled for a site.
Enabling Guarding in the SMB Installer Portal
To enable Guarding for a customer, perform the following:
Note: Guarding is only available for activated, real (not demo) New Zealand and Australia sites.
Log into the SMB Installer Portal and navigate to the site.
From the menu on the right-hand side of the customer’s site configuration screen, click Enable Guarding.
The Guarding Subscription lightbox displays.
Enter the Client Code. This is provided by the Guarding company and us ually starts with 'GAL'.
If the customer wants a guard to be called automatically when an incident occurs, enable the Automatically Request Guard toggle.
In the Request Guard After field, enter the number of minutes (0-15) after which the customer wants a guard to be automatically called out, when an incident is raised through the SMB app.
Click OK.
If a guard call-out is made either manually or via Auto-Guarding, the customer will incur a call-out fee.
A customer's site is first created and then configured in the Gallagher SMB Installer Portal.
Log into the SMB Installer Portal.
Login details can be requested through Gallagher Sales Order Management team.
Click the + ADD NEW SITE button located at the top of the screen.
The 'New Site' wizard displays.
Enter a Name for the site.
It is important to consult with the customer to identify a meaningful name for the site - as well as areas, doors, inputs, and outputs - as these names will appear in the Gallagher SMB App.
Select the Timezone, Country and Address of the site.
Ensure you select the appropriate 'Country'. The associated country code is used as the default dialling prefix (country code) when adding phone numbers in the Gallagher SMB App.
Click Next.
The Key Account Holder screen displays.
Enter the Name, Email and Cellphone number of the key account holder.
The key account holder should be the main point of contact at the customer’s site and they will be the first person to receive access to the SMB security solution. An invitation is sent to this person once the site is activated.
Click Next.
The Setup screen displays.
Select the appropriate Configuration Template. If you select 'NZ AU Base Kit' or 'USA Base Kit', after you click 'SAVE', the site is given a default configuration as outlined in Default configuration overview. If you select 'NZ AU Controller Only' or 'USA Controller Only', the site will only have a Controller added by default.
Select the Billing Frequency. The available options are Monthly and Annually. Subscription billing commences once the site is activated.
Enable the Site uses tags check box if the site will be issuing key tags to users. This will enable the key tag assignment and management functionality within the Gallagher SMB App.
Tags are considered a single-factor credential. If tags are used for access, the area the doors are associated with must be configured to disarm with a single-factor authentication. This is part of the Area configuration lightbox.
Click the Save button.
The site is created, and the default configuration is displayed.
About Demo Sites
The Demo Site workflow is designed to provide SMB Partners with a platform to train technicians to configure SMB Sites. Demo Sites can also be used for promoting the solution to potential customers. All SMB Partners have a default of five (5) Demo Sites available to configure. Demo Sites can be deleted at any stage in the process and are non-chargeable. If you require more than five demo sites at one time, please contact your Gallagher representative with an explanation so this can be adjusted in the system.
Demo Sites can have hardware allocated to them and they can be fully activated and used in the same way as a real site. By activating the site, SMB Partners can demonstrate the registration process and SMB app to potential customers.
Demo Sites are not development sites and are not monitored by Gallagher's development teams. Demo Sites should be used for training and promotion only.
Creating a Demo Site
Log into the SMB Installer Portal.
Login details can be requested through Gallagher Sales Order Management team.
Click the SUPPORT tab at the top of the screen.
Under 'Manage Demo Sites', click the + ADD NEW DEMO SITE button.
The 'New Demo Site' wizard displays.
Enter a Name for the site. The name of the site, areas, doors, inputs, and outputs will appear in the Gallagher SMB App.
Select the Timezone, Country and Address of the site.
Ensure you select the appropriate 'Country'. The associated country code is used as the default dialling prefix (country code) when adding phone numbers in the Gallagher SMB App.
Click Next.
The Account Holder screen displays.
Enter the Name, Email and Cellphone number of the key account holder.
The key account holder should be the main point of contact at the customer’s site and they will be the first person to receive access to the SMB security solution. An invitation is sent to this person once the site is activated. As this is a demo site, it can be the Technician.
Click Next.
The Setup screen displays.
Select the appropriate Configuration Template. Once the site creation wizard is completed, this template provides a default configuration for the site.
Select the Billing Frequency. This defaults to non-chargeable. No subscription is charged for Demo Sites.
Enable the Site uses tags toggle if the site will be issuing key tags to users. This will enable the key tag assignment and management functionality within the Gallagher SMB App.
Tags are considered a single-factor credential. If tags are used for access, the area the doors are associated with must be configured to disarm with a single-factor authentication. This is part of the Area configuration lightbox.
Click the Save button.
The Demo Site is created, and the default configuration is displayed.
All other configuration procedures are the same as a real site, as is outlined in the Installer Help, documentation, and training videos.
Identifying Demo Sites
Demo Sites will appear on the SITES tab. They can be identified within the list by the word '(Demo)' that appears after their status in the 'Status' column. Demo Sites will also appear under the 'Manage Demo Sites' section in the SUPPORT tab.
Deleting a Demo Site
Log into the SMB Installer Portal.
Login details can be requested through Gallagher Sales Order Management team.
On the SITES tab, use the search box to search for the Demo Site to be deleted, or go to the SUPPORT tab to see a list of Demo Sites.
Click on the site that is to be deleted.
Click SITE DETAILS on the right-hand side of the screen.
The 'Site Details' lightbox displays.
Click the DELETE button.
A warning displays.
Click OK to delete or CANCEL to return to the site configuration page.
Once a Demo Site is deleted, there is no further record of this site. Gallagher does not store any history, events or users’ details about the site.
Reusing the Demo Site Controller
If a Controller was assigned to a site that was deleted and you wish to use the Controller for a different site, the previous site’s configuration must be cleared from the controller. To clear a Controller’s configuration, refer to Clearing the Controller's configuration in the topic 'Bring Controller online'.
An area is a collection of sensors that the customer will want to arm or disarm together, separately from other areas. Areas typically define a physical space within the customer’s site, and include the sensors installed in that space.
Example: The manager's office is set up as a separate area from the reception. The receptionist is able to disarm the reception, leaving the office secure.
Area Groups allow areas of a site to be grouped to suit the way the business owner wants to operate their site. Area Groups typically define parts of the site which are physically separate from each other, so that entering one doesn’t necessarily mean you want to enter or disarm another.
Example: The site has an office block and a separate warehouse. Staff that work in the office block typically don’t have access to the warehouse. By creating two area groups, fully privileged users can easily disarm the office block on arrival while leaving the warehouse armed, or vice versa.
If a site wants to use Key Tags, cards, or User Codes to access an area, the area must use Single Factor. In the Area's properties, set the Locally disarm area option to 'Single Factor'.
When first created, the site is populated with default input and output data. The inputs are assigned to the default Area - Area 1, and default Area Group - Default Area Group.
The data can be viewed by 'As wired' and 'By area'. For configuring Areas and Area Groups, 'By area' is the easiest view to be in.
To add a new Area, select the + ADD NEW button and select 'Area'.
From the Areas tab, select the Area you have created to open its properties.
Name the Area something meaningful to the customer.
If the site has Area Groups configured, the Area Group drop-down list displays. Select an Area Group for the Area to be added to, or leave it in the 'Default Area Group'.
If using Key Tags, Cards, or User Codes to arm & disarm an Area, change the Locally disarm area to 'Single Factor'. 'Two Factor' can only be used if the customer is using the SMB app only.
Select the customer's desired behaviour from the Default Arming Mode drop-down list. This option determines how the Area arms when it is armed via SMB tags and User Codes or Automatic Arming schedule. It does not affect arming via the SMB app, which always uses the Bypass method.
Force Arm: When the Area is armed via SMB tag, User Code, or schedule, it will arm even if there are open (active) Inputs in the Area. Any input that is open when the Area arms will immediately trigger an alarm, and an incident will be raised.
Bypass: When the Area is armed via SMB tag, User Code, or schedule, it will arm even if there are open (active) Inputs in the Area. When the Area arms, any open Input will be bypassed, i.e. it will not trigger an alarm or raise an incident until the Area is disarmed and armed again.
Fail to Arm: When the Area is armed via SMB tag, User Code, or schedule, it will fail to arm if there are open (active) Inputs in the Area. If arming fails, this is raised in an incident. If arming fails when attempting to arm at an access reader, the reader will also briefly sound a siren noise to indicate the arming failed. If no Inputs in the Area are open, the Area will arm successfully.
Assign Inputs and Outputs as required.
To configure the Delay Warnings tab, refer to the following sections: Configure Entry Delay and Configure Exit Delay.
Once finished configuring the Area, click OK to close and save your changes.
Note: Once the Area is configured, its Event History tab displays all events associated with this output. Events can be filtered.
Assign the Area to Area Groups, if applicable.
To add a new Area Group, select the + ADD NEW button and select 'Area Group'. Or, select an existing Area Group to open its properties.
Name the Area Group something meaningful to the customer.
To add Areas to the Area Group, select the + ASSIGN AREAS button, then select the check box next to each Area you wish to add to the Area Group.
Once finished, click OK to close and save your changes.
Note: Once you have created at least one Area Group, all Areas must be in one Area Group. An Area cannot be in multiple Area Groups. To accommodate this, all Areas that you have not yet added to an Area Group, and all newly created Areas, are added to a 'Default Area Group' by default.
Since all Areas must be in an Area Group (once you have created at least one Area Group), you cannot simply remove an Area from its group. To remove an Area from an Area Group, add it to another Area Group or the 'Default Area Group'. This will remove it from its previous group, since it can only be in one group.
Once an Area Group has had all of its Areas moved to another group, it can be deleted. If all Area Groups are deleted, the 'Default Area Group' is also deleted.
The Gallagher SMB solution supports three different readers or the ability to configure a door without a reader.
Gallagher SMB T11 (C500430/C500431)
Gallagher SMB T15 (C500480/C500481)
Gallagher T30 Multi Tech Keypad (C300490/C300491)
The Gallagher SMB Reader provides users with a convenient way to control their site’s security. The reader can be used for local alarm management, access control, or both.
Arming Reader: When a reader is not associated with a door, it's an arming reader, by default.
Access Reader: When a reader is added to a door, it's can perform both jobs, access and (local) arming.
Arming and disarming affect a whole site or area. When one or more areas are armed, all doors in those areas are locked.
A privileged user can locally arm or disarm their site at a reader using their smartphone, SMB Key Tag, SMB Card, or User Code. A user’s smartphone communicates using Bluetooth® to the reader. This functionality is useful if internet connectivity has been lost. The areas that a user can arm and disarm are determined by their roles and configured privileges.
Users arm and disarm areas by:
presenting their smartphone, SMB Key Tag, or SMB Card to the reader (a single badge is required to disarm the site and a double badge to arm the site), or
entering their User Code (T30 Keypad only).
Gallagher SMB T11 and T15
When a T11 or T15 is configured as an arming reader, the reader’s LED will display:
Green: one or more areas are disarmed.
Red: all areas are armed.
Gallagher SMB T30 Keypad
When a T30 Multi Tech Keypad is configured as an arming reader, the reader’s LED squiggle will display:
Green: one or more areas are disarmed.
Red: all areas are armed.
And the reader’s LED Arm (shield) icon will display:
Green: one or more areas are disarmed.
Red: all areas are armed.
Quick Flash White: a long press on the Arm (shield icon) button causes the LED to flash white briefly, ready for the user to present their smartphone, SMB Key Tag, or SMB Card, or enter their User Code, to start the arming process.
Blue: a long press on the '0' button changes the LED Arm icon to blue or white to reveal the reader's supported technology; blue is the Multi Tech variant and white is the MIFARE variant.
Access control affects only one door at a time. When a door is unlocked with a user's credential, only that door momentarily unlocks to allow access. Additionally, if the door's area was armed and the user has the privilege to disarm, entering their credential disarms that area only.
If a reader is assigned to a door, a user can locally request access at the reader. Access can be requested using a smartphone, SMB Key Tag, SMB Card, or User Code. Access control is limited to Bluetooth® for iOS devices. Android devices will use NFC for access control by default (if enabled on the device) or Bluetooth®.
Users gain access through doors by:
presenting their smartphone, SMB Key Tag, or SMB Card to the reader, or
entering their User Code (T30 Keypad only).
When configured as an access reader, the reader’s LED (squiggle) will display:
Solid green: the door is unlocked.
Solid red: the door is locked.
Flashes green: access has been granted.
Flashed red: access has been denied.
Note: When assigned to a door, the reader’s LED squiggle will always display the locked state of the door, not the armed or disarmed state of the site.
From the Hardware tab, click the + ADD NEW button and select a reader.
Enter a name for the reader.
Enter the reader's serial number in the Serial Number field. After plugging in the reader, the serial number can be copied from the controller's event history. The serial number can also be found on the back of the reader and on its packaging.
If required, adjust the reader's Bluetooth Connection Settings. Refer to the section below.
Click OK.
Notes:
If all T30 Keypads are removed from the site configuration, all User Code functionality is hidden within the SMB app, including existing User Codes. If the T30 Keypad is ever added back again, any previously-configured User Codes will remain and can be used again (and new ones can again be generated).
If you are replacing a T15/T11 reader with a T30 Keypad, the door associated with the reader must be unlocked.
Once a reader has been assigned to a door, the 'Enable NFC connectivity' check box is included in the reader's properties, and is enabled by default. Refer to the section below.
The Enable NFC connectivity check box is included in the properties of all readers that have been assigned to a door. Hence, you will not see this option on readers you have only just created. After assigning the reader within a door's properties, you can return to the reader's properties and:
select the 'Enable NFC connectivity' check box to allow Mobile Credentials to request access via NFC and Bluetooth® (selected by default), or
deselect the 'Enable NFC connectivity' check box to force Mobile Credentials to request access via Bluetooth® and not NFC. SMB tags are unaffected by this setting.
Environmental factors (e.g. metal surfaces) will affect the reader's Bluetooth® performance. The following Bluetooth® connection settings can be adjusted to improve the user's phone performance when communicating with the reader.
These settings are adjusted in the SMB Installer Portal on the Reader's properties tab.
Transmit Power
Increasing the Transmit Power will increase the readers Bluetooth® read range. Adjusting this range will increase both the Door Connection and Local Arming ranges. The default value is -26 dBm (decibel-milliwatts).
Door Connection Range
This is the range at which the customer’s Bluetooth® device will automatically connect to the reader and grant access to the user if the user has access privilege to the area the door is associated to. The default value is 45 dBm (decibel-milliwatts) and must always be less than the value set for the local arming range.
Local Arming Range
This is the range within which the user can manually connect their Bluetooth® device to the reader to arm or disarm their alarm system. The default value is 64 dBm (decibel-milliwatts).
Note: These settings will need to be checked and adjusted according to the site as the distance at which a device connects to the reader depends on the construction of the wall the reader is placed on and the types of devices (phones) the users will be using.
In the following situations, if the T30 Keypad loses power and comes back online, it might cause the Keypad to become unresponsive:
T30 Keypad is unplugged and connected back.
The Controller is power cycled.
The Controller is soft restarted or restarted from the controller debug page.
When replacing a T15/T11 reader with a T30 Keypad, the door must be unlocked.
If the T30 Keypad becomes unresponsive, unlocking and then locking the door will recover the reader.
In situations where organisations or Site Managers are apprehensive about managing their own alarms and don’t want to take on this responsibility outside of work hours, Third-Party Monitoring can be configured for the site.
Alarm messages are sent from the Controller at the site to the nominated monitoring station in a standard format in accordance with a set of rules. Monitoring stations will have software that interprets messages received. The software will send notifications to nominated personnel at the site or display details on a workstation at the station in a form that is easy for an operator to action.
The monitoring company can notify relevant parties in accordance with an agreed action plan. This could be people from your site, your security technician, or a guarding company who will send someone to check your premises.
If Third-Party Monitoring is enabled, the Site Manager will not receive alarm incident notifications.
Actions taken by the monitoring station will depend on the response plan defined by the customer.
Possible actions are:
do nothing
monitoring station software sends an automated notification to nominated people at the site
telephone nominated personnel at the site one by one in an escalation sequence
call a guard out
contact police.
The required response by the monitoring station may depend on:
the day of the week and/or time of day
what happened
the value of property at the site
the level of trust the business owner has in the people who have access to the site
how much the business owner is prepared to pay monitoring for the service
whether the system is police graded and/or the alarm has been verified. The rules and requirements for calling the police vary by country and jurisdiction. If required, verification could be by someone at the premises, video verification, or following dual activation.
Messages are sent from the SMB system to the monitoring station in Contact ID format. This is a standard protocol used worldwide to communicate what is happening on a site to a monitoring station.
The message format is: ACCT MT Q XYZ GG CCC
Code mappings and the rules for formatting and determining which messages to send are fixed. The need or ability for a Technician to configure anything has been minimised.
Entry Delay provides some time (default of 30 seconds) for a user to disarm an area, after entering the site. It is ideally suited for intruder alarm sites, where a user has entered using a physical key, and must then disarm the site.
To configure entry delay, perform the following procedure:
Click the Areas tab.
Select the area to configure entry delay for.
Select the Delay Warnings tab.
Enable Entry Delay. The default entry delay time is 30 seconds. This is the period of time a user will have to disarm the site, after entry.
Click the Assign Inputs button and assign one or more entry points.
The first entry point to be activated will trigger entry delay. When the area is in delay, entry points will not raise an alarm until the delay period has expired. Non-entry point sensors will immediately raise an alarm when the area is in delay or armed.
Notes:
Assignment of an entry point is required if entry delay has been enabled.
Only inputs assigned to the area, can be assigned as entry points.
Inputs assigned to an access-controlled door cannot be assigned as entry points.
Battery Low and Mains Failure inputs cannot be assigned as entry points.
When a disabled input is assigned as an entry point, it will be automatically enabled.
When an input is assigned as an entry point, the input’s alarm response will be set to ‘Secure Alarm’.
If required, select the readers to beep when the area is in entry delay.
Any reader can be assigned as a delay warning. When the area is in delay, the reader will emit a continuous beep, until such time, as the delay has been cancelled, or the delay period has expired.
If required, select the outputs to activate when the area is in entry delay.
Any output, excluding door relays, can be assigned as a delay warning. The output will activate, until such time, as entry delay has been cancelled, or entry delay has expired. The output could be a piezo buzzer or light that provides an audible or visual indication to users, that the area is in entry delay. An output is useful when the audio from a reader cannot be heard, (e.g. a user has entered an upstairs office, failing to disarm before entry).
Note: To complete the configuration, a warning (reader or output) must be assigned.
If the delay warning output is on, and delay occurs, the output will remain on for the delay period and will turn off when the delay has been cancelled, or the delay period has expired. If the output is an Alarm Output, the output will be on when the area is in alarm, (i.e. will remain on after the delay period, if the area is in alarm). Likewise, if the output is a Reflected Output, the output will be on when the area is armed, (i.e. remain on after the delay expires, if the area is armed).
If the delay period expires and an incident is generated, auto-guard callout will occur from the time the incident was raised. For example, if the system has been configured to call a guard after 10 minutes, and entry delay is configured for 30 seconds, the system will call a guard 10 minutes and 30 seconds after activation of the first entry point.
If a customer isolates an entry point when arming, the input will continue to trigger entry delay. An alarm will be raised that entry delay has timed out (if timed out), however, the isolated input will not raise an alarm. This is expected behaviour. Ideally, the customer should not arm the area when the entry point is open.
Exit Delay provides some time (default of 30 seconds) for an on-site user to exit or disarm the area, after an arming request has been sent. It is ideally suited when a user has remotely armed an area, unaware that a user is on-site. It provides the on-site user with an opportunity to disarm the area (cancel the arming request) or to exit the area.
Functionality:
After arming an area (or several/all areas), the area's configured Exit Delay starts counting down (if Exit Delay is enabled). If a user with the Privilege to disarm presents a valid credential at one of the area's readers before the delay period expires, the 'arm' action is cancelled and the area/site remains disarmed.
The area's Exit Delay period expires (and the area is armed) as soon as a door that accesses the area is opened and closed. If one of the area's access doors is opened or closed after the Exit Delay period has expired, an alarm is raised.
To configure exit delay, perform the following procedure:
Click the Areas tab.
Select the area to configure exit delay for.
Select the Delay Warnings tab.
Enable Exit Delay. The default exit delay time is 30 seconds. This is the period of time a user will have to exit or disarm the area, after an arming request has been sent.
Click the Assign Inputs button and assign one or more exit points.
When an exit point closes, exit delay will cancel, and the area will immediately arm. For example, a reed switch on a door, when closed, will immediately arm the area.
Notes:
Assignment of an exit point is optional.
Only inputs assigned to the area, can be assigned as exit points.
Battery Low and Mains Failure inputs cannot be assigned as exit points.
When a disabled input is assigned as an exit point, it will be automatically enabled.
When an input is assigned as an exit point, the input’s alarm response will be set to ‘Secure Alarm’.
If required, select the readers to beep when the area is in entry delay.
Any reader can be assigned as a delay warning. When the area is in delay, the reader will emit a continuous beep, until such time, as the delay has been cancelled, or the delay period has expired.
If required, select the outputs to activate when the area is in exit delay.
Any output, excluding door relays, can be assigned as a delay warning. The output will activate, until such time, as exit delay has been cancelled, or exit delay has expired. The output could be a piezo buzzer or light that provides an audible or visual indication to users, that the area is in exit delay. An output is useful when the audio from a reader cannot be heard, (e.g. the site has been armed remotely, and an onsite user is unable to hear the reader beep).
Note: To complete the configuration, a warning (reader or output) must be assigned.
If the delay warning output is on, and delay occurs, the output will remain on for the delay period and will turn off when the delay has been cancelled, or the delay period has expired. If the output is an Alarm Output, the output will be on when the area is in alarm, (i.e. will remain on after the delay period, if the area is in alarm). Likewise, if the output is a Reflected Output, the output will be on when the area is armed, (i.e. remain on after the delay expires, if the area is armed).
If an input is open when an area configured with exit delay is armed, the input will raise an alarm. For areas without exit delay, the user will be notified that the input is open when attempting to arm.
If an input is open when an area configured with exit delay is armed, the input will raise an alarm. For areas without exit delay, the user will be notified that the input is open when attempting to arm.
A door's 'Status' tab only displays when a reader is assigned to the door and the reader is online.
You can view a door's status to diagnose connection faults with the door. To view a door's status, open the door's properties and select the 'Status' tab. This tab displays the state of the door and all items assigned to the door. Status is updated in real-time.
A door's 'Event History' tab only displays when a reader is assigned to the door and the reader is online.
You can view a door's event history to see a record of its historical events. For example, the event history will include a record of access denied events, access granted events, lock and unlock overrides, and other alarms such as 'forced' or 'open longer than expected'. You can filter the event history by 'All Events', 'Alarms', or 'Active Alarms', and by the time the event occurred.
After the configuration has been published and before the site is activated, you can unlock a door from within the SMB Installer Portal.
Opening the door The 'Open Door' override is intended to let someone through the door, and let the door lock again once they have passed through. Next to the door item, click Open Door. The door will unlock momentarily, then relock.
Unlocking the door
The ‘Unlock Door’ override is intended to unlock the door for a set period of time.
Next to the door item, click Unlock Door.
Set the Duration in Minutes. This duration is how long the door will remain unclocked for, before locking again. The default is 10 minutes.
Click OK. The door will unlock for the set duration, then relock.
To re-lock the door manually, select Lock Door. When the site is activated, the ‘Unlock Door’ override will be cancelled.
About inputs: Inputs detect the voltage level change on the input to determine the state of the device connected. For example, if the voltage on the input is 2.5 Vdc (normal) and then changes to 3.3 Vdc as a result of the alarm relay opening, then this will be reported as an alarm condition.
All inputs on the Gallagher SMB solution have the same operational characteristics. They are provided to allow the connection of monitored switches for intruder detectors, door and window monitoring, fire alarm detection, and general equipment monitoring.
From the Hardware tab, open the input you want to configure.
Name the input something meaningful to the customer (e.g. 'Office PIR' rather than 'PIR 1'), as the names are present within the customer app.
Select the required Area.
Select the Sensor type.
Select the appropriate Alarm Response type. Options include:
'Secure Alarm': When activated, the item will generate an alarm if the area it is assigned to is armed. Commonly used for intruder items such as PIRs or Reed Switches.
'24 Hour Alarm': When activated, the item will generate an alarm, regardless of whether the area it is assigned to is armed or not. Generally used for system alarms or building alarms.
'24 Hour Silent Alarm': Similar to the 24 Hour Alarm, but the alarm output for the area will not be activated. This can be used to discreetly raise an alarm when duress or holdup buttons are being used without alerting the threat to the fact an alarm has been raised.
'Alarm when disarmed': When activated, the item will only generate an alarm when the area is disarmed. Generally used for safety issues onsite.
'No Event Recorded': When activated, neither an event nor an alarm will be generated. This can be used when nothing needs to be recorded and no one needs to be alerted.
Note: See About input Alarm Responses below for more information.
Click the + ASSIGN OUTPUTS button and assign the appropriate output(s) to the input. The outputs you assign here will turn on when this input opens.
Notes:
The 'Outputs' box displays all outputs assigned to this input.
The Status tab displays the current status of this input.
The Event History tab displays all events associated with this input. Events can be filtered.
Once finished configuring the output, click OK to close and save your changes.
See the 'Configure Areas' topic to assign this input to Areas.
Note: For inputs that are not currently being used, we recommend disabling the input by setting its toggle to Off. This ensures the controller ignores all unused inputs and avoids unnecessary open circuit tamper alarms being raised.
About outputs: All outputs on the Gallagher SMB system, irrespective of the actual hardware unit, have the same operational characteristics. They are provided to allow control of external devices such as door locks, lighting, sirens, and external systems.
From the Hardware tab, open the output you want to configure.
Name the output something meaningful to the customer (e.g. 'Office Light' rather than 'Light 1'), as the names are present within the customer app.
Select the Output type from the drop-down list: Siren, Strobe, Light, or Pulsed.
If you selected 'Siren', 'Strobe', or 'Light', enter the Maximum On Time in minutes and/or seconds. Defaults to None.
If you selected 'Pulsed', enter the Pulsed Time in minutes and/or seconds. Defaults to 5 seconds.
Notes:
The 'Used on Areas' box displays all Areas this output is assigned to.
The 'Used on Inputs' box displays all inputs this output is assigned to.
The Status tab displays the current status of this output.
The Event History tab displays all events associated with this output. Events can be filtered.
Once finished configuring the output, click OK to close and save your changes.
See the 'Configure Areas' topic to assign this output to Areas.
Additional I/O boards can be added to expand the solution to 128 Inputs and 61 Outputs.
The following I/O Boards are compatible with the SMB Solution:
Gallagher SMB 8In Board
Gallagher SMB 8In 4Out Board
Gallagher HBUS 16 In 16 Out Board
To add more I/O Boards:
From the Hardware tab, click the + ADD NEW button.
Select '8 In Board', '8 In 4 Out Board', or '16 in 16 Out Board' from the drop-down list.
The Properties lightbox displays.
Enter the Name and Serial Number of the board that is being added to the site.
If different EOL Resistors are required, select the required option from the drop-down list.
Click OK.
To configure the additional inputs and outputs, refer to the procedures above.
Refer to the table below for a detailed overview of the behaviour of each of the Alarm Response types:
A user can request access by presenting their smartphone, SMB Key Tag or SMB Card at the door’s reader or entering a User Code into the T30 Keypad. The smartphone must host the Gallagher SMB app with a valid mobile credential for the site.
iOS smartphones communicate with the reader using Bluetooth®. Android smartphones communicate with the reader using NFC or Bluetooth®. The tag and card communicate with the reader using NFC.
Access granted events will appear in the History log of the Site Manager’s app when access has been granted and taken through the door. The user’s name and door name are reported.
Notes:
Location permission must be enabled on Android devices, as without this permission the device’s Bluetooth® won’t scan, even if Bluetooth® itself is enabled.
Only Site Managers and privileged Site Admins can view doors and their locked/unlocked status within the Gallagher SMB app.
For an access granted event to appear in the History log, access must be granted and taken through the door. The door’s open sensor must change state.
Door configuration supports a reader on one side of the door only. The solution does not support entry and exit readers on the same door.
To be granted access, the user must have privilege to the area the door leads into. If they have privilege for the area, access will be granted, and the controller will unlock the door.
If the area the door leads into is armed, the system will prompt for a second factor to disarm. The user must have privilege to disarm the area the door leads into, hence must present a valid FIDO authenticator (PIN, Fingerprint, or Face ID). The controller will then disarm the area and unlock the door.
Notes:
Access decisions are made at the controller, not the reader.
Site Members cannot arm or disarm areas, hence if the door leads into an armed area, access will be denied. A Site Manager or Site Admin must first disarm the area.
If an area is disarmed as a result of a successful access request, it is not re-armed if access isn’t taken.
Exiting the area is achieved by either turning the door handle (mortise lock) or by using a push button release (magnetic lock). The door will temporarily unlock, allowing the user to pass through.
Note: The Request to Exit must transition to the closed state to unlock the door. If it transitions to the opened state, invert the Request to Exit input.
Unlocking the door from within the Gallagher SMB app will perform an unlock override. The door will not automatically change back to the locked state, until scheduled to do so. For example, if the door is scheduled to lock at 5pm each day, but a user unlocks the door from within the app at 6pm. The door will not lock again until 5pm the following day, unless a user locks it from within the app or the site is armed.
Note: Arming the site will automatically lock all doors.
Doors with readers can be used for access control. They allow people to access them with a valid credential.
Gates, roller doors, or cupboards without a reader are not considered ‘access control’ doors, as the door is locked and unlocked remotely via the app or open-door button.
Within the customer app:
Doors without readers are displayed on the 'Doors' tab.
All Site Managers get privilege by default.
Site Admins have the optional Additional Privilege to lock/unlock remote doors to selected areas.
'Unlock by' and 'Lock by' will appear in the History Log. These are not Access Granted events, as the system doesn't know who (if anyone) opened the door.
Refer to the table below for a detailed overview of the behaviour of each of the Alarm Response types:
Once the site has been created, the default configuration will display. The default configuration supports the pre-wired mains power failure and battery low inputs.
If configuring the site remotely before installation, the controller assignment can be completed last, prior to site activation.
To associate a controller with a site, perform the following procedure:
Navigate to the customer's site.
Click the Scan controller QR code button and scan the QR code printed on the controller.
If using a laptop, take a photo of the QR code using your phone and present it to the laptop. If you are unable to scan the controller's QR code, you can enter the controller's ID in the Controller ID field. The controller's ID is printed on the controller, below the QR code.
Click the ASSIGN CONTROLLER button.
The controller will come online and connect to the Gallagher cloud. An IP address is automatically assigned to the controller via DHCP. There is no MAC address or IP addressing required. The controller will download the latest firmware and update its default configuration. This takes approximately five ( 5 ) minutes.
Notes:
If the controller does not come online, check the site has an internet connection.
If the site has a firewall preventing the controller from connecting to the internet, the following ports on the controller need to be reachable:
| Port | Protocol | Details |
|---|---|---|
If the message 'Cannot assign controller' displays, the controller has already been assigned to a site.
Select the Controller.
The ‘Controller’ lightbox displays.
Notes:
If the site is using tamper detection, the controller’s optical tampers can be enabled here.
The controller’s firmware version and application version are shown here.
The Controller's 'EOL Resistors' setting is only applied to the '8In Board 1' by default; not the '8In4Out Board 1'. This is because the 8In4Out Board's two power-monitored inputs (Battery Low and Mains Failure) require 4k7 Ohm Rs in order to function, and therefore are set this way in the 8In4Out Board's default configuration.
The controller’s ‘Event History’ shows events generated by the controller, and cloud events that are related to the controller. Use the event history to help diagnose issues with the site.
This topic gives an overview of the default configuration that comes with a new SMB site.
Note: If you selected a "Controller Only" Configuration Template during the site creation, only a Controller item is added by default. All other items can be added manually.
If you selected the 'NZ AU Base Kit' Configuration Template when creating the site, the following default configuration is applied:
| Item | Description |
|---|---|
If you selected the 'USA Base Kit' Configuration Template when creating the site, the following default configuration is applied:
| Item | Description |
|---|---|
For New Zealand and Australia sites, the Permaconn PM54 is the available alarm transmitter. For North American sites, the Alula BAT-Connect is available.
NZ/AUS: Permaconn PM54 The Permaconn PM54 can also function as an alarm communicator, transmitting alarms from the Gallagher SMB Controller to a monitoring station using the Contact ID alarms transmission protocol. The Permaconn PM54 is powered by the Gallagher SMB Kit and provides connection to the site's WAN or Wi-Fi.
North America: Alula BAT-Connect The Alula BAT-Connect is an alarm communicator, transmitting alarms from the Gallagher SMB Controller to a monitoring station using the Contact ID alarms transmission protocol. The Alula BAT-Connect is powered by the Gallagher SMB Kit and provides connection to the site's WAN, cellular, or Wi-Fi.
If the customer requires third-party monitoring, configure the alarm transmitter.
In the , click the MONITORING tab.
Enter the Account Code received from the monitoring station and click SAVE.
The Alarm Transmitter item displays.
Enable the toggle next to the Alarm Transmitter.
Note: If you are also enabling the IP Alarm Transmitter, select which transmitter is the primary one from the Primary option (next to the 'Account Code' field).
Click on the Alarm Transmitter to open its properties. The Alarm Transmitter lightbox displays.
Enter the transmitter device's serial number or MAC address (this is an optional field).
To enable , enable the Periodic Dialling toggle.
To set the frequency of dialling tests, select either Dial daily at or Dial every.
Dial daily at: Select this option to have a periodic dial occur at the same specified time each day. Consider selecting a unique time for each site so the load on monitoring stations is spread throughout the day. If you change the periodic dial time, notify the monitoring station of the new test time. The time will automatically adjust for daylight savings.
Dial every: Select this option if you require more frequent periodic test dials. This means that a test dial will occur at the interval specified, starting at the time that has been specified. Any time can be entered as the start time. Daylight savings corrections will be applied when the Controller's clock is updated.
If required, select the Skip periodic dial following successful alarm dial check box.
With this option selected, the periodic dial test will be skipped if there has been a successful alarm dial since the last periodic dial test. If the periodic dial is skipped, the next time you can expect a periodic dial is at the configured time the next day or after the periodic dial interval, depending on how it is configured.
Click OK to complete the configuration.
For more information about your alarm transmitter, refer to the appropriate installation note:
About Periodic Dialling
A timer test (also known as the ‘periodic test’ or ‘24 hour’ test) is an affirmation to the monitoring station that the alarm system is capable of sending Contact ID. Most alarm systems send one test per day. The signal is fixed in its format and will be sent with an XYZ (Contact ID event code) of 602 and it will be sent in the (GG) partition or Alarm Zone 00. Only one periodic test can be enabled per account number for accurate reporting of line status (this is a consideration when using multiple Diallers using single client code reporting). It may be necessary to configure periodic tests from different diallers into different account numbers. It will also be reported as a new event and will have a CCC of 000, (e.g. 123418160200000, where 1234 is the account number).
If a test is not received when it should have been, action is taken by the monitoring station staff.
Publishing configuration with monitoring enabled pushes the monitoring-related configuration to the controller. This publishing is also the trigger for the controller to carry out dial checks and construct and send messages to the monitoring station.
THE MONITORING STATION WILL RECEIVE ALARMS FROM THE SITE WHENEVER MONITORING IS ENABLED AND A PERMACONN IS CONNECTED OR THE IP ALARM TRANSMITTER IS ENABLED (even if installation and configuration are still underway).
Monitoring Report
Generating the report Once a site is activated, a Monitoring Report will be available to download and send to the monitoring station. The Monitoring Report outlines the XZY Codes, GG Codes, Zone list CCC Codes, and User CCC Codes.
Under Site Actions on the right-hand side of the screen, click Download Monitoring Report.
A warning appears: Only published changes will appear in the report. NOTE: This report contains personal data. Please respect privacy laws.
Click Download.
The Monitoring Report downloads as a CSV file.
Send the file to the monitoring station.
As no users are created for the site yet, the User List CCC Codes will only contain the Key Account Holder. The Monitoring Report can be downloaded at any stage, and you may wish to wait until the Site is set up with more users before downloading and sending the report.
Users' CCC codes If an incident occurs and the monitoring station doesn’t know who the user is by name, they will have a CCC code. In the SMB app, the customer can search for this code.
For the Site Manager to find which user the CCC code is related to:
Log into the SMB customer app.
Select Team from the navigation bar.
In the search field, enter the CCC code.
The user with the related CCC code appears in the search results.
The IP Alarm Transmitter requires no additional hardware; only the Controller is required.
Firmware requirement: To use IP Alarms, the Controller must be using Application version 2-3-11 or higher. Check the 'Application' field in the Controller's properties.
If the customer requires third-party monitoring, you can configure the IP Alarm Transmitter as an alternative or addition to the Permaconn or Alula alarm transmitter.
In the , click the MONITORING tab.
Enter the Account Code received from the monitoring station and click SAVE.
The IP Alarm Transmitter item displays.
Enable the toggle next to the IP Alarm Transmitter.
Note: If you are also enabling the Permaconn or Alula alarm transmitter, select which transmitter is the primary one from the Primary option (next to the 'Account Code' field).
Click on the IP Alarm Transmitter to open its properties.
The IP Alarm Transmitter lightbox displays.
Select the required Protocol for transmitting to the monitoring station.
CSV uses Comma Separated Values (CSV) format for transmitting alarms. This method uses TCP/IP and is unencrypted.
DC-09 Gallagher uses Gallagher's own format of DC-09. Select this option if you are transmitting alarms to a Gallagher receiver. Encryption is available.
DC-09 SIA uses the Security Industry Association (SIA) protocol for DC-09. You will most likely want this option when transmitting to a third-party monitoring station. Encryption is available.
If you selected a DC-09 protocol, the Encryption check box displays. Optionally select this check box to encrypt all transmissions from the Controller, then enter the Encryption Key.
You can either generate this Encryption Key yourself and then provide it to the monitoring station, or request an Encryption Key from the monitoring station. Either way, the monitoring station must have the same key that you enter here.
For the IP Alarm Transmitter to provide authentication, select the Authentication check box and enter the Username and Password that will be used by the monitoring station to authenticate the data received.s
Note: The Username and Password must not contain the following characters: < > & ‘ “ ,
Enable as many Receivers as you like; there are two available. You must enable at least one Receiver for the IP Alarm Transmitter to function.
Transmissions are sent to 'Receiver 2' if attempts with 'Receiver 1' fail.
In the IP field of the enabled receiver(s), enter the IP address of the receiver. This must be provided to you by the monitoring station.
In the Port field of the enabled receiver(s), enter the Port used by the receiver. This must also be provided to you by the monitoring station.
To enable , select the time under the Polling field and enter how often a heartbeat will be sent to poll the receiver. Otherwise, select 'None'.
Click OK to complete the configuration.
A timer test or 'poll' (also known as the ‘periodic test’ or ‘24 hour’ test) is an affirmation to the monitoring station that the alarm system is capable of sending Contact ID. Most alarm systems send one test per day. The signal is fixed in its format and will be sent with an XYZ (Contact ID event code) of 602 and it will be sent in the (GG) partition or Alarm Zone 00. Only one periodic test can be enabled per account number for accurate reporting of line status (this is a consideration when using multiple Diallers using single client code reporting). It may be necessary to configure periodic tests from different diallers into different account numbers. It will also be reported as a new event and will have a CCC of 000, (e.g. 123418160200000, where 1234 is the account number).
If a test ('poll') is not received when it should have been, action is taken by the monitoring station staff.
Publishing configuration with monitoring enabled pushes the monitoring-related configuration to the controller. This publishing is also the trigger for the controller to carry out dial checks and construct and send messages to the monitoring station.
THE MONITORING STATION WILL RECEIVE ALARMS FROM THE SITE WHENEVER MONITORING IS ENABLED AND A PERMACONN IS CONNECTED OR THE IP ALARM TRANSMITTER IS ENABLED (even if installation and configuration are still underway).
Monitoring Report
Generating the report Once a site is activated, a Monitoring Report will be available to download and send to the monitoring station. The Monitoring Report outlines the XZY Codes, GG Codes, Zone list CCC Codes, and User CCC Codes.
Under Site Actions on the right-hand side of the screen, click Download Monitoring Report.
A warning appears: Only published changes will appear in the report. NOTE: This report contains personal data. Please respect privacy laws.
Click Download.
The Monitoring Report downloads as a CSV file.
Send the file to the monitoring station.
As no users are created for the site yet, the User List CCC Codes will only contain the Key Account Holder. The Monitoring Report can be downloaded at any stage, and you may wish to wait until the Site is set up with more users before downloading and sending the report.
Users' CCC codes If an incident occurs and the monitoring station doesn’t know who the user is by name, they will have a CCC code. In the SMB app, the customer can search for this code.
For the Site Manager to find which user the CCC code is related to:
Log into the SMB customer app.
Select Team from the navigation bar.
In the search field, enter the CCC code.
The user with the related CCC code appears in the search results.
| Alarm Response | Alarm/event behaviour if the input's area is armed | Remote notification if the input's area is armed? | Activate outputs assigned to the input's area if the area is armed? | Keep alarms/relays active if the input's area is armed? | Alarm/event behaviour if the input's area is disarmed | Remote notification if the input's area is disarmed? | Activate outputs assigned to the input's area if the area is disarmed? | Deactivate the outputs activated by this event response once the alarm is acknowledged? |
|---|---|---|---|---|---|---|---|---|
The reader's properties now include the option to choose whether NFC connectivity is enabled or not for Mobile Credentials. Refer to for details.
'Event Only': Used for audit purposes to record activity that someone may want to interrogate at a later date. Often used to record ‘return to normal’ events (e.g. Controller front no longer tamperd). Note: See below for more information.
For more information about how the customer can use Schedules, see .
'Event Only': Used for audit purposes to record activity that someone may want to interrogate at a later date. Often used to record ‘return to normal’ events (e.g. Controller front no longer tampered). Note: See below for more information.
All actions for these doors must be performed in the SMB Customer app. SMB Key Tags, SMB Cards, and User Codes cannot be used for these doors. See .
| Alarm Response | Alarm/event behaviour if the input's area is armed | Remote notification if the input's area is armed? | Activate outputs assigned to the input's area if the area is armed? | Keep alarms/relays active if the input's area is armed? | Alarm/event behaviour if the input's area is disarmed | Remote notification if the input's area is disarmed? | Activate outputs assigned to the input's area if the area is disarmed? | Deactivate the outputs activated by this event response once the alarm is acknowledged? |
|---|
(NZ/AUS only)
(North America only)
67
UDP
DHCP to internal router
53
UDP
DNS to internal router
123
UDP
NTP to time.google.com
443
TCP
SMB Cloud HTTPS
500 - Controller 1
A Controller item. You cannot delete this item from the configuration.
Most sites will only require one Controller. The Controller acts as the head of the other configuration items, and is responsible for making access decisions and distributing firmware updates to the other hardware items.
501 - 8In Board 1
An input board. You may optionally delete this item.
This board is connected to and powered by the Controller. The 8In Board comes with eight Inputs that can be individually configured. You cannot delete individual Inputs.
502 - 8In4Out Board 1
An input and output board. You may optionally delete this item, however, since it is used for monitoring mains power failure and low battery by default, you should configure the Inputs of another Board to monitor these if you delete this one.
This board is connected to and powered by the Controller. The 8In4Out Board comes with eight Inputs and four Outputs that can be individually configured. You cannot delete individual Inputs or Outputs.
By default, this 8In4Out Board does not use the 'Use Site Default' EOL Resistors setting. This is because the two power-monitored inputs (Battery Low and Mains Failure) require 4K7 Ohm Rs in order to function, and therefore are set this way by default.
508 - Permaconn Alarm Dialler
Found on the MONITORING tab after the Account Code is entered. Sites created with the 'NZ AU Base Kit' Configuration Template come with a Permaconn in the default configuration. You cannot delete this item from the configuration, but you can toggle it to be disabled.
500 - Controller 1
A Controller item. You cannot delete this item from the configuration.
Most sites will only require one Controller. The Controller acts as the head of the other configuration items, and is responsible for making access decisions and distributing firmware updates to the other hardware items.
501 - 8In4Out Board 1
An input and output board. You may optionally delete this item, however, since it is used for monitoring mains power failure and low battery by default, you should configure the Inputs of another Board to monitor these if you delete this one.
This board is connected to and powered by the Controller. The 8In4Out Board comes with eight Inputs and four Outputs that can be individually configured. You cannot delete individual Inputs or Outputs.
502 - 8In4Out Board 2
A second input and output board. You may optionally delete this item.
This board is connected to and powered by the Controller. The 8In4Out Board comes with eight Inputs and four Outputs that can be individually configured. You cannot delete individual Inputs or Outputs.
511 - Alula Alarm Dialler
Found on the MONITORING tab after the Account Code is entered. Sites created with the 'USA Base Kit' Configuration Template come with an Alua in the default configuration. You cannot delete this item from the configuration, but you can toggle it to be disabled.
Secure Alarm
Raise Alarm
Yes (default IP Alarm Transmitter)
Yes
No
No Event / No Alarm
N/A
N/A
Yes
24 Hour Alarm
Raise Alarm
Yes (default IP Alarm Transmitter)
Yes
No
Raise Alarm
Yes (default IP Alarm Transmitter)
Yes
Yes
24 Hour Silent Alarm
Raise Alarm
Yes (default IP Alarm Transmitter)
No
No
Raise Alarm
Yes (default IP Alarm Transmitter)
No
N/A
Alarm when disarmed
Event Only
N/A
N/A
N/A
Raise Alarm
Yes (default IP Alarm Transmitter)
Yes
Yes
No Event Recorded
No Event / No Alarm
N/A
N/A
N/A
No Event / No Alarm
N/A
N/A
N/A
Access Silent / Secure Alarm | Raise Alarm | Yes (default IP Alarm Transmitter) | Yes | No | Raise Alarm | Yes (default IP Alarm Transmitter) | No | Yes |
Secure Alarm | Raise Alarm | Yes (default IP Alarm Transmitter) | Yes | No | No Event / No Alarm | N/A | N/A | Yes |
24 Hour Alarm | Raise Alarm | Yes (default IP Alarm Transmitter) | Yes | No | Raise Alarm | Yes (default IP Alarm Transmitter) | Yes | Yes |
Event Only | Event Only | N/A | N/A | N/A | Event Only | N/A | N/A | N/A |
No Event Recorded | No Event / No Alarm | N/A | N/A | N/A | No Event / No Alarm | N/A | N/A | N/A |
The Display Names button lets Technicians change the names of an SMB site's roles, which are by default 'Site Manager', 'Site Admin', and 'Site Member'. An SMB customer may request this, for example, so that the role names in the app correspond with the job titles that they already use.
Click the Display Names button.
The Display Names lightbox displays.
Change the Role Names as requested by the customer.
Click OK. Wherever a role type is displayed or selectable in the SMB app, the new role names will now be displayed.
Reset Role Names: You can click the RESET button in the Display Names lightbox to reset the Role Names to the defaults of 'Site Manager', 'Site Admin', and 'Site Member'.
The Site Details button allows the general details of the site to be changed after it has been created. The site must be in Installer Mode for the site details to be changed.
To modify the Site Details:
Click the Site Details button.
The Site Details lightbox displays.
Change the details as required, such as the Name, Timezone, Country and Address of the site.
Note: For a timezone change to take effect on the Controller, you must publish the configuration.
Change the Subscription and Guarding details as required.
Note: These are not applicable for Demo Sites.
The Site uses tags toggle defines whether Key Tag assignment and management functionality is enabled.
Tags are considered a single-factor credential. If tags are used for access, the area the doors are associated with must be configured to disarm with a single-factor authentication. This is part of the Area configuration.
Click the OK button.
The site details are changed.
The 'SITE ACTIONS' section of a site in the Installer Portal contains key actions around the configuration and activation of the site. The available options depend on the current state of the site, but can include:
At all times:
View the Site Details
View, add, and modify Site Notes
View and change the Key Account Holder
Only before the site is activated:
Activate the site (see Activation)
Only once the site is activated:
Download the Monitoring Report (see Alarm transmitters or IP Alarms)
Only in Installer Mode (or before the site is activated):
Modify the Site Details
Enable Test Mode (cannot be done manually before activation)
Test Mode allows Technicians to install, configure, and test an SMB site without annoying or alarming anyone by setting off the sirens or any other type of device activated in response to an alarm. Test mode also prevents Site Managers, guards, and monitoring services from responding to alarms generated while the system is being tested.
Test Mode can be used as part of your ongoing maintenance process. All Gallagher-manufactured parts are covered under the Gallagher SMB Product Warranty Policy. Annual testing and maintenance checks are recommended to ensure the solution is meeting the customer’s needs.
Test Mode starts automatically when a new site is created, and ends when the site is activated.
Test Mode gives Technicians the ability to test individual outputs. Alarm Relays are bypassed, and technicians can ‘chirp’ test outputs from this screen.
When Test Mode is enabled for new sites:
All alarm outputs are automatically bypassed. This prevents sirens etc. being activated during Test Mode.
The Installer Portal will display a banner showing when Test Mode will expire.
During Test Mode (new sites)
Technicians can "Test" individual outputs by using the TEST found next to the outputs in the Installer Portal. This will override the output to On for 1 second, then Bypass the alarm output again (or cancel the override) which will turn it off.
Enabling Test Mode for existing sites
Once a site is activated, ask the Site Manager to enable Installer Mode within the Gallagher SMB app. Notes:
Installer Mode allows Technicians to make configuration changes to the site in the Installer Portal and publish changes to the Controller.
Test Mode can only be enabled after Installer Mode has been enabled.
Test Mode puts the site in a state that is no longer production-ready (alarm relays will not activate), therefore Test Mode can only be enabled for a short period of time, less than 24 hours.
If Installer Mode is disabled, Test Mode will automatically be disabled too.
After Installer Mode is enabled in the Customer app, the Enable Test button is visible in the Installer Portal.
Select Enable Test Mode in the Admin section of the Installer Portal.
Select an expiry time.
If the site has Monitoring or Guarding enabled, a message will display to remind the Technician to contact the Monitoring or Guarding company to advise that the system is being tested. This will prevent unnecessary call-outs.
Note: Test Mode can only be enabled if there are no Guard call-outs currently in progress for the site.
When Test Mode is enabled:
All alarm outputs are automatically bypassed. This prevents sirens etc. being activated during Test Mode.
Any currently in-progress Incidents will not receive any new alarms (existing incidents remain open).
A new Test Mode incident is created to capture any alarms generated during Test Mode.
A notification is sent to all Site Managers alerting them that Test Mode is enabled.
The Installer Portal will display a banner showing when Test Mode will expire.
The Customer app will display a banner explaining that the site is under maintenance.
During Test Mode (existing sites)
Any alarms generated will be added to the 'Test Mode Incident'.
Technicians can "Test" individual outputs by using the TEST found next to the outputs in the Installer Portal.
This will override the output to On for 1 second, then Bypass the alarm output again (or cancel the override) which will turn it off.
If Monitoring is enabled during Test Mode, the Technician will be advised, when publishing the change, that the Monitoring company needs to be informed that the system is under test.
Disabling Test Mode (existing sites)
Test Mode can be disabled due to any of the following occurring:
The Technician selects Disable Test Mode in the Admin section of the Installer Portal.
The Test Mode period expires.
The site is taken out of Installer Mode (expires or is manually disabled).
Ideally, a technician disables Test Mode manually by selecting Disable Test Mode in the Admin section of the Installer Portal when they have finished testing, as the site will be 'live' again when Test Mode is disabled.
For sites with Monitoring or Guarding enabled, if Test Mode is disabled manually, a reminder will display to inform the Monitoring or Guarding company that testing has finished.
When Test Mode is disabled:
Incidents generated during Test Mode are automatically closed.
Alarm outputs are un-bypassed.
Banners in both the Customer app and the Installer Portal are removed.
You can set the length that User Codes will be when they are generated for users in the SMB app. User codes that have already been assigned to users will not be affected if you change the minimum user code length.
Note that this option only displays if at least one T30 Terminal has been configured for the site. The User Code Length can only be changed before the site has been activated or while in Installer Mode.
To set the minimum User Code length:
If the site has been activated, ask the customer to enable Installer Mode.
Click the User Code Length button.
The User Code Length lightbox displays.
Select the Minimum length from the drop-down list. Generally, longer User Codes are considered more secure.
Click the OK button. New User Codes will now be generated at this length in the SMB app.
The Key Account Holder button lets Install Managers view the details of the Key Account Holder and also change the Key Account Holder.
Note: Install Technicians cannot change the Key Account Holder. For more about Technician roles, refer to Installer Portal overview > 'TECHNICIANS tab'.
Click the Key Account Holder button.
The Key Account Holder lightbox displays.
Click the CHANGE KEY ACCOUNT HOLDER button.
The New Key Account Holder lightbox displays.
Enter the email address of an existing SMB app user for this site.
Click OK.
In the confirmation pop-up, tick the check box then click OK.
The selected user is given the Site Manager role and is made the Key Account Holder. They will receive an email informing them of the change.
If you wish to use the customer app to test the site's access, alarm, and app behaviour from the perspective of the customer, you can invite yourself to the site. This can only be done before the site has been activated or while in Installer Mode. As a Technician, you have some restrictions in the customer app. You cannot:
see the details of any user (except for names in events)
create, delete, or send invites to users
close incidents
manually call out a guard.
You can only invite yourself to sites where you are recorded as being a Technician of the customer's Installer. You can send as many invitations as you like. You can have just one credential per site per technician. If you invite yourself as a user to multiple sites, you can interact with readers at all of those sites and can switch between sites in the customer app.
To request a credential for yourself to the customer's site:
If the site has been activated, ask the customer to enable Installer Mode.
Click the Invite Myself To The Site button.
This sends an invitation to the email address entered against your Technician account; there is no option to send it to a different email address. SMS verification is not required.
Download the Gallagher SMB app if you have not already.
Select the Complete Registration link in the email invitation.
Changes made within the Installer Portal do not take effect until they are published to the Controller with the PUBLISH or REFRESH button. The PUBLISH button displays when there are pending hardware changes; the REFRESH button displays at all other times to allow you to ensure the Controller configuration is up to date (e.g. if you have made a non-hardware site change).
When publishing/refreshing configuration to the Controller, doors will revert to their original schedule regardless of whether the customer has performed an override. For example, if the customer has overridden the schedule to Free, and then a Lock Door override is performed, the door will lock and the override will be lost.
Once changes have been published to the Controller, there is no way to restore to a previously published version. To revert the site configuration to how it was when it was last published, select DISMISS CHANGES under Unpublished Changes.
Note: Configuration can only be published/refreshed when the Controller is online.
All changes appear in the sidebar to the right under Unpublished Changes.
Note: If no changes have been made since the last publish, the 'Unpublished Changes' section does not display.
Select the floating PUBLISH button to publish the changes.
Note: If the Controller is offline, the button will be disabled. If there are no pending hardware configuration changes, the 'REFRESH' button shows instead.
When PUBLISH is selected, a pop-up window will appear asking you to confirm you want the changes published. Select Publish Changes. Note: For all newly-installed sites, when the Controller comes online, it will immediately start downloading new firmware. If the firmware is still downloading when you attempt to publish the changes, a warning will appear. If changes are published while the download is not completed, the download will restart from the beginning.
After the configuration has been published, a small confirmation displays.
If you have not made any hardware changes, but need to update the Controller's configuration anyway (e.g. you changed the site's timezone), you can use the 'REFRESH' button.
Select the floating REFRESH button to publish the current configuration to the Controller. Note: If the Controller is offline, the button will be disabled. If you have pending hardware configuration changes, the 'PUBLISH' button shows instead.
When REFRESH is selected, a pop-up window will appear asking you to confirm you want the Controller to be updated. Select Yes. Note: For all newly-installed sites, when the Controller comes online, it will immediately start downloading new firmware. If the firmware is still downloading when you attempt to refresh the configuration, a warning will appear. If configuration is refreshed while the download is not completed, the download will restart from the beginning.
After the configuration has been refreshed, a small confirmation displays.
The Site Notes button opens the notes for the site, where you can add, edit, and delete notes for you and other Technicians to refer to.
Click the Site Notes button.
The Notes lightbox displays.
Click the + button to create a new note.
Type out the note you would like to add for this site. Each note is limited to 500 characters.
Click the SAVE button.
The note is added to the left-hand navigation panel within the Notes lightbox. Notes are listed in this panel in order of most recently modified.
Click the x button to close the Notes lightbox.
Click the Site Notes button.
The Notes lightbox displays.
Select the note from the left-hand navigation panel.
Type in the text area to make any required changes.
Click SAVE, then click the x button to close the Notes lightbox.
Click the Site Notes button.
The Notes lightbox displays.
Select the note from the left-hand navigation panel, and click the DELETE button.
Click YES, then click the x button to close the Notes lightbox.