openstreetmap
Draft an Ops Purchase Policy Document
Taken from Ops call...
"policy for purchasing" document, which currently is focused on specs, and add information such as the process for obtaining approval for purchases.
Some discussion questions
- when do we decide to go ahead with purchasing a machine in budget
- how to handle stuff not decided in the budget process
- what lifespan do we spec the machine for
- how do we decide and approve system specs
As an extension of what I wrote in https://github.com/openstreetmap/operations/issues/1105#issuecomment-2227267807, maybe besides rather obvious RAM upgrades, you could consider adding a section and policy about possible CPU upgrades to servers once affordable refurbished higher end CPUs hit the market, usually about 4-5 years after original release of a processor generation.
I need a purchasing policy that covers who needs to approve what and who we ask at which stage. Predicted lifespan would also be in-scope. I'm not worried about specifying upgrade information in the doc.