Technical Reference Model – what should it look like?

Lots of enterprises struggle with the sprawl of technology products and standards.  ICT Managers know that reducing the variety in the set of products that must be supported will reduce costs and improve support levels.

One of the core tools of the Enterprise Architect is the Technical Reference Model or TRM.

In Australian Government, the AGA provides a reference taxonomy that can be used to develop a TRM.  You can learn all about the AGA TRM here:  http://www.finance.gov.au/e-government/strategy-and-governance/aga-rm/trm.html Talking to people who have used it, and having used it myself in two government agencies, I can say that it is not an easy model to work with.  The categories seem outdated and awkward.  (AGIMO are working on an update.)

If your objective is to define a set of standard technologies that will provide the basis for rationalising and consolidating your technology set, then a simple visual model like this might work. (Note this is only meant to be a sample, not a complete model, and I’m not trying to make any comment re the particular vendors listed.)

In my experience, a simple diagram like this offers the following benefits:

  • No modelling tools required
  • Simple format that is easily understood
  • Avoids clutter with product version details (although a detailed format with products versions can be useful too)
  • Provides a clear path to less complexity in your technology environment

Would this work in your organisation?

This entry was posted in Uncategorized. Bookmark the permalink.

Comments are closed.