Create a searchable repository for RFQs
The first thing I do when I have to issue a new RFQ is look for someone that has recently had a similar requirement so I can use their SOW and technical requirements as a template. So much effort is wasted on writing and rewriting statements of work, getting SMEs to provide technical specs - all for something that has already been purchased by the government probably numerous times. How many RFQs for web hosting services have been written - does each have to be a completely new effort?
This would be as easy as taking the publicly available RFQs and depositing them into a cloud storage solution and making them searchable. Eventually, you could even have ratings from government personnel or even vendors on the quality of the RFQs in the repository.
3 comments
-
Joel Worst
commented
More replicated content just means more infrastructure, applications, interfaces, newly funded mgmt groups, data input error and people forced to use it. Also personal judgment calls on what goes in, and what doesn't. As You put it, Mr. Tuttle, the differing needs of divisions within organizations within Agencies can't know what any other Agency entities would consider useful. Plus, requiring Your personnel to manually access one more application to post dumb data that just sits waiting for someone to manually search and pull it isn't collaboration or knowledge transfer. It turns into something more like "what You're going to find out, is all I'm going to tell You".
*Proposal: Automating content awareness based on its metadata and its evolving context based use is one approach. Software data integration frameworks [not data fusion, cuz we don't want new infrastructure, systems, and training for personnel(COST)] can automate data discovery and awareness real-time delivering only metadata (info about content) so the created data always lives with its creator(best data integrity). The framework builds a single automated intelligent real-time information space of discoverable content through extending the reachable self-healing network to infinite nodes in each of their differing domains. Automated smart push/pull brings content to one's attention based on their specific need, role, or mission. If this content is used in that specific situation, the metadata is automatically updated. This provides greater context (what the content means to probable users) and is now smart push/pulled based on new profile needs requiring that knowledge. And then the Terminator said "I'll be Back"… WOW. Sorry for the rant. This is the field in which I work. And I tell You the problem with Transparency is, it isn't. Even when that's the first order of business or mandate, at some point it's always gonna get to "what You're going to find out, is all I'm going to tell You". Thoughts? -
David Shumway
commented
This works on the Industry Side too. Nobody likes to reinvent the wheel and if one has information previously used, all the better.
-
Hal Good, CPPO
commented
Professional organizations serving state and local government (example NIGP) already do this. It is a great resource. One can analyze the best of RFOs others have developed and refine the requirements to fit the specific procurement.
