At the gate and on site Level two within a short time Works without a connection

Custom app for access and patrols at a port facility

Raising the security level to level two is not an announcement but a series of actions on site: extra checks, different access rules, monitoring of restricted zones. Those actions are carried out by people at a gate and on a quay, and you only know whether they were done if someone recorded it there.

Why the site is the point of execution

Every ISPS-regulated port facility works with an approved security plan, a designated security officer and three security levels. The plan describes access control, restricted zones, personnel screening, cargo handling and drills.

The plan itself is fixed and is usually in order. What is missing is the trail of execution. When the level is raised, extra measures must be put in place within a short time, and they are carried out by the gate guard, the crane operator and the team patrolling the quay. Without recording at that point, confirmation to the officer is just a phone call.

The same applies to day-to-day operations. A driver without an appointment, a contractor who wants to enter the site unescorted, a gate left open: those moments happen at the gate and disappear into a watch log that nobody searches.

How we build this

The action at the gate is the unit here. If that is where you record who came in and which measure is active, your accountability follows from it.

1
Walking the gate and the quayside with your team

We look at how much time there is per vehicle, who is on duty and what is written down at the moment. That shapes the design more than the plan does.

2
Designing the level change as an action

Who is notified, who confirms which measure, and within what time. This is the core of it, and it is rarely set up properly.

3
Offline as the starting point

On a quayside, in a warehouse or among containers, the network drops out. The app keeps working and syncs later, with the actual timestamp.

4
Rehearsing a level increase

We run through an increase and measure how long it takes before every measure is confirmed. That figure is your real response capability.

What the app actually does

The app does little, and that little has to work in the rain and in the dark. Which components you need depends on the size of your site.

Checking access at the gate

Scan a pass or search by name and see whether this person or vehicle is allowed on site, in which zone and until when. Green or red, not a list someone has to search through.

Level change with confirmation per measure

When the level goes up, everyone is notified and each person responsible confirms their measure. Afterwards you have a record of how quickly everything was in place and who did what.

Patrols along restricted zones

For each patrol, which points are due, with a tag at the object. A patrol ticked off without proof of presence is just an assertion when the authorities come to inspect.

Deviations recorded immediately

An open gate, an unescorted visitor, a skipped check. Each one becomes an action with an owner instead of a line in a watch log.

Working fully offline

Checks, patrols and reports carry on without a connection and sync later, with the actual timestamp.

Connecting to the gate and the security plan

Passes and barriers already exist; we connect to them through integrations. The register side is covered on ISPS software.

Who we build for

What happens on your site determines where the emphasis lies. Four situations.

Terminals and storage and transhipment

Heavy traffic and many external drivers. Speed at the gate decides whether the check is actually done or whether the queue grows too long and people get waved through.

Industry with its own quay

Little traffic but the same requirements. There is no gatekeeper, so the check falls to someone who does it on top of other work, and it has to fit into a few taps.

Port companies with multiple facilities

The level often changes for the whole area while each facility has its own plan. You want to confirm per facility and see across the whole where things are not yet in place.

Contractors and maintenance on site

Work on installations brings in people who need escorting. This is the point where access control gets stretched in practice and where recording pays off most. If your site also falls under the Wwke, a second accountability obligation runs alongside it.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The app is the field side of your security plan and does not change that plan. What it records ends up in the register you use to account for yourself.

React Native or native iOS and Android Offline storage with the actual timestamp Access control by pass or name Zone and validity checks Level change with confirmation per measure Patrols with tags at the object Deviations with owner and deadline Visitor and escort registration Integration with access systems Integration with the measures register Works in the dark and with gloves on Remote device management Audit logging per action Hosting in the EU

Why Appfront

A level increase is a series of actions

We have each measure confirmed by the person who carries it out. A message to the group does not prove that it is actually active.

Inspectors ask for access to records, not a plan

We build the trail of checks, rounds and exercises, because that is what gets requested and what paper cannot deliver.

There is no signal on a quay

Offline is the starting point. An app that stalls between containers gets replaced by a nod from the gatekeeper.

Third-party data sits at the gate

Drivers and contractors are not your staff. We only show what the check requires and keep visitor data for a limited period.

Security and privacy

A device at the gate holds the key to your site: who may go where, which zones are restricted and which measures belong to which level. That is exactly the overview someone with bad intentions is looking for. We tie permissions to the user rather than the device, show each role no more than the check requires, limit offline storage to the shift at hand and make sure a lost device can be disconnected remotely.

Registering people also calls for restraint. Drivers and contractors are not your employees, and what you record about them you process on the basis of a legal obligation, not because it is convenient. We therefore do not show document numbers where a name will do, and we set an explicit retention period on visitor data instead of keeping it indefinitely. The evidence the app produces, on the other hand, must be tamper-proof. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.

Frequently asked questions about the port security app

No. Gates, passes and barriers stay; we connect to them. What the app adds is the reason behind a permission and a record of what was checked: which zone, on the basis of which screening, until when, and who assessed it.

When the level goes up, those involved receive a message with the measures that apply to them, and each person responsible confirms that their measure is active. That way you can see afterwards how quickly everything was in place and which measure lagged behind, instead of relying on a round of phone calls.

Yes, that is the starting point. Checks, rounds and reports are stored locally with the actual time and synchronise as soon as there is a connection. Between containers and in sheds, having no signal is the normal situation.

Usually yes, with their own roles and access limited to the facility where they work. What you want to avoid is the evidence of your security sitting in your security supplier's system, because you are the one who is accountable.

As little as possible: enough to justify access and no more. We do not show document numbers where a name will do, and we set a retention period on the data. What exactly is permitted depends on your security plan and on privacy rules; agree this up front.

This app is the field side. The ISPS software is the register of measures per level, screening validity, exercises and reporting to the supervisory authority. They share a single data source.

Yes, and that is often the second benefit. An exercise consists of actions on the site, and you record those with the same app: who took part, what went wrong, what was done about it. That material ends up in the file you make available for inspection on request.

That depends on the number of gates and facilities, whether it integrates with existing access control systems and whether visitor registration is required. Access control with rounds is usually usable quickly; integrations with gate equipment cost more. We give a substantiated estimate after the discovery phase.

Want to know how quickly level two is really in place?

At the next exercise, ask how long it took before each measure was confirmed as active. If nobody knows, that is the work to be done. We build this as a standalone app and as part of a broader custom app or custom software project.

Edit content