Implementation of You Only Look Once (YOLO) Technology and Reinforcement Learning for Web-Based Project Monitoring ^†

Abstract

Project monitoring is an important element in project management that aims to ensure project implementation in accordance with the plan, schedule, budget, and objectives that have been set. The ineffectiveness of project monitoring can cause various problems, such as delays, cost overruns, inappropriate quality of results, and poor communication between stakeholders. To address these issues, technological advances such as YOLO (You Only Look Once) and Reinforcement Learning (RL) offer innovative solutions through real-time visual detection and data-driven automated decision making. This research aims to develop a web-based project monitoring system that integrates YOLO to detect activities in the field, such as workers and heavy equipment, and RL to provide optimal recommendations for resource management. The implementation of the system is expected to increase efficiency, reduce risk, and support more accurate decision making. Based on previous research, the adoption of AI technology in project monitoring is proven to reduce operational costs and increase productivity. This web-based system is designed to provide flexibility and accessibility, allowing users to monitor projects in real-time through an interactive interface. The expected outcome of this research is the creation of an effective technological solution to improving the efficiency of construction project management, as supported by the findings of previous research that shows the great potential of AI in the construction sector.

1. Introduction

Project monitoring is an important process in project management that aims to ensure that the implementation of the project runs according to the plan, schedule, budget, and objectives that have been set. In practice, project monitoring involves collecting, analyzing, and reporting project data on an ongoing basis to identify potential problems and take corrective action if needed. Problems that often arise due to the absence of project monitoring are difficulties in accurate estimation of project time and cost, delays in identifying the risk of project delays, complexity in the formation and management of effective teams, lack of real-time visibility of team productivity, and difficulty in optimizing resource allocation and budget. Digital project management faces complex challenges in ensuring a balance between productivity, budget, and deadlines. Project supervisors need to make quick and informed decisions regarding resource allocation but often lack accurate real-time data for decision making. Technological advances have presented various tools to support efficient project monitoring, one of which is the implementation of YOLO and RL technologies for project monitoring to provide innovative solutions to overcome challenges in project management, such as risk detection and resource optimization. Previous research shows that the adoption of AI technology in the construction industry can reduce operational costs and increase productivity [1]. The integration of YOLO and RL can result in a system capable of detecting visual conditions in real time and performing automated decision making. For example, YOLO can be used to monitor worker and machine activities at the project site, while RL can provide optimal recommendations based on real-time data analysis. Studies such as the one conducted by Chen show the effectiveness of this combination in smart surveillance systems [2]. The expected solution was to create a web-based application to offer flexibility and accessibility to monitor and manage projects efficiently. This technology allows users to access real-time project data through an interactive interface. Web-based systems supported by AI technology can improve the efficiency of supervision and decision making in construction projects [3].

2. Materials and Methods

A research methodology that can be used for the implementation of YOLO technology and Reinforcement Learning for web-based project monitoring is followed. As shown in Figure 1, the research stages consist of problem identification, project initialization, methodology, conclusions, and system implementation.

2.1. Problem Identification

Problem identification is carried out on data assumptions in one of the IT projects. Problems that often arise in the absence of project monitoring are difficulties in accurate estimation of project time and cost, delays in identifying the risk of project delays, complexity in the formation and management of effective teams, lack of real-time visibility of team productivity, and difficulty in optimizing resource allocation and budget.

2.2. Project Initialization

Project initiation is the initial stage in project management where the project idea or need is defined, evaluated, and approved to proceed. This stage involves identifying the objectives, scope, stakeholders, and required resources. Project initiation aims to ensure that the project is feasible and in line with organizational goals before resources are allocated. At project initiation, data are collected for risk analysis, project progress tracking, and performance evaluation [4]. Data collection includes budget prediction and optimization, estimation of project completion time, and team performance evaluation.

2.3. Project Monitoring Methods

Project monitoring is an integrated system that uses modern web technologies to monitor, analyze, and manage projects in real-time, with a focus on digital collaboration and data-driven decision making [5]. In other words, modern project monitoring uses web technology to integrate project management tools, data analysis, and team collaboration in one centralized system [6]. The project monitoring method uses two methods, as follows.

2.3.1. Yolo Method

YOLO as an algorithm uses a single convolutional network to simultaneously predict multiple bounding boxes and class probabilities, making it very fast compared to two-stage detector methods [7]. YOLO as a detector that optimizes speed and accuracy simultaneously by using one neural network to predict objects [8]. The YOLO method includes the calculation of bounding box prediction, intersection over union (IoU), and loss function.

