Skip to main content

Discover Hamilton Security

Hamilton Security replaces the paper duty log with a timestamped, shared register, completed by instructions, missions, patrols and keys. This article introduces its everyday uses and what your administrator prepares beforehand.

A security team works around the clock, in relays, and must be able to prove what happened and when. Hamilton Security gives it a single tool where every event is recorded to the minute, where the instructions in force are permanently available, and where the work of one shift passes naturally to the next.

What you can do every day

An agent's day begins with the start of shift. At that moment, the shift-start sheet gathers the information to know and the applicable instructions, including the temporary instructions in force that day, for example during building works or an event. The end of service is declared in the same way, which makes the handover explicit.

The heart of the activity is the duty log. Every event is recorded there with its type, its place and its time, then followed up until it is closed. Nothing is lost between two teams, and the history remains available. Around this register, the agent runs the missions assigned to them and tracks those of the day, completes control checklists, and reviews the patrol activity carried out on the site.

Several routine operations have their own screen. Key lending and return are traced, cabinet by cabinet. Fire permits are issued and then followed up until they are closed, which is essential to frame hot work. People movements observed by the teams are recorded as they happen. Internal messaging finally makes it possible to send a message to a colleague and to see at a glance which agents are on site.

On the supervision side, activity reports are generated and printed over the period of your choice, and statistics and dashboards give the overall view: volume and nature of events, activity by site and by period.

What the administrator sets up

The setup starts with places, described in finer detail than in the other products: buildings, sectors, streets and rooms, to which events are attached. Across several sites, sites and site groups determine the scope visible to each team.

Then comes the substance of the duty log. Events are organized into families, with their fields and their rules, and completed by the events the application generates automatically. Instruction sheets and permanent instructions form the library that agents consult at shift start, and shift periods describe how your teams' hours are split.

Planned activity is prepared in two ways. Missions are defined by type and schedule, then placed in an agenda. Patrols are described by their routes, the tags placed at checkpoints and the patrollers allowed to perform them. Checklists structure the controls to carry out.

That leaves resources and people. Key cabinets, keys and loan authorizations frame lending. Agents, teams and qualifications determine who may do what, and user rights groups define what each person sees in the application. Resident and visitor records, finally, are shared with the reception logic of the site.

What connects to your environment

Hamilton Security communicates with your mail server for alerts and report deliveries, and with your other applications through the Hamilton API. General settings and labels make it possible to adapt the wording of the application to that of your teams, which matters particularly in a profession where terms vary from one organization to the next.

Workstations and their peripherals are declared site by site, so that each security post has what it needs. Custom report templates finally let you produce documents in your own format, or in the one expected by your client if you operate on behalf of a third party.

Where to start

If you are an agent, see "Start and end your shift" then "Consult instructions and shift-start sheets" and "Keep the duty log: record, follow up and close events". For the day's tasks, see "Run missions and track daily missions" and "Complete checklists".

If you supervise operations, see "View statistics and dashboards" and "Generate and print activity reports". If you are preparing the rollout, start with "Set up locations: places, buildings, sectors, streets and rooms" then "Configure events, event families and system events" in the Hamilton Security administrator guides.

Did this answer your question?