SAP in the cloud: Rethinking core processes and architecture

In its initial stages, ERP, particularly SAP, was frequently considered an ambitious undertaking. However, over time, it has demonstrated its effectiveness. From operational and commercial management to customer relationship management, human resources management, financial administration, and logistics operations management, SAP has proven its versatility in handling nearly every aspect.

While SAP has become indispensable for numerous organizations and their information systems, it has left behind a varied legacy. Some projects experienced delays, others were initially abandoned and later resumed, and challenges emerged in integrating with other systems or adapting to new processes. However, once implemented, whether it’s an ERP of SAP origin or from another vendor, it proves to be not only useful but highly stable. Moreover, it ensures tangible improvements in efficiency, including faster decision-making and task execution, enhanced collaboration, regulatory compliance, and optimized budget management.

Hence, it comes as no surprise that the declaration of the obligatory shift of all SAP instances to the cloud, initially set for 2025 and later revised to 2027, has triggered apprehension in numerous companies. Concerns about potential costs, intricacies, required efforts, and risks associated with business continuity have surfaced. The paramount risk lies in addressing this project solely from an IT perspective. The key is to transform it into an opportunity to revamp processes and the fundamental architecture—this time, leveraging insights gained from prior deployments.

The enterprise architect, cloud migration strategist for SAP instances

As business requirements and processes have evolved since the initial implementation of SAP, the landscape has been shaped by successive mergers and acquisitions, necessitating connections between information systems. Unfortunately, the information system map hasn’t always been consistently updated. Nevertheless, the valuable lesson from initial deployments is clear: only with a comprehensive understanding of businesses, their processes, and the information system can an ERP project be effectively managed and rendered more reliable.

In such circumstances, business architects play a pivotal role in bolstering this transformation initiative. Beyond providing an overarching perspective of the information system (comprising structure, interactions, handled data, supported processes, and hosted technical infrastructures), they also consolidate all the essential skills required for a successful migration project from SAP to the cloud. This involves concretely outlining the strategy and deployment scenarios. The approach may be structured by process, business function, geographic sector, etc., contingent on existing dependencies and the correlated risks of complexity.

Hence, with each formulated scenario, the enterprise architect can evaluate potential effects on the overall information system or on specific data (varying in criticality) – this evaluation includes estimating the financial repercussions. The goal is to ascertain the value-to-risk ratio for each scenario, enabling the prioritization of various phases in the migration process.

Creating a fresh architecture and implementing new processes: What’s the approach?

During a transformation initiative, migrating SAP instances to the cloud transcends a mere replication of the existing setup. For the business architect, the foundational step is defining objectives and shaping the target architecture in the cloud. The impacts, such as changes in application structure and interfacing, costs, and service guarantees (SLA, security), will vary based on the decisions made. The challenge is to make informed choices for an application that remains central to the core business, even in the cloud.

Likewise, there’s a need for a pre-migration effort to gather and standardize processes to effectively accommodate shifts in working methods.

Regardless of the approach taken, change management is a critical phase that demands attention. Given the project’s genuine transformative nature, support is not incidental; it is integral for ensuring the project’s seamless progression to completion and the swift adoption of new tools by stakeholders involved in the business.

Source: mega

In 2008, the world was jolted by a financial crisis of unprecedented magnitude, surpassing the severity of past significant upheavals, such as the notorious Black Thursday of 1929. The global financial system, interwoven through intricate connections and dominated by influential players across multiple markets, succumbed to a domino effect where the collapse of one institution swiftly triggered the downfall of others. Today, the hyper-digitally connected world of financial institutions poses an even greater threat: should a key player’s information system falter, the system’s collapse could be near-instantaneous and of an unprecedented magnitude.

In this context, the Digital Operational Resilience Act (DORA) aims to guarantee the resilience of financial institutions and their associated third parties in a sector that is 100% digital and subject to constant cyber threats. DORA is a new EU regulation that mandates that companies and organizations in the financial sector manage all components of operational resilience: ability to protect, detect, contain, recover and repair ICT incidents.

In all, no fewer than 22,000 organizations will be impacted by this regulation.

To meet the obligations laid down by the DORA, financial institutions, and their third parties must implement and document a series of measures around their Information and Communication Technologies (ICT) which can be categorized into 4 main themes. By January 17, 2025, these 22,000 companies must ensure that all necessary preparations are in place to meet their obligations under these guidelines.

1 – Set up an ICT risk management system (Pillar 1)

The first pillar of the DORA is the most important: it serves as the foundation from which all other elements derive. It is also one of the most complex, as it requires a holistic approach based on a detailed knowledge of the company, its operations, and processes (especially the most critical ones), and above all its technological architecture (systems and applications supporting these processes).

Once this risk management system is in place, the DORA mandates a control obligation, which can be carried out continuously or at predefined frequencies. These highly detailed controls cover business and procedural aspects, as well as the technological layer – right down to the smallest application involved in a critical process. While most financial institutions already have such controls in place, it should be noted that IT controls specific to the DORA will be required to ensure full compliance with this new regulation.

