Parking Management Solution
Business Use Case
Serene Township (ST) is easily the biggest integrated township in Bengaluru, India consisting
currently of 15 high-rise buildings – branded as Serene High, 50 individual houses – branded as
Serene Luxury, a hospital, a supermarket, a restaurant, a bank and a school. This township sees a lot
of visitors every day. Each of the above entities have got ample parking spaces for visitors who have
to pay per hour basis for using the parking lot at the time of exit.
With the ST estate management team focussing on reducing the townships carbon footprint, one of
the initiatives has been to give a 20% discount to Electric Vehicles on parking.
Create a Salesforce based solution for the estate management team of ST can achieve the above
objectives.
ERD
Types of Users
Builder, Estate Manager, Security Guard
Use Cases
1) Use standard object Account to designate each of the current 7 entities in Serene Township.
Use an appropriate standard object to keep information of the various persons from these
entities who also act as points of contact for the ST estate management team (e.g. Serene
High could have at-least 15 people who are Association Presidents from each of the 15 high
rises, the Bank could have one or more people nominated to act as points of contact for the
estate management, etc.).
2) Accounts can only be created by the Builder. Others can only view the Account records.
3) There should be a field on the Account object that indicates the number of visitor Parking
Slots. If a new value is entered, then the system should automatically create those many
Parking Slot records. If an existing value is changed and saved, then the system should
automatically create or delete Parking Slot records to match that number (delete only empty
parking slots; slots created the newest should be prioritized for deletion first).
(Implementation guideline: use Flows to achieve this).
4) Each Parking Slot should have a unique alpha-numeric name which is also painted on the
floor of the parking slot.
5) Each of the Accounts has a team of Security Guards. A Security Guard team is the owner of
the Parking Slot records of the Account to which he\she belongs. (Implementation guide: use
the concept of Queues for a team of Security Guards).
6) The Status field (Occupied \ Free) on the Parking Slot object is the only thing a Security
Guard can edit. It is used by them to mark whenever is slot if Occupied or Freed – however
they should not be able to see the Parking Slots list view since they set Occupied \ Freed via
Screen Flows.
7) There should be a screen flow on the Home Page of the app that allows the Security Guard
to select a ‘free’ Parking Slot and set it’s status to Occupied. While doing this, the guard
should also be prompted to enter the vehicle number and upon submission, a new Vehicle
record having the record Name as that entered number should also be created. If a record
already exists with the same vehicle number, then the details should just be displayed. In
both cases, the Entry Time field on the Vehicle should be stamped with the current date-
time.
8) There should be another screen flow on the Home Page that allows the Security Guard to
select a Parking Slot and set it’s status to Freed. This screen flow should also show the
details of the Vehicle that is exiting the Parking Slot and its Exit Time field should be stamped
with the current date-time. When the status is set to Freed, a Bill record should be
automatically created by the system.
9) The Amount field of the Bill record should have a value of: Rs.0 if time parked < 2 hours OR a
value calculated at Rs.50 per hour for every hour after the first 2 hours (Implementation
guideline: use Apex to achieve this).
10) Every time a new Vehicle record is created, the system should be able to identify if it is an
Electric Vehicle or not. This is done based on the fact that Electric Vehicles have a vehicle
number that always starts with EV. If it is an Electric Vehicle, then the Bill record generated
should show Amount, Discount Percentage and Discounted Amount fields. A 20% discount
has to be applied to the Amount. (Hint: 2 different page layouts are expected for Bills for EVs
and that for regular vehicles).
11) Estate Managers (there is one Estate Manager for each of the 7 Accounts currently) are
owners of the Account records. Each Estate Manager can only see his\her own Account.
Also, like Security Guards, they cannot create or edit the Accounts.
12) Only Estate Managers can see a field call Parking Revenue on the Account records. It should
show the sum of all the Amounts of Discounted Amounts of the Bills generated under that
Account.
13) As per legal requirements, Vehicle details should not be stored in the system for more than
one year. Hence every day, there should be some mechanism with which all Vehicle records
over a year old get deleted.
14) Estate Managers, in the Home Page, should see a Dashboard that shows them various
essential information.
15) Ensure that overall test class coverage is over 95%. Test classes should have positive and
negative test scenarios.
