Menu

You are here

Home » TBM

TBM

OCIO Monthly Reporting Metrics

The purpose of this page is to publish data related to the state's IT performance, and is part of a series of public reports developed by the OCIO. This dashboard contains information about IT Project Assessments completed by agencies, IT projects under OCIO oversight, and IT fiscal information for state agencies. This dashboard is updated monthly on the 17th of each month, or the first business day immediately after the 17th. 

 

Getting Started with TBM

Developing the Statewide Cost Model

In the State of Washington, cost modeling is done in accordance with the adopted taxonomy and starts with modeling costs to the technology towers. TBM Program technology towers are key to the foundation and support moving to the next level of maturity which entails modeling costs to the applications, business services and business capabilities.

Modeling Cost to Technology Towers

Standard 113.40 - TBM Reporting Solution Standard

Standard 113.40 – TBM Reporting Solution Standard

 

STANDARD STATEMENT

The reporting solution used within the TBM Program to track, monitor and report IT expenditures is from Apptio, Inc.

 

TEST TBM Program in Action

The TBM Program monitors statewide IT spend by capturing data on new expenditures (IT Acquisitions), ongoing expenditures (Maintenance and Operations) and spend between agencies (EL Charges - Data Processing InterAgency). 

TBM Taxonomy Standard

TBM Navigating Change & Process Improvements

Navigating TBM Program Changes

Washington state TBM Program journey started in 2012. The program encountered and overcame several challenges during the early years. Leveraging lessons learned, in 2016 the community supported a program "reboot" that was more centered on a strategic approach resulting in increased value. Following are published articles on navigating TBM Program changes and capturing value in Washington state.

TBM Taxonomy

To facilitate communication and gain alignment between IT, Finance and Business areas we recognized a common language or taxonomy was needed.  The program initially used a "custom" taxonomy to identify pools of cost and technologies which resulted in everyone speaking a common language however led to missed opportunities in executive level reporting. To close the gap on the reporting,  the program moved to industry standard TBM Taxonomy that’s governed and maintained by the TBM Council Board Committee on Standards.

Pages