Ability to identify when other units attend jobs

[Gauci2711]

HI Team,

I am wondering if we are able to identify how many times a specific unit attends a job outside of their boundary, i.e a unit supports a neighbouring unit with some rfa's?

We are calculating the workloads of each unit and wanted to ensure we tried to capture as many jobs as possible.

Kind Regards

Shane Gauci

[OSPFNeighbour]

Hey man,

How do you define a teams unit? would you expect it to just be what unit the team is attached to, or what unit the majority of the people on the team are from?

Just thinking through what data is needed to calculate this. In Central Cluster we normal hand over the team to the away HQ if we are assisting so wouldnt be able to use the attached HQ to get the number you need.

[Gauci2711]

HI Tim, Thanks for getting back quickly. I guess it is how the data is inputted, if we go with the majority of member option that should capture both ways of inputting. Is there an option to use the team name? I guess that is hit and miss also lol Cheers, Shane Gauci From: Tim Dykes <notifications@github.com> Sent: Tuesday, 25 June 2019 3:53 PM To: NSWSESMembers/Lighthouse <Lighthouse@noreply.github.com> Cc: Shane Gauci <shane.gauci1@one.ses.nsw.gov.au>; Author <author@noreply.github.com> Subject: Re: [NSWSESMembers/Lighthouse] Ability to identify when other units attend jobs (#127) Hey man, How do you define a teams unit? would you expect it to just be what unit the team is attached to, or what unit the majority of the people on the team are from? Just thinking through what data is needed to calculate this. In Central Cluster we normal hand over the team to the away HQ if we are assisting so wouldnt be able to use the attached HQ to get the number you need. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#127?email_source=notifications&email_token=AMOF3CBNE7HMSX6ZSHIK75TP4GXEDA5CNFSM4H3ETXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPC4CQ#issuecomment-505294346>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMOF3CGVI3ZAD63XOLRLOWTP4GXEDANCNFSM4H3ETXAA>.

[sjcliffe]

A bit off topic but I've had a look at this for the stuff I'm doing with the mystic beacon reports and it wouldn't be too hard to include. Basically: for each Unit team check the jobs attended and if they belong to a different Unit count them.

Presumably you would want a breakdown of the job types (storm, search, rescue etc)?

[OSPFNeighbour]

That logic doesnt really work when you transfer teams around the cluster Tim Dykes

…

On Thu, 27 Jun 2019 at 14:31, Steve Cliffe ***@***.***> wrote: A bit off topic but I've had a look at this for the stuff I'm doing with the mystic beacon reports and it wouldn't be too hard to include. Basically: for each Unit team check the jobs attended and if they belong to a different Unit count them. Presumably you would want a breakdown of the job types (storm, search, rescue etc)? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#127?email_source=notifications&email_token=ABMH2NUQFYGG3VRKGJUORPLP4Q7CVA5CNFSM4H3ETXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYVUOVI#issuecomment-506152789>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABMH2NSPKTSKKAWDLSPX2X3P4Q7CVANCNFSM4H3ETXAA> .

[sjcliffe]

It works in our cluster. We have 2 Units, teams are created at the Unit level and regularly attend jobs in the other Unit's area particularly for searches.

How does it work in your cluster?

[OSPFNeighbour]

Change the HQ of the team to the Unit which they are assisting. Guess you can use the CreatedAt field to work out where they came from

…

On Thu, 27 Jun 2019 at 14:38, Steve Cliffe ***@***.***> wrote: It works in our cluster. We have 2 Units, teams are created at the Unit level and regularly attend jobs in the other Unit's area particularly for searches. How does it work in your cluster? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#127?email_source=notifications&email_token=ABMH2NWOTQ25KED2VTL3YS3P4Q75PA5CNFSM4H3ETXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYVWGCA#issuecomment-506159880>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABMH2NRERSUD46RIVDKC4PTP4Q75PANCNFSM4H3ETXAA> .

[Gauci2711]

HI Tim and Steve, Steve – what you discussed initially is what I thought would be the process. For the need I have at the moment, we are just looking at the units workload over a period of time (overall RFA numbers) but a breakdown further would definitely be of some kind of assistance if we are able to do it. I guess the process of how we create teams and share them between units & clusters need to be defined better and then communicated to provide the data easier for this type of report. Beacon is a part of a project I am working on for the Southern Zone where we have to increase the use of beacon and ensure every job is captured as the number of RFAs attended per year effect Vehicle replacement, commanders rank and insignia etc and in some cases it is not truly representing what the units do every year. I am keen to see what we are able to do. Cheers, Shane Gauci <snip signature> From: Tim Dykes <notifications@github.com> Sent: Thursday, 27 June 2019 2:53 PM To: NSWSESMembers/Lighthouse <Lighthouse@noreply.github.com> Cc: Shane Gauci <shane.gauci1@one.ses.nsw.gov.au>; Author <author@noreply.github.com> Subject: Re: [NSWSESMembers/Lighthouse] Ability to identify when other units attend jobs (#127) Change the HQ of the team to the Unit which they are assisting. Guess you can use the CreatedAt field to work out where they came from

On Thu, 27 Jun 2019 at 14:38, Steve Cliffe ***@***.******@***.***>> wrote: It works in our cluster. We have 2 Units, teams are created at the Unit level and regularly attend jobs in the other Unit's area particularly for searches. How does it work in your cluster? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#127?email_source=notifications&email_token=ABMH2NWOTQ25KED2VTL3YS3P4Q75PA5CNFSM4H3ETXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYVWGCA#issuecomment-506159880>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABMH2NRERSUD46RIVDKC4PTP4Q75PANCNFSM4H3ETXAA> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#127?email_source=notifications&email_token=AMOF3CAVFG3KZIEDWGXGMJLP4RBSZA5CNFSM4H3ETXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYV5JCY#issuecomment-506188939>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMOF3CBWYDKJSMBC6K2Z35LP4RBSZANCNFSM4H3ETXAA>.

[sjcliffe]

I've added a "Neighbouring Jobs by Month" graph to the Unit job summary report at https://mystic.ses.nsw.gov.au/beaconreports/

Currently only implemented for this year but let me know if this is what you're after.

The job type breakdown graphs don't currently take these extra jobs into account.

[Gauci2711]

Hi Steve, Thanks heaps, I will have a play and see how it goes. Thanks for your efforts! Kind Regards, Shane Gauci From: Steve Cliffe <notifications@github.com> Sent: Tuesday, 2 July 2019 11:18 AM To: NSWSESMembers/Lighthouse <Lighthouse@noreply.github.com> Cc: Shane Gauci <shane.gauci1@one.ses.nsw.gov.au>; Author <author@noreply.github.com> Subject: Re: [NSWSESMembers/Lighthouse] Ability to identify when other units attend jobs (#127) I've added a "Neighbouring Jobs by Month" graph to the Unit job summary report at https://mystic.ses.nsw.gov.au/beaconreports/ Currently only implemented for this year but let me know if this is what you're after. The job type breakdown graphs don't currently take these extra jobs into account. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#127?email_source=notifications&email_token=AMOF3CG42R57NAW4UBWNNZDP5KUEHA5CNFSM4H3ETXAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY7YTBY#issuecomment-507480455>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMOF3CF5PFRICHZACQRI2UTP5KUEHANCNFSM4H3ETXAA>.