TBM Framework & Taxonomy

 View Only
Back to Library

TBM Taxonomy v3.0 

​
Attachment(s)
pdf file
TBMC TBM Taxonomy V3.0.1 FINAL 2018-11-02.pdf   2.97 MB   1 version
Uploaded - 09-22-2020
 
Download
11-16-2018 13:24

This paper provides a detailed description of the Technology Business Management (TBM) taxonomy Version 3.0 updated November 2018.  The document is made available via the TBM Council’s community web site, TBM Connect (www.TBMConnect.org), for all members to read and use the information. For more information on the Standards Committee, see last page of this document or refer to the TBM Council Standards Committee Charter, also available on TBM Connect.

 

Summary of the 2.1 to 3.0 changes:

Cost Pools

  • Level 1 definitions:  No changes; created definitions for the Cost Pools.  

IT Towers

  • Level 1 definitions:  No changes; created definitions for the IT Resource Towers. 

 

Services

  • Level 1 & 2 definitions
    • Created definitions for the Service Types and Service Categories. 
  • Products & Services
    • Extended layer name from “Services” to “Products & Services” to recognize Agile continuous investment
  • Platform Services
    • Added new Foundation Platform (e.g. SAP Basis, Force.com) under Application Services
    • Renamed “Machine Learning & AI” to “Decision Intelligence & Automation” under Application Services
    • Added a service offering for Geospatial Analytics under Data > Data Analytics & Visualization
  • Delivery Services
    • Security Service replaced and broken out into five separate services:  Identity & Access Management, Security Awareness, Cybersecurity & Incident Response, Threat & Vulnerability Management, and Data Privacy & Security.
  • Business Application Services: 
    • Split into 2 separate service types:  Business Services and Shared Services
    • The phrase, "Applications and services that enable ..." added to Business Service / Shared Service definitions to reinforce the scope of technology costs not the business operations costs
  • Shared Services
    • Reviewed EBM Workgroup deliverables, refined and consolidated into 8 new service categories: Finance Services; Workforce Services; Vendor & Procurement Services; Health, Safety, Security & Environment Services; Risk, Audit & Compliance Services; Legal Services; Property & Facility Services; Corporate Communication Services
  • Business Services
    • Continued to use the “generic” categories from 2.0/2.1
    • Coordinated with Healthcare workgroup to create the Healthcare Provider services extensions to the taxonomy
    • Established a “technology extension kit” to enable other vertical workgroups to incorporate extensions to the taxonomy

 

Updated 4/19/2019 to include the missing definition for IT Resource Sub-Tower: Compute > High Performance Compute

Statistics
1 Favorited
60 Views
1 Files
0 Shares
49 Downloads

Comments

Amber Knight
06-29-2020 17:16

I was curious if there are additional definitions for some of the Specific areas defined under service names?  Specifically, Under Delivery Services, Security and Compliance Category, Identity & Access Management Service name, there are a number of specific areas.  Is there a place I can find a definitions for these?

Steve Carrell
11-06-2019 18:50

Point of clarification on the "TBM Taxonomy," specifically that it is rather a collection of taxonomies with classes, relationships, and constraints that describe the structure of data as it is organized and used in TBM.  More precisely then, it is an ontology.

 

A taxonomy aims to classify a single subject area (class) into parent/child relationships where a child item can have only one parent.  By comparison, an ontology can include several taxonomies and “attempts to describe and capture an entire subject area, with all of its complexity.”

 

In the TBM model several taxonomies are specified or referenced including cost pools, IT towers, services, and capabilities (see Figure 1 in the 3.0 document).  More importantly, the model defines relationships between these taxonomies (see Figure 2 in the 3.0 document).  These relationships define how to “translate” between the various taxonomies, i.e., the layers of the model.  Thus, the TBM model presented is more accurately and precisely defined as an ontology.

 

Why does this matter?  While this may be viewed as “just” semantics, semantics are how we communicate.  The purpose of this model is to communicate the TBM ontology.  As the TBM world interacts with other disciplines it is essential that we use clear and precise language to describe this model.  Improper semantics, like improper grammar, reflect a lack of discipline and rigor.

Todd Tucker Steve Morley Ed Hayman

Brian McCarty
10-07-2019 16:42

Curious if there is plans to have a taxonomy update in 2019 or 2020. Perhaps an announcement at the conference in a few weeks?

Stacie Taylor
04-01-2019 15:48

On Page 30, there are 8 types listed under the Application Services under Platform Services (in the gray box on the right near the top of the page).  However, in the definitions below, there are only 7 types with definitions.  It looks like ERP Foundation and Development Platform were combined into Foundation Platform in the definitions?

Michael Kristensen
12-03-2018 07:25

This document lacks the definition for High Performance Computing, IT Sub-Tower.

High Performance Computing as a separate IT Sub-Tower under Compute 

Related Entries and Links

No Related Resource entered.