The business processes outlined in the About the Requirements for the Motor Loaner System Requirements Sample Application topic will be accomplished with the following designs:
- About the Business Process Design
- About the Business Process Design
- About the Business Process Design
- About the Business Process Design
- About the Business Process Design
- About the Business Process DesignCheck-Out Wizard
- Check-In Wizard
- Service Ticket Generation Process Flow
- Service Ticket Approval Alert Process Flow
- Vehicle Status Updater Process Flow
- Management Reports
| Note |
|---|
For each item in this topic, the requirement or requirements from the About the Requirements for the Motor Loaner System RequirementsSample Application topic that are satisfied by the design appear after each numbered item in parentheses. |
Anchor Check-Out Wizard Check-Out Wizard
Check-Out Wizard
| Check-Out Wizard | |
| Check-Out Wizard |
The system will include a Check-Out Wizard that provides step-by-step instructions for a rental clerk to complete a rental check-out. The system automatically creates a Rental Agreements record for each check-out operation. The wizard will operate in conjunction with a Rental Agreements entity object, which will encapsulate the logic for creating the Rental Agreements record (so the behavior for creating a Rental Agreement manually and for using the wizard is the same; see BPR19: Enforce Rental Agreement Consistency).
- A Check-Out Wizard will be developed that allows the Rental Clerk to enter a rental period (start and expected return dates) and display the vehicles available for rent during the specified time period. This list can further be 'filtered' defining additional required features of the rental vehicle. (BPR13: Automatically Identify Available Vehicles; BPR14: Simplify Rental Check-Out Procedure; UIR1: Check-Out and Check-In Interfaces)
- The Check-Out Wizard will prompt for additional information if a vehicle chosen for rental has existing damage so the customer is not penalized for the damage upon return. (BPR15: Track Existing Damage)
- Any Rental Accessories will be available for selection and inclusion in the rental agreement from the Check-Out Wizard wizard as well. (BPR16: Track Rental Accessories)
- Once the Check-Out process is complete, the system will automatically update the vehicle's status to indicate that is it rented. (BPR11: Automatically Track Vehicle Status and Mileage)
| Anchor | ||||
|---|---|---|---|---|
|
The system will include a Check-In wizard that provides step-by-step instructions for a rental clerk to process the return of a rented vehicle. The system automatically updates an existing Rental Agreements record for each check-in operation. Note that the wizard will operate in conjunction with a Rental Agreements entity object, which will encapsulate the logic for updating the Rental Agreements record (so the behavior for creating a Rental Agreement manually and for using the wizard is the same; see BPR19: Enforce Rental Agreement Consistency).
- All fields of the Rental Agreement that should be filled out upon a vehicles return will be managed through a Check-In Wizard. (BPR17: Simplify Rental Check-In Procedure; UIR1: Check-Out and Check-In Interfaces)
- The Rental Agreements entity object will ensure that the ending mileage must be greater than or equal to the starting mileage. (BPR18: Ensure Ending Mileage Is Greater Than or Equal to Starting Mileage)
- The wizard will provide the rental clerk with the opportunity to indicate that a vehicle is being returned with new damage that requires repair. (BPR20: Automatically Send Damaged Vehicles for Servicing)
- Once the Check-In process is complete, the system will automatically update the vehicle's mileage based on the return mileage and the vehicle's status to indicate that is it either available for rent or has been sent for servicing. (BPR11: Automatically Track Vehicle Status and Mileage)
| Anchor | ||||
|---|---|---|---|---|
|
To address requirements BPR20: Automatically Send Damaged Vehicles for Servicing and BPR21: Automatically Determine If Vehicle Requires Scheduled Maintenance, the system will use a process flow fired before changes to a Rental Agreements record are committed.
...
The following diagram illustrates the proposed steps in this process flow:
| Anchor | ||||
|---|---|---|---|---|
|
To address the BPR23: Service Ticket Approval requirement, the system will use a process fired before changes to a Service Tickets record are committed.
...
The following diagram illustrates the proposed steps in this process flow:
| Anchor | ||||
|---|---|---|---|---|
|
To address the BRP24: Automatically Update Vehicle Status Once Servicing Approved requirement, the system will use a process fired after changes are saved to a Service Tickets record.
If the Service Ticket is saved with a Status of Complete and the Release to Fleet option selected (following a manager's approval), then the process flow will automatically determine if there are any other open Service Tickets for the same vehicle. If there are no open tickets, the vehicle's status is updated to Available. If there are open tickets, the vehicle's status is updated to Servicing. The process flow will use the Update Vehicles Record process component, which is generated automatically by Aptify when creating the Vehicles entity, to change the vehicle's status as needed.
The following diagram illustrates the proposed steps in this process flow:
| Anchor | ||||
|---|---|---|---|---|
|
The system will include two shared views available included on a manager dashboard to satisfy the reporting requirements, BPR25: Easily Accessible Reports to Determine Vehicle Status and BPR26: Easily Accessible Report to Forecast Vehicle Returns:
- Pie chart of all vehicles grouped by status with a specified drill-down List View that displays vehicle details for a particular status when an area of the chart is selected.
- List view display all rented vehicles expected to be returned on the current date.