1. Detect includes the when a car is trying to enter a society complex. It could use different hardware solutions for detecting a vehicle like weight, magnetic loop, sensors and solar sensors

2. Identification is done by VRN which can be achieved by different ways like ANPR , RFID tags and NFC to identify and map the RFID tags to the VRN and VRN to the user details

3. Validation is can be done by the backend systems where we have the registered RFIDs and we can map the data of the vehicle trying to enter the society via RFID and map those to the users eventually

4. Action is the after process of validation, that if validated the boom barriers can open or close depending on the validation

STEPs redefined

Detect: To detect when a car is trying to enter a society complex, we can use different hardware solutions like weight, magnetic loop, sensors, and solar sensors. These sensors can be installed at the entrance of the society, and the data collected by these sensors can be sent to the app's backend.

Identify: To identify the vehicle, we can use ANPR, RFID tags, or NFC. ANPR can be used to capture the license plate number of the vehicle, which can be used to identify the owner of the vehicle. RFID tags can be attached to the vehicle, and the tag information can be stored in the app's backend, along with the user details. NFC can be used to enable contactless identification of the user and the vehicle. Once the identification is complete, the app can map the RFID tags to the VRN and VRN to the user details.

Validate: The validation can be done by the app's backend systems, where we have the registered RFID tags and vehicle information stored. The app can check if the vehicle and the user are authorised to enter the society. If validated, the app can trigger the action to open the boom barriers.

Action: The action after validation can be to open or close the boom barriers depending on the validation result. The app can trigger the action to open the boom barriers, and the security guard present at the entrance of the society can ensure the smooth entry of the vehicle.

The relevant stake holders would be :

1. the end users/car owners/residents of the society

2. Operator - the security guard who will be present at the entrance of the society

3. Client - the society admin who will be appointing the Operator

4. Us - as a company who will be setting up all of this - park+

Onboarding

Project onboarding - this goes with the pre sales effort from the Park+ team to get any society onboarded, once onboarded all sorts of data is collected such as Name, location, Tags, flats in that location, hardware needs etc

User Onboarding - Park+ hosts a workshop called Carnival after the project onboarding, the event is help to provide RFID tags to the project and the users are onboarded, the user install the park+ app enters the vehicle details and enters the RFID and secret code( the envelope) provided to them at the Carnival which will already be mapped in your DB to that project and now is mapped to that vehicle as well. similar flow is there for self onboarding (without carnival) as well

There are 2 deliverables from park+

the Park+ app and the Client dashboard that is provided to the Project admin to monitor everything and on about the society parking.

Possible features without referring to the existing ones

Real-time monitoring of parking availability and occupancy for the entire society or multiple parking lots within the society.

Reports on usage and revenue generation for each parking lot or the entire society, enabling better financial planning for the society admin.

Automatic billing and payment processing for parking fees, with flexible pricing options that allow the society admin to set different rates for different parking slots based on location, size, etc.

Integration with navigation apps to help users locate their parking spot, with the app providing a map of the society showing the location of available parking slots.

A feedback system to allow society admins to collect feedback from users and improve the overall parking experience.

checking out all the services and processes in the Society product

there are different ID mapping at different services that exist for the entire ecosystem

Infra - Infra refers to the entire project, all information regarding the project ( society) no. flats , how many and what tags are mapped to that prticular project and sorts

Hardware - hardware refers to all the hardware products, the boom barrier etc

Firmware - Firmware interacts with the hardware and verifies the command.

Vehicle - the vehicle service is where the vehicles are mapped to Infra service where you could fetch that this X vehicle is from the Y society

Activity - Records all acitivities and communicates with other services , like the car entering and leaving the Infra, a new tag being registered and mapped to a user in that Infra(Infras are given an x+500 amount of tags which are already mapped to that Infra)

User - User services refers to all the information regarding the user and the mapped vehicle for that user

Notification

tell me how i will achieve each step using different technologies and how will we incorporate this in an app

how will be the onboarding look like for both Society and the end user?

how will we get them onboarded and what should our strategy be?

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.