In a broader sense, there will be a heightened need for closer collaboration between Risk and Control teams and the IT department.

2 – Identify and control third parties (Pillar 5)

Recognizing the growing complexity of financial information systems and its multitude of entities, applications, and infrastructures, the European regulator has broadened the scope of cautionary obligations to third-party services integrated within these architectures. This encompasses not only business partners who are inherently subject to the DORA, but also all technology partners.

Application publishers, cloud providers, and other Managed Services Providers (MSPs) will be impacted by the new European regulation. Specifically, regarding the terms of the Service Level Agreement (SLA) and the security they provide. Additionally, it will be crucial to establish contingency plans for substitute third parties in case of system failure or security breaches.

The concentration of services within a single third party can constitute a risk in itself: what happens if the main (or even only) cloud service provider is attacked? For this reason, it may be worthwhile for financial institutions to develop a multi-vendor strategy to limit the risks (and damage) in the event of an attack or a failure of a key third party.

3 – Regularly test your continuity capabilities (Pillar 3)

Risk awareness in the financial sector is nothing new. Business continuity and the threat of a domino effect have led most institutions to build contingency plans for their key processes. These are useful, if not vital solutions, provided they are regularly tested to ensure that they will continue to perform properly when situations take a turn for the worse.

Cybersecurity capabilities must be constantly tested and updated to counter the ever-evolving cyber threats. Cybersecurity is a living discipline requiring continual testing and updates in this relentless pursuit of protecting sensitive data and digital assets. For financial institutions, the imperative lies in establishing an ongoing investment plan and fostering genuine agility to uphold state-of-the-art cybersecurity systems to shield against the latest and most sophisticated malware.

4 – Report and share incidents (Pillar 2 and 4)

Finally, the DORA – in a similar manner to the RGPD regulation established a few years ago – imposes a new obligation for financial sector participants: maintain a comprehensive incident register serving as a reliable audit trail in the event of regulatory scrutiny. But not only that, in the event of a major incident, this register will serve as evidence that preventive actions were implemented proactively to ensure the IS’s resistance and overall operational resilience.

At the same time, major incidents must be reported to the supervisory authorities. Beyond the identification of potential risks of propagation, the main aim is to build a knowledge base of cyberattacks, malicious acts, and threats. This knowledge base can then be shared with industry players to identify best practices that can be deployed to limit the impact of such threats.

This clear, easy-to-understand knowledge sharing also applies internally, by establishing a communication framework that can be understood by most employees. It’s important to recognize that operational resilience is everyone’s business. This holds true for key stakeholders such as Executive Management, the Risk Department (often merged with the Business Continuity Department), the Information Systems or Information Systems Security Department, and the Purchasing Department.

Although operational resilience and cyber security remain eminently technical in substance, the consequences of an incident extend well beyond the confines of the company, due to the potential ripple effect. The resilience of information systems and overall corporate resilience have emerged as highly strategic concerns that now find their way into executive committee discussions – even more so since, despite the technical nature of the subject, executives can be held criminally liable. So, better safe than sorry, and prepare for the January 2025 deadline.

In the ever-evolving world of data management, it’s common to hear two titles: Chief Data Officer (CDO) and Chief Information Officer (CIO). While the two roles may seem similar, they have distinct differences. A CDO oversees the management, governance, and utilization of an organization’s data assets.

They ensure data is used effectively and securely throughout the organization and are increasingly critical figures in this age of digital transformation. In contrast, a CIO is responsible for the organization’s overall technology strategy and the implementation and management of information technology systems. While both roles deal with data, the emphasis and scope of responsibility differ, reflecting this approach to data management and technology.

It’s their differences that can have a significant impact on an organization’s overall strategic alignment, budgeting, operations, and return on investment. With an ever-increasing amount of data generated in organizations and tighter regulations regarding data management, it is essential to understand the distinctions between these two roles and the value they bring to the organization.

Understanding these roles is critical in decision-making regarding whom to hire, how to divide responsibilities, and how to prioritize projects, allowing the organization to utilize its data and technology assets for success optimally.

What is a Chief Data Officer?

A Chief Data Officer (CDO) is a senior executive responsible for managing an organization’s data ecosystem. The CDO is responsible for developing and implementing data strategies that align with the organization’s goals. This includes data governance, data management, data analytics, and developing data-related policies and procedures to allow value creation from Data.

The CDO works closely with other senior executives, including the CEO, CIO, and CFO, to ensure data is used effectively throughout the organization. Key responsibilities of the CDO include:

• Identifying data-related risks and opportunities.
• Ensuring compliance with regulatory requirements.
• Make Data more easily accessible to all business & technical users.
• Fostering a culture of data-driven decision-making
• Enable Innovation based on Data (A.I)

CDOs must have a strong understanding of Business strategic needs, objectives for the company, and linked use cases as well as technology, data analysis, and data management practices.

In today’s data-driven economy, CDOs are critical in ensuring organizations leverage their data effectively, manage data-related risks, make informed decisions, and can deliver disruptive innovation (A.I.)

