Build the renewal budget
Give finance a year-by-year forecast of what must be replaced and what it costs, with a running total, instead of a spreadsheet rebuilt every autumn.
A vendor milestone should not become a budget emergency. ConnectMyAssets is a tool for EoL EoS management, built to manage end of life network equipment and end of support across your estate: you keep the lifecycle catalogue (entered by hand or imported from CSV), every device gets its status, the replacement is priced in your currency and spread over the coming years, and Soron warns you before each date with the lead time you choose.
Request a demoGive finance a year-by-year forecast of what must be replaced and what it costs, with a running total, instead of a spreadsheet rebuilt every autumn.
Devices past their end of support receive no more security fixes. Find them all, see where they are and replace the most exposed first, with the vulnerabilities of each device in view.
NIS2, ISO 27001 and DORA reviews ask how unsupported hardware is tracked. Show the statuses, the dates and their source, and the renewal plan.
The catalogue belongs to a group of network devices and is inherited below: a region or an MSP customer can carry its own dates and price where you allow it.
The EoL/EoS module connects the lifecycle of your hardware models with your inventory. See which devices are out of support, which soon will be, what replacing them costs and in which year to plan it.
Enter end-of-support and end-of-life dates per model or per family of models (all the models starting with C9300-, for example), with the replacement model, its unit price and a note on where the dates come from. Before saving, the form shows which models and how many devices the entry covers.
Import the catalogue from a CSV file prepared from your vendors’ announcements: a dry run checks every line and names the ones in error before anything is written. Export it, edit it in a spreadsheet and import it again.
Each device gets its status (end of life, end of support, approaching, supported or unknown) on its page and in the CMDB, as a column and a filter. The list of models without a date, the most devices first, tells you what to fill in next.
The estimated budget multiplies the replacement unit price by the number of devices to replace, in the currency you set for ConnectMyAssets. It also says how many devices the estimate leaves out for lack of a price.
The forecast books each device in the year of its end of life (or of its end of support when no end of life is known), over 1 to 15 years, with the budget of each year and the running total. A date already past is booked in the current year as overdue.
Export the renewal plan to CSV: one line per group and model, with the year, the devices, the replacement, its unit price and the cost, ready for budget discussions and purchase orders.
Get a Soron alert for each device whose end of support or end of life falls within the number of days you choose, or is already past. Notify the right team in-app, by e-mail, syslog or webhook.
A lifecycle entry belongs to a group and applies to every group below. Where you allow it, a sub-group can hide an entry and enter its own dates and price; each device page says which entry it reads and from which group.
A lifecycle entry matches the model each device reports at its SSH collection, exactly, or every model starting with the text of a family. The nearest group wins, then the model’s own entry, then the longest family.
The catalogue starts empty and nothing is downloaded: dates vary with contracts and vendor terminology, so you enter them, with a note on their source.
A device is “approaching” when its next date falls within the window (365 days by default, from 30 to 1 825). Devices approaching or past a date are the ones the budget counts.
Reading and editing the catalogue are permissions per group of network devices: each team sees the figures of its scope only, and the report follows the scope chosen in the header.
Enter or import the lifecycle dates of your models, starting with the models without a date.
Find the affected devices and their status in the report and the CMDB.
Price the replacements and spread them by year.
Export the plan, organise the replacements and let Soron warn you before each date.
Prepare your project and define your scope.
End of support (EoS) is the day the vendor stops supporting the hardware, including security fixes. End of life (EoL) is the day it must be out of your network. ConnectMyAssets keeps both dates per model and gives every device the status that follows.
From you. You enter the milestones published by your vendors for each model or family of models, or import them from a CSV file, with a note on their source. You keep control of dates that vary with contracts and vendor terminology.
It computes an estimated budget (replacement unit price times the number of devices, in your currency) and a yearly forecast over 1 to 15 years, and exports a renewal plan to CSV. It also tells you how many devices the estimate leaves out for lack of a price, so your decisions rest on complete figures.
Yes. The Soron rule “end of life or support approaching” raises an alert for each device whose date falls within the number of days you set, or is already past, per group of network devices, with notifications in-app, by e-mail, syslog or webhook.
No: a software update and hardware renewal address different decisions. EoL/EoS management helps plan the replacement of devices; firmware management helps track versions and run upgrade campaigns on the devices that stay.
See what ConnectMyAssets can change for your team. On your infrastructure, with your requirements.
Request a demo