Kombajn

ES: With low priority:
1. I have idea for improvement in claim tab - when there is a break down, we need to select first "break down" category, then select name of the device from checkbox, and then we need to put manually name of the device+breakdown.... Mayby subject can be generated based on selected category and name of the device, it will be displayed in "subject window" but person adding the claim can edit the subject
Additionally, it shows automatically analyst who prepared the analysis when selecting report number. So it should fill automatically line "assigned" with the same person (with possiblility to change if for example we know that this person is on long sick leave ect. can't handle the claim and senior says somebody else should handle it). And Person responsible is a senior/manager responsible for the vessel - this info is inserted in kombajn i CBM table and displayed on mailer module. It could be filled automatically after selecting vessel

2. zgodnie z rozmową z Edytą proponuję, żeby w oknie to-do z automatu pojawiała się rubryka "Tomorrow" do wypełnienia - to sprawi, że nie będziemy musieli o tym pamiętać, a Edyta przypominać nam o tym, że nie wypełniliśmy.

3. Hi, about fdb flags - lets block cost flag for some fdb flags. We shouldn't choose any cost flag if one of following fdb flags was choosen: 1. Recommendation not done 2. Lack response from crew 3. Action postpone 4. Rejected by supr 5. Other job performed. it will reduce number of mistakes during choosing flags

4. My first suggestion for today is adding a new function in Harmonogram. Sometimes for one report we must use data from more than 1 email. Our work becomes much easier if we will have a chance to see the date and hour of the 2nd, 3rd etc. email. So, maybe we'll add a checking box here (for people with weekly permission) and in case of additional email we will click on it. Later on we should have an option to write the date and hour of those additional email(s). Function should be repeatable - sometimes the crew is sendind 3-4 mails to one report, with 1-2 days of "break" between mails Advantages: 1) better information during fill database, you can see very quick what mail is your mail, is everything okay etc; 2) more clear situation for weekly people doing harmonogram, we can see that email is assigned to the report and thank of that; 3) better controlling.

5. JK: mam pomysł jak usprawnić ładowanie listy fdb, może niech działa jak lista claimów, że trzeba podać daty? z tą różnicą, że domyślnie, okienka by były puste i należałoby wstawić day zanim się w ogóle jakiekolwiek fdb zobczy. Statystyki jak są robione i tak z reguły z jakiegoś okresu a nie z całej historii bazy więc wątpię, żeby to przeszkadzało, a powinno zmniejszyć czas ładowania listy. Oczywiście fajnie jakby po zrobieniu jakichś zmian te daty się nie resetowały i odświeżało tylko listę fdb z tego zakresu, a nie ładowało od nowa wszystkie, tak jak to jest teraz

6. Utkilens reports has to be exported to termomarine, right now we has to send report, then finish the send task and then the report is exportable - before that it is not possible to export the report. First of all, it is part of send task so should be done with "send" task. Secondly imo it will be better to make it similar to cbm export, so make it possible to export the report during send and make it unpossible to end the utkilen tasks if the report was not exported

7. hi, weekly, harmo It would be nice to make a possibility to give "new details" reject without getting a task from task list - sometimes crew send new measurements when fill database was finished but analysis not started yet. When harmo person find those measurements write to senior and ask to assign him to this task and then gives reject. It will be faster and easier to make possibility to give "new details" reject to a task without taking it. Additionaly Im not sure if current solution is good, bc when someone give the task back to analysis then it backs to person which gave the reject - in such cases much better will be just back the task to task list - when it back to harmo person he/she just have to back it to task list, usually he/she will not make this analysis. For example in harmonogram in info tab lets make additional button "New details", permission weekly +, only works on analysis stage. additionally we can give a condition that it only works if someone has a task in the task list others in progress ID 103 or 104 or 878

8. Importing CBM Report file via mailer, let's make some new auto check. Sometimes we are sending task older than the newest, for example accept for U2 was finished today on 10, crew send new measurements and we added new report (U3) before send U2 so during send report number in mailer is the newest report number. It bothers me that some times someone could upload report U2 to U3. I think a good idea is to prepare one of below solution, to avoid such mistakes: a) autocheck name of the .pdf file - in each of report file names there is always report number so IT could add checking the name if there is the same number as the one to which the report is exported - if not there should be info in kombajn/skype/teams/gg b) make dropdown menu in maile unchangeable, choosen report number is always the same as task which you has as in progress, or make it changeable but current(your current) task will be defaulty choosen

9. I believe we could improve our team's efficiency and professionalism by standardizing the way we send touch lists. Having multiple formats and styles creates confusion and inconsistency and its unprofessional. I propose that the IT department develop a standardized template, perhaps a Word or Excel document, which by the way could automatically populate dates from an Excel Datasheet. This would ensure a uniform and professional appearance for all touch lists. SM