What is a Chief Information Officer?

A Chief Information Officer (CIO) is a high-level executive position within an organization responsible for overseeing the implementation and management of the company’s information technology (IT) systems. The primary role of a CIO is to strategically plan and execute the technology initiatives that help the organization achieve its business goals.

They must also possess a deep understanding of the latest trends in technology and use this knowledge to drive innovation and digital transformation within the organization. In addition to managing the technical aspects of the business, a CIO is also responsible for managing the IT budget and ensuring that technology investments deliver a return on investment.

This requires a keen financial awareness and strong project management and negotiation skills. Overall, the Chief Information Officer plays a critical role in shaping the overall technology strategy of an organization and ensuring that the organization is equipped with the right tools to stay competitive in an ever-changing business landscape.

The Chief Information Officer (CIO) manages an organization’s technological strategies and systems. Their primary responsibility is to ensure that technology is properly aligned with the goals and mission of the company. They must provide technical leadership to the IT department and deliver high-quality technology services. CIO responsibilities include:

• Overseeing the day-to-day IT operations.
• Managing the systems’ security.
• Developing and implementing IT policies.
• Identifying areas of improvement for the technology infrastructure in sync with business & strategic goals for the company.

The CIO is also responsible for staying informed about technological advancements and trends and evaluating how those advancements could benefit the company. A CIO must communicate effectively with other top executives and department heads to ensure that IT-related decisions support and align with the overall business strategy. They coordinate with other executives and department heads to ensure that cross-functional teams work to resolve business issues effectively and efficiently.

An essential responsibility for any CIO is ensuring that the company’s technological infrastructure is scalable and can accommodate growth. This requires them to stay aware of emerging technological trends and develop strategies to implement new technologies. Finally, the CIO must ensure the company complies with relevant data protection and privacy laws.

This includes overseeing data protection policies, risk assessments, disaster recovery, and business continuity planning. Overall, the CIO plays a critical role in ensuring that an organization’s technology infrastructure is secure, cost-effective, efficient, and aligned with the company’s objectives.

How does the Chief Data Officer fit into an organization?

The Chief Data Officer (CDO) is a senior executive overseeing a company’s data strategy, management, and governance. The CDO must collaborate with other executives to ensure data is used effectively to achieve strategic objectives. Their roles typically include:

• Set up the Data Governance Program and the Data Office Team
• Create Data Catalog and Business Glossaries
• Recruit Data Owners for each essential Data
• Creating a data culture with a Data Community
• Developing and implementing data-related strategies.
• Ensuring data quality.
• Managing data risks.
• Ensuring compliance with regulations.
• Enabling Data Self-service and Data Reuse for Business and Technical Stakeholders

The CDO’s responsibilities also include overseeing data security measures, data privacy, and data ethics frameworks within the organization. CDOs fit into the organization by reporting directly to the CEO or COO. As companies become more data-driven, the CDO often works closely with the Chief Information Officer (CIO) and Chief Technology Officer (CTO).

The main goal of the CDO is to drive business growth and deliver value through data initiatives. In some companies, the CDO may also oversee operational functions like creating and managing data architecture and setting up data management systems. The CDO’s role can be highly complex and differs from one organization to another.

However, the CDO must be an excellent communicator with strong leadership and interpersonal skills to work with organizational stakeholders. They must have a deep understanding of business needs, data, and analytics and a keen eye for identifying critical insights from data. They also must stay up-to-date with the latest data-related technologies and emerging data trends. Overall, the CDO is an essential part of an organization that values and utilizes data to improve business outcomes.

How do Chief Data Officers and Chief Information Officers collaborate and integrate?

Chief Data Officers (CDOs) and Chief Information Officers (CIOs) collaborate and integrate to ensure the organization’s data and information infrastructure are aligned. They work together to address strategic and operational concerns, including defining data and information needs, identifying compliance and regulatory requirements, and overseeing data governance practices.

Since they both have different but complementary roles, they establish a common ground to share resources and expertise. CDOs focus on data management, data catalog, business glossaries, data quality, management compliance with data regulations, and analytics. At the same time, CIOs concentrate on technology and infrastructure, including information management, security, and architecture. Together, they ensure they provide the entire organization with the necessary data and information to support the development and implementation of successful business strategies.

The CDO and CIO partnership also ensures that organizations can adapt to new technology and regulatory demands, resulting in accelerated growth and innovation. Their combined efforts streamline digital processes, allowing for better decision-making and data-driven insights. CDOs and CIOs must work closely and keep an open dialogue, ensuring everyone benefits from the partnership.

Chief Data Officers drive change by providing simple access to metadata via data catalog.

Chief Data Officers drive change by providing simple access to data to all company stakeholders.

The Data Catalog is a simple way to allow any user to search and find actual data available in the company – and all the potential linked data that could be used in conjunction to create new value.

This Technical Catalog is built via technical metadata discovery and needs to be enriched with documentation, types, and tags such as “Personal,” “Critical,” “Sensitive,” Financial,” Marketing”,… data.

