Enterprise Module Inventory

What this page is for

Same reporting spine as project Module Inventory, with Site and Plant filters. Use it to see lifecycle mix, Availability Risk, catalog counts, and where a catalog is used — then open a PLC into its project Asset Map for detail.

Tabs

• Catalog rollup — unique catalog numbers across selected sites, with lifecycle status, instance count, sites present, plus Module description and Manufacturer from the Lifecycle CSV.
• By controller (default) — lifecycle cards, Overall Risk Rating, and expandable Site → Plant → PLC table. Each PLC shows Risk %, Risk Rating, and lifecycle counts.
• Where used — search a catalog and see which site / PLC has it; Open jumps to PCS Asset Map with that catalog highlighted.
• Processors — CPU catalog + firmware rollup across sites.

Lifecycle colours

Think of every module as a spare part on a shelf:

• Active — still supported; easy to replace.
• Active Mature — still OK, but aging.
• End of Life (EOL) — winding down; harder to get.
• Discontinued — no longer sold; highest worry for spares.
• Unknown — not matched in the Lifecycle list.

Availability Risk — plain English

One-liner: we score each PLC on how much of its hardware is getting hard to buy or support — not how often it fails today.

Risk % (the percentage)

Of all the modules on this PLC, how much of the “pain” is Discontinued or End of Life?

• Discontinued counts fully (worst).
• End of Life counts about half.
• Active, Active Mature, and Unknown do not add to the percentage (they still show on the cards).

A larger PLC with the same number of bad cards gets a lower % — the problem is spread across more healthy modules.

Risk Rating badge (Low / Medium / High / Critical)

The percentage sets a starting band. Then we apply a safety bump: if a PLC has a lot of Discontinued cards in absolute numbers (10 or more), we raise the rating even if the percentage looks milder.

Why? Because 12 discontinued cards is still 12 things you may struggle to replace — whether the PLC has 50 modules or 100.

Why % and badge can disagree

Example (illustrative numbers only):

• PLC A — 15%, Medium — fewer discontinued cards (under the bump threshold).
• PLC B — 12%, High — slightly lower %, but more discontinued cards (10+), so the rating is raised one band.

Takeaway: percentage = “how bad is the mix?” · badge = “should we worry about this PLC for spares?” — and absolute discontinued count can tip the badge.

Overall Risk Rating (company / site)

Overall Risk Rating = the worst PLC Risk Rating present in the current filter (any Critical PLC → Critical, else any High → High, else any Medium → Medium, else Low). The company / site Risk % figure uses the same formula over all modules in view — informational context beside the overall band.

Calculation

Per PLC (and for the company / site Risk % figure over all modules in view):

Risk Rating bands from Risk %

• Low — under 8%
• Medium — 8% or more
• High — 20% or more
• Critical — 35% or more

Absolute bumps (after the band from %)

• ≥ 10 Discontinued → raise one band
• ≥ 25 Discontinued → raise two bands
• ≥ 40 EOL (and Disc bump not already higher) → raise one band

These bumps use absolute counts, not percentages — that is why a lower Risk % can still show a higher badge.

Training module

Printable 8-slide workshop pack (plain English + formula + worked example + exercises): Enterprise Module Inventory — Training Module. Use Print / PDF for handouts or present fullscreen.

Filters and exports

• Sites in view / Plants in view — tick to include; All sites / All plants toggles. Counts update for the selection.
• Refresh enterprise data — re-runs the SQL Express rollup from included projects.
• Export PDF / Excel — company summary and risk; Catalog CSV/PDF include description and manufacturer when present in Lifecycle.