Lord Auriel, on 02 December 2023 - 03:20 AM, said:
I disagree. I work for big companies who deal with big tech. Netapp solutions, mail platforms.
You are looking at a typical P1 incident. It works just the same as when we have these. The number of people working on it doesn't change the outcome or the solution time one second really.
This issue that PGI are having, is one of the kind where in reality, there is one person who takes the lead in developing the database script, another one who takes the lead in communication and so on. The absolute last thing you ever want is three people working on the same problem, because: for what? it just takes time. Meddling with databases in such a manner where you don't have months to prepare and play around on a dev environment, is extremely dangerous. You just can't mess this up.
Now for people that dont know.P1 incidents are priority 1 incidents.Urgent/critical affecting several users or the full enterprise.OR negatively affecting the ability to transact time sensitive business that would have substantial bottom line impact to the business.
P2 just for the record is a high/important affecting one or more users that prevents or negatively impacts business operations.
I will agree with you.This is a priority 1 case since we have a widespread network failure or issue significally hampering normal operations.Name it as you like.Bottom line people cant play normally.
Now we have categorized the problem.In order to recomment any kind of solution I probably would be needing more info.
Since infromation like that should stay within the company we can talk generally how to manage a few cases.
If the problem is hardware, some purchased equiptment, most likely it should be covered from a warranty or a support contract.If equiptment failed, wheather by phone or email you must contact engineers to adress the problem.They probably will run some troubleshooting steps with someone from PGI to try to fix the issue if possible or establish exactly what the problem is.Following the completion of diagnostics you either fix it or get new equiptment.
If the problem is software, now things get more complicated depending on a number of factors.To name a few, server technologies, networking, storage, data, applications etc.Those might seem chaotic, but as you mention there must be people from PGI who take the lead on certain areas.
Now i dont recommend 4-5 people messing around with code all at the same time when i propose more manpower.I just proposed more people to be actively evolved on adressing P1-P2 problems each on their respected field.You cant have one person on lead for everything for example.It feels like that on PGI.Resources are not just people.You can add to that money, 3rd party services and whatever else is needed to get the job done.
Take care