DREF Imminent returns!

[anamariaescobar]

We are ready to re-start the work, below you will find all the fields currently used in the DREF Imminent Application and how they map out to the new form:

General Observations

• Tittle on the Export must be "Imminent DREF operation" instead of "DREF Operation"

Operation Overview

• Emergency appeal planned: Hide this field
• Upload map: Hide this field
• Type of Onset: Let's keep this field but it should default to "Sudden", no option to be changed
• Disaster Category: Hide this field
• If available please upload Crisis categorization Analysis: Hide this field

Event Detail ---> Replace name with "Scenario Analysis"

• Previous Operations: Hide the whole section
• Description of the Event: Hide the whole section, only Total people at risk and Sources of information will remain visible
• Add new question: When and where is the hazard expected to happen? : Guidance: Narrative including Date and geographical areas
• Add new question: Explain the underlying vulnerabilities and risks the hazard poses for at-risk communities? : Text. Guidance: Based on comparison of past events, what humanitarian impacts do you expect? Of what magnitude? (e.g. last time there was a cyclone making landfall with this windspeed, XX houses were destroyed, and we had to launch a DREF/emergency appeal for CHF xxx)
• Add new space to attach documents: Upload any additional support document (Optional)

Action/Needs ---> Hide the whole section

Operation

• Hide the whole section, only "Total Targeted Population" section and "Will surge personnel be deployed?" will remain visible.
• Add new space to attach documents: "If the National Society has developed contingency plans, or recently carried out PER assessment or readiness check for instance, kindly attached those documents here"
• Add new question: Which of the expected severe humanitarian impacts of the hazard are your actions addressing? Why were these impacts chosen? --> Guidance: Prioritized impact of the foreseen disaster
• Add new section: "Proposed actions", this section will be similar to "planned interventions" in the other forms, but the grouping wont be by sector (Shelter, Health, etc) but by type of intervention, there will be only two boxes, "Early Actions" and "Early Response", with Activities (we want to find a way to "tag" each one of the activities with sectors) and budget, some extra rows at the end, please see picture attached below (please note that the sub-total should be a sum of the budgets, it should ALWAYS total 75k, so we can add some logic and a warning if it is not matching)
  

Operational Timeframes and Contacts---> Stays the same, only hide the Glide number

@tovari @udaynwa @marcovvu1

[samshara]

@anamariaescobar We reviewed the requested changes, and most of these appear to be minor.
However, we have some questions:

• When we say "hide," are we only hiding the field, or should it be removed entirely? If we're simply hiding it, this might mean the database continues to store fields that aren’t needed. If we decide to clean up these fields, we could lose previous data.

• Regarding the following:

Add new section: "Proposed actions." This section will be similar to "planned interventions" in other forms, but the grouping will be by type of intervention (not by sector, e.g., Shelter, Health, etc.). It will have only two boxes, "Early Actions" and "Early Response," with Activities (we would like to "tag" each activity with sectors) and budget. Some additional rows at the end are required, as shown in the picture below (please note that the sub-total should sum the budgets to always total 75k. We could add logic and a warning if it doesn’t match.)

Should the Activities box be a text field where we can enter multiple sectors (text fields) with the budget for that box/column, or should it be broken down by individual sectors with a budget field for each? Also, do we need to link to actual sectors in GO, or is free text sufficient?

Also, do we need to include the "Surge deployment" and "Indirect cost" sections?

• Since we are modifying the entire form, have we considered the impact on the Operational Update and Final Report forms? Some fields that are hidden here may appear in these reports. Should the new fields also appear in the Operational Update and Final Report forms?

cc @tovari @marcovvu1 @tovari

[anamariaescobar]

Hello @samshara !!!

Here some answers to your questions:

• When we say "hide," are we only hiding the field, or should it be removed entirely? If we're simply hiding it, this might mean the database continues to store fields that aren’t needed. If we decide to clean up these fields, we could lose previous data. We want to hide them, we don't want to loose the data we have collected so far for those fields, but it wont be needed going forward, is there a way we re-name those fields adding Deprecated or something like that?

• Regarding the following:

Add new section: "Proposed actions." This section will be similar to "planned interventions" in other forms, but the grouping will be by type of intervention (not by sector, e.g., Shelter, Health, etc.). It will have only two boxes, "Early Actions" and "Early Response," with Activities (we would like to "tag" each activity with sectors) and budget. Some additional rows at the end are required, as shown in the picture below (please note that the sub-total should sum the budgets to always total 75k. We could add logic and a warning if it doesn’t match.)

Should the Activities box be a text field where we can enter multiple sectors (text fields) with the budget for that box/column, or should it be broken down by individual sectors with a budget field for each? Also, do we need to link to actual sectors in GO, or is free text sufficient? I think for this one we might want to have one field for the activity and a corresponding field for the sector (which yes, it should link to the actual sectors we have in GO) and then have the ability to add another activity with their corresponding sector (like in the risk section we have for other DREF applications, instead of having a big blank text box

• Also, do we need to include the "Surge deployment" and "Indirect cost" sections? Surge deployment should appear and ALWAYS be 10k if the answer to Surge deployment under the Operation section is set to yes. Indirect costs will always appear and it will always be 5k if surge question is no, and 5,8k if the answer is yes

• Since we are modifying the entire form, have we considered the impact on the Operational Update and Final Report forms? Some fields that are hidden here may appear in these reports. Should the new fields also appear in the Operational Update and Final Report forms? With this new Imminent form there will be no Operational Update for Imminent, the only Operational Update will be to change the operation to a response, we will make some mapping to se what fields can be prepopulated from the Application. For the final report, we will post another ticket with the requirements.

We do need to discuss how are we going to handle the transition time, when we launch this new imminent form we need to block the previous one, but if there is any imminent operations that began before the launch, they should continue with the previous behavior and forms, I think it would be useful to set up a call to discuss this, let me know what you think?

One more thing that I forgot to add on the previous ticket:

• We need a new additional export, which will be the regular export plus the 2 las pages of the document attached (so the user will have the option to download just the export or the export+PGA whichc is including the last 2 pages).
  Imminent DREF request.docx

@samshara @tovari @marcovvu1