Network Asset Lifecycle Tracker

Track source-mapped lifecycle dates, quantity-weighted replacement windows and transparent local priorities across device groups.

Beta · Browser-local planning, not a live EoX database, verified support entitlement or security certification.

1. Assessment and inventory

No current-date assumption. End of Sale (EOS) is not End of Support. EOL below is your retirement planning target, not an announcement date. LDOS is the last support day; today is included. Blank milestone dates remain Unknown.

Each row is a disjoint inventory slice, 1–1000000 units; maximum100 rows. Avoid overlapping quantities. Use site aliases; credentials are unnecessary. Hardware dates do not assess the running software lifecycle.

Only explicit Save stores this tool’s inputs in this browser. Reopen requires fresh analysis. Exports contain entered inventory; no input-derived requests or analytics.

Engineering example results appear here after the method file loads. This is a planning example, not a live inventory.

2. Lifecycle dashboard

Cumulative replacement view — overlapping, do not add

Includes overdue and today. Quantity at Risk is known user-target/support constraints due within3calendar years; unknown deadlines are separate. Missing-date quantity may overlap at-risk.

Mutually exclusive windows — each row counted once

WindowQuantity

Filters and sorting change displayed rows only. All-inventory totals and CSV remain unchanged.

Questions

Does End of Sale mean support has ended?

No. Map exact notice milestones by meaning. This tracker separates sale, user retirement target and last support day; missing support information stays unknown.

Can I add the1/2/3year quantities?

Cumulative cards overlap and must not be added. Use the mutually exclusive buckets to partition all inventory including overdue, today and unknown.

Are manual dates verified automatically?

No. References remain local text. Reconfirm the exact product, support contract and notice revision before execution.

Method, sources and date mapping

Planning date is the earliest known user EOL target or LDOS; End of Sale alone never creates a replacement deadline. Calendar-year boundaries clamp leap day to February28. Local risk rules and recommendations are not vendor security severity.

Base: overdue/today/year1 High; years2–3 Moderate; beyond3 Low; no deadline Unknown. High criticality escalates High→Critical and Moderate→High. Missing any milestone changes Low/Moderate to Unknown; known urgency is retained.

The bounded catalog has2 exact hardware PIDs from1 official amended notice, not worldwide/current EoX coverage. EOL user target remains unknown until entered; inventory counts and software versions are user data.

Engineering method

V2 vendor integration: reserved documentation only; zero active adapters, APIs or background updates.

Engineering workflow

Network Change Planner / MOP — separate execution planning

Related planning

Network Change Planner / MOP — separate execution planning