Are Standardization from Enterprise Architecture

Are calibration and conception in conflict? I have no doubt calibration and intro argon in conflict, at least(prenominal) to nearly extent, because standardization (almost by definition) reduces the amount of variation of regalees or systems simultaneously used in a company. That is the whole point of standardization. If you reduce the variation allowed in the company, consequently necessarily you would lose some knowledgeability that could have happened.I think if innovation is viewed in an evolutionary way, mass variation would be created by the local units steeringed on their individual needs and only the best innovations would e retained and scaled to the rest of the company. If all the companies departments are allowed to develop topically optimal solutions to their problems, certainly some of these variations will be better (at least for the unit) than by using a standardized software or technologies company-wide.To watch with the evolutionary theme, using any centr ally dictated standardized process would reduce the possible variation in which could be selected from the environment of each business unit. Think the better to view standardization vs.. mental home as an inescapable trade-off. Does an enterprise architecture that allows a company to increase running(a) efficiency, ease of integration, reduce development costs, duplication of systems, simplify the acquisition of brand-new modules, and sometimes vastly reduced maintenance costs worth some drop in the regularize of innovation?I would argue that is abruptly worth it in in most instances. The key is to view this as an optimal trade-off where you can retain almost all of the innovation while also increasing standardization. An Enterprise Architecture that standardizes the types of technologies used crosswise the many (PH/Dot. Net or Unix/Microsoft) is in the best interest of the company.When you by choice limit the available options of each individual business units options (such as when Timberjack fixed to use Unix and that immediately removed many otherwise eligible companies) you are going to reduce the chance of finding the perfect solution for all(prenominal) possible module. Fortunately, most companies can settle on a very(prenominal) good but not perfect solution with any of the foodstuff leading platforms without getting a major drop in innovation.Agreeing on a standardized portfolio of technologies and processes, a company can then focus its resources on take new functionality to their users without wasting so many resources exhausting to hold together a Frankincense combination of dozens of systems, technologies and processes together that work perfect in isolation. Ultimately, using more resources on bringing new functionality will increase the total value of the IT department and the rate the department can innovate. Are Standardization from Enterprise Architecture and Innovation in Conflict? By Seasonableness