To be able to create Data Catalogs, the CDO needs help to identify what applications are collecting and how there are processing data.

Not because they need to know what data needs managing intuitively. It’s just that no one has an excellent holistic understanding and record of the flow of data through the organization, the rationale for its capture, and for what purpose. The latter issue is a more recent requirement driven by the need for transparency around the processing of data to comply with data protection legislation.

Why is it important to understand CDOs’ and CIOs’ data perspectives?

Because the resolution of the Chief Data Officer’s challenges will, in turn, resolve the Chief Information Officer’s difficulties in reliably sourcing accurate and trusted data, by providing an inexhaustible supply of valuable data assets, your Chief Information Officer can avoid the frustration of not getting access to the correct data when needed.

You can accelerate your organization’s digital journey by proactively managing the data friction your key stakeholders encounter daily and creating a more accessible and open data architecture to empower data users across the organization.

How can CIOs and CDOs join forces? By focusing on three essential activities:

1. Build Information Roadmaps

Information Roadmaps are the foundation stone of any digital transformation.

• Match your Information Demand to your Data Supply
  Are you managing and governing the correct data to address the organization’s information priorities?
• Build and focus on your Data Supply Chain.
  The technical and organizational frameworks and safeguards, including metadata and data protection by design, to share and deliver sustainable data assets to your stakeholders.

Is it that simple? Well, maybe not, but no matter the industry you work in or the complexity of your organization, these are the most important steps you will take in your journey toward data supremacy because, as the Chief Data Officer, that’s what is expected of you.

Imagine having sustainable, re-usable, high quality, lawful and compliant data at your fingertips with complete transparency about the processing/use of that data.

Imagine the Chief Information Officers’ sigh of relief when the continuous burden of searching, bashing (figuratively speaking), and integrating the same data assets repeatedly is removed.

Their purpose is to free up the CIO, the Digital Transformation team, the Data Scientists, and the Marketers to focus on how data-driven business outcomes produce value. Your purpose is to create the headroom needed to do this and manage the data risks, making these teams effective at creating value for your organization and customers. This blog is about how you can do that.

2. How can data-driven business outcomes produce value for your business?

How do you unlock the information your digital and analytics programs need while at the same time maximizing the opportunity to repurpose the data – and all the while ensuring the secondary uses remain compliant and lawful?

There are ways of achieving this through a collaborative process across the organization using visual representations of your applications, data, strategy, risks, and controls to understand and navigate your organization’s data flows.

The transformation of your organization from a knowledgeable enterprise to an intelligent one begins with two simple questions:

• What is the change you are trying to affect? And,
• What are the metrics/measures by which you will determine if the change has been successful?

Answering these two fundamental questions of your business stakeholders, not just the Chief Information Officer brings focus and purpose to the information demands being asked of you.

And qualifying those requirements to understand what data is needed (breadth and depth), the geographic scope, the security classification of required data, the data protection safeguards (policies) needed, and the priority for delivery frame the prize size and scope of the challenge.

3. Why make assumptions about what data assets are a priority?

Working and collaborating with your stakeholders to develop a rolling information roadmap helps you, the CDO, anticipate and navigate the complexities of the data supply chain to keep the data flowing. Translating this demand into requirements and actionable steps is the next stage, and this is when tooling makes all the difference.

Rationalizing data demand into deliverables that benefit more than one stakeholder is the key to maximizing data value and reducing time to market.

This is when metadata management solutions, supporting the methods and techniques needed to frame the data demand and understand the impact on IT Assets, will cut through the complexities of the data requirements rationalization process.

Whereas a simple spreadsheet may suffice in the short term to collate the requirements, my experience recommends having a metadata management solution in your sights from the start so it can be migrated to the tool more efficiently when the time comes, usually a couple of months into this process. If you are fortunate, you will have this capability established and available.

In advance of and post-GDPR enforcement, several tools have entered the marketplace supporting data management and compliance governance.

Many of these tools address the immediate organizational safeguards and primary data protection legislation compliance requirements, e.g., Servicing DSAR (Data Subject Access Requests), DPIAs, and RTBs (Right to be Forgotten). Still, they must accommodate the governance of requirements, continuously sourcing, preparing, managing, and protecting data assets for secondary processing.

More often than not, this capability needs to be noticed by the tool vendors.

Why is this? Because they have yet to understand the multidimensional challenge of curating data that is Fit-for-Purpose, Accurate, Complete, and Timely to drive Data Science, AI, and Machine Learning.

Understanding, with precision, the right source, quality, and timing of data acquisition for data analytics requires a comprehensive understanding of how data is collected and managed across the business landscape.

It would be best to have a tool that supports business and technical data and architecture definitions.

This will help you document and visualize the connectedness and flow of data.

These touchpoints represent where compliance with the principles of privacy by design is most relevant. At the juncture where applications collect data, people touch data, processes ingest data, and technology processes data, the security and privacy risks of data are greatest.

