Why Spreadsheet-Led CMDB Maintenance Fails In Film And Television

4 min read
Last updated on

Spreadsheet-led configuration management fails in film and television because the equipment moves faster than anyone can type. Cameras, routers, encoders and control surfaces are reconfigured for each production, moved between studios, galleries and outside broadcast units, hired in and returned. A spreadsheet records where something was when someone last updated it. The configuration management database (CMDB) built from those spreadsheets inherits every stale row, and the first people to find out are usually engineers trying to work out what's live during a change or an incident.

Key Takeaways

  • Spreadsheet-led configuration management fails in film and television because production equipment is reconfigured and moved faster than anyone can update a record.
  • Each department's list is a working document that was never designed to feed change impact or incident diagnosis.
  • The failure is often a handoff. A status set at goods-in, such as in stock or non-operational, is never updated when the kit goes into service, so live rooms show as empty.
  • Measure drift with three comparisons: lifecycle status against network activity, recorded location against where the equipment answers from, and spreadsheet rows against configuration items.
  • Walk the rooms first, discover lightly in agreed windows with patterns written for broadcast equipment, make installation a step with an owner and record hired kit as a class of its own.
  • Production estates slide back to spreadsheets when the CMDB is slower to update than a shared file, so keep the CMDB quicker and give each department a report rather than a spreadsheet.

Why broadcast and production estates outrun manual records

Most enterprise infrastructure changes through planned projects. Production equipment changes every time a show is set up or struck.

  • Equipment moves between rooms, sites and productions, sometimes weekly.
  • Hired equipment arrives and leaves without passing through normal procurement.
  • Networks are reconfigured for each production, and addresses are reused.
  • Freelance crews set up kit and leave before any record is updated.
  • Different departments keep their own lists, in their own formats.

Each of those lists is someone's working document. None of them was designed to feed change impact or incident diagnosis.

What a broken record chain looks like in practice

At one broadcaster, the chain between procurement, asset management and configuration management had broken down. Equipment that was live and carrying output was recorded in ServiceNow as "in stock" and "non-operational".

Because the equipment wasn't recorded as installed, some production control rooms showed as empty, with no relationships to any service. To anyone reading the CMDB, those rooms weren't live production networks.

They were. A scan of one of those rooms, run on the strength of the records, took it offline during a live broadcast.

No single spreadsheet was to blame. The failure was a handoff: a status set at goods-in that was never updated when the kit went into service.

Finding where your records have drifted

Before replacing anything, measure the drift. Three comparisons show it quickly.

CompareWhat a mismatch means
Lifecycle status against network activityKit recorded as in stock or retired is responding on the network, so it's live
Recorded location against the room it answers fromEquipment has moved without the record following
Spreadsheet rows against configuration items (CIs)Equipment known to one team is missing from the CMDB, or the reverse

Run them room by room, starting with the rooms that carry live output. Any room that shows as empty but has active network addresses goes to the top of the list.

Replacing the spreadsheets without stopping production

Walk the rooms first. For production and control rooms, a physical inventory with the engineers who run them is faster and safer than any scan. Record make, model, network address and function.

Discover lightly where it's safe. Use discovery patterns written for broadcast equipment, with restricted ports, protocols and concurrency, in windows the engineers agree. Keep the status of live kit current from what discovery sees.

Fix the lifecycle handoff. Make "installed" a step with an owner. When kit is deployed, the person deploying it updates status and location, or a discovery result updates it automatically. Status set at goods-in should never be the last word.

Treat hired kit as a class of its own. Record hire equipment when it arrives, with an expected return date, and flag anything still active after that date.

Give departments reports, not spreadsheets. Once the CMDB holds the data, each team gets a filtered view of it. Updates happen in one place.

Holding the line once the CMDB is current

Production estates slide back to spreadsheets when the CMDB is slower to update than a shared file. Keep it quicker.

Provide a simple move request for engineers, with location and status in a few fields. Link production set-up and strike to change records, so the equipment affected is captured as part of the change. Certify each room's contents with its lead engineer on a regular cycle.

Track key performance indicators (KPIs) per room: CIs whose status disagrees with network activity, and days since the room was last certified. Name each room's owner in the RACI (responsible, accountable, consulted, informed) for configuration management.

Our articles on phased discovery rollouts and vulnerability coverage for broadcast equipment go further into safe scanning for this kind of estate.

How Apex helps

We've worked extensively on broadcast estates, including light-touch discovery of production equipment. Our two-week CMDB health baseline scores which CIs are trustworthy and which are guesses, room by room, and shows where lifecycle status disagrees with what's live. The output is a report you can take to your change advisory board.

Our discovery and integration coverage review then establishes what's missing from the estate view and how to bring it in safely. We scope it with you at an initial consultation.

Book a CMDB diagnostic call or arrange a meeting with a consultant.

Frequently asked questions

Can discovery keep up with production equipment moves?

For network-connected kit, discovery can confirm what's live and where it answers from. Physical moves still benefit from a quick manual update at the time.

How should hired equipment be recorded?

As CIs with a hire flag, supplier and expected return date. Anything still active after that date needs a check.

Why is lifecycle status so often wrong?

It's usually set at procurement and never updated when kit is deployed. Make deployment an owned step, or let discovery update status automatically.

Should we scan production rooms at all?

Only after a physical inventory, with restricted, light-touch settings in agreed windows.

Written by Kinga Staniszewska, Apex Configuration Group.

Book a free call to discuss how Apex can help you on your journey to a better CMDB

 

Kinga Staniszewska

By Kinga Staniszewska

Configuration Management Consultant at Apex Configuration Group, based in the Warsaw Metropolitan Area. Kinga specialises in operating the day-to-day processes of configuration management and guiding…

Full profile & credentials →

Get Email Notifications