Booking and departure information can support an operator’s security procedures. The applicability of ISPS requirements and the approved security process must be determined by the responsible professionals.
Identify the checks, responsibilities and information required under the applicable ship and port-facility arrangements. Do not begin by assuming a ticket scan covers every access-control requirement.
The relevant security process determines which checks and records are needed. Booking details and ticket-control results may support parts of that process, but they do not replace a security plan or an authorised operating decision. Identify the information required at each point and assess the associated permissions and interfaces with the responsible professionals.
Passenger bookings, journey details and ticket-control results may form part of the operational information staff use. Confirm which records, permissions and interfaces the particular process requires.
The software supports configured workflows. It does not certify compliance, replace a security plan or decide whether an individual vessel or route falls within a legal regime.
IMO: SOLAS XI-2 and the ISPS Code
Review the applicable requirements with your designated security officer and competent authority.
Prepare passengers and vehicles for their departure by checking the booking and the details your operation requires.
Explore Check-in
Give the departure team a practical way to check tickets for the sailing they are boarding.
Explore Boarding
A passenger manifest concerns the people travelling, not simply the number of tickets sold.
Explore Passenger Manifest: Data & Operating ProcessBring your questions about software in isps-related workflows to a discussion of your routes and working procedures.
