A Technology Type tells Strategy Overview what a device is. Add its purchase date and Strategy Overview works out when it needs replacing, what that costs, and how healthy it is today.
Map it once. Budgets and grades follow.
Here is one workstation, step by step:
Technology Type: what the device is. You map it once for each configuration type. This one is a Workstation, mapped from your PSA.
Budget class: how long it lasts and what it costs to replace. Each type has a default. This one is on Standard: 4 years, $1,200.
Budget: purchase date plus the class lifespan, at the class cost. It was bought in March 2024, so the budget is $1,200 in March 2028.
End of Life: the lifespan end or the OS end of support, whichever comes first. Windows 10 support ended in October 2025, well before March 2028, so that is its End of Life.
Grade: how close today is to End of Life. That date has passed, so it reads Danger.
Why the budget and the grade can disagree
The budget follows age alone, so this workstation stays budgeted for 2028. The grade also checks the operating system, so it reads Danger today. The answer may be an upgrade, not a new machine.
How the grade is set
Every item gets one End of Life date, and the grade follows how close it is. Warning starts 12 months out by default, and you can change that per type.
Healthy: more than 12 months before End of Life.
Warning: within the last 12 months before End of Life.
Danger: End of Life has passed.
Grade Needed: not enough data to work out a date, usually a missing purchase date.
Getting set up
Map your configuration types. In your integration settings, open Configuration Types, run Auto-Suggest, check each suggestion and save.
Set your budget classes. Enter the lifespan and replacement cost you actually use. Each type has one default class.
Put items on a class. New items land on the default class. Existing items start on the Custom budget class, so select them and apply one.
Check one client first. Confirm their Budget before doing the rest.
When you know better than the data
Budget, Month or Year: type over it and the item moves to the Custom budget class.
Grade or End of Life: set it yourself and it wins until you choose Auto.
One client: override a class for that company, or add a class just for them.
Good to know
The purchase date drives the budget. No purchase date, no replacement year.
OS, memory and warranty never move the budget. The OS can move the grade.
In standalone groups, you set budgets and grades yourself. The next section explains the difference.
Technology Types and standalone groups
Every group in the Technology module is one or the other. A Technology Type works out budgets and grades for you. In a standalone group, you set them yourself.
Configuration types mapped to the same type show as one group in the Technology module, named after the type, and each item keeps its configuration type in a column. Anything that isn't on a type, like cameras, SSL certificates or software licenses, is a standalone group.
| Technology Types | Standalone groups |
Columns | Set by Strategy Overview | You choose them |
Budget | Automatic, by budget class | You enter it |
Grade | Automatic, from End of Life | You set it |
Relating items in the Assessment
Each configuration type stays its own group underneath the type, with all of its columns, even ones the type hides. Relate Managed Workstation or Laptop to an Assessment item, and choose its columns in Settings.
Mapping groups you already have
Nothing moves until you save the mapping. Completed Reports never change.
Their items arrive on the Custom budget class, so existing budgets stay put.
Items on the Custom budget class use the default class lifespan for End of Life.
Grades set by hand stay until you choose Auto.