2.3.2. Reinforcement Learning (RF) Method

Reinforcement Learning is a machine learning paradigm in which an agent learns through interaction with the environment, takes actions based on current conditions, and receives rewards as feedback to optimize its decision-making policy [9]. In this case, this method is used for decision-making policies in a project application. The reinforcement learning (RF) method includes the calculation of the Time Formula (days_simulated), Calculation of Steps for Time Calculation, Budget Formula, and Calculation for Each User.

2.4. Project Conclusion

The project conclusion is the final part of the project report or evaluation that summarizes the results, achievements, and overall evaluation of the project. This conclusion consists of goal achievement, team performance evaluation, and project budget.

2.5. System Implementation

The system implementation stage is part of the end of this research, which aims to prove that the YOLO and Reinforcement Learning methods are successfully used in project monitoring. The system implementation stage is the creation of a website-based system using the php programming language and mysql database. System builders include Requirement Analysis, System Design, Implementation, Testing, Deployment, and Maintenance [10].

3. Results and Discussion

The following are the steps in discussing the YOLO and Reinforcement Learning methods in project monitoring along with the implementation results in the form of systems, characteristics and elements, and the role of information systems.

3.1. Project Initialization

Project initiation is an important foundation for overall project success. Without this stage, the project risks problems such as waste of resources, misalignment of goals, or failure to achieve the desired results. In the data project, initialization is performed on data assumptions in one of the IT projects.

3.1.1. Subsubsection

The importance of financial statement analysis is evident in the budget forecasting process, which can be used to identify financial trends, forecast future funding requirements, and manage financial risks more effectively. With a good understanding of financial statements, project managers can optimize resource allocation and improve efficiency in project implementation [11]. The following data on the prediction of budget optimization were used in the study:

●

Total project budget.

●

Cost per team or per hour.

●

Completed assignments and their costs.

●

Estimated time remaining for the active task.

The project details, including the assumed project identity as shown in

Table 1. Assumed project identity.

Project Name	Description	Budget	Category
Mentory	Mentory is an innovative app designed to facilitate the search for professional mentors in various fields.	Rp. 150,000,000,-	Service Marketplace

and the cost per member as shown in

Table 2. Cost per member.

No.	Employee Name	Maintenance Cost	Expertise
1	Employee A	Rp. 21,000/h	Android Developer
2	Employee B	Rp. 18,000/h	Android Developer
3	Employee C	Rp. 18,000/h	Android Developer
4	Employee D	Rp. 20,500/h	Backend Developer
5	Employee E	Rp. 17,000/h	Backend Developer
6	Employee F	Rp. 17,000/h	DevOps Engineer
7	Employee G	Rp. 15,000/h	UI/UX Designer

, are outlined in the study for effective budget forecasting and resource allocation.

3.1.2. Estimated Project Completion Time

The project is divided into several main stages, and each stage is given time and cost estimates based on labor, software, and infrastructure requirements. The results showed that careful planning in the early stages of the project can reduce the risk of delays and cost overruns [12]. The following are data assumptions in the time estimation stage of project completion:

●

Number of tasks.

●

Average duration of task completion per team member.

●

Time already spent on specific tasks.

●

Time allocated at the beginning of the project.

The estimated project completion time, as outlined in

Table 3. Estimated project completion time.

Task Name	Employee	Deadline Start	Deadline End	Status
App UI/UX Design	Employee G	27 January 2025 00:00	26 February 2025 00:00	Already Working
Mentor Search Feature Development	Employee A	27 January 2025 11:16	26 February 2025 11:17	Already Working
Guidance Session Booking System Development	Employee B	27 January 2025 11:17	26 February 2025 11:17	Already Working
Backend and Infrastructure Setup	Employee D	27 January 2025 11:18	26 February 2025 11:18	Already Working
Development of Chat and Video Call Features	Employee C	27 January 2025 11:18	26 February 2025 11:18	Already Working
Integration of Review and Rating System	Employee E	27 January 2025 11:19	26 February 2025 11:19	Already Working
Application Testing—Mobile	Employee A	28 February 2025 11:19	28 March 2025 11:19	Not yet done
Application Testing—Backend	Employee B	27 February 2025 11:20	29 March 2025 11:20	Not yet done
Application Testing—Integration	Employee C	28 February 2025 11:20	30 March 025 11:20	Not yet done
Mobile Application Deployment	Employee A	28 February 2025 11:21	7 March 2025 11:21	Not yet done
Backend Application Deployment	Employee D	28 February 2025 11:22	24 March 2025 11:22	Not yet done
Backend Monitoring	Employee E	8 February 2025 11:22	28 February 2025 11:22	Not yet done
Mobile Application Monitoring	Employee B	8 February 2025 11:23	28 February 2025 11:23	Not yet done
Finalization and Launch Preparation	Employee G	27 February 2025 11:23	28 February 2025 11:23	Not yet done
CI/CD Setup	Employee F	27 January 2025 13:41	12 February 2025 13:41	Already Working
Monitoring & Logging	Employee F	13 February 2025 13:42	27 February 2025 13:42	Not yet done