These pinch points are where the practical application of data protection by design will drive compliance with privacy principles and demonstrate the effectiveness of your organization’s data safeguards.

Connecting all these dimensions – People, Processes, and Technology – to data and information assets is essential for adequate data provenance and Big Data governance, a critical requirement for many regulations, not just the GDPR.

How do new technologies impact the roles of CDOs and CIOs?

New technologies have revolutionized how organizations operate, and their impact on the roles of Chief Data Officers (CDOs) and Chief Information Officers (CIOs) must be addressed.

With digital transformation becoming more prevalent, CDOs have been tasked with aligning data strategy with business goals, driving innovation, and creating value from data.

They manage the organization’s governance, quality, privacy, and data security. Meanwhile, CIOs are responsible for developing and implementing the IT plan, ensuring the technology infrastructure supports the company’s goals, and managing the day-to-day operations of IT systems.

With the advent of Artificial intelligence (AI) and Machine Learning (ML) technologies, the CIO’s role has been expanded to include managing and analyzing big data, enhancing digital security, and creating strategies for using emerging technologies. Overall, new technologies have created new opportunities and challenges for CDOs and CIOs, and these roles are expected to evolve with the increasing rate of innovation.

What is the future outlook for Chief Data Officer and Chief Information Officer positions?

The future outlook for Chief Data Officer (CDO) and Chief Information Officer (CIO) positions is favorable, as these roles continue to grow in importance within organizations. The CDO is responsible for ensuring the quality, security, and accessibility of an organization’s data.

The CIO is in charge of managing IT infrastructure and implementing technology strategies to support business operations. The rise of big data, artificial intelligence, and the Internet of Things has resulted in an exponential growth of data, which has led to an increased need for data governance and management. As a result, CDOs are becoming crucial to modern-day businesses.

Moreover, CIOs are expected to be more strategic in developing technology-focused business strategies that align with organizational goals. The successful integration of technology within an organization will continue to be a key driver of growth in the future. Therefore, the demand for qualified and experienced CDOs and CIOs is predicted to rise in the coming years, making these positions crucial for companies striving to stay competitive and innovative in the digital age.

Summary

After analyzing the differences between Chief Data Officer and Chief Information Officer, it can be concluded that both positions have distinct organizational roles.

While the Chief Information Officer manages technology and information systems to support the company’s business objectives, the Chief Data Officer manages the organization’s data assets.

The CDO is focused on deriving insights from data, creating data policies, quality assurance, and data governance, and designing strategies to maximize data potential for the organization’s benefit.

However, these two positions must work collaboratively for the organization to achieve its goals.

Effective communication, cooperation, and collaboration must be between CDO and CIO to achieve the desired outcome. CIOs must connect with CDOs and see their value and expertise to implement data-driven strategies thoroughly.

At the same time, CDOs must work with CIOs to ensure that data assets are effectively integrated into the organization’s overall technology and information systems.

In summary, CDOs and CIOs have unique roles critical to the business’s success.

Therefore, a collaborative and symbiotic relationship between these professionals is essential for the organization’s success.

Contributor:

Gerry Rankin, formerly Global Head – Privacy Risk Management at Anonos Inc, and former Head of Data Privacy, Security, and Control at HSBC Global Banking & Markets for Big Data and Programme Director of Global Data Sharing for HSBC Group CDO. With 25+ years of cross-industry Data Management and Governance experience, including Financial Services, Manufacturing, Telecoms, Advertising, and Air Express, Gerry has a deep understanding of the challenges organizations are facing to accelerate the commercialization of data that will drive more excellent value for their stakeholders and investors, but also the need to sustain demonstrable and transparent control of data and information in an increasingly regulated data world.

He has led data governance and compliance programs in large and complex organizations to drive greater data agility, helping people to develop and understand the changing regulatory landscape of data privacy risk and how this impacts the long-term digital transformation of their business.

Source: mega.com

In today’s fast-paced and ever-changing business landscape, enterprise architecture (EA) has become a crucial tool for organizations to stay competitive and efficient. By designing and optimizing the structure and processes of an enterprise, EA can help businesses align their goals, resources, and technology to drive innovation and growth.

However, the complexity and scale of modern enterprises often pose significant challenges to EA practitioners. Traditional EA planning and implementation methods may need help to keep up with the speed and diversity of business operations and IT systems. That’s where artificial intelligence (AI) comes in.

As a powerful technology that can automate, analyze, and optimize complex tasks and data, AI can potentially revolutionize the field of EA. By leveraging AI capabilities such as machine learning, natural language processing, and predictive analytics, EA professionals can gain new insights into their organization’s performance, risks, and opportunities. They can also develop more agile and adaptive EA strategies that respond to business environment changes and customer needs.

Innovation: How is AI used in Enterprise Architecture?

Enterprise Architecture is a method of continuously transforming organizations that must constantly adapt to their ecosystem: regulations, customer expectations, new technologies, etc. This collaborative method is based on a knowledge graph that describes the company’s constituents and their interactions and on a software governance tool to frame and orchestrate the transformation while remaining agile.

