Government Administration · ServiceNow

How the Library of Congress Brought IT Planning and Demand Management Together in ServiceNow

The Library of Congress wanted cleaner technology asset data and a better handle on IT demand. We improved its Technical Reference Model and Demand Management and connected both to the ServiceNow ITSM setup it already runs.

Outcome Highlights

  • Cleaner asset data

    vendor and technology asset information that's better structured and more accurate

  • Stronger IT governance

    a firmer grip on how IT demand moves from request to decision

  • One ServiceNow environment

    TRM, Demand Management and ITSM working as a unit

  • A demand backlog cleared

    open Demand Management items addressed, with a better user experience

Project at a Glance

Client
Library of Congress
Industry
Government Administration
Platform
ServiceNow (ITSM, Technical Reference Model and Demand Management)
Integrations
The Library's existing ServiceNow ITSM systems
Services
Our team covered TRM enhancements, Demand Management improvements and integration with ITSM

Summary

The Library of Congress is the research library of the U.S. Congress and the largest library in the world. Behind it sits a big IT operation, and the Library already ran that operation on ServiceNow. It wanted more from the platform. IT planning needed more automation, technology asset data needed to be consistent, and demand requests needed a clearer path from start to finish.

Stack Intelligence enhanced the Library's Technical Reference Model (TRM) to categorize and normalize IT asset data. We also worked through the Demand Management backlog, improved how the module works for its users and connected TRM and Demand Management to the Library's ServiceNow ITSM systems.

The Challenge

The Library didn't need a new platform. It needed the one it had to do more.

  • IT planning took too much manual work.

    Planning needed more automation inside ServiceNow.

  • Asset data wasn't consistent.

    Technology and vendor information had to be categorized and normalized before anyone could rely on it.

  • Demand management needed tightening.

    Requests needed a stronger lifecycle, and the Demand Management module had a backlog of open items.

  • Pieces of ServiceNow sat apart.

    TRM and Demand Management needed to connect with the ITSM systems already in place.

Our Approach

We worked inside the Library's existing ServiceNow environment, improving what was there and connecting it, so nothing had to be rebuilt from scratch.

What we built

  1. 01

    An enhanced Technical Reference Model.

    The TRM now categorizes and normalizes IT asset data, so vendor and technology records follow one structure.

  2. 02

    A better Demand Management module.

    We cleared backlog items and improved the user experience for the people submitting and reviewing demand.

  3. 03

    Connected ITSM.

    TRM and Demand Management now tie into the Library's existing ServiceNow ITSM systems, giving IT operations one environment to work from.

Tech Stack

  • ServiceNow
  • ITSM
  • Technical Reference Model
  • Demand Management

FAQs

A TRM is a catalog of the technologies an organization uses, organized into categories so asset and vendor data follows one standard. At the Library of Congress, the enhanced TRM categorizes and normalizes IT asset data.

It tracks IT requests from the first idea through review and decision, so leaders can see what's being asked for and prioritize it. At the Library of Congress, we cleared the module's backlog and improved its user experience.

Yes. As an enterprise software consulting firm, our team takes on ServiceNow work too. For the Library of Congress, that meant improving TRM and Demand Management and connecting both to ServiceNow ITSM.

Want More Out of the ServiceNow Platform You Already Have?

Where does your IT team still rely on manual planning or messy asset data? We'll show you how ServiceNow TRM and Demand Management could tighten it up.