, is based on these assumptions.

3.1.3. Team Performance Evaluation

Project team performance is not only influenced by the achievement of financial targets but also by operational efficiency, client satisfaction, and the capabilities and productivity of human resources in the team [13]. The following are the results of the team performance evaluation research stages:

●

Number of tasks completed by each team member.

●

Average task completion time per member.

●

Attendance rate or uptime (can be obtained from monitoring tools).

The team performance evaluation results, as shown in

Table 4. Team performance evaluation.

Name	Cost per Hour	Total Effective Hours	Total Ineffective Hours	Total Task Hours Exceed Deadline	Total Tasks Exceed Deadline	Total Tasks	Task Completed	Unfinished Tasks
Employee A	Rp. 21,000	589	90	0	0	3	1	2
Employee B	Rp. 18,000	513	70	0	0	3	1	2
Employee C	Rp. 18,000	699	76	52	1	2	1	1
Employee D	Rp. 20,500	699	76	52	1	2	1	1
Employee E	Rp. 17,000	635	92	4	1	2	1	1
Employee F	Rp. 17,000	732	43	385	1	2	1	1
Employee G	Rp. 15,000	611	92	0	0	2	1	1

, summarize these key metrics.

3.2. Project Monitoring Methods

The next stage is the stage of applying or calculating project assumption data using the method used for monitoring, as follows.

3.2.1. Yolo Method

The steps in project monitoring using the YOLO method are bounding box prediction, intersection over union, and loss function. The following are the steps in solving using the YOLO method:

●

Bounding box prediction

Each grid cell predicts a bounding box that includes the following:

$$B=\{x,y,w,h,C,P1,P2,\dots ,Pn\}$$

(1)

where

x, y: The center coordinates of the bounding box relative to the grid cell.

w, h: The width and height of the bounding box relative to the image size.

C: Confidence score representing the certainty that the box contains an object, calculates as:

$$C=P\left(object\right)\times IoUpred, truth$$

$$P1,P2,\dots ,Pn : Probabilities for each object class.$$

●

Intersection over union (IoU)

Measuring the quality of bounding box prediction with

$$IoU={\displaystyle \frac{Area of Overlap}{Area of Union}}$$

(2)

Area of Overlap: The area of overlap between the prediction box and the ground truth.

Area of Union: The combined area of the two boxes.

●

Loss Function

YOLO optimizes detection using the following loss function:

$$\mathcal{L}={\mathcal{L}}_{coord}+{\mathcal{L}}_{conf}+{\mathcal{L}}_{class}$$

(3)

Coordinate Loss:

$${\mathcal{L}}_{coord}={\lambda }_{coord}\sum _{i=0}^{S^2}\sum _{j=0}^B{1}_{ij}^{obj}\left[{\left(x_i-\widehat{x_i}\right)}^2+{\left(y_i-\widehat{y_i}\right)}^2+{\left(\sqrt{w_i}-\sqrt{\widehat{w_i}}\right)}^2+{\left(\sqrt{h_i}-\sqrt{\widehat{h_i}}\right)}^2\right]$$

(4)

Confidence Loss:

$${\mathcal{L}}_{conf}=\sum _{i=0}^{S^2}\sum _{j=0}^B\left[1_{ij}^{obj}{\left(C_i-\widehat{C_i}\right)}^2+{\lambda }_{noobj}{1}_{ij}^{noobj}{\left(C_i-\widehat{C_i}\right)}^2\right]$$

(5)

Class Probability Loss:

$${\mathcal{L}}_{class}=\sum _{i=0}^{S^2}\sum _{c\in classes}{\left(p_i\left(c\right)-{\widehat{p}}_i\left(c\right)\right)}^2$$

(6)

3.2.2. Reinforcement Learning (RL) Method

The steps in project monitoring using the Reinforcement Learning method, including Time Formula (days_simulated), Calculation of Steps for Time Calculation, Budget Formula, and Calculation for Each User are as follows:

●

Time Formula (days_simulated)