In the field of EA, classical algorithms are used to perform impact analyses, scenario comparisons, or the analysis of the propagation of incidents within the company’s structure. But as one might imagine, a business is a complex, non-linear system involving many variables. And for such a system, it is difficult to model a priori the equations of its behavior and the rules which govern its evolution.

Artificial intelligence, especially Deep Learning, plays on different levels of abstraction – hence the notion of depth – to extract meaning from data and produce a result while freeing itself from knowing the equations that govern the system.

Here are some fields of application of AI and Deep Learning relevant to EA:

Image recognition

This allows you to photograph drawings to convert them into structured models instantly. Models can be a process, data, application structures, models, computer networks, etc. The conversion of the drawing into a structured model makes it then possible to analyze it, for example, to know that such sensitive data is used within the framework of a given business process.

Linguistic translation

Many companies need to communicate internally in different languages: an official working language supplemented by local languages allowing each linguistic community to contribute to its native language. Instant or batch machine translation works very well to build a multilingual repository and facilitate internal communication and alignment.

Transformation of models

The particularity of any model is that it is not universal. Models are representations of reality designed for a particular use. We must transform the models to produce different views for various services. One may rely on a dual mechanism of formal graph transformation plus artificial intelligence to offer opinions that meet the concerns of multiple users in the company.

Natural Language Processing (NLP)

The (almost) natural language processing techniques are based on the semantic analysis of the question and its approximation to information from the frame of reference [via vector distances, for example – cf. Word2vec]. The provision of results via queries and reports makes it easier for all company employees to consult the data so that they understand its operation and structure and contribute to its transformation.

Data normalization

On the same principle as NLP techniques, data normalization makes reconciling terms and presenting data summaries possible. Typically, scan your IS in search of applications or technologies deployed across the company. The raw data will contain duplicates and variants – name differences, typos, minor versions of software, etc. – or insignificant components that will drown out the valuable information. It is, therefore, necessary to extract a clean, consolidated view, put it into perspective, and classify the management levers of the company.

Metadata and recognition of business patterns

New cloud tools embed more and more metadata, both in the context of big data and computer processing – descriptions of APIs, ETLs, etc. The semantic analysis of these metadata and their reconciliation with the information in the repository – portfolios of the company’s processes, functions, and products – facilitate the connection between the teams in charge of operational management and those in charge of new developments and continuous transformation. It is a crucial contributor to the success of agility on a scale.

Risk analysis of transformation projects

By collecting operational data from projects coupled with architectural data – scale, domain, complexity, ramifications, technologies, the scale of the transformation, timing, and resources … – we can try to predict the risk level of a transformation project. This risk is, of course, different from one company to another and considers many factors, such as that of its project culture, for example. Here, enough data from a company is needed to obtain a relevant signature that characterizes it.

Transforming Enterprise Architecture with AI-Driven Insights: A New Approach to Business Optimization

AI can be applied in various ways to enhance enterprise architecture projects, but the starting phase is particularly crucial. Using AI in starting an enterprise architecture program can have a significant impact compared to traditional methods. Without AI, identifying areas that need improvement in an organization can be time-consuming, resource-intensive, and prone to human error. For instance, manual data analysis may only effectively identify some bottlenecks, leading to developing an enterprise architecture program that must fully address the organization’s needs.

On the other hand, organizations can save time and resources by utilizing AI in the initial stages of developing an enterprise architecture program while gaining more accurate insights.

AI tools can quickly and efficiently analyze large volumes of data to pinpoint areas that require improvement, such as process bottlenecks or areas lacking automation.

By having a more precise understanding of these areas, organizations can develop a more effective enterprise architecture program that is tailored to their specific needs. AI can provide a competitive advantage by enabling organizations to build more efficient and effective enterprise architecture programs.

How Can AI Empower EA Architects in Their Daily Jobs?

AI can significantly assist EA architects in their daily job by providing valuable insights, automating repetitive tasks, and analyzing complex data in real time.

AI can help by delivering EA architects with best practices based on data-driven analysis. By leveraging advanced data analytics techniques, AI can identify patterns and trends that are invisible to the human eye, allowing EA architects to develop more informed and effective strategies.

Furthermore, AI can enable real-time, multi-source data analysis to assist EA architects in making prompt and informed decisions. For instance, in the automotive industry, AI can use advanced NLP to analyze unstructured data, such as vehicle specifications, internal communications, and maintenance logs, to identify key insights and trends.

With this information, EA architects can make informed decisions based on the current state of the business, supply chain trends, and production efficiency. By leveraging AI to analyze internal data sources, automotive companies can develop effective enterprise architecture strategies tailored to their specific needs and optimize their operations for success.

In addition to providing valuable insights, AI can automate repetitive tasks, freeing time for EA architects to focus on more strategic activities. For example, AI-powered chatbots can handle routine inquiries from stakeholders, freeing up EA architects’ time to work on more complex tasks such as designing and implementing new systems and architectures.

