We like to think of enterprise architecture (EA) as system engineering for the enterprise. Sources differ on the definition of EA:

ISO/IEC 42010: 2007  defines ‘‘architecture’’ as: ‘‘the fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.’’

TOGAF® defines the term Architecture as having two meanings depending upon the context:

• A formal description of a system or a detailed plan of the system at component level to guide its implementation.
• The structure of components, their inter-relationships and the principles and guidelines governing their design and evolution over time.

Wikipedia  sum EA up in the following way:

“To some, 'enterprise architecture' refers either to the structure of a business, or the documents and diagrams that describe that structure. To others, 'enterprise architecture' refers to the business methods that seek to understand and document that structure. A third use of 'enterprise architecture' is a reference to a business team that uses EA methods to produce architectural descriptions of the structure of an enterprise.“

Our experienced EA practitioners are TOGAF 9 certified and generally use the framework when assisting customers with EA.

Below is an extract from TOGAF 9.1 Introduction Chapter addressing the need for EA:

Why do I need an enterprise architecture?

The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.

Today's CEOs know that the effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage. An enterprise architecture addresses this need, by providing a strategic context for the evolution of the IT system in response to the constantly changing needs of the business environment.

Furthermore, a good enterprise architecture enables you to achieve the right balance between IT efficiency and business innovation. It allows individual business units to innovate safely in their pursuit of competitive advantage. At the same time, it ensures the needs of the organization for an integrated IT strategy are met, permitting the closest possible synergy across the extended enterprise.

The advantages that result from a good enterprise architecture bring important business benefits, which are clearly visible in the net profit or loss of a company or organization:

• A more efficient business operation:
  • Lower business operation costs
  • More agile organization
  • Business capabilities shared across the organization
  • Lower change management costs
  • More flexible workforce
  • Improved business productivity
• A more efficient IT operation:
  • Lower software development, support, and maintenance costs
  • Increased portability of applications
  • Improved interoperability and easier system and network management
  • Improved ability to address critical enterprise-wide issues like security
  • Easier upgrade and exchange of system components
• Better return on existing investment, reduced risk for future investment:
  • Reduced complexity in the business and IT
  • Maximum return on investment in existing business and IT infrastructure
  • The flexibility to make, buy, or out-source business and IT solutions
  • Reduced risk overall in new investments and their cost of ownership
• Faster, simpler, and cheaper procurement:
• Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan
• The procurement process is faster - maximizing procurement speed and flexibility without sacrificing architectural coherence
• The ability to procure heterogeneous, multi-vendor open systems
• The ability to secure more economic capabilities

A strong system engineering approach is key to the success of any product. We take clients through the engineering lifecycle to ensure that requirements are well understood and the solution integrates well within the customer environment. We then assist client to manage the design, acquisition and manufacturing process to ensure that requirements are constantly interrogated.

The value of systems engineering is supported by accountability offices internationally. Quoting from a 2012 report (link to http://www.gao.gov/assets/590/589695.pdf) on defence acquisition by the United States Government Accountability Office, "Systems engineering is the primary means for determining whether and how the challenge posed by a program’s requirements can be met with available resources. It is a disciplined learning process that translates capability requirements into specific design features and thus identifies key risks to be resolved. Our prior best practices work has indicated that if detailed systems engineering is done before the start of product development, the program can resolve these risks through trade-offs and additional investments, ensuring that risks have been sufficiently retired or that they are clearly understood and adequately resourced if they are being carried forward.”

SE planning, as documented in an Systems Engineering Plan (SEP), identifies the most effective and efficient path to deliver a capability, from identifying user needs and concepts through delivery and sustainment. SE event-driven technical reviews and audits assess program maturity and determine the status of the technical risks associated with cost, schedule and performance goals.

Additional SE benefits are that it:

• Supports development of realistic and achievable program performance, schedule and cost goals as documented in the Joint Capabilities Integration and Development System (JCIDS) documents, Acquisition Program Baseline (APB) and Acquisition Strategy (AS).
• Provides the end-to-end, integrated perspective of the technical activities and processes across the system life cycle, including how the system fits into a larger system of systems (SoS) construct.
• Emphasizes the use of integrated, consistent and repeatable processes to reduce risk while maturing and managing the technical baseline. The final product baseline forms the basis for production, sustainment, future changes and upgrades.
• Provides insight into system life-cycle resource requirements and impacts on human health and the environment.

Our qualitied system engineers are available to assist you throughout the acquisition process. We adapt system engineering principles to ensure that even smaller projects meet or exceed the requirement of the customer.