Contracting: Interior's path to Drupal in the Cloud (v2.0)
The purpose of this track is two-fold - one angle helps you to understand the advantages of Drupal from an organizational leadership angle and the other is to highlight the great Drupal sites and projects you're working on and to show what's possible. These sessions are business focused, and will be non-technical.
Once upon a time (2009), a consulting group estimated that producing a new (awesome) DOI.gov web presence would cost a bit more than $11 million. Naturally, we didn't take their recommended path. Instead (after a few years of research, conversation and negotiation), we awarded a contract for platform-as-a-service cloud hosting and Drupal architecture for all of the Department's bureaus (10) and offices (many). We arranged for new designs and migrated DOI.gov to the new platform. BSEE.gov is under construction.
We still haven't hit the $1 million mark.
Follow the long and winding road from research, through internal politics, in (and out and back in again) to the core acquisitions process and finally an award.
Learn from our mistakes (yes, we made them), our lucky guesses (there were a few), and even the occasional wisdom.
Ask us lots of questions.
The three speakers for the proposed Drupal GovCon session are the primary actors for the process: DOI's Director of Digital Strategy, Tim Fullerton, and Deputy Director Larry Gillick, plus OCIO adviser-in-chief Andrew Havely.
Feel free to check out this auto-archived video from a live presentation we did in late 2014, Interior's New Web Platform.
UPDATE: Find out what happens when your PaaS reaches contractual capacity, when you goof on an IGE, and when you really (really) want HTTPS and there's no contract vehicle in place.