Introduction
Technology Reference Models (TRMs) generally focus on the standardized classification and categorization of technology components. They provide a common, abstract framework that guides technology choices, promotes interoperability, and ensures consistency in the underlying technical infrastructure across an organization.
In Ardoq, this can be achieved in two ways:
Firstly, through the creation of a Technology Product Catalog and the identification of approved standards within that catalog. Further details on the mechanism for achieving this can be found in the Technology Portfolio Management Solution. Ref: Technology Portfolio Management Metamodel | Ardoq Help
Secondly, through the extension of your Technology Product Catalog to incorporate references from your Technical Capability model.
This article will explore the second mechanism in more depth, looking at how technical capabilities can be used to understand the different roles technologies currently play in your organization and what role they can play in governing an evolving technology portfolio.
The Value of Technology Reference Models
TRMs can help answer the following business questions:
What are the key Technical Capabilities that require direction and management within the enterprise?
How are these Technical Capabilities realized by the existing application portfolio?
What technology products exist that could also support the realization of this capability?
Where would the enterprise benefit from the identification of standard technology solutions for realizing a technical capability, to reduce or prevent duplication, and to manage cost?
By answering these questions, the following benefits can be achieved:
Improved Strategic Alignment by ensuring technology investments directly support and enable technical capabilities, aligning IT strategy with technology delivery.
Enhanced Decision-Making by having a clear framework for evaluating technology choices, allowing for more informed decisions on technology standards, rationalization, and investment.
Increased Agility and Innovation through standardizing technology products for specific capabilities, reducing complexity, and by allowing for quicker adoption of new technologies and a focus on innovation.
Better Communication and Collaboration by creating a common language between business and IT stakeholders, making it easier to communicate the value and purpose of technology across the organization.
Optimized Cost and Efficiency helps identify redundant technologies and consolidate products, leading to cost savings through reduced licensing, maintenance, and support overhead.
Technology Reference Model Stakeholders
Key Stakeholders for a TRM include:
The Chief Information Officer (CIO) / Chief Technology Officer (CTO) is responsible for the overall technology strategy and vision. The reference model is a crucial tool for the CIO/CTO to ensure that technology investments align with business goals and that the IT landscape is efficient and well-governed.
Application and Solution Architects are the primary consumers of the reference model. They use it to select appropriate technologies for new projects and to ensure that the solutions they design adhere to organizational standards and best practices, promoting consistency and reducing technical debt.
The Chief Enterprise Architect is the owner and creator of the model who uses it to define and communicate technology standards and to guide the organization's technology evolution. This role ensures the model's integrity and its alignment with both business and IT strategies.
Technology Product Managers are responsible for the lifecycle of specific technology products. The reference model helps them understand which products are standard, which are being phased out, and which new technologies are being considered, enabling them to manage their product portfolios effectively.
Business and IT Leadership includes department heads, project sponsors, and other senior leaders. They use the reference model to understand the technology landscape, to make informed decisions about technology-related projects, and to ensure that technology is a key enabler for their business initiatives.
Technology Reference Model Metamodel
The metamodel for creating a TRM is the same as the Technical Capability Modeling and Realization Solution, with the addition of the following connections:
Technical Capability ‘Is Realized By’ Technology Product
Technology Product ‘Deploys To’ Application
The ‘Approved Standard’ date range field should also be added, as well as a new ‘Is Standard?’ field which is a calculated checkbox (see Field Gremlin).
Fig.1 Technology Reference Model metamodel
Technology Reference Models in Ardoq
The first step toward a TRM is the process of producing a foundation Technical Capability model. For more information on the process, see the Technical Capability Modeling and Realization Solution Guide and What Are Technical Capabilities? | Ardoq Help.
An example technical capability map is shown below:
Fig.2 Technical Capability map
By following the Technical Capability Modeling and Realization Solution Guide, you can map the existing application portfolio to technical capabilities. An example of this mapping is shown below:
Fig.3 Technical Capabilities realized by Applications as per the Technical Capability Modeling and Realization Solution
By extending this approach, we can also reference Technology Products that are capable of providing the Technical Capability. This can be achieved by extending the surveys below to capture the required information:
Technical Capability Detail & Realization Survey (TC->App/Tech Product) - TCM (see Technical Capability Modeling and Realization Solution)
Technology Product Review Survey - TPM (see Technology Portfolio Management Solution)
An example mapping from Technical Capability to relevant Technology Products is shown below:
Fig.4 Technology Products with the potential to realize Technical Capabilities
By setting the Approved Standard dates on the Is Realized By reference, you can identify from the potential Technology Products those you wish to use a standard for the capability. The Technical Capability map below shows all available Technology Products and identifies the chosen standard (highlighted in green).
Fig.5 Potential Technology Products alongside the identified standard
You can also use the Architecture Records Solution to manage all your defined standards and capture the concerns and rationale behind the creation of each standard.
Fig.6 Architecture Standard record for the adoption of RabbitMQ as the standard Message Broker technology
Once you have an identified standard, you are able to show on a single capability map the different ways a capability could be realised, the identified standard product(s) for that capability, and the products currently deployed.
Fig.7 Technical Capability map showing deployed Technology Products (blue) alongside all potential products (white) and the identified standard (green)
By mapping Technology Products to Technical Capabilities, the TRM can support the communication of technology standards across capabilities, as well as identify technology options for adoption or rationalization. This model can also be used in conjunction with your existing capability realization information to help identify variation from the reference model and any resulting risks or technical debt.
Field Gremlin - ‘Is Standard?’
The Gremlin for the ‘Is Standard?’ calculated checkbox is shown below:
today = new Date().format('YYYY-MM-dd');
g.E()
.hasId(ids)
.project('id', 'name', 'value')
.by(id)
.by('name')
.by(
choose(
and(
has('approved_standard_start_date', lte(today)),
has('approved_standard_end_date', gte(today))
),
constant(true),
constant(false)
)
)