III. Results

This section presents the one-month pilot results of Spark Mobile, assessing its effectiveness in achieving the project’s core objectives. The goal of automatically updating the analytics dashboard every hour is evaluated through system logs and data synchronization accuracy. The enforcement of the policy requiring car wash businesses to actively update 4 to 8 new service offerings is measured through service management records. Lastly, the objective of maintaining an average waiting time of 20–30 minutes for regular car wash packages is assessed using recorded service durations. The findings highlight Spark Mobile’s performance in system automation, business participation, and operational efficiency in delivering timely car wash services.

General Objective: Automatically update the analytics dashboard accurately every hour.

Login Time (YYYY-MM-DD HH:MM:SS)	Log out Time (YYYY-MM-DD HH:MM:SS)	Duration	Status
2024-10-10 20:59:53	2024-10-10 22:00:54	1 hour and 1 minute	Offline
2024-12-10 00:00:53	2024-12-10 00:30:53	30 minutes	offline

Table 1: User Login and Logout Information

The presented data in Table 1 provides empirical evidence regarding user session characteristics that directly inform the system's capability to achieve its general objective of executing hourly automated updates to the analytics dashboard. The recorded sessions demonstrate significant variability in duration, ranging from a concise 30-minute interval to a 61-minute session that marginally exceeds the designated update cycle. Both recorded instances conclude with an "Offline" status, suggesting an automated termination protocol. This temporal data carries important implications for the dashboard's update mechanism, particularly concerning data integrity maintenance during transitional periods between update cycles. The observed session patterns necessitate robust temporal synchronization protocols to ensure update accuracy, especially when user sessions either terminate abruptly or extend beyond standard update intervals. These findings underscore the technical requirement for the system to accommodate temporal anomalies while maintaining uninterrupted data currency, thereby preserving the analytical dashboard's reliability and precision in reflecting real-time user activities.

Specific Objective 1: Maintain the 20 – 30 minute average waiting time for customers availed for regular car wash packages.

Slot	Date	Time	Current System (hh:mm:ss)	Spark Mobile (hh:mm:ss)	Time Difference (hh:mm:ss)
1	11/14/2024	10:00 AM	00:45:29	00:29:27	00:16:02
2	11/14/2024	05:30 PM	00:33:20	00:20:19	00:13:01
3	12/9/2024	12:16 PM	00:55:19	00:27:00	00:41:09
Average Waiting Time:			00:39:24	00:24:53	00:14:31

Table 2: Compared Average Waiting Time of Current System and Spark Mobile

The data presented in Table 2 evaluates Spark Mobile's performance in achieving Specific Objective 1: maintaining a 20–30 minute average waiting time for regular car wash packages. The results demonstrate a consistent reduction in waiting times compared to the current system, with improvements ranging from 13 minutes (33:20 vs. 20:19) to 41 minutes (55:19 vs. 27:00). On average, Spark Mobile decreased waiting times by 36.9%, from 39 minutes 24 seconds to 24 minutes 53 seconds, nearing the target benchmark. Notably, the platform maintained efficiency even during peak hours, as seen in the 12:16 PM slot, where it reduced wait times from 55:19 to 27:00. These improvements suggest that Spark Mobile's optimized scheduling and digital workflow management enhance operational efficiency. However, the 24:53 average still slightly exceeds the ideal range, indicating potential for further refinement in demand distribution and service transitions. Overall, the findings validate that digital transformation significantly improves service speed and reliability in car wash operations.

Specific Objective 2: Implement a policy for car wash businesses to update 4 to 8 new service offerings actively.

Current System
PubMat	Date Posted	Date Updated
Tarpaulin	June 15, 2021	October 19, 2023
Tarpaulin	October 19, 2023	November 14, 2024

Table 3: Current System Service List Updates

The data in Table 3 demonstrates the current system's inadequate service update frequency relative to Specific Objective 2's requirement of maintaining 4-8 active service offerings. Analysis reveals only one service type ("Tarpaulin") was updated twice across a 40-month period - first after 28 months (June 2021 to October 2023), then after 13 months (October 2023 to November 2024). This update pattern shows neither consistency in timing nor diversity in services, falling significantly short of the target range. The prolonged intervals between updates (averaging 20 months) and singular service focus indicate systemic limitations in service innovation management. These findings substantiate the necessity of implementing structured update policies to ensure regular refresh cycles and service portfolio expansion. The current practice of irregular, minimal updates fails to meet industry standards for dynamic service offerings, negatively impacting competitive positioning and customer retention. Implementation of the proposed policy would establish measurable benchmarks for both update frequency (quarterly recommended) and service variety (4-8 offerings), addressing these operational deficiencies while aligning with market expectations for continuous service innovation.