The RFP and IT Logistics For Washington's "Pot Czar" 117
Esther Schindler writes "Last fall, the state of Washington passed a marijuana legalization referendum, and needed to acquire an outside consultant to run the program. 'As it normally does, the state put out a request for proposal for a consultant to run the new legal marijuana program,' writes Ron Miller. 'As word leaked out that there was an RFP open for what essentially was a "pot czar," the floodgates opened. It would be the most popular RFP in the state's history. The Liquor Control Board needed a way to process these requests quickly and cheaply.' In a typical RFP scenario, they would get maybe half a dozen responses. This one got close to 100. Miller writes about the cloud workflow required to solve the task: 'He chose these particular tools because they all had open APIs, which allowed him to mash them together easily into the solution. They were easy to use, so reviewers could learn the system with little or no training, and they were mobile, so users could access the system from any device. In particular he wanted reviewers to be able to use the system on a tablet.' I suppose this could have been written about more mundane RFPs, but I bet you'll find this more interesting than most."
Probably not just about pot (Score:5, Insightful)
I imagine this was so popular because of the chance to run a pot legalization program as a consultant. This would be a multi-year job, but Washington State will likely not be the last state to implement this. The consultancy who wins this bid can then bid to help other states in the future, with the only credible claim of reliable experience with this issue. Being the winner of this project would be akin to striking oil.
Huh? This was a problem? (Score:4, Insightful)
Receiving less than a hundred proposals was a problem? Reading simple documents on a tablet and submitting responses was a problem? I fail to see how this required anything more than email and a simple spreadsheet, database, or website.
Re:Probably not just about pot (Score:5, Insightful)
I can't help but think that the pot business now is something like the Internet was circa about 1991. There was a sense it was going to be a big deal and there was going to be a lot of money made, but nobody quite knew how to do it right away.
And like the Internet, I'll be looking back 20 years from now amazed at how much money has been made off it and how it's universally accepted, just like the Internet.
Re:$7800 (Score:5, Insightful)
"Did they really need to create a $7800 (not including license fees) RFP review system when there were only 100 applicants? And now the company that was paid to create it is selling it to other agencies."
My thought too. Looks like Washington is not immune from the typical State bureaucracy syndrome. My guess would be that at least 80% of the responses would weed themselves out in the first couple of paragraphs, which might take maybe a day to go through.
The rest might need more thorough vetting, but hell, that's only 20.
Re:$7800 (Score:5, Insightful)
Can it be used for all future RFP requests? Do the users like it better (more convenient, easier)?
For $7,800, that would be incredible ($10,000 limit I understand, not much for such a project in my opinion). Think about what corporations spend on small IT projects (internally or externally developed).
I'm assuming the developer was familiar with all of the tools and already had ample experience piecing them together. The time frame makes it so.
Re:100?? (Score:4, Insightful)
So big deal, 100... It is not uncommon for a science dept at a university to get 400 applications for a tenure track position.
Or even as many as 420.
Re:Lazy (Score:4, Insightful)
An RFP for a complicated consulting job can be 50 pages long or more with additional addendums and appendixes.
I wrote an RFP for a project with a medical device company and it was 30+ pages.
These are dense pages also. We're basically talking about a draft project plan or business plan. Milestones, deliverables, ROI calculations, tables of data, lists of requirements, software, hardware, etc
100 applications would be at minimum 1000 pages of details.