Centralized Fleet Management: A Guide for Public Fleets

Centralized fleet management brings fleet data, standards, policies, and oversight together so an organization can manage vehicles and equipment as one fleet instead of a collection of disconnected operations.

I’ve been thinking about centralization and why the conversation around it can get difficult, especially in public fleets.

The word itself can create some resistance. People hear “centralization” and understandably start thinking about control. Who owns the vehicles? Who controls the budget? Who gets to make decisions? Is fleet going to tell an operating department how to do its job?

I think that can distract us from the real opportunity.

For me, centralized fleet management starts with something much more basic: can we see the fleet?

Can we confidently say what assets we have, where they are, what condition they’re in, whether they’re being maintained properly, how they’re being utilized, what they’re costing us, and when they should be replaced? And when leadership, finance, administration, or elected officials ask those questions, can we stand behind the answers?

You would think those would be relatively easy questions for a fleet to answer. In a lot of organizations, they aren't. The information may be spread across departments, spreadsheets, paper records, individual systems, and sometimes individual people.

That’s where I think centralization starts to become interesting. It gives us an opportunity to create a clearer picture of the fleet and use that picture to make better decisions for the organization.

What Is Centralized Fleet Management?

Centralized fleet management is an operating model in which an organization establishes common oversight, systems, data, policies, or processes for managing vehicles and equipment across departments or locations.

There are a lot of ways to do that.

Some public organizations have a central fleet department responsible for nearly everything related to vehicles and equipment. Others leave quite a bit of operational responsibility with individual departments while establishing common fleet policies, systems, data standards, and reporting.

Areas that may be centralized or standardized include fleet management information systems and data, asset records, preventive maintenance standards, maintenance and repair processes, vehicle specifications and procurement, fuel management, parts and inventory, motor pools, vehicle utilization, lifecycle and replacement planning, budgeting, and performance measurement.

The Municipal Technical Advisory Service at the University of Tennessee recommends centralizing municipal fleet management responsibility when practical, citing greater consistency, accountability, asset utilization, right-sizing, and standardization among the potential benefits.

Those are all worthwhile outcomes. I think the larger value, though, is the ability to understand what is happening across the fleet and act on it.

That’s an important distinction because centralization can become a discussion about organizational authority very quickly. I’m much more interested in whether it helps us manage the fleet better and better support the people who depend on it.

Centralized vs. Decentralized Fleet Management: What's the Difference?

In a centralized fleet management model, fleet information, standards, policies, and often decision-making are coordinated across the organization.

In a decentralized fleet management model, individual departments, agencies, campuses, or operating units have greater autonomy over their vehicles and equipment.

I’ve seen enough fleets over the years to be cautious about declaring one organizational model inherently better than another. You can have a decentralized fleet with excellent processes, good communication, and reliable data. You can put everything under one fleet department and still struggle.

Where things tend to get difficult is fragmentation.

One department tracks maintenance one way. Another has its own spreadsheet. Somebody else has a separate system. Replacement decisions are made using different criteria. Utilization means something slightly different depending on who you ask. Then somebody at the organizational level asks a pretty reasonable question about the fleet and it takes three weeks and six people to answer it.

Even then, you may not be completely confident that everybody calculated the answer the same way.

For public fleets, that creates a larger concern because we're managing public resources. We need to understand where the money is going, what we're getting for it, and whether those resources are supporting the mission as effectively as they should.

What Are the Benefits of Centralized Fleet Management?

The benefits of centralized fleet management tend to build on each other. Better information helps create better processes. Better processes improve the information. Over time, you begin to see the fleet much more clearly.

1. Create One Reliable View of Fleet Data

One of the first questions I ask when working with a fleet is where the data lives.

That answer tells you quite a bit.

Fleet leaders need to understand an asset across its lifecycle. We need the maintenance history, costs, utilization, fuel, age, condition, assignment, and other information that helps explain what has happened to that asset and what we should probably do next.

