Enterprise Architecture Database ‘Digital Twin’ is a light-weight tool that maps the business capabilities and links them to the underlying technology portfolios. Lack of central repository of applications, infrastructure technologies and relationship to the business capabilities /processes affects focused IT investments. Often this knowledge is incomplete, undocumented and dispersed in the minds of many people. EADB excels in its approach to rearchitecting the County for digital transformation, enhance visibility and align County’s business strategy to strategic technology planning.
To simplify the complexity and avoid building a large and expensive configuration management database, EADB organizes the application components supporting a business capability into a business solution. Business solution is associated with the specific underpinning infrastructure elements. Changes to the technology components are detected with automated scanning tools and workflows notify responsible owners. Applications (with disaster recovery plan and roadmap), data objects (indicating System of record or replication, transformation or aggregation), infrastructure elements (with life cycle planning and roadmap) and unstructured documents (with tagging and search) are all interconnected and maintained within EADB intuitive UI. Applications and Technology components are categorized into Technical domains that align with Gartner Magic Quadrant.
Technical features of the application focused on cloud computing building the application using Azure platform (Cosmos DB, Azure Search, Azure Application Service).
This tool provides us with insights and helps us to both create our business-aligned IT investment strategy, as well as address some operational problems like technology lifecycle planning and setting the right support and operating models.
EADB Helps in answering important questions:
Who is the business owner of a particular business?
Who are the technical owners of the technologies underpinning the business capability?
What are the best opportunities for synergies and de-duplication in our technology portfolios?
What emerging technologies are relevant for us?
Where are our identity stores?
Where are the unstructured documents related to a business or technology portfolios?
What is our virtualization and cloud adaptation rate?
Where is the design and operational documents of our systems?
What disruptors, opportunities, and strategy are associated with a business capability?
What are the technologies that support a particular business capability?
How much do we spend operating the technologies for a particular business capability?
What business capability would be impacted if a technology component to e changed?
Where do we have sensitive information?
What happens to business capabilities when a technology component fails?
What critical business capabilities are supported by low quality or aging technology?
What are the redundancies in our business, application, and infrastructure portfolios?
What is the age/quality/mobile enablement/ profiles of our systems?
What are 3-year technology roadmaps and how to do they support the business strategy?
What is the measurable impact of a specific IT investment?
- Application Roadmap: Roadmap for each application is a time-dependent function
- Technology Roadmap: Alternative solutions for a given Technology Area
- Maturity Model: Report on the lifecycle KPIs for a particular technology model
- Heat Map: Business capabilities dependent on unsupported technologies
- Virtualization: Aggregate report on on-prem and cloud adaptation
- Database by Model: Aggregate report on various databases in use
- Server OS by Mode: Various servers and operation system models in use
- Directory Services: Identifies identity stores used in the organization
- Development Framework: Aggregate view of all development environments
- Orphan Elements: Any technology/application component who is not part of a solution.
- Capabilities & Owners: Capabilities (Business and IT) and their organizational owners