Vehicle gate control
Vehicle Release Control
The system lets gate staff release a vehicle from the service department only after its repair order has been cleared in the DMS.
Problem
A vehicle was released from the service department using a printed document or phone confirmation. The transaction was not recorded in any system, so staff could not later determine which vehicles left, when, or who was responsible.
Solution
The version under development checks eligibility in the DMS through the gateway, retrieves the repair order again at confirmation, and records the release only if the source still reports a valid status.
Progress
The implemented version already supports gate access, lookup, revalidation, duplicate-safe recording, and auditing. The production integration is validated by location before the application goes into operation.
My role
I designed and built the gate workflow, gateway integration, duplicate prevention, and updates for connected screens.
How it works
The workflow, still under development, checks the current DMS status before recording a vehicle release at a dealership location.
Scroll horizontally to view the full diagram.
Key functions
- Current list of repair orders eligible for release, by location.
- Release confirmation checks the source record at the time of the transaction.
- Gate staff use their own credentials, with the location determined by the access point.
- An audit record for every attempt and confirmation, linked to the session and location.
- Three business roles: gate staff, corporate staff with access across locations, and administrator.
- Blocks the release if the repair order changes or the location's DMS does not confirm it.
- Synchronizes the location directory with the gateway after validation.
Technical details
- Backend
- NestJS 11 · TypeORM · PostgreSQL 15
- Frontend
- React 19 · Vite · TanStack Query · Zod · Tailwind 4
- Infrastructure
- Elastic Beanstalk · RDS PostgreSQL · SES
- Data source
- GP Data Gateway · repair orders cleared in the DMS