A centralized fleet management information system, or FMIS, can create a common system of record for that information.

The same principle appears in federal fleet requirements. Federal agencies are required to maintain an FMIS that collects accurate inventory, cost, and utilization data across the complete lifecycle of each motor vehicle and provides information needed for internal and external reporting.

State and local fleets may operate under different requirements, but the management challenge is familiar. When you're accountable for the fleet, having confidence in your information matters.

And confidence is the key word there.

Having data and trusting the data are two different things.

2. Standardize Critical Fleet Processes

I’ve seen this play out several times. Two departments can be doing essentially the same work and recording it differently enough that the resulting data tells two different stories.

That becomes a real problem when we start comparing costs, PM compliance, downtime, technician productivity, utilization, or almost any other fleet measure.

Common processes give the data context.

Preventive maintenance standards, inspections, work orders, parts practices, vehicle specifications, replacement criteria, and reporting definitions are all areas where some consistency can be extremely valuable.

That consistency also makes continuous improvement much easier. When we understand how work is supposed to happen, we can identify where it isn’t happening that way, understand why, and decide whether the process needs to change.

Without that baseline, we can spend an awful lot of time debating the numbers.

3. Improve Vehicle and Equipment Utilization

Utilization is one of the areas where having a fleet-wide view can change the way we think about an asset.

A department may have a vehicle that it uses. That fact by itself doesn't tell us very much.

How often is it being used? What is it being used for? How critical is that use? Is another asset available that could perform the same mission? Is there another department that needs the asset more? Could a motor pool or shared asset accomplish the same thing?

Those are fleet questions, but they're also stewardship questions.

Centralized visibility gives us the ability to look across departments and understand how assets are being used as organizational resources. That can identify opportunities to reassign equipment, share assets, create motor pools, and right-size the fleet.

It can also validate assets that may appear underutilized on paper. Anyone who has spent time around public fleets knows that mileage alone doesn't tell you whether an asset is necessary. Criticality matters. Mission matters. Use case matters.

Good data helps us have that more complete conversation.

4. Strengthen Lifecycle and Replacement Planning

Replacement planning touches almost everything we do in fleet.

Keep an asset too long and maintenance costs can increase, downtime can increase, technician workload can increase, reliability can suffer, and residual value can disappear. Replace too early and you may leave useful economic life on the table.

Getting that decision right requires information.

When maintenance history, costs, utilization, age, condition, and other lifecycle information are scattered across different systems, replacement planning becomes much harder than it needs to be. A common fleet system gives us the ability to evaluate assets using a consistent methodology and understand the whole story of the asset.

That becomes particularly important when we're asking for money.

Most of us have been in the room where finance or leadership looks at the replacement request and asks, “Why this vehicle? Why now?”

We should have a good answer.

The stronger our data is, the easier it becomes to explain the recommendation in terms the rest of the organization can understand.

5. Improve Accountability and Reporting

Public fleet professionals are stewards of public resources. That carries a responsibility to understand how those resources are being used and to communicate that clearly.

When leadership asks why maintenance costs changed, how well assets are being utilized, whether PMs are being completed, or why the replacement budget needs to increase, we should be able to tell that story.

Centralization helps because we're working from common records and definitions. We spend less time collecting and reconciling information and more time understanding what it means.

That last part is where I think fleet leadership is going.

The value isn't producing another report. The value is understanding what the report is telling us and knowing what to do about it.

What Role Does an FMIS Play in Fleet Centralization?

A fleet management information system provides much of the information infrastructure needed to manage fleet operations consistently.

The U.S. Department of Energy describes an FMIS as a centralized system for identifying, collecting, and analyzing asset-level fleet data.

For a public fleet, an FMIS can become the common environment for managing assets, maintenance, work orders, preventive maintenance, parts, fuel, costs, inspections, utilization, and lifecycle planning.

I think there’s a trap here, though.

An organization can centralize the fleet on an org chart and still have fragmented information. You can have one fleet director, one department, and one set of policies while important data continues to live in spreadsheets, paper files, separate databases, and disconnected systems.

