Understand
The problem
Enterprise Architectures (EAs) contain all the internal and external aspects of your organization, including all the "Ws", like what you do, why you do it, how you do it, who you need to do it, etc. EAs not only represent your current state but also allow you to visualize a desirable future and communicate to others the rationale for change.
Over the years, we found that companies usually face issues like:
Much time is spent re-discovering current state instead of working on addressing their issues.
Documentation is outdated soon after projects are over.
Structured information is disconnected from diagrams.
Changes do not propagate through all the disconnected documents.
Artifacts show business viewpoints rather poorly.
Many important links among People, Process and Technology are not evident.
It is difficult to have a holistic view of the characteristics and life cycle status of all the moving parts required to run the organization.
It is difficult to visualize the full impact of change, which underestimates risks and complexity of projects, and usually leads to overruns in cost and time, or in harsh reductions in scope to meet budgets.
Our approach
Many organizations came to the realization that the only way to address these problems is to implement and maintain an Enterprise Architecture Repository (EAR), to centrally manage the information about their organizations.
They quickly become aware that doing this requires heavy lifting in four areas:
Defining and naming the entities, relationships, and attributes (usually called the "EAR metamodel") and agreeing on the required classifiers and their valid options.
Capturing, cleansing, normalizing, and summarizing large amounts of information, to be able to present calls to action using perspectives that are relevant to many different audiences.
Creating and embedding solid processes to maintain the currency of the EAR, recognizing that organizations are in constant evolution and that decisions need relatively current information.
Accepting that it is not possible to capture and maintain everything from day one, that the footprint of the EAR will be expanded, and that its content details will increase over time.
Libra’s unique Enterprise Architecture Repository (EAR) Managed Services is a unique combination of proven methodologies, experienced talent, and practical tools that effectively address these four requirements.
Preparation
Advice on where to start and how to evolve your EAR.
Definition of the Enterprise Architecture Metamodel (all element types, attributes, and relationships) required to represent your company’s Operational, Motivational, and Transformational domains.
Provision of a cloud-based, SOC-2 Type 2 Enterprise Architecture Repository based on Ardoq.
SSO based on a connection to your Microsoft Active Directory.
No limitation imposed on the number of Applications, Interfaces, Technologies, Vendors, Organization Units, Business Roles, People, Companies, Products, Capabilities, Processes, Strategies, Projects, Risks, Contracts, Rights, etc.
Definition of the Application, Technologies, Information, and Capability reference models and all other classifiers that may be required.
Ongoing
Data Capture through interviews and existing documents.
Alignment with your internal processes to keep information current.
Preparation and administration of surveys to maintain data currency and enhance data quality.
Data cleansing, de-duplication, renaming, and preparation for upload.
Manual data entries and data extractions.
Preparation of dashboards, reports, and presentations.
Ongoing Data Quality Management.
Data backups and restores.
Cadence meetings to understand upcoming needs and ensure satisfaction.