Time is calculated as the number of iterations required to reach the done state (done = True) in the RL environment. The done state occurs when the $completio{n}_{rate}$ (state) approaches or reaches 99%:

$$ne{w}_{completio{n}_{rate}}=curren{t}_{completio{n}_{rate}}+(action+1)\times 0.01$$

(7)

where

• action: A discrete value (0 to 9) chosen by the PPO model, representing a 1% to 10% increase in work effectiveness.
• days_simulated: Total iterations (days) required until

$$ne{w}_{completio{n}_{rate}}\ge 0.99$$

(8)

●

Calculation Steps for Time Calculation

Initial State Initialization:

$$curren{t}_{completio{n}_{rate}}=av{g}_{completio{n}_{rate}}={\displaystyle \frac{\sum \left(\frac{complete{d}_{tasks}}{tota{l}_{tasks}}\right)}{N}}$$

(9)

RL iteration

The state is updated using the following formula:

$$ne{w}_{completion\_rate} =curren{t}_{completio{n}_{rate}}+(action+1)\times 0.01$$

(10)

If $ne{w_{completion}}_{rate} \ge 0.99$, the simulation is complete.

Final Results

It takes 7 iterations (days) to achieve a ≥ 99% completion rate.

Summary Formula for time calculation

$$day{s}_{simulated}=i=1\sum k with condition ne{w}_{completio{n}_{rate}}\ge 0.99$$

(11)

where

• k: Number of iterations until $ne{w}_{completio{n}_{rate}} \ge 0.99$.
• $ne{w}_{completio{n}_{rate}}$is updated every iteration based on the action selected by the PPO model.

●

Budget Formula

Total Initial Cost Formula

$$estimate{d}_{cos{t}_i}=tota{l}_{effectivehour{s}_i}\times use{r}_{sp{h}_i}$$

(12)

$$pendin{g}_{cos{t}_i}=pendin{g}_{tas{ks}_i}\times \left({\displaystyle \frac{tota{l}_{effectivehour{s}_i}}{tota{l_{tasks}}_i}}\right)\times use{r}_{sp{h}_i}$$

(13)

$$tota{l}_{initialcost}=\sum _{i=1}^{N}estimate{d}_{cos{t}_i}\times pendin{g}_{cos{t}_i}$$

(14)

RL Additional Cost Formula

$$dail{y}_{cos{t}_i}=use{r}_{sp{h}_i}\times \left({\displaystyle \frac{tota{l}_{effectivehour{s}_i}}{tota{l_{tasks}}_i}}\right)$$

(15)

$$r{l_{additional}}_{cost}=\sum _{i=1}^{N}dail{y}_{cos{t}_i}\times day{s}_{simulated}$$

(16)

Final Total Cost Formula

$$tota{l}_{cos{t}_{rl}}=tota{l}_{initialcost}+r{l}_{additionalcost}$$

(17)

●

Calculation for Each User

Based on data from the report_users.csv file, calculations are made for each user. Here are the details of the data:

• days_simulated = 7 (from RL simulation)
• Column Values: $use{r}_{sph}, tota{l}_{effectivehours}, tota{l}_{tasks}, pendin{g}_{tasks}$.
• Calculation of Each User:

• Employee A

$$estimate{d}_{cost}=589\times \mathrm{21,000}=\mathrm{12,369,000}$$

$$pendin{g}_{cost}=2\times (589/3)\times \mathrm{21,000}=\mathrm{8,239,000}$$

$$dail{y}_{cost}=\mathrm{21,000}\times 589/3=\mathrm{4,121,000}$$

$$r{l}_{additionalcost}=\mathrm{4,121,000}\times 7=\mathrm{28,847,000}$$

$$Total User Cost=\mathrm{12,369,000}+\mathrm{8,239,000}+\mathrm{28,847,000}=\mathrm{49,455,000}$$

2.

Employee B

$$estimate{d}_{cost}=513\times \mathrm{18,000}=\mathrm{9,234,000}$$

$$pendin{g}_{cost}=2\times (513/3)\times \mathrm{18,000}=\mathrm{6,156,000}$$

$$dail{y}_{cost}=\mathrm{18,000}\times 513/3=\mathrm{3,078,000}$$

$$r{l}_{additionalcost}=\mathrm{3,078,000}\times 7=\mathrm{21,546,000}$$

$$Total User Cost=\mathrm{9,234,000}+\mathrm{6,156,000}+\mathrm{21,546,000}=\mathrm{36,936,000}$$

3.

Employee C

$$estimate{d}_{cost}=699\times \mathrm{18,000}=\mathrm{12,582,000}$$

