TBM Taxonomy Services Layer Version 4.

0*
Best Practices to Define Tech Categories
Business Delivery Infrastructure
Customer Manufacturing Product Sales & Security & Strategy &
Development Operations Support Compute Data Center Network Storage
Service & Delivery Management Marketing Compliance Planning

Inventory & Product Customer Design & Capacity Business Continuity Business Solution Application Compute on Enterprise Data
Customer Care Data Network Backup & Archive
Warehousing Development Analytics Development Management & Disaster Recovery Consulting Support Demand Center

Modernization Deployment & Cyber Security & Enterprise Distributed Storage

Order Management Manufacturing Product Planning Customer Sales Central Print Mainframe Other Data Center Domain Services
& Migration Administration Incident Response Architecture (CDN)

Marketing & Event Data Privacy Innovation File & Object

Product Delivery System Integration IT Training Physical Compute Internet
Advertising Management & Security & Ideation Storage

Sales Force & IT Service Governance, Risk IT Vendor Virtual Compute Networked
Resource Planning Testing Service Desk Load Balancing
Channel Mgmt Management & Compliance Management & Containers Storage

Identity & Access Program, Product & Virtual Private

Service Delivery Scheduling
Management Project Management Network

Technology Business
Security Awareness Voice Network
Management

Threat &
Vulnerability Mgmt

Platform Shared & Corporate Workplace

Corporate Health, Property & Risk, Audit & Vendor & Client Communication
Application Data Finance Legal Workforce Connectivity
Communications Safety, Security Facility Services Compliance Procurement Computing & Collaboration
& Environmental Services Services
Application Community Accounts Payables Services Development & Benefits Bring Your Own
Database Case Management Collaboration Network Access
Hosting Outreach & Expense Space Planning Contract Management Device
Auditing
Reimbursement Healthcare Management
Content Data Analytics External Services Employee
Contract Review Fleet Management Computer Communication Remote Access
Management & Visualizations Communications Accounts Breach Mgmt & Communications &
(non-logistics) Sourcing and
Receivable Occupational Remediation Relations
Procurement
Decision Intelligence Government Safety
Data Management Legal Counsel Mobile Print
& Automation Relations General Accounting Food & Beverage Business Continuity Employee
Supplier
& Reporting Oversight & Planning & Development
Management
Development Stakeholder Enforcement Management
Data Warehouse Operations, Virtual Client Productivity
Platform Relations Payroll & Time Employee Transitions
Maintenance, Repair
Reporting Policy & & Separation
& Improvements Investigations
Foundation Governance
Distributed Cache Performance,
Platform Planning & Mgmt
Records Retention & Rewards
Accounting Physical Security
Management Management
Message Bus
& Integration Project
Workspace Risk Policy
Accounting
Services Management Management
Search Revenue
Accounting Recruitment

Streaming
Treasury Workforce
Management Service Type

Tax Service Category

Service Name

BEST PRACTICES
Technical capabilities represent an organization’s IT Don’t overlap Breadth over depth Long-term stability
capabilities, independent of its structure, processes, Good technical capabilities do not overlap; they are mutually While more levels can help to get a better structure, it comes at the Properly defined technical capabilities are fairly stable over time,
people, or domains. They help to organize IT components exclusive. If you are able to assign your level 2 stacks without any cost of increased complexity. We recommend keeping the technical persisting throughout any organizational changes. Only major
(e.g., a service, software, or hardware). ambiguity, you are on the right track. capabilities to no more than three levels down. business model updates should affect them.

*Taxonomy by Technology Business Management Council. ©2016-2020 Technology Business Management Council. All Rights Reserved.
www.leanix.net