AI can also help EA architects generate essential documentation and report more efficiently using advanced natural language processing tools like GPT-3. This NLP tool generates high-quality text that closely resembles human writing, enabling EA architects to automate the report and document creation process.

This saves valuable time and effort, allowing them to focus on more strategic activities and provide excellent value to the business. By integrating AI tools such as GPT-3 into their workflow, EA architects can optimize their productivity, streamline their tasks, and become more effective.

Preventing Enterprise Architecture Failure: How AI Can Help Manage Complexity and Optimize Decision Making

Enterprise architecture projects can fail for various reasons, such as a lack of support from leadership, poor communication between stakeholders, and an inadequate understanding of the business’s needs.

However, one of the most common reasons for EA project failure is the inability to manage complexity effectively. With the rise of big data and increasing business complexity, EA architects face more challenges than ever.

This is where AI can play a significant role in preventing EA project failure. AI-powered tools can help EA architects manage complexity by providing insights and identifying patterns that would be difficult to detect using traditional methods.

For example, AI can help EA architects analyze large volumes of data from different sources and provide valuable insights into business processes and systems.

Moreover, AI can be a valuable asset to EA architects in identifying and anticipating potential issues that may impede project success. For instance, AI can flag potential risks and dependencies impacting project timelines, budgets, or scope. With this knowledge, EA architects can more effectively manage risk and prevent project failure.

Beyond risk management, AI can also enhance the decision-making process for EA architects. By providing timely and accurate insights, AI can help EA architects make informed decisions more efficiently.

With AI-powered tools, EA architects can evaluate various scenarios and predict their impact on the organization. EA architects can reduce the risk of poor decision-making by making decisions based on data-driven analysis rather than intuition alone.

Leveraging AI Techniques for Enhanced Enterprise Architecture Tools

Enterprise architects can leverage the power of AI techniques to enhance their tools and gain valuable insights into their organization’s architecture.

One such technique is neural graph networks (GNN), which can help EA architects analyze complex data and identify patterns and relationships between systems and processes. By leveraging GNN, EA architects can better understand the enterprise’s architecture and optimize its performance.

Machine learning (ML) recommendation systems can be a powerful tool for EA architects to make informed decisions confidently. By analyzing large volumes of data, ML recommendation systems can classify and recommend the best course of action based on current business needs and performance metrics.

The system can provide a confidence rate with each recommendation, enabling EA architects to evaluate the risk associated with each decision and make informed choices.

Strategy to Envision the Future of AI at the Service of Enterprise Architecture

It should be promising! As we can see from the examples mentioned above, Enterprise Architecture is not immune to the attractiveness of AI’s potential. We will see developments in its usage in the years to come. We are working on its application to the most difficult challenges for companies: continuous transformation and the design of the future-proof enterprise. But this requires a powerful representation (digital twin) of the company and large volumes of data, two drivers for new types of solutions.

We are also working on solutions to identify transformation opportunities and recommend transformation scenarios. For example, the identification and recommendations of migration strategies to the Cloud … To be continued!

Final thoughts on AI’s role in enterprise architecture

In conclusion, integrating AI in enterprise architecture can transform this critical field by providing valuable insights, enhancing decision-making, and improving the enterprise’s overall performance. However, addressing AI ethics, security, transparency, and explainability concerns is essential to ensure that AI is used responsibly and effectively.

By leveraging AI techniques such as graph deep learning, advanced NLP and language understanding, ML recommendation systems, image recognition, and pattern recognition, EA architects can optimize the enterprise’s architecture, reduce risk, and increase the chances of project success.

Ultimately, integrating AI in enterprise architecture is not a replacement for human expertise but rather an enhancement, providing EA architects with powerful tools to deliver value to the business more efficiently and effectively.

Challenges

How the Atomic Weapons Establishment uses Enterprise Architecture to understand its IT Estate AWE plays a crucial role in the UK’s national defense. The organization has been at the forefront of the country’s nuclear defense program for over 60 years and supports the ‘Continuous At Sea Deterrence program’ and national nuclear security.

Supporting all of this work is a large complex IT estate of wide and varied systems and applications. Because of this, the need arose to move from PowerPoint and paper-based solution design into an IT modelling solution where dependencies and relationships are more explicit.

The main driver of the project was to understand the cost of IT software and applications, how IT is utilized across the business and when technology needed to be refreshed. With so many solutions, vendors and applications to map, diagrams and modelling were the most logical fit or this and represent the best approach to the goal of full business visibility into how everything fit together.

IT Portfolio Management meets architecture

AWE decided to look for a software that will support them to answer many overlapping questions:

• Understand cost of IT and how it is used across the organization
• Providing a systematic modelling approach to capture design information
• Advanced awareness and planning for technology lifecycles and obsolescence
• Reduce costs through efficiency and avoiding technology duplications and redundancies
• More efficient regulatory compliance and audit preparation

They have selected the HOPEX platform for its strong IT portfolio management and architecture capabilities.

The IT portfolio management provides the platform to provide full inventories of all systems, applications and software indicating dependencies, relationships, vendor support information and costs.

