Project

General

Profile

Actions

roos-fs tasks #794

open

(PROJECT) Planned vs Executed Services Weekly Graph

Added by Vadim Pariev 5 months ago. Updated 5 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
11/23/2025
Due date:
% Done:

0%

Estimated time:
80:00 h

Description

General
We need to create a simple graph and table that compare planned services per week with executed (completed) services per week.

Planned services calculation:
In general there are 3 logical types of data:

  • Manual entered data (Yellow)
  • Deafault calculation data (red)
  • Actual data (Grey)

Manual entered data (Yellow)

The system should allow the user to set the planned amount of services in two points

  1. Volume of done services expected in by the week (see highloighed with yellow in the file)
  2. Volume of expected planned services per week (see highloighed with yellow in the file)

Deafault calculation data (red)

  1. Volume of services expected in by the week (see highloighed with red in the file) - this is calculated simply by taking the total amount of order deviding them by the amount of weeks and providing the progression of what is expected to be finished by the end week.
  2. Volume of expected planned services per week (see highloighed with yellow in the file) this is calculated simply by taking the total amount of order deviding them by the amount of weeks and shown what is the expected amount of services needs to be finished in order to be on time till the end of the project)

Actual data (Grey)

  1. Actual volume (cumulutive) - here we just state how many services are completed by this week (based on the system data)
  2. Actual volume (weekly) - here we just state how many services are completed in this week (based on the system data)

It is clealy stated how many services are still not planned.

Executed services calculation:
For each week, count how many services were actually completed.

Graph requirements:

Two lines:
Both are using the manual entries
Planned services per week
Executed services per week

The X-axis is weeks.
Y-axis amount of services.

See example from the customer attached.

Status indicator:
A small indicator (with colorcode)should show whether the project is:

On schedule
Ahead of schedule
Behind schedule

Other requirements:

  • reuser the designs from this page, especially the grath https://omspreview.roos-fs.com/statistics
  • make sure taht design is consistent
  • the feature and overview is awailable on the single project overview page
  • New tab in the project overview under the name "Controlling"

Files

Target_curve_DE_Cabin Floor.xlsx (91.4 KB) Target_curve_DE_Cabin Floor.xlsx Vadim Pariev, 12/04/2025 01:31 PM
graph 1.png (112 KB) graph 1.png pic 1 Olena Tretjakova, 01/08/2026 07:58 AM
graph 2.png (149 KB) graph 2.png pic 2 Olena Tretjakova, 01/08/2026 08:08 AM
Actions #1

Updated by Vadim Pariev 5 months ago

  • Status changed from Backlog to Open
Actions #2

Updated by Ivan Danyliv 5 months ago

  • Status changed from Open to In progress
Actions #3

Updated by Ivan Danyliv 5 months ago

  • Estimated time set to 24:00 h
Actions #4

Updated by Ivan Danyliv 5 months ago

  • Status changed from In progress to Open
Actions #5

Updated by Vadim Pariev 5 months ago

  • Subject changed from Planned vs Executed Services Weekly Graph to (PROJECT) Planned vs Executed Services Weekly Graph
  • Description updated (diff)
Actions #6

Updated by Ivan Danyliv 5 months ago

  • Status changed from Open to In progress
Actions #7

Updated by Ivan Danyliv 5 months ago

  • Status changed from In progress to In review
Actions #8

Updated by Ivan Danyliv 5 months ago

  • Status changed from In review to Open
Actions #9

Updated by Vadim Pariev 5 months ago

  • Description updated (diff)
Actions #10

Updated by Vadim Pariev 5 months ago

  • Description updated (diff)
Actions #11

Updated by Vadim Pariev 5 months ago

  • File deleted (Target_curve_DE_Battery Cover.xlsx)
Actions #13

Updated by Ivan Danyliv 5 months ago

  • Status changed from Open to In progress
Actions #14

Updated by Ivan Danyliv 5 months ago

  • Status changed from In progress to Open
