Categories
erwin Expert Blog

Managing Emerging Technology Disruption with Enterprise Architecture

Emerging technology has always played an important role in business transformation. In the race to collect and analyze data, provide superior customer experiences, and manage resources, new technologies always interest IT and business leaders.

KPMG’s The Changing Landscape of Disruptive Technologies found that today’s businesses are showing the most interest in emerging technology like the Internet of Things (IoT), artificial intelligence (AI) and robotics. Other emerging technologies that are making headlines include natural language processing (NLP) and blockchain.

In many cases, emerging technologies such as these are not fully embedded into business environments. Before they enter production, organizations need to test and pilot their projects to help answer some important questions:

  • How do these technologies disrupt?
  • How do they provide value?

Enterprise Architecture’s Role in Managing Emerging Technology

Pilot projects that take a small number of incremental steps, with small funding increases along the way, help provide answers to these questions. If the pilot proves successful, it’s then up to the enterprise architecture team to explore what it takes to integrate these technologies into the IT environment.

This is the point where new technologies go from “emerging technologies” to becoming another solution in the stack the organization relies on to create the business outcomes it’s seeking.

One of the easiest, quickest ways to try to pilot and put new technologies into production is to use cloud-based services. All of the major public cloud platform providers have AI and machine learning capabilities.

Integrating new technologies based in the cloud will change the way the enterprise architecture team models the IT environment, but that’s actually a good thing.

Modeling can help organizations understand the complex integrations that bring cloud services into the organization, and help them better understand the service level agreements (SLAs), security requirements and contracts with cloud partners.

When done right, enterprise architecture modeling also will help the organization better understand the value of emerging technology and even cloud migrations that increasingly accompany them. Once again, modeling helps answer important questions, such as:

  • Does the model demonstrate the benefits that the business expects from the cloud?
  • Do the benefits remain even if some legacy apps and infrastructure need to remain on premise?
  • What type of savings do you see if you can’t consolidate enough close an entire data center?
  • How does the risk change?

Many of the emerging technologies garnering attention today are on their way to becoming a standard part of the technology stack. But just as the web came before mobility, and mobility came before AI,  other technologies will soon follow in their footsteps.

To most efficiently evaluate these technologies and decide if they are right for the business, organizations need to provide visibility to both their enterprise architecture and business process teams so everyone understands how their environment and outcomes will change.

When the enterprise architecture and business process teams use a common platform and model the same data, their results will be more accurate and their collaboration seamless. This will cut significant time off the process of piloting, deploying and seeing results.

Outcomes like more profitable products and better customer experiences are the ultimate business goals. Getting there first is important, but only if everything runs smoothly on the customer side. The disruption of new technologies should take place behind the scenes, after all.

And that’s where investing in pilot programs and enterprise architecture modeling demonstrate value as you put emerging technology to work.

Emerging technology - Data-driven business transformation

Categories
erwin Expert Blog

Enterprise Architect: A Role That Keeps Evolving

Enterprise architect is a common job title within IT organizations at large companies, but the term lacks any standard definition. Ask someone on the business side what their organization’s enterprise architects do, and you’ll likely get a response like, “They work with IT,” which is true, but also pretty vague.

What the enterprise architects at your organization do depends in large part on how the IT department is organized. At some organizations, enterprise architects work closely with the software applications in a role that some might refer to as a solution architect.

In other organizations, the role of enterprise architect might carry more traditional IT responsibilities around systems management. Other enterprise architects, especially at large organizations, might specialize in exploring how emerging technologies can be tested and later integrated into the business.

Technology research and advisory firm Gartner predicts that enterprise architects will increasingly move into an internal consultancy function within large organizations. While this use of the role is not currently widespread, it’s easy to see how it could make sense for some businesses.

If, for example, a business sets a goal to increase its website sales by 20 percent in one year’s time, meeting that goal will require that different IT and business functions work together.

The business side might tackle changes to the marketing plan and collect data about website visitors and shoppers, but ultimately they will need to collaborate with someone on the technology side to discuss how IT can help reach that goal. And that’s where an enterprise architect in the role of an internal consultant comes into play.

Each business is going to organize its enterprise architects in a way that best serves the organization and helps achieve its goals.

That’s one of the reasons the enterprise architect role has no standard definition. Most teams consist of members with broad IT experience, but each member will often have some role-specific knowledge. One team member might specialize in security, for example, and another in applications.

Like the tech industry in general, the only constant in enterprise architecture is change. Roles and titles will continue to evolve, and as the business and IT sides of the organization continue to come together in the face of digital transformation, how these teams are organized, where they report, and the types of projects they focus on are sure to change over time.

Enterprise integration architect is one role in enterprise architecture that’s on the rise. These architects specialize in integrating the various cloud and on-premise systems that are now common in the hybrid/multi-cloud infrastructures powering the modern enterprise.

Enterprise Architect: A Role That Keeps Evolving

For the Enterprise Architect, Business Experience Becomes a Valuable Commodity

Regardless of the specific title, enterprise architects need the ability to work with both their business and IT colleagues to help improve business outcomes. As enterprise architecture roles move closer to the business, those with business knowledge are becoming valuable assets. This is especially true for industry-specific business knowledge.

As industry and government compliance regulations, for example, become part of the business fabric in industries like financial services, healthcare and pharmaceuticals, many enterprise architects are developing specializations in these industries that demonstrate their understanding of the business and IT sides of these regulations.

This is important because compliance permeates every area of many of these organizations, from the enterprise architecture to the business processes, and today it’s all enabled by software. Compliance is another area where Gartner’s internal consultancy model for enterprise architects could benefit a number of organizations. The stakes are simply too high to do anything but guarantee all of your processes are compliant.

Enterprise architect is just one role in the modern organization that increasingly stands with one foot on the business side and the other in IT. As your organization navigates its digital transformation, it’s important to use tools that can do the same.

erwin, Inc.’s industry-leading tools for enterprise architecture and business process modeling use a common repository and role-based views, so business users, IT users and those who straddle the line have the visibility they need. When everyone uses the same tools and the same data, they can speak the same language, collaborate more effectively, and produce better business outcomes. That’s something the whole team can support, regardless of job title.

Business Process Modeling Use Cases