EAMS is an powerful communication tool since it allows communication across the organization, regardless the stakeholder´s background and domain of expertise.
EAMS blueprints fill the gap that exists between the Enterprise Architecture languages (e.g. Archimate, BPMN, UML, IDEF, and so on) and the natural language. In fact, on one hand, Enterprise Architecture languages are suitable to express design constraints and ensure coherence but are too complex and known only by a few within organizations, and thus unable to support a wider enterprise communication, on the other hand, natural languages are widely well known but too fuzzy to sustain the structured and coherency one needs to communicate Architecture.
EAMS blueprints solve this dilemma because they are both understandable by everyone in the organization and at the same time they ensure the fundamental constraints that are relevant for architecture coherence. Such constraints are imbedded in EAMS core blueprints: organic, context, structure and integration, that can be used to understand the architecture of any concept, any instance of a concept or any set of instances. These blueprints have its roots in the General System Theory, as presented in EAMS early publication (click here). Upon such core blueprints, many others can be built, as for example the Layered Blueprint presented in the Cartography section.
EAMS blueprints are interactive, and one can navigate through them by clicking in blueprints artifacts. Navigation between blueprints can be configured according to the user profile. One can also establish also the level of detail of the architectural representations and the which are the most adequate:
|Representation types||Graphical Interfaces||Media|
|Blueprints||EAMS Application||PowerPoint Reports|
|Charts||EAMS Web||Excel Files|
|Data grids||Word Files|