Custom software for the ISPS security plan
Every ISPS-regulated port facility has an approved security plan. What is rarely there is evidence that the measures in that plan were carried out when it mattered. And the moment that matters most is the switch to a higher security level: that is when measures nobody has practised this month have to be put in place within a short time.
Why the level change is the pivotal moment
The ISPS Code has applied to ships and port facilities since 2004. In the Netherlands, implementation is laid down in the Port Security Act (Havenbeveiligingswet), with the measures prescribed in European Regulation 725/2004. Each facility must have a security assessment, an approved security plan, a designated security officer and operate at one of three security levels.
The plan describes access control, restricted areas, screening of personnel, cargo handling and drills. The security officer oversees this through their own inspections, organises drills and training, and sends the report of the annual full-scale exercise to Bureau Port Security. Reports of all exercises must be made available to the supervisory authorities on request.
What a plan does not solve is execution under time pressure. When the level is raised to level two, different measures apply: more checks, different access rules, extra monitoring of restricted areas. These are in the plan and then have to be put in place within a short time. If you are searching a folder at that moment for which measures apply and who carries them out, you are too late, and if you cannot show afterwards that they were carried out, you have a problem with the supervisory authorities.
This page is about management and the plan. Registration on the quayside itself, at the gate and during the patrol, is described under the access and patrol app for a port facility.
How we build this
Here the measure is the unit, not the plan. If every measure is tied to a level and to someone responsible for carrying it out, a level change becomes a button rather than a meeting.
We convert the approved plan into individual measures, each with an owner, a level and a check point. The plan itself remains the authoritative document and does not change.
What happens when the level goes up, who is notified and who has to confirm. This is the part where most facilities rely on experience rather than on how things are set up.
Access checks, inspection patrols and drills are recorded at the moment they happen rather than collected afterwards. Evidence that depends on manual work is missing exactly when you need it.
We simulate a level increase and measure how long it takes for every measure to be confirmed. That time is your actual response capability.
What the software actually does
The register of measures per level underpins everything. Which components you need depends on the size of your facility and on how many parties come onto the site.
Measures per security level
For each measure: which level activates it, who carries it out and how it is confirmed. A plan in text cannot answer that question at the moment the level goes up.
Level change with confirmation
When the security level is raised, the notification goes out to everyone involved, and each measure is confirmed as active. Afterwards there is a record of when the level changed and how quickly everything was in place.
Access, screening and restricted zones
Who may go where, on what grounds and until when. Screening validity periods and access rights expire, and discovering an expired authorisation during an inspection is the worst possible moment.
Exercises and training on record
When an exercise took place, who took part, what went wrong and what was done about it, including the annual full-scale exercise and the report that follows from it.
Incidents and deviations with follow-up
An open gate, an unescorted visitor, a skipped check. Each becomes an action with an owner and a deadline instead of a note in a guard logbook.
Evidence for inspections in one place
Exercise reports, completed checks and level history in a single overview, ready to present for inspection. During an inspection, how quickly you can show it is a signal in itself.
Who we build for
What happens on your site determines where the emphasis lies. Four situations.
Terminals and storage and transhipment
Heavy traffic, many external drivers and changing shifts. Access control is the largest volume here and, at the same time, the part of the plan most often bypassed.
Industry with its own quay
You see yourself as a producer, and yet you have a security obligation as well. The organisation isn't set up for a security officer, while the requirements are the same as for a terminal.
Port companies with multiple facilities
Each facility has its own plan and its own officer, but the level often changes for the whole area. You want to be able to steer per facility and report across the whole.
Contractors and maintenance on site
Work on installations brings people on site who shouldn't be there without an escort. That is exactly the point where access control gets stretched in practice. If your site also falls under the Wwke, a second accountability obligation runs alongside this one.
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 security plan is approved and doesn't change lightly. Everything relating to its implementation should therefore be configurable without changing the plan itself, and stored per version.
Why Appfront
The level change is the real work
We build it as an action with confirmation per measure, so that afterwards it is clear how quickly everything was in place and who did what.
Inspectors ask for access to records, not a plan
Exercise reports must be made available for inspection on request. We bring that evidence together instead of collecting it from scratch each time.
Authorisations expire silently
Screening and access rights have end dates that nobody keeps track of. We monitor them and flag them in advance rather than during an inspection.
Connecting to your access system
Gates, passes and cameras already exist. We connect to them through integrations instead of building a second access administration.
Security and privacy
With this subject, the content of the system itself is the risk. An overview of your restricted zones, your measures per level and your outstanding shortcomings is exactly the document someone with bad intentions is looking for. We therefore set access tightly per role and per facility, show no more than a function needs, and log every view. Even administrators don't automatically see everything.
There is also a personal data side that weighs more heavily than with an ordinary access app. Screening staff touches on personal privacy, and visitor registration means recording data about people who do not work for you. We keep the minimum: the outcome and the expiry date rather than the investigation itself, and visit data with an explicit retention period rather than indefinitely. The evidence the registration 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 CVD policy.
Frequently asked questions about ISPS and port security
For each port facility: a security assessment, an approved security plan, a designated security officer and operation at one of three security levels. Among other things, the plan describes access control, restricted areas, screening of personnel, cargo handling and exercises. In the Netherlands, implementation runs through the Port Security Act (Havenbeveiligingswet), with the measures from the European regulation.
No, and it can't. The plan is approved and remains leading. What we build is its execution: linking measures to levels, having level changes confirmed, and recording exercises and checks. If the plan changes, the set-up changes with it, not the other way round.
Then the additional measures from your plan apply, and they must actually be active within a short time. In practice, things go wrong not because people don't know what has to happen, but because nobody has an overview of what is already in place and what is not. That is why we build confirmation per measure rather than a notification to the group.
The report of the annual full-scale exercise goes to Bureau Port Security. In addition, reports of all exercises must be made available to the supervisory authorities on request. That means even the smaller exercises must be easy to find, and those are precisely the ones that now usually disappear into a mailbox.
If your facility is subject to ISPS, the same requirements apply as for a terminal, regardless of how you see yourself. For industrial companies this is often the unpleasant discovery: it comes with a designated officer, a plan and an exercise schedule. Whether your quay falls under it is decided by the competent authority, not by your size.
Usually yes, and that is the biggest gain, because access control has the highest volume. We connect to your existing access system through integrations, so that permissions are managed in one place. What we add is the reason behind a permission: which zone, on the basis of which screening, until when.
Terminal operations is about cargo flows, planning and handling; see port software and maritime software. ISPS is about the security of the facility and about demonstrability towards the supervisory authority. They share the terrain and little else.
That depends on the number of facilities, whether access and visitor registration are included, and whether integrations with existing systems are needed. The measures register with level switching is usually quick to put to use and gives you an immediate overview; integrations cost more. We give a well-founded estimate after the discovery phase.
Demonstrating level changes and exercises?
Ask how long it takes before all level-two measures are confirmed active, and look at where that answer comes from. That is the question that comes back in an audit. We build this as a standalone application and as part of a broader custom software project.