Skip to main content
Version: 6.12

Scheduling a site on test mode

It maybe required that a site needs to be put on Test Mode using a schedule. Although There is no direct method for this currently, it is possible to achieve this by using a scheduled action plan. This Document will focus on a case where by a site needs to be put on test for a period of time on a weekly basis while a test fire alarm is activated.

Initial Setup in Patriot​

If the schedule for the client that needs to have a scheduled Test Mode is already being used for Auto Status Monitoring then a new 'dummy' area will need to be created. For the purpose of this case study we will assume the clients schedule is already being used and there fore will need to setup a new area. A new Action plan will also be needed.

User Setup
The Monitor User Open/Close Action Plan is assigned to Keyholder A.

Setup Steps

  • Create a new area for the client and set the area to something obscure as this area will only be used for the Test Mode feature. Something like 00FS would be appropriate.

  • Navigate to the Action Plan menu in Maintenance > General > Action Plans and create a new action plan. Call it Scheduled Fire Test Mode and give it the required priority

  • In the original Fire action plan set an alternative action plan

Monitor User Open/Close Action Plan
Monitor User Open/Close is the first of two new Action Plans required by this example - Signal Type is set to Cascade, and Scheduling is active.

The Unauthorised User Unset is a priority (Activating) Action Plan with no active Scheduled Actions. This Action Plan is not designed to be assigned to any Client, Event, User or Zone in Patriot, instead its sole purpose is to act as the alternate Action Plan to Monitor User Open/Close. The Signal Type is again set to Cascade, this is important as it ensures that when this Action Plan is chosen (i.e. Keyholder A disarms the client premise) the client premise's state will be updated to Open/Unset in addition to an Activation being generated.

Unauthorised Open Action Plan
Unauthorised Open is the second of two new Action Plans required by this example - Signal Type is set to Cascade, and Scheduling is inactive.

In Practice​

Keyholder B, who always has set/unset rights (no assigned Action Plan), opens the site just after 0900 hrs on Monday morning:

Open signal received from Keyholder B
Open signal received from Keyholder B.

No Action Plan is assigned to Keyholder B, Patriot chooses the level 1 Action Plan "Unset with User #" which is assigned to the event type. No Activation is triggered.

Keyholder A, who only has set rights, closes the site just after 1700 hrs Monday evening:

Patriot receives the set signal from Keyholder A
Close signal received from Keyholder A.

The Monitor User Open/Close Action Plan is assigned to user Keyholder A. Patriot overrides the Level 1 Action Plan and selects the user assigned Action Plan and cascades up the signal type of Closing (Set). Scheduling is active on the selected Action Plan but because the site status is currently open, the alternate Action Plan is not chosen.No Activation is triggered.

Just after 2200 hrs the same Monday evening Keyholder A opens the site:

Open signal received from Keyholder A
Open signal received from Keyholder A.

The Monitor User Open/Close Action Plan is assigned to user Keyholder A. Patriot overrides the Level 1 Action Plan and selects the user assigned Action Plan. Scheduling is active on the selected Action Plan and the site status is currently closed so the alternate Action Plan Unauthorised User Unset is chosen and the Opening (Unset) signal type is cascaded up from the Level 1 Action Plan.Activation is triggered.