The person responsible for the fleet is still trying to assemble the picture.

That’s why I tend to think about information centralization as part of the foundation. The FMIS should capture the activity already happening throughout the fleet and turn it into information that helps people make decisions.

More data isn't necessarily the goal. Most fleets already have plenty of data.

Useful data is the goal.

Can I see something happening in the fleet, understand why it's happening, decide what to do about it, and explain that decision to somebody else?

That’s decision-grade visibility, and I think that’s where an FMIS becomes much more than a digital filing cabinet.

What Can Public Fleets Learn From Utah's Centralization?

The State of Utah is an interesting example because its experience shows how centralization can actually develop inside a large public organization.

On an episode of The Fleet Success Show, longtime fleet leader Steve Saltzgiver talked about his 12 years with the State of Utah, where he eventually became director of fleet operations. During his tenure, an outside fleet study recommended consolidating state fleet operations.

At the time, there were roughly 30 independent fleets, including organizations such as public safety and higher education.

Think about the complexity involved in bringing that together.

One of the early steps was getting organizations onto a common fleet management information system. That created a common foundation they could begin building from.

What I find most useful about the Utah story is that the consolidation took years.

That feels much closer to the reality I've seen in fleet.

Centralization changes responsibilities, processes, systems, budgets, expectations, and sometimes long-established ways of doing business. People need to understand what is changing and why. Departments need confidence that the new approach will still allow them to accomplish their missions.

Software can support that work, but software doesn't create organizational trust.

That takes time.

For fleet leaders considering centralization, I think there’s a lot to be said for establishing the common foundation, showing people that it works, solving problems for them, and continuing to build from there.

Does Centralized Fleet Management Mean Every Decision Is Centralized?

No.

And this is probably where I think some centralization efforts get themselves into trouble.

A police department, public works operation, transit agency, university, parks department, and fire department can all be part of the same organization and have very different missions. Their equipment requirements are different. Their operating environments are different. Their definitions of criticality can be very different.

Fleet needs to understand that.

I've always viewed fleet as a service provider. We bring expertise in vehicles, equipment, maintenance, lifecycle management, procurement, utilization, and all the other things we spend our careers learning. Our customers bring expertise in the missions they're responsible for accomplishing.

The best outcome usually comes from bringing those two perspectives together.

So I think the useful question is: What needs to be consistent for us to manage this as one fleet, and where do departments need flexibility to accomplish their missions?

Asset records probably need consistency. Maintenance standards probably need consistency. Replacement methodology and reporting definitions probably need consistency.

How a department deploys a particular asset may require considerably more flexibility.

That's okay.

The purpose of centralization is to help the organization operate better. Fleet exists to support that organization and its mission.

How Do You Centralize Fleet Management?

I would start by understanding the current state.

What assets do we have? Where are they assigned? How are they being used? Where does the data live? Who is maintaining them? How are costs being recorded? What standards already exist? Where are departments doing things differently, and is there a legitimate operational reason for those differences?

You learn a lot simply by asking those questions.

From there, I’d begin establishing common data standards and a common system of record. Get agreement on what the information means and how it should be captured. Then start looking at the processes where consistency matters most: preventive maintenance, inspections, work orders, asset histories, lifecycle planning, replacement criteria, and the measures the organization uses to understand performance.

I’d also spend a lot of time talking to the departments involved.

This is easy to underestimate.

Those departments know their missions. They know their operational challenges. They may also have very legitimate reasons for doing something differently. Understanding those reasons can help fleet distinguish between a process that truly needs flexibility and one that's simply been done the same way for 20 years.

There’s usually some of both.

As the information gets better, use it. Look at utilization. Look at maintenance. Look at replacement. Look at costs. Find opportunities where the centralized approach can solve an actual problem for somebody.

That’s how you build confidence in the model.

