ICT301: Enterprise Architecture Analysis Report for Chubb Organization

This report provides a comprehensive analysis of the Enterprise Architecture (EA) implemented at the Chubb organization. It begins with an introduction to EA and its importance in aligning business goals with IT infrastructure, highlighting its role in improving decision-making and data organization. The report then delves into a case study of Chubb, an insurance company, detailing its transition to a federated model and the components of its new EA model, including target architecture and EA practice. It explores how Chubb's EA framework evolved, comparing the centralized architecture implemented in 2012 with the EA3 framework. The report outlines the benefits of EA for Chubb, such as improved IT operations and strategic alignment. The report also includes the comparison of EA framework with EA3 framework, and concludes by discussing the advantages of the EA framework implemented by Chubb. Finally, it references various sources to support the analysis.

Running head: ENTERPRISE ARCHITECTURE
Enterprise Architecture
Name of Student-
Name of University-
Author’s Note-

1ENTERPRISE ARCHITECTURE
Introduction
Enterprise architecture (EA) in an organization helps to meet the business problem of the
organization in future (Kerlin 2017). EA helps in building organization stability and fulfill the
goal of an organization. EA includes different abstraction layer that forms complete as well as
common information view along with guidance and direction to achieve the goals. EA helps to
improve the decision based activities. EA helps to organize the digital data and reduces the
complexity of data organization (Upward and Jones 2016). This helps in establishing the process
of solid technology and helps in ensuring that technology is used across the functional areas and
business units in the organization.
This report explains the need of EA within an organization. The organization that is taken
in this report includes Chubb organization. This report explains the working environment of
Chubb organization and the way EA has changed its working process. This report also compares
the EA framework with EA3. Chubb organization has encountered many advantages with the
implementation of EA in its business. Those advantages are explained in this report and a
conclusion stating either EA framework or EA3 framework is more appropriate is explained in
this report. This report details the EA framework and the EA3 that can be implemented in
organizations.
Case Description
The organization that is taken in this report is an insurance company and provides
casualty products of insurance as well as services to different businesses and individuals. Chubb
changed its working process model to a federated model. The components that are included in
the new EA model of Chubb is target architecture and Enterprise architecture practice. Target

2ENTERPRISE ARCHITECTURE
architecture in EA model include architecture principles, governance, reference architectures, as
well as emerging technologies that helps in maximizing the integration plan for the organization.
The EA practice that is changed in Chubb mainly includes five domain: Platform architecture,
technical information, application and IT Strategy and Governance. With the new architecture
that Chubb has implemented, the organization has become more capable of handling the demand
management and handling the leadership development in the organization.
The EA that was designed for Chubb organization was comprehensive, mature as well as
well-developed. But with involvement of new technologies in the business structure, and having
demand from Chubb to provide detailed and better information and pressure to be more efficient
and have new innovate have resulted to re-evaluate as well as redesign role of EA and IT
function in the organization (Jallow et al. 2017). The organization changed and redesigned its EA
framework in 2012 which was created through centralized mechanism so that the IT solutions
can be integrated. Chubb considered EA to be the crown jewel for the organization and thinks
that when EA is right, all other business process will run correctly and efficiently in the
organization.
Architecture in case
The new architecture for Chubb was designed in the year 2012. The new architecture that
was built included strong architecture function having comprehensive strategy, governance,
standards, as well as the key enterprise assets as well as solutions. But with this architecture,
standards were difficult to enforce (Chofreh, Goni and Klemeš 2018). The management of
Chubb needed to rationalize the existing technologies and the enterprise applications so that
consolidated plan can be developed for the organization. After the evaluation, new centralized

3ENTERPRISE ARCHITECTURE
architecture was created Knight in 2012. Knight added resource manager in the new architecture
so that to develop the architecture skills and deploy them in the framework.
The EA framework of Chubb also included EA Practice for managing the architects on
daily basis. With the implementation of EA practice in the new architecture helped Chubb to
develop relationship with all stakeholders in the hierarchical chain and with the organization’s
stakeholders (Vargas et al. 2016). The architecture domain of the organization was divided in
four parts in EA department: Platform architecture, information architecture, technical
architecture, and application architecture. In 2014, another technical lead was appointed to have
a clear and single aim of architect and EA practice. The new redesigned and centralized EA
function had a broad scope and helps to enforce the standards and principles in the organization.
The architecture included EA practice and Target architecture.
The target architecture that was developed for the organization helped to articulate the
present enterprise architecture and the target architecture that was envisioned. Current EA
includes set of systems as well as processes including the business capabilities as well as
technical capabilities as EA point of view (Anbarasan 2018). The target architecture include high
level vision that helps in showing business goals as well as the IT solution in future. The target
architecture of the new EA was divided in four different parts: Architecture Principles,
architecture governance, conceptual or reference architectures and the emerging technology
included in the enterprise. For developing the new EA model for the company, the employees
needed both internal skills as well as external skills. The target architecture of Chubb included
different domains and responsibilities of maintaining different domains were given to different
teams.
Comparison of framework

