Architecture Home
Architecture models based on my experience. If you'd like to discuss further please check the Architecture Case Studies
Architecture Services
Architecture Services
IT Vision Development - Work with CIO and senior management to document the vision and build a target architecture to meet that vision
IT Portfolio Analysis (Current State) - Collect all the information of the current systems and document using a standard modeling language
Gap Analysis And Roadmap - Build a roadmap to move the architecture from current state to the target state. Document the transition states and changes required to reach that state.
Migration Planning - Help managers plan the delivery of EA capabilities
Business Case / Trade-Off Analysis - Help find the right option for each change
Pre-Sales Vendor Selection - Support stakeholders through the procurement process
Market Analysis White Paper (Opportunities) - Document the impact of any technology on the IT systems and build a business case if required by the stakeholders
Implementation Governance Support - Support the stakeholders in guiding the project teams
Portfolio Optimisation - Identify and eliminate redundancies in the IT landscape
Architecture Advisory - Support project teams with best practices, patterns etc...
Digital Transformation Advisory - Support stakeholders to make an informed choice during their digital journey
Cloud Migration - Support the stakeholders during their cloud migration journey
Architecture modelling (Archimate) - Document various high-level architecture views
Document Review - Monitor the projects and guide the team as required
Why Hire An Architect? Benefits of Hiring An Experienced EA
Why Standardise IT Documentation?
Communicate your ideas effectively within and outside the organisation
Precisely document IT systems that are easy to read
Get knowledge out of people's head
Reduce dependency on a single team or individual who "knows the systems"
Meaningfully link Business concepts with IT Systems to provide traceability
EA Documentation : Standardisation Using Archimate Modeling Language
Architecture Roadmaps Development & Implementation Approach
Discuss various target scenarios with the stakeholders
Visualise the target systems to automate business activities required for each scenario
Agree on a Target(Business+IT) with stakeholders
Build IT principles, standards, guidelines to move the current systems towards the Target
Govern the various change programs and projects using the agreed principles
Update the current and target architecture at the every stage
Roadmaps: Enterprise Architecture Development & Implementation Plan
Portfolio Analysis Approach
PACE layering method to analyse the IT portfolio to optimise the assets in the landscape
Categorising systems in this way helps stakeholders to prioritise the systems that are important to them. This then can be used to reduce the overall complexity.
Portfolio Analysis Approach
API Layering Approach
API Layering can helps organisations manage change to their systems in a more structured manner. Layering helps in decoupling the Systems Of Records and the front-office Systems Of Innovation. This layering is based on Gartner's PACE layering approach.
IT Principles defined based on these could drive individual projects towards the desired target state.
API Layering Approach - eCommerce Example
An eCommerce System
An eCommerce system consists of a set of systems to capture, process and fulfil orders. It may contain subsystems to manage products, marketing, inventory, prices, tax, discounts, payments, ship & track, returns.
Case Study : An eCommerce Solution
Digital Marketing Technology Key Selection Criteria
Few considerations when selecting a good Digital Marketing solution:
Dynamic Segmentation - Identification of users into various segments while using your website. Profiling users could become a key input to your campaign design.
Campaign design - Providing self-service capability to the marketeers is critical to avoid IT intervention for every minor change to campaigns.
Analytics - A good analytics function will enable better segmentation and tuning of the campaigns.
Case Study: A Digital Marketing Solution
Digital Banking Key Considerations
With an increasing focus on cost reduction, Banks are preparing to digitise much of their systems.
Banks needs to consider few things when embarking on this digital journey:
Physical Branches - Digitisation of the systems can help bring most of the process online, making it easier to transact using the mobile phones. As less people go to the branches, banks can consolidate them based on their usage.
3rd Party Branches - Process standardisation can help in leveraging 3rd party branches in locations where it is not feasible to keep a branch open.
App Developers - Enabling Open Banking will help app developers in bringing innovative apps to the customers.
Automation - Internal processes could be automated with AI/RPA kind of technology to remove any redundant activity that don't require human intervention.
Case Study: Capability Map Of A Retail Banking System