Architecture provides the platform to enable model-based designs of how the inventory of “stuff” needs to be deployed, enriching the lists developed as part of applications and technology portfolio management activities.

Better understanding of the IT estate thanks to a complete overview

Clear deliverables have been produced that are shared with various stakeholders across the organization in graphical form.

The outcomes of the project that have better enabled AWE to understand its IT estate are as follows:

• A managed central repository of IT estate information providing key information for decision-making and awareness
• Clear understanding of the relationship between systems, applications and software, and how all of this supports the business
• Software obsolescence roadmaps to enable improved forward planning
• Required reporting available “out of the box” reducing time to publishing the information

About Atomic Weapons Establishment (AWE)

Atomic Weapons Establishment’s role in keeping the UK safe is to manufacture, maintain and develop the warheads for Trident, the country’s ultimate deterrent, and use its unique skills and expertise to support nuclear threat reduction. The organization operates from four sites across the UK and has some of the most advanced research, design and production facilities in the world.

Process modeling in today’s business psyche is almost always driven by process automation or robotization. This is a natural and laudable objective, but it should not overshadow the fact that process modeling is the first and foremost prerequisite to business transformation. Process modeling, in essence, helps design an organization’s operating model by defining the most efficient processes to deliver a product or a service to customers. Therefore, business Process Modeling (BPM) drivers are much more varied and complex than automation alone. But above all, this practice requires the regular monitoring of the models themselves to adapt to an ever-changing ecosystem.

Operational excellence and digital transformation: the real fundamentals of BPM

Business Process Modeling – or Business Process Modeling & Notation (BPMN) – is a standard methodology using graphical forms to represent business processes, enabling organizations to design their value chains. But not only that:  like an “X-ray,” process modeling identifies strengths, weaknesses, critical or subsidiary processes in the business model, and potential candidates for automation.

If this methodology is often linked to an automation project, other drivers can lead to BPM initiatives. These include the digitization of business processes – as illustrated recently, due to the pandemic, by the shift from physical outlets to online sales. A graphical representation (diagram) of a process helps significantly with its understanding and performance analysis and facilitates the whole digitization process. Identifying the process sequences that can be improved to achieve operational excellence and optimization is also essential. These two objectives alone account for nearly 60% of BPM projects.

Business Process Modeling facilitates process standardization depending on the organization’s size, activity, business area, or competitive environment. It fosters the communication and implementation of the optimal process regarding operational efficiency within the organization. This is common among fast-food companies that want to offer their customers the same quality and service regardless of location.

Compliance, risk management, and resilience: natural drivers for BPM

While compliance has long been a secondary driver of BPM, this trend has reversed recently in a globalized and interdependent economy that is putting more and more risks on businesses. It has even become the primary driver for 30% of companies. This is particularly true in highly regulated financial services and healthcare industries.

New players such as Neobanks also feel the pressure; after having shaken up the traditional players, some have been called to order by Regulators to model their processes to prove that they were in “control” of their operations and had all the regulatory procedures in place to comply with applicable regulations, which was not always the case.

Resilience is also an area where BPM can be a game changer for organizations operating in an increasingly digitalized world, as it highlights the IT dependencies necessary for proper process execution. This is a crucial step when implementing a business continuity strategy, as it facilitates the revert to “degraded” processes in the event of disruptions to support operating at a minimum condition.

In the same way, process modeling enables the rapid identification of operational interconnections within the organization in the context of risk management. This method facilitates impact analyses and the anticipation of domino effects on the company’s value chain due to endogenous or exogenous events: cyber-attacks, pandemics and lockdowns, geopolitical tensions, increased energy costs, etc.

Process modeling: a forecasting exercise

Although processes define how an organization operates, they are not static but constantly evolving. This implies regular monitoring of possible variances and deviations between the modeled version of the process (the reference) and its application “in the field” to analyze the potential impacts on performance. Specifically, BPM is an iterative approach that must be regularly questioned according to a rhythm specific to each company. This is the role of the process owners, who are responsible for the efficiency and quality of their processes.

Process modeling is also a forecasting exercise that requires intelligence and analysis, which must lead organizations to question the possibilities for improvement to gain efficiency, competitiveness, and quality and anticipate the consequences of future regulations (compliance) or to prevent the occurrence of specific risks.

With increasing crises and extreme technological, economic, and social changes, process modeling constitutes more than ever a “life insurance” for organizations, essential to their agility, security, efficiency, and, ultimately, their resilience.

About the author

Cyril Amblard-Ladurantie is a Senior Product Marketing Manager for GRC (Governance, Risk & Compliance) and BPA (Business Process Analysis) at MEGA International with more than 17 years of experience focusing on GRC technology. Before joining MEGA International, he was a manager at a major Advisory firm (EY), focusing on advising clients on their digital GRC journey, coordinating implementation projects, and providing project management expertise. Before his experience at EY, Cyril held consulting and pre-sales positions at a significant international GRC and regulatory intelligence provider (****).

Source: mega.com