aebrown wrote:Although I would certainly agree that most if not all callings can benefit from using WiFi, I think it's certainly possible and even required to draw lines if your building's current network simply won't support hundreds of people using the connection simultaneously. Sure, we may all agree that the nursery leader [B]could benefit from accessing LDS.org, but is that more important than the bishop accessing CDOL to find how to contact another bishop or to enter a missionary application, or for a ward clerk to adjust an upcoming event on a calendar that had to be moved and send out notifications about it? Those answers are pretty clear.[/B]
Bro. Brown, you assuming that the bishops calling is more important than the Nursery Leader. Some would say its higher up the ladder than the Nursery Leader. When in actuality its on the same track just in a different station. And at times the nursery class has to have priority over what the Bishop needs are. And lets not forget that the Bishops number one priority should be the youth of the church, from primary ages on up to Young Adults.
So in your scenario I would say on Sunday during meeting hours gospel instruction should take priority over the bishop or clerks trying to do as you described, that would include the nursery leader. Those other things are not as important as they may seem and can be done later when the building is not as busy.
aebrown wrote:Leadership often requires making judgments about how to allocate relatively scarce resources (budgets, building use, the bishop's time, etc.); this is a similar situation where in some cases some people will simply have to be denied WiFi access.
I agree but those judgments and decisions have to be prioritized on sound principles. To base the decision solely on ones calling is not sound principles. You have to take into consideration all the stake holders involved and how they would benefit as well as the organization. In our case of out the password to all the members (stake Holder) it would seem that the organization has more to benefit from it than to lose, even if the may at times cause the net work to slow down.
aebrown wrote:That doesn't mean that leaders and other people involved don't make efforts to improve the network so that more people can benefit from it, but that may take some time.
I know they are doing what they can with what they have to work with. But with holding the password while we work to make things better does not benefit anyone.
aebrown wrote:I don't see how the only possible conclusion is that "the management side of FM has no practical experience." My first assumption (which I know is certainly true in some cases) is that budgets are sometimes tight and when the FM group has to prioritize needs, enhanced WiFi coverage may come behind fixing a leaky roof, paying the electric bill, and resurfacing the parking lot that is riddled with potholes.
I agree there has to be priority's set in all things and there has to be leeway for unseen contingencies. However, having a back ground in FM (22 years in the Air Force managing millions of dollars of Facilities and infrastructural) I know that practical experience is more important when it comes to making decisions and prioritizing requirements. What limited experience I have had with the local FM group it was obvious that they had no piratical experience when it came to Management of the Facilities and setting priorities.
aebrown wrote:Certainly some FM groups are weak in the IT area, but it doesn't seem practical for the Church to create a whole local organization for managing IT, so there will be some rough areas as we implement IT improvements.
I'm not talking about a separate organization. I'm talking about hiring personnel who have experience in installing and repairing net works, and getting the job done. STS should not have to give direction to the FM Group on what needs done or how to do. However, I have seen examples of that scenario many times on this form and in my own stake.