Writing RFPs is much more than procuring a technology system. A good RFP has captured the needs of the stakeholders (field users, dispatch operators, maintainers, support teams, fiduciaries, board members, etc.) that are impacted by the system of interest and has identified the supporting systems and their level of impact. The RFP sets the stage for the contracted agreement between parties, it defines the initial set of requirements, and outlines how the project should be implemented, transitioned, and managed. By applying a systems engineering mentality, it makes the process of RFP development easier by utilizing a checklist mentality to ensuring all bits are considered and captured.