4ENTERPRISE ARCHITECTURE
The analysis of EA and the documentation process of EA is mainly accomplished with
EA implementation methodology of EA and includes mainly six areas: the framework, present
and future architectural views, the components that are included in the framework, a detailed
plan that can manage the ongoing transition of the views and vertical threads effecting
architecture at all levels (Casturi and Sunderraman 2019). With the EA framework,
documentation as well as analysis are standardized and the organization can get hierarchical
view of its working architecture with integrated strategy, technology perspective, and from
business perspective.
EA Cube Framework was introduced in 2004 and has more minute and acute details
compared to EA framework. There are more number of features included in EA Cube framework
and this framework is built on different hierarchies. Hierarchies in EA Cube framework helps to
avoid the Sub- architectures. The business goals in an organization defines the way Enterprise
Architecture can be designed (Shad et al. 2019). EA Cube mainly includes the primary function
for organizing and includes planning of the IT resources as well as documentation included in
EA. This Framework includes five layers; Goals/ Initiatives, Products/ Services, Data/
Information, System/ Architecture, and Network/ Infrastructure. There is also Lines of Business
that states particular activity in the organization and includes five layers architecture.
Conclusion
EA include many benefits in Chubb Organization like providing insights as well as
overview of the organization structure. The EA architecture also helps in determining the
dependencies between the applications and the processes included in the organization. The
benefits that EA had on Chubb Organization are:

5ENTERPRISE ARCHITECTURE
1. EA helped the organization to have a simplified enterprise with working process.
2. EA helped to align the technology operation of the business to satisfy the goal of the
organization.
3. This also helped to align the components of the organization to strategy.
4. With the implementation of centralized EA framework in Chubb, the IT operation
improved.
5. This framework helps to have effective management and information exploitation with
help of IT.
6. EA helped the organization to return on the existing plan and that has enabled the
organization to have reduced the risks in their future investments.
As the centralized EA framework that was re-designed in the organization helped to
mature the ongoing EA that was already existing the organization. New EA underscores EA
evolution and helped in increasing the IT functions delivered by the organization. The IT
function that is developed in the organization can be considered as strategic heart and are
considered as simple manufacture of the systems.
As the working environment of Chubb already has an EA framework, the best framework
that could have been implemented from the existing model is improving the EA model that was
able to accomplish the changeable goals, the resources, standards as well as processes that are
included in the organization. For implementing EA cube framework in the working environment,
the architecture was to be changed totally. The EA framework that was included in Chubb helps
the organization transform legacy of all fragmented applications, the processes included as well

6ENTERPRISE ARCHITECTURE
as the organizational structure of the company. The manual as well as automated process of the
environment were integrated using the EA framework.

7ENTERPRISE ARCHITECTURE
References
Anbarasan, P., 2018. Stakeholder engagement in sustainable enterprise: Evolving a conceptual
framework, and a case study of ITC. Business Strategy and the Environment, 27(3), pp.282-299.
Chofreh, A.G., Goni, F.A. and Klemeš, J.J., 2018. Sustainable enterprise resource planning
systems implementation: A framework development. Journal of cleaner production, 198,
pp.1345-1354.
Jallow, A.K., Demian, P., Anumba, C.J. and Baldwin, A.N., 2017. An enterprise architecture
framework for electronic requirements information management. International Journal of
Information Management, 37(5), pp.455-472.
Kerlin, J., 2017. Conclusion: Revising the Macro-Institutional Social Enterprise
Framework'. Shaping social enterprise: understanding institutional context and influence, by
Janelle Kerlin, pp.277-305.
Kerlin, J.A. ed., 2017. Shaping social enterprise: Understanding institutional context and
influence. Emerald Group Publishing.
Peng, G., Privette, J.L., Tilmes, C., Bristol, S., Maycock, T., Bates, J.J., Hausman, S., Brown, O.
and Kearns, E.J., 2018. A conceptual enterprise framework for managing scientific data
stewardship.
Shad, M.K., Lai, F.W., Fatt, C.L., Klemeš, J.J. and Bokhari, A., 2019. Integrating sustainability
reporting into enterprise risk management and its relationship with business performance: A
conceptual framework. Journal of Cleaner production, 208, pp.415-425.

8ENTERPRISE ARCHITECTURE
Upward, A. and Jones, P., 2016. An ontology for strongly sustainable business models: Defining
an enterprise framework compatible with natural and social science. Organization &
Environment, 29(1), pp.97-123.
Vargas, A., Cuenca, L., Boza, A., Sacala, I. and Moisescu, M., 2016. Towards the development
of the framework for inter sensing enterprise architecture. Journal of Intelligent
Manufacturing, 27(1), pp.55-72.
Casturi, R. and Sunderraman, R., 2019, March. Enterprise Framework for Business Intelligence
Tools on Cloud Computing Environment for Investment Platforms. In Proceedings of the 9th
International Conference on Information Systems and Technologies (pp. 1-7).