This turned out to be far, far worse than the casual overprovisioning that the central computing unit had been trying to avoid in the first place. Except that when a cost and paperwork became attached, the units did anything in their power to avoid having wired Ethernet ports. Once a large academic institution started charge-backs for wired Ethernet ports, which I felt originally to be the smart and correct decision to reflect the cost of providing those ports. Simple software compatibility will now be used against you by your own divisions, just like it's used against you by all your vendors. If you let them block something you need or want it might even turn political - they're going to give the veto for no reason unless you back their play on something totally unrelated. This can even happen with open-source software if the unit rejects an upgrade or change. Because the division will decide not to ever pay for upgrades they don't feel they need, and that will end up blocking you from pursuing your other goals. Who "owns" the apps? Pays for them? Decides when they need to be upgraded for intrinsic or extrinsic reasons? If you don't know the answers to that, you do now.Īs attractive as it may seem to require the costs to be paid by the business unit, it's usually not the best idea unless you have a mature process around that. They want IT to pay for an upgrade since we broke Acrobat.
0 kommentar(er)