And keep improving it. An organizational change or FMIS implementation isn't the finish line. Data quality needs ongoing attention. Processes evolve. People change. Training matters. The organization's mission changes.

A statewide organization with thousands of assets will take a different path than a municipal fleet with a few hundred. I don't think there is one perfect roadmap.

The common thread is visibility. Once you can see the fleet clearly, you have a much better chance of improving it.

How Do You Know if Your Fleet Needs More Centralization?

Listen to the questions that are difficult to answer.

How many assets do we have?

What does this class cost us?

How many vehicles are underutilized?

What's our PM compliance?

What should we replace next year?

Why did maintenance costs increase?

How much downtime are we experiencing?

If answering those questions requires emails to five departments, several spreadsheets, a couple of phone calls, and somebody saying, “Give me a few days,” there may be an opportunity.

The same is true when different departments maintain separate asset records, maintenance history lives in multiple systems, processes vary significantly, replacement decisions use inconsistent criteria, or fleet-wide reporting requires substantial manual reconciliation.

I’d also pay attention to how much knowledge resides with individual people.

Fleet is going through a significant generational transition. We have experienced professionals retiring with decades of technical and institutional knowledge. When the answer to an important question is “Go ask Bob; he knows how we do that,” we have a vulnerability.

Shared systems, documented processes, and consistent data help retain some of that knowledge and make the organization less dependent on any one person.

These are all signs worth investigating. The answer may involve greater centralization, better processes, better technology, or some combination of the three.

The important thing is recognizing the blind spot.

Centralized Fleet Management Should Create Clarity, Not Bureaucracy

After working around fleet for a long time, this is where I come out on centralization.

It should make life easier for the organization.

Fleet should have a clearer picture of the assets. Departments should get better service. Leadership should have better information. Finance should have more confidence in the numbers. Replacement decisions should be easier to explain. Maintenance should become more consistent. The organization should be able to make better use of the resources it already has.

More approvals and paperwork aren't measures of success.

I’d measure success by the questions we can answer.

Are our assets ready to support the mission? Are we maintaining them appropriately? Are we using our resources well? Do we understand where our costs are coming from? Can we see problems early enough to do something about them? Can we explain our replacement needs? Can we stand behind the information we're giving leadership?

Those are meaningful fleet questions.

And I think there’s a leadership lesson underneath all of this.

Fleet professionals spend our careers supporting other people. Police officers need vehicles to respond. Public works crews need equipment to maintain the community. Parks departments need assets to do their work. Universities need transportation to support students, faculty, staff, and everything happening across a campus.

We're usually in the background.

That's the job.

The better we understand our fleet, the better we can support all of those people doing the work the organization exists to do.

Centralization can help us get there. The value comes from the clarity it creates and what we choose to do with that clarity.

Get a Clearer View of Your Public Fleet With RTA Fleet360

Centralizing fleet operations is difficult work because you're dealing with much more than technology. You're dealing with people, history, budgets, processes, departmental needs, organizational priorities, and sometimes a fair amount of politics.

The technology still matters.

RTA Fleet360 is built for public-sector and in-house fleets that need a clearer view of their operations. It creates a common system of record across maintenance, assets, costs, utilization, lifecycle planning, reporting, and the other information fleet leaders need to manage the operation.

One of the things I value about RTA is the amount of fleet experience inside the organization. Our team includes former fleet managers with more than 450 years of combined fleet management experience. They've lived these challenges. They understand that what looks simple on a screen may be considerably more complicated when you're trying to make it work in a shop, across departments, or in front of a budget committee.

That's particularly important with centralization because the software is only part of the work.

You still need to decide what should be standardized, what should remain flexible, how the data should be structured, how processes should work, and how you're going to bring people along.

If disconnected systems and processes are making it difficult to see what is happening across your fleet, we'd be happy to talk through it with you and share what we've learned from other public fleets.

Sometimes the first step is simply getting a clearer picture of where you are.

This article was inspired by a recent episode of our podcast. Check out the full episode for even more tips and tricks: