In our vision, Enterprise Architecture is instrumental in supporting organizational transformation, by increasing agility, so organizations can change smoother, faster and be more cost-effective.
EAMS allows for better planning capabilities by enabling organizations to have a representation of the AS-IS and the foreseen TO-BE, that results from on-going and planned change initiatives.
EAMS is focused on representing the organization Architecture’s past, present and future states, in a way that all stakeholders can understand. Future architecture states are achieved by consolidating what each stakeholder is planning, into unified architectural views.
Thus EAMS is all about time, enterprise cartography and changes.
EAMS is a new kind of EA tool, which collects and manages information from one or various sources and presents it in a comprehensible time based visual formats.
EAMS IS BOTH:
An Information Aggregator
A Powerful Visualizer
An information aggregator with connectors for the main Business and IT applications and catalogs (EA, BI e CMDB…)
An organization’s enterprise architecture solution should always be transversely implemented across the organizational landscape, functioning as a centralized corporate repository (physical or virtual) of the information contained in other existing systems.
EAMS provides a framework, connectors and integration mechanisms that combine and conciliate the information exchange between the architecture repository and other applications, thus promoting a single integrated and consolidate view of the data gathered from the various repositories and catalogs.
A powerful visualizer mapping information in relevant contexts establishing cartographical reference of all relevant information and adding a powerful feature for time navigation on the architectural blueprints.
Unlike most EA tools, EAMS is not oriented towards modeling activities. Every diagram modeled by a user, has to be manually conciliated, maintained and versioned, which leads to a chaotic operational scenario with substantial complexity requiring considerable amounts of efforts, driving the Enterprise Architecture initiative into the ground. Instead, EAMS is based in automation mechanisms that, supported only by repository data, can generate the architectural artifacts necessary to sustain the EA planning, operation and management.
Such allows the users to explore and navigate in time (anticipate) in a seamless manner through architectural views of past, current and target scenarios.
All of this converges into an easy to use communication tool that was built not only for technical profiles, but also for all other stakeholders involved in EA initiatives.