$$pendin{g}_{cost}=1\times (699/3)\times \mathrm{18,000}=\mathrm{6,291,000}$$

$$dail{y}_{cost}=\mathrm{18,000}\times 699/3=\mathrm{6,291,000}$$

$$r{l}_{additionalcost}=\mathrm{6,291,000}\times 7=\mathrm{44,037,000}$$

$$Total User Cost=\mathrm{12,582,000}+\mathrm{6,291,000}+\mathrm{44,037,000}=\mathrm{62,910,000}$$

4.

Employee D

$$estimate{d}_{cost}=699\times \mathrm{20,500}=\mathrm{14,329,500}$$

$$pendin{g}_{cost}=1\times (699/2)\times \mathrm{20,500}=\mathrm{7,164,750}$$

$$dail{y}_{cost}=\mathrm{20,500}\times 699/2=\mathrm{7,164,750}$$

$$r{l}_{additionalcost}=\mathrm{7,164,750}\times 7=\mathrm{50,153,250}$$

$$Total User Cost=\mathrm{14,329,500}+\mathrm{7,164,750}+\mathrm{50,153,250}=\mathrm{71,647,500}$$

5.

Employee E

$$estimate{d}_{cost}=635\times \mathrm{17,000}=\mathrm{10,795,000}$$

$$pendin{g}_{cost}=1\times (635/2)\times \mathrm{17,000}=\mathrm{5,397,500}$$

$$dail{y}_{cost}=\mathrm{17,000}\times 635/2=\mathrm{5,397,500}$$

$$r{l}_{additionalcost}=\mathrm{5,397,500}\times 7=\mathrm{37,782,500}$$

$$Total User Cost=\mathrm{10,795,000}+\mathrm{5,397,500}+\mathrm{37,782,500}=\mathrm{53,975,000}$$

6.

Employee F

$$estimate{d}_{cost}=732\times \mathrm{17,000}=\mathrm{12,444,000}$$

$$pendin{g}_{cost}=1\times (732/2)\times \mathrm{17,000}=\mathrm{6,222,000}$$

$$dail{y}_{cost}=\mathrm{17,000}\times 732/2=\mathrm{6,222,000}$$

$$r{l}_{additionalcost}=\mathrm{6,222,000}\times 7=\mathrm{43,554,000}$$

$$Total User Cost=\mathrm{12,444,000}+\mathrm{6,222,000}+\mathrm{43,554,000}=\mathrm{62,220,000}$$

7.

Employee G

$$estimate{d}_{cost}=611\times \mathrm{15,000}=\mathrm{9,165,000}$$

$$pendin{g}_{cost}=1\times (611/2)\times \mathrm{15,000}=\mathrm{4,582,500}$$

$$dail{y}_{cost}=\mathrm{15,000}\times 2611=\mathrm{4,582,500}$$

$$r{l}_{additionalcost}=\mathrm{4,582,500}\times 7=\mathrm{32,077,500}$$

$$Total User Cost=\mathrm{9,165,000}+\mathrm{4,582,500}+\mathrm{32,077,500}=\mathrm{45,825,000}$$

3.3. Project Conclusion

The conclusion of the results of this project with a total cost of Rp. 338,929,500 with an estimated workmanship of 7 days and 7 employees involved where the initial budget was Rp. 150,000,000, -, so there is an excess cost of Rp. 188,929,500.

3.4. System Implementation

In the Implementation of YOLO technology and Reinforcement Learning for web-based project monitoring, a web-based system has been successfully developed. The following are the results of the implementation:

3.4.1. Database Design

At the system implementation stage, a database design is needed for the data modeling process that can represent business or application needs in the form of an organized data structure. The following is the database design in the monitoring system, as shown in Figure 2.

3.4.2. Menu Display

Furthermore, this stage will display the results of making the system, namely the menu display. A well-designed menu display will improve user experience (UX) and make the application or system easier to use. The following are some of the menu views created, as shown in Figure 3:

4. Conclusions

This research shows that the YOLO and Reinforcement Learning methods are effective for improving project monitoring and budget optimization. With this approach, the project can be completed in a shorter time with more accurate cost estimation. Cost calculations based on team members’ working hours, additional costs due to delays, and cost calculations using RL simulation resulted in a total project cost of Rp 338,929,500 with a total over budget of Rp 188,929,500, which consumed a total of seven project days by achieving a completion rate of ≥99%. With the application of RL-based optimization, additional costs can be minimized and project efficiency increased with the reported reduction in resources of the four-person team with poor performance.