A Proposed eFSR Blockchain System for Optimal Planning of Facility Services with Probabilistic Arrivals and Stochastic Service Durations
Abstract
:1. Introduction
2. Electronic Facility Services Record
2.1. Scheduling Optimization Model
- (a)
- Objective functions
- (i)
- Minimizing idle time and overtime costs
- (ii)
- Maximizing number of completed tasks for all buildings
- The order time of each service j, sotj, is treated as a probabilistic parameter with discrete possible outcomes associated with different probabilities. Based on technical knowledge, the possible outcome for the ordering times xz (xz = x1, …, XZ) is associated with a probability, pz (pz = p1, …, PZ) as given in constraints (5) and (6). Inequality (7) states that sotj cannot be a negative value.
- Task k from order j is only assigned to technician c during period i at or after sotj as stated in Equations (8) and (9).
- Practically, the task execution durations are stochastic parameters modeled by continuous normal distributions. Let sdtk denote the standard duration required to complete task k. The sdtk is generated from a normal distribution which is characterized separately for each type e with mean µe and standard deviation σe as expressed in Equation (10). Further, the sdtk shall be a non-negative value as stated in Inequality (11).
- Let adtk denote the actual duration required to execute task k. The adtk depends on technician effectiveness, βc, which is different from one technician to another. Hence, the actual time, adtk, should be equal to sdtk when βc is 100%; however, when βc is less than 100%, adtk will be longer than sdtk. Mathematically, this is presented in Equation (12).
- Let Tadtci denote the total actual task durations executed by technician c in interval i. Then, Tadtci is calculated as presented in Equation (13).
- Let dlci denote the idle time incurred by technician c in interval i. In addition, let avci be a binary variable that indicates the availability of technician c in interval i, where the value of one means that technician c is available in interval i and zero means otherwise. Then, the dlci is calculated by subtracting tadtci from the threshold hour of idle time, h, if the technician was available in that interval, avci, as presented in Equation (14).
- The dlci should be greater than or equal to zero and less than or equal to the maximum allowable idle time, mdl, as stated in Inequality (15).
- The total idle time in hours, Tdtl, incurred by all technicians in all intervals is computed as presented in Equation (16).
- Let ovtci denote the overtime incurred by technician c in interval i. Then, the ovtci is calculated when the technician is available in this interval, avci, as shown in Equation (17).
- The ovtci should be greater than or equal to zero and less than or equal to the maximum allowable overtime, mov, as stated in Inequality (18).
- The total overtime in hours, Tovt, incurred by all technicians in all intervals is computed as given in Equation (19).
- The skills required to complete task k should be respected. Thus, task k which requires skills should be assigned to technician c who has at least all the required skills to complete the task. Let ωcs be a binary parameter that determines whether technician c owns skill s, where the value of one indicates that technician c has skill s and zero indicates otherwise. Additionally, let δks be a binary parameter that determines whether task k requires skill s, where a value of one indicates it requires such and zero indicates otherwise. This constraint is mathematically stated in Equation (20).
- Service task k should be assigned only once to technician c in interval i. This is mathematically stated in Equation (21).
- Let χ(ek), (e′k′) be a binary variable which determines whether task k of type e depends on task k′ of type e′, where χ(ek), (e′k′) equals one when the task k depends on task k′ and zero otherwise. Let χ(e′k′), (ek) be a binary variable which determines whether task k′ of type e′ depends on task k of type e, where χ(e′k′), (ek) equals one when the task k′ of type e′ depends on task k of type e and zero otherwise. Assume that there are two tasks k and k′ of types e and e′, respectively. Let task k′ depends on task k. Then, task k should be assigned first; i.e., χ(e′k′), (ek) = 1. In addition, if the task k has not been assigned, then task k′ cannot be assigned as stated in Equation (22). When the execution of task k is scheduled after task k′ (χ(ek), (e′k′) = 1) but task k′ has not been performed yet, then task k cannot be assigned as stated in Equation (23). If task k depends on task k′ (χ(ek), (e′k′) = 1) and task k′ has been assigned, then task k might be assigned to be executed as presented in Equation (24). Similarly, if task k′ depends on task k (χ(e′k′), (ek)= 1) and task k has been assigned to be executed, then task k′ might be assigned to be executed as expressed in Equation (25).
- The variable Zjkeci is binary variable, as stated in Equation (26).
2.2. Sequencing Optimization Model
- Objective functions
- Minimizing delay costs to ensure that technicians respond quickly to service calls. Assume that a delay in task completion incurs delay costs. Let Tdt denote the total delay time in hours by all technicians in all intervals. In addition, let cdt denote the cost per delay hour. Then, total cost of delay time, TCdt, is mathematically expressed in Equation (27).
- Minimizing the sum of the start times for the assigned tasks to ensure quick response to all services. Let stjkeci denote the sequencing start time for task k of service j of type e as assigned to technician c in interval i. The start times of service tasks should be sequenced at the earliest possible times to guarantee lower incurred costs. Consequently, the second objective function for sequencing service tasks is formulated to ensure fast response times by minimizing the sequencing start times, as presented in Equation (29).
- 2.
- Constraints of sequencing model
- (1)
- The execution of any service task k of service j from type e by technician c in interval i should start after the order time of service j, sotj, as expressed in Equation (30).
- (2)
- Let ftjkeci denote the sequencing finish time for task k of type e in service j that is assigned to technician c in interval i. Then, ftjkeci is computed by adding the actual duration required to execute task k, adtk, to the sequencing start time, stjkeci, as calculated in Equation (31).
- (3)
- Let ftbj denote the finish time of service j. Therefore, ftbj should equal the finish time of the latest executed task k from service j of type e by technician c in interval i ftjkeci, as stated in Equation (32).
- (4)
- Let dutj denote the due date for completing service j. The delay time is incurred when the execution of any service extends after its due date, dutj. Then, the total delay time, Tdt, can be calculated—see Inequality (33)—as the difference between the service finish time, ftbj, and its due date, dutj. Moreover, the difference should be greater than or equal to zero as stated in Equation (34).
- (5)
- Technician c cannot perform more than one task at the same time. For example, suppose that technician c was assigned to complete task k of service j and task k’ of service j’ in the same interval i. Then, the sequencing start times for tasks k and k’ should not be set at the same time as expressed in Inequalities (35) and (36). Let service j’ belong to the set of J services (j’ ∈ J); task k’ belongs to the set of K tasks (k’ ∈ K); type e’ belongs to the set of E types (e’ ∈ E). In addition, let M denote a very large number.
- (6)
- When performing the tasks of service j, the tasks are prioritized such that the task with the smallest label number should be executed first unless that task depends on another task (χ(ek), (e’k’) = 0). For example, suppose that a specific service j has three tasks (k = 1, 2, 3). Then, the sequencing start time for task 1 should begin before tasks 2 and 3. Similarly, task 2 should be executed before task 3, as presented in Equation (37). Let technician c’ belong to the set of C technicians (c’ ∈ C). Mathematically,
- (7)
- The dependency between the scheduled tasks should be respected during the sequencing process. For example, suppose that there are two tasks (task k’ of type e’ and task k of type e) related to the same service j such that task k’ depends on task k (χ(e’k’), (ek) = 1). Additionally, suppose that the executions of tasks k and k’ have been assigned to be completed by the two technicians c and c’ in interval i (Zjkeci = Zjk’e’c’i = 1), respectively. Then, the start time of task k’ should begin after the finish time of task k as stated in Equation (38).
2.3. Block Data Storage and Sharing
2.4. Performance Monitoring and Assessment
3. Application and Research Results
4. Research Results
5. Conclusions
Author Contributions
Funding
Institutional Review Board Statement
Informed Consent Statement
Data Availability Statement
Conflicts of Interest
References
- Nazali Mohd Noor, M.; Pitt, M. A critical review on innovation in facilities management service delivery. Facilities 2009, 27, 211–228. [Google Scholar] [CrossRef]
- Durdyev, S.; Ashour, M.; Connelly, S.; Mahdiyar, A. Barriers to the implementation of Building Information Modelling (BIM) for facility management. J. Build. Eng. 2022, 46, 103736. [Google Scholar] [CrossRef]
- Mustaffa, S.A.H.; Adnan, H.; Jusoff, K. Facilities management challenges and opportunity in the Malaysian property sector. J. Sustain. Dev. 2008, 1, 79–85. [Google Scholar]
- Opoku, A.; Lee, J.Y. The Future of Facilities Management: Managing Facilities for Sustainable Development. Sustainability 2022, 14, 1705. [Google Scholar] [CrossRef]
- Jain, A.; Soojin Yoon, F.; Kang, K.; Hastak, M. Implementation of the Data-Driven Analytics Protocol through Facility Management and Real Estate Industry Cases. J. Manag. Eng. 2022, 38, 04021077. [Google Scholar] [CrossRef]
- Gunasekara, H.G.; Sridarran, P.; Rajaratnam, D. Effective use of blockchain technology for facilities management procurement process. J. Facil. Manag. 2022, 20, 452–468. [Google Scholar] [CrossRef]
- Hijazi, A.A.; Perera, S.; Alashwal, A.; Calheiros, R.N. Blockchain adoption in construction supply chain: A review of studies across multiple sectors. In Proceedings of the International Council for Research and Innovation in Building and Construction (CIB) World Building Congress, Hongkong, China, 17–21 June 2019. [Google Scholar]
- Zhao, G.; Liu, S.; Lopez, C.; Lu, H.; Elgueta, S.; Chen, H.; Boshkoska, B.M. Blockchain technology in agri-food value chain management: A synthesis of applications, challenges, and future research directions. Comput. Ind. 2019, 109, 83–99. [Google Scholar] [CrossRef]
- Tanwar, S.; Parekh, K.; Evans, R. Blockchain-based electronic healthcare record system for healthcare 4.0 applications. J. Inf. Secur. Appl. 2020, 50, 102407. [Google Scholar] [CrossRef]
- Olawumi, T.O.; Chan, D.W.; Ojo, S.; Yam, M.C. Automating the modular construction process: A review of digital technologies and future directions with blockchain technology. J. Build. Eng. 2021, 46, 103720. [Google Scholar] [CrossRef]
- Lemieux, V.L. Trusting records: Is Blockchain technology the answer? Rec. Manag. J. 2016, 26, 110–139. [Google Scholar] [CrossRef]
- Banerjee, A. Blockchain Technology: Supply Chain Insights from ERP. Adv. Comput. 2018, 111, 69–98. [Google Scholar] [CrossRef]
- Ying, W.; Jia, S.; Du, W. Digital enablement of blockchain: Evidence from HNA group. Int. J. Inf. Manag. 2018, 39, 1–4. [Google Scholar] [CrossRef]
- Jeet, R.; Singh Kang, S. Investigating the progress of human e-healthcare systems with understanding the necessity of using emerging blockchain technology. Mater. Today Proc. 2020. [Google Scholar] [CrossRef]
- Ismail, L.; Materwala, H.; Zeadally, S. Lightweight Blockchain for Healthcare. IEEE Access 2019, 7, 149935–149951. [Google Scholar] [CrossRef]
- Zhu, Q.; Bai, C.; Sarkis, J. Blockchain technology and supply chains: The paradox of the atheoretical research discourse. Transp. Res. Part E Logist. Transp. Rev. 2022, 164, 102824. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Al-Hawadi, A.; Lepkova, N. Blockchain Design with Optimal Maintenance Planning. Buildings 2022, 12, 1902. [Google Scholar] [CrossRef]
- Sahney, R.; Sharma, M. Electronic health records: A general overview. Curr. Med. Res. Pract. 2018, 8, 67–70. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Al-Shalaldeh, H.; Lepkova, N. Proposed procedure for optimal maintenance scheduling under emergent failures. J. Civ. Eng. Manag. 2020, 26, 396–409. [Google Scholar] [CrossRef] [Green Version]
- Al-Refaie, A.; Qapaja, A.; Al-Hawadi, A. Optimal Fuzzy Scheduling and Sequencing of Work-Intensive Multiple Projects Under Normal and Unexpected Events. Int. J. Inf. Technol. Proj. Manag. 2021, 12, 64–89. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Al-Hawadi, A.; Fraij, S. Optimization models for clustering of solid waste collection process. Eng. Optim. 2020, 53, 2056–2069. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Almowas, H. Multi-objective maintenance planning under preventive maintenance. J. Qual. Maint. Eng. 2021. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Abedalqader, H. Optimal berth scheduling and sequencing under unexpected events. J. Oper. Res. Soc. 2022, 73, 430–444. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Judeh, M.; Chen, T. Optimal multiple-period scheduling and sequencing of operating room and intensive care unit. Oper. Res. 2018, 18, 645–670. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Chen, T.; Judeh, M. Optimal operating room scheduling for normal and unexpected events in a smart hospital. Oper. Res. 2018, 18, 579–602. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Lepkova, N.; Camlibel, M.E. The Relationships between the Pillars of TPM and TQM and Manufacturing Performance Using Structural Equation Modeling. Sustainability 2022, 14, 1497. [Google Scholar] [CrossRef]
- Al-Refaie, A.; Al-Hawadi, A. Optimal fuzzy repairs’ scheduling and sequencing of failure types over multiple periods. J. Ambient Intell. Humaniz. Comput. 2022, 13, 201–217. [Google Scholar] [CrossRef]
- Carrizo Moreira, A.; Campos Silva Pais, G. Single Minute Exchange of Die: A Case Study Implementation. J. Technol. Manag. Innov. 2011, 6, 129–146. [Google Scholar] [CrossRef]
Parameter | Value | Parameter | Value |
---|---|---|---|
Number of service orders | 47 | Number of technicians | 4 |
Number of tasks | 140 | Number of technician skills | 6 |
Number of task types | 7 | Number of studied intervals (days) | 12 |
Maximum allowable idle time (h) | 3 | Unit cost per idle hour | $45/h |
Maximum allowable overtime (h) | 4 | Unit cost per over hour | $60/h |
Full-time working hours (h) | 9 | Unit cost per delay day | $225/day |
Threshold hour of idle time (h) | 8 | - |
Description | Value | ||||||
---|---|---|---|---|---|---|---|
Order time (day) | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
Probability | 9% | 23% | 21% | 15% | 16% | 7% | 9% |
Number of ordered services | 6 | 8 | 8 | 7 | 7 | 5 | 6 |
Facility j | K | sotj | dutj | Facility j | K | sotj | dutj | Facility j | K | sotj | dutj |
---|---|---|---|---|---|---|---|---|---|---|---|
1 | 2 | 1 | 5 | 17 | 3 | 1 | 1 | 33 | 2 | 5 | 11 |
2 | 3 | 3 | 4 | 18 | 4 | 6 | 10 | 34 | 2 | 4 | 10 |
3 | 4 | 5 | 8 | 19 | 3 | 2 | 11 | 35 | 3 | 6 | 11 |
4 | 4 | 6 | 9 | 20 | 2 | 4 | 12 | 36 | 3 | 2 | 4 |
5 | 3 | 5 | 7 | 21 | 2 | 6 | 12 | 37 | 3 | 7 | 12 |
6 | 2 | 3 | 12 | 22 | 4 | 1 | 1 | 38 | 4 | 1 | 8 |
7 | 2 | 5 | 8 | 23 | 2 | 2 | 2 | 39 | 3 | 2 | 9 |
8 | 5 | 7 | 12 | 24 | 2 | 3 | 10 | 40 | 2 | 4 | 6 |
9 | 6 | 1 | 4 | 25 | 3 | 2 | 3 | 41 | 2 | 4 | 7 |
10 | 1 | 3 | 6 | 26 | 3 | 4 | 12 | 42 | 4 | 7 | 9 |
11 | 3 | 5 | 11 | 27 | 3 | 6 | 12 | 43 | 2 | 7 | 10 |
12 | 4 | 7 | 12 | 28 | 4 | 4 | 6 | 44 | 2 | 5 | 9 |
13 | 2 | 3 | 12 | 29 | 3 | 3 | 6 | 45 | 3 | 7 | 12 |
14 | 5 | 1 | 5 | 30 | 2 | 2 | 8 | 46 | 3 | 2 | 11 |
15 | 6 | 3 | 8 | 31 | 2 | 4 | 10 | 47 | 3 | 5 | 12 |
16 | 1 | 3 | 9 | 32 | 4 | 2 | 9 |
Type, e | Description | Mean, µe | Standard Deviation, σe | Number of Tasks, K |
---|---|---|---|---|
1 | Maintenance of oil and fat traps | 2 | 0.14 | 20 |
2 | Maintenance of lifts | 2.75 | 0.17 | 19 |
3 | Cleaning of premises | 4.1 | 0.3 | 22 |
4 | Waste disposal | 3.55 | 0.1 | 22 |
5 | Woodwork | 1.65 | 0.12 | 19 |
6 | Electrical work | 2.01 | 0.1 | 18 |
7 | Minor repairs | 3.75 | 0.2 | 20 |
Facility j | k | e | sdtk | Facility j | k | e | sdtk | Facility j | k | e | sdtk |
---|---|---|---|---|---|---|---|---|---|---|---|
1 | 1 | 2 | 2.44 | 15 | 48 | 1 | 1.80 | 31 | 95 | 5 | 1.44 |
2 | 1 | 2.11 | 49 | 5 | 1.74 | 32 | 96 | 6 | 1.79 | ||
2 | 3 | 2 | 2.30 | 50 | 6 | 1.94 | 97 | 3 | 3.41 | ||
4 | 3 | 3.44 | 51 | 3 | 4.39 | 98 | 3 | 3.91 | |||
5 | 2 | 2.23 | 52 | 3 | 3.66 | 99 | 7 | 3.46 | |||
3 | 6 | 2 | 2.44 | 16 | 53 | 2 | 2.63 | 33 | 100 | 1 | 1.87 |
7 | 3 | 3.56 | 17 | 54 | 6 | 1.84 | 101 | 5 | 1.35 | ||
8 | 6 | 1.73 | 55 | 2 | 2.56 | 34 | 102 | 5 | 1.43 | ||
9 | 3 | 3.75 | 56 | 2 | 2.38 | 103 | 3 | 3.75 | |||
4 | 10 | 4 | 3.04 | 18 | 57 | 1 | 1.79 | 35 | 104 | 2 | 2.44 |
11 | 4 | 3.34 | 58 | 5 | 1.66 | 105 | 4 | 3.13 | |||
12 | 6 | 1.77 | 59 | 6 | 1.87 | 106 | 1 | 1.87 | |||
13 | 7 | 3.23 | 60 | 3 | 4.01 | 36 | 107 | 1 | 1.55 | ||
5 | 14 | 4 | 3.24 | 19 | 61 | 3 | 3.63 | 108 | 4 | 3.27 | |
15 | 7 | 3.38 | 62 | 2 | 2.39 | 109 | 4 | 3.25 | |||
16 | 2 | 2.37 | 63 | 6 | 1.94 | 37 | 110 | 5 | 1.46 | ||
6 | 17 | 5 | 1.54 | 20 | 64 | 1 | 1.76 | 111 | 7 | 3.44 | |
18 | 6 | 1.66 | 65 | 2 | 2.57 | 112 | 4 | 3.35 | |||
7 | 19 | 3 | 3.66 | 21 | 66 | 6 | 1.95 | 38 | 113 | 7 | 3.64 |
20 | 4 | 3.22 | 67 | 4 | 3.24 | 114 | 2 | 2.73 | |||
8 | 21 | 2 | 2.36 | 22 | 68 | 5 | 1.42 | 115 | 5 | 1.49 | |
22 | 4 | 3.27 | 69 | 7 | 3.30 | 116 | 6 | 1.75 | |||
23 | 4 | 3.07 | 70 | 6 | 1.82 | 39 | 117 | 3 | 4.01 | ||
24 | 7 | 3.38 | 71 | 7 | 3.19 | 118 | 3 | 4.04 | |||
25 | 7 | 3.11 | 23 | 72 | 1 | 1.99 | 119 | 6 | 1.87 | ||
9 | 26 | 1 | 1.98 | 73 | 5 | 1.58 | 40 | 120 | 3 | 3.91 | |
27 | 4 | 3.05 | 24 | 74 | 6 | 1.95 | 121 | 3 | 3.06 | ||
28 | 5 | 1.59 | 75 | 5 | 1.52 | 41 | 122 | 3 | 3.48 | ||
29 | 7 | 3.32 | 25 | 76 | 3 | 3.42 | 123 | 2 | 2.33 | ||
30 | 4 | 3.40 | 77 | 7 | 3.44 | 42 | 124 | 6 | 1.81 | ||
31 | 7 | 3.79 | 78 | 1 | 1.93 | 125 | 1 | 1.82 | |||
10 | 32 | 1 | 1.83 | 26 | 79 | 5 | 1.50 | 126 | 1 | 1.94 | |
11 | 33 | 5 | 1.42 | 80 | 6 | 1.89 | 127 | 6 | 1.96 | ||
34 | 6 | 1.82 | 81 | 3 | 3.18 | 43 | 128 | 4 | 3.18 | ||
35 | 3 | 3.68 | 27 | 82 | 2 | 2.77 | 129 | 5 | 1.54 | ||
12 | 36 | 3 | 3.28 | 83 | 2 | 2.63 | 44 | 130 | 7 | 3.48 | |
37 | 2 | 2.22 | 84 | 2 | 2.56 | 131 | 4 | 3.14 | |||
38 | 4 | 3.09 | 28 | 85 | 4 | 3.23 | 45 | 132 | 7 | 3.35 | |
39 | 1 | 1.85 | 86 | 2 | 2.33 | 133 | 1 | 1.95 | |||
13 | 40 | 1 | 1.72 | 87 | 1 | 1.85 | 134 | 5 | 1.36 | ||
41 | 7 | 3.60 | 88 | 4 | 3.24 | 46 | 135 | 6 | 1.96 | ||
14 | 42 | 1 | 1.79 | 29 | 89 | 4 | 3.15 | 136 | 3 | 3.62 | |
43 | 4 | 3.26 | 90 | 5 | 1.51 | 137 | 3 | 3.92 | |||
44 | 5 | 1.63 | 91 | 7 | 3.32 | 47 | 138 | 7 | 3.39 | ||
45 | 7 | 3.61 | 30 | 92 | 4 | 3.47 | 139 | 1 | 1.94 | ||
46 | 4 | 3.36 | 93 | 7 | 3.64 | 140 | 5 | 1.58 | |||
15 | 47 | 7 | 3.34 | 31 | 94 | 1 | 1.85 | - |
Technician c | Effectiveness βc | Skills Matrix ωcs | Availability avci | |||||
---|---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |||
1 | 88% | 1 | 1 | 0 | 1 | 0 | 1 | 1 |
2 | 93% | 0 | 0 | 1 | 1 | 1 | 0 | 1 |
3 | 90% | 1 | 0 | 1 | 0 | 1 | 0 | 1 |
4 | 92% | 0 | 1 | 0 | 1 | 0 | 1 | 1 |
Technician, c | Days | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | |
1 | 10.48 | 10.29 | 6.31 | 8.92 | 7.51 | 11.68 | 8.42 | 8.88 | 7.45 | 8.88 | 8.47 | 7.62 |
2 | 8.54 | 7.71 | 7.46 | 11.08 | 7.38 | 8.66 | 8.94 | 7.29 | 7.33 | 7.41 | 8.93 | 7.60 |
3 | 8.36 | 7.77 | 7.96 | 8.80 | 8.25 | 8.85 | 9.81 | 7.44 | 8.02 | 7.75 | 7.83 | 7.54 |
4 | 8.76 | 9.00 | 7.49 | 8.95 | 8.64 | 9.00 | 8.53 | 7.70 | 8.87 | 7.89 | 8.20 | 8.99 |
c | Day 1 | Day 2 | Day 3 |
1 | 6, 9, 10 | 1, 7, 27 | 5, 29 |
2 | 26, 30, 55 | 28, 31, 42 | 43, 49, 63 |
3 | 54, 56, 69 | 72, 73, 76 | 77, 78, 96 |
4 | 44, 68, 70, 71 | 99, 107, 108 | 109, 113 |
c | Day 4 | Day 5 | Day 6 |
1 | 2, 3, 4 | 14, 17, 32 | 13,15, 19 |
2 | 45, 46, 11 | 40, 47, 48 | 51, 52 |
3 | 79, 81, 85 | 86, 87, 88 | 89, 90, 91 |
4 | 114, 115, 117 | 118, 120 | 116, 121, 122 |
c | Day 7 | Day 8 | Day 9 |
1 | 16, 20, 34 | 12, 21, 35 | 22, 36 |
2 | 50, 53, 57, 74 | 60, 82 | 58, 61, 75 |
3 | 8, 92, 93 | 94, 97, 102 | 95, 98, 100 |
4 | 119, 123, 124, 125 | 126, 127, 128 | 129, 130, 131 |
c | Day 10 | Day 11 | Day 12 |
1 | 18, 23, 38 | 24, 37, 39 | 25, 41 |
2 | 59, 62, 83 | 33, 64, 65, 84 | 66, 67, 80 |
3 | 101, 103, 106 | 104, 105, 110 | 111, 112 |
4 | 132, 133, 135 | 136, 137 | 134, 138, 139, 140 |
Day | Technicians | Total | |||
---|---|---|---|---|---|
1 | 2 | 3 | 4 | ||
1 | 3 | 3 | 3 | 4 | 13 |
2 | 3 | 3 | 3 | 3 | 12 |
3 | 2 | 3 | 3 | 2 | 10 |
4 | 3 | 3 | 3 | 3 | 12 |
5 | 3 | 3 | 3 | 2 | 11 |
6 | 3 | 2 | 3 | 3 | 11 |
Technician | Task | stk | ftk | Technician | Task | stk | ftk |
---|---|---|---|---|---|---|---|
Day 1 | Day 2 | ||||||
1 | 6 | 0 | 2.77 | 1 | 1 | 0 | 2.78 |
1 | 9 | 2.77 | 7.03 | 1 | 7 | 2.78 | 6.82 |
1 | 10 | 7.03 | 10.48 | 1 | 27 | 6.82 | 10.29 |
2 | 26 | 0 | 2.13 | 2 | 28 | 0 | 1.71 |
2 | 30 | 2.13 | 5.79 | 2 | 31 | 1.71 | 5.79 |
2 | 55 | 5.79 | 8.54 | 2 | 42 | 5.79 | 7.71 |
3 | 54 | 0 | 2.05 | 3 | 72 | 0 | 2.21 |
3 | 56 | 2.75 | 5.39 | 3 | 73 | 2.21 | 3.97 |
3 | 69 | 5.39 | 9.06 | 3 | 76 | 3.97 | 7.77 |
4 | 70 | 0 | 1.98 | 4 | 99 | 0 | 3.76 |
4 | 71 | 1.98 | 5.45 | 4 | 107 | 3.76 | 5.44 |
4 | 44 | 5.45 | 7.22 | 4 | 108 | 5.44 | 9 |
4 | 68 | 7.22 | 8.76 | - | |||
Day 3 | Day 4 | ||||||
1 | 29 | 0 | 3.77 | 1 | 2 | 0 | 2.39 |
1 | 5 | 3.77 | 6.31 | 1 | 3 | 2.39 | 5.01 |
2 | 43 | 0 | 3.51 | 1 | 4 | 5.01 | 11.54 |
2 | 63 | 3.51 | 5.59 | 2 | 45 | 0 | 3.88 |
2 | 49 | 5.59 | 7.46 | 2 | 46 | 3.88 | 7.49 |
3 | 77 | 0 | 3.83 | 2 | 11 | 7.49 | 11.08 |
3 | 78 | 3.83 | 5.97 | 3 | 79 | 0 | 1.67 |
3 | 96 | 5.97 | 7.96 | 3 | 81 | 1.67 | 5.21 |
4 | 113 | 0 | 3.96 | 3 | 85 | 5.21 | 8.8 |
4 | 109 | 3.96 | 7.49 | 4 | 114 | 0 | 2.97 |
- | 4 | 115 | 2.97 | 4.59 | |||
4 | 117 | 4.59 | 8.95 | ||||
Day 5 | Day 6 | ||||||
1 | 32 | 0 | 2.07 | 1 | 13 | 0 | 3.67 |
1 | 17 | 2.07 | 3.82 | 1 | 15 | 3.67 | 7.52 |
1 | 14 | 3.82 | 7.51 | 1 | 19 | 7.52 | 11.68 |
2 | 40 | 0 | 1.85 | 2 | 51 | 0 | 4.72 |
2 | 47 | 1.85 | 5.44 | 2 | 52 | 4.72 | 8.66 |
2 | 48 | 5.44 | 7.38 | 3 | 89 | 0 | 3.5 |
3 | 86 | 0 | 2.59 | 3 | 90 | 3.5 | 5.17 |
3 | 87 | 2.59 | 4.65 | 3 | 91 | 5.17 | 8.85 |
3 | 88 | 4.65 | 8.25 | 4 | 116 | 0 | 1.9 |
4 | 118 | 0 | 4.39 | 4 | 121 | 1.9 | 5.22 |
4 | 120 | 4.39 | 8.64 | 4 | 122 | 5.22 | 9 |
Day | Technicians | Total | |||
---|---|---|---|---|---|
1 | 2 | 3 | 4 | ||
7 | 3 | 4 | 3 | 4 | 14 |
8 | 3 | 2 | 3 | 3 | 11 |
9 | 2 | 3 | 3 | 3 | 11 |
10 | 3 | 3 | 3 | 3 | 12 |
11 | 3 | 4 | 3 | 2 | 12 |
12 | 2 | 3 | 2 | 4 | 11 |
Technician | Task | sti | fti | Technician | Task | sti | fti |
---|---|---|---|---|---|---|---|
Day 7 | Day 8 | ||||||
1 | 16 | 0 | 2.7 | 1 | 12 | 0 | 2.01 |
1 | 20 | 2.7 | 6.35 | 1 | 35 | 2.01 | 6.19 |
1 | 34 | 6.35 | 8.42 | 1 | 21 | 6.19 | 8.88 |
2 | 74 | 0 | 2.1 | 2 | 60 | 0 | 4.31 |
2 | 50 | 2.1 | 4.19 | 2 | 82 | 4.31 | 7.29 |
2 | 53 | 4.19 | 7.02 | 3 | 97 | 0 | 3.79 |
2 | 57 | 7.02 | 8.94 | 3 | 94 | 3.79 | 5.85 |
3 | 8 | 0 | 1.92 | 3 | 102 | 5.85 | 7.44 |
3 | 92 | 1.92 | 5.77 | 4 | 126 | 0 | 2.11 |
3 | 93 | 5.77 | 9.81 | 4 | 127 | 2.11 | 4.24 |
4 | 119 | 0 | 2.04 | 4 | 128 | 4.24 | 7.7 |
4 | 123 | 2.04 | 4.58 | - | |||
4 | 124 | 4.58 | 6.55 | ||||
4 | 125 | 6.55 | 8.53 | ||||
Day 9 | Day 10 | ||||||
1 | 22 | 0 | 3.72 | 1 | 18 | 0 | 1.89 |
1 | 36 | 3.72 | 7.45 | 1 | 38 | 1.89 | 5.4 |
2 | 61 | 0 | 3.9 | 1 | 23 | 5.4 | 8.88 |
2 | 75 | 3.9 | 5.54 | 2 | 62 | 0 | 2.57 |
2 | 58 | 5.54 | 7.33 | 2 | 59 | 2.57 | 4.58 |
3 | 98 | 0 | 4.35 | 2 | 83 | 4.58 | 7.41 |
3 | 95 | 4.35 | 5.95 | 3 | 103 | 0 | 4.17 |
3 | 100 | 5.95 | 8.02 | 3 | 101 | 4.17 | 5.67 |
4 | 130 | 0 | 3.78 | 3 | 106 | 5.67 | 7.75 |
4 | 131 | 3.78 | 7.19 | 4 | 135 | 0 | 2.13 |
4 | 129 | 7.19 | 8.87 | 4 | 132 | 2.13 | 5.77 |
- | 4 | 133 | 5.77 | 7.89 | |||
Day 11 | Day 12 | ||||||
1 | 37 | 0 | 2.52 | 1 | 41 | 0 | 4.09 |
1 | 39 | 2.52 | 4.63 | 1 | 25 | 4.09 | 7.62 |
1 | 24 | 4.63 | 8.47 | 2 | 80 | 0 | 2.03 |
2 | 64 | 0 | 1.89 | 2 | 66 | 2.03 | 4.12 |
2 | 65 | 1.89 | 4.65 | 2 | 67 | 4.12 | 7.6 |
2 | 84 | 4.65 | 7.41 | 3 | 111 | 0 | 3.82 |
2 | 33 | 7.41 | 8.93 | 3 | 112 | 3.82 | 7.54 |
3 | 104 | 0 | 2.72 | 4 | 138 | 0 | 3.69 |
3 | 105 | 2.72 | 6.2 | 4 | 139 | 3.69 | 5.79 |
3 | 110 | 6.2 | 7.83 | 4 | 140 | 5.79 | 7.51 |
4 | 136 | 0 | 3.94 | 4 | 134 | 7.51 | 8.99 |
4 | 137 | 3.94 | 8.2 | - |
Facility j | dutj | ftbj | fti | Facility j | dutj | ftbj | fti | Facility j | dutj | ftbj | fti |
---|---|---|---|---|---|---|---|---|---|---|---|
1 | 5 | 4 | 2.39 | 17 | 1 | 1 | 8.54 | 33 | 11 | 10 | 5.67 |
2 | 4 | 4 | 11.54 | 18 | 10 | 10 | 4.58 | 34 | 10 | 10 | 4.17 |
3 | 8 | 7 | 1.92 | 19 | 11 | 10 | 2.57 | 35 | 11 | 11 | 6.20 |
4 | 9 | 8 | 2.01 | 20 | 12 | 11 | 4.65 | 36 | 4 | 3 | 7.49 |
5 | 7 | 7 | 2.70 | 21 | 12 | 12 | 7.60 | 37 | 12 | 12 | 7.54 |
6 | 12 | 10 | 1.89 | 22 | 1 | 1 | 9.06 | 38 | 8 | 6 | 1.90 |
7 | 8 | 7 | 6.35 | 23 | 2 | 2 | 3.97 | 39 | 9 | 7 | 2.04 |
8 | 12 | 12 | 7.62 | 24 | 10 | 9 | 5.54 | 40 | 6 | 6 | 5.22 |
9 | 4 | 3 | 3.77 | 25 | 3 | 3 | 5.97 | 41 | 7 | 7 | 4.58 |
10 | 6 | 5 | 2.07 | 26 | 12 | 12 | 2.03 | 42 | 9 | 8 | 4.24 |
11 | 11 | 11 | 8.93 | 27 | 12 | 11 | 7.41 | 43 | 10 | 9 | 8.87 |
12 | 12 | 11 | 4.63 | 28 | 6 | 5 | 8.25 | 44 | 9 | 9 | 7.19 |
13 | 12 | 12 | 4.09 | 29 | 6 | 6 | 8.85 | 45 | 12 | 12 | 8.99 |
14 | 5 | 4 | 7.49 | 30 | 8 | 7 | 9.81 | 46 | 11 | 11 | 8.20 |
15 | 8 | 7 | 4.19 | 31 | 10 | 9 | 5.95 | 47 | 12 | 12 | 7.51 |
16 | 9 | 7 | 7.02 | 32 | 9 | 9 | 4.35 | - |
Time (Hour) | Day | Total | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | ||
dltci | 0.00 | 0.52 | 2.78 | 0.00 | 1.11 | 0.00 | 0.00 | 1.57 | 1.22 | 0.95 | 0.17 | 1.24 | 9.56 |
ovtci | 1.48 | 1.29 | 0.00 | 2.08 | 0.00 | 2.68 | 0.81 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 8.34 |
Cost ($) | Day | Total Costs ($) | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | ||
Idle time | 0.00 | 23.40 | 125.10 | 0.00 | 49.95 | 0.00 | 0.00 | 70.65 | 54.90 | 42.75 | 7.65 | 55.80 | 430.20 |
Overtime | 88.80 | 77.40 | 0.00 | 124.80 | 0.00 | 160.80 | 48.60 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 500.40 |
Total costs | 88.80 | 100.80 | 125.10 | 124.80 | 49.95 | 160.80 | 48.60 | 70.65 | 54.90 | 42.75 | 7.65 | 55.80 | 930.60 |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2023 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (https://creativecommons.org/licenses/by/4.0/).
Share and Cite
Al-Refaie, A.; Al-Hawadi, A. A Proposed eFSR Blockchain System for Optimal Planning of Facility Services with Probabilistic Arrivals and Stochastic Service Durations. Buildings 2023, 13, 240. https://doi.org/10.3390/buildings13010240
Al-Refaie A, Al-Hawadi A. A Proposed eFSR Blockchain System for Optimal Planning of Facility Services with Probabilistic Arrivals and Stochastic Service Durations. Buildings. 2023; 13(1):240. https://doi.org/10.3390/buildings13010240
Chicago/Turabian StyleAl-Refaie, Abbas, and Ahmad Al-Hawadi. 2023. "A Proposed eFSR Blockchain System for Optimal Planning of Facility Services with Probabilistic Arrivals and Stochastic Service Durations" Buildings 13, no. 1: 240. https://doi.org/10.3390/buildings13010240
APA StyleAl-Refaie, A., & Al-Hawadi, A. (2023). A Proposed eFSR Blockchain System for Optimal Planning of Facility Services with Probabilistic Arrivals and Stochastic Service Durations. Buildings, 13(1), 240. https://doi.org/10.3390/buildings13010240