Add information about progress of task

[LaChope]

@kostobog Number from statistics, how much should be done, how much was done.

From this: https://docs.google.com/spreadsheets/d/13zMQOvi8Cgr1Emxv7TKGTlIo1Za2wU48BX_PRp3p8es/edit#gid=386279150 ?

[kalamartin]

• est-min from time-estimate table
• number of mechanics performed time booking on this specifics TC in this specifics WP
• average time spend on this TC from history data
• time booked in this WP on this TC @lalisand @LaChope

[blcham]

@blcham

[blcham]

@kostobog please describe in steps what needs to be done

[kostobog]

Based on discussion with MK, this is what needs to be done.

---

1)

Implementing est-min

1. model - Add a est-min property to TaskPlan Entity
2. Data access - Load est-min per TC step from data repository, calculate est-min per TC
3. planning - in planning retrieve est-min per TC and set it in TaskPlans.

---

2)

Performed time bookings per TC

• It can be implemented on client side - this should be equivalent to the number of plan parts (SessionPlans) of TC's TaskPlans.
• number of mechanics of performed sessions on a TC can be also implemnted on the client side. Count the different mechanics of the plan parts (SessionPlans) of the TCs TaskPlan.

---

3)

Average time spend on this TC from history data

1. model - Add work-time-estimate property in TaskType
2. data processing - calculate average time spent per taskTypeIRI across all closed WPs. Store the results as a work-time-estimate property of taskTypeIRI.
3. data access - Rewrite loading TaskTypes from data repo to load the new property work-time-estimate.
4. client side - Client can access the TaskType from TaskPlans to present the work-time-estimate value.

---

4)

time booked in this WP on this TC - I assume this is the planned work time, in this case this is already implemented

@blcham

[blcham]

1. -- need to add construct queries @kostobog, then implement on frontend
2. -- implemented already on backed, need to be implemented only frontend
3. -- need to add construct queries @kostobog, then implement on frontend
4. -- implemented already on backed, need to be implemented only frontend

[blcham]

@kostobog if possible add statistics to separate graph

[kostobog]

I added statistics average work time and est-min to separate graph <http://onto.fel.cvut.cz/ontologies/csat-maintenance/statistics>.

The statistics were calculated using the queries TC average work time and TC execution est-min

[blcham]

@kostobog Can you evaluate what was done from points 1,2,3,4 ?

In case all was done I will create specific issues to automate the solution, by two steps:

• [ ] https://github.com/kbss-cvut/aircraft-maintenance-planning-system/issues/184
• [ ] Run it from the dashboard after each update

[kostobog]

@blcham All four points were implemented.

[kostobog]

Progress in tooltip updated in https://github.com/kbss-cvut/csat-maintenance-planner/pull/162

[kostobog]

@kalamartin Check progress in plan editor. Progress should appear for all plan parts above and including task plans (i.e. TCs and WOs). The performance parameters are: Estimated work-time

• Estimated work-time for TCs and WOs - EstMin value
• Estimated work-time for plans composed of TCs and WOs - sum of EstMin of its parts

Average work-time

• Average work-time for TC executions across history WP.
• Average work-time for plans composed of TCs - sum of Average work-times of its parts

Work-time

• Work-time for work sessions - the duration of the work session
• Work-time for TCs and WOs - sum of duration of work sessions
• Work-time for plans composed of TCs and WOs - sum of Work-times of its part

Duration - for all plan parts shows duration between start and end of the plan

Mechanic count - for all plan parts shows the number of different mechanics

[kalamartin]

Tested, all seems working. Should we close this issue or we will continue also with statistics based on TermIt data?

@blcham @kostobog

[kalamartin]

Closed with reference to #152