United StatesA React Native application that helps Birdi's airport officers scan, capture and approve vehicle checkpoint transactions, online or offline.
Birdi
AviationBirdi required a mobile application for officers managing vehicle checkpoint activity at Los Angeles airport facilities. The application needed to support the work officers perform at a checkpoint: confirming the correct checkpoint post, checking the people and vehicles requesting access, capturing supporting information and recording the final decision.
Softlabs completed a React Native application for Android and iOS that brings checkpoint validation, badge scanning, QR code verification, document capture, licence-plate capture, officer review and transaction records into one mobile workflow.
Validation, scanning, capture, review and decision in a single application.
OCR assists the officer; the officer still reviews, corrects and decides.
Designed around what an officer actually does at a checkpoint post.
Airport checkpoint officers need a clear way to check people, vehicles and supporting documents while keeping a record of each transaction. Birdi needed one mobile application that could support these steps across different checkpoint situations.
An officer may need to review badge details, vehicle information, documents, licence plates, visitor information and escort details. Entering all of this manually can create extra work and inconsistent records.
The application was designed to reduce manual entry by using badge scanning, QR scanning, document capture, licence-plate capture and OCR.
A standard visitor, an escorted visitor, a vehicle and a medical escort do not always follow the same checkpoint process.
Birdi needed an application that could guide officers through the correct workflow and collect the relevant details for each transaction type.
Officers may need to record checkpoint activity when the network connection is unavailable or unstable.
The solution therefore needed a local transaction queue and configurable offline synchronisation so stored records could be sent when synchronisation was available.
Softlabs built a React Native airport checkpoint application for Android and iOS. An officer signs in through Okta with multi-factor authentication and validates the selected checkpoint post using GPS, then begins the correct visitor, vehicle, escort or medical escort workflow.
During a transaction the officer can scan a badge or QR code, capture documents and licence plates, review OCR-extracted information and correct it when needed, then approve or deny the transaction. Queued activity is stored locally with configurable offline synchronisation.
How It Works
The officer signs in through Okta and completes multi-factor authentication before using the checkpoint application.
The officer selects the post where they are working. GPS supports validation of the selected checkpoint location.
Supported workflows include visitors, vehicles, escorts and medical escorts.
A badge or QR code is scanned when available, bringing visitor information into the transaction.
The officer uses the mobile device to capture a supporting document or a vehicle licence plate.
OCR reads the captured image and shows the result to the officer, who can check and correct it before continuing.
Visitor, vehicle, escort and document information is checked together, with alerts flagging relevant items.
After completing the required checks, the officer records an approve or deny decision.
The completed transaction joins the record, available later through transaction history.
Without synchronisation, transactions stay queued locally and are sent once syncing is available again.
The Birdi application includes a workflow for recording an emergency vehicle checkpoint transaction, keeping it inside the same mobile application while allowing it to follow its own path.
Problems & Fixes
Each challenge is paired with the application’s response, so you can see exactly how the workflow supports officers.
Tap to explore each challenge
Officers may need to enter the same type of information manually: badge, document, vehicle and licence-plate details.
The application supports badge scanning, QR scanning, document capture, licence-plate capture and OCR. Officers can review and correct the extracted information before saving it.
Officers need to confirm they are working at the correct post, with a clear connection between the transaction and the selected checkpoint.
The officer selects the checkpoint post, and GPS supports validation of the selected location.
One process does not fit every checkpoint visit: visitor, vehicle, escort and medical escort transactions require different information.
The application provides separate workflows so officers can follow the relevant process for each transaction type.
OCR information may need human correction, as text extracted from a document or licence-plate image can be imperfect.
The application shows extracted information to the officer and allows review and correction before the transaction continues.
Officers need a clear final decision. A checkpoint record must show what happened at the end of the review.
The officer can approve or deny the transaction after checking the required information.
Network access may be limited, and a weak connection can prevent immediate synchronisation.
The application includes a local queue and configurable offline synchronisation for records waiting to be sent.
Previous activity needs to remain available for officers reviewing earlier checkpoint transactions.
The application includes transaction history and detailed transaction records.
Problems & Fixes
Each challenge is paired with the application’s response, so you can see exactly how the workflow supports officers.
Officers may need to enter the same type of information manually: badge, document, vehicle and licence-plate details.
The application supports badge scanning, QR scanning, document capture, licence-plate capture and OCR. Officers can review and correct the extracted information before saving it.
A cross-platform airport checkpoint application that brings post validation, identity and vehicle checks, image capture, OCR review, transaction decisions, alerts, history and offline queuing into one mobile system.
Sixteen capabilities, grouped by the part of the checkpoint they support, from officer sign-in through to what happens when the network drops.
4 features
Officers access the application through Okta and complete multi-factor authentication.
The officer selects the post where the transaction is taking place.
GPS supports validation of the selected checkpoint post.
The application can scan a badge during the checkpoint workflow.
4 features
Officers scan QR codes as part of visitor or vehicle verification.
The mobile device captures images of supporting documents.
Officers capture a vehicle licence plate during a transaction.
OCR extracts supported information from captured images.
4 features
The officer checks and corrects OCR-extracted information before continuing.
Separate processes for visitors and for vehicles.
Escort and medical escort information recorded in the relevant workflow.
The officer records the final checkpoint decision in the application.
4 features
The application can show alerts during checkpoint activity.
Officers view previous transactions and their recorded details.
Transactions wait locally when synchronisation is unavailable.
Offline synchronisation can be configured for queued records.
A similar checkpoint application can support organisations that need to verify people and vehicles before allowing access to a controlled location.
Softlabs can help you plan and build a mobile checkpoint application for visitor, vehicle, escort and document-verification workflows.
Discuss Your Checkpoint ApplicationAnswers about how the checkpoint application works, what it covers and how it behaves offline.
An airport vehicle checkpoint management system is software that helps officers check people, vehicles and supporting information at a controlled access point. It can guide officers through badge or QR scanning, document capture, licence-plate verification, visitor and escort details, alerts and the final approve or deny decision.
Softlabs completed a React Native checkpoint application for Birdi for use by airport officers at Los Angeles airport facilities. The Android and iOS application supports Okta sign-in with MFA, GPS checkpoint validation, badge and QR scanning, document and licence-plate capture, OCR review, multiple checkpoint workflows, transaction decisions, alerts, history and offline queuing.
The officer opens the scanner during a checkpoint transaction and scans the available QR code. The scanned information becomes part of the transaction workflow so the officer can review it together with the other visitor, vehicle and document details before making a decision.
Yes. OCR assists with extracting supported information from a captured document or licence-plate image, but the officer remains responsible for reviewing it. The application allows the officer to correct the extracted information before continuing with the transaction.
Yes. The application includes workflows for visitors, vehicles, escorts and medical escorts. This allows officers to collect information relevant to the type of checkpoint transaction instead of using one identical process for every visit.
The application includes a local queue and configurable offline synchronisation. When immediate synchronisation is not available, transactions can wait in the local queue and be sent when synchronisation becomes available. The exact synchronisation behaviour depends on its configuration.
