ServiceNow Asset Management Managed Support

What a Managed Support Engagement for Asset Management Covers

A managed support engagement for ServiceNow Asset Management with Oblytech provides ongoing oversight of your asset data and processes. We monitor data quality: are new assets being added correctly, are decommissioned assets being retired on time, are asset records kept current with actual infrastructure changes. We track metrics: asset aging, licence compliance, unmanaged hardware and orphaned assets. We provide a dedicated contact for questions about asset configuration, best practices or when issues arise. We perform quarterly reviews with your team to identify gaps and plan improvements.

Managed support includes access to our Asset Management expertise. If hardware vendors change, we advise on configuration updates. If audit findings identify asset tracking gaps, we help you address them. If licence compliance creates questions, we guide your team on best practices and configuration. The engagement ensures your asset management stays effective as your infrastructure evolves.

Typical Starting Problems and Data Challenges

Many organisations discover that their asset database does not match reality. Inventory shows servers that were decommissioned years ago still listed. Newly purchased hardware sits in inventory not yet added to ServiceNow. Asset costs are estimated guesses rather than actual purchase prices. Depreciation schedules are not consistently applied. When auditors ask about asset ownership and cost, the data is not reliable.

Hardware lifecycle includes retirement. When equipment reaches end-of-life, costs to maintain might exceed replacement costs. Depreciation schedules inform when replacement should be planned. Asset Management tracks this so you do not end up operating expensive equipment past its useful life.

For equipment on warranty, track warranty coverage. When warranty expires, you must decide whether to purchase extended support or accept the risk of unplanned outages. Tracking warranty dates ensures these decisions are made proactively rather than reactively when failures occur.

Another common problem is silos: hardware is tracked in one system, software licences in another, cloud resources in a third. ServiceNow CMDB tracks running configurations but does not always align with financial asset records. Reconciliation between systems is manual and occurs rarely. Managed support breaks down these silos and ensures asset data is consistent and authoritative.

Data Quality Monitoring and Reconciliation

We set up automated checks to detect data quality issues. Assets without a location are flagged. Hardware past end-of-support dates are highlighted. Licences nearing renewal are identified. These checks run regularly and alert your team to problems. We perform quarterly audits of high-value asset categories to ensure records match physical reality. We work with your procurement and finance teams to ensure newly purchased hardware is added to ServiceNow promptly and with correct financial data.

Reconciliation with upstream systems is ongoing. If hardware is purchased, we ensure it appears in asset records with correct cost and depreciation schedule. If software is inventoried separately, we help sync licensing data to asset records. If cloud consumption is tracked elsewhere, we advise on how to represent cloud assets in ServiceNow depending on your licensing and financial requirements.

Hardware and Software Lifecycle Tracking

Effective asset management requires understanding lifecycle: when hardware was purchased, when end-of-support occurs, when end-of-life is reached and when it should be retired. We configure ServiceNow to track these milestones. Lifecycle rules can automatically update asset status: from active to aging to end-of-support to retired. Alerts notify teams when servers approach end-of-support so replacement can be planned before support expires.

Software lifecycle is managed similarly. Licence expiry dates are tracked. When a licence nears expiry, it is flagged for renewal. If a licence expires, the software is marked unsupported. This drives renewal or software replacement decisions. Tracking licence status across thousands of installations is manual without good data; ServiceNow makes it manageable.

Compliance and Audit Support

Auditors often request proof of asset ownership and cost. With good data, you can generate reports showing what you own, when it was purchased, cost basis and depreciation schedule. We help you prepare for audits by ensuring asset records are complete and defensible. We work with your internal audit and compliance teams to understand what documentation auditors expect and ensure ServiceNow contains that information.

Licence compliance is a common audit focus. Software vendors audit customer usage to verify you are licensed for the quantity and versions you use. Good asset tracking makes licence audits straightforward: you can demonstrate exactly which software is installed where and confirm you are within your licence terms. Without this data, compliance becomes painful and risky.

Continuous Improvement and Strategic Planning

Asset data supports strategic planning. By tracking hardware age and end-of-support dates, you can forecast capital expenditure: when will a large percentage of your servers need replacement. By tracking licence expirations, you can plan renewal budgets. By tracking cloud spending, you can optimise subscriptions and negotiate vendor contracts based on usage patterns. Managed support helps you use asset data strategically, not just for compliance.

Handling asset requests as a service with clear approvals

This section is for the service owner who receives a steady flow of asset requests, such as a new laptop for a starter, a loan device for a contractor or a license reassignment, and who wants those requests to update the register without manual rework. Under managed support, most of the day-to-day value comes from how each request type is defined. A request that changes ownership, a request that changes financial value and a request that only changes a note need different approvals and different evidence, and treating them alike is the usual reason the register drifts.

Each request type should answer four questions before it goes live: who may ask for it, who approves it, which record fields it changes, and what evidence closes it. A new device request, for example, changes the lifecycle status, the assigned user and sometimes the cost center. A reassignment changes the owner and the location only. Writing these down as separate catalog items, rather than one generic asset form, keeps the audit trail readable. The catalog request eligibility guidance covers how to decide who can see each item in the first place.

Request types, approvers and record changes

The correction row is deliberately light. Forcing a full approval for a typo teaches people to avoid the process, and then the register is changed through side routes that nobody records. Where the change touches value or ownership, the approval should be heavier, and the table makes that proportion visible to requesters.

Running the monthly operating review

1. Review requests that have been open longer than the service owner’s agreed limit, and identify which approver is holding each one.
2. Check the list of devices with status changes that did not go through a catalog request, since these point to informal routes.
3. Compare the count of assets by status with the physical or network evidence for a rotating sample of locations.
4. Look for loan devices past their return date and assign a named person to chase each one.
5. Review the disposal queue against finance records, so that assets sent for disposal are removed from the register only when the certificate is on file.
6. Record decisions and open actions in a short note, and send it to the approvers so the next review starts from a shared position.

What goes wrong in managed asset request services

The first failure is an approval chain that sends every request to one busy manager. Requests then wait, requesters create workarounds, and the register loses the link between what was asked for and what was delivered. Distributing approval by cost center or request type removes the bottleneck, provided each approver knows what they are approving. The second failure is a service that closes requests when the paperwork is complete rather than when the record is right. A request can be approved, fulfilled and closed while the asset still shows the previous owner. Closure should check the record, not only the ticket.

The third failure is an operating review that reports on ticket volume without looking at the register itself. Volume measures how busy the team is, but the register is what the business relies on. The review should always include at least one check of the data against evidence, so the service owner knows whether the requests are producing accurate results. The audit trail evidence guidance covers what should be kept for that purpose.

Questions service owners ask about asset request services

Should every asset change go through a request?

No. Automated changes from discovery and approved imports should update the register directly, and the request route is for changes that a person decides. Mixing the two creates noise in the approvals and hides the changes that really need a decision.

What do we do when a requester refuses to use the form?

Find out why before enforcing the rule. Often the form asks for information the requester does not have, or the catalog item does not match their situation. Fixing the form is usually faster than disciplining the requester, and it avoids a backlog of side requests.

How should loan devices be tracked when the borrower leaves early?

The leaver process should trigger a check for any assets assigned to that person, including loan devices. The asset record should show the return as pending until the device is physically received, and it should not be closed on the basis of an email.

Who should own the monthly review?

The service owner should chair it, with a finance contact and a representative from the asset team. Without finance in the room, the review tends to focus on operational tidiness and misses value and disposal issues.

Next step for running asset requests as a service

A request catalog is easiest to fix while it is still small.