Buyer's Guide
Buyer's Guide & Sample Requirements for Infrastructure Planning Software
Define the capability before you define the vendor — the requirements that actually differentiate planning platforms, not the feature checkboxes every vendor can claim.
Quick answer. The requirement that separates a real planning platform from a list-maker is true multi-constraint optimization: solving budgets, condition targets, and treatment rules together across the network to produce the strongest defensible multi-year program — not a worst-first, ranked, or benefit-cost-scored worklist. Build your RFP around that, plus open and modifiable models, on-demand scenario comparison, plain-language recommendations, GIS interoperability, and simple SaaS pricing with unlimited users. The sample language below is yours to adapt.
How to use this guide
These are model requirements for an infrastructure planning software RFP — a starting point you adapt to your agency, not a copy-paste contract. Each table below is one requirement area with sample language you can lift into your scope of work and scoring rubric. Every requirement is marked Mandatory or Desirable and paired with a short note on why it matters. The requirements are pavement-first but extensible to other asset classes; add asset-specific sections as supplements.
Anti-bias note for evaluators. These requirements are written to be vendor-neutral and capability-based. They map to the criteria in our how-to-evaluate guide so your scoring rubric and your scope of work stay aligned. Verify any vendor’s response against independent sources and a demonstration on your own data.
Section A — Planning & analysis
These requirements define the core analytical capability — how the system actually arrives at a recommended program and whether your team can run, understand, and defend it. They should carry the most weight in scoring, and A-1 is the one that genuinely separates platforms from list-makers.
| Requirement | Sample RFP language | Priority |
|---|---|---|
| A-1 True multi-constraint optimization | "Describe your recommendation method. Confirm the system performs true multi-constraint optimization — solving budgets, targets, and rules together — rather than year-by-year ranking, prioritization, or benefit-cost scoring of a worklist. Simple ranking, prioritization, or benefit-cost scoring of a worklist shall not be considered equivalent." Why it matters: ranking and prioritization pick from a list; true optimization weighs all constraints at once to find a stronger program from the same budget. | Mandatory |
| A-2 Multi-year scenario comparison | "Proposers shall demonstrate the ability for staff to independently create, compare, and modify at least three multi-year funding scenarios in a single view, including projected condition outcome and cumulative cost of each." Why it matters: lets staff run what-ifs directly, on demand, as budgets and priorities change. | Mandatory |
| A-3 Open, flexible models & formulas | "Describe how cost formulas, deterioration/behavior models, and calculated fields are defined. Confirm they support arbitrary curve shapes, can reference any collected variable, can be created manually or AI-generated, and that the agency can inspect and modify all of them." Why it matters: your data and engineering judgment drive the model — not a vendor's fixed menu of curves — and you can defend every number because you can see it. No unmodifiable "black box." | Mandatory |
| A-4 Plain-language explanation of recommendations | "The system shall produce, for each recommended treatment, a written rationale in plain English suitable for inclusion in public budget documents without manual interpretation by an engineer." Why it matters: answers "why this road and not that one?" defensibly, in language commissioners and residents can read. | Mandatory |
| A-5 Natural-language / AI-assisted planning | "Describe any AI or natural-language capabilities for building plans, searching data, and generating documentation. Indicate whether these are native or sold as a separate module." Why it matters: lets a small team produce and document plans directly, and surfaces which AI is included vs licensed separately. | Desirable |
| A-6 Visual, editable work plans | "The system shall provide an interactive work-planning interface in which staff can reschedule or modify programmed work and immediately see the effect on budget and projected condition, without exporting to a spreadsheet." Why it matters: a plan staff can edit stays current; static PDF outputs are obsolete on delivery. | Mandatory |
GFOA recommends a capital improvement plan cover at least three, and preferably five or more, years. GFOA Multi-Year Capital Planning best practice. MAP-21 requires a risk-based transportation asset management plan for the National Highway System. FHWA asset management (MAP-21).
Section B — Data, configuration & interoperability
These requirements ensure the system fits your data and your existing environment. The planning layer should configure to your ratings and rules, and work alongside the GIS and asset systems you already run — not force a rip-and-replace.
| Requirement | Sample RFP language | Priority |
|---|---|---|
| B-1 Configurable data model & condition scales | "Describe how the agency configures condition indices, fields, and rules. Confirm new fields and condition scales can be added without custom development." Why it matters: your ratings and rules, your way — with room to grow into other asset classes later. | Mandatory |
| B-2 Works alongside existing GIS & asset systems | "The selected solution shall integrate with the agency's existing GIS and asset data sources (e.g., Esri, PAVER/MicroPAVER, EAM/CMMS) and shall not require decommissioning current maintenance-management systems as a condition of use." Why it matters: no rip-and-replace; adopt for planning without disrupting operations. | Mandatory |
| B-3 Built-in maps & reporting | "Describe the system's native mapping and reporting. Can non-GIS staff produce a public-meeting condition map and a finance-ready program summary directly from current data?" Why it matters: frees the program from depending on scarce GIS staff for routine outputs. | Desirable |
Section C — Security, records & platform
These requirements cover the obligations that come with government spending decisions — auditability, public records, security, recovery, and data ownership — plus whether the platform is one your staff can actually use. Require truthful, evidenced status rather than claimed certifications.
| Requirement | Sample RFP language | Priority |
|---|---|---|
| C-1 Audit trail & role-based access | "The system shall log all data and plan modifications with user, timestamp, and change detail, and shall support role-based permissions and public-records retention requirements." Why it matters: public-records and accountability requirements for government spending decisions. | Mandatory |
| C-2 Security, disaster recovery & data ownership | "Describe your security controls, backup and disaster-recovery approach (including recovery objectives), and confirm the agency owns its data and may export it in full, in open formats, at any time and at no additional cost." Why it matters: sound SaaS security, a real recovery plan, and data you own and can take with you. | Mandatory |
| C-3 Modern web platform & usability | "Describe the platform architecture (web vs. installed desktop client) and the typical training time for a non-engineer to independently produce a multi-year plan." Why it matters: tools staff can use independently get used — and a plan only delivers value if it stays current. | Desirable |
For how InfraMind approaches these areas, see our security and accessibility pages.
Section D — Commercial
The commercial requirement keeps the deal predictable and the path to value short — so a capable product doesn't stall on per-seat math or a vague implementation timeline after award.
| Requirement | Sample RFP language | Priority |
|---|---|---|
| D-1 Simple SaaS pricing with unlimited users | "Provide a simple annual subscription price that includes unlimited users, hosting, updates, and support, and state the elapsed time from contract to the agency's first usable multi-year plan." Why it matters: predictable budgeting and broad staff access, with no per-seat math and a fast path to a usable plan. | Mandatory |
Pair this with how to buy. Once your requirements are set, see how to buy for how InfraMind is procured directly — by quote or RFP response. To justify the purchase internally, use the business case for capital planning software.
Questions to ask any vendor
The answers to these reveal more than any feature list. Ask them in the demo, on your own data, and listen for whether the vendor describes a real capability or talks around it.
- Is your recommendation engine true multi-constraint optimization, or ranking / prioritization / benefit-cost scoring?
- Can we see and change the deterioration models, formulas, and treatment rules behind a recommendation?
- Does pricing include unlimited users, or are there per-seat fees?
- How long from signature to our first usable multi-year plan, and who does the work?
- Is this a modern web platform, and how long to train a non-engineer?
- Can a non-GIS staffer produce a public-meeting map and a finance summary from today's data?
Vendor evaluation scorecard
A weighted scorecard keeps the evaluation honest — it forces the panel to spend its points on the capabilities that actually differentiate platforms. The weights below reflect that priority order; treat them as a starting point.
| Evaluation criterion | Weight |
|---|---|
| True multi-constraint optimization | 20% |
| Open / flexible models & formulas | 15% |
| Multi-year scenario comparison | 10% |
| Plain-language defensible recommendations | 10% |
| Visual, live-editable work plans | 10% |
| Configurable data model & GIS interoperability | 10% |
| Natural-language / AI-assisted planning | 5% |
| Security / DR / data ownership | 10% |
| Simple SaaS pricing & time-to-first-plan | 10% |
Note: adjust the weights to your priorities.
Frequently asked questions
Want this scoped to your network?
Send us the asset classes and systems in scope and we'll help you tailor these requirements — and show how InfraMind responds to each one, on your own data — on a working demo.