---

Principles

As for applying Architecture discipline to the Enterprise, it’s about considering the overall entity, its purpose, and its implantation in the environment.
Then, it’s also about considering its heterogeneity and its dynamics.

The conceiving work starts by identifying and integrating the needs and the constraints.
Constraints, in architecture, does not mean pain-points. It means considerations that guide the architect in his creative work.
The principle consists of identifying criteria and their relevancy in terms of shaping.

Another point is that shaping happens at scale.
e.g., when conceiving a hospital, you don’t start by a sole care room.
From overall to detailed levels, shaping involves different scales and granularities. [“Scale” in Enterprise Architecture]
Architecture starts by defining main axes of shaping which will constitute generic criteria for further and more detailed shaping (i.e., this is what makes the
scheme scalable and adaptable).

Yet another point is that Architecture can integrate it all because it does not shape from a viewpoint, a particular focus or any specific concern.
Here’s the thing, a built isn’t made of views, isn’t an assembly of views. Views are used to illustrate a conceived built.
Architecture addresses the Enterprise constitutively. This is how and why Enterprise Architecture can address the Enterprise as a whole.
In fact, this is by shaping the whole, constitutively, that you can fulfil respective concerns.

Another point is that Architecture is about shaping space.
The principle is to define the different spaces needed and dedicated to the different activities.
The difference with building architecture is that the space size is limitless.
The interest being the assignation of the space. It also means that Architecture is not about modeling activities but shaping their dedicated spaces.
Components exists as such, within space, and not through their links representing their usages.
And this is the first key point to introduce adaptability.

In summary, while current practices are stuck in modeling, at a detailed level, professional Architecture (building) shapes space and provides an environment for modeled activities. That environment, being shaped, already integrates the relevant generic criteria in order to assure overall coherence.
This is what introduce stability.

Relevancy

Overall, thanks to its original approach, EXCOGITEA_® allows to address concerns and brings concepts which are overlooked, ignored or even unknown by current practices, and which yet are key, foundational.

Shaping the Enterprise as a whole is foundational.
Current practices consider more specific scopes and sub-domains (BDAT, security, …), but, unless the whole is shaped, their real boundaries, and their real correlations, cannot be known.

Considering scales (natural in building architecture discipline) is key.
It allows to manage granularities, of constituents and stakeholders sights and scopes.
Besides, in terms of designing, it can be used to address genericity and modularity. This is also what makes correlations, from overall coherence to diversity of specificity.

Whether items are static or dynamic, EXCOGITEA_® brings a constitutive approach.
It considers items not only because of their usage but regarding their existence, their nature.
In that sense, it is also viewpoints–agnostic. E.g.: a data/information can be seen through a business viewpoint, a technical viewpoint, a legal viewpoint.
While current practices deal with separated canvas (Business model, Operating model, Capability map, …) and wander what can be the correlations, EXCOGITEA_® addresses the shaping of the built, per say. And a built isn’t an assembly of views. Views are derived from the built.

Instead of anticipating a resulting mesh, EXCOGITEA_® shapes spaces, purposely. [Enterprise … purposely Architecture]
Correlations are defined at generic level, through shaped spaces. Links between components can be created and modified at will, upon needs.
This is what makes the scheme adaptable.

Besides, EXCOGITEA_® is aligned with COBIT^® Principles. Not only for IT though, but furthermore extended to the whole Enterprise:

And even more, thanks to its original approach, EXCOGITEA_® goes way beyond “a single framework” and provides “a single built”.
It relegates frameworks to cogitation tools.
It means that it lowers and even eliminates the risk for Organisations of having to choose “the right one” to adopt/adapt.

Benefits

ECOGITEA_® is granting Companies a consciousness of their built.
Besides the building activities considerations, ECOGITEA_® allows to evaluate Operational Excellence and trigger Enterprise optimization.
Furthermore than the operational sight, EXCOGITEA_® covers tactical and strategic sights, which at some point are visions of the built in time.
EXCOGITEA_® provides realistic and accurate view of the built which integrates all required criteria (in terms of impact, feasibility, costs, …) to support decision-making.

EXCOGITEA_® re-gives sense to Enterprise Architecture.
Its original approach allows to brings what’s missing to current practices and it allows to frame them when needed.
EXCOGITEA_® constitutes a foundational context, a cradle for existing related disciplines. Therefore, the principle isn’t to deny them, but to support them.

E.g.: