Enterprise IT portfolios grow fast. Costs spread across apps, platforms, vendors, and cloud services. Over time, leaders lose a clear view of what each system does, what it costs, and why it still exists. That problem gets worse when agencies inherit legacy tools, fund programs in silos, or lack common service definitions.
That is where TBM can help. Technology Business Management gives agencies a common taxonomy for cost, service, and consumption. When you pair that structure with application rationalization and a TIME framework approach, leaders can make better portfolio decisions. They can identify systems to tolerate, invest in, migrate, or eliminate using facts instead of opinion.
At Artisan Analytix, this topic sits at the center of our IT Financial Management and FinOps work. Through our support on the Commonwealth of Virginia VITA MSI program, we have worked in chargeback and showback operations across more than 65 state agencies. That work includes Apptio Cloudability, Apptio/TBM Studio administration, executive dashboards in Power BI, supplier financial coordination, and SLA compliance across service towers. Those same disciplines matter in large-scale portfolio rationalization.
For government leaders, this is not only a cost exercise. It is also a governance, mission, and risk exercise. Agencies must align technology decisions with the CFO Act, OMB Circular A-11 capital planning, OMB Circular A-123 internal controls, FITARA oversight practices, FISMA requirements, and NIST Risk Management Framework expectations. A strong rationalization model helps connect all of those concerns in one operating view.
This article explains how to apply TBM taxonomy and TIME-style rationalization at scale. It focuses on practical steps. It also shows how to use usage telemetry, total cost, and business value scoring to guide action across complex portfolios.
Why TBM matters in IT portfolio rationalization
Most agencies already know they have overlap in their application landscape. The hard part is proving it in a way that finance, IT, security, and mission leaders all trust. Different teams often classify the same system in different ways. One office sees a platform as mission critical. Another sees the same platform as underused and expensive. Without a common language, rationalization stalls.
TBM addresses that problem by creating a shared model for technology cost and service data. The TBM Council taxonomy helps map spend into towers, sub-towers, applications, business services, and cost pools. That structure gives agencies a repeatable way to compare systems across programs. It also supports better showback and chargeback conversations because business owners can see what they consume and why it costs what it costs.
In a rationalization effort, TBM does more than organize invoices. It links cost to value. Agencies can connect labor, hosting, software, support, security, and vendor spend to a named application or service. They can also trace those costs upward to mission capabilities and downward to infrastructure components. That visibility matters when leaders must decide whether to modernize a tool, keep it as is, move it to a new platform, or retire it.
This is one reason platforms like Apptio are often central to mature ITFM programs. Apptio helps organize financial and operational data into useful cost models. It can support a more disciplined view of application total cost, service unit economics, and business alignment. When paired with dashboards in Power BI or Tableau, that data becomes easier for executives to read and use.
TBM also supports policy goals that agencies already face. OMB Circular A-11 asks agencies to improve planning and investment discipline. OMB Circular A-123 emphasizes internal control and accountability. FITARA has pushed greater CIO visibility over IT resources for years. A TBM model strengthens those efforts because it makes the portfolio easier to govern.
Agencies should not treat TBM as a one-time reporting project. It works best as an operating model. That means standard definitions, regular data refreshes, clear ownership, and an agreed method for cost allocation. When those basics are in place, rationalization decisions gain credibility across finance and IT.
How the TIME framework helps leaders sort the portfolio
The TIME framework is a practical way to classify applications for action. In most organizations, TIME stands for Tolerate, Invest, Migrate, and Eliminate. The value of this model is its simplicity. Leaders can use it to move from a long list of systems to a manageable set of strategic choices.
Tolerate applies to systems that still serve a purpose and can remain in place for now. These applications may not be ideal, but they do not create enough risk or inefficiency to justify near-term disruption. A tolerate decision should still include guardrails. Agencies should define support expectations, security obligations, and a trigger that would move the system into another category later.
Invest fits applications that are important to mission delivery and worth improving. These systems often have strong user adoption, solid business value, and a future role in the target architecture. The right action may include interface improvements, stronger data management, automation, cloud optimization, or security enhancement. Invest decisions should connect to enterprise architecture and capital planning, not just local preferences.
Migrate is useful when the capability is still needed, but the current platform is no longer the right fit. That may mean moving from a legacy on-premise system to a managed cloud platform, consolidating multiple tools into one enterprise service, or shifting users to a standard shared application. Migration decisions should account for data conversion, integration dependencies, access controls, records retention, and operational continuity.
Eliminate applies to systems that no longer justify their cost or complexity. These are often duplicate tools, unsupported niche apps, or platforms with little active usage. Elimination can free staff time and reduce attack surface. It can also simplify audits, improve inventory quality, and lower the burden on service desks and infrastructure teams.
The key is not the acronym alone. The key is the scoring model behind it. TIME decisions should reflect cost, usage, technical condition, cyber risk, and mission value. Agencies should avoid making those choices from one data point, such as license count or stakeholder opinion. A balanced model creates a stronger basis for governance.
TIME also works well in waves. An agency does not need to classify every application on day one. It can start with a critical segment, such as end-user tools, case management apps, financial systems, or collaboration platforms. Early wins build trust and improve the data model for later phases.
Build a defensible scoring model with cost, telemetry, and value
Effective application rationalization depends on scoring. If the model is weak, the program becomes political. If the model is clear, portfolio conversations become easier. A good model usually combines three major dimensions: total cost, usage telemetry, and business value. Agencies can then add risk, technical health, and compliance as supporting factors.
Start with total cost. This must go beyond software license fees. Agencies should include hosting, cloud consumption, contractor support, internal labor, infrastructure, cybersecurity tooling, maintenance, and vendor management. Shared services create a challenge here. TBM helps by assigning those shared costs through standard allocation rules. That is where Apptio cost models can be especially useful.
Next, measure usage telemetry. This is where many programs fall short. Leaders may know what they pay for, but not what users actually use. Telemetry can include logins, transaction volumes, storage growth, feature adoption, interface traffic, compute usage, service desk tickets, and peak demand patterns. For infrastructure and cloud-hosted systems, Cloudability and similar tools can help connect consumption data to cost. For SaaS and enterprise applications, agencies may need to pull telemetry from platform logs, identity tools, or vendor admin consoles.
Then score business value. This is often the hardest dimension because it includes both mission and operational factors. Agencies should ask simple questions. Does the application support a statutory mission? Is it required for financial operations, grants, safety, inspections, or casework? Does it support a high-visibility executive priority? Does it enable unique data or workflows that no other system can handle today? A structured scorecard helps convert those answers into comparable ratings.
Technical health should sit beside those core dimensions. Agencies should review vendor support status, integration complexity, code maintainability, defect history, scalability, resilience, accessibility, and cyber posture. FISMA and NIST RMF considerations belong here. A system with strong mission value but weak security may still remain in the portfolio, but leaders should classify it with eyes open and plan remediation or migration.
Keep the model easy to explain. Too many variables can slow decisions. A simple weighted approach often works best. Define each criterion. Assign clear ownership for the source data. Refresh scores on a regular schedule. Then publish the results in a dashboard that both executives and program managers can understand.
Visualization matters. Power BI and Tableau are useful for turning scoring outputs into action lists. Leaders should be able to filter by bureau, mission area, cost center, hosting model, or system owner. They should also see where a portfolio has redundant tools, unsupported technologies, or low-usage applications that consume shared resources.
Use TBM taxonomy to connect applications to services and spending
Many rationalization efforts fail because applications are reviewed in isolation. A single app may appear inexpensive until leaders see all the hidden support around it. Another app may seem costly until they learn it supports multiple mission services and absorbs shared enterprise functions. TBM helps solve this by connecting applications to the full service and cost chain.
Using TBM taxonomy, agencies can map applications to business services, IT towers, cost pools, and resource owners. That means a case management platform is not just a software line item. It becomes part of a larger picture that includes hosting, storage, network, support labor, security tools, service desk activity, and vendor operations. This matters when deciding whether to invest or migrate.
In practice, agencies should start with a clean application inventory. Each record should include owner, function, users, interfaces, hosting model, data sensitivity, support model, lifecycle stage, and related contracts. Then link each application to cost objects in the TBM model. If the agency already runs showback or chargeback, much of this structure may already exist. The rationalization team can build on it instead of starting from zero.
Our experience supporting Virginia VITA MSI reflects this discipline. In that environment, IT financial management requires shared definitions, supplier financial coordination, and executive reporting across many agencies and service towers. Those same controls help a rationalization program because they improve traceability. Leaders can see where spend sits, who owns it, and which services depend on it.
TBM taxonomy also supports enterprise architecture planning. Once applications are grouped by capability and cost, agencies can spot patterns. They may find several tools doing similar work in different bureaus. They may see aging platforms with high support effort. They may also uncover strategic platforms that deserve more funding because they support many downstream services.
This service-based view is important for state and federal agencies alike. Government organizations rarely retire systems in a vacuum. Each decision affects interfaces, records, access rights, reporting, help desk workflows, and vendor agreements. TBM makes those dependencies easier to model and discuss before action begins.
Governance, controls, and policy alignment for government agencies
Portfolio rationalization needs strong governance. Without it, agencies end up with inconsistent scoring, local exceptions, and delayed decisions. A clear governance model should define who owns the inventory, who approves classifications, who validates costs, and who signs off on final TIME actions. CIO, CFO, CISO, enterprise architecture, and program leadership all need a seat at the table.
For federal agencies, this work should align with existing policy requirements. OMB Circular A-11 supports disciplined planning for capital assets and major IT investments. OMB Circular A-123 reinforces internal control and management accountability. FITARA has long encouraged stronger CIO oversight of IT resources. Rationalization programs can support all of these objectives by improving transparency and reducing fragmented spending.
Security and privacy must remain part of the model from the start. FISMA requires agencies to manage information security risk. NIST RMF gives a structured process for categorization, control selection, assessment, authorization, and continuous monitoring. If an agency classifies a system as tolerate or migrate, it still needs to maintain required controls while that decision remains in effect. TIME categories do not replace security governance. They should work with it.
Records management also matters. Some systems appear to be good candidates for elimination until the agency reviews legal retention, audit support, or evidentiary needs. Financial systems may also tie into CFO Act reporting obligations, Treasury interfaces, grants oversight, or audit trails. The rationalization team should engage records, legal, and audit stakeholders early to avoid delays late in the process.
Business continuity is another key control area. Before retiring or consolidating systems, agencies should assess how service levels, recovery objectives, and supplier dependencies will change. This is especially important in shared service environments. ISO-aligned management disciplines can help here. Artisan Analytix maintains certifications that reflect formal quality, IT service management, information security, and business continuity practices. Those same management habits support disciplined governance in portfolio work.
The governance model should also define an exception process. Some applications will not fit the standard pattern. That is normal. The goal is not to force every system into the same answer. The goal is to make exceptions visible, justified, time-bound, and reviewed by the right leaders.
How to run a rationalization program at scale
Large portfolios can overwhelm even well-run agencies. The best way forward is to use a phased approach. Start with a pilot domain that matters to leadership and has enough data to support decisions. Examples include collaboration tools, analytics platforms, internal workflow apps, or cloud-hosted business systems. A focused pilot helps teams test scoring rules, validate the inventory, and refine governance.
Phase one should center on data readiness. Build the inventory. Confirm owners. Map costs in the TBM model. Gather telemetry from identity, infrastructure, cloud, SaaS, and service management sources. Review contract and renewal dates. Flag systems with missing or weak metadata. It is better to identify data gaps early than to debate them in executive review sessions.
Phase two should apply scoring and draft TIME classifications. This is where cross-functional workshops help. Finance can validate total cost. Architecture can assess technical fit. Security can review control posture. Program teams can score mission value and user dependency. Keep notes on every decision. An agency should be able to explain why a system landed in a given category.
Phase three should focus on action plans. TIME labels alone do not change the portfolio. Each application needs a next step, owner, timeline, dependency list, and governance path. For tolerate, define support terms and review triggers. For invest, define enhancement priorities and funding alignment. For migrate, define landing platforms and cutover steps. For eliminate, define decommission controls, archive needs, and user transition support.
Automation can improve this process. UiPath and similar tools can help with repetitive inventory tasks, document extraction, or workflow routing when agencies manage large review volumes. Dashboards in Power BI can show progress by bureau or category. ServiceNow can help track approvals, dependencies, and operational tasks linked to migration or retirement actions.
Communication is just as important as tooling. Program offices may resist rationalization if they think it is only a cost-cutting exercise. Leaders should explain that the goal is better mission support, lower operational drag, clearer accountability, and stronger resilience. The strongest programs combine financial discipline with user-centered change management.
Immediate actions agencies can take now
Agencies do not need to wait for a major transformation program to begin. They can take practical steps now. First, create a single application inventory owner. If no one owns the list, the list will never stay current. Second, adopt a plain-language definition for what counts as an application, platform, and service. Third, agree on a minimum data set for each record.
Next, choose a simple scoring model. Start with total cost, usage telemetry, business value, and technical risk. Keep the first version simple enough to use within a few weeks. Then improve it over time. Leaders often learn more from early portfolio conversations than from a perfect model that arrives too late.
Agencies should also connect rationalization to budget and renewal cycles. Review high-cost contracts, low-usage subscriptions, and aging support agreements before option years or renewal dates. Tie findings into the FY2026 and upcoming FY2027 planning cycle where possible. That helps turn analysis into real decisions.
Another smart step is to stand up executive reporting. Even a basic Power BI dashboard can improve visibility if it shows inventory status, cost concentration, duplicate capabilities, and draft TIME categories. The goal is not visual polish. The goal is a shared fact base.
For agencies with mature ITFM practices, this is a natural extension of showback and chargeback. If you already use Apptio or Cloudability, expand the conversation from “what did we spend” to “what capability did we fund, and should we keep funding it this way.” That shift moves ITFM from reporting into strategy.
Artisan Analytix helps public sector leaders connect financial management, TBM, and portfolio decision-making. Our work spans IT Financial Management, FinOps, data analytics, digital transformation, and program implementation. If your agency is looking to strengthen chargeback, improve cost transparency, or launch a structured rationalization effort, explore our expertise or contact us to continue the conversation.
At scale, rationalization is not about finding one perfect score. It is about building a repeatable system for better decisions. With TBM, a clear TIME framework, and reliable cost and telemetry data, agencies can make those decisions with greater confidence and control.