ServiceNow Asset Management Optimisation

What Asset Management Optimisation Covers

Asset Management optimisation helps organizations get full value from the IT Asset Management module on the Now Platform. Many organizations have asset data scattered across spreadsheets, multiple systems, or incomplete in ServiceNow. Asset Management optimisation brings inventory under control, establishes clean data, builds workflows that scale, and creates reporting that drives real business decisions about spending and lifecycle. The engagement focuses on both the technical setup (configuration, integrations, data loading) and the organizational elements (process design, governance, team capability).

Common Starting Problems

Most organizations entering asset optimisation face several recurring challenges. Inventory data is incomplete or stale: hardware locations are unknown, software licenses are not tracked, mobile devices disappear, and depreciation calculations are wrong. Multiple people own the asset data and disagree about the source of truth. Procurement and IT operations don’t align on asset definitions or ownership. Audits reveal compliance gaps: unlicensed software, assets not meeting security baselines, or critical hardware not backed up. Cost control is weak: organizations spend money on renewal licenses they already have, or on hardware they forgot they owned. Asset lifecycle is undefined: when does an asset retire, who is responsible for disposal, where does the data go?

Typical Approach and Deliverables

Asset optimisation engagements typically start with a discovery phase: auditing your current state, interviewing stakeholders across IT, finance, procurement, and compliance, and identifying the highest-impact problems to solve. We define target scope (what assets matter most to track), clean existing data (deduplication, validation, enrichment), and configure ServiceNow to hold asset information with the right fields and relationships. Integration is a key piece: connecting asset data from your CMDB, directory service, hardware vendors, or procurement systems so asset records stay current. Reporting and dashboards are built to show asset utilization, cost, lifecycle status, and compliance. Governance is established: who enters assets, who approves changes, what reviews happen regularly, how often data is refreshed. Training equips teams to use the new processes.

Initial Assessment and Discovery

Optimisation engagements begin by understanding your current state: what asset data do you have, where is it stored, what is missing or inaccurate? We interview stakeholders across IT, finance, procurement, and operations to understand pain points and priorities. We assess your technology landscape: what systems hold asset data, what integrations exist, what gaps are causing problems. We evaluate your team’s capacity and capability: can your current staff maintain the optimisation, or do you need help? Discovery results guide the rest of the engagement and ensure scope is realistic.

How Asset Optimisation Connects to Other Modules

Asset Management doesn’t exist in isolation on the Now Platform. It connects closely to the CMDB (Configuration Management Database) where infrastructure relationships are stored. Changes to assets flow to Change Management so approvals are tracked and audited. Incidents logged against assets help identify problem hardware or software. Procurement integrates with asset data so you know what you ordered, what arrived, and what costs were. Hardware Asset Management covers the life of a hardware asset from procurement to disposal, and it is a separate part of the Asset Management suite. Software Asset Management Professional tracks software licenses, usage, and compliance. Financial integrations allow depreciation calculation and cost reporting. When these connections are weak, organizations cannot see the true cost of IT or make informed decisions.

Pitfalls and Lessons Learned

Asset optimisation often surfaces common pitfalls. Starting without clear business drivers means you optimize the wrong things and don’t get buy-in. Trying to track too much detail creates overhead that teams cut corners to avoid. Treating asset data as an IT-only function misses the reality that finance, procurement, and operations need it too. Launching optimization without governance and accountability means data quality degrades again within months. Underestimating integration complexity leads to data sync failures or manual workarounds. Overcomplicating process usually fails: simpler processes with good governance are more sustainable than perfect processes that nobody follows.

Building Organization Capability

Lasting asset optimisation requires your organization to own and maintain the improvements. Engagements include knowledge transfer: documenting processes, training your teams, and embedding your staff alongside Oblytech consultants so they learn by doing. Success depends on assigning clear ownership of asset data, defining processes that teams will actually follow, establishing regular reviews to keep data quality high, and measuring progress so you know whether the effort is delivering value.

How Oblytech Supports Asset Management Optimisation

Oblytech leads engagements that transform asset management from scattered, disconnected data into a reliable system that serves procurement, finance, operations, and compliance. We assess your current environment and constraints, design the target state based on your business needs and maturity level, configure ServiceNow to support the design, integrate data sources, and build reporting. We work with your teams throughout so your organization builds capability and ownership. After the engagement concludes, your teams are equipped to maintain and evolve the asset management system as your business changes.

Finding the capability that is already paid for but unused

This section is for the asset manager whose ServiceNow asset module is live but whose reports are still built in spreadsheets, and who wants to know which parts of the module are worth using before buying anything new. Optimization in this context is mostly a matter of sequence. Most organizations have the capability to answer their main questions already. What they lack is a short list of the questions that matter, a clear owner for each, and a rule for which configuration serves which question.

A practical way to start is to write down the five questions the business asks about assets most often, such as what is deployed in a given department, what is out of support, or what is worth recovering through disposal. For each question, record where the answer currently comes from and whether the module answers it without manual work. The gap between those two lists is the optimization backlog. Items with a high business value and low configuration effort go first. Items that need new data sources or new integrations go to a later phase, because they depend on decisions outside the asset team.

Scoring optimization levers against effort and value

The license reclaim row is worth a note. Automating a reclaim before the team has done one by hand usually produces incorrect reclaims, because the rules for what counts as unused are still unsettled. The software license optimization approach covers how to define use before a workflow acts on it.

A sequence for the first optimization cycle

1. Write the five business questions and the current answer source for each, and confirm which ones the module can already answer.
2. Pick two levers from the table that have a low effort score and a clear owner in the business.
3. Define a success test for each lever in terms of a result someone outside the asset team can check.
4. Make the change in a test environment, and run the new output beside the existing one for a full reporting cycle.
5. Retire the old output only after the new one has matched through a month-end, and record the date of retirement.
6. Choose the next two levers from the results, not from the original wish list.

Traps in asset module optimization

The most common trap is adding fields to answer each new question. Every field becomes a thing that someone must fill in, and an asset record with dozens of optional fields is one where most of them are blank. Before adding a field, check whether an existing one, combined with a report, answers the question. The second trap is building reports that look impressive but depend on data that nobody owns. A dashboard showing cost per user is only as good as the cost and assignment data behind it, and that data should have a named steward before the dashboard goes live.

The third trap is treating optimization as finished once the first reports are running. Reports that are not reviewed decay quickly. Each report should have a named reader and a named decision it supports. A report without a decision behind it is a candidate for removal at the next review, and removing unused outputs is itself an optimization. The CMDB data quality rules are a useful reference for the data checks that keep reports credible.

Questions about optimizing an asset module

Should we upgrade the module before optimizing it?

Not as a first step. Optimization should establish which capabilities are missing for real questions. Upgrading first often adds capability that nobody has a use for, while the existing gaps remain.

How do we know which fields to remove?

Look at fill rates over a full year, then check with the people who enter the data. A field that is blank because the process changed may be important again, so removal should follow a conversation rather than a count.

Who should own the optimization backlog?

The asset manager should own it, but each lever needs a business owner for the decision it supports. Without a business owner, a lever can be configured perfectly and still never be used.

When is optimization not the right answer?

When the register is not trusted. Reports built on wrong data simply spread the wrong numbers more widely. In that case, reconcile the core data first, and optimize once the figures can be relied upon.

Next step for an asset module review

Five questions, two levers and a month of parallel running is a sensible first cycle.