Actions #15

Updated by Ivan Danyliv 5 months ago

  • Status changed from Open to In progress
Actions #16

Updated by Ivan Danyliv 5 months ago

  • Estimated time changed from 24:00 h to 75:00 h
Actions #17

Updated by Ivan Danyliv 5 months ago

  • Estimated time changed from 75:00 h to 80:00 h
Actions #18

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #19

Updated by Ivan Danyliv 4 months ago

  • Status changed from In review to In progress
Actions #20

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to Open
Actions #21

Updated by Ivan Danyliv 4 months ago

  • Status changed from Open to In progress
Actions #22

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #23

Updated by Ivan Danyliv 4 months ago

  • Status changed from In review to In progress
Actions #24

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #25

Updated by Danyl Kozub 4 months ago

  • Status changed from In review to Deployed (QA)
  • Assignee changed from Ivan Danyliv to Olena Tretjakova

Updated by Olena Tretjakova 4 months ago

Environment: Staging.

Actual Result:

  1. When the user enters data into the VOI Planned row in the Planning and Review table, an unnecessary element appears in the field, and the entered data is aligned too close to the left side of the field. pic 1

  2. The number of services in the VOI Planned row can be higher than the number of created services.

  3. Each subsequent field in the VOI Planned row allows entering a number lower than the previous one. pic 2

  4. The data in the Weekly Target row should correspond to the data in the VOI Planned row in the same way that Weekly Target by OMS corresponds to VOI Planned by OMS. After the VOI Planned row is filled in, the Weekly Target row should be filled in automatically.

  5. Changes in the Weekly Target row affect the graph of actually completed services, even though they have no relation to the services actually performed.

  6. The number of services in VOI Planned OMS decreases when a service in the project is cancelled, but this contradicts the expected logic because the number of planned services should remain the same as the number of created services.

Actions #27

Updated by Ivan Danyliv 4 months ago

  • Status changed from QA Failed to In progress
Actions #28

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #29

Updated by Ivan Danyliv 4 months ago

  • Status changed from In review to Deployed (QA)
Actions #30

Updated by Ivan Danyliv 4 months ago

  • Assignee changed from Ivan Danyliv to Olena Tretjakova
Actions #31

Updated by Olena Tretjakova 4 months ago

  • Status changed from Deployed (QA) to Open
  • Assignee changed from Olena Tretjakova to Ivan Danyliv
Actions #32

Updated by Ivan Danyliv 4 months ago

  • Status changed from Open to In progress
Actions #33

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #34

Updated by Ivan Danyliv 4 months ago

  • Status changed from In review to Deployed (QA)
Actions #35

Updated by Ivan Danyliv 4 months ago

  • Assignee changed from Ivan Danyliv to Olena Tretjakova
Actions #36

Updated by Ivan Danyliv 4 months ago

  • Status changed from Deployed (QA) to In progress
  • Assignee changed from Olena Tretjakova to Ivan Danyliv
Actions #37

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #38

Updated by Ivan Danyliv 4 months ago

  • Status changed from In review to In progress
Actions #39

Updated by Ivan Danyliv 4 months ago

  • Status changed from In progress to In review
Actions #40

Updated by Ivan Danyliv 4 months ago

  • Status changed from In review to Deployed (QA)
Actions #41

Updated by Ivan Danyliv 4 months ago

  • Assignee changed from Ivan Danyliv to Olena Tretjakova
Actions #42

Updated by Olena Tretjakova 4 months ago

  • Status changed from Deployed (QA) to Ready for Deployment (prod)
  • Assignee changed from Olena Tretjakova to Vadim Pariev

Environment: Staging

Actual Result:
All acceptance criteria have been met.

Actions #43

Updated by Vadim Pariev 3 months ago

  • Status changed from Ready for Deployment (prod) to Closed
Actions #44

Updated by Albert Katasonov 5 days ago

  • Project changed from 8 to Roos-fs-ZIP
Actions

Also available in: Atom PDF