[Daniel Brooks]

A vendor may call every change a configuration, even when upgrades become difficult. How can a buyer identify the boundary?

[Sofia Bennett]

Accepted answer

Ask whether the change uses supported settings, survives standard upgrades, is covered by normal support, and can be reproduced from documented configuration. Treat custom code, unsupported database changes, unique forks, and vendor-only manual steps as customization with separate ownership, testing, maintenance, security, and exit costs. Record the baseline and require change control. FAR Part 7 supports life-cycle cost analysis, not just first-release cost.

[Ethan Cole]

Community reply

If a vendor supports custom code but charges separately for every upgrade, is that still considered configuration?

[Author]

Posts