The following status messages should be displayed on the Portal:
1) "Failed" (when a POD deployment has been initiated and has failed in any way)
a) Note that should a POD be in this state, the user should be able to redeploy the POD. There are two ways we could accomplish this:
i) Make the "Failed" status message hypertext sensitive, that, when clicked, would raise a modal pop-up that would allow the user to attempt to redeploy,remove or cancel and return to the screen which invoked the popup. (more work, but better human factors.)
ii) Allow the user to redeploy by following the same procedure they followed when first attempting deployment, including using the EXACT same information, moving the original failed POD records to a zombie state.
2) "Decommissioned" should replace "DEAD"
3) "Decom/Reused" for "Zombie" status (I am open to some word-smithing on this one...)
4) "In Service" for a POD that has successfully deployed
This may require work for both the portal and regional controller...
Medium
The following status messages should be displayed on the Portal:
1) "Failed" (when a POD deployment has been initiated and has failed in any way)
a) Note that should a POD be in this state, the user should be able to redeploy the POD. There are two ways we could accomplish this:
i) Make the "Failed" status message hypertext sensitive, that, when clicked, would raise a modal pop-up that would allow the user to attempt to redeploy,remove or cancel and return to the screen which invoked the popup. (more work, but better human factors.)
ii) Allow the user to redeploy by following the same procedure they followed when first attempting deployment, including using the EXACT same information, moving the original failed POD records to a zombie state.
2) "Decommissioned" should replace "DEAD"
3) "Decom/Reused" for "Zombie" status (I am open to some word-smithing on this one...)
4) "In Service" for a POD that has successfully deployed
This may require